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
On Sat, 21 Mar 1998, John Szumowski wrote:
> [cc'd to debian-user mailing list]
>
> 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 iso
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
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
type iso9660 not supported by k
[cc'd to debian-user mailing list]
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
type iso96
5 matches
Mail list logo