From steve at nexpath.com Thu Apr 1 00:15:01 2004 From: steve at nexpath.com (Steve Gehlbach) Date: Thu Apr 1 00:15:01 2004 Subject: More n00by questions... In-Reply-To: References: Message-ID: <406BAB7A.9050403@nexpath.com> Vic Berdin wrote: >>Sis630 steps The pcchips 787cl+ is a sis630 mainboard, if that helps. The config is at util/config/pcchips787.config. This is all v1. It does not use DOC mem. -Steve From mdeschamps at mangrove-systems.com Thu Apr 1 02:32:01 2004 From: mdeschamps at mangrove-systems.com (root) Date: Thu Apr 1 02:32:01 2004 Subject: nowby question Message-ID: <1080806129.1220.36.camel@Calliphara> hello, I've been watching an reading a lot in this interesting adventure... I've been trying to get Linuxbios work first on a SiS530 but through mailing list, tree docs, and surroundings i didn't find out enough support on this. So i decide to switch to another board that have been greatly tested. I am willing now to make LinuxBios work on a Apollo PLE133 mainboard, this is a VIA EPIA chipset based motherboard (http://www.viavpsd.com/product/epia_mini_itx_spec.jsp?motherboardId=21) 00.0 Host bridge: VIA 0601 (rev5) 01.0 PCI bridge : VIA 8601 11.0 ISA bridge : VIA 8231 11.1 IDE interf : VT82C586 (rev6) 11.2 USB interf : VT82C586B (rev 1e) 11.3 USB interf : VT82C586B (rev 1e) 11.4 Bridge : VIA 8235 (rev10) 11.5 audio : VIA 3058 (rev 40) 12.0 Ethernet : VIA 3065 (rev51) 1:00.0 VGA Trident: 8500(rev 6a) on a via C3 CPU working kernel 2.4.18 I'am looking for a kernel patch for VIA Epia on this kernel but couldn't find one. Would it mean it needn't a fix ? Also wandering on a "easiest" way to get my config work : on v1 or in v2 (I got to take care of the portability with v1-v2 issues?) Knowing that at the end (of this adventure:) I will make it boot on a M-DoC 2000... yet firstly I'll burn a bios chip and boot a IDE HD... step by step :) This is a RFC, so anything helpful on my methods, developpement risk, wayouts, adviced other docs are very welcome Thanks. Mathieu Deschamps, From mdeschamps at mangrove-systems.com Thu Apr 1 05:08:01 2004 From: mdeschamps at mangrove-systems.com (root) Date: Thu Apr 1 05:08:01 2004 Subject: VIA EPIA question Message-ID: <1080815526.1220.38.camel@Calliphara> hello, I've been watching an reading a lot in this interesting adventure... I've been trying to get Linuxbios work first on a SiS530 but through mailing list, tree docs, and surroundings i didn't find out enough support on this. So i decide to switch to another board that have been greatly tested. I am willing now to make LinuxBios work on a Apollo PLE133 mainboard, this is a VIA EPIA chipset based motherboard (http://www.viavpsd.com/product/epia_mini_itx_spec.jsp?motherboardId=21) 00.0 Host bridge: VIA 0601 (rev5) 01.0 PCI bridge : VIA 8601 11.0 ISA bridge : VIA 8231 11.1 IDE interf : VT82C586 (rev6) 11.2 USB interf : VT82C586B (rev 1e) 11.3 USB interf : VT82C586B (rev 1e) 11.4 Bridge : VIA 8235 (rev10) 11.5 audio : VIA 3058 (rev 40) 12.0 Ethernet : VIA 3065 (rev51) 1:00.0 VGA Trident: 8500(rev 6a) on a via C3 CPU working kernel 2.4.18 I'am looking for a kernel patch for VIA Epia on this kernel but couldn't find one. Would it mean it needn't a fix ? Also wandering on a "easiest" way to get my config work : on v1 or in v2 (I got to take care of the portability with v1-v2 issues?) Knowing that at the end (of this adventure:) I will make it boot on a M-DoC 2000... yet firstly I'll burn a bios chip and boot a IDE HD... step by step :) This is a RFC, so anything helpful on my methods, developpement risk, wayouts, adviced other docs are very welcome Thanks. Mathieu Deschamps, _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Thu Apr 1 09:52:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 1 09:52:01 2004 Subject: More n00by questions... In-Reply-To: Message-ID: So, if you want to write an update howto ;-) let's start over. what's the motherboard and motherboard chipset. Sorry, this project is changing so fast it's hard to keep the docs up to date. ron From rminnich at lanl.gov Thu Apr 1 12:06:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 1 12:06:00 2004 Subject: VIA EPIA question In-Reply-To: <1080815526.1220.38.camel@Calliphara> Message-ID: On 1 Apr 2004, root wrote: > I am willing now to make LinuxBios work on a Apollo PLE133 mainboard, > this is a VIA EPIA chipset based motherboard > (http://www.viavpsd.com/product/epia_mini_itx_spec.jsp?motherboardId=21) you would want to use V2 with that, and the process overall is MUCH easier than V1. no kernel patch needed so far on this board. ron From michaelh at cipheroptics.com Thu Apr 1 13:13:01 2004 From: michaelh at cipheroptics.com (Michael Hale) Date: Thu Apr 1 13:13:01 2004 Subject: abit SI-1Ns Message-ID: Hi all, I have an abit SI-1Ns with an intel 845GV chipset. I would like to put linuxbios on this board... but according to the status page it looks like this board is not supported. I am an applications programmer, not a hardware programmer... so I am somewhat at a loss as to where I should start. Can someone point me in the right direction for getting linuxbios running on this board? Thanks, Michael From rminnich at lanl.gov Thu Apr 1 14:15:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 1 14:15:01 2004 Subject: abit SI-1Ns In-Reply-To: Message-ID: you should get the chipset docs from developer.intel.com, then you should try to figure out how the freebios v2 tree works. ron From ebiederman at lnxi.com Thu Apr 1 20:31:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Thu Apr 1 20:31:01 2004 Subject: unreliably booting off a BCM5701. In-Reply-To: <20040324161117.GA5137@suse.de> References: <20040322170110.GA6915@suse.de> <20040322174456.GA9378@suse.de> <20040322204314.GA11093@suse.de> <20040324161117.GA5137@suse.de> Message-ID: Stefan Reinauer writes: > * Eric W. Biederman [040324 00:34]: > > Ok that is peculiar. 2.6.5rc1 has some patches to head.S which possibly > > accounts for it as soon as I have a moment I will check and see if > > that is what breaks it. From the looks the changes to head.S should > > not break anything.... > > Ok. I'll try to investigate this later, but apparently these changes > seem to influence the situation. 2.6.5rc3 has been tested and works here... > > > No memtest yet, but filo and etherboot, and linux kernel 2.4 - When they > > > get loaded, they seem to work seamlessly... > > > > So the etherboot and filo issues were resolved? > > They start fine. The issues I had are still there, though. I'll build a > memtest86 and do some testing... > > > > 5.3.recent? > > > > 5.3.x is the development version, and there is some major development > > going on there to implement pxe support so I don't know what is > > going on. > > Ok, I'll try going back. Can you recommend a certain version? Any 5.2 should be fine. Eric From John.Usher at perth.maptek.com.au Thu Apr 1 21:24:00 2004 From: John.Usher at perth.maptek.com.au (John Usher (Maptek)) Date: Thu Apr 1 21:24:00 2004 Subject: Linux Startup Times Message-ID: <20E0F651F8B82F45ABCBACC58A2D995B35B277@mexper1> Hi all, Its a bit off topic, but has anyone here done any work on reducing the Linux startup times? Linux on our systems is taking more than 10 seconds to start, and I guess its due to it searching for devices and the like. Any pointers to any resources or information to assist with reducing these times would be great. ...John... -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Thu Apr 1 22:43:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 1 22:43:00 2004 Subject: Linux Startup Times [PMX:#] In-Reply-To: <20E0F651F8B82F45ABCBACC58A2D995B35B277@mexper1> Message-ID: On Fri, 2 Apr 2004, John Usher (Maptek) wrote: > Linux startup times? Linux on our systems is taking more than 10 seconds > to start, and I guess its due to it searching for devices and the like. with/without the rc scripts? ron From John.Usher at perth.maptek.com.au Thu Apr 1 22:47:59 2004 From: John.Usher at perth.maptek.com.au (John Usher (Maptek)) Date: Thu Apr 1 22:47:59 2004 Subject: Linux Startup Times [PMX:#] Message-ID: <20E0F651F8B82F45ABCBACC58A2D995B35B279@mexper1> without rc scripts - I'm talking before getting to the starting init stage... -----Original Message----- From: ron minnich [mailto:rminnich at lanl.gov] Sent: Friday, 2 April 2004 12:09 PM To: John Usher (Maptek) Cc: linuxbios at clustermatic.org Subject: Re: Linux Startup Times [PMX:#] On Fri, 2 Apr 2004, John Usher (Maptek) wrote: > Linux startup times? Linux on our systems is taking more than 10 seconds > to start, and I guess its due to it searching for devices and the like. with/without the rc scripts? ron From yfede at tiscali.it Fri Apr 2 02:59:00 2004 From: yfede at tiscali.it (yfede) Date: Fri Apr 2 02:59:00 2004 Subject: Linux Startup Times [PMX:#] References: Message-ID: <001201c4188b$f76d9050$2f00a8c0@home> I guess it was without rc scripts and init, just time needed by bios+kernel to boot... I'm interested in the same subject, but have no idea of what to do for reducing both. I noticed that the majority of time is taken by IDE hardware to be probed. I know that I can force BIOS settings not to probe for it every time, just setting the correct parameters in CMOS for disks instead of making BIOS guess what the values are every time. Is it possible to do the same with linux kernel as well? Another solution for reducing boot times would be skipping completely BIOS initializations, since linux kernel doesn't rely on them and performs them again when it starts. This could be done by replacing BIOS firmware with a simpler one that only loads kernel in ram and starts it... kinda of LILO on ROM, if you got what I mean. Does something like that exist? Thank you in advance for attention, Fede. ----- Original Message ----- From: "ron minnich" To: "John Usher (Maptek)" Cc: Sent: Friday, April 02, 2004 6:08 AM Subject: Re: Linux Startup Times [PMX:#] > On Fri, 2 Apr 2004, John Usher (Maptek) wrote: > > > Linux startup times? Linux on our systems is taking more than 10 seconds > > to start, and I guess its due to it searching for devices and the like. > > with/without the rc scripts? > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Fri Apr 2 11:19:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 2 11:19:01 2004 Subject: Linux Startup Times [PMX:#] In-Reply-To: <001201c4188b$f76d9050$2f00a8c0@home> Message-ID: On Fri, 2 Apr 2004, yfede wrote: > I noticed that the majority of time is taken by IDE hardware to be probed. yes, and this time is required by the IDE standard. > This could be done by replacing BIOS firmware with a simpler one that > only loads kernel in ram and starts it... kinda of LILO on ROM, if you > got what I mean. Does something like that exist? uh, what list is this again? Oh yea, the one where we did this already, starting 4 years ago. ron From dwh at lanl.gov Fri Apr 2 11:49:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Fri Apr 2 11:49:01 2004 Subject: Linux Startup Times [PMX:#] In-Reply-To: <001201c4188b$f76d9050$2f00a8c0@home> Message-ID: Sort of like LinuxBIOS ( www.linuxbios.org )? :) On Fri, 2 Apr 2004, yfede wrote: > I guess it was without rc scripts and init, just time needed by bios+kernel > to boot... > I'm interested in the same subject, but have no idea of what to do for > reducing both. > I noticed that the majority of time is taken by IDE hardware to be probed. > I know that I can force BIOS settings not to probe for it every time, just > setting the correct parameters in CMOS for disks instead of making BIOS > guess what the values are every time. > Is it possible to do the same with linux kernel as well? > Another solution for reducing boot times would be skipping completely BIOS > initializations, since linux kernel doesn't rely on them and performs them > again when it starts. This could be done by replacing BIOS firmware with a > simpler one that only loads kernel in ram and starts it... kinda of LILO on > ROM, if you got what I mean. Does something like that exist? > Thank you in advance for attention, > Fede. > > ----- Original Message ----- > From: "ron minnich" > To: "John Usher (Maptek)" > Cc: > Sent: Friday, April 02, 2004 6:08 AM > Subject: Re: Linux Startup Times [PMX:#] > > > > On Fri, 2 Apr 2004, John Usher (Maptek) wrote: > > > > > Linux startup times? Linux on our systems is taking more than 10 seconds > > > to start, and I guess its due to it searching for devices and the like. > > > > with/without the rc scripts? > > > > ron > > > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From svante.signell at telia.com Fri Apr 2 12:10:01 2004 From: svante.signell at telia.com (Svante Signell) Date: Fri Apr 2 12:10:01 2004 Subject: Can I execute a linuxbios image from linux? In-Reply-To: <20040401004640.GA1768@ohio.localdomain> References: <1080761416.18828.668.camel@em2.my.own.domain> <20040401004640.GA1768@ohio.localdomain> Message-ID: <1080927392.18828.699.camel@em2.my.own.domain> Kevin, Thank you for the information. I'll check if this equipment is usable for my hardware. The crucial thing is whether the BIOS chip is socketed or not. We'll see, at least I know the size is 2Mbit, since the latest BIOS binary (A6120IMS.200) supported by MSI is 261144kbyte. Does anybody have experience with removing a soldered chip on a motherboard without destroying anything? I sent in an update enquiry about my BIOS version (AMI) to www.esupport.com and they offered me to purchase a new one, supporting modern CPUs and up to Windows XP, for around the same price as the "BIOS saviour" board costs. Since I'm only running Linux on this computer, I'm not interested in booting other OSes. I'm mostly interested to be able to upgrade the box with faster (dual) processors. However, according to the answers obtained so far there seems to be no interest at all to make LinuxBIOS(V2) work with older motherboards, such as the widely spread 440BX-based ones. As mentioned in earlier postings, I'm willing to be a test pilot for this port, but I cannot do it without help from the LinuxBIOS developers. Thanks, Svante On Thu, 2004-04-01 at 02:46, Kevin O'Connor wrote: > On Wed, Mar 31, 2004 at 09:30:16PM +0200, Svante Signell wrote: > > Is there a way to try out a new BIOS without risking to end up with an > > unbootable main-board, ethernet, serial port, some special card > > connected to the south-bridge (PIIX4) e.g. a special PCI/ISA card, etc? > > Other solutions including soldering, EEPROM programming devices, etc? > > A number of people are using the "BIOS Savior" product with success. See: > http://www.ioss.com.tw/eg/rd1/index.html > > Depending on which part you need, you can mail order it from mwave.com, > pcmods.com, or probably a bunch of other places. > > -Kevin From rminnich at lanl.gov Fri Apr 2 12:43:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 2 12:43:01 2004 Subject: Can I execute a linuxbios image from linux? In-Reply-To: <1080927392.18828.699.camel@em2.my.own.domain> Message-ID: On Fri, 2 Apr 2004, Svante Signell wrote: > Thank you for the information. I'll check if this equipment is usable > for my hardware. The crucial thing is whether the BIOS chip is socketed > or not. We'll see, at least I know the size is 2Mbit, since the latest > BIOS binary (A6120IMS.200) supported by MSI is 261144kbyte. Does anybody > have experience with removing a soldered chip on a motherboard without > destroying anything? 2 Mbit == 256K, too small for a kernel. I think Bari Ari will tell us if you can get that part off :-) > However, according to the answers obtained so far there seems to be no > interest at all to make LinuxBIOS(V2) work with older motherboards, such > as the widely spread 440BX-based ones. As mentioned in earlier postings, > I'm willing to be a test pilot for this port, but I cannot do it without > help from the LinuxBIOS developers. LinuxBIOS generally works fine with 440BX boards. ron From stuge-linuxbios at cdy.org Fri Apr 2 13:05:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Fri Apr 2 13:05:01 2004 Subject: Can I execute a linuxbios image from linux? In-Reply-To: <1080927392.18828.699.camel@em2.my.own.domain> References: <1080761416.18828.668.camel@em2.my.own.domain> <20040401004640.GA1768@ohio.localdomain> <1080927392.18828.699.camel@em2.my.own.domain> Message-ID: <20040402183055.GE15826@foo.birdnet.se> On Fri, Apr 02, 2004 at 07:36:32PM +0200, Svante Signell wrote: > for my hardware. The crucial thing is whether the BIOS chip is socketed > or not. We'll see, at least I know the size is 2Mbit, since the latest > BIOS binary (A6120IMS.200) supported by MSI is 261144kbyte. Does anybody > have experience with removing a soldered chip on a motherboard without > destroying anything? Sure, both PLCC and DIL packages can be desoldered without any problems as long as it's possible/easy to access the chip physically on the board. (A PLCC ROM tucked in close to e.g. a PCI slot is more problematic..) After desoldering the ROM, it's quite possible to fit a socket there instead. If you want professional help with this I'll gladly assist. I'm in Malm?. //Peter From svante.signell at telia.com Sat Apr 3 03:56:01 2004 From: svante.signell at telia.com (Svante Signell) Date: Sat Apr 3 03:56:01 2004 Subject: Can I execute a linuxbios image from linux? In-Reply-To: References: Message-ID: <1080984123.2743.728.camel@em2.my.own.domain> On Fri, 2004-04-02 at 20:08, ron minnich wrote: > On Fri, 2 Apr 2004, Svante Signell wrote: > > > Thank you for the information. I'll check if this equipment is usable > > for my hardware. The crucial thing is whether the BIOS chip is socketed > > or not. We'll see, at least I know the size is 2Mbit, since the latest > > BIOS binary (A6120IMS.200) supported by MSI is 261144kbyte. Does anybody Sorry my mistake: 261.144 kbyte = 256 Kibyte = 2 Mibit = 2.097152 Mbit. > 2 Mbit == 256K, too small for a kernel. I thought the LinuxBIOS was parts from of a kernel. What size is needed? It seems that the flash sizes are 1,2 and 4 Mibit, at least for older boards. Have I missed something here? > I think Bari Ari will tell us if you can get that part off :-) Is he on this list? > > However, according to the answers obtained so far there seems to be no > > interest at all to make LinuxBIOS(V2) work with older motherboards, such > > as the widely spread 440BX-based ones. As mentioned in earlier postings, > > I'm willing to be a test pilot for this port, but I cannot do it without > > help from the LinuxBIOS developers. > > LinuxBIOS generally works fine with 440BX boards. Do you mean the target for 440BX in freebios version1, freebios/util/config/l440bx-test12.config? Do the latest kernels,e.g. 2.4.25 still have to be patched with the 2.4.13 patch, freebios/src/kernel_patches/linux-2.4.13-l440gx.diff? Is the onboard SCSI and dual CPU supported? From Antony at Soft-Solutions.co.uk Sat Apr 3 04:21:01 2004 From: Antony at Soft-Solutions.co.uk (Antony Stone) Date: Sat Apr 3 04:21:01 2004 Subject: Can I execute a linuxbios image from linux? In-Reply-To: <1080984123.2743.728.camel@em2.my.own.domain> References: <1080984123.2743.728.camel@em2.my.own.domain> Message-ID: <200404031047.09412.Antony@Soft-Solutions.co.uk> On Saturday 03 April 2004 10:22 am, Svante Signell wrote: > I thought the LinuxBIOS was parts from of a kernel. What size is needed? > It seems that the flash sizes are 1,2 and 4 Mibit, at least for older > boards. Have I missed something here? LinuxBIOS is not the Linux kernel. LinuxBIOS is boot code which gets hardware working sufficiently to start a kernel. Where that kernel is found and booted from is your choice. Some people put it on an IDE device (eg: hard disk), some people use Compact Flash (which is basically an IDE interface as well), some people use Disk On Chip (which can go in the Bios socket on some motherboards), some people download it across a network... You are correct that you cannot fit a Linux kernel into a BIOS chip. However LinuxBIOS is much smaller than that, and can load a kernel from several locations depending on your hardware and your preference. Regards, Antony. -- Your work is both good and original. Unfortunately the parts that are good aren't original, and the parts that are original aren't good. - Samuel Johnson Please reply to the list; please don't CC me. From ebiederman at lnxi.com Sat Apr 3 15:20:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sat Apr 3 15:20:01 2004 Subject: Linux Startup Times [PMX:#] In-Reply-To: <20E0F651F8B82F45ABCBACC58A2D995B35B279@mexper1> References: <20E0F651F8B82F45ABCBACC58A2D995B35B279@mexper1> Message-ID: "John Usher (Maptek)" writes: > without rc scripts - I'm talking before getting to the starting init > stage... There is some ongoing research on this. But the cheap trick is to build everything that has a long probe time as a module. Eric From ebiederman at lnxi.com Sat Apr 3 15:35:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sat Apr 3 15:35:01 2004 Subject: FILO 0.4 In-Reply-To: <20031015114727.GA890@tsn.or.jp> References: <20031015114727.GA890@tsn.or.jp> Message-ID: SONE Takeshi writes: > I just released FILO 0.4. > http://te.to/~ts1/filo/ > > I'll work on config file support next time. Is this work still ongoing? At first stab at a config file could hard code it's location like you currently do the kernel image. Another question listing files. Currently you have that support completely removed from the Grub code. Any thoughts on adding that. Eric From yhlu at tyan.com Sat Apr 3 18:30:00 2004 From: yhlu at tyan.com (Yinghai Lu) Date: Sat Apr 3 18:30:00 2004 Subject: =?gb2312?B?tPC4tDogRklMTyAwLjQ=?= In-Reply-To: Message-ID: <200404032329.i33NTM001096@nwn.definitive.org> It seems someone (Greg ???) merge FILO into the LinuxBIOS hardwaremain.c and it is can be loaded instead of elfboot. In normal bios, when booting Etherboot with ASK_BOOT, and using Q can exit from Etherboot and back into BIOS, then can boot into HD and use HD bootloader. In LinuxBIOS, if LinuxBIOS is using elfboot to boot Etherboot elf, when Q from Etherboot, should continue to do the code after elfboot. So may put the filo after elfboot. But I think the best way is merged filo into Etherboot instead of Linuxbios directly. Then We can use tg3-fs_stream.zelf or tg3_filo.zelf as payload of LinuxBIOS. It is more better if filo support boot loader (lilo) in HD. Regards Yinghai Lu -----????----- ???: linuxbios-admin at clustermatic.org [mailto:linuxbios-admin at clustermatic.org] ?? Eric W. Biederman ????: 2004?4?3? 13:02 ???: SONE Takeshi ??: linuxbios at clustermatic.org ??: Re: FILO 0.4 SONE Takeshi writes: > I just released FILO 0.4. > http://te.to/~ts1/filo/ > > I'll work on config file support next time. Is this work still ongoing? At first stab at a config file could hard code it's location like you currently do the kernel image. Another question listing files. Currently you have that support completely removed from the Grub code. Any thoughts on adding that. Eric _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From gwatson at lanl.gov Sat Apr 3 20:03:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Sat Apr 3 20:03:01 2004 Subject: =?UTF-8?Q?Re:_=E7=AD=94=E5=A4=8D:_FILO_0.4_[PMX:#]?= In-Reply-To: <200404032329.i33NTM001096@nwn.definitive.org> References: <200404032329.i33NTM001096@nwn.definitive.org> Message-ID: <6B4E2E5A-85D7-11D8-92F6-000393A47A5C@lanl.gov> Yeah sorry, I kind of did that by stealth. Ron and I get lots of requests from people wanting to use LB but who don't know how to deal with the payload issue. We decided that it would be really nice to have a simple bootloader that understands some basic filesystems built into LB. That way people can get going without having to deal with etherboot or FILO directly. A nice side effect is that it simplifies the FILO code significantly - in fact the only code that is really required is the filesystem support. Also, another major plus is that the code supports PPC as well as x86. Up to now I've had no bootloaders (etherboot or FILO) that work on PPC. Greg On 03/04/2004, at 4:56 PM, Yinghai Lu wrote: > It seems someone (Greg ???) merge FILO into the LinuxBIOS > hardwaremain.c and > it is can be loaded instead of elfboot. > > In normal bios, when booting Etherboot with ASK_BOOT, and using Q can > exit > from Etherboot and back into BIOS, then can boot into HD and use HD > bootloader. > > In LinuxBIOS, if LinuxBIOS is using elfboot to boot Etherboot elf, > when Q > from Etherboot, should continue to do the code after elfboot. So may > put the > filo after elfboot. > > But I think the best way is merged filo into Etherboot instead of > Linuxbios > directly. Then We can use tg3-fs_stream.zelf or tg3_filo.zelf as > payload of > LinuxBIOS. > > It is more better if filo support boot loader (lilo) in HD. > > Regards > > Yinghai Lu > > -----????----- > ???: linuxbios-admin at clustermatic.org > [mailto:linuxbios-admin at clustermatic.org] ?? Eric W. Biederman > ????: 2004?4?3? 13:02 > ???: SONE Takeshi > ??: linuxbios at clustermatic.org > ??: Re: FILO 0.4 > > SONE Takeshi writes: > >> I just released FILO 0.4. >> http://te.to/~ts1/filo/ >> >> I'll work on config file support next time. > > Is this work still ongoing? At first stab at a config > file could hard code it's location like you currently do > the kernel image. > > Another question listing files. Currently you have that > support completely removed from the Grub code. Any thoughts > on adding that. > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Sat Apr 3 20:28:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Sat Apr 3 20:28:01 2004 Subject: FILO 0.4 In-Reply-To: Message-ID: I was wondering about listing files. Once you add that, you add a command interpreter, and that way lies madness. If, however, file listed all the files it found while attempting to load an image, that might be enough. ron From yhlu at tyan.com Sat Apr 3 22:02:01 2004 From: yhlu at tyan.com (Yinghai Lu) Date: Sat Apr 3 22:02:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: <6B4E2E5A-85D7-11D8-92F6-000393A47A5C@lanl.gov> Message-ID: <200404040301.i3431f001768@nwn.definitive.org> The current ide_disk part in Etherboot only scan 10 (???) sectors from /dev/hda header. So the user muse cat boot.elf /dev/hda, I have modified Etherboot source code to scan more sectors so it can find elf in /dev/hda1. (the /dev/hda1 should be physical partition 1). The Linux Distribution is installed from /dev/hda2. then I can use kernel and initrd in /boot to produce elf and cat that in /dev/hda1. After that, I can boot from NIC or HD via cmos conf. The Etherboot group seems to stop enhancing the ide_disk part. I think maybe because > In normal bios, when booting Etherboot with ASK_BOOT, and using Q can exit > from Etherboot and back into BIOS, then can boot into HD and use HD bootloader. And most users of Etherboot are from Normal BIOS ???? ( they don't like pxe ??) How much works need to done to put filo in Etherboot for LinuxBIOS users? PS: Nobody in PPC is using Etherboot??? Regards YH -----????----- ???: Greg Watson [mailto:gwatson at lanl.gov] ????: 2004?4?3? 17:29 ???: Yinghai Lu ??: 'SONE Takeshi'; 'Eric W. Biederman'; linuxbios at clustermatic.org ??: Re: ??: FILO 0.4 [PMX:#] Yeah sorry, I kind of did that by stealth. Ron and I get lots of requests from people wanting to use LB but who don't know how to deal with the payload issue. We decided that it would be really nice to have a simple bootloader that understands some basic filesystems built into LB. That way people can get going without having to deal with etherboot or FILO directly. A nice side effect is that it simplifies the FILO code significantly - in fact the only code that is really required is the filesystem support. Also, another major plus is that the code supports PPC as well as x86. Up to now I've had no bootloaders (etherboot or FILO) that work on PPC. Greg On 03/04/2004, at 4:56 PM, Yinghai Lu wrote: > It seems someone (Greg ???) merge FILO into the LinuxBIOS > hardwaremain.c and > it is can be loaded instead of elfboot. > > In normal bios, when booting Etherboot with ASK_BOOT, and using Q can > exit > from Etherboot and back into BIOS, then can boot into HD and use HD > bootloader. > > In LinuxBIOS, if LinuxBIOS is using elfboot to boot Etherboot elf, > when Q > from Etherboot, should continue to do the code after elfboot. So may > put the > filo after elfboot. > > But I think the best way is merged filo into Etherboot instead of > Linuxbios > directly. Then We can use tg3-fs_stream.zelf or tg3_filo.zelf as > payload of > LinuxBIOS. > > It is more better if filo support boot loader (lilo) in HD. > > Regards > > Yinghai Lu > > -----????----- > ???: linuxbios-admin at clustermatic.org > [mailto:linuxbios-admin at clustermatic.org] ?? Eric W. Biederman > ????: 2004?4?3? 13:02 > ???: SONE Takeshi > ??: linuxbios at clustermatic.org > ??: Re: FILO 0.4 > > SONE Takeshi writes: > >> I just released FILO 0.4. >> http://te.to/~ts1/filo/ >> >> I'll work on config file support next time. > > Is this work still ongoing? At first stab at a config > file could hard code it's location like you currently do > the kernel image. > > Another question listing files. Currently you have that > support completely removed from the Grub code. Any thoughts > on adding that. > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From ebiederman at lnxi.com Sat Apr 3 23:07:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sat Apr 3 23:07:00 2004 Subject: ç­å¤: FILO 0.4 [PMX:#] In-Reply-To: <6B4E2E5A-85D7-11D8-92F6-000393A47A5C@lanl.gov> References: <200404032329.i33NTM001096@nwn.definitive.org> <6B4E2E5A-85D7-11D8-92F6-000393A47A5C@lanl.gov> Message-ID: Greg Watson writes: > Yeah sorry, I kind of did that by stealth. Ron and I get lots of requests from > people wanting to use LB but who don't know how to deal with the payload > issue. We decided that it would be really nice to have a simple bootloader that > understands some basic filesystems built into LB. That way people can get going > without having to deal with etherboot or FILO directly. A nice side effect is > that it simplifies the FILO code significantly - in fact the only code that is > really required is the filesystem support. Also, another major plus is that the > code supports PPC as well as x86. Up to now I've had no bootloaders (etherboot > or FILO) that work on PPC. Then we refactor and make building the bootloader part of the tree. These things are policy engines. We need to separate mechanism and policy. As far as I can tell this level of support crosses the line. etherboot is portable and would not be hard to get running on ppc. Eric From ebiederman at lnxi.com Sat Apr 3 23:11:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sat Apr 3 23:11:01 2004 Subject: FILO 0.4 In-Reply-To: References: Message-ID: ron minnich writes: > I was wondering about listing files. Once you add that, you add a command > interpreter, and that way lies madness. > > If, however, file listed all the files it found while attempting to load > an image, that might be enough. What grub does is essentially tab completion in it's command line editor. Which is a bit peculiar but sane. Eric From yhlu at tyan.com Sun Apr 4 15:05:00 2004 From: yhlu at tyan.com (Yinghai Lu) Date: Sun Apr 4 15:05:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: <200404041904.i34J4c009783@nwn.definitive.org> I have checked the Etherboot, and it would be some easier to integrate filo into Etherboot. May add one BOOT_FILO in cmos.layout. In the core/main.c, will judge if boot type is BOOT_FILO, and will call filo, and set state still =4, so it can boot next device. The problem is it is some kind of hard code. How can I enable tg3-filo.zelf? Regards YH. -----????----- ???: Eric W. Biederman [mailto:eric at lnxi.com] ?? Eric W. Biederman ????: 2004?4?3? 20:33 ???: Greg Watson ??: Yinghai Lu; 'SONE Takeshi'; linuxbios at clustermatic.org ??: Re: g-e$: FILO 0.4 [PMX:#] Greg Watson writes: > Yeah sorry, I kind of did that by stealth. Ron and I get lots of requests from > people wanting to use LB but who don't know how to deal with the payload > issue. We decided that it would be really nice to have a simple bootloader that > understands some basic filesystems built into LB. That way people can get going > without having to deal with etherboot or FILO directly. A nice side effect is > that it simplifies the FILO code significantly - in fact the only code that is > really required is the filesystem support. Also, another major plus is that the > code supports PPC as well as x86. Up to now I've had no bootloaders (etherboot > or FILO) that work on PPC. Then we refactor and make building the bootloader part of the tree. These things are policy engines. We need to separate mechanism and policy. As far as I can tell this level of support crosses the line. etherboot is portable and would not be hard to get running on ppc. Eric From yhlu at tyan.com Sun Apr 4 16:31:01 2004 From: yhlu at tyan.com (Yinghai Lu) Date: Sun Apr 4 16:31:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: <200404042030.i34KU1010094@nwn.definitive.org> Eric, Greg just move the fs support from filo to linuxbios, and create fs_stream. It still calls the elfboot to load the elfimage in HD. And it doesn't support linux_load. So it is some kind of boot loader you said. It is really enhancement to ide_stream.c Regards YH -----????----- ???: Eric W. Biederman [mailto:eric at lnxi.com] ?? Eric W. Biederman ????: 2004?4?3? 20:33 ???: Greg Watson ??: Yinghai Lu; 'SONE Takeshi'; linuxbios at clustermatic.org ??: Re: g-e$: FILO 0.4 [PMX:#] Greg Watson writes: > Yeah sorry, I kind of did that by stealth. Ron and I get lots of requests from > people wanting to use LB but who don't know how to deal with the payload > issue. We decided that it would be really nice to have a simple bootloader that > understands some basic filesystems built into LB. That way people can get going > without having to deal with etherboot or FILO directly. A nice side effect is > that it simplifies the FILO code significantly - in fact the only code that is > really required is the filesystem support. Also, another major plus is that the > code supports PPC as well as x86. Up to now I've had no bootloaders (etherboot > or FILO) that work on PPC. Then we refactor and make building the bootloader part of the tree. These things are policy engines. We need to separate mechanism and policy. As far as I can tell this level of support crosses the line. etherboot is portable and would not be hard to get running on ppc. Eric From gwatson at lanl.gov Sun Apr 4 19:41:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Sun Apr 4 19:41:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: <200404042057.i34Kv1Wk032339@mailproxy3.lanl.gov> References: <200404042057.i34Kv1Wk032339@mailproxy3.lanl.gov> Message-ID: <2F75B58F-8695-11D8-92F6-000393A47A5C@lanl.gov> Correct. I haven't included linux_load, though it would probably be easy to do. FILO simply calls elfboot to load the image from a filesystem. Merging FILO with etherboot is a fine idea, but it doesn't solve the loader problem for PPC. At this point I don't see any requirement to port etherboot to PPC, but if anyone would like to take it on then feel free. :-) I think the case for including a simple FILO-like loader in linuxbios is a strong one. Apart from instant PPC loader support and reducing the difficulty of deploying linuxbios, it's possible to make use of much of the existing linuxbios code which significantly reduces duplication and complexity in the payload. Greg On 04/04/2004, at 2:57 PM, Yinghai Lu wrote: > Eric, > > Greg just move the fs support from filo to linuxbios, and create > fs_stream. > > It still calls the elfboot to load the elfimage in HD. And it doesn't > support linux_load. > > So it is some kind of boot loader you said. > > It is really enhancement to ide_stream.c > > Regards > > YH > > -----????----- > ???: Eric W. Biederman [mailto:eric at lnxi.com] ?? Eric W. Biederman > ????: 2004?4?3? 20:33 > ???: Greg Watson > ??: Yinghai Lu; 'SONE Takeshi'; linuxbios at clustermatic.org > ??: Re: g-e$: FILO 0.4 [PMX:#] > > Greg Watson writes: > >> Yeah sorry, I kind of did that by stealth. Ron and I get lots of >> requests > from >> people wanting to use LB but who don't know how to deal with the >> payload >> issue. We decided that it would be really nice to have a simple >> bootloader > that >> understands some basic filesystems built into LB. That way people can >> get > going >> without having to deal with etherboot or FILO directly. A nice side >> effect > is >> that it simplifies the FILO code significantly - in fact the only code > that is >> really required is the filesystem support. Also, another major plus is > that the >> code supports PPC as well as x86. Up to now I've had no bootloaders > (etherboot >> or FILO) that work on PPC. > > Then we refactor and make building the bootloader part of the tree. > These things are policy engines. We need to separate mechanism and > policy. > > As far as I can tell this level of support crosses the line. > > etherboot is portable and would not be hard to get running on ppc. > > Eric > From rminnich at lanl.gov Sun Apr 4 22:16:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 4 22:16:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: <200404041904.i34J4c009783@nwn.definitive.org> Message-ID: On Sun, 4 Apr 2004, Yinghai Lu wrote: > I have checked the Etherboot, and it would be some easier to integrate filo > into Etherboot. Not everyone here at LANL is that satisfied with etherboot, and in fact we are moving over to FILO. There are a lot of reasons. We've just had lots better luck with FILO when all things are considered. ron From ebiederman at lnxi.com Sun Apr 4 22:36:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sun Apr 4 22:36:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: <2F75B58F-8695-11D8-92F6-000393A47A5C@lanl.gov> References: <200404042057.i34Kv1Wk032339@mailproxy3.lanl.gov> <2F75B58F-8695-11D8-92F6-000393A47A5C@lanl.gov> Message-ID: Greg Watson writes: > Correct. I haven't included linux_load, though it would probably be > easy to do. FILO simply calls elfboot to load the image from a > filesystem. Feature bloat. If we want to take a snapshot of the source tree of FILO or any other bootloader into the LinuxBIOS tree under util. Build that part of the build and build a complete romimage that works. I am fine with that. It is even reasonable to make it so you can drop in external trees like etherboot and have everything build together nicely. Actual linking things together instead of including them together is unacceptable. > Merging FILO with etherboot is a fine idea, but it doesn't solve the > loader problem for PPC. At this point I don't see any requirement to > port etherboot to PPC, but if anyone would like to take it on then > feel free. :-) It is a half way decent stand alone portable bootloader. There are a lot of other ones out there as well. Etherboot is something simple and small that exists as an alternative. Etherboot should be a fairly trivial port which is why I suggest it. > I think the case for including a simple FILO-like loader in linuxbios > is a strong one. Apart from instant PPC loader support and reducing > the difficulty of deploying linuxbios, it's possible to make use of > much of the existing linuxbios code which significantly reduces > duplication and complexity in the payload. I have not seen it yet. The reason FILO simplifies is because it a simple first pass. But this complicates LinuxBIOS, and includes policy. Both of which are bad. Any builtin policy more complicated than slurp in one hard coded executable and run it I refuse to touch, and elfload gives us that. This is a line I refuse to cross and will delete code from CVS if necessary to enforce. Bootloaders can and should be board independent. That makes then easier to test and develop. And it very much simplifies the test of the whole thing. In addition we have had way to many questions of what is the right policy for a bootloader to implement, on this list. I refuse to couple that to the LinuxBIOS core. And I don't want some stupid policy in there like FILO's that would require me to upgrade my firmware just to upgrade my OS. Eric From ebiederman at lnxi.com Sun Apr 4 22:40:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sun Apr 4 22:40:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: References: Message-ID: ron minnich writes: > On Sun, 4 Apr 2004, Yinghai Lu wrote: > > > I have checked the Etherboot, and it would be some easier to integrate filo > > into Etherboot. > > Not everyone here at LANL is that satisfied with etherboot, and in fact we > are moving over to FILO. There are a lot of reasons. We've just had lots > better luck with FILO when all things are considered. It's a good thing we have a choice then isn't it. And this just reinforces my certainty that none of these should be linked into the LinuxBIOS core. Personally the one I want is based on a real live kernel. And if I can get some time that is what you will see. Eric From ebiederman at lnxi.com Sun Apr 4 22:44:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sun Apr 4 22:44:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: References: Message-ID: ron minnich writes: > On Sun, 4 Apr 2004, Yinghai Lu wrote: > > > I have checked the Etherboot, and it would be some easier to integrate filo > > into Etherboot. > > Not everyone here at LANL is that satisfied with etherboot, and in fact we > are moving over to FILO. There are a lot of reasons. We've just had lots > better luck with FILO when all things are considered. Ron, is LANL going to maintain FILO then? Unless I hear from SONE soon it is starting to look like like FILO is unmaintained. Has any one implemented config files? Has any one implemented listing of files? What do you do when you don't have a disk? Eric From rminnich at lanl.gov Sun Apr 4 23:29:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 4 23:29:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: On 4 Apr 2004, Eric W. Biederman wrote: > Personally the one I want is based on a real live kernel. And if I can > get some time that is what you will see. Sure. That's where I started this project from almost 5 years ago. We only have this plethora of bootloaders (etherboot, filo, 9load, etc.) because our initial goals of a real live kernel proved techincally impossible -- flash was too small. 2.6 + bigger flashes might put us back where we were 4 years ago with the L440GX+ boards, with 1 MB flash and a 2.4.7 kernel that easily fit in that space. We can hope so. IIRC you and I had some discussion on this several years ago, on this list, and you were firmly in the Etherboot camp, as you thought the small fast Etherboot kernel had advantages over a full live Linux kernel. You made some excellent arguments in favor of this idea. I argued that the Etherboot approach was fundamentally flawed, and that in the end I wanted a live kernel in there for booting. We agreed to disagree. So I'm glad to have you back :-) Just kidding. You and I both know the excellent Etherboot work you did was a real accomplishment and definitely saved our collective necks. But: you have to at some point consider what people are asking for, and we do think about that as we get a lot of requests here not reflected to the list. Some ongoing requests: VGA that works in linuxbios, and a boot prompt that can allow a user to type a pathname to a CD image and do an install. One build, not two or three. And people want it in one package. The requirement with the current setup to build multiple binaries such as Etherboot at present can't do this. Greg's test integrated FILO can. We also need the emulator in linuxbios because that is the only practical way to get to this demand. And it's got to be very very small. Some of the recent changes in V2 have been tough on the embedded folks, and that is of real concern to us. Please bear in mind that you folks at LNXI are not as affected by the embedded world as we are down here, and I have had a number of comments about V2 in that regard. Hence these trial changes. Plus, a simple fact: if you don't like them, don't enable them. Nobody's locking them in. We are making them available to those who can use them. The goal is flexibility. We've also had lots of people with issues with the ELF loader approach. Requiring an ELF target is requiring a policy as near as I can tell. Many people don't want to deal with mkelfImage, esp. as it has proven to be non-portable in some cases (maybe this can be fixed, but if you mkelfImage on a 64-bit K8, etherboot coughs and dies in the elf loader -- there are issues). Also, re this: "In addition we have had way to many questions of what is the right policy for a bootloader to implement, on this list. I refuse to couple that to the LinuxBIOS core. And I don't want some stupid policy in there like FILO's that would require me to upgrade my firmware just to upgrade my OS. " To most people, the distinction between "payload in flash" and "linuxbios in flash" is immaterial. In other words, these folks don't care about the seperation between LinuxBIOS and payload! they are much happier with an integrated one-step system that boots an OS. What they want is to be able to install from CD. Etherboot won't let them do this, and neither will an ELF loader. Integrated Filo gives people something they can use today, that will be easy to build. Finally, let's remember that the ultimate goal of a project such as LinuxBIOS is utility, not beauty and beauty alone. Sometimes what some people consider beautiful is sacrificed in order to support needs of customers. Let's not go so far into concern for beauty that we forget that lesson. I'm maxed out on 'beauty uber alles' on the Plan 9 list. Anyway, before this conversation gets too hot, please everyone take a deep breath, remember your email etiquette, and don't forget we are all friends here. It's important to resolve these issues in an atmosphere of cordiality. ron From gwatson at lanl.gov Sun Apr 4 23:33:00 2004 From: gwatson at lanl.gov (Greg Watson) Date: Sun Apr 4 23:33:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: References: <200404042057.i34Kv1Wk032339@mailproxy3.lanl.gov> <2F75B58F-8695-11D8-92F6-000393A47A5C@lanl.gov> Message-ID: On 04/04/2004, at 9:02 PM, Eric W. Biederman wrote: > Greg Watson writes: > >> Correct. I haven't included linux_load, though it would probably be >> easy to do. FILO simply calls elfboot to load the image from a >> filesystem. > > Feature bloat. No, it's functionality that is needed for PPC but is not available anywhere else. > > If we want to take a snapshot of the source tree of FILO or any other > bootloader into the LinuxBIOS tree under util. Build that part of the > build and build a complete romimage that works. I am fine > with that. It is even reasonable to make it so you can drop in > external trees like etherboot and have everything build together > nicely. > > Actual linking things together instead of including them together > is unacceptable. > >> Merging FILO with etherboot is a fine idea, but it doesn't solve the >> loader problem for PPC. At this point I don't see any requirement to >> port etherboot to PPC, but if anyone would like to take it on then >> feel free. :-) > > It is a half way decent stand alone portable bootloader. There > are a lot of other ones out there as well. Etherboot is something > simple and small that exists as an alternative. > > Etherboot should be a fairly trivial port which is why I suggest it. > >> I think the case for including a simple FILO-like loader in linuxbios >> is a strong one. Apart from instant PPC loader support and reducing >> the difficulty of deploying linuxbios, it's possible to make use of >> much of the existing linuxbios code which significantly reduces >> duplication and complexity in the payload. > > I have not seen it yet. The reason FILO simplifies is because > it a simple first pass. But this complicates LinuxBIOS, and includes > policy. Both of which are bad. I don't get this policy stuff. This code is doing no more that adding another stream device, of which there are already two. Someone building LinuxBIOS is perfectly liberty to choose to load an ELF image from ROM, directly from an IDE device, or from a filesystem mounted on an IDE device. > > Any builtin policy more complicated than slurp in one hard coded > executable and run it I refuse to touch, and elfload gives us that. > This is a line I refuse to cross and will delete code from > CVS if necessary to enforce. > > Bootloaders can and should be board independent. That makes > then easier to test and develop. And it very much simplifies > the test of the whole thing. I agree. It would be nice if they were architecture independent as well. > > In addition we have had way to many questions of what is the right > policy for a bootloader to implement, on this list. I refuse > to couple that to the LinuxBIOS core. And I don't want some stupid > policy in there like FILO's that would require me to upgrade > my firmware just to upgrade my OS. By policy, do you mean a file name in a valid filesystem? As opposed to a valid ELF header? The distinction seems pretty fine to me. Being able to mount a compact flash device on another machine and drop multiple kernel versions onto it certainly helped me to get the EPIA going though. Greg From rminnich at lanl.gov Sun Apr 4 23:42:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 4 23:42:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: On 4 Apr 2004, Eric W. Biederman wrote: > Ron, is LANL going to maintain FILO then? Right now, LANL doesn't by itself maintain everything any way. Look at the excellent work you and Yinghai and others do every day on LinuxBIOS. > Unless I hear from SONE soon it is starting to look like like FILO is > unmaintained. If there is interest in FILO, then I expect we'll have good people (like you, but obviously not you :0) ) to help out. > Has any one implemented config files? not sure what you mean. > Has any one implemented listing of files? not yet. > What do you do when you don't have a disk? For the communities which need FILO, this is not a concern. ron From rminnich at lanl.gov Sun Apr 4 23:56:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 4 23:56:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: RE the bigger issue of compiling things direct into linuxbios. I've been thinking for some time of an experiment, namely turning this whole business inside-out. Think of it this way: there is a runtime startup for every program your write, called in old times crt0 (which is why I used that name for LinuxBIOS). But from your point of view, your program is not crt0, it's main(). So looking from the point of view of the compiler and library writers, who know nothing of your program when they write the compilers and libraries, the world is libc.a and crt0. You don't care about that, and from your point of view, the world is your program. You use the compiler to get your startup code and some library calls. This leads to a natural question: what if we think of linuxbios as something to be linked into a boot loader such as openbios, filo, 9load, or even a special linux kernel? In other words, invert our view of the world: we don't compile a boot loader as part of building linuxbios; we compile linuxbios into a bootloader. Linuxbios provides startup (analogous to crt0) and some library functions the boot loader needs (print* support, pci enumeration, etc) but the really important bit is the boot loader. In this view, linuxbios is a library that you link your bootloader with to build a bios. This really changes things around a bit. It also removes some nasty problems, as the bootloader no longer has to supply (e.g.) its own PCI enumeration code, and can use the linuxbios PCI enumeration code, which can help boot loaders avoid bugs in chips (consider the VT8601 and the PCI bugs it used to have). This view is sort of halfway from old bios ideas (INT xy) and current ideas (the payload doesn't know linuxbios exists). It's a huge change -- maybe a very bad idea, as it means that now LinuxBIOS provides an API, which we never intended it to do. I have no idea if it even makes sense -- just wondering. Back to our irregularly scheduled arguments :-) ron From ts1 at tsn.or.jp Mon Apr 5 05:14:00 2004 From: ts1 at tsn.or.jp (Takeshi Sone) Date: Mon Apr 5 05:14:00 2004 Subject: FILO 0.4 [PMX:#] Message-ID: Eric, Sorry for not replying soon. I've been busy with real job and life, config file support is not yet written, though I'm still willing to do it (+ USB support etc..) This situation would not seem to change in a month or two.. > -----Original Message----- > From: ebiederman at lnxi.com (Eric W. Biederman) > Sent: 04 Apr 2004 21:10:51 -0600 > To: ron minnich > Subject: Re: FILO 0.4 [PMX:#] > > ron minnich writes: > > > On Sun, 4 Apr 2004, Yinghai Lu wrote: > > > > > I have checked the Etherboot, and it would be some easier to integrate filo > > > into Etherboot. > > > > Not everyone here at LANL is that satisfied with etherboot, and in fact we > > are moving over to FILO. There are a lot of reasons. We\'ve just had lots > > better luck with FILO when all things are considered. > > Ron, is LANL going to maintain FILO then? > > Unless I hear from SONE soon it is starting to look like like FILO is > unmaintained. > > Has any one implemented config files? > Has any one implemented listing of files? > > What do you do when you don\'t have a disk? > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios ___________________________________________________________________________ From stepan at openbios.org Mon Apr 5 08:22:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Mon Apr 5 08:22:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: References: <200404042057.i34Kv1Wk032339@mailproxy3.lanl.gov> <2F75B58F-8695-11D8-92F6-000393A47A5C@lanl.gov> Message-ID: <20040405124659.GA18106@openbios.org> * Eric W. Biederman [040405 05:02]: > If we want to take a snapshot of the source tree of FILO or any other > bootloader into the LinuxBIOS tree under util. Build that part of the > build and build a complete romimage that works. I am fine > with that. It is even reasonable to make it so you can drop in > external trees like etherboot and have everything build together > nicely. > > Actual linking things together instead of including them together > is unacceptable. What about the following: Currently LinuxBIOS divides into 2 fundamental parts: 1) hardware initialization 2) getting and starting the payload This second part consists of two parts, again: i) elfloader ii) payload Note, this is only one possible design. Maybe, this design is bloated for some application cases. Eric, you want to make a hard cut between what is LinuxBIOS and what is not. This is generally a good idea, as it keeps the different initialization steps distinct from reach other. What, if we add another cut by dividing hardware initialization frin the payload-loader? Instead of packing stuff like filo to util, we could do: * create a directory loader which can hold all "loaders" * move the elf loader with a Config.lb to a subdirectory in there * create other directories for other "loaders" like filo. If done right, filo can still be compiled as a payload, or built in if the win in size is noticable. A target config file could probably choose which method to use, without overhead. Also, syncing with other trees, like Takeshi's filo tree could be fairly easy, too. I don't think we really have a conflict in direction here at all. LinuxBIOS itself should be as small as possible, and the different parts should be as independent as possible. But we also want to be a lot more flexible than the existing solutions.. > In addition we have had way to many questions of what is the right > policy for a bootloader to implement, on this list. I refuse > to couple that to the LinuxBIOS core. And I don't want some stupid > policy in there like FILO's that would require me to upgrade > my firmware just to upgrade my OS. Please explain, how is filo worse here than putting linux in flash? Stefan From donbrown at usa.net Mon Apr 5 10:16:01 2004 From: donbrown at usa.net (Don Brown) Date: Mon Apr 5 10:16:01 2004 Subject: Largest BIOS Workspace Message-ID: <000901c41b1c$26addfe0$c801a8c0@DEMOLAPTOP> Within BIOS in general and LinuxBIOS in particular, what is the largest workspace available. Are we limited to a 4 meg chip to store LinuxBIOS? Can we build or lever into some larger area? Don Brown, Atlanta GA -------------- next part -------------- An HTML attachment was scrubbed... URL: From Antony at Soft-Solutions.co.uk Mon Apr 5 10:24:01 2004 From: Antony at Soft-Solutions.co.uk (Antony Stone) Date: Mon Apr 5 10:24:01 2004 Subject: Largest BIOS Workspace In-Reply-To: <000901c41b1c$26addfe0$c801a8c0@DEMOLAPTOP> References: <000901c41b1c$26addfe0$c801a8c0@DEMOLAPTOP> Message-ID: <200404051550.19750.Antony@Soft-Solutions.co.uk> On Monday 05 April 2004 3:41 pm, Don Brown wrote: > Within BIOS in general and LinuxBIOS in particular, what is the largest > workspace available. Are we limited to a 4 meg chip to store LinuxBIOS? > Can we build or lever into some larger area? Depends on your motherboard (primarily - how many address lines go to the BIOS socket?). If you use banked architectures such as DoC then you can access much larger amounts of storage on a device plugged into that socket, however I'm not sure if that meets your needs (maybe you're looking for a simple contiguous memory space)? Regards, Antony. -- You can spend the whole of your life trying to be popular, but at the end of the day the size of the crowd at your funeral will be largely dictated by the weather. - Frank Skinner Please reply to the list; please don't CC me. From YhLu at tyan.com Mon Apr 5 14:06:00 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 5 14:06:00 2004 Subject: =?GB2312?B?tPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85CB5@TYANWEB> Sone, You may add the zelf make option as Etherboot to make payload smaller. YH. -----????----- ???: Takeshi Sone [mailto:ts1 at tsn.or.jp] ????: 2004?4?5? 2:40 ???: ebiederman at lnxi.com ??: linuxbios at clustermatic.org ??: Re: FILO 0.4 [PMX:#] Eric, Sorry for not replying soon. I've been busy with real job and life, config file support is not yet written, though I'm still willing to do it (+ USB support etc..) This situation would not seem to change in a month or two.. > -----Original Message----- > From: ebiederman at lnxi.com (Eric W. Biederman) > Sent: 04 Apr 2004 21:10:51 -0600 > To: ron minnich > Subject: Re: FILO 0.4 [PMX:#] > > ron minnich writes: > > > On Sun, 4 Apr 2004, Yinghai Lu wrote: > > > > > I have checked the Etherboot, and it would be some easier to integrate filo > > > into Etherboot. > > > > Not everyone here at LANL is that satisfied with etherboot, and in fact we > > are moving over to FILO. There are a lot of reasons. We\'ve just had lots > > better luck with FILO when all things are considered. > > Ron, is LANL going to maintain FILO then? > > Unless I hear from SONE soon it is starting to look like like FILO is > unmaintained. > > Has any one implemented config files? > Has any one implemented listing of files? > > What do you do when you don\'t have a disk? > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios ___________________________________________________________________________ _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From YhLu at tyan.com Mon Apr 5 14:14:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 5 14:14:01 2004 Subject: =?GB2312?B?tPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85CBA@TYANWEB> Eric, If the put the etherboot and filo in the ROM at the same time for fallback mode, Is it possible to make payload be selected by the elfboot? ( Controlled by cmos layout or key) Or let the Etherboot load another elf in ROM instead of HD? ( in the boot option add BOOT_ELF or BOOT_ZELF together with BOOT_NIC, BOOT_DISK, BOOT_FLOPPY). Regards YH -----????----- ???: Stefan Reinauer [mailto:stepan at openbios.org] ????: 2004?4?5? 5:47 ???: Eric W. Biederman ??: Greg Watson; YhLu; 'SONE Takeshi'; linuxbios at clustermatic.org ??: Re: FILO 0.4 [PMX:#] * Eric W. Biederman [040405 05:02]: > If we want to take a snapshot of the source tree of FILO or any other > bootloader into the LinuxBIOS tree under util. Build that part of the > build and build a complete romimage that works. I am fine > with that. It is even reasonable to make it so you can drop in > external trees like etherboot and have everything build together > nicely. > > Actual linking things together instead of including them together > is unacceptable. What about the following: Currently LinuxBIOS divides into 2 fundamental parts: 1) hardware initialization 2) getting and starting the payload This second part consists of two parts, again: i) elfloader ii) payload Note, this is only one possible design. Maybe, this design is bloated for some application cases. Eric, you want to make a hard cut between what is LinuxBIOS and what is not. This is generally a good idea, as it keeps the different initialization steps distinct from reach other. What, if we add another cut by dividing hardware initialization frin the payload-loader? Instead of packing stuff like filo to util, we could do: * create a directory loader which can hold all "loaders" * move the elf loader with a Config.lb to a subdirectory in there * create other directories for other "loaders" like filo. If done right, filo can still be compiled as a payload, or built in if the win in size is noticable. A target config file could probably choose which method to use, without overhead. Also, syncing with other trees, like Takeshi's filo tree could be fairly easy, too. I don't think we really have a conflict in direction here at all. LinuxBIOS itself should be as small as possible, and the different parts should be as independent as possible. But we also want to be a lot more flexible than the existing solutions.. > In addition we have had way to many questions of what is the right > policy for a bootloader to implement, on this list. I refuse > to couple that to the LinuxBIOS core. And I don't want some stupid > policy in there like FILO's that would require me to upgrade > my firmware just to upgrade my OS. Please explain, how is filo worse here than putting linux in flash? Stefan From dwh at lanl.gov Mon Apr 5 15:22:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Mon Apr 5 15:22:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: I've got one word for ya Ron: .ebuild Just kidding :) (Or am I?) On Sun, 4 Apr 2004, ron minnich wrote: > One build, not two or three. And people want it in one package. From YhLu at tyan.com Mon Apr 5 15:29:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 5 15:29:01 2004 Subject: int 15 e820h Message-ID: <3174569B9743D511922F00A0C943142304B85CCD@TYANWEB> Ron, When kernel is loading, it will call int 15, e820h to get memory map. Where does LinuxBIOS put the int 15 e820h processing code? Regards YH From ebiederman at lnxi.com Mon Apr 5 23:11:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 5 23:11:01 2004 Subject: int 15 e820h In-Reply-To: <3174569B9743D511922F00A0C943142304B85CCD@TYANWEB> References: <3174569B9743D511922F00A0C943142304B85CCD@TYANWEB> Message-ID: YhLu writes: > Ron, > > When kernel is loading, it will call int 15, e820h to get memory map. > > Where does LinuxBIOS put the int 15 e820h processing code? It does not have any mkelfImage bypass that piece of kernel code. We read an equivalent table out of the LinuxBIOS table and pass it to the kernel instead. Eric From ebiederman at lnxi.com Mon Apr 5 23:34:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 5 23:34:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: References: Message-ID: Takeshi Sone writes: > Eric, > Sorry for not replying soon. > I've been busy with real job and life, config file support is not > yet written, though I'm still willing to do it (+ USB support etc..) > This situation would not seem to change in a month or two.. Ok. I was starting to wonder if you were out there. I am looking at using FILO as a disked based bootloader. So I might just write that code and send you a patch. Right now I think a bootloader of this type with a config file is not terribly useful. Eric From jbors at mail.ru Mon Apr 5 23:56:01 2004 From: jbors at mail.ru (Dmitry Borisov) Date: Mon Apr 5 23:56:01 2004 Subject: FILO 0.4 [PMX:#] References: Message-ID: <007201c41b8e$d60e8bc0$0300a8c0@amr.corp.intel.com> > I am looking at using FILO as a disked based bootloader. So I might > just write that code and send you a patch. > > Right now I think a bootloader of this type with a config file is > not terribly useful. > Bootloader sounds nice. It should be compatible with Win2K and XP right ? Dmitry/ From ebiederman at lnxi.com Tue Apr 6 00:46:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Apr 6 00:46:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: References: Message-ID: ron minnich writes: > RE the bigger issue of compiling things direct into linuxbios. > > I've been thinking for some time of an experiment, namely turning this > whole business inside-out. Think of it this way: there is a runtime > startup for every program your write, called in old times crt0 (which is > why I used that name for LinuxBIOS). But from your point of view, your > program is not crt0, it's main(). > > So looking from the point of view of the compiler and library writers, who > know nothing of your program when they write the compilers and libraries, > the world is libc.a and crt0. You don't care about that, and from your > point of view, the world is your program. You use the compiler to get your > startup code and some library calls. > > This leads to a natural question: what if we think of linuxbios as > something to be linked into a boot loader such as openbios, filo, 9load, > or even a special linux kernel? In other words, invert our view of the > world: we don't compile a boot loader as part of building linuxbios; we > compile linuxbios into a bootloader. Linuxbios provides startup (analogous > to crt0) and some library functions the boot loader needs (print* support, > pci enumeration, etc) but the really important bit is the boot loader. > > In this view, linuxbios is a library that you link your bootloader with to > build a bios. This really changes things around a bit. It also removes > some nasty problems, as the bootloader no longer has to supply (e.g.) its > own PCI enumeration code, and can use the linuxbios PCI enumeration code, > which can help boot loaders avoid bugs in chips (consider the VT8601 and > the PCI bugs it used to have). The amount of code we are talking about there is about a 1000 lines (at least on x86), and can easily be shared by cut and paste. I would be surprised if PPC and other architectures were worse, but they may be. As for avoiding bugs, the solution is to dump our device tree via the LinuxBIOS table. That is on the TODO list. It has not been a big enough problem for anyone to care about implementing it yet. > This view is sort of halfway from old bios ideas (INT xy) and current > ideas (the payload doesn't know linuxbios exists). It's a huge change -- > maybe a very bad idea, as it means that now LinuxBIOS provides an API, > which we never intended it to do. I have no idea if it even makes sense -- > just wondering. Yes this is how you implement a bad imitation of an OS. First you start adding functions that the core LinuxBIOS code cares nothing about so they are poorly maintained. Then you turn into a shared library so multiple programs running on the system can call you. Then you implement support for binary plugin options roms. You have to write multiple versions of your code for: 8, 16, 32, 64, and 128 bit processor modes. And they have to all cooperate nicely. Basically you do what everyone has always done before and resulted in a big maintenance nightmare. I refuse to even consider maintaining that. I am really only interested only interested in supporting free-standing programs. > Back to our irregularly scheduled arguments :-) Eric From rminnich at lanl.gov Tue Apr 6 12:22:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 12:22:00 2004 Subject: Largest BIOS Workspace In-Reply-To: <000901c41b1c$26addfe0$c801a8c0@DEMOLAPTOP> Message-ID: On Mon, 5 Apr 2004, Don Brown wrote: > Within BIOS in general and LinuxBIOS in particular, what is the largest > workspace available. Are we limited to a 4 meg chip to store LinuxBIOS? > Can we build or lever into some larger area? you can take as big an area as you want, but you need a chip that big. The limit is the chip, not linuxbios. also, 4 meg: you mean megabits or megabytes? Lotsa confusion from people on this ... ron From rminnich at lanl.gov Tue Apr 6 12:34:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 12:34:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: On Mon, 5 Apr 2004, Hendricks David W. wrote: > I've got one word for ya Ron: .ebuild ARGARGARG. You're kidding. ron From rminnich at lanl.gov Tue Apr 6 12:37:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 12:37:01 2004 Subject: int 15 e820h In-Reply-To: <3174569B9743D511922F00A0C943142304B85CCD@TYANWEB> Message-ID: On Mon, 5 Apr 2004, YhLu wrote: > When kernel is loading, it will call int 15, e820h to get memory map. nowhere. This is the idea behind Eric's linuxbios tables. Also IIRC we do have e820 tables in memory: has linux stopped using them? Linux used to say: "We don't need no steenking BIOS". With the later 2.4.x and 2.6, they seem to be saying "We really need the steenking BIOS". What is going on with Linux? They're moving backwards. We really don't want to support INT type stuff. ron From rminnich at lanl.gov Tue Apr 6 13:01:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 13:01:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: On 5 Apr 2004, Eric W. Biederman wrote: > I am looking at using FILO as a disked based bootloader. So I might > just write that code and send you a patch. We want FILO in FLASH, not on disk. We are using FLASH-based FILO to replace FLASH-based Etherboot on Pink and will be using FILO to replace Etherboot on Lightning and Blue Steel to load images from IDE-FLASH. We are very happy with its capability in that mode. It's just a ton easier for a sysadmin to mount the IDE-FLASH as ext2 and change kernel file names instead of dd-ing raw kernel images onto an IDE-FLASH. FILO lets us treat IDE-FLASH as a file system, and Etherboot had us treating it as a raw disk. We prefer FILO at this point, and I think we will not be the only ones. Also we have found the build procedure for FILO to be less prone to error and problems than for Etherboot. That's not to say Etherboot does not have *many* applications: it is terrific for lots of things, just not for our clusters right now. > Right now I think a bootloader of this type with a config file is > not terribly useful. It is all context. I think we need to turn our thinking a bit. The BIOS you use is going to become more application-specific. What you have in an embedded "black box" will not need to be identical to what you have on your desk or your cluster. I think this is all to the good. ron From rminnich at lanl.gov Tue Apr 6 13:04:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 13:04:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: On 5 Apr 2004, Eric W. Biederman wrote: > (some good points). > I am really only interested only interested in supporting free-standing > programs. Yeah, I think I share your interest. Having a BIOS with an API could be a can of worms. Back to our regularly scheduled discussion. ron From YhLu at tyan.com Tue Apr 6 13:34:01 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 6 13:34:01 2004 Subject: =?GB2312?B?tPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85D81@TYANWEB> So you must use filo as normal payload and Etherboot as fallback payload. Then if I want to boot from network in normal mode, how to do? Why just merge filo into Etherboot? So we can use tg3--filo.zelf instead of tg3--ide_disk.zelf. Regards YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?6? 10:28 ???: Eric W. Biederman ??: Takeshi Sone; linuxbios at clustermatic.org ??: Re: FILO 0.4 [PMX:#] On 5 Apr 2004, Eric W. Biederman wrote: > I am looking at using FILO as a disked based bootloader. So I might > just write that code and send you a patch. We want FILO in FLASH, not on disk. We are using FLASH-based FILO to replace FLASH-based Etherboot on Pink and will be using FILO to replace Etherboot on Lightning and Blue Steel to load images from IDE-FLASH. We are very happy with its capability in that mode. It's just a ton easier for a sysadmin to mount the IDE-FLASH as ext2 and change kernel file names instead of dd-ing raw kernel images onto an IDE-FLASH. FILO lets us treat IDE-FLASH as a file system, and Etherboot had us treating it as a raw disk. We prefer FILO at this point, and I think we will not be the only ones. Also we have found the build procedure for FILO to be less prone to error and problems than for Etherboot. That's not to say Etherboot does not have *many* applications: it is terrific for lots of things, just not for our clusters right now. > Right now I think a bootloader of this type with a config file is > not terribly useful. It is all context. I think we need to turn our thinking a bit. The BIOS you use is going to become more application-specific. What you have in an embedded "black box" will not need to be identical to what you have on your desk or your cluster. I think this is all to the good. ron _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Tue Apr 6 13:47:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 13:47:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: BTW I'm on vacation, so if you don't hear from me it's not that I don't care, it's just that I am not paid to care while on vacation :-) ron From rminnich at lanl.gov Tue Apr 6 13:48:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 13:48:00 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: Message-ID: On Tue, 6 Apr 2004, ron minnich wrote: > On 5 Apr 2004, Eric W. Biederman wrote: > > > (some good points). > > I am really only interested only interested in supporting free-standing > > programs. > > Yeah, I think I share your interest. Having a BIOS with an API could be a > can of worms. actually, I should say, from 5 years ago, that the planned API for the BIOS was ... Linux. Sigh, I keep forgetting. Sorry. ron From rminnich at lanl.gov Tue Apr 6 13:52:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 13:52:00 2004 Subject: =?GB2312?B?tPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B85D81@TYANWEB> Message-ID: On Tue, 6 Apr 2004, YhLu wrote: > So you must use filo as normal payload and Etherboot as fallback payload. we can't use etherboot on Pink anyway for network boots. There is no ethernet on Pink. 1024 nodes with no Ethernet. instead, using Filo, we have normal and fallback kernel images on the ext-2 formatted IDE FLASH. ron > So we can use tg3--filo.zelf instead of tg3--ide_disk.zelf. no need here. ron From YhLu at tyan.com Tue Apr 6 14:04:01 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 6 14:04:01 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85D86@TYANWEB> You must prepare 1024 IDE flash one by one at the beginning. It took one week to get it done? YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?6? 11:19 ???: YhLu ??: Eric W. Biederman; Takeshi Sone; linuxbios at clustermatic.org ??: Re: ??: FILO 0.4 [PMX:#] On Tue, 6 Apr 2004, YhLu wrote: > So you must use filo as normal payload and Etherboot as fallback payload. we can't use etherboot on Pink anyway for network boots. There is no ethernet on Pink. 1024 nodes with no Ethernet. instead, using Filo, we have normal and fallback kernel images on the ext-2 formatted IDE FLASH. ron > So we can use tg3--filo.zelf instead of tg3--ide_disk.zelf. no need here. ron From pyro at linuxlabs.com Tue Apr 6 14:11:01 2004 From: pyro at linuxlabs.com (Steven James) Date: Tue Apr 6 14:11:01 2004 Subject: =?GB2312?B?tPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B85D81@TYANWEB> References: <3174569B9743D511922F00A0C943142304B85D81@TYANWEB> Message-ID: Greetings, You can use bootselect in utils/baremetal to choose between multiple payloads. G'day, sjames -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 2701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 ----------------------------------------------------------------------- On Tue, 6 Apr 2004, YhLu wrote: > So you must use filo as normal payload and Etherboot as fallback payload. > > Then if I want to boot from network in normal mode, how to do? > > Why just merge filo into Etherboot? > > So we can use tg3--filo.zelf instead of tg3--ide_disk.zelf. > > Regards > > YH > > -----????----- > ???: ron minnich [mailto:rminnich at lanl.gov] > ????: 2004?4?6? 10:28 > ???: Eric W. Biederman > ??: Takeshi Sone; linuxbios at clustermatic.org > ??: Re: FILO 0.4 [PMX:#] > > On 5 Apr 2004, Eric W. Biederman wrote: > > > I am looking at using FILO as a disked based bootloader. So I might > > just write that code and send you a patch. > > We want FILO in FLASH, not on disk. We are using FLASH-based FILO to > replace FLASH-based Etherboot on Pink and will be using FILO to replace > Etherboot on Lightning and Blue Steel to load images from IDE-FLASH. We > are very happy with its capability in that mode. It's just a ton easier > for a sysadmin to mount the IDE-FLASH as ext2 and change kernel file names > instead of dd-ing raw kernel images onto an IDE-FLASH. FILO lets us treat > IDE-FLASH as a file system, and Etherboot had us treating it as a raw > disk. We prefer FILO at this point, and I think we will not be the only > ones. Also we have found the build procedure for FILO to be less prone to > error and problems than for Etherboot. > > That's not to say Etherboot does not have *many* applications: it is > terrific for lots of things, just not for our clusters right now. > > > Right now I think a bootloader of this type with a config file is > > not terribly useful. > > It is all context. I think we need to turn our thinking a bit. The BIOS > you use is going to become more application-specific. What you have in an > embedded "black box" will not need to be identical to what you have on > your desk or your cluster. I think this is all to the good. > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Tue Apr 6 14:29:00 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 6 14:29:00 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85D8E@TYANWEB> choose_stream can be moved into freebios2. hardware main can call that before elfboot. Need to get boot_order from CMOS and device load which pay load first. YH -----????----- ???: Steven James [mailto:pyro at linuxlabs.com] ????: 2004?4?6? 11:38 ???: YhLu ??: ron minnich; Eric W. Biederman; Takeshi Sone; linuxbios at clustermatic.org ??: Re: ??: FILO 0.4 [PMX:#] Greetings, You can use bootselect in utils/baremetal to choose between multiple payloads. G'day, sjames -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 2701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 ----------------------------------------------------------------------- On Tue, 6 Apr 2004, YhLu wrote: > So you must use filo as normal payload and Etherboot as fallback payload. > > Then if I want to boot from network in normal mode, how to do? > > Why just merge filo into Etherboot? > > So we can use tg3--filo.zelf instead of tg3--ide_disk.zelf. > > Regards > > YH > > -----????----- > ???: ron minnich [mailto:rminnich at lanl.gov] > ????: 2004?4?6? 10:28 > ???: Eric W. Biederman > ??: Takeshi Sone; linuxbios at clustermatic.org > ??: Re: FILO 0.4 [PMX:#] > > On 5 Apr 2004, Eric W. Biederman wrote: > > > I am looking at using FILO as a disked based bootloader. So I might > > just write that code and send you a patch. > > We want FILO in FLASH, not on disk. We are using FLASH-based FILO to > replace FLASH-based Etherboot on Pink and will be using FILO to replace > Etherboot on Lightning and Blue Steel to load images from IDE-FLASH. We > are very happy with its capability in that mode. It's just a ton easier > for a sysadmin to mount the IDE-FLASH as ext2 and change kernel file names > instead of dd-ing raw kernel images onto an IDE-FLASH. FILO lets us treat > IDE-FLASH as a file system, and Etherboot had us treating it as a raw > disk. We prefer FILO at this point, and I think we will not be the only > ones. Also we have found the build procedure for FILO to be less prone to > error and problems than for Etherboot. > > That's not to say Etherboot does not have *many* applications: it is > terrific for lots of things, just not for our clusters right now. > > > Right now I think a bootloader of this type with a config file is > > not terribly useful. > > It is all context. I think we need to turn our thinking a bit. The BIOS > you use is going to become more application-specific. What you have in an > embedded "black box" will not need to be identical to what you have on > your desk or your cluster. I think this is all to the good. > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Tue Apr 6 23:23:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 6 23:23:00 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B85D86@TYANWEB> Message-ID: On Tue, 6 Apr 2004, YhLu wrote: > You must prepare 1024 IDE flash one by one at the beginning. It took one > week to get it done? 30 seconds to update. The initial case is hard though :-) Linux Networx (Eric, really) set it all up before Pink arrived. ron From bari at onelabs.com Wed Apr 7 21:44:01 2004 From: bari at onelabs.com (Bari Ari) Date: Wed Apr 7 21:44:01 2004 Subject: XScale Port Message-ID: <4074B4C9.9010700@onelabs.com> We're starting back up a LinuxBIOS port to ARM with the Xscale processors. The port should make it easier for anyone using the PXA, IXP, IXC and IOP Intel parts in the future. We're going to be looking at also supporting PCI-PCI bridges (transparent and non-transparent) and PCI southbridges that are used in the x86 PC world. I'm interested in what, if any graphics controllers were used and supported via the PPC port of LinuxBIOS. Were any PC type graphics controllers used (eg. ATI, Silicon Motion) and how were they supported for init., driver etc. -Bari From YhLu at tyan.com Thu Apr 8 00:27:01 2004 From: YhLu at tyan.com (YhLu) Date: Thu Apr 8 00:27:01 2004 Subject: 5705 support Message-ID: <3174569B9743D511922F00A0C943142304B85EB0@TYANWEB> Eric, Etherboot 5.2.4 can recognize the 5705, but when download elf, it does not end. 5.3.7 has the same problem, even in Normal BIOS. Regards YH [tg3-5705]Ethernet addr: 00:E0:81:60:3B:84 Tigon3 [partno(BCM95705C3) rev 3003 PHY(unknown)] (PCI:33MHz:32-bit) Link is up at 100 Mbps, half duplex. Searching for server (DHCP)... ..Me: 192.168.1.194, Server: 192.168.1.1, Gateway 192.168.1.1 Loading 192.168.1.1:ram0_2.5_2.6.5_k8_mydisk7.elf ...(ELF)... ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ ............................................................................ .......................... From YhLu at tyan.com Thu Apr 8 00:29:00 2004 From: YhLu at tyan.com (YhLu) Date: Thu Apr 8 00:29:00 2004 Subject: =?GB2312?B?tPC4tDogaW50IDE1IGU4MjBo?= Message-ID: <3174569B9743D511922F00A0C943142304B85EB1@TYANWEB> Because the NUMA is not mature in Linux, or just X86-64?? YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?6? 10:04 ???: YhLu ??: Eric W. Biederman; linuxbios at clustermatic.org ??: Re: int 15 e820h On Mon, 5 Apr 2004, YhLu wrote: > When kernel is loading, it will call int 15, e820h to get memory map. nowhere. This is the idea behind Eric's linuxbios tables. Also IIRC we do have e820 tables in memory: has linux stopped using them? Linux used to say: "We don't need no steenking BIOS". With the later 2.4.x and 2.6, they seem to be saying "We really need the steenking BIOS". What is going on with Linux? They're moving backwards. We really don't want to support INT type stuff. ron From YhLu at tyan.com Thu Apr 8 00:30:01 2004 From: YhLu at tyan.com (YhLu) Date: Thu Apr 8 00:30:01 2004 Subject: =?GB2312?B?tPC4tDogaW50IDE1IGU4MjBo?= Message-ID: <3174569B9743D511922F00A0C943142304B85EB2@TYANWEB> So the header add by mkelfImage, bypass the int 15 e820h. YH -----????----- ???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] ????: 2004?4?5? 20:38 ???: YhLu ??: ron minnich; linuxbios at clustermatic.org ??: Re: int 15 e820h YhLu writes: > Ron, > > When kernel is loading, it will call int 15, e820h to get memory map. > > Where does LinuxBIOS put the int 15 e820h processing code? It does not have any mkelfImage bypass that piece of kernel code. We read an equivalent table out of the LinuxBIOS table and pass it to the kernel instead. Eric From YhLu at tyan.com Thu Apr 8 00:58:00 2004 From: YhLu at tyan.com (YhLu) Date: Thu Apr 8 00:58:00 2004 Subject: pnp init call and winbond HWM enable patch. Message-ID: <3174569B9743D511922F00A0C943142304B85EB4@TYANWEB> Ron or Ollie, Please help to commit the patch. 1. pnp init calling patch. ( two ops confusing in old code) 2. Winbond w83627hf HWM enable. In case for lmsensors to read sensors in addition to smbus to adm1027, it can access other behind w83627hf. Eric, Does the NSC PC87360 need outb 0x2e 0x87 two times to enter extension function mode to manipulate the 0x30 above regs of LPC? Regards YH -------------- next part -------------- A non-text attachment was scrubbed... Name: fb2_pnp_init_winbond_hwm_enable_change.diff.bz2 Type: application/octet-stream Size: 3639 bytes Desc: not available URL: From YhLu at tyan.com Thu Apr 8 01:01:01 2004 From: YhLu at tyan.com (YhLu) Date: Thu Apr 8 01:01:01 2004 Subject: =?GB2312?B?tPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85EB5@TYANWEB> Can the user use the disk bootloader to install OS into HD? YH -----????----- ???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] ????: 2004?4?5? 21:02 ???: Takeshi Sone ??: linuxbios at clustermatic.org ??: Re: FILO 0.4 [PMX:#] Takeshi Sone writes: > Eric, > Sorry for not replying soon. > I've been busy with real job and life, config file support is not > yet written, though I'm still willing to do it (+ USB support etc..) > This situation would not seem to change in a month or two.. Ok. I was starting to wonder if you were out there. I am looking at using FILO as a disked based bootloader. So I might just write that code and send you a patch. Right now I think a bootloader of this type with a config file is not terribly useful. Eric _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From ebiederman at lnxi.com Thu Apr 8 01:33:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Thu Apr 8 01:33:01 2004 Subject: XScale Port In-Reply-To: <4074B4C9.9010700@onelabs.com> References: <4074B4C9.9010700@onelabs.com> Message-ID: Bari Ari writes: > We're starting back up a LinuxBIOS port to ARM with the Xscale processors. The > port should make it easier for anyone using the PXA, IXP, IXC and IOP Intel > parts in the future. We're going to be looking at also supporting PCI-PCI > bridges (transparent and non-transparent) and PCI southbridges that are used in > the x86 PC world. The bridge code should pretty much just work in freebios2. A really weird bridge might need some non default routines but basically things should work. Eric From ts1 at tsn.or.jp Thu Apr 8 07:51:01 2004 From: ts1 at tsn.or.jp (Takeshi Sone) Date: Thu Apr 8 07:51:01 2004 Subject: =?iso-2022-jp?B?GyRCRXobKEI/Pzo=?= FILO 0.4 [PMX:#] In-Reply-To: <3174569B9743D511922F00A0C943142304B85EB5@TYANWEB> References: <3174569B9743D511922F00A0C943142304B85EB5@TYANWEB> Message-ID: <20040408130129.GA23563@tsn.or.jp> On Wed, Apr 07, 2004 at 10:36:33PM -0700, YhLu wrote: > Can the user use the disk bootloader to install OS into HD? Yes, I have successfully booted off SuSE and other Linux CD-ROMs with LinuxBIOS+FILO. -- Takeshi From mdeschamps at mangrove-systems.com Thu Apr 8 08:15:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Thu Apr 8 08:15:01 2004 Subject: LinuxBios and Openbios's dev/bios capacity Message-ID: <1081430628.1299.52.camel@Calliphara> I've found in OpenBios dev/bios a good reason to hope i could spare the cost of a "physical" flashing device , and a ease using. That is to say getting LinuxBios building the .bin and flash the onboard BIOS via the dev/bios mechanism. I have a via/epia and a SST39 series 20A (256Ko) bios chip on I'd thought I could read/write this bios with cat my.bin >/dev/bios but by insmoding bios.o. But i got a kmess coming from lines 123-126 printk code of bios.c "BIOS : No flash devices found" This resulting in a console message "Device busy" (that is, though, a bit paradoxal notfound != busy isn't it ? :) ) I can't catch what have missed me... Is dev/bios couldn't be used in my aim ? Gratefull if experienced people could help me. Cordialy. Mathieu From gwatson at lanl.gov Thu Apr 8 11:14:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Thu Apr 8 11:14:01 2004 Subject: Clustermatic 4 wins ClusterWorld Award Message-ID: <4534EB49-8979-11D8-BEFB-000393A47A5C@lanl.gov> Hi all, I'm pleased to announce that yesterday Clustermatic 4 won the ClusterWorld Excellence in Cluster Technology Award for Open Source Software. I'd like to thank everyone who worked so hard to achieve this outstanding result. Thanks also to Daniel Gruner and Jim Phillips for agreeing to act as reference sites for Clustermatic. Best regards, Greg From mdeschamps at mangrove-systems.com Thu Apr 8 11:15:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Thu Apr 8 11:15:01 2004 Subject: VIA EPIA Build Error MAX_REBOOT_CT Message-ID: <1081441392.1299.71.camel@Calliphara> I'am building a new rom but now,I got stuck because of #error "MAX_REBOOT_CNT not defined" in make process of build target even though i defined this in Config.lb Here is a process trace : ####################################################################### if (cd fallback; \ make linuxbios.rom)\ then true; else exit 1; fi; make[1]: Entering directory `/home/root/projet-07042004/freebios/freebios2/build/epia/fallbac k' cp /home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base crt0.S gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E -I/home/root/projet/freebios/freebios2/src -D __ROMCC__=0 -D__ROMCC_MINOR__=38 -I/home/root/projet/freebios/freebios2/src/include -I/home/r oot/projet/freebios/freebios2/src/arch/i386/include -I/usr/lib/gcc-lib/i486-linux/egcs-2.91.6 6/include /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c > ./failover.E gcc: unrecognized option `-no-gcc' In file included from /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c: 7: /home/root/projet/freebios/freebios2/src/pc80/mc146818rtc_early.c:5: #error "MAX_REBOOT_CNT n ot defined" make[1]: *** [failover.E] Error 1 make[1]: Leaving directory `/home/root/projet-07042004/freebios/freebios2/build/epia/fallback ' make: *** [fallback-rom] Error 1 ################################################################# What is that pc80 directory in which it errors ? The parameter MAX_BOOT_CT is the counter that holds the survival of kernel messages after # boots, isn't it ? I've also joined the Config file on which i haven't made much changes except what it asked for. Please mail me a clue, just ask if you need moer info on the slab. Thanks in advance. ################################################################ # Sample config file for EPIA # This will make a target directory of ./epia # # Change for experimentation MD # loadoptions target epia uses ARCH uses CONFIG_COMPRESS uses CONFIG_IOAPIC uses CONFIG_ROM_STREAM uses CONFIG_ROM_STREAM_START uses CONFIG_UDELAY_TSC uses CPU_FIXUP uses FALLBACK_SIZE uses HAVE_FALLBACK_BOOT uses HAVE_MP_TABLE uses HAVE_PIRQ_TABLE uses HAVE_HARD_RESET uses i586 uses i686 uses INTEL_PPRO_MTRR uses HEAP_SIZE uses IRQ_SLOT_COUNT uses MAINBOARD_PART_NUMBER uses MAINBOARD_VENDOR uses CONFIG_SMP uses CONFIG_MAX_CPUS uses MEMORY_HOLE uses PAYLOAD_SIZE uses _RAMBASE uses _ROMBASE uses ROM_IMAGE_SIZE uses ROM_SECTION_OFFSET uses ROM_SECTION_SIZE uses ROM_SIZE uses STACK_SIZE uses USE_FALLBACK_IMAGE uses USE_OPTION_TABLE uses HAVE_OPTION_TABLE uses MAXIMUM_CONSOLE_LOGLEVEL uses DEFAULT_CONSOLE_LOGLEVEL # Sample config file for EPIA # This will make a target directory of ./epia # # Change for experimentation MD # loadoptions target epia uses ARCH uses CONFIG_COMPRESS uses CONFIG_IOAPIC uses CONFIG_ROM_STREAM uses CONFIG_ROM_STREAM_START uses CONFIG_UDELAY_TSC uses CPU_FIXUP uses FALLBACK_SIZE uses HAVE_FALLBACK_BOOT uses HAVE_MP_TABLE uses HAVE_PIRQ_TABLE uses HAVE_HARD_RESET uses i586 uses i686 uses INTEL_PPRO_MTRR uses HEAP_SIZE uses IRQ_SLOT_COUNT uses MAINBOARD_PART_NUMBER uses MAINBOARD_VENDOR uses CONFIG_SMP uses CONFIG_MAX_CPUS uses MEMORY_HOLE uses PAYLOAD_SIZE uses _RAMBASE uses _ROMBASE uses ROM_IMAGE_SIZE uses ROM_SECTION_OFFSET uses ROM_SECTION_SIZE uses ROM_SIZE uses STACK_SIZE uses USE_FALLBACK_IMAGE uses USE_OPTION_TABLE uses HAVE_OPTION_TABLE uses MAXIMUM_CONSOLE_LOGLEVEL uses DEFAULT_CONSOLE_LOGLEVE uses CONFIG_CONSOLE_SERIAL8250 uses MAINBOARD uses CONFIG_CHIP_CONFIGURE uses XIP_ROM_SIZE uses XIP_ROM_BASE uses LINUXBIOS_EXTRA_VERSION uses TTYS0_BAUD uses MAX_REBOOT_CNT option TTYS0_BAUD=19200 option CONFIG_CHIP_CONFIGURE=1 option MAXIMUM_CONSOLE_LOGLEVEL=7 option DEFAULT_CONSOLE_LOGLEVEL=7 option CONFIG_CONSOLE_SERIAL8250=1 option CPU_FIXUP=1 option CONFIG_UDELAY_TSC=0 option i686=1 option i586=1 option INTEL_PPRO_MTRR=1 option ROM_SIZE=256*1024 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_STREAM=1 option HAVE_FALLBACK_BOOT=1 # # More Options # option MAX_REBOOT_CNT=10 ### ### Compute the location and size of where this firmware image ### (linuxBIOS plus bootloader) will live in the boot rom chip. ### option FALLBACK_SIZE=131072 ## LinuxBIOS C code runs at this location in RAM option _RAMBASE=0x00004000 # ### ### Compute the start location and size size of ### The linuxBIOS bootloader. ### # # Arima hdama romimage "normal" option USE_FALLBACK_IMAGE=0 option ROM_IMAGE_SIZE=0x10000 option LINUXBIOS_EXTRA_VERSION=".0Normal" mainboard via/epia # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf payload ../../../../../lnxieepro100.ebi end romimage "fallback" option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0x10000 option LINUXBIOS_EXTRA_VERSION=".0Fallback" mainboard via/epia # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf payload ../../../../../lnxieepro100.ebi end buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback" From gwatson at lanl.gov Thu Apr 8 12:02:05 2004 From: gwatson at lanl.gov (Greg Watson) Date: Thu Apr 8 12:02:05 2004 Subject: VIA EPIA Build Error MAX_REBOOT_CT In-Reply-To: <1081441392.1299.71.camel@Calliphara> References: <1081441392.1299.71.camel@Calliphara> Message-ID: Check the Makefile.settings in the fallback directory and see if MAX_REBOOT_CNT is defined. If it isn't then there's some problem with the configuration. If it is, then it's not getting passed to the gcc command line. Greg On 08/04/2004, at 10:23 AM, Mathieu Deschamps wrote: > > I'am building a new rom but now,I got stuck because of > #error "MAX_REBOOT_CNT not defined" > in make process of build target even though i defined this in Config.lb > Here is a process trace : > > ####################################################################### > if (cd fallback; \ > make linuxbios.rom)\ > then true; else exit 1; fi; > make[1]: Entering directory > `/home/root/projet-07042004/freebios/freebios2/build/epia/fallbac > k' > cp /home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base > crt0.S > gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E > -I/home/root/projet/freebios/freebios2/src -D > __ROMCC__=0 -D__ROMCC_MINOR__=38 > -I/home/root/projet/freebios/freebios2/src/include -I/home/r > oot/projet/freebios/freebios2/src/arch/i386/include > -I/usr/lib/gcc-lib/i486-linux/egcs-2.91.6 > 6/include > > /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c > > > ./failover.E > gcc: unrecognized option `-no-gcc' > In file included from > /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c: > 7: > /home/root/projet/freebios/freebios2/src/pc80/mc146818rtc_early.c:5: > #error "MAX_REBOOT_CNT n > ot defined" > make[1]: *** [failover.E] Error 1 > make[1]: Leaving directory > `/home/root/projet-07042004/freebios/freebios2/build/epia/fallback > ' > make: *** [fallback-rom] Error 1 > ################################################################# > > > What is that pc80 directory in which it errors ? > The parameter MAX_BOOT_CT is the counter that holds the survival > of kernel messages after # boots, isn't it ? > > > I've also joined the Config file on which i haven't > made much changes except what it asked for. > > Please mail me a clue, just ask if you need moer info on the slab. > > > Thanks in advance. > > ################################################################ > # Sample config file for EPIA > # This will make a target directory of ./epia > # > # Change for experimentation MD > # > loadoptions > > target epia > > uses ARCH > uses CONFIG_COMPRESS > uses CONFIG_IOAPIC > uses CONFIG_ROM_STREAM > uses CONFIG_ROM_STREAM_START > uses CONFIG_UDELAY_TSC > uses CPU_FIXUP > uses FALLBACK_SIZE > uses HAVE_FALLBACK_BOOT > uses HAVE_MP_TABLE > uses HAVE_PIRQ_TABLE > uses HAVE_HARD_RESET > uses i586 > uses i686 > uses INTEL_PPRO_MTRR > uses HEAP_SIZE > uses IRQ_SLOT_COUNT > uses MAINBOARD_PART_NUMBER > uses MAINBOARD_VENDOR > uses CONFIG_SMP > uses CONFIG_MAX_CPUS > uses MEMORY_HOLE > uses PAYLOAD_SIZE > uses _RAMBASE > uses _ROMBASE > uses ROM_IMAGE_SIZE > uses ROM_SECTION_OFFSET > uses ROM_SECTION_SIZE > uses ROM_SIZE > uses STACK_SIZE > uses USE_FALLBACK_IMAGE > uses USE_OPTION_TABLE > uses HAVE_OPTION_TABLE > uses MAXIMUM_CONSOLE_LOGLEVEL > uses DEFAULT_CONSOLE_LOGLEVEL > > > # Sample config file for EPIA > # This will make a target directory of ./epia > # > # Change for experimentation MD > # > loadoptions > > target epia > > uses ARCH > uses CONFIG_COMPRESS > uses CONFIG_IOAPIC > uses CONFIG_ROM_STREAM > uses CONFIG_ROM_STREAM_START > uses CONFIG_UDELAY_TSC > uses CPU_FIXUP > uses FALLBACK_SIZE > uses HAVE_FALLBACK_BOOT > uses HAVE_MP_TABLE > uses HAVE_PIRQ_TABLE > uses HAVE_HARD_RESET > uses i586 > uses i686 > uses INTEL_PPRO_MTRR > uses HEAP_SIZE > uses IRQ_SLOT_COUNT > uses MAINBOARD_PART_NUMBER > uses MAINBOARD_VENDOR > uses CONFIG_SMP > uses CONFIG_MAX_CPUS > uses MEMORY_HOLE > uses PAYLOAD_SIZE > uses _RAMBASE > uses _ROMBASE > uses ROM_IMAGE_SIZE > uses ROM_SECTION_OFFSET > uses ROM_SECTION_SIZE > uses ROM_SIZE > uses STACK_SIZE > uses USE_FALLBACK_IMAGE > uses USE_OPTION_TABLE > uses HAVE_OPTION_TABLE > uses MAXIMUM_CONSOLE_LOGLEVEL > uses DEFAULT_CONSOLE_LOGLEVE > uses CONFIG_CONSOLE_SERIAL8250 > uses MAINBOARD > uses CONFIG_CHIP_CONFIGURE > uses XIP_ROM_SIZE > uses XIP_ROM_BASE > uses LINUXBIOS_EXTRA_VERSION > uses TTYS0_BAUD > uses MAX_REBOOT_CNT > > > option TTYS0_BAUD=19200 > > option CONFIG_CHIP_CONFIGURE=1 > > option MAXIMUM_CONSOLE_LOGLEVEL=7 > option DEFAULT_CONSOLE_LOGLEVEL=7 > option CONFIG_CONSOLE_SERIAL8250=1 > > option CPU_FIXUP=1 > option CONFIG_UDELAY_TSC=0 > option i686=1 > option i586=1 > option INTEL_PPRO_MTRR=1 > option ROM_SIZE=256*1024 > > option HAVE_OPTION_TABLE=1 > option CONFIG_ROM_STREAM=1 > option HAVE_FALLBACK_BOOT=1 > > # > # More Options > # > option MAX_REBOOT_CNT=10 > > > > ### > ### Compute the location and size of where this firmware image > ### (linuxBIOS plus bootloader) will live in the boot rom chip. > ### > option FALLBACK_SIZE=131072 > > ## LinuxBIOS C code runs at this location in RAM > option _RAMBASE=0x00004000 > > # > ### > ### Compute the start location and size size of > ### The linuxBIOS bootloader. > ### > > # > # Arima hdama > romimage "normal" > option USE_FALLBACK_IMAGE=0 > option ROM_IMAGE_SIZE=0x10000 > option LINUXBIOS_EXTRA_VERSION=".0Normal" > mainboard via/epia > # payload > /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf > # payload ../../../../tg3--ide_disk.zelf > payload ../../../../../lnxieepro100.ebi > end > > romimage "fallback" > option USE_FALLBACK_IMAGE=1 > option ROM_IMAGE_SIZE=0x10000 > option LINUXBIOS_EXTRA_VERSION=".0Fallback" > mainboard via/epia > # payload > /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf > # payload ../../../../tg3--ide_disk.zelf > payload ../../../../../lnxieepro100.ebi > end > > buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback" > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Thu Apr 8 12:21:01 2004 From: YhLu at tyan.com (YhLu) Date: Thu Apr 8 12:21:01 2004 Subject: =?utf-8?B?562U5aSNOiDnrZQ/PzogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85ED5@TYANWEB> So, if I can enable the ati rage xl in LinuxBIOS, I can substitute the normal bios with LinuxBIOS. YH -----????----- ???: Takeshi Sone [mailto:ts1 at tsn.or.jp] ????: 2004?4?8? 6:01 ???: YhLu ??: ebiederman at lnxi.com; linuxbios at clustermatic.org ??: Re: ???: FILO 0.4 [PMX:#] On Wed, Apr 07, 2004 at 10:36:33PM -0700, YhLu wrote: > Can the user use the disk bootloader to install OS into HD? Yes, I have successfully booted off SuSE and other Linux CD-ROMs with LinuxBIOS+FILO. -- Takeshi From itz at californiadigital.com Thu Apr 8 15:07:01 2004 From: itz at californiadigital.com (Ian Zimmerman) Date: Thu Apr 8 15:07:01 2004 Subject: clueless Message-ID: <877jwq2pie.fsf@californiadigital.com> I want to explore using LinuxBIOS with one of a few particular motherboards. But I don't really know where to start, despite the fact that the boards are listed on the Web site as working. This is because there are only 4 documents in the HOWTO directory explaining the details for 4 boards; what about the dozens of others? How do I know, for example, if I need the Disk On Chip? I am talking specifically about the Tyan Tiger MPX and its cousins. If there is a FAQ list likely to answer this (and other similarly clueless questions I'm sure will follow from me) I'll be grateful for a pointer. But nothing either in the distribution itself of on the official website qualifies, I am afraid. From mdeschamps at mangrove-systems.com Fri Apr 9 08:24:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Fri Apr 9 08:24:01 2004 Subject: VIA EPIA Build Error MAX_REBOOT_CT In-Reply-To: References: <1081441392.1299.71.camel@Calliphara> Message-ID: <1081517549.1299.110.camel@Calliphara> pffiu ...You were right it's not passed to gcc. You hold one Greg thanks you ! ... I saw that the target echo: and the make echo echoes every variables in makefile.settings (fallback's one) In makefile, there is D_item function that's called on each VARIABLES from included Makefile.settings. Theses calls are made by CPUFLAGS : it's empty whereas VARIABLES is containing MAX_REBOOT_CNT. In visu: Added in target echo: @echo CPUFLAGS='$(CPUFLAGS)' @echo VARIABLES='$(VARIABLES)' tried and as a result got this: CPUFLAGS= VARIABLES= ARCH CROSS_COMPILE CC ... ... MAX_REBOOT_CNT .... XIP_ROM_BASE XIP_ROM_SIZE er .. Well my makefile is corrumpt, buggy, or so ? I used LB 1.1.6 is it knowed to bug somehow like my problem ? On the "buggy side" here's what i've thought : It could be a D_item malfunction (but i can't point which one) or a bad call in CPUFLAGS (but i'am less confident in this way) There is the head -20 of it : ------------------------------------------ # File: via/epia/epia/fallback/Makefile # This file was generated by 'via/epia/epia/config.py via/epia/Config.lb /home/root/projet/freebios/freebios2' # Get the value of TOP, VARIABLES, and several other variables. include Makefile.settings # Function to create an item like -Di586 or -DCONFIG_MAX_CPUS='1' or -Ui686 D_item = $(if $(subst undefined,,$(origin $1)),-D$1$(if $($1),='$($1)',),-U$1) # Compute the value of CPUFLAGS here during make's first pass. CPUFLAGS := $(foreach _var_,$(VARIABLES),$(call D_item,$(_var_))) CPP:= $(CC) -no-gcc -x assembler-with-cpp -DASSEMBLY -E LIBGCC_FILE_NAME := $(shell $(CC) -print-libgcc-file-name) GCC_INC_DIR := $(shell $(CC) -print-search-dirs | sed -ne "s/install: \(.*\)/\1include/gp") CPPFLAGS := -I$(TOP)/src/include -I$(TOP)/src/arch/$(ARCH)/include -I$(GCC_INC_DIR) $(CPUFLAGS) ROMCCPPFLAGS := -D__ROMCC__=0 -D__ROMCC_MINOR__=38 CFLAGS := $(CPU_OPT) $(CPPFLAGS) -Os -nostdinc -nostdlib -fno-builtin -Wall HOSTCFLAGS:= -Os -Wall LINUXBIOS_PAYLOAD-$(CONFIG_COMPRESS):=linuxbios_payload.nrv2b --------------------------------------------- What do you think about this ? I also can't help recalling that this makefile has been built by buildtarget,could it be involved ? mathieu Le jeu 08/04/2004 ? 19:12, Greg Watson a ?crit : > Check the Makefile.settings in the fallback directory and see if > MAX_REBOOT_CNT is defined. If it isn't then there's some problem with > the configuration. If it is, then it's not getting passed to the gcc > command line. > > Greg > > On 08/04/2004, at 10:23 AM, Mathieu Deschamps wrote: > > > > > I'am building a new rom but now,I got stuck because of > > #error "MAX_REBOOT_CNT not defined" > > in make process of build target even though i defined this in Config.lb From mdeschamps at mangrove-systems.com Fri Apr 9 08:44:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Fri Apr 9 08:44:01 2004 Subject: LinuxBios "official" requirements. Message-ID: <1081518783.1299.128.camel@Calliphara> I've read several documentation on LinuxBios and related projects, though I didn't find out a LinuxBios requirements "true" paper. I still have the 2.4.xx kernel compiling oriented slab that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), Binutils 2.10, util-linux 2.10. Also I had a quite old python version (1.1 or so), i got it updated to 2.2.3 when I've seen the python script insulted me while running buildtarget. What are the "official" requirements ? What I try to say is that a REQUIEREMENTS file in the source tree LACKS, Maybe it lacks also in the site page (IMHO, the early page info should mention this)... cordialy, mathieu From YhLu at tyan.com Fri Apr 9 12:39:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 9 12:39:00 2004 Subject: Flash_rom Message-ID: <3174569B9743D511922F00A0C943142304B85F79@TYANWEB> Ollie, I checked the flash_rom, and find that you remove the code for check if the sector is really erased. Also I found the flash_rom can not work under 2.6.4.and 2.6.5 in x86_64 mode, and it seems only last 4k can not be erased. [0x7f000, 0x7ffff]. Regards YH From YhLu at tyan.com Fri Apr 9 14:56:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 9 14:56:00 2004 Subject: =?GB2312?B?tPC4tDogRmxhc2hfcm9t?= Message-ID: <3174569B9743D511922F00A0C943142304B85F9B@TYANWEB> Ollie, Only happens in s2885, it seems there is problem in AGP GART in 2.6.5, it reserve [4G-4k,4G). ???? Regards YH. -----????----- ???: YhLu ????: 2004?4?9? 10:58 ???: Li-Ta Lo ??: 'ron minnich'; 'linuxbios at clustermatic.org' ??: Flash_rom Ollie, I checked the flash_rom, and find that you remove the code for check if the sector is really erased. Also I found the flash_rom can not work under 2.6.4.and 2.6.5 in x86_64 mode, and it seems only last 4k can not be erased. [0x7f000, 0x7ffff]. Regards YH _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From YhLu at tyan.com Fri Apr 9 16:41:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 9 16:41:00 2004 Subject: =?GB2312?B?tPC4tDogRmxhc2hfcm9t?= Message-ID: <3174569B9743D511922F00A0C943142304B85FBA@TYANWEB> Ollie, The problem happens in all above 4G RAM installed and in 2.6.5. Regards YH -----????----- ???: YhLu ????: 2004?4?9? 13:15 ???: YhLu; Li-Ta Lo ??: 'ron minnich'; 'linuxbios at clustermatic.org' ??: ??: Flash_rom Ollie, Only happens in s2885, it seems there is problem in AGP GART in 2.6.5, it reserve [4G-4k,4G). ???? Regards YH. -----????----- ???: YhLu ????: 2004?4?9? 10:58 ???: Li-Ta Lo ??: 'ron minnich'; 'linuxbios at clustermatic.org' ??: Flash_rom Ollie, I checked the flash_rom, and find that you remove the code for check if the sector is really erased. Also I found the flash_rom can not work under 2.6.4.and 2.6.5 in x86_64 mode, and it seems only last 4k can not be erased. [0x7f000, 0x7ffff]. Regards YH _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From dwh at lanl.gov Fri Apr 9 17:32:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Fri Apr 9 17:32:00 2004 Subject: =?GB2312?B?tPC4tDogRmxhc2hfcm9t?= [PMX:#] In-Reply-To: <3174569B9743D511922F00A0C943142304B85FBA@TYANWEB> Message-ID: It looks like this error is not consistent. You can run flash_rom multiple times and it will eventually flash successfully using kernel 2.6.5 (Use the -v flag). Weird... On Fri, 9 Apr 2004, YhLu wrote: > Ollie, > > The problem happens in all above 4G RAM installed and in 2.6.5. > > Regards > > YH > > -----????????----- > ??????: YhLu > ????????: 2004??4??9?? 13:15 > ??????: YhLu; Li-Ta Lo > ????: 'ron minnich'; 'linuxbios at clustermatic.org' > ????: ????: Flash_rom > > Ollie, > > Only happens in s2885, it seems there is problem in AGP GART in 2.6.5, it > reserve [4G-4k,4G). ???? > > Regards > > YH. > > -----????????----- > ??????: YhLu > ????????: 2004??4??9?? 10:58 > ??????: Li-Ta Lo > ????: 'ron minnich'; 'linuxbios at clustermatic.org' > ????: Flash_rom > > Ollie, > > I checked the flash_rom, and find that you remove the code for check if the > sector is really erased. > > Also I found the flash_rom can not work under 2.6.4.and 2.6.5 in x86_64 > mode, and it seems only last 4k can not be erased. [0x7f000, 0x7ffff]. > > Regards > > YH > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Fri Apr 9 17:34:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 9 17:34:00 2004 Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IEZsYXNoX3JvbSBbUE1YOiNd?= Message-ID: <3174569B9743D511922F00A0C943142304B85FD3@TYANWEB> remove the code for check if the sector is really erased. ( compare if it is =0xff). And it is only last 4k. YH -----????----- ???: Hendricks David W. [mailto:dwh at lanl.gov] ????: 2004?4?9? 15:43 ???: YhLu ??: 'Li-Ta Lo'; 'ron minnich'; 'linuxbios at clustermatic.org' ??: Re: ????: Flash_rom [PMX:#] It looks like this error is not consistent. You can run flash_rom multiple times and it will eventually flash successfully using kernel 2.6.5 (Use the -v flag). Weird... On Fri, 9 Apr 2004, YhLu wrote: > Ollie, > > The problem happens in all above 4G RAM installed and in 2.6.5. > > Regards > > YH > > -----????????----- > ??????: YhLu > ????????: 2004??4??9?? 13:15 > ??????: YhLu; Li-Ta Lo > ????: 'ron minnich'; 'linuxbios at clustermatic.org' > ????: ????: Flash_rom > > Ollie, > > Only happens in s2885, it seems there is problem in AGP GART in 2.6.5, it > reserve [4G-4k,4G). ???? > > Regards > > YH. > > -----????????----- > ??????: YhLu > ????????: 2004??4??9?? 10:58 > ??????: Li-Ta Lo > ????: 'ron minnich'; 'linuxbios at clustermatic.org' > ????: Flash_rom > > Ollie, > > I checked the flash_rom, and find that you remove the code for check if the > sector is really erased. > > Also I found the flash_rom can not work under 2.6.4.and 2.6.5 in x86_64 > mode, and it seems only last 4k can not be erased. [0x7f000, 0x7ffff]. > > Regards > > YH > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Fri Apr 9 17:38:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 9 17:38:00 2004 Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IEZsYXNoX3JvbSBbUE1YOiNd?= Message-ID: <3174569B9743D511922F00A0C943142304B85FD4@TYANWEB> Actually, the last 4k is erased to 0xff. But the last 4k can not be read. Only get 0x00 back. YH -----????----- ???: Hendricks David W. [mailto:dwh at lanl.gov] ????: 2004?4?9? 15:43 ???: YhLu ??: 'Li-Ta Lo'; 'ron minnich'; 'linuxbios at clustermatic.org' ??: Re: ????: Flash_rom [PMX:#] It looks like this error is not consistent. You can run flash_rom multiple times and it will eventually flash successfully using kernel 2.6.5 (Use the -v flag). Weird... On Fri, 9 Apr 2004, YhLu wrote: > Ollie, > > The problem happens in all above 4G RAM installed and in 2.6.5. > > Regards > > YH > > -----????????----- > ??????: YhLu > ????????: 2004??4??9?? 13:15 > ??????: YhLu; Li-Ta Lo > ????: 'ron minnich'; 'linuxbios at clustermatic.org' > ????: ????: Flash_rom > > Ollie, > > Only happens in s2885, it seems there is problem in AGP GART in 2.6.5, it > reserve [4G-4k,4G). ???? > > Regards > > YH. > > -----????????----- > ??????: YhLu > ????????: 2004??4??9?? 10:58 > ??????: Li-Ta Lo > ????: 'ron minnich'; 'linuxbios at clustermatic.org' > ????: Flash_rom > > Ollie, > > I checked the flash_rom, and find that you remove the code for check if the > sector is really erased. > > Also I found the flash_rom can not work under 2.6.4.and 2.6.5 in x86_64 > mode, and it seems only last 4k can not be erased. [0x7f000, 0x7ffff]. > > Regards > > YH > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Sat Apr 10 00:19:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Sat Apr 10 00:19:01 2004 Subject: =?utf-8?B?562U5aSNOiDnrZQ/PzogRklMTyAwLjQgW1BNWDojXQ==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B85ED5@TYANWEB> Message-ID: On Thu, 8 Apr 2004, YhLu wrote: > So, if I can enable the ati rage xl in LinuxBIOS, I can substitute the > normal bios with LinuxBIOS. exactly. And we would have resolved one of the biggest issues people have with using linuxbios. ron From YhLu at tyan.com Sat Apr 10 01:06:01 2004 From: YhLu at tyan.com (YhLu) Date: Sat Apr 10 01:06:01 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogtPA/PzogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B85FF3@TYANWEB> I'm talking to ATI and try to get datasheet that has reg info in it. -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?9? 22:30 ???: YhLu ??: Takeshi Sone; ebiederman at lnxi.com; linuxbios at clustermatic.org ??: Re: ??: ???: FILO 0.4 [PMX:#] On Thu, 8 Apr 2004, YhLu wrote: > So, if I can enable the ati rage xl in LinuxBIOS, I can substitute the > normal bios with LinuxBIOS. exactly. And we would have resolved one of the biggest issues people have with using linuxbios. ron From rminnich at lanl.gov Sat Apr 10 11:30:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Sat Apr 10 11:30:00 2004 Subject: VIA EPIA Build Error MAX_REBOOT_CT In-Reply-To: <1081517549.1299.110.camel@Calliphara> Message-ID: On 9 Apr 2004, Mathieu Deschamps wrote: > # Function to create an item like -Di586 or -DCONFIG_MAX_CPUS='1' or -Ui686 > D_item = $(if $(subst undefined,,$(origin $1)),-D$1$(if > $($1),='$($1)',),-U$1) youch. I had not wanted to carry this to V2, how did it get in there? > > # Compute the value of CPUFLAGS here during make's first pass. > CPUFLAGS := $(foreach _var_,$(VARIABLES),$(call D_item,$(_var_))) Two pass makefiles? Calls to D_item? Calls to things in a makefile? Yikes, why not just get rid of makefiles and generate C programs? :-) We made a real effort with the new config tool to avoid this type of thing. This construct is very nonportable to other make systems and it measurably slows down the process of building. The first time I built a bios with the new config system it took < 10 seconds. It has gotten slower since then, not even accounting for romcc overhead. Plus, still worse, you can't just look at a makefile and see how variables are set. It's confusing. Another major goal of the new config tool was to enable people to just look at Makefile.settings and know exactly what the settings would be. This type of 'GNU make magic' removes our ability to meet that goal. It's a de-facto second or third pass on the config tool which is not visible to people. The final problem is that this can hide errors in Config.lb files, as we have seen. Rewriting variables in makefiles strikes me as a questionable way to proceed. Can someone point to a requirement that we have this in there? Why can't correctly structured config files remove the need for this macro? thanks ron From rminnich at lanl.gov Sun Apr 11 21:25:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 11 21:25:00 2004 Subject: epia-m Message-ID: OK, I have an 'emergency get it going' thing this week for epia-m. So anyone working with that thing please contact me and tell me how far you are with V1 and epia-m. thanks ron From rminnich at lanl.gov Sun Apr 11 21:29:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 11 21:29:00 2004 Subject: EPIA-M "Magic Potion"? In-Reply-To: <200403280455.i2S4t2RI009530@xdr.com> Message-ID: On Sat, 27 Mar 2004, Dave Ashley wrote: > Here's what I have. This can go after > mainboardinit southbridge/via/vt8235/setup_misc.inc > // enable VGA device > movl $CONFIG_ADDR(0, 0x00, 0xe1), %eax > movb $0xbd, %dl // enable vga with 8 megs > PCI_WRITE_CONFIG_BYTE This code is in there but set for 32M. > // The stupid firewire device (undocumented) steps on IO 0+ on reset > movl $CONFIG_ADDR(0, 0x0d*8, 0x15), %eax > movb $0x1c, %dl > PCI_WRITE_CONFIG_BYTE it seems to be in there. > > // use CMOS byte 0x0e as marker so we only reboot once >. >. >. this is in there too. ron From rminnich at lanl.gov Sun Apr 11 21:34:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 11 21:34:01 2004 Subject: EPIA-M "Magic Potion"? In-Reply-To: <00cb01c41539$f98245c0$0300a8c0@amr.corp.intel.com> Message-ID: On Sun, 28 Mar 2004, Dmitry Borisov wrote: > Ron, > FYI: I did some changes in hardwaremain.c to make sure splash is called > after VGA init and early enough to see the splash. > It may brake some other builds, unlikely though... IF my epia-m builds I will try all of this EXCEPT for the hardwaremain changes for now. I worry just a bit since those change the order of some operations. But I will try them later. ron From fedde at fedde.net Mon Apr 12 05:15:00 2004 From: fedde at fedde.net (fedde at fedde.net) Date: Mon Apr 12 05:15:00 2004 Subject: Via Epia V8000 bios Message-ID: <2313.212.125.245.19.1081765572.squirrel@webmail.fedde.net> Hi all! Fist of all i would say linuxbios looks like a great project, and now it can maby help me. I got a Via EPia V8000 @ 800mhz (http://www.viavpsd.com/product/epia_v_spec.jsp?motherboardId=141) that is strugeling abit. It appears the onboard 1.06 bios has problems with with wireless network cards that is made of atheros due the irq sharing on the pci slot that it's sharing with the usb that is not needed. The board is booting from a CF disk on the ide, so i would also like to know if it's possible to treat the ide controller as normal, so it's possible to change the CF with a hard drive later on? So, anybody wanna have a go creating bios for this board, or give me som guidelines on how to disable and creating the bios, but i got not too much experience with bios creation. Any help would be appriciated becouse i'm stuck with two of these boards that are unusable for me. Sincerly FredriK B From nacho at estudio-verona.com Mon Apr 12 06:45:00 2004 From: nacho at estudio-verona.com (Ignacio Verona) Date: Mon Apr 12 06:45:00 2004 Subject: Newbie with epia M-II Message-ID: <407A8413.6070203@estudio-verona.com> hi! This is my first post. I'm trying to develop my own Car PC and using LinuxBios I hope to get faster boot times. I'm using a Via EPIA M-II 10000. What are the first steps I should take? The epia bios is socketed on 32-lead PLCC format. What is the biggest rom size I could get? It is possible to use DOC on this motherboard (may be, I could fit a usable linux system on... less than 64mb). I've reading the list archive but I'm still a little lost. All help will be aprecciated. Thanks!! From gwatson at lanl.gov Mon Apr 12 07:28:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Mon Apr 12 07:28:01 2004 Subject: Newbie with epia M-II In-Reply-To: <407A8413.6070203@estudio-verona.com> References: <407A8413.6070203@estudio-verona.com> Message-ID: <6EAFCE3D-8C7E-11D8-8F75-000393A47A5C@lanl.gov> Not sure what the biggest PLCC is, but it's probably not much over 1MB. We use a 64MB IDE FLASH on some of our EPIA's which is easily big enough for a kernel and RAM disk. The nice thing about the IDE FLASH is that it can easily be replaced by a disk if you want. It seems the main difference between the EPIA and the EPIA-M (and possibly the EPIA-10000) is the type of RAM used (SDRAM/DDR). It's going to take some work to add DDR support to current EPIA image. Greg On 12/04/2004, at 5:57 AM, Ignacio Verona wrote: > hi! This is my first post. I'm trying to develop my own Car PC and > using LinuxBios I hope to get faster boot times. I'm using a Via EPIA > M-II 10000. What are the first steps I should take? The epia bios is > socketed on 32-lead PLCC format. What is the biggest rom size I could > get? It is possible to use DOC on this motherboard (may be, I could > fit a usable linux system on... less than 64mb). > > I've reading the list archive but I'm still a little lost. All help > will be aprecciated. Thanks!! > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From Antony at Soft-Solutions.co.uk Mon Apr 12 07:30:00 2004 From: Antony at Soft-Solutions.co.uk (Antony Stone) Date: Mon Apr 12 07:30:00 2004 Subject: Newbie with epia M-II In-Reply-To: <407A8413.6070203@estudio-verona.com> References: <407A8413.6070203@estudio-verona.com> Message-ID: <200404121340.49524.Antony@Soft-Solutions.co.uk> On Monday 12 April 2004 12:57 pm, Ignacio Verona wrote: > hi! This is my first post. I'm trying to develop my own Car PC and using > LinuxBios I hope to get faster boot times. I'm using a Via EPIA M-II > 10000. What are the first steps I should take? Search the archives to see if anyone else has built LinuxBIOS for that board; if not, check your chipset with lspci and see if someone has got that chipset working on a different board. > The epia bios is socketed on 32-lead PLCC format. What is the biggest rom > size I could get? It is possible to use DOC on this motherboard (may be, I > could fit a usable linux system on... less than 64mb). 64Mbytes for a usable Linux system is not a challenge. Rather than thinking of DoC, you'd be better of using Compact Flash. If your motherboard doesn't have a CF socket directly, you can use a simple (and cheap) CF-IDE adapter and put the CF where the HDD normally connects. Don't think that you have to put the entire Linux kernel into the chip in the BIOS socket - you don't. You just need a bootloader (that's essentially what LinuxBIOS is) in the BIOS chip, and that loads your kernel from wherever you want - CF is a good choice for this type of application, unless you want to store Gbytes of MP3s and have a hard drive anyway? Depends on what your car PC application / purpose is. Regards, Antony. -- These clients are often infected by viruses or other malware and need to be fixed. If not, the user at that client needs to be fixed... - Henrik Nordstrom, on Squid users' mailing list Please reply to the list; please don't CC me. From gwatson at lanl.gov Mon Apr 12 07:33:00 2004 From: gwatson at lanl.gov (Greg Watson) Date: Mon Apr 12 07:33:00 2004 Subject: LinuxBios "official" requirements. In-Reply-To: <1081518783.1299.128.camel@Calliphara> References: <1081518783.1299.128.camel@Calliphara> Message-ID: <3215C139-8C7F-11D8-8F75-000393A47A5C@lanl.gov> Yes, most of us are too busy getting LinuxBIOS working to spare the time to write much documentation. I can say that I've built most of the targets successfully using a stock RH9 (YD3.0.1 for PPC) machine. That's probably as good a base-line as any. Greg On 09/04/2004, at 7:53 AM, Mathieu Deschamps wrote: > I've read several documentation on LinuxBios and related > projects, though I didn't find out a LinuxBios requirements > "true" paper. I still have the 2.4.xx kernel compiling oriented slab > that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), > Binutils 2.10, util-linux 2.10. > > Also I had a quite old python version (1.1 or so), i got it updated > to 2.2.3 when I've seen the python script insulted me while running > buildtarget. > > > What are the "official" requirements ? > > What I try to say is that a REQUIEREMENTS file in the source tree > LACKS, > Maybe it lacks also in the site page (IMHO, the early page info should > mention this)... > > cordialy, > mathieu > > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From gwatson at lanl.gov Mon Apr 12 07:36:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Mon Apr 12 07:36:01 2004 Subject: LinuxBios and Openbios's dev/bios capacity In-Reply-To: <1081430628.1299.52.camel@Calliphara> References: <1081430628.1299.52.camel@Calliphara> Message-ID: <949CED28-8C7F-11D8-8F75-000393A47A5C@lanl.gov> This seems like an openbios issue to me. Greg On 08/04/2004, at 7:23 AM, Mathieu Deschamps wrote: > I've found in OpenBios dev/bios a good reason to hope i could spare > the > cost of a "physical" flashing device , and a ease using. That is to say > getting LinuxBios building the .bin and flash the onboard BIOS via the > dev/bios mechanism. > > I have a via/epia and a SST39 series 20A (256Ko) bios chip on > I'd thought I could read/write this bios with cat my.bin >/dev/bios > but by insmoding bios.o. But i got a kmess coming from lines 123-126 > printk code of bios.c > "BIOS : No flash devices found" > This resulting in a console message "Device busy" (that is, though, a > bit paradoxal notfound != busy isn't it ? :) ) > > I can't catch what have missed me... Is dev/bios couldn't be used in > my aim ? > > Gratefull if experienced people could help me. > Cordialy. > > Mathieu > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From gwatson at lanl.gov Mon Apr 12 07:43:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Mon Apr 12 07:43:01 2004 Subject: FILO 0.4 [PMX:#] In-Reply-To: <20040405124659.GA18106@openbios.org> References: <200404042057.i34Kv1Wk032339@mailproxy3.lanl.gov> <2F75B58F-8695-11D8-92F6-000393A47A5C@lanl.gov> <20040405124659.GA18106@openbios.org> Message-ID: <8D34DB23-8C80-11D8-8F75-000393A47A5C@lanl.gov> Stefan, I think this is a great idea. I'll talk it over with Ron and Ollie this week and look at how it might be implemented. Greg On 05/04/2004, at 6:46 AM, Stefan Reinauer wrote: > * Eric W. Biederman [040405 05:02]: >> If we want to take a snapshot of the source tree of FILO or any other >> bootloader into the LinuxBIOS tree under util. Build that part of the >> build and build a complete romimage that works. I am fine >> with that. It is even reasonable to make it so you can drop in >> external trees like etherboot and have everything build together >> nicely. >> >> Actual linking things together instead of including them together >> is unacceptable. > > What about the following: > > Currently LinuxBIOS divides into 2 fundamental parts: > > 1) hardware initialization > 2) getting and starting the payload > > This second part consists of two parts, again: > > i) elfloader > ii) payload > > Note, this is only one possible design. Maybe, this design is bloated > for some application cases. > > Eric, you want to make a hard cut between what is LinuxBIOS and what is > not. This is generally a good idea, as it keeps the different > initialization steps distinct from reach other. What, if we add another > cut by dividing hardware initialization frin the payload-loader? > > Instead of packing stuff like filo to util, we could do: > > * create a directory loader which can hold all "loaders" > * move the elf loader with a Config.lb to a subdirectory in there > * create other directories for other "loaders" like filo. > > If done right, filo can still be compiled as a payload, or built in if > the win in size is noticable. A target config file could probably > choose > which method to use, without overhead. Also, syncing with other trees, > like Takeshi's filo tree could be fairly easy, too. > > I don't think we really have a conflict in direction here at all. > LinuxBIOS itself should be as small as possible, and the different > parts > should be as independent as possible. But we also want to be a lot more > flexible than the existing solutions.. > >> In addition we have had way to many questions of what is the right >> policy for a bootloader to implement, on this list. I refuse >> to couple that to the LinuxBIOS core. And I don't want some stupid >> policy in there like FILO's that would require me to upgrade >> my firmware just to upgrade my OS. > > Please explain, how is filo worse here than putting linux in flash? > > > Stefan > From bari at onelabs.com Mon Apr 12 09:13:01 2004 From: bari at onelabs.com (Bari Ari) Date: Mon Apr 12 09:13:01 2004 Subject: XScale Port In-Reply-To: <3B1C9C2C-8C80-11D8-8F75-000393A47A5C@computer.org> References: <4074B4C9.9010700@onelabs.com> <3B1C9C2C-8C80-11D8-8F75-000393A47A5C@computer.org> Message-ID: <407AA6E7.5000305@onelabs.com> Greg Watson wrote: > I've only just embarked on the road to video for PPC. Currently I've > tried a Matrox board which works fine, mainly because it doesn't need Too bad Matrox doesn't sell chips anymore. > any BIOS support at all (nice). ATI is proving difficult for the x86 > people because of a lack of chipset information (not nice). I believe Looking into ATI as well since Richard is working with the M1. > they have nvidia working with the x86 emulator, so I'll be trying that > next. x86 emulator will probably be to ugly a path to use on an ARM platform. -Bari From vberdin at eazix.com Mon Apr 12 09:14:00 2004 From: vberdin at eazix.com (Vic Berdin) Date: Mon Apr 12 09:14:00 2004 Subject: Any possible updates for LinuxBIOS... Message-ID: ... supporting the AMD GX2 and CS5535 companion chip? just hoping, Vic --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.656 / Virus Database: 421 - Release Date: 4/9/2004 From rminnich at lanl.gov Mon Apr 12 09:33:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 12 09:33:00 2004 Subject: XScale Port In-Reply-To: <407AA6E7.5000305@onelabs.com> Message-ID: On Mon, 12 Apr 2004, Bari Ari wrote: > > they have nvidia working with the x86 emulator, so I'll be trying that > > next. > > x86 emulator will probably be to ugly a path to use on an ARM platform. I'm not sure I agree. I think it is doable. ron From rminnich at lanl.gov Mon Apr 12 09:33:20 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 12 09:33:20 2004 Subject: Any possible updates for LinuxBIOS... In-Reply-To: Message-ID: On Mon, 12 Apr 2004, Vic Berdin wrote: > > ... supporting the AMD GX2 and CS5535 companion chip? it's on the list ... ron From linuxbios at matter.net Mon Apr 12 11:37:00 2004 From: linuxbios at matter.net (Larry Matter) Date: Mon Apr 12 11:37:00 2004 Subject: Newbie with epia M-II In-Reply-To: <200404121340.49524.Antony@Soft-Solutions.co.uk> References: <407A8413.6070203@estudio-verona.com> <200404121340.49524.Antony@Soft-Solutions.co.uk> Message-ID: <2272.192.168.1.137.1081788498.squirrel@mail.matter.net> > On Monday 12 April 2004 12:57 pm, Ignacio Verona wrote: > >> hi! This is my first post. I'm trying to develop my own Car PC and using >> LinuxBios I hope to get faster boot times. I'm using a Via EPIA M-II >> 10000. What are the first steps I should take? > > Search the archives to see if anyone else has built LinuxBIOS for that > board; > if not, check your chipset with lspci and see if someone has got that > chipset > working on a different board. I also have an EPIA MII, though it is the fanless 6000. I have successfully installed LinuxBIOS and it is loading etherboot (verified by looking at the serial output and my dhcp server log). I'm currently stuck getting an etherboot image that works, but I'm sure I'll get past that soon. I basically followed the epia howto but used via/epia-m as the mainboard in my config file. I also used the exact version of etherboot as the howto even though there are much newer versions. >> The epia bios is socketed on 32-lead PLCC format. What is the biggest >> rom >> size I could get? It is possible to use DOC on this motherboard (may be, >> I >> could fit a usable linux system on... less than 64mb). > > 64Mbytes for a usable Linux system is not a challenge. > > Rather than thinking of DoC, you'd be better of using Compact Flash. If > your > motherboard doesn't have a CF socket directly, you can use a simple (and > cheap) CF-IDE adapter and put the CF where the HDD normally connects. The MII does come with an onboard CF slot (and pcmcia slot) but I believe it is connected via cardbus; it does not present itself as an ide device - standard bios cannot boot from it. You might be able to get that adapter working using yenta socket driver, etc., but it is probably a lot easier to get an CF-IDE adapter working first. You probably want to use FILO instead of etherboot too, but I'm not sure about that. I'm still very much a LinuxBIOS newbie too. Good Luck! And make sure you get a Bios Savior! Larry From ollie at lanl.gov Mon Apr 12 12:14:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Mon Apr 12 12:14:01 2004 Subject: Flash_rom In-Reply-To: <3174569B9743D511922F00A0C943142304B85F79@TYANWEB> References: <3174569B9743D511922F00A0C943142304B85F79@TYANWEB> Message-ID: <1081790765.2853.25.camel@exponential.lanl.gov> On Fri, 2004-04-09 at 11:57, YhLu wrote: > Ollie, > > I checked the flash_rom, and find that you remove the code for check if the > sector is really erased. > We had some problem about the erase/write check. It caused false alarm which means when it complained about a sector not erased, the sector is actually erased. If your want to ckech the programming, use the -v verify option. > Also I found the flash_rom can not work under 2.6.4.and 2.6.5 in x86_64 > mode, and it seems only last 4k can not be erased. [0x7f000, 0x7ffff]. > We tried flash_rom in 64bit kernel. But I don't know which version. David, can you answer this ? Ollie From gwatson at lanl.gov Mon Apr 12 13:31:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Mon Apr 12 13:31:01 2004 Subject: XScale Port In-Reply-To: References: Message-ID: <88EDF6F9-8CB0-11D8-8F75-000393A47A5C@lanl.gov> On 12/04/2004, at 8:44 AM, ron minnich wrote: > On Mon, 12 Apr 2004, Bari Ari wrote: > >>> they have nvidia working with the x86 emulator, so I'll be trying >>> that >>> next. >> >> x86 emulator will probably be to ugly a path to use on an ARM >> platform. > > I'm not sure I agree. > > I think it is doable. > > ron > > Yes, I think it will work with PPC. If it does then there's no reason it won't for the ARM. We should know soon :-) Greg From joshua at joshuawise.com Mon Apr 12 13:57:00 2004 From: joshua at joshuawise.com (Joshua Wise) Date: Mon Apr 12 13:57:00 2004 Subject: XScale Port In-Reply-To: References: Message-ID: <200404121508.16377.joshua@joshuawise.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 12 April 2004 10:44 am, ron minnich wrote: > > x86 emulator will probably be to ugly a path to use on an ARM platform. > I'm not sure I agree. > I think it is doable. Just remember that ARM is probably too slow to emulate x86 anywhere near as fast as you would like to run drivers. Also remember that XScale does not have floating point, so it's not really worth your while to put a 3D accel on an XScale system. FWIW, most XScale machines that I've seen use the "pxafb" - the internal LCD driver. For an alternative for LinuxBIOS that works on ARM systems, you might consider looking into the handhelds.org bootldr, or my LAB (Linux As Bootldr) code. If you have questions, ping me on IRC ... irc.freenode.net #handhelds.org (I'm joshua_.) > ron joshua - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAeukfPn9tWOqA4LMRAkvTAJ9OCvBDvvGjdED0ZAPBgNtz6VkNpgCbBCQ/ xndpbKC6F7QMuKbyUqcSeaQ= =AC3V -----END PGP SIGNATURE----- From rminnich at lanl.gov Mon Apr 12 14:06:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 12 14:06:01 2004 Subject: XScale Port In-Reply-To: <200404121508.16377.joshua@joshuawise.com> Message-ID: On Mon, 12 Apr 2004, Joshua Wise wrote: > Just remember that ARM is probably too slow to emulate x86 anywhere near as > fast as you would like to run drivers. maybe. I want to see it run. Those VGA BIOSes run in 8086 mode, remember, and boy are they slow. ron From joshua at joshuawise.com Mon Apr 12 14:17:01 2004 From: joshua at joshuawise.com (Joshua Wise) Date: Mon Apr 12 14:17:01 2004 Subject: XScale Port In-Reply-To: References: Message-ID: <200404121528.36878.joshua@joshuawise.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > maybe. I want to see it run. Those VGA BIOSes run in 8086 mode, remember, > and boy are they slow. Not just any 8086s, though... 3.0ghz 8086s :) I can see running an old ISA vga card, maybe a PCI crapcard, but not a 3d accel. On the flip side, you could just log bus accesses and cache it all, saving you the effort of emulating the BIOS all over again... then if something is not what you expect, you just start emulating the VGA bios. (Although I suppose the best thing to do would really just be to get the specs from the hardware manufacturer, or to disassemble the VGA bios and reimplement it in C!) > ron - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAeu3kPn9tWOqA4LMRArUTAJ0WCEponmxir7IxIV/z5os42egO0gCeKztw lhYnocfOuqFbWIsuc9whhVI= =01Ak -----END PGP SIGNATURE----- From nacho at estudio-verona.com Mon Apr 12 14:28:00 2004 From: nacho at estudio-verona.com (Ignacio Verona) Date: Mon Apr 12 14:28:00 2004 Subject: Newbie with epia M-II In-Reply-To: <2272.192.168.1.137.1081788498.squirrel@mail.matter.net> References: <407A8413.6070203@estudio-verona.com> <200404121340.49524.Antony@Soft-Solutions.co.uk> <2272.192.168.1.137.1081788498.squirrel@mail.matter.net> Message-ID: <1081806009.2736.1.camel@GranMarmota> > I basically followed the epia howto but used via/epia-m as the mainboard > in my config file. I also used the exact version of etherboot as the > howto even though there are much newer versions. Where is the howto? I've googled but haven't found anything on "linuxbios epia howto". Thanks!! From bari at onelabs.com Mon Apr 12 15:50:01 2004 From: bari at onelabs.com (Bari Ari) Date: Mon Apr 12 15:50:01 2004 Subject: XScale Port In-Reply-To: <200404121508.16377.joshua@joshuawise.com> References: <200404121508.16377.joshua@joshuawise.com> Message-ID: <407B0327.9090906@onelabs.com> Joshua Wise wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 12 April 2004 10:44 am, ron minnich wrote: > >>>x86 emulator will probably be to ugly a path to use on an ARM platform. >> >>I'm not sure I agree. >>I think it is doable. > > Just remember that ARM is probably too slow to emulate x86 anywhere near as > fast as you would like to run drivers. Also remember that XScale does not > have floating point, so it's not really worth your while to put a 3D accel on > an XScale system. FWIW, most XScale machines that I've seen use the "pxafb" - > the internal LCD driver. I can't say much, but we need and use the 3-D graphics. > > For an alternative for LinuxBIOS that works on ARM systems, you might consider > looking into the handhelds.org bootldr, or my LAB (Linux As Bootldr) code. If > you have questions, ping me on IRC ... irc.freenode.net #handhelds.org (I'm > joshua_.) We could just run Angel, U-Boot or Redboot but we would like LinuxBIOS since there are PC type peripherals on-board, PCI bridges, southbridges, audio accelerators etc (theswe are not weenie PDA boards). We may have 8-16 cpu's on PCI-X 64b/133. Areas where LinuxBIOS beats the pants off the other bootloaders. -Bari From YhLu at tyan.com Mon Apr 12 16:04:00 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 12 16:04:00 2004 Subject: ATI rage xl.init Message-ID: <3174569B9743D511922F00A0C943142304B86080@TYANWEB> Stefan, I move the kernel patch that init rage xl for fb into LinuxBIOS. You can disable the patch in Kernel and still can use rage xl for fb. Regards YH -------------- next part -------------- A non-text attachment was scrubbed... Name: ati_ragexl.tar.bz2 Type: application/octet-stream Size: 16664 bytes Desc: not available URL: From nacho at estudio-verona.com Mon Apr 12 16:30:01 2004 From: nacho at estudio-verona.com (Ignacio Verona) Date: Mon Apr 12 16:30:01 2004 Subject: Newbie with epia M-II In-Reply-To: <1081806009.2736.1.camel@GranMarmota> References: <407A8413.6070203@estudio-verona.com> <200404121340.49524.Antony@Soft-Solutions.co.uk> <2272.192.168.1.137.1081788498.squirrel@mail.matter.net> <1081806009.2736.1.camel@GranMarmota> Message-ID: <1081813297.2731.12.camel@GranMarmota> I've another question. LinuxBios "loads" a normal kernel? So I'll be able to use mpeg accel. on my MB if it's supported? My main goal is to get as fast as possible boot times. Thanks! From nacho at estudio-verona.com Mon Apr 12 16:37:00 2004 From: nacho at estudio-verona.com (Ignacio Verona) Date: Mon Apr 12 16:37:00 2004 Subject: Which Bios-Savior for 32-lead PLCC bios? In-Reply-To: <200404121528.36878.joshua@joshuawise.com> References: <200404121528.36878.joshua@joshuawise.com> Message-ID: <1081813737.2735.17.camel@GranMarmota> Hi! I'm just starting with LinuxBios, and want to buy a Bios-Savior (for my first steps). I'm developing for a Via Epia MII which has a 32-lead plcc (a square with 8 lead by each side) SST-39SF020A flash. What model should I buy for this? Thanks! From ollie at lanl.gov Mon Apr 12 17:35:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Mon Apr 12 17:35:00 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= =?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= Flash_rom [PMX:#] In-Reply-To: <3174569B9743D511922F00A0C943142304B85FD4@TYANWEB> References: <3174569B9743D511922F00A0C943142304B85FD4@TYANWEB> Message-ID: <1081810009.2853.29.camel@exponential.lanl.gov> On Fri, 2004-04-09 at 16:56, YhLu wrote: > Actually, the last 4k is erased to 0xff. > > But the last 4k can not be read. Only get 0x00 back. > We don't have any of your problems here except for the old 49lf040 stability issue. We tried with systems with more than 4GB of ram. Ollie From joshua at joshuawise.com Mon Apr 12 17:39:00 2004 From: joshua at joshuawise.com (Joshua Wise) Date: Mon Apr 12 17:39:00 2004 Subject: XScale Port In-Reply-To: <407B0327.9090906@onelabs.com> References: <200404121508.16377.joshua@joshuawise.com> <407B0327.9090906@onelabs.com> Message-ID: <200404121850.42387.joshua@joshuawise.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I can't say much, but we need and use the 3-D graphics. Well, good luck with your floating point on XScale :) > We could just run Angel, U-Boot or Redboot but we would like LinuxBIOS > since there are PC type peripherals on-board, PCI bridges, southbridges, > audio accelerators etc (theswe are not weenie PDA boards). We may have > 8-16 cpu's on PCI-X 64b/133. Areas where LinuxBIOS beats the pants off > the other bootloaders. Hmm... Sounds like an xscale (or other SoC) is not a great fit for this, but I assume you know best :) Sorry I couldn't help more. > -Bari j - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAex1BPn9tWOqA4LMRAoU9AJ9uJqfHDztI5z8NfbT+JNOtQH3DuACdFZUC pVQo14fzop8HrZpyB51jleg= =Olei -----END PGP SIGNATURE----- From ebiederman at lnxi.com Mon Apr 12 18:46:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 12 18:46:00 2004 Subject: 2.6 kernel In-Reply-To: <20040412230853.GA38378@lnxi.com> References: <20040412230853.GA38378@lnxi.com> Message-ID: Greg Lewis writes: > Hi Eric, > > We're having a look at 2.6 kernels again. Just curious if you have ever > gotten any of the 2.6 kernels up and playing nice with etherboot and > mkelfimage. If so, I'd be interested in what versions of each you were > using :). Also, do we have a general method of verifying the validity of > an EBi other than booting a node with it? Thanks. Yes. I have had reports of people having problems but nothing confirmed. I looked into it a while ago and I got it to work so I don't know how to pursue further complaints. mkelfImage 2.5 linux kernel 2.6.5rc3 (Which was the latest at the time I looked). etherboot 5.2.2eb2 (The patches were to my build configuration) Hmm. Make certain you have a known working binary version of mkelfImage. A 2.4 kernel can verify that. You can look at the ELF sections and suck out the compress kernel portion at 1MB. After accounting for the 16bit real mode section you can do a binary compare of the kernel pieces. There is the checksum which can be verified. I believe FILO has a tool to verify that. I know it has a tool that will write it in user space. You can boot the kernel in another manner and see if that works. Eric From ebiederman at lnxi.com Mon Apr 12 19:16:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 12 19:16:01 2004 Subject: ATI rage xl.init In-Reply-To: <3174569B9743D511922F00A0C943142304B86080@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86080@TYANWEB> Message-ID: YhLu writes: > Stefan, > > I move the kernel patch that init rage xl for fb into LinuxBIOS. You can > disable the patch in Kernel and still can use rage xl for fb. Cool. I have been meaning to try that for a long time I just have not been able to find the time. Unless we see some serious problems this looks like a good model for how to handle onboard graphics chips. Eric From YhLu at tyan.com Mon Apr 12 19:33:00 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 12 19:33:00 2004 Subject: =?GB2312?B?tPC4tDogRklMTyAwLjQgW1BNWDojXQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B860F8@TYANWEB> I just find the fifo can boot the elfimage in the rom. If the etherboot is put in the beginning, Use boot:mem at 0xfff80000 can load the Etherboot. Great... YH -----????----- ???: Greg Watson [mailto:gwatson at lanl.gov] ????: 2004?4?12? 5:55 ???: Stefan Reinauer ??: linuxbios at clustermatic.org ??: Re: FILO 0.4 [PMX:#] Stefan, I think this is a great idea. I'll talk it over with Ron and Ollie this week and look at how it might be implemented. Greg On 05/04/2004, at 6:46 AM, Stefan Reinauer wrote: > * Eric W. Biederman [040405 05:02]: >> If we want to take a snapshot of the source tree of FILO or any other >> bootloader into the LinuxBIOS tree under util. Build that part of the >> build and build a complete romimage that works. I am fine >> with that. It is even reasonable to make it so you can drop in >> external trees like etherboot and have everything build together >> nicely. >> >> Actual linking things together instead of including them together >> is unacceptable. > > What about the following: > > Currently LinuxBIOS divides into 2 fundamental parts: > > 1) hardware initialization > 2) getting and starting the payload > > This second part consists of two parts, again: > > i) elfloader > ii) payload > > Note, this is only one possible design. Maybe, this design is bloated > for some application cases. > > Eric, you want to make a hard cut between what is LinuxBIOS and what is > not. This is generally a good idea, as it keeps the different > initialization steps distinct from reach other. What, if we add another > cut by dividing hardware initialization frin the payload-loader? > > Instead of packing stuff like filo to util, we could do: > > * create a directory loader which can hold all "loaders" > * move the elf loader with a Config.lb to a subdirectory in there > * create other directories for other "loaders" like filo. > > If done right, filo can still be compiled as a payload, or built in if > the win in size is noticable. A target config file could probably > choose > which method to use, without overhead. Also, syncing with other trees, > like Takeshi's filo tree could be fairly easy, too. > > I don't think we really have a conflict in direction here at all. > LinuxBIOS itself should be as small as possible, and the different > parts > should be as independent as possible. But we also want to be a lot more > flexible than the existing solutions.. > >> In addition we have had way to many questions of what is the right >> policy for a bootloader to implement, on this list. I refuse >> to couple that to the LinuxBIOS core. And I don't want some stupid >> policy in there like FILO's that would require me to upgrade >> my firmware just to upgrade my OS. > > Please explain, how is filo worse here than putting linux in flash? > > > Stefan > _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From hansolofalcon at worldnet.att.net Mon Apr 12 20:08:00 2004 From: hansolofalcon at worldnet.att.net (Gregg C Levine) Date: Mon Apr 12 20:08:00 2004 Subject: ATI rage xl.init In-Reply-To: Message-ID: <000801c420f5$754be140$6401a8c0@who5> Hello from Gregg C Levine It happens that I can use the frame buffer functions on my ATI Rage 128 without much of a hassle. In fact that's the native mode of the video card. (And this is on a native BIOS, not the subject of the group.) Without breaking your NDA, could you enlighten the group regarding how you are going about the enabling of this ATI card? And where did you find the details for the frame buffer modes for this ATI video card? Were they provided that way? If so, then I don't need to know. ------------------- Gregg C Levine hansolofalcon at worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."? Obi-Wan Kenobi > -----Original Message----- > From: linuxbios-admin at clustermatic.org [mailto:linuxbios- > admin at clustermatic.org] On Behalf Of Eric W. Biederman > Sent: Monday, April 12, 2004 8:29 PM > To: YhLu > Cc: ron minnich; Stefan Reinauer; Takeshi Sone; linuxbios at clustermatic.org > Subject: Re: ATI rage xl.init > > YhLu writes: > > > Stefan, > > > > I move the kernel patch that init rage xl for fb into LinuxBIOS. You can > > disable the patch in Kernel and still can use rage xl for fb. > > Cool. I have been meaning to try that for a long time I just have > not been able to find the time. > > Unless we see some serious problems this looks like a good model for > how to handle onboard graphics chips. > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From YhLu at tyan.com Mon Apr 12 20:24:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 12 20:24:01 2004 Subject: =?utf-8?B?562U5aSNOiBBVEkgcmFnZSB4bC5pbml0?= Message-ID: <3174569B9743D511922F00A0C943142304B8610B@TYANWEB> The patch origninally is for kernel 2.4.21. Stefan sent that to me. It is developed by SGI??? And it is under GPL I have tried to move that to 2.6. and it works. I'm talking to ATI, and try to get more data sheet and then We can get the output from beginning in LinuxBIOS. ( It's not very begninnig, should in PCI init stage). Regards YH -----????----- ???: Gregg C Levine [mailto:hansolofalcon at worldnet.att.net] ????: 2004?4?12? 18:20 ???: Linuxbios ??: RE: ATI rage xl.init Hello from Gregg C Levine It happens that I can use the frame buffer functions on my ATI Rage 128 without much of a hassle. In fact that's the native mode of the video card. (And this is on a native BIOS, not the subject of the group.) Without breaking your NDA, could you enlighten the group regarding how you are going about the enabling of this ATI card? And where did you find the details for the frame buffer modes for this ATI video card? Were they provided that way? If so, then I don't need to know. ------------------- Gregg C Levine hansolofalcon at worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."? Obi-Wan Kenobi > -----Original Message----- > From: linuxbios-admin at clustermatic.org [mailto:linuxbios- > admin at clustermatic.org] On Behalf Of Eric W. Biederman > Sent: Monday, April 12, 2004 8:29 PM > To: YhLu > Cc: ron minnich; Stefan Reinauer; Takeshi Sone; linuxbios at clustermatic.org > Subject: Re: ATI rage xl.init > > YhLu writes: > > > Stefan, > > > > I move the kernel patch that init rage xl for fb into LinuxBIOS. You can > > disable the patch in Kernel and still can use rage xl for fb. > > Cool. I have been meaning to try that for a long time I just have > not been able to find the time. > > Unless we see some serious problems this looks like a good model for > how to handle onboard graphics chips. > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Mon Apr 12 21:06:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 12 21:06:01 2004 Subject: XScale Port In-Reply-To: <200404121528.36878.joshua@joshuawise.com> Message-ID: On Mon, 12 Apr 2004, Joshua Wise wrote: > Not just any 8086s, though... 3.0ghz 8086s :) Actually they seem to be timing-compatible, so I'm not sure they are 3 Ghz 8086s. > just log bus accesses and cache it all, saving you the effort of emulating > the BIOS all over again... You would think that might work. It doesn't. :-( > start emulating the VGA bios. (Although I suppose the best thing to do would > really just be to get the specs from the hardware manufacturer, or to > disassemble the VGA bios and reimplement it in C!) - get specs: impossible - disassemble and rewrite in C: get sued. we've been through this discussion before. I used to be on the "we'll get specs" side of this argument. For the most part, I was wrong. So I am now, with regret, on the emulation side. ron From rminnich at lanl.gov Mon Apr 12 21:20:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 12 21:20:01 2004 Subject: ATI rage xl.init In-Reply-To: Message-ID: On 12 Apr 2004, Eric W. Biederman wrote: > Unless we see some serious problems this looks like a good model for > how to handle onboard graphics chips. > I agree I like this too, however, it still does not solve things like the nvidia cards. ron From bari at onelabs.com Mon Apr 12 21:30:00 2004 From: bari at onelabs.com (Bari Ari) Date: Mon Apr 12 21:30:00 2004 Subject: XScale Port In-Reply-To: <200404121850.42387.joshua@joshuawise.com> References: <200404121508.16377.joshua@joshuawise.com> <407B0327.9090906@onelabs.com> <200404121850.42387.joshua@joshuawise.com> Message-ID: <407B531F.2060603@onelabs.com> Joshua Wise wrote: > Well, good luck with your floating point on XScale :) The non-blab order was lifted today by Intel on a few new parts. Take another look some new PCA XScale parts. -Bari From mdeschamps at mangrove-systems.com Tue Apr 13 02:30:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Tue Apr 13 02:30:01 2004 Subject: LinuxBios and Openbios's dev/bios capacity In-Reply-To: <949CED28-8C7F-11D8-8F75-000393A47A5C@lanl.gov> References: <1081430628.1299.52.camel@Calliphara> <949CED28-8C7F-11D8-8F75-000393A47A5C@lanl.gov> Message-ID: <1081841986.1299.147.camel@Calliphara> err :) well that's true ... I hope to have some help ... Up to a point theses projects are so close and so complementar, I'd bet some LinuxBios people would have resolve this "elementary" but annoying problem. More over, I saw that Stefan Reinauer posts from times to times answer on this mailing list... thanks whatever... Le lun 12/04/2004 ? 14:47, Greg Watson a ?crit : > This seems like an openbios issue to me. > > Greg > > On 08/04/2004, at 7:23 AM, Mathieu Deschamps wrote: > > > I've found in OpenBios dev/bios a good reason to hope i could spare > > the > > cost of a "physical" flashing device , and a ease using. That is to say > > getting LinuxBios building the .bin and flash the onboard BIOS via the > > dev/bios mechanism. > > > > I have a via/epia and a SST39 series 20A (256Ko) bios chip on > > I'd thought I could read/write this bios with cat my.bin >/dev/bios > > but by insmoding bios.o. But i got a kmess coming from lines 123-126 > > printk code of bios.c > > "BIOS : No flash devices found" > > This resulting in a console message "Device busy" (that is, though, a > > bit paradoxal notfound != busy isn't it ? :) ) > > > > I can't catch what have missed me... Is dev/bios couldn't be used in > > my aim ? > > > > Gratefull if experienced people could help me. > > Cordialy. > > > > Mathieu > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > > From mdeschamps at mangrove-systems.com Tue Apr 13 03:19:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Tue Apr 13 03:19:00 2004 Subject: LinuxBios "official" requirements. In-Reply-To: <3215C139-8C7F-11D8-8F75-000393A47A5C@lanl.gov> References: <1081518783.1299.128.camel@Calliphara> <3215C139-8C7F-11D8-8F75-000393A47A5C@lanl.gov> Message-ID: <1081844909.1299.197.camel@Calliphara> Hum ... under certains "embedded conditions" redhat is somewhat heavy to "handle"... ... anyway Linuxbios aims to work on various hardware device (provided that we make it work :) so it is on various linux distribution, isn't it so ? if not, IMHO, it should be :) And more over, seriously, it will gain even more credibility if it's proven to work on other distrib. It is again the same crosspoint : portability on every layer, down from hardware conformance and standards, up to software versions and "use conventions". Enough bla-bla'ing, as soon as I got it compiled and proven work on my SuSE 6.2 modified (from tail to head), I post the enumeration soft-components, I'am sure it will be appreciated. mathieu Le lun 12/04/2004 ? 14:44, Greg Watson a ?crit : > Yes, most of us are too busy getting LinuxBIOS working to spare the > time to write much documentation. I can say that I've built most of the > targets successfully using a stock RH9 (YD3.0.1 for PPC) machine. > That's probably as good a base-line as any. > > Greg > > On 09/04/2004, at 7:53 AM, Mathieu Deschamps wrote: > > > I've read several documentation on LinuxBios and related > > projects, though I didn't find out a LinuxBios requirements > > "true" paper. I still have the 2.4.xx kernel compiling oriented slab > > that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), > > Binutils 2.10, util-linux 2.10. > > > > Also I had a quite old python version (1.1 or so), i got it updated > > to 2.2.3 when I've seen the python script insulted me while running > > buildtarget. > > > > > > What are the "official" requirements ? > > > > What I try to say is that a REQUIEREMENTS file in the source tree > > LACKS, > > Maybe it lacks also in the site page (IMHO, the early page info should > > mention this)... > > > > cordialy, > > mathieu > > > > > > > > > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > > From stepan at openbios.org Tue Apr 13 07:10:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Apr 13 07:10:01 2004 Subject: ATI rage xl.init In-Reply-To: <3174569B9743D511922F00A0C943142304B86080@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86080@TYANWEB> Message-ID: <20040413122142.GA8032@openbios.org> * YhLu [040412 23:23]: > I move the kernel patch that init rage xl for fb into LinuxBIOS. You can > disable the patch in Kernel and still can use rage xl for fb. wonderful! I've commited this to the V2 CVS and moved the Trident Blade3d driver there as well. I changed the directory layout a little bit to suit northbridge/southbridge/mainboard by using driver/vendor/device as the path to the device init code. What is the right way of getting this code into a LinuxBIOS build? Should there be some "driver" directive like there's "northbridge" and "southbridge"? Or is there some better idea? If we can now get hands on loading firmware into the LSI1020/1030, we'd be prepared for a lot of nice opteron servers and possibly many others. Stefan From ebiederman at lnxi.com Tue Apr 13 07:27:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Apr 13 07:27:00 2004 Subject: ATI rage xl.init In-Reply-To: <20040413122142.GA8032@openbios.org> References: <3174569B9743D511922F00A0C943142304B86080@TYANWEB> <20040413122142.GA8032@openbios.org> Message-ID: Stefan Reinauer writes: > * YhLu [040412 23:23]: > > I move the kernel patch that init rage xl for fb into LinuxBIOS. You can > > disable the patch in Kernel and still can use rage xl for fb. > > wonderful! I've commited this to the V2 CVS and moved the Trident > Blade3d driver there as well. I changed the directory layout a little > bit to suit northbridge/southbridge/mainboard by using > driver/vendor/device as the path to the device init code. > > What is the right way of getting this code into a LinuxBIOS build? > Should there be some "driver" directive like there's "northbridge" and > "southbridge"? Or is there some better idea? Use the dir command. northbridge/southbridge/etc are just specializations of it. > If we can now get hands on loading firmware into the LSI1020/1030, we'd > be prepared for a lot of nice opteron servers and possibly many others. The Linux driver does not load the firmware? Or do we need SCSI support? Eric From stepan at openbios.org Tue Apr 13 07:53:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Apr 13 07:53:00 2004 Subject: ATI rage xl.init In-Reply-To: References: <3174569B9743D511922F00A0C943142304B86080@TYANWEB> <20040413122142.GA8032@openbios.org> Message-ID: <20040413130531.GA9758@openbios.org> * Eric W. Biederman [040413 14:40]: > > What is the right way of getting this code into a LinuxBIOS build? > > Should there be some "driver" directive like there's "northbridge" and > > "southbridge"? Or is there some better idea? > Use the dir command. northbridge/southbridge/etc are just specializations > of it. Ah, right! > > If we can now get hands on loading firmware into the LSI1020/1030, we'd > > be prepared for a lot of nice opteron servers and possibly many others. > > The Linux driver does not load the firmware? Or do we need SCSI support? The Linux driver does not load the firmware at the moment. The Linux driver just bails out without being able to load anything from disk. Otoh, it's kind of crucial to boot off SCSI drives in future. Since the LSI10[2|3]0 is pretty wide spread among opteron systems, it would give us a pretty good start. Stefan From stepan at openbios.org Tue Apr 13 07:58:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Apr 13 07:58:00 2004 Subject: LinuxBios and Openbios's dev/bios capacity In-Reply-To: <1081430628.1299.52.camel@Calliphara> References: <1081430628.1299.52.camel@Calliphara> Message-ID: <20040413131033.GB9758@openbios.org> Hi, * Mathieu Deschamps [040408 15:23]: > I've found in OpenBios dev/bios a good reason to hope i could spare the > cost of a "physical" flashing device , and a ease using. That is to say > getting LinuxBios building the .bin and flash the onboard BIOS via the > dev/bios mechanism. I've been updating whole clusters in basically no time using /dev/bios, but it has no proper error recovery nor does it work with recent kernels (2.6) yet. The existing code should definitely be integrated into the MTD (memory technology devices) code in the Linux kernel, or into the userspace flash utilities available in LinuxBIOS. > I have a via/epia and a SST39 series 20A (256Ko) bios chip on > I'd thought I could read/write this bios with cat my.bin >/dev/bios > but by insmoding bios.o. But i got a kmess coming from lines 123-126 > printk code of bios.c > "BIOS : No flash devices found" > This resulting in a console message "Device busy" (that is, though, a > bit paradoxal notfound != busy isn't it ? :) ) Can you send an lspci and lspci -n output? The error messages were kind of randomly chosen, just to keep the driver from loading if no flash devices are available. > I can't catch what have missed me... Is dev/bios couldn't be used in > my aim ? It is, it's just kind of an abandoned project, since it does not really fit well to today's needs in flexibility and code reuse. Any patches, hints, ideas are of course welcome. Stefan From gwatson at lanl.gov Tue Apr 13 08:26:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Tue Apr 13 08:26:01 2004 Subject: LinuxBios "official" requirements. In-Reply-To: <1081844909.1299.197.camel@Calliphara> References: <1081518783.1299.128.camel@Calliphara> <3215C139-8C7F-11D8-8F75-000393A47A5C@lanl.gov> <1081844909.1299.197.camel@Calliphara> Message-ID: Mathieu, I think you misunderstood. I wasn't implying RH9 as the "default distribution" for LinuxBIOS. I was simply suggesting that the development tools (gcc, libc, python, etc.) that are supplied with RH9 are a good approximation of the versions required to guarantee a successful build. Greg On 13/04/2004, at 2:28 AM, Mathieu Deschamps wrote: > Hum ... under certains "embedded conditions" redhat is somewhat heavy > to "handle"... ... anyway Linuxbios aims to work on various hardware > device (provided that we make it work :) so it is on various linux > distribution, isn't it so ? if not, IMHO, it should be :) > > And more over, seriously, it will gain even more credibility if it's > proven to work on other distrib. > It is again the same crosspoint : portability on every layer, down > from > hardware conformance and standards, up to software versions and "use > conventions". > > Enough bla-bla'ing, as soon as I got it compiled and proven work on > my > SuSE 6.2 modified (from tail to head), I post the enumeration > soft-components, I'am sure it will be appreciated. > > mathieu > > > Le lun 12/04/2004 ? 14:44, Greg Watson a ?crit : >> Yes, most of us are too busy getting LinuxBIOS working to spare the >> time to write much documentation. I can say that I've built most of >> the >> targets successfully using a stock RH9 (YD3.0.1 for PPC) machine. >> That's probably as good a base-line as any. >> >> Greg >> >> On 09/04/2004, at 7:53 AM, Mathieu Deschamps wrote: >> >>> I've read several documentation on LinuxBios and related >>> projects, though I didn't find out a LinuxBios requirements >>> "true" paper. I still have the 2.4.xx kernel compiling oriented slab >>> that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), >>> Binutils 2.10, util-linux 2.10. >>> >>> Also I had a quite old python version (1.1 or so), i got it updated >>> to 2.2.3 when I've seen the python script insulted me while running >>> buildtarget. >>> >>> >>> What are the "official" requirements ? >>> >>> What I try to say is that a REQUIEREMENTS file in the source tree >>> LACKS, >>> Maybe it lacks also in the site page (IMHO, the early page info >>> should >>> mention this)... >>> >>> cordialy, >>> mathieu >>> >>> >>> >>> >>> _______________________________________________ >>> Linuxbios mailing list >>> Linuxbios at clustermatic.org >>> http://www.clustermatic.org/mailman/listinfo/linuxbios >>> >> >> > From stepan at openbios.org Tue Apr 13 08:36:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Apr 13 08:36:01 2004 Subject: LinuxBios "official" requirements. In-Reply-To: <1081518783.1299.128.camel@Calliphara> References: <1081518783.1299.128.camel@Calliphara> Message-ID: <20040413134754.GA10961@openbios.org> * Mathieu Deschamps [040409 15:53]: > I've read several documentation on LinuxBios and related > projects, though I didn't find out a LinuxBios requirements > "true" paper. I still have the 2.4.xx kernel compiling oriented slab > that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), > Binutils 2.10, util-linux 2.10. egcs is pretty much outdated. I've been using: make-3.80-179 gcc-3.3.3-33 binutils-2.15.90.0.1.1-30 util-linux-2.12-59 python-2.3.3-65 > Also I had a quite old python version (1.1 or so), i got it updated > to 2.2.3 when I've seen the python script insulted me while running > buildtarget. Anything older than 2.1 won't work. > What I try to say is that a REQUIEREMENTS file in the source tree LACKS, > Maybe it lacks also in the site page (IMHO, the early page info should > mention this)... Maybe it would make sense to enhance the available LinuxBIOS on AMD64 document (freebios2/documentation/LinuxBIOS-AMD64.pdf) to contain information about the other ports as well. LinuxBIOS v2 does a great job unifying things. Stefan From rminnich at lanl.gov Tue Apr 13 08:48:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 08:48:01 2004 Subject: LinuxBios and Openbios's dev/bios capacity In-Reply-To: <1081841986.1299.147.camel@Calliphara> Message-ID: On 13 Apr 2004, Mathieu Deschamps wrote: > err :) well that's true ... I hope to have some help ... it's a harder problem than it sounds. Did you try linuxbios flash_rom utility? I agree it is elementary, and it is annoying, it's just that there are so many combinations of hardware out there that no one system supports them all. ron From rminnich at lanl.gov Tue Apr 13 08:53:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 08:53:01 2004 Subject: ATI rage xl.init In-Reply-To: <20040413122142.GA8032@openbios.org> Message-ID: On Tue, 13 Apr 2004, Stefan Reinauer wrote: > What is the right way of getting this code into a LinuxBIOS build? > Should there be some "driver" directive like there's "northbridge" and > "southbridge"? Or is there some better idea? Driver sounds ok to me. This would get the driver into the static device tree. The convention could be that drivers are called with the same passes that any other static device is called with. I think the structure of V2 would support this just fine. ron From rminnich at lanl.gov Tue Apr 13 08:56:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 08:56:01 2004 Subject: ATI rage xl.init In-Reply-To: Message-ID: On 13 Apr 2004, Eric W. Biederman wrote: > The Linux driver does not load the firmware? Or do we need SCSI support? You're going to love this one Eric :-) I might just need it for Plan 9 :-) So, much as I always disliked the idea of loading SCSI firmware, I might want it now :-( ron From rminnich at lanl.gov Tue Apr 13 08:59:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 08:59:01 2004 Subject: ATI rage xl.init In-Reply-To: Message-ID: On Tue, 13 Apr 2004, ron minnich wrote: > Driver sounds ok to me. This would get the driver into the static device > tree. The convention could be that drivers are called with the same passes > that any other static device is called with. It's true that 'dir' would work. The other commands are all for the most part handly aliases for 'dir'. So if people want to just go with 'dir', fine, if we want another noise word, 'device' is fine too. One thing, the new noise word 'device' does give us the future ability to do special things for devices if we need to. ron From stepan at openbios.org Tue Apr 13 09:07:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Apr 13 09:07:00 2004 Subject: ATI rage xl.init In-Reply-To: References: Message-ID: <20040413141905.GA11308@openbios.org> * ron minnich [040413 16:06]: > I might just need it for Plan 9 :-) > > So, much as I always disliked the idea of loading SCSI firmware, I might > want it now :-( SCSI firmware imho really belongs on the SCSI controller you put in. At least as long as we don't live in a world of perfect, intelligent and self-initializing hardware, this is the way of smallest trouble if we don't want to lock potential customers/users away. For onboard hardware this means we want a minimal set of drivers in LinuxBIOS, unfortunately. Stefan From stepan at openbios.org Tue Apr 13 09:11:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Apr 13 09:11:01 2004 Subject: ATI rage xl.init In-Reply-To: References: Message-ID: <20040413142323.GB11308@openbios.org> * ron minnich [040413 16:10]: > It's true that 'dir' would work. The other commands are all for the most > part handly aliases for 'dir'. > > So if people want to just go with 'dir', fine, if we want another noise > word, 'device' is fine too. One thing, the new noise word 'device' does > give us the future ability to do special things for devices if we need to. I've adapted the newisys khepri build to use the trident blade 3d code in drivers/. What boards use an onboard Rage XL? * Tyan S2880? * Arima HDAM* * AMD Quartet any more? Stefan From mdeschamps at mangrove-systems.com Tue Apr 13 09:23:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Tue Apr 13 09:23:00 2004 Subject: LinuxBios "official" requirements. In-Reply-To: <20040413134754.GA10961@openbios.org> References: <1081518783.1299.128.camel@Calliphara> <20040413134754.GA10961@openbios.org> Message-ID: <1081866740.1299.278.camel@Calliphara> Well, thank you very much it's only what I was looking for. I know for now ecgs is quite "old" but since it's recommanded for kernel compilation... If I knew I get that bother... Pfiou, all the components needs to be upgraded... so the shortcut is called Red Hat 9 ... Le mar 13/04/2004 ? 15:47, Stefan Reinauer a ?crit : > * Mathieu Deschamps [040409 15:53]: > > I've read several documentation on LinuxBios and related > > projects, though I didn't find out a LinuxBios requirements > > "true" paper. I still have the 2.4.xx kernel compiling oriented slab > > that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), > > Binutils 2.10, util-linux 2.10. > > egcs is pretty much outdated. I've been using: > make-3.80-179 > gcc-3.3.3-33 > binutils-2.15.90.0.1.1-30 > util-linux-2.12-59 > python-2.3.3-65 > > > Also I had a quite old python version (1.1 or so), i got it updated > > to 2.2.3 when I've seen the python script insulted me while running > > buildtarget. > > Anything older than 2.1 won't work. > > > What I try to say is that a REQUIEREMENTS file in the source tree LACKS, > > Maybe it lacks also in the site page (IMHO, the early page info should > > mention this)... > > Maybe it would make sense to enhance the available LinuxBIOS on AMD64 > document (freebios2/documentation/LinuxBIOS-AMD64.pdf) to contain > information about the other ports as well. LinuxBIOS v2 does a great job > unifying things. Truely a good document to start with, it gave me a good "overall view" to what linuxbios is up to : so a port' would be thaaaaat great. > > Stefan > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Tue Apr 13 09:37:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 09:37:01 2004 Subject: ATI rage xl.init In-Reply-To: <20040413142323.GB11308@openbios.org> Message-ID: On Tue, 13 Apr 2004, Stefan Reinauer wrote: > What boards use an onboard Rage XL? > * Tyan S2880? > * Arima HDAM* > * AMD Quartet ibm e325 ron From ebiederman at lnxi.com Tue Apr 13 09:47:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Apr 13 09:47:00 2004 Subject: ATI rage xl.init In-Reply-To: <20040413142323.GB11308@openbios.org> References: <20040413142323.GB11308@openbios.org> Message-ID: Stefan Reinauer writes: > * ron minnich [040413 16:10]: > > It's true that 'dir' would work. The other commands are all for the most > > part handly aliases for 'dir'. > > > > So if people want to just go with 'dir', fine, if we want another noise > > word, 'device' is fine too. One thing, the new noise word 'device' does > > give us the future ability to do special things for devices if we need to. > > I've adapted the newisys khepri build to use the trident blade 3d code > in drivers/. > > What boards use an onboard Rage XL? > * Tyan S2880? > * Arima HDAM* > * AMD Quartet > > any more? Probably not in the freebios2 tree.. Pretty much every server board I have touched in the last 3 years has one. If I have some spare time that will be a good excuse to do some forward ports. Eric From YhLu at tyan.com Tue Apr 13 11:17:00 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 13 11:17:00 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= Message-ID: <3174569B9743D511922F00A0C943142304B86134@TYANWEB> >If we can now get hands on loading firmware into the LSI1020/1030, we'd >be prepared for a lot of nice opteron servers and possibly many others. I understand that The LSI seems not to want to let me put the code that I have referred to their NDA documents under GPL. Beside that still need to add some code to filo to make it understand scsi_disk. I will try to talk to them again. Regards YH -----????----- ???: Stefan Reinauer [mailto:stepan at openbios.org] ????: 2004?4?13? 5:22 ???: YhLu ??: ron minnich; Stefan Reinauer; Takeshi Sone; ebiederman at lnxi.com; linuxbios at clustermatic.org ??: Re: ATI rage xl.init * YhLu [040412 23:23]: > I move the kernel patch that init rage xl for fb into LinuxBIOS. You can > disable the patch in Kernel and still can use rage xl for fb. wonderful! I've commited this to the V2 CVS and moved the Trident Blade3d driver there as well. I changed the directory layout a little bit to suit northbridge/southbridge/mainboard by using driver/vendor/device as the path to the device init code. What is the right way of getting this code into a LinuxBIOS build? Should there be some "driver" directive like there's "northbridge" and "southbridge"? Or is there some better idea? If we can now get hands on loading firmware into the LSI1020/1030, we'd be prepared for a lot of nice opteron servers and possibly many others. Stefan From YhLu at tyan.com Tue Apr 13 11:22:00 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 13 11:22:00 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= Message-ID: <3174569B9743D511922F00A0C943142304B86137@TYANWEB> Tyan s2850 Tyan S2880 Tyan S2881 Tyan S2882 Tyan S4880 Tyan S4882 -----????----- ???: Stefan Reinauer [mailto:stepan at openbios.org] ????: 2004?4?13? 7:23 ???: ron minnich ??: YhLu; Takeshi Sone; ebiederman at lnxi.com; linuxbios at clustermatic.org ??: Re: ATI rage xl.init * ron minnich [040413 16:10]: > It's true that 'dir' would work. The other commands are all for the most > part handly aliases for 'dir'. > > So if people want to just go with 'dir', fine, if we want another noise > word, 'device' is fine too. One thing, the new noise word 'device' does > give us the future ability to do special things for devices if we need to. I've adapted the newisys khepri build to use the trident blade 3d code in drivers/. What boards use an onboard Rage XL? * Tyan S2880? * Arima HDAM* * AMD Quartet any more? Stefan From YhLu at tyan.com Tue Apr 13 11:31:01 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 13 11:31:01 2004 Subject: FILO features request Message-ID: <3174569B9743D511922F00A0C943142304B8613C@TYANWEB> Eric, Are you adding features to filo? I hope it can 1. understand grub.conf in HD --- and append console=tty0 console=ttyS0,115200 automatically 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and append console=tty0 console=ttyS0,115200 automatically 3. editor to boot command line 4. auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) mem at 0xfff80000 mem at 0xfff90000 mem at 0xfffa0000 mem at 0xfffb0000 .... Regards YH From ebiederman at lnxi.com Tue Apr 13 13:18:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Apr 13 13:18:01 2004 Subject: ATI rage xl.init In-Reply-To: <20040413141905.GA11308@openbios.org> References: <20040413141905.GA11308@openbios.org> Message-ID: Stefan Reinauer writes: > * ron minnich [040413 16:06]: > > I might just need it for Plan 9 :-) > > > > So, much as I always disliked the idea of loading SCSI firmware, I might > > want it now :-( > > SCSI firmware imho really belongs on the SCSI controller you put in. At > least as long as we don't live in a world of perfect, intelligent and > self-initializing hardware, this is the way of smallest trouble if we > don't want to lock potential customers/users away. For onboard hardware > this means we want a minimal set of drivers in LinuxBIOS, unfortunately. If we can do it, I don't see a problem putting the code somewhere in the motherboard BIOS. Basically the LinuxBIOS mandate is to make the hardware functional. One thing to watch is that a LinuxBIOS driver is not really a driver more of an initializer. However there is no point in doing work that can be done elsewhere, like probing a scsi or ide chain for devices. Eric From ebiederman at lnxi.com Tue Apr 13 13:21:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Tue Apr 13 13:21:01 2004 Subject: FILO features request In-Reply-To: <3174569B9743D511922F00A0C943142304B8613C@TYANWEB> References: <3174569B9743D511922F00A0C943142304B8613C@TYANWEB> Message-ID: YhLu writes: > Eric, > > Are you adding features to filo? I've thought about it but I don't have the time at the moment :( > I hope it can > 1. understand grub.conf in HD --- and append console=tty0 > console=ttyS0,115200 automatically It currently does not look at any configuration files. > 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and > append console=tty0 console=ttyS0,115200 automatically Nope it does not do that either. > 3. editor to boot command line It does have that. > 4. auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) > mem at 0xfff80000 > mem at 0xfff90000 > mem at 0xfffa0000 > mem at 0xfffb0000 > .... That is certainly a sane idea. Eric From rminnich at lanl.gov Tue Apr 13 14:37:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 14:37:01 2004 Subject: VGA bios on epia-m Message-ID: I'm trying to extract it. I'm wondering if anyone else has, and if so, where in the bios image it was? I can't see anything at an offset that makes lots of sense. Unless the bios copies the vga bios to ram at 0xc000, oh joy. ron From jbors at mail.ru Tue Apr 13 20:24:00 2004 From: jbors at mail.ru (Dmitry Borisov) Date: Tue Apr 13 20:24:00 2004 Subject: VGA bios on epia-m References: Message-ID: <010501c421c0$cd0b8c20$0300a8c0@amr.corp.intel.com> Well, Here is the command I use. dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528 Dmitry/ ----- Original Message ----- Subject: VGA bios on epia-m > > I'm trying to extract it. I'm wondering if anyone else has, and if so, > where in the bios image it was? I can't see anything at an offset that > makes lots of sense. Unless the bios copies the vga bios to ram at 0xc000, > oh joy. > > ron From rminnich at lanl.gov Tue Apr 13 21:51:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 21:51:01 2004 Subject: VGA bios on epia-m In-Reply-To: <010501c421c0$cd0b8c20$0300a8c0@amr.corp.intel.com> Message-ID: On Tue, 13 Apr 2004, Dmitry Borisov wrote: > Well, > Here is the command I use. > dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528 yeah, that works on a booted system. I was looking for somethat that would work on a bios file, preferably on linux. ron From rminnich at lanl.gov Tue Apr 13 21:53:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 13 21:53:01 2004 Subject: VGA bios on epia-m In-Reply-To: <010501c421c0$cd0b8c20$0300a8c0@amr.corp.intel.com> Message-ID: BTW Dmitry I have integrated all your changes (with some mods for things not done quite right) into V1 and will test tomorrow. The EPIA-M is coming up however. Once again, once all this works, then is the time for the V2 port. ron From ebiederman at lnxi.com Wed Apr 14 00:22:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Apr 14 00:22:00 2004 Subject: VGA bios on epia-m In-Reply-To: References: Message-ID: ron minnich writes: > I'm trying to extract it. I'm wondering if anyone else has, and if so, > where in the bios image it was? I can't see anything at an offset that > makes lots of sense. Unless the bios copies the vga bios to ram at 0xc000, > oh joy. The last BIOS romimage format I understood compressed option roms in a hacked up lharc format. Eric From mdeschamps at mangrove-systems.com Wed Apr 14 02:48:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Wed Apr 14 02:48:00 2004 Subject: LinuxBios "official" requirements and ROM building In-Reply-To: <20040413134754.GA10961@openbios.org> References: <1081518783.1299.128.camel@Calliphara> <20040413134754.GA10961@openbios.org> Message-ID: <1081929406.1299.300.camel@Calliphara> I've ty to build rom on a other Machine with RH9 Le mar 13/04/2004 ? 15:47, Stefan Reinauer a ?crit : > * Mathieu Deschamps [040409 15:53]: > > I've read several documentation on LinuxBios and related > > projects, though I didn't find out a LinuxBios requirements > > "true" paper. I still have the 2.4.xx kernel compiling oriented slab > > that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), > > Binutils 2.10, util-linux 2.10. > > egcs is pretty much outdated. I've been using: > make-3.80-179 > gcc-3.3.3-33 > binutils-2.15.90.0.1.1-30 > util-linux-2.12-59 > python-2.3.3-65 > But I just dipose: make -3.79.1 gcc 3.2.2 20030222 (Red Hat Linux 3.2.2-5) bintutils version 2.13.90.0.1 util-linux-2.11y Python 2.2.2 I got this output : ###################################################################### cp /home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base crt0.S gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E -I/home/root/projet/freebios/freebios2/src -D__ROMCC__=0 -D__ROMCC_MINOR__=38 -I/home/root/projet/freebios/freebios2/src/include -I/home/root/projet/freebios/freebios2/src/arch/i386/include -I -DARCH='i386' -DCROSS_COMPILE -DCC='gcc' -DHOSTCC='gcc' -DOBJCOPY='objcopy' -DLINUXBIOS_VERSION='1.1.6' -DLINUXBIOS_BUILD='mer avr 14 09:46:21 CEST 2004' -DLINUXBIOS_COMPILE_TIME='09:46:21' -DLINUXBIOS_COMPILE_BY='root' -DLINUXBIOS_COMPILE_HOST='Calliphara' -DLINUXBIOS_COMPILE_DOMAIN -DLINUXBIOS_COMPILER='version gcc 3.2.2 20030222 (Red Hat Linux 3.2.2-5)' -DLINUXBIOS_LINKER='GNU ld version 2.13.90.0.18 20030206' -DLINUXBIOS_ASSEMBLER='Version de l'assembleur GNU 2.13.90.0.18 (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206' -DHAVE_FALLBACK_BOOT='1' -DROM_IMAGE_SIZE='0x10000' -DPAYLOAD_SIZE='0x10000' -D_ROMBASE='0xffff0000' -D_RESET='0xffff0000' -D_EXCEPTION_VECTORS='0xffff0100' -DSTACK_SIZE='0x4000' -DHEAP_SIZE='0x8000' -D_RAMBASE='0x4000' -DCONFIG_COMPRESS='1' -DCONFIG_UNCOMPRESSED='0' -DCONFIG_LB_MEM_TOPK='1024' -DHAVE_OPTION_TABLE='1' -DUSE_OPTION_TABLE='0' -DLB_CKS_RANGE_START='49' -DLB_CKS_RANGE_END='125' -DLB_CKS_LOC='126' -DCRT0='/home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base' -DDEBUG='1' -DCONFIG_CONSOLE_VGA='1' -DCONFIG_CONSOLE_LOGBUF='0' -DCONFIG_CONSOLE_SROM='0' -DCONFIG_CONSOLE_SERIAL8250='1' -DDEFAULT_CONSOLE_LOGLEVEL='7' -DMAXIMUM_CONSOLE_LOGLEVEL='7' -DCONFIG_SERIAL_POST='1' -DTTYS0_BASE='0x3f8' -DTTYS0_BAUD='19200' -DTTYS0_LCS='0x3' -DMAINBOARD='/home/root/projet/freebios/freebios2/src/mainboard/via/epia' -DMAINBOARD_PART_NUMBER='epia' -DMAINBOARD_VENDOR='via' -DCONFIG_SMP='0' -DCONFIG_MAX_CPUS='1' -DCONFIG_MAX_PHYSICAL_CPUS='1' -DCONFIG_LOGICAL_CPUS='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' -DCONFIG_ROM_STREAM_START='0xfffe0000' -DCONFIG_FS_STREAM='0' -DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' -DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 console=tty0 console=ttyS0,115200"' -DCONFIG_IDE='1' -DIDE_BOOT_DRIVE='0' -DIDE_OFFSET='0' -DHARD_RESET_BUS='1' -DHARD_RESET_DEVICE='5' -DHARD_RESET_FUNCTION='0' -DMAX_REBOOT_CNT='10' -DFAKE_SPDROM='0' -DHAVE_ACPI_TABLES='0' -DCONFIG_CHIP_CONFIGURE='1' -DCPU_FIXUP='1' -DCONFIG_UDELAY_TSC='0' -Di686='1' -Di586='1' -DINTEL_PPRO_MTRR='1' -DROM_SIZE='0x40000' -DFALLBACK_SIZE='0x20000' -DUSE_FALLBACK_IMAGE='1' -DLINUXBIOS_EXTRA_VERSION='.0Fallback' -DHAVE_MP_TABLE='0' -DHAVE_HARD_RESET='1' -DHAVE_PIRQ_TABLE='1' -DIRQ_SLOT_COUNT='5' -DROM_SECTION_SIZE='0x20000' -DROM_SECTION_OFFSET='0x20000' -DXIP_ROM_SIZE='0x10000' -DXIP_ROM_BASE='0xffff0000' /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c > ./failover.E #*#/bin/sh: -c: line 1: syntax error near unexpected token `(' #*#/bin/sh: -c: line 1: `gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E -I/home/root/projet/freebios/freebios2/src -D__ROMCC__=0 -D__ROMCC_MINOR__=38 -I/home/root/projet/freebios/freebios2/src/include -I/home/root/projet/freebios/freebios2/src/arch/i386/include -I -DARCH='i386' -DCROSS_COMPILE -DCC='gcc' -DHOSTCC='gcc' -DOBJCOPY='objcopy' -DLINUXBIOS_VERSION='1.1.6' -DLINUXBIOS_BUILD='mer avr 14 09:46:21 CEST 2004' -DLINUXBIOS_COMPILE_TIME='09:46:21' -DLINUXBIOS_COMPILE_BY='root' -DLINUXBIOS_COMPILE_HOST='Calliphara' -DLINUXBIOS_COMPILE_DOMAIN -DLINUXBIOS_COMPILER='version gcc 3.2.2 20030222 (Red Hat Linux 3.2.2-5)' -DLINUXBIOS_LINKER='GNU ld version 2.13.90.0.18 20030206' -DLINUXBIOS_ASSEMBLER='Version de l'assembleur GNU 2.13.90.0.18 (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206' -DHAVE_FALLBACK_BOOT='1' -DROM_IMAGE_SIZE='0x10000' -DPAYLOAD_SIZE='0x10000' -D_ROMBASE='0xffff0000' -D_RESET='0xffff0000' -D_EXCEPTION_VECTORS='0xffff0100' -DSTACK_SIZE='0x4000' -DHEAP_SIZE='0x8000' -D_RAMBASE='0x4000' -DCONFIG_COMPRESS='1' -DCONFIG_UNCOMPRESSED='0' -DCONFIG_LB_MEM_TOPK='1024' -DHAVE_OPTION_TABLE='1' -DUSE_OPTION_TABLE='0' -DLB_CKS_RANGE_START='49' -DLB_CKS_RANGE_END='125' -DLB_CKS_LOC='126' -DCRT0='/home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base' -DDEBUG='1' -DCONFIG_CONSOLE_VGA='1' -DCONFIG_CONSOLE_LOGBUF='0' -DCONFIG_CONSOLE_SROM='0' -DCONFIG_CONSOLE_SERIAL8250='1' -DDEFAULT_CONSOLE_LOGLEVEL='7' -DMAXIMUM_CONSOLE_LOGLEVEL='7' -DCONFIG_SERIAL_POST='1' -DTTYS0_BASE='0x3f8' -DTTYS0_BAUD='19200' -DTTYS0_LCS='0x3' -DMAINBOARD='/home/root/projet/freebios/freebios2/src/mainboard/via/epia' -DMAINBOARD_PART_NUMBER='epia' -DMAINBOARD_VENDOR='via' -DCONFIG_SMP='0' -DCONFIG_MAX_CPUS='1' -DCONFIG_MAX_PHYSICAL_CPUS='1' -DCONFIG_LOGICAL_CPUS='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' -DCONFIG_ROM_STREAM_START='0xfffe0000' -DCONFIG_FS_STREAM='0' -DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' -DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 console=tty0 console=ttyS0,115200"' -DCONFIG_IDE='1' -DIDE_BOOT_DRIVE='0' -DIDE_OFFSET='0' -DHARD_RESET_BUS='1' -DHARD_RESET_DEVICE='5' -DHARD_RESET_FUNCTION='0' -DMAX_REBOOT_CNT='10' -DFAKE_SPDROM='0' -DHAVE_ACPI_TABLES='0' -DCONFIG_CHIP_CONFIGURE='1' -DCPU_FIXUP='1' -DCONFIG_UDELAY_TSC='0' -Di686='1' -Di586='1' -DINTEL_PPRO_MTRR='1' -DROM_SIZE='0x40000' -DFALLBACK_SIZE='0x20000' -DUSE_FALLBACK_IMAGE='1' -DLINUXBIOS_EXTRA_VERSION='.0Fallback' -DHAVE_MP_TABLE='0' -DHAVE_HARD_RESET='1' -DHAVE_PIRQ_TABLE='1' -DIRQ_SLOT_COUNT='5' -DROM_SECTION_SIZE='0x20000' -DROM_SECTION_OFFSET='0x20000' -DXIP_ROM_SIZE='0x10000' -DXIP_ROM_BASE='0xffff0000' /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c > ./failover.E' make: *** [failover.E] Erreur 2 ######################################################################### first the make process now recognize the make functions (it seems anyway) but second, I still have these errors, it seems like a bad parse isn't it ? Make v3.79 isn't good enough ? /bin/sh: -c: line 1: syntax error near unexpected token `(' /bin/sh: -c: line 1: `gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E > Also I had a quite old python version (1.1 or so), i got it updated > > to 2.2.3 when I've seen the python script insulted me while running > > buildtarget. > > Anything older than 2.1 won't work. endly, I get confused Stefan : you said you made it with python-2.3.3-65 and then you said "Anything older than 2.1 won't work." I must have dropped the purse before the coin would:) > > > What I try to say is that a REQUIEREMENTS file in the source tree LACKS, > > Maybe it lacks also in the site page (IMHO, the early page info should > > mention this)... > > Maybe it would make sense to enhance the available LinuxBIOS on AMD64 > document (freebios2/documentation/LinuxBIOS-AMD64.pdf) to contain > information about the other ports as well. LinuxBIOS v2 does a great job > unifying things. > > Stefan > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From mdeschamps at mangrove-systems.com Wed Apr 14 04:57:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Wed Apr 14 04:57:00 2004 Subject: LinuxBios "official" requirements and ROM building again Message-ID: <1081937127.16994.7.camel@Calliphara> I've ty to build rom on a other Machine with RH9 Le mar 13/04/2004 ? 15:47, Stefan Reinauer a ?crit : > * Mathieu Deschamps [040409 15:53]: > > I've read several documentation on LinuxBios and related > > projects, though I didn't find out a LinuxBios requirements > > "true" paper. I still have the 2.4.xx kernel compiling oriented slab > > that is to say : GNU Make 3.77, ECGS 1.1.2 (GCC 2.91.66), > > Binutils 2.10, util-linux 2.10. > > egcs is pretty much outdated. I've been using: > make-3.80-179 > gcc-3.3.3-33 > binutils-2.15.90.0.1.1-30 > util-linux-2.12-59 > python-2.3.3-65 > But I just dipose: make -3.79.1 gcc 3.2.2 20030222 (Red Hat Linux 3.2.2-5) bintutils version 2.13.90.0.1 util-linux-2.11y Python 2.2.2 I got this output : ###################################################################### cp /home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base crt0.S gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E -I/home/root/projet/freebios/freebios2/src -D__ROMCC__=0 -D__ROMCC_MINOR__=38 -I/home/root/projet/freebios/freebios2/src/include -I/home/root/projet/freebios/freebios2/src/arch/i386/include -I -DARCH='i386' -DCROSS_COMPILE -DCC='gcc' -DHOSTCC='gcc' -DOBJCOPY='objcopy' -DLINUXBIOS_VERSION='1.1.6' -DLINUXBIOS_BUILD='mer avr 14 09:46:21 CEST 2004' -DLINUXBIOS_COMPILE_TIME='09:46:21' -DLINUXBIOS_COMPILE_BY='root' -DLINUXBIOS_COMPILE_HOST='Calliphara' -DLINUXBIOS_COMPILE_DOMAIN -DLINUXBIOS_COMPILER='version gcc 3.2.2 20030222 (Red Hat Linux 3.2.2-5)' -DLINUXBIOS_LINKER='GNU ld version 2.13.90.0.18 20030206' -DLINUXBIOS_ASSEMBLER='Version de l'assembleur GNU 2.13.90.0.18 (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206' -DHAVE_FALLBACK_BOOT='1' -DROM_IMAGE_SIZE='0x10000' -DPAYLOAD_SIZE='0x10000' -D_ROMBASE='0xffff0000' -D_RESET='0xffff0000' -D_EXCEPTION_VECTORS='0xffff0100' -DSTACK_SIZE='0x4000' -DHEAP_SIZE='0x8000' -D_RAMBASE='0x4000' -DCONFIG_COMPRESS='1' -DCONFIG_UNCOMPRESSED='0' -DCONFIG_LB_MEM_TOPK='1024' -DHAVE_OPTION_TABLE='1' -DUSE_OPTION_TABLE='0' -DLB_CKS_RANGE_START='49' -DLB_CKS_RANGE_END='125' -DLB_CKS_LOC='126' -DCRT0='/home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base' -DDEBUG='1' -DCONFIG_CONSOLE_VGA='1' -DCONFIG_CONSOLE_LOGBUF='0' -DCONFIG_CONSOLE_SROM='0' -DCONFIG_CONSOLE_SERIAL8250='1' -DDEFAULT_CONSOLE_LOGLEVEL='7' -DMAXIMUM_CONSOLE_LOGLEVEL='7' -DCONFIG_SERIAL_POST='1' -DTTYS0_BASE='0x3f8' -DTTYS0_BAUD='19200' -DTTYS0_LCS='0x3' -DMAINBOARD='/home/root/projet/freebios/freebios2/src/mainboard/via/epia' -DMAINBOARD_PART_NUMBER='epia' -DMAINBOARD_VENDOR='via' -DCONFIG_SMP='0' -DCONFIG_MAX_CPUS='1' -DCONFIG_MAX_PHYSICAL_CPUS='1' -DCONFIG_LOGICAL_CPUS='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' -DCONFIG_ROM_STREAM_START='0xfffe0000' -DCONFIG_FS_STREAM='0' -DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' -DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 console=tty0 console=ttyS0,115200"' -DCONFIG_IDE='1' -DIDE_BOOT_DRIVE='0' -DIDE_OFFSET='0' -DHARD_RESET_BUS='1' -DHARD_RESET_DEVICE='5' -DHARD_RESET_FUNCTION='0' -DMAX_RE! BOOT_CNT='10' -DFAKE_SPDROM='0' -DHAVE_ACPI_TABLES='0' -DCONFIG_CHIP_CONFIGURE='1' -DCPU_FIXUP='1' -DCONFIG_UDELAY_TSC='0' -Di686='1' -Di586='1' -DINTEL_PPRO_MTRR='1' -DROM_SIZE='0x40000' -DFALLBACK_SIZE='0x20000' -DUSE_FALLBACK_IMAGE='1' -DLINUXBIOS_EXTRA_VERSION='.0Fallback' -DHAVE_MP_TABLE='0' -DHAVE_HARD_RESET='1' -DHAVE_PIRQ_TABLE='1' -DIRQ_SLOT_COUNT='5' -DROM_SECTION_SIZE='0x20000' -DROM_SECTION_OFFSET='0x20000' -DXIP_ROM_SIZE='0x10000' -DXIP_ROM_BASE='0xffff0000' /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c > ./failover.E #*#/bin/sh: -c: line 1: syntax error near unexpected token `(' #*#/bin/sh: -c: line 1: `gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E -I/home/root/projet/freebios/freebios2/src -D__ROMCC__=0 -D__ROMCC_MINOR__=38 -I/home/root/projet/freebios/freebios2/src/include -I/home/root/projet/freebios/freebios2/src/arch/i386/include -I -DARCH='i386' -DCROSS_COMPILE -DCC='gcc' -DHOSTCC='gcc' -DOBJCOPY='objcopy' -DLINUXBIOS_VERSION='1.1.6' -DLINUXBIOS_BUILD='mer avr 14 09:46:21 CEST 2004' -DLINUXBIOS_COMPILE_TIME='09:46:21' -DLINUXBIOS_COMPILE_BY='root' -DLINUXBIOS_COMPILE_HOST='Calliphara' -DLINUXBIOS_COMPILE_DOMAIN -DLINUXBIOS_COMPILER='version gcc 3.2.2 20030222 (Red Hat Linux 3.2.2-5)' -DLINUXBIOS_LINKER='GNU ld version 2.13.90.0.18 20030206' -DLINUXBIOS_ASSEMBLER='Version de l'assembleur GNU 2.13.90.0.18 (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206' -DHAVE_FALLBACK_BOOT='1' -DROM_IMAGE_SIZE='0x10000' -DPAYLOAD_SIZE='0x10000' -D_ROMBASE='0xffff0000' -D_RESET='0xffff0000' -D_EXCEPTION_VECTORS='0xffff0100' -DSTACK_SIZE='0x4000' -DHEAP_SIZE='0x8000' -D_RAMBASE='0x4000' -DCONFIG_COMPRESS='1' -DCONFIG_UNCOMPRESSED='0' -DCONFIG_LB_MEM_TOPK='1024' -DHAVE_OPTION_TABLE='1' -DUSE_OPTION_TABLE='0' -DLB_CKS_RANGE_START='49' -DLB_CKS_RANGE_END='125' -DLB_CKS_LOC='126' -DCRT0='/home/root/projet/freebios/freebios2/src/arch/i386/config/crt0.base' -DDEBUG='1' -DCONFIG_CONSOLE_VGA='1' -DCONFIG_CONSOLE_LOGBUF='0' -DCONFIG_CONSOLE_SROM='0' -DCONFIG_CONSOLE_SERIAL8250='1' -DDEFAULT_CONSOLE_LOGLEVEL='7' -DMAXIMUM_CONSOLE_LOGLEVEL='7' -DCONFIG_SERIAL_POST='1' -DTTYS0_BASE='0x3f8' -DTTYS0_BAUD='19200' -DTTYS0_LCS='0x3' -DMAINBOARD='/home/root/projet/freebios/freebios2/src/mainboard/via/epia' -DMAINBOARD_PART_NUMBER='epia' -DMAINBOARD_VENDOR='via' -DCONFIG_SMP='0' -DCONFIG_MAX_CPUS='1' -DCONFIG_MAX_PHYSICAL_CPUS='1' -DCONFIG_LOGICAL_CPUS='0' -DCONFIG_IDE_STREAM='0' -DCONFIG_ROM_STREAM='1' -DCONFIG_ROM_STREAM_START='0xfffe0000' -DCONFIG_FS_STREAM='0' -DCONFIG_FS_EXT2='0' -DCONFIG_FS_ISO9660='0' -DCONFIG_FS_FAT='0' -DAUTOBOOT_DELAY='2' -DAUTOBOOT_CMDLINE='"hdc1:/vmlinuz root=/dev/hdc3 console=tty0 console=ttyS0,115200"' -DCONFIG_IDE='1' -DIDE_BOOT_DRIVE='0' -DIDE_OFFSET='0' -DHARD_RESET_BUS='1' -DHARD_RESET_DEVICE='5' -DHARD_RESET_FUNCTION='0' -DMAX_RE! BOOT_CNT='10' -DFAKE_SPDROM='0' -DHAVE_ACPI_TABLES='0' -DCONFIG_CHIP_CONFIGURE='1' -DCPU_FIXUP='1' -DCONFIG_UDELAY_TSC='0' -Di686='1' -Di586='1' -DINTEL_PPRO_MTRR='1' -DROM_SIZE='0x40000' -DFALLBACK_SIZE='0x20000' -DUSE_FALLBACK_IMAGE='1' -DLINUXBIOS_EXTRA_VERSION='.0Fallback' -DHAVE_MP_TABLE='0' -DHAVE_HARD_RESET='1' -DHAVE_PIRQ_TABLE='1' -DIRQ_SLOT_COUNT='5' -DROM_SECTION_SIZE='0x20000' -DROM_SECTION_OFFSET='0x20000' -DXIP_ROM_SIZE='0x10000' -DXIP_ROM_BASE='0xffff0000' /home/root/projet/freebios/freebios2/src/mainboard/via/epia/failover.c > ./failover.E' make: *** [failover.E] Erreur 2 ######################################################################### first the make process now recognize the make functions (it seems anyway) but second, I still have these errors, it seems like a bad parse isn't it ? Make v3.79 isn't good enough ? /bin/sh: -c: line 1: syntax error near unexpected token `(' /bin/sh: -c: line 1: `gcc -no-gcc -x assembler-with-cpp -DASSEMBLY -E Note : I've step deeper into fallback directory where make echo does this error which is correlate to the upper one : #######################################################" . . . HAVE_ACPI_TABLES=0 HAVE_FALLBACK_BOOT=1 HAVE_HARD_RESET=1 HAVE_MP_TABLE=0 HAVE_OPTION_TABLE=1 HAVE_PIRQ_TABLE=1 HEAP_SIZE=0x8000 HOSTCC=gcc IDE_BOOT_DRIVE=0 IDE_OFFSET=0 IDE_SWAB= INTEL_PPRO_MTRR=1 IRQ_SLOT_COUNT=5 ISA_IO_BASE= ISA_MEM_BASE= LB_CKS_LOC=126 LB_CKS_RANGE_END=125 LB_CKS_RANGE_START=49 /bin/sh: -c: line 1: syntax error near unexpected token `(' /bin/sh: -c: line 1: `echo LINUXBIOS_ASSEMBLER='Version de l'assembleur GNU 2.13.90.0.18 (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206'' make: *** [echo] Erreur 2 ####################################################################" Makefile.settings export : export LINUXBIOS_ASSEMBLER:=$(shell touch dummy.s ; $(CC) -c -Wa,-v dummy.s 2>&1; rm -f dummy.s dummy.o ) well Ron ...I've got another one :) there must be another way to gain gcc -Wa version ... :/ > Also I had a quite old python version (1.1 or so), i got it updated > > to 2.2.3 when I've seen the python script insulted me while running > > buildtarget. > > Anything older than 2.1 won't work. endly, I get confused Stefan : you said you made it with python-2.3.3-65 and then you said "Anything older than 2.1 won't work." I must have dropped the purse before the coin would:) From mdeschamps at mangrove-systems.com Wed Apr 14 05:24:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Wed Apr 14 05:24:00 2004 Subject: Build error and Makefile.settings Message-ID: <1081938718.16994.17.camel@Calliphara> ok i've found were it bugs : when it does this : export LINUXBIOS_ASSEMBLER:=$(shell touch dummy.s ; $(CC) -c -Wa,-v dummy.s 2>&1; rm -f dummy.s dummy.o ) the answer should be when typing make echo : LINUXBIOS_ASSEMBLER="Version de l'assembleur GNU 2.13.90.0.18 (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206" But the ' character makes a parse error even if the string is quoted ' ' I propose to patch this quckly: export LINUXBIOS_ASSEMBLER:=$(shell touch dummy.s ; $(CC) -c -Wa,-v dummy.s 2>&1 | tr -s '\''; rm -f dummy.s dummy.o ) mathieu From rminnich at lanl.gov Wed Apr 14 08:17:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 14 08:17:00 2004 Subject: VGA bios on epia-m In-Reply-To: Message-ID: On 13 Apr 2004, Eric W. Biederman wrote: > The last BIOS romimage format I understood compressed option roms > in a hacked up lharc format. ah, ok, I've heard about this. OK, time to boot under normal bios and do it that way :-) ron From rminnich at lanl.gov Wed Apr 14 08:21:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 14 08:21:01 2004 Subject: Build error and Makefile.settings In-Reply-To: <1081938718.16994.17.camel@Calliphara> Message-ID: On 14 Apr 2004, Mathieu Deschamps wrote: > the answer should be when typing make echo : > LINUXBIOS_ASSEMBLER="Version de l'assembleur GNU 2.13.90.0.18 > (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206" > But the ' character makes a parse error even if the string is quoted ' ' ack! Now I bet we never thought of that one! > I propose to patch this quckly: > export LINUXBIOS_ASSEMBLER:=$(shell touch dummy.s ; $(CC) -c -Wa,-v > dummy.s 2>&1 | tr -s '\''; rm -f dummy.s dummy.o ) sounds good. ron From rminnich at lanl.gov Wed Apr 14 08:23:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 14 08:23:01 2004 Subject: Build error and Makefile.settings In-Reply-To: Message-ID: BTW Mathieu you've just discovered our first internationalization bug ... in a Makefile. Ow! ron From ts1 at tsn.or.jp Wed Apr 14 10:26:01 2004 From: ts1 at tsn.or.jp (Takeshi Sone) Date: Wed Apr 14 10:26:01 2004 Subject: FILO features request In-Reply-To: <3174569B9743D511922F00A0C943142304B8613C@TYANWEB> References: <3174569B9743D511922F00A0C943142304B8613C@TYANWEB> Message-ID: <20040414153749.GA6011@tsn.or.jp> On Tue, Apr 13, 2004 at 09:50:55AM -0700, YhLu wrote: > I hope it can > 1. understand grub.conf in HD --- and append console=tty0 > console=ttyS0,115200 automatically > 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and > append console=tty0 console=ttyS0,115200 automatically I don't like the idea to have compatibility to existing bootloaders. It sounds like a beginning of nightmare. Instead, Linux CDs can directly support FILO. Boot CDs can have /boot/filo.conf, and installers can generate /boot/filo.conf in the installed hard disk. It's technically easy. Stefan Reinauer was positive to add this support to SuSE's installation CD when I talked to him about this issue. > 3. editor to boot command line It already has very limited editor. > 4. auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) > mem at 0xfff80000 > mem at 0xfff90000 > mem at 0xfffa0000 > mem at 0xfffb0000 > .... Maybe, we can make FILO to have the default config file in ROM, which includes the filo.conf from boot device (CD or HD). So the config file in ROM knows how to boot Etherboot in ROM. But this is too complicated at the moment. -- Takeshi From mdeschamps at mangrove-systems.com Wed Apr 14 11:35:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Wed Apr 14 11:35:01 2004 Subject: Build error and Makefile.settings In-Reply-To: References: Message-ID: <1081961041.17796.23.camel@Calliphara> So kind of you to cheer me up Ron !! because I found a new one, as it say "the least not the last" :'( I've brought some V1 files dealing with CONFIG_VGA_CONSOLE=1 option into V2 source tree (in bulldoze mode) (oh, on the fly there's still no support of this kind on V2 for epia-m ?) Rather than modified these file includes, I'd have liked to "change makefile" concerning the -I option pass to gcc. And what a surprise dooh : it's sed'ing for "install:" but in french it's "install?s:" ################################## SYNOPSIS : #grep -n -e "GCC_INC" < Makefile 15: GCC_INC_DIR := $(shell $(CC) -print-search-dirs | sed -ne "s/install: \(.*\)/\1include/gp") 16: CPPFLAGS := -I$(TOP)/src/include -I$(TOP)/src/arch/$(ARCH)/include -I$(GCC_INC_DIR) $(CPUFLAGS) #gcc -print-search-dirs | grep"/usr/lib/gcc-lib/i386-redhat-linux/3.2.2" install?s: /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/ programmes: =/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/:/usr/lib/gcc/i386-redhat-linux/3.2.2/:/usr/lib/gcc/i386-redhat-linux/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/bin/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/bin/ libraries: =/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/lib/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../:/lib/i386-redhat-linux/3.2.2/:/lib/:/usr/lib/i386-redhat-linux/3.2.2/:/usr/lib/ ################################# So it can find nothing for sure... Who is enough french language lover to translate even thoses words every body understand in english ? Gosh !:[ Well, it looks like 'am gone for a super bug hunt :) Or if anybody could spare me that sweating ? Every trick is welcome ! mathieu Le mer 14/04/2004 ? 15:35, ron minnich a ?crit : > BTW Mathieu you've just discovered our first internationalization bug ... > in a Makefile. Ow! > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Wed Apr 14 16:23:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 14 16:23:01 2004 Subject: FILO features request In-Reply-To: <20040414153749.GA6011@tsn.or.jp> Message-ID: On Thu, 15 Apr 2004, Takeshi Sone wrote: > On Tue, Apr 13, 2004 at 09:50:55AM -0700, YhLu wrote: > > I hope it can > > 1. understand grub.conf in HD --- and append console=tty0 > > console=ttyS0,115200 automatically > > 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and > > append console=tty0 console=ttyS0,115200 automatically > > I don't like the idea to have compatibility to existing bootloaders. > It sounds like a beginning of nightmare. yes. I really am not enthusiastic about turning filo back into grub. ron From rminnich at lanl.gov Wed Apr 14 16:25:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 14 16:25:01 2004 Subject: Build error and Makefile.settings In-Reply-To: <1081961041.17796.23.camel@Calliphara> Message-ID: On 14 Apr 2004, Mathieu Deschamps wrote: > Rather than modified these file includes, I'd have liked to "change > makefile" concerning the -I option pass to gcc. And what a surprise dooh > : it's sed'ing for "install:" but in french it's "install??s:" In V2, I have tried to remove makefile rules that call shell scripts. These types of rules seem very simple at first but as you can see turn into a real nightmare over time. Please take another look at how V2 works with an eye to removing these types of rules. I would rather not reintroduce them into v2. I notice a few have come back but I would very much like to limit their use. thanks ron From bmaly at angstrom.com Wed Apr 14 16:46:01 2004 From: bmaly at angstrom.com (Brian Maly) Date: Wed Apr 14 16:46:01 2004 Subject: ATI rage xl.init Message-ID: <1081980199.16313.24.camel@maly> Question about getting the ATI XLrage working... I tried the new ati/xlrage driver on an arima/hdama. Linuxbios reports: ati_regbase = 0xfd002400 ati_ragexl_init: 3D RAGE (XL PCI-33MHz) [0x4752 rev 0x27] Devices initialized Im then loading the atyfb.o framebuffer kernel module (I assume this is the right one to use). The screen then does some init and switches to a video mode the monitor seems happy with, but nothing but lines appear (much like the lines you get when X doesnt recognize the video right) Using fbset to change video modes does seem to work, the screen resolution changes, but I cant use the fbdevice with any frame buffer test programs or with X (the lines never go away). Im trying: (1) to get the framebuffer working as the graphical console, and (2) get this working under X. Is there some secret to getting this working? Maybe I am missing an important step or something.... Also, Im assuming that in order to use the framebuffer as the console, I can pass "vga = 792" and "video=atyfb:mode:1024x768,font:SUN12x22" to linux when it boot. Do I need to set CONFIG_CONSOLE_VGA = 1 in Config.lb? any help is appreciated. -Regards, Brian From rminnich at lanl.gov Wed Apr 14 16:49:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 14 16:49:00 2004 Subject: ATI rage xl.init In-Reply-To: <1081980199.16313.24.camel@maly> Message-ID: 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 From YhLu at tyan.com Wed Apr 14 17:02:01 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 14 17:02:01 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= Message-ID: <3174569B9743D511922F00A0C943142304B8627D@TYANWEB> The original fb driver for ati rage xl has problem. It use mclk=100Mhz, xclk default is mclk. Actually it should be mclk=83Mhz, and xclk=63Mhz. So please check the kernel you have built with Normal bios to see if you can get ouput. I guess you will get bland screen. Please make use only enable atyfb in kernel. Also please let me know your kernel version, and I could send you one kernel patch. Regards YH -----????----- ???: Brian Maly [mailto:bmaly at angstrom.com] ????: 2004?4?14? 15:03 ???: linuxbios at clustermatic.org ??: Re: ATI rage xl.init Question about getting the ATI XLrage working... I tried the new ati/xlrage driver on an arima/hdama. Linuxbios reports: ati_regbase = 0xfd002400 ati_ragexl_init: 3D RAGE (XL PCI-33MHz) [0x4752 rev 0x27] Devices initialized Im then loading the atyfb.o framebuffer kernel module (I assume this is the right one to use). The screen then does some init and switches to a video mode the monitor seems happy with, but nothing but lines appear (much like the lines you get when X doesnt recognize the video right) Using fbset to change video modes does seem to work, the screen resolution changes, but I cant use the fbdevice with any frame buffer test programs or with X (the lines never go away). Im trying: (1) to get the framebuffer working as the graphical console, and (2) get this working under X. Is there some secret to getting this working? Maybe I am missing an important step or something.... Also, Im assuming that in order to use the framebuffer as the console, I can pass "vga = 792" and "video=atyfb:mode:1024x768,font:SUN12x22" to linux when it boot. Do I need to set CONFIG_CONSOLE_VGA = 1 in Config.lb? any help is appreciated. -Regards, Brian _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From KingCrab at gmx.net Thu Apr 15 08:15:01 2004 From: KingCrab at gmx.net (Markus Wolters) Date: Thu Apr 15 08:15:01 2004 Subject: Linuxbios on ECS K7S5A? Message-ID: <2483.1082035634@www14.gmx.net> Hi everyone, I just heard of linuxbios and I wonder if anyone has it working on a elitegroup K7S5A? Are there any tutorials or maybe complette roms ready for flashing? Thanks everyone, Markus -- NEU : GMX Internet.FreeDSL Ab sofort DSL-Tarif ohne Grundgeb?hr: http://www.gmx.net/info From firstone5 at hotmail.com Thu Apr 15 10:08:00 2004 From: firstone5 at hotmail.com (M. Renee Hopkins) Date: Thu Apr 15 10:08:00 2004 Subject: EPIA-M Message-ID: Just read forum mail today. I've got ME-6000 here. Please let me know if I can support efforts to test epia-m freebios V1. _________________________________________________________________ Get rid of annoying pop-up ads with the new MSN Toolbar ? FREE! http://toolbar.msn.com/go/onm00200414ave/direct/01/ From linuxbios at matter.net Thu Apr 15 11:56:00 2004 From: linuxbios at matter.net (Larry Matter) Date: Thu Apr 15 11:56:00 2004 Subject: "IP-Config: Failed to open eth0" on epia-m Message-ID: <33682.192.168.1.140.1082048876.squirrel@mail.matter.net> sorry if this is off-topic for this list: I just started trying linuxbios because I am unhappy with how long it takes the standard bios to boot over pxe (though it does work nicely). I have built linuxbios from cvs from 8-apr and used etherboot 5.0.8 as the payload. This works and etherboot succesfully loads my kernel (2.4.22) from my tftp server. The kernel however, fails to open eth0 and so the nfs mount of my root parition fails, etc. The exact same kernel with (almost) identical command line, booted over pxe works just fine. I diff'd the output of the kernel startup and found a few things that might be significant: linuxBIOS/etherboot: via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker http://www.scyld.com/network/via-rhine.html PCI: No IRQ known for interrupt pin A of device 00:12.0. Please try using pci=biosirq. eth0: VIA VT6102 Rhine-II at 0x1400, 00:40:63:d4:17:70, IRQ 0. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. Via BIOS/PXE: via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker http://www.scyld.com/network/via-rhine.html eth0: VIA VT6102 Rhine-II at 0xec00, 00:40:63:d4:17:70, IRQ 5. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. I say "almost" exact same command line because PXE appends "BOOT_IMA" to it, not sure why. I've googled as much as I know how and have not found anything relevent. If anyone has any ideas I would appreciate it. Thanks, Larry Matter From dwh at lanl.gov Thu Apr 15 15:21:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Apr 15 15:21:00 2004 Subject: "IP-Config: Failed to open eth0" on epia-m In-Reply-To: <33682.192.168.1.140.1082048876.squirrel@mail.matter.net> Message-ID: Uh oh, I think this was another consequence of a broken pci-irq.c file in the Linux source. If you look in your arch/i386/kernel/pci-irq.c, get rid of the xor in the pirq_cyrix_get and pirq_cyrix_set functions like so: static int pirq_cyrix_get(struct pci_dev *router, struct pci_dev *dev, i nt pirq) { return read_config_nybble(router, 0x5C, (pirq-1)/*^1*/); } static int pirq_cyrix_set(struct pci_dev *router, struct pci_dev *dev, i nt pirq, int irq) { write_config_nybble(router, 0x5C, (pirq-1)/*^1*/, irq); return 1; } Recompile your kernel, replace your image, and see what happens. On Thu, 15 Apr 2004, Larry Matter wrote: > sorry if this is off-topic for this list: > > I just started trying linuxbios because I am unhappy with how long it > takes the standard bios to boot over pxe (though it does work nicely). > > I have built linuxbios from cvs from 8-apr and used etherboot 5.0.8 as the > payload. This works and etherboot succesfully loads my kernel (2.4.22) > from my tftp server. The kernel however, fails to open eth0 and so the > nfs mount of my root parition fails, etc. > > The exact same kernel with (almost) identical command line, booted over > pxe works just fine. I diff'd the output of the kernel startup and found > a few things that might be significant: > > linuxBIOS/etherboot: > > via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker > http://www.scyld.com/network/via-rhine.html > PCI: No IRQ known for interrupt pin A of device 00:12.0. Please try using > pci=biosirq. > eth0: VIA VT6102 Rhine-II at 0x1400, 00:40:63:d4:17:70, IRQ 0. > eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. > > > Via BIOS/PXE: > > via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker > http://www.scyld.com/network/via-rhine.html > eth0: VIA VT6102 Rhine-II at 0xec00, 00:40:63:d4:17:70, IRQ 5. > eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. > > I say "almost" exact same command line because PXE appends "BOOT_IMA" to > it, not sure why. > > I've googled as much as I know how and have not found anything relevent. > If anyone has any ideas I would appreciate it. > > Thanks, > Larry Matter > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Thu Apr 15 16:09:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 15 16:09:01 2004 Subject: "IP-Config: Failed to open eth0" on epia-m In-Reply-To: <33682.192.168.1.140.1082048876.squirrel@mail.matter.net> Message-ID: On Thu, 15 Apr 2004, Larry Matter wrote: > sorry if this is off-topic for this list: > > I just started trying linuxbios because I am unhappy with how long it > takes the standard bios to boot over pxe (though it does work nicely). I have also just built a linuxbios, and it gets to filo and is fine ... but I STILL have the damned 'half baud rate' bug for anyone who has the fix. Dave Ashley fixed this I think. > via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker > http://www.scyld.com/network/via-rhine.html > PCI: No IRQ known for interrupt pin A of device 00:12.0. Please try using > pci=biosirq. > eth0: VIA VT6102 Rhine-II at 0x1400, 00:40:63:d4:17:70, IRQ 0. > eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. the IRQ is not getting set correctly, I will look at this too. ron From rminnich at lanl.gov Thu Apr 15 16:16:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 15 16:16:00 2004 Subject: "IP-Config: Failed to open eth0" on epia-m In-Reply-To: Message-ID: On Thu, 15 Apr 2004, Hendricks David W. wrote: > Uh oh, I think this was another consequence of a broken pci-irq.c file in > the Linux source. If you look in your arch/i386/kernel/pci-irq.c, > get rid of the xor in the pirq_cyrix_get and pirq_cyrix_set functions like > so: > static int pirq_cyrix_get(struct pci_dev *router, struct pci_dev > *dev, i > nt pirq) { > return read_config_nybble(router, 0x5C, (pirq-1)/*^1*/); > } > > static int pirq_cyrix_set(struct pci_dev *router, struct pci_dev > *dev, i > nt pirq, int irq) { > write_config_nybble(router, 0x5C, (pirq-1)/*^1*/, irq); > return 1; > } > > Recompile your kernel, replace your image, and see what happens. I don't think this is it, since cyrix is geode stuff. I am not sure what it is though. Do you want to send David and me the whole serial output? ron From rminnich at lanl.gov Thu Apr 15 18:28:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 15 18:28:01 2004 Subject: epia-m Message-ID: I have, I hope, synced Dave Ashley's and Dmitry's changes into the current V1 tree in a sane way. Filo is working as a payload. VGA bios does something but the screen is quite scrambled. Linux boots from IDE-FLASH but the baud rate is pretty wrong. The 'x2' baud rate problem is still there; anyone recall this fix? Syncing my tree to Dave's did not do the trick. Anyone who does epia-m can take a look. Dmitry there were a few things you did which were not quite kosher for the linuxbios tree, but overall everything you sent is in there. ron From rminnich at lanl.gov Thu Apr 15 18:40:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 15 18:40:01 2004 Subject: epia-m video came up this time. Message-ID: Hmm, one more power cycle and I got video console. Well, that's pretty nice! ron From jbors at mail.ru Thu Apr 15 19:07:01 2004 From: jbors at mail.ru (=?koi8-r?Q?=22?=Dmitry Borisov=?koi8-r?Q?=22=20?=) Date: Thu Apr 15 19:07:01 2004 Subject: epia-m video came up this time. In-Reply-To: Message-ID: You see Ron, If you don't do changes in hardwaremain, it won't show the graphic console. The order in which it calls VGA bios does not make sense to show the splash( it is actually almost the last call ). The splash itself somewhere in a middle relying on internal VGA initialization... If you can suggest something that works it would be great. Dmitry/ -----Original Message----- Subject: epia-m video came up this time. > > Hmm, one more power cycle and I got video console. Well, that's pretty > nice! > > ron > From rminnich at lanl.gov Thu Apr 15 22:15:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 15 22:15:01 2004 Subject: epia-m video came up this time. In-Reply-To: Message-ID: I will try out moving the code around as your patch suggest. I don't expect it will cause trouble. ron From linuxbios at matter.net Thu Apr 15 23:13:01 2004 From: linuxbios at matter.net (Larry Matter) Date: Thu Apr 15 23:13:01 2004 Subject: "IP-Config: Failed to open eth0" on epia-m In-Reply-To: References: <33682.192.168.1.140.1082048876.squirrel@mail.matter.net> Message-ID: <1138.192.168.1.137.1082089547.squirrel@mail.matter.net> > but I STILL have the damned 'half baud rate' bug for anyone who has the > fix. > > Dave Ashley fixed this I think. I'm *so* glad you mentioned that. It was driving me nucking futs. I found a post from Dave that at least mentions how to get around it. Now I can send you that output... Larry p.s., here is the post if you joined the list late like me: http://www.clustermatic.org/pipermail/linuxbios/2003-December/006195.html From stepan at openbios.org Fri Apr 16 04:59:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 16 04:59:00 2004 Subject: LinuxBios "official" requirements and ROM building again In-Reply-To: <1081937127.16994.7.camel@Calliphara> References: <1081937127.16994.7.camel@Calliphara> Message-ID: <20040416101236.GA21621@openbios.org> * Mathieu Deschamps [040414 12:05]: > I've ty to build rom on a other Machine with RH9 try switching the language to english before building: export LANG="" > endly, I get confused Stefan : you said you made it with > python-2.3.3-65 and then you said "Anything older than 2.1 won't work." > I must have dropped the purse before the coin would:) yes. 2.3.3 is newer than 2.1. Anything older than 2.1 won't work. Where's the problem? Stefan From stepan at openbios.org Fri Apr 16 05:07:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 16 05:07:01 2004 Subject: ????: FILO 0.4 [PMX:#] In-Reply-To: <3174569B9743D511922F00A0C943142304B860F8@TYANWEB> References: <3174569B9743D511922F00A0C943142304B860F8@TYANWEB> Message-ID: <20040416102001.GD21621@openbios.org> * YhLu [040413 02:53]: > I just find the fifo can boot the elfimage in the rom. > > If the etherboot is put in the beginning, > Use > boot:mem at 0xfff80000 > can load the Etherboot. Just an idea. We could store the start addresses of the different payloads (maybe also an identifier) into the LinuxBIOS table. Then any payload knowing this information can easily switch to another payload or list available payloads. Stefan From stepan at openbios.org Fri Apr 16 06:57:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 16 06:57:00 2004 Subject: FILO features request In-Reply-To: <20040414153749.GA6011@tsn.or.jp> References: <3174569B9743D511922F00A0C943142304B8613C@TYANWEB> <20040414153749.GA6011@tsn.or.jp> Message-ID: <20040416121029.GA22667@openbios.org> * Takeshi Sone [040414 17:37]: > On Tue, Apr 13, 2004 at 09:50:55AM -0700, YhLu wrote: > > I hope it can > > 1. understand grub.conf in HD --- and append console=tty0 > > console=ttyS0,115200 automatically > > 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and > > append console=tty0 console=ttyS0,115200 automatically > > I don't like the idea to have compatibility to existing bootloaders. > It sounds like a beginning of nightmare. Not necessarily. One could do this modular, just like the sound drivers are now.. :) > Instead, Linux CDs can directly support FILO. > Boot CDs can have /boot/filo.conf, and installers can > generate /boot/filo.conf in the installed hard disk. > It's technically easy. > Stefan Reinauer was positive to add this support to SuSE's installation > CD when I talked to him about this issue. For the user interface, one could go the way with modular code, too. Elilo, the EFI boot loader, does a nice thing there. It has a "chooser" interface, allowing several user interfaces. Each user interface has a name, a probe function and a choose function. The probe function can check whether the current chooser works on the current machine (on Itanic this could be checking UGA availability before trying to show a graphical menu) > Maybe, we can make FILO to have the default config file in ROM, which > includes the filo.conf from boot device (CD or HD). > So the config file in ROM knows how to boot Etherboot in ROM. > But this is too complicated at the moment. How would that config file have to look? Something similar to the grub menu.lst would be fitting, wouldn't it? title Linux kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 console=ttyS0,115200n8 initrd (hd0,0)/boot/initrd Stefan From stepan at openbios.org Fri Apr 16 07:02:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 16 07:02:00 2004 Subject: FILO features request In-Reply-To: References: <20040414153749.GA6011@tsn.or.jp> Message-ID: <20040416121510.GB22667@openbios.org> * ron minnich [040414 23:34]: > I really am not enthusiastic about turning filo back into grub. I think the idea is great, honestly. The menu/user interface code is not grub's weakness. Neither is the config file syntax. What started out with a half-ways clean design was just featurized beyound reusability. Stefan From linuxbios at xdr.com Fri Apr 16 08:20:01 2004 From: linuxbios at xdr.com (Dave Ashley) Date: Fri Apr 16 08:20:01 2004 Subject: epia-m 1/2 baud rate fix Message-ID: <200404161332.i3GDWuUq023760@xdr.com> The post for fixing the 1/2 baud rate problem on epia-m is here: http://www.clustermatic.org/pipermail/linuxbios/2003-December/006207.html The earlier post mentioned probably had the setserial workaround but this is no good, you don't get 115200 baud or other baud rates that don't go into 57,600 exactly (like 38,400). I'm on vacation this past week in Florida so haven't been able to assist any on the epia-m work. One thing I noticed in Dmitri's patch is it seemed to cut out all my code to initialize the VT1211's hardware monitor (used for temperature + voltage monitoring). Other stuff seemed to be hacked and slashed out that I found necessary, but didn't appear to be replaced elsewhere. When I get back to the office hopefully I can do a cvs checkout of latest version and give it a shot and see if it works for me. It sounds like it is working for everyone else right now, which is good news, so congrats all around. So if it's this far along, it would be nice to get the SPD auto detection working. Maybe the path to that is integrate all these V1 changes into V2 and do it in V2. -Dave From rminnich at lanl.gov Fri Apr 16 08:43:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 08:43:01 2004 Subject: "IP-Config: Failed to open eth0" on epia-m In-Reply-To: <1138.192.168.1.137.1082089547.squirrel@mail.matter.net> Message-ID: I even found the fix Dave posted, in C, and am figuring out the best way to apply it. ron From rminnich at lanl.gov Fri Apr 16 09:04:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 09:04:00 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: <200404161332.i3GDWuUq023760@xdr.com> Message-ID: On Fri, 16 Apr 2004, Dave Ashley wrote: > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltage monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. don't worry. I did not apply the patch Dmitri sent. I just used it as a guide to the actual changes I made. All your stuff is still in there. Check the CVS and you should see your stuff intact. I really need that serial port patch though. > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. That's the next step. Once you bless this V1 port, I start the V2 port. That will become the port of choice for EPIA-M. I'll need some help with that one ... this is a time-available thing for me right now, but I'm giving it all the time I can. ron From rminnich at lanl.gov Fri Apr 16 09:12:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 09:12:01 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: <200404161332.i3GDWuUq023760@xdr.com> Message-ID: On Fri, 16 Apr 2004, Dave Ashley wrote: > The post for fixing the 1/2 baud rate problem on epia-m is here: > http://www.clustermatic.org/pipermail/linuxbios/2003-December/006207.html OK, this fix is in the tree, build works, so I've committed it. I think it should work fine, but I'm still home, will test as soon as I get in. ron From rminnich at lanl.gov Fri Apr 16 10:01:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 10:01:01 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: Message-ID: On Fri, 16 Apr 2004, ron minnich wrote: > On Fri, 16 Apr 2004, Dave Ashley wrote: > > > The post for fixing the 1/2 baud rate problem on epia-m is here: > > http://www.clustermatic.org/pipermail/linuxbios/2003-December/006207.html > > OK, this fix is in the tree, build works, so I've committed it. I think it > should work fine, but I'm still home, will test as soon as I get in. The fix works fine. Now if only Linux, once loaded, would show reasonable output on the serial port. Weird. ron From stepan at openbios.org Fri Apr 16 10:12:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 16 10:12:00 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: References: Message-ID: <20040416152517.GA24441@openbios.org> * ron minnich [040416 17:13]: > > OK, this fix is in the tree, build works, so I've committed it. I think it > > should work fine, but I'm still home, will test as soon as I get in. > > The fix works fine. > > Now if only Linux, once loaded, would show reasonable output on the serial > port. Weird. What's the problem? I had something similar with my geode box at home. As soon as Linux 2.6 tries to initialize the serial port, the serial console breaks away, hanging the system. Could not resolve this until now Stefan From rminnich at lanl.gov Fri Apr 16 10:29:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 10:29:00 2004 Subject: epia-m 1/2 vga In-Reply-To: Message-ID: Dmitry, I can not not move the vga stuff before final_mainboard_fixup -- it won't work if I do. I think in general hardwaremain should wait to touch VGA until this point. You can take a look at CVS if you want and see what to fix in epia-m to make this go. Serial port now works fine at the right speeds. Dave, see what you think of CVS. Filo works fine, but I can not yet elfboot a kernel image from IDE-FLASH. The kernel just prints lots of ????????????? and eventually blows up. Weird. I can't get to a baud rate setting that works. I gotta go do some paying work, and I want to see what you all think of the current state of things anyway, so please get back to me and let me know how it all looks. ron From rminnich at lanl.gov Fri Apr 16 10:32:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 10:32:01 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: <20040416152517.GA24441@openbios.org> Message-ID: On Fri, 16 Apr 2004, Stefan Reinauer wrote: > What's the problem? I had something similar with my geode box at home. > As soon as Linux 2.6 tries to initialize the serial port, the serial > console breaks away, hanging the system. Could not resolve this until > now I don't know, but with vga console working I hope to have a linux that will drive vga console, allowing me to debug serial port. Monday. ron From jbors at mail.ru Fri Apr 16 11:05:01 2004 From: jbors at mail.ru (Dmitry Borisov) Date: Fri Apr 16 11:05:01 2004 Subject: epia-m 1/2 vga References: Message-ID: <011201c423ce$5b02ecd0$0900a8c0@amr.corp.intel.com> No problem, We might just do some temporary hack for EPIA-M only and leave it as a voluntary patch. The splash screen is a really nice thing for embedded devices. I can update HOWTO with this information. Dmitry/ ----- Original Message ----- Subject: Re: epia-m 1/2 vga > > Dmitry, I can not not move the vga stuff before final_mainboard_fixup -- > it won't work if I do. I think in general hardwaremain should wait to > touch VGA until this point. > From mdeschamps at mangrove-systems.com Fri Apr 16 11:19:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Fri Apr 16 11:19:01 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: <200404161332.i3GDWuUq023760@xdr.com> References: <200404161332.i3GDWuUq023760@xdr.com> Message-ID: <1082132860.23851.57.camel@Calliphara> Hello LinuxBios fellows, I know i'am a bit asking for trouble in what i like but if not trying to someone else will anyway (as i've read). I'am trying to bring this fix smbenablebus.inc into v2, following advices and notices of Dave by build time i got : /mainboard/via/epia/smbus.inc: Assembler message: smbus.inc:49:Error: invalid character "_" in mnemonic smbus.inc:50:Error: invalid character "_" in mnemonic smbus.inc:51:Error: invalid character "_" in mnemonic crt0.S:155:Warning: inderect jmp without '*' make[1]: *** [crt0.o] Error 1 make[1]: *** [fallback-rom] Error 1 It stops in 51 in smbus.inc but there are other mnemonics with this char... A out-of-the-bit question : I've noticed that we're building a fallbackrom, and i found the concept unavoidable and very interesting, but does/should it needs all the capabilities a normal rom has ? (for example half rate would be enough, you know thinking let's try not to give it too much reasons to break down:-) Indeed i thought fallback rom was some kind of in-case-of-emergency-boot-anyway-please.. just enough abilities some we can repair the normal rom to boot up back from. Well it just a something that passed by me... Have nice week-end. mathieu Le ven 16/04/2004 ? 15:32, Dave Ashley a ?crit : > The post for fixing the 1/2 baud rate problem on epia-m is here: > http://www.clustermatic.org/pipermail/linuxbios/2003-December/006207.html > > The earlier post mentioned probably had the setserial workaround but this > is no good, you don't get 115200 baud or other baud rates that don't go into > 57,600 exactly (like 38,400). > > I'm on vacation this past week in Florida so haven't been able to assist > any on the epia-m work. > > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltage monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. > > When I get back to the office hopefully I can do a cvs checkout of latest > version and give it a shot and see if it works for me. It sounds like it > is working for everyone else right now, which is good news, so congrats all > around. > > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. > > -Dave > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >On Fri, 16 Apr 2004, Dave Ashley wrote: > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltageOn Fri, 16 Apr 2004, Dave Ashley wrote: > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltage monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. don't worry. I did not apply the patch Dmitri sent. I just used it as a guide to the actual changes I made. All your stuff is still in there. Check the CVS and you should see your stuff intact. I really need that serial port patch though. > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. That's the next step. Once you bless this V1 port, I start the V2 port. That will become the port of choice for EPIA-M. I'll needOn Fri, 16 Apr 2004, Dave Ashley wrote: > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltage monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. don't worry. I did not apply the patch Dmitri sent. I just used it as a guide to the actual changes I made. All your stuff is still in there. Check the CVS and you should see your stuff intact. I really need that serial port patch though. > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. That's the next step. Once you bless this V1 port, I start the V2 port. That will become the port of choice for EPIA-M. I'll need some help with that one ... this is a time-available thing for me right now, but I'm giving it all the time I can. ron some help with that one ... this is a time-available thing for me right now, but I'm giving it all the time I can. ron monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. >don't worry. I did not apply the patch Dmitri sent. I just used it as a >guide to the actual changes I made. All your stuff is still in there. >Check the CVS and you should see your stuff intact. I really need that >serial port patch though. > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. >That's the next step. Once you bless this V1 port, I start the V2 port. >That will become the port of choice for EPIA-M. >I'll need some help with that one ... this is a time-available thing for >me right now, but I'm giving it all the time I can. >ron From mdeschamps at mangrove-systems.com Fri Apr 16 11:22:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Fri Apr 16 11:22:00 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: <200404161332.i3GDWuUq023760@xdr.com> References: <200404161332.i3GDWuUq023760@xdr.com> Message-ID: <1082132860.23851.57.camel@Calliphara> Hello LinuxBios fellows, I know i'am a bit asking for trouble in what i like but if not trying to someone else will anyway (as i've read). I'am trying to bring this fix smbenablebus.inc into v2, following advices and notices of Dave by build time i got : /mainboard/via/epia/smbus.inc: Assembler message: smbus.inc:49:Error: invalid character "_" in mnemonic smbus.inc:50:Error: invalid character "_" in mnemonic smbus.inc:51:Error: invalid character "_" in mnemonic crt0.S:155:Warning: inderect jmp without '*' make[1]: *** [crt0.o] Error 1 make[1]: *** [fallback-rom] Error 1 It stops in 51 in smbus.inc but there are other mnemonics with this char... A out-of-the-bit question : I've noticed that we're building a fallbackrom, and i found the concept unavoidable and very interesting, but does/should it needs all the capabilities a normal rom has ? (for example half rate would be enough, you know thinking let's try not to give it too much reasons to break down:-) Indeed i thought fallback rom was some kind of in-case-of-emergency-boot-anyway-please.. just enough abilities some we can repair the normal rom to boot up back from. Well it just a something that passed by me... Have nice week-end. mathieu Le ven 16/04/2004 ? 15:32, Dave Ashley a ?crit : > The post for fixing the 1/2 baud rate problem on epia-m is here: > http://www.clustermatic.org/pipermail/linuxbios/2003-December/006207.html > > The earlier post mentioned probably had the setserial workaround but this > is no good, you don't get 115200 baud or other baud rates that don't go into > 57,600 exactly (like 38,400). > > I'm on vacation this past week in Florida so haven't been able to assist > any on the epia-m work. > > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltage monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. > > When I get back to the office hopefully I can do a cvs checkout of latest > version and give it a shot and see if it works for me. It sounds like it > is working for everyone else right now, which is good news, so congrats all > around. > > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. > > -Dave > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >On Fri, 16 Apr 2004, Dave Ashley wrote: > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltageOn Fri, 16 Apr 2004, Dave Ashley wrote: > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltage monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. don't worry. I did not apply the patch Dmitri sent. I just used it as a guide to the actual changes I made. All your stuff is still in there. Check the CVS and you should see your stuff intact. I really need that serial port patch though. > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. That's the next step. Once you bless this V1 port, I start the V2 port. That will become the port of choice for EPIA-M. I'll needOn Fri, 16 Apr 2004, Dave Ashley wrote: > One thing I noticed in Dmitri's patch is it seemed to cut out all my > code to initialize the VT1211's hardware monitor (used for temperature + > voltage monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. don't worry. I did not apply the patch Dmitri sent. I just used it as a guide to the actual changes I made. All your stuff is still in there. Check the CVS and you should see your stuff intact. I really need that serial port patch though. > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. That's the next step. Once you bless this V1 port, I start the V2 port. That will become the port of choice for EPIA-M. I'll need some help with that one ... this is a time-available thing for me right now, but I'm giving it all the time I can. ron some help with that one ... this is a time-available thing for me right now, but I'm giving it all the time I can. ron monitoring). Other stuff seemed to be hacked and slashed out that > I found necessary, but didn't appear to be replaced elsewhere. >don't worry. I did not apply the patch Dmitri sent. I just used it as a >guide to the actual changes I made. All your stuff is still in there. >Check the CVS and you should see your stuff intact. I really need that >serial port patch though. > So if it's this far along, it would be nice to get the SPD auto detection > working. Maybe the path to that is integrate all these V1 changes into V2 > and do it in V2. >That's the next step. Once you bless this V1 port, I start the V2 port. >That will become the port of choice for EPIA-M. >I'll need some help with that one ... this is a time-available thing for >me right now, but I'm giving it all the time I can. >ron From rminnich at lanl.gov Fri Apr 16 11:24:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 11:24:00 2004 Subject: epia-m 1/2 vga In-Reply-To: <011201c423ce$5b02ecd0$0900a8c0@amr.corp.intel.com> Message-ID: On Fri, 16 Apr 2004, Dmitry Borisov wrote: > No problem, > We might just do some temporary hack for EPIA-M only and leave it as a > voluntary patch. > The splash screen is a really nice thing for embedded devices. I can update > HOWTO with this information. send HOWTO, please look at CVS and see if you can get splash screen working and send me a patch. ron From rminnich at lanl.gov Fri Apr 16 11:25:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 11:25:01 2004 Subject: epia-m 1/2 baud rate fix In-Reply-To: <1082132860.23851.57.camel@Calliphara> Message-ID: On 16 Apr 2004, Mathieu Deschamps wrote: > I'am trying to bring this fix smbenablebus.inc into v2, following > advices and notices of Dave don't do this. Just wait until we're all happy with V1, I will build a V2 version. If you are using .inc files you're going the WRONG direction. ron From ollie at lanl.gov Fri Apr 16 11:55:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Fri Apr 16 11:55:01 2004 Subject: Broadcom NIC, MPTable and APIC ID for HDAMA Message-ID: <1082135237.5334.2651.camel@exponential.lanl.gov> Eric, The broadcom nic on hdama is connected behind the 8131. So the IRQ should be routed by the APIC on 8131, right ? But in the current mptable.c it is /* PCI Ints: Type Polarity Trigger Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ /* On board nics */ smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x03<<2)|0, 0x02, 0x13); smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x04<<2)|0, 0x02, 0x13); The IRQ is routed by APIC #2 which is in 8111. Is it correct ? Why is it still working ? Ollie From YhLu at tyan.com Fri Apr 16 12:03:50 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 16 12:03:50 2004 Subject: =?GB2312?B?tPC4tDogQnJvYWRjb20gTklDLCBNUFRhYmxlIGFuZCBBUElDIElE?= =?GB2312?B?IGZvciBIREFNQQ==?= Message-ID: <3174569B9743D511922F00A0C943142304B863A9@TYANWEB> That's decided by HW. YH -----????----- ???: Li-Ta Lo [mailto:ollie at lanl.gov] ????: 2004?4?16? 10:07 ???: Eric Biederman; LinuxBIOS ??: Broadcom NIC, MPTable and APIC ID for HDAMA Eric, The broadcom nic on hdama is connected behind the 8131. So the IRQ should be routed by the APIC on 8131, right ? But in the current mptable.c it is /* PCI Ints: Type Polarity Trigger Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ /* On board nics */ smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x03<<2)|0, 0x02, 0x13); smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, bus_8131_1, (0x04<<2)|0, 0x02, 0x13); The IRQ is routed by APIC #2 which is in 8111. Is it correct ? Why is it still working ? Ollie _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Fri Apr 16 14:10:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 14:10:01 2004 Subject: epia-m IRQ routing Message-ID: kernel 2.4.25 can't use the PIRQ table on epia-m. I think the table is right. Anyone know if the 2.4.25 kernel can handle this router on this board? This is the last hold-up: ethernet irq is not working out. 'No IRQ found ...' ron From YhLu at tyan.com Fri Apr 16 14:56:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 16 14:56:00 2004 Subject: =?GB2312?B?tPC4tDogZXBpYS1tIElSUSByb3V0aW5n?= Message-ID: <3174569B9743D511922F00A0C943142304B863CC@TYANWEB> Why just try 2.4.26? Only tg3.c has problem in opteron MB. YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?16? 12:22 ???: linuxbios at clustermatic.org ??: epia-m IRQ routing kernel 2.4.25 can't use the PIRQ table on epia-m. I think the table is right. Anyone know if the 2.4.25 kernel can handle this router on this board? This is the last hold-up: ethernet irq is not working out. 'No IRQ found ...' ron _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Fri Apr 16 15:44:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 15:44:00 2004 Subject: =?GB2312?B?tPC4tDogZXBpYS1tIElSUSByb3V0aW5n?= In-Reply-To: <3174569B9743D511922F00A0C943142304B863CC@TYANWEB> Message-ID: On Fri, 16 Apr 2004, YhLu wrote: > Why just try 2.4.26? I'm stuck to this version for now. I can't try .26 ron From YhLu at tyan.com Fri Apr 16 15:45:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 16 15:45:00 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogZXBpYS1tIElSUSByb3V0aW5n?= Message-ID: <3174569B9743D511922F00A0C943142304B863D2@TYANWEB> 2.4.22 is the most stabe one. -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?16? 13:56 ???: YhLu ??: linuxbios at clustermatic.org ??: Re: ??: epia-m IRQ routing On Fri, 16 Apr 2004, YhLu wrote: > Why just try 2.4.26? I'm stuck to this version for now. I can't try .26 ron From ollie at lanl.gov Fri Apr 16 16:30:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Fri Apr 16 16:30:01 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= Broadcom NIC, MPTable and APIC ID for HDAMA [PMX:#] In-Reply-To: <3174569B9743D511922F00A0C943142304B863A9@TYANWEB> References: <3174569B9743D511922F00A0C943142304B863A9@TYANWEB> Message-ID: <1082151746.5334.2653.camel@exponential.lanl.gov> On Fri, 2004-04-16 at 11:21, YhLu wrote: > That's decided by HW. > Do you mean even the device is behind the PCIX bridge, it's IRQ is not routed by the APIC on the bridge ? Ollie > YH > > -----????----- > ???: Li-Ta Lo [mailto:ollie at lanl.gov] > ????: 2004?4?16? 10:07 > ???: Eric Biederman; LinuxBIOS > ??: Broadcom NIC, MPTable and APIC ID for HDAMA > > Eric, > > The broadcom nic on hdama is connected behind the 8131. > So the IRQ should be routed by the APIC on 8131, right ? > But in the current mptable.c it is > > /* PCI Ints: Type Polarity > Trigger > Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ > /* On board nics */ > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, (0x03<<2)|0, 0x02, 0x13); > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, > (0x04<<2)|0, 0x02, 0x13); > > The IRQ is routed by APIC #2 which is in 8111. Is it correct ? > Why is it still working ? > > Ollie > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Fri Apr 16 16:32:01 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 16 16:32:01 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogQnJvYWRjb20gTklDLCBNUFRhYmxlIGFuZCBB?= =?GB2312?B?UElDIElEIGZvciBIREFNQSBbUE1YOiNd?= Message-ID: <3174569B9743D511922F00A0C943142304B863D6@TYANWEB> The arima's PCI-X ioapic is poorly connected. -----????----- ???: Li-Ta Lo [mailto:ollie at lanl.gov] ????: 2004?4?16? 14:42 ???: YhLu ??: Eric Biederman; LinuxBIOS ??: Re: ??: Broadcom NIC, MPTable and APIC ID for HDAMA [PMX:#] On Fri, 2004-04-16 at 11:21, YhLu wrote: > That's decided by HW. > Do you mean even the device is behind the PCIX bridge, it's IRQ is not routed by the APIC on the bridge ? Ollie > YH > > -----????----- > ???: Li-Ta Lo [mailto:ollie at lanl.gov] > ????: 2004?4?16? 10:07 > ???: Eric Biederman; LinuxBIOS > ??: Broadcom NIC, MPTable and APIC ID for HDAMA > > Eric, > > The broadcom nic on hdama is connected behind the 8131. > So the IRQ should be routed by the APIC on 8131, right ? > But in the current mptable.c it is > > /* PCI Ints: Type Polarity > Trigger > Bus ID PCIDEVNUM|IRQ APIC ID PIN# */ > /* On board nics */ > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, (0x03<<2)|0, 0x02, 0x13); > smp_write_intsrc(mc, mp_INT, > MP_IRQ_TRIGGER_DEFAULT|MP_IRQ_POLARITY_DEFAULT, > bus_8131_1, > (0x04<<2)|0, 0x02, 0x13); > > The IRQ is routed by APIC #2 which is in 8111. Is it correct ? > Why is it still working ? > > Ollie > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From steve at nexpath.com Fri Apr 16 16:50:01 2004 From: steve at nexpath.com (Steve Gehlbach) Date: Fri Apr 16 16:50:01 2004 Subject: epia-m IRQ routing In-Reply-To: References: Message-ID: <40804C65.10008@nexpath.com> > kernel 2.4.25 can't use the PIRQ table on epia-m. I think the table is > right. Anyone know if the 2.4.25 kernel can handle this router on this > board? Do we have enough info to route the irq in the bridge chip in linuxbios, assuming the kernel doesn't know about epia-m? If so, you can set the upper bit(s) in the link byte in the irq table and linux will use it as pre-routed. No kernel patch needed. See v1 /src/mainboard/stpc/consumer2; I did this for the stpc. -Steve From twocats at hotmail.com Fri Apr 16 17:39:01 2004 From: twocats at hotmail.com (Thomas Spear) Date: Fri Apr 16 17:39:01 2004 Subject: flash_rom Problem Message-ID: This is what happens when I try to build flash_rom: root@(none):/home/freebios2/util/flash_and_burn# make gcc -O2 -g -Wall -Werror -c -o flash_rom.o flash_rom.c gcc -O2 -g -Wall -Werror -c -o flash_enable.o flash_enable.c flash_enable.c:3: pci/pci.h: No such file or directory make: *** [flash_enable.o] Error 1 Someone please tell what I've done wrong. Where does "pci/pci.h" come from? The romimage seems to build ok (I don't really know since I can't flash the rom and try it). Thanks. _________________________________________________________________ From ollie at lanl.gov Fri Apr 16 18:04:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Fri Apr 16 18:04:01 2004 Subject: flash_rom Problem In-Reply-To: References: Message-ID: <1082157375.5334.2655.camel@exponential.lanl.gov> On Fri, 2004-04-16 at 16:51, Thomas Spear wrote: > This is what happens when I try to build flash_rom: > > root@(none):/home/freebios2/util/flash_and_burn# make > gcc -O2 -g -Wall -Werror -c -o flash_rom.o flash_rom.c > gcc -O2 -g -Wall -Werror -c -o flash_enable.o flash_enable.c > flash_enable.c:3: pci/pci.h: No such file or directory > make: *** [flash_enable.o] Error 1 > > Someone please tell what I've done wrong. Where does "pci/pci.h" come from? > The romimage seems to build ok (I don't really know since I can't flash > the rom and try it). > you need to install the pci-devel rpm. Ollie > Thanks. > > _________________________________________________________________ > >From must-see cities to the best beaches, plan a getaway with the Spring > Travel Guide! http://special.msn.com/local/springtravel.armx > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Fri Apr 16 18:15:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 18:15:01 2004 Subject: epia-m IRQ routing In-Reply-To: <40804C65.10008@nexpath.com> Message-ID: On Fri, 16 Apr 2004, Steve Gehlbach wrote: > Do we have enough info to route the irq in the bridge chip in linuxbios, > assuming the kernel doesn't know about epia-m? yes, we do. We're going to fix this. We went ahead and patched linux for the VIA however for now. Linux is up and running with vga on the epia-m. The V2 port starts next week. Greg is going to start by putting the skeleton code in the V2 tree. ron From rminnich at lanl.gov Fri Apr 16 18:16:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 16 18:16:00 2004 Subject: flash_rom Problem In-Reply-To: Message-ID: what system? We've seen that non-redhat systems don't ship with pci utils, so /usr/include/pci/pci.h is not there. SuSE is one example. ron From stepan at openbios.org Fri Apr 16 18:32:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 16 18:32:01 2004 Subject: flash_rom Problem In-Reply-To: References: Message-ID: <20040416234553.GA7834@openbios.org> * ron minnich [040417 01:28]: > > what system? We've seen that non-redhat systems don't ship with pci utils, > so /usr/include/pci/pci.h is not there. SuSE is one example. SuSE has an extra RPM for pciutils-devel. Per default only pciutils is installed. Stefan From ts1 at tsn.or.jp Sun Apr 18 08:42:00 2004 From: ts1 at tsn.or.jp (Takeshi Sone) Date: Sun Apr 18 08:42:00 2004 Subject: FILO features request In-Reply-To: <20040416121029.GA22667@openbios.org> References: <3174569B9743D511922F00A0C943142304B8613C@TYANWEB> <20040414153749.GA6011@tsn.or.jp> <20040416121029.GA22667@openbios.org> Message-ID: <20040418135508.GB32423@tsn.or.jp> On Fri, Apr 16, 2004 at 02:10:29PM +0200, Stefan Reinauer wrote: > For the user interface, one could go the way with modular code, too. > Elilo, the EFI boot loader, does a nice thing there. It has a "chooser" > interface, allowing several user interfaces. Each user interface has a > name, a probe function and a choose function. The probe function can > check whether the current chooser works on the current machine (on > Itanic this could be checking UGA availability before trying to show a > graphical menu) That sounds nice. > > Maybe, we can make FILO to have the default config file in ROM, which > > includes the filo.conf from boot device (CD or HD). > > So the config file in ROM knows how to boot Etherboot in ROM. > > But this is too complicated at the moment. > > How would that config file have to look? Something similar to the grub > menu.lst would be fitting, wouldn't it? > > title Linux > kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 console=ttyS0,115200n8 > initrd (hd0,0)/boot/initrd Similar, but not the same. Grub has many commands that FILO would never understand. -- Takeshi From wjjsun at eyou.com Mon Apr 19 00:45:01 2004 From: wjjsun at eyou.com (=?gb2312?B?zfW98L2h?=) Date: Mon Apr 19 00:45:01 2004 Subject: etherboot-5.2.4 linuxbios error! Message-ID: <282354249.19433@eyou.com> Dear sir: I want to use etherboot-5.2.4 under linuxbios, but when I comment -DPCBIOS and uncomment -DLINUX line in arch/i386/Config, I can not compile the source rightly!! the message as follow: ld -N -Ttext 0x20000 -T arch/i386/core/etherboot.lds -o bin/undi.tmp bin/start32.o bin/pcbios.o bin/memsizes.o bin/basemem.o bin/linuxbios.o bin/config.o bin/undi.o bin/bootlib.a bin/undi.o(.text+0x8b): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_end' bin/undi.o(.text+0x90): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_start' bin/undi.o(.text+0x96): In function `allocate_base_mem_data': : undefined reference to `allot_base_memory' bin/undi.o(.text+0xe9): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_end' bin/undi.o(.text+0xee): In function `allocate_base_mem_data': : undefined reference to `_trivial_irq_handler_start' bin/undi.o(.text+0x11d): In function `free_base_mem_data': : undefined reference to `_trivial_irq_handler_end' bin/undi.o(.text+0x122): In function `free_base_mem_data': : undefined reference to `_trivial_irq_handler_start' bin/undi.o(.text+0x129): In function `free_base_mem_data': : undefined reference to `forget_base_memory' bin/undi.o(.text+0x238): In function `shoot_targets': : undefined reference to `forget_base_memory' bin/undi.o(.text+0x376): In function `hunt_pixie': : undefined reference to `get_free_base_memory' bin/undi.o(.text+0x642): In function `undi_call_loader': : undefined reference to `__undi_call' bin/undi.o(.text+0x6c0): In function `undi_call_silent': : undefined reference to `__undi_call' bin/undi.o(.text+0x76e): In function `undi_loader': : undefined reference to `allot_base_memory' bin/undi.o(.text+0x7ba): In function `undi_loader': : undefined reference to `allot_base_memory' bin/undi.o(.text+0xdde): In function `undi_full_shutdown': : undefined reference to `forget_base_memory' bin/undi.o(.text+0xe12): In function `undi_full_shutdown': : undefined reference to `forget_base_memory' bin/bootlib.a(pic8259.o)(.text+0x251): In function `install_trivial_irq_handler': : undefined reference to `fake_irq' bin/bootlib.a(pic8259.o)(.text+0x35e): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_start' bin/bootlib.a(pic8259.o)(.text+0x367): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_end' bin/bootlib.a(pic8259.o)(.text+0x36c): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_start' bin/bootlib.a(pic8259.o)(.text+0x392): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_start' bin/bootlib.a(pic8259.o)(.text+0x397): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler_end' bin/bootlib.a(pic8259.o)(.text+0x3b2): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_handler' bin/bootlib.a(pic8259.o)(.text+0x3bd): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_trigger_count' bin/bootlib.a(pic8259.o)(.text+0x3c8): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_chain_to' bin/bootlib.a(pic8259.o)(.text+0x3d6): In function `copy_trivial_irq_handler': : undefined reference to `_trivial_irq_chain' bin/bootlib.a(pic8259.o)(.data+0x0): undefined reference to `_trivial_irq_handler' bin/bootlib.a(pic8259.o)(.data+0x4): undefined reference to `_trivial_irq_trigger_count' bin/bootlib.a(pic8259.o)(.data+0x8): undefined reference to `_trivial_irq_chain_to' bin/bootlib.a(pic8259.o)(.data+0xc): undefined reference to `_trivial_irq_chain' make: *** [bin/undi.tmp] Error 1 Can somebody help me! Thank you! wjjsun e-mail:wjjsun at eyou.com From linuxbios at xdr.com Mon Apr 19 15:58:01 2004 From: linuxbios at xdr.com (Dave Ashley) Date: Mon Apr 19 15:58:01 2004 Subject: EPIA-M build problem Message-ID: <200404192111.i3JLB8bk016150@xdr.com> I didn't get far: 1) CVS checkout latest 2) Take /freebios/src/mainboard/via/epia-m/example.config, A) comment out #payload /opt/cwlinux/etherboot/src/bin32/via-rhine.ebi towards bottom B) Note: There are 2 conflicting target lines, and 2 conflicting payload lines. 3) Run python config script: python /ram/freebios/util/config/NLBConfig.py example.config /ram/freebios/ (Worked ok, no errors) 4) Go into /ram/freebios/obj and do "make" 5) Fails with this: make: *** No rule to make target `/ram/freebios/src/mainboard/via/epia-m/earlysetup.inc', needed by `crt0.s'. Stop. Could it be a missing cvs commit? -Dave From linuxbios at xdr.com Mon Apr 19 17:12:01 2004 From: linuxbios at xdr.com (Dave Ashley) Date: Mon Apr 19 17:12:01 2004 Subject: epia-m IRQ issue Message-ID: <200404192225.i3JMP4rN016543@xdr.com> I've stuck in my own earlysetup.inc file and it works ok. My payload and my vgabios.bin seem to function but I'm dying inside linux because none of the IRQ's are assigned. I put in some debug code and the IRQ numbers in the pci configuration space don't seem to be getting set. For example the ethernet controller has IRQ 0 for its setting. There is no change to linux required to get this to work right, something is broken in linuxbios that was working before. PCI routing tables--I don't even really understand what these are, don't know if they apply here. Linux is scanning the pci config space to get the bios assigned irq's and they are probably all 0. -Dave From rminnich at lanl.gov Mon Apr 19 17:20:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 19 17:20:01 2004 Subject: EPIA-M build problem [PMX:#] In-Reply-To: <200404192111.i3JLB8bk016150@xdr.com> Message-ID: On Mon, 19 Apr 2004, Dave Ashley wrote: > Could it be a missing cvs commit? boy do I feel stupid! yes it is. SORRY. ron From rminnich at lanl.gov Mon Apr 19 17:23:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 19 17:23:00 2004 Subject: EPIA-M build problem [PMX:#] In-Reply-To: <200404192111.i3JLB8bk016150@xdr.com> Message-ID: sorry, Dave, it's committed. ron From rminnich at lanl.gov Mon Apr 19 17:29:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 19 17:29:01 2004 Subject: epia-m IRQ issue [PMX:#] In-Reply-To: <200404192225.i3JMP4rN016543@xdr.com> Message-ID: once more, shall we diff CVS and your tree? this is something simple, I know, just not sure what. ron From linuxbios at xdr.com Mon Apr 19 17:41:00 2004 From: linuxbios at xdr.com (Dave Ashley) Date: Mon Apr 19 17:41:00 2004 Subject: EPIA-M IRQ [FIXED] Message-ID: <200404192254.i3JMsigZ016733@xdr.com> >once more, shall we diff CVS and your tree? this is something simple, I >know, just not sure what. I fixed it by modifying this file freebios/src/mainboard/via/epia-m/mainboard.c Inside final_southbridge_fixup add this at the bottom of the function: pci_routing_fixup(); I've booted off this latest version with my payload + my vgabios.bin and have SVGA output working, mpeg-2 video playback working, audio out working, networking up, the pci-card we have in the epia-m functions fully. I think with this change it is good to go for V2. This doesn't require any changes in the linux ebi file I load with the etherboot payload. -Dave From rminnich at lanl.gov Mon Apr 19 17:47:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 19 17:47:00 2004 Subject: EPIA-M IRQ [FIXED] [PMX:#] In-Reply-To: <200404192254.i3JMsigZ016733@xdr.com> Message-ID: On Mon, 19 Apr 2004, Dave Ashley wrote: > I fixed it by modifying this file > freebios/src/mainboard/via/epia-m/mainboard.c > Inside final_southbridge_fixup add this at the bottom of the function: > pci_routing_fixup(); committed, cvs update and try again, and thanks for your patience. ron From linuxbios at xdr.com Mon Apr 19 17:52:01 2004 From: linuxbios at xdr.com (Dave Ashley) Date: Mon Apr 19 17:52:01 2004 Subject: EPIA-M IRQ cvs update Message-ID: <200404192305.i3JN5688016811@xdr.com> >committed, cvs update and try again, and thanks for your patience. I tried this but none of your recent cvs commits are visible (the earlysetup.inc or the mainboard.c change). Remember I'm still just using the pond-scum cvs server: cvs -z3 -d:pserver:anonymous at cvs.freebios.sourceforge.net:/cvsroot/freebios co freebios -Dave From rminnich at lanl.gov Mon Apr 19 18:58:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 19 18:58:01 2004 Subject: EPIA-M IRQ cvs update [PMX:#] In-Reply-To: <200404192305.i3JN5688016811@xdr.com> Message-ID: I can send you the tree but let's just wait until tomorrow. I've asked sourceforge about LANL paying them some amount per year for "premium" service, which would mean you guys would get instant turnaround on checkouts. They've never replied to me on this question. I think they're missing an opportunity with this idea ... ron From stuge-linuxbios at cdy.org Mon Apr 19 20:29:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Mon Apr 19 20:29:01 2004 Subject: EPIA-M IRQ cvs update [PMX:#] In-Reply-To: References: <200404192305.i3JN5688016811@xdr.com> Message-ID: <20040420014228.GA18387@foo.birdnet.se> On Mon, Apr 19, 2004 at 06:10:59PM -0600, ron minnich wrote: > I've asked sourceforge about LANL paying them some amount per year for > "premium" service, which would mean you guys would get instant > turnaround on checkouts. They've never replied to me on this question. > I think they're missing an opportunity with this idea ... Is the turnaround for Savannah equally bad? Do they offer everything that's available at sf.net? (Hasn't this been discussed before?) //Peter From rminnich at lanl.gov Mon Apr 19 22:43:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 19 22:43:00 2004 Subject: EPIA-M IRQ cvs update [PMX:#] In-Reply-To: <20040420014228.GA18387@foo.birdnet.se> Message-ID: On Tue, 20 Apr 2004, Peter Stuge wrote: > Is the turnaround for Savannah equally bad? Do they offer everything > that's available at sf.net? (Hasn't this been discussed before?) there is a lot more to a site like sourceforge than the system they use or delays for users. yes, we've been here before. No good alternative yet (considering the total picture). I just can't figure out why nobody at sf.net will talk to me about this "premium service" idea. ron From linuxbios at xdr.com Tue Apr 20 08:08:01 2004 From: linuxbios at xdr.com (Dave Ashley) Date: Tue Apr 20 08:08:01 2004 Subject: epia-m latest cvs works Message-ID: <200404201321.i3KDLBWa021296@xdr.com> I cvs updated and the latest changes were there (earlysetup.inc and the mainboard.c). I built the rom with this script: # Modify the example.config to point to the right payloads for vgabios.bin # and the etherboot payload cd /ram/build rm -rf obj python /ram/freebios/util/config/NLBConfig.py example.config /ram/freebios/ make -C obj NOTE: I had /ram/freebios as the cvs checked out tree. Here is the diff on the example.config from the tree and the one I used: 5d4 < target /opt/cwlinux/buildrom/epia-m 28c27 < target /ram/freebios/obj --- > target /ram/build/obj 48c47 < payload /opt/cwlinux/etherboot/src/bin32/via-rhine.ebi --- > #payload /opt/cwlinux/etherboot/src/bin32/via-rhine.ebi Which is pretty simple, just picking my payload and vgabios.bin. My vgabios.bin is just extracted from the c000:0000 memory after having boot up from the stock bios, same as everyone else's. My payload is based on etherboot 5.0.10 but other versions of etherboot are fine too. Anyway this tree builds fine for my needs. It also appears the temperature monitoring functions of the VT1211 are also working correctly. One of the tweaks I do in my version now is switch the ttyS0 and ttyS1 so ttyS0 ends up being the inside one. Now that I think about it there is an obscure bit I had to set to enable that internal port, but I've posted about this in this mailing list. I think I enable the parallel port also. I don't enable the IDE controller(s) but those appear to be on now but I'm not sure. -Dave From rminnich at lanl.gov Tue Apr 20 09:47:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 20 09:47:01 2004 Subject: epia-m latest cvs works In-Reply-To: <200404201321.i3KDLBWa021296@xdr.com> Message-ID: On Tue, 20 Apr 2004, Dave Ashley wrote: > One of the tweaks I do in my version now is switch the ttyS0 and ttyS1 > so ttyS0 ends up being the inside one. Now that I think about it there > is an obscure bit I had to set to enable that internal port, but I've > posted about this in this mailing list. I think I enable the parallel > port also. I don't enable the IDE controller(s) but those appear to be > on now but I'm not sure. OK, I think IDE works since FILO works, but we'll try that. Greg Watson has populated the V2 tree with skeleton code, and we'll start trying to see if that will work. ron From firstone5 at hotmail.com Tue Apr 20 09:53:00 2004 From: firstone5 at hotmail.com (M. Renee Hopkins) Date: Tue Apr 20 09:53:00 2004 Subject: epia-m latest cvs works Message-ID: I just built fresh LB from CVS for EPIA-M ME-600. Seems a lot of progress has been made. Payload included VGA bios and FILO. Seems like most all components detected. I'm going to test MPEG, X11, mouse and will report soon. Previously, MPEG2 used too much CPU and was jerky, AGP seemed slow, mouse was very slow. Thanks LB Team! 00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (re v 80) 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/ VT8235 PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Aud io Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] i ntegrated CastleRock graphics (rev 03) _________________________________________________________________ From mdeschamps at mangrove-systems.com Tue Apr 20 10:50:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Tue Apr 20 10:50:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest Message-ID: <1082476764.1296.23.camel@Calliphara> Hello, I was wondering in what measure it would be possible to read/write a bios via a LPT port. If i am not mistaking, every flashing facility solution reads/writes a onboard bios chip. I know this could sound very strange to you. Also, I know how difficult it is to handle request that steps aside of what the system is meant to do. But I don't feel confident with bios hot plugging... I've read this is a sensible operation and well ... Mainly i couldn't afford to "break" my unique build machine bios ! I'd rather like to make a backup copy of my bios in another chip and then to cold plug this copy to work with Linuxbios. Has anyone felt this worry . How come could I resolve this ? thanks in advance mathieu From rminnich at lanl.gov Tue Apr 20 10:52:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 20 10:52:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <1082476764.1296.23.camel@Calliphara> Message-ID: bios hot plugging has worked for us now for four years. It's scary but I would not worry about it, or just bet a bios savior. ron From YhLu at tyan.com Tue Apr 20 14:19:00 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 20 14:19:00 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= Message-ID: <3174569B9743D511922F00A0C943142304B864FA@TYANWEB> 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 at lanl.gov] ????: 2004?4?14? 15:01 ???: Brian Maly ??: linuxbios at 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 at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Tue Apr 20 14:35:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 20 14:35:01 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B864FA@TYANWEB> Message-ID: 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 From stepan at openbios.org Tue Apr 20 18:10:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Tue Apr 20 18:10:01 2004 Subject: EPIA-M IRQ cvs update In-Reply-To: <200404192305.i3JN5688016811@xdr.com> References: <200404192305.i3JN5688016811@xdr.com> Message-ID: <20040419234121.GB15319@openbios.org> * Dave Ashley [040420 01:05]: > >committed, cvs update and try again, and thanks for your patience. > > I tried this but none of your recent cvs commits are visible > (the earlysetup.inc or the mainboard.c change). Remember I'm still just > using the pond-scum cvs server: > cvs -z3 -d:pserver:anonymous at cvs.freebios.sourceforge.net:/cvsroot/freebios co freebios the public CVS server is really slow at syncing. Try the hourly images at http://snapshots.linuxbios.org/ Stefan From itz at californiadigital.com Tue Apr 20 18:24:01 2004 From: itz at californiadigital.com (Ian Zimmerman) Date: Tue Apr 20 18:24:01 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <1082476764.1296.23.camel@Calliphara> References: <1082476764.1296.23.camel@Calliphara> Message-ID: <87pta2p6f2.fsf@californiadigital.com> Mathieu> I'd rather like to make a backup copy of my bios in another Mathieu> chip and then to cold plug this copy to work with Linuxbios. Mathieu> Has anyone felt this worry . Same here. I feel that the reliance on hotplugging flash chips has limited linuxbios audience to hard-core metal hackers. From rminnich at lanl.gov Tue Apr 20 19:07:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 20 19:07:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <87pta2p6f2.fsf@californiadigital.com> Message-ID: On 20 Apr 2004, Ian Zimmerman wrote: > Same here. > > I feel that the reliance on hotplugging flash chips has limited > linuxbios audience to hard-core metal hackers. but what else can you do? Can you afford a flash burner? The set of people who can afford this is smaller than the set of people who can hot plug. I had not realized however that hot plug is such a big issue, so suggestions for alternatives that are affordable would be great Thanks! ron From stuge-linuxbios at cdy.org Tue Apr 20 19:12:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Tue Apr 20 19:12:01 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <87pta2p6f2.fsf@californiadigital.com> References: <1082476764.1296.23.camel@Calliphara> <87pta2p6f2.fsf@californiadigital.com> Message-ID: <20040421002514.GA26297@foo.birdnet.se> On Tue, Apr 20, 2004 at 04:37:37PM -0700, Ian Zimmerman wrote: > > Mathieu> I'd rather like to make a backup copy of my bios in another > Mathieu> chip and then to cold plug this copy to work with Linuxbios. > > Mathieu> Has anyone felt this worry . > > Same here. > > I feel that the reliance on hotplugging flash chips has limited > linuxbios audience to hard-core metal hackers. While it is obviously true that a number of people in the audience are worried about hotplugging the BIOS ROM I don't think it has a very negative impact yet - LinuxBIOS is getting closer and closer to a very stable release but in order to get there, more hard-core hackers are needed anyway to contribute support for various system components such as CPUs, chipsets etc. Also, any BIOS software probably isn't targeted even at power users - more so at system integrators and/or retailers, who are in a much better financial position for getting "pro" BIOS tools such as a standalone programmer. On the other hand, there's always the possibility of getting a BIOS-saviour, or even a cheaper model standalone programmer at $200. (They're usually not really good until up at $400-$500 though.) //Peter From John.Usher at perth.maptek.com.au Tue Apr 20 20:15:00 2004 From: John.Usher at perth.maptek.com.au (John Usher (Maptek)) Date: Tue Apr 20 20:15:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest Message-ID: <20E0F651F8B82F45ABCBACC58A2D995B0332BC@mexper1> For what it's worth (and so far it only works on a win* machine, we use the following cheap programmer with our ST M29F040B parts. Works a treat, but programming through the lpt port is not the fasted. The fact that only windows is supported is also a bit of a bummer. http://www.jedmicro.com.au/PROM.htm j -----Original Message----- From: ron minnich [mailto:rminnich at lanl.gov] Sent: Wednesday, 21 April 2004 8:20 AM To: Ian Zimmerman Cc: linuxbios at clustermatic.org Subject: Re: flash_n_burn rom utils, /dev/bios ... resquest On 20 Apr 2004, Ian Zimmerman wrote: > Same here. > > I feel that the reliance on hotplugging flash chips has limited > linuxbios audience to hard-core metal hackers. but what else can you do? Can you afford a flash burner? The set of people who can afford this is smaller than the set of people who can hot plug. I had not realized however that hot plug is such a big issue, so suggestions for alternatives that are affordable would be great Thanks! ron _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From YhLu at tyan.com Tue Apr 20 20:18:00 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 20 20:18:00 2004 Subject: ATI rage xl.init Message-ID: <3174569B9743D511922F00A0C943142304B86528@TYANWEB> 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 at openbios.org ? Regards YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?20? 12:48 ???: YhLu ??: Brian Maly; linuxbios at 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: fb2_tyan_0420.change.diff.bz2 Type: application/octet-stream Size: 44602 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: filo-0.4.1_btext.tar.bz2 Type: application/octet-stream Size: 105706 bytes Desc: not available URL: From YhLu at tyan.com Tue Apr 20 20:44:00 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 20 20:44:00 2004 Subject: flash_rom start and size Message-ID: <3174569B9743D511922F00A0C943142304B8652C@TYANWEB> 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. Regards YH From linuxbios at rebel.com.au Tue Apr 20 21:19:01 2004 From: linuxbios at rebel.com.au (Chris) Date: Tue Apr 20 21:19:01 2004 Subject: [linuxbios] RE: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <20E0F651F8B82F45ABCBACC58A2D995B0332BC@mexper1> Message-ID: Hi I am new to this group and currently in the lurk stage but can I pass a comment/suggestion. I get a huge amount of spam, and on a cursory glance a lot of the mail from this group "appears" spammy I am not saying it is, just that when you view the subject lines they often appear like subjects designed to foil filtering systems can I suggest a standard element be placed in the subject line such as I have done that way it will be easier to seperate the linux bios mailings from the spam mailings I am also a member of the ASRG "Anti Spam Research Group" and they use a system that looks like this subject: [ASRG] 3: description the number is for pre-organised topics such as 0 = general 1 = new ideas etc... Regards Chris > -----Original Message----- > From: linuxbios-admin at clustermatic.org > [mailto:linuxbios-admin at clustermatic.org]On Behalf Of John Usher > (Maptek) > Sent: Wednesday, 21 April 2004 10:58 AM > To: linuxbios at clustermatic.org > Subject: RE: flash_n_burn rom utils, /dev/bios ... resquest > > > For what it's worth (and so far it only works on a win* machine, we use > the following cheap programmer with our ST M29F040B parts. Works a > treat, but programming through the lpt port is not the fasted. > > The fact that only windows is supported is also a bit of a bummer. > > > http://www.jedmicro.com.au/PROM.htm > > j > > -----Original Message----- > From: ron minnich [mailto:rminnich at lanl.gov] > Sent: Wednesday, 21 April 2004 8:20 AM > To: Ian Zimmerman > Cc: linuxbios at clustermatic.org > Subject: Re: flash_n_burn rom utils, /dev/bios ... resquest > > > On 20 Apr 2004, Ian Zimmerman wrote: > > > Same here. > > > > I feel that the reliance on hotplugging flash chips has limited > > linuxbios audience to hard-core metal hackers. > > but what else can you do? Can you afford a flash burner? The set of > people > who can afford this is smaller than the set of people who can hot plug. > > I had not realized however that hot plug is such a big issue, so > suggestions for alternatives that are affordable would be great > > Thanks! > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Tue Apr 20 22:30:00 2004 From: rminnich at lanl.gov (Ronald G. Minnich) Date: Tue Apr 20 22:30:00 2004 Subject: [linuxbios] RE: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: Message-ID: On Wed, 21 Apr 2004, Chris wrote: > can I suggest a standard element be placed in the subject line such as I > have done we looked at doing this years ago but there were objections. Any objections now from anyone? ron From ebiederman at lnxi.com Wed Apr 21 00:17:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Apr 21 00:17:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: References: Message-ID: "Chris" writes: > Hi > > I am new to this group and currently in the lurk stage > > but can I pass a comment/suggestion. > > I get a huge amount of spam, and on a cursory glance a lot of the mail from > this group "appears" spammy > > I am not saying it is, just that when you view the subject lines they often > appear like subjects designed to foil filtering systems Subject lines are for humans the other headers are for machines. > can I suggest a standard element be placed in the subject line such as I > have done > > that way it will be easier to seperate the linux bios mailings from the spam > mailings Look at the List-Id: that should be completely constant. That is what I filter by and it makes it trivial. I filter not to get rid of spam but to separate the LinuxBIOS mailing list traffic and the linux kernel mailing list traffic etc. If you want something practically spoof proof ask for the mailing list to gpg sign messages. Then you can be certain the message at least came from the mailing list. I have not seen any spam come through this mailing list. Or even spoofed as such. If you really want to stop spam. Don't concentrate on the fact that it is unwanted mail. Concentrate on the fact that it is bulk mail, and that it is generally fraudulent. Detecting mail is passing in bulk or that it does not have a legitimate source do not sound like hard problems. > I am also a member of the ASRG "Anti Spam Research Group" and they use a > system that looks like this > > subject: [ASRG] 3: description > > the number is for pre-organised topics such as 0 = general 1 = new ideas > etc... Things like that get extremely ugly when you cross post, or the mailing system does not recognize your Re: line so you get things like: Re: [linuxbios] Re: [linuxbios] or: Re: [linuxbios] RE: flash_n_burn rom utils, /dev/bios, ... resquest And we have a diverse enough crowd we don't get consistent recognition of the Re: line anyway. Yhlu I think posts with Chinese character set which makes things interesting. Hacked subject lines just clutter up things up. As for adding numbers for general categories that is just silly. If you want to describe what is going on feel free to add: [IDEA] or [PATCH] or whatever. Enumerations with numerical values are just silly when they are for human consumption. The next logical step is to progress forward to writing programs in machine code to give more control so they are not susceptible to viruses. Eric From linuxbios at rebel.com.au Wed Apr 21 00:38:00 2004 From: linuxbios at rebel.com.au (Chris) Date: Wed Apr 21 00:38:00 2004 Subject: [linuxbios]RE: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: Message-ID: > > > > I am not saying it is, just that when you view the subject > lines they often > > appear like subjects designed to foil filtering systems > > Subject lines are for humans the other headers are for machines. > I have given up on filters. Dont trust them to do the job. so I use them to pick the obvious spam then the remaining emails get scanned by trusty human eye and brain for the final decision. Unfortunately some of the very cryptic subject lines appear to be spam so I tossed the first few until I realised my mistake. (bugger does that make me as reliable as spam filters) I will try the list-id header. and mark it as friendly if it has it. > Re: [linuxbios] Re: [linuxbios] If the list server placed the tag in it wouldn't be a problem and no-one would have to type it the list server can delete any redundant tags and then forward the mail > > As for adding numbers for general categories that is just silly. If > you want to describe what is going on feel free to add: [IDEA] or > [PATCH] or whatever. Enumerations with numerical values are just > silly when they are for human consumption. not really its just shorter to read and write, with only 6 choices the ASRG works very well > The next logical step is > to progress forward to writing programs in machine code to give more > control so they are not susceptible to viruses. > now your just being really silly Regards Chris > -----Original Message----- > From: Eric W. Biederman [mailto:eric at lnxi.com]On Behalf Of Eric W. > Biederman > Sent: Wednesday, 21 April 2004 3:03 PM > To: Chris > Cc: John Usher (Maptek); linuxbios at clustermatic.org > Subject: Re: flash_n_burn rom utils, /dev/bios ... resquest > > > "Chris" writes: > > > Hi > > > > I am new to this group and currently in the lurk stage > > > > but can I pass a comment/suggestion. > > > > I get a huge amount of spam, and on a cursory glance a lot of > the mail from > > this group "appears" spammy > > > > I am not saying it is, just that when you view the subject > lines they often > > appear like subjects designed to foil filtering systems > > Subject lines are for humans the other headers are for machines. > > > can I suggest a standard element be placed in the subject line such as I > > have done > > > > that way it will be easier to seperate the linux bios mailings > from the spam > > mailings > > Look at the List-Id: that should be completely constant. That is what > I filter by and it makes it trivial. I filter not to get rid of spam > but to separate the LinuxBIOS mailing list traffic and the linux > kernel mailing list traffic etc. > > If you want something practically spoof proof ask for the mailing > list to gpg sign messages. Then you can be certain the message > at least came from the mailing list. > > I have not seen any spam come through this mailing list. Or even > spoofed as such. > > If you really want to stop spam. Don't concentrate on the fact > that it is unwanted mail. Concentrate on the fact that it is > bulk mail, and that it is generally fraudulent. Detecting mail is > passing in bulk or that it does not have a legitimate source do not > sound like hard problems. > > > I am also a member of the ASRG "Anti Spam Research Group" and they use a > > system that looks like this > > > > subject: [ASRG] 3: description > > > > the number is for pre-organised topics such as 0 = general 1 = new ideas > > etc... > > Things like that get extremely ugly when you cross post, > or the mailing system does not recognize your Re: line > so you get things like: > > Re: [linuxbios] Re: [linuxbios] > or: > Re: [linuxbios] RE: flash_n_burn rom utils, /dev/bios, ... resquest > > And we have a diverse enough crowd we don't get consistent recognition > of the Re: line anyway. Yhlu I think posts with Chinese character > set which makes things interesting. > > Hacked subject lines just clutter up things up. > > As for adding numbers for general categories that is just silly. If > you want to describe what is going on feel free to add: [IDEA] or > [PATCH] or whatever. Enumerations with numerical values are just > silly when they are for human consumption. The next logical step is > to progress forward to writing programs in machine code to give more > control so they are not susceptible to viruses. > > Eric > > > > > > From linuxbios at rebel.com.au Wed Apr 21 01:01:00 2004 From: linuxbios at rebel.com.au (Chris) Date: Wed Apr 21 01:01:00 2004 Subject: [linuxbios]Now that I have your attention :) In-Reply-To: Message-ID: No not really I was just passing comment But I do have a question, based a little on laziness cause I could not find adequate mention of my ideas in respect to LinuxBios. I have thought about a embedded operating system for some time, for two main reasons the first is obvious and well documented That is the desire to have a computer come with an OS that runs as soon as it is started. perfect for all sorts of things The second does not seem to have been covered or at least I have not been able to unearth much information about it. So I wanted to see if it was in the charter of this group. What I am referring to is a method to enable device manufacturers to have a consistant interface to the hardware. If an OS writer such as M$ does not support a device it is very hard to get that device to work if at all. Manufacturers have to write device drivers for many different os's and versions, consequently they only write for the most popular and forget less popular and older systems. What I envisage is a common device interface. Allowing any manufacturer create one piece of software for their hardware and except for constraints such as recompiling for different cpu's etc their hardware will work on any system. (within reason). So all you need is one API written for each OS that gives the the manufacturer access to that particular device REGARDLESS of whether the OS was written to handle that device. For example NT 4.0 has no idea what a USB device is. So you can't use one. period! this was the main reason I went to XP and its griped me ever since. I am sure that in the linux world it is annoying to have to write new drivers for every little piece of hardware that comes out. Wouldn't it be nice if the device manufacturer could simply recompile their driver to suit linux or sun or mac(bsd) the only real place for such an interface is at the BIOS level, lest OS writers pervert it for their own good. and if that BIOS was provided licence free to Mainboard manufacturers wouldn't that be something. Sorry If I am going over old material, As I said I have not found articles relating to this. Regards Chris > -----Original Message----- > From: Chris [mailto:linuxbios at rebel.com.au] > Sent: Wednesday, 21 April 2004 3:21 PM > To: Eric W. Biederman; Chris > Cc: John Usher (Maptek); linuxbios at clustermatic.org > Subject: [linuxbios]RE: flash_n_burn rom utils, /dev/bios ... resquest > > > > > > > > I am not saying it is, just that when you view the subject > > lines they often > > > appear like subjects designed to foil filtering systems > > > > Subject lines are for humans the other headers are for machines. > > > > I have given up on filters. Dont trust them to do the job. so I > use them to > pick the obvious spam > then the remaining emails get scanned by trusty human eye and > brain for the > final decision. > > Unfortunately some of the very cryptic subject lines appear to be > spam so I > tossed the first few until I realised my mistake. > (bugger does that make me as reliable as spam filters) > > I will try the list-id header. and mark it as friendly if it has it. > > > > Re: [linuxbios] Re: [linuxbios] > > If the list server placed the tag in it wouldn't be a problem and no-one > would have to type it > the list server can delete any redundant tags and then forward the mail > > > > > > As for adding numbers for general categories that is just silly. If > > you want to describe what is going on feel free to add: [IDEA] or > > [PATCH] or whatever. Enumerations with numerical values are just > > silly when they are for human consumption. > > not really its just shorter to read and write, with only 6 > choices the ASRG > works very well > > > The next logical step is > > to progress forward to writing programs in machine code to give more > > control so they are not susceptible to viruses. > > > > now your just being really silly > > Regards > Chris > > > > > > -----Original Message----- > > From: Eric W. Biederman [mailto:eric at lnxi.com]On Behalf Of Eric W. > > Biederman > > Sent: Wednesday, 21 April 2004 3:03 PM > > To: Chris > > Cc: John Usher (Maptek); linuxbios at clustermatic.org > > Subject: Re: flash_n_burn rom utils, /dev/bios ... resquest > > > > > > "Chris" writes: > > > > > Hi > > > > > > I am new to this group and currently in the lurk stage > > > > > > but can I pass a comment/suggestion. > > > > > > I get a huge amount of spam, and on a cursory glance a lot of > > the mail from > > > this group "appears" spammy > > > > > > I am not saying it is, just that when you view the subject > > lines they often > > > appear like subjects designed to foil filtering systems > > > > Subject lines are for humans the other headers are for machines. > > > > > can I suggest a standard element be placed in the subject > line such as I > > > have done > > > > > > that way it will be easier to seperate the linux bios mailings > > from the spam > > > mailings > > > > Look at the List-Id: that should be completely constant. That is what > > I filter by and it makes it trivial. I filter not to get rid of spam > > but to separate the LinuxBIOS mailing list traffic and the linux > > kernel mailing list traffic etc. > > > > If you want something practically spoof proof ask for the mailing > > list to gpg sign messages. Then you can be certain the message > > at least came from the mailing list. > > > > I have not seen any spam come through this mailing list. Or even > > spoofed as such. > > > > If you really want to stop spam. Don't concentrate on the fact > > that it is unwanted mail. Concentrate on the fact that it is > > bulk mail, and that it is generally fraudulent. Detecting mail is > > passing in bulk or that it does not have a legitimate source do not > > sound like hard problems. > > > > > I am also a member of the ASRG "Anti Spam Research Group" and > they use a > > > system that looks like this > > > > > > subject: [ASRG] 3: description > > > > > > the number is for pre-organised topics such as 0 = general 1 > = new ideas > > > etc... > > > > Things like that get extremely ugly when you cross post, > > or the mailing system does not recognize your Re: line > > so you get things like: > > > > Re: [linuxbios] Re: [linuxbios] > > or: > > Re: [linuxbios] RE: flash_n_burn rom utils, /dev/bios, ... resquest > > > > And we have a diverse enough crowd we don't get consistent recognition > > of the Re: line anyway. Yhlu I think posts with Chinese character > > set which makes things interesting. > > > > Hacked subject lines just clutter up things up. > > > > As for adding numbers for general categories that is just silly. If > > you want to describe what is going on feel free to add: [IDEA] or > > [PATCH] or whatever. Enumerations with numerical values are just > > silly when they are for human consumption. The next logical step is > > to progress forward to writing programs in machine code to give more > > control so they are not susceptible to viruses. > > > > Eric > > > > > > > > > > > > > From mdeschamps at mangrove-systems.com Wed Apr 21 02:37:00 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Wed Apr 21 02:37:00 2004 Subject: [linuxbios]RE: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: References: Message-ID: <1082533681.1296.50.camel@Calliphara> I just want to rise, RESPECTFULLY, *YOUR* paradox : Look you are talking about spams on maillist right ? >: Gosh ! And you dare keeping up the title flash_n_burn rom utils, /dev/bios ... title that has no meaning in regards of your mail's content. That's a bit strong ! As a result (maybe) a depreciation of the original topic : who'd like to follow a swinging topic from flashin' chips to spam issue on maillist ? Nevertheless, this resquest (the early one : "fear" of the hot plug and means to avoid it) on which you gained attention -as you said- may be not of your interest but you could respect it and not try (intended or not !) to pollute it. Have you noticed, moreover, it seems to be a shared resquest (many reactions) ? For all his, I think that you've act like people you denounce and I'am sorry for you. respectfully and with no hard feelings mathieu 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 ... Le mer 21/04/2004 ? 07:50, Chris a ?crit : > > > > > > I am not saying it is, just that when you view the subject > > lines they often > > > appear like subjects designed to foil filtering systems > > > > Subject lines are for humans the other headers are for machines. > > > > I have given up on filters. Dont trust them to do the job. so I use them to > pick the obvious spam > then the remaining emails get scanned by trusty human eye and brain for the > final decision. > > Unfortunately some of the very cryptic subject lines appear to be spam so I > tossed the first few until I realised my mistake. > (bugger does that make me as reliable as spam filters) > > I will try the list-id header. and mark it as friendly if it has it. > > > > Re: [linuxbios] Re: [linuxbios] > > If the list server placed the tag in it wouldn't be a problem and no-one > would have to type it > the list server can delete any redundant tags and then forward the mail > > > > > > As for adding numbers for general categories that is just silly. If > > you want to describe what is going on feel free to add: [IDEA] or > > [PATCH] or whatever. Enumerations with numerical values are just > > silly when they are for human consumption. > > not really its just shorter to read and write, with only 6 choices the ASRG > works very well > > > The next logical step is > > to progress forward to writing programs in machine code to give more > > control so they are not susceptible to viruses. > > > > now your just being really silly > > Regards > Chris > > > > > > -----Original Message----- > > From: Eric W. Biederman [mailto:eric at lnxi.com]On Behalf Of Eric W. > > Biederman > > Sent: Wednesday, 21 April 2004 3:03 PM > > To: Chris > > Cc: John Usher (Maptek); linuxbios at clustermatic.org > > Subject: Re: flash_n_burn rom utils, /dev/bios ... resquest > > > > > > "Chris" writes: > > > > > Hi > > > > > > I am new to this group and currently in the lurk stage > > > > > > but can I pass a comment/suggestion. > > > > > > I get a huge amount of spam, and on a cursory glance a lot of > > the mail from > > > this group "appears" spammy > > > > > > I am not saying it is, just that when you view the subject > > lines they often > > > appear like subjects designed to foil filtering systems > > > > Subject lines are for humans the other headers are for machines. > > > > > can I suggest a standard element be placed in the subject line such as I > > > have done > > > > > > that way it will be easier to seperate the linux bios mailings > > from the spam > > > mailings > > > > Look at the List-Id: that should be completely constant. That is what > > I filter by and it makes it trivial. I filter not to get rid of spam > > but to separate the LinuxBIOS mailing list traffic and the linux > > kernel mailing list traffic etc. > > > > If you want something practically spoof proof ask for the mailing > > list to gpg sign messages. Then you can be certain the message > > at least came from the mailing list. > > > > I have not seen any spam come through this mailing list. Or even > > spoofed as such. > > > > If you really want to stop spam. Don't concentrate on the fact > > that it is unwanted mail. Concentrate on the fact that it is > > bulk mail, and that it is generally fraudulent. Detecting mail is > > passing in bulk or that it does not have a legitimate source do not > > sound like hard problems. > > > > > I am also a member of the ASRG "Anti Spam Research Group" and they use a > > > system that looks like this > > > > > > subject: [ASRG] 3: description > > > > > > the number is for pre-organised topics such as 0 = general 1 = new ideas > > > etc... > > > > Things like that get extremely ugly when you cross post, > > or the mailing system does not recognize your Re: line > > so you get things like: > > > > Re: [linuxbios] Re: [linuxbios] > > or: > > Re: [linuxbios] RE: flash_n_burn rom utils, /dev/bios, ... resquest > > > > And we have a diverse enough crowd we don't get consistent recognition > > of the Re: line anyway. Yhlu I think posts with Chinese character > > set which makes things interesting. > > > > Hacked subject lines just clutter up things up. > > > > As for adding numbers for general categories that is just silly. If > > you want to describe what is going on feel free to add: [IDEA] or > > [PATCH] or whatever. Enumerations with numerical values are just > > silly when they are for human consumption. The next logical step is > > to progress forward to writing programs in machine code to give more > > control so they are not susceptible to viruses. > > > > Eric > > > > > > > > > > > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From ebiederman at lnxi.com Wed Apr 21 02:40:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Apr 21 02:40:01 2004 Subject: [IDEA] make the BIOS the OS. In-Reply-To: References: Message-ID: "Chris" writes: > No not really I was just passing comment > > But I do have a question, based a little on laziness cause I could not find > adequate mention of my ideas in respect to LinuxBios. > > I have thought about a embedded operating system for some time, for two main > reasons the first is obvious and well documented > > That is the desire to have a computer come with an OS that runs as soon as > it is started. perfect for all sorts of things > > The second does not seem to have been covered or at least I have not been > able to unearth much information about it. > So I wanted to see if it was in the charter of this group. > > What I am referring to is a method to enable device manufacturers to have a > consistant interface to the hardware. > > If an OS writer such as M$ does not support a device it is very hard to get > that device to work if at all. > > Manufacturers have to write device drivers for many different os's and > versions, consequently they only write for the most popular and forget less > popular and older systems. No, OS developers do. Manufacturers only need to provide documentation. > What I envisage is a common device interface. Allowing any manufacturer > create one piece of software for their hardware and except for constraints > such as recompiling for different cpu's etc their hardware will work on any > system. (within reason). You are describing an OS. An OS is the hardware abstraction layer. All attempts to the contrary are non sense. > So all you need is one API written for each OS that gives the the > manufacturer access to that particular device REGARDLESS of whether the OS > was written to handle that device. > > For example NT 4.0 has no idea what a USB device is. So you can't use one. > period! this was the main reason I went to XP and its griped me ever since. This is a problem with closed source not with the driver development model. If you have the source and modification rights to it. When something is important enough you can do whatever you like. > I am sure that in the linux world it is annoying to have to write new > drivers for every little piece of hardware that comes out. If they are close enough a generic driver can be written. This is why there are standards for hardware manufacturers. > Wouldn't it be nice if the device manufacturer could simply recompile their > driver to suit linux or sun or mac(bsd) Only if it was not utter crap. Occasionally that happens. Mostly hardware manufacturers are not good at writing code. > the only real place for such an interface is at the BIOS level, lest OS > writers pervert it for their own good. > > and if that BIOS was provided licence free to Mainboard manufacturers > wouldn't that be something. It is almost impossible to update a BIOS in the field, (human factors). And it is very dangerous. Who wants to update take the risk of killing their machine just so their new whatzit will work? > Sorry If I am going over old material, As I said I have not found articles > relating to this. I don't know if it has ever been written about. But the idea comes up often. You would probably find some sympathy at Intel among their EFI group. But then EFI is peculiar DOS/WIN clone anyway... Eric From andreas.huebner at hp.com Wed Apr 21 04:35:00 2004 From: andreas.huebner at hp.com (andreas.huebner at hp.com) Date: Wed Apr 21 04:35:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: References: Message-ID: <20040421094824.GA18589@smstf09.bbn.hp.com> Hi all, On Tue, Apr 20, 2004 at 11:33:06PM -0600, Eric W. Biederman wrote: > > If you want something practically spoof proof ask for the mailing > list to gpg sign messages. Then you can be certain the message > at least came from the mailing list. GPG signed mails are not readable with old versions of outlook. And yes, outlook is not the best choice but sometimes the only client which is allowed to be used. Andreas From mdeschamps at mangrove-systems.com Wed Apr 21 04:50:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Wed Apr 21 04:50:01 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: References: Message-ID: <1082540876.1296.73.camel@Calliphara> Le mer 21/04/2004 ? 02:20, ron minnich a ?crit : > On 20 Apr 2004, Ian Zimmerman wrote: > > > Same here. > > > > I feel that the reliance on hotplugging flash chips has limited > > linuxbios audience to hard-core metal hackers. > > but what else can you do? Can you afford a flash burner? The set of people > who can afford this is smaller than the set of people who can hot plug. 1. I can't afford a "true" flash burner 2. Hot plug on PLCC (for example) leaves me (and others as it seems) worry : half a millimeter between chip pins and a working motherboard : what if i'am a bit stress and lift up badly the chip ? I got the answer... It's where the difficulty relies : I find it a pity linuxbios offers so much and resolve via soft a lots of non Open/Free bios problems, and though couldn't free itself from this "mechanical" issue... if I can say so... :) "Draft" Propositions : 1. why not building a flash_rom util which could send bios code steam via LTP, COM or USB, PCI : the aim not to touch the "working" bios(even though its not needed after boot time) . Plusvalue of this : Cold plug : Make a backup copy for example 2. trying to disconnect/diswire bios socket from the up mainboard (that is to say to get 0v on every pin of the socket) . Ideal view (mb manufacturers !) : get a jumper to handle this 3 ... err .. run dry mathieu > > I had not realized however that hot plug is such a big issue, so > suggestions for alternatives that are affordable would be great > > Thanks! > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From ebiederman at lnxi.com Wed Apr 21 06:08:00 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Wed Apr 21 06:08:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <1082540876.1296.73.camel@Calliphara> References: <1082540876.1296.73.camel@Calliphara> Message-ID: Mathieu Deschamps writes: > Le mer 21/04/2004 ? 02:20, ron minnich a ?crit : > > On 20 Apr 2004, Ian Zimmerman wrote: > > > > > Same here. > > > > > > I feel that the reliance on hotplugging flash chips has limited > > > linuxbios audience to hard-core metal hackers. > > > > but what else can you do? Can you afford a flash burner? The set of people > > who can afford this is smaller than the set of people who can hot plug. > > 1. I can't afford a "true" flash burner > 2. Hot plug on PLCC (for example) leaves me (and others as it seems) > worry : > half a millimeter between chip pins and a working motherboard : > what if i'am a bit stress and lift up badly the chip ? I got the > answer... In practice I have not seen this happen. The only things I have fried are BIOS chips themselves by pluggin them in backwards. > It's where the difficulty relies : I find it a pity linuxbios offers so > much and resolve via soft a lots of non Open/Free bios problems, and > though couldn't free itself from this "mechanical" issue... if I can say > so... :) For users if there is a known good binary release for a board changing BIOS chips is not an issue. This is only an issue for developers, and users willing to live on the edge because they don't know if what they are about to flash will work. Once LinuxBIOS is up and running on a board we have two copies and you can flash just so there is really not an issue. > "Draft" Propositions : > > > 1. why not building a flash_rom util which could send bios code steam > via LTP, COM or USB, PCI : the aim not to touch the "working" bios(even > though its not needed after boot time) . Plusvalue of this : Cold plug : > Make a backup copy for example If this was done in software it would need to put the code some place. That takes RAM. You need the BIOS to enable RAM. catch-22. > 2. trying to disconnect/diswire bios socket from the up mainboard (that > is to say to get 0v on every pin of the socket) . Ideal view (mb > manufacturers !) : get a jumper to handle this Sounds like a sane alternative to me, if you can solder that well. > 3 ... err .. run dry Right. We try to provide suggestions within the range of doability. It is not that we want to make things hard on developers/testers it is just that things are hard and tricky taking over a system that low down. Eric From rminnich at lanl.gov Wed Apr 21 09:20:00 2004 From: rminnich at lanl.gov (Ronald G. Minnich) Date: Wed Apr 21 09:20:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: Message-ID: based on Eric's writeup I think we'll forgo [linuxbios] in the subject. Thanks, Eric. ron From rminnich at lanl.gov Wed Apr 21 09:44:00 2004 From: rminnich at lanl.gov (Ronald G. Minnich) Date: Wed Apr 21 09:44:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <1082540876.1296.73.camel@Calliphara> Message-ID: On 21 Apr 2004, Mathieu Deschamps wrote: > half a millimeter between chip pins and a working motherboard : > what if i'am a bit stress and lift up badly the chip ? I got the > answer... ah! the problem! go to your friendly Radio Shack (I have seem them in France, is that your location?) and get the PLCC puller. It's a great cheap tool and it is almost IMPOSSIBLE to hurt anything with it! > 1. why not building a flash_rom util which could send bios code steam > via LTP, COM or USB, PCI : the aim not to touch the "working" bios(even > though its not needed after boot time) . Plusvalue of this : Cold plug : > Make a backup copy for example It's a great idea but what are you going to hook that USB port to? a $400 programmer, that's what. That's the problem. > 2. trying to disconnect/diswire bios socket from the up mainboard (that > is to say to get 0v on every pin of the socket) . Ideal view (mb > manufacturers !) : get a jumper to handle this I don't think you can get them to do it. > 3 ... err .. run dry hot plug. ron From mdeschamps at mangrove-systems.com Wed Apr 21 10:36:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Wed Apr 21 10:36:01 2004 Subject: [BIOS] hot plug / cold plug In-Reply-To: References: Message-ID: <1082562421.1296.93.camel@Calliphara> Le mer 21/04/2004 ? 16:57, Ronald G. Minnich a ?crit : > On 21 Apr 2004, Mathieu Deschamps wrote: > > > half a millimeter between chip pins and a working motherboard : > > what if i'am a bit stress and lift up badly the chip ? I got the > > answer... > > ah! the problem! > > go to your friendly Radio Shack (I have seem them in France, is that your > location?) and get the PLCC puller. It's a great cheap tool and it is > almost IMPOSSIBLE to hurt anything with it! Well, I've just gone to their internet site a few minute ago. But you know now it has gone farther than a simple question a harm. It's a question of safety, and of comfort > > > 1. why not building a flash_rom util which could send bios code steam > > via LTP, COM or USB, PCI : the aim not to touch the "working" bios(even > > though its not needed after boot time) . Plusvalue of this : Cold plug : > > Make a backup copy for example > > It's a great idea but what are you going to hook that USB port to? a $400 > programmer, that's what. That's the problem. true. > > 2. trying to disconnect/diswire bios socket from the up mainboard (that > > is to say to get 0v on every pin of the socket) . Ideal view (mb > > manufacturers !) : get a jumper to handle this > > I don't think you can get them to do it. I alone surely not ! If the demand exists the offer will except if them, don't want it, but why would they ?. It not new that the comfort of use and customization is a true plusvalue in computing and in electronics (hardware). Maybe it could appear to be just "tuning" but not only. > 3 ... err .. run dry > > hot plug. I can't help thinking that working on same bios that went up is a bad idea (in ref of: never build in the source directory). Promise I stop doing my hammer head :) I'll stop bother with it : I'll go hot pluging because i've now understood there's no other alternative. > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From hansolofalcon at worldnet.att.net Wed Apr 21 10:40:01 2004 From: hansolofalcon at worldnet.att.net (Gregg C Levine) Date: Wed Apr 21 10:40:01 2004 Subject: [linuxbios] RE: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: Message-ID: <008301c427b8$dcab5c20$6401a8c0@who5> Hello from Gregg C Levine None from me. ------------------- Gregg C Levine hansolofalcon at worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."? Obi-Wan Kenobi > -----Original Message----- > From: linuxbios-admin at clustermatic.org [mailto:linuxbios- > admin at clustermatic.org] On Behalf Of Ronald G. Minnich > Sent: Tuesday, April 20, 2004 11:43 PM > To: Chris > Cc: John Usher (Maptek); linuxbios at clustermatic.org > Subject: Re: [linuxbios] RE: flash_n_burn rom utils, /dev/bios ... resquest > > On Wed, 21 Apr 2004, Chris wrote: > > > can I suggest a standard element be placed in the subject line such as I > > have done > > we looked at doing this years ago but there were objections. > > Any objections now from anyone? > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From ollie at lanl.gov Wed Apr 21 10:51:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Apr 21 10:51:00 2004 Subject: flash_n_burn rom utils, /dev/bios ... resquest In-Reply-To: <20040421002514.GA26297@foo.birdnet.se> References: <1082476764.1296.23.camel@Calliphara> <87pta2p6f2.fsf@californiadigital.com> <20040421002514.GA26297@foo.birdnet.se> Message-ID: <1082563456.12282.2.camel@exponential.lanl.gov> On Tue, 2004-04-20 at 18:25, Peter Stuge wrote: > On Tue, Apr 20, 2004 at 04:37:37PM -0700, Ian Zimmerman wrote: > > > > Mathieu> I'd rather like to make a backup copy of my bios in another > > Mathieu> chip and then to cold plug this copy to work with Linuxbios. > > > > Mathieu> Has anyone felt this worry . > > > > Same here. > > > > I feel that the reliance on hotplugging flash chips has limited > > linuxbios audience to hard-core metal hackers. > > While it is obviously true that a number of people in the audience are > worried about hotplugging the BIOS ROM I don't think it has a very > negative impact yet - LinuxBIOS is getting closer and closer to a very > stable release but in order to get there, more hard-core hackers are > needed anyway to contribute support for various system components such > as CPUs, chipsets etc. > > Also, any BIOS software probably isn't targeted even at power users - > more so at system integrators and/or retailers, who are in a much > better financial position for getting "pro" BIOS tools such as a > standalone programmer. > > On the other hand, there's always the possibility of getting a > BIOS-saviour, or even a cheaper model standalone programmer at $200. > (They're usually not really good until up at $400-$500 though.) > One of the problem I found with those standalone flash programmer is the speed. It take a long time to erase/program a flash chip with these programmers. And those programmers only work under Windows. This is very unproductive when one is in a modify/compile/test cycle. Ollie > > //Peter > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From ollie at lanl.gov Wed Apr 21 10:56:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Apr 21 10:56:01 2004 Subject: flash_rom start and size In-Reply-To: <3174569B9743D511922F00A0C943142304B8652C@TYANWEB> References: <3174569B9743D511922F00A0C943142304B8652C@TYANWEB> Message-ID: <1082563759.12282.6.camel@exponential.lanl.gov> 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 > From YhLu at tyan.com Wed Apr 21 11:18:01 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 21 11:18:01 2004 Subject: =?GB2312?B?tPC4tDogZmxhc2hfcm9tIHN0YXJ0IGFuZCBzaXpl?= Message-ID: <3174569B9743D511922F00A0C943142304B86552@TYANWEB> 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 at 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 > From YhLu at tyan.com Wed Apr 21 11:24:00 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 21 11:24:00 2004 Subject: FILO --> zelf format to reduce size to 32k below. Message-ID: <3174569B9743D511922F00A0C943142304B86555@TYANWEB> Eric, Can you add something in filo Makefile and make it produce zelf format? If the size to be 32k below, for fallback boot the payload could be FILO+Etherboot --> [384k, 416k](FILO) + [416k, 448k) (Etherboot) , instead of putting the Etherboot in the [0,64k) of ROM, and FILO in the [384k, 448k). Regards YH From ollie at lanl.gov Wed Apr 21 11:35:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Apr 21 11:35:01 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= flash_rom start and size In-Reply-To: <3174569B9743D511922F00A0C943142304B86552@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86552@TYANWEB> Message-ID: <1082566142.12282.10.camel@exponential.lanl.gov> On Wed, 2004-04-21 at 10:40, YhLu wrote: > 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). there is no way you can really lock the flash. > 2. or I only want to update the payload image in the beginning, [0,64k). > you need some kind of flash translation layer to accomplish this. You need to back up some part of the erase block you want reserve , erase the block and write with updated and reserved data. You probably need MTD. Ollie > Regards > > Yinghai Lu > -----????----- > ???: Li-Ta Lo [mailto:ollie at 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 > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Wed Apr 21 11:40:01 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 21 11:40:01 2004 Subject: flash_rom start and size Message-ID: <3174569B9743D511922F00A0C943142304B86563@TYANWEB> In the PMC pm49fl004, You got eight 64K size blocks. You can erase the individual block and write that block only. Regards YH -----????----- ???: Li-Ta Lo [mailto:ollie at lanl.gov] ????: 2004?4?21? 9:49 ???: YhLu ??: LinuxBIOS ??: Re: ??: flash_rom start and size On Wed, 2004-04-21 at 10:40, YhLu wrote: > 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). there is no way you can really lock the flash. > 2. or I only want to update the payload image in the beginning, [0,64k). > you need some kind of flash translation layer to accomplish this. You need to back up some part of the erase block you want reserve , erase the block and write with updated and reserved data. You probably need MTD. Ollie > Regards > > Yinghai Lu > -----????----- > ???: Li-Ta Lo [mailto:ollie at 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 > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From ollie at lanl.gov Wed Apr 21 11:49:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Apr 21 11:49:01 2004 Subject: flash_rom start and size In-Reply-To: <3174569B9743D511922F00A0C943142304B86563@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86563@TYANWEB> Message-ID: <1082566951.12282.13.camel@exponential.lanl.gov> On Wed, 2004-04-21 at 11:03, YhLu wrote: > In the PMC pm49fl004, You got eight 64K size blocks. > > You can erase the individual block and write that block only. > > Regards > > YH > The problem is the block size is different for different flash parts. It requires a lot of code to handle this difference. It is the reason why MTD got so big. Ollie > -----????----- > ???: Li-Ta Lo [mailto:ollie at lanl.gov] > ????: 2004?4?21? 9:49 > ???: YhLu > ??: LinuxBIOS > ??: Re: ??: flash_rom start and size > > On Wed, 2004-04-21 at 10:40, YhLu wrote: > > 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). > > there is no way you can really lock the flash. > > > 2. or I only want to update the payload image in the beginning, [0,64k). > > > > you need some kind of flash translation layer to accomplish this. You > need to back up some part of the erase block you want reserve , erase > the block and write with updated and reserved data. > > You probably need MTD. > > Ollie > > > Regards > > > > Yinghai Lu > > -----????----- > > ???: Li-Ta Lo [mailto:ollie at 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 > > > > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > From rminnich at lanl.gov Wed Apr 21 12:06:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 21 12:06:01 2004 Subject: [BIOS] hot plug / cold plug In-Reply-To: <1082562421.1296.93.camel@Calliphara> Message-ID: On 21 Apr 2004, Mathieu Deschamps wrote: > Well, I've just gone to their internet site a few minute ago. > But you know now it has gone farther than a simple question a > harm. It's a question of safety, and of comfort the tradeoff is money. If you don't have money, you have to go this route. I don't see any way out. > I alone surely not ! If the demand exists the offer will > except if them, don't want it, but why would they ?. You can try. In my experience, with them punching out millions of these boards a month, they won't want to spend any money/time on a design change that will compromise the board (as this jumper would). > I'll go hot pluging because i've now understood > there's no other alternative. yeah, I'm sorry. ron From rminnich at lanl.gov Wed Apr 21 12:15:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 21 12:15:00 2004 Subject: flash_rom start and size In-Reply-To: <3174569B9743D511922F00A0C943142304B86563@TYANWEB> Message-ID: for the Alphas long ago I modified flash_rom as follows: flash_rom e Erase the blocks flash_rom r read the blocks flash_rom p 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 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 From YhLu at tyan.com Wed Apr 21 12:17:00 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 21 12:17:00 2004 Subject: =?GB2312?B?tPC4tDogZmxhc2hfcm9tIHN0YXJ0IGFuZCBzaXpl?= Message-ID: <3174569B9743D511922F00A0C943142304B86570@TYANWEB> It could only process 64k block. YH -----????----- ???: ron minnich [mailto:rminnich at 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 Erase the blocks flash_rom r read the blocks flash_rom p 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 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 From rminnich at lanl.gov Wed Apr 21 12:22:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 21 12:22:00 2004 Subject: =?GB2312?B?tPC4tDogZmxhc2hfcm9tIHN0YXJ0IGFuZCBzaXpl?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86570@TYANWEB> Message-ID: On Wed, 21 Apr 2004, YhLu wrote: > It could only process 64k block. yes, that's true. It will not work with flexible parts. ron From ollie at lanl.gov Wed Apr 21 16:33:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Apr 21 16:33:01 2004 Subject: ATI rage xl.init In-Reply-To: <3174569B9743D511922F00A0C943142304B86528@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86528@TYANWEB> Message-ID: <1082583994.12282.262.camel@exponential.lanl.gov> 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 at 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 From YhLu at tyan.com Wed Apr 21 17:55:01 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 21 17:55:01 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= Message-ID: <3174569B9743D511922F00A0C943142304B865D7@TYANWEB> 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 at 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 at 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: fb2_tyan_0420_1.change.diff.bz2 Type: application/octet-stream Size: 44592 bytes Desc: not available URL: From rminnich at lanl.gov Thu Apr 22 07:54:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 22 07:54:01 2004 Subject: EPIA (NOT EPIA-M) VGA Message-ID: 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 From mdeschamps at mangrove-systems.com Thu Apr 22 08:26:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Thu Apr 22 08:26:01 2004 Subject: Open bios dev/bios bug report Message-ID: <1082641050.1296.171.camel@Calliphara> 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:[] 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: [] .rodata.str1.1 [bios] 0x9ce (0xc7433f34)) [] .rodata.str1.1 [bios] 0x984 (0xc7433f38)) [] .rodata.str1.1 [bios] 0x84b (0xc7433f3c)) [] proc_file_read [kernel] 0xb6 (0xc7433f5c)) [] sys_read [kernel] 0x85 (0xc7433f9c)) [] 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 From stepan at openbios.org Thu Apr 22 08:32:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Thu Apr 22 08:32:00 2004 Subject: descriptive subjects ;) Message-ID: <20040422134203.GA7638@openbios.org> * Mathieu Deschamps [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 From rminnich at lanl.gov Thu Apr 22 08:38:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 22 08:38:00 2004 Subject: Open bios dev/bios bug report In-Reply-To: <1082641050.1296.171.camel@Calliphara> Message-ID: On 22 Apr 2004, Mathieu Deschamps wrote: > 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. If you're going to do that why not just use MTD? If it works it is pretty ideal. ron From mdeschamps at mangrove-systems.com Thu Apr 22 09:33:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Thu Apr 22 09:33:01 2004 Subject: Open bios dev/bios bug report In-Reply-To: References: Message-ID: <1082644968.1303.37.camel@Calliphara> Le jeu 22/04/2004 ? 15:51, ron minnich a ?crit : > On 22 Apr 2004, Mathieu Deschamps wrote: > > > 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. > > If you're going to do that why not just use MTD? > If it works it is pretty ideal. > > > ron > > short answer: True this is the final goal. other answer: This because of I gave myself several milestone before getting a LinuxBios booting my littlish kernel on DOC for embedded station. First get my main bios open and same other bios chip mounted onto a PCI novotech card with a DIP to PLCC adapter, if it's possible. I want to make it with dev/bios and the make a backup copy of my SST bios chip. I have done already one with someone that let me use his eeprom programmer, and well that horrible to handle, what a nightmare !! So long live dev/bios and its cat /dev/bios > /dev/otherbios because I have never seen a such simple call doing so much that's truely elegant. So I was saying, I want to make a(nother) backup copy with it, thus validating dev/bios : and if this new bios boots i'll go on Burn onto it my linuxbios.bin with no payload, debug with serial port, understand, correct buggy things. When it seems to be all right, i'll go on. I'll build a new linuxbios with a Hard disk IDE kernel payload , VGA support, Network support ... understand ... correct things... go on Endly, I'll build a new lb : a kernel payload for a DOC onto a PCI card DOC slot. In the Doc I'll try to put the main bios this aims : 1 flash chip centralizing bios and os a shared goal I believe :) And to be able to upgrade OS and bios on the same go (would be a plus)...Server centralize various linuxbios to distribute to clients is also to courageous aim fo me. In fact , we don't know how up this could go, so I let try to combine and see how far the rabbit hole runs ... Oh ...nearly forgot, i try also to clean my source tree, and to document my work also to submit it to linuxbios community . mathieu From mdeschamps at mangrove-systems.com Thu Apr 22 10:35:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Thu Apr 22 10:35:01 2004 Subject: descriptive subject ;) Message-ID: <1082645709.1303.48.camel@Calliphara> * Mathieu Deschamps [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 From kevin at koconnor.net Thu Apr 22 10:52:00 2004 From: kevin at koconnor.net (Kevin O'Connor) Date: Thu Apr 22 10:52:00 2004 Subject: =?utf-8?B?562U5aSN?= =?utf-8?Q?=3A?= flash_rom start and size In-Reply-To: <1082566142.12282.10.camel@exponential.lanl.gov> References: <3174569B9743D511922F00A0C943142304B86552@TYANWEB> <1082566142.12282.10.camel@exponential.lanl.gov> Message-ID: <20040422160532.GA14330@ohio.localdomain> On Wed, Apr 21, 2004 at 10:49:02AM -0600, Li-Ta Lo wrote: > On Wed, 2004-04-21 at 10:40, YhLu wrote: > > 2. or I only want to update the payload image in the beginning, [0,64k). > > > > you need some kind of flash translation layer to accomplish this. You > need to back up some part of the erase block you want reserve , erase > the block and write with updated and reserved data. If the start and end positions are not aligned to block boundaries then flash_rom should just return an error. It would be nice to be able to update a payload without having to burn the whole flash. (Rewriting the whole flash risks the possibility of an incomplete write which could leave the machine unbootable.) Of course, if the user wishes to do this then it should be the responsibility of the user to know the flash part and what boundaries to align the payloads. -Kevin -- --------------------------------------------------------------------- | Kevin O'Connor "BTW, IMHO we need a FAQ for | | kevin at koconnor.net 'IMHO', 'FAQ', 'BTW', etc. !" | --------------------------------------------------------------------- From stuge-linuxbios at cdy.org Thu Apr 22 11:02:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Thu Apr 22 11:02:01 2004 Subject: Open bios dev/bios bug report In-Reply-To: <1082644968.1303.37.camel@Calliphara> References: <1082644968.1303.37.camel@Calliphara> Message-ID: <20040422161543.GA14178@foo.birdnet.se> On Thu, Apr 22, 2004 at 04:42:48PM +0200, Mathieu Deschamps wrote: > > > > > 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. > > > > If you're going to do that why not just use MTD? > > If it works it is pretty ideal. > > short answer: True this is the final goal. > > other answer: This because of I gave myself several milestone before > getting a LinuxBios booting my littlish kernel on DOC for embedded > station. MTD is for all Memory Technology Devices - not just DOC. See http://www.linux-mtd.infradead.org/ and then enable it in your nearest kernel. :) //Peter From bmaly at angstrom.com Thu Apr 22 14:19:00 2004 From: bmaly at angstrom.com (Brian Maly) Date: Thu Apr 22 14:19:00 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= ATI rage xl.init In-Reply-To: <3174569B9743D511922F00A0C943142304B864FA@TYANWEB> References: <3174569B9743D511922F00A0C943142304B864FA@TYANWEB> Message-ID: <1082662636.9235.43.camel@maly> 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 at lanl.gov] > ????: 2004?4?14? 15:01 > ???: Brian Maly > ??: linuxbios at 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 at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From YhLu at tyan.com Thu Apr 22 14:24:00 2004 From: YhLu at tyan.com (YhLu) Date: Thu Apr 22 14:24:00 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= Message-ID: <3174569B9743D511922F00A0C943142304B8666A@TYANWEB> In the MB Config.lb, you need to enable keyboard and mouse in superio part. YH -----????----- ???: Brian Maly [mailto:bmaly at angstrom.com] ????: 2004?4?22? 12:37 ???: YhLu ??: ron minnich; linuxbios at 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 at lanl.gov] > ????: 2004?4?14? 15:01 > ???: Brian Maly > ??: linuxbios at 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 at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From bmaly at angstrom.com Thu Apr 22 15:46:01 2004 From: bmaly at angstrom.com (Brian Maly) Date: Thu Apr 22 15:46:01 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= =?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= ATI rage xl.init In-Reply-To: <3174569B9743D511922F00A0C943142304B8666A@TYANWEB> References: <3174569B9743D511922F00A0C943142304B8666A@TYANWEB> Message-ID: <1082667898.9235.47.camel@maly> I added the following and it worked like a charm: pnp 2e.5 on # Mouse irq 0x70 = 12 thanks again. -Regards, Brian On Thu, 2004-04-22 at 15:43, YhLu wrote: > In the MB Config.lb, you need to enable keyboard and mouse in superio part. > > YH > > -----????----- > ???: Brian Maly [mailto:bmaly at angstrom.com] > ????: 2004?4?22? 12:37 > ???: YhLu > ??: ron minnich; linuxbios at 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 at lanl.gov] > > ????: 2004?4?14? 15:01 > > ???: Brian Maly > > ??: linuxbios at 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 at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From rminnich at lanl.gov Thu Apr 22 16:25:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 22 16:25:00 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= =?UTF-8?Q?_=E7=AD=94=E5=A4=8D=3A?= ATI rage xl.init In-Reply-To: <1082667898.9235.47.camel@maly> Message-ID: can you send me a diff -u and I will apply this path. ron From kfuchs at winternet.com Thu Apr 22 23:20:01 2004 From: kfuchs at winternet.com (Ken Fuchs) Date: Thu Apr 22 23:20:01 2004 Subject: On which mainboards does LinuxBIOS function best? Message-ID: <200404230433.i3N4XwI14744@ecstasy1.winternet.com> 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 From YhLu at tyan.com Fri Apr 23 00:24:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 23 00:24:00 2004 Subject: Merge filo into Etherboot. Message-ID: <3174569B9743D511922F00A0C943142304B866F8@TYANWEB> 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 From mdeschamps at mangrove-systems.com Fri Apr 23 02:11:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Fri Apr 23 02:11:01 2004 Subject: Open bios dev/bios bug report In-Reply-To: <20040422161543.GA14178@foo.birdnet.se> References: <1082644968.1303.37.camel@Calliphara> <20040422161543.GA14178@foo.birdnet.se> Message-ID: <1082704848.1267.8.camel@Calliphara> Le jeu 22/04/2004 ? 18:15, Peter Stuge a ?crit : > On Thu, Apr 22, 2004 at 04:42:48PM +0200, Mathieu Deschamps wrote: > > > > > > > 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. > > > > > > If you're going to do that why not just use MTD? > > > If it works it is pretty ideal. > > > > short answer: True this is the final goal. > > > > other answer: This because of I gave myself several milestone before > > getting a LinuxBios booting my littlish kernel on DOC for embedded > > station. > > MTD is for all Memory Technology Devices - not just DOC. > > See http://www.linux-mtd.infradead.org/ and then enable it in your > nearest kernel. :) oh I know this quite well. I think I didn't made myself clear enough. Dev/bios opens or intents to open all the flash device of your hardware (that's explains read/write/>? MANY bios) , but I wondering if it could opens a DOC, since it's a IDE bus Flash device. Anyhow, DoC is the final goal first I intent to flash a "standard" bios chip > > > //Peter > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From stepan at openbios.org Fri Apr 23 04:14:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 23 04:14:01 2004 Subject: Merge filo into Etherboot. In-Reply-To: <3174569B9743D511922F00A0C943142304B866F8@TYANWEB> References: <3174569B9743D511922F00A0C943142304B866F8@TYANWEB> Message-ID: <20040423092939.GA16890@openbios.org> * YhLu [040423 07:47]: > 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? There's also a new development branch of grub called grub2. It might be worth looking at that one, keeping the guys from doing nasty PCisms while it's still under development Stefan From stepan at openbios.org Fri Apr 23 05:13:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 23 05:13:01 2004 Subject: Open bios dev/bios bug report In-Reply-To: <1082704848.1267.8.camel@Calliphara> References: <1082644968.1303.37.camel@Calliphara> <20040422161543.GA14178@foo.birdnet.se> <1082704848.1267.8.camel@Calliphara> Message-ID: <20040423102913.GA17853@openbios.org> * Mathieu Deschamps [040423 09:20]: > oh I know this quite well. I think I didn't made myself clear enough. > Dev/bios opens or intents to open all the flash device of your > hardware (that's explains read/write/>? MANY bios) , but I wondering if > it could opens a DOC, since it's a IDE bus Flash device. No, /dev/bios can't do DOC. Only directly mapped chips (system bios, and in theory pci option roms) can be accessed. No DOC, no CF. You have to go MTD for those. Stefan From stepan at openbios.org Fri Apr 23 06:26:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 23 06:26:01 2004 Subject: Open bios dev/bios bug report In-Reply-To: <1082641050.1296.171.camel@Calliphara> References: <1082641050.1296.171.camel@Calliphara> Message-ID: <20040423114215.GA18733@openbios.org> * Mathieu Deschamps [040422 15:37]: > BIOS driver v0.3.2 (writing disabled) for 2.4.20-8 Have you tried the bk version from bk clone bk://openbios.bkbits.net/unstable ? Stefan From rminnich at lanl.gov Fri Apr 23 09:20:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 23 09:20:00 2004 Subject: Open bios dev/bios bug report In-Reply-To: <1082704848.1267.8.camel@Calliphara> Message-ID: On 23 Apr 2004, Mathieu Deschamps wrote: > oh I know this quite well. I think I didn't made myself clear enough. > Dev/bios opens or intents to open all the flash device of your > hardware (that's explains read/write/>? MANY bios) , but I wondering if > it could opens a DOC, since it's a IDE bus Flash device. My first and most successful use of MTD was for DoC. It worked very well. ron From nacho at estudio-verona.com Fri Apr 23 09:36:01 2004 From: nacho at estudio-verona.com (Ignacio Verona) Date: Fri Apr 23 09:36:01 2004 Subject: Via epia m-II BiosSavior problems Message-ID: <1724.192.168.1.3.1082732061.squirrel@mail.estudio-verona.com> 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. From bmaly at angstrom.com Fri Apr 23 10:52:00 2004 From: bmaly at angstrom.com (Brian Maly) Date: Fri Apr 23 10:52:00 2004 Subject: =?ISO-8859-1?Q?Re:_=E7=AD=94=E5=A4=8D:_=E7?==?ISO-8859-1?Q?=AD=94=E5=A4=8D:_ATI_ra?=ge xl.init In-Reply-To: References: Message-ID: <1082732838.40893126a27eb@rand.angstrom.com> This change got the mouse working on arima/hdama (and automagically got the keyboard working as well) for ATI RageXL framebuffer console and X. Was this what you wanted? Maybe I misunderstood... -Regards, Brian [brian at localhost hdama]$ pwd /home/brian/freebios2/src/mainboard/arima/hdama [brian at localhost hdama]$ diff -u Config.lb.old Config.lb --- Config.lb.old 2004-04-23 11:45:01.000000000 -0400 +++ Config.lb 2004-04-23 11:46:56.000000000 -0400 @@ -291,7 +291,8 @@ io 0x60 = 0x3f8 irq 0x70 = 4 pnp 2e.4 off # SWC - pnp 2e.5 off # Mouse + pnp 2e.5 on # Mouse + irq 0x70 = 12 pnp 2e.6 on # Keyboard io 0x60 = 0x60 io 0x62 = 0x64 @@ -299,7 +300,7 @@ pnp 2e.7 off # GPIO pnp 2e.8 off # ACB pnp 2e.9 off # FSCM - pnp 2e.a off # WDT + pnp 2e.a off # WDT end end end Quoting ron minnich : > can you send me a diff -u and I will apply this path. > > ron > From mdeschamps at mangrove-systems.com Fri Apr 23 10:56:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Fri Apr 23 10:56:01 2004 Subject: Openbios 1.0.RC1 build problems In-Reply-To: <1082726976.1560.32.camel@Calliphara> References: <1082726976.1560.32.camel@Calliphara> Message-ID: <1082736452.1560.43.camel@Calliphara> Well I've tryied to make dev/bios with the old makefile and it works perfectly and i know why. The version i got unstable200404xx handle 2.6kernel policy change on modules or something like that But I still don't understand these part of your code: ifeq ($(KERNEL)/.config,$(wildcard $(KERNEL)/.config)) include $(KERNEL)/.config endif # see if we need module versions ifdef CONFIG_MODVERSIONS CFLAGS += -DMODVERSIONS endif In the 0.3.2 version in never hear about the need to include the kernel .config. When i say to managed to make it works that true, but it's tainted and this is an ugly "bricologe" Please I really need somebody to get me out of this . mathieu Le ven 23/04/2004 ? 15:29, Mathieu Deschamps a ?crit : > ok , I try a recent unstable version via openbios/snapshot/ > and just typed make without changing anything, it's seems > a .config file has not been built or a file misses in the > tar into forth directory. > > It's a new source tree organisation :) with a beautifull ncurse > config menu. > > ======================= > checking whether ln -s works... yes > checking for gcc... /usr/bin/gcc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether /usr/bin/gcc accepts -g... yes > checking for /usr/bin/gcc option to accept ANSI C... none needed > checking how to run the C preprocessor... /usr/bin/gcc -E > checking for bison... bison -y > checking for flex... flex > checking for yywrap in -lfl... yes > checking lex output file root... lex.yy > checking whether yytext is a pointer... yes > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whetherbut I can't find my herd back ! Please... g++ accepts > -g... yes > checking for m4... m4 > checking for as... as > checking for strip... strip > checking for ld... ld > checking for nm... nm > checking for install... install > checking dependency style... new > configure: creating ./config.status > config.status: creating Makefile.defs > config.status: creating mconfig.h > + Entering lxdialog > Compiling checklist.o : ok > Compiling menubox.o : ok > Compiling textbox.o : ok > Compiling yesno.o : ok > Compiling inputbox.o : ok > Compiling util.o : ok > Compiling lxdialog.o : ok > Compiling msgbox.o : ok > = Building lxdialog : ok > + Entering kconfig > Compiling zconf-y.o : ok > Compiling mconf.o : ok > = Building mconfig : ok > Compiling conf.o : ok > = Building config : ok > > > # End of OpenBIOS configuration. > # The next step is probably 'make'. > > config.status: creating Makefile.defs > config.status: creating mconfig.h > config.status: mconfig.h is unchanged > = Building openbios-1.0.RC1 [avr 23 2004 15:03] > + Entering libc > Compiling ctype.o : ok > Compiling extra.o : ok > Compiling misc.o : ok > Compiling string.o : ok > Compiling vsprintf.o : ok > Compiling diskio.o : ok > Compiling byteorder.o : ok > + Entering kernel > Compiling dict.o : ok > Compiling primitives.o : okmake -f Makefile.24 > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 bios_core.c -o bios_core.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 flashchips.c -o flashchips.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 pcisets.c -o pcisets.o > pcisets.c:234: warning: `gporeg_save' defined but not used > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 filesystem.c -o filesystem.o > filesystem.c:292: `THIS_MODULE' undeclared here (not in a function) > filesystem.c:292: initializer element is not constant > filesystem.c:292: (near initialization for `bios_fops.owner') > make: *** [filesystem.o] Error 1 > > Compiling stack.o : ok > Compiling bootstrap.o : ok > = Building forthc : ok > + Entering toke > Compiling toke.o : ok > Compiling emit.o : ok > Compiling dictionary.o : ok > Compiling stack.o : ok > Compiling stream.o : ok > Compiling macros.o : ok > Compiling scanner.o : ok > = Building toke : ok > + Entering forth > make[2]: *** No rule to make target `../.config', needed by > `../obj-x86/build/forth/lib.dict'. Stop. > make[1]: *** [sub-forth-all] Error 2 > make: *** [auto-bootstrap] Error 2 > > -------------------------------- > If i try to make devbios in devbios i have a > --------------------------------- > [unstable/dev/bios]make > > make -C /usr/src/linux SUBDIRS=`pwd` modules > make[1]: Entering directory `/usr/src/linux-2.4.20' > make -C /home/root/projet/src/unstable/utils/devbios > CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i486 > -malign-functions=0 -malign-jumps=0 -malign-loops=0 -DMODULE > -DMODVERSIONS -include > /usr/src/linux-2.4.20/include/linux/modversions.h" MAKING_MODULES=1 > modules > make[2]: Entering directory > `/home/root/projet-20042004/src/unstable/utils/devbios' > make[2]: *** No rule to make target `modules'. Stop. > make[2]: Leaving directory > `/home/root/projet-20042004/src/unstable/utils/devbios' > make[1]: *** [_mod_/home/root/projet/src/unstable/utils/devbios] Error 2 > make[1]: Leaving directory `/usr/src/linux-2.4.20' > make: *** [module] Error 2 > > I also try :wq > > > make -f Makefile.24 > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 bios_core.c -o bios_core.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 flashchips.c -o flashchips.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 pcisets.c -o pcisets.o > pcisets.c:234: warning: `gporeg_save' defined but not used > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 filesystem.c -o filesystem.o > filesystem.c:292: `THIS_MODULE' undeclared here (not in a function) > filesystem.c:292: initializer element is not constant > filesystem.c:292: (near initialization for `bios_fops.owner') > make: *** [filesystem.o] Error 1 > > > What's wrong ? I have lost myself in this new dist. > > mathieu From ollie at lanl.gov Fri Apr 23 12:15:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Fri Apr 23 12:15:00 2004 Subject: Why devices ARE or NOT on bus 0 ? Message-ID: <1082741333.18711.1075.camel@exponential.lanl.gov> Hello guys, How does the enumeration decide if the devices in 8111/8131 are on bus 0 or other bus ? Isn't that all these non-coherent devices are on PCIDEV(0,0,0), at power up ? How are they changed to their "real" PCIDEVFN ? We are having problems on ibm/e325 that these devices remain on bus 0 such that the current HT and PCI scan or resource allocation is totally fucked. The devices are on bus 0 device 1 or something, these devices are enumerated first than the northbridge so the northbridge does not get correct information about its "link" and can not set IO/MEM/BUS routing correctly (actually it refuse to set at all). Does anyone can help on this ? Ollie From YhLu at tyan.com Fri Apr 23 12:33:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 23 12:33:00 2004 Subject: ATI rage xl.init Message-ID: <3174569B9743D511922F00A0C943142304B8671A@TYANWEB> You only commit 4 & 5 ? -----????----- ???: Li-Ta Lo [mailto:ollie at 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 at 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 From ollie at lanl.gov Fri Apr 23 12:46:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Fri Apr 23 12:46:01 2004 Subject: ATI rage xl.init In-Reply-To: <3174569B9743D511922F00A0C943142304B8671A@TYANWEB> References: <3174569B9743D511922F00A0C943142304B8671A@TYANWEB> Message-ID: <1082743228.18711.1077.camel@exponential.lanl.gov> 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 at 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 at 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 > > From YhLu at tyan.com Fri Apr 23 14:52:00 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 23 14:52:00 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= Message-ID: <3174569B9743D511922F00A0C943142304B86741@TYANWEB> So I need to produce another patch except 3, 4 & 5? -----????----- ???: Li-Ta Lo [mailto:ollie at 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 at 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 at 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 > > From dwh at lanl.gov Fri Apr 23 16:38:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Fri Apr 23 16:38:00 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86741@TYANWEB> Message-ID: The only thing that didn't patch cleanly on my setup was a config file for a Tyan board. Was there anything else that didn't apply cleanly to a CVS tree, Ollie? It might be nice to get that ATi and btext stuff in there quickly since there are likely others who are very, very interested in this patch. Though I know Ron wanted to review the superIO and PNP changes a little more after finishing his paperwork :-/ On Fri, 23 Apr 2004, YhLu wrote: > So I need to produce another patch except 3, 4 & 5? > > -----????????----- > ??????: Li-Ta Lo [mailto:ollie at 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 at 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 at 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 > > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Fri Apr 23 17:11:01 2004 From: YhLu at tyan.com (YhLu) Date: Fri Apr 23 17:11:01 2004 Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IEFUSSByYWdlIHhsLmluaXQ=?= Message-ID: <3174569B9743D511922F00A0C943142304B86787@TYANWEB> 3, 4, 5 already in the CVS tree. YH -----????----- ???: Hendricks David W. [mailto:dwh at lanl.gov] ????: 2004?4?23? 14:52 ???: YhLu ??: Li-Ta Lo; ron minnich; Stefan Reinauer; LinuxBIOS ??: Re: ????: ATI rage xl.init The only thing that didn't patch cleanly on my setup was a config file for a Tyan board. Was there anything else that didn't apply cleanly to a CVS tree, Ollie? It might be nice to get that ATi and btext stuff in there quickly since there are likely others who are very, very interested in this patch. Though I know Ron wanted to review the superIO and PNP changes a little more after finishing his paperwork :-/ On Fri, 23 Apr 2004, YhLu wrote: > So I need to produce another patch except 3, 4 & 5? > > -----????????----- > ??????: Li-Ta Lo [mailto:ollie at 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 at 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 at 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 > > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From rminnich at lanl.gov Fri Apr 23 17:20:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 23 17:20:01 2004 Subject: =?GB2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= In-Reply-To: Message-ID: On Fri, 23 Apr 2004, Hendricks David W. wrote: > The only thing that didn't patch cleanly on my setup was a config file for > a Tyan board. Was there anything else that didn't apply cleanly to a CVS > tree, Ollie? It might be nice to get that ATi and btext stuff in there > quickly since there are likely others who are very, very interested in > this patch. Though I know Ron wanted to review the superIO and PNP > changes a little more after finishing his paperwork :-/ Ollie and David I'll let you go for it. I was most worried about the change to k8 north code. Please check that. It seems like this code is really needed. ron From rminnich at lanl.gov Fri Apr 23 17:23:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Fri Apr 23 17:23:00 2004 Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IEFUSSByYWdlIHhsLmluaXQ=?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86787@TYANWEB> Message-ID: On Fri, 23 Apr 2004, YhLu wrote: > 3, 4, 5 already in the CVS tree. so 1,2, should go in now I think, and 6,7, clearly go in? ron From ebiederman at lnxi.com Fri Apr 23 20:52:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Fri Apr 23 20:52:01 2004 Subject: Why devices ARE or NOT on bus 0 ? In-Reply-To: <1082741333.18711.1075.camel@exponential.lanl.gov> References: <1082741333.18711.1075.camel@exponential.lanl.gov> Message-ID: Li-Ta Lo writes: > Hello guys, > > How does the enumeration decide if the devices in > 8111/8131 are on bus 0 or other bus ? In LinuxBIOS only the cpus are on bus 0, at least when we are done. > Isn't that > all these non-coherent devices are on PCIDEV(0,0,0), > at power up ? How are they changed to their "real" > PCIDEVFN ? Not quite. Their bridge decides their bus number. The just start out at devfn 0 on which ever bus they are assigned. We do enumerate one of the chains statically before the general resource allocator hits, and I think we leave it at bus 0. > We are having problems on ibm/e325 that these devices > remain on bus 0 such that the current HT and PCI scan > or resource allocation is totally fucked. The devices > are on bus 0 device 1 or something, these devices are > enumerated first than the northbridge so the northbridge > does not get correct information about its "link" and > can not set IO/MEM/BUS routing correctly (actually it > refuse to set at all). You might need to specify the bridges/busses in Config.lb. I know the current code works and can handle this. > Does anyone can help on this ? Without something like a serial console trace so that the details of what are going on are clear I don't know. I have a hunch. The default code for setting things up is for pci devices. In the opteron mainboard files we need to specify non-default operations so we do the hypertransport scan. One of the things that does is to put everything back at devfn 0 if they have changed from someplace else. amdk8_scan_root_bus very deliberately avoids all of the other functions that are not cpus so if you are using it I don't see how you would run into the problem you have described. Eric From stepan at openbios.org Sat Apr 24 18:04:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Sat Apr 24 18:04:00 2004 Subject: ATI rage xl.init In-Reply-To: <3174569B9743D511922F00A0C943142304B86528@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86528@TYANWEB> Message-ID: <20040424232017.GA2633@openbios.org> Yinghai, > 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. I merged most of the missing stuff now. I had rejects in the following files, thus I did not touch them. Please resend a working diff against the next snapshot that appears. src/mainboard/tyan/s2882/Config.lb src/mainboard/tyan/s2885/Config.lb src/superio/winbond/w83627hf/superio.c src/superio/winbond/w83627hf/w83627hf_early_serial.c Also, do these two files belong in the ATI driver directory? ati/ragexl/fb.h ati/ragexl/fbcon.h Can they go somewhere generic? Let's try to reuse as much of the code as possible. src/include/pc80/btext.h: I've put this to console/btext.h since the btext console code lives in console/, not in pc80/ Stefan From stepan at openbios.org Sat Apr 24 18:23:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Sat Apr 24 18:23:00 2004 Subject: ??????: ??????: ATI rage xl.init In-Reply-To: References: <3174569B9743D511922F00A0C943142304B86787@TYANWEB> Message-ID: <20040424233920.GA4265@openbios.org> * ron minnich [040424 00:35]: > On Fri, 23 Apr 2004, YhLu wrote: > > > 3, 4, 5 already in the CVS tree. good, then things should be complete now. > so 1,2, should go in now I think, and 6,7, clearly go in? They're in now. I also included 8. YhLu, are they needed? Stefan From rminnich at lanl.gov Sun Apr 25 10:28:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 25 10:28:00 2004 Subject: ATI rage xl.init In-Reply-To: <20040424232017.GA2633@openbios.org> Message-ID: stefan, thanks very much. ron From yhlu at tyan.com Sun Apr 25 12:59:01 2004 From: yhlu at tyan.com (Yinghai Lu) Date: Sun Apr 25 12:59:01 2004 Subject: ATI rage xl.init In-Reply-To: <20040424233920.GA4265@openbios.org> Message-ID: <200404251658.i3PGwGK06607@nwn.definitive.org> 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. Regards YH -----????----- ???: Stefan Reinauer [mailto:stepan at openbios.org] ????: 2004?4?24? 16:39 ???: ron minnich ??: YhLu; Hendricks David W.; Li-Ta Lo; LinuxBIOS ??: Re: ??????: ??????: ATI rage xl.init * ron minnich [040424 00:35]: > On Fri, 23 Apr 2004, YhLu wrote: > > > 3, 4, 5 already in the CVS tree. good, then things should be complete now. > so 1,2, should go in now I think, and 6,7, clearly go in? They're in now. I also included 8. YhLu, are they needed? Stefan From yhlu at tyan.com Sun Apr 25 13:03:39 2004 From: yhlu at tyan.com (Yinghai Lu) Date: Sun Apr 25 13:03:39 2004 Subject: =?gb2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= In-Reply-To: <20040424232017.GA2633@openbios.org> Message-ID: <200404251658.i3PGwGK06608@nwn.definitive.org> >Also, do these two files belong in the ATI driver directory? > ati/ragexl/fb.h > ati/ragexl/fbcon.h >Can they go somewhere generic? Let's try to reuse as >much of the code as possible. I suggest We move these files to common place after we add fb/btext support to other onboard display chip. >src/include/pc80/btext.h: I've put this to console/btext.h since the >btext console code lives in console/, not in pc80/ You are right. Regards YH From ebiederman at lnxi.com Sun Apr 25 13:29:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Sun Apr 25 13:29:01 2004 Subject: ATI rage xl.init In-Reply-To: <200404251658.i3PGwGK06607@nwn.definitive.org> References: <200404251658.i3PGwGK06607@nwn.definitive.org> Message-ID: "Yinghai Lu" writes: > 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. As a general rule devices don't need that and it is the responsibility of the device driver to enable/os to enable it. So the master bit should only be enabled for devices that are needed to boot. So we do need to enable this on the ioapic that transmit interrupts over the pci bus for example. Both because it is needed to boot and because it is architectural hardware. Unless someone can show me a relevant passage of the pci spec, that says differently. Any linux device driver that can't cope with a device that does not have it's bus master bit clear and needs it set is broken. Devices with bus master set are allowed to DMA into main memory whenever they feel like it so it is dangerous to enable that bit indiscriminately. Eric From yhlu at tyan.com Sun Apr 25 15:34:00 2004 From: yhlu at tyan.com (Yinghai Lu) Date: Sun Apr 25 15:34:00 2004 Subject: =?gb2312?B?tPC4tDogQVRJIHJhZ2UgeGwuaW5pdA==?= In-Reply-To: Message-ID: <200404251933.i3PJX9K07122@nwn.definitive.org> I will double check if current kernel need that for every onboard device. YH -----????----- ???: Eric W. Biederman [mailto:eric at lnxi.com] ?? Eric W. Biederman ????: 2004?4?25? 11:47 ???: Yinghai Lu ??: 'Stefan Reinauer'; 'ron minnich'; 'Hendricks David W.'; 'Li-Ta Lo'; 'LinuxBIOS' ??: Re: ATI rage xl.init "Yinghai Lu" writes: > 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. As a general rule devices don't need that and it is the responsibility of the device driver to enable/os to enable it. So the master bit should only be enabled for devices that are needed to boot. So we do need to enable this on the ioapic that transmit interrupts over the pci bus for example. Both because it is needed to boot and because it is architectural hardware. Unless someone can show me a relevant passage of the pci spec, that says differently. Any linux device driver that can't cope with a device that does not have it's bus master bit clear and needs it set is broken. Devices with bus master set are allowed to DMA into main memory whenever they feel like it so it is dangerous to enable that bit indiscriminately. Eric From rminnich at lanl.gov Sun Apr 25 18:55:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Sun Apr 25 18:55:01 2004 Subject: ATI rage xl.init In-Reply-To: <200404251813.i3PIDGm6017148@mailproxy3.lanl.gov> Message-ID: 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 From stepan at openbios.org Mon Apr 26 03:49:00 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Mon Apr 26 03:49:00 2004 Subject: ATI rage xl.init In-Reply-To: References: <200404251658.i3PGwGK06607@nwn.definitive.org> Message-ID: <20040426090554.GB27004@openbios.org> * Eric W. Biederman [040425 20:46]: > As a general rule devices don't need that and it is the responsibility > of the device driver to enable/os to enable it. How do other OSes besides Linux do this? Are they broken as well? > Unless someone can show me a relevant passage of the pci spec, > that says differently. I think we can allow fixes for OS level problems in LinuxBIOS to some small extent, even though fixing the OS is highest priority if the OS is the problem. > Any linux device driver that can't cope with a device that does > not have it's bus master bit clear and needs it set is broken. s/linux//. There's a lot of things broken that we cope with, ie the need for both mptable and pirq table seems like such a thing. > Devices with bus master set are allowed to DMA into main memory > whenever they feel like it so it is dangerous to enable that > bit indiscriminately. --> If at all, it should be done with careful checking. Stefan From stepan at openbios.org Mon Apr 26 03:55:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Mon Apr 26 03:55:01 2004 Subject: ATI rage xl.init In-Reply-To: References: <200404251813.i3PIDGm6017148@mailproxy3.lanl.gov> Message-ID: <20040426090921.GC27004@openbios.org> * ron minnich [040426 02:09]: > 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. Then doing this for a small set of devices where it is tested and doesn't hurt seems ok, until there's a set of kernel fixes available. The way LinuxBIOS handles pci "initialization drivers" seems like the cleanest solution. It's still kind of a workaround, but at least it is not hacked somewhere into the code, but added in as a module Stefan From mdeschamps at mangrove-systems.com Mon Apr 26 04:06:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Mon Apr 26 04:06:01 2004 Subject: Still wandering how to parameter dev/bios Message-ID: <1082971084.1269.9.camel@Calliphara> hello, I still trying to parameter dev/bios to get it open another bios, but I just don't know. By default, insmod bios.o opens main bios into /dev/bios. As written in the README.bios, it is possible to open other devices since it says something on mknod /dev/gfxbios c 104 1 and also mknod /dev/hddbios c 104 2. Making nodes is possible by simply insmoding bios driver don't open every bios. If anyone already get it work onto other bios, please mail me your way so I can study it. Other idea also welcome. mathieu From stepan at openbios.org Mon Apr 26 04:33:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Mon Apr 26 04:33:01 2004 Subject: Still wandering how to parameter dev/bios In-Reply-To: <1082971084.1269.9.camel@Calliphara> References: <1082971084.1269.9.camel@Calliphara> Message-ID: <20040426094932.GB27277@openbios.org> * Mathieu Deschamps [040426 11:18]: > I still trying to parameter dev/bios to get it open another > bios, but I just don't know. By default, insmod bios.o opens > main bios into /dev/bios. As written in the README.bios, it > is possible to open other devices since it says something on > mknod /dev/gfxbios c 104 1 and also mknod /dev/hddbios c 104 2. > Making nodes is possible by simply insmoding bios driver don't open > every bios. If anyone already get it work onto other bios, please > mail me your way so I can study it. Opening other firmware chips besides the system firmware does not work currently. It stopped working with 2.4.x and I never got it working again (Haven't really looked into it, though since this works fine with mtd) Stefan From stepan at openbios.org Mon Apr 26 04:50:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Mon Apr 26 04:50:01 2004 Subject: Openbios 1.0.RC1 build problems In-Reply-To: <1082736452.1560.43.camel@Calliphara> References: <1082726976.1560.32.camel@Calliphara> <1082736452.1560.43.camel@Calliphara> Message-ID: <20040426100727.GA27764@openbios.org> * Mathieu Deschamps [040423 18:07]: > But I still don't understand these part of your code: > > ifeq ($(KERNEL)/.config,$(wildcard $(KERNEL)/.config)) > include $(KERNEL)/.config > endif > # see if we need module versions > ifdef CONFIG_MODVERSIONS > CFLAGS += -DMODVERSIONS > endif This is needed for those using module versioning. > In the 0.3.2 version in never hear about the need to > include the kernel .config. Yes. 0.3.2 is broken wrt module versioning > When i say to managed to make it works that true, > but it's tainted and this is an ugly "bricologe" taintet? Stefan From mdeschamps at mangrove-systems.com Mon Apr 26 08:35:01 2004 From: mdeschamps at mangrove-systems.com (Mathieu Deschamps) Date: Mon Apr 26 08:35:01 2004 Subject: Openbios 1.0.RC1 build problems ... solved ! In-Reply-To: <20040426100727.GA27764@openbios.org> References: <1082726976.1560.32.camel@Calliphara> <1082736452.1560.43.camel@Calliphara> <20040426100727.GA27764@openbios.org> Message-ID: <1082987237.1970.12.camel@Calliphara> ok I've found why it does this : > > > make -f Makefile.24 > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 bios_core.c -o bios_core.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 flashchips.c -o flashchips.o > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 pcisets.c -o pcisets.o > pcisets.c:234: warning: `gporeg_save' defined but not used > gcc -c -D__KERNEL__ -I/usr/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-common > -fno-strict-aliasing -pipe -DMODULE -DDEBUG -DMODVERSIONS > -mpreferred-stack-boundary=2 -march=i586 filesystem.c -o filesystem.o > filesystem.c:292: `THIS_MODULE' undeclared here (not in a function) > filesystem.c:292: initializer element is not constant > filesystem.c:292: (near initialization for `bios_fops.owner') > make: *** [filesystem.o] Error 1 > > It's because the $KERNEL is /usr/src/linux then gcc's -I is $KERNEL/include. It lacks module.h, because on my distro (RH9) module.h is in $KERNEL/include/linux/. It needs a Makefile.24 little update :) error was mentioning THIS_MODULE,module.h is the file that's containing #define THIS_MODULE (&__this_module) At the end it can be insmod anyway because of unresolved syms, it done for 2.6 kernel, well i knew what i was risking. Where could i find the 02/06/10 or the 02/04/12 version of devbios still based upon kernel 2.4 building ? Le lun 26/04/2004 ? 12:07, Stefan Reinauer a ?crit : > * Mathieu Deschamps [040423 18:07]: > > > But I still don't understand these part of your code: > > > > ifeq ($(KERNEL)/.config,$(wildcard $(KERNEL)/.config)) > > include $(KERNEL)/.config > > endif > > # see if we need module versions > > ifdef CONFIG_MODVERSIONS > > CFLAGS += -DMODVERSIONS > > endif > > This is needed for those using module versioning. > > > In the 0.3.2 version in never hear about the need to > > include the kernel .config. > > Yes. 0.3.2 is broken wrt module versioning > > > When i say to managed to make it works that true, > > but it's tainted and this is an ugly "bricologe" > > taintet? It's a module state, fo example when you force loading of a module hasn't been compiled for the machine you are trying to insmoding. It seems it's also some kind of internal authenficate signature. > > Stefan > > > From rminnich at lanl.gov Mon Apr 26 09:07:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 09:07:01 2004 Subject: ATI rage xl.init In-Reply-To: <20040426090554.GB27004@openbios.org> Message-ID: On Mon, 26 Apr 2004, Stefan Reinauer wrote: > > Devices with bus master set are allowed to DMA into main memory > > whenever they feel like it so it is dangerous to enable that > > bit indiscriminately. > > --> If at all, it should be done with careful checking. Here is a possible scenario. You are in linuxbios after somehow falling into it -- i.e., no power up, no reset has happened. Devices for whatever reason are not totally reset, including the ethernet device. The ethernet device is the kind with on-chip buffer queue pointerss. You enable bus master. Chip gets a broadcast packet. It writes it somewhere to memory, over code that won't get run in 2 or 3 weeks. 2 or 3 weeks later, the code is executed. Your kernel goes kaboom! How do you figure out what happened? This is a possible scenario that can happen once you start enabling bus master in the bios. ron From ollie at lanl.gov Mon Apr 26 10:41:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Mon Apr 26 10:41:01 2004 Subject: Why devices ARE or NOT on bus 0 ? In-Reply-To: References: <1082741333.18711.1075.camel@exponential.lanl.gov> Message-ID: <1082994930.18711.1081.camel@exponential.lanl.gov> > You might need to specify the bridges/busses in Config.lb. > I know the current code works and can handle this. > > > Does anyone can help on this ? > > Without something like a serial console trace so that the details > of what are going on are clear I don't know. > Please see that attached log. As you ca see the HyperTransport scan is not actually done in northbridge.c:amdk8_scan_chain(). It only prints the message before and after the for loop but skip the loop. Ollie > I have a hunch. The default code for setting things up is > for pci devices. In the opteron mainboard files we need to specify > non-default operations so we do the hypertransport scan. One > of the things that does is to put everything back at devfn 0 > if they have changed from someplace else. > > amdk8_scan_root_bus very deliberately avoids all of the other > functions that are not cpus so if you are using it I don't see > how you would run into the problem you have described. > > Eric > -------------- next part -------------- LinuxBIOS-1.1.6.0Fallback Thu Apr 22 15:12:08 MDT 2004 starting... setting up resource map....done. 02 nodes initialized. ht reset - Ram1.00 Ram1.01 Ram2.00 Ram2.01 Ram3 Initializing memory: done Initializing memory: done Clearing LinuxBIOS memory: done Ram4 Copying LinuxBIOS to ram. Jumping to LinuxBIOS. POST: 0x39 LinuxBIOS-1.1.6.0Fallback Thu Apr 22 15:12:08 MDT 2004 booting... POST: 0x40 Finding PCI configuration type. PCI: Using configuration type 1 POST: 0x5f Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Northbridge Enumerating: AMD K8 CPU Enumerating: AMD K8 CPU Enumerating: AMD 8111 Southbridge Enumerating: NSC 87366 Enumerating buses... PCI: pci_scan_bus for bus 0 POST: 0x24 PCI: 00:01.0 [1022/7450] bus ops PCI: 00:01.0 [1022/7450] enabled PCI: 00:01.1 [1022/7451] ops PCI: 00:01.1 [1022/7451] enabled PCI: 00:02.0 [1022/7450] bus ops PCI: 00:02.0 [1022/7450] enabled PCI: 00:02.1 [1022/7451] ops PCI: 00:02.1 [1022/7451] enabled PCI: 00:03.0 [1022/7460] bus ops PCI: 00:03.0 [1022/7460] enabled PCI: 00:04.0 [1022/7468] bus ops PCI: 00:04.0 [1022/7468] enabled PCI: 00:04.1 [1022/7469] ops PCI: 00:04.1 [1022/7469] enabled PCI: 00:04.2 [1022/746a] enabled PCI: 00:04.3 [1022/746b] ops PCI: 00:04.3 [1022/746b] enabled PCI: 00:04.5 [1022/746d] ops PCI: 00:04.5 [1022/746d] enabled PCI: 00:04.6 [1022/746e] ops PCI: 00:04.6 [1022/746e] enabled PCI: 00:18.0 [1022/1100] bus ops PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled PCI: 00:19.0 [1022/1100] bus ops PCI: 00:19.0 [1022/1100] enabled PCI: 00:19.1 [1022/1101] enabled PCI: 00:19.2 [1022/1102] enabled PCI: 00:19.3 [1022/1103] ops PCI: 00:19.3 [1022/1103] enabled POST: 0x25 PCI: pci_scan_bus for bus 1 POST: 0x24 PCI: 01:01.0 [14e4/1648] enabled PCI: 01:01.1 [14e4/1648] enabled PCI: 01:02.0 [1000/0030] enabled POST: 0x25 PCI: pci_scan_bus returning with max=01 POST: 0x55 PCI: pci_scan_bus for bus 2 POST: 0x24 POST: 0x25 PCI: pci_scan_bus returning with max=02 POST: 0x55 PCI: pci_scan_bus for bus 3 POST: 0x24 PCI: 03:00.0 [1022/7464] ops PCI: 03:00.0 [1022/7464] enabled PCI: 03:00.1 [1022/7464] ops PCI: 03:00.1 [1022/7464] enabled PCI: 03:00.2 [1022/7463] ops PCI: 03:00.2 [1022/7463] enabled PCI: 03:01.0 [1022/7462] ops PCI: 03:01.0 [1022/7462] enabled PCI: 03:05.0 [1002/4752] enabled POST: 0x25 PCI: pci_scan_bus returning with max=03 POST: 0x55 amdk8_scan_chains max: 3 starting... amdk8_scan_chains max: 3 done amdk8_scan_chains max: 3 starting... amdk8_scan_chains max: 3 done PCI: pci_scan_bus returning with max=03 POST: 0x55 done POST: 0x66 Allocating resources... Allocating VGA resource ASSIGN RESOURCES, bus 0 PCI: 00:01.0 1c <- [0x00001000 - 0x00001fff] bus 1 io PCI: 00:01.0 24 <- [0xfd200000 - 0xfd1fffff] bus 1 prefmem PCI: 00:01.0 20 <- [0xfd100000 - 0xfd1fffff] bus 1 mem ASSIGN RESOURCES, bus 1 PCI: 01:01.0 10 <- [0xfd100000 - 0xfd10ffff] mem PCI: 01:01.0 18 <- [0xfd110000 - 0xfd11ffff] mem PCI: 01:01.1 10 <- [0xfd120000 - 0xfd12ffff] mem PCI: 01:01.1 18 <- [0xfd130000 - 0xfd13ffff] mem PCI: 01:02.0 10 <- [0x00001000 - 0x000010ff] io PCI: 01:02.0 14 <- [0xfd140000 - 0xfd14ffff] mem PCI: 01:02.0 1c <- [0xfd150000 - 0xfd15ffff] mem ASSIGNED RESOURCES, bus 1 PCI: 00:01.1 10 <- [0xfd200000 - 0xfd200fff] mem PCI: 00:02.0 1c <- [0x00003000 - 0x00002fff] bus 2 io PCI: 00:02.0 24 <- [0xfd200000 - 0xfd1fffff] bus 2 prefmem PCI: 00:02.0 20 <- [0xfd200000 - 0xfd1fffff] bus 2 mem PCI: 00:02.1 10 <- [0xfd201000 - 0xfd201fff] mem PCI: 00:03.0 1c <- [0x00002000 - 0x00002fff] bus 3 io PCI: 00:03.0 24 <- [0xfd200000 - 0xfd1fffff] bus 3 prefmem PCI: 00:03.0 20 <- [0xfc000000 - 0xfd0fffff] bus 3 mem ASSIGN RESOURCES, bus 3 PCI: 03:00.0 10 <- [0xfd000000 - 0xfd000fff] mem PCI: 03:00.1 10 <- [0xfd001000 - 0xfd001fff] mem PCI: 03:00.2 10 <- [0xfd004000 - 0xfd0040ff] mem PCI: 03:00.2 14 <- [0xfd005000 - 0xfd00501f] mem PCI: 03:01.0 10 <- [0xfd002000 - 0xfd002fff] mem PCI: 03:05.0 10 <- [0xfc000000 - 0xfcffffff] mem PCI: 03:05.0 14 <- [0x00002000 - 0x000020ff] io PCI: 03:05.0 18 <- [0xfd003000 - 0xfd003fff] mem ASSIGNED RESOURCES, bus 3 PCI: 00:04.0 00 <- [0x00000000 - 0xffffffff] io PCI: 00:04.0 00 <- [0x00000000 - 0xffffffff] mem PCI: 00:04.1 20 <- [0x00003ce0 - 0x00003cef] io PCI: 00:04.2 10 <- [0x00003cc0 - 0x00003cdf] io PCI: 00:04.3 58 <- [0x00003000 - 0x000030ff] io PCI: 00:04.5 10 <- [0x00003400 - 0x000034ff] io PCI: 00:04.5 14 <- [0x00003c80 - 0x00003cbf] io PCI: 00:04.6 10 <- [0x00003800 - 0x000038ff] io PCI: 00:04.6 14 <- [0x00003c00 - 0x00003c7f] io PCI: 00:18.3 94 <- [0xf8000000 - 0xfbffffff] mem PCI: 00:19.3 94 <- [0xf8000000 - 0xfbffffff] mem ASSIGNED RESOURCES, bus 0 done. POST: 0x88 Enabling resourcess... PCI: 00:01.0 bridge ctrl <- 0003 PCI: 00:01.0 cmd <- 147 PCI: 01:01.0 cmd <- 142 PCI: 01:01.1 cmd <- 142 PCI: 01:02.0 cmd <- 143 PCI: 00:01.1 cmd <- 146 PCI: 00:02.0 bridge ctrl <- 0003 PCI: 00:02.0 cmd <- 147 PCI: 00:02.1 cmd <- 146 PCI: 00:03.0 bridge ctrl <- 000b PCI: 00:03.0 cmd <- 147 PCI: 03:00.0 cmd <- 142 PCI: 03:00.1 cmd <- 142 PCI: 03:00.2 cmd <- 142 PCI: 03:01.0 cmd <- 142 PCI: 03:05.0 cmd <- 1c3 PCI: 00:04.0 cmd <- 14f PCI: 00:04.1 cmd <- 141 PCI: 00:04.2 cmd <- 141 PCI: 00:04.3 cmd <- 141 PCI: 00:04.5 cmd <- 141 PCI: 00:04.6 cmd <- 141 PCI: 00:18.0 cmd <- 140 PCI: 00:18.1 cmd <- 140 PCI: 00:18.2 cmd <- 140 PCI: 00:18.3 cmd <- 140 PCI: 00:19.0 cmd <- 140 PCI: 00:19.1 cmd <- 140 PCI: 00:19.2 cmd <- 140 PCI: 00:19.3 cmd <- 140 done. Initializing devices... PCI: 00:18.0 init NB: Function 0 Misc Control.. done. PCI: 00:19.0 init NB: Function 0 Misc Control.. done. PCI: 00:01.0 init PCI: 00:02.0 init PCI: 00:03.0 init PCI: 00:04.0 init RTC Init RTC: Checksum invalid zeroing cmos Invalid CMOS LB checksum enabling HPET @0xfed00000 PCI: 00:04.1 init IDE1 IDE0 PCI: 00:04.3 init set power on after power fail PCI: 00:18.0 init NB: Function 0 Misc Control.. done. PCI: 00:18.3 init NB: Function 3 Misc Control.. done. PCI: 00:19.0 init NB: Function 0 Misc Control.. done. PCI: 00:19.3 init NB: Function 3 Misc Control.. done. PCI: 03:00.0 init PCI: 03:00.1 init PCI: 03:00.2 init Devices initialized POST: 0x89 mem[0].basek = 00000000 mem[0].sizek = 00000280 mem[1].basek = 00000300 mem[1].sizek = 001ffd00 POST: 0x70 totalram: 2048M Initializing CPU #0 POST: 0x60 Enabling cache... Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) type: WB Setting fixed MTRRs(24-88) type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 2048MB, type WB DONE variable MTRRs Clear out the extra MTRR's call intel_enable_fixed_mtrr() call intel_enable_var_mtrr() Leave setup_mtrrs POST: 0x6a done. Max cpuid index : 1 Vendor ID : AuthenticAMD Processor Type : 0x00 Processor Family : 0x0f Processor Model : 0x05 Processor Mask : 0x00 Processor Stepping : 0x08 Feature flags : 0x078bfbff POST: 0x92 MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled POST: 0x93 Clearing memory 0K - 1048576K: --------------- done Setting up local apic... apic_id: 0 done. POST: 0x9b CPU #0 Initialized POST: 0x75 secondary_cpu_init Waiting for 2 CPUS to stop mem[0].basek = 00000000 mem[0].sizek = 00000280 mem[1].basek = 00000300 mem[1].sizek = 001ffd00 Initializing CPU #1 POST: 0x60 Enabling cache... Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) type: WB Setting fixed MTRRs(24-88) type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 2048MB, type WB DONE variable MTRRs Clear out the extra MTRR's call intel_enable_fixed_mtrr() call intel_enable_var_mtrr() Leave setup_mtrrs POST: 0x6a done. Max cpuid index : 1 Vendor ID : AuthenticAMD Processor Type : 0x00 Processor Family : 0x0f Processor Model : 0x05 Processor Mask : 0x00 Processor Stepping : 0x08 Feature flags : 0x078bfbff POST: 0x92 MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled POST: 0x93 Clearing memory 1048576K - 2097152K: ---------------- done Setting up local apic... apic_id: 1 done. POST: 0x9b CPU #1 Initialized secondary_cpu_init 1/1 All AP CPUs stopped POST: 0x9a Checking IRQ routing tables... /home/ollie/work/freebios2_ollie/src/arch/i386/boot/pirq_routing.c: 33:check_pirq_routing_table() - irq_routing_table located at: 0x0000dcc0 /home/ollie/work/freebios2_ollie/src/arch/i386/boot/pirq_routing.c: 41:check_pirq_routing_table() - checksum is: 0x45 but should be: 0x46 done. Copying IRQ routing tables to 0xf0000...done. Verifing copy of IRQ routing tables at 0xf0000...done POST: 0x96 Wrote the mp table end at: 00000020 - 000001bc Wrote linuxbios table at: 00000500 - 00000d58 checksum 6c12 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 POST: 0xf8 23:stream_init() - rom_stream: 0xfffe0000 - 0xfffeffff Found ELF candiate at offset 0 New segment addr 0x100000 size 0x21f10 offset 0xa0 filesize 0x7f68 (cleaned up) New segment addr 0x100000 size 0x21f10 offset 0xa0 filesize 0x7f68 New segment addr 0x121f20 size 0x48 offset 0x8020 filesize 0x48 (cleaned up) New segment addr 0x121f20 size 0x48 offset 0x8020 filesize 0x48 Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000021f10 filesz: 0x0000000000007f68 Clearing Segment: addr: 0x0000000000107f68 memsz: 0x0000000000019fa8 Loading Segment: addr: 0x0000000000121f20 memsz: 0x0000000000000048 filesz: 0x0000000000000048 Jumping to boot code at 0x105928 POST: 0xfe FILO version 0.4.1 (ollie at exponential.lanl.gov) Tue Apr 20 15:04:55 MDT 2004 collect_linuxbios_info: Searching for LinuxBIOS tables... find_lb_table: Found canidate at: 00000500 find_lb_table: header checksum o.k. find_lb_table: table checksum o.k. find_lb_table: record count o.k. collect_linuxbios_info: Found LinuxBIOS table at: 00000500 convert_memmap: 0x00000000000000 0x00000000000db8 16 convert_memmap: 0x00000000000db8 0x0000000009f248 1 convert_memmap: 0x000000000c0000 0x00000000030000 1 convert_memmap: 0x000000000f0000 0x00000000000400 16 convert_memmap: 0x000000000f0400 0x0000007ff0fc00 1 pci_init: Scanning PCI: found 27 devices pci_init: 00:01.0 1022:7450 0604 00 pci_init: 00:01.1 1022:7451 0800 10 pci_init: 00:02.0 1022:7450 0604 00 pci_init: 00:02.1 1022:7451 0800 10 pci_init: 00:03.0 1022:7460 0604 00 pci_init: 00:04.0 1022:7468 0601 00 pci_init: 00:04.1 1022:7469 0101 8a pci_init: 00:04.2 1022:746a 0c05 00 pci_init: 00:04.3 1022:746b 0000 00 pci_init: 00:04.5 1022:746d 0401 00 pci_init: 00:04.6 1022:746e 0703 00 pci_init: 00:18.0 1022:1100 0600 00 pci_init: 00:18.1 1022:1101 0600 00 pci_init: 00:18.2 1022:1102 0600 00 pci_init: 00:18.3 1022:1103 0600 00 pci_init: 00:19.0 1022:1100 0600 00 pci_init: 00:19.1 1022:1101 0600 00 pci_init: 00:19.2 1022:1102 0600 00 pci_init: 00:19.3 1022:1103 0600 00 pci_init: 01:01.0 14e4:1648 0200 00 pci_init: 01:01.1 14e4:1648 0200 00 pci_init: 01:02.0 1000:0030 0100 00 pci_init: 03:00.0 1022:7464 0c03 10 pci_init: 03:00.1 1022:7464 0c03 10 pci_init: 03:00.2 1022:7463 0c03 20 pci_init: 03:01.0 1022:7462 0200 00 pci_init: 03:05.0 1002:4752 0300 00 Press for default boot, or for boot prompt... 3 2 1 timed out boot: hda1:/newkernel root=/dev/hda3 console=tty0 console=ttyS0,115200 hda: LBA48 40GB: IC35L060AVV207-0 Unknown filesystem type boot: hda1:/newkernel root=/dev/hda3 console=tty0 console=ttyS0,115200                                                                hda2:/boot/x86_64 root=/dev/hda2 console=ttyS0,115200 console=tty0 Mounted reiserfs Found Linux version 2.6.5 (root at k) #6 SMP Thu Apr 15 15:45:04 MDT 2004 bzImage. Loading kernel... ok Jumping to entry point... Bootdata ok (command line is root=/dev/hda2 console=ttyS0,115200 console=tty0) Linux version 2.6.5 (root at k) (gcc version 3.3.1 (SuSE Linux)) #6 SMP Thu Apr 15 15:45:04 MDT 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000db8 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 - 0000000080000000 (usable) init_memory_mapping Scan SMP from 0000010000000000 for 1024 bytes. On node 0 totalpages: 524288 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 520192 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: IBM <6>Product ID: E325 <6>APIC at: 0xFEE00000 Processor #0 15:5 APIC version 16 Bootup CPU Processor #1 15:5 APIC version 16 Bus #0 is PCI Bus #1 is PCI Bus #2 is PCI Bus #3 is PCI Bus #4 is ISA I/O APIC #2 Version 17 at 0xFEC00000. I/O APIC #3 Version 17 at 0xFD200000. I/O APIC #4 Version 17 at 0xFD201000. Int: type 3, pol 0, trig 0, bus 4, IRQ 00, APIC ID 2, APIC INT 00 Int: type 0, pol 0, trig 0, bus 4, IRQ 01, APIC ID 2, APIC INT 01 Int: type 0, pol 0, trig 0, bus 4, IRQ 00, APIC ID 2, APIC INT 02 Int: type 0, pol 0, trig 0, bus 4, IRQ 03, APIC ID 2, APIC INT 03 Int: type 0, pol 0, trig 0, bus 4, IRQ 04, APIC ID 2, APIC INT 04 Int: type 0, pol 0, trig 0, bus 4, IRQ 05, APIC ID 2, APIC INT 05 Int: type 0, pol 0, trig 0, bus 4, IRQ 06, APIC ID 2, APIC INT 06 Int: type 0, pol 0, trig 0, bus 4, IRQ 07, APIC ID 2, APIC INT 07 Int: type 0, pol 0, trig 0, bus 4, IRQ 08, APIC ID 2, APIC INT 08 Int: type 0, pol 0, trig 0, bus 4, IRQ 09, APIC ID 2, APIC INT 09 Int: type 0, pol 0, trig 0, bus 4, IRQ 0a, APIC ID 2, APIC INT 0a Int: type 0, pol 0, trig 0, bus 4, IRQ 0b, APIC ID 2, APIC INT 0b Int: type 0, pol 0, trig 0, bus 4, IRQ 0c, APIC ID 2, APIC INT 0c Int: type 0, pol 0, trig 0, bus 4, IRQ 0d, APIC ID 2, APIC INT 0d Int: type 0, pol 0, trig 0, bus 4, IRQ 0e, APIC ID 2, APIC INT 0e Int: type 0, pol 0, trig 0, bus 4, IRQ 0f, APIC ID 2, APIC INT 0f Int: type 0, pol 0, trig 0, bus 0, IRQ 13, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 0, IRQ 11, APIC ID 2, APIC INT 11 Int: type 0, pol 0, trig 0, bus 3, IRQ 03, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 3, IRQ 14, APIC ID 2, APIC INT 10 Int: type 0, pol 0, trig 0, bus 1, IRQ 04, APIC ID 3, APIC INT 00 Int: type 0, pol 0, trig 0, bus 1, IRQ 05, APIC ID 3, APIC INT 01 Int: type 0, pol 0, trig 0, bus 1, IRQ 08, APIC ID 3, APIC INT 02 Int: type 0, pol 0, trig 0, bus 2, IRQ 0c, APIC ID 2, APIC INT 10 Int: type 0, pol 0, trig 0, bus 2, IRQ 0d, APIC ID 2, APIC INT 11 Int: type 0, pol 0, trig 0, bus 2, IRQ 0e, APIC ID 2, APIC INT 12 Int: type 0, pol 0, trig 0, bus 2, IRQ 0f, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 2, IRQ 10, APIC ID 2, APIC INT 11 Int: type 0, pol 0, trig 0, bus 2, IRQ 11, APIC ID 2, APIC INT 12 Int: type 0, pol 0, trig 0, bus 2, IRQ 12, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 2, IRQ 13, APIC ID 2, APIC INT 10 Lint: type 3, pol 0, trig 0, bus 4, IRQ 00, APIC ID ff, APIC LINT 00 Lint: type 1, pol 0, trig 0, bus 4, IRQ 00, APIC ID ff, APIC LINT 01 Processors: 2 set_pte_phys ffffffffff5fd000 to fee00000 spp_getpage 000001000341d000 spp_getpage 000001000341e000 mapped APIC to ffffffffff5fd000 ( fee00000) set_pte_phys ffffffffff5fc000 to fec00000 mapped IOAPIC to ffffffffff5fc000 (00000000fec00000) set_pte_phys ffffffffff5fb000 to fd200000 mapped IOAPIC to ffffffffff5fb000 (00000000fd200000) set_pte_phys ffffffffff5fa000 to fd201000 mapped IOAPIC to ffffffffff5fa000 (00000000fd201000) Built 1 zonelists Kernel command line: root=/dev/hda2 console=ttyS0,115200 console=tty0 Initializing CPU#0 PID hash table entries: 16 (order 4: 256 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1595.073 MHz processor. Console: colour VGA+ 80x25 Memory: 2056248k/2097152k available (1681k kernel code, 40112k reserved, 691k data, 408k init) Calibrating delay loop... 3129.34 BogoMIPS Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Mount-cache hash table entries: 256 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) POSIX conformance testing by UNIFIX Using local APIC NMI watchdog using perfctr0 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU0: stepping 08 per-CPU timeslice cutoff: 1023.59 usecs. task migration cache decay timeout: 2 msecs. Getting VERSION: 40010 Getting VERSION: 40010 Getting ID: 0 Getting ID: f000000 Getting LVT0: 700 Getting LVT1: 400 enabled ExtINT on CPU#0 ESR value before enabling vector: 00000008 ESR value after enabling vector: 00000000 CPU present map: 3 Booting processor 1/1 rip 6000 rsp 1007ff95f58 Setting warm reset code and vector. 1. 2. 3. Asserting INIT. Waiting for send to finish... +Deasserting INIT. Waiting for send to finish... +#startup loops: 2. Sending STARTUP #1. After apic_write. Initializing CPU#1 CPU#1 (phys ID: 1) waiting for CALLOUT Startup point 1. Waiting for send to finish... +Sending STARTUP #2. After apic_write. Startup point 1. Waiting for send to finish... +After Startup. Before Callout 1. After Callout 1. CALLIN, before setup_local_APIC(). masked ExtINT on CPU#1 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Calibrating delay loop... 3186.68 BogoMIPS Stack at about 000001007ff95f0c CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) OK. stepping 08 CPU has booted. Before bogomips. Total of 2 processors activated (6316.03 BogoMIPS). Before bogocount - setting activated=1. Boot done. ENABLING IO-APIC IRQs Using IO-APIC 2 ...changing IO-APIC physical APIC ID to 2 ... ok. Using IO-APIC 3 ...changing IO-APIC physical APIC ID to 3 ... ok. Using IO-APIC 4 ...changing IO-APIC physical APIC ID to 4 ... ok. Synchronizing Arb IDs. ..TIMER: vector=0x31 pin1=2 pin2=0 testing the IO APIC....................... .................................... done. Using local APIC timer interrupts. Detected 12.461 MHz APIC timer. checking TSC synchronization across 2 CPUs: cpu 1: waiting for commence passed. time.c: Using PIT/TSC based timekeeping. waiting for cpu 1 cpu 1: setting up apic clock cpu 1: enabling apic timer cpu 1 eSetting cpu_online_map Brought up 2 CPUs NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) SCSI subsystem initialized PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: IDE base address fixup for 0000:00:04.1 PCI: Scanning for ghost devices on bus 0 PCI: Scanning for ghost devices on bus 1 PCI: Scanning for ghost devices on bus 2 PCI: Scanning for ghost devices on bus 3 PCI: IRQ init PCI: Interrupt Routing Table found at 0x00000100000f0000 00:18 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 00:01 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 01:02 slot=00 0:03/def8 1:00/def8 2:00/def8 3:00/def8 01:01 slot=00 0:01/def8 1:02/def8 2:00/def8 3:00/def8 00:02 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 02:03 slot=01 0:01/def8 1:02/def8 2:03/def8 3:04/def8 02:04 slot=02 0:02/def8 1:03/def8 2:04/def8 3:01/def8 00:03 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 03:00 slot=00 0:00/def8 1:00/def8 2:00/def8 3:04/def8 03:05 slot=00 0:01/def8 1:00/def8 2:00/def8 3:00/def8 00:04 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 00:18 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 PCI: Attempting to find IRQ router for 1022:746b PCI: Using IRQ router AMD8111 [1022/746b] at 0000:00:04.3 PCI: IRQ fixup querying PCI -> IRQ mapping bus:0, slot:4, pin:3. PCI->APIC IRQ transform: (B0,I4,P3) -> 19 querying PCI -> IRQ mapping bus:0, slot:4, pin:1. PCI->APIC IRQ transform: (B0,I4,P1) -> 17 querying PCI -> IRQ mapping bus:0, slot:4, pin:1. PCI->APIC IRQ transform: (B0,I4,P1) -> 17 querying PCI -> IRQ mapping bus:1, slot:1, pin:0. PCI->APIC IRQ transform: (B1,I1,P0) -> 24 querying PCI -> IRQ mapping bus:1, slot:1, pin:1. PCI->APIC IRQ transform: (B1,I1,P1) -> 25 querying PCI -> IRQ mapping bus:1, slot:2, pin:0. PCI->APIC IRQ transform: (B1,I2,P0) -> 26 querying PCI -> IRQ mapping bus:3, slot:0, pin:3. PCI->APIC IRQ transform: (B3,I0,P3) -> 19 querying PCI -> IRQ mapping bus:3, slot:0, pin:3. PCI->APIC IRQ transform: (B3,I0,P3) -> 19 querying PCI -> IRQ mapping bus:3, slot:0, pin:3. PCI->APIC IRQ transform: (B3,I0,P3) -> 19 querying PCI -> IRQ mapping bus:3, slot:1, pin:0. querying PCI -> IRQ mapping bus:0, slot:3, pin:1. querying PCI -> IRQ mapping bus:3, slot:5, pin:0. PCI->APIC IRQ transform: (B3,I5,P0) -> 16 PCI: Allocating resources PCI: Resource fd200000-fd200fff (f=204, d=0, p=0) PCI: Resource fd201000-fd201fff (f=204, d=0, p=0) PCI: Resource 00000f00-00000f0f (f=101, d=0, p=0) PCI: Resource 00003cc0-00003cdf (f=101, d=0, p=0) PCI: Resource 00003400-000034ff (f=101, d=0, p=0) PCI: Resource 00003c80-00003cbf (f=101, d=0, p=0) PCI: Resource 00003800-000038ff (f=101, d=0, p=0) PCI: Resource 00003c00-00003c7f (f=101, d=0, p=0) PCI: Resource fd100000-fd10ffff (f=204, d=0, p=0) PCI: Resource fd110000-fd11ffff (f=204, d=0, p=0) PCI: Resource fd120000-fd12ffff (f=204, d=0, p=0) PCI: Resource fd130000-fd13ffff (f=204, d=0, p=0) PCI: Resource 00001000-000010ff (f=101, d=0, p=0) PCI: Resource fd140000-fd14ffff (f=204, d=0, p=0) PCI: Resource fd150000-fd15ffff (f=204, d=0, p=0) PCI: Resource fd000000-fd000fff (f=200, d=0, p=0) PCI: Resource fd001000-fd001fff (f=200, d=0, p=0) PCI: Resource fd004000-fd0040ff (f=200, d=0, p=0) PCI: Resource fd005000-fd00501f (f=200, d=0, p=0) PCI: Resource fd002000-fd002fff (f=200, d=0, p=0) PCI: Resource fc000000-fcffffff (f=200, d=0, p=0) PCI: Resource 00002000-000020ff (f=101, d=0, p=0) PCI: Resource fd003000-fd003fff (f=200, d=0, p=0) set_pte_phys ffffffffff600000 to 38a000 spp_getpage 000001000374d000 IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ ikconfig 0.7 with /proc/config* lp: driver loaded but no devices found Real Time Clock Driver v1.12 Non-volatile memory driver v1.2 hw_random: AMD768 system management I/O registers at 0x3000. hw_random hardware driver 1.0.0 loaded Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Using anticipatory io scheduler floppy0: no floppy controllers found Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx AMD8111: IDE controller at PCI slot 0000:00:04.1 AMD8111: chipset revision 3 AMD8111: not 100% native mode: will probe irqs later AMD8111: 0000:00:04.1 (rev 03) UDMA133 controller ide0: BM-DMA at 0x0f00-0x0f07, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0x0f08-0x0f0f, BIOS settings: hdc:pio, hdd:pio hda: IC35L060AVV207-0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 1024KiB hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100) hda: hda1 hda2 mice: PS/2 mouse device common for all mice i8042.c: Can't read CTR while initializing i8042. NET: Registered protocol family 2 IP: routing cache hash table of 8192 buckets, 128Kbytes TCP: Hash tables configured (established 262144 bind 65536) ip_conntrack version 2.1 (8192 buckets, 65536 max) - 440 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team ipt_recent v0.3.1: Stephen Frost . http://snowman.net/projects/ipt_recent/ arp_tables: (C) 2002 David S. Miller NET: Registered protocol family 1 NET: Registered protocol family 17 found reiserfs format "3.6" with standard journal Reiserfs journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 reiserfs: checking transaction log (hda2) for (hda2) Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 408k freed Adding 1052216k swap on /dev/hda1. Priority:42 extents:1 ieee1394: raw1394: /dev/raw1394 device initialized Welcome to SuSE Linux 9.0 (x86-64) - Kernel 2.6.5 (ttyS0). l login: guest Password: Last login: Wed Apr 21 15:56:21 on ttyS0 Have a lot of fun... guest at l:/> su Password: l:/ # lspci -vvv 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [a0] Capabilities: [b8] #08 [8000] Capabilities: [c0] #08 [0041] 00:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [a0] Capabilities: [b8] #08 [8000] 00:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [c0] #08 [0083] Capabilities: [f0] #08 [8000] 00:04.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=1M] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [68] PCI-X non-bridge device. Command: DPERE- ERO- RBC=0 OST=4 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) (prog-if 10 [OHCI]) Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=64K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 03:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA]) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=128K] Capabilities: [5c] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- l:/ # lspci -xxx 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00: 22 10 50 74 57 01 30 02 12 00 04 06 00 40 81 00 10: 00 00 00 00 00 00 00 00 00 01 01 40 11 11 20 22 20: 10 fd 10 fd 21 fd 11 fd 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 ff 00 03 00 40: 05 00 1f 00 00 00 00 00 02 0c 00 00 01 2c 00 00 50: 00 00 03 00 00 00 05 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 07 b8 83 00 08 00 03 00 0e 00 0e 00 02 00 02 00 b0: 00 00 00 00 00 00 00 00 08 c0 00 80 00 00 00 03 c0: 08 00 41 00 22 00 11 11 22 00 00 00 22 04 35 00 d0: 02 00 35 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 08 08 0e 00 08 08 0e 00 0f 0f 16 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00: 22 10 51 74 06 00 00 02 01 10 00 08 00 00 00 00 10: 04 00 20 fd 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 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 03 00 00 00 04 00 20 fd 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:02.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00: 22 10 50 74 57 01 30 02 12 00 04 06 00 40 81 00 10: 00 00 00 00 00 00 00 00 00 02 02 40 31 21 20 22 20: 20 fd 10 fd 21 fd 11 fd 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 ff 00 03 00 40: 05 00 1f 00 00 00 00 00 00 00 00 00 01 2c 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 07 b8 83 00 10 00 03 00 0e 00 0e 00 02 00 02 00 b0: 00 00 00 00 00 00 00 00 08 00 00 80 00 00 00 04 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 00 00 00 00 00 00 00 00 00 00 00:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00: 22 10 51 74 06 00 00 02 01 10 00 08 00 00 00 00 10: 04 10 20 fd 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 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 03 00 00 00 04 10 20 fd 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:03.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 00: 22 10 60 74 47 01 30 02 07 00 04 06 00 40 01 00 10: 00 00 00 00 00 00 00 00 00 03 03 40 20 20 00 22 20: 00 fc 00 fd 20 fd 10 fd 00 00 00 00 00 00 00 00 30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 0b 08 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 04 06 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 08 f0 83 00 22 00 00 00 d0 00 00 00 22 00 01 00 d0: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 08 00 01 00 08 00 11 00 0f 00 1a 00 00 00 00 00 f0: 08 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00:04.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 00: 22 10 68 74 0f 00 20 02 05 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 30 07 80 01 00 00 02 ff ff 00 01 00 00 00 c0 50: 00 00 00 00 85 01 00 00 44 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 de 00 00 00 00 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: 01 00 d0 fe 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 00: 22 10 69 74 05 00 00 02 03 8a 01 01 00 40 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00 40: 43 f0 0f 00 00 00 00 00 5e 20 5e 20 22 00 20 20 50: 03 c0 03 c6 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 (rev 02) 00: 22 10 6a 74 01 00 00 02 02 00 05 0c 00 40 00 00 10: c1 3c 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 00 00 00 00 00 00 00 00 00 04 00 00 40: 02 00 05 0c 00 00 00 00 06 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.3 Non-VGA unclassified device: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) 00: 22 10 6b 74 00 00 80 02 05 00 00 00 00 40 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 80 d1 00 07 00 00 00 00 20 14 10 00 00 00 00 00 50: 00 80 00 00 0f 00 00 00 01 30 00 00 00 00 00 00 60: 00 00 00 00 13 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 01 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: 3d 40 7f 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-8111 AC97 Audio (rev 03) 00: 22 10 6d 74 01 00 00 02 03 00 01 04 00 40 00 00 10: 01 34 00 00 81 3c 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 00 00 00 00 00 00 00 00 00 02 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.6 Modem: Advanced Micro Devices [AMD] AMD-8111 MC97 Modem (rev 03) 00: 22 10 6e 74 01 00 00 02 03 00 03 07 00 40 00 00 10: 01 38 00 00 01 3c 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 00 00 00 00 00 00 00 00 00 02 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 00 11 00 00 10 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 40: 01 01 09 00 08 08 01 00 01 01 01 00 01 01 01 00 50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00 60: 10 00 01 00 e4 01 00 00 00 c8 00 0f 5c 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 08 a0 01 21 d0 00 11 77 22 00 75 80 02 00 00 00 90: c7 13 30 06 00 00 00 00 00 00 00 00 00 00 00 00 a0: 08 c0 01 21 20 00 11 11 22 04 75 80 02 00 00 00 b0: 56 04 51 02 00 00 00 00 07 00 00 00 00 00 00 00 c0: 08 00 01 21 20 00 11 11 22 05 75 80 02 00 00 00 d0: 13 56 13 04 00 00 00 00 03 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 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 01 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 03 00 00 00 00 00 3f 00 03 00 40 00 01 00 7f 00 50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00 70: 00 00 00 00 06 00 00 00 00 00 00 00 07 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: 03 d0 fe 00 10 d0 fe 00 03 0a 00 00 10 0b 00 00 b0: 03 c0 fe 00 10 c0 fe 00 03 00 fc 00 10 2f fe 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 33 00 00 00 10 f0 ff 01 e0: 00 00 00 00 00 00 00 00 00 00 00 00 03 01 00 ff f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 02 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 fe e0 03 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 40 00 00 00 00 00 00 00 35 33 72 13 20 0a 10 00 90: 00 8c 23 08 08 0b 5b 0a 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: a4 c3 94 84 5e 00 00 00 75 59 98 ce 9f 3c ba fa c0: 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 52 ae cf f1 ac f1 af ef 18 dc 97 fa ff 85 d5 9d e0: 1b af d5 50 b8 e5 4c fc be cf 8c f2 f7 96 ed e4 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 03 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: ff 3b 00 00 40 00 c0 02 00 00 00 00 00 00 00 00 50: 10 50 10 00 10 00 00 00 16 16 16 00 00 e0 02 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 11 01 02 51 11 80 00 50 00 38 00 08 1b 22 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 02 00 00 00 7c 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 e0 b2 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 07 07 e2 04 00 00 00 00 00 00 25 00 e0: 00 00 00 00 20 16 59 00 1b 01 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 00 11 00 00 10 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 40: 08 08 01 00 01 01 09 00 01 01 01 00 01 01 01 00 50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00 60: 11 00 01 00 e4 00 00 00 00 c8 00 0f 78 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 08 a0 01 21 d0 00 11 77 22 00 75 80 02 00 00 00 90: 7f d7 00 06 00 00 00 00 00 00 00 00 00 00 00 00 a0: 08 c0 01 21 d0 00 11 77 22 00 75 80 02 00 00 00 b0: e0 f3 31 06 00 00 00 00 00 00 00 00 00 00 00 00 c0: 08 00 01 21 20 00 11 11 22 05 75 80 02 00 00 00 d0: 13 56 13 04 00 00 00 00 03 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 00 00 00 00 00 00 00 00 00 00 00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 01 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 03 00 00 00 00 00 3f 00 03 00 40 00 01 00 7f 00 50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00 70: 00 00 00 00 06 00 00 00 00 00 00 00 07 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: 03 d0 fe 00 10 d0 fe 00 03 0a 00 00 10 0b 00 00 b0: 03 c0 fe 00 10 c0 fe 00 03 00 fc 00 10 2f fe 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 33 00 00 00 10 f0 ff 01 e0: 00 00 00 00 00 00 00 00 00 00 00 00 03 01 00 ff f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 02 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 fe e0 03 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 04 00 00 00 00 00 00 00 35 33 72 13 20 0a 10 00 90: 00 8c 13 08 08 0b 5b 06 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 08 84 91 84 5e 00 00 00 3d 98 3d cc 0f 10 fe e7 c0: 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: e5 f9 9d b2 fb e4 c6 3d 08 a5 8a bd 99 4d 9a 65 e0: d0 49 d8 b8 75 66 87 da cc b3 a8 2f 8b 66 5c f5 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 03 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: ff 3b 00 00 40 00 c0 02 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 16 16 16 00 40 de 02 40 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 11 01 02 51 11 80 00 50 00 38 00 08 1b 22 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 02 00 00 00 7c 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 38 00 00 60 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 07 07 e2 04 00 00 00 00 00 00 25 00 e0: 00 00 00 00 20 14 56 00 1b 01 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) 00: e4 14 48 16 42 01 b0 02 03 00 00 02 10 40 80 00 10: 04 00 10 fd 00 00 00 00 04 00 11 fd 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 a6 02 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 40 00 40: 07 48 02 00 08 01 43 04 01 50 02 c0 00 21 00 64 50: 03 58 70 00 2a 32 04 80 05 00 86 00 98 e0 a0 00 60: 6d 23 89 44 00 00 00 00 00 00 03 20 00 00 00 00 70: 02 32 00 00 c6 00 00 00 50 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 01 00 fe 90 28 02 90: 01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 01:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) 00: e4 14 48 16 42 01 b0 02 03 00 00 02 10 40 80 00 10: 04 00 12 fd 00 00 00 00 04 00 13 fd 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 a6 02 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 02 40 00 40: 07 48 02 00 09 01 43 04 01 50 02 c0 00 21 00 64 50: 03 58 3c 00 c1 fb db bd 05 00 86 00 bc ef e1 b1 60: 88 ff eb df 72 bc 00 00 00 00 03 20 00 00 00 00 70: 02 32 00 00 c6 00 00 00 50 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 fe 90 68 02 90: 01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 04 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 00 00 00 00 00 00 00 00 00 00 01:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) 00: 00 10 30 00 43 01 30 02 07 00 00 01 10 40 00 00 10: 01 10 00 00 04 00 14 fd 00 00 00 00 04 00 15 fd 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 10 12 30: 00 00 00 00 50 00 00 00 00 00 00 00 00 01 11 12 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 01 58 02 06 00 00 00 00 05 68 80 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 07 00 40 00 10 01 43 06 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 00: 22 10 64 74 02 01 80 02 0b 10 03 0c 00 40 80 00 10: 00 00 00 fd 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 00 00 00 00 00 00 00 00 00 04 00 50 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 00: 22 10 64 74 02 01 80 02 0b 10 03 0c 00 40 00 00 10: 00 10 00 fd 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 00 00 00 00 00 00 00 00 00 04 00 50 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:00.2 USB Controller: Advanced Micro Devices [AMD]: Unknown device 7463 (rev 02) 00: 22 10 63 74 02 00 10 02 02 20 03 0c 00 40 00 00 10: 00 40 00 fd 00 50 00 fd 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 63 74 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 04 00 00 40: 01 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 20 20 01 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 22 10 63 74 01 00 00 00 40 30 00 01 00 00 00 00 80: 0a 88 00 40 00 00 00 00 01 00 82 fe 00 01 00 00 90: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:01.0 Ethernet controller: Advanced Micro Devices [AMD] AMD-8111 Ethernet (rev 03) 00: 22 10 62 74 02 00 10 02 03 00 00 02 10 40 00 00 10: 00 20 00 fd 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 40 00 00 00 00 00 00 00 00 01 18 18 40: 01 00 02 fe 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 00: 02 10 52 47 83 00 90 02 27 00 00 03 10 40 00 00 10: 00 00 00 fc 01 20 00 00 00 30 00 fd 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 5c 00 00 00 00 00 00 00 00 01 08 00 40: 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 02 5c 10 00 01 00 00 ff 00 00 00 00 01 00 02 06 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 l:/ # lspci -tv -[00]-+-01.0-[01]--+-01.0 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet | +-01.1 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet | \-02.0 LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI +-01.1 Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC +-02.0-[02]-- +-02.1 Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC +-03.0-[03]--+-00.0 Advanced Micro Devices [AMD] AMD-8111 USB | +-00.1 Advanced Micro Devices [AMD] AMD-8111 USB | +-00.2 Advanced Micro Devices [AMD]: Unknown device 7463 | +-01.0 Advanced Micro Devices [AMD] AMD-8111 Ethernet | \-05.0 ATI Technologies Inc Rage XL +-04.0 Advanced Micro Devices [AMD] AMD-8111 LPC +-04.1 Advanced Micro Devices [AMD] AMD-8111 IDE +-04.2 Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 +-04.3 Advanced Micro Devices [AMD] AMD-8111 ACPI +-04.5 Advanced Micro Devices [AMD] AMD-8111 AC97 Audio +-04.6 Advanced Micro Devices [AMD] AMD-8111 MC97 Modem +-18.0 Advanced Micro Devices [AMD] K8 NorthBridge +-18.1 Advanced Micro Devices [AMD] K8 NorthBridge +-18.2 Advanced Micro Devices [AMD] K8 NorthBridge +-18.3 Advanced Micro Devices [AMD] K8 NorthBridge +-19.0 Advanced Micro Devices [AMD] K8 NorthBridge +-19.1 Advanced Micro Devices [AMD] K8 NorthBridge +-19.2 Advanced Micro Devices [AMD] K8 NorthBridge \-19.3 Advanced Micro Devices [AMD] K8 NorthBridge l:/ # lspci -v 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: 00001000-00001fff Memory behind bridge: fd100000-fd1fffff Capabilities: [a0] Capabilities: [b8] #08 [8000] Capabilities: [c0] #08 [0041] 00:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Flags: bus master, medium devsel, latency 0 Memory at fd200000 (64-bit, non-prefetchable) [size=4K] 00:02.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 64 Bus: primary=00, secondary=02, subordinate=02, sec-latency=64 Capabilities: [a0] Capabilities: [b8] #08 [8000] 00:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Flags: bus master, medium devsel, latency 0 Memory at fd201000 (64-bit, non-prefetchable) [size=4K] 00:03.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 64 Bus: primary=00, secondary=03, subordinate=03, sec-latency=64 I/O behind bridge: 00002000-00002fff Memory behind bridge: fc000000-fd0fffff Capabilities: [c0] #08 [0083] Capabilities: [f0] #08 [8000] 00:04.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) Flags: bus master, 66Mhz, medium devsel, latency 0 00:04.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) (prog-if 8a [Master SecP PriP]) Flags: bus master, medium devsel, latency 64 I/O ports at 0f00 [size=16] 00:04.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 (rev 02) Flags: medium devsel, IRQ 19 I/O ports at 3cc0 [size=32] 00:04.3 Non-VGA unclassified device: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) Flags: medium devsel 00:04.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-8111 AC97 Audio (rev 03) Flags: medium devsel, IRQ 17 I/O ports at 3400 [size=256] I/O ports at 3c80 [size=64] 00:04.6 Modem: Advanced Micro Devices [AMD] AMD-8111 MC97 Modem (rev 03) (prog-if 00 [Generic]) Flags: medium devsel, IRQ 17 I/O ports at 3800 [size=256] I/O ports at 3c00 [size=128] 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel Capabilities: [80] #08 [2101] Capabilities: [a0] #08 [2101] Capabilities: [c0] #08 [2101] 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel 00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel Capabilities: [80] #08 [2101] Capabilities: [a0] #08 [2101] Capabilities: [c0] #08 [2101] 00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel 00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel 00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge Flags: fast devsel 01:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) Subsystem: IBM: Unknown device 02a6 Flags: 66Mhz, medium devsel, IRQ 24 Memory at fd100000 (64-bit, non-prefetchable) [size=64K] Memory at fd110000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable- 01:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) Subsystem: IBM: Unknown device 02a6 Flags: 66Mhz, medium devsel, IRQ 25 Memory at fd120000 (64-bit, non-prefetchable) [size=64K] Memory at fd130000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable- 01:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) Subsystem: Micro-Star International Co., Ltd.: Unknown device 1210 Flags: 66Mhz, medium devsel, IRQ 26 I/O ports at 1000 [size=256] Memory at fd140000 (64-bit, non-prefetchable) [size=64K] Memory at fd150000 (64-bit, non-prefetchable) [size=64K] Expansion ROM at [disabled] [size=1M] Capabilities: [50] Power Management version 2 Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [68] PCI-X non-bridge device. 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) (prog-if 10 [OHCI]) Flags: medium devsel, IRQ 19 Memory at fd000000 (32-bit, non-prefetchable) [size=4K] 03:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) (prog-if 10 [OHCI]) Flags: medium devsel, IRQ 19 Memory at fd001000 (32-bit, non-prefetchable) [size=4K] 03:00.2 USB Controller: Advanced Micro Devices [AMD]: Unknown device 7463 (rev 02) (prog-if 20 [EHCI]) Subsystem: Advanced Micro Devices [AMD]: Unknown device 7463 Flags: medium devsel, IRQ 19 Memory at fd004000 (32-bit, non-prefetchable) [size=256] Memory at fd005000 (32-bit, non-prefetchable) [size=32] Capabilities: [80] #0a [4000] Capabilities: [88] Power Management version 2 03:01.0 Ethernet controller: Advanced Micro Devices [AMD] AMD-8111 Ethernet (rev 03) Flags: medium devsel Memory at fd002000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at [disabled] [size=64K] Capabilities: [40] Power Management version 2 03:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA]) Flags: stepping, medium devsel, IRQ 16 Memory at fc000000 (32-bit, non-prefetchable) [size=16M] I/O ports at 2000 [size=256] Memory at fd003000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at [disabled] [size=128K] Capabilities: [5c] Power Management version 2 l:/ # lspci -t -[00]-+-01.0-[01]--+-01.0 | +-01.1 | \-02.0 +-01.1 +-02.0-[02]-- +-02.1 +-03.0-[03]--+-00.0 | +-00.1 | +-00.2 | +-01.0 | \-05.0 +-04.0 +-04.1 +-04.2 +-04.3 +-04.5 +-04.6 +-18.0 +-18.1 +-18.2 +-18.3 +-19.0 +-19.1 +-19.2 \-19.3 l:/ # Restarting system. Copying LinuxBIOS to ram. Jumping to LinuxBIOS. POST: 0x39 LinuxBIOS-1.1.6.0Fallback Thu Apr 22 15:37:17 MDT 2004 rebooting... POST: 0x40 Finding PCI configuration type. PCI: Using configuration type 1 POST: 0x5f Enumerating: AMD K8 Northbridge Enumerating: AMD K8 Northbridge Enumerating: AMD K8 CPU Enumerating: AMD K8 CPU Enumerating: AMD 8111 Southbridge Enumerating: NSC 87366 Enumerating buses... PCI: pci_scan_bus for bus 0 POST: 0x24 PCI: 00:01.0 [1022/7450] bus ops PCI: 00:01.0 [1022/7450] enabled PCI: 00:01.1 [1022/7451] ops PCI: 00:01.1 [1022/7451] enabled PCI: 00:02.0 [1022/7450] bus ops PCI: 00:02.0 [1022/7450] enabled PCI: 00:02.1 [1022/7451] ops PCI: 00:02.1 [1022/7451] enabled PCI: 00:03.0 [1022/7460] bus ops PCI: 00:03.0 [1022/7460] enabled PCI: 00:04.0 [1022/7468] bus ops PCI: 00:04.0 [1022/7468] enabled PCI: 00:04.1 [1022/7469] ops PCI: 00:04.1 [1022/7469] enabled PCI: 00:04.2 [1022/746a] enabled PCI: 00:04.3 [1022/746b] ops PCI: 00:04.3 [1022/746b] enabled PCI: 00:04.5 [1022/746d] ops PCI: 00:04.5 [1022/746d] enabled PCI: 00:04.6 [1022/746e] ops PCI: 00:04.6 [1022/746e] enabled PCI: 00:18.0 [1022/1100] bus ops PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] ops PCI: 00:18.3 [1022/1103] enabled PCI: 00:19.0 [1022/1100] bus ops PCI: 00:19.0 [1022/1100] enabled PCI: 00:19.1 [1022/1101] enabled PCI: 00:19.2 [1022/1102] enabled PCI: 00:19.3 [1022/1103] ops PCI: 00:19.3 [1022/1103] enabled POST: 0x25 PCI: pci_scan_bus for bus 1 POST: 0x24 PCI: 01:01.0 [14e4/1648] enabled PCI: 01:01.1 [14e4/1648] enabled PCI: 01:02.0 [1000/0030] enabled POST: 0x25 PCI: pci_scan_bus returning with max=01 POST: 0x55 PCI: pci_scan_bus for bus 2 POST: 0x24 POST: 0x25 PCI: pci_scan_bus returning with max=02 POST: 0x55 PCI: pci_scan_bus for bus 3 POST: 0x24 PCI: 03:00.0 [1022/7464] ops PCI: 03:00.0 [1022/7464] enabled PCI: 03:00.1 [1022/7464] ops PCI: 03:00.1 [1022/7464] enabled PCI: 03:00.2 [1022/7463] ops PCI: 03:00.2 [1022/7463] enabled PCI: 03:01.0 [1022/7462] ops PCI: 03:01.0 [1022/7462] enabled PCI: 03:05.0 [1002/4752] enabled POST: 0x25 PCI: pci_scan_bus returning with max=03 POST: 0x55 amdk8_scan_chains max: 3 starting... amdk8_scan_chains max: 3 done amdk8_scan_chains max: 3 starting... amdk8_scan_chains max: 3 done PCI: pci_scan_bus returning with max=03 POST: 0x55 done POST: 0x66 Allocating resources... Allocating VGA resource ASSIGN RESOURCES, bus 0 PCI: 00:01.0 1c <- [0x00001000 - 0x00001fff] bus 1 io PCI: 00:01.0 24 <- [0xfd200000 - 0xfd1fffff] bus 1 prefmem PCI: 00:01.0 20 <- [0xfd100000 - 0xfd1fffff] bus 1 mem ASSIGN RESOURCES, bus 1 PCI: 01:01.0 10 <- [0xfd100000 - 0xfd10ffff] mem PCI: 01:01.0 18 <- [0xfd110000 - 0xfd11ffff] mem PCI: 01:01.1 10 <- [0xfd120000 - 0xfd12ffff] mem PCI: 01:01.1 18 <- [0xfd130000 - 0xfd13ffff] mem PCI: 01:02.0 10 <- [0x00001000 - 0x000010ff] io PCI: 01:02.0 14 <- [0xfd140000 - 0xfd14ffff] mem PCI: 01:02.0 1c <- [0xfd150000 - 0xfd15ffff] mem ASSIGNED RESOURCES, bus 1 PCI: 00:01.1 10 <- [0xfd200000 - 0xfd200fff] mem PCI: 00:02.0 1c <- [0x00003000 - 0x00002fff] bus 2 io PCI: 00:02.0 24 <- [0xfd200000 - 0xfd1fffff] bus 2 prefmem PCI: 00:02.0 20 <- [0xfd200000 - 0xfd1fffff] bus 2 mem PCI: 00:02.1 10 <- [0xfd201000 - 0xfd201fff] mem PCI: 00:03.0 1c <- [0x00002000 - 0x00002fff] bus 3 io PCI: 00:03.0 24 <- [0xfd200000 - 0xfd1fffff] bus 3 prefmem PCI: 00:03.0 20 <- [0xfc000000 - 0xfd0fffff] bus 3 mem ASSIGN RESOURCES, bus 3 PCI: 03:00.0 10 <- [0xfd000000 - 0xfd000fff] mem PCI: 03:00.1 10 <- [0xfd001000 - 0xfd001fff] mem PCI: 03:00.2 10 <- [0xfd004000 - 0xfd0040ff] mem PCI: 03:00.2 14 <- [0xfd005000 - 0xfd00501f] mem PCI: 03:01.0 10 <- [0xfd002000 - 0xfd002fff] mem PCI: 03:05.0 10 <- [0xfc000000 - 0xfcffffff] mem PCI: 03:05.0 14 <- [0x00002000 - 0x000020ff] io PCI: 03:05.0 18 <- [0xfd003000 - 0xfd003fff] mem ASSIGNED RESOURCES, bus 3 PCI: 00:04.0 00 <- [0x00000000 - 0xffffffff] io PCI: 00:04.0 00 <- [0x00000000 - 0xffffffff] mem PCI: 00:04.1 20 <- [0x00003ce0 - 0x00003cef] io PCI: 00:04.2 10 <- [0x00003cc0 - 0x00003cdf] io PCI: 00:04.3 58 <- [0x00003000 - 0x000030ff] io PCI: 00:04.5 10 <- [0x00003400 - 0x000034ff] io PCI: 00:04.5 14 <- [0x00003c80 - 0x00003cbf] io PCI: 00:04.6 10 <- [0x00003800 - 0x000038ff] io PCI: 00:04.6 14 <- [0x00003c00 - 0x00003c7f] io PCI: 00:18.3 94 <- [0xf8000000 - 0xfbffffff] mem PCI: 00:19.3 94 <- [0xf8000000 - 0xfbffffff] mem ASSIGNED RESOURCES, bus 0 done. POST: 0x88 Enabling resourcess... PCI: 00:01.0 bridge ctrl <- 0003 PCI: 00:01.0 cmd <- 157 PCI: 01:01.0 cmd <- 142 PCI: 01:01.1 cmd <- 142 PCI: 01:02.0 cmd <- 143 PCI: 00:01.1 cmd <- 146 PCI: 00:02.0 bridge ctrl <- 0003 PCI: 00:02.0 cmd <- 157 PCI: 00:02.1 cmd <- 146 PCI: 00:03.0 bridge ctrl <- 080b PCI: 00:03.0 cmd <- 147 PCI: 03:00.0 cmd <- 142 PCI: 03:00.1 cmd <- 142 PCI: 03:00.2 cmd <- 142 PCI: 03:01.0 cmd <- 142 PCI: 03:05.0 cmd <- 1c3 PCI: 00:04.0 cmd <- 14f PCI: 00:04.1 cmd <- 145 PCI: 00:04.2 cmd <- 141 PCI: 00:04.3 cmd <- 141 PCI: 00:04.5 cmd <- 141 PCI: 00:04.6 cmd <- 141 PCI: 00:18.0 cmd <- 140 PCI: 00:18.1 cmd <- 140 PCI: 00:18.2 cmd <- 140 PCI: 00:18.3 cmd <- 140 PCI: 00:19.0 cmd <- 140 PCI: 00:19.1 cmd <- 140 PCI: 00:19.2 cmd <- 140 PCI: 00:19.3 cmd <- 140 done. Initializing devices... PCI: 08:18.0 init NB: Function 0 Misc Control.. done. PCI: 08:19.0 init NB: Function 0 Misc Control.. done. PCI: 00:01.0 init PCI: 00:02.0 init PCI: 00:03.0 init PCI: 00:04.0 init RTC Init Invalid CMOS LB checksum enabling HPET @0xfed00000 PCI: 00:04.1 init IDE1 IDE0 PCI: 00:04.3 init set power on after power fail PCI: 00:18.0 init NB: Function 0 Misc Control.. done. PCI: 00:18.3 init NB: Function 3 Misc Control.. done. PCI: 00:19.0 init NB: Function 0 Misc Control.. done. PCI: 00:19.3 init NB: Function 3 Misc Control.. done. PCI: 03:00.0 init PCI: 03:00.1 init PCI: 03:00.2 init Devices initialized POST: 0x89 mem[0].basek = 00000000 mem[0].sizek = 00000280 mem[1].basek = 00000300 mem[1].sizek = 001ffd00 POST: 0x70 totalram: 2048M Initializing CPU #0 POST: 0x60 Enabling cache... Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) type: WB Setting fixed MTRRs(24-88) type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 2048MB, type WB DONE variable MTRRs Clear out the extra MTRR's call intel_enable_fixed_mtrr() call intel_enable_var_mtrr() Leave setup_mtrrs POST: 0x6a done. Max cpuid index : 1 Vendor ID : AuthenticAMD Processor Type : 0x00 Processor Family : 0x0f Processor Model : 0x05 Processor Mask : 0x00 Processor Stepping : 0x08 Feature flags : 0x078bfbff POST: 0x92 MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled POST: 0x93 Clearing memory 0K - 1048576K: --------------- done Setting up local apic... apic_id: 0 done. POST: 0x9b CPU #0 Initialized POST: 0x75 secondary_cpu_init Waiting for 2 CPUS to stop mem[0].basek = 00000000 mem[0].sizek = 00000280 mem[1].basek = 00000300 mem[1].sizek = 001ffd00 Initializing CPU #1 POST: 0x60 Enabling cache... Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) type: WB Setting fixed MTRRs(24-88) type: WB DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 2048MB, type WB DONE variable MTRRs Clear out the extra MTRR's call intel_enable_fixed_mtrr() call intel_enable_var_mtrr() Leave setup_mtrrs POST: 0x6a done. Max cpuid index : 1 Vendor ID : AuthenticAMD Processor Type : 0x00 Processor Family : 0x0f Processor Model : 0x05 Processor Mask : 0x00 Processor Stepping : 0x08 Feature flags : 0x078bfbff POST: 0x92 MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled POST: 0x93 Clearing memory 1048576K - 2097152K: ---------------- done Setting up local apic... apic_id: 1 done. POST: 0x9b CPU #1 Initialized secondary_cpu_init 1/1 All AP CPUs stopped POST: 0x9a Checking IRQ routing tables... /home/ollie/work/freebios2_ollie/src/arch/i386/boot/pirq_routing.c: 33:check_pirq_routing_table() - irq_routing_table located at: 0x0000dcc0 /home/ollie/work/freebios2_ollie/src/arch/i386/boot/pirq_routing.c: 41:check_pirq_routing_table() - checksum is: 0x45 but should be: 0x46 done. Copying IRQ routing tables to 0xf0000...done. Verifing copy of IRQ routing tables at 0xf0000...done POST: 0x96 Wrote the mp table end at: 00000020 - 000001bc Wrote linuxbios table at: 00000500 - 00000d58 checksum 650b Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 POST: 0xf8 23:stream_init() - rom_stream: 0xfffe0000 - 0xfffeffff Found ELF candiate at offset 0 New segment addr 0x100000 size 0x21f10 offset 0xa0 filesize 0x7f68 (cleaned up) New segment addr 0x100000 size 0x21f10 offset 0xa0 filesize 0x7f68 New segment addr 0x121f20 size 0x48 offset 0x8020 filesize 0x48 (cleaned up) New segment addr 0x121f20 size 0x48 offset 0x8020 filesize 0x48 Dropping non PT_LOAD segment Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000021f10 filesz: 0x0000000000007f68 Clearing Segment: addr: 0x0000000000107f68 memsz: 0x0000000000019fa8 Loading Segment: addr: 0x0000000000121f20 memsz: 0x0000000000000048 filesz: 0x0000000000000048 Jumping to boot code at 0x105928 POST: 0xfe FILO version 0.4.1 (ollie at exponential.lanl.gov) Tue Apr 20 15:04:55 MDT 2004 collect_linuxbios_info: Searching for LinuxBIOS tables... find_lb_table: Found canidate at: 00000500 find_lb_table: header checksum o.k. find_lb_table: table checksum o.k. find_lb_table: record count o.k. collect_linuxbios_info: Found LinuxBIOS table at: 00000500 convert_memmap: 0x00000000000000 0x00000000000db8 16 convert_memmap: 0x00000000000db8 0x0000000009f248 1 convert_memmap: 0x000000000c0000 0x00000000030000 1 convert_memmap: 0x000000000f0000 0x00000000000400 16 convert_memmap: 0x000000000f0400 0x0000007ff0fc00 1 pci_init: Scanning PCI: found 27 devices pci_init: 00:01.0 1022:7450 0604 00 pci_init: 00:01.1 1022:7451 0800 10 pci_init: 00:02.0 1022:7450 0604 00 pci_init: 00:02.1 1022:7451 0800 10 pci_init: 00:03.0 1022:7460 0604 00 pci_init: 00:04.0 1022:7468 0601 00 pci_init: 00:04.1 1022:7469 0101 8a pci_init: 00:04.2 1022:746a 0c05 00 pci_init: 00:04.3 1022:746b 0000 00 pci_init: 00:04.5 1022:746d 0401 00 pci_init: 00:04.6 1022:746e 0703 00 pci_init: 00:18.0 1022:1100 0600 00 pci_init: 00:18.1 1022:1101 0600 00 pci_init: 00:18.2 1022:1102 0600 00 pci_init: 00:18.3 1022:1103 0600 00 pci_init: 00:19.0 1022:1100 0600 00 pci_init: 00:19.1 1022:1101 0600 00 pci_init: 00:19.2 1022:1102 0600 00 pci_init: 00:19.3 1022:1103 0600 00 pci_init: 01:01.0 14e4:1648 0200 00 pci_init: 01:01.1 14e4:1648 0200 00 pci_init: 01:02.0 1000:0030 0100 00 pci_init: 03:00.0 1022:7464 0c03 10 pci_init: 03:00.1 1022:7464 0c03 10 pci_init: 03:00.2 1022:7463 0c03 20 pci_init: 03:01.0 1022:7462 0200 00 pci_init: 03:05.0 1002:4752 0300 00 Press for default boot, or for boot prompt... 3 2 1  boot: hda1:/newkernel root=/dev/hda3 console=tty0 console=ttyS0,115200 hda: LBA48 40GB: IC35L060AVV207-0 Unknown filesystem type boot: hda1:/newkernel root=/dev/hda3 console=tty0 console=ttyS0,115200                                                                /boot/x86_64 Unknown filesystem type boot: /boot/x86_64              hda2:/boot/x86_64 root=/dev/hda2 console=ttyS0,115200 console=tty0 Mounted reiserfs Found Linux version 2.6.5 (root at k) #6 SMP Thu Apr 15 15:45:04 MDT 2004 bzImage. Loading kernel... ok Jumping to entry point... Bootdata ok (command line is root=/dev/hda2 console=ttyS0,115200 console=tty0) Linux version 2.6.5 (root at k) (gcc version 3.3.1 (SuSE Linux)) #6 SMP Thu Apr 15 15:45:04 MDT 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000db8 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 - 0000000080000000 (usable) init_memory_mapping Scan SMP from 0000010000000000 for 1024 bytes. On node 0 totalpages: 524288 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 520192 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: IBM <6>Product ID: E325 <6>APIC at: 0xFEE00000 Processor #0 15:5 APIC version 16 Bootup CPU Processor #1 15:5 APIC version 16 Bus #0 is PCI Bus #1 is PCI Bus #2 is PCI Bus #3 is PCI Bus #4 is ISA I/O APIC #2 Version 17 at 0xFEC00000. I/O APIC #3 Version 17 at 0xFD200000. I/O APIC #4 Version 17 at 0xFD201000. Int: type 3, pol 0, trig 0, bus 4, IRQ 00, APIC ID 2, APIC INT 00 Int: type 0, pol 0, trig 0, bus 4, IRQ 01, APIC ID 2, APIC INT 01 Int: type 0, pol 0, trig 0, bus 4, IRQ 00, APIC ID 2, APIC INT 02 Int: type 0, pol 0, trig 0, bus 4, IRQ 03, APIC ID 2, APIC INT 03 Int: type 0, pol 0, trig 0, bus 4, IRQ 04, APIC ID 2, APIC INT 04 Int: type 0, pol 0, trig 0, bus 4, IRQ 05, APIC ID 2, APIC INT 05 Int: type 0, pol 0, trig 0, bus 4, IRQ 06, APIC ID 2, APIC INT 06 Int: type 0, pol 0, trig 0, bus 4, IRQ 07, APIC ID 2, APIC INT 07 Int: type 0, pol 0, trig 0, bus 4, IRQ 08, APIC ID 2, APIC INT 08 Int: type 0, pol 0, trig 0, bus 4, IRQ 09, APIC ID 2, APIC INT 09 Int: type 0, pol 0, trig 0, bus 4, IRQ 0a, APIC ID 2, APIC INT 0a Int: type 0, pol 0, trig 0, bus 4, IRQ 0b, APIC ID 2, APIC INT 0b Int: type 0, pol 0, trig 0, bus 4, IRQ 0c, APIC ID 2, APIC INT 0c Int: type 0, pol 0, trig 0, bus 4, IRQ 0d, APIC ID 2, APIC INT 0d Int: type 0, pol 0, trig 0, bus 4, IRQ 0e, APIC ID 2, APIC INT 0e Int: type 0, pol 0, trig 0, bus 4, IRQ 0f, APIC ID 2, APIC INT 0f Int: type 0, pol 0, trig 0, bus 0, IRQ 13, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 0, IRQ 11, APIC ID 2, APIC INT 11 Int: type 0, pol 0, trig 0, bus 3, IRQ 03, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 3, IRQ 14, APIC ID 2, APIC INT 10 Int: type 0, pol 0, trig 0, bus 1, IRQ 04, APIC ID 3, APIC INT 00 Int: type 0, pol 0, trig 0, bus 1, IRQ 05, APIC ID 3, APIC INT 01 Int: type 0, pol 0, trig 0, bus 1, IRQ 08, APIC ID 3, APIC INT 02 Int: type 0, pol 0, trig 0, bus 2, IRQ 0c, APIC ID 2, APIC INT 10 Int: type 0, pol 0, trig 0, bus 2, IRQ 0d, APIC ID 2, APIC INT 11 Int: type 0, pol 0, trig 0, bus 2, IRQ 0e, APIC ID 2, APIC INT 12 Int: type 0, pol 0, trig 0, bus 2, IRQ 0f, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 2, IRQ 10, APIC ID 2, APIC INT 11 Int: type 0, pol 0, trig 0, bus 2, IRQ 11, APIC ID 2, APIC INT 12 Int: type 0, pol 0, trig 0, bus 2, IRQ 12, APIC ID 2, APIC INT 13 Int: type 0, pol 0, trig 0, bus 2, IRQ 13, APIC ID 2, APIC INT 10 Lint: type 3, pol 0, trig 0, bus 4, IRQ 00, APIC ID ff, APIC LINT 00 Lint: type 1, pol 0, trig 0, bus 4, IRQ 00, APIC ID ff, APIC LINT 01 Processors: 2 set_pte_phys ffffffffff5fd000 to fee00000 spp_getpage 000001000341d000 spp_getpage 000001000341e000 mapped APIC to ffffffffff5fd000 ( fee00000) set_pte_phys ffffffffff5fc000 to fec00000 mapped IOAPIC to ffffffffff5fc000 (00000000fec00000) set_pte_phys ffffffffff5fb000 to fd200000 mapped IOAPIC to ffffffffff5fb000 (00000000fd200000) set_pte_phys ffffffffff5fa000 to fd201000 mapped IOAPIC to ffffffffff5fa000 (00000000fd201000) Built 1 zonelists Kernel command line: root=/dev/hda2 console=ttyS0,115200 console=tty0 Initializing CPU#0 PID hash table entries: 16 (order 4: 256 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1595.034 MHz processor. Console: colour VGA+ 80x25 Memory: 2056248k/2097152k available (1681k kernel code, 40112k reserved, 691k data, 408k init) Calibrating delay loop... 3129.34 BogoMIPS Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Mount-cache hash table entries: 256 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) POSIX conformance testing by UNIFIX Using local APIC NMI watchdog using perfctr0 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU0: stepping 08 per-CPU timeslice cutoff: 1023.59 usecs. task migration cache decay timeout: 2 msecs. Getting VERSION: 40010 Getting VERSION: 40010 Getting ID: 0 Getting ID: f000000 Getting LVT0: 700 Getting LVT1: 400 enabled ExtINT on CPU#0 ESR value before enabling vector: 00000008 ESR value after enabling vector: 00000000 CPU present map: 3 Booting processor 1/1 rip 6000 rsp 1007ff95f58 Setting warm reset code and vector. 1. 2. 3. Asserting INIT. Waiting for send to finish... +Deasserting INIT. Waiting for send to finish... +#startup loops: 2. Sending STARTUP #1. After apic_write. Initializing CPU#1 CPU#1 (phys ID: 1) waiting for CALLOUT Startup point 1. Waiting for send to finish... +Sending STARTUP #2. After apic_write. Startup point 1. Waiting for send to finish... +After Startup. Before Callout 1. After Callout 1. CALLIN, before setup_local_APIC(). masked ExtINT on CPU#1 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Calibrating delay loop... 3186.68 BogoMIPS Stack at about 000001007ff95f0c CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) OK. stepping 08 CPU has booted. Before bogomips. Total of 2 processors activated (6316.03 BogoMIPS). Before bogocount - setting activated=1. Boot done. ENABLING IO-APIC IRQs Using IO-APIC 2 ...changing IO-APIC physical APIC ID to 2 ... ok. Using IO-APIC 3 ...changing IO-APIC physical APIC ID to 3 ... ok. Using IO-APIC 4 ...changing IO-APIC physical APIC ID to 4 ... ok. Synchronizing Arb IDs. ..TIMER: vector=0x31 pin1=2 pin2=0 testing the IO APIC....................... .................................... done. Using local APIC timer interrupts. Detected 12.461 MHz APIC timer. checking TSC synchronization across 2 CPUs: cpu 1: waiting for commence passed. time.c: Using PIT/TSC based timekeeping. waiting for cpu 1 cpu 1: setting up apic clock cpu 1: enabling apic timer cpu 1 eSetting cpu_online_map Brought up 2 CPUs NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) SCSI subsystem initialized PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: IDE base address fixup for 0000:00:04.1 PCI: Scanning for ghost devices on bus 0 PCI: Scanning for ghost devices on bus 1 PCI: Scanning for ghost devices on bus 2 PCI: Scanning for ghost devices on bus 3 PCI: IRQ init PCI: Interrupt Routing Table found at 0x00000100000f0000 00:18 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 00:01 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 01:02 slot=00 0:03/def8 1:00/def8 2:00/def8 3:00/def8 01:01 slot=00 0:01/def8 1:02/def8 2:00/def8 3:00/def8 00:02 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 02:03 slot=01 0:01/def8 1:02/def8 2:03/def8 3:04/def8 02:04 slot=02 0:02/def8 1:03/def8 2:04/def8 3:01/def8 00:03 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 03:00 slot=00 0:00/def8 1:00/def8 2:00/def8 3:04/def8 03:05 slot=00 0:01/def8 1:00/def8 2:00/def8 3:00/def8 00:04 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 00:18 slot=00 0:00/def8 1:00/def8 2:00/def8 3:00/def8 PCI: Attempting to find IRQ router for 1022:746b PCI: Using IRQ router AMD8111 [1022/746b] at 0000:00:04.3 PCI: IRQ fixup querying PCI -> IRQ mapping bus:0, slot:4, pin:3. PCI->APIC IRQ transform: (B0,I4,P3) -> 19 querying PCI -> IRQ mapping bus:0, slot:4, pin:1. PCI->APIC IRQ transform: (B0,I4,P1) -> 17 querying PCI -> IRQ mapping bus:0, slot:4, pin:1. PCI->APIC IRQ transform: (B0,I4,P1) -> 17 querying PCI -> IRQ mapping bus:1, slot:1, pin:0. PCI->APIC IRQ transform: (B1,I1,P0) -> 24 querying PCI -> IRQ mapping bus:1, slot:1, pin:1. PCI->APIC IRQ transform: (B1,I1,P1) -> 25 querying PCI -> IRQ mapping bus:1, slot:2, pin:0. PCI->APIC IRQ transform: (B1,I2,P0) -> 26 querying PCI -> IRQ mapping bus:3, slot:0, pin:3. PCI->APIC IRQ transform: (B3,I0,P3) -> 19 querying PCI -> IRQ mapping bus:3, slot:0, pin:3. PCI->APIC IRQ transform: (B3,I0,P3) -> 19 querying PCI -> IRQ mapping bus:3, slot:0, pin:3. PCI->APIC IRQ transform: (B3,I0,P3) -> 19 querying PCI -> IRQ mapping bus:3, slot:1, pin:0. querying PCI -> IRQ mapping bus:0, slot:3, pin:1. querying PCI -> IRQ mapping bus:3, slot:5, pin:0. PCI->APIC IRQ transform: (B3,I5,P0) -> 16 PCI: Allocating resources PCI: Resource fd200000-fd200fff (f=204, d=0, p=0) PCI: Resource fd201000-fd201fff (f=204, d=0, p=0) PCI: Resource 00000f00-00000f0f (f=101, d=0, p=0) PCI: Resource 00003cc0-00003cdf (f=101, d=0, p=0) PCI: Resource 00003400-000034ff (f=101, d=0, p=0) PCI: Resource 00003c80-00003cbf (f=101, d=0, p=0) PCI: Resource 00003800-000038ff (f=101, d=0, p=0) PCI: Resource 00003c00-00003c7f (f=101, d=0, p=0) PCI: Resource fd100000-fd10ffff (f=204, d=0, p=0) PCI: Resource fd110000-fd11ffff (f=204, d=0, p=0) PCI: Resource fd120000-fd12ffff (f=204, d=0, p=0) PCI: Resource fd130000-fd13ffff (f=204, d=0, p=0) PCI: Resource 00001000-000010ff (f=101, d=0, p=0) PCI: Resource fd140000-fd14ffff (f=204, d=0, p=0) PCI: Resource fd150000-fd15ffff (f=204, d=0, p=0) PCI: Resource fd000000-fd000fff (f=200, d=0, p=0) PCI: Resource fd001000-fd001fff (f=200, d=0, p=0) PCI: Resource fd004000-fd0040ff (f=200, d=0, p=0) PCI: Resource fd005000-fd00501f (f=200, d=0, p=0) PCI: Resource fd002000-fd002fff (f=200, d=0, p=0) PCI: Resource fc000000-fcffffff (f=200, d=0, p=0) PCI: Resource 00002000-000020ff (f=101, d=0, p=0) PCI: Resource fd003000-fd003fff (f=200, d=0, p=0) set_pte_phys ffffffffff600000 to 38a000 spp_getpage 000001000374d000 IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ ikconfig 0.7 with /proc/config* lp: driver loaded but no devices found Real Time Clock Driver v1.12 Non-volatile memory driver v1.2 hw_random: AMD768 system management I/O registers at 0x3000. hw_random hardware driver 1.0.0 loaded Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Using anticipatory io scheduler floppy0: no floppy controllers found Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx AMD8111: IDE controller at PCI slot 0000:00:04.1 AMD8111: chipset revision 3 AMD8111: not 100% native mode: will probe irqs later AMD8111: 0000:00:04.1 (rev 03) UDMA133 controller ide0: BM-DMA at 0x0f00-0x0f07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x0f08-0x0f0f, BIOS settings: hdc:DMA, hdd:pio hda: IC35L060AVV207-0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 1024KiB hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100) hda: hda1 hda2 mice: PS/2 mouse device common for all mice i8042.c: Can't read CTR while initializing i8042. NET: Registered protocol family 2 IP: routing cache hash table of 8192 buckets, 128Kbytes TCP: Hash tables configured (established 262144 bind 65536) ip_conntrack version 2.1 (8192 buckets, 65536 max) - 440 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team ipt_recent v0.3.1: Stephen Frost . http://snowman.net/projects/ipt_recent/ arp_tables: (C) 2002 David S. Miller NET: Registered protocol family 1 NET: Registered protocol family 17 found reiserfs format "3.6" with standard journal Reiserfs journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 reiserfs: checking transaction log (hda2) for (hda2) Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 408k freed Adding 1052216k swap on /dev/hda1. Priority:42 extents:1 ieee1394: raw1394: /dev/raw1394 device initialized Welcome to SuSE Linux 9.0 (x86-64) - Kernel 2.6.5 (ttyS0). l login: guest Password: Last login: Thu Apr 22 15:26:58 on ttyS0 Have a lot of fun... guest at l:/> lspci -bash: lspci: command not found guest at l:/> /sbin/sl        su Password: l:/ # lspcu i 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00:02.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00:03.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 00:04.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 00:04.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 00:04.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 (rev 02) 00:04.3 Non-VGA unclassified device: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) 00:04.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-8111 AC97 Audio (rev 03) 00:04.6 Modem: Advanced Micro Devices [AMD] AMD-8111 MC97 Modem (rev 03) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 01:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) 01:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) 01:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 03:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 03:00.2 USB Controller: Advanced Micro Devices [AMD]: Unknown device 7463 (rev 02) 03:01.0 Ethernet controller: Advanced Micro Devices [AMD] AMD-8111 Ethernet (rev 03) 03:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) l:/ # lspci -vvv 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [a0] Capabilities: [b8] #08 [8000] Capabilities: [c0] #08 [0041] 00:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [a0] Capabilities: [b8] #08 [8000] 00:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) (prog-if 10 [IO-APIC]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [c0] #08 [0083] Capabilities: [f0] #08 [8000] 00:04.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=1M] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [68] PCI-X non-bridge device. Command: DPERE- ERO- RBC=0 OST=4 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) (prog-if 10 [OHCI]) Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=64K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 03:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA]) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=128K] Capabilities: [5c] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- l:/ # lspci -xxx 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00: 22 10 50 74 57 01 30 02 12 00 04 06 00 40 81 00 10: 00 00 00 00 00 00 00 00 00 01 01 40 11 11 20 22 20: 10 fd 10 fd 21 fd 11 fd 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 ff 00 03 00 40: 05 00 1f 00 00 00 00 00 02 0c 00 00 01 2c 00 00 50: 00 00 03 00 00 00 05 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 07 b8 83 00 08 00 03 00 0e 00 0e 00 02 00 02 00 b0: 00 00 00 00 00 00 00 00 08 c0 00 80 00 00 00 03 c0: 08 00 41 00 22 00 11 11 22 00 00 00 22 04 35 00 d0: 02 00 35 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 08 08 0e 00 08 08 0e 00 0f 0f 17 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00: 22 10 51 74 06 00 00 02 01 10 00 08 00 00 00 00 10: 04 00 20 fd 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 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 03 00 00 00 04 00 20 fd 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:02.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) 00: 22 10 50 74 57 01 30 02 12 00 04 06 00 40 81 00 10: 00 00 00 00 00 00 00 00 00 02 02 40 31 21 20 22 20: 20 fd 10 fd 21 fd 11 fd 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 ff 00 03 00 40: 05 00 1f 00 00 00 00 00 00 00 00 00 01 2c 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 07 b8 83 00 10 00 03 00 0e 00 0e 00 02 00 02 00 b0: 00 00 00 00 00 00 00 00 08 00 00 80 00 00 00 04 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 00 00 00 00 00 00 00 00 00 00 00:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) 00: 22 10 51 74 06 00 00 02 01 10 00 08 00 00 00 00 10: 04 10 20 fd 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 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 03 00 00 00 04 10 20 fd 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:03.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 00: 22 10 60 74 47 01 30 02 07 00 04 06 00 40 01 00 10: 00 00 00 00 00 00 00 00 00 03 03 40 20 20 00 22 20: 00 fc 00 fd 20 fd 10 fd 00 00 00 00 00 00 00 00 30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 0b 08 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 04 06 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 08 f0 83 00 22 00 00 00 d0 00 00 00 22 00 01 00 d0: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 08 00 01 00 08 00 11 00 0f 00 1a 00 00 00 00 00 f0: 08 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00:04.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 00: 22 10 68 74 0f 00 20 02 05 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 30 07 80 01 00 00 02 ff ff 00 01 00 00 00 c0 50: 00 00 00 00 85 01 00 00 44 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 de 00 00 00 00 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: 01 00 d0 fe 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 00: 22 10 69 74 05 00 00 02 03 8a 01 01 00 40 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00 40: 43 f0 0f 00 00 00 00 00 5e 20 5e 20 22 00 20 20 50: 03 c0 03 c6 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 (rev 02) 00: 22 10 6a 74 01 00 00 02 02 00 05 0c 00 40 00 00 10: c1 3c 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 00 00 00 00 00 00 00 00 00 04 00 00 40: 02 00 05 0c 00 00 00 00 06 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.3 Non-VGA unclassified device: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) 00: 22 10 6b 74 00 00 80 02 05 00 00 00 00 40 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 80 d1 00 07 00 00 00 00 20 14 10 00 00 00 00 00 50: 00 80 00 00 0f 00 00 00 01 30 00 00 00 00 00 00 60: 00 00 00 00 13 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 01 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: a4 f0 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-8111 AC97 Audio (rev 03) 00: 22 10 6d 74 01 00 00 02 03 00 01 04 00 40 00 00 10: 01 34 00 00 81 3c 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 00 00 00 00 00 00 00 00 00 02 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:04.6 Modem: Advanced Micro Devices [AMD] AMD-8111 MC97 Modem (rev 03) 00: 22 10 6e 74 01 00 00 02 03 00 03 07 00 40 00 00 10: 01 38 00 00 01 3c 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 00 00 00 00 00 00 00 00 00 02 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 00 11 00 00 10 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 40: 01 01 09 00 08 08 01 00 01 01 01 00 01 01 01 00 50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00 60: 10 00 01 00 e4 01 00 00 00 c8 00 0f 5c 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 08 a0 01 21 d0 00 11 77 22 00 75 80 02 00 00 00 90: c7 13 30 06 00 00 00 00 00 00 00 00 00 00 00 00 a0: 08 c0 01 21 20 00 11 11 22 04 75 80 02 00 00 00 b0: 56 04 51 02 00 00 00 00 07 00 00 00 00 00 00 00 c0: 08 00 01 21 20 00 11 11 22 05 75 80 02 00 00 00 d0: 13 56 13 04 00 00 00 00 03 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 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 01 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 03 00 00 00 00 00 3f 00 03 00 40 00 01 00 7f 00 50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00 70: 00 00 00 00 06 00 00 00 00 00 00 00 07 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: 03 d0 fe 00 10 d0 fe 00 03 0a 00 00 10 0b 00 00 b0: 03 c0 fe 00 10 c0 fe 00 03 00 fc 00 10 2f fe 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 33 00 00 00 10 f0 ff 01 e0: 00 00 00 00 00 00 00 00 00 00 00 00 03 01 00 ff f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 02 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 fe e0 03 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 40 00 00 00 00 00 00 00 35 33 72 13 20 0a 10 00 90: 00 8c 23 08 08 0b 5b 0a 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 08 86 67 d0 c3 00 00 00 75 59 98 ce 9f 3c ba fa c0: 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 52 ae cf f1 ac f1 af ef 18 dc 97 fa ff 85 d5 9d e0: 1b af d5 50 b8 e5 4c fc be cf 8c f2 f7 96 ed e4 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 03 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: ff 3b 00 00 40 00 c0 02 00 00 00 00 00 00 00 00 50: 10 50 10 00 10 00 00 00 16 16 16 00 00 bf 01 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 11 01 02 51 11 80 00 50 00 38 00 08 1b 22 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 02 00 00 00 7c 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 e0 b2 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 07 07 e2 04 00 00 00 00 00 00 25 00 e0: 00 00 00 00 20 16 59 00 1b 01 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 00 11 00 00 10 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 40: 08 08 01 00 01 01 09 00 01 01 01 00 01 01 01 00 50: 01 01 01 00 01 01 01 00 01 01 01 00 01 01 01 00 60: 11 00 01 00 e4 00 00 00 00 c8 00 0f 78 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 08 a0 01 21 d0 00 11 77 22 00 75 80 02 00 00 00 90: 7f d7 00 06 00 00 00 00 00 00 00 00 00 00 00 00 a0: 08 c0 01 21 d0 00 11 77 22 00 75 80 02 00 00 00 b0: e0 f3 31 06 00 00 00 00 00 00 00 00 00 00 00 00 c0: 08 00 01 21 20 00 11 11 22 05 75 80 02 00 00 00 d0: 13 56 13 04 00 00 00 00 03 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 00 00 00 00 00 00 00 00 00 00 00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 01 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 03 00 00 00 00 00 3f 00 03 00 40 00 01 00 7f 00 50: 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 60: 00 00 00 00 04 00 00 00 00 00 00 00 05 00 00 00 70: 00 00 00 00 06 00 00 00 00 00 00 00 07 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: 03 d0 fe 00 10 d0 fe 00 03 0a 00 00 10 0b 00 00 b0: 03 c0 fe 00 10 c0 fe 00 03 00 fc 00 10 2f fe 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 33 00 00 00 10 f0 ff 01 e0: 00 00 00 00 00 00 00 00 00 00 00 00 03 01 00 ff f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 02 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 fe e0 03 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 04 00 00 00 00 00 00 00 35 33 72 13 20 0a 10 00 90: 00 8c 13 08 08 0b 5b 06 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: c8 35 64 d0 c3 00 00 00 3d 98 3d cc 0f 10 fe e7 c0: 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: e5 f9 9d b2 fb e4 c6 3d 08 a5 8a bd 99 4d 9a 65 e0: d0 49 d8 b8 75 66 87 da cc b3 a8 2f 8b 66 5c f5 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00: 22 10 03 11 00 00 00 00 00 00 00 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 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: ff 3b 00 00 40 00 c0 02 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 16 16 16 00 00 bd 01 40 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 11 01 02 51 11 80 00 50 00 38 00 08 1b 22 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 02 00 00 00 7c 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 38 00 00 60 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 07 07 e2 04 00 00 00 00 00 00 25 00 e0: 00 00 00 00 20 14 55 00 1b 01 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) 00: e4 14 48 16 42 01 b0 02 03 00 00 02 10 40 80 00 10: 04 00 10 fd 00 00 00 00 04 00 11 fd 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 a6 02 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 40 00 40: 07 48 02 00 08 01 43 04 01 50 02 c0 00 21 00 64 50: 03 58 70 00 2a 32 04 80 05 00 86 00 98 e0 a0 00 60: 6d 23 89 44 00 00 00 00 00 00 03 20 00 00 00 00 70: 02 32 00 00 c6 00 00 00 50 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 01 00 fe 90 28 02 90: 01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 01:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) 00: e4 14 48 16 42 01 b0 02 03 00 00 02 10 40 80 00 10: 04 00 12 fd 00 00 00 00 04 00 13 fd 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 a6 02 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 02 40 00 40: 07 48 02 00 09 01 43 04 01 50 02 c0 00 21 00 64 50: 03 58 3c 00 c1 fb db bd 05 00 86 00 bc ef e1 b1 60: 88 ff eb df 72 bc 00 00 00 00 03 20 00 00 00 00 70: 02 32 00 00 c6 00 00 00 50 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 fe 90 68 02 90: 01 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 04 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 00 00 00 00 00 00 00 00 00 00 01:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) 00: 00 10 30 00 43 01 30 02 07 00 00 01 10 40 00 00 10: 01 10 00 00 04 00 14 fd 00 00 00 00 04 00 15 fd 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 10 12 30: 00 00 00 00 50 00 00 00 00 00 00 00 00 01 11 12 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 01 58 02 06 00 00 00 00 05 68 80 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 07 00 40 00 10 01 43 06 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 00: 22 10 64 74 02 01 80 02 0b 10 03 0c 00 40 80 00 10: 00 00 00 fd 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 00 00 00 00 00 00 00 00 00 04 00 50 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 00: 22 10 64 74 02 01 80 02 0b 10 03 0c 00 40 00 00 10: 00 10 00 fd 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 00 00 00 00 00 00 00 00 00 04 00 50 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:00.2 USB Controller: Advanced Micro Devices [AMD]: Unknown device 7463 (rev 02) 00: 22 10 63 74 02 00 10 02 02 20 03 0c 00 40 00 00 10: 00 40 00 fd 00 50 00 fd 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 63 74 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 04 00 00 40: 01 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 20 20 01 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 22 10 63 74 01 00 00 00 40 30 00 01 00 00 00 00 80: 0a 88 00 40 00 00 00 00 01 00 82 fe 00 01 00 00 90: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:01.0 Ethernet controller: Advanced Micro Devices [AMD] AMD-8111 Ethernet (rev 03) 00: 22 10 62 74 02 00 10 02 03 00 00 02 10 40 00 00 10: 00 20 00 fd 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 40 00 00 00 00 00 00 00 00 01 18 18 40: 01 00 02 fe 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 03:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 00: 02 10 52 47 83 00 90 02 27 00 00 03 10 40 00 00 10: 00 00 00 fc 01 20 00 00 00 30 00 fd 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 5c 00 00 00 00 00 00 00 00 01 08 00 40: 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 02 5c 10 00 01 00 00 ff 00 00 00 00 01 00 02 06 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 00 00 00 00 00 00 00 00 00 00 l:/ # lspci -tv -[00]-+-01.0-[01]--+-01.0 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet | +-01.1 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet | \-02.0 LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI +-01.1 Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC +-02.0-[02]-- +-02.1 Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC +-03.0-[03]--+-00.0 Advanced Micro Devices [AMD] AMD-8111 USB | +-00.1 Advanced Micro Devices [AMD] AMD-8111 USB | +-00.2 Advanced Micro Devices [AMD]: Unknown device 7463 | +-01.0 Advanced Micro Devices [AMD] AMD-8111 Ethernet | \-05.0 ATI Technologies Inc Rage XL +-04.0 Advanced Micro Devices [AMD] AMD-8111 LPC +-04.1 Advanced Micro Devices [AMD] AMD-8111 IDE +-04.2 Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 +-04.3 Advanced Micro Devices [AMD] AMD-8111 ACPI +-04.5 Advanced Micro Devices [AMD] AMD-8111 AC97 Audio +-04.6 Advanced Micro Devices [AMD] AMD-8111 MC97 Modem +-18.0 Advanced Micro Devices [AMD] K8 NorthBridge +-18.1 Advanced Micro Devices [AMD] K8 NorthBridge +-18.2 Advanced Micro Devices [AMD] K8 NorthBridge +-18.3 Advanced Micro Devices [AMD] K8 NorthBridge +-19.0 Advanced Micro Devices [AMD] K8 NorthBridge +-19.1 Advanced Micro Devices [AMD] K8 NorthBridge +-19.2 Advanced Micro Devices [AMD] K8 NorthBridge \-19.3 Advanced Micro Devices [AMD] K8 NorthBridge l:/ # lspci -t -[00]-+-01.0-[01]--+-01.0 | +-01.1 | \-02.0 +-01.1 +-02.0-[02]-- +-02.1 +-03.0-[03]--+-00.0 | +-00.1 | +-00.2 | +-01.0 | \-05.0 +-04.0 +-04.1 +-04.2 +-04.3 +-04.5 +-04.6 +-18.0 +-18.1 +-18.2 +-18.3 +-19.0 +-19.1 +-19.2 \-19.3 l:/ # From hcwang at netd.com Mon Apr 26 12:01:02 2004 From: hcwang at netd.com (HC Wang) Date: Mon Apr 26 12:01:02 2004 Subject: tyan s2880 build broken? Message-ID: <000101c42bb2$03be9050$bd01000a@WANG> Hi, I checked out linuxbios2 tree from sourceforge.net, and I have problem with building bios for tyan s2880 motherboard, here is the error message from buildtarget tyan/s2880: Configuring PART mainboard, path tyan/s2880 ===> NOTE: Changing default value of LB_CKS_RANGE_START ===> NOTE: Changing default value of LB_CKS_RANGE_END ===> NOTE: Changing default value of LB_CKS_LOC Configuring DIR ../common/lsi_scsi/Config.lb ===> ERROR: Could not open file "/home/hcwang/linux-bios/freebios2/src/mainboard/tyan/s2880/../common/lsi_sc si/Config.lb" tyan/s2880/Config.lb:0 mainboard/tyan/s2880/Config.lb:0 ../common/lsi_scsi/Config.lb:0 [hcwang at primary targets]$ pwd /home/hcwang/linux-bios/freebios2/targets Has anybody experience similar problem? Thanks, HC -------------- next part -------------- An HTML attachment was scrubbed... URL: From hcwang at netd.com Mon Apr 26 12:12:01 2004 From: hcwang at netd.com (HC Wang) Date: Mon Apr 26 12:12:01 2004 Subject: amd opteron dram controller Message-ID: <000601c42bb3$9d5d3c10$bd01000a@WANG> Hi, I am working on post code for an embedded opteron board, I have some problem with dram controller initialization, problem I have seen are (1) after setting DramInit bit (bit 8) in dram configuration low register (bus 0, dev 24, func 2, reg 0x90), processor clear this bit after a while but DramEnable (bit 10) and MemClrStatus (bit 11) never set high, is this a problem? If so what is causing it? (2) After DramInit bit is cleared by processor, I can access sdram from 0x00000000 to 0x0009ffff, fill it with pattern and verify it. But I can't write into address space from 0x000A0000 - 0x000EFFFF, even MTRRs associated with it are set to UC type. Is this correct? (3) Can't write memory above 1M (from 0x00100000 and up), but I can alter the memory content by using AMD HDT.. Any ideas? Thanks, HC -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Mon Apr 26 12:17:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 12:17:01 2004 Subject: tyan s2880 build broken? In-Reply-To: <000101c42bb2$03be9050$bd01000a@WANG> Message-ID: I think with Stefan's last set of patches we're missing some cvs adds? Stefan? ron From YhLu at tyan.com Mon Apr 26 12:19:24 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 12:19:24 2004 Subject: tyan s2880 build broken? Message-ID: <3174569B9743D511922F00A0C943142304B86816@TYANWEB> I will change the code to disable the lsi_scsi as the default. Do you have lsi 1030 onboard? You need to use it? If you need to use it, I send you pre-built image, because I can not publish the source code of lsi_scsi. LSI don?t want to. Regards YH _____ ???: HC Wang [mailto:hcwang at netd.com] ????: 2004?4?26? 10:15 ???: linuxbios at clustermatic.org ??: tyan s2880 build broken? Hi, I checked out linuxbios2 tree from sourceforge.net, and I have problem with building bios for tyan s2880 motherboard, here is the error message from buildtarget tyan/s2880: Configuring PART mainboard, path tyan/s2880 ===> NOTE: Changing default value of LB_CKS_RANGE_START ===> NOTE: Changing default value of LB_CKS_RANGE_END ===> NOTE: Changing default value of LB_CKS_LOC Configuring DIR ../common/lsi_scsi/Config.lb ===> ERROR: Could not open file "/home/hcwang/linux-bios/freebios2/src/mainboard/tyan/s2880/../common/lsi_sc si/Config.lb" tyan/s2880/Config.lb:0 mainboard/tyan/s2880/Config.lb:0 ../common/lsi_scsi/Config.lb:0 [hcwang at primary targets]$ pwd /home/hcwang/linux-bios/freebios2/targets Has anybody experience similar problem? Thanks, HC -------------- next part -------------- An HTML attachment was scrubbed... URL: From rminnich at lanl.gov Mon Apr 26 12:24:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 12:24:00 2004 Subject: amd opteron dram controller In-Reply-To: <000601c42bb3$9d5d3c10$bd01000a@WANG> Message-ID: is this with linuxbios? ron From rminnich at lanl.gov Mon Apr 26 12:27:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 12:27:01 2004 Subject: tyan s2880 build broken? In-Reply-To: <3174569B9743D511922F00A0C943142304B86816@TYANWEB> Message-ID: On Mon, 26 Apr 2004, YhLu wrote: > If you need to use it, I send you pre-built image, because I can not publish > the source code of lsi_scsi. LSI don??t want to. grr. Is there a ROM BIOS for it? ron From rminnich at lanl.gov Mon Apr 26 12:32:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 12:32:00 2004 Subject: tyan s2880 build broken? In-Reply-To: <3174569B9743D511922F00A0C943142304B86816@TYANWEB> Message-ID: On Mon, 26 Apr 2004, YhLu wrote: > I will change the code to disable the lsi_scsi as the default. > > Do you have lsi 1030 onboard? You need to use it? > > If you need to use it, I send you pre-built image, because I can not publish > the source code of lsi_scsi. LSI don??t want to. I committed the change and s2880 builds again. ron From rminnich at lanl.gov Mon Apr 26 12:34:21 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 12:34:21 2004 Subject: tyan s2880 build broken? In-Reply-To: <3174569B9743D511922F00A0C943142304B86816@TYANWEB> Message-ID: I just commented out the #dir ../ entry in mainboard/tyan/s2880/Config.lb and the buildtarget seems ok. I will commit. ron From YhLu at tyan.com Mon Apr 26 12:38:46 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 12:38:46 2004 Subject: =?GB2312?B?tPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9rZW4/?= Message-ID: <3174569B9743D511922F00A0C943142304B86821@TYANWEB> 1. In freebios2/src/mainboard/tyan/s2880/Config.lb comment out dir ../common/lsi_scsi 2. In freebios2/targets/tyan/s2880/Config.lb comment out option ROM_SIZE = 475136 Don't forget 2. otherwise the final image will short some. Regards YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?26? 10:42 ???: YhLu ??: HC Wang; linuxbios at clustermatic.org ??: Re: tyan s2880 build broken? I just commented out the #dir ../ entry in mainboard/tyan/s2880/Config.lb and the buildtarget seems ok. I will commit. ron From ebiederman at lnxi.com Mon Apr 26 12:41:59 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 26 12:41:59 2004 Subject: Why devices ARE or NOT on bus 0 ? In-Reply-To: <1082994930.18711.1081.camel@exponential.lanl.gov> References: <1082741333.18711.1075.camel@exponential.lanl.gov> <1082994930.18711.1081.camel@exponential.lanl.gov> Message-ID: Li-Ta Lo writes: > > You might need to specify the bridges/busses in Config.lb. > > I know the current code works and can handle this. > > > > > Does anyone can help on this ? > > > > Without something like a serial console trace so that the details > > of what are going on are clear I don't know. > > > > Please see that attached log. As you ca see the HyperTransport scan > is not actually done in northbridge.c:amdk8_scan_chain(). It only > prints the message before and after the for loop but skip the loop. Please reread my hunch below. It looks like I nailed it on the head. The fact that the first pci_scan_bus shows devices below 0x18 is confirmation of this. mainboard_operations needs to specify amdk8_scan_root_bus. > > I have a hunch. The default code for setting things up is > > for pci devices. In the opteron mainboard files we need to specify > > non-default operations so we do the hypertransport scan. One > > of the things that does is to put everything back at devfn 0 > > if they have changed from someplace else. > > > > amdk8_scan_root_bus very deliberately avoids all of the other > > functions that are not cpus so if you are using it I don't see > > how you would run into the problem you have described. > > Eric From rminnich at lanl.gov Mon Apr 26 12:46:22 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 12:46:22 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9rZW4/?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86829@TYANWEB> Message-ID: On Mon, 26 Apr 2004, YhLu wrote: > When enabling lsi_scsi support, It need leave 48k in the BIOS ROM for > lsi_scsi fw. So need to change normal mode ROM_SIZE to 512k-48k. OK, BTW you can do this: option ROM_SIZE = 512*1024 - 48*1024 which is not as readable as 512k-48k, but is pretty readable. ron From rminnich at lanl.gov Mon Apr 26 12:49:10 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 12:49:10 2004 Subject: =?GB2312?B?tPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9rZW4/?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86821@TYANWEB> Message-ID: On Mon, 26 Apr 2004, YhLu wrote: > Don't forget 2. otherwise the final image will short some. What should it be? ron From YhLu at tyan.com Mon Apr 26 12:53:29 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 12:53:29 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9rZW4/?= Message-ID: <3174569B9743D511922F00A0C943142304B86829@TYANWEB> When enabling lsi_scsi support, It need leave 48k in the BIOS ROM for lsi_scsi fw. So need to change normal mode ROM_SIZE to 512k-48k. After that, cat fwx, normal linuxbios, fallback linuxbios to 512k final image. YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?26? 10:49 ???: YhLu ??: HC Wang; linuxbios at clustermatic.org ??: Re: ??: tyan s2880 build broken? On Mon, 26 Apr 2004, YhLu wrote: > Don't forget 2. otherwise the final image will short some. What should it be? ron From YhLu at tyan.com Mon Apr 26 12:56:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 12:56:01 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9r?= =?GB2312?B?ZW4/?= Message-ID: <3174569B9743D511922F00A0C943142304B86831@TYANWEB> When I using the new config to deal with it, the tool seems doesn?t support expression. I will check that in current config tool. YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?26? 10:57 ???: YhLu ??: HC Wang; linuxbios at clustermatic.org ??: Re: ??: ??: tyan s2880 build broken? On Mon, 26 Apr 2004, YhLu wrote: > When enabling lsi_scsi support, It need leave 48k in the BIOS ROM for > lsi_scsi fw. So need to change normal mode ROM_SIZE to 512k-48k. OK, BTW you can do this: option ROM_SIZE = 512*1024 - 48*1024 which is not as readable as 512k-48k, but is pretty readable. ron From rminnich at lanl.gov Mon Apr 26 13:00:20 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 13:00:20 2004 Subject: =?GB2312?B?tPC4tDogtPC4tDogtPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9r?= =?GB2312?B?ZW4/?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86831@TYANWEB> Message-ID: On Mon, 26 Apr 2004, YhLu wrote: > When I using the new config to deal with it, the tool seems doesn??t support > expression. I will check that in current config tool. it supports the expression, it just gets it wrong. Sorry. Another bug! ron From ebiederman at lnxi.com Mon Apr 26 13:02:31 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 26 13:02:31 2004 Subject: amd opteron dram controller In-Reply-To: References: Message-ID: ron minnich writes: > is this with linuxbios? It does not sound like it as we already handle these issues. Eric From ebiederman at lnxi.com Mon Apr 26 13:04:46 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 26 13:04:46 2004 Subject: tyan s2880 build broken? In-Reply-To: <3174569B9743D511922F00A0C943142304B86816@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86816@TYANWEB> Message-ID: YhLu writes: > I will change the code to disable the lsi_scsi as the default. > > Do you have lsi 1030 onboard? You need to use it? > > If you need to use it, I send you pre-built image, because I can not publish > the source code of lsi_scsi. LSI don?t want to. If you can't publish the source then distributing the binary with the code compiled from that source linked in violates the GPL. Eric From YhLu at tyan.com Mon Apr 26 13:10:00 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 13:10:00 2004 Subject: tyan s2880 build broken? Message-ID: <3174569B9743D511922F00A0C943142304B8683B@TYANWEB> So I need disable the code always, and don't send the image to the end user. What's pity! YH. -----????----- ???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] ????: 2004?4?26? 11:12 ???: YhLu ??: linuxbios at clustermatic.org ??: Re: tyan s2880 build broken? YhLu writes: > I will change the code to disable the lsi_scsi as the default. > > Do you have lsi 1030 onboard? You need to use it? > > If you need to use it, I send you pre-built image, because I can not publish > the source code of lsi_scsi. LSI don?t want to. If you can't publish the source then distributing the binary with the code compiled from that source linked in violates the GPL. Eric From nacho at estudio-verona.com Mon Apr 26 13:18:00 2004 From: nacho at estudio-verona.com (Ignacio Verona) Date: Mon Apr 26 13:18:00 2004 Subject: Via Epia-MII BiosSavior problems Message-ID: <200404262032.40883.nacho@estudio-verona.com> 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, using the serial console, I can see LinuxBios boot up, but I hangs (this does not worry my at this time), 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. From rminnich at lanl.gov Mon Apr 26 14:37:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 14:37:00 2004 Subject: amd opteron dram controller In-Reply-To: Message-ID: On 26 Apr 2004, Eric W. Biederman wrote: > It does not sound like it as we already handle these issues. just wanted to make sure :-) ron From jochen at roemling.net Mon Apr 26 15:00:01 2004 From: jochen at roemling.net (Jochen Roemling) Date: Mon Apr 26 15:00:01 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions Message-ID: <408D6DA8.6060807@roemling.net> Hi all, I'm trying to build up a PVR (Personal Video Recorder) using LinuxBIOS because of it's fast startup time and because I'm interested in playing around with this on-the-edge matter. I spent hours on the net trying to find a suitable motherboard. To be serious: I found not even one that seems to be supported by LinuxBIOS, supports everything I need and is still in the shops of the retailers or eBay. The Status page on linuxbios.org seems to contain mainly very small boards with only 2 or 3 PCI slots that are aimed towards cluster nodes. Those questions may all sound like newbee questions to you, but please reply at least yes or no, I would then commit a HOWTO if I get the whole stuff working: 1. I found out that LinuxBIOS supports VGA only for very few chipsets like the SiS630. If I would use a VGA card that comes with it's own BIOS (let's say some ATI radeon) and not using any on-board-VGA-device, would it work if the mainboard has a LinuxBIOS-supported chipset? My feelings say "yes", don't they? 2. I'm going to use the Hauppauge PVR 350 card that has a TV-out which - according to the net - is available to Linux as a frame buffer device, so X and the TV Applications should be able to use this. Does this mean I would be able to boot LinuxBIOS with serial console only and then start up XFree86 using this PVR 350 Framebuffer device? 3. Just to verify that I understood everything right: The Kernel that is burned into the DoC will be the kernel that runs the machine after bootup and it is possible to mount the root fs via NFS just like LTSP does? Or will the kernel on the DoC just to be used to initialize the hardware and then load another kernel via the net or from disk? Or do I have both possibilities? 4. Is it correct that kernel 2.4.19 is the latest one supported by LinuxBIOS? Should the patches be good for 2.4.26 also? What about 2.6? Maybe you can recommend some motherboards out of the box that are still available in the shops? They should support CPUs with about 1200 MHz, have at least 2 PCI slots for TV cards, another PCI slot for an AC97 soundcard with optical SP/DIF output (only if there is no such linux-supported connector on-board) and another PCI slot for a 3com network card with BootROM (not needed if the LinuxBIOS on the DoC is running the whole machine and can mount root via NFS or if the board can net-boot via the on-board NIC). Thanks in advance for your help which will be highly appreciated! Best regards Jochen From ollie at lanl.gov Mon Apr 26 15:53:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Mon Apr 26 15:53:00 2004 Subject: Why devices ARE or NOT on bus 0 ? In-Reply-To: References: <1082741333.18711.1075.camel@exponential.lanl.gov> <1082994930.18711.1081.camel@exponential.lanl.gov> Message-ID: <1083013655.18413.2.camel@exponential.lanl.gov> On Mon, 2004-04-26 at 11:58, Eric W. Biederman wrote: > Li-Ta Lo writes: > > > > You might need to specify the bridges/busses in Config.lb. > > > I know the current code works and can handle this. > > > > > > > Does anyone can help on this ? > > > > > > Without something like a serial console trace so that the details > > > of what are going on are clear I don't know. > > > > > > > Please see that attached log. As you ca see the HyperTransport scan > > is not actually done in northbridge.c:amdk8_scan_chain(). It only > > prints the message before and after the for loop but skip the loop. > > Please reread my hunch below. It looks like I nailed it on the head. > The fact that the first pci_scan_bus shows devices below 0x18 is > confirmation of this. > > mainboard_operations needs to specify amdk8_scan_root_bus. > What exactly are you talking about ? It is amdk8_scan_root_bus in ibm/e325/mainboard.c. static struct device_operations mainboard_operations = { .read_resources = root_dev_read_resources, .set_resources = root_dev_set_resources, .enable_resources = enable_childrens_resources, .init = mainboard_init, .scan_bus = amdk8_scan_root_bus, .enable = 0, }; Ollie From dwh at lanl.gov Mon Apr 26 16:01:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Mon Apr 26 16:01:01 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions In-Reply-To: <408D6DA8.6060807@roemling.net> Message-ID: On Mon, 26 Apr 2004, Jochen Roemling wrote: > I spent hours on the net trying to find a suitable motherboard. To be > serious: I found not even one that seems to be supported by LinuxBIOS, > supports everything I need and is still in the shops of the retailers or > eBay. The Status page on linuxbios.org seems to contain mainly very > small boards with only 2 or 3 PCI slots that are aimed towards cluster > nodes. The EPIA-M seems to be a popular choice for personal video apps. > reply at least yes or no, I would then commit a HOWTO if I get the whole > stuff working: Awesome. > 1. I found out that LinuxBIOS supports VGA only for very few chipsets > like the SiS630. If I would use a VGA card that comes with it's own BIOS > (let's say some ATI radeon) and not using any on-board-VGA-device, would > it work if the mainboard has a LinuxBIOS-supported chipset? My feelings > say "yes", don't they? Vendors haven't exactly been the most cooperative with sharing VGABIOS info. But we do have video working at least on the EPIA, SiS630, and now the Rage XL chips that come on server boards like the S2885 and HDAMA. However, you probably want something more powerful than those. We don't have nVidia or ATi Radeon support coming up from the get-go just yet, but so far we've been able to start a GeForce FX vgabios with 8x AGP support on a Tyan S2885. This is done with an x86 emulator that runs the vgabios after LinuxBIOS has already started. > 3. Just to verify that I understood everything right: The Kernel that is > burned into the DoC will be the kernel that runs the machine after > bootup and it is possible to mount the root fs via NFS just like LTSP > does? Or will the kernel on the DoC just to be used to initialize the > hardware and then load another kernel via the net or from disk? Or do I > have both possibilities? You can boot your kernel from pretty much anywhere. If your flash part is big enough, you can put a kernel on it. Otherwise, you can boot off an ide hard disk, compact flash, or over the network. > 4. Is it correct that kernel 2.4.19 is the latest one supported by > LinuxBIOS? Should the patches be good for 2.4.26 also? What about 2.6? You can run any kernel. We're currently running 2.6.5 on our Opteron systems. > Maybe you can recommend some motherboards out of the box that are still > available in the shops? They should support CPUs with about 1200 MHz, HOw much did you want to spend on the thing? If you want fast, you might want to try a Tyan S2880, as YhLu has that working with VGA (Rage XL). It also has plenty of PCI slots, and will take dual Opterons. From bmaly at angstrom.com Mon Apr 26 16:09:00 2004 From: bmaly at angstrom.com (Brian Maly) Date: Mon Apr 26 16:09:00 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions In-Reply-To: <408D6DA8.6060807@roemling.net> References: <408D6DA8.6060807@roemling.net> Message-ID: <1083014458.16313.102.camel@maly> > 1. I found out that LinuxBIOS supports VGA only for very few chipsets > like the SiS630. If I would use a VGA card that comes with it's own BIOS > (let's say some ATI radeon) and not using any on-board-VGA-device, would > it work if the mainboard has a LinuxBIOS-supported chipset? My feelings > say "yes", don't they? > You will need some video device supported by linuxbios. If the video chipset is supported in linuxbios, then it should work, but its worth mentioning that VGA is not yet supported on many/most motherboards... Framebuffer support may be a better option. You could use something like an ATI RageXL or other supported framebuffer device. > 2. I'm going to use the Hauppauge PVR 350 card that has a TV-out which - > according to the net - is available to Linux as a frame buffer device, > so X and the TV Applications should be able to use this. Does this mean > I would be able to boot LinuxBIOS with serial console only and then > start up XFree86 using this PVR 350 Framebuffer device? > You will probably need to initialize this device somehow. If you had a kernel module or some XFree86 patch that does the all of the video init (i.e. biosless init), this will work. Otherwise you will have to create a linuxbios driver for this device so the init can be done in linuxbios. > 3. Just to verify that I understood everything right: The Kernel that is > burned into the DoC will be the kernel that runs the machine after > bootup and it is possible to mount the root fs via NFS just like LTSP > does? Or will the kernel on the DoC just to be used to initialize the > hardware and then load another kernel via the net or from disk? Or do I > have both possibilities? > you can do (1) kernel on DoC, use (2) FILO to boot a kernel off the HD, or (3) etherboot to load the kernel from the network. > 4. Is it correct that kernel 2.4.19 is the latest one supported by > LinuxBIOS? Should the patches be good for 2.4.26 also? What about 2.6? > Linuxbios should boot most kernels. almost all 2.4.X and 2.6.X have worked fine for me. > Maybe you can recommend some motherboards out of the box that are still > available in the shops? They should support CPUs with about 1200 MHz, > have at least 2 PCI slots for TV cards, another PCI slot for an AC97 > soundcard with optical SP/DIF output (only if there is no such > linux-supported connector on-board) and another PCI slot for a 3com > network card with BootROM (not needed if the LinuxBIOS on the DoC is > running the whole machine and can mount root via NFS or if the board can > net-boot via the on-board NIC). Some Opteron MB's have some decent support (even framebuffer).. i.e. Arima/hdama or most of the Tyan's. Tyan may give you a better selection because more motherboards are supported. This assumes you want to dish out some $$$ for an opteron. From rminnich at lanl.gov Mon Apr 26 16:16:25 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 16:16:25 2004 Subject: tyan s2880 build broken? In-Reply-To: <3174569B9743D511922F00A0C943142304B8683B@TYANWEB> Message-ID: On Mon, 26 Apr 2004, YhLu wrote: > So I need disable the code always, and don't send the image to the end user. > > What's pity! you might want to talk to LSI about this, but Eric is right. LSI needs to get their act together. ron From YhLu at tyan.com Mon Apr 26 16:24:16 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 16:24:16 2004 Subject: =?GB2312?B?tPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9rZW4/?= Message-ID: <3174569B9743D511922F00A0C943142304B86884@TYANWEB> I have talked to the LSI two times. I have asked our HW engineers to use adapted chip except special customer requirement. Adaptec don't need download FW into it. Regards YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?26? 14:20 ???: YhLu ??: ebiederman at lnxi.com; linuxbios at clustermatic.org ??: Re: tyan s2880 build broken? On Mon, 26 Apr 2004, YhLu wrote: > So I need disable the code always, and don't send the image to the end user. > > What's pity! you might want to talk to LSI about this, but Eric is right. LSI needs to get their act together. ron From YhLu at tyan.com Mon Apr 26 16:31:37 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 16:31:37 2004 Subject: =?GB2312?B?tPC4tDogUFZSIHdpdGggTGludXhCSU9TLiBXaGF0IGJvYXJkIGlz?= =?GB2312?B?IHJlY29tbWVuZGVkPyBTb21lIHF1ZXN0aW9ucw==?= Message-ID: <3174569B9743D511922F00A0C943142304B86886@TYANWEB> S2850 would be better that s2880. It only takes one CPU. YH -----????----- ???: Hendricks David W. [mailto:dwh at lanl.gov] ????: 2004?4?26? 14:11 ???: Jochen Roemling ??: linuxbios at clustermatic.org ??: Re: PVR with LinuxBIOS. What board is recommended? Some questions On Mon, 26 Apr 2004, Jochen Roemling wrote: > I spent hours on the net trying to find a suitable motherboard. To be > serious: I found not even one that seems to be supported by LinuxBIOS, > supports everything I need and is still in the shops of the retailers or > eBay. The Status page on linuxbios.org seems to contain mainly very > small boards with only 2 or 3 PCI slots that are aimed towards cluster > nodes. The EPIA-M seems to be a popular choice for personal video apps. > reply at least yes or no, I would then commit a HOWTO if I get the whole > stuff working: Awesome. > 1. I found out that LinuxBIOS supports VGA only for very few chipsets > like the SiS630. If I would use a VGA card that comes with it's own BIOS > (let's say some ATI radeon) and not using any on-board-VGA-device, would > it work if the mainboard has a LinuxBIOS-supported chipset? My feelings > say "yes", don't they? Vendors haven't exactly been the most cooperative with sharing VGABIOS info. But we do have video working at least on the EPIA, SiS630, and now the Rage XL chips that come on server boards like the S2885 and HDAMA. However, you probably want something more powerful than those. We don't have nVidia or ATi Radeon support coming up from the get-go just yet, but so far we've been able to start a GeForce FX vgabios with 8x AGP support on a Tyan S2885. This is done with an x86 emulator that runs the vgabios after LinuxBIOS has already started. > 3. Just to verify that I understood everything right: The Kernel that is > burned into the DoC will be the kernel that runs the machine after > bootup and it is possible to mount the root fs via NFS just like LTSP > does? Or will the kernel on the DoC just to be used to initialize the > hardware and then load another kernel via the net or from disk? Or do I > have both possibilities? You can boot your kernel from pretty much anywhere. If your flash part is big enough, you can put a kernel on it. Otherwise, you can boot off an ide hard disk, compact flash, or over the network. > 4. Is it correct that kernel 2.4.19 is the latest one supported by > LinuxBIOS? Should the patches be good for 2.4.26 also? What about 2.6? You can run any kernel. We're currently running 2.6.5 on our Opteron systems. > Maybe you can recommend some motherboards out of the box that are still > available in the shops? They should support CPUs with about 1200 MHz, HOw much did you want to spend on the thing? If you want fast, you might want to try a Tyan S2880, as YhLu has that working with VGA (Rage XL). It also has plenty of PCI slots, and will take dual Opterons. _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From jochen at roemling.net Mon Apr 26 16:48:01 2004 From: jochen at roemling.net (Jochen Roemling) Date: Mon Apr 26 16:48:01 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions In-Reply-To: <1083014458.16313.102.camel@maly> References: <408D6DA8.6060807@roemling.net> <1083014458.16313.102.camel@maly> Message-ID: <408D86EF.5060502@roemling.net> Brian Maly wrote: >>1. I found out that LinuxBIOS supports VGA only for very few chipsets >>like the SiS630. If I would use a VGA card that comes with it's own BIOS >>(let's say some ATI radeon) and not using any on-board-VGA-device, would >>it work if the mainboard has a LinuxBIOS-supported chipset? My feelings >>say "yes", don't they? >> >You will need some video device supported by linuxbios. If the video >chipset is supported in linuxbios, then it should work, but its worth >mentioning that VGA is not yet supported on many/most motherboards... >Framebuffer support may be a better option. You could use something like >an ATI RageXL or other supported framebuffer device. > > > Okay, so the Mainboard BIOS initializes all other BIOSes (VGA, SCSI...). I always thought they pop up by themselves (silly, yeah) and only the on-board components that are normally initialized by the Mainboard BIOS need to be activated... maybe this thought was formed because the VGA BIOS is always first and then ... forget it. But ATI Rage XL sounds good. It's just the category I was looking for: Fast, cheap, passive cooling, available in eBay. Very good. >>2. I'm going to use the Hauppauge PVR 350 card that has a TV-out which - >>according to the net - is available to Linux as a frame buffer device, >>so X and the TV Applications should be able to use this. Does this mean >>I would be able to boot LinuxBIOS with serial console only and then >>start up XFree86 using this PVR 350 Framebuffer device? >> >> >You will probably need to initialize this device somehow. If you had a >kernel module or some XFree86 patch that does the all of the video init >(i.e. biosless init), this will work. Otherwise you will have to create >a linuxbios driver for this device so the init can be done in linuxbios. > > We will see. The PVR 350 project page sounds promissing. The card has no own BIOS, the TV out is just a frame buffer device and they have their own kernel module for it. >you can do (1) kernel on DoC, use (2) FILO to boot a kernel off the HD, >or (3) etherboot to load the kernel from the network. > > > Okay, this is still not quite understood: In order to be able to initialize the mainboard the mainline kernel has to be patched with some kind of boot-loader-from-DoC-thing. But where are the patches for 2.6? They are not in CVS. And what about this Etherboot: Can I use some ordinary BootROM? I don't think so. This means, the code on the DoC simulates a BootROM and then does dhcp, tftp and the like? I gues I have to seek out for more documentation. This seems to be a good solution because you never have to update your DoC again once it does it's job. With the kernel in the DoC you may want to upgrade from time to time if new kernels arrive. >Arima/hdama or most of the Tyan's. Tyan may give you a better selection >because more motherboards are supported. This assumes you want to dish >out some $$$ for an opteron. > > No, definitely not. I thought about a more consumer-like board with an Athlon or Celeron. SiS630 sounded like a good choise, but the only boards I could find was a Gigabyte GA-6SMZ7, which is nowhere in the stores. Same with the ASUS CUSI. And this EPIA pops up everywhere on PVR pages, but it has only 2 PCI slots... very dificult to decide... Thanks for your quick reply btw. Jochen From dwh at lanl.gov Mon Apr 26 16:55:46 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Mon Apr 26 16:55:46 2004 Subject: =?GB2312?B?tPC4tDogdHlhbiBzMjg4MCBidWlsZCBicm9rZW4/?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86884@TYANWEB> Message-ID: What about 3Ware? They had someone on this list a while ago, so maybe they'd be willing to help. On Mon, 26 Apr 2004, YhLu wrote: > I have talked to the LSI two times. > > I have asked our HW engineers to use adapted chip except special customer > requirement. Adaptec don't need download FW into it. > > Regards > > YH > > > > -----????????----- > ??????: ron minnich [mailto:rminnich at lanl.gov] > ????????: 2004??4??26?? 14:20 > ??????: YhLu > ????: ebiederman at lnxi.com; linuxbios at clustermatic.org > ????: Re: tyan s2880 build broken? > > On Mon, 26 Apr 2004, YhLu wrote: > > > So I need disable the code always, and don't send the image to the end > user. > > > > What's pity! > > you might want to talk to LSI about this, but Eric is right. LSI needs to > get their act together. > > ron > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Mon Apr 26 17:09:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 17:09:01 2004 Subject: =?utf-8?B?562U5aSNOiDnrZTlpI06IHR5YW4gczI4ODAgYnVpbGQgYnJva2Vu?= =?utf-8?B?Pw==?= Message-ID: <3174569B9743D511922F00A0C943142304B86894@TYANWEB> I talked to lsi again, and they will do sth. -----????----- ???: Hendricks David W. [mailto:dwh at lanl.gov] ????: 2004?4?26? 15:02 ???: YhLu ??: linuxbios at clustermatic.org ??: Re: ????: tyan s2880 build broken? What about 3Ware? They had someone on this list a while ago, so maybe they'd be willing to help. On Mon, 26 Apr 2004, YhLu wrote: > I have talked to the LSI two times. > > I have asked our HW engineers to use adapted chip except special customer > requirement. Adaptec don't need download FW into it. > > Regards > > YH > > > > -----????????----- > ??????: ron minnich [mailto:rminnich at lanl.gov] > ????????: 2004??4??26?? 14:20 > ??????: YhLu > ????: ebiederman at lnxi.com; linuxbios at clustermatic.org > ????: Re: tyan s2880 build broken? > > On Mon, 26 Apr 2004, YhLu wrote: > > > So I need disable the code always, and don't send the image to the end > user. > > > > What's pity! > > you might want to talk to LSI about this, but Eric is right. LSI needs to > get their act together. > > ron > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From johnl at blurbco.com Mon Apr 26 17:53:00 2004 From: johnl at blurbco.com (John Laur) Date: Mon Apr 26 17:53:00 2004 Subject: Via Epia-MII BiosSavior problems In-Reply-To: <200404262032.40883.nacho@estudio-verona.com> References: <200404262032.40883.nacho@estudio-verona.com> Message-ID: <408D9649.80005@blurbco.com> Ignacio Verona wrote: > 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, using the serial console, I can see LinuxBios boot > up, but I hangs (this does not worry my at this time), 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?? The flash part that they are using in the newer RD1-PL's is kind of crappy. It takes me quite a few tries to get it to flash properly. I have put the original bios onto the RD1 and do my LinuxBIOS developing on the original flash part. I suspect you are probably in the same situation. Flash with your switch set to RD1 and then do a verify to make sure that it worked ok.. Repeat if not until you are successful. This has taken me someitmes 10 times to get a correct flash.. I don't know if it's flash_rom's fault or the flash part. I suspect the latter is the problem since there is never a problem flashing the original part. John From ebiederman at lnxi.com Mon Apr 26 18:02:01 2004 From: ebiederman at lnxi.com (Eric W. Biederman) Date: Mon Apr 26 18:02:01 2004 Subject: Why devices ARE or NOT on bus 0 ? In-Reply-To: <1083013655.18413.2.camel@exponential.lanl.gov> References: <1082741333.18711.1075.camel@exponential.lanl.gov> <1082994930.18711.1081.camel@exponential.lanl.gov> <1083013655.18413.2.camel@exponential.lanl.gov> Message-ID: Li-Ta Lo writes: > On Mon, 2004-04-26 at 11:58, Eric W. Biederman wrote: > > Li-Ta Lo writes: > > > > > > You might need to specify the bridges/busses in Config.lb. > > > > I know the current code works and can handle this. > > > > > > > > > Does anyone can help on this ? > > > > > > > > Without something like a serial console trace so that the details > > > > of what are going on are clear I don't know. > > > > > > > > > > Please see that attached log. As you ca see the HyperTransport scan > > > is not actually done in northbridge.c:amdk8_scan_chain(). It only > > > prints the message before and after the for loop but skip the loop. > > > > Please reread my hunch below. It looks like I nailed it on the head. > > The fact that the first pci_scan_bus shows devices below 0x18 is > > confirmation of this. > > > > mainboard_operations needs to specify amdk8_scan_root_bus. > > > > > What exactly are you talking about ? It is amdk8_scan_root_bus > in ibm/e325/mainboard.c. > > static struct device_operations mainboard_operations = { > .read_resources = root_dev_read_resources, > .set_resources = root_dev_set_resources, > .enable_resources = enable_childrens_resources, > .init = mainboard_init, > .scan_bus = amdk8_scan_root_bus, > .enable = 0, > }; Hmm. So it is there. For some reason it is not being called. A missing chip.h perhaps? My old copy of that code does: max = pci_scan_bus(&root->link[0], PCI_DEVFN(0x18, 0), 0xff, max); So it starts at device 0x18 (The first cpu) and works down. That is not happening so that code is not being called. I don't know why/how it is failing except possibly for fragility in the config tool. But I observe it is not. Eric From YhLu at tyan.com Mon Apr 26 18:48:00 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 18:48:00 2004 Subject: =?GB2312?B?tPC4tDogV2h5IGRldmljZXMgQVJFIG9yIE5PVCBvbiBidXMgMCA/?= Message-ID: <3174569B9743D511922F00A0C943142304B868C3@TYANWEB> Does "up" "across" control something now? cpu k8 "cpu0" register "across" = "{ .chip = &amd8131, .ht_width=16, .ht_speed=600 }" end YH -----????----- ???: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] ????: 2004?4?26? 16:20 ???: Li-Ta Lo ??: LinuxBIOS ??: Re: Why devices ARE or NOT on bus 0 ? Li-Ta Lo writes: > On Mon, 2004-04-26 at 11:58, Eric W. Biederman wrote: > > Li-Ta Lo writes: > > > > > > You might need to specify the bridges/busses in Config.lb. > > > > I know the current code works and can handle this. > > > > > > > > > Does anyone can help on this ? > > > > > > > > Without something like a serial console trace so that the details > > > > of what are going on are clear I don't know. > > > > > > > > > > Please see that attached log. As you ca see the HyperTransport scan > > > is not actually done in northbridge.c:amdk8_scan_chain(). It only > > > prints the message before and after the for loop but skip the loop. > > > > Please reread my hunch below. It looks like I nailed it on the head. > > The fact that the first pci_scan_bus shows devices below 0x18 is > > confirmation of this. > > > > mainboard_operations needs to specify amdk8_scan_root_bus. > > > > > What exactly are you talking about ? It is amdk8_scan_root_bus > in ibm/e325/mainboard.c. > > static struct device_operations mainboard_operations = { > .read_resources = root_dev_read_resources, > .set_resources = root_dev_set_resources, > .enable_resources = enable_childrens_resources, > .init = mainboard_init, > .scan_bus = amdk8_scan_root_bus, > .enable = 0, > }; Hmm. So it is there. For some reason it is not being called. A missing chip.h perhaps? My old copy of that code does: max = pci_scan_bus(&root->link[0], PCI_DEVFN(0x18, 0), 0xff, max); So it starts at device 0x18 (The first cpu) and works down. That is not happening so that code is not being called. I don't know why/how it is failing except possibly for fragility in the config tool. But I observe it is not. Eric _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From stuge-linuxbios at cdy.org Mon Apr 26 19:37:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Mon Apr 26 19:37:01 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions In-Reply-To: <408D86EF.5060502@roemling.net> References: <408D6DA8.6060807@roemling.net> <1083014458.16313.102.camel@maly> <408D86EF.5060502@roemling.net> Message-ID: <20040427005211.GA8246@foo.birdnet.se> On Tue, Apr 27, 2004 at 12:02:23AM +0200, Jochen Roemling wrote: > Brian Maly wrote: > > >you can do (1) kernel on DoC, use (2) FILO to boot a kernel off the HD, > >or (3) etherboot to load the kernel from the network. > > Okay, this is still not quite understood: Currently there are a number of options to the DiskOnChip. LinuxBIOS in itself is quite small, in the tens of KBs. LinuxBIOS initializes hardware and then hands over to a "payload". LinuxBIOS and the payload both have to fit in the flash ROM on the mainboard. The payload needs to be in a specific format. The payload can contain a kernel or a bootloader such as FILO or Etherboot or even some other software, e.g. the baremetal toolkit even if it hasn't been mentioned for a while. Both FILO and Etherboot support loading a kernel from various media. FILO is popular for loading a kernel from IDE media, ie. harddisk, CD-ROM, CompactFlash-in-IDE-adapter, etc. Etherboot is the best choice for loading the kernel from the network. FILO and Etherboot are also quite small, also in the tens of KBs. A kernel is the opposite - large. In order to use a kernel for payload there has to be room in the flash memory part on the mainboard and unfortunately this usually isn't the case. 2 Megabit parts are very common these days and 2Mbit == 256Kbyte, so no kernel in there. 4 Megabit parts are becoming popular and with 512Kbyte of room a kernel is feasible, but not really a full-blown one. Rather this would require a "two kernel monte" where the first kernel loads a fuller-featured kernel from somewhere. This required Eric Biederman's kexec() patch in earlier 2.4, I'm not sure if kexec() is integrated in later 2.4 and 2.6. The DOC was initially used as a trick to get more storage space from the flash ROM - as you might have found, the DOC replaces the flash ROM and allows windowed (aka paged) access to all of the DOC memory through a small window. This works well, but the catch is that only 512 bytes are available for the very first code to be executed when the CPU is reset, and these 512 bytes of code have to initialize the system RAM. This has proved to be difficult at best with current systems. > And what about this Etherboot: Can I use some ordinary BootROM? I > don't think so. This means, the code on the DoC simulates a BootROM > and then does dhcp, tftp and the like? I gues I have to seek out for > more documentation. Etherboot was initially developed as a bootrom project targeted at boot ROMs on networking cards. Etherboot has turned out to be very usable for other purposes as well, such as LinuxBIOS. :) > >Arima/hdama or most of the Tyan's. Tyan may give you a better selection > >because more motherboards are supported. This assumes you want to dish > >out some $$$ for an opteron. > > No, definitely not. I thought about a more consumer-like board with an > Athlon or Celeron. > SiS630 sounded like a good choise, but the only boards I could find was > a Gigabyte GA-6SMZ7, which is nowhere in the stores. Same with the ASUS > CUSI. And this EPIA pops up everywhere on PVR pages, but it has only 2 > PCI slots... very dificult to decide... Check out the entire EPIA line, I think there are models that combine passive cooling with TV-out, which is why it's popular for TV-things. There has been success with video initialization of the VGA on EPIA boards too, as I recall. However this was in the old "version 1" branch and all current development efforts are going into the "version 2" branch - each mainboard being moved over in turn. I believe the good people at LANL are working on completing the EPIA support right now. My humble suggestion would be to try to find a suitable EPIA board and use LinuxBIOS with FILO as the payload, and use a CF+IDE-adapter for kernel and system storage. I haven't done any work to support the suggestion, but still it seems and feels like the shortest path to your goal, especially since Ron+Ollie+Greg at LANL and others are working on finalizing EPIA support in v2. :) Hope this helps! (Oh, and feel free to edit this short writeup and put it on the web somewhere to serve as some kind of status report..) //Peter From stuge-linuxbios at cdy.org Mon Apr 26 19:46:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Mon Apr 26 19:46:01 2004 Subject: tyan s2880 build broken? In-Reply-To: <3174569B9743D511922F00A0C943142304B86894@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86894@TYANWEB> Message-ID: <20040427010049.GB8246@foo.birdnet.se> On Mon, Apr 26, 2004 at 03:13:51PM -0700, YhLu wrote: > I talked to lsi again, and they will do sth. Great news, even if we haven't seen the results. Thanks a lot! :) //Peter From rminnich at lanl.gov Mon Apr 26 20:33:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 20:33:00 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions In-Reply-To: <20040427005211.GA8246@foo.birdnet.se> Message-ID: On Tue, 27 Apr 2004, Peter Stuge wrote: > My humble suggestion would be to try to find a suitable EPIA board and > use LinuxBIOS with FILO as the payload, and use a CF+IDE-adapter for > kernel and system storage. I haven't done any work to support the > suggestion, but still it seems and feels like the shortest path to your > goal, especially since Ron+Ollie+Greg at LANL and others are working on > finalizing EPIA support in v2. :) that's the right way to go -- it's how we do our EPIAs here. linuxbios + file (in FLASH) + Linux kernel (in IDE-FLASH) ron From YhLu at tyan.com Mon Apr 26 20:46:01 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 20:46:01 2004 Subject: Etherboot 5.2.4 + btext console + filo patch Message-ID: <3174569B9743D511922F00A0C943142304B868E0@TYANWEB> Stefan or Eric, Please help to test the patch. After add sth in filo_x.c, we can support simple menu.... Regards YH -------------- next part -------------- A non-text attachment was scrubbed... Name: etherboot-5.2.4_btext_filo.diff.bz2 Type: application/octet-stream Size: 84900 bytes Desc: not available URL: From YhLu at tyan.com Mon Apr 26 21:02:00 2004 From: YhLu at tyan.com (YhLu) Date: Mon Apr 26 21:02:00 2004 Subject: =?GB2312?B?tPC4tDogRXRoZXJib290IDUuMi40ICsgYnRleHQgY29uc29sZSAr?= =?GB2312?B?IGZpbG8gcGF0Y2g=?= Message-ID: <3174569B9743D511922F00A0C943142304B868E4@TYANWEB> Ron, Do you need to create contrib or payload dir to put such kind of patch. Because Etherboot group may not accept such kind of patch. Regards YH -----????----- ???: YhLu ????: 2004?4?26? 19:11 ???: Stefan Reinauer; ebiederman at lnxi.com; ron minnich ??: Linuxbios at clustermatic.org ??: Etherboot 5.2.4 + btext console + filo patch Stefan or Eric, Please help to test the patch. After add sth in filo_x.c, we can support simple menu.... Regards YH From rminnich at lanl.gov Mon Apr 26 21:12:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Mon Apr 26 21:12:00 2004 Subject: =?GB2312?B?tPC4tDogRXRoZXJib290IDUuMi40ICsgYnRleHQgY29uc29sZSAr?= =?GB2312?B?IGZpbG8gcGF0Y2g=?= In-Reply-To: <3174569B9743D511922F00A0C943142304B868E4@TYANWEB> Message-ID: On Mon, 26 Apr 2004, YhLu wrote: > Do you need to create contrib or payload dir to put such kind of patch. I think this has come up. I hate like heck to think about putting a fork of Etherboot in the linuxbios tree. It just seems like a bad idea. I think we need to figure out what about it Etherboot group might not like, and try to resolve it. This is a conflict resolution step we try (and do not always succeed) to apply in this group. Sometimes, we just proceed without resolving the disagreement, but that is obviously not desirable. Filo is a different situation, as it has no real home and I don't think Takeshita would object if Filo was in a contrib part of the linuxbios tree. comments anyone? ron From jbors at mail.ru Mon Apr 26 21:19:01 2004 From: jbors at mail.ru (Dmitry Borisov) Date: Mon Apr 26 21:19:01 2004 Subject: EPIA-M startup times Message-ID: <009001c42c00$1a106240$0900a8c0@amr.corp.intel.com> Guys, Just wanted to have your estimate about startup times for EPIA-M mobo. ATM it takes about 9 secs to go to payload. 7 secs to go to splash. Which seems to be really high values. Does anyone can say what it would be if everything is "perfect" ? How much time at minimum the BIOS can take assuming RAM, VGA and PCI initialized properly ? If the answer would be 4 secs in ideal case, I'll invest some time to tighten it up... If 9 secs is a minimum, then... Any suggestions ? Dmitry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevin at koconnor.net Mon Apr 26 23:57:01 2004 From: kevin at koconnor.net (Kevin O'Connor) Date: Mon Apr 26 23:57:01 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions In-Reply-To: <408D86EF.5060502@roemling.net> References: <408D6DA8.6060807@roemling.net> <1083014458.16313.102.camel@maly> <408D86EF.5060502@roemling.net> Message-ID: <20040427051142.GA3221@ohio.localdomain> On Tue, Apr 27, 2004 at 12:02:23AM +0200, Jochen Roemling wrote: > Okay, this is still not quite understood: In order to be able to > initialize the mainboard the mainline kernel has to be patched with some > kind of boot-loader-from-DoC-thing. But where are the patches for 2.6? All recent Linux kernels can handle the DoC via the MTD driver. However, I don't think many linuxbios developers are using the DoC anymore. New developments have enabled linuxbios to get the kernel from ide disks (eg compactflash) and from an ethernet network. If I were you I wouldn't go the DoC route. >And this EPIA pops up everywhere on PVR pages, but it has only 2 > PCI slots... very dificult to decide... You should also be aware that the EPIA processors are not the fastest. If you use the PVR-350 and use its hardware MPEG2 compression and decompression you should be ok. But, if you try to use the epia's cpu to compress and/or decompress you could hit the cpu limits. -Kevin -- --------------------------------------------------------------------- | Kevin O'Connor "BTW, IMHO we need a FAQ for | | kevin at koconnor.net 'IMHO', 'FAQ', 'BTW', etc. !" | --------------------------------------------------------------------- From linuxbios at matter.net Tue Apr 27 01:04:01 2004 From: linuxbios at matter.net (Larry Matter) Date: Tue Apr 27 01:04:01 2004 Subject: PVR with LinuxBIOS. What board is recommended? Some questions In-Reply-To: <20040427051142.GA3221@ohio.localdomain> References: <408D6DA8.6060807@roemling.net> <1083014458.16313.102.camel@maly> <408D86EF.5060502@roemling.net> <20040427051142.GA3221@ohio.localdomain> Message-ID: <34090.192.168.1.140.1083046733.squirrel@mail.matter.net> I am also building a PVR solution and am hoping LinuxBIOS will help the startup time (and be a neat project). >>And this EPIA pops up everywhere on PVR pages, but it has only 2 >> PCI slots... very dificult to decide... > > You should also be aware that the EPIA processors are not the fastest. If > you use the PVR-350 and use its hardware MPEG2 compression and > decompression you should be ok. But, if you try to use the epia's cpu to > compress and/or decompress you could hit the cpu limits. I'm currently using EPIA-M's with MythTV (http://mythtv.org) and am quite happy with them. My project is described at http://linpvr.org. I would be happy to talk to you about my experience. It's off-topic for this list but you can email me or use the forum on my website. I currently have LinuxBIOS loading etherboot as the payload and that loads a kernel over the net. I don't have VGA working yet but I understand that has been done by others so I'm hopeful this will work out. Larry From linuxbios at matter.net Tue Apr 27 01:23:00 2004 From: linuxbios at matter.net (Larry Matter) Date: Tue Apr 27 01:23:00 2004 Subject: EPIA-M startup times In-Reply-To: <009001c42c00$1a106240$0900a8c0@amr.corp.intel.com> References: <009001c42c00$1a106240$0900a8c0@amr.corp.intel.com> Message-ID: <34103.192.168.1.140.1083047838.squirrel@mail.matter.net> > Guys, > Just wanted to have your estimate about startup times for EPIA-M mobo. > ATM it takes about 9 secs to go to payload. Hmm. I'm seeing about 5 seconds from power on until I get an etherboot message. This is on an EPIA MEII 6000. I don't have the vga bios in there, would that account for the difference? Then etherboot prints out: Analyzing Media type,this will take several seconds........OK It doesn't actually take very long, but it bothers me anyway :-) It's about 18-20 seconds until the kernel starts all the way up and complains about my lack of a valid NFS root. Larry From rminnich at lanl.gov Tue Apr 27 08:43:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 27 08:43:01 2004 Subject: EPIA-M startup times In-Reply-To: <009001c42c00$1a106240$0900a8c0@amr.corp.intel.com> Message-ID: On Mon, 26 Apr 2004, Dmitry Borisov wrote: > ATM it takes about 9 secs to go to payload. yikes! I think it is time to revive Ollie's serial post + tsc, which for some reason went away. That's nuts. > 7 secs to go to splash. Which seems to be really high values. > Does anyone can say what it would be if everything is "perfect" ? 1 second to go to payload is pretty good. 9 seconds is really odd. we need to start tracing timing again. ron From ollie at lanl.gov Tue Apr 27 11:09:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Tue Apr 27 11:09:00 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= Why devices ARE or NOT on bus 0 ? In-Reply-To: <3174569B9743D511922F00A0C943142304B868C3@TYANWEB> References: <3174569B9743D511922F00A0C943142304B868C3@TYANWEB> Message-ID: <1083082998.18413.4.camel@exponential.lanl.gov> On Mon, 2004-04-26 at 18:12, YhLu wrote: > Does "up" "across" control something now? > > cpu k8 "cpu0" > register "across" = "{ .chip = &amd8131, .ht_width=16, .ht_speed=600 > }" > end > I don't think so but I change it because it is LDT1 connecting to the HUB. Ollie From ollie at lanl.gov Tue Apr 27 11:56:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Tue Apr 27 11:56:00 2004 Subject: IBM/E325 problem fixed, other problems remain Message-ID: <1083085858.18413.14.camel@exponential.lanl.gov> Hello, I fixed the problem of all device on bus 0. It was an undefined struct chip_control mainboard_ibm_e325_control, it is declared in chip.h but is not actually defined in mainboar.c. Ron forgot to change the name of the strucutre to ibm_e325 from arima_hdama. Now the questions, why didn't gcc complain about this ? If that line in chip.h is treated as "declaration" than missing the real definition in mainboard.c for the IBM/E325 before is an error. If that line in chip.h is a definition than the second definition in mainboard.c for all other mainboards is an error. Why does not gcc say anything ? Should I go back to school to learn C programming language again ? Ollie From firstone5 at hotmail.com Tue Apr 27 12:25:01 2004 From: firstone5 at hotmail.com (M. Renee Hopkins) Date: Tue Apr 27 12:25:01 2004 Subject: EPIA-M startup times Message-ID: Are you using recent CVS co? I'll bench mine and post soon. _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee? Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 From jochen at roemling.net Tue Apr 27 13:22:01 2004 From: jochen at roemling.net (Jochen Roemling) Date: Tue Apr 27 13:22:01 2004 Subject: PVR with LinuxBIOS. Etherboot questions In-Reply-To: <20040427005211.GA8246@foo.birdnet.se> References: <408D6DA8.6060807@roemling.net> <1083014458.16313.102.camel@maly> <408D86EF.5060502@roemling.net> <20040427005211.GA8246@foo.birdnet.se> Message-ID: <408EA853.9070203@roemling.net> Peter Stuge wrote: >Etherboot was initially developed as a bootrom project targeted at >boot ROMs on networking cards. Etherboot has turned out to be very >usable for other purposes as well, such as LinuxBIOS. :) > > Things are becoming clearer now. I remembered the site http://www.rom-o-matic.net from the days I fiddled around with LTSP (Linux Terminal Server Project). Am I right with those assumtions: 1. I decided to use a Gigabit GA-6BXC board. They cost no more than 5,- Euro + 50,- Euro for a Pentium III 1GHz Slot 1 + few Euro for cheap SD-RAM. Thats perfect and has enough PCI slots. If the PVR-350 framebuffer makes trouble I have the Option to buy another 5,- Euro ATI Rage XL AGP card and use this. 2. I follow the documentation in freebios/Documentation/configmanual.ps and create a build dir 3. do the config and run "make" 4. Create an ELF-image on rom-o-matic.net fitting my NIC 5. Combining the ELF-image with the LinuxBIOS bootloader 6. Create an EEPROM image somehow 7. Buying an EEPROM fitting the mainboard BIOS socket and find someone who can burn the image to a chip 8. Inserting the chip into the BIOS socket. Boot. Done. 9. The Etherboot will contact my LTSP-server via DHCP/tftp. That's the part I'm familiar with. Is this correct? I don't have any clue how steps 5 and 6 will work. Can you please point me to any document or give me some keyword? By the way: I've already tried to compile the GA-6BXC bootloader, but make ended with: gcc -nostdlib -r -o linuxbios_c.o c_start.o linuxbios.a /usr/lib/gcc-lib/i486-linux/3.3.3/libgcc.a gcc -nostdlib -nostartfiles -static -o linuxbios_c -T /home/jochen/linuxbios/freebios/src/config/linuxbios_c.ld linuxbios_c.o linuxbios_c.o(.text+0x61f): In function `mainboard_fixup': : undefined reference to `pci_zero_irq_settings' collect2: ld returned 1 exit status make: *** [linuxbios_c] Error 1 The string "pci_zero_irq_settings" does not appear in the Linux Kernel headers nor in any file of the freebios tree except the function call that the linker complains about. It is in src/mainboard/gigabit/ga-6bxc/mainboard.c, so board-specific. Any idea? >Hope this helps! (Oh, and feel free to edit this short writeup and put >it on the web somewhere to serve as some kind of status report..) > > > Yeah, it did. We are not done, but my understanding for this whole matter grows. Unfortunately my website is in German, but as soon as I bought the hardware and start fiddling I will compile some kind of HOWTO or report. The problem is just that all documentation available is aimed to BIOS hackers. I know C a bit, can read it quite well and I am able to compile OSS-software or the kernel, but when it comes to unresolved symbols, Makefiles or assembly language, I'm out. Thanks so far, best regards Jochen From prl at peterlister.co.uk Tue Apr 27 13:38:00 2004 From: prl at peterlister.co.uk (Peter Lister) Date: Tue Apr 27 13:38:00 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= Etherboot 5.2.4 + btext console + filo patch In-Reply-To: References: Message-ID: <1083091952.12942.12809.camel@eddie> On Tue, 2004-04-27 at 03:26, ron minnich wrote: > I think this has come up. I hate like heck to think about putting a fork > of Etherboot in the linuxbios tree. It just seems like a bad idea. Very bad idea - especially as Etherboot is undergoing significant development just now, with the PXE support (essentially Etherboot's equivalent of ADLO) being complete. Also a managment change, as Ken Yap has handed over to Marty Connor and Tim Legge. > I think we need to figure out what about it Etherboot group might not > like, and try to resolve it. Why not just ask? :) It's being discussed on etherboot-developers right now. > Filo is a different situation, as it has no real home and I don't think > Takeshita would object if Filo was in a contrib part of the linuxbios > tree. My suggestion is to consider managing FILO as part of the Etherboot tree - Etherboot already has an IDE disk driver, which predates FILO, IIRC. The two projects are obvious complements. Also, I'd bet that an integrated set of net / disk / flash device services would play much better for integration with other projects like grub2. From rminnich at lanl.gov Tue Apr 27 13:45:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 27 13:45:01 2004 Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D=3A?= Etherboot 5.2.4 + btext console + filo patch In-Reply-To: <1083091952.12942.12809.camel@eddie> Message-ID: On 27 Apr 2004, Peter Lister wrote: > My suggestion is to consider managing FILO as part of the Etherboot tree > - Etherboot already has an IDE disk driver, which predates FILO, IIRC. > The two projects are obvious complements. Also, I'd bet that an > integrated set of net / disk / flash device services would play much > better for integration with other projects like grub2. There is enough appeal to the simplicity of FILO that we're not as interested (here anyway) in the etherboot integration. FILO is a small simple loader that does what it does well; Etherboot is a whole lot more complex. That does not mean I think merging it in is bad, but I also would like to see it maintain its seperate existence. ron From YhLu at tyan.com Tue Apr 27 13:56:01 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 27 13:56:01 2004 Subject: Etherboot 5.2.4 + btext console + filo patch Message-ID: <3174569B9743D511922F00A0C943142304B8694F@TYANWEB> To me filo is just like enhancement to Etherboot ide_disk.zelf. but it is more smart that it can understand file system and boot linux/initrd instead of elf. If we can put filo into Etherboot official tree, we can make use of the framework of Etherboot. For example in Etherboot you still can only produce filo.zelf, and it is less 32k now. I didn't enable the multiboot in filo of Etherboot yet. YH -----????----- ???: ron minnich [mailto:rminnich at lanl.gov] ????: 2004?4?27? 12:00 ???: Peter Lister ??: YhLu; Stefan Reinauer; Eric W Biederman; LinuxBIOS ??: Re: ??: Etherboot 5.2.4 + btext console + filo patch On 27 Apr 2004, Peter Lister wrote: > My suggestion is to consider managing FILO as part of the Etherboot tree > - Etherboot already has an IDE disk driver, which predates FILO, IIRC. > The two projects are obvious complements. Also, I'd bet that an > integrated set of net / disk / flash device services would play much > better for integration with other projects like grub2. There is enough appeal to the simplicity of FILO that we're not as interested (here anyway) in the etherboot integration. FILO is a small simple loader that does what it does well; Etherboot is a whole lot more complex. That does not mean I think merging it in is bad, but I also would like to see it maintain its seperate existence. ron From dwh at lanl.gov Tue Apr 27 14:14:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Tue Apr 27 14:14:00 2004 Subject: IBM/E325 problem fixed, other problems remain In-Reply-To: <1083085858.18413.14.camel@exponential.lanl.gov> Message-ID: No, school sucks. *falls back asleep* On Tue, 27 Apr 2004, Li-Ta Lo wrote: > Should I go back to school to learn C programming language again ? > > Ollie From rminnich at lanl.gov Tue Apr 27 14:26:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Tue Apr 27 14:26:01 2004 Subject: Etherboot 5.2.4 + btext console + filo patch In-Reply-To: <3174569B9743D511922F00A0C943142304B8694F@TYANWEB> Message-ID: On Tue, 27 Apr 2004, YhLu wrote: > To me filo is just like enhancement to Etherboot ide_disk.zelf. but it is > more smart that it can understand file system and boot linux/initrd instead > of elf. good point. Seems like pinging the etherboot guys is a good idea! ron From bari at onelabs.com Tue Apr 27 14:45:01 2004 From: bari at onelabs.com (Bari Ari) Date: Tue Apr 27 14:45:01 2004 Subject: IBM POWER 976 Support Message-ID: <408EBC1B.8070708@onelabs.com> http://bbs.gzeasy.com/index.php?showtopic=149175 I wonder how much work it will take for LinuxBIOS on XBox-II? -Bari From YhLu at tyan.com Tue Apr 27 14:57:01 2004 From: YhLu at tyan.com (YhLu) Date: Tue Apr 27 14:57:01 2004 Subject: IBM POWER 976 Support Message-ID: <3174569B9743D511922F00A0C943142304B86957@TYANWEB> You can read Chinese? -----????----- ???: Bari Ari [mailto:bari at onelabs.com] ????: 2004?4?27? 13:02 ???: LinuxBIOS ??: IBM POWER 976 Support http://bbs.gzeasy.com/index.php?showtopic=149175 I wonder how much work it will take for LinuxBIOS on XBox-II? -Bari _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From hansolofalcon at worldnet.att.net Tue Apr 27 15:06:01 2004 From: hansolofalcon at worldnet.att.net (Gregg C Levine) Date: Tue Apr 27 15:06:01 2004 Subject: IBM POWER 976 Support In-Reply-To: <3174569B9743D511922F00A0C943142304B86957@TYANWEB> Message-ID: <003901c42c95$430d2260$6401a8c0@who5> Hello from Gregg C Levine Ah, but the picture wasn't done in Chinese. The rest of the website was done that way. I agree, Bari, I wonder how much work it would take to do that. ------------------- Gregg C Levine hansolofalcon at worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."? Obi-Wan Kenobi > -----Original Message----- > From: linuxbios-admin at clustermatic.org [mailto:linuxbios- > admin at clustermatic.org] On Behalf Of YhLu > Sent: Tuesday, April 27, 2004 4:22 PM > To: Bari Ari; LinuxBIOS > Subject: Re: IBM POWER 976 Support > > You can read Chinese? > > -----????????----- > ??????: Bari Ari [mailto:bari at onelabs.com] > ????????: 2004??4??27?? 13:02 > ??????: LinuxBIOS > ????: IBM POWER 976 Support > > http://bbs.gzeasy.com/index.php?showtopic=149175 > > I wonder how much work it will take for LinuxBIOS on XBox-II? > > -Bari > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios From bari at onelabs.com Tue Apr 27 17:04:00 2004 From: bari at onelabs.com (Bari Ari) Date: Tue Apr 27 17:04:00 2004 Subject: IBM POWER 976 Support In-Reply-To: <3174569B9743D511922F00A0C943142304B86957@TYANWEB> References: <3174569B9743D511922F00A0C943142304B86957@TYANWEB> Message-ID: <408EDC9B.5020303@onelabs.com> I wish. I even get lost on take out menus. The pic's are in English luckily. -Bari YhLu wrote: > You can read Chinese? > > -----????----- > ???: Bari Ari [mailto:bari at onelabs.com] > ????: 2004?4?27? 13:02 > ???: LinuxBIOS > ??: IBM POWER 976 Support > > http://bbs.gzeasy.com/index.php?showtopic=149175 > > I wonder how much work it will take for LinuxBIOS on XBox-II? > > -Bari > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > > From cdac_manisha at yahoo.com Wed Apr 28 00:04:01 2004 From: cdac_manisha at yahoo.com (manisha s) Date: Wed Apr 28 00:04:01 2004 Subject: Boot PC from Compact Flash Message-ID: <20040428051924.69808.qmail@web50706.mail.yahoo.com> Hi All, I m new to this mailing list. I want to boot my laptop from 128Mb Compact Flash(CF) Card. On laptop i have already RedHat 9 with kernel version 2.4.22. I downloaded the pebble linux distribution and successsfully downloaded (wrote) this on to the CF. The CF card is available as /dev/sdb on the linux through CF card reader/writer. I changed /etc/grub.conf file so as to include the CF card title Pebble(Pebble) root (hd0,1) kernel /mnt/pebble/boot/vmlinuz-2.4.22-pebble ro root=/dev/sdb1 title Red Hat Linux (2.4.22) root (hd0,1) kernel /boot/vmlinuz-2.4.22 ro root=/dev/hda2 initrd /boot/initrd-2.4.22.img should i copy the vmlinuz-2.4.22-pebble to /boot directory? should i change other than this? plz shed some light on this issue? Thanks in advance __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover From stuge-linuxbios at cdy.org Wed Apr 28 06:23:01 2004 From: stuge-linuxbios at cdy.org (Peter Stuge) Date: Wed Apr 28 06:23:01 2004 Subject: Boot PC from Compact Flash In-Reply-To: <20040428051924.69808.qmail@web50706.mail.yahoo.com> References: <20040428051924.69808.qmail@web50706.mail.yahoo.com> Message-ID: <20040428113805.GA22888@foo.birdnet.se> On Tue, Apr 27, 2004 at 10:19:24PM -0700, manisha s wrote: > Hi All, > I m new to this mailing list. > > I want to boot my laptop from 128Mb Compact Flash(CF) > Card. > On laptop i have already RedHat 9 with kernel version > 2.4.22. This has little to do with LinuxBIOS I'm afraid. > I downloaded the pebble linux distribution and > successsfully downloaded (wrote) this on to the CF. > > The CF card is available as /dev/sdb on the linux > through CF card reader/writer. Your CF reader probably connects via USB and the usb-storage layer in Linux presents it as a SCSI device. > I changed /etc/grub.conf file so as to include the CF > card > > title Pebble(Pebble) > root (hd0,1) > kernel /mnt/pebble/boot/vmlinuz-2.4.22-pebble > ro root=/dev/sdb1 > > title Red Hat Linux (2.4.22) > root (hd0,1) > kernel /boot/vmlinuz-2.4.22 ro root=/dev/hda2 > initrd /boot/initrd-2.4.22.img > > > should i copy the vmlinuz-2.4.22-pebble to /boot > directory? GRUB does not include a USB stack. It can not load the kernel from CF. > should i change other than this? > > plz shed some light on this issue? If you really want to boot from the CF, get a 2.5" IDE-CF adapter, search this mailing list archive for URL. If you want to know whether LinuxBIOS could run on your laptop, which unfortunately is unlikely due to the high degree of customization common in laptop mainboards, you should send us lspci -v output. //Peter From ollie at lanl.gov Wed Apr 28 11:15:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Apr 28 11:15:01 2004 Subject: SMBus and HW monitor Message-ID: <1083169818.18413.35.camel@exponential.lanl.gov> Ron, You copied some smbus and hw monitor code from hdama to e325. Are they correct on this board ? Is the hardware the same across those k8 boards ? Should we move it to some shared directory ? Ollie From ollie at lanl.gov Wed Apr 28 13:21:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Wed Apr 28 13:21:01 2004 Subject: Canonical order of dev_find_device() Message-ID: <1083177383.18413.43.camel@exponential.lanl.gov> Eric, Is there any order for dev_find_device() ? In linux kernel, if there are two devices have the same vendor and device ID, the one with lower BUSDEVFN will be returned first and when the function is called again with the first returned device structure as parameter, the one with higher BUSDEVFN will be returned. Is it the same for LinuxBIOS ? There are some hard coded BUS_DEV_FNs for 8111/8131 bridges in mptable.c for all mainboards. Can we just search for these bridges by ID instead of the hardcoded values ? Ollie From rminnich at lanl.gov Wed Apr 28 14:29:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 14:29:01 2004 Subject: SMBus and HW monitor In-Reply-To: <1083169818.18413.35.camel@exponential.lanl.gov> Message-ID: On Wed, 28 Apr 2004, Li-Ta Lo wrote: > You copied some smbus and hw monitor code from hdama > to e325. Are they correct on this board ? Is the > hardware the same across those k8 boards ? Should we > move it to some shared directory ? I have no clue. Sorry. I just don't know what's on that damned board. It may be time to go read chip package names :-( ron From evan at ddos.com Wed Apr 28 15:28:01 2004 From: evan at ddos.com (Langlois Evan) Date: Wed Apr 28 15:28:01 2004 Subject: LinuxBIOS Video? Message-ID: <36824.68.92.26.41.1083184466.squirrel@mercury.ddos.com> Hi, If video isn't supported on a particular board, does this mean that video won't work at all? I could live with no video until after the Linux kernel initialized things, but I'm guessing that the card won't even be listed in the device table. Could someone explain this to me? Does this apply only to on-board video, or all add-on cards. Am I right in guessing that no add-on video cards are supported? Would it be possible to go into 16 bit mode temporarily to jump into the video ROM and initialize the card? Basically, I want a fast desktop (K8 maybe, the bus speeds seem to make it worth it) without a PC BIOS (I only use Linux, usually Gentoo). It looks like LinuxBIOS is mainly for headless clusters. The "Status" file on the web site looks painfully outdated, and the FAQ really needs some updates, and the mainboard directory in the source wasn't quite specific about what was supported either. I haven't gotten anything from this list in awhile, so please copy me directly as it would seem mail from the list isn't getting to me for some reason (possibly a problem at my end). Thanks, Evan Langlois From dwh at lanl.gov Wed Apr 28 15:37:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Wed Apr 28 15:37:00 2004 Subject: LinuxBIOS Video? In-Reply-To: <36824.68.92.26.41.1083184466.squirrel@mercury.ddos.com> Message-ID: It's a bit sketchy at the time. Right now we can use ATi embedded devices (Rage XL) pretty well, some older stuff like on the SiS630, and EPIA whatever. But for newer stuff like GeForce cards, we have had to toggle some IORRs and stuff and run the VGABIOS after Linux is booted. From here, framebuffering can be used for console display and X can run fully accelerated in AGP8x with fast writes and side band addressing. This has only been tested by us on the Tyan S2885. On Wed, 28 Apr 2004, Langlois Evan wrote: > Hi, > > If video isn't supported on a particular board, does this mean that video > won't work at all? I could live with no video until after the Linux > kernel initialized things, but I'm guessing that the card won't even be > listed in the device table. > > Could someone explain this to me? Does this apply only to on-board video, > or all add-on cards. Am I right in guessing that no add-on video cards > are supported? Would it be possible to go into 16 bit mode temporarily > to jump into the video ROM and initialize the card? > > Basically, I want a fast desktop (K8 maybe, the bus speeds seem to make it > worth it) without a PC BIOS (I only use Linux, usually Gentoo). It looks > like LinuxBIOS is mainly for headless clusters. The "Status" file on the > web site looks painfully outdated, and the FAQ really needs some updates, > and the mainboard directory in the source wasn't quite specific about what > was supported either. > > I haven't gotten anything from this list in awhile, so please copy me > directly as it would seem mail from the list isn't getting to me for some > reason (possibly a problem at my end). > > Thanks, > Evan Langlois > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From dwh at lanl.gov Wed Apr 28 15:37:27 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Wed Apr 28 15:37:27 2004 Subject: LinuxBIOS Video? In-Reply-To: <36824.68.92.26.41.1083184466.squirrel@mercury.ddos.com> Message-ID: It's a bit sketchy at the time. Right now we can use ATi embedded devices (Rage XL) pretty well, some older stuff like on the SiS630, and EPIA whatever. But for newer stuff like GeForce cards, we have had to toggle some IORRs and stuff and run the VGABIOS after Linux is booted. From here, framebuffering can be used for console display and X can run fully accelerated in AGP8x with fast writes and side band addressing. This has only been tested by us on the Tyan S2885. On Wed, 28 Apr 2004, Langlois Evan wrote: > Hi, > > If video isn't supported on a particular board, does this mean that video > won't work at all? I could live with no video until after the Linux > kernel initialized things, but I'm guessing that the card won't even be > listed in the device table. > > Could someone explain this to me? Does this apply only to on-board video, > or all add-on cards. Am I right in guessing that no add-on video cards > are supported? Would it be possible to go into 16 bit mode temporarily > to jump into the video ROM and initialize the card? > > Basically, I want a fast desktop (K8 maybe, the bus speeds seem to make it > worth it) without a PC BIOS (I only use Linux, usually Gentoo). It looks > like LinuxBIOS is mainly for headless clusters. The "Status" file on the > web site looks painfully outdated, and the FAQ really needs some updates, > and the mainboard directory in the source wasn't quite specific about what > was supported either. > > I haven't gotten anything from this list in awhile, so please copy me > directly as it would seem mail from the list isn't getting to me for some > reason (possibly a problem at my end). > > Thanks, > Evan Langlois > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From YhLu at tyan.com Wed Apr 28 16:01:01 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 28 16:01:01 2004 Subject: =?GB2312?B?tPC4tDogTGludXhCSU9TIFZpZGVvPw==?= Message-ID: <3174569B9743D511922F00A0C943142304B86A2B@TYANWEB> To make the onboard ati rage xl framebuffer work under linux, you need patch for 2.4.22 and 2.6.5. the original ati framebuffer even not work under normal bios. In SUN sparc openboot and PowerPC MAC, I guess they are using framebuffer to show text for booting....---> they have limited display card. How about us, only support ati rage xl now. I wonder if we can enable framebuffer for add on display card so we can get output from crt via btext console. YH -----????----- ???: Hendricks David W. [mailto:dwh at lanl.gov] ????: 2004?4?28? 13:52 ???: Langlois Evan ??: linuxbios at clustermatic.org ??: Re: LinuxBIOS Video? It's a bit sketchy at the time. Right now we can use ATi embedded devices (Rage XL) pretty well, some older stuff like on the SiS630, and EPIA whatever. But for newer stuff like GeForce cards, we have had to toggle some IORRs and stuff and run the VGABIOS after Linux is booted. From here, framebuffering can be used for console display and X can run fully accelerated in AGP8x with fast writes and side band addressing. This has only been tested by us on the Tyan S2885. On Wed, 28 Apr 2004, Langlois Evan wrote: > Hi, > > If video isn't supported on a particular board, does this mean that video > won't work at all? I could live with no video until after the Linux > kernel initialized things, but I'm guessing that the card won't even be > listed in the device table. > > Could someone explain this to me? Does this apply only to on-board video, > or all add-on cards. Am I right in guessing that no add-on video cards > are supported? Would it be possible to go into 16 bit mode temporarily > to jump into the video ROM and initialize the card? > > Basically, I want a fast desktop (K8 maybe, the bus speeds seem to make it > worth it) without a PC BIOS (I only use Linux, usually Gentoo). It looks > like LinuxBIOS is mainly for headless clusters. The "Status" file on the > web site looks painfully outdated, and the FAQ really needs some updates, > and the mainboard directory in the source wasn't quite specific about what > was supported either. > > I haven't gotten anything from this list in awhile, so please copy me > directly as it would seem mail from the list isn't getting to me for some > reason (possibly a problem at my end). > > Thanks, > Evan Langlois > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From YhLu at tyan.com Wed Apr 28 16:01:24 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 28 16:01:24 2004 Subject: =?GB2312?B?tPC4tDogTGludXhCSU9TIFZpZGVvPw==?= Message-ID: <3174569B9743D511922F00A0C943142304B86A2B@TYANWEB> To make the onboard ati rage xl framebuffer work under linux, you need patch for 2.4.22 and 2.6.5. the original ati framebuffer even not work under normal bios. In SUN sparc openboot and PowerPC MAC, I guess they are using framebuffer to show text for booting....---> they have limited display card. How about us, only support ati rage xl now. I wonder if we can enable framebuffer for add on display card so we can get output from crt via btext console. YH -----????----- ???: Hendricks David W. [mailto:dwh at lanl.gov] ????: 2004?4?28? 13:52 ???: Langlois Evan ??: linuxbios at clustermatic.org ??: Re: LinuxBIOS Video? It's a bit sketchy at the time. Right now we can use ATi embedded devices (Rage XL) pretty well, some older stuff like on the SiS630, and EPIA whatever. But for newer stuff like GeForce cards, we have had to toggle some IORRs and stuff and run the VGABIOS after Linux is booted. From here, framebuffering can be used for console display and X can run fully accelerated in AGP8x with fast writes and side band addressing. This has only been tested by us on the Tyan S2885. On Wed, 28 Apr 2004, Langlois Evan wrote: > Hi, > > If video isn't supported on a particular board, does this mean that video > won't work at all? I could live with no video until after the Linux > kernel initialized things, but I'm guessing that the card won't even be > listed in the device table. > > Could someone explain this to me? Does this apply only to on-board video, > or all add-on cards. Am I right in guessing that no add-on video cards > are supported? Would it be possible to go into 16 bit mode temporarily > to jump into the video ROM and initialize the card? > > Basically, I want a fast desktop (K8 maybe, the bus speeds seem to make it > worth it) without a PC BIOS (I only use Linux, usually Gentoo). It looks > like LinuxBIOS is mainly for headless clusters. The "Status" file on the > web site looks painfully outdated, and the FAQ really needs some updates, > and the mainboard directory in the source wasn't quite specific about what > was supported either. > > I haven't gotten anything from this list in awhile, so please copy me > directly as it would seem mail from the list isn't getting to me for some > reason (possibly a problem at my end). > > Thanks, > Evan Langlois > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ Linuxbios mailing list Linuxbios at clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios From cforney at opus.com Wed Apr 28 16:26:01 2004 From: cforney at opus.com (Craig C Forney) Date: Wed Apr 28 16:26:01 2004 Subject: Best choice for I/O hub for AMD Opteron In-Reply-To: <20040426163200.11932.57209.Mailman@nwn.definitive.org> Message-ID: <006601c42d68$ce8c5ad0$6400a8c0@opusone> Looking for advice and counsel regarding LinuxBIOS support for I/O hub alternatives ... We've just completed a very dense cPCI dual Opteron design with an AMD 8111 as the I/O hub, no superIO, no 8131, no 8151, with 8GB SDRAM. LinuxBIOS seems to work fine, although the lack of legacy support for serial I/O was problematic (we ended up simulating a serial port). Thanks for everyone's support on helping us with early issues getting up to speed with LinuxBIOS. For our next generation, we would like to use a better supported and more integrated I/O hub than the 8111 (USB 2.0 doesn't work on the 8111, to start with). The nVidia nForce 3-2506B and the VIA K8T800 Pro seem to have a lot of potential, but I'm concerned about support for these from the manufacturers as far as LinuxBIOS is concerned. We don't mind helping with debug on any new code required, but we don't want to even start unless we have some confidence that there will be some level of support and effort behind our choice (and that we are not alone). Are there any opinions out there about these (or other) candidates related to LinuxBIOS? Any comments appreciated. Regards, Craig Forney Opus Innovations LLC Cupertino, CA From evan at ddos.com Wed Apr 28 16:36:01 2004 From: evan at ddos.com (Langlois Evan) Date: Wed Apr 28 16:36:01 2004 Subject: LinuxBIOS Video? In-Reply-To: References: <36824.68.92.26.41.1083184466.squirrel@mercury.ddos.com> Message-ID: <46698.68.92.26.41.1083188560.squirrel@mercury.ddos.com> > It's a bit sketchy at the time. Right now we can use ATi embedded devices > (Rage XL) pretty well, some older stuff like on the SiS630, and EPIA > whatever. But for newer stuff like GeForce cards, we have had to toggle > some IORRs and stuff and run the VGABIOS after Linux is booted. From here, > framebuffering can be used for console display and X can run fully > accelerated in AGP8x with fast writes and side band addressing. This has > only been tested by us on the Tyan S2885. What are the chances of this working on the Tyan S2875S ? Possible with an ATI Radeon card instead of GeForce (assuming the same tricks work on both). http://www.tyan.com/products/html/tigerk8ws.html And does booting from SATA work? I heard something about Tyan supporting LinuxBIOS - is it actually possible to order with LinuxBIOS pre-installed? I noticed there is a port80 LED on this board as well - which may help. Thanks, Evan From dwh at lanl.gov Wed Apr 28 16:42:00 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Wed Apr 28 16:42:00 2004 Subject: LinuxBIOS Video? In-Reply-To: <46698.68.92.26.41.1083188560.squirrel@mercury.ddos.com> Message-ID: We haven't had any success with Radeon cards in LinuxBIOS in our lab, though Ollie Lho might have some more information on that for you. And yes, Tyan does support LinuxBIOS. Just ask YhLu what the best option is. He even has the LSI controller working on the newer Tyan boards, AFAIK. On Wed, 28 Apr 2004, Langlois Evan wrote: > > It's a bit sketchy at the time. Right now we can use ATi embedded devices > > (Rage XL) pretty well, some older stuff like on the SiS630, and EPIA > > whatever. But for newer stuff like GeForce cards, we have had to toggle > > some IORRs and stuff and run the VGABIOS after Linux is booted. From here, > > framebuffering can be used for console display and X can run fully > > accelerated in AGP8x with fast writes and side band addressing. This has > > only been tested by us on the Tyan S2885. > > What are the chances of this working on the Tyan S2875S ? Possible with > an ATI Radeon card instead of GeForce (assuming the same tricks work on > both). > > http://www.tyan.com/products/html/tigerk8ws.html > > And does booting from SATA work? > > I heard something about Tyan supporting LinuxBIOS - is it actually > possible to order with LinuxBIOS pre-installed? I noticed there is a > port80 LED on this board as well - which may help. > > Thanks, > Evan > From dwh at lanl.gov Wed Apr 28 16:42:22 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Wed Apr 28 16:42:22 2004 Subject: LinuxBIOS Video? In-Reply-To: <46698.68.92.26.41.1083188560.squirrel@mercury.ddos.com> Message-ID: We haven't had any success with Radeon cards in LinuxBIOS in our lab, though Ollie Lho might have some more information on that for you. And yes, Tyan does support LinuxBIOS. Just ask YhLu what the best option is. He even has the LSI controller working on the newer Tyan boards, AFAIK. On Wed, 28 Apr 2004, Langlois Evan wrote: > > It's a bit sketchy at the time. Right now we can use ATi embedded devices > > (Rage XL) pretty well, some older stuff like on the SiS630, and EPIA > > whatever. But for newer stuff like GeForce cards, we have had to toggle > > some IORRs and stuff and run the VGABIOS after Linux is booted. From here, > > framebuffering can be used for console display and X can run fully > > accelerated in AGP8x with fast writes and side band addressing. This has > > only been tested by us on the Tyan S2885. > > What are the chances of this working on the Tyan S2875S ? Possible with > an ATI Radeon card instead of GeForce (assuming the same tricks work on > both). > > http://www.tyan.com/products/html/tigerk8ws.html > > And does booting from SATA work? > > I heard something about Tyan supporting LinuxBIOS - is it actually > possible to order with LinuxBIOS pre-installed? I noticed there is a > port80 LED on this board as well - which may help. > > Thanks, > Evan > From bari at onelabs.com Wed Apr 28 22:19:01 2004 From: bari at onelabs.com (Bari Ari) Date: Wed Apr 28 22:19:01 2004 Subject: Best choice for I/O hub for AMD Opteron In-Reply-To: <006601c42d68$ce8c5ad0$6400a8c0@opusone> References: <006601c42d68$ce8c5ad0$6400a8c0@opusone> Message-ID: <4090780F.4070305@onelabs.com> Craig C Forney wrote: > Looking for advice and counsel regarding LinuxBIOS support for I/O hub > alternatives ... > For our next generation, we would like to use a better supported and > more integrated I/O hub than the 8111 (USB 2.0 doesn't work on the 8111, > to start with). The nVidia nForce 3-2506B and the VIA K8T800 Pro seem > to have a lot of potential, but I'm concerned about support for these > from the manufacturers as far as LinuxBIOS is concerned. We don't mind > helping with debug on any new code required, but we don't want to even > start unless we have some confidence that there will be some level of > support and effort behind our choice (and that we are not alone). > > Are there any opinions out there about these (or other) candidates > related to LinuxBIOS? I doubt that you'll get any support from nVidia unless they can make a ton of $$ off your project. VIA will get you hardware specs once you make it into their trusted circle or unless they can make a ton of $$ off your project, which puts you into their trusted circle. AMD is great with specs but they only offer their chipsets as a reference and have no long term plans to support them. Checkout ALI or consider rolling your own with a Xilinx or Altera FPGA. USB from an FPGA is usually the only big catch. A PCI 2.0 4-port host is under $5 but adds to the real estate. PLX also has a HyperTransport to PCI-X bridge. There are a few more things on the horizon but still under NDA. -Bari From rminnich at lanl.gov Wed Apr 28 22:21:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 22:21:01 2004 Subject: =?GB2312?B?tPC4tDogTGludXhCSU9TIFZpZGVvPw==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86A2B@TYANWEB> Message-ID: On Wed, 28 Apr 2004, YhLu wrote: > I wonder if we can enable framebuffer for add on display card so we can get > output from crt via btext console. it's going to happen. First we have to resolve issues with the k8 and linuxbios. ron From rminnich at lanl.gov Wed Apr 28 22:21:14 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 22:21:14 2004 Subject: =?GB2312?B?tPC4tDogTGludXhCSU9TIFZpZGVvPw==?= In-Reply-To: <3174569B9743D511922F00A0C943142304B86A2B@TYANWEB> Message-ID: On Wed, 28 Apr 2004, YhLu wrote: > I wonder if we can enable framebuffer for add on display card so we can get > output from crt via btext console. it's going to happen. First we have to resolve issues with the k8 and linuxbios. ron From rminnich at lanl.gov Wed Apr 28 22:34:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 22:34:01 2004 Subject: Best choice for I/O hub for AMD Opteron In-Reply-To: <006601c42d68$ce8c5ad0$6400a8c0@opusone> Message-ID: I can only say that to date, for this high end stuff, neither VIA nor Nvidia have been very interested in linuxbios. Historically, VIA has been friendlier to linuxbios than most vendors, however. They have certainly been helpful to users of the EPIA series. What you can try to do is ask each vendor for the linuxbios support you need if you use their part. Ask for docs you need to make the part work. Don't make a decision until you are sure you have all the docs you need. You can even try to get sample bios code for making the part work. We'll help you if we can. ron From rminnich at lanl.gov Wed Apr 28 22:37:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 22:37:01 2004 Subject: LinuxBIOS Video? In-Reply-To: <46698.68.92.26.41.1083188560.squirrel@mercury.ddos.com> Message-ID: On Wed, 28 Apr 2004, Langlois Evan wrote: > What are the chances of this working on the Tyan S2875S ? Possible with > an ATI Radeon card instead of GeForce (assuming the same tricks work on > both). It should work fine since the approach we take is 8086 emulation to support the bios. > And does booting from SATA work? not tried. > I heard something about Tyan supporting LinuxBIOS - is it actually > possible to order with LinuxBIOS pre-installed? I noticed there is a > port80 LED on this board as well - which may help. yes indeed. You can contact Charlie Ding (cding at tyan.com) who has been very helpful to linuxbios users. ron From rminnich at lanl.gov Wed Apr 28 22:37:21 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 22:37:21 2004 Subject: LinuxBIOS Video? In-Reply-To: <46698.68.92.26.41.1083188560.squirrel@mercury.ddos.com> Message-ID: On Wed, 28 Apr 2004, Langlois Evan wrote: > What are the chances of this working on the Tyan S2875S ? Possible with > an ATI Radeon card instead of GeForce (assuming the same tricks work on > both). It should work fine since the approach we take is 8086 emulation to support the bios. > And does booting from SATA work? not tried. > I heard something about Tyan supporting LinuxBIOS - is it actually > possible to order with LinuxBIOS pre-installed? I noticed there is a > port80 LED on this board as well - which may help. yes indeed. You can contact Charlie Ding (cding at tyan.com) who has been very helpful to linuxbios users. ron From rminnich at lanl.gov Wed Apr 28 22:38:01 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 22:38:01 2004 Subject: LinuxBIOS Video? In-Reply-To: Message-ID: On Wed, 28 Apr 2004, Hendricks David W. wrote: > We haven't had any success with Radeon cards in LinuxBIOS in our lab, > though Ollie Lho might have some more information on that for you. oops. I didn't realize we had trouble with them. oh well. ron From rminnich at lanl.gov Wed Apr 28 22:38:12 2004 From: rminnich at lanl.gov (ron minnich) Date: Wed Apr 28 22:38:12 2004 Subject: LinuxBIOS Video? In-Reply-To: Message-ID: On Wed, 28 Apr 2004, Hendricks David W. wrote: > We haven't had any success with Radeon cards in LinuxBIOS in our lab, > though Ollie Lho might have some more information on that for you. oops. I didn't realize we had trouble with them. oh well. ron From YhLu at tyan.com Wed Apr 28 22:47:00 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 28 22:47:00 2004 Subject: LinuxBIOS Video? Message-ID: <3174569B9743D511922F00A0C943142304B86A58@TYANWEB> 1. S2875 support is in the CVS tree already. 2. ATI randon --- At this time, you may not get the output from very beginning. 3. boot sata --- good question, I will try that. Maybe need to add some code in filo. Regards YH From YhLu at tyan.com Wed Apr 28 22:51:01 2004 From: YhLu at tyan.com (YhLu) Date: Wed Apr 28 22:51:01 2004 Subject: LinuxBIOS Video? Message-ID: <3174569B9743D511922F00A0C943142304B86A58@TYANWEB> 1. S2875 support is in the CVS tree already. 2. ATI randon --- At this time, you may not get the output from very beginning. 3. boot sata --- good question, I will try that. Maybe need to add some code in filo. Regards YH From joshua at joshuawise.com Thu Apr 29 14:13:00 2004 From: joshua at joshuawise.com (Joshua Wise) Date: Thu Apr 29 14:13:00 2004 Subject: [administrivia] Broken mail servers In-Reply-To: References: Message-ID: <200404291527.58096.joshua@joshuawise.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, evan at ddos.com, it appears your mailserver is broken and is sending email that you are CC'ed to (and possibly any email that you recieve from the list) back to the list. The appropriate message headers showing me this are: Received: from nwn.definitive.org (unknown [65.242.93.132]) by joshuawise.com (Postfix on joshuawise.com) with ESMTP id 28645322A for ; Wed, 28 Apr 2004 23:59:58 -0400 (EDT) Received: from nwn.definitive.org (localhost.localdomain [127.0.0.1]) by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2cGK25945; Wed, 28 Apr 2004 22:38:16 -0400 Received: from mercury.ddos.com (mercury.ddos.com [64.5.62.66]) by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2bEK25893 for ; Wed, 28 Apr 2004 22:37:14 -0400 Received: by mercury.ddos.com (Postfix, from userid 5002) id C531A25418; Wed, 28 Apr 2004 22:44:32 -0500 (CDT) Received: from mailwasher-b.lanl.gov (unknown [192.16.0.25]) by mercury.ddos.com (Postfix) with ESMTP id 80D302540F for ; Wed, 28 Apr 2004 22:44:19 -0500 (CDT) Received: from mailrelay2.lanl.gov (localhost.localdomain [127.0.0.1]) by mailwasher-b.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgik022283 for ; Wed, 28 Apr 2004 21:52:42 -0600 Received: from ccs-mail.lanl.gov (localhost.localdomain [127.0.0.1]) by mailrelay2.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgp9023660; Wed, 28 Apr 2004 21:52:42 -0600 Received: from maxroach.lanl.gov (maxroach.lanl.gov [128.165.250.187]) by ccs-mail.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgwO012761; Wed, 28 Apr 2004 21:52:42 -0600 Please fix this. joshua - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAkVc9Pn9tWOqA4LMRAsmMAJ9QejlN1ieCmRIWV6p32q0ja6SLcQCgsFdB xOtNV7Ngkf0zYrJ5Q8VOe/k= =gE5n -----END PGP SIGNATURE----- From joshua at joshuawise.com Thu Apr 29 14:16:10 2004 From: joshua at joshuawise.com (Joshua Wise) Date: Thu Apr 29 14:16:10 2004 Subject: [administrivia] Broken mail servers In-Reply-To: References: Message-ID: <200404291527.58096.joshua@joshuawise.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, evan at ddos.com, it appears your mailserver is broken and is sending email that you are CC'ed to (and possibly any email that you recieve from the list) back to the list. The appropriate message headers showing me this are: Received: from nwn.definitive.org (unknown [65.242.93.132]) by joshuawise.com (Postfix on joshuawise.com) with ESMTP id 28645322A for ; Wed, 28 Apr 2004 23:59:58 -0400 (EDT) Received: from nwn.definitive.org (localhost.localdomain [127.0.0.1]) by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2cGK25945; Wed, 28 Apr 2004 22:38:16 -0400 Received: from mercury.ddos.com (mercury.ddos.com [64.5.62.66]) by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2bEK25893 for ; Wed, 28 Apr 2004 22:37:14 -0400 Received: by mercury.ddos.com (Postfix, from userid 5002) id C531A25418; Wed, 28 Apr 2004 22:44:32 -0500 (CDT) Received: from mailwasher-b.lanl.gov (unknown [192.16.0.25]) by mercury.ddos.com (Postfix) with ESMTP id 80D302540F for ; Wed, 28 Apr 2004 22:44:19 -0500 (CDT) Received: from mailrelay2.lanl.gov (localhost.localdomain [127.0.0.1]) by mailwasher-b.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgik022283 for ; Wed, 28 Apr 2004 21:52:42 -0600 Received: from ccs-mail.lanl.gov (localhost.localdomain [127.0.0.1]) by mailrelay2.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgp9023660; Wed, 28 Apr 2004 21:52:42 -0600 Received: from maxroach.lanl.gov (maxroach.lanl.gov [128.165.250.187]) by ccs-mail.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgwO012761; Wed, 28 Apr 2004 21:52:42 -0600 Please fix this. joshua - -- Joshua Wise | www.joshuawise.com GPG Key | 0xEA80E0B3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAkVc9Pn9tWOqA4LMRAsmMAJ9QejlN1ieCmRIWV6p32q0ja6SLcQCgsFdB xOtNV7Ngkf0zYrJ5Q8VOe/k= =gE5n -----END PGP SIGNATURE----- From dwh at lanl.gov Thu Apr 29 14:52:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Apr 29 14:52:01 2004 Subject: LinuxBIOS Video? In-Reply-To: Message-ID: I thought we did, I could be mistaken... I don't think I ever saw the Tyan Tachyon (Radeon 9800 Pro) come up in our lab, not even with the emulator. On Wed, 28 Apr 2004, ron minnich wrote: > On Wed, 28 Apr 2004, Hendricks David W. wrote: > > > We haven't had any success with Radeon cards in LinuxBIOS in our lab, > > though Ollie Lho might have some more information on that for you. > > oops. I didn't realize we had trouble with them. > > oh well. > > ron > From dwh at lanl.gov Thu Apr 29 14:53:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Apr 29 14:53:01 2004 Subject: LinuxBIOS Video? In-Reply-To: Message-ID: I thought we did, I could be mistaken... I don't think I ever saw the Tyan Tachyon (Radeon 9800 Pro) come up in our lab, not even with the emulator. On Wed, 28 Apr 2004, ron minnich wrote: > On Wed, 28 Apr 2004, Hendricks David W. wrote: > > > We haven't had any success with Radeon cards in LinuxBIOS in our lab, > > though Ollie Lho might have some more information on that for you. > > oops. I didn't realize we had trouble with them. > > oh well. > > ron > From dwh at lanl.gov Thu Apr 29 14:54:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Apr 29 14:54:01 2004 Subject: LinuxBIOS Video? In-Reply-To: <3174569B9743D511922F00A0C943142304B86A58@TYANWEB> Message-ID: Awesome. Are you using the Radeon's VGABIOS, init without BIOS (ATi-specific), or another method? On Wed, 28 Apr 2004, YhLu wrote: > 2. ATI randon --- At this time, you may not get the output from very > beginning. From dwh at lanl.gov Thu Apr 29 14:54:19 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Apr 29 14:54:19 2004 Subject: LinuxBIOS Video? In-Reply-To: <3174569B9743D511922F00A0C943142304B86A58@TYANWEB> Message-ID: Awesome. Are you using the Radeon's VGABIOS, init without BIOS (ATi-specific), or another method? On Wed, 28 Apr 2004, YhLu wrote: > 2. ATI randon --- At this time, you may not get the output from very > beginning. From dwh at lanl.gov Thu Apr 29 14:56:01 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Apr 29 14:56:01 2004 Subject: [administrivia] Broken mail servers In-Reply-To: <200404291527.58096.joshua@joshuawise.com> Message-ID: Maybe that's why his domain name is "ddos" :) On Thu, 29 Apr 2004, Joshua Wise wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > evan at ddos.com, it appears your mailserver is broken and is sending email that > you are CC'ed to (and possibly any email that you recieve from the list) back > to the list. > > The appropriate message headers showing me this are: > > Received: from nwn.definitive.org (unknown [65.242.93.132]) > by joshuawise.com (Postfix on joshuawise.com) with ESMTP id 28645322A > for ; Wed, 28 Apr 2004 23:59:58 -0400 (EDT) > Received: from nwn.definitive.org (localhost.localdomain [127.0.0.1]) > by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2cGK25945; > Wed, 28 Apr 2004 22:38:16 -0400 > Received: from mercury.ddos.com (mercury.ddos.com [64.5.62.66]) > by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2bEK25893 > for ; Wed, 28 Apr 2004 22:37:14 -0400 > Received: by mercury.ddos.com (Postfix, from userid 5002) > id C531A25418; Wed, 28 Apr 2004 22:44:32 -0500 (CDT) > Received: from mailwasher-b.lanl.gov (unknown [192.16.0.25]) > by mercury.ddos.com (Postfix) with ESMTP id 80D302540F > for ; Wed, 28 Apr 2004 22:44:19 -0500 (CDT) > Received: from mailrelay2.lanl.gov (localhost.localdomain [127.0.0.1]) > by mailwasher-b.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id > i3T3qgik022283 > for ; Wed, 28 Apr 2004 21:52:42 -0600 > Received: from ccs-mail.lanl.gov (localhost.localdomain [127.0.0.1]) > by mailrelay2.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id > i3T3qgp9023660; > Wed, 28 Apr 2004 21:52:42 -0600 > Received: from maxroach.lanl.gov (maxroach.lanl.gov [128.165.250.187]) > by ccs-mail.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgwO012761; > Wed, 28 Apr 2004 21:52:42 -0600 > > Please fix this. > joshua > > > - -- > Joshua Wise | www.joshuawise.com > GPG Key | 0xEA80E0B3 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) > > iD8DBQFAkVc9Pn9tWOqA4LMRAsmMAJ9QejlN1ieCmRIWV6p32q0ja6SLcQCgsFdB > xOtNV7Ngkf0zYrJ5Q8VOe/k= > =gE5n > -----END PGP SIGNATURE----- > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From dwh at lanl.gov Thu Apr 29 14:56:20 2004 From: dwh at lanl.gov (Hendricks David W.) Date: Thu Apr 29 14:56:20 2004 Subject: [administrivia] Broken mail servers In-Reply-To: <200404291527.58096.joshua@joshuawise.com> Message-ID: Maybe that's why his domain name is "ddos" :) On Thu, 29 Apr 2004, Joshua Wise wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > evan at ddos.com, it appears your mailserver is broken and is sending email that > you are CC'ed to (and possibly any email that you recieve from the list) back > to the list. > > The appropriate message headers showing me this are: > > Received: from nwn.definitive.org (unknown [65.242.93.132]) > by joshuawise.com (Postfix on joshuawise.com) with ESMTP id 28645322A > for ; Wed, 28 Apr 2004 23:59:58 -0400 (EDT) > Received: from nwn.definitive.org (localhost.localdomain [127.0.0.1]) > by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2cGK25945; > Wed, 28 Apr 2004 22:38:16 -0400 > Received: from mercury.ddos.com (mercury.ddos.com [64.5.62.66]) > by nwn.definitive.org (8.11.6/8.11.6) with ESMTP id i3T2bEK25893 > for ; Wed, 28 Apr 2004 22:37:14 -0400 > Received: by mercury.ddos.com (Postfix, from userid 5002) > id C531A25418; Wed, 28 Apr 2004 22:44:32 -0500 (CDT) > Received: from mailwasher-b.lanl.gov (unknown [192.16.0.25]) > by mercury.ddos.com (Postfix) with ESMTP id 80D302540F > for ; Wed, 28 Apr 2004 22:44:19 -0500 (CDT) > Received: from mailrelay2.lanl.gov (localhost.localdomain [127.0.0.1]) > by mailwasher-b.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id > i3T3qgik022283 > for ; Wed, 28 Apr 2004 21:52:42 -0600 > Received: from ccs-mail.lanl.gov (localhost.localdomain [127.0.0.1]) > by mailrelay2.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id > i3T3qgp9023660; > Wed, 28 Apr 2004 21:52:42 -0600 > Received: from maxroach.lanl.gov (maxroach.lanl.gov [128.165.250.187]) > by ccs-mail.lanl.gov (8.12.10/8.12.10/(ccn-5)) with ESMTP id i3T3qgwO012761; > Wed, 28 Apr 2004 21:52:42 -0600 > > Please fix this. > joshua > > > - -- > Joshua Wise | www.joshuawise.com > GPG Key | 0xEA80E0B3 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) > > iD8DBQFAkVc9Pn9tWOqA4LMRAsmMAJ9QejlN1ieCmRIWV6p32q0ja6SLcQCgsFdB > xOtNV7Ngkf0zYrJ5Q8VOe/k= > =gE5n > -----END PGP SIGNATURE----- > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From ollie at lanl.gov Thu Apr 29 14:57:00 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Apr 29 14:57:00 2004 Subject: LinuxBIOS Video? In-Reply-To: References: Message-ID: <1083269559.18413.52.camel@exponential.lanl.gov> On Thu, 2004-04-29 at 14:07, Hendricks David W. wrote: > I thought we did, I could be mistaken... I don't think I ever saw the > Tyan Tachyon (Radeon 9800 Pro) come up in our lab, not even with the > emulator. > Last time I check, the ATI vgabios wanted to install int 0x10 handler and call into itself via int 0x10. The emulator can't do this yet. Ollie From ollie at lanl.gov Thu Apr 29 14:57:13 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Apr 29 14:57:13 2004 Subject: LinuxBIOS Video? In-Reply-To: References: Message-ID: <1083269559.18413.52.camel@exponential.lanl.gov> On Thu, 2004-04-29 at 14:07, Hendricks David W. wrote: > I thought we did, I could be mistaken... I don't think I ever saw the > Tyan Tachyon (Radeon 9800 Pro) come up in our lab, not even with the > emulator. > Last time I check, the ATI vgabios wanted to install int 0x10 handler and call into itself via int 0x10. The emulator can't do this yet. Ollie From evan at ddos.com Thu Apr 29 15:00:00 2004 From: evan at ddos.com (Langlois Evan) Date: Thu Apr 29 15:00:00 2004 Subject: [administrivia] Broken mail servers In-Reply-To: References: <200404291527.58096.joshua@joshuawise.com> Message-ID: <2425.68.92.26.41.1083269222.squirrel@mercury.ddos.com> > Maybe that's why his domain name is "ddos" :) Its because of some bad integration between the mail server and an inhouse spam removal system. I'm going to rewrite it this weekend during our other upgrades. From ollie at lanl.gov Thu Apr 29 15:13:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Thu Apr 29 15:13:01 2004 Subject: Enable v.s. Enabled Message-ID: <1083270501.18413.57.camel@exponential.lanl.gov> Hi, I changed the device:enable and chip_device_path::enable to device:enabled and chip_device_path::enabled because they are acutally verbs describe the status of the devices. I also change all the affected code I can find, there should be no problems except you have to re-run the config tool. Ollie From rminnich at lanl.gov Thu Apr 29 16:30:00 2004 From: rminnich at lanl.gov (ron minnich) Date: Thu Apr 29 16:30:00 2004 Subject: LinuxBIOS Video? In-Reply-To: <1083269559.18413.52.camel@exponential.lanl.gov> Message-ID: On Thu, 29 Apr 2004, Li-Ta Lo wrote: > Last time I check, the ATI vgabios wanted to install int 0x10 handler > and call into itself via int 0x10. The emulator can't do this yet. Right, I had forgotten this problem. Silly VGA BIOS. ron From aphthong at sizzard.com Thu Apr 29 16:55:00 2004 From: aphthong at sizzard.com (aphthong at sizzard.com) Date: Thu Apr 29 16:55:00 2004 Subject: LinuxBIOS Video? In-Reply-To: References: <1083269559.18413.52.camel@exponential.lanl.gov> Message-ID: <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> So has anyone gotten an ATI video card to work without the emulation BIOS? Jordan At 02:45 PM 4/29/2004, ron minnich wrote: >On Thu, 29 Apr 2004, Li-Ta Lo wrote: > > > Last time I check, the ATI vgabios wanted to install int 0x10 handler > > and call into itself via int 0x10. The emulator can't do this yet. > >Right, I had forgotten this problem. > >Silly VGA BIOS. > >ron > >_______________________________________________ >Linuxbios mailing list >Linuxbios at clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios From gwatson at lanl.gov Thu Apr 29 17:59:01 2004 From: gwatson at lanl.gov (Greg Watson) Date: Thu Apr 29 17:59:01 2004 Subject: Enable v.s. Enabled In-Reply-To: <1083270501.18413.57.camel@exponential.lanl.gov> References: <1083270501.18413.57.camel@exponential.lanl.gov> Message-ID: Was it annoying you or something :-) Greg On 29/04/2004, at 2:28 PM, Li-Ta Lo wrote: > Hi, > > I changed the device:enable and chip_device_path::enable to > device:enabled and chip_device_path::enabled because they > are acutally verbs describe the status of the devices. > I also change all the affected code I can find, there should > be no problems except you have to re-run the config tool. > > Ollie > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios at clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > From stepan at openbios.org Fri Apr 30 06:40:01 2004 From: stepan at openbios.org (Stefan Reinauer) Date: Fri Apr 30 06:40:01 2004 Subject: LinuxBIOS Video? In-Reply-To: <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> References: <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> Message-ID: <20040430115835.GA8581@openbios.org> * aphthong at sizzard.com [040430 00:09]: > So has anyone gotten an ATI video card to work without the emulation BIOS? Yes, RageXL works with the appropriate patches. Stefan From rsmith at bitworks.com Fri Apr 30 09:34:01 2004 From: rsmith at bitworks.com (Richard Smith) Date: Fri Apr 30 09:34:01 2004 Subject: LinuxBIOS Video? In-Reply-To: <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> References: <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> Message-ID: <4092676B.5020100@bitworks.com> aphthong at sizzard.com wrote: > So has anyone gotten an ATI video card to work without the emulation BIOS? I'm working on an Rage Mobility M1 right now. Yesterday I finshed porting some old GX DOS init code from thier developemnet site over to linux and I'm just about to start messing with figureing out the register differences between a GX and an M1. Although they are both Mach64 based the M1 seems to have different address for things. This dosen't really help most people though as the Mobility M1 only found in laptops, embedded setups, or custom boards like ours. You won't find a general purpose video card with an M1 on it and I don't know of any non-laptop moterboards with one. From aphthong at sizzard.com Fri Apr 30 09:48:01 2004 From: aphthong at sizzard.com (aphthong at sizzard.com) Date: Fri Apr 30 09:48:01 2004 Subject: LinuxBIOS Video? In-Reply-To: <4092676B.5020100@bitworks.com> References: <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> Message-ID: <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> Well, it's good to know that someone got it working. I'm currently doing it for a Radeon 9000 chip. At 09:49 AM 4/30/2004 -0500, Richard Smith wrote: >aphthong at sizzard.com wrote: > >>So has anyone gotten an ATI video card to work without the emulation BIOS? > >I'm working on an Rage Mobility M1 right now. Yesterday I finshed porting >some old GX DOS init code from thier developemnet site over to linux and >I'm just about to start messing with figureing out the register >differences between a GX and an M1. Although they are both Mach64 based >the M1 seems to have different address for things. > >This dosen't really help most people though as the Mobility M1 only found >in laptops, embedded setups, or custom boards like ours. You won't find a >general purpose video card with an M1 on it and I don't know of any >non-laptop moterboards with one. > > >_______________________________________________ >Linuxbios mailing list >Linuxbios at clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios From rsmith at bitworks.com Fri Apr 30 10:04:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Fri Apr 30 10:04:00 2004 Subject: LinuxBIOS Video? In-Reply-To: <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> References: <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> Message-ID: <40926E6A.9040404@bitworks.com> aphthong at sizzard.com wrote: > Well, it's good to know that someone got it working. > > I'm currently doing it for a Radeon 9000 chip. So you have gone through all the NDA agreements to get access to the dev site? If so perhaps we should try to coordinate? Of course the Radeon 9000 may be completely different since its based on a different core isn't it? Are they going to let you release your code GPL? From aphthong at sizzard.com Fri Apr 30 10:34:01 2004 From: aphthong at sizzard.com (aphthong at sizzard.com) Date: Fri Apr 30 10:34:01 2004 Subject: LinuxBIOS Video? In-Reply-To: <40926E6A.9040404@bitworks.com> References: <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> Message-ID: <5.2.1.1.2.20040430084510.02cf5a68@mail.sizzard.com> Yeah, I am getting access to ATI info. Because of the NDA I don't know how much I can release through GPL. My second problem there is that the linuxbios2 tree has drifted enough that it may be too much of a pain to sync back up. Also a pain since I have a new Northbridge/Southbridge. I'm willing to coordinate to the limitations of the NDA, so I'll check out how far I can go. The chip is different, but most of the time the designs are just derivative, so I would expect them to be close. Jordan At 10:19 AM 4/30/2004 -0500, Richard Smith wrote: >aphthong at sizzard.com wrote: > >>Well, it's good to know that someone got it working. >>I'm currently doing it for a Radeon 9000 chip. > >So you have gone through all the NDA agreements to get access to the dev site? > >If so perhaps we should try to coordinate? Of course the Radeon 9000 may >be completely different since its based on a different core isn't it? > >Are they going to let you release your code GPL? > > From ollie at lanl.gov Fri Apr 30 10:48:01 2004 From: ollie at lanl.gov (Li-Ta Lo) Date: Fri Apr 30 10:48:01 2004 Subject: Enable v.s. Enabled In-Reply-To: References: <1083270501.18413.57.camel@exponential.lanl.gov> Message-ID: <1083341021.18413.61.camel@exponential.lanl.gov> On Thu, 2004-04-29 at 17:14, Greg Watson wrote: > Was it annoying you or something :-) > Yea, I can't tell from the variable name if it is a function or just a boolean. Ollie > Greg > > On 29/04/2004, at 2:28 PM, Li-Ta Lo wrote: > > > Hi, > > > > I changed the device:enable and chip_device_path::enable to > > device:enabled and chip_device_path::enabled because they > > are acutally verbs describe the status of the devices. > > I also change all the affected code I can find, there should > > be no problems except you have to re-run the config tool. > > > > Ollie > > > > > > > > _______________________________________________ > > Linuxbios mailing list > > Linuxbios at clustermatic.org > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > > From rsmith at bitworks.com Fri Apr 30 10:49:00 2004 From: rsmith at bitworks.com (Richard Smith) Date: Fri Apr 30 10:49:00 2004 Subject: LinuxBIOS Video? In-Reply-To: <5.2.1.1.2.20040430084510.02cf5a68@mail.sizzard.com> References: <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> <5.2.1.1.2.20040430084510.02cf5a68@mail.sizzard.com> Message-ID: <409278D7.506@bitworks.com> aphthong at sizzard.com wrote: > Yeah, I am getting access to ATI info. Because of the NDA I don't know > how much I can release through GPL. My second problem there is that the > linuxbios2 tree has drifted enough that it may be too much of a pain to Ask and see. I asked and got full permission to release any code I generate under GPL. I'm working with v1. The 440bx tree hasn't been ported. Well right now its not even linuxbios. My board boots linux bios but I'm running user space app from a serial console. Perhaps we can compare notes once both of us get something working. From aphthong at sizzard.com Fri Apr 30 13:24:01 2004 From: aphthong at sizzard.com (aphthong at sizzard.com) Date: Fri Apr 30 13:24:01 2004 Subject: LinuxBIOS Video? In-Reply-To: <409278D7.506@bitworks.com> References: <5.2.1.1.2.20040430084510.02cf5a68@mail.sizzard.com> <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <1083269559.18413.52.camel@exponential.lanl.gov> <5.2.1.1.2.20040429150802.00b2dba0@mail.sizzard.com> <5.2.1.1.2.20040430080211.02cfa248@mail.sizzard.com> <5.2.1.1.2.20040430084510.02cf5a68@mail.sizzard.com> Message-ID: <5.2.1.1.2.20040430113521.00bbca80@mail.sizzard.com> I would recommend the newer tree. It's still pretty cryptic, but much cleaner than the old tree. It took me about three weeks to get a new NB/SB up and running. But I had to deal with hardware that was being debugged at the same time. I'll let you know when I get it up and running. Jordan At 09:03 AM 4/30/2004, Richard Smith wrote: >aphthong at sizzard.com wrote: > >>Yeah, I am getting access to ATI info. Because of the NDA I don't know >>how much I can release through GPL. My second problem there is that the >>linuxbios2 tree has drifted enough that it may be too much of a pain to > >Ask and see. I asked and got full permission to release any code I >generate under GPL. > >I'm working with v1. The 440bx tree hasn't been ported. Well right now >its not even linuxbios. My board boots linux bios but I'm running user >space app from a serial console. > >Perhaps we can compare notes once both of us get something working. > > >_______________________________________________ >Linuxbios mailing list >Linuxbios at clustermatic.org >http://www.clustermatic.org/mailman/listinfo/linuxbios