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.
Lenovo ThinkPad Laptop PC 15" FHD Core i5 16GB RAM 256GB SSD Windows 11 Pro HDM
$239.99
Lenovo ThinkPad Laptop PC Computer 15.6" Core i5 8GB RAM 256GB SSD Windows 11
$198.50
15.6" Lenovo ThinkPad Laptop PC: Intel i5 16GB RAM 512 SSD Windows 10 Webcam
$229.99
Lenovo ThinkBook 15 Gen 4 Notebook 15.6" FHD AMD R7 5825U 16GB RAM 512GB SSD
$479.99
Lenovo ThinkPad T14S Gen 1 14-inch (2020) i5-10310U 16 GB SSD 256 GB - B Grade
$199.99
Lenovo N22 Laptop PC Computer 11.6" Windows 10 4GB RAM 64GB SSD HDMI WiFi
$89.99
Lenovo Ideapad 1 14" Laptop - Celeron N4020 with 4GB Memory - Intel UHD Graph...
$149.99
Lenovo LOQ 15.6" FHD 144Hz Gaming Laptop i5-12450HX 12GB RAM 512GB SSD RTX 3050
$599.99
14" Lenovo ThinkPad Laptop: Intel i5 Quad Core 16GB RAM 1TB SSD Windows 11
$249.95
Lenovo Thinkpad X390 Yoga 13.3" 2in1 TOUCH i5-8365U 256GB SSD 8GB Win 10 Laptop
$199.99