Hello Everyone,
Some time back I read a message about this error showing up when Ubuntu was booted live. I cannot recollect whether it was on this list or elsewhere else. However today at a client's place when I tried Kubuntu 8.04 + KDE4 live on an unbranded Intel 865G mobo, it showed the same error lines after the initial kernel loading. After a second try, I let it move further and after 4 or 5 lines of the error, it booted further normally and brought the desktop up. One very good advantage of 8.04 is that NTFS partitions can be directly viewed in the GUI file browser (Dolphin) with write access. So it is ideal for taking backups from NTFS partitions to other NTFS partitions....something that was a PITA till now.
On Wed, May 14, 2008 at 11:41 PM, Rony gnulinuxist@gmail.com wrote:
Hello Everyone,
Some time back I read a message about this error showing up when Ubuntu was booted live. I cannot recollect whether it was on this list or elsewhere else.
Yeah that error was encountered by me, not only with live cd but also live usb, in both kubuntu and ubuntu.
However today at a client's place when I tried Kubuntu
8.04 + KDE4 live on an unbranded Intel 865G mobo,
This error was due to the floppy drive. mine is intel 915 mobo. previously when i was trying to install or even boot the error was coming. but after when i connected my floppy drive. the error disappeared...Dont why this happned? Does new dapper requires floppy drive to boot?
mukesh yadav wrote:
On Wed, May 14, 2008 at 11:41 PM, Rony gnulinuxist@gmail.com wrote:
However today at a client's place when I tried Kubuntu
8.04 + KDE4 live on an unbranded Intel 865G mobo,
This error was due to the floppy drive. mine is intel 915 mobo. previously when i was trying to install or even boot the error was coming. but after when i connected my floppy drive. the error disappeared...Dont why this happned? Does new dapper requires floppy drive to boot?
It may be some entry in the BIOS that causes this but the error lines will disappear after 4 or 5 times and the booting will progress further. So if anyone encounters this error, just wait a little longer till the process moves further.
It may be some entry in the BIOS that causes this but the error lines will disappear after 4 or 5 times and the booting will progress further. So if anyone encounters this error, just wait a little longer till the process moves further.
yeah may be right but when I tried to install in that error.... installer gave me error that there is Read/write problem in my hard disk.
but when i reconnected the floppy drive it worked fine.
mukesh yadav wrote:
It may be some entry in the BIOS that causes this but the error lines will disappear after 4 or 5 times and the booting will progress further. So if anyone encounters this error, just wait a little longer till the process moves further.
yeah may be right but when I tried to install in that error.... installer gave me error that there is Read/write problem in my hard disk.
but when i reconnected the floppy drive it worked fine.
AFAIR the error that you mentioned was for fd0 not cdrom.
mukesh yadav wrote:
This error was due to the floppy drive. mine is intel 915 mobo. previously when i was trying to install or even boot the error was coming. but after when i connected my floppy drive. the error disappeared...Dont why this happned? Does new dapper requires floppy drive to boot?
I recollect now, my system too had the floppy disconnected as the new mobo's port was far away from the floppy drive's cable.
On Wed, May 14, 2008 at 11:41 PM, Rony gnulinuxist@gmail.com wrote:
Hello Everyone,
Some time back I read a message about this error showing up when Ubuntu was booted live. I cannot recollect whether it was on this list or elsewhere else. However today at a client's place when I tried Kubuntu 8.04 + KDE4 live on an unbranded Intel 865G mobo, it showed the same error lines after the initial kernel loading. After a second try, I let it move further and after 4 or 5 lines of the error, it booted further normally and brought the desktop up. One very good advantage of 8.04 is that NTFS partitions can be directly viewed in the GUI file browser (Dolphin) with write access. So it is ideal for taking backups from NTFS partitions to other NTFS partitions....something that was a PITA till now.
I also faced the similar problem with Debian Etch. It started appearing when I removed my FDD from MoBo. I used to press `sysrq' to kill that process and continue with further processes. But for this `sysrq' means pressing `Print Screen' on keyboard and not `Alt+PrintScreen' combination.
I think we need to pass a kernel parameter for `not to read fd0' . I am not sure though. I remember reading `kernel-parameters.txt' in Linux kernel documentation. I forgot the parameter name, I couldn't solve the problem either. The name of the parameter is there in the error which is displayed every time.
-
Abhishek Ambe rkar [अभिषेक ] -
mukesh yadav -
Rony