Anaconda multiple Ethernet cards question
Till Maas
opensource at till.name
Wed Sep 23 12:53:06 UTC 2009
On Thu, Sep 24, 2009 at 11:35:19AM +0300, Aioanei Rares wrote:
> Till Maas wrote:
>> On Mon, Sep 21, 2009 at 11:20:59AM +0300, Aioanei Rares wrote:
>>
>>> On 09/21/2009 08:53 AM, nodata wrote:
>>>
>>>> Am Montag, den 21.09.2009, 02:07 +0200 schrieb Benny Amorsen:
>>>>
>>>>> Aioanei Rares<schaiba at gmail.com> writes:
>>>>>
>>>>>
>>>>>> I think it would be niftier if the identification string of the card
>>>>>> was printed also (eg VIA Rhine III) so people would know what card to
>>>>>> choose and how.
>>>>>>
>>>>> For extra points, add a "identify nic" button which blinks the LED's of
>>>>> the appropriate nic.
>>>>>
>>>> Doesn't the "identify" button in Anaconda already do this?
>>>>
>>>>
>>> Yes, it does, but like I said, it only works if one has an Ethernet
>>> cable with signal coming from it plugged in.
>>>
>>
>> On my X41 thinkpad "ethtool -p eth0" works without any attached network cable
>> to identify it. So it might be either a bug in anaconda or thr NIC might
>> not be able to do this.
> Both my NICs are capable of this as Debian is listing their names in the
> installer, so do the *BSDs.
There seems to be a misunderstanding. I wrote about making the LEDs of
the NIC blink to identify them, not about getting a string that
describes them. You can test this with "ethtool -p eth1" and look at the
LEDs.
Regards
Till
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20090923/98a926ea/attachment.bin
More information about the devel
mailing list