Hi,
When you configured your kernel (with 'make menuconfig' or 'make
xconfig'), did you select the rtl8139 driver? This is under the
Network Devices options, 10/100 MBPS. I personally suggest compiling
it as a module so that an "M" shows up next to it in the square
brackets.
For compiling the ker
e -
From: "Elizabeth Barham" <[EMAIL PROTECTED]>
To:
Sent: Thursday, May 02, 2002 7:53 PM
Subject: Re: SIOCADDRT : No such device
> [EMAIL PROTECTED] writes:
>
> > Also, when I do make config, I select all default. How do I know,
> > what card, I have.
&
--
On Thu, 2 May 2002 19:36:00
dkotian3 wrote:
>Hi,
>>>What an ifconfig give you ?
>> ifconfig eth0
> eth0: error fetching interface information: Device not found
Hi,
Can you also mail the output of cat /proc/interrupts.
I have a weird feeling that your eth0 will not be listed there,
Thanks
[EMAIL PROTECTED] writes:
> Also, when I do make config, I select all default. How do I know,
> what card, I have.
Depends on your machine's bus. For pci, use "lspci". It has
a verbose option which can be increased with more v's, as in
lspci -vv
With an ISA bus (and PNP devices), use
pnpdump
Hi,
>>What an ifconfig give you ?
ifconfig eth0
eth0: error fetching interface information: Device not found
>>Did you compile it in the kernel ?
I did it, and boot with the new kernel.
I have both 2.2.19 installed from CD and also 2.4.18 (source from
kernel.org).
When I do uname -a, I c
On Thu, 2 May 2002 12:29:44 +0500 (IST)
[EMAIL PROTECTED] wrote:
> Thanks ,
> Could someone help in how to add network drivers for debian.
> The network card seems to be RTL8129.
>
> Thanks and Regards
> Deepak
RTL8129/39.. Drivers have an excellent support these days. I have been using
mine
>Thanks ,
>Could someone help in how to add network drivers for debian.
>The network card seems to be RTL8129.
>
>Thanks and Regards
>Deepak
Hi,
What an ifconfig give you ?
Did you compile it in the kernel ?
Did you configure your /etc/network/interfaces file ?
Give us more informations...
Thanks ,
Could someone help in how to add network drivers for debian.
The network card seems to be RTL8129.
Thanks and Regards
Deepak
[EMAIL PROTECTED] wrote
You'll have to put a driver for your nic in /etc/modules.
--
Sincerely,
David Smead
http://www.amplepower.com.
On Thu, 2 May 2002
You'll have to put a driver for your nic in /etc/modules.
--
Sincerely,
David Smead
http://www.amplepower.com.
On Thu, 2 May 2002 [EMAIL PROTECTED] wrote:
> Hi,
>
> I have a similar porblem.
> I have upgraded it to 2.4.18 from the source code www.kernel.org.
> And when I do ifconfig eth0, I ge
>I have a similar porblem.
>I have upgraded it to 2.4.18 from the source code >www.kernel.org.
>And when I do ifconfig eth0, I get No such device.
>Is there a way to do it ?
Well, Thanks to Elizabeth..I made this work under my current kernel version.
The problem as Elizabeth mentioned was that
Hi,
I have a similar porblem.
I have upgraded it to 2.4.18 from the source code www.kernel.org.
And when I do ifconfig eth0, I get No such device.
Is there a way to do it ?
Any help on this would be appreciated.
Thanks and Regards
Deepak
[EMAIL PROTECTED] wrote
"Kapil Khosla" <[EMAIL PROTECTED
"Kapil Khosla" <[EMAIL PROTECTED]> writes:
> Hi, I want to set up the route of my newly setup network. I have DEC
> 21143 chipsets and I have compiled/insmod the driver but am not sure
> if it works as I dont have the networking set up yet. I am working
> with Potato 2.2.19 kernel.
> Do I need ne
> I use my Debian 2.2r2 as a router, but it always shows the message
> "SIOCADDRT: File exists" at boot every time.
> I use the kernel 2.2.17 that come with the debian 2.2.
That's because your using the old /etc/init.d/network file, what you can
do is edit that file and comment:
#route a
On 12 Jun 2000, Jason Quigley wrote:
> BTW, somebody mentioned problems with disk performance under 2.2.15 and that
> I should stay with 2.2.14.
>
> I am interested in getting LVM working on my system and the only 2.2.x
> system that will be patched will be 2.2.15+.
>
> Does anybody know if this
BTW, somebody mentioned problems with disk performance under 2.2.15 and that
I should stay with 2.2.14.
I am interested in getting LVM working on my system and the only 2.2.x
system that will be patched will be 2.2.15+.
Does anybody know if this person was using the wrong orifice to communicate?
Mark wrote:
> Hmm, ok, but the networks file is stock, set up by the debian install. I
> have upgraded the kernel from 2.0.38 to 2.2.15 - would this be the "route"
> of the problem?
:) Yup.
If I am not entirely mistaken, the 2.2.x kernel doesn't need the route
entry as it sets routes automatical
On 12/06/00 at 19:37 Corey Popelier spake the following magic words:
>Umm, two aspects I can think of:
>
>(1) in kernel 2.2.x -net isn't required at all iirc, so route add
>127.0.0.1 lo should be enough.
>(2) I would have thought the route should be 127.0.0.0 not 127.0.0.1
>... my /etc/init.d/netwo
Umm, two aspects I can think of:
(1) in kernel 2.2.x -net isn't required at all iirc, so route add
127.0.0.1 lo should be enough.
(2) I would have thought the route should be 127.0.0.0 not 127.0.0.1
... my /etc/init.d/network says 127.0.0.0 but don't take that for gospel.
Cheers,
Corey Popelier
using rotue add -net in 2.2.x is redundant as 2.2. already adds the route
automatically, its nothing to worry about it doesnt hurt anything.
nate
On Wed, 29 Dec 1999, Daniel [iso-8859-1] P?rez P?rez wrote:
danito >I use Debian 2.1 and I have changed my Kernel 2.0.36 to 2.2.4 and
danito >when
route add -host 127.0.0.1 lo
is added automatically by kernel. You don't need to do it again. If you want to
overwrite it with some other options - use it with full syntax.
goto /usr/src/linux/Documentation
On Wed, Dec 29, 1999 at 03:34:29PM -0500, Sebastian Canagaratna wrote:
> Try from the co
Try from the command line:
ifconfig lo 127.0.0.1
route add -host 127.0.0.1 lo
If this works you can put this in the following file:
/etc/init.d/network
To be on the safe side copy your original network file.
This is what I have on my machine and I don't have any problems.
Make sure the rest of
I had the same problem upgrading from kernel 2.0.x to 2.2.13:
SIOCADDRT: Invalid argument
I solved the SIOCADDRT error message updating the
/etc/init.d/network script. Just to be safe I installed also the
netbase_3.12-2 package for Slink
(http://www.debian.org/~rcw/2.2/warnings.html).
BTW, just t
No script changes it. It's part of the netbase package, if I'm
not mistaken. It is considered a configuration file, so upgrading
netbase shouldn't overwrite your changes.
Bryan
On 19-Oct-99 Hans Gubitz wrote:
> On Mon, Oct 18, 1999 at 09:31:54PM -0400, Bryan Scaringe wrote:
>> 2) As for SIOCAD
Your bset bet would be to leave the file, but delete all of the modules
from it. Some scripts may expect it to be there.
Bryan
On 19-Oct-99 Richard Weil wrote:
> Can /etc/modules be deleted safely? After upgrading from 2.0.36 -> 2.2.12 I
> noticed
> that /etc/modules was trying to load modules
Can /etc/modules be deleted safely? After upgrading from 2.0.36 -> 2.2.12 I
noticed
that /etc/modules was trying to load modules I didn't need/want. I ended up
commenting everything out. Is there any reason not to delete the file?
Richard Weil
Hans Gubitz wrote:
> On Mon, Oct 18, 1999 at 09:
On Mon, Oct 18, 1999 at 09:31:54PM -0400, Bryan Scaringe wrote:
> 2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
> route add -net 127.0.0.0
>to:
> route add -net 127.0.0.0 netmask 255.255.255.0 lo
>
I had the same problem (2.0.36->2.2.12) in my /etc/init.d/ne
1) dmesg only covers kernel messages. There are other messages
that get printed to the screen when the system starts up that
don't get shown by dmesg. To see these, I just hold down
and use and to scroll through
the messages. Probably not the most scientific approach, but
it w
1) dmesg only covers kernel messages. There are other messages
that get printed to the screen when the system starts up that
don't get shown by dmesg. To see these, I just hold down
and use and to scroll through
the messages. Probably not the most scientific approach, but
it w
> "Kai" == Kai Rascher <[EMAIL PROTECTED]> writes:
Kai> Hi experts, I installed kernel 2.2.11 (Debian 2.1) and
Kai> everything seem all right. But there are two messages
Kai> ´SIOCADDRT invalid argument´ during boot process I don´t
Kai> understand. I´m pretty sure that this me
Remove the route -add stuff from /etc/init.d/network and you'll be fine.
Its OK to leave the route -add default gw line if you have a gateway on
your network.
The error message isn't harmful, so if you're squeemish about editing init
files, don't worry.
On Mon, 19 Apr 1999, Armin Wegner wrote:
Well, let's see. You're looking for somthing that you know was said on this
mailing list recently. Dosn't that suguest to you that you want to look at
the mailing list archives? So you go to "www.debian.org" in your favorite
web browser, and find "Mailing List Archives" on the map to the left.
On Sat, 17 Apr 1999, Chad A. Adlawan wrote:
> hi Vaidhy,
> i also got the same error as u guys did, that is, i got it after i
> upgraded from 2.0.36 to 2.2.4. do u think that same fix'll still work for
> me ? i dont feel too comfortable removing some lines from my init.d/network
> because thou
Vaidhyanathan G Mayilrangam wrote:
> Just comment the route -add default gw statement alone.. My guess is moving
> to IPCHAINS made the statement unnecessary.. If that solves the problem,
> then it is great :)
>
2.2.x kernels need this done. There's a bunch of stuff in the archives for
debian-us
Just comment the route -add default gw statement alone.. My guess is moving
to IPCHAINS made the statement unnecessary.. If that solves the problem,
then it is great :)
Regards,
Vaidhy
On Sat, Apr 17, 1999 at 11:20:01AM +0800, Chad A. Adlawan wrote:
> hi Vaidhy,
> i also got the same error as u
hi Vaidhy,
i also got the same error as u guys did, that is, i got it after i
upgraded from 2.0.36 to 2.2.4. do u think that same fix'll still work for
me ? i dont feel too comfortable removing some lines from my init.d/network
because though i get those error messages, my box is still working
Got the same error... The cure is to remove the route -add parameters in
/etc/init.d/network for eth0, lo, and any other adapters... It is not
necessary to remove the route -add default gw parameter if you have a
gateway.
On Fri, 16 Apr 1999, Vaidhyanathan G Mayilrangam wrote:
> Hi Chris,
>
>
Hi Chris,
I generally get the message during network initialization when something is
missing or wrong.. Can you post the relevant boot message. (Use dmesg).
Regards,
Vaidhy
On Fri, Apr 16, 1999 at 09:15:37PM -0400, Chris Brown wrote:
> Greetings,
> I'm cleaning up the boot messages of a sy
Are you running a 2.1.x kernel? If so comment out the route commands in
/etc/init.d/network and read linux/Documentation/Changes in the kernel
source.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lindsay Allen <[EMAIL PROTECTED]> Perth, Western Australia
voice +61 8
38 matches
Mail list logo
