Re: Network not working on Shuttle XS35GTV2
On Fri, 13 Jan 2012 14:07:48 -0600, Selim T. Erdogan wrote: It probably isn't this simple but have you tried running the following? ifup eth0 Thanks for your suggestion! I've just tried it. With the static interface configuration it sets the IP address but I can't ping anything in the LAN and the link led on the switch is still off. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jes954$98n$1...@dough.gmane.org
Re: Network not working on Shuttle XS35GTV2
It probably isn't this simple but have you tried running the following? ifup eth0 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120113200748.ga5...@cs.utexas.edu
Re: Network not working on Shuttle XS35GTV2
On Mi, 11 ian 12, 23:56:56, Ramon Hofer wrote: Unfortunately there are no leds on the Shuttle. When I first noticed the problem the link leds on the switch weren't on. Is that led still off? Then I tried a different cable on a different port. Afterwards I installed Win 7. After installing the driver it could connect to the internet with the second cable attached to the second port. Thereafter I tried the cable which was attached to my laptop and a third port on the switch. The laptop has no problem connecting to the internet. As far as I understand you eliminated the switch and the cable as sources of problems. Do you think the Shuttle support can help me? But I doubt that they know what to do and will tell me to install Windows :-( Yes, this might happen, but as far as I understand you already verified that it works with Windows. Maybe you should contact them anyway, even if just to let them know that Linux users of their products exist. Other things to try: - BIOS options or even update(s) - a newer kernel (you could use a USB stick to copy it over) - the Linux Live CD with the most recent kernel you can find However, at this point I'm just guessing. I found a related Ubuntu bug, maybe you should add more info there... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Network not working on Shuttle XS35GTV2
On Thu, 12 Jan 2012 11:46:17 +0200, Andrei Popescu wrote: On Mi, 11 ian 12, 23:56:56, Ramon Hofer wrote: Unfortunately there are no leds on the Shuttle. When I first noticed the problem the link leds on the switch weren't on. Is that led still off? Yes, the leds are still off. Then I tried a different cable on a different port. Afterwards I installed Win 7. After installing the driver it could connect to the internet with the second cable attached to the second port. Thereafter I tried the cable which was attached to my laptop and a third port on the switch. The laptop has no problem connecting to the internet. As far as I understand you eliminated the switch and the cable as sources of problems. Yes. Do you think the Shuttle support can help me? But I doubt that they know what to do and will tell me to install Windows :-( Yes, this might happen, but as far as I understand you already verified that it works with Windows. Maybe you should contact them anyway, even if just to let them know that Linux users of their products exist. That's a good point. I will do that. Other things to try: - BIOS options or even update(s) I reseted the BIOS to the factory default. But I will play again with the setting. Maybe Shuttle can deliver me a newer version. Compared to the newest BIOS on their homepage I already have the newest version. - a newer kernel (you could use a USB stick to copy it over) - the Linux Live CD with the most recent kernel you can find Ah yes, that was a former question if you meant a memory stick or a ethernet stick. I will download the newest kernel and try to install it. Otherwise I will try a live CD. Which one would be the best? However, at this point I'm just guessing. I found a related Ubuntu bug, maybe you should add more info there... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 I posted that bug. I will post the dmesg and ifconfig logs there. But I have no clue how to run this apport-collect 880316 command Brad mentioned in post #2. But maybe I can install Ubunt server version and run the command there. Or maybe it's possible to switch to a terminal with Ctrl+Alt+F2 like during the Debian installation. Thanks a lot for your help! Best regards Ramon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jemgfi$gr5$1...@dough.gmane.org
Re: Network not working on Shuttle XS35GTV2
On Tue, 10 Jan 2012 23:09:21 +, Ramon Hofer wrote: On Wed, 11 Jan 2012 00:01:16 +0200, Andrei Popescu wrote: On Ma, 10 ian 12, 16:22:10, Ramon Hofer wrote: You wrote in your first answer I should update to the newest kernel. At the moment is 2.6.32-5-amd64 installed. How can I do that without a network connection? USB sticks can be very handy in such cases. It would also be useful if you could attach some bigger informations: ifconfig -a dmesg dmesg http://pastebin.com/sBtbX2T7 In dmesg (Pastebin lines 448ff) there seems that the interface is recognized. But I don't know if the firmware bug (line 262) may be the problem. On the Shuttle website the BIOS version 1.03 is the newest one which is the on that's installed on my box too. The interface broke some time ago but with Debian and OpenELEC there was no problem only with Ubuntu. Really strange. Regards Ramon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jeko26$j78$1...@dough.gmane.org
Re: Network not working on Shuttle XS35GTV2
On Mi, 11 ian 12, 19:31:18, Ramon Hofer wrote: dmesg http://pastebin.com/sBtbX2T7 What I'm missing in your dmesg is a Link is Up... notice. Please make sure you have the correct ethernet cable and the link led is on. You might also want to test with a known good cable and check the link led also on the other side (switch?). You might also want to test different ports on your switch or even replace with a known good switch. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Network not working on Shuttle XS35GTV2
On Wed, 11 Jan 2012 23:30:56 +0200, Andrei Popescu wrote: On Mi, 11 ian 12, 19:31:18, Ramon Hofer wrote: dmesg http://pastebin.com/sBtbX2T7 What I'm missing in your dmesg is a Link is Up... notice. Please make sure you have the correct ethernet cable and the link led is on. You might also want to test with a known good cable and check the link led also on the other side (switch?). You might also want to test different ports on your switch or even replace with a known good switch. Unfortunately there are no leds on the Shuttle. When I first noticed the problem the link leds on the switch weren't on. Then I tried a different cable on a different port. Afterwards I installed Win 7. After installing the driver it could connect to the internet with the second cable attached to the second port. Thereafter I tried the cable which was attached to my laptop and a third port on the switch. The laptop has no problem connecting to the internet. It's really strange :-? Do you think the Shuttle support can help me? But I doubt that they know what to do and will tell me to install Windows :-( Best regards Ramon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jel7k8$f4$1...@dough.gmane.org
Re: Network not working on Shuttle XS35GTV2
On Tue, 10 Jan 2012 00:34:29 +0200, Andrei Popescu wrote: On Lu, 09 ian 12, 16:07:38, Ramon Hofer wrote: I can skip the network setup of netinst. But I can't skip the part when I have to choose a Debian mirror? It should be possible. Worst case the Back button should get you to a menu where you can just choose the next step ;) Aha. With the UNetbootin's Debian Stable_NetInstall_x64 option it's not possible to skip the network setup. But with this one it is: http://cdimage.debian.org/debian-cd/6.0.3/amd64/iso-cd/debian-6.0.3-amd64- netinst.iso I installed SSH server and Standard system utilities. `dmesg | grep -i firmware` returns [ 0.874429] pci :00:1f.0: [Firmware Bug]: TigerPoint LPC.BM_STS cleared `lspci | grep Ethernet` gives 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) `ifconfig` lists only the loopback interface. I can run `ifconfig eth0 up` and then eth0 is listed by `ifconfig`. I added the following to /etc/network/interfaces without any difference: iface eth0 inet static address 192.168.1.201 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 You wrote in your first answer I should update to the newest kernel. At the moment is 2.6.32-5-amd64 installed. How can I do that without a network connection? What else can I do? Best regards Ramon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jehoji$7i8$1...@dough.gmane.org
Re: Network not working on Shuttle XS35GTV2
On Ma, 10 ian 12, 16:22:10, Ramon Hofer wrote: You wrote in your first answer I should update to the newest kernel. At the moment is 2.6.32-5-amd64 installed. How can I do that without a network connection? USB sticks can be very handy in such cases. It would also be useful if you could attach some bigger informations: ifconfig -a dmesg Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Network not working on Shuttle XS35GTV2
On Wed, 11 Jan 2012 00:01:16 +0200, Andrei Popescu wrote: On Ma, 10 ian 12, 16:22:10, Ramon Hofer wrote: You wrote in your first answer I should update to the newest kernel. At the moment is 2.6.32-5-amd64 installed. How can I do that without a network connection? USB sticks can be very handy in such cases. It would also be useful if you could attach some bigger informations: ifconfig -a dmesg What kind of usb stick do you mean? Can i copy the package to a stick? Or do you mean an ethernet usb stick? I addes the eth0 part to interfaces. Before ifconfig only showed lo. /etc/network/interfaces http://pastebin.com/k3TMRRcZ ifconfig -a http://pastebin.com/Zc7dzzva dmesg http://pastebin.com/sBtbX2T7 Best regards Ramon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jeigf1$ht5$1...@dough.gmane.org
Re: Network not working on Shuttle XS35GTV2
On Du, 08 ian 12, 17:18:57, Ramon Hofer wrote: Hi all I used a Shuttle XS35GTV2 as XBMC frontend with OpenELEC. Since some time it lost its Network connection (I use ethernet not WLAN). I have no clue why this happend. I suggest it was due to the OpenELEC update 1.02. ... Can you help me getting the network interface running for the netinst? Or would it be easier to install Debian using ISO-CD or DVD and then somehow fix the problem? I looked up the online specs for your device and there is no mention of the network chipset used, but I'm guessing it is one of the newer RTL chipsets. You can still use the netinst, because it does have the minimum amount of packages. Afterwards make sure you run the latest kernel from stable or even backports. You might also need firmware, a dmesg | grep -i firmware should tell. Hope this helps, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Network not working on Shuttle XS35GTV2
Thanks alot for you answer Andrei! On Mon, 09 Jan 2012 10:07:28 +0200, Andrei Popescu wrote: On Du, 08 ian 12, 17:18:57, Ramon Hofer wrote: Hi all I used a Shuttle XS35GTV2 as XBMC frontend with OpenELEC. Since some time it lost its Network connection (I use ethernet not WLAN). I have no clue why this happend. I suggest it was due to the OpenELEC update 1.02. ... Can you help me getting the network interface running for the netinst? Or would it be easier to install Debian using ISO-CD or DVD and then somehow fix the problem? I looked up the online specs for your device and there is no mention of the network chipset used, but I'm guessing it is one of the newer RTL chipsets. Sorry, I should have posted it here. lspci gave 02:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03) 03:00.0 Network controller: Realtek Semiconductor C., Ltd Device 8176 (rev 01) You can still use the netinst, because it does have the minimum amount of packages. Afterwards make sure you run the latest kernel from stable or even backports. You might also need firmware, a dmesg | grep -i firmware should tell. I can skip the network setup of netinst. But I can't skip the part when I have to choose a Debian mirror? After the installer fails to setup the network dmesg | grep -i firmware returns: [ 0.904131] pci :00:1f.0: [Firmware Bug]: TigerPoint LPC.BM_STS cleared I wanted to install an ISO image but there are 52 cd images and another 10 update images. I suppose I would had to download and use all of them to install? Best regards Ramon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jef3ca$uvp$1...@dough.gmane.org
Re: Network not working on Shuttle XS35GTV2
On Lu, 09 ian 12, 16:07:38, Ramon Hofer wrote: I can skip the network setup of netinst. But I can't skip the part when I have to choose a Debian mirror? It should be possible. Worst case the Back button should get you to a menu where you can just choose the next step ;) After the installer fails to setup the network dmesg | grep -i firmware returns: [ 0.904131] pci :00:1f.0: [Firmware Bug]: TigerPoint LPC.BM_STS cleared I wanted to install an ISO image but there are 52 cd images and another 10 update images. I suppose I would had to download and use all of them to install? The latest CD1 for any Desktop Environment (you don't plan to use one anyway) is more than enough. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Network not working on Shuttle XS35GTV2
Hi all I used a Shuttle XS35GTV2 as XBMC frontend with OpenELEC. Since some time it lost its Network connection (I use ethernet not WLAN). I have no clue why this happend. I suggest it was due to the OpenELEC update 1.02. Since I'd like to use XBMC as MythTV frontend too I want to install Debian stable and compile XBMC PVR libcmyth [1]. I'd like to have a only a minimal system to compile and run XBMC. Therefore I wanted to install Debian stable netinst AMD64. But the installer can't setup the network interface which is quite strange as it worked after I discovered problems with the Ubuntu installer and then switched to OpenELEC. I posted it to the Ubuntu mailing list [2]. I installed Windows to check that there's not hardware failure. Can you help me getting the network interface running for the netinst? Or would it be easier to install Debian using ISO-CD or DVD and then somehow fix the problem? Best regards Ramon [1] http://forum.xbmc.org/showthread.php?t=110694 [2] http://markmail.org/message/jlwnouankyyd4he5 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jecj61$q03$1...@dough.gmane.org
Network Not Working - multipart post
I am trying to install debian on my wife's computer. It already has Windows XP installed and running on the first partition and used to have Mandrake 10 on another partition. Both Windows XP and Mandrake 10 recognized all hardware components including the built in network chipset. I tried different debian CDs including Sarge testing net-install and Etch testing net-install and finally Sarge Stable DVD from Linux Format Magazine Cover CD. All these CDs have the same problem.. network is not work-ing :-) I then tested the network chipset by using Knoppix Live 4.0 DVD and it was detected and automatically configured properly. Here are some information I gathered so far. I will post Debian's Stable (Sarge), Testing (Etch) and Knoppix's data each in a separate post in reply to this to make it easy for others to read: -- Computer: Acer ASPIRE 6634 (A), PIII 866MHz Built-in Network Chipset: Intel(R) PRO/100 VE (not wireless) -- Windows Settings: Location: PCI Slot 4 (PCI bus 1, device 8, function 0) Memory Usage: 8012-80120FFF I/O Range: 70C0-70FF IRQ: 10 IP: 10.0.0.2 Netmask: 255.255.255.0 Broadcast: 10.0.0.255 Gateway: 10.0.0.138 DNS: 10.0.0.138 -- I noticed the following: 1) Debian Sarge is using an older kernel with an older e100 driver while Debian Etch is using kernel 2.6.12, same as Knoppix 4.0 but only Knoppix 4.0 works 2) I also noticed that Debian Stable and Testing for a strange reason disable IRQ10 and assign IRQ11 to network port, while Windows and Knoppix work with IRQ10. I checked the BIOS and in the Onboard Peripherals it list only these: * Serial Port 1 and 2 * Parallal Port * Floppy, IDE, PS/2, USB Host Controllers * Audio Chip and none is using IRQ 10 or 11. -- All help is greatly appreciated: -- -- http://www.mishkah.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Network Not Working - multipart post (Debian Sarge (Stable))
/uname -a/ Linux farabi 2.6.8-2-686 #1 Thu May 19 17:53:30 JST 2005 i686 GNU/Linux -- //etc/resolve.conf/ search lan nameserver 10.0.0.138 -- //etc/network/interfaces/ # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.0.0.2 netmask 255.255.255.0 network 10.0.0.0 broadcast 10.0.0.255 gateway 10.0.0.138 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 10.0.0.138 dns-search lan -- /ping -c 3 10.0.0.138/ PING 10.0.0.138 (10.0.0.138) 56(84) bytes of data. From 10.0.0.2 icmp_seq=1 Destination Host Unreachable From 10.0.0.2 icmp_seq=2 Destination Host Unreachable From 10.0.0.2 icmp_seq=3 Destination Host Unreachable --- 10.0.0.138 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms , pipe 3 -- /ping -c 3 127.0.0.1/ PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.050 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.031 ms --- 127.0.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.031/0.043/0.050/0.011 ms -- /ping -c 3 10.0.0.2/ PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.049 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.018 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.029 ms --- 10.0.0.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.018/0.032/0.049/0.012 ms -- /ifconfig/ eth0 Link encap:Ethernet HWaddr 00:00:E2:4E:AC:F1 inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::200:e2ff:fe4e:acf1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:27 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2544 (2.4 KiB) TX bytes:2544 (2.4 KiB) -- /lspci/ :00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) :00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 02) :00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 02) :00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02) :00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 02) :00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 02) :01:00.0 Multimedia audio controller: Avance Logic Inc. ALS4000 Audio Chipset :01:01.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) :01:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 01) -- /lsmod | grep e100/ e100 32608 0 mii 5120 1 e100 -- /dmesg | grep eth/ e100: eth0: e100_probe: addr 0x8012, irq 11, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex NETDEV WATCHDOG: eth0: transmit timed out e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex eth0: no IPv6 routers present -- /dmesg | grep e100/ e100: Intel(R) PRO/100 Network Driver, 3.0.18 e100: Copyright(c) 1999-2004 Intel Corporation e100: eth0: e100_probe: addr 0x8012, irq 11, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex -- //etc/network/options/ ip_forward=no spoofprotect=yes syncookies=no -- /route/ Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface localnet * 255.255.255.0 U 0 0 0 eth0 default 10.0.0.138 0.0.0.0 UG 0 0 0 eth0 -- /dmesg |grep IRQ / ACPI: IRQ9 SCI: Level Trigger. ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 5 6 7 *9 10 11 12
Re: Network Not Working - multipart post
Knoppix 4.0 Live DVD works fine and automatically detects and configures the built-in ethernet port which I can use to connect to the router and the internet without a problem. /-- /uname -a/ Linux Knoppix 2.6.12 #2 SMP Tue Aug 9 23:20:52 CEST 2005 i686 GNU/Linux -- //etc/resolve.conf/ search lan nameserver 10.0.0.138 -- //etc/network/interfaces/ # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo iface lo inet loopback -- /ping -c 3 10.0.0.138/ PING 10.0.0.138 (10.0.0.138): 56 data bytes 64 bytes from 10.0.0.138: icmp_seq=0 ttl=64 time=0.4 ms 64 bytes from 10.0.0.138: icmp_seq=1 ttl=64 time=0.4 ms 64 bytes from 10.0.0.138: icmp_seq=2 ttl=64 time=0.4 ms --- 10.0.0.138 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.4/0.4/0.4 ms -- /ifconfig/ eth0 Link encap:Ethernet HWaddr 00:00:E2:4E:AC:F1 inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1549 (1.5 KiB) TX bytes:1772 (1.7 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:700 (700.0 b) TX bytes:700 (700.0 b) -- /lspci/ :00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) :00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 02) :00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 02) :00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02) :00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 02) :00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 02) :01:00.0 Multimedia audio controller: Avance Logic Inc. ALS4000 Audio Chipset :01:01.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) :01:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 01) -- /lsmod | grep e100/ e100 37248 0 mii 8320 1 e100 -- /dmesg | grep eth/ e100: eth0: e100_probe: addr 0x8012, irq 10, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex -- /dmesg | grep e100/ e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI e100: Copyright(c) 1999-2005 Intel Corporation e100: eth0: e100_probe: addr 0x8012, irq 10, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex -- //etc/network/options/ ip_forward=no spoofprotect=yes syncookies=no -- /route/ Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 * 255.255.255.0 U 0 0 0 eth0 default SpeedTouch.lan 0.0.0.0 UG 0 0 0 eth0 -- /dmesg |grep IRQ/ PCI: Discovered primary peer bus 02 [IRQ] PCI: Using IRQ router PIIX/ICH [8086/2440] at :00:1f.0 PCI: Found IRQ 3 for device :00:1f.2 PCI: Found IRQ 10 for device :00:1f.4 Serial: 8250/16550 driver $Revision: 1.90 $ 14 ports, IRQ sharing disabled PCI: Found IRQ 10 for device :01:08.0 PCI: Found IRQ 11 for device :01:00.0 PCI: Sharing IRQ 11 with :00:02.0 PCI: Found IRQ 9 for device :00:1f.5 PCI: Sharing IRQ 9 with :00:1f.3 PCI: Sharing IRQ 9 with :01:01.0 i810: Intel ICH2 found at IO 0x8800 and 0x8400, MEM 0x and 0x, IRQ 9 PCI: Found IRQ 11 for device :00:02.0 PCI: Sharing IRQ 11 with :01:00.0 -- -- http://www.mishkah.org Linux version 2.6.12 ([EMAIL PROTECTED]) (gcc-Version 3.3.6 (Debian 1:3.3.6-7)) #2 SMP Tue Aug 9 23:20:52 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 0fed (usable) BIOS-e820: 0fed - 0fee (reserved) BIOS-e820: 0fee - 0fee8000 (ACPI data)
Re: Network Not Working - multipart post
Debian Sarge (Stable) does not detect the built-in ethernet port, so I can not connect to the router or the internet. -- uname -a Linux farabi 2.6.8-2-686 #1 Thu May 19 17:53:30 JST 2005 i686 GNU/Linux -- /etc/resolve.conf search lan nameserver 10.0.0.138 -- /etc/network/interfaces/ # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.0.0.2 netmask 255.255.255.0 network 10.0.0.0 broadcast 10.0.0.255 gateway 10.0.0.138 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 10.0.0.138 dns-search lan -- ping -c 3 10.0.0.138 PING 10.0.0.138 (10.0.0.138) 56(84) bytes of data. From 10.0.0.2 icmp_seq=1 Destination Host Unreachable From 10.0.0.2 icmp_seq=2 Destination Host Unreachable From 10.0.0.2 icmp_seq=3 Destination Host Unreachable --- 10.0.0.138 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms , pipe 3 -- ping -c 3 127.0.0.1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.050 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.031 ms --- 127.0.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.031/0.043/0.050/0.011 ms -- ping -c 3 10.0.0.2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.049 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.018 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.029 ms --- 10.0.0.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.018/0.032/0.049/0.012 ms -- ifconfig eth0 Link encap:Ethernet HWaddr 00:00:E2:4E:AC:F1 inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::200:e2ff:fe4e:acf1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:27 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2544 (2.4 KiB) TX bytes:2544 (2.4 KiB) -- lspci :00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) :00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 02) :00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 02) :00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02) :00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 02) :00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 02) :01:00.0 Multimedia audio controller: Avance Logic Inc. ALS4000 Audio Chipset :01:01.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) :01:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 01) -- lsmod | grep e100 e100 32608 0 mii 5120 1 e100 -- dmesg | grep eth e100: eth0: e100_probe: addr 0x8012, irq 11, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex NETDEV WATCHDOG: eth0: transmit timed out e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex eth0: no IPv6 routers present -- dmesg | grep e100 e100: Intel(R) PRO/100 Network Driver, 3.0.18 e100: Copyright(c) 1999-2004 Intel Corporation e100: eth0: e100_probe: addr 0x8012, irq 11, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex -- /etc/network/options ip_forward=no spoofprotect=yes syncookies=no -- route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface localnet * 255.255.255.0 U 0 0 0 eth0 default 10.0.0.138 0.0.0.0 UG 0 0 0 eth0 -- dmesg |grep IRQ ACPI: IRQ9 SCI: Level Trigger.
Re: Network Not Working - multipart post
Debian Etch (Testing) does not detect the built-in ethernet port, so I can not connect to the router or the internet. -- /uname -a/ Linux farabi 2.6.12-1-386 #1 Tue Sep 27 12:41:08 JST 2005 i686 GNU/Linux -- //etc/network/interfaces/ # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.0.0.2 netmask 255.255.255.0 network 10.0.0.0 broadcast 10.0.0.255 gateway 10.0.0.138 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 10.0.0.138 dns-search lan -- /ping -c 3 10.0.0.138/ PING 10.0.0.138 (10.0.0.138) 56(84) bytes of data. From 10.0.0.2 icmp_seq=1 Destination Host Unreachable From 10.0.0.2 icmp_seq=2 Destination Host Unreachable From 10.0.0.2 icmp_seq=3 Destination Host Unreachable --- 10.0.0.138 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1998ms , pipe 3 -- /ping -c 3 10.0.0.2/ Code: PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.057 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.033 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.052 ms --- 10.0.0.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.033/0.047/0.057/0.011 ms -- /ping -c 3 127.0.0.1/ PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.064 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.056 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.016 ms --- 127.0.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.016/0.045/0.064/0.021 ms -- /ifconfig/ eth0 Link encap:Ethernet HWaddr 00:00:E2:4E:AC:F1 inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:23 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2016 (1.9 KiB) TX bytes:2016 (1.9 KiB) -- /dmesg | grep eth/ e100: eth0: e100_probe: addr 0x8012, irq 11, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex NETDEV WATCHDOG: eth0: transmit timed out e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex -- / dmesg | grep e100/ Code: e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI e100: Copyright(c) 1999-2005 Intel Corporation e100: eth0: e100_probe: addr 0x8012, irq 11, MAC addr 00:00:E2:4E:AC:F1 e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex -- /route/ Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface localnet * 255.255.255.0 U 0 0 0 eth0 default 10.0.0.138 0.0.0.0 UG 0 0 0 eth0 -- /dmesg |grep IRQ/ ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [PILC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [PILD] (IRQs *3 4 5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [PILE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [PILF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [PILG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [PILH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) PCI: Using ACPI for IRQ routing Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled ACPI: PCI Interrupt Link [PILA] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt :01:08.0[A] - Link [PILA] - GSI 11 (level, low) - IRQ 11 ACPI: PCI Interrupt :00:1f.5[b]: no GSI - using IRQ 9 PCI: setting IRQ 9 as level-triggered i810: Intel ICH2 found at IO 0x8800 and 0x8400, MEM 0x and 0x, IRQ 9 ACPI: PCI Interrupt :01:00.0[A] - Link [PILA] - GSI 11 (level, low) - IRQ 11 ACPI: PCI Interrupt :00:1f.2[D]: no GSI - using IRQ 3 PCI: setting IRQ 3 as level-triggered [c012f3ac] __do_IRQ+0xb0/0xc4 [c0105039] do_IRQ+0x1d/0x28 [c010503e] do_IRQ+0x22/0x28 Disabling IRQ #3 ACPI: PCI Interrupt :00:1f.4[C]: no GSI - using IRQ 10 PCI: setting IRQ 10 as level-triggered [c012f3ac] __do_IRQ+0xb0/0xc4 [c0105039] do_IRQ+0x1d/0x28
Re: Network Not Working - multipart post
I put a working PCI network card from my computer that also runs Debian Testing (Etch) into this computer and installed from a Debian Testing netinstall CD that has a 2.6.12 kernel. Again, Debian didn't detect the built-in network port. -- /dmesg | grep eth/ eth0: RealTek RTL8139 at 0x7400, 00:c0:26:59:8a:0b, IRQ 10 eth0: Identified 8139 chip type 'RTL-8139C' e100: eth1: e100_probe: addr 0x80101000, irq 11, MAC addr 00:00:E2:4E:AC:F1 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth0: transmit timed out eth0: Transmit timeout, status 0c 0005 c07f media 10. eth0: Tx queue start entry 4 dirty entry 0. eth0: Tx descriptor 0 is 0008a03c. (queue head) eth0: Tx descriptor 1 is 0008a03c. eth0: Tx descriptor 2 is 0008a03c. eth0: Tx descriptor 3 is 0008a03c. eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth0: transmit timed out eth0: Transmit timeout, status 0c 0005 c07f media 10. eth0: Tx queue start entry 4 dirty entry 0. eth0: Tx descriptor 0 is 0008a03c. (queue head) eth0: Tx descriptor 1 is 0008a03c. eth0: Tx descriptor 2 is 0008a03c. eth0: Tx descriptor 3 is 0008a03c. eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth0: transmit timed out eth0: Transmit timeout, status 0c 0005 c07f media 10. eth0: Tx queue start entry 4 dirty entry 0. eth0: Tx descriptor 0 is 0008a03c. (queue head) eth0: Tx descriptor 1 is 0008a03c. eth0: Tx descriptor 2 is 0008a03c. eth0: Tx descriptor 3 is 0008a03c. eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 eth0: RealTek RTL8139 at 0x7400, 00:c0:26:59:8a:0b, IRQ 10 eth0: Identified 8139 chip type 'RTL-8139C' eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth0: transmit timed out eth0: Transmit timeout, status 0c 0005 c07f media 10. eth0: Tx queue start entry 4 dirty entry 0. eth0: Tx descriptor 0 is 0008a03c. (queue head) eth0: Tx descriptor 1 is 0008a03c. eth0: Tx descriptor 2 is 0008a03c. eth0: Tx descriptor 3 is 0008a03c. eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 -- /dmesg | grep 8139/ 8139too Fast Ethernet driver 0.9.27 eth0: RealTek RTL8139 at 0x7400, 00:c0:26:59:8a:0b, IRQ 10 eth0: Identified 8139 chip type 'RTL-8139C' 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004) 8139too Fast Ethernet driver 0.9.27 eth0: RealTek RTL8139 at 0x7400, 00:c0:26:59:8a:0b, IRQ 10 eth0: Identified 8139 chip type 'RTL-8139C' -- I also did: modprobe -r e100 modprobe -r 8139cp modprobe -r 8139too modprobe 8139too ifup eth0 it said something that it is connected to IRQ 10 but still it didn't work. -- /dmesg | grep IRQ/ ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [PILC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [PILD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [PILE] (IRQs *3 4 5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [PILF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [PILG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [PILH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) PCI: Using ACPI for IRQ routing Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled ACPI: PCI Interrupt :01:01.0[A]: no GSI - using IRQ 10 PCI: setting IRQ 10 as level-triggered eth0: RealTek RTL8139 at 0x7400, 00:c0:26:59:8a:0b, IRQ 10 ACPI: PCI Interrupt Link [PILA] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt :01:08.0[A] - Link [PILA] - GSI 11 (level, low) - IRQ 11 ACPI: PCI Interrupt :00:1f.5[B]: no GSI - using IRQ 10 i810: Intel ICH2 found at IO 0x8800 and 0x8400, MEM 0x and 0x, IRQ 10 [c012f3ac] __do_IRQ+0xb0/0xc4 [c0105039] do_IRQ+0x1d/0x28 [c010503e] do_IRQ+0x22/0x28 Disabling IRQ #10 ACPI: PCI Interrupt :01:00.0[A] - Link [PILA] - GSI 11 (level, low) - IRQ 11 ACPI: PCI Interrupt :00:1f.2[D]: no GSI - using IRQ 10 ACPI: PCI Interrupt :00:1f.4[C]: no GSI - using IRQ 10 ACPI: PCI Interrupt :01:01.0[A]: no GSI - using IRQ 10 eth0: RealTek RTL8139 at 0x7400, 00:c0:26:59:8a:0b, IRQ 10 -- /ifconfig/ eth0 Link encap:Ethernet HWaddr 00:C0:26:59:8A:0B inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0x7400 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1904 (1.8 KiB) TX bytes:1904 (1.8 KiB) -- /ping -c 3 10.0.0.138/ PING 10.0.0.138 (10.0.0.138
Network Not Working - multipart post
I am trying to install debian on my wife's computer. It already has Windows XP installed and running on the first partition and used to have Mandrake 10 on another partition. Both Windows XP and Mandrake 10 recognized all hardware components including the built in network chipset. I tried different debian CDs including Sarge testing net-install and Etch testing net-install and finally Sarge Stable DVD from Linux Format Magazine Cover CD. All these CDs have the same problem.. network is not work-ing :-) I then tested the network chipset by using Knoppix Live 4.0 DVD and it was detected and automatically configured properly. Here are some information I gathered so far. I will post Debian's Stable (Sarge), Testing (Etch) and Knoppix's data each in a separate post in reply to this to make it easy for others to read: -- Computer: Acer ASPIRE 6634 (A), PIII 866MHz Built-in Network Chipset: Intel(R) PRO/100 VE (not wireless) -- Windows Settings: Location: PCI Slot 4 (PCI bus 1, device 8, function 0) Memory Usage: 8012-80120FFF I/O Range: 70C0-70FF IRQ: 10 IP: 10.0.0.2 Netmask: 255.255.255.0 Broadcast: 10.0.0.255 Gateway: 10.0.0.138 DNS: 10.0.0.138 -- I noticed the following: 1) Debian Sarge is using an older kernel with an older e100 driver while Debian Etch is using kernel 2.6.12, same as Knoppix 4.0 but only Knoppix 4.0 works 2) I also noticed that Debian Stable and Testing for a strange reason disable IRQ10 and assign IRQ11 to network port, while Windows and Knoppix work with IRQ10. I checked the BIOS and in the Onboard Peripherals it list only these: * Serial Port 1 and 2 * Parallal Port * Floppy, IDE, PS/2, USB Host Controllers * Audio Chip and none is using IRQ10 or 11. -- All help is greatly appreciated: -- http://www.mishkah.org -- http://www.mishkah.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Network Not Working - multipart post
I am trying to install debian on my wife's computer. It already has Windows XP installed and running on the first partition and used to have Mandrake 10 on another partition. Both Windows XP and Mandrake 10 recognized all hardware components including the built in network chipset. I tried different debian CDs including Sarge testing net-install and Etch testing net-install and finally Sarge Stable DVD from Linux Format Magazine Cover CD. All these CDs have the same problem.. network is not work-ing :-) I then tested the network chipset by using Knoppix Live 4.0 DVD and it was detected and automatically configured properly. Here are some information I gathered so far. I will post Debian's Stable (Sarge), Testing (Etch) and Knoppix's data each in a separate post in reply to this to make it easy for others to read: -- Computer: Acer ASPIRE 6634 (A), PIII 866MHz Built-in Network Chipset: Intel(R) PRO/100 VE (not wireless) -- Windows Settings: Location: PCI Slot 4 (PCI bus 1, device 8, function 0) Memory Usage: 8012-80120FFF I/O Range: 70C0-70FF IRQ: 10 IP: 10.0.0.2 Netmask: 255.255.255.0 Broadcast: 10.0.0.255 Gateway: 10.0.0.138 DNS: 10.0.0.138 -- I noticed the following: 1) Debian Sarge is using an older kernel with an older e100 driver while Debian Etch is using kernel 2.6.12, same as Knoppix 4.0 but only Knoppix 4.0 works 2) I also noticed that Debian Stable and Testing for a strange reason disable IRQ10 and assign IRQ11 to network port, while Windows and Knoppix work with IRQ10. I checked the BIOS and in the Onboard Peripherals it list only these: * Serial Port 1 and 2 * Parallal Port * Floppy, IDE, PS/2, USB Host Controllers * Audio Chip and none is using IRQ10 or 11. -- All help is greatly appreciated: -- http://www.mishkah.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
network not working
hi i just installed unstable on a machine. everything seems fine other than the fact that i cant access http or ping any hosts other than my router. is this perhaps because i have a http proxy installed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Network not working with Debian and Real Time Kernel 3.1...
I'm running Debian w/ kernel 2.4.18 and real-time Linux v. 3.1. The kernel compiles without problems, but on two completely different computers, the network does not function properly. Within the pix firewall at our location, only ssh works into and out of the computers (ping works also, and resolving names works). I can ftp to other machines within our firewall, but I have no access to anything beyond the firewall. As soon as I move the computer out of the firewall (on the dmz) the machines behave normally. The only way I can access the outside world from within the pix firewall is using a proxy. Other (different) machines are configured with the same kerneland real time linux,and they work fine inside the firewall (ie, they cancommunicate with everyone beyond the firewall). Is this an ethernet card driver since the other mahines work from within the firewall? One machine is running an eepro100 and the other is running a 3c59x. I've tried swapping out cards, but this will not resolve the problem. Am I perhaps configuring the kernel improperly? Any help would be greatly appreciated. Thanks! Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo.
Network not working, but card seems fine
I have installed Debian on at least a dozen systems now (I guess I'm not a total newbie now...) Anyway -- this is the first time I have had a system with a 905c 3Com card not be able to get out on the network. (All but one of my systems us 905x cards)... System sets up fine, ifconfig reports correct information. Tornado drivers seems to be loading (as seen in the dmesg output). I can ping the IP of the card, but when I try to ping or apt-get update, sending packets to the outside world, nothing happens. Changed cables, changed ports on the switch, etc., etc. (Oh, yes -- the connection lights on the card indicate electrical connection with the switch). Where do I look now? Thanks -- Randy
Re: Network not working, but card seems fine
On 21-Nov-2001 Randolph S. Kahle wrote: I have installed Debian on at least a dozen systems now (I guess I'm not a total newbie now...) Anyway -- this is the first time I have had a system with a 905c 3Com card not be able to get out on the network. (All but one of my systems us 905x cards)... System sets up fine, ifconfig reports correct information. Tornado drivers seems to be loading (as seen in the dmesg output). I can ping the IP of the card, but when I try to ping or apt-get update, sending packets to the outside world, nothing happens. Changed cables, changed ports on the switch, etc., etc. (Oh, yes -- the connection lights on the card indicate electrical connection with the switch). could be a weird irq issue or it may be an odd card. Try moving the slot the card is in and then try swapping cards.
Re: Network Not Working!
Peter Ludwig: error connecting to 192.168.0.11:139 (No route to host) What does route tell you? That's /sbin/route from the netbase package. Jiri -- [EMAIL PROTECTED] We'll know the future has arrived when every mailer transparently quotes lines that begin with From , but no-one remembers why.
[FIXED] Re: Network Not Working!
On 11 Feb 1999, Carey Evans wrote: Peter Ludwig [EMAIL PROTECTED] writes: This is the response I get from SMBCLIENT : Added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 startlmhosts: Can't open lmhosts file /etc/lmhosts. Error was No such file or directory This is generally harmless, and you can ignore it for now. Umm... why? What IS the /etc/lmhosts file? And if samba wants it, why is it not referred to in the Samba Documentation (the only thing I haven't done is grep the files to find it, perhaps I should...)? error connecting to 192.168.0.11:139 (No route to host) Trying to use 192.168.0.xxx is asking for trouble, in my opinion. Try setting Linux and Windows to 192.168.1.something. The files to modify are /etc/init.d/network, /etc/hostname and /etc/hosts. The hosts file could look something like: All those files where correct, but I'll fill you in on what I've done (because I seem to have fixed the problem here). I checked all the settings on the Win95 Machine (They where set correctly) I then went and checked over the whole config here, everything appeared like it should be working. I then went in and tried to look at the IPX routing table - oooh.. problem here... Output from route :- IPX: this needs to be written As I was trying to setup the network to run as an IPX network (due to various reasons, namely wanting the win95 machine to able to dial the internet as well as be conencted to the linux box, and win95 does not handle multiple TCP-IP links very cleanly), I gathered that it would be best to try the network WITHOUT the IPX backbone, and hey - it worked! I wonder if anyone else has had the same problem with setting up an IPX network... Thanks for all the info people, it has been very helpful. Peter Ludwig
Re: Network Not Working!
Roland E. Lipovits [EMAIL PROTECTED] writes: On Thu, Feb 11, 1999 at 12:36:14AM +1300, Carey Evans wrote: Trying to use 192.168.0.xxx is asking for trouble, in my opinion. Try Why? Oops. Because: 1. It was after midnight the first day back at work, and I really shouldn't post in that condition. (At least when I'm drunk the posts are usually amusing to everyone else.) 2. Because I'm very wary of putting too many zeros or ones (bits) in an IP address. For instance, 192.168.1.224 is a bad address for a host when the netmask is 255.255.255.240, but that's not always obvious at first glance. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ The risk of U.S. national security resting in the hands of adults who play with children's toys during office hours is left as an exercise to the reader. - Bruce Martin in RISKS
Re: [FIXED] Re: Network Not Working!
Peter Ludwig [EMAIL PROTECTED] writes: Umm... why? What IS the /etc/lmhosts file? And if samba wants it, why is it not referred to in the Samba Documentation (the only thing I haven't done is grep the files to find it, perhaps I should...)? $ man lmhosts Reformatting lmhosts(5), please wait... [...] This *is* with Samba 2.2.0beta3 though, so you might not have it in your version. Basically, you use this file if you don't have a WINS server, all your hosts have static names, broadcasting names isn't working properly, or you think it might speed things up. e.g. I have: 192.168.15.7NEPTUNE because broadcast doesn't work over a PPP link and I want to be able to access Neptune at work from my home dialup, without worrying about how WINS will work when I disconnect. More information is in the smb.conf(5) man page under `name resolve order'. If your network works and you don't have an lmhosts file, the only effect is that you get an annoying error, which is why I said you could ignore it. You could also put the following in your smb.conf. name resolve order = bcast host -- Carey Evans http://home.clear.net.nz/pages/c.evans/ The risk of U.S. national security resting in the hands of adults who play with children's toys during office hours is left as an exercise to the reader. - Bruce Martin in RISKS
Re: Network Not Working!
Peter Ludwig [EMAIL PROTECTED] writes: I installed Debian telling it that I was on a network (the home network, two machines, nothing fancy), and yet I seem to be unable to talk to the other machine. This is the response I get from SMBCLIENT : Added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 startlmhosts: Can't open lmhosts file /etc/lmhosts. Error was No such file or directory This is generally harmless, and you can ignore it for now. error connecting to 192.168.0.11:139 (No route to host) Trying to use 192.168.0.xxx is asking for trouble, in my opinion. Try setting Linux and Windows to 192.168.1.something. The files to modify are /etc/init.d/network, /etc/hostname and /etc/hosts. The hosts file could look something like: - 127.0.0.1 localhost 192.168.1.1 linux linux.kahnnet # I'm just making up the domain. 192.168.1.2 win95 win95.kahnnet - It should look the same in C:\WINDOWS\HOSTS too. Also on Win95, set the default gateway to your Linux box. Things to try now: On Linux: `netstat -rn', `/sbin/ifconfig', `ping 192.168.1.1', `ping 192.168.1.2', `ping win95'. $ telnet win95 Trying 192.168.1.2... telnet: Unable to connect to remote host: Connection refused $ smbclient -L win95 -I 192.168.1.2 [...] $ smbclient -L win95 [... should be the same] On Win95: C:\PING 192.168.1.1 Start-Find-Computer LINUX Start-Run telnet 192.168.1.1 The output of these commands would be useful. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ The risk of U.S. national security resting in the hands of adults who play with children's toys during office hours is left as an exercise to the reader. - Bruce Martin in RISKS
Re: Network Not Working!
On Thu, Feb 11, 1999 at 12:36:14AM +1300, Carey Evans wrote: Trying to use 192.168.0.xxx is asking for trouble, in my opinion. Try Why? Regards, Lipo -- Roland E. Lipovits Vienna, Austria
Re: Network Not Working!
On 10-Feb-99 Carey Evans wrote: Trying to use 192.168.0.xxx is asking for trouble, in my opinion. Why? I've been using this series for years on a home Linux LAN with no problems at all that I'm aware of. Try setting Linux and Windows to 192.168.1.something. What difference does it make to change from 192.168.0.xxx to 192.168.1.xxx? Or is it a Windows thing? Ted. E-Mail: (Ted Harding) [EMAIL PROTECTED] Date: 10-Feb-99 Time: 11:54:30 -- XFMail --
Network Not Working!
I'm having fun here :) I've got the system setup to handle my ISP almost perfectly (still am having a problem with fetchmail not responding to all requests properly), now I've got a problem with the network at home. I installed Debian telling it that I was on a network (the home network, two machines, nothing fancy), and yet I seem to be unable to talk to the other machine. This is the response I get from SMBCLIENT : Added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 startlmhosts: Can't open lmhosts file /etc/lmhosts. Error was No such file or directory error connecting to 192.168.0.11:139 (No route to host) Now I've tried looking for a reference to /etc/lmhosts in the Samba documentation, and no help there - nothing in reference documentation about that file. I get a response from the Win95 machine (when trying to telnet to the linux box) of Host not found or some such nonsense. The Win95 Machine is setup to connect to it correctly (at least as far as I am able to determine it is). Thanks in Advance, Peter Ludwig
My network stoped working, why?
I have a generic 496 running Debian with a NE2000 clone as it's Ethernet card. One morning about 4 days ago, the other machines on the network stopped seeing it. Not this was probably about the time cleanup scripts are run. I have swapped the card with a card from another Linux box. The card I took out of this box works fine in the other machine, and the one I know have in the Debian box was working great in the other machine. I have rebuilt the kernel, both with and without loadable modules. When I build it with modules I get an error about not finding a file in /lib/modules-2.0.27/net. Building it without module sleminates this problem. However on boot up I always get some messages about SIO* loading? failed because of no such device. I have tried doing a MAKEDEV eth0, but this fails also. I had also recently upgraded from the latest I-connect CD. I out of ideas here. Can someone suggest what to check next please? Thanks. -- Stan Brown [EMAIL PROTECTED]404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead...Henry Spencer (c) 1997 Stan Brown. Redistribution via the Microsoft Network is prohibited. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
RE: My network stoped working, why?
Hi Stan: Try to determine the status of you network interface via ifconfig. If it is up and running, ping that card. If thats OK, check the physical connections. Perhaps you were moving things around and something is loose. Stan Brown wrote: -- I have a generic 496 running Debian with a NE2000 clone as it's Ethernet card. One morning about 4 days ago, the other machines on the network stopped seeing it. Not this was probably about the time cleanup scripts are run. I have swapped the card with a card from another Linux box. The card I took out of this box works fine in the other machine, and the one I know have in the Debian box was working great in the other machine. I have rebuilt the kernel, both with and without loadable modules. When I build it with modules I get an error about not finding a file in /lib/modules-2.0.27/net. Building it without module sleminates this problem. However on boot up I always get some messages about SIO* loading? failed because of no such device. I have tried doing a MAKEDEV eth0, but this fails also. I had also recently upgraded from the latest I-connect CD. I out of ideas here. Can someone suggest what to check next please? Thanks. -- Stan Brown [EMAIL PROTECTED]404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead...Henry Spencer (c) 1997 Stan Brown. Redistribution via the Microsoft Network is prohibited. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
