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 Controller 1 (rev a2)
:00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
:00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
:00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
:00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
:00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
:00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
:00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
:00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
:00:05.0 VGA compatible controller: nVidia Corporation C51 PCI 
Express Bridge (rev a2)

:00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
:00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2)
:00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2)
:00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller 
(rev a2)
:00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller 
(rev a2)

:00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
:00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA 
Controller (rev a1)

:00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
:00:10.1 0403: nVidia Corporation MCP51 High Definition Audio (rev a2)
:00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)
:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration
:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Address Map
:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] DRAM Controller
:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control
:04:05.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host 
Controller (rev 80)
:04:09.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus 
Reference Card (rev 01)



And lspci -n :

:00:00.0 0500: 10de:02f0 (rev a2)
:00:00.1 0500: 10de:02fa (rev a2)
:00:00.2 0500: 10de:02fe (rev a2)
:00:00.3 0500: 10de:02f8 (rev a2)
:00:00.4 0500: 10de:02f9 (rev a2)
:00:00.5 0500: 10de:02ff (rev a2)
:00:00.6 0500: 10de:027f (rev a2)
:00:00.7 0500: 10de:027e (rev a2)
:00:02.0 0604: 10de:02fc (rev a1)
:00:03.0 0604: 10de:02fd (rev a1)
:00:04.0 0604: 10de:02fb (rev a1)
:00:05.0 0300: 10de:0240 (rev a2)
:00:09.0 0500: 10de:0270 (rev a2)
:00:0a.0 0601: 10de:0260 (rev a2)
:00:0a.1 0c05: 10de:0264 (rev a2)
:00:0b.0 0c03: 10de:026d (rev a2)
:00:0b.1 0c03: 10de:026e (rev a2)
:00:0d.0 0101: 10de:0265 (rev a1)
:00:0e.0 0101: 10de:0266 (rev a1)
:00:10.0 0604: 10de:026f (rev a2)
:00:10.1 0403: 10de:026c (rev a2)
:00:14.0 0680: 10de:0269 (rev a1)
:00:18.0 0600: 1022:1100
:00:18.1 0600: 1022:1101
:00:18.2 0600: 1022:1102
:00:18.3 0600: 1022:1103
:04:05.0 0c00: 1106:3044 (rev 80)
:04:09.0 0280: 1814:0201 (rev 01)


The problem was :

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 who had the same problem :


http://www.nvnews.net/vbulletin/showpost.php?p=792214postcount=212

It's strange as I didn't have this problem with the netboot CD for 
AMD64. Two interfaces were found too, but the configuration was 
successfully detected by DHCP and the rest of the installation was OK.



Somebody said me that the second network interface was the firewire, but 
I still can't use the network. Did I something wrong or is it an 
installer bug ?


Thanks.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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 who had the same problem :
 
 http://www.nvnews.net/vbulletin/showpost.php?p=792214postcount=212
 
 It's strange as I didn't have this problem with the netboot CD for 
 AMD64. Two interfaces were found too, but the configuration was 
 successfully detected by DHCP and the rest of the installation was OK.
 
 
 Somebody said me that the second network interface was the firewire, but 
 I still can't use the network. Did I something wrong or is it an 
 installer bug ?


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?





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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 (the new one 
20060204)... and it didnt work just like with i386 !


I can't answer your questions now as I have rebooted to windows. But I 
have tried with DHCP by diffusion, DHCP by giving the IP of the host, 
manual configuration, for the two interfaces and no result...


It's very strange and now I have some doubts. Maybe it wasn't an AMD64 
netboot that I used last time (when it worked), but what else can it be ?


I have access from windows to my ext3 partition where the system was 
installed, and I have found this file /var/log/installer/lsb-release :


DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=3.1 (installer build 20060128)

+ the kernel in /boot/ is vmlinuz-2.6.15-1-amd64-generic. It seems that 
I used the daily AMD64 netboot, doesnt it ?


Maybe some usefull informations can be extract from 
/var/log/installer/syslog but I don't know how to use it. At least I 
have found this :



Jan 29 15:07:22 net/hw-detect.hotplug: Detected hotpluggable network 
interface eth0
Jan 29 15:07:22 net/hw-detect.hotplug: Detected hotpluggable network 
interface eth1
Jan 29 15:07:22 net/hw-detect.hotplug: Detected hotpluggable network 
interface lo


[...]

Jan 29 15:09:16 dhclient: eth1: unknown hardware address type 24
Jan 29 15:09:17 dhclient: eth1: unknown hardware address type 24
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 eth0 to 255.255.255.255 port 
67 interval 7

Jan 29 15:09:17 dhclient: DHCPOFFER from 192.168.0.254
Jan 29 15:09:19 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 29 15:09:19 dhclient: DHCPACK from 192.168.0.254
Jan 29 15:09:19 dhclient: bound to 192.168.0.3 -- renewal in 432000 seconds.
Jan 29 15:09:28 netcfg[8478]: INFO: Detected eth0 as a hotpluggable device
Jan 29 15:09:28 netcfg[8478]: INFO: Detected eth0 as a hotpluggable device


[...]

Jan 29 15:09:33 choose-mirror[8586]: DEBUG: command: wget -q 
http://ftp.crans.org/debian-amd64/debian//dists/etch/Release -O - | grep 
^Suite: | cut -d' ' -f 2
Jan 29 15:09:36 choose-mirror[8586]: DEBUG: command: wget -q 
http://ftp.crans.org/debian-amd64/debian//dists/unstable/Release -O - | 
grep ^Codename: | cut -d' ' -f 2

Jan 29 15:09:36 choose-mirror[8586]: INFO: codename set to: sid
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (libc6): package 
doesn't exist (ignored)
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (libdebian-installer4): 
search, dependency from cdebconf-udeb
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver 
(libdebian-installer4-udeb): mark, dependency from cdebconf-udeb
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (libtextwrap1): package 
doesn't exist (ignored)
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (cdebconf-udeb): mark, 
dependency from localechooser
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (iso-3166-udeb): mark, 
dependency from localechooser
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (di-utils): mark, 
dependency from localechooser

Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (localechooser): mark
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (libdebconfclient0): 
search, dependency from kbd-chooser
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver 
(libdebconfclient0-udeb): mark, dependency from kbd-chooser
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (console-keymaps): 
search, dependency from kbd-chooser
Jan 29 15:09:36 main-menu[3187]: DEBUG: resolver (console-keymaps-usb): 
mark, dependency from kbd-chooser


[...]

Jan 29 15:09:38 main-menu[3187]: DEBUG: configure anna, status: 2
Jan 29 15:09:39 anna[8622]: DEBUG: install hw-detect, enhances installed 
packages hw-detect
Jan 29 15:09:39 anna[8622]: DEBUG: install apt-mirror-setup, queued by 
anna-install



--
SoUL