Re: CPU refactoring status....
ron minnich [EMAIL PROTECTED] writes: On 13 Jul 2004, Eric W. Biederman wrote: I think someone needs to log into the cvs server and fix it. Which like requires a project admin to ask the sourceforge administrators. I'll do it tomorrow. usually these things time out, but ... [EMAIL PROTECTED]@! Agreed. Thank you very much for taking the time to do this. What does it involve anyway? Eric ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: CPU refactoring status....
you need to send me the file name again (I forgot it) and then I file a trouble ticket with sourceforge, etc., etc., since I don't have direct access to the repo. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Serenade BIOS
Hi Ollie, I finally got the AMD Seranade board andtried the Serenade Linux BIOS. But I've got the serial port message like followingand doesn't have any VGA output. (Seranade board come with a ATI Rage VGA card), I suppose the current Serenade LinuxBIOS doesn't have the VGA support?The serial output has a lot of "POST: 0x00" message output at at beginning and ending make me think I probably missed something. The changesI did with the BIOS is very minor.they are: 1.option ROM_SIZE changed to 512K, instead of 1MB to fit my Flash Part size. 2. option MAXIMUM_CONSOLE_LOGLEVEL andoption DEFAULT_CONSOLE_LOGLEVEL changed to value 7, instead of value 8, in order to build. (Follow your instruction) Any input would be appriciated. Thanks Tony --- Attached Seranade LinuxBIOS Serial Port output POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00 LinuxBIOS-1.1.6.0Fallback Tue Jul 13 19:16:21 PDT 2004 starting...setting up resource mapdone.02 nodes initialized.coherent_ht_finalizedoneht reset - LinuxBIOS-1.1.6.0Fallback Tue Jul 13 19:16:21 PDT 2004 starting...setting up resource mapdone.02 nodes initialized.coherent_ht_finalizedonePCI: 00:01.00PCI: 00:01.01PCI: 00:02.00PCI: 00:02.01PCI: 00:03.00PCI: 00:04.00PCI: 00:04.01PCI: 00:04.02PCI: 00:04.03PCI: 00:04.05PCI: 00:04.06PCI: 00:18.00PCI: 00:18.01PCI: 00:18.02PCI: 00:18.03PCI: 00:19.00PCI: 00:19.01PCI: 00:19.02PCI: 00:19.03Ram1.00Ram1.01Ram2.00Ram2.01No memory for this cpuRam3Initializing memory: doneClearing LinuxBIOS memory: doneRam4PCI: 00:01.00PCI: 00:01.01PCI: 00:02.00PCI: 00:02.01PCI: 00:03.00PCI: 00:04.00PCI: 00:04.01PCI: 00:04.02PCI: 00:04.03PCI: 00:04.05PCI: 00:04.06PCI: 00:18.00PCI: 00:18.01PCI: 00:18.02PCI: 00:18.03PCI: 00:19.00PCI: 00:19.01PCI: 00:19.02PCI: 00:19.03POST: 0x39LinuxBIOS-1.1.6.0Fallback Tue Jul 13 19:16:21 PDT 2004 booting...POST: 0x40Finding PCI configuration type.POST: 0x5fEnumerating static devices...Enumerating buses...POST: 0x24POST: 0x25POST: 0x24POST: 0x25POST: 0x24POST: 0x25POST: 0x55POST: 0x24POST: 0x25POST: 0x55POST: 0x24POST: 0x25POST: 0x55POST: 0x55POST: 0x55donePOST: 0x66Allocating resources...done.POST: 0x88Enabling resourcess...Kid 0 of k8: bridge ctrl says: 0x0Kid 1 of k8: bridge ctrl says: 0x0Kid 2 of k8: bridge ctrl says: 0x0Kid 0 of k8: bridge ctrl says: 0x0Kid 1 of k8: bridge ctrl says: 0x0Kid 2 of k8: bridge ctrl says: 0x0done.Initializing devices...POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00POST: 0x00 Senerade BIOS will keep sending "POST: 0x00" message. - Original Message - From: "Li-Ta Lo" [EMAIL PROTECTED]To: "Tony Cheng" [EMAIL PROTECTED]Cc: "LinuxBIOS" [EMAIL PROTECTED]Sent: Monday, June 28, 2004 8:06 AMSubject: Re: Serenade BIOS On Fri, 2004-06-25 at 17:17, Tony Cheng wrote: Hi Ollie, The Serenade BIOS I've got from CVS Server can not build. Do you see this also? The payload size of my binary is about 55k. The error messages are as follow: objcopy -O binary linuxbios_c linuxbios_payload.bin ./nrv2b e linuxbios_payload.bin linuxbios_payload.nrv2b input/output = 67188/26767 = 2.510 cp linuxbios_payload.nrv2b linuxbios_payload gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o /usr/bin/ld: section .id [ffd8 - ffef] overlaps section .payload [9750 - ffe2] collect2: ld returned 1 exit status make[1]: *** [linuxbios] Error 1 make[1]: Leaving directory `/root/dl/freebios2/targets/amd/serenade/serenade/fallback' make: *** [fallback-rom] Error 1 It is the 64kB size limit problem. Please set the option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 in Config.lb to some lower value. Ollie Thanks Tony
Re: Serenade BIOS
On Wed, 2004-07-14 at 13:17, Tony Cheng wrote: Hi Ollie, I finally got the AMD Seranade board and tried the Serenade Linux BIOS. But I've got the serial port message like following and doesn't have any VGA output. (Seranade board come with a ATI Rage VGA card), I suppose the current Serenade LinuxBIOS doesn't have the VGA support? The serial output has a lot of POST: 0x00 message output at at beginning and ending make me think I probably missed something. The serenade port does not support VGA yet. It is normal to have those post 0x00. The keyboard controller on that board is serously fucked up. LinuxBIOS is trying to init the keyboard when printing these 0x00. Please grep something like init_keyboard and remove it. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V1 PIRQ table
I've reciently learned that my PIRQ table isn't making it into RAM. Going through the code I see that the the last thing that hardware_main does before loading an elf image is call write_tables() which will try and copy the various tables to thier final destination. I don't uderstand how this will work. In order for those writes to go to RAM you have to have your shadowing control set up properly. On my chipset at this stage both reads and writes to areas such as f are forwarded to PCI so the write will fail. I don't see any mention of enableing writes for these ranges to go to RAM. Am I missing something? ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V1 PIRQ table
On Wed, 14 Jul 2004, Richard Smith wrote: I don't uderstand how this will work. In order for those writes to go to RAM you have to have your shadowing control set up properly. On my chipset at this stage both reads and writes to areas such as f are forwarded to PCI so the write will fail. What I do in this case is set CONFIG_COMPRESSED to 0, since if you don't have shadow ram working you're toast. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V1 PIRQ table
ron minnich wrote: On Wed, 14 Jul 2004, Richard Smith wrote: I don't uderstand how this will work. In order for those writes to go to RAM you have to have your shadowing control set up properly. On my chipset at this stage both reads and writes to areas such as f are forwarded to PCI so the write will fail. What I do in this case is set CONFIG_COMPRESSED to 0, since if you don't have shadow ram working you're toast. I don't use compression. I've got shadow ram working fine. ADLO won't boot without it. I was just asking before I try to add something that isn't necessary. The tables depend on shadowing yes? ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V1 PIRQ table
On Wed, 14 Jul 2004, Richard Smith wrote: The tables depend on shadowing yes? no, they don't. If you don't have shadowing, and you don't have compression, then the tables will be there in FLASH and linux will find them. I think I don't understand the problem, I misread it, so I'll go back and reread. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: How to build vgabios
On Wed, 2004-07-14 at 16:47, David Aubin wrote: Hello, I am having difficulty building vgabios. Can someone please give me a hand? I took the latest code off of the freebios2 branch (6 days old, by Ollie) I get the following Errors when I try to compile. It looks like I am missing files in the drop #include pci/pci.h you need to rpm -i (yast ??) pciutil-devel. Ollie ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00
Richard, Thanks for your suggestions. I tried them, however, the system still hangs when jumping to boot code at 0x7c00. Examine this file and see if it has the BIOS extension signature of 0xaa55 (or 0x55aa depending on what endian you view it as) You should also see some text iding the bios. I enabled all shadowing and found 0xaa55 and bios copyright information at the beginning of file. In ./util/ADLO/bochs/bios/rombios.c there should be a #define DEBUG_SERIAL. Set that to 1 and all of the bios messages will go out the serial port. My source has DEBUG_SERIAL and by default it is enabled. Nothing appears for this default configuration. I also tried to disabled DEBUG_SERIAL, but no video appears either. Right now I suspect that something wrong with loder.s. My question is how to debug loader.s? Thanks again. Simon Cheng www.msica.com ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: ADLO: linuxbios v1 hangs after jumping to boot code at 0x7c00
Simon Xin Cheng wrote: Richard, Thanks for your suggestions. I tried them, however, the system still hangs when jumping to boot code at 0x7c00. Right now I suspect that something wrong with loder.s. My question is how to debug loader.s? Thanks again. The most likely problem is that your shadowing is not working. Right after loader finishes copying to ram and you have enabled reads to be routed to RAM dump the first few bytes from 0x7c00 and dump them out the seial port and make sure things really got copied to RAM. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
