i82801xx nic problems.

Hello,
I am racking my brains with this. No matter what I do I can't seem to  
get the nic working. The nic is onboard the i82801DB southbridge down  
from the PCI bridge, so my Config.lb looks something like this:

device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
chip drivers/pci/onboard
device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet  
Controller
end
end

But no matter what I try coreboot thinks it is a static device and  
disables it.

do_pci_scan_bridge for PCI: 00:1e.0
PCI: pci_scan_bus for bus 01
PCI: devfn 0x0, bad id 0xffffffff
PCI: devfn 0x8, bad id 0xffffffff
PCI: devfn 0x10, bad id 0xffffffff
PCI: devfn 0x18, bad id 0xffffffff
PCI: devfn 0x20, bad id 0xffffffff
PCI: devfn 0x28, bad id 0xffffffff
PCI: devfn 0x30, bad id 0xffffffff
PCI: devfn 0x38, bad id 0xffffffff
Disabling static device: PCI: 01:08.0

This wouldn't really be a problem if Linux detected it but that is not  
even happening. I am really stumped here. I even tried loading the  
Intel Boot Agent pci rom from the original bios but the same thing  
happens. Help?
Thanks - Joe

[Corey Osgood]

On Jan 30, 2008 9:50 AM,  wrote:
> Hello,
> I am racking my brains with this. No matter what I do I can't seem to
> get the nic working. The nic is onboard the i82801DB southbridge down
> from the PCI bridge, so my Config.lb looks something like this:
>
> device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> chip drivers/pci/onboard
> device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
> Controller
> end
> end

I think your config is wrong, and at the very least, you don't need the
"chip" line, unless you're loading a rom for it. Bear with me, I'm stuck in
windows atm, but I'm pretty sure it's lspci -t that shows how the devices
are connected. Might also be a good idea to look at the setup for another
board, perhaps the intel jarrell or xe7501devkit has an onboard nic

-Corey
> But no matter what I try coreboot thinks it is a static device and
> disables it.
>
> do_pci_scan_bridge for PCI: 00:1e.0
> PCI: pci_scan_bus for bus 01
> PCI: devfn 0x0, bad id 0xffffffff
> PCI: devfn 0x8, bad id 0xffffffff
> PCI: devfn 0x10, bad id 0xffffffff
> PCI: devfn 0x18, bad id 0xffffffff
> PCI: devfn 0x20, bad id 0xffffffff
> PCI: devfn 0x28, bad id 0xffffffff
> PCI: devfn 0x30, bad id 0xffffffff
> PCI: devfn 0x38, bad id 0xffffffff
> Disabling static device: PCI: 01:08.0
>
> This wouldn't really be a problem if Linux detected it but that is not
> even happening. I am really stumped here. I even tried loading the
> Intel Boot Agent pci rom from the original bios but the same thing
> happens. Help?
> Thanks - Joe

Quoting Corey Osgood :
> On Jan 30, 2008 9:50 AM,  wrote:
> > Hello,
> > I am racking my brains with this. No matter what I do I can't seem to
> > get the nic working. The nic is onboard the i82801DB southbridge down
> > from the PCI bridge, so my Config.lb looks something like this:
> >
> > device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> > chip drivers/pci/onboard
> > device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
> > Controller
> > end
> > end
>
> I think your config is wrong, and at the very least, you don't need the
> "chip" line, unless you're loading a rom for it. Bear with me, I'm stuck in
> windows atm, but I'm pretty sure it's lspci -t that shows how the devices
> are connected. Might also be a good idea to look at the setup for another
> board, perhaps the intel jarrell or xe7501devkit has an onboard nic

I tried it with and without with no luck.

lspci -t
+-1e.0-[0000:01]----08.0
> > But no matter what I try coreboot thinks it is a static device and
> > disables it.
> >
> > do_pci_scan_bridge for PCI: 00:1e.0
> > PCI: pci_scan_bus for bus 01
> > PCI: devfn 0x0, bad id 0xffffffff
> > PCI: devfn 0x8, bad id 0xffffffff
> > PCI: devfn 0x10, bad id 0xffffffff
> > PCI: devfn 0x18, bad id 0xffffffff
> > PCI: devfn 0x20, bad id 0xffffffff
> > PCI: devfn 0x28, bad id 0xffffffff
> > PCI: devfn 0x30, bad id 0xffffffff
> > PCI: devfn 0x38, bad id 0xffffffff
> > Disabling static device: PCI: 01:08.0
> >
> > This wouldn't really be a problem if Linux detected it but that is not
> > even happening. I am really stumped here. I even tried loading the
> > Intel Boot Agent pci rom from the original bios but the same thing
> > happens. Help?
> > Thanks - Joe

Quoting [e-mail]:
> Quoting Corey Osgood :
> > On Jan 30, 2008 9:50 AM,  wrote:
> > > Hello,
> > > I am racking my brains with this. No matter what I do I can't seem to
> > > get the nic working. The nic is onboard the i82801DB southbridge down
> > > from the PCI bridge, so my Config.lb looks something like this:
> > >
> > > device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> > > chip drivers/pci/onboard
> > > device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
> > > Controller
> > > end
> > > end
>
> lspci -t
> +-1e.0-[0000:01]----08.0
> > > But no matter what I try coreboot thinks it is a static device and
> > > disables it.
> > >
> > > do_pci_scan_bridge for PCI: 00:1e.0
> > > PCI: pci_scan_bus for bus 01
> > > Disabling static device: PCI: 01:08.0

Well, I think I may have figured this out???
When comparing the coreboot to original bios PCI Bridge 00:1e.0  
registers, it seems if the LAN controller wants use of the PCI bus it  
needs to request it. Kind of funny:-)
With coreboot register 0x82 (PCI_MAST_STS?PCI Master Status Register)  
is defaulted to 0x00. The original bios has bit 6 set (0x40), which is  
"The ICH4?s internal LAN controller has requested use of the PCI bus."  
So if I set this bit, coreboot should find the device when scanning  
the bus, correct?

I will try it out later tonight and report back.

Thanks - Joe

Quoting [e-mail]:
> Quoting [e-mail]:
> > Quoting Corey Osgood :
> > > On Jan 30, 2008 9:50 AM,  wrote:
> > > > Hello,
> > > > I am racking my brains with this. No matter what I do I can't seem to
> > > > get the nic working. The nic is onboard the i82801DB southbridge down
> > > > from the PCI bridge, so my Config.lb looks something like this:
> > > >
> > > > device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> > > > chip drivers/pci/onboard
> > > > device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
> > > > Controller
> > > > end
> > > > end
> >
> > lspci -t
> > +-1e.0-[0000:01]----08.0
> > > > But no matter what I try coreboot thinks it is a static device and
> > > > disables it.
> > > >
> > > > do_pci_scan_bridge for PCI: 00:1e.0
> > > > PCI: pci_scan_bus for bus 01
> > > > Disabling static device: PCI: 01:08.0
>
> Well, I think I may have figured this out???
> When comparing the coreboot to original bios PCI Bridge 00:1e.0
> registers, it seems if the LAN controller wants use of the PCI bus it
> needs to request it. Kind of funny:-)
> With coreboot register 0x82 (PCI_MAST_STS?PCI Master Status Register)
> is defaulted to 0x00. The original bios has bit 6 set (0x40), which is
> "The ICH4?s internal LAN controller has requested use of the PCI bus."
> So if I set this bit, coreboot should find the device when scanning the
> bus, correct?
>
> I will try it out later tonight and report back.

Nope no luck:-((((

Thanks - Joe

[Peter Stuge]

On Wed, Jan 30, 2008 at 09:50:08AM -0500, [e-mail] wrote:
> device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> chip drivers/pci/onboard
> device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
>
> do_pci_scan_bridge for PCI: 00:1e.0
> PCI: pci_scan_bus for bus 01
> PCI: devfn 0x38, bad id 0xffffffff
> Disabling static device: PCI: 01:08.0

It was mentioned a while ago that the PCI ids in debug output is
offset by one from the config ids. I don't know for sure, but it's
worth investigating.

//Peter

Quoting Peter Stuge :
> On Wed, Jan 30, 2008 at 09:50:08AM -0500, [e-mail] wrote:
> > device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> > chip drivers/pci/onboard
> > device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
> >
> > do_pci_scan_bridge for PCI: 00:1e.0
> > PCI: pci_scan_bus for bus 01
> > PCI: devfn 0x38, bad id 0xffffffff
> > Disabling static device: PCI: 01:08.0
>
> It was mentioned a while ago that the PCI ids in debug output is
> offset by one from the config ids. I don't know for sure, but it's
> worth investigating.
>
> //Peter

Hmm the correct device id is listed in pci_ids.h, is that what you mean?
I have a feeling that the nic is not powering on. With the original  
bios the lights on the nic come on about 3 seconds after power up.  
With coreboot there are no lights at all. I wonder if there is a  
register switch to turn it on???? I'm stumped.....I wonder if the guys  
at etherboot could help me???

Thanks - Joe

Quoting [e-mail]:
> Quoting Peter Stuge :
> > On Wed, Jan 30, 2008 at 09:50:08AM -0500, [e-mail] wrote:
> > > device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> > > chip drivers/pci/onboard
> > > device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
> > >
> > > do_pci_scan_bridge for PCI: 00:1e.0
> > > PCI: pci_scan_bus for bus 01
> > > PCI: devfn 0x38, bad id 0xffffffff
> > > Disabling static device: PCI: 01:08.0
> >
> > It was mentioned a while ago that the PCI ids in debug output is
> > offset by one from the config ids. I don't know for sure, but it's
> > worth investigating.
> >
> > //Peter
>
> Hmm the correct device id is listed in pci_ids.h, is that what you mean?
> I have a feeling that the nic is not powering on. With the original
> bios the lights on the nic come on about 3 seconds after power up.
> With coreboot there are no lights at all. I wonder if there is a
> register switch to turn it on???? I'm stumped.....I wonder if the guys
> at etherboot could help me???

How would do a dump of the nics eeprom in Linux? I'm thinking this is  
where the problem is coming from???

Thanks - Joe

[Corey Osgood]

Use awarddeco. afaik the site is down, but it must be mirrored somewhere.

On 1/31/08, [e-mail]  wrote:
> Quoting [e-mail]:
> > Quoting Peter Stuge :
> > > On Wed, Jan 30, 2008 at 09:50:08AM -0500, [e-mail]
>
> wrote:
> > > > device pci 1e.0 on # PCI bridge: Intel Corporation 82801 PCI Bridge
> > > > chip drivers/pci/onboard
> > > > device pci 08.0 on end # Intel Corporation 82801DB PRO/100 VE Ethernet
> > > >
> > > > do_pci_scan_bridge for PCI: 00:1e.0
> > > > PCI: pci_scan_bus for bus 01
> > > > PCI: devfn 0x38, bad id 0xffffffff
> > > > Disabling static device: PCI: 01:08.0
> > >
> > > It was mentioned a while ago that the PCI ids in debug output is
> > > offset by one from the config ids. I don't know for sure, but it's
> > > worth investigating.
> > >
> > > //Peter
> >
> > Hmm the correct device id is listed in pci_ids.h, is that what you mean?
> > I have a feeling that the nic is not powering on. With the original
> > bios the lights on the nic come on about 3 seconds after power up.
> > With coreboot there are no lights at all. I wonder if there is a
> > register switch to turn it on???? I'm stumped.....I wonder if the guys
> > at etherboot could help me???
>
> How would do a dump of the nics eeprom in Linux? I'm thinking this is
> where the problem is coming from???
>
> Thanks - Joe

Quoting Corey Osgood :
> > How would do a dump of the nics eeprom in Linux? I'm thinking this is
> > where the problem is coming from???
>
> Use awarddeco. afaik the site is down, but it must be mirrored somewhere.

Huh? How do I do a register dump of the eeprom with awarddeco? That  
would be for  getting the pci rom. I already have the the pci rom, and  
an AMI bios not Award. But, that doesn't matter to coreboot because it  
won't load a pci rom for a device that it can't detect. I wonder if  
there is a way to load the pci rom before the bus scan. I'm thinking  
the original bios does that, and the pci rom acually turns on the  
device and sets up it's registers. Anyone want to take a shot here???

Thanks - Joe