The box is running fine with kernel 220.127.116.11.
It's an iDEQ200V box with a BioStar motherboar, VIA KM400 + VT8237 chipset.
Here's my BIOS information based on dmidecode:
Vendor: Phoenix Technologies, LTD
Version: 6.00 PG
Release Date: 08/19/2003
Runtime Size: 128 kB
ROM Size: 512 kB
ISA is supported
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/360 KB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 KB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
AGP is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
( .. more info available if useful ..)
Did anybody discovered similar issues or have any ideas on how to solve that?
Thanks for any help,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
If you try a recompile without xtables and iptables,will everything
work? I'm hoping the next patch will resolve this issue.
> I'm trying to upgrade to kernel 1.6.19. The boot process immediatly
> locks in a loop with the message: "atkbd.c: Spurious ACK on
> isa0060/serio0. Some program might be trying access hardware
The above message is a result of the keyboard LEDs being flashed after
a failed boot.
See my posting
with a patch to suppress these repeated messages, so you can see what
the real problem is.
Alan J. Wylie http://www.wylie.me.uk/
"Perfection [in design] is achieved not when there is nothing left to add,
but rather when there is nothing left to take away."
-- Antoine de Saint-Exupery
You actually don't need a patch - just boot with i8042.panicblink=0.
This issue (messages) is properly fixed in input tree.