Frans Pop a écrit : > On Tuesday 30 December 2008, M.-A. DARCHE wrote: >> Comments/Problems: >> The installation could not go on due to the fact that the DHCP server >> from the SpeedTouch 530 router modem was not found. No lease could be >> obtained from it. I have retried many times, even providing a machine >> name along. So no network, no time server found, no mirror available. > > It looks like the hardware-summary was made on the (already installed) > Etch system. Is that correct? > It is. You are right. I thought that using reportbug package might provide useful information. > From the loaded modules in that summary, I see that you use PPPoE, but > I see no sign of PPPoE support in the installation log. If you need > PPPoE support, please try booting with the following boot parameter: > modules=ppp-udeb > I used to rely on PPPoE on the Etch system but from some weeks I am only using the router modem as a DHCP server on that Etch system. And this is like this that I was intending to install and use the new Lenny system. The "modules=ppp-udeb" boot parameter I know of as it is how I have installed the Etch system. >> The problem might be that the debian-installer gets confused by the >> fact that there are 2 network interfaces on this machine: a classical >> Ethernet card and a FireWire card (that I don't use). > > That's not it. From your syslog: > >> Dec 30 01:10:39 kernel: [ 214.500529] forcedeth 0000:00:08.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:16:e6:86:b1:02 >> Dec 30 01:10:39 kernel: [ 214.500535] forcedeth 0000:00:08.0: highdma csum vlan pwrctl mgmt timirq gbit lnktim msi desc-v3 >> Dec 30 01:10:39 net/hw-detect.hotplug: Detected hotpluggable network interface eth0 >> Dec 30 01:10:40 kernel: [ 215.252106] ieee1394: Host added: ID:BUS[0-00:1023] GUID[0016e65600b9dd23] >> Dec 30 01:10:42 hw-detect: insmod /lib/modules/2.6.26-1-486/kernel/drivers/ieee1394/sbp2.ko >> Dec 30 01:10:42 kernel: [ 217.008577] eth1394: eth1: IPv4 over IEEE 1394 (fw-host0) >> Dec 30 01:10:42 hw-detect: insmod /lib/modules/2.6.26-1-486/kernel/drivers/ieee1394/eth1394.ko >> Dec 30 01:10:42 net/hw-detect.hotplug: Detected hotpluggable network interface eth1 > [...] >> Dec 30 01:10:53 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port67 interval 7 >> Dec 30 01:11:00 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 > > So, the forcedeth card is eth0 and the firewire one is eth1, and DHCP > is trying correctly on eth0. > I thought this might be the cause of the issue because on the Etch system the ethernet card is seen as eth1. Could there be a problem in the way the ethernet card is labeled or tracked by the installer? If so, is there a way to make the dhcpdiscover try on all available interfaces instead of only the one detected/selected? Best and warm regards, -- Marc-Aurèle DARCHE AFUL <http://www.aful.org/> Association Francophone des Utilisateurs de Linux/Logiciels Libres French speaking Linux and Libre Software Users' Association
Attachment:
signature.asc
Description: OpenPGP digital signature