coreboot April 2004

coreboot@coreboot.org

47 participants
130 discussions

Open bios dev/bios bug report
by Mathieu Deschamps 23 Apr '04

23 Apr '04

Hello, I want to make /dev/bios work because LinuxBIOS flash utils just write whereas /dev/bios is IMO a elegant way to read/write/>? to many bios. My mainboard bios is a SST29EE020 (which is supported to write) I do a setpci -s 0:11.0 40b.54 that's ok considering my lspci' output: Device: 00:00.0 Class: Host bridge Vendor: VIA Technologies, Inc. Device: VT8601 [Apollo ProMedia] SVendor: VIA Technologies, Inc. SDevice: 6010 Rev: 05 00: 06 11 01 06 06 00 90 a2 05 00 00 06 00 08 00 00 10: 08 00 00 d0 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 06 11 10 60 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 Device: 00:01.0 Class: PCI bridge Vendor: VIA Technologies, Inc. Device: VT8601 [Apollo ProMedia AGP] 00: 06 11 01 86 07 00 30 a2 00 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 00 00 20: 00 e0 f0 e2 f0 ff 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00 Device: 00:11.0 Class: ISA bridge Vendor: VIA Technologies, Inc. Device: VT8231 [PCI-to-ISA Bridge] SVendor: VIA Technologies, Inc. SDevice: 6010 Rev: 10 00: 06 11 31 82 87 00 10 02 10 00 01 06 00 00 80 00 10: 00 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 06 11 10 60 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 Device: 00:11.1 Class: IDE interface Vendor: VIA Technologies, Inc. Device: VT82C586/B/686A/B PIPC Bus Master IDE SVendor: VIA Technologies, Inc. SDevice: 6010 Rev: 06 ProgIf: 8a 00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 d0 00 00 00 00 00 00 00 00 00 00 06 11 10 60 30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 00 00 Device: 00:11.2 Class: USB Controller Vendor: VIA Technologies, Inc. Device: USB SVendor: VIA Technologies, Inc. (Wrong ID) SDevice: USB Controller Rev: 1e 00: 06 11 38 30 07 00 10 02 1e 00 03 0c 08 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 d4 00 00 00 00 00 00 00 00 00 00 25 09 34 12 30: 00 00 00 00 80 00 00 00 00 00 00 00 03 04 00 00 Device: 00:11.3 Class: USB Controller Vendor: VIA Technologies, Inc. Device: USB SVendor: VIA Technologies, Inc. (Wrong ID) SDevice: USB Controller Rev: 1e 00: 06 11 38 30 07 00 10 02 1e 00 03 0c 08 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 d8 00 00 00 00 00 00 00 00 00 00 25 09 34 12 30: 00 00 00 00 80 00 00 00 00 00 00 00 03 04 00 00 Device: 00:11.4 Class: Bridge Vendor: VIA Technologies, Inc. Device: VT8235 ACPI SVendor: VIA Technologies, Inc. SDevice: 6010 Rev: 10 00: 06 11 35 82 00 00 90 02 10 00 80 06 00 00 00 00 10: 00 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 06 11 10 60 30: 00 00 00 00 68 00 00 00 00 00 00 00 00 00 00 00 Device: 00:11.5 Class: Multimedia audio controller Vendor: VIA Technologies, Inc. Device: VT82C686 AC97 Audio Controller SVendor: VIA Technologies, Inc. SDevice: 6010 Rev: 40 00: 06 11 58 30 01 00 10 02 40 00 01 04 00 00 00 00 10: 01 dc 00 00 01 e0 00 00 01 e4 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 10 60 30: 00 00 00 00 c0 00 00 00 00 00 00 00 0a 03 00 00 Device: 00:12.0 Class: Ethernet controller Vendor: VIA Technologies, Inc. Device: VT6102 [Rhine-II] SVendor: VIA Technologies, Inc. SDevice: VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Rev: 51 00: 06 11 65 30 07 00 10 02 51 00 00 02 08 20 00 00 10: 01 e8 00 00 00 00 00 e3 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 02 01 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 03 08 Device: 01:00.0 Class: VGA compatible controller Vendor: Trident Microsystems Device: CyberBlade/i1 SVendor: Trident Microsystems SDevice: 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 i do insmod bios ; dmesg| tail -3 says : BIOS driver v0.3.2 (writing disabled) for 2.4.20-8 BIOS: host bridge is 1106, 601, 0 BIOS: isa bridge is 1106, 8231, 88 BIOS: 256k flashchip (ID 0x10bf) found at physical address 0xfff80000 (va=0xc80db000+0x180000). so that seems to me quite ok but doing cat /proc/bios i got Erreur de segmentation (Segfault) and then doing dmesg| tail -30, I got: BIOS driver v0.3.2 (writing disabled) for 2.4.20-8 BIOS: host bridge is 1106, 601, 0 BIOS: isa bridge is 1106, 8231, 88 BIOS: 256k flashchip (ID 0x10bf) found at physical address 0xfff80000 (va=0xc80db000+0x180000). invalid operand: 0000 bios via82cxxx_audio uart401 ac97_codec sound soundcore parport_pc lp parport autofs via-rhine mii ipt_REJECT iptable_filter ip_tables keybdev mousedev hid in CPU: 0 EIP: 0060:[<c80d43ea>] Not tainted EFLAGS: 00010283 EIP is at bios_read_proc [bios] 0xaa (2.4.20-8) eax: 000000cb ebx: 00000000 ecx: 000000cb edx: 00000000 esi: 00000001 edi: 00000c00 ebp: 00000030 esp: c7433f30 ds: 0068 es: 0068 ss: 0068 Process cat (pid: 2983, stackpage=c7433000) Stack: c5a7d0b6 c80d6eee c80d6ea4 c80d6d6b 00000005 00000000 00000001 c6cd5d40 00000c00 c5a7d000 00001000 c01602e6 c5a7d000 c7433f88 00000000 00000c00 c7433f84 00000000 c7432000 c6cd5d40 00000000 00000001 c5a7d000 0804cd48 Call Trace: [<c80d6eee>] .rodata.str1.1 [bios] 0x9ce (0xc7433f34)) [<c80d6ea4>] .rodata.str1.1 [bios] 0x984 (0xc7433f38)) [<c80d6d6b>] .rodata.str1.1 [bios] 0x84b (0xc7433f3c)) [<c01602e6>] proc_file_read [kernel] 0xb6 (0xc7433f5c)) [<c013fa25>] sys_read [kernel] 0x85 (0xc7433f9c)) [<c0109103>] system_call [kernel] 0x33 (0xc7433fc0)) Code: 0f 4f 44 24 3c 83 c4 1c 5b 5e 5f 5d c3 0f b7 85 74 99 0d c8 What went wrong ? Plus what is strange is that it can anyway read the bios with cat /dev/bios which is truely 262144 bytes but I'am wondering if it's clean or not, maybe i'am reading another bios. On this point actually, I can't exactly figure out how i could say to dev/bios read this bios or read that one. It so up levelled :) Am wandering where I can parameter it :) Please explain me, I founding a big hope and true interest on dev/bios. thanks in advance mathieu

4 7

Merge filo into Etherboot.
by YhLu 22 Apr '04

22 Apr '04

Eric, I have merged the filo into the Etherboot 5.2.4 and make use Etherboot Makefile etc to produce tg3--filo.zelf or filo.zelf Todo: to get rid of duplicate static function in filo. Can you put that changes in the Etherboot and as one official distribution? YH

2 1

On which mainboards does LinuxBIOS function best?
by Ken Fuchs 22 Apr '04

22 Apr '04

The status web page has only three values for each mainboard: unsupported, unstable (not verified stable) and stable. There doesn't seem to be an easy way to tell whether one mainboard works better than another. How does one know whether LinuxBIOS on a particular mainboard supports multiuser X for example? How does one determine which DoC models are supported, i.e. M2800, M2802, M2808, M2811, M3331, etc. for a particular mainboard BIOS socket? I assume the mainboards with 512KB (2Mb) BIOS should contain a full compressed LinuxBIOS kernel. Would 1MB or more be recommended? I'm looking for an inexpensive 1P AMD mainboard on which I can install LinuxBIOS with relative ease and gain maximum LinuxBIOS functionality from it. I would also like to follow one of the HOWTOs or create a new HOWTO for such a mainboard. Any mainboard suggestions? Would a DoC be required? Sincerely, Ken Fuchs <kfuchs(a)winternet.com>

1 0

答复: ATI rage xl.init
by YhLu 22 Apr '04

22 Apr '04

Ron, I have enabled the ati rage xl frame buffer in LinuxBIOS, also moved the btext.c to the LinuxBIOS. So I can get output on CRT in LinuxBIOS after the ati device init. I'm going to add one console besides console8250.c and vgaconsole.c. Please suggest the console name for that: 1. fbconsole.c 2. or btextconsole.c to honor the btext.c author The btext.c is in the linux/arch/ppc/kernel/btext.c Regards YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月14日 15:01 收件人: Brian Maly 抄送: linuxbios(a)clustermatic.org 主题: Re: ATI rage xl.init Ollie knows better than me but I'm guesssing there are still some registers not set right in linuxbios. Note that to date for our nvidia stuff we've had to set these registers by hand in a shell script. VGA is still not quite right, but we're trying to get it. ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

3 2

答复: flash_rom start and size
by YhLu 22 Apr '04

22 Apr '04

For example, 1. I only want to let end user to flash normal part [0-384k), and don't let him touch fallback part [384k, 512k). 2. or I only want to update the payload image in the beginning, [0,64k). Regards Yinghai Lu -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月21日 9:09 收件人: YhLu 抄送: LinuxBIOS 主题: Re: flash_rom start and size On Tue, 2004-04-20 at 20:06, YhLu wrote: > Ollie or David, > > Can you modify the flash_rom to take start and size command line? > > I mean > > Flash_rom -start=0k -size=384k xxxx.rom > > And xxxx.rom only to be 384k. > Why do you want to do this ? You should prepare the image the same size as your flash chip. There are techinical difficulty doing this. Most flash parts are block/sector erase and byte program. There is no general way to start from an abitrary address to any size. Ollie > Regards > > YH >

3 2

descriptive subject ;)
by Mathieu Deschamps 22 Apr '04

22 Apr '04

* Mathieu Deschamps <mdeschamps(a)mangrove-systems.com> [040421 09:48]: > ps final 'peak' : IMO, putting [linuxbios] before titles is a *bad* > idea : on a linuxbios maillist, the only root topic is linuxbios > obviously so no need to repeat it in title ... >I disagree. It's a good thing to detect quickly and easily whether >a mail is private or coming in via the list. > >Stefan Simple to notice this : all the message in which I'am CC i got them twice in my mail box. quick & simple. Otherwise I got them just once (coming just from via the list). Honestly i found this sole system enough, what is more some message I believed to be not interessing to me (after reading) appear to be relevant later on : maybe it's because i'am a rookie :) mathieu

1 0

descriptive subjects ;)
by Stefan Reinauer 22 Apr '04

22 Apr '04

1 0

EPIA (NOT EPIA-M) VGA
by ron minnich 22 Apr '04

22 Apr '04

Sorry, I've lost track. Has anyone here tested EPIA VGA? Does it work? I've just gotten a request for an EPIA with VGA running Filo. ron

1 0

答复: ATI rage xl.init
by YhLu 21 Apr '04

21 Apr '04

I use stefan Linuxbios snapshots to produce diff. If there still problem, I would send you my tree tar ball. Regards YH -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月21日 14:47 收件人: YhLu 抄送: ron minnich; Stefan Reinauer; LinuxBIOS 主题: Re: ATI rage xl.init On Tue, 2004-04-20 at 19:38, YhLu wrote: > Ron, > > Please commit ati rage xl support. > > 1. ati rage xl support > 2. add btext_console to use rage xl fb. > 3. enable pnp init calling > 4. superio Winbond: real enable/disable device. > 5. superio Winbond: enable HW > 6. Tyan S2850 support update > 7. Tyan S2875 support added. > 8. Move some PCI master enable driver to /driver dir. > > Stefan, > > Please test the filo too, I add the btext_console into it. > On vocation? Why using stepan(a)openbios.org ? > > there are some conflicts between your tree and the current CVS. Could you do cvs update and send me the patch again ? Ollie

1 0

答复: flash_rom start and size
by YhLu 21 Apr '04

21 Apr '04

It could only process 64k block. YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月21日 10:29 收件人: YhLu 抄送: Li-Ta Lo; LinuxBIOS 主题: Re: flash_rom start and size for the Alphas long ago I modified flash_rom as follows: flash_rom e <start block #> <length in blocks> Erase the blocks flash_rom r <start block #> <length in blocks> read the blocks flash_rom p <file name> <start block #> program with file name starting at start block #. Program up to the limit of the file size or the flash size, whichever is small. This was for partial programming. flash_rom s <start block #> <lenght in blocks> program using stdin as the data, starting at start block # and for length blocks OR eof on stdin, whichever was smaller. This was pretty handy for the DS10, which had 2 MB of flash in 64KB blocks, and had areas of flash we could not rewrite. maybe we need this for the general case? ron

2 1

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot April 2004