Re: [debian-knoppix] bootsplash
Klaus Knopper wrote:
486 DX100 with 28 MB Ram (and some swap). Takes about 10 Minutes to boot
until the first Window in KDE, but still works. ;-)
integrated FPU, so this support is useless for it.
Does this really save much space, dropping only a few emulated FPU
ernel math emulation
Linux can emulate a math coprocessor (used for floating point
operations) if you don't have one. 486DX and Pentium processors have
a math coprocessor built in, 486SX and 386 do not, unless you added
a 487DX or 387, respectively. (The messages during boot time can
give you some hints here ["man dmesg"].) Everyone needs either a
coprocessor or this emulation.
If you don't have a math coprocessor, you need to say Y here; if you
say Y here even though you have a coprocessor, the coprocessor will
be used nevertheless. (This behaviour can be changed with the kernel
command line option "no387", which comes handy if your coprocessor
is broken. Try "man bootparam" or see the documentation of your boot
loader (lilo or loadlin) about how to pass options to the kernel at
boot time.) This means that it is a good idea to say Y here if you
intend to use this kernel on different machines.
More information about the internals of the Linux math coprocessor
emulation can be found in <file:arch/i386/math-emu/README>.
If you are not sure, say Y; apart from resulting in a 66 KB bigger
kernel, it won't hurt.
unbelivable, but yes.
And is a 486-optimized kernel still compatible to AMD processors?
it doesn't make any sence really to compile for i486.
Isn't that the same problem? There is a warning in the Help for this
NOTE: If you say "64GB" here,
then the kernel will not boot on CPUs that don't support PAE!
...only 64GB (which is quite logical).
Ok, I will switch it on in the next kernel update then. Not right now.
When 2.4.21 comes out, whenever that will be. ;-)
If you switch on ACPI, you change code in most parts of the kernel, not
only the power management. It also affects modules and SMP code.
hm... the settings only talk about OSPM (and is loadable as a module) -
the newest debian-Kernel has this modules (and works here!)
Worst case scenario. But at least al devices are unmounted before that
happens, I hope. ;-)
yes - it's a board with totally f*cked bios :(
You should boot with "noapm" in that case.
at that time it crashes, it doesn't make any difference ;)
Interesting. Do you have any reports on advantages/disadvantages on
not really... technical it can at worst case prevent the computer from
going to suspend...
Btw, suspend-to-RAM does NOT work anymore on the majority of notebooks I
have seen, if you compile in ACPI. Including my new Asus L3800C. :-(
In APM mode, suspend still works fine, even that the manual keeps telling
me that APM is not supported.
debian-knoppix mailing list