ews
suggesting that this might solve the problem- it doesn't, in my case),
while the cdrom and the iso9660 filesys are set up as modules.
These messages sometimes fill up an entire screen- but more than being
an annoyance that I'd like to solve, I wonder why they're occuring.
Thanks!
John Maheu wrote:
>
[snip]
> I just had a similar experience with 2.0.33 and fs.
>
> It could be that module dependences where not calculated when you
> rebooted.
> Check to see if /lib/modules/2.0.32/modules.dep exists.
> If not run depmod -a in /lib/modules/2.0.32
Thanks! That did the trick...d
Ben Pfaff wrote:
>
>After compiling a more modularized kernel today (using Debian 1.3.1 with
>kernel src 2.0.32) I've lost my cdrom- everything was working perfectly
>with the bloated standard kernel...
>When I try "mount -t iso9660 /dev/scd0 /cdrom" I see something like "fs
>t
tly in, not as modules.
I'm attaching my /usr/src/linux/.config- I can't figure out why things
aren't working! (I apologize for the length of this post)
Any hints would be appreciated...
Thanks!
John Szumowski
[EMAIL PROTECTED]
#
# Automatically generated by make menuconfig:
4 matches
Mail list logo