--
make me
---
make: *** No rule to make target `me'. Stop.
2.4.14 built okay for me, but I find that I can no longer mount a loop
filesystem any longer. If I try to load the loop module manually, it
produces the following message:
# insmod loop
Using /lib/modules/2.4.14-1/kernel/drivers/block/loop.o
/lib/modules/2.4.14-1/kernel/drivers/block/loop.o: unresolved symbol deactivate_page
--
---------------------------------------------------------------------------
Michael | mfaurot | The groundhog is like most other prophets; it delivers
Faurot | atww.org | its message and then disappears.
Thats a bit odd Jonathon, but lenmme see what ythe bottom of my lastQuote:>2.4.14 won't compile for me. It appears that the function
>deactivate_page was removed or renamed in 2.4.14, but a reference to it
>wasn't removed from drivers/block/loop.c.
I get a failure at the "ld this and that >vmlinux" stage, and its
reported as being in drivers/block/block.o, but thats the same variable
name as is being reported here, deactivate_page.
Cheers, Gene
--
Gene Heskett, CET, UHK |Amiga A2k Zeus040, 70MB ram, 31 gigs
email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
<http://www.iolinc.net/gene_heskett>
This messages reply content, but not any previously quoted material,
is ? 2001 by Gene Heskett, all rights reserved.
--
> > 2.4.14 won't compile for me. It appears that the function
> > deactivate_page was removed or renamed in 2.4.14, but a reference to it
> > wasn't removed from drivers/block/loop.c.
> Go to drivers/block/loop.c
> Delete the two deactivate_page(page); lines ( or comment them out ).
--
Kasper Dupont
>> > 2.4.14 won't compile for me. It appears that the function
>> > deactivate_page was removed or renamed in 2.4.14, but a reference to it
>> > wasn't removed from drivers/block/loop.c.
>> Go to drivers/block/loop.c
>> Delete the two deactivate_page(page); lines ( or comment them out ).
>How can we be sure that removing the calls will not break anything?
Temporarily, I suspect it will build if in the 'make xconfig' one were to
turn off the loopback device. I intend to try that tonight as I just
had 2.4.13-ac6 totally loose track of its cache after I had mounted a
previously unmounted reiserfs partition. I noticed that the MEM bar of
xosview was full width of its window, and a free reported I had the
magic 4gigs number for a cache buffer. Obviously, reboot, and again after I
turn the tmpfs stuff on, which accidently got cleared in that config.
Cheers, Gene
--
Gene Heskett, CET, UHK |Amiga A2k Zeus040, 70MB ram, 31 gigs
email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
<http://www.iolinc.net/gene_heskett>
This messages reply content, but not any previously quoted material,
is ? 2001 by Gene Heskett, all rights reserved.
--
I believe that if you compile the driver in the kernel you get this at
build time. Same problem, just bites you a bit later. I would have
expected depmod to notice this, but I don't really have a list of what
it finds and doesn't. Or perhaps it did and you didn't notice when you
installed the modules?
--
His first management concern is not solving the problem, but covering
his ass. If he lived in the middle ages he'd wear his codpiece backward.
How do you run mkinitrd if you don't have a loop device? Isn't 2.4.xQuote:>Temporarily, I suspect it will build if in the 'make xconfig' one were to
>turn off the loopback device. I intend to try that tonight as I just
>had 2.4.13-ac6 totally loose track of its cache after I had mounted a
>previously unmounted reiserfs partition. I noticed that the MEM bar of
>xosview was full width of its window, and a free reported I had the
>magic 4gigs number for a cache buffer. Obviously, reboot, and again after I
>turn the tmpfs stuff on, which accidently got cleared in that config.
<snip>Quote:> >> Go to drivers/block/loop.c
> >> Delete the two deactivate_page(page); lines ( or comment them out ).
> >How can we be sure that removing the calls will not break anything?
I think we don't have to remove anything, the changes are in
linux/mm/swap.c. The
function activate_page is still there, but the reverse function
deactivate_page was
removed from this source. The code for activate_page hasn't change, so
when the
original code fro deactivate_page is inserted in swap.c (i've copied
this piece of code
from the 2.4.13 source-tree), the compiler returns no errors and also
loopback mounts are working.
Bernd
As to what happened to 2.4.13-ac6 that caused it to suddenly think I
had -4.127etc gigs of memory, I have no idea.
Cheers, Gene
--
Gene Heskett, CET, UHK |Amiga A2k Zeus040, 70MB ram, 31 gigs
email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
<http://www.iolinc.net/gene_heskett>
This messages reply content, but not any previously quoted material,
is ? 2001 by Gene Heskett, all rights reserved.
--
>> >How can we be sure that removing the calls will not break
>> >anything?
> <snip>
> I think we don't have to remove anything, the changes are in
> linux/mm/swap.c. The
> function activate_page is still there, but the reverse function
> deactivate_page was
> removed from this source. The code for activate_page hasn't
> change, so when the
> original code fro deactivate_page is inserted in swap.c (i've
> copied this piece of code
> from the 2.4.13 source-tree), the compiler returns no errors
> and also loopback mounts are working.
> Bernd
kernel.org/pub/linux/kernel/people/axboe/patches/v2.5/2.5.1-pre4/bio-pre4-1
should make it work again, feedback is welcome.
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
3. 2.4.14 doesn't compile: deactivate_page not defined in loop.c
4. IPC with pipes. Cannot Read!
5. problem with kernel 2.4.14 drivers/block/loop.c mm/swap.c
6. Automounting on Solaris 2.4 with NIS+
7. 2.4.14 is missing deactivate_page, needed by loop.o
9. Kernel 2.4.14 compile fail (block.o)
10. Unwanted Swapping in 2.4.14-pre8, no swapping in 2.4.14-pre6aa1
11. SB 5.1 driver doesn't load, kernel 2.4.14
12. Memory accounting problem in 2.4.13, 2.4.14pre, and possibly 2.4.14
13. 2.4.14-pre8: 'free' still reports bogus 'cached' value.