The default kernel boot hangs with the following line displayed on the screen:
blk_update_request: I/O error, dev fd0, sector 0
First thing to note is that there is no floppy disk drive attached to the PC.
When I boot through the grub “Advanced options for openSUSE Leap 42.2” recovery mode kernel the system boots OK, but I see the following lines in the boot output:
blk_update_request: I/O error, dev fd0, sector 0
Floppy: error -5 while reading block 0
Both the normal kernel boot and the recovery mode boot appear to have a “–no-floppy” parameters.
I have tried black listing the floppy module; disabling the floppy in the BIOS configuration. I would appreciate some new suggestions on how to proceed?
Did a re-install of leap 42.2 and the box boots cleanly.
Previously I added community repos and did install of recommended stuff through “yast->Extras->Install All Matching Recommended Packages”; this installed the G04 Nvidia modules; looked back in the install logs for the previously installed openSUSE 13.2 and it chose to install the G03 Nvidia modules. The display controller hardware is identified as GM107GL (Quadro K620); googled for driver info but not found anything useful; anybody any thoughts?
See if the BIOS thinks there is a floppy. This can confuse things if there is not. ie BIOS says there is a floppy the OS says great where is it I can’t find it.
I believe it is something to do with the Nvidia drivers; the Nvidia G03 drivers are more reliable than the G04 on my hardware, the G03 reliably boots in recovery mode the G04 does not; neither G03/G04 boots with the default kernel boot; whatever determined that the G04 drivers is correct for my hardware (GM107GL, Quadro K620) is buggy, openSUSE 13.2 correctly identified the G03 driver. I’ve deleted the Nvidia repository and un-installed the Nvidia drivers for the moment.
I have now had a couple of lock-ups (2 week period) on desktop machine with the open source video driver installed; also had one lock-up on laptop (1 week period), hence probably nothing to do with the video drivers; all lock-up occur during the boot. When the lock-up occurs I cannot switch to a simple text login (cntl+alt+Fx) all I can do is hold the power button until power down. Can somebody provide some pointer on the how/which logs to inspect with the systemd now in control of the boot.
When a boot is performed through the recovery kernel, does this boot have options that force the serialisation of the launch of the various boot processes?
