* Stefan Reinauer <[EMAIL PROTECTED]> [060302 17:23]: > # grep ttyS.*irq messages > Feb 28 15:11:36 testnode kernel: ttyS0 at I/O 0x3f8 (irq = 0) is a 16550A > Feb 28 15:11:36 testnode kernel: ttyS1 at I/O 0x2f8 (irq = 0) is a 16550A > Feb 28 18:14:49 testnode kernel: ttyS0 at I/O 0x3f8 (irq = 0) is a 16550A > Feb 28 18:14:49 testnode kernel: ttyS1 at I/O 0x2f8 (irq = 4) is a 16550A > > AMIBIOS: > > Jan 3 14:34:39 testnode kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > Jan 3 14:34:39 testnode kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > Jan 3 18:29:46 testnode kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > Jan 3 18:29:46 testnode kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > > Any idea why and how that could happen? Ok, here's some details:
The systems which are causing problems all have a W83627HF revision ID = 0x17 The OK systems with linuxbios all have: W83627HF revision ID = 0x41 Unfortunately there does not seem to be a revision guide on the winbond website. Any ideas anyone? Stefan -- linuxbios mailing list [email protected] http://www.openbios.org/mailman/listinfo/linuxbios
