Dual PIII boots and runs from 7.2.0 CD but after HD Inst hangs on boot

**thriftee** · 01-01-2016, 10:50 PM

7.2.0 booted and ran fine from the CD.

I did the HD install, and there were no problems.

It says to reboot, so I try to reboot, it starts booting, the Grub screen comes up, has KNOPPIX option, but it hangs after "Booting the Kernel".

I tried adding debug to the boot command, but it says that's invalid...

Any ideas how to diagnose?

PS: the drives are SCSI, but I figured if it can see them and format when booted from CD I would think it can see them ok

thanks

**thriftee** · 01-02-2016, 03:36 AM

Here is lspci -v output

Code:

 00:00.0 Host bridge: Intel Corporation 440GX - 82443GX Host bridge 	Flags: bus master, medium devsel, latency 64 	Memory at f8000000 (32-bit, prefetchable) [size=64M] 	Capabilities: [a0] AGP version 1.0 	Kernel driver in use: agpgart-intel    00:01.0 PCI bridge: Intel Corporation 440GX - 82443GX AGP bridge (prog-if 00 [Normal decode]) 	Flags: bus master, 66MHz, medium devsel, latency 64 	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 	I/O behind bridge: 0000d000-0000dfff 	Memory behind bridge: fca00000-feafffff 	Prefetchable memory behind bridge: e4800000-f48fffff    00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) 	Flags: bus master, medium devsel, latency 0    00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master]) 	Flags: bus master, medium devsel, latency 64 	[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8] 	[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1] 	[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8] 	[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1] 	I/O ports at ffa0 [size=16] 	Kernel driver in use: ata_piix    00:07.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) 	Flags: bus master, medium devsel, latency 64, IRQ 9 	I/O ports at ef80 [size=32] 	Kernel driver in use: uhci_hcd    00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 	Flags: medium devsel, IRQ 9 	Kernel driver in use: piix4_smbus    00:0e.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891 (rev 01) 	Subsystem: Adaptec 2940U2W SCSI Controller 	Flags: bus master, medium devsel, latency 64, IRQ 10 	BIST result: 00 	I/O ports at e800 [disabled] [size=256] 	Memory at febff000 (64-bit, non-prefetchable) [size=4K] 	Expansion ROM at febc0000 [disabled] [size=128K] 	Capabilities: [dc] Power Management version 1 	Kernel driver in use: aic7xxx    00:0f.0 Multimedia audio controller: Ensoniq Device 4880 (rev 02) 	Subsystem: Ensoniq Device 2003 	Flags: bus master, slow devsel, latency 64, IRQ 10 	I/O ports at ef00 [size=64] 	Capabilities: [dc] Power Management version 1    00:12.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Wireless Network Adapter (rev 01) 	Subsystem: Netgear WG311T 108 Mbps Wireless PCI Adapter (rev.A3) 	Flags: bus master, medium devsel, latency 168, IRQ 5 	Memory at febe0000 (32-bit, non-prefetchable) [size=64K] 	Capabilities: [44] Power Management version 2 	Kernel driver in use: ath5k    01:00.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX 5500] (rev a1) (prog-if 00 [VGA controller]) 	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11 	Memory at fd000000 (32-bit, non-prefetchable) [size=16M] 	Memory at e8000000 (32-bit, prefetchable) [size=128M] 	Expansion ROM at feae0000 [disabled] [size=128K] 	Capabilities: [60] Power Management version 2 	Capabilities: [44] AGP version 3.0

I did edit it to make it readable but the forum removed it all

**Werner P. Schulz** · 01-02-2016, 08:02 AM

Please use "Go Advanced" for your posting → use the icon "#" (Wrap [CODE] tags around selected text) → now insert the copy of "lspci -v" within the tags.

**thriftee** · 01-02-2016, 04:41 PM

Thanks, Werner, yes that makes it a lot more readable.

The most important thing is to be able to do the HD install and be able to boot again from the HD with the same drivers (if I'm using the right word). I tried to use the debug option to get it to give me clues where the problem was in the boot, but I don't know the correct syntax to add it to the grub boot line.

Any help getting it booted to HD would be appreciated. This is the first linux OS where I''ve been able to get the SCSI to boot, the Wireless to connect, and the usb hub and sound card to both appear.

Thanks

Code:

00:00.0 Host bridge: Intel Corporation 440GX - 82443GX Host bridge     
Flags: bus master, medium devsel, latency 64     
Memory at f8000000 (32-bit, prefetchable) [size=64M]     
Capabilities: [a0] AGP version 1.0     
Kernel driver in use: agpgart-intel    

00:01.0 PCI bridge: Intel Corporation 440GX - 82443GX AGP bridge (prog-if 00 [Normal decode])     
Flags: bus master, 66MHz, medium devsel, latency 64     
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64     
I/O behind bridge: 0000d000-0000dfff     
Memory behind bridge: fca00000-feafffff     
Prefetchable memory behind bridge: e4800000-f48fffff    

00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)     
Flags: bus master, medium devsel, latency 0    

00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master])     
Flags: bus master, medium devsel, latency 64     
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]     
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]     
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]     
[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]     
I/O ports at ffa0 [size=16]     
Kernel driver in use: ata_piix    

00:07.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])     
Flags: bus master, medium devsel, latency 64, IRQ 9     
I/O ports at ef80 [size=32]     
Kernel driver in use: uhci_hcd    

00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)     
Flags: medium devsel, IRQ 9     
Kernel driver in use: piix4_smbus    

00:0e.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891 (rev 01)     
Subsystem: Adaptec 2940U2W SCSI Controller     
Flags: bus master, medium devsel, latency 64, IRQ 10     
BIST result: 00     
I/O ports at e800 [disabled] [size=256]     
Memory at febff000 (64-bit, non-prefetchable) [size=4K]     
Expansion ROM at febc0000 [disabled] [size=128K]     
Capabilities: [dc] Power Management version 1     
Kernel driver in use: aic7xxx    

00:0f.0 Multimedia audio controller: Ensoniq Device 4880 (rev 02)     
Subsystem: Ensoniq Device 2003     
Flags: bus master, slow devsel, latency 64, IRQ 10     
I/O ports at ef00 [size=64]     
Capabilities: [dc] 
Power Management version 1    

00:12.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Wireless Network Adapter (rev 01)     
Subsystem: Netgear WG311T 108 Mbps Wireless PCI Adapter (rev.A3)     
Flags: bus master, medium devsel, latency 168, IRQ 5     
Memory at febe0000 (32-bit, non-prefetchable) [size=64K]     
Capabilities: [44] Power Management version 2     
Kernel driver in use: ath5k    

01:00.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX 5500] (rev a1) (prog-if 00 [VGA controller])     
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11     
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]     
Memory at e8000000 (32-bit, prefetchable) [size=128M]     
Expansion ROM at feae0000 [disabled] [size=128K]     
Capabilities: [60] Power Management version 2     
Capabilities: [44] AGP version 3.0

**thriftee** · 01-02-2016, 06:20 PM

Ok, I had tried "debug" yesterday on the boot command line, but got a syntax error, today I tried verbose and it didn't do anything, so then in a wild random attempt I changed logging level to 5 and added both verbose and debug, and finally it started spitting out what it was doing.

It is hanging right after: "[2.0802555] Waiting for root device /dev/sdc3..." which is the SCSI drive I loaded knoppix 7.2.0 onto. My guess is that the SCSI driver is not loaded. Is there a way to tell it to load the SCSI driver someplace before here?

**klaus2008** · 01-02-2016, 07:04 PM

Hi,

I suggest you boot Knoppix off the CD and use the command lsmod to find out which kernel modules are to be loaded for your SCSI adaptor.
These kernel modules have to be offered to the Knoppix kernel at boot time before it can access your SCSI HDD. The usual way to do so is to create an initial root disk and configure the boot loader so that the kernel loads it.
There are tools in the Debian distribution which help you create the initrd.

On the other hand, you could compile yourself a Linux kernel which includes the kernel modules needed by your SCSI adaptor.

**thriftee** · 01-02-2016, 08:02 PM

Thanks, klaus Here is the lsmod output while booted from the cd. How can I tell what is loaded when booting from HD? Or is the answer just to guess what is needed?

Code:

root@Microknoppix:/home/knoppix# lsmod
Module                  Size  Used by
ipv6                  212138  18 
parport_pc             23972  1 
ppdev                   4167  0 
lp                      6185  0 
parport                21928  3 lp,ppdev,parport_pc
arc4                    1463  2 
ath5k                 108297  0 
ath                    10993  1 ath5k
mac80211              347664  1 ath5k
i2c_piix4               6804  0 
cfg80211              319430  3 ath,ath5k,mac80211
aic7xxx                98445  0 
ttm                    38344  0 
drm_kms_helper         20665  0 
root@Microknoppix:/home/knoppix#

**klaus2008** · 01-03-2016, 01:01 AM

After lsmod has shown the loaded kernel modules you can use the command modinfo to get more information about each kernel module. Example:

Code:

modinfo -d aic7xxx
modinfo -n aic7xxx

**thriftee** · 01-04-2016, 05:22 AM

Klaus,

I understand the idea, and appreciate the suggestion.

I spent the evening looking for a good how to or example, and didn't find anything close enough that I could work from.

Any suggestions for where to find a tutorial or good instructions or example?

Thanks

**klaus2008** · 01-05-2016, 06:37 PM

Hi!

I suggest that you use the command mkinitramfs to create an initial ramdisk.

Code:

sudo mkinitramfs -o /home/knoppix/initrd-$(uname -r)

Then you have to copy the initrd to the directory where the kernel resides. The configuration file of your bootloader has to be edited so that the kernel makes use of your initrd.

There exists a manpage for the command mkinitramfs

Code: