On Sun, Feb 11, 2007 at 10:06:41PM -0700, Gordon Farquharson wrote:
On 2/10/07, Gordon Farquharson [EMAIL PROTECTED] wrote:
On 1/18/07, Martin Michlmayr [EMAIL PROTECTED] wrote:
Well, I still believe this is a problem with udev. CCing Marco.
I just tested a patch [1,2] that was applied to
On Feb 12, Steve Langasek [EMAIL PROTECTED] wrote:
The problem seems as simple as that the ipx4xx driver is *not* included in
d-i, but is included in the installed kernel; so in the installer, the
module is never loaded resulting in the USB adapter getting the eth0 name,
but after a reboot
On Mon, Feb 12, 2007 at 10:40:39AM +0100, Marco d'Itri wrote:
On Feb 12, Steve Langasek [EMAIL PROTECTED] wrote:
The problem seems as simple as that the ipx4xx driver is *not* included in
d-i, but is included in the installed kernel; so in the installer, the
module is never loaded
On Feb 12, Steve Langasek [EMAIL PROTECTED] wrote:
No, wait... When a new network interface is added it will get the next
available name, this is a supported configuration.
Ok, so this is true when the built-in device is loaded first at boot time
and is initially assigned eth0, there is no
Hi Steve
On 2/12/07, Steve Langasek [EMAIL PROTECTED] wrote:
The problem seems as simple as that the ipx4xx driver is *not* included in
d-i, but is included in the installed kernel; so in the installer, the
module is never loaded resulting in the USB adapter getting the eth0 name,
but after a
On Feb 12, Gordon Farquharson [EMAIL PROTECTED] wrote:
Will udev add this new rule to
/etc/udev/rules.d/z25_persistent-net.rules ? Since no new rules are
Yes, this is the whole point.
being added on my test system, does this tells whether something like
DRIVERS==?* is matching or not ?
Hi Marco
On 2/12/07, Marco d'Itri [EMAIL PROTECTED] wrote:
On Feb 12, Steve Langasek [EMAIL PROTECTED] wrote:
No, wait... When a new network interface is added it will get the next
available name, this is a supported configuration.
Ok, so this is true when the built-in device is loaded
Hi Marco
On 2/12/07, Marco d'Itri [EMAIL PROTECTED] wrote:
being added on my test system, does this tells whether something like
DRIVERS==?* is matching or not ?
Apparently not. I see that I already suggested this in my first
reply on december 14.
Yeah, your comment in your previous email
severity 407460 important
reassign 407460 nic-usb-modules-2.6.18-4-ixp4xx-di
thanks
On Mon, Feb 12, 2007 at 11:56:06AM -0700, Gordon Farquharson wrote:
The problem seems as simple as that the ipx4xx driver is *not* included in
d-i, but is included in the installed kernel; so in the installer,
Processing commands for [EMAIL PROTECTED]:
severity 407460 important
Bug#407460: USB ethernet interface renamed after installation on NSLU2 which
causes the system to be inaccessible
Severity set to `important' from `serious'
reassign 407460 nic-usb-modules-2.6.18-4-ixp4xx-di
Bug#407460: USB
Hi Marco
On 2/10/07, Gordon Farquharson [EMAIL PROTECTED] wrote:
On 1/18/07, Martin Michlmayr [EMAIL PROTECTED] wrote:
Well, I still believe this is a problem with udev. CCing Marco.
I just tested a patch [1,2] that was applied to udev to fix the
network interface renaming code to see if
On 1/18/07, Martin Michlmayr [EMAIL PROTECTED] wrote:
Well, I still believe this is a problem with udev. CCing Marco.
Marco, a while ago, you suggested that the problem could be due to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389250
but I still see the problem with 2.6.20 which
However, when booting after the installation, the NPE driver seems to
assume control of the interface name eth0, which causes something to
rename the interface of the USB to ethernet adapter to eth1_rename.
it sounds to me like the built in nic is getting detected first before the USB
to
Package: debian-installer
Version: 20061102
Severity: serious
I'm not sure which package to assign this bug to, but since it causes
the system to be inaccessible after an install, debian-installer seems
like a good place to start.
Summary of the problem:
After an installation of Debian on the
* Gordon Farquharson [EMAIL PROTECTED] [2007-01-18 08:57]:
I'm not sure which package to assign this bug to, but since it causes
the system to be inaccessible after an install, debian-installer seems
like a good place to start.
Well, I still believe this is a problem with udev. CCing Marco.
15 matches
Mail list logo
