coreboot

coreboot@coreboot.org

3 participants
39562 discussions

w49f002u.c ?
by Damien Charlet 22 Sep '03

22 Sep '03

First, Thank you for your answers. Unfortunately I tried again and again today and I can't properly flash my winbond chip. I even tried to nice -19 flash_rom, remove the print's but it doesn't help. I dumped several time the content burned, and there are each time several errors, not twice the same, randomly placed across the chip. The wrong bytes are often burned as FF, but this is not always the case. What else could I try ? Where should I dig into ? Thx Damien -- Damien(.)Charlet(AT pu-pm.univ-fcomte.fr) Doctorant UIN:78754463 Laboratoire d'Informatique de l'Universite de Franche-Comte FRE CNRS 2661 - Centre de Developement du Multimedia de Montbeliard Tel: +33-(0)3.81.99.47.76 damien.charlet(a)pu-pm.univ-fcomte.fr

3 5

Re: epia800 direct vga working
by Nathanael D. Noblet 22 Sep '03

22 Sep '03

Hello, So I've got the epia800 working with the original BIOS that was extracted from the original BIOS. I've been looking over the code that was submitted, and as well as the difference between register settings on boot with regular BIOS settings and LinuxBIOS settings. I have been trying to get DirectFB to work with the epiafb module. It works when I boot with regular bios, but not the LinuxBIOS version. Here are the differences between the two. ORIGINAL 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) 00: 23 10 00 85 07 00 b0 02 6a 00 00 03 00 20 00 00 10: 00 00 80 e1 00 00 00 e2 00 00 00 e1 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 23 10 00 85 30: 00 00 00 00 80 00 00 00 00 00 00 00 0b 01 00 00 LINUXBIOS with extracted VGABIOS 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) 00: 23 10 00 85 03 00 b0 02 6a 00 00 03 00 40 00 00 10: 00 00 80 fd 00 00 80 fe 00 00 00 fe 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 23 10 00 85 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 01 00 00 I remember working on a sis530 board that had to set particular registers, I'm wondering if someone can give me a little tutorial on how to read these values and turn them into a corresponding register address so that I can play around with the settings to get it all working. Once I have that all working like the original bios I guess the direct vga changes could incorporate the changes and we would not need the VGABIOS if I am not mistaken? I'd like to help, but need to know how to go about reading the above in a better way then I know right now... -- Nathanael D. Noblet <nathanael(a)gnat.ca> Gnat Solutions

2 1

linuxbios on epia-m -- not starting
by Niki Waibel 22 Sep '03

22 Sep '03

linuxbios does not start ... i can see: === LinuxBIOS-1.0.0 Mon Sep 22 02:17:36 CEST 2003 starting... Copying LinuxBIOS to ram. Jumping to LinuxBIOS. === that's it. first i tought it is a mem problem (512MB Infineon CL2). i changed 0x350 to 0x150 in src/northbridge/via/vt8623/raminit.inc and i've activated ../freebios/src/ram/ramtest.inc in ../freebios/src/mainboard/via/epia-m/Config. it seems that everything is ok: === LinuxBIOS-1.0.0 Mon Sep 22 12:38:53 CEST 2003 starting... Testing SDRAM : 00000000-0009ffff SDRAM fill: 0009ffff SDRAM verify: 0009ffff Done. Copying LinuxBIOS to ram. Jumping to LinuxBIOS. === so i tried to figure out where the stop occurs. i verified if the code is copied correctly: === LinuxBIOS-1.0.0 Mon Sep 22 02:17:36 CEST 2003 starting... Copying LinuxBIOS to ram. NIKI: Jumping to LinuxBIOS. src: 000f0b70 dst: 00004000 size: 0000aa8c src_code: 010f2efa00405215 dst_code: 010f2efa00405215 === -> fine. unfort i dont know much about x86 asm... but it seems that the problem is somewhere in c_start.s ... if i put movl $0xfffe0000, %edi jmp *%edi to the top of the _start: function then linuxbios loops. (i just wanted to check if the copied code is executed...) is that a better way to find out what's wrong? by the way: === gcc -x assembler-with-cpp -DASSEMBLY -E ... crt0.S > crt0.s gcc ... -o crt0.o crt0.s crt0.S: Assembler messages: crt0.S:163: Warning: indirect jmp without `*' === instead of: leal _iseg, %edi jmp %edi shouldn't it be: leal _iseg, %edi jmp *%edi ? niki w. waibel

3 7

/dev/nvram useable?
by Hubert Denkmair 22 Sep '03

22 Sep '03

Hello again, does anyone know if/how the linux /dev/nvram device is working with linuxbios and my Epia5000? I would love to store some status information of my car mp3 player in the nvram, since power supply can be cut any time and I want my harddisk to be mounted readonly. On linuxbios startup, the following two lines are printed: >RTC Init >Invalid CMOS LB checksum And after every linuxbios boot, when switching back to the original BIOS, it complains "CMOS checksum error, defaults loaded..." Writing to /dev/nvram raises no error (echo "hello" > /dev/nvram), but reading from /dev/nvram results in "reading `/dev/nvram': Input/output error" :( (How) can I use the nvram? Is there another possibility, maybe without the /dev/nvram device driver? Hubert

2 1

about SIS630 base mainboard & direct VGA support
by bendany 22 Sep '03

22 Sep '03

hi all, I am working with a mainboard similar to PCCHIPS m758lmr+. I want to enable VGA support. but I get some error message. ======================================================== PCCHIPS m758lmr+ (and similar)...Entering the initregs process Southbridge fixup done for SIS 603 handle_superio start, nsuperio 1 handle_superio: Pass 2, check #0, s 0000bba0 s->super 0000bef8 handle_superio: Pass 2, Superio SiS 950 handle_superio: port 0x2e, defaultport 0x2e handle_superio: Using port 0x2e Call finishup handle_superio: Pass 2, done #0 handle_superio done INSTALL REAL-MODE IDT DO THE VGA BIOS found VGA: vid=1039, did=6300 0x55 0xaa 0x60 0xe9 0x53 0x2 0x31 0x2e 0x30 0x37 0x2e 0x35 0x34 0x20 0x2d 0x6a biosint: # 0x6, eax 0x0 ebx 0x10 ecx 0x20 edx 0x9d2e biosint: ebp 0x12060 esp 0xff6 edi 0xe0ac esi 0x846a2 biosint: ip 0x3 cs 0x0 flags 0x46 biosint: Unsupport int #0x6 biosint: # 0x6, eax 0x0 ebx 0x10 ecx 0x20 edx 0x9d2e biosint: ebp 0x12060 esp 0xff6 edi 0xe0ac esi 0x846a2 biosint: ip 0x3 cs 0x0 flags 0x46 biosint: Unsupport int #0x6 biosint: # 0x6, eax 0x0 ebx 0x10 ecx 0x20 edx 0x9d2e biosint: ebp 0x12060 esp 0xff6 edi 0xe0ac esi 0x846a2 biosint: ip 0x3 cs 0x0 flags 0x46 ........................... =================================================================== It seems that the biosint unsupport some bioscall. how can I solve this problem? btw: this mainboard works fine with LinuxBIOS+FILO. best reguards. bendany.

2 1

EPIA5000 & parallel port
by Hubert Denkmair 21 Sep '03

21 Sep '03

Hello again, linuxbios+filo works now on my EPIA, thanks to everybody who helped me :-) There seems to be just one more problem - Is it possible that the parallel port is not initialized correctly by LinuxBIOS? I need it for my LCD which is controlled by LCDproc. With my original BIOS, everything works smoothly - with or without kernel parallel port support. But with LinuxBIOS nothing happens on the Display, seems as if no data is written to the port. LCDproc doesn't complain at all, but that's no surprise since it does not get any feedback from the LCD device anyways. Additionally, seems as if a kernel compiled with parallel port support doesn't find it either: --- imaudo:/# echo "Hallo" > /dev/lp0 bash: /dev/lp0: No such device --- Thanks for your help, again! Hubert

2 1

flash_rom & epia 800
by Damien Charlet 21 Sep '03

21 Sep '03

Hello list, First of all thank all of you for this great work. I'd like to flash my epia 800 + bios savior with linuxbios. Un fortunately flash_rom doesn't manage to write correctly the rom image, even after numerous tries. I removed the prints statement in w49f002u.c (the chip detected) to see if that helps with timings, but it doesn't change anything. The version I use is last friday's CVS. I've seen that different people have had problems of the same type, how have you solved that ? thx Damien -- Damien(.)Charlet(AT pu-pm.univ-fcomte.fr) Doctorant UIN:78754463 Laboratoire d'Informatique de l'Universite de Franche-Comte FRE CNRS 2661 - Centre de Developement du Multimedia de Montbeliard Tel: +33-(0)3.81.99.47.76 damien.charlet(a)pu-pm.univ-fcomte.fr

2 1

Re: EPIA5000 & parallel port
by Sven Luebke 21 Sep '03

21 Sep '03

At 11:49 21.09.2003 +0200, you wrote: Hi Hubert! >There seems to be just one more problem - Is it possible that the parallel >port is not initialized correctly by LinuxBIOS? It's not initialized at all... >I need it for my LCD which is controlled by LCDproc. > >With my original BIOS, everything works smoothly - with or without kernel >parallel port support. But with LinuxBIOS nothing happens on the Display, >seems as if no data is written to the port. LCDproc doesn't complain at >all, but that's no surprise since it does not get any feedback from the >LCD device anyways. >Additionally, seems as if a kernel compiled with parallel port support >doesn't find it either: I had the same problem and implemented the parallel port initialization. It is working now, patches sent to Ron Minnich, but he wanted to do some cosmetic changes next week. If you are in a hurry, you can download it here, http://www.mikrosol.de/southbridge.c copy it to freebios\src\superio\via\vt8231\ http://www.mikrosol.de/setup_serial.inc copy it to freebios\src\southbridge\via\vt8231\ then recompile, flash and lcdproc should work now! Best regards, Sven

1 1

Homemade BIOS switch for EPIA boards (and others with 2MBit chips)
by Sven Luebke 21 Sep '03

21 Sep '03

Hi! I didn't find the BIOS Sa**our here in Germany so I made my own one. Of course this hack is nothing special, but perhaps useful for beginners! EPIA5000 owners don't have to modificate the board itself. Background: The capacity of the new flash chip is twice as large (4MBit) as the original chip, so we can burn a full BIOS in the lower part of the memory AND in the upper part of the memory. To choose between them, we use the highest address pin (A18). If A18 is low, the "lower" BIOS is selected, if it is high, the "upper" BIOS is activated (you need a reboot of course). I use this setup since 5 days and everything is working as it should. Please don't build it, if you do not know what I'm talking about!!! Use it at your own risk !!!! Installation: Take a AMD 29F040(B)-70 (you can find them on ebay) flash chip, bend Pin 1 (A18) in the other direction, as close to the chip as possible. Then solder an isolated wire to this pin, isolate this pin EVERYWHERE with a piece of tape (it's IMPORTANT, that it doesn't get contact with the PLCC socket pin, you can't bend it so close to the chip) and solder this wire to the "middle" contact (which connects EITHER to the left pin OR to the right pin) of a 3-pin-switch. Now you have to find a 5V and GND source, solder/connect two isolated wires to them and solder the other side of the wires to the two other pins of the 3-pin-switch. For other boards than the EPIA5000 you have to be sure, that the supply voltage of the flash chip (called VCC) is 5V, otherwise you have to measure it and search for a source equal to the measured voltage (!!!they have to be the same!!!). For the EPIA5000 you can use the "Modem wakeup" connector, take an appropriate plug inclusive wires and connect the other sides of the wire to the switch (that's what I did). If your board is powered on, TURN OFF YOUR BOARD NOW, insert the AMD flash chip (take out the SSF 39SF020A before :-) ) and make sure, that pin 1 of the flash chip has no electrical contact to the PLCC socket contact. Make sure that you soldered your switch as described above: Pin 1 of the flash chip has to be connected (through the switch) to EITHER VCC (for EPIA = 5V) OR GND. If everything was OK, you are ready with the hardware part. Reinsert the original flash chip, boot Linux, get the original BIOS file, replace /freebios/util/flash_and_burn/flash_rom.c with this one at http://www.mikrosol.de/flash_rom.c (it is the SAME sourcecode, but the size of the 29F040 is reduced to burn only 256KB), compile it, take the chip out while power is turned on, insert the soldered AMD chip, write the original bios to the flash chip (if you have an EPROM Programmer, use it, cause it is safer) and mark the position of the switch. Everytime you will switch to this position, you are booting the ORIGINAL BIOS. If you want to burn the other part of the memory, switch to the other side (while power is on and you are at the console) and burn it. Be aware that both parts of the memory are writable, so you have to check the position of the switch BEFORE you are flashing. Flashing at the marked position of the switch is only necessary, if you want to replace the original bios. That's all! Really helpful I think! Best regards, Sven

1 0

Fw: about util/vgabios
by rimy2000 20 Sep '03

20 Sep '03

----- Original Message ----- From: "ron minnich" <rminnich(a)lanl.gov> To: "elife elife" <rimy2000(a)hotmail.com> Cc: <linuxbios(a)clustermatic.org> Sent: Sunday, September 07, 2003 12:00 PM Subject: Re: about util/vgabios > On Sun, 7 Sep 2003, elife elife wrote: > > > > > Hi, > > I am trying util/vgabios but encounter a strange problem: testbios seems > > fetching wrong instruction > > > > [root@linux vgabios]# ./testbios -s 64k -t ~/lb/500video.bios.bin > > running file /root/lb/500video.bios.bin > > No base specified. defaulting to 0xc0000 > > No initial code segment specified. defaulting to 0xc000 > > No initial instruction pointer specified. defaulting to 0x0003 > > Switching to single step mode. > > AX=00ff BX=0000 CX=0000 DX=0080 SP=fff8 BP=0000 SI=0000 > > DI=0000 > > DS=0040 ES=0000 SS=0030 CS=c000 IP=0005 NV UP DI PL NZ NA PO > > NC > > c000:0003 eb53 JMP 58 > > c000:3 - > > AX=00ff BX=0000 CX=0000 DX=0080 SP=fff8 BP=0000 SI=0000 > > DI=0000 > > DS=0040 ES=0000 SS=0030 CS=c000 IP=005a NV UP DI PL NZ NA PO > > NC > > c000:0058 0000 ADD [BX+SI],AL > > c000:58 - > > > > [root@linux lb]# od -x 500vi* |more > > 0000000 aa55 eb60 3753 3034 3030 c237 2a8a 522a > > 0000020 5345 5245 4556 2044 00b1 4f46 2052 4249 > > 0000040 204d 4f43 504d 5441 4249 4c49 5449 2a59 > > 0000060 2a2a a807 0000 1090 3130 302f 2f37 3032 > > 0000100 3230 0000 2e31 3431 3c20 4144 203e 2020 > > 0000120 3156 2033 2020 2020 83e9 075e 6f43 7970 > > > > testbios said c000:0058 is 0000 but in file, it's E9835E JMP > > 5EDE > > > > Best Regards! > > interesting, I have seen a similar sort of problem but was not sure what > it was. I'll try to take a look. > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot