kernel_problems
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | kernel_problems [2014/11/24 01:14] (current) – created 0.0.0.0 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Kernel_problems ====== | ||
| + | River is currently booting off a PATA disk connected to a JMicron PATA controller. | ||
| + | The current kernel is a hand-rolled 2.6.26-gentoo-r4, | ||
| + | |||
| + | The JMicron controller is picked up last, behind four LVM disks, and one new system disk, so appears as < | ||
| + | |||
| + | ===== Building a new kernel for the current OS ===== | ||
| + | The following kernel sources are installed | ||
| + | * 2.6.28-gentoo-r1 | ||
| + | * 2.6.27-gentoo-r2 | ||
| + | * 2.6.26-gentoo-r4 | ||
| + | |||
| + | Using genkernel, with the default configuration and additional support for nl80211 wireless | ||
| + | |||
| + | ==== kernel-genkernel-x86-2.6.28-gentoo-r1 ==== | ||
| + | When used to boot the current OS: | ||
| + | |||
| + | / | ||
| + | / | ||
| + | | ||
| + | | ||
| + | |||
| + | One or more critical startup scripts failed to start! | ||
| + | | ||
| + | |||
| + | / | ||
| + | | ||
| + | | ||
| + | / | ||
| + | / | ||
| + | | ||
| + | | ||
| + | |||
| + | One or more critical startup scripts failed to start! | ||
| + | | ||
| + | |||
| + | | ||
| + | |||
| + | When used to boot the new OS: | ||
| + | |||
| + | ... | ||
| + | |||
| + | ===== Building a new OS ===== | ||
| + | ==== kernel-genkernel-x86-2.6.28-gentoo-r1 ==== | ||
| + | When used to boot the new OS | ||
| + | |||
| + | Looks like it doesn' | ||
| + | Also get lots of errors pertaining to ext3. Possibly a corrupt filesystem. | ||
| + | Could try rebuilding base OS in VMware - maybe river' | ||
| + | |||
| + | When used to boot the current OS (on a whim) | ||
| + | |||
| + | Block device /dev/sdf2 is not a valid root device... | ||
| + | Could not find the root block device in . | ||
| + | |||
| + | Because the kernel picks up the JMicron controller first. The boot device is now < | ||
| + | |||
| + | | ||
| + | | ||
| + | |||
| + | ===== Building yet another OS in vmware ===== | ||
| + | While attempting to rebuild the OS again in VMware, the following errors were encountered. The physical disk < | ||
| + | |||
| + | {{wiki: | ||
kernel_problems.txt · Last modified: by 0.0.0.0
