Re: AMD64 DHCP Network Configuration Failure
Wow, that did it! I took the card out and reinstalled and everything worked! Now it gets an IP address and connects to the internet and everything! Thank you so much! LOL. You have no idea how long I have been trying to get it to work. :) From: Dave <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Subject: Re: AMD64 DHCP Network Configuration Failure Date: Mon, 17 Jan 2005 19:19:56 -0500 Bob Proulx wrote: What does lspci say? lspci | grep Ethernet It seems strange to me that your "DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard" would have a tulip based network interface chip. IIRC that has an nvidia based onboard gigabit lan. But perhaps it is so and it is tulip as I do not have any firsthand information. The lspci will say for sure. I am guessing that your latest install is guessing the wrong driver for your interface. The first thing I would do would be to verify that the right driver module is loaded for your networking. You may need to give the system help in getting that correct. Bob I have the DFI board in question as well and its working flawlessly. I built it with the ~nov 15th-ish 4mb install image. I had a similar problem with the ethernet, but a quick search revealed the solution. Forcedeth module had to be used to get me online. AFAIK I'm still using it. I'm totally screwed if this goes down, as I have lost my printed list on what had to be done at the network setup portion. It was a fairly simple workaround. I liked it better than the Nvidia drivers which seemed to have mucked up the onboard sound once I installed them. I have no output from "lspci | grep Ethernet" (or grep -i eth) but I have forcedeth module loaded on startup. I believe the workaround during instal was to pause at the section configuring the network, alt-f2 into another console, log in as root, and remove the ethernet over firewire, insert forcedeth and the network now detects as normal. I'm currently running 2.6.9-9-amd64-k8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
On Mon, 17 Jan 2005 22:33:29 +, Pat C <[EMAIL PROTECTED]> wrote: > Well, the base systems installs however, DHCP still does not work. Here's > what I did: > > run "dhclient eth0" > > Here is the output: > --- > eth1: unkown hardware address type 24 > eth1: unkown hardware address type 24 > Listening on LPF/eth0/00:20:78:06:02:ed > Sending on LPF/eth0/00:20:78:06:02:ed > Sending on Socket/fallback/fallback-net > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 > 5 bad udp checksums in 5 packets I recall seeing this when I was trying to use an old tulip based Ethernet card. I tried another card - a $20 Realtek based gigabit card - and that problem went away. I concluded that the old card had flaws that caused it to not work well with a faster CPU. (It had worked without difficulty with an 850 MHz Athlon.) One other hint was that my DHCP server logged the request but the AMD64 client never saw them. thanks, hank -- '95 K75RT - "BABY K" '95 Miata - "OUR LC" '95 F250 4x4 - anon Beautiful Sunny Winfield -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
Bob Proulx wrote: What does lspci say? lspci | grep Ethernet It seems strange to me that your "DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard" would have a tulip based network interface chip. IIRC that has an nvidia based onboard gigabit lan. But perhaps it is so and it is tulip as I do not have any firsthand information. The lspci will say for sure. I am guessing that your latest install is guessing the wrong driver for your interface. The first thing I would do would be to verify that the right driver module is loaded for your networking. You may need to give the system help in getting that correct. Bob I have the DFI board in question as well and its working flawlessly. I built it with the ~nov 15th-ish 4mb install image. I had a similar problem with the ethernet, but a quick search revealed the solution. Forcedeth module had to be used to get me online. AFAIK I'm still using it. I'm totally screwed if this goes down, as I have lost my printed list on what had to be done at the network setup portion. It was a fairly simple workaround. I liked it better than the Nvidia drivers which seemed to have mucked up the onboard sound once I installed them. I have no output from "lspci | grep Ethernet" (or grep -i eth) but I have forcedeth module loaded on startup. I believe the workaround during instal was to pause at the section configuring the network, alt-f2 into another console, log in as root, and remove the ethernet over firewire, insert forcedeth and the network now detects as normal. I'm currently running 2.6.9-9-amd64-k8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
Pat C wrote: > David Sawyer wrote: > > Pat C wrote: > > > do it. When I go to configure it manually to see if it works, I put in > > > all the information and then the system goes blank. > > > > What do you do to configure it manually. Did you edit the > > /etc/network/interfaces file, or just type ifconfig eth0 ip netmask > > netmask_addr. > > No, this is during the installation process. There is an option that > allows you to manually put in an IP address and gateway and so on. Is > there a way to see the linux unpack and load before it gets to choosing a > language? It scrolls by too fast for me to read. > > When exactly does the system go blank. During startup if you changed > > the above file I mentioned, or after using ifconfig? > > ... > > Can you do anything when it goes blank, try switching consoles or > > Ct-alt-del it. Or Is the system hard frozen? I agree. When I hear of a system going blank I am thinking that it crashed. A kernel panic. But I think the poster is using it as a slang for something completely different. > When I try putting the values in manually, I put in the IP address, > netmask, gateway, and nameserver. AHHh... ok, I think I figured it out. > If you put in a nameserver and you're not using a nameserver (me) then it > hangs. Hangs, going blank. These terms confuse us poor folks on the mailing list who are used to specific meanings for those words. It would be most helpful if you could be very precise and to describe exactly what it is that is happening. > When I check "lsmod", Tulip shows up so the module is running I > assume. Any other thoughts? Thanks! What does lspci say? lspci | grep Ethernet It seems strange to me that your "DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard" would have a tulip based network interface chip. IIRC that has an nvidia based onboard gigabit lan. But perhaps it is so and it is tulip as I do not have any firsthand information. The lspci will say for sure. I am guessing that your latest install is guessing the wrong driver for your interface. The first thing I would do would be to verify that the right driver module is loaded for your networking. You may need to give the system help in getting that correct. Bob signature.asc Description: Digital signature
Re: AMD64 DHCP Network Configuration Failure
Well, the base systems installs however, DHCP still does not work. Here's what I did: run "dhclient eth0" Here is the output: --- eth1: unkown hardware address type 24 eth1: unkown hardware address type 24 Listening on LPF/eth0/00:20:78:06:02:ed Sending on LPF/eth0/00:20:78:06:02:ed Sending on Socket/fallback/fallback-net DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 5 bad udp checksums in 5 packets DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 No DHCPOFFERS received No working leases in persistant database Sleeping. When I check "lsmod", Tulip shows up so the module is running I assume. Any other thoughts? Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
From: David Sawyer <[EMAIL PROTECTED]> Reply-To: David Sawyer <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Subject: Re: AMD64 DHCP Network Configuration Failure Date: Mon, 17 Jan 2005 14:58:30 -0500 On Mon, 17 Jan 2005 18:37:21 +, Pat C <[EMAIL PROTECTED]> wrote: > I just put a new system together. Here are the specs: > > AMD64 3200+ CPU > 512MB DDR 3200 RAM > 3DFX 16MB Graphics Card... old, yes I know :) > Standard CD-Drive > 20GB IDE Hard Drive > 550 Watt Power Supply > Antec Case > Bridgecom 10/100 Fast Ethernet NIC > DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard (onboard > 10/100/1000 Ethernet, Audio, USB, and Firewire) > > I am using the SargeAMD64 NetInstall .ISO Everything works until I get to > the network configuration section. My Bridgecom 10/100 card shows up, as > well as firewire (eth1). However, my onboard ethernet on the motherboard > doesn't. Ok I think, I'll just use the older one for now. It goes to get > DHCP information and can't do it. I put in my hostname and it still can't > do it. When I go to configure it manually to see if it works, I put in all > the information and then the system goes blank. What do you do to configure it manually. Did you edit the /etc/network/interfaces file, or just type ifconfig eth0 ip netmask netmask_addr. No, this is during the installation process. There is an option that allows you to manually put in an IP address and gateway and so on. Is there a way to see the linux unpack and load before it gets to choosing a language? It scrolls by too fast for me to read. When exactly does the system go blank. During startup if you changed the above file I mentioned, or after using ifconfig? When I try putting the values in manually, I put in the IP address, netmask, gateway, and nameserver. AHHh... ok, I think I figured it out. If you put in a nameserver and you're not using a nameserver (me) then it hangs. I left the nameserver out and it worked and continued on to the hostname setup. I think it would be beneficial to add a check so that if the nameserver doesn't work it can continue on without one. This might confuse people. Also there is a default value in the nameserver. Maybe just leave it blank? I will continue with the installation and see if I can configure DHCP from the commandline. Thank you. Can you do anything when it goes blank, try switching consoles or Ct-alt-del it. Or Is the system hard frozen? >I know everything should > work because I tried an old version of Debian for i386 and it could find > everything for DHCP easily. Does anyone have any suggestions? Could this > be a bug? Thank you for the help. :) DHCP seems like less of a problem as the system blanking when you try to configure it. If the network card and module are working, you can run dhclient anytime. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
On Mon, 17 Jan 2005 18:37:21 +, Pat C <[EMAIL PROTECTED]> wrote: > I just put a new system together. Here are the specs: > > AMD64 3200+ CPU > 512MB DDR 3200 RAM > 3DFX 16MB Graphics Card... old, yes I know :) > Standard CD-Drive > 20GB IDE Hard Drive > 550 Watt Power Supply > Antec Case > Bridgecom 10/100 Fast Ethernet NIC > DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard (onboard > 10/100/1000 Ethernet, Audio, USB, and Firewire) > > I am using the SargeAMD64 NetInstall .ISO Everything works until I get to > the network configuration section. My Bridgecom 10/100 card shows up, as > well as firewire (eth1). However, my onboard ethernet on the motherboard > doesn't. Ok I think, I'll just use the older one for now. It goes to get > DHCP information and can't do it. I put in my hostname and it still can't > do it. When I go to configure it manually to see if it works, I put in all > the information and then the system goes blank. What do you do to configure it manually. Did you edit the /etc/network/interfaces file, or just type ifconfig eth0 ip netmask netmask_addr. When exactly does the system go blank. During startup if you changed the above file I mentioned, or after using ifconfig? Can you do anything when it goes blank, try switching consoles or Ct-alt-del it. Or Is the system hard frozen? >I know everything should > work because I tried an old version of Debian for i386 and it could find > everything for DHCP easily. Does anyone have any suggestions? Could this > be a bug? Thank you for the help. :) DHCP seems like less of a problem as the system blanking when you try to configure it. If the network card and module are working, you can run dhclient anytime. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
AMD64 DHCP Network Configuration Failure
I just put a new system together. Here are the specs: AMD64 3200+ CPU 512MB DDR 3200 RAM 3DFX 16MB Graphics Card... old, yes I know :) Standard CD-Drive 20GB IDE Hard Drive 550 Watt Power Supply Antec Case Bridgecom 10/100 Fast Ethernet NIC DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard (onboard 10/100/1000 Ethernet, Audio, USB, and Firewire) I am using the SargeAMD64 NetInstall .ISO Everything works until I get to the network configuration section. My Bridgecom 10/100 card shows up, as well as firewire (eth1). However, my onboard ethernet on the motherboard doesn't. Ok I think, I'll just use the older one for now. It goes to get DHCP information and can't do it. I put in my hostname and it still can't do it. When I go to configure it manually to see if it works, I put in all the information and then the system goes blank. I know everything should work because I tried an old version of Debian for i386 and it could find everything for DHCP easily. Does anyone have any suggestions? Could this be a bug? Thank you for the help. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
