ke4nt1
Group: Members
Posts: 2329
Joined: Oct. 2003 |
 |
Posted: Oct. 09 2004,03:23 |
 |
I have seen this occur when certain memory addresses are accessed that should not be
during the loading of the apm and acpi portions of the knoppix autodetection routines ..
This used to be an issue with multiprocessor boards, but a memory workaround was made..
The floppy image will give you another method of booting up that may
help to resolve the initial issue with detection ..
Have you tried the many options available at the boot line, like noagp, nomce,
failsafe, noacpi, noapic, noscsi, noapm, etc..
Usually, ONE of these will "workaround" the memory issue, and allow you to
complete the sequences at boottime.. Finding the right one that works
can be challenging, but once you know it, your set!
Another option is to preset certain portions of memory to be off limits
with bios options that SOME computers offer..
Another is to disable some features like caches, power management, etc.
in your bios, and see if that helps response..
Then we can isolate the area involved, and prescribe a fix..
Of course, a google search using keywords like
" linux" and "your model number" may be helpful,
Also , look for bios updates for your box ..
73
ke4nt
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
