On Tue, Apr 23, 2002 at 04:47:20PM -0400, Thomas R. Shemanske wrote:
>
> First, the presumption is that this is not a PCMCIA interface.
>
Yes.
> Second, it might help to see /etc/network/interfaces
>
OK. Here it is:
# /etc/network/interfaces -- configuration file for ifup(8),
Sridhar M.A. wrote:
On Sat, Apr 20, 2002 at 03:03:59PM -0800, Greg C. Madden wrote:
> >
> I missed the Config_Filter option myself for awhile, nic card could not
> be activated during boot.
>
> Kernel config file (.config)
>
> # Networking options
> #
> CONFIG_P
On Sat, Apr 20, 2002 at 03:03:59PM -0800, Greg C. Madden wrote:
> >
> I missed the Config_Filter option myself for awhile, nic card could not
> be activated during boot.
>
> Kernel config file (.config)
>
> # Networking options
> #
> CONFIG_PACKET=y
> # CONFIG_PACKE
Found the problem and fixed it - I needed to set CONFIG_FILTER to 1 (enable
socket filter support) during kernel configuration and recompile the kernel
- it is required for the dhclient to work. Thanks for your help!
Deepak
At 01:27 AM 4/21/02 , David Smead wrote:
bring the interface down th
bring the interface down that is using it first.
--
Sincerely,
David Smead
http://www.amplepower.com.
On Sat, 20 Apr 2002, Deepak Subburam wrote:
> I have the following in /etc/networking/interfaces:
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> # The loopback inte
Deepak Subburam <[EMAIL PROTECTED]> writes:
> Also, when I try to rmmod 3c509 (the module I compiled and loaded for the
> network device support), I get the message:
> 3c509: Device or resource busy
Try taking the interface down with ifconfig prior to removing the
module like so:
ifconfig eth0 d
I have the following in /etc/networking/interfaces:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created during the Debian
installation
auto eth0
iface eth0 inet dhcp
Also
On Sat, 2002-04-20 at 13:01, Deepak Subburam wrote:
> Hello!
> I am a new user to Debian (and Linux) and just compiled the 2.4.18 kernel
> since the 2.2.20-compact kernel that I was using did not support sound or
> my USB mouse.
>
> The new kernel works fine and my soundcard and USB mouse work O
]
Sent: 20 April 2002 22:14
To: Deepak Subburam
Cc: debian-user@lists.debian.org
Subject: Re: Can't connect to internet with new kernel
What do you have in /etc/network/interfaces?
--
Sincerely,
David Smead
http://www.amplepower.com.
On Sat, 20 Apr 2002, Deepak Subburam wrote:
> Hello!
Deepak Subburam <[EMAIL PROTECTED]> writes:
[before]
> eth0 Link encap:Ethernet HWaddr 00:60:08:20:19:C8
>inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
...
[after]
> eth0 Link encap:Ethernet HWaddr 00:60:08:20:19:C8
[no ip a
What do you have in /etc/network/interfaces?
--
Sincerely,
David Smead
http://www.amplepower.com.
On Sat, 20 Apr 2002, Deepak Subburam wrote:
> Hello!
> I am a new user to Debian (and Linux) and just compiled the 2.4.18 kernel
> since the 2.2.20-compact kernel that I was using did not support
Hello!
I am a new user to Debian (and Linux) and just compiled the 2.4.18 kernel
since the 2.2.20-compact kernel that I was using did not support sound or
my USB mouse.
The new kernel works fine and my soundcard and USB mouse work OK! However,
my 3COM 3c509B card doesn't work and I can't conn
12 matches
Mail list logo