[LinuxBIOS] Random Bios Postcodes after 0x88 with 440BX
roger at eskimo.com
Fri Apr 27 07:34:07 CEST 2007
On Fri, 2007-04-27 at 00:49 +0200, Uwe Hermann wrote:
> On Wed, Apr 25, 2007 at 07:26:21PM -0700, roger wrote:
> > I don't know if the above are listed in an order that states these
> > postcodes should be reported on the device or any order, but I do get
> > the following reported on my postcard in order:
> > 0x80, 0x88, E7
> > 0x80, 0x88, 27
> > 0x80, 0x88, A1, AC
> How does your POST card look like? Does it only display two digits or
> more? Or are the above numbers meant as a series of POST codes?
Has been the norm after specifying the interrupts and correcting the
iobase of the ttyS0 port in auto.c
My latest build, will do the following after a warm reboot and yanking
all by 1 sticking of memory:
12 (or sometimes 11)
I don't know if this is progress or not. Or even if it's just
encountering a memory bug before console init?
> (also, why 0x80 but E7 without the "0x"?)
Just denoting hex as it's coded. :-/
Just got my other Bios Savior today for my Tyan S1832DL and will give
this 440BX a try. No need to specify the SuperIO as I've already
verified it's the same as the S1846 you've been working on.
So my S1832DL *should* give me something on serial without too much
I'll try to start building a new tree tomorrow.
Really, I don't see why the DFI P2XBL 440bx isn't giving output as it's
been with it's SuperIO chip since LinuxBiosv1. All I can think of it's
a bug before console init or bug with enabling early_ttyS0. :-/
Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61
Thu Apr 26 22:24:55 PDT 2007
More information about the coreboot