Bug#350912: network doesnt work working version is unknown (closed)

2006-02-05 Thread Geert Stappers
On Sun, Feb 05, 2006 at 07:23:38AM +0100, Christian Perrier wrote: My conclusion again: the problem is on your side! Then we can close the bug report, don't we? done ( yesterday ;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Bug#350912: network doesnt work

2006-02-05 Thread Adrien
Frans Pop a écrit : My conclusion: the problem you have is local. Good luck tracing it. I suggest using a network sniffer like ethereal to find out what's going where. Ok, this is my last question than I don't bother you again :) Can it be a network/hardware problem even if it works

Bug#350912: network doesnt work (lspci result)

2006-02-04 Thread Adrien
Hi, as I didnt send the output of lspci and lspci -n last time, here is the output of lspci : :00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) :00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) :00:00.2 RAM memory: nVidia Corporation C51 Memory

Bug#350912: network doesnt work (lspci result)

2006-02-04 Thread Christian Perrier
Two network interfaces were detected where there is only one onboard. Then the DHCP configuration doesn't detect anything, so it's impossible to download the Releases file on the next step. I tryed to fill manually the IP/netmask/gateway/etc and it's the same. I found at least one person

Bug#350912: network doesnt work (lspci result)

2006-02-04 Thread Adrien
Christian Perrier a écrit : I guess you did choose the other interface, ie the non firewire one... Anyway, what does ifconfig say on 2nd console? If an interface (let's say eth0) is configured, what does grep eth0 /var/log/syslog report? I have tried again this time with AMD64 netboot

Bug#350912: network doesnt work

2006-02-04 Thread Frans Pop
On Saturday 04 February 2006 19:06, Adrien wrote: Jan 29 15:09:17 dhclient: Listening on LPF/eth0/00:13:d4:b1:41:71 Jan 29 15:09:17 dhclient: Sending on LPF/eth0/00:13:d4:b1:41:71 Jan 29 15:09:17 dhclient: Sending on Socket/fallback/fallback-net Jan 29 15:09:17 dhclient: DHCPDISCOVER on

Bug#350912: network doesnt work

2006-02-04 Thread Adrien
Frans Pop a écrit : AFAICT these parts of the log show that you _do_ have a working network connection and the installer is able to download the Release file. Yes, but this log has been written by the previous install, which was successfull. The install that I have tryed today wasn't

Bug#350912: network doesnt work

2006-02-04 Thread Frans Pop
On Saturday 04 February 2006 21:39, Adrien wrote: Yes, but this log has been written by the previous install, which was successfull. The install that I have tryed today wasn't successful and dhclient never received a repond from the dhcp server. I have just tested netboot installs on my em64t

Bug#350912: network doesnt work working version is unknown

2006-02-04 Thread Geert Stappers
On Sat, Feb 04, 2006 at 09:39:23PM +0100, Adrien wrote: Frans Pop a écrit : AFAICT these parts of the log show that you _do_ have a working network connection and the installer is able to download the Release file. Yes, but this log has been written by the previous install, which was

Bug#350912: network doesnt work working version is unknown

2006-02-04 Thread Adrien
Geert Stappers a écrit : Please confirm that the working install was with AMD64 and the failing install is with i386. Finding back which version did work, would be really helpfull. Well I'll try to explain it better... I have tested 3 installations. First was with AMD64 daily netboot and

Bug#350912: network doesnt work working version is unknown

2006-02-04 Thread Frans Pop
On Saturday 04 February 2006 23:39, Adrien wrote: And I'm sure the third installation was done with this file : http://amd64.debian.net/debian-installer/daily/netboot/mini.iso in its today version (20060204). What could be the problem ? - something has been broken between 20060128 and

Bug#350912: network doesnt work working version is unknown

2006-02-04 Thread Christian Perrier
My conclusion again: the problem is on your side! Then we can close the bug report, don't we? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]