Deephay Z wrote:
Greetings all,
since I need to install the wireless device driver for the Debian system,
so I compiled and installed the 2.6.13.2 version kernel, but the eth0
(wired-ethernet card) now cannot be found using the newer kernel. Some kinda
":eth0: no such device" is displayed on t
sorry for this dupicate post, I just thought the post through the usenet is
not
going to sucess..
On Tue, 20 Sep 2005 00:38:51 +0800
Deephay Z <[EMAIL PROTECTED]> wrote:
> Greetings all,
>
> since I need to install the wireless device driver for the Debian system,
> so I compiled and instal
Greetings all,
since I need to install the wireless device driver for the Debian system,
so I compiled and installed the 2.6.13.2 version kernel, but the eth0
(wired-ethernet card) now cannot be found using the newer kernel. Some kinda
":eth0: no such device" is displayed on the screen during bo
I fingered it out. In /var/lib/dhcp/dhcp.leases the
dlink put in a very long lease(about 3 months) I
deleted the entry now my machine knows nothing about
192.168.0.1. Kevin if you don't want to wait you can
shorten the amount of time it looks for a dhcp server
in
/etc/dhclient.conf timeout
I set
On Sun, 13 Jul 2003 14:03:16 -0700 (PDT)
Bruce Banner <[EMAIL PROTECTED]> wrote:
> Okay I only used the exclamation marks to get your
> attention. My problem is that I had to change my IP
> address from dhcp to static to setup my dlink
> broadband router then I changed eth0 back to dhcp.
> Now u
Okay I only used the exclamation marks to get your
attention. My problem is that I had to change my IP
address from dhcp to static to setup my dlink
broadband router then I changed eth0 back to dhcp.
Now upon rebooting my laptop if I don't have my cable
plugged in it takes along time for it to ge
Sent: Friday, September 27, 2002 11:20 PM
Subject: Re: 1Re: eth0 problem after kernal package upgrade
> "Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
>
> Neal> a... I found the driver in
> Neal> /lib/modules/2.4.18-k7/kernel/drivers/net/
&g
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> a... I found the driver in
Neal> /lib/modules/2.4.18-k7/kernel/drivers/net/
>> "eth0: Macronix 98715 PMAC rev 37 at 0xd400,
>> 00:80:C6:EA:C0:69, IRQ 4 eth0: EEPROM default media type
>> 10baseT. via-rhine.c:v
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> Thanks Shayamal. I have the following lines from 'dmesg' on
Neal> 2.2.20 kernel:
Neal> "eth0: Macronix 98715 PMAC rev 37 at 0xd400,00:80:C6:EA:C0:69, IRQ 4
Neal> eth0: EEPROM default media type 10baseT.
Neal> via-
a... I found the driver in /lib/modules/2.4.18-k7/kernel/drivers/net/
- Original Message -
From: "Neal Pollock" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Shyamal Prasad"
<[EMAIL PROTECTED]>
Sent: Friday, September 27, 2002 10:19 PM
Subject:
for 2.4.18 from this?
Neal.
- Original Message -
From: "Shyamal Prasad" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 27, 2002 9:22 AM
Subject: Re: eth0 problem after kernal package upgrade
> "Neal" == Neal Pollock <[EMAIL
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> Thanks for the repsonse, here's my details:
Neal> http://members.rogers.com/npollock1/sysinfo.txt
Neal,
I think the only thing you missed there is the kind of NIC you
have. If you don't know this look in the output of 'lspci'
Thanks for the repsonse, here's my details:
http://members.rogers.com/npollock1/sysinfo.txt
Neal.
- Original Message -
From: "nate" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 2:46 PM
Subject: Re: eth0 problem after kern
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> i recently upgraded my kernel from 2.2.20 to 2.4.18 using a
Neal> kernel image via dselect. Unfortunately when I boot the new
Neal> kernel i cannot establish an internet connection. Am I
Neal> correct in assuming that
Neal Pollock said:
> i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image
> via dselect. Unfortunately when I boot the new kernel i cannot establish
> an internet connection. Am I correct in assuming that i need to to
> check:
>
> a) eth0 is properly configured
> b) dhcpclien
Neal Pollock wrote:
> i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image via
> dselect. Unfortunately when I boot the new kernel i cannot establish an
> internet connection. Am I correct in assuming that i need to to check:
>
> a) eth0 is properly configured
> b) dhcpclien
i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image via
dselect. Unfortunately when I boot the new kernel i cannot establish an
internet connection. Am I correct in assuming that i need to to check:
a) eth0 is properly configured
b) dhcpclient obtained an IP
inorder to tro
Well, I'm realizing what has happened here. I installed potato on my
wife's machine and in the libranet cd it asked for network connection
data. I entered my IP address (static IP), dns name servers, gateway,
domain, etc.. then when I configured the kernel, I configured it using
dhcp.
Now, I find
I just did a dist-upgrade and installed netscape 4.76. Now it seems my
eth0 connection (cable modem) won't stay active. I am unable to connect
to anything and then when I switch to init 1 and back [ctrl-d] then I
have a connection that works.
Has anyone else had this problem? I'm wondering if it'
On Sat, Nov 25, 2000 at 01:58:12PM +1100, Daniel Knights wrote:
> >Do the servers all have the same type of network-cards? I have a 3Com
> >3c900 Combo and it seems this card doesn't react anymore after some
> >time. An ifdown+ifup brings it back again.
> >Phil
> >
> Hi Phil
>
> The card is a Ne
>
> The card is a Netgear with a Tulip Digital 21040 chip which is what we have
> in the Redhat and SuSe servers and they do not behave this way.
Do they all have the same kernel (read: driver) version ? Maybe Suse/RH
use a newer driver ? Because I can remember tulip drivers having problems
with
>Do the servers all have the same type of network-cards? I have a 3Com
>3c900 Combo and it seems this card doesn't react anymore after some
>time. An ifdown+ifup brings it back again.
>Phil
>
Hi Phil
The card is a Netgear with a Tulip Digital 21040 chip which is what we have
in the Redhat and SuSe
On Sat, Nov 25, 2000 at 02:20:59AM +1100, Daniel Knights wrote:
> I have added 3 Debian boxes to my network and they all seem OK, till I
> noticed that when changing some of the cat5 cables around, that the 3
> debian boxes eth0 does not start passing data again when cat 5 is replaced,
> the ca
Hi,
I have added 3 Debian boxes to my network and they all seem OK, till I
noticed that when changing some of the cat5 cables around, that the 3
debian boxes eth0 does not start passing data again when cat 5 is replaced,
the cables were only removed for a minute or less.I did not notice
stra
Thanks Jor-el,
I upgraded dhcpcd and netbase and it works like a charm. The fact that 2.2
kernels require an upgrade is documented in the release notes section on
www.debian.org. (Yes I am embarrassed - I should have caught that myself)
Thanks also to Paul Wade, who also dropped me a helpful not
I am using such a system. I compiled the kernel with module autoloading,
but I also have /etc/modules like this
#auto
ne2k-pci
It works fine. My network card is automatically detected an
-BEGIN PGP SIGNED MESSAGE-
Rupert,
I assume that you are running Slink. Have to installed the upgrade
versions of the packages that are required for your to be running the
2.2.x kernels? I belive the net-tools package is one of the packages that
need to be ugraded, so I am not at
On Mon, Aug 02, 1999 at 09:25:14PM -0400, Rupert Brooks wrote:
> Hi,
>
> I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my
> ne2000 clone PCI ethernet card does not work with either.
>
> With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded
> without a hitc
Hi,
I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my
ne2000 clone PCI ethernet card does not work with either.
With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded
without a hitch and dhcpcd configured the ip information flawlessly. (
I use an ADSL conne
29 matches
Mail list logo
