* ok, which wise guy did this?
@ 2003-01-22 11:47 jamal
2003-01-22 12:13 ` Chris Wedgwood
2003-01-22 12:15 ` Padraig
0 siblings, 2 replies; 4+ messages in thread
From: jamal @ 2003-01-22 11:47 UTC (permalink / raw)
To: netdev; +Cc: linux-kernel
I just booted my spanking new P4 HT PC last night using 2.5.58
and to my dissapointment the enumeration of the ethx devices is
reversed. I have 5 ethernet ports on this; eth0-4 on 2.4.x are now listed
as eth4-0. This is rude.
I immediately pointed a finger at monsieur J Garzik (thinking ethernet,
PCI enumeration hmm) but he has denied any responsibility ;-> ;-> He
thinks it may be the sysfs people.
Can anyone give justification for this? Regardless of justification
can we have some form of backward compatibility flag?
cheers,
jamal
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ok, which wise guy did this?
2003-01-22 11:47 ok, which wise guy did this? jamal
@ 2003-01-22 12:13 ` Chris Wedgwood
2003-01-22 12:15 ` Padraig
1 sibling, 0 replies; 4+ messages in thread
From: Chris Wedgwood @ 2003-01-22 12:13 UTC (permalink / raw)
To: jamal; +Cc: netdev, linux-kernel
On Wed, Jan 22, 2003 at 06:47:35AM -0500, jamal wrote:
> Can anyone give justification for this?
different bioses enumerate devices differently?
> Regardless of justification can we have some form of backward
> compatibility flag?
can you check if the bios is enumerating the devices the same way the
kernel presents them?
--cw
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ok, which wise guy did this?
2003-01-22 11:47 ok, which wise guy did this? jamal
2003-01-22 12:13 ` Chris Wedgwood
@ 2003-01-22 12:15 ` Padraig
1 sibling, 0 replies; 4+ messages in thread
From: Padraig @ 2003-01-22 12:15 UTC (permalink / raw)
To: jamal; +Cc: netdev, linux-kernel
jamal wrote:
> I just booted my spanking new P4 HT PC last night using 2.5.58
> and to my dissapointment the enumeration of the ethx devices is
> reversed. I have 5 ethernet ports on this; eth0-4 on 2.4.x are now listed
> as eth4-0. This is rude.
If you depend on the order then you must explicitly name the devices
like you want. I've done something like this in the past.
ip link set dev eth0 name interface-1
ip link set dev eth1 name interface-2
I guess you could use a temp name and keep the eth[0-4]
naming if you prefer.
Pádraig.
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: ok, which wise guy did this?
@ 2003-01-22 16:19 Larry Sendlosky
0 siblings, 0 replies; 4+ messages in thread
From: Larry Sendlosky @ 2003-01-22 16:19 UTC (permalink / raw)
To: jamal, netdev; +Cc: linux-kernel
Didn't the same thing happen in the 2.2 -> 2.4
transition? I believe it was for all PCI devices.
And I thought there was a boot arg something
like pci=reverse. Does it still exist?
larry
-----Original Message-----
From: jamal [mailto:hadi@cyberus.ca]
Sent: Wednesday, January 22, 2003 6:48 AM
To: netdev@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: ok, which wise guy did this?
I just booted my spanking new P4 HT PC last night using 2.5.58
and to my dissapointment the enumeration of the ethx devices is
reversed. I have 5 ethernet ports on this; eth0-4 on 2.4.x are now listed
as eth4-0. This is rude.
I immediately pointed a finger at monsieur J Garzik (thinking ethernet,
PCI enumeration hmm) but he has denied any responsibility ;-> ;-> He
thinks it may be the sysfs people.
Can anyone give justification for this? Regardless of justification
can we have some form of backward compatibility flag?
cheers,
jamal
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-01-22 16:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-22 11:47 ok, which wise guy did this? jamal
2003-01-22 12:13 ` Chris Wedgwood
2003-01-22 12:15 ` Padraig
-- strict thread matches above, loose matches on Subject: below --
2003-01-22 16:19 Larry Sendlosky
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox