When I attempt to install Feisty herd 5 using media that has been checked, I still get the same error messages as before during the boot process:
udevd[4076]: lookup_group: specified group 'nvram' unknown
udevd-event[4122]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@mice': No such file or directory
[ 80.056000] intel_rng: FWH not detected
[ 81.760000] si3054: cannot initialize. EXT MID = 0000
The only difference from my original bug report is that I am no longer able to reproduce the following error message:
[ 91.796000] BUG: soft lockup detected on CPU#0
To clarify the original bug report, the above error messages appear between displaying the splash screen with the progress bar and the gnome desktop. So, even though I get error messages, I consistently reach the desktop which enables me to proceed with the installation.
Also, Mikael Nilsson suggested that the problem might only occur when the wireless was turned off. However, I have tested with both wireless turned on and off, and I get the exact same results both times.
When I attempt to install Feisty herd 5 using media that has been checked, I still get the same error messages as before during the boot process:
udevd[4076]: lookup_group: specified group 'nvram' unknown udev/db/ class@input@ mice': No such file or directory
udevd-event[4122]: udev_db_add_device: unable to create db file '/dev/.
[ 80.056000] intel_rng: FWH not detected
[ 81.760000] si3054: cannot initialize. EXT MID = 0000
The only difference from my original bug report is that I am no longer able to reproduce the following error message:
[ 91.796000] BUG: soft lockup detected on CPU#0
To clarify the original bug report, the above error messages appear between displaying the splash screen with the progress bar and the gnome desktop. So, even though I get error messages, I consistently reach the desktop which enables me to proceed with the installation.
Also, Mikael Nilsson suggested that the problem might only occur when the wireless was turned off. However, I have tested with both wireless turned on and off, and I get the exact same results both times.