[coreboot] NIC working, IP assigned but not connected.
Knut Kujat
knuku at gap.upv.es
Tue Jan 19 13:15:48 CET 2010
Knut Kujat escribió:
> Sorry,
> forgot to attach the file!
>
> bye
> Knut Kujat escribió:
>
>> Hi,
>>
>> I already managed to get IRQs assigned for my two NICs. As happy as I
>> was about that I asked for a IP to test if the board works correctly
>> so I booted with coreboot into my suse 11.2 made a ifconfig and saw
>> that i've got a valid IP, Mask everthing set up fine through DHCP. But
>> I'm unable to connect to whatever I can't do pings, navigation just
>> nothing. I of course did pings with ip addresses to see if it maybe
>> only a DNS issue but its not, the weird part is that the DNS servers
>> get well configured by the DHCP server.
>>
>> I did test with the factory BIOS and I get the exact same network
>> configuration and it actually works.
>>
>> The only difference I could see are shown below:
>>
>> _Factory BIOS:
>> _
>> Setting up (localfs) network interfaces:
>> lo
>> lo IP address: 127.0.0.1/8
>> IP address: 127.0.0.2/8
>> lo
>> doneok
>> eth0 device: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03)
>> [ 14.435358] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
>> Control: RX/TX <-------- This line doesn't show up when booting
>> with coreboot
>> [ 14.435981] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 14.441734] ADDRCONF(NETDEV_CHANGE): eth0: link becomes
>> ready <--------- This line doesn't show up when
>> booting with coreboot
>> eth0 Starting DHCP4 client[ 14.968730] NET: Registered
>> protocol family 17 <--------- Start immediately not so with
>> coreboot
>> .
>> eth0 IP address: ###.##.##.###/##
>> (####.gap.upv.es) <---------
>> I scrambled the IP
>> eth0
>> done eth1 device: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03)
>> No configuration found for eth1
>> eth1
>> unusedSetting up service (localfs) network . . . . . . . . .
>> .done
>>
>> _Coreboot:_
>>
>> eth0 device: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03)
>> [ 16.448334] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> eth0 Starting DHCP4 client[ 17.260820] NET: Registered
>> protocol family 17
>> [ 17.351033] pci 0000:01:01.0: using bridge 0000:00:07.0 INT B to
>> get IRQ 19
>> [ 17.393206] pci 0000:01:01.0: PCI->APIC IRQ transform: INT B -> IRQ
>> 19 ok
>> . . . . . . . .
>> eth0 DHCP4 client NOT running
>> eth0
>> failed eth1 device: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03)
>> No configuration found for eth1
>> eth1
>> unusedWaiting for mandatory devices: eth0 __NSC__
>> 3 2 0
>> eth0 device: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03)
>> eth0 DHCP4 client (dhcpcd) is running
>> eth0 . . . but is still waiting for data
>> eth0 IP address: 1##.##.##.###/##
>> <------- Finally it gets
>> the IP assign
>> eth0
>> waiting
>> eth0 interface could not be set up until now
>> failedSetting up service (localfs) network . . . . . . . . .
>> .failed
>>
>> I already added the network option rom obtained from the original BIOS
>> rom to the Coreboot rom but no changes.
>>
>> Please find attached the whole coreboot log for more info.
>>
>> I have no idea what possibly could be wrong so I'm open and grateful
>> for every comment.
>>
>> THX in advanced,
>> Knut Kujat.
>>
>>
>
>
Never mind! I solved it. I got the wrong IRQ assign to the NIC but thats
because...
smp_write_intsrc(mc, mp_INT, MP_IRQ_TRIGGER_LEVEL|MP_IRQ_POLARITY_LOW,
m->bus_8132_2, (3<<2)|0, m->apicid_8132_2,0x0);
when I assign a 0x0 in that line I actually get irq 31 assign to the
NIC. So I guess there is some sort of conversation to do here because
what I need is IRQ 5 for the NIC not 31 (even if 31 seems to work fine).
THX,
Knut Kujat.
More information about the coreboot
mailing list