coreboot

coreboot@coreboot.org

12 participants
39779 discussions

RE: ATI rage xl.init
by ron minnich 26 Apr '04

26 Apr '04

On Sun, 25 Apr 2004, Yinghai Lu wrote: > 8. > > Sometimes, if you not enable PCI master, the device can not work properly in > Linux. > > But Eric/Ron didn't enable that in PCI main loop, because some devices don't > need that. because it is a bad idea to do this. The Linux driver should do this, not LinuxBIOS. We have always resisted this because it can cause real trouble if the device decides to do an I/O. ron

2 1

Re: ATI rage xl.init
by YhLu 25 Apr '04

25 Apr '04

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 ? Regards YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月20日 12:48 收件人: YhLu 抄送: Brian Maly; linuxbios(a)clustermatic.org 主题: Re: 答复: ATI rage xl.init On Tue, 20 Apr 2004, YhLu wrote: > 2. or btextconsole.c to honor the btext.c author sounds good. Credit where credit is due. ron

5 4

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

23 Apr '04

So I need to produce another patch except 3, 4 & 5? -----邮件原件----- 发件人: Li-Ta Lo [mailto:ollie@lanl.gov] 发送时间: 2004年4月23日 11:00 收件人: YhLu 抄送: ron minnich; Stefan Reinauer; LinuxBIOS 主题: Re: ATI rage xl.init On Fri, 2004-04-23 at 11:56, YhLu wrote: > You only commit 4 & 5 ? > I haven't commit anything yet. I am busy working on the ibm/e325 HT enumeration problem. I will look at the patch next week. Ollie > -----邮件原件----- > 发件人: 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 > >

3 2

Re: ATI rage xl.init
by YhLu 23 Apr '04

23 Apr '04

You only commit 4 & 5 ? -----邮件原件----- 发件人: 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

2 1

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

23 Apr '04

In the MB Config.lb, you need to enable keyboard and mouse in superio part. YH -----邮件原件----- 发件人: Brian Maly [mailto:bmaly@angstrom.com] 发送时间: 2004年4月22日 12:37 收件人: YhLu 抄送: ron minnich; linuxbios(a)clustermatic.org 主题: Re: 答复: ATI rage xl.init I first wanted to say how nice it is to see linux boot from linuxbios with graphical console and have X come up... a beautiful thing! So now when linux boots, video looks good, but I am unable to use the mouse + keyboard. I have CONFIG_CONSOLE_SERIAL8250 defined in linuxbios and I think this may have something to with it (but then again this could just be a generic linux problem and nothing to do with linuxbios). Any ideas? Will I need btextconsole.c to fix this? Im just trying to determine if I need to modify something in linuxbios resolve this? Otherwise Ill assume this to be a more generic linux console problem and proceed from there. any input is welcome. thanks... -Regards, Brian On Tue, 2004-04-20 at 15:41, YhLu wrote: > 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 3

Via epia m-II BiosSavior problems
by Ignacio Verona 23 Apr '04

23 Apr '04

Hi! Just a few minutes ago I've built my first linuxbios romimage. This week, I bought a RD1-PL BiosSavior for my MB (PLCC socket) and installed it. For all this week, the BiosSavior has been working, with the switch on "ORG" position, and correctly loading factory bios. And, for writing my new BIOS to the "backup" memory of the BiosSavior, I did put the switch to the RD1 position, and then #./flash_rom romimage. Ok, it seems to be well written to the memory, but before trying to load the new linuxbios I wanted to boot using the old and... It will not boot!! With the switch on ORG position nothing happens (I dont know what happens with linuxbios, I still do not have a serial cable) but the only way I can boot my mobo is removing the biossavior and installing the original flash chip into the original socket... Did I bought the wrong BiosSavior? What happens?? Thanks.

1 0

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 23 Apr '04

23 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot