Looks like dma is killing you. It's on by default and can be changed in /etc/init.d/bootmisc.sh. Boot the Knoppix cd, mount your /root partition and edit the file.
KNOPPIX 3.3-2003-11-19 downloaded OK and its MD5 checked OK
I had installed 3.2 on hard drive earlier and it works perfectly so I used
the same installation instructions with 3.3. The installation ran perfectly.
3.3's boot seems normal until it suddenly stops with this message on the monitor:
Cleaning: /tmp /vat/lock /var/run 4095Mb
blk: queue c0334b60,I/O limit (mask 0xffffffff)
blk: queue c0334ca8, I/O limit (mask 0xffffffff)
hda: dma_intr: status=0x51 {DriveReady SeekCompleteError}
hda: dma_intr: error=0x84 {DriveStatusError Bad CRC}
hda: dma_intr: status=0x51 {DriveReady SeekCompleteError}
hda: dma_intr: error=0x84 {DriveStatusError Bad CRC}
hda: dma_intr: status=0x51 {DriveReady SeekCompleteError}
hda: dma_intr: error=0x84 {DriveStatusError Bad CRC}
hda: dma_intr: status=0x51 {DriveReady SeekCompleteError}
hda: dma_intr: error=0x84 {DriveStatusError Bad CRC}
The keyboard has no effect----the system is locked (with a blinking
cursor). I have to do a pushbutton restart..
Any clues?
Looks like dma is killing you. It's on by default and can be changed in /etc/init.d/bootmisc.sh. Boot the Knoppix cd, mount your /root partition and edit the file.
My image CD had some missing files---I burned a new one using different
software and this one works OK.
When I ran the CD version, it seemed to work OK.
Thanks.
Thanks for the DMA info. I checked out /etc/init.d/bootmisc.sh and it reads
# enable DMA
/sbin/hdparm -qd1 /dev/hda
/sbin/hdparm -qd1 /dev/hdb
I have no idea if this is OK as is or if it has to be changed.
I've just discovered that there's more to this problem that deserves a new posting..... look for 'Crazy booting"
well mine locked up as well (but i don't remember any dma messages). I fixed it by installing GRUB - YMMV.
Thanks to rickenbacherus's suggestion, I edited /etc/init.d/bootmisc.sh thusly
# enable DMA
# /sbin/hdparm -qd1 /dev/hda
# /sbin/hdparm -qd1 /dev/hdb
and now 3.3 boots up properly using 3.3's LILO
Before I did this, I tried booting 3.3 with a Progeny Debian installer floppy and it also booted properly so apparently, it was some disagreement between the 3.3's LILO and DMA.
I have since changed to boot with GRUB and it boots OK.
Thanks all for the assistance.
You probably just need to edit the dma out of the lilo.conf on the append line.
Dell PowerEdge R720 Server - 2x8c CPU,256Gb RAM, 128Gb SSD/3x900Gb SAS, Proxmox
$340.00
Dell PowerEdge R620 Server 2x E5-2660 v1 2.2GHz 16 Cores 256GB RAM 2x 300GB HDD
$89.99
Dell PowerEdge R730XD 28 Core Server 2X Xeon E5-2680 V4 H730 128GB RAM No HDD
$389.99
DELL PowerEdge R730 Server 2x E5-2680v4 2.4GHz =28 Cores 32GB H730 4xRJ45
$284.00
Dell PowerEdge R230 Single Intel Xeon E3-1220 v5 @3.00GHz 16GB RAM No HDD H330
$102.50
Dell PowerEdge R730, 2 sinks, SystemBoard, 8 trays,H330,Idrac 8 exp, 2x750w Psu
$135.00
Dell PowerEdge R710 2.5" 2U Server 2x X5670 2.93GHZ 12-Core 128gb 2x 1TB SAS
$214.99
Dell PowerEdge R610 1U Server 2x Intel Xeon E5504 2.0Ghz 8GB RAM NO HD NO OS,QTY
$86.95
DELL PowerEdge R630 8SFF Server 2x E5-2690v4 2.6GHz =28 Cores 256GB H730 4xRJ45
$600.00
Dell Poweredge R720 2x Xeon E5-2660 v2 2.2GHz 20-Cores / 192gb / H710 / 2x 750w
$239.99