Re: Networking not working
On Sat, 5 Nov 2005 10:46:26 -0600, "Thomas F. O'Connell" <[EMAIL PROTECTED]> wrote: > > On Nov 5, 2005, at 8:49 AM, Austin (Ozz) Denyer wrote: > > > On Fri, 4 Nov 2005 20:54:16 -0600, "Thomas F. O'Connell" > > <[EMAIL PROTECTED]> wrote: > >> > >> Has anyone had any difficulty getting networking going under sarge > >> amd64? > > > > It would help greatly if you could give us some error messages to chew > > on. > > Well, here's what happens: > > During installation, it gets to the point where it recognizes and > displays my three network interfaces. I choose the e100, which has > traditionally been eth0, as the primary interface. Looking on the Alt- > F3 virtual console, I see the following lines: > > insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/mii.ko > insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/e100.ko > insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/tg3.ko > > Then, back on the installer console, it tells me that it's going to > detect DHCP. This fails. There are no further messages or errors on > the other console other than: > > insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/block/ > floppy.ko > FATAL: Error inserting floppy (/lib/modules/2.6.8-11-amd64-generic/ > kernel/drivers/block/floppy.ko): No such device > > But that's not related to DHCP detection, is it? No. > Then I try to configure the network manually with the IP the box had > before I attempted to reinstall, along with the local network address > for the router and the correct netmask. I leave the nameserver blank. Do you allow the installer to continue anyway? I had to, and then finish setting up networking after the reboot. What does ifconfig show? > The installer pauses for a bit and then returns with the hostname > prompt. > > Is there any way to determine at this point in the installation > process whether the network card has been successfully recognized and > is working? Or to further diagnose why DHCP was not able to be > autoconfigured? Would expert mode help? I'd check the output of ifconfig. Also (and I know this may sound silly) check to make sure that the network cable is plugged into the right NIC. If you have three NICs then they may not be getting assigned the way you think. Mine swapped over after installing X/KDE for some reason. Regards, Ozz. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 5, 2005, at 11:12 AM, Thomas F. O'Connell wrote: On Nov 5, 2005, at 10:46 AM, Thomas F. O'Connell wrote: On Nov 5, 2005, at 8:49 AM, Austin (Ozz) Denyer wrote: On Fri, 4 Nov 2005 20:54:16 -0600, "Thomas F. O'Connell" <[EMAIL PROTECTED]> wrote: So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? It would help greatly if you could give us some error messages to chew on. Well, here's what happens: During installation, it gets to the point where it recognizes and displays my three network interfaces. I choose the e100, which has traditionally been eth0, as the primary interface. Looking on the Alt-F3 virtual console, I see the following lines: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/e100.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/tg3.ko Then, back on the installer console, it tells me that it's going to detect DHCP. This fails. There are no further messages or errors on the other console other than: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/block/ floppy.ko FATAL: Error inserting floppy (/lib/modules/2.6.8-11-amd64-generic/ kernel/drivers/block/floppy.ko): No such device But that's not related to DHCP detection, is it? Then I try to configure the network manually with the IP the box had before I attempted to reinstall, along with the local network address for the router and the correct netmask. I leave the nameserver blank. The installer pauses for a bit and then returns with the hostname prompt. Is there any way to determine at this point in the installation process whether the network card has been successfully recognized and is working? Or to further diagnose why DHCP was not able to be autoconfigured? Would expert mode help? For what it's worth, I am now having the same problem with the sid amd64 testing netinst image. Okay. I'm a little closer to tracking it down, now. For comparison with sarge and sid, I tried the Ubuntu AMD64 installer CD. The installer is, of course, very similar to Debian, but the Ubuntu installer chose a different ordering for my network cards, putting one of the Broadcom NetXtreme cards as eth0 rather than the Intel Ethernet Pro 100. I had just been assuming that the Intel was the card I had been using before reinstalling this system, but I guess it's been one of the two Broadcoms because DHCP autoconfiguration worked. If I can be of assistance in improving default selection of the primary network interface for the Debian Installer, please let me know. I don't know if this is an amd64 issue or not, so also please let me know if I should post the results of all these attempts on another list. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 5, 2005, at 10:46 AM, Thomas F. O'Connell wrote: On Nov 5, 2005, at 8:49 AM, Austin (Ozz) Denyer wrote: On Fri, 4 Nov 2005 20:54:16 -0600, "Thomas F. O'Connell" <[EMAIL PROTECTED]> wrote: So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? It would help greatly if you could give us some error messages to chew on. Well, here's what happens: During installation, it gets to the point where it recognizes and displays my three network interfaces. I choose the e100, which has traditionally been eth0, as the primary interface. Looking on the Alt-F3 virtual console, I see the following lines: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/e100.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/tg3.ko Then, back on the installer console, it tells me that it's going to detect DHCP. This fails. There are no further messages or errors on the other console other than: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/block/ floppy.ko FATAL: Error inserting floppy (/lib/modules/2.6.8-11-amd64-generic/ kernel/drivers/block/floppy.ko): No such device But that's not related to DHCP detection, is it? Then I try to configure the network manually with the IP the box had before I attempted to reinstall, along with the local network address for the router and the correct netmask. I leave the nameserver blank. The installer pauses for a bit and then returns with the hostname prompt. Is there any way to determine at this point in the installation process whether the network card has been successfully recognized and is working? Or to further diagnose why DHCP was not able to be autoconfigured? Would expert mode help? For what it's worth, I am now having the same problem with the sid amd64 testing netinst image. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 5, 2005, at 8:49 AM, Austin (Ozz) Denyer wrote: On Fri, 4 Nov 2005 20:54:16 -0600, "Thomas F. O'Connell" <[EMAIL PROTECTED]> wrote: So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? It would help greatly if you could give us some error messages to chew on. Well, here's what happens: During installation, it gets to the point where it recognizes and displays my three network interfaces. I choose the e100, which has traditionally been eth0, as the primary interface. Looking on the Alt- F3 virtual console, I see the following lines: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/e100.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/tg3.ko Then, back on the installer console, it tells me that it's going to detect DHCP. This fails. There are no further messages or errors on the other console other than: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/block/ floppy.ko FATAL: Error inserting floppy (/lib/modules/2.6.8-11-amd64-generic/ kernel/drivers/block/floppy.ko): No such device But that's not related to DHCP detection, is it? Then I try to configure the network manually with the IP the box had before I attempted to reinstall, along with the local network address for the router and the correct netmask. I leave the nameserver blank. The installer pauses for a bit and then returns with the hostname prompt. Is there any way to determine at this point in the installation process whether the network card has been successfully recognized and is working? Or to further diagnose why DHCP was not able to be autoconfigured? Would expert mode help? -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Fri, 4 Nov 2005 20:54:16 -0600, "Thomas F. O'Connell" <[EMAIL PROTECTED]> wrote: > > So I finally made it through the installation process (see nearby > thread about software RAID, LVM, and LILO), and lo and behold: > networking isn't working. The primary ethernet card (of three) in > this machine is an Intel Ethernet Pro 100, and the e100 module seems > to load fine and be recognized, but I don't seem to be able to ping > the router on my local network, so I'm suspicious of the network card. > > During installation, DHCP was not detected, and after reboot during > base-config, apt setup couldn't be completed normally because, I > suspect, of networking issues. > > Has anyone had any difficulty getting networking going under sarge > amd64? It would help greatly if you could give us some error messages to chew on. I just set up my new box (Tyan K8WE dual-Opteron246) using Len Sorensen's modified Sarge installer with the 2.6.12 kernel (Thanks, Len!). Initially my NICs were not detected either - all it found was the FireWire networking, which I don't use. I continued anyway, and on reboot the NICs were found and the forcedeth driver loaded. However, I did have to add them to /etc/network/interfaces and then run /etc/init.d/networking stop|start to get them running properly. I've since upgraded to 2.6.14-2 to get around the Opteron SMP issues. Note - after installing X/KDE, my NICs swapped over (!). The only issue I have with it now is my graphics card (EVGA GeForce 6600GT PCI-E) but looking at the posts over the last few days it appears I'm not alone there (it needs the nVidia 7714 driver)... For the time being I'm using the VESA driver (the nv driver causes screen corruption after a few minutes of use) but it's not really a big issue for me, as I just need to get a lot of (mainly text) on the screen at once - FPS is unimportant. Regards, Ozz. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On 11/4/05, Hamish Moffatt <[EMAIL PROTECTED]> wrote: > On Sat, Nov 05, 2005 at 12:02:22AM -0600, Thomas F. O'Connell wrote: > > On Nov 4, 2005, at 9:04 PM, lordSauron wrote: > > >Yes, it seemed to me that most of the NICs aren't supported yet. I > > >had to forsake my mboard integrated Realtek Gigabit Ethernet for a old > > >3Com 100/10 PCI card until kernel -12 debuted, in which support was > > >added. I don't know who to contact to request the addding of your > > >particular card, but when you do, ensure to send him/her/it (you never > > >know...) every single last detail about the card, all the way down to > > >the S/N, so that there's no confusion about which driver they're > > >working with. > > > > > >Hope you find a solution! > > > > Is there any way to track device driver support? > > What devices do you have? > > I haven't found the situation to be as bad as lordSauron says. > > The Realtek 8169 on an AthlonXP board I have has worked since early 2.6.x > with the r8169 driver. In kernel -11 it didn't work at all with my ECS Elitegroup nForce 2-A board which has a... oh, I'm sorry. It wasn't Realtek. That was my audio device (which also didn't work with -11, BTW). My mboard manual says it's a "IEEE 802.3 nVidia MAC for 100Base-TX/10Base-T Fast Ethernet/Ethernet," however, I thought that the Linux installer said it was a Realtek product... whatever. Whatever's on the aforesaid mboard, that's what I have/had. > The Gigabyte Athlon64 board has on-board NICs supported using the > sk98lin and forcedeth drivers. I started with 2.6.8 and those were > supported fine. Lucky you. I was not so fortunate. It works now, so I'm not particularly feeling bad/good, but it did put me on a older set of PCI components for a good month or so until the new Kernel came out. -- === GCB v3.1 === GCS d-(+) s+:- a? C+() UL+++() P L++(+++) E- W+(+++) N++ w--- M>++ PS-- PE Y+ PGP- t++(+++) 5? X? R !tv>-- b++> DI+++> D-- G !e h(*) !r x--- === EGCB v3.1 ===
Re: Networking not working
On Sat, Nov 05, 2005 at 12:02:22AM -0600, Thomas F. O'Connell wrote: > On Nov 4, 2005, at 9:04 PM, lordSauron wrote: > >Yes, it seemed to me that most of the NICs aren't supported yet. I > >had to forsake my mboard integrated Realtek Gigabit Ethernet for a old > >3Com 100/10 PCI card until kernel -12 debuted, in which support was > >added. I don't know who to contact to request the addding of your > >particular card, but when you do, ensure to send him/her/it (you never > >know...) every single last detail about the card, all the way down to > >the S/N, so that there's no confusion about which driver they're > >working with. > > > >Hope you find a solution! > > Is there any way to track device driver support? What devices do you have? I haven't found the situation to be as bad as lordSauron says. The Realtek 8169 on an AthlonXP board I have has worked since early 2.6.x with the r8169 driver. The Gigabyte Athlon64 board has on-board NICs supported using the sk98lin and forcedeth drivers. I started with 2.6.8 and those were supported fine. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 4, 2005, at 9:04 PM, lordSauron wrote: Yes, it seemed to me that most of the NICs aren't supported yet. I had to forsake my mboard integrated Realtek Gigabit Ethernet for a old 3Com 100/10 PCI card until kernel -12 debuted, in which support was added. I don't know who to contact to request the addding of your particular card, but when you do, ensure to send him/her/it (you never know...) every single last detail about the card, all the way down to the S/N, so that there's no confusion about which driver they're working with. Hope you find a solution! Is there any way to track device driver support? -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
Yes, it seemed to me that most of the NICs aren't supported yet. I had to forsake my mboard integrated Realtek Gigabit Ethernet for a old 3Com 100/10 PCI card until kernel -12 debuted, in which support was added. I don't know who to contact to request the addding of your particular card, but when you do, ensure to send him/her/it (you never know...) every single last detail about the card, all the way down to the S/N, so that there's no confusion about which driver they're working with. Hope you find a solution!
Networking not working
So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
