Making an Ubuntu Server - Part 2: The Frustration
Added: September 6th, 2007 (tagged with: computer)
Yesterday's work on my new Ubuntu Server did not go so well. After going to Best Buy to pick up a new (320GB) Hard Drive, I began my attempt to install Ubuntu 7.04 Server Edition. After going through the install process, reboot the system, and I am presented with a nice set of error messages:
ACPI: Invalid PBLK length [5]
8139too 0000:02:0d.0: Chip not responding, ignoring board
kinit: name_to_dev_t(/dev/sda5) = sda(8,5)
kinit: trying to resume from /dev/sda5
kinit: No resume image, doing normal boot
* setting preliminary keymap [OK]
* starting basic networking [OK]
* starting kernal event manager [OK]
* loading hardware drivers...
intel_rng: FWH not detected
iTwo_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware
Right... Coming from a Windows world, these errors mean nothing to me... Research time...
ACPI is the Advanced Configuration and Power Interface. It seems there is a problem with ASUS motherboards returning a PBLK (?) length of 5 when the expected length is 6. Doesn't look like this is a serious issue, others have ignored the error and booted fine.
8139too seems to have something to do with a RealTek Network Card (not sure if I have a RealTek or not, but I probably do if I'm getting this error) - need to investigate more when I get home.
name_to_dev_t(/dev/sda5) = sda(8,5) might have something to do with my partitions being mis-numbered in terms of where they are located on the HDD, found some information on the Ubuntu Forms that might help.
intel_rng: FWH not detected means the Intel hardware Random Number Generator was not detected in the FirmWare Hub. From what I can find on a few forums, this is not a problem, but it has caused some people to experience a 1-2 minute boot delay. I'm not sure if I gave my system that much time to boot, so (when I get a chance) my first step is to see if the system will boot if I give it a few minutes.
After some investigation, it's a little comforting to know there may be solutions to the errors I am seeing, but coming from a Windows world, it's nice when things "just work" (in terms of hardware support).
