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 L
* 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 Marc
> 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 et
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 in
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
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
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 rebo
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
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 i
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 e
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
Gordon Farquharson wrote:
> 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 th
Steve Langasek wrote:
> severity 407460 important
> reassign 407460 nic-usb-modules-2.6.18-4-ixp4xx-di
> thanks
What does nic-usb-modules-2.6.18-4-ixp4xx-di have to do with this?
--
see shy jo
signature.asc
Description: Digital signature
* Joey Hess <[EMAIL PROTECTED]> [2007-02-13 15:24]:
> Er, it is included in d-i:
No, nic-modules is not included on the ixp4xx image.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Martin Michlmayr wrote:
> * Joey Hess <[EMAIL PROTECTED]> [2007-02-13 15:24]:
> > Er, it is included in d-i:
>
> No, nic-modules is not included on the ixp4xx image.
So the right package is debian-installer and the bug can be fixed by
adding nic-modules?
--
see shy jo
On Tue, Feb 13, 2007 at 03:27:36PM -0500, Joey Hess wrote:
> Steve Langasek wrote:
> > severity 407460 important
> > reassign 407460 nic-usb-modules-2.6.18-4-ixp4xx-di
> > thanks
> What does nic-usb-modules-2.6.18-4-ixp4xx-di have to do with this?
Is ixp4xx the flavor used for installs on NSLU2?
* Joey Hess <[EMAIL PROTECTED]> [2007-02-13 15:38]:
> > No, nic-modules is not included on the ixp4xx image.
>
> So the right package is debian-installer and the bug can be fixed by
> adding nic-modules?
No. If nic-modules is included (and hence the ixp4xx ethernet
driver), USB will get eth1 and
* Steve Langasek <[EMAIL PROTECTED]> [2007-02-13 12:54]:
> Is ixp4xx the flavor used for installs on NSLU2? In testing there was an
> nslu2 flavor, but that's no longer present in unstable.
>
> I understood that ixp4xx is the flavor being used.
ixp4xx is the platform and NSLU2 is one ixp4xx devi
Martin Michlmayr wrote:
> No. If nic-modules is included (and hence the ixp4xx ethernet
> driver), USB will get eth1 and the installer won't work at all because
> it will use eth0, which is the ixp4xx device that doesn't work because
> of the missing microcode.
I take it that netcfg's use of link
* Joey Hess <[EMAIL PROTECTED]> [2007-02-13 16:27]:
> I take it that netcfg's use of link detection doesn't make it default to
> eth1 in this case?
No, oldsys-preseed always sets netcfg/choose_interface. Although now
I'm starting to wonder whether this is a good idea...
> The rule could go in ro
* Joey Hess <[EMAIL PROTECTED]> [2007-02-13 18:15]:
> > And then the unofficial ixp4xx image which contains the microcode
> > would simply need to remove that file from the initramfs.
>
> There are other arm machines that use ixp4xx ethernet though.
So? None of them will work without the proprie
* Martin Michlmayr <[EMAIL PROTECTED]> [2007-02-13 23:18]:
> So? None of them will work without the proprietary microcode that
> cannot be included in Debian.
(In theory, there could be a IXP4xx based device that contains the
microcode in flash; but the ixp4xx driver in Debian doesn't allow
loadi
Martin Michlmayr wrote:
> The rule Gordon suggested could be included on all arm machines since
> it mentions the ixp4xx driver:
>
> # Built-in Ethernet Adapter (NPE-B microcode not present)
> SUBSYSTEM=="net", DRIVERS=="ixp4xx_mac", NAME="eth1"
>
> And then the unofficial ixp4xx image which cont
On Tue, Feb 13, 2007 at 06:15:47PM -0500, Joey Hess wrote:
> > The rule Gordon suggested could be included on all arm machines since
> > it mentions the ixp4xx driver:
> > # Built-in Ethernet Adapter (NPE-B microcode not present)
> > SUBSYSTEM=="net", DRIVERS=="ixp4xx_mac", NAME="eth1"
> > And th
Hi Martin
I'm CC'ing this message to debian-boot because we may like to get this
fix into RC2.
On 2/13/07, Martin Michlmayr <[EMAIL PROTECTED]> wrote:
Anyway, I'm away from my slug for the next 3 weeks, but maybe someone
can try adding such a udev rule and the nic-modules udeb and see
whether i
Hi Martin
I tried a build of the installer from trunk (revision 45431) and
nearly fell of my chair:
---
[!!] Install the base system
Unable to install initramfs-tools
An error was returned while trying to install the initramfs-tools
package onto the target system.
Check /var/log/syslog or see v
On 2/25/07, Gordon Farquharson <[EMAIL PROTECTED]> wrote:
How about the following idea for a quick and simple workaround to this
problem (it is based on something Steve suggested earlier in the
thread).
Include the ixp4xx NPE driver modules in both the official and
unofficial installer images a
* Gordon Farquharson <[EMAIL PROTECTED]> [2007-02-25 23:19]:
> + if [ -h /lib/firmware/NPE-B ]; then
> + INTERFACE=eth0
> + else
> + INTERFACE=eth1
> +
On Monday 26 February 2007 17:29, Martin Michlmayr wrote:
> I'm happy to make this change if Frans thinks that it's not too late
> to do it. (FWIW, I can guarantee that changes proposed by Gordon are
> fully tested.)
It's up to you, but please be very quick and make sure that it does not
cause r
* Frans Pop <[EMAIL PROTECTED]> [2007-02-26 17:35]:
> It's up to you, but please be very quick and make sure that it does
> not cause regressions as RC2 will be very soon now, so
> reverting/fixing it may not be possible.
OK, done. I also asked Gordon to test it again.
--
Martin Michlmayr
http:/
* Gordon Farquharson <[EMAIL PROTECTED]> [2007-02-26 23:10]:
> 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
> Need to get 932kB of archives.
> After unpacking 2541kB of additional disk space will be used.
> WARNING: The following packages cannot be authenticated!
> libvolume-id0
Gordon Farquharson wrote:
> I tried a build of the installer from trunk (revision 45431) and
> nearly fell of my chair:
Known problem at the top of DebianInstaller/Today in the wiki.
--
see shy jo
signature.asc
Description: Digital signature
On Feb 27, 2007, at 6:23 PM, Joey Hess wrote:
Gordon Farquharson wrote:
I tried a build of the installer from trunk (revision 45431) and
nearly fell of my chair:
Known problem at the top of DebianInstaller/Today in the wiki.
I don't see any reference at all on the wiki to Gordon Farquharso
On Monday 16 April 2007 19:46, Markus Knapp wrote:
> Last week I got a new NSLU2, took the new install-image from
> http://www.slug-firmware.net/d-dls.php and tried to install.
> Hardly everithing went good till the installation of the base system.
> There I got the same error as mentioned here:
>
Am 16.04.2007 um 20:43 schrieb Frans Pop:
On Monday 16 April 2007 19:46, Markus Knapp wrote:
Last week I got a new NSLU2, took the new install-image from
http://www.slug-firmware.net/d-dls.php and tried to install.
Hardly everithing went good till the installation of the base system.
There I go
On Monday 16 April 2007 20:56, Markus Knapp wrote:
> Sounds good. But is there any list around where I can see what
> mirrors only support IPv4? Preferable european mirrors.
> Or do I have to try and error? One install run takes about half an
> hour so that wouldn't be a good option.
Most don't. U
On Monday 16 April 2007 22:11, Markus Knapp wrote:
> Tried that but still the same problem.
No, different problem.
> I'll add the complete syslog, perhaps someone knows what's going wrong.
> Apr 16 21:20:07 net-retriever: gpgv:
> Apr 16 21:20:07 net-retriever: Signature made Sun Apr 8 09:38:40
>
* Frans Pop <[EMAIL PROTECTED]> [2007-04-16 22:29]:
> Looks like an essential GPG key is missing in that image. The people
> who built this image will have to look into that.
>
> Martin, can you pick up on this?
Hmm, someone else reported this but I don't quite understand why
people would see thi
On Monday 16 April 2007 19:46, Markus Knapp wrote:
> Apr 14 13:25:00 base-installer: Err http://ftp.se.debian.org etch
> Release.gpg
> Apr 14 13:25:00 base-installer: Could not create a socket for
> 2001:6b0:e:2018::137 (f=10 t=1 p=6) - socket (97 Address family not
> supported by protocol) [IP: 20
Hi Frans
On Apr 16, 9:31 pm, Frans Pop <[EMAIL PROTECTED]> wrote:
> Just tried if I could reproduce this IPv6 problem and I cannot, at least
> not by just pointing an install to this same mirror and not even after
> manually loading the ipv6-modules udeb.
> Wonder if that too is something specifi
On Wednesday 18 April 2007 15:40, Gordon Farquharson wrote:
> Martin Guy reported that he gets these messages when using a kernel
> that didn't have IPv6 support compiled in, which seems like it would
> make sense.
Huh? Do any debian kernels have IPv6 compiled in then?
I tested with i386 which onl
Hi Frans
On Apr 18, 8:30 am, Frans Pop <[EMAIL PROTECTED]> wrote:
> Huh? Do any debian kernels have IPv6 compiled in then?
Probably not (I haven't checked), but I think what he meant by
"compiled in" could refer literately to compiled in or loaded as a
module. Sorry for the sloppy wording.
> An
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-ixp4
Hi there!
Last week I got a new NSLU2, took the new install-image from
http://www.slug-firmware.net/d-dls.php and tried to install.
Hardly everithing went good till the installation of the base system.
There I got the same error as mentioned here:
initramfs-tools could not be installed.
Any n
Hi Markus
On 4/16/07, Markus Knapp <[EMAIL PROTECTED]> wrote:
Last week I got a new NSLU2, took the new install-image from
http://www.slug-firmware.net/d-dls.php and tried to install.
Hardly everithing went good till the installation of the base system.
There I got the same error as mentioned he
48 matches
Mail list logo
