Bug#408818: d-i: needing parameter interface=eth0

[stappers@stappers.nl (Geert Stappers)]

Op 28-01-2007 om 23:07 schreef Rick Thomas:
> 
> 
> Does looking closely at what Phill supplied for his original report  
> help any?:
> 
> >Output of lspci -nn and lspci -vnn:
> >phill:/home/phill# lspci -nn
> >... <snip> ...
> >00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102  
> >[Rhine-II] [1106:3065] (rev 7c)
> >... <snip>
> >
> >Output of lspci -vnn:
> >phill:/home/phill# lspci -vnn
> >...<snip>...
> >00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102  
> >[Rhine-II] [1106:3065] (rev 7c)
> >        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:80ed]
> >        Flags: bus master, medium devsel, latency 64, IRQ 217
> >        I/O ports at d800 [size=256]
> >        Memory at febff800 (32-bit, non-prefetchable) [size=256]
> >        Capabilities: [40] Power Management version 2
> >...<snip>
> 
> I'm not enough of a PCI hardware guru to know if this is going to be  
> recognized as a NIC.  Anybody else?

It is a NIC. Later in the install process it becomes eth1.

> Also, I saw a bunch of PCI bridges and so on.  Is is possible that  
> the NIC is on the far side of one of them and that's confusing the  
> issue?  Or am I talking total nonsense?
> 
> Just a thought...

That is also how I see it.


HtH
GSt