Hi,
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Thanks! Carl-Daniel
Hi Carl-Daniel
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Sorry for the delay, but i somehow missed your message.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Best regards ST
Hi ST,
On 08.05.2007 22:45, ST wrote:
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Thanks!
A few interesting differences between the dumps: * LinuxBIOS has subsystem vendor/id 1022:2b80 for all devices -> Bug or feature? * Some devices seem to have disappeared under LB or were they just removed from the PCI slots? * More stuff...
00:00.0 0500: 10de:0369 (rev a1) 00:01.0 0601: 10de:0360 (rev a2) 00:01.1 0c05: 10de:0368 (rev a2) 00:01.2 0500: 10de:036a (rev a2) +00:01.3 0b40: 10de:036b (rev a2) New device? SMU (System Management Unit) hidden by factory BIOS
00:02.0 0c03: 10de:036c (rev a1) (prog-if 10 [OHCI]) 00:02.1 0c03: 10de:036d (rev a2) (prog-if 20 [EHCI]) 00:04.0 0101: 10de:036e (rev a1) (prog-if 8a [Master SecP PriP]) 00:05.0 0101: 10de:037f (rev a2) (prog-if 85 [Master SecO PriO]) 00:05.1 0101: 10de:037f (rev a2) (prog-if 85 [Master SecO PriO]) 00:05.2 0101: 10de:037f (rev a2) (prog-if 85 [Master SecO PriO]) -00:06.0 0604: 10de:0370 (rev a2) (prog-if 01 [Subtractive decode]) +00:06.0 0604: 10de:0370 (rev a2) (prog-if 00 [Normal decode]) Decoding changed
00:06.1 0403: 10de:0371 (rev a2) 00:08.0 0680: 10de:0373 (rev a2) +00:0a.0 0604: 10de:0376 (rev a2) (prog-if 00 [Normal decode]) +00:0b.0 0604: 10de:0374 (rev a2) (prog-if 00 [Normal decode]) +00:0c.0 0604: 10de:0374 (rev a2) (prog-if 00 [Normal decode]) +00:0d.0 0604: 10de:0378 (rev a2) (prog-if 00 [Normal decode]) +00:0e.0 0604: 10de:0375 (rev a2) (prog-if 00 [Normal decode]) New devices? PCIe bridges
00:0f.0 0604: 10de:0377 (rev a2) (prog-if 00 [Normal decode]) 00:18.0 0600: 1022:1100 -01:07.0 0200: 10ec:8139 (rev 10) Disappeared device? Realtek 8139 nic -01:08.0 0280: 1244:0a00 (rev 02) Disappeared device? AVM A1 ISDN card -01:0a.0 0c00: 104c:8024 (prog-if 10 [OHCI]) Disappeared device? TI Firewire controller
-02:00.0 0300: 10de:0393 (rev a1) (prog-if 00 [VGA]) +07:00.0 0300: 10de:0393 (rev a1) (prog-if 00 [VGA]) Different bus?
Regards, Carl-Daniel
On 5/11/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Hi ST,
On 08.05.2007 22:45, ST wrote:
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Thanks!
A few interesting differences between the dumps:
- LinuxBIOS has subsystem vendor/id 1022:2b80 for all devices -> Bug or feature?
you could change it in MB Option.lb. I never boot that MB to normal BIOS to check subsystem vendor/id and just use values for AMD cheetah.
- Some devices seem to have disappeared under LB or were they just removed from the PCI slots?
- More stuff...
00:00.0 0500: 10de:0369 (rev a1) 00:01.0 0601: 10de:0360 (rev a2) 00:01.1 0c05: 10de:0368 (rev a2) 00:01.2 0500: 10de:036a (rev a2) +00:01.3 0b40: 10de:036b (rev a2) New device? SMU (System Management Unit) hidden by factory BIOS
00:02.0 0c03: 10de:036c (rev a1) (prog-if 10 [OHCI]) 00:02.1 0c03: 10de:036d (rev a2) (prog-if 20 [EHCI]) 00:04.0 0101: 10de:036e (rev a1) (prog-if 8a [Master SecP PriP]) 00:05.0 0101: 10de:037f (rev a2) (prog-if 85 [Master SecO PriO]) 00:05.1 0101: 10de:037f (rev a2) (prog-if 85 [Master SecO PriO]) 00:05.2 0101: 10de:037f (rev a2) (prog-if 85 [Master SecO PriO]) -00:06.0 0604: 10de:0370 (rev a2) (prog-if 01 [Subtractive decode]) +00:06.0 0604: 10de:0370 (rev a2) (prog-if 00 [Normal decode]) Decoding changed
00:06.1 0403: 10de:0371 (rev a2) 00:08.0 0680: 10de:0373 (rev a2) +00:0a.0 0604: 10de:0376 (rev a2) (prog-if 00 [Normal decode]) +00:0b.0 0604: 10de:0374 (rev a2) (prog-if 00 [Normal decode]) +00:0c.0 0604: 10de:0374 (rev a2) (prog-if 00 [Normal decode]) +00:0d.0 0604: 10de:0378 (rev a2) (prog-if 00 [Normal decode]) +00:0e.0 0604: 10de:0375 (rev a2) (prog-if 00 [Normal decode]) New devices? PCIe bridges
could disable some of them, in MB Config.lb
00:0f.0 0604: 10de:0377 (rev a2) (prog-if 00 [Normal decode]) 00:18.0 0600: 1022:1100 -01:07.0 0200: 10ec:8139 (rev 10) Disappeared device? Realtek 8139 nic -01:08.0 0280: 1244:0a00 (rev 02) Disappeared device? AVM A1 ISDN card -01:0a.0 0c00: 104c:8024 (prog-if 10 [OHCI]) Disappeared device? TI Firewire controller
-02:00.0 0300: 10de:0393 (rev a1) (prog-if 00 [VGA]) +07:00.0 0300: 10de:0393 (rev a1) (prog-if 00 [VGA]) Different bus?
After disable some PCIE bus, the bus number will be same.
YH
On Fri, May 11, 2007 at 12:29:39PM -0700, yhlu wrote:
On 5/11/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
A few interesting differences between the dumps:
- LinuxBIOS has subsystem vendor/id 1022:2b80 for all devices -> Bug or feature?
you could change it in MB Option.lb. I never boot that MB to normal BIOS to check subsystem vendor/id and just use values for AMD cheetah.
The Gigabyte vendor id is 0x1458; how can I find out what MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID should be set to for this board?
Thanks, Ward.
On 5/22/07, Ward Vandewege ward@gnu.org wrote:
The Gigabyte vendor id is 0x1458; how can I find out what MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID should be set to for this board?
boot into linux with Normal BIOS. (---sorry to say that words. someone doesn't think that is normal and standard). then lspci -vvxxx some device could have subsystem id...
YH
On Tue, May 22, 2007 at 01:37:25PM -0700, yhlu wrote:
On 5/22/07, Ward Vandewege ward@gnu.org wrote:
The Gigabyte vendor id is 0x1458; how can I find out what MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID should be set to for this board?
boot into linux with Normal BIOS. (---sorry to say that words. someone doesn't think that is normal and standard).
OK :)
then lspci -vvxxx some device could have subsystem id...
Yeah, that was my first thought too. I've been looking; the output is attached. I can't really tell which of those devices has the device id I should choose. Which one do you think it is?
Thanks, Ward.
Ward Vandewege wrote:
On Tue, May 22, 2007 at 01:37:25PM -0700, yhlu wrote:
On 5/22/07, Ward Vandewege ward@gnu.org wrote:
The Gigabyte vendor id is 0x1458; how can I find out what MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID should be set to for this board?
boot into linux with Normal BIOS. (---sorry to say that words. someone doesn't think that is normal and standard).
OK :)
then lspci -vvxxx some device could have subsystem id...
Yeah, that was my first thought too. I've been looking; the output is attached. I can't really tell which of those devices has the device id I should choose. Which one do you think it is?
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 01 50 ^^^^^
-Corey
On Tue, May 22, 2007 at 05:42:55PM -0400, Corey Osgood wrote:
Ward Vandewege wrote:
On Tue, May 22, 2007 at 01:37:25PM -0700, yhlu wrote:
On 5/22/07, Ward Vandewege ward@gnu.org wrote:
The Gigabyte vendor id is 0x1458; how can I find out what MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID should be set to for this board?
boot into linux with Normal BIOS. (---sorry to say that words. someone doesn't think that is normal and standard).
OK :)
then lspci -vvxxx some device could have subsystem id...
Yeah, that was my first thought too. I've been looking; the output is attached. I can't really tell which of those devices has the device id I should choose. Which one do you think it is?
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 01 50 ^^^^^
Uhm - yes, but those are the device ids for each pci device, which are also listed in the 'Subsytem' line. I was under the impression that the MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID setting was a device ID for the whole motherboard - is that correct? If not, what does that setting mean?
I see that for some other boards it is set to something that makes sense for the whole board - the Tyan s2881 for instance has 2881 as the device id.
Thanks, Ward.
Ward Vandewege wrote:
On Tue, May 22, 2007 at 05:42:55PM -0400, Corey Osgood wrote:
Ward Vandewege wrote:
On Tue, May 22, 2007 at 01:37:25PM -0700, yhlu wrote:
On 5/22/07, Ward Vandewege ward@gnu.org wrote:
The Gigabyte vendor id is 0x1458; how can I find out what MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID should be set to for this board?
boot into linux with Normal BIOS. (---sorry to say that words. someone doesn't think that is normal and standard).
OK :)
then lspci -vvxxx some device could have subsystem id...
Yeah, that was my first thought too. I've been looking; the output is attached. I can't really tell which of those devices has the device id I should choose. Which one do you think it is?
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 01 50 ^^^^^
Uhm - yes, but those are the device ids for each pci device, which are also listed in the 'Subsytem' line. I was under the impression that the MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID setting was a device ID for the whole motherboard - is that correct? If not, what does that setting mean?
I see that for some other boards it is set to something that makes sense for the whole board - the Tyan s2881 for instance has 2881 as the device id.
Sorry. I always thought that all of the devices were supposed to be set to the same device ID, that device ID would be the mainboard's ID, and that vendors were just really lax about setting them up correctly (because aside from us, hardly anyone uses them). If you look at the output from my laptop, nearly all the subsystem device IDs, including the network card, are set to 0x3091, if they're set at all (and I *think* that's how it's supposed to be):
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01) 00: 02 10 50 59 06 00 20 22 01 00 00 06 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 3c 10 91 30 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00: 02 10 3f 5a 07 00 30 02 00 00 04 06 00 40 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 40 91 91 20 22 20: 10 c0 10 c0 01 c8 f1 cf 00 00 00 00 00 00 00 00 30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 0c 00
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller 00: 02 10 74 43 17 00 b0 02 00 10 03 0c 10 40 80 00 10: 00 00 00 c0 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 3c 10 91 30 30: 00 00 00 00 d0 00 00 00 00 00 00 00 0b 01 00 00
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller 00: 02 10 75 43 17 00 b0 02 00 10 03 0c 10 40 00 00 10: 00 10 00 c0 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 3c 10 91 30 30: 00 00 00 00 d0 00 00 00 00 00 00 00 0b 01 00 00
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller 00: 02 10 73 43 17 00 b0 02 00 20 03 0c 10 40 00 00 10: 00 20 00 c0 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 3c 10 91 30 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 00 00
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11) 00: 02 10 72 43 03 00 30 02 11 00 05 0c 00 00 80 00 10: 01 84 00 00 00 30 00 c0 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 3c 10 91 30 30: 00 00 00 00 b0 00 00 00 00 00 00 00 00 00 00 00
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI 00: 02 10 76 43 05 00 30 02 00 8a 01 01 00 00 00 00 10: f1 01 00 00 f5 03 00 00 71 01 00 00 75 03 00 00 20: 11 84 00 00 00 00 00 00 00 00 00 00 3c 10 91 30 30: 00 00 00 00 70 00 00 00 00 00 00 00 ff 01 00 00
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge 00: 02 10 77 43 0f 00 20 02 00 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 3c 10 91 30 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge 00: 02 10 71 43 07 00 a0 02 00 01 04 06 00 40 81 00 10: 00 00 00 00 00 00 00 00 00 05 09 40 a1 a1 80 22 20: 20 c0 20 c0 00 50 f0 53 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02) 00: 02 10 70 43 17 00 30 04 02 00 01 04 08 40 80 00 10: 00 34 00 c0 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 3c 10 91 30 30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 02 02 00
00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02) 00: 02 10 78 43 17 00 30 04 02 00 03 07 08 40 80 00 10: 00 38 00 c0 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 3c 10 91 30 30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 02 02 00
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 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
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 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
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 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
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 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
01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE) 00: 02 10 55 59 07 00 b0 02 00 00 00 03 08 ff 00 00 10: 08 00 00 c8 01 90 00 00 00 00 10 c0 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 3c 10 91 30 30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 01 08 00
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00: ec 10 39 81 07 00 90 02 10 00 00 02 00 40 00 00 10: 01 a0 00 00 00 80 20 c0 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 3c 10 91 30 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 20 40
05:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) 00: e4 14 18 43 06 00 00 00 02 00 80 02 00 40 00 00 10: 00 40 20 c0 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 3c 10 55 13 30: 00 00 00 00 00 00 00 00 00 00 00 00 03 01 00 00
05:09.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 00: 4c 10 31 80 07 00 10 02 00 00 07 06 20 a8 82 00 10: 00 00 20 c0 a0 00 00 02 05 06 09 b0 00 00 00 50 20: 00 f0 ff 53 00 00 00 54 00 f0 ff 57 00 a4 00 00 30: fc a4 00 00 00 a8 00 00 fc a8 00 00 ff 01 00 05 40: 3c 10 91 30 01 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
06:00.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface 00: 4c 10 66 90 06 00 10 02 00 00 80 02 00 40 00 00 10: 00 00 02 54 00 00 00 54 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 02 1c 00 00 37 17 33 00 30: 00 00 00 00 40 00 00 00 00 00 00 00 10 01 00 00
-Corey
On 11.05.2007 21:29, yhlu wrote:
On 5/11/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Hi ST,
On 08.05.2007 22:45, ST wrote:
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Thanks!
A few interesting differences between the dumps:
- LinuxBIOS has subsystem vendor/id 1022:2b80 for all devices -> Bug or feature?
you could change it in MB Option.lb. I never boot that MB to normal BIOS to check subsystem vendor/id and just use values for AMD cheetah.
Normal BIOS subsystem vendor/device ids are a problem because we use them in flashrom to look up flash enable GPIO pins. I have a patch which changes the subsystem vendor id for the GA-M57SLI, BUT... the subsystem device id is not constant for a given board, the GA-M57SLI has ~7 different subsystem device ids. Can we assign different sub-devids to different devices? The code seems to be unable to cope with that.
Regards, Carl-Daniel
* Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net [070523 00:41]:
Normal BIOS subsystem vendor/device ids are a problem because we use them in flashrom to look up flash enable GPIO pins. I have a patch which changes the subsystem vendor id for the GA-M57SLI, BUT... the subsystem device id is not constant for a given board, the GA-M57SLI has ~7 different subsystem device ids. Can we assign different sub-devids to different devices? The code seems to be unable to cope with that.
I think this should be done in mainboard.c
On 5/23/07, Stefan Reinauer stepan@coresystems.de wrote:
I think this should be done in mainboard.c
current way is: you have set_subsystem_id in pci_device ops. there is one default in pci_device.c that will use default vaule in Options.lb.
the solution will be make Config.lb take different subssystem id for mcp55 with register info. and different device under mcp55 wil used those info to set in their own set_subsystem_id.
Do you really need that subsystem be different?
YH
Hi Daniel
- Some devices seem to have disappeared under LB or were they just removed from the PCI slots?
No, nothing unplugged in between the to lspci runs. Thats currently my problem with LB, besides the missing cpufreq due to missing acpi :-(.
But i was rather busy, so i had no time to look into it myself :-(.
ST
Hello Yinghai,
have you tested PCI slot functions on the GA-M57SLI?
On 12.05.2007 21:50, ST wrote:
-01:07.0 0200: 10ec:8139 (rev 10) Disappeared device? Realtek 8139 nic -01:08.0 0280: 1244:0a00 (rev 02) Disappeared device? AVM A1 ISDN card -01:0a.0 0c00: 104c:8024 (prog-if 10 [OHCI]) Disappeared device? TI Firewire controller
- Some devices seem to have disappeared under LB or were they just removed from the PCI slots?
No, nothing unplugged in between the to lspci runs. Thats currently my problem with LB [...]
I forgot whether PCI cards in PCI slots need a LB config change or should they work out of the box?
Regards, Carl-Daniel
On 5/14/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Hello Yinghai,
have you tested PCI slot functions on the GA-M57SLI?
I forgot whether PCI cards in PCI slots need a LB config change or should they work out of the box?
it should work out of the BOX, but irq routting in mptable could be adjusted.
please verify if pci bridge in MB config.lb is off.
YH
Hello YH
it should work out of the BOX, but irq routting in mptable could be adjusted.
please verify if pci bridge in MB config.lb is off.
I am sorry but i don't find such an option there? This is the config.lb taken directly from the svn repository. Any hints to unhide the PCI cards are very welcome.
The only reference to pci bridge i find in the src/mb directory for the m57 is irq_tables.c:98://pci bridge
and the next line
write_pirq_info(pirq_info, bus_mcp55[0], ((sbdn+6)<<3)|0, 0x1, 0xdef8, 0x2, 0xdef8, 0x3, 0xdef8, 0x4, 0xdef8, 0, 0);
Is there s.t. besides the source which documents the inner workings of LB? I didn't find anything on linuxbios.org.
Btw. http://linuxbios.org/FAQ seems to be borken.
Regards ST
On 17.05.2007 01:08, Peter Stuge wrote:
On Thu, May 17, 2007 at 12:47:52AM +0200, ST wrote:
please verify if pci bridge in MB config.lb is off.
I am sorry but i don't find such an option there?
I guess this would be:
device pci 6.0 on end # PCI
on line 339 of src/mainboard/gigabyte/m57sli/Config.lb
Did that work out?
Regards, Carl-Daniel
Hi Carl-Daniel
Did that work out?
No :-(. I just tried right now, but it didn't work. Unfortunatly i didn't save the output of lspci but it appeared the same to me as before. If you guys have some other suggestions to get PCI cards working on this board, let me know :-).
Regards ST
PS: The changes i made to the Config.lb file --- Config.lb (Revision 2690) +++ Config.lb (Arbeitskopie) @@ -336,7 +336,7 @@ device pci 5.0 on end # SATA 0 device pci 5.1 on end # SATA 1 device pci 5.2 on end # SATA 2 - device pci 6.0 on end # PCI + device pci 6.0 off end # PCI device pci 6.1 on end # AZA device pci 8.0 on end # NIC device pci 9.0 off end # NIC
On 08.05.2007 22:45, ST wrote:
Hi Carl-Daniel
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Sorry for the delay, but i somehow missed your message.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Verifying a LB port is very interesting work and leads to lots of head scratching.
Here is a list of more problems, some really serious.
-00:06.0 0604: 10de:0370 (rev a2) (prog-if 01 [Subtractive decode]) +00:06.0 0604: 10de:0370 (rev a2) (prog-if 00 [Normal decode])
Does changed decode mean anything?
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
SERR- changed to SERR+.
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
sec-latency=32 probably had a reason in the vendor BIOS. Why change?
I/O behind bridge: 00008000-00008fff
I/O behind bridge: 0000f000-00000fff
The LinuxBIOS I/O range is backwards (end before start) and has a different size. Same for other I/O ranges.
Memory behind bridge: fb000000-fcffffff
Memory behind bridge: fff00000-000fffff
The LinuxBIOS memory range is backwards and has a different size. Same for other mem ranges.
Prefetchable memory behind bridge: 50000000-500fffff
Prefetchable memory behind bridge: fff00000-000fffff
Same here.
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Parity- changed to Parity+.
Other devices had the same classes of problems. I'd like to get an explanation for all of the above to be able to correct some of the differences.
I have at least one patch for the GA-M57SLI lined up, answering the above questions will lead to more of them.
Regards, Carl-Daniel
Could someone please look at the mail quoted below? Thanks! Carl-Daniel
On 23.05.2007 00:22, Carl-Daniel Hailfinger wrote:
On 08.05.2007 22:45, ST wrote:
Hi Carl-Daniel
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Sorry for the delay, but i somehow missed your message.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Verifying a LB port is very interesting work and leads to lots of head scratching.
Here is a list of more problems, some really serious.
-00:06.0 0604: 10de:0370 (rev a2) (prog-if 01 [Subtractive decode]) +00:06.0 0604: 10de:0370 (rev a2) (prog-if 00 [Normal decode])
Does changed decode mean anything?
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-SERR- changed to SERR+.
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0sec-latency=32 probably had a reason in the vendor BIOS. Why change?
I/O behind bridge: 00008000-00008fff
I/O behind bridge: 0000f000-00000fffThe LinuxBIOS I/O range is backwards (end before start) and has a different size. Same for other I/O ranges.
Memory behind bridge: fb000000-fcffffff
Memory behind bridge: fff00000-000fffffThe LinuxBIOS memory range is backwards and has a different size. Same for other mem ranges.
Prefetchable memory behind bridge: 50000000-500fffff
Prefetchable memory behind bridge: fff00000-000fffffSame here.
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-Parity- changed to Parity+.
Other devices had the same classes of problems. I'd like to get an explanation for all of the above to be able to correct some of the differences.
I have at least one patch for the GA-M57SLI lined up, answering the above questions will lead to more of them.
Regards, Carl-Daniel
Yinghai, can you look at the mail below?
ST/Ward, can you apply the attached patch and then post a LB boot log on a GA-M57SLI with BIOS_DEBUG or BIOS_SPEW and additionally dmasg and lspci -vvvnx from the same boot? This would help greatly to clear up the resource confusion.
Regards, Carl-Daniel
On 23.05.2007 00:22, Carl-Daniel Hailfinger wrote:
On 08.05.2007 22:45, ST wrote:
Hi Carl-Daniel
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Sorry for the delay, but i somehow missed your message.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Verifying a LB port is very interesting work and leads to lots of head scratching.
Here is a list of more problems, some really serious.
-00:06.0 0604: 10de:0370 (rev a2) (prog-if 01 [Subtractive decode]) +00:06.0 0604: 10de:0370 (rev a2) (prog-if 00 [Normal decode])
Does changed decode mean anything?
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-SERR- changed to SERR+.
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0sec-latency=32 probably had a reason in the vendor BIOS. Why change?
I/O behind bridge: 00008000-00008fff
I/O behind bridge: 0000f000-00000fffThe LinuxBIOS I/O range is backwards (end before start) and has a different size. Same for other I/O ranges.
Memory behind bridge: fb000000-fcffffff
Memory behind bridge: fff00000-000fffffThe LinuxBIOS memory range is backwards and has a different size. Same for other mem ranges.
Prefetchable memory behind bridge: 50000000-500fffff
Prefetchable memory behind bridge: fff00000-000fffffSame here.
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-Parity- changed to Parity+.
Other devices had the same classes of problems. I'd like to get an explanation for all of the above to be able to correct some of the differences.
I have at least one patch for the GA-M57SLI lined up, answering the above questions will lead to more of them.
Regards, Carl-Daniel
--- src/devices/device_util.c (Revision 2727) +++ src/devices/device_util.c (Arbeitskopie) @@ -467,10 +467,11 @@ #endif } printk_debug( - "%s %02x <- [0x%010Lx - 0x%010Lx] %s%s%s\n", + "%s %02x <- [0x%010Lx - 0x%010Lx] size 0x%08Lx gran 0x%02x %s%s%s\n", dev_path(dev), resource->index, base, end, + resource->size, resource->gran, buf, resource_type(resource), comment);
On 6/20/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Yinghai, can you look at the mail below?
ST/Ward, can you apply the attached patch and then post a LB boot log on a GA-M57SLI with BIOS_DEBUG or BIOS_SPEW and additionally dmasg and lspci -vvvnx from the same boot? This would help greatly to clear up the resource confusion.
Regards, Carl-Daniel
On 23.05.2007 00:22, Carl-Daniel Hailfinger wrote:
On 08.05.2007 22:45, ST wrote:
Hi Carl-Daniel
could someone with a GA-M57SLI please post a lspci -vvvnx to the list, preferably both under LB and factory BIOS? I'm trying to verify some code I wrote.
Sorry for the delay, but i somehow missed your message.
Attached to this mail you will find the output of lspci -vvvnx under the original bios version f8 and under linuxbios updated from today (2007-05-08).
Verifying a LB port is very interesting work and leads to lots of head scratching.
Here is a list of more problems, some really serious.
-00:06.0 0604: 10de:0370 (rev a2) (prog-if 01 [Subtractive decode]) +00:06.0 0604: 10de:0370 (rev a2) (prog-if 00 [Normal decode])
Does changed decode mean anything?
LPC/PCI, there are some conf. Some MB could let you select the conf on decoding in BIOS.
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-SERR- changed to SERR+.
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0sec-latency=32 probably had a reason in the vendor BIOS. Why change?
We don't touch it, Kernel driver will fix it if necessery.
I/O behind bridge: 00008000-00008fff
I/O behind bridge: 0000f000-00000fffThe LinuxBIOS I/O range is backwards (end before start) and has a different size. Same for other I/O ranges.
mean it is disabled for that device.
Memory behind bridge: fb000000-fcffffff
Memory behind bridge: fff00000-000fffffThe LinuxBIOS memory range is backwards and has a different size. Same for other mem ranges.
Prefetchable memory behind bridge: 50000000-500fffff
Prefetchable memory behind bridge: fff00000-000fffffSame here.
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-Parity- changed to Parity+.
On Wed, Jun 20, 2007 at 05:15:17PM +0200, Carl-Daniel Hailfinger wrote:
can you apply the attached patch and then post a LB boot log on a GA-M57SLI with BIOS_DEBUG or BIOS_SPEW and additionally dmasg and lspci -vvvnx from the same boot? This would help greatly to clear up the resource confusion.
Hi Daniel,
find attached the dmesg, lspci and serial console log. I added dmesg and lspci of the prop. Bios (Version F8). Hope it's usefull.
Regards,
Andi
--- src/devices/device_util.c (Revision 2727) +++ src/devices/device_util.c (Arbeitskopie) @@ -467,10 +467,11 @@ #endif } printk_debug(
"%s %02x <- [0x%010Lx - 0x%010Lx] %s%s%s\n",
"%s %02x <- [0x%010Lx - 0x%010Lx] size 0x%08Lx gran 0x%02x %s%s%s\n", dev_path(dev), resource->index, base, end,resource->size, resource->gran, buf, resource_type(resource), comment);
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
All right Carl-Daniel, find a boot log, dmesg and lspci -vvvnx attached after running with your patch.
Thanks, Ward.
On Wed, Jun 20, 2007 at 05:15:17PM +0200, Carl-Daniel Hailfinger wrote:
Yinghai, can you look at the mail below?
ST/Ward, can you apply the attached patch and then post a LB boot log on a GA-M57SLI with BIOS_DEBUG or BIOS_SPEW and additionally dmasg and lspci -vvvnx from the same boot? This would help greatly to clear up the resource confusion.
Regards, Carl-Daniel
-
Andreas B. Mundt -
Carl-Daniel Hailfinger -
Corey Osgood -
Peter Stuge -
ST -
Stefan Reinauer -
Ward Vandewege -
yhlu