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.
1U BareMetal pfsense opnsense Router Firewall DNS Server 6x 10GB Ethernet Ports
$149.00
Supermicro 1U X11DPU 2x Xeon Gold 6132 2.6GHz / 128gb / 10x 2.5 Trays / 2x 750w
$649.99
1U Supermicro Server 10 Bay 2x Intel Xeon 3.3Ghz 8C 128GB RAM 480GB SSD 2x 10GBE
$273.00
1U 20" Short Depth Server Firewall PFSense X11SSH-F Xeon 3.5Ghz 32GB RAM NVME
$247.00
HP ProLiant Xeon E3-1220L V2 MicroServer Gen8 2.30 GHz 16 GB RAM NO DRIVES
$199.00
Open Eye OE-MTX08 8TB Micro Server With Linux (Boots To Login) No Accessories
$282.92
Genuine HP ProLiant MicroServer Gen8 Intel Pentium G2020T 2.5GHz 712318-001
$199.95
CEOhack 1U X9DRW-3TF+ 4 Bay Server 64GB DDR3 1x E5-2667 V2 3.30GHz 8C 1x 1TB HDD
$119.00
Supermicro CSE 823-6 2U 6 Bay Chassis ,1xPWS 653-2H 650Wsold as in the photo,
$119.75
Supermicro 505-2 Mini-1U Server 5018A-FTN4 16GB 2.4ghz Atom + Rack Ears
$183.08