• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Debian installer can't configure network device

M

Mucman

Diamond Member
I checked my DHCP log on my router and I see the following :

Jan 15 09:59:39 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 09:59:41 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 09:59:46 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 09:59:47 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 09:59:56 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 09:59:57 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:00:16 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:00:17 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:00:35 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:00:36 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:13:41 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:13:42 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:13:48 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:13:49 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:01 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:02 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:09 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:10 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:24 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:25 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:34 - dhcpd: DHCPDISCOVER from 00:01:02:3d:c5:3f via eth1
Jan 15 10:14:35 - dhcpd: DHCPOFFER on 192.168.0.13 to 00:01:02:3d:c5:3f via eth1

This is only after two times to configure the network. In the Debian installer I go to the shell (ASH shell) I can ping 127.0.0.1, but I can't
ping localhost , 192.168.0.1 , nor the IP that I am supposed to get from my router. When I configure the network manually the only thing that works
is that I can ping my IP address, but I still can't ping 192.168.0.1

I installed Debian this way for Potato, but I am trying out Woody now and I have hit this road block, but this seems like a network error of some kind.

Any ideas?
 
This is getting weird....

I checked my ARP table in my win2k box and I saw an entry for the IP to the Debian box with the appropriate IP (I configured the network settings manualy). The MAC was correct, so I am guessing this came as a broadcast from the Debian machine. I removed the entry from the ARP cache and then tried to ping 192.168.0.4 (the IP I gave the machine) I got request not found and the ARP table showed all 0's for the MAC.

I am starting to link this to flakiness of the new Woody distro now. I am going to try it again with the Potato boot disks and see if the same problems occur.
 
I am starting to link this to flakiness of the new Woody distro now. I am going to try it again with the Potato boot disks and see if the same problems occur.

I would suspect something else, I've done network installs of woody several times (all with custom boot disks for XFS support though) and never had that problem.
 
I am having problems pin-pointing the problem though. Someone on the debian-users list fixed his problem by using the brand new woody bootdisks (he was using the potato disks). I am going to re-format my disks and re make the boot disks. I need to use the disks for UDMA66 (or above) or else my HD isn't detected, and the new Woody floppys support the 3c905c, right?
 
I didn't use the normal woody boot disks becuse I needed (well, wanted) XFS support, so I compiled my own kernel with support for all the hardware I had built in.
 
When I try to use the module already compiled in the kernel I get the following messages in my log file :

SIOCSIFADDR : No buffer space available
SIOCSIFNETMASK: Cannot assign requested address
SIOCSIFBRDADDR: Cannot assign requested address

I also don't see the the DHCP requests coming from the machine using the default kernel settings.

I think when I am done with this, I am going to go through a crash course on making my own boot floppies 🙂
 
Argh... You are right... I just tried it with the Potato disks that I had no problem on last time and I get the same problem 🙁. Maybe problems with my NIC? The Potato drivers
worked fine before and now they don't. I know the cable is good because I swapped it with mine and I seem to have no problems.
 
How much better is XFS vs. ext3?

XFS FAQ
XFS Home page

I think when I am done with this, I am going to go through a crash course on making my own boot floppies

It's not hard, and all I did was compile my own kernel with all my hardware support built in and put it on the boot disk, overwriting the 'linux' kernel already there.
Putting utils on the root disk just consists of gunzip'ing it, mounting the image over loopback, copying files to it, re-gzip'ing it and writing it to a floppy again.
 
A long day at work and my brother challenging me to a game of Links 2001 has made this reply very very late. Now I sit here with a 20oz coffee, biscotti, and my O'reilly's "Running Linux" book. I think I am ready to roll 🙂

I have bookmarked those links for future reference (my darn bookmark list is getting huge, maybe I should take a few days to read it all). I find it odd that this is happening
considering everything I have is supported by Woody.

I got about 3 hours to play around with this! Wish me luck

<edit>Nevermind! Looks like the computer is on its last legs... 2/3 PCI slots don't work now... going to bury this old relic when AST was in its hey-day.</edit>
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top