coreboot February 2006

coreboot@coreboot.org

33 participants
54 discussions

Re: [LinuxBIOS] BIOS Saver RD1
by Ken Fuchs 05 Jun '07

05 Jun '07

> On Wed, Aug 03, 2005 at 11:59:20AM +0900, Jun OKAJIMA wrote: > > Probably, most guys here use BIOS Saver. > > And it works well? > > In mine, RD1 for PLCC gets not being writable suddenly. > > I mean, it seems writable but # flash_rom -v fails. > > I solved this problem by a quick hack. > > > > How about yours? You can write RD1 or W49F002U well? > > Any problem happen? Johnathan McDowell wrote: > Even after that it's sometimes a bit flakey and I have to erase, then > write it. I've put the board's original BIOS in the RD1 and am writing > to the SST 39SF020A instead, which works without problems. I've read posts about the RD1 that suggest its integrated flash device is low quality and it may take 10 or more flash attempts to get a good flash update to the RD1 flash device. As a result, many RD1 BIOS Savior users will flash the commercial BIOS image (or other known good BIOS image) into the RD1 integrated flash device as many times as needed to get an image that boots. Then use the original BIOS device to flash test BIOS image (usually LinuxBIOS images among this group), since the original BIOS device usually flashes OK on the first attempt. I've used the RD1 in the above fashion with great success on the Tyan S2885 mainboard. The same RD1 would not work on the nVidia CK8-04 CRB mainboard. I think the CK8-04 CRB requires a flash device that the RD1 does not support. However, the RD1 worked well as an "do nothing" adapter which allowed swapping the BIOS flash device between my flash burner and the mainboard without any wear to the mainboard's BIOS socket. BTW, my flash burner is an older Enhanced Willem Universal Programmer. I got mine for only $60 US over a year ago. I've seen it for less than $40 on eBay a few weeks ago. The newest model is going for about $50 US. It does a LinuxBIOS flash in about 5 minutes; not bad for a $60 burner. However, it does require changing DIP switches to match an image for each device it can program. Great for the amateur or professional with a small budget. > > BTW, a cable of your RD1 is not broken? > > I needed soldering to fix it. > Mine was fine out of the box. Mine cable and switch worked fine out of the box as well. Sincerely, Ken Fuchs <kfuchs(a)winternet.com> ami-mac-sun

16 47

[LinuxBIOS] LinuxBIOS support for nvidia CK804 northbridge?
by Carl-Daniel Hailfinger 19 Apr '06

19 Apr '06

Hi, in the process of trying to find any motherboard with more than 3 PCI-Express slots and LinuxBIOS support, I failed miserably. It seems such boards only exist with nVidia CK804 northbridges for which I couldn't find any code in the LinuxBIOS source code. Section 2.9 of the LinuxBIOS FAQ suggests to send lspci -vvv to this list for closer inspection. One of those systems with 4 PCIe slots is the Asus K8N-SLI Deluxe. The lspci below contains four PCIe gigabit ethernet controllers at 0000:01:00.0, 0000:02:00.0, 0000:03:00.0 and 0000:04:00.0. It's the only motherboard with this northbridge I have access to at the moment. switch:~ # lspci -vvv 0000:00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Capabilities: [44] #08 [01e0] Capabilities: [e0] #08 [a801] 0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 0000:00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at e400 [size=32] Region 4: I/O ports at 4c00 [size=64] Region 5: I/O ports at 4c40 [size=64] Capabilities: [44] 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- 0000:00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 201 Region 0: Memory at d3004000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] 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- 0000:00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 (750ns min, 250ns max) Interrupt: pin B routed to IRQ 177 Region 0: Memory at d3005000 (32-bit, non-prefetchable) [size=256] Capabilities: [44] #0a [2098] 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- 0000:00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) Subsystem: ASUSTeK Computer Inc.: Unknown device 812a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 (500ns min, 1250ns max) Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at dc00 [size=256] Region 1: I/O ports at e000 [size=256] Region 2: Memory at d3003000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] 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- 0000:00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 (750ns min, 250ns max) Region 4: I/O ports at f000 [size=16] Capabilities: [44] 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- 0000:00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) (prog-if 85 [Master SecO PriO]) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 177 Region 0: I/O ports at 09f0 [size=8] Region 1: I/O ports at 0bf0 [size=4] Region 2: I/O ports at 0970 [size=8] Region 3: I/O ports at 0b70 [size=4] Region 4: I/O ports at d800 [size=16] Region 5: Memory at d3002000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] 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- 0000:00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) (prog-if 85 [Master SecO PriO]) Subsystem: ASUSTeK Computer Inc.: Unknown device 815a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 185 Region 0: I/O ports at 09e0 [size=8] Region 1: I/O ports at 0be0 [size=4] Region 2: I/O ports at 0960 [size=8] Region 3: I/O ports at 0b60 [size=4] Region 4: I/O ports at c400 [size=16] Region 5: Memory at d3001000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] 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- 0000:00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=128 I/O behind bridge: 0000a000-0000afff Memory behind bridge: ce000000-d0ffffff Prefetchable memory behind bridge: c0000000-c7ffffff BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- 0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) Subsystem: ASUSTeK Computer Inc.: Unknown device 8141 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 (250ns min, 5000ns max) Interrupt: pin A routed to IRQ 193 Region 0: Memory at d3000000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at b000 [size=8] Capabilities: [44] 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- 0000:00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, cache line size 08 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 00009000-00009fff Memory behind bridge: cc000000-cdffffff Prefetchable memory behind bridge: 00000000fff00000-0000000000000000 BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B- 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- Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [58] #08 [a800] Capabilities: [80] #10 [0141] 0000:00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, cache line size 08 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 00008000-00008fff Memory behind bridge: ca000000-cbffffff Prefetchable memory behind bridge: 00000000fff00000-0000000000000000 BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B- 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- Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [58] #08 [a800] Capabilities: [80] #10 [0141] 0000:00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, cache line size 08 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00007000-00007fff Memory behind bridge: c8000000-c9ffffff Prefetchable memory behind bridge: 00000000fff00000-0000000000000000 BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B- 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- Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [58] #08 [a800] Capabilities: [80] #10 [0141] 0000:00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, cache line size 08 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00006000-00006fff Memory behind bridge: d1000000-d2ffffff Prefetchable memory behind bridge: 00000000fff00000-0000000000000000 BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B- 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- Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [58] #08 [a800] Capabilities: [80] #10 [0141] 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Capabilities: [80] #08 [2101] 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- 0000:01:00.0 Ethernet controller: SysKonnect SK-9Exx 10/100/1000Base-T Adapter (rev 10) Subsystem: SysKonnect SK-9E21D 10/100/1000Base-T Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR- Latency: 0, cache line size 08 Interrupt: pin A routed to IRQ 233 Region 0: Memory at d2000000 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at 6000 [size=256] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [e0] #10 [0011] 0000:02:00.0 Ethernet controller: SysKonnect SK-9Exx 10/100/1000Base-T Adapter (rev 10) Subsystem: SysKonnect SK-9E21D 10/100/1000Base-T Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR- Latency: 0, cache line size 08 Interrupt: pin A routed to IRQ 225 Region 0: Memory at c9000000 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at 7000 [size=256] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [e0] #10 [0011] 0000:03:00.0 Ethernet controller: SysKonnect SK-9Exx 10/100/1000Base-T Adapter (rev 10) Subsystem: SysKonnect SK-9E21D 10/100/1000Base-T Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR- Latency: 0, cache line size 08 Interrupt: pin A routed to IRQ 217 Region 0: Memory at cb000000 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at 8000 [size=256] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [e0] #10 [0011] 0000:04:00.0 Ethernet controller: SysKonnect SK-9Exx 10/100/1000Base-T Adapter (rev 10) Subsystem: SysKonnect SK-9E21D 10/100/1000Base-T Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR- Latency: 0, cache line size 08 Interrupt: pin A routed to IRQ 209 Region 0: Memory at cd000000 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at 9000 [size=256] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [e0] #10 [0011] 0000:05:06.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000 AGP 8x] (rev c1) (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- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (1250ns min, 250ns max) Interrupt: pin A routed to IRQ 12 Region 0: Memory at ce000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at c0000000 (32-bit, prefetchable) [size=128M] 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- 0000:05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 808b 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 (500ns min, 1000ns max), cache line size 08 Interrupt: pin A routed to IRQ 12 Region 0: Memory at d0008000 (32-bit, non-prefetchable) [size=2K] Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] 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- 0000:05:0c.0 Ethernet controller: Marvell Technology Group Ltd. Gigabit Ethernet Controller (rev 13) Subsystem: ASUSTeK Computer Inc. Marvell 88E8001 Gigabit Ethernet Controller (Asus) 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 (5750ns min, 7750ns max), cache line size 08 Interrupt: pin A routed to IRQ 209 Region 0: Memory at d0004000 (32-bit, non-prefetchable) [size=16K] Region 1: I/O ports at a000 [size=256] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data The only references to something similar were a post archived at http://www.mail-archive.com/linuxbios@openbios.org/msg00792.html but the thread seemed to end inconclusive and another post at http://www.mail-archive.com/linuxbios@openbios.org/msg01023.html Is there any support for that nvidia northbridge underway? Regards, Carl-Daniel

3 9

[LinuxBIOS] bus 0 dev 0 and fidvid change
by Lu, Yinghai 04 Apr '06

04 Apr '06

Please check the issue 41, I make K8 MB can be compiled, and It include bus0/dev0 and fidvid change enhancement HT_CHAIN_UNITID_BASE Default is 1, and if it is 6, then amd8131 will be from 6, also if it is 0, will assume ht chain only have one HT device... HT_CHAIN_END_UNITID_BASE Default is 0x20 --- mean do not use that, if it is 0, the amd8111 will be dev0 SB_HT_CHAIN_UNITID_OFFSET_ONLY Default is 1, so if HT_CHAIN_UNITID_BASE!=1, will only offset unitid of SB CHAIN. K8_SB_HT_CHAIN_ON_BUS0 Deault is 0, if it is 1, will put sb chain on bus 0, even for S2885 sb ht is on link2, it will put on bus0. K8_SET_FIDVID in cache_as_ram_auto.c or auto.c Fidvid change to sync the fid on 4 way or more system with different cpu installed.... Put following sequence in your cache_as_ram_auto.c after ht is set. enable_fid_change(); enable_fid_change_on_sb(); init_fidvid_bsp(bsp_apicid); please check init_cpus.c and fidvid.c and amd8111_early_ctrl.c for detail.... YH

2 1

Re: [LinuxBIOS] RES: RES: Rumba target and AMD RDK THINCLIENT
by Li-Ta Lo 13 Mar '06

13 Mar '06

On Fri, 2006-02-24 at 16:28 -0300, Jardel Silveira wrote: > Dear Li-Ta Lo, > > > I´ve just tried to compile rumba now and i´ve got this ouputÇ > > N_OFFSET='0x0' -DXIP_ROM_SIZE='0x10000' -DXIP_ROM_BASE='0xfffd0000' > -DCONFIG_UDELAY_TSC='1' -DCONFIG_TSC_X86RDTSC_CALIBRATE_WITH_TIMER2='0' > -DCONFIG_UDELAY_IO='0' > /home/jardel/projetos/LinuxBIOSv2/src/mainboard/amd/rumba/auto.c -o auto.inc > raminit.c:3.61: > struct mem_controller undeclared > make[1]: ** [auto.inc] Erro 1 > make[1]: Leaving directory > `/home/jardel/projetos/LinuxBIOSv2/targets/amd/rumba/rumba/normal' > make: ** [normal/linuxbios.rom] Erro 1 > jardel@jardel:~/projetos/LinuxBIOSv2/targets/amd/rumba/rumba$ ls > > I just committed other part of the change. Could you try it again? -- Li-Ta Lo <ollie(a)lanl.gov> Los Alamos National Lab

8 33

[LinuxBIOS] Success report on VIA EPIA-M10000
by Leon Woestenberg 04 Mar '06

04 Mar '06

Hello all, just wanted to report that I have gotten my EPIA-M10000 to boot LinuxBIOS 2184, then FILO 0.4.2, then Ubuntu with kernel 2.6.12 into X without problems. This time round (for learning purposes) I extracted the VGA BIOS from the BIOS upgrade file, and not from a running EPIA. (Still note that there is an error in the EPIA HOWTO about how to extract the VGA BIOS from memory. -- See my messages of the past few days for context.) For completeness, here is a small diff, plus an adapted Makefile that made this work. Thanks for all the work you guys have put into it. Next up is inclusion of the ACPI table. Regards, Leon. --- Index: src/mainboard/via/epia-m/mainboard.c =================================================================== --- src/mainboard/via/epia-m/mainboard.c (revision 2184) +++ src/mainboard/via/epia-m/mainboard.c (working copy) @@ -30,7 +30,7 @@ device_t dev; printk_info("write_protect_vgabios\n"); - dev = dev_find_device(PCI_VENDOR_ID_VIA, 0x3123, 0); + dev = dev_find_device(PCI_VENDOR_ID_VIA, 0x3122, 0); if(dev) pci_write_config8(dev, 0x61, 0xaa); } Index: targets/via/epia-m/Config.lb =================================================================== --- targets/via/epia-m/Config.lb (revision 2184) +++ targets/via/epia-m/Config.lb (working copy) @@ -55,7 +55,7 @@ # payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf # payload ../../../../tg3--ide_disk.zelf # payload ../../../../../lnxieepro100.ebi - payload /filo.elf + payload /home/leon/sandbox/linuxbios-2184/filo.elf end buildrom ./linuxbios.rom ROM_SIZE "fallback" Index: targets/via/epia-m/Config.vga.filo =================================================================== --- targets/via/epia-m/Config.vga.filo (revision 2184) +++ targets/via/epia-m/Config.vga.filo (working copy) @@ -38,20 +38,14 @@ option ROM_SECTION_OFFSET=0x10000 option ROM_SECTION_SIZE=0x18000 option LINUXBIOS_EXTRA_VERSION=".0Normal" -# payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf -# payload ../../../../tg3--ide_disk.zelf -# payload ../../../../../lnxieepro100.ebi - payload /filo.elf + payload /home/leon/sandbox/linuxbios-2184/filo.elf end romimage "fallback" option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0xc000 option LINUXBIOS_EXTRA_VERSION=".0Fallback" -# payload /usr/share/etherboot/5.1.9pre2-lnxi-lb/tg3--ide_disk.zelf -# payload ../../../../tg3--ide_disk.zelf -# payload ../../../../../lnxieepro100.ebi - payload /filo.elf + payload /home/leon/sandbox/linuxbios-2184/filo.elf end buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback" --- --- # File: via/epia-m/epia-m/Makefile is autogenerated all: ./linuxbios.rom include Makefile.settings fallback/linuxbios.rom: if (cd fallback; \ make linuxbios.rom)\ then true; else exit 1; fi; clean: fallback-clean fallback-clean: (cd fallback; make clean) ./linuxbios.rom: fallback/linuxbios.rom cat /home/leon/sandbox/linuxbios-2184/vgabios.bin fallback/linuxbios.rom > ./linuxbios.rom .PHONY: all clean fallback-clean fallback/linuxbios.rom Makefile: /home/leon/sandbox/linuxbios-2184/targets/via/epia-m/epia-m/config.py /home/leon/sandbox/linuxbios-2184/targets/via/epia-m/Config.lb (cd /home/leon/sandbox/linuxbios-2184/targets ; via/epia-m/epia-m/config.py via/epia-m/Config.lb /home/leon/sandbox/linuxbios-2184) ---

4 7

Re: [LinuxBIOS] does any one have access to the VT8237 docs
by Samet, Matt 28 Feb '06

28 Feb '06

I looked online for a while and could not find the VT8237 datasheet. I tried asking VIA for the doc (they have a form you can fill out for the NDA) but they didn't respond either. I looked through the list archives and saw that Bari Ari was working on adding support for the vt8237 -- Bari, any chance of an update? Thanks, -=matt -----Original Message----- From: linuxbios-bounces(a)linuxbios.org [mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Adam Talbot Sent: Tuesday, February 28, 2006 1:51 PM To: linuxbios(a)linuxbios.org Subject: [LinuxBIOS] does any one have access to the VT8237 docs Still trying to get my EBC3266 board to post with linux bios. That board is based on the VT8623 and VT8237 chips. I currently am unable to get any console. I would guess that is because I am unable to start the south bridge, where the vt1211 is attached. I was hoping that is was close enughf to the VT8235, but I guess I am wrong. OK, time to start trying to add support for the VT8237 south bridge. Does any one have access to the Docs for the VT8237? -Adam Talbot -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios

2 1

[LinuxBIOS] does any one have access to the VT8237 docs
by Adam Talbot 28 Feb '06

28 Feb '06

Still trying to get my EBC3266 board to post with linux bios. That board is based on the VT8623 and VT8237 chips. I currently am unable to get any console. I would guess that is because I am unable to start the south bridge, where the vt1211 is attached. I was hoping that is was close enughf to the VT8235, but I guess I am wrong. OK, time to start trying to add support for the VT8237 south bridge. Does any one have access to the Docs for the VT8237? -Adam Talbot

1 0

[LinuxBIOS] EPIA-M VGA BIOS - X gives VIA(0): Bad V-BIOS checksum
by Leon Woestenberg 27 Feb '06

27 Feb '06

Hello all, my target: VIA EPIA-M 10000 Latest linuxbios (rev 2177) I extracted the VIA VGA BIOS from the EPIA running official BIOS rev. 1.13. However, my X server reports: VIA(0): Bad V-BIOS checksum. Everything before that looks good. Upon boot, I *do* get VGA output of FILO. Would could be the cause? See below for details on what I did. Regards, Leon. ---<sidenote>--- As a sidenote, I think the HOWTO/EPIA-M is wrong about how to extract: WRONG: dd if=/dev/mem of=/video.bios.bin \ WRONG: bs=1 count=65536 skip=790528 Note that 790528=0xC1000 and 65536=0x10000 /dev/mem must be read from 0xC000-0xD000 (VGA BIOS), whereas /proc/kcore must be read from 0xC1000-0xD1000 because kcore is an ELF 'view' to the memory, with a 0x1000 ELF header at 0xC000. What I did is extract from 0xC000-0xD000 as follows: dd if=/dev/mem of=/113mem.bin skip=1536 count=128 (bs=512 by default) ---</sidenote>--- leon@nehemiah:/$ ls -ald /113mem.bin -rw-r--r-- 1 root root 65536 2006-02-23 03:57 /113mem.bin leon@nehemiah:/$ hexdump -C /113mem.bin | head -n 10 00000000 55 aa 7d e9 26 7f 5e 1b fa f9 f4 82 00 00 00 00 |U.}.&.^.........| 00000010 00 00 00 00 00 00 00 00 44 00 d4 b0 c6 00 49 42 |........D.....IB| 00000020 4d 20 43 4f 4d 50 41 54 49 42 4c 45 42 43 50 4f |M COMPATIBLEBCPO| 00000030 53 54 00 00 18 00 30 34 2f 31 38 2f 30 33 01 15 |ST....04/18/03..| 00000040 00 c0 c6 00 50 43 49 52 06 11 22 31 00 00 18 00 |....PCIR.."1....| 00000050 00 00 00 03 40 00 51 01 00 80 00 00 00 01 20 20 |....@.Q....... | 00000060 20 56 49 41 20 54 65 63 2e 49 6e 63 2e 20 20 20 | VIA Tec.Inc. | 00000070 20 20 20 20 20 20 20 20 20 56 45 52 2e 56 54 33 | VER.VT3| 00000080 31 32 33 20 20 20 20 01 15 01 12 56 49 41 20 20 |123 ....VIA | 00000090 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 00 | ....| leon@nehemiah:/$ md5sum /113mem.bin 87017abc14c53e51a269fe59b5ba1508 /113mem.bin

2 1

[LinuxBIOS] How to ID flash chip type from software?
by Anton Borisov 27 Feb '06

27 Feb '06

Hello. There is a tricky case - I can't see which exactly flash chip installed in system. flashrom from v2161 was unable to identify it too. I found an interesting site - http://ctflasher.sourceforge.net - however this tool doesn't have bios-flasher yet. lspci -v 00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) Subsystem: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface Flags: bus master, fast devsel, latency 0 Memory at f8000000 (32-bit, prefetchable) [size=64M] Capabilities: [e4] #09 [0106] 00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02) (prog-if 00 [VGA]) Subsystem: Intel Corp.: Unknown device 4246 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f0000000 (32-bit, prefetchable) [size=128M] Memory at ffa00000 (32-bit, non-prefetchable) [size=512K] I/O ports at ec00 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [d0] Power Management version 1 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev c2) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: ff900000-ff9fffff 00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: Intel Corp.: Unknown device 4246 Flags: bus master, medium devsel, latency 0, IRQ 5 I/O ports at <unassigned> I/O ports at <unassigned> I/O ports at <unassigned> I/O ports at <unassigned> I/O ports at ffa0 [size=16] Memory at 1f000000 (32-bit, non-prefetchable) [size=1K] 00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) Subsystem: Intel Corp.: Unknown device 4246 Flags: medium devsel, IRQ 10 I/O ports at e800 [size=32] 01:01.0 Ethernet controller: Intel Corp.: Unknown device 107c (rev 05) Subsystem: Intel Corp.: Unknown device 1376 Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 15 Memory at ff900000 (32-bit, non-prefetchable) [size=128K] Memory at ff920000 (32-bit, non-prefetchable) [size=128K] I/O ports at d800 [size=64] Expansion ROM at ff940000 [disabled] [size=128K] Capabilities: [dc] Power Management version 2 Capabilities: [e4] PCI-X non-bridge device. 01:02.0 Ethernet controller: Intel Corp.: Unknown device 107c (rev 05) Subsystem: Intel Corp.: Unknown device 1376 Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 10 Memory at ff960000 (32-bit, non-prefetchable) [size=128K] Memory at ff980000 (32-bit, non-prefetchable) [size=128K] I/O ports at d400 [size=64] Expansion ROM at ff9a0000 [disabled] [size=128K] Capabilities: [dc] Power Management version 2 Capabilities: [e4] PCI-X non-bridge device. 01:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 01) Subsystem: Intel Corp.: Unknown device 302f Flags: bus master, medium devsel, latency 32, IRQ 5 Memory at ff9d0000 (32-bit, non-prefetchable) [size=4K] I/O ports at d000 [size=64] Capabilities: [dc] Power Management version 2 cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 3.00GHz stepping : 1 cpu MHz : 2994.007 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pni monitor ds_cpl cid xtpr bogomips : 5914.62 Thanks. -- Sincerely, Anton Borisov

5 16

[LinuxBIOS] FILO Enabling VIA_SOUND breaks keyboard in Linux? [VIA EPIA-M10000]
by Leon Woestenberg 25 Feb '06

25 Feb '06

Hello, further experimenting with EPIA-M10000: I am using the default FILO 0.4.2 "Config" for x86, except for the AUTOBOOT_FILE which I have set to: AUTOBOOT_FILE = "hdc1:/vmlinuz-2.6.12-10-386 initrd=hdc1:/initrd.img-2.6.12-10-386 root=/dev/hdc2 ro vga=771 console=tty0 console=ttyS0,115200" This time I tried enabling sound: SUPPORT_SOUND = 1 VIA_SOUND = 1 During booting it reported "No sound device found".* The next problem was I had keyboard control during the FILO console, but no longer in Linux. When I changed back to disabling sound and reflashing LinuxBIOS, this problem dissappeared. I have then fully reproduced this whole sequence again from the start. Can the FILO sound probe do this? I thought it is merely scanning PCI? Regards, Leon. * leon@nehemiah:~/sandbox/filo-0.4.2$ sudo lspci -s 00:11.5 0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) leon@nehemiah:~/sandbox/filo-0.4.2$ sudo lspci -n -s 00:11.5 0000:00:11.5 0401: 1106:3059 (rev 50) whereas: leon@nehemiah:~/sandbox/filo-0.4.2/drivers$ tail -n 3 via-sound.c struct sound_driver viasnd_driver[] __sound_driver = { {0x1106, 0x3058, &viasnd_ops}, /* VT82C686 AC97 Audio Controller */ };

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot February 2006