> Although I am relatively new to Linux, I have done kernel upgrades in > the past without a problem. I cannot figure out what is going wrong > this time! My system is using mkinitrd from the mkintrd-2.6-1 RPM. > Does anyone have any suggestions how to overcome this last hurdle in > the kernel upgade? Run "modprobe loop" then try it again. While the devices may physically exist in /dev, it may be the case that there is no kernel support for them and running modprobe will trigger the kernel to load the device support for it. Afterwards, running "dmesg" should show something along the lines of: loop: registered device at major 7 Regards, Dave _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
- Re: (no subject) Wolfgang Pfeiffer
- (no subject) shoe
- RE: (no subject) Burke, Thomas G.
- (no subject) Raja
- (no subject) Mobeen Azhar
- Re: (no subject) Mikkel L. Ellertson
- Kernel upgrade from 2.2.16 to 2.2.17 Mobeen Azhar
- RE: Kernel upgrade from 2.2.16 to 2.2.1... Eddie Strohmier
- RE: Kernel upgrade from 2.2.16 to 2... Eddie Strohmier
- RE: Kernel upgrade from 2.2.16... Mobeen Azhar
- routing problem after dropping PPP connection Dave Wreski
- routing problem after dropping PPP connecti... Paul Greene
- (no subject) Xin Zhao
- RPM dependencey problem, was: Re: (no subject) Dave Reed
- Re: RPM dependencey problem, was: Re: (no s... Trond Eivind Glomsrød
- Re: RPM dependencey problem, was: Re: (... Xin Zhao
- Re: RPM dependencey problem, was: R... Trond Eivind Glomsrød
- Re: (no subject) Statux
- Re: (no subject) Mikkel L. Ellertson
- Re: (no subject) John Aldrich
- Re: (no subject) Michael Burger