coreboot October 2003

coreboot@coreboot.org

52 participants
115 discussions

help, about the rom size of LinuxBIOS.
by bendany 16 Oct '03

16 Oct '03

hi,all. My mb is EPIA M800, and I got some 1Mb flash chips. I can compile LinuxBIOS+VGABIOS+FILO, got a 256kbytes rom. but when I change config file , to make it fit in 1Mb flash, I got a 196kbytes rom. I think the size of linuxbios, filo, and vgabios(which is 48kbyte) can fit into 128kbyte flash rom. so how can I make it? here is my wrong config: ========================================================= # # LinuxBIOS config file for: VIA epia mini-itx # target build # via epia mainboard via/epia # Enable Serial Console for debugging option SERIAL_CONSOLE=1 option TTYS0_BAUD=115200 option DEFAULT_CONSOLE_LOGLEVEL=9 option DEBUG=1 # Use 256KB Standard Flash as Normal BIOS option RAMTEST=1 option USE_GENERIC_ROM=1 option STD_FLASH=1 #option ZKERNEL_START=0xfffc0000 option ROM_SIZE=131072 # payload size = 192KB option PAYLOAD_SIZE=98304 # use ELF Loader to load Etherboot option USE_ELF_BOOT=1 option VGABIOS_START=0xfffc0000 option ZKERNEL_START=0xfffcc000 option HAVE_FRAMEBUFFER=1 option SMA_SIZE=8 option CONFIG_VGABIOS=1 option CONFIG_REALMODE_IDT=1 option CONFIG_PCIBIOS=1 dir src/bioscall # Use FILO,VGABIOS as payload payload ../payload.bin addaction romimage /bin/cp -f romimage $(HOME)/linuxbios_epia.bin ======================================================== Best Reguards. Ben.

3 2

Solo tests with 1.1.5 fail
by Stefan Reinauer 16 Oct '03

16 Oct '03

Hi, I get reboots again, this time it's not dependent on the gcc version I use.. Eric, there are some weird bits in the attached log, can you help to interpret them? From what I see some the SuperIO setup has severe trouble, and some of the resources seem to be given out twice... Stefan -- Architecture Team SuSE Linux AG

1 2

RE: Linuxbios digest, Vol 1 #637 - 4 msgs
by Phil Wilkins 16 Oct '03

16 Oct '03

Huge apologies guys, I appear to have mailed the entire digest back to the list by accident... Sorry again :) Phil. ============================================================================== For more information on Hargreaves Lansdown, visit our web site http://www.hargreaveslansdown.co.uk IMPORTANT NOTICE This email is intended solely for the recipient and is confidential and not for third party unauthorised distribution. If an addressing, or transmission, error has misdirected this email, please notify the author by replying to this email or notifying the system manager (internal.security(a)hargreaveslansdown.co.uk) if you are not the intended recipient you must not disclose, distribute, copy, print or rely on this email. Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of Hargreaves Lansdown. In addition, staff are not authorised to enter into any contract through email and therefore nothing contained herein should be construed as such. This email has been prepared using information believed by the author to be reliable and accurate but Hargreaves Lansdown makes no warranty as to the accuracy or completeness. In particular, Hargreaves Lansdown does not accept responsibility for any changes made to this email after it was sent. All group companies are Authorised and regulated by the Financial Services Authority and registered in England and the registered office is Kendal House, 4 Brighton Mews, Clifton, Bristol, BS8 2NX. Telephone: 0117 9889880 ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________

1 0

bus allocation
by Stefan Reinauer 16 Oct '03

16 Oct '03

Hi, the bus allocation is currently very different from what older LinuxBIOS trees and Phoenix/Award BIOS do. One obvious change is that Bus 0 has no devices except the CPUs, bus 1 contains the 8151/8131 and 8111, bus2 the pci/agp bus behind the bridge on bus1 etc. I wonder whether this can cause trouble. Does hardware expect the bus to be arranged in a certain way? i.e. all 8111 devices before the agp bus or similar? I found that the solo dies right before it should do PNP SuperIO enumeration: hdama.log: PCI: pci_scan_bus for bus 4 PCI: 04:00.0 [1022/7464] ops PCI: 04:00.0 [1022/7464] enabled PCI: 04:00.1 [1022/7464] ops PCI: 04:00.1 [1022/7464] enabled PCI: 04:00.2 [1022/7463] ops PCI: 04:00.2 [1022/7463] enabled amd8111_enable dev: PCI: 04:01.0 lpc_dev: PCI: 01:04.0 index: 9 reg: ff9f -> fd9f done PCI: 04:01.0 [ffff/ffff] disabled PCI: 04:06.0 [1002/4752] enabled PCI: pci_scan_bus returning with max=04 PNP: 002e.0 enabled PNP: 002e.1 enabled PNP: 002e.2 enabled PNP: 002e.3 enabled solo.log: PCI: pci_scan_bus for bus 3 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 amd8111_enable dev: PCI: 03:01.0 lpc_dev: PCI: 01:05.0 index: 9 reg: ff9f -> fd9f done PCI: 03:01.0 [ffff/ffff] disabled PCI: 03:05.0 [10b7/9200] enabled Copying LinuxBIOS to ram. Jumping to LinuxBIOS. LinuxBIOS-1.1.5.0-Fallback Mi Okt 15 15:30:52 CEST 2003 rebooting... <hang> Stefan -- ARCHITECTURE TEAM SUSE LINUX AG

1 1

RE: Linuxbios digest, Vol 1 #636 - 9 msgs
by Phil Wilkins 16 Oct '03

16 Oct '03

-----Original Message----- From: linuxbios-request(a)clustermatic.org [mailto:linuxbios-request@clustermatic.org] Sent: 16 October 2003 09:51 To: linuxbios(a)clustermatic.org Subject: Linuxbios digest, Vol 1 #636 - 9 msgs Send Linuxbios mailing list submissions to linuxbios(a)clustermatic.org To subscribe or unsubscribe via the World Wide Web, visit http://www.clustermatic.org/mailman/listinfo/linuxbios or, via email, send a message with subject or body 'help' to linuxbios-request(a)clustermatic.org You can reach the person managing the list at linuxbios-admin(a)clustermatic.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Linuxbios digest..." Today's Topics: 1. Re: Number of resets in 1.1.5 (YhLu) 2. Re: Number of resets in 1.1.5 (Eric W. Biederman) 3. Re: Number of resets in 1.1.5 (Eric W. Biederman) 4. Re: FILO 0.4 (SONE Takeshi) 5. Re: FILO 0.4 (Ronald G. Minnich) 6. Re: LinuxBIOS + FILO boots RedHat 9 CD-ROM (SONE Takeshi) 7. help, about the rom size of LinuxBIOS. (bendany) 8. Re: help, about the rom size of LinuxBIOS. (SONE Takeshi) 9. (fwd) Re: Epox Boards [sachse(a)gmx.net] (Stefan Reinauer) --__--__-- Message: 1 From: YhLu <YhLu(a)tyan.com> To: Stefan Reinauer <stepan(a)suse.de>, linuxbios(a)clustermatic.org Subject: Re: Number of resets in 1.1.5 Date: Wed, 15 Oct 2003 09:54:13 -0700 Stephan, The code seems already only reset once in the misc_control.c. Other reset may be caused by other reasons. Regards YH. -----ÓÊ¼þÔ¼þ----- ·¢¼þÈË: Stefan Reinauer [mailto:stepan@suse.de] ·¢ËÍÊ±¼ä: 2003Äê10ÔÂ15ÈÕ 4:51 ÊÕ¼þÈË: linuxbios(a)clustermatic.org Ö÷Ìâ: Number of resets in 1.1.5 Hi, LinuxBIOS 1.1.5 currently does a couple of resets on the HDAMA before it actually boots the payload. Is this elementary for getting HT to work properly, or is it based on the current algorithm? To keep boot times as short as possible, it'd be better to only do one reset and gather all setup functions that need reset before that. Stefan -- Architecture Team SuSE Linux AG _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios --__--__-- Message: 2 To: Stefan Reinauer <stepan(a)suse.de> Cc: linuxbios(a)clustermatic.org Subject: Re: Number of resets in 1.1.5 From: ebiederman(a)lnxi.com (Eric W. Biederman) Date: 15 Oct 2003 11:33:39 -0600 Stefan Reinauer <stepan(a)suse.de> writes: > Hi, > > LinuxBIOS 1.1.5 currently does a couple of resets on the HDAMA before > it actually boots the payload. Is this elementary for getting HT to > work properly, or is it based on the current algorithm? A reset is necessary for the change in settings to take effect. The current algorithm is stupid and makes all of those decisions locally. > To keep boot times as > short as possible, it'd be better to only do one reset and gather all > setup functions that need reset before that. Right. I am not quite certain what the most maintainable technique really is. I am tempted to put off initializing most of RAM until someplace in the main body of the code, and have a variable I can set to tell the code I would like to do a reset. Mostly I figured make it work properly today. Optimize it tomorrow. Eric --__--__-- Message: 3 To: YhLu <YhLu(a)tyan.com> Cc: Stefan Reinauer <stepan(a)suse.de>, linuxbios(a)clustermatic.org Subject: Re: Number of resets in 1.1.5 From: ebiederman(a)lnxi.com (Eric W. Biederman) Date: 15 Oct 2003 11:34:15 -0600 YhLu <YhLu(a)tyan.com> writes: > Stephan, > > The code seems already only reset once in the misc_control.c. Other > reset may be caused by other reasons. There are also resets from hypertransport.c to get the link speed set properly. Eric --__--__-- Message: 4 Date: Thu, 16 Oct 2003 03:48:43 +0900 To: Andrew Ip <aip(a)cwlinux.com> Cc: linuxbios(a)clustermatic.org Subject: Re: FILO 0.4 From: SONE Takeshi <ts1(a)tsn.or.jp> On Wed, Oct 15, 2003 at 09:50:56PM +0800, Andrew Ip wrote: > > It can boot distro CDs if you give a proper command line. SuSE 8.2 > > LiveEval CD worked without a glitch, I enjoyed the KDE desktop, > > OpenOffice, etc, from the CD on an EPIA booted from LinuxBIOS. > Wonder full. Does X work? Yes, X works if VGABIOS is used. > > I tried to configure EPIA (V1) code to use native mode, > > and the ports read something not 0xff, but the drive doesn't respond > > to soft reset. I don't know the bug is in FILO, LinuxBIOS, or the > > hardware. > IIRC, EPIA has to use compatible mode; otherwise, system will have > problem with IRQ. I don't use IRQ. According to the comment in the southbridge code, it has speed problem when native mode. I took that it does work in native mode.. -- Takeshi --__--__-- Message: 5 Date: Wed, 15 Oct 2003 13:06:06 -0600 (MDT) From: "Ronald G. Minnich" <rminnich(a)lanl.gov> To: Andrew Ip <aip(a)cwlinux.com> cc: SONE Takeshi <ts1(a)tsn.or.jp>, <linuxbios(a)clustermatic.org> Subject: Re: FILO 0.4 On Wed, 15 Oct 2003, Andrew Ip wrote: > > PCI support in IDE driver is also added (or recovered), but the > > native PCI mode is not fully tested. I tried to configure EPIA (V1) > > code to use native mode, and the ports read something not 0xff, but > > the drive doesn't respond to soft reset. I always had trouble with the 8231 native mode 3 years ago. I ended up giving up and always using compatibility mode. I will try to fix compat. mode in v2. ron --__--__-- Message: 6 Date: Thu, 16 Oct 2003 04:37:55 +0900 To: linuxbios(a)clustermatic.org Subject: Re: LinuxBIOS + FILO boots RedHat 9 CD-ROM From: SONE Takeshi <ts1(a)tsn.or.jp> On Sun, Oct 12, 2003 at 04:42:35AM +0900, SONE Takeshi wrote: > Before RedHat I tried KNOPPIX 3.3. It uses El Torito floppy emulation > and I already added the code to mount the El Torito floppy image. It > boots, but hangs during the device detection phase I think. I succeeded to boot KNOPPIX 3.3 with this FILO command line: boot: hdc1:/vmlinuz initrd=hdc1:/miniroot.gz noagp noapic These options skip some parts of auto-detection. -- Takeshi --__--__-- Message: 7 From: "bendany" <bendany(a)mistdl.com> To: <linuxbios(a)clustermatic.org> Subject: help, about the rom size of LinuxBIOS. Date: Thu, 16 Oct 2003 10:28:58 +0800 hi,all. My mb is EPIA M800, and I got some 1Mb flash chips. I can compile LinuxBIOS+VGABIOS+FILO, got a 256kbytes rom. but when I change config file , to make it fit in 1Mb flash, I got a 196kbytes rom. I think the size of linuxbios, filo, and vgabios(which is 48kbyte) can fit into 128kbyte flash rom. so how can I make it? here is my wrong config: ========================================================= # # LinuxBIOS config file for: VIA epia mini-itx # target build # via epia mainboard via/epia # Enable Serial Console for debugging option SERIAL_CONSOLE=1 option TTYS0_BAUD=115200 option DEFAULT_CONSOLE_LOGLEVEL=9 option DEBUG=1 # Use 256KB Standard Flash as Normal BIOS option RAMTEST=1 option USE_GENERIC_ROM=1 option STD_FLASH=1 #option ZKERNEL_START=0xfffc0000 option ROM_SIZE=131072 # payload size = 192KB option PAYLOAD_SIZE=98304 # use ELF Loader to load Etherboot option USE_ELF_BOOT=1 option VGABIOS_START=0xfffc0000 option ZKERNEL_START=0xfffcc000 option HAVE_FRAMEBUFFER=1 option SMA_SIZE=8 option CONFIG_VGABIOS=1 option CONFIG_REALMODE_IDT=1 option CONFIG_PCIBIOS=1 dir src/bioscall # Use FILO,VGABIOS as payload payload ../payload.bin addaction romimage /bin/cp -f romimage $(HOME)/linuxbios_epia.bin ======================================================== Best Reguards. Ben. --__--__-- Message: 8 Date: Thu, 16 Oct 2003 16:30:22 +0900 To: bendany <bendany(a)mistdl.com> Cc: linuxbios(a)clustermatic.org Subject: Re: help, about the rom size of LinuxBIOS. From: SONE Takeshi <ts1(a)cma.co.jp> On Thu, Oct 16, 2003 at 10:28:58AM +0800, bendany wrote: > My mb is EPIA M800, and I got some 1Mb flash chips. > I can compile LinuxBIOS+VGABIOS+FILO, got a 256kbytes rom. > but when I change config file , to make it fit in 1Mb flash, > I got a 196kbytes rom. > I think the size of linuxbios, filo, and vgabios(which is 48kbyte) > can fit into 128kbyte flash rom. so how can I make it? I guess you have to specify the size of LinuxBIOS itself. (maybe ROM_IMAGE_SIZE?) By default it is 64KB. -- Takeshi --__--__-- Message: 9 Date: Thu, 16 Oct 2003 11:18:35 +0200 From: Stefan Reinauer <stepan(a)suse.de> To: linuxbios(a)clustermatic.org Subject: (fwd) Re: Epox Boards [sachse(a)gmx.net] Does anyone know whether these work? ----- Forwarded message from Mark-Andres Hohm <sachse(a)gmx.net> ----- Date: Wed, 15 Oct 2003 19:48:34 +0200 From: Mark-Andres Hohm <sachse(a)gmx.net> To: Stefan Reinauer <stepan(a)suse.de> Subject: Re: Epox Boards ============================================================================== For more information on Hargreaves Lansdown, visit our web site http://www.hargreaveslansdown.co.uk IMPORTANT NOTICE This email is intended solely for the recipient and is confidential and not for third party unauthorised distribution. If an addressing, or transmission, error has misdirected this email, please notify the author by replying to this email or notifying the system manager (internal.security(a)hargreaveslansdown.co.uk) if you are not the intended recipient you must not disclose, distribute, copy, print or rely on this email. Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of Hargreaves Lansdown. In addition, staff are not authorised to enter into any contract through email and therefore nothing contained herein should be construed as such. This email has been prepared using information believed by the author to be reliable and accurate but Hargreaves Lansdown makes no warranty as to the accuracy or completeness. In particular, Hargreaves Lansdown does not accept responsibility for any changes made to this email after it was sent. All group companies are Authorised and regulated by the Financial Services Authority and registered in England and the registered office is Kendal House, 4 Brighton Mews, Clifton, Bristol, BS8 2NX. Telephone: 0117 9889880 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefan Reinauer wrote: | * Mark-Andres Hohm <sachse(a)gmx.net> [031013 20:59]: | |>-----BEGIN PGP SIGNED MESSAGE----- |>Hash: SHA1 |> |>Have anyone expirience with Epox board and linuxbios? | | | _Which_ Epox board? Can you send lspci -vvv? | | Stefan here are the lspci from the epox kta3pro this have to work with linux and win 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03) ~ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- ~ Latency: 8 ~ Region 0: Memory at d0000000 (32-bit, prefetchable) [size=32M] ~ Capabilities: [a0] AGP version 2.0 ~ Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2,x4 ~ Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none> ~ Capabilities: [c0] 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- 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (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- <TAbort- <MAbort+ >SERR- <PERR- ~ Latency: 0 ~ Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 ~ I/O behind bridge: 0000f000-00000fff ~ Memory behind bridge: d4000000-d5ffffff ~ Prefetchable memory behind bridge: d2000000-d3ffffff ~ BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- ~ Capabilities: [80] 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- 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) ~ Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 0 ~ Capabilities: [c0] 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- 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) ~ Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 ~ Region 4: I/O ports at 9000 [size=16] ~ Capabilities: [c0] 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- 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 16) (prog-if 00 [UHCI]) ~ Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32, cache line size 08 ~ Interrupt: pin D routed to IRQ 11 ~ Region 4: I/O ports at 9400 [size=32] ~ Capabilities: [80] 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- 00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) ~ Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] ~ Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Interrupt: pin ? routed to IRQ 9 ~ Capabilities: [68] 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- 00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50) ~ Subsystem: VIA Technologies, Inc. Onboard Audio on EP7KXA ~ Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Interrupt: pin C routed to IRQ 5 ~ Region 0: I/O ports at 9c00 [size=256] ~ Region 1: I/O ports at a000 [size=4] ~ Region 2: I/O ports at a400 [size=4] ~ Capabilities: [c0] 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- 00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) ~ Subsystem: Allied Telesyn International AT-2500TX/ACPI ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 (8000ns min, 16000ns max) ~ Interrupt: pin A routed to IRQ 10 ~ Region 0: I/O ports at a800 [size=256] ~ Region 1: Memory at d7001000 (32-bit, non-prefetchable) [size=256] ~ Capabilities: [50] Power Management version 1 ~ Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) ~ Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:0b.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U ~ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 (2000ns min, 2000ns max), cache line size 08 ~ Interrupt: pin A routed to IRQ 11 ~ Region 0: I/O ports at ac00 [disabled] [size=256] ~ Region 1: Memory at d7000000 (32-bit, non-prefetchable) [size=4K] ~ Expansion ROM at <unassigned> [disabled] [size=64K] 00:0e.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 04) ~ Subsystem: Triones Technologies, Inc. HPT370A ~ Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 120 (2000ns min, 2000ns max) ~ Interrupt: pin A routed to IRQ 10 ~ Region 0: I/O ports at b000 [size=8] ~ Region 1: I/O ports at b400 [size=4] ~ Region 2: I/O ports at b800 [size=8] ~ Region 3: I/O ports at bc00 [size=4] ~ Region 4: I/O ports at c000 [size=256] ~ Expansion ROM at <unassigned> [disabled] [size=128K] ~ Capabilities: [60] 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- 01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) (prog-if 00 [VGA]) ~ Subsystem: CardExpert Technology: Unknown device 0000 ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 (1250ns min, 250ns max) ~ Interrupt: pin A routed to IRQ 12 ~ Region 0: Memory at d4000000 (32-bit, non-prefetchable) [size=16M] ~ Region 1: Memory at d2000000 (32-bit, prefetchable) [size=32M] ~ Expansion ROM at <unassigned> [disabled] [size=64K] ~ Capabilities: [60] Power Management version 1 ~ Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) ~ Status: D0 PME-Enable- DSel=0 DScale=0 PME- ~ Capabilities: [44] AGP version 2.0 ~ Status: RQ=31 SBA- 64bit- FW- Rate=x1,x2,x4 ~ Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none> - ---------------------------------------------------------------------------- ----- here are the log from my 2nd board which is only wors with linux because ist the router. its a epox 8k9a. 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge ~ Subsystem: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge ~ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- ~ Latency: 8 ~ Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M] ~ Capabilities: [a0] AGP version 2.0 ~ Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2,x4 ~ Command: RQ=31 SBA- AGP- 64bit- FW- Rate=<none> ~ Capabilities: [c0] 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- 00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (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- <TAbort- <MAbort+ >SERR- <PERR- ~ Latency: 0 ~ Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 ~ I/O behind bridge: 00009000-00009fff ~ Memory behind bridge: dc000000-ddffffff ~ Prefetchable memory behind bridge: d8000000-dbffffff ~ BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- ~ Capabilities: [80] 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- 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) ~ Subsystem: Realtek Semiconductor Co., Ltd. RT8139 ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 (8000ns min, 16000ns max) ~ Interrupt: pin A routed to IRQ 19 ~ Region 0: I/O ports at a000 [size=256] ~ Region 1: Memory at df001000 (32-bit, non-prefetchable) [size=256] 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) ~ Subsystem: Realtek Semiconductor Co., Ltd. RT8139 ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 (8000ns min, 16000ns max) ~ Interrupt: pin A routed to IRQ 19 ~ Region 0: I/O ports at a400 [size=256] ~ Region 1: Memory at df000000 (32-bit, non-prefetchable) [size=256] 00:0e.0 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07) ~ Subsystem: Triones Technologies, Inc.: Unknown device 0001 ~ Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 120 (2000ns min, 2000ns max) ~ Interrupt: pin A routed to IRQ 17 ~ Region 0: I/O ports at a800 [size=8] ~ Region 1: I/O ports at ac00 [size=4] ~ Region 2: I/O ports at b000 [size=8] ~ Region 3: I/O ports at b400 [size=4] ~ Region 4: I/O ports at b800 [size=256] ~ Expansion ROM at <unassigned> [disabled] [size=128K] ~ Capabilities: [60] 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- 00:0e.1 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07) ~ Subsystem: Triones Technologies, Inc.: Unknown device 0001 ~ Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 120 (2000ns min, 2000ns max) ~ Interrupt: pin A routed to IRQ 17 ~ Region 0: I/O ports at bc00 [size=8] ~ Region 1: I/O ports at c000 [size=4] ~ Region 2: I/O ports at c400 [size=8] ~ Region 3: I/O ports at c800 [size=4] ~ Region 4: I/O ports at cc00 [size=256] ~ Capabilities: [60] 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- 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge ~ Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 0 ~ Capabilities: [c0] 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- 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) ~ Subsystem: Unknown device 1695:3005 ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 ~ Interrupt: pin A routed to IRQ 255 ~ Region 4: I/O ports at dc00 [size=16] ~ Capabilities: [c0] 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- 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50) ~ Subsystem: Unknown device 1695:3005 ~ Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- ~ Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Interrupt: pin C routed to IRQ 12 ~ Region 0: I/O ports at e000 [size=256] ~ Capabilities: [c0] 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- 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS (prog-if 00 [VGA]) ~ Subsystem: Giga-byte Technology: Unknown device 4005 ~ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- ~ Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- ~ Latency: 32 (2000ns min), cache line size 08 ~ Interrupt: pin A routed to IRQ 16 ~ Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M] ~ Region 1: I/O ports at 9000 [size=256] ~ Region 2: Memory at dd000000 (32-bit, non-prefetchable) [size=16K] ~ Expansion ROM at <unassigned> [disabled] [size=128K] ~ Capabilities: [50] AGP version 2.0 ~ Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2,x4 ~ Command: RQ=0 SBA+ AGP- 64bit- FW- Rate=<none> ~ 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- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/jYhuPC4Ugo8dWvcRAkaHAJ41qrX/dERy2uuSfPhkyD3mmMQ94wCfasJd k6skYq275YuYv92I5Ct/bUc= =aty1 -----END PGP SIGNATURE----- ----- End forwarded message ----- Best regards, Stefan Reinauer -- Architecture Team SuSE Linux AG --__--__-- _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios End of Linuxbios Digest ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________ ============================================================================== For more information on Hargreaves Lansdown, visit our web site http://www.hargreaveslansdown.co.uk IMPORTANT NOTICE This email is intended solely for the recipient and is confidential and not for third party unauthorised distribution. If an addressing, or transmission, error has misdirected this email, please notify the author by replying to this email or notifying the system manager (internal.security(a)hargreaveslansdown.co.uk) if you are not the intended recipient you must not disclose, distribute, copy, print or rely on this email. Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of Hargreaves Lansdown. In addition, staff are not authorised to enter into any contract through email and therefore nothing contained herein should be construed as such. This email has been prepared using information believed by the author to be reliable and accurate but Hargreaves Lansdown makes no warranty as to the accuracy or completeness. In particular, Hargreaves Lansdown does not accept responsibility for any changes made to this email after it was sent. All group companies are Authorised and regulated by the Financial Services Authority and registered in England and the registered office is Kendal House, 4 Brighton Mews, Clifton, Bristol, BS8 2NX. Telephone: 0117 9889880 ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________

1 0

LinuxBIOS + FILO boots RedHat 9 CD-ROM
by SONE Takeshi 15 Oct '03

15 Oct '03

I'm adding ATAPI CD-ROM driver and ISO-9660 filesystem to FILO. So far, RedHat 9 installation CD-ROM boots with FILO commandline like: boot: hdc:/isolinux/vmlinuz initrd=hdc:/isolinux/initrd.img (hdc is my CD-ROM drive). It sometimes fails to detect my USB mouse, but the fullscreen graphical installer is working beautifully on my EPIA 5000. :) (I'm using VGABIOS. I didn't try a PS/2 mouse since it is reported to not work on EPIA). Before RedHat I tried KNOPPIX 3.3. It uses El Torito floppy emulation and I already added the code to mount the El Torito floppy image. It boots, but hangs during the device detection phase I think. Perhaps it expects the video is already switched to graphical mode by the realmode part of Linux, which we don't execute. I have already downloaded SuSE and Debian iso images, but I ran out of my coasters. Anyway, guys, this is fun. :) I'll release FILO 0.4 when some cleanup work is done. Current CD driver is hackish and has an issue with media detection. -- Takeshi

1 1

Re: Number of resets in 1.1.5
by YhLu 15 Oct '03

15 Oct '03

Stephan, The code seems already only reset once in the misc_control.c. Other reset may be caused by other reasons. Regards YH. -----邮件原件----- 发件人: Stefan Reinauer [mailto:stepan@suse.de] 发送时间: 2003年10月15日 4:51 收件人: linuxbios(a)clustermatic.org 主题: Number of resets in 1.1.5 Hi, LinuxBIOS 1.1.5 currently does a couple of resets on the HDAMA before it actually boots the payload. Is this elementary for getting HT to work properly, or is it based on the current algorithm? To keep boot times as short as possible, it'd be better to only do one reset and gather all setup functions that need reset before that. Stefan -- Architecture Team SuSE Linux AG _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

Number of resets in 1.1.5
by Stefan Reinauer 15 Oct '03

15 Oct '03

Hi, LinuxBIOS 1.1.5 currently does a couple of resets on the HDAMA before it actually boots the payload. Is this elementary for getting HT to work properly, or is it based on the current algorithm? To keep boot times as short as possible, it'd be better to only do one reset and gather all setup functions that need reset before that. Stefan -- Architecture Team SuSE Linux AG

2 1

EPIA M800 works fine.
by bendany 15 Oct '03

15 Oct '03

hi,all. today I get an epia M800 mb, and use the original BIOS, install debian woody. after that, I build a linuxbios, with FILO 0.3 and VGA support, just replace the original BIOS. it works!, without any modification! ;-) Best Reguards. Ben.

2 1

Fwd: New 1U Chassis for 2 EPIA
by Nathanael Noblet 14 Oct '03

14 Oct '03

Uh there was for a time people looking for cheap epia stuff with cases. although I don't know many details, these look neat. Begin forwarded message: > > http://www.travla.com/Products/products.html > > or for each chassis are: > > http://www.travla.com/Products/C147/c147.html > http://www.travla.com/Products/C146/c146.html > -- Nathanael Noblet Gnat Solutions 4604 Monterey Ave NW Calgary, AB T3B 5K4 T/F 403.288.5360 C 403.809.5368 http://www.gnat.ca/

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot October 2003