Hi People,
Just like the subject says: the form at http://www.linuxbios.org/help/index.html gives a really cute 404.
Should I therefore mail my request for help to the mailing list or should I wait until the form gets back working?
Regards,
Erik Smit
Works fine as far as I can tell, I am not getting the 404. But feel free to post here anyway if it's more convenient for you.
On Thu, 3 Jun 2004, Erik Smit wrote:
Hi People,
Just like the subject says: the form at http://www.linuxbios.org/help/index.html gives a really cute 404.
Should I therefore mail my request for help to the mailing list or should I wait until the form gets back working?
Regards,
Erik Smit
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Strange, I get a 404 at http://www.linuxbios.org/cgi-bin/linuxbios/help.cgi when I click the 'submit form' button.
Anyhow, here's my information.
I have a 'Lex CV860A' which is untested at http://www.linuxbios.org/status/index.html.
The flash device is a "AMIC A29002".
I tried the freebios/src/mainboard/lex/cv860a/example.config with both a memtest86+ payload and filo payload.
At first this does not compile due to what seems to be something that was forgotten in the freebios/src/southbridge/via/vt82c686/southbridge.c file.
+++ freebios.cvs060304/src/southbridge/via/vt82c686/southbridge.c 2002-10-11 01:55:17.000000000 +0200 +++ freebios/src/southbridge/via/vt82c686/southbridge.c 2004-06-03 20:11:04.000000000 +0200 @@ -93,7 +93,7 @@ // 0x80 is enable com port b, 0x1 is to make it com2, 0x8 is enable com port a as com1 enables = 0x80 | 0x1 | 0x8 ; if (dev) { - pci_write_config_byte(0, devfn, 0x83, enables); + pci_write_config_byte(dev, 0x83, enables); } // note: this is also a redo of some port of assembly, but we want everything up. // set com1 to 115 kbaud
After flashing the machine does not boot or give any output over the serial port.
We have a nullmodem cable from the ttyS0 to another machine which I'm sure is functioning because the linuxkernel and getty are able to work over it.
I have added 'option SERIAL_POST=1' to the configfile and retried but still nothing appears on the serial line.
Anything else I can try to debug this problem?
This is the lspci output:
debian:/# lspci 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05) 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP] 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 06) 0000:00:07.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1a) 0000:00:07.3 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1a) 0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50) 0000:00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) debian:/# lspci -n 0000:00:00.0 Class 0600: 1106:0601 (rev 05) 0000:00:01.0 Class 0604: 1106:8601 0000:00:07.0 Class 0601: 1106:0686 (rev 40) 0000:00:07.1 Class 0101: 1106:0571 (rev 06) 0000:00:07.2 Class 0c03: 1106:3038 (rev 1a) 0000:00:07.3 Class 0c03: 1106:3038 (rev 1a) 0000:00:07.4 Class 0680: 1106:3057 (rev 40) 0000:00:07.5 Class 0401: 1106:3058 (rev 50) 0000:00:08.0 Class 0200: 10ec:8139 (rev 10) 0000:00:09.0 Class 0200: 10ec:8139 (rev 10) 0000:00:0b.0 Class 0200: 10ec:8139 (rev 10) 0000:01:00.0 Class 0300: 1023:8500 (rev 6a)
Regards,
Erik Smit
On Thu, Jun 03, 2004 at 09:21:58AM -0600, Hendricks David W. wrote:
Works fine as far as I can tell, I am not getting the 404. But feel free to post here anyway if it's more convenient for you.
On Thu, 3 Jun 2004, Erik Smit wrote:
Hi People,
Just like the subject says: the form at http://www.linuxbios.org/help/index.html gives a really cute 404.
Should I therefore mail my request for help to the mailing list or should I wait until the form gets back working?
Regards,
Erik Smit
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
I think that ought to work as a via epia, use V2.
ron
On Thu, Jun 03, 2004 at 09:37:53AM -0600, ron minnich wrote:
I think that ought to work as a via epia, use V2.
freebios2?
Well, the EPIA has a vt8231 southbridge where this board has a vt82c686. Won't this give problems?
Regards,
Erik Smit
On Thu, 3 Jun 2004, Erik Smit wrote:
Well, the EPIA has a vt8231 southbridge where this board has a vt82c686. Won't this give problems?
There used to be 8231 support. If think they are similar enough it could work.
ron
On Thu, Jun 03, 2004 at 09:44:56AM -0600, ron minnich wrote:
On Thu, 3 Jun 2004, Erik Smit wrote:
Well, the EPIA has a vt8231 southbridge where this board has a vt82c686. Won't this give problems?
There used to be 8231 support. If think they are similar enough it could work.
I just tried to build freebios2/targets/via/epia by running buildtarget on it and then running make. This is on the cvs of today. I got the following error:
/opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c: In function `check_pirq_routing_table': /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:21: error: assignment of read-only variable `intel_irq_routing_table' /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:42: error: assignment of read-only member `checksum' make[1]: *** [pirq_routing.o] Error 1
I just commented these two lines out since they only appear to be used when something is broken. Then it compiled fine.
Then I flashed in the resulting linuxbios.bin using uniflash since flash_and_burn doesn't support the AMIC A29002 chip on this board.
Still, after rebooting, nothing appears on the serial port. Can I conclude from this that this board is not yet supported (out of the box)?
Is there anything else I can try or maybe help debug the problem?
Regards,
Erik Smit
On Thu, 3 Jun 2004, Erik Smit wrote:
Then I flashed in the resulting linuxbios.bin using uniflash since flash_and_burn doesn't support the AMIC A29002 chip on this board.
linuxbios.rom -- you got the wrong file. sorry about that.
ron
On Thu, Jun 03, 2004 at 10:55:14AM -0600, ron minnich wrote:
On Thu, 3 Jun 2004, Erik Smit wrote:
Then I flashed in the resulting linuxbios.bin using uniflash since flash_and_burn doesn't support the AMIC A29002 chip on this board.
linuxbios.rom -- you got the wrong file. sorry about that.
Sorry, that was a typo, I did infact take linuxbios.rom. (There isn't even a linuxbios.bin. :)
Regards,
Erik Smit
On Thu, Jun 03, 2004 at 07:07:12PM +0200, Erik Smit wrote:
On Thu, Jun 03, 2004 at 10:55:14AM -0600, ron minnich wrote:
On Thu, 3 Jun 2004, Erik Smit wrote:
Then I flashed in the resulting linuxbios.bin using uniflash since flash_and_burn doesn't support the AMIC A29002 chip on this board.
linuxbios.rom -- you got the wrong file. sorry about that.
Sorry, that was a typo, I did infact take linuxbios.rom. (There isn't even a linuxbios.bin. :)
Still, after rebooting, nothing appears on the serial port. Can I conclude from this that this board is not yet supported (out of the box)?
Is there anything else I can try or maybe help debug the problem?
Also, is it possible to sponsor one (or more) boards or perhaps fund somebody to work on this?
Regards,
Erik Smit
with the fuctory bios in place, make sure that your minicom setup is right. Let me know.
ron
On Thu, Jun 03, 2004 at 01:04:10PM -0600, ron minnich wrote:
with the fuctory bios in place, make sure that your minicom setup is right. Let me know.
My terminal setup is right since I actually give the reboot command through the serial connection.
I just put the linuxbios.rom I build for the EPIA on an actual VIA EPIA-V we have here. It boots up to this point:
LinuxBIOS-1.1.6.0Fallback Fri Jun 4 00:34:01 CEST 2004 starting... 87 is the comm register SMBus controller enabled vt8601 init starting 00000000 is the north 1106 0601 0120d4 is the computed timing NOP PRECHARGE DUMMY READS CBR MRS NORMAL set ref. rate enable multi-page open Slot 00 is SDRAM 20000000 bytes 0100 is the chip size 000e is the MA type Slot 01smbus_error: 04 Device Error is empty Slot 02smbus_error: 04 Device Error is empty Slot 03smbus_error: 04 Device Error is empty vt8601 done
Then it starts to constantly repeat this: 00:06 11 01 06 06 00 90 22 05 00 00 06 00 00 00 00 10:08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30:00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50:ac 08 80 00 00 00 40 40 4e 00 00 00 40 40 40 40 60:3f 00 00 30 e4 e4 e4 00 42 ac 65 0d 08 7f 00 00 70:00 00 00 00 00 00 00 00 01 f0 00 00 00 00 00 00 80:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0:02 00 20 00 03 02 00 07 00 00 00 00 08 02 00 00 b0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0:00 00 00 00 00 00 01 01 00 00 00 00 00 00 00 00
I've tried different payloads but the same stuff happens. Anything I can do about this?
Also, I've checked out the freebios(1) source and build an EPIA rom from this and this does probably boot with the same filo payload and actually boots a linux kernel and works, yay!
Also2, the cvs checkout of today still give this error on building:
/opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c: In function `check_pirq_routing_table': /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:21: error: assignment of read-only variable `intel_irq_routing_table' /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:42: error: assignment of read-only member `checksum' make[1]: *** [pirq_routing.o] Error 1
I 'solved' this by commenting out the two lines, but I'm sure this is not right. Any proper way to solve this?
Regards,
Erik Smit
The 8231 is not seeing the smbus. Damn.
I don't know what to tell you at this point.
ron
* ron minnich rminnich@lanl.gov [040604 17:33]:
The 8231 is not seeing the smbus. Damn.
I don't know what to tell you at this point.
Is it not? The log seems to indicate ram has been found in slot0
Stefan
On Fri, 4 Jun 2004, Erik Smit wrote:
LinuxBIOS-1.1.6.0Fallback Fri Jun 4 00:34:01 CEST 2004 starting... 87 is the comm register SMBus controller enabled vt8601 init starting 00000000 is the north 1106 0601 0120d4 is the computed timing NOP PRECHARGE DUMMY READS CBR MRS NORMAL set ref. rate enable multi-page open Slot 00 is SDRAM 20000000 bytes 0100 is the chip size 000e is the MA type Slot 01smbus_error: 04 Device Error is empty Slot 02smbus_error: 04 Device Error is empty Slot 03smbus_error: 04 Device Error is empty vt8601 done
Then it starts to constantly repeat this: 00:06 11 01 06 06 00 90 22 05 00 00 06 00 00 00 00 10:08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30:00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50:ac 08 80 00 00 00 40 40 4e 00 00 00 40 40 40 40 60:3f 00 00 30 e4 e4 e4 00 42 ac 65 0d 08 7f 00 00 70:00 00 00 00 00 00 00 00 01 f0 00 00 00 00 00 00 80:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0:02 00 20 00 03 02 00 07 00 00 00 00 08 02 00 00 b0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0:00 00 00 00 00 00 01 01 00 00 00 00 00 00 00 00
I've tried different payloads but the same stuff happens. Anything I can
do about this?
it found the memory and I think is programming it incorrectly.
Sorry for the previous wrong comment.
Also, I've checked out the freebios(1) source and build an EPIA rom from this and this does probably boot with the same filo payload and actually boots a linux kernel and works, yay!
ok, weird.
Also2, the cvs checkout of today still give this error on building:
/opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c: In function `check_pirq_routing_table': /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:21: error: assignment of read-only variable `intel_irq_routing_table' /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:42: error: assignment of read-only member `checksum' make[1]: *** [pirq_routing.o] Error 1
Ollie or Stepan or Greg or David or I need to fix this. Anyone?
ron
On Fri, 2004-06-04 at 09:36, ron minnich wrote:
Also2, the cvs checkout of today still give this error on building:
/opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c: In function `check_pirq_routing_table': /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:21: error: assignment of read-only variable `intel_irq_routing_table' /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:42: error: assignment of read-only member `checksum' make[1]: *** [pirq_routing.o] Error 1
Ollie or Stepan or Greg or David or I need to fix this. Anyone?
It is the const keyword. Why we don't have this problem before ? Is the function actually been called in other platform ?
Ollie
On Fri, 4 Jun 2004, Li-Ta Lo wrote:
It is the const keyword. Why we don't have this problem before ? Is the function actually been called in other platform ?
yes, that's what is so weird. This just started happening but I can find no changes that would have made it start happening. Weird.
ron
On Fri, 2004-06-04 at 10:02, ron minnich wrote:
On Fri, 4 Jun 2004, Li-Ta Lo wrote:
It is the const keyword. Why we don't have this problem before ? Is the function actually been called in other platform ?
yes, that's what is so weird. This just started happening but I can find no changes that would have made it start happening. Weird.
ron
What is the targe he is building ? EPIA ?
Ollie
* ron minnich rminnich@lanl.gov [040604 18:02]:
On Fri, 4 Jun 2004, Li-Ta Lo wrote:
It is the const keyword. Why we don't have this problem before ? Is the function actually been called in other platform ?
yes, that's what is so weird. This just started happening but I can find no changes that would have made it start happening. Weird.
It depends on the compiler version you are using. Gcc behaves different every minor version now. My gcc (3.3.3, SUSE 9.1) shows the same thing as a warning.
Stefan
* ron minnich rminnich@lanl.gov [040604 17:36]:
Also2, the cvs checkout of today still give this error on building:
/opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c: In function `check_pirq_routing_table': /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:21: error: assignment of read-only variable `intel_irq_routing_table' /opt/linuxbios/freebios2/src/arch/i386/boot/pirq_routing.c:42: error: assignment of read-only member `checksum' make[1]: *** [pirq_routing.o] Error 1
Ollie or Stepan or Greg or David or I need to fix this. Anyone?
I will comment the two table fixing functions out for now until we generate this table dynamically
Stefan
* Stefan Reinauer stepan@openbios.org [040605 12:12]:
I will comment the two table fixing functions out for now until we generate this table dynamically
The table is checked twice, once the original and once the copy. Since the checking of the original does not change the fact whether the the table is copied at all, I will unify these and only check the copy of the pirq table. There we can change checksum and length as we wish.
Stefan
* Stefan Reinauer stepan@openbios.org [040605 12:29]:
- Stefan Reinauer stepan@openbios.org [040605 12:12]:
I will comment the two table fixing functions out for now until we generate this table dynamically
The table is checked twice, once the original and once the copy. Since the checking of the original does not change the fact whether the the table is copied at all, I will unify these and only check the copy of the pirq table. There we can change checksum and length as we wish.
If noone is going to object the attached patch, I am going to submit this soon.
Stefan
* Stefan Reinauer stepan@openbios.org [040605 12:38]:
Index: arch/i386/boot/pirq_routing.c
RCS file: /cvsroot/freebios/freebios2/src/arch/i386/boot/pirq_routing.c,v retrieving revision 1.8 diff -u -r1.8 pirq_routing.c --- arch/i386/boot/pirq_routing.c 15 Apr 2004 17:33:20 -0000 1.8 +++ arch/i386/boot/pirq_routing.c 5 Jun 2004 10:36:43 -0000 @@ -78,6 +73,9 @@ } } printk_info("done\n");
- check_routing_table((struct irq_routing_table *)addr);
- return 0;
} #else
This should be check_pirq_routing_table() of course.
Stefan
looks ok to me.
ron
Ron,
I would start to add Intel 875 support. I check there are two via northbridge support in V2. Which one is more mature?
Regards
YH
On Fri, Jun 04, 2004 at 09:36:36AM -0600, ron minnich wrote:
I've tried different payloads but the same stuff happens. Anything I can
do about this?
it found the memory and I think is programming it incorrectly.
Sorry for the previous wrong comment.
Is there anything I can do about this? Maybe help debugging? I have tried changing the slot the memory is in but the same stuff happens.
Regards,
Erik Smit
On Thu, 3 Jun 2004, Erik Smit wrote:
Just like the subject says: the form at http://www.linuxbios.org/help/index.html gives a really cute 404.
my fault.
I gave up on that because the messages I got through it were useless.
ron
-
Erik Smit -
Hendricks David W. -
Li-Ta Lo -
ron minnich -
Stefan Reinauer -
Yinghai Lu