Yury Sulsky [EMAIL PROTECTED] wrote:
- When I recompiled, I simply changed all of the modules that I need to be
built-in, including the tulip driver. Maybe I have to do something extra to
get this to work?
The tulip driver is known to be broken on some older chipsets. You can
use the de4x5
I'm pretty sure that I'm using dhclient, that's what gets installed by
default, right?
The default DHCP client for Debian is 'pump'. Although I have had several
recommendations from others to abandon pump in favor of dhclient or dhcpcd.
On Wed, 2002-04-10 at 12:05, Steve Juranich wrote:
I'm pretty sure that I'm using dhclient, that's what gets installed by
default, right?
The default DHCP client for Debian is 'pump'. Although I have had several
recommendations from others to abandon pump in favor of dhclient or dhcpcd.
you sure about that? My install of woody came with dhclient and in fact
IIRC the install itself uses dhclient.
I'd bet money on it (not a lot though). It's true that the install uses
dhclient, but after several debian installs, the only dhcp client that Debian
has ever installed for me has
Hi,
I recently installed debian, and once I got the hang of it, I tried to
recompile the kernel. Problem is, the network stops working. This occurs
both going from a 2.2 kernel to a 2.4 one, and both using make-kpkg and
make bzlilo. What's weird is that eth0 is still there, but it can't ping
any
On Tue, 2002-04-09 at 14:14, Yury Sulsky wrote:
Hi,
I recently installed debian, and once I got the hang of it, I tried to
recompile the kernel. Problem is, the network stops working. This occurs
both going from a 2.2 kernel to a 2.4 one, and both using make-kpkg and
make bzlilo. What's
Crispin, thanks for replying.
I checked dmesg | grep tulip and dmesg | grep eth0, and the returned
lines looked the same as what I got with the default kernel. Besides,
wouldn't ifconfig -a not find eth0 if the tulip driver wasn't working?
I also installed the dhcping package, which checks to
On Tue, 2002-04-09 at 11:49, Yury Sulsky wrote:
Crispin, thanks for replying.
I checked dmesg | grep tulip and dmesg | grep eth0, and the returned
lines looked the same as what I got with the default kernel. Besides,
wouldn't ifconfig -a not find eth0 if the tulip driver wasn't working?
On Tue, 2002-04-09 at 08:22, Crispin Wellington wrote:
On Tue, 2002-04-09 at 11:49, Yury Sulsky wrote:
Crispin, thanks for replying.
I checked dmesg | grep tulip and dmesg | grep eth0, and the returned
lines looked the same as what I got with the default kernel. Besides,
wouldn't
I'm pretty sure that I'm using dhclient, that's what gets installed by
default, right?
Actually thanks for you help guys, but recompiling the kernel isn't that
important... I guess I can keep the default one until I figure out what I'm
doing wrong.
Thanks again,
Yury
On Tue, 2002-04-09 at
On Tue, 2002-04-09 at 16:32, Yury Sulsky wrote:
I'm pretty sure that I'm using dhclient, that's what gets installed by
default, right?
Actually thanks for you help guys, but recompiling the kernel isn't that
important... I guess I can keep the default one until I figure out what I'm
doing
11 matches
Mail list logo
