Re: SIOCADDRT : No such device
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 kernel, do: make depend make bzImage (but this depends on the architecture; for i386 I like this) make modules make modules_install The modules_install places the modules in the /lib/modules directory. "Deepak Kotian" <[EMAIL PROTECTED]> writes: > The network card seems to be rtl8139. Where could one find .deb > packages or insatallables for these packages ? It's a part of the kernel but can be compiled: 1) Into the kernel (I don't recommend this one because it's less flexable) or 2) As a module. When the compilition is done (and the modules compilation if using step (2) above), be sure ad do "make modules_install". That "installs" the modules by placing them in a standard location (/lib/modules). > Please also Note: why would 2.4.18(kernel built from kernel.org > site) kernel boot is NOT on network and 2.2.19 kernel is on network > and it is the same machine. Most likely because the module utilities (modutils) aren't able to find the modules. Elizabeth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT : No such device
Thanks , I will check that. But, still one problem still remains, why would 2.4.18(kernel built from kernel.org site) kernel boot is not on network and 2.2.19 kernel is on network and it is the same machine. The network card seems to be rtl8139. Where could one find .deb packages or insatallables for these packages ? Please let me know. About Kapil question, >>Can you also mail the output of cat /proc/interrupts. >>I have a weird feeling that your eth0 will not be listed there, What if it is not there ? What do we conclude. Please let me know. I do not have the access tomy office machine. But will check it and send it tomorrow. Please also Note: why would 2.4.18(kernel built from kernel.org site) kernel boot is NOT on network and 2.2.19 kernel is on network and it is the same machine. Thanks and Regards Deepak Thanks and Regards Deepak - Original Message - 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. > > 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 > > Otherwise, peer into the machine, find the NIC or firmware module > making up your networking device and note the name of the manufacturer > and any numbers on it. > > Elizabeth > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: SIOCADDRT : No such device
-- 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 Kapil >>>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 can see the kernel. > >>>Did you configure your /etc/network/interfaces file ? > >When I boot it with 2.2.19, it is on network, when I boot it >2.4.18, it is not on network. Probably some drivers is missing. > >Also, when I do make config, I select all default. >How do I know, what card, I have. > >Procedure for upgrade , that was followed!! But cannot telnet to it, probably >network card not recognized. >1) unzip linunx-2.4.18.tar.gz >2) cd linux >3) make mrproper >4) make config >Selected default >5) make dep clean bzImage >6) make modules modules_install >7) cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.18 >8) cp System.map /boot/System.map-2.4.18 >9) setup /etc/lilo.conf for new entry in bootlist , >10) /sbin/lilo >11) reboot > >How do I know, what network card I have and why doesn't 2.4.18 >kernel source pick it up automatically or is it the driver is >not there and what driver should I installed > >Thanks and Regards >Deepak > > >[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 > >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... > > >++ >| Why Reboot ?! | >| Use Debian GNU/Linux! | >| http:\\www.debianworld.org | >++ >* > >Ce message et toutes les pieces jointes (ci-apres le "message") sont >confidentiels et etablis a l'intention exclusive de ses destinataires. >Toute utilisation ou diffusion non autorisee est interdite. >Tout message electronique est susceptible d'alteration. >La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de >ce message s'il a ete altere, deforme ou falsifie. > > > >This message and any attachments (the "message") are confidential and >intended solely for the addressees. >Any unauthorised use or dissemination is prohibited. >E-mails are susceptible to alteration. >Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be >liable for the message if altered, changed or falsified. > >* > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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. 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 Otherwise, peer into the machine, find the NIC or firmware module making up your networking device and note the name of the manufacturer and any numbers on it. Elizabeth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: SIOCADDRT : No such device
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 can see the kernel. >>Did you configure your /etc/network/interfaces file ? When I boot it with 2.2.19, it is on network, when I boot it 2.4.18, it is not on network. Probably some drivers is missing. Also, when I do make config, I select all default. How do I know, what card, I have. Procedure for upgrade , that was followed!! But cannot telnet to it, probably network card not recognized. 1) unzip linunx-2.4.18.tar.gz 2) cd linux 3) make mrproper 4) make config Selected default 5) make dep clean bzImage 6) make modules modules_install 7) cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.18 8) cp System.map /boot/System.map-2.4.18 9) setup /etc/lilo.conf for new entry in bootlist , 10) /sbin/lilo 11) reboot How do I know, what network card I have and why doesn't 2.4.18 kernel source pick it up automatically or is it the driver is not there and what driver should I installed Thanks and Regards Deepak [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 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... ++ | Why Reboot ?! | | Use Debian GNU/Linux! | | http:\\www.debianworld.org | ++ * Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT : No such device
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 with no difficulty. I prefer to compiler the driver into the kernel and I am pretty sure that in your case also you just have to set up the interface right and everything will be fine. As David said in his mail, do the following if you have a static IP Put the info in /etc/network/interfaces. Mine looks like: auto eth0 iface eth0 inet static address 192.168.8.30 netmask 255.255.255.0 network 192.168.8.0 broadcast 192.168.8.255 gateway 192.168.8.254 If howevery you want to load the driver as a module , first see the output of the lsmod command. Do you see any 8139too ? If "not" then what you might have to do is download the driver and "insmod". This will load the driver into the running kernel as a module. Man pages to see:- insmod lsmod ifconfig Thanks Kapil > > > > > > [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 [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 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]> 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 networking setup before I can setup 'route' ? > > > > You need to have the NICs bound to an ethernet device for route to > > work. > > > > Generally, ifconfig should show you whether or not a NIC is noticed by > > the kernel. You said that you insmod'ed them - did you receive any > > report that this may have not worked while doing it? > > > > sockios.h: > > /* Routing table calls. */ > > #define SIOCADDRT 0x890B /* add routing table entry */ > > #define SIOCDELRT 0x890C /* delete routing table entry */ > > #define SIOCRTMSG 0x890D /* call to routing system */ > > > > The SIOCADDRT is what operation is reporting the error. > > > > When you do an ifconfig eth0, do you see anything? > > > > Regards, Eliizabeth > > > > > > > The problem which I am having while setting up route is : route add > > > -net 192.168.2.0 netmask 255.255.255.0 eth0 SIOCADDRT : No such > > > device > > > > > > route add default gw 192.168.2.1 eth0 Network unreachable > > > > > > 192.168.2.1 is my gateway to the world and all the computers on the > > > LAN have to be assigned IP in the range of 192.168.2.* > > > > > > What does this error mean ( SIOCADDRT)? Thanks Kapil > > > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: SIOCADDRT : No such device
>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... ++ | Why Reboot ?! | | Use Debian GNU/Linux! | | http:\\www.debianworld.org | ++ * Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT : No such device
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 [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 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]> 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 networking setup before I can setup 'route' ? > > You need to have the NICs bound to an ethernet device for route to > work. > > Generally, ifconfig should show you whether or not a NIC is noticed by > the kernel. You said that you insmod'ed them - did you receive any > report that this may have not worked while doing it? > > sockios.h: > /* Routing table calls. */ > #define SIOCADDRT 0x890B /* add routing table entry */ > #define SIOCDELRT 0x890C /* delete routing table entry */ > #define SIOCRTMSG 0x890D /* call to routing system */ > > The SIOCADDRT is what operation is reporting the error. > > When you do an ifconfig eth0, do you see anything? > > Regards, Eliizabeth > > > > The problem which I am having while setting up route is : route add > > -net 192.168.2.0 netmask 255.255.255.0 eth0 SIOCADDRT : No such > > device > > > > route add default gw 192.168.2.1 eth0 Network unreachable > > > > 192.168.2.1 is my gateway to the world and all the computers on the > > LAN have to be assigned IP in the range of 192.168.2.* > > > > What does this error mean ( SIOCADDRT)? Thanks Kapil > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT : No such device
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 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]> 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 networking setup before I can setup 'route' ? > > You need to have the NICs bound to an ethernet device for route to > work. > > Generally, ifconfig should show you whether or not a NIC is noticed by > the kernel. You said that you insmod'ed them - did you receive any > report that this may have not worked while doing it? > > sockios.h: > /* Routing table calls. */ > #define SIOCADDRT 0x890B /* add routing table entry */ > #define SIOCDELRT 0x890C /* delete routing table entry */ > #define SIOCRTMSG 0x890D /* call to routing system */ > > The SIOCADDRT is what operation is reporting the error. > > When you do an ifconfig eth0, do you see anything? > > Regards, Eliizabeth > > > > The problem which I am having while setting up route is : route add > > -net 192.168.2.0 netmask 255.255.255.0 eth0 SIOCADDRT : No such > > device > > > > route add default gw 192.168.2.1 eth0 Network unreachable > > > > 192.168.2.1 is my gateway to the world and all the computers on the > > LAN have to be assigned IP in the range of 192.168.2.* > > > > What does this error mean ( SIOCADDRT)? Thanks Kapil > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT : No such device
>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 my network card was not bound to eth0. Thus ifconfig was not showing any eth0. I thus did /sbin/ifconfig eth0 192.168.2.36 netmask 255.255.255.0 Then I gave my route commands for Gateway etc and everything is fine now. Thanks Kapil > >Thanks and Regards >Deepak > > >[EMAIL PROTECTED] wrote >"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 networking setup before I can setup 'route' ? > >You need to have the NICs bound to an ethernet device for route to >work. > >Generally, ifconfig should show you whether or not a NIC is noticed by >the kernel. You said that you insmod'ed them - did you receive any >report that this may have not worked while doing it? > >sockios.h: >/* Routing table calls. */ >#define SIOCADDRT 0x890B /* add routing table entry */ >#define SIOCDELRT 0x890C /* delete routing table entry */ >#define SIOCRTMSG 0x890D /* call to routing system */ > >The SIOCADDRT is what operation is reporting the error. > >When you do an ifconfig eth0, do you see anything? > >Regards, Eliizabeth > > >> The problem which I am having while setting up route is : route add >> -net 192.168.2.0 netmask 255.255.255.0 eth0 SIOCADDRT : No such >> device >> >> route add default gw 192.168.2.1 eth0 Network unreachable >> >> 192.168.2.1 is my gateway to the world and all the computers on the >> LAN have to be assigned IP in the range of 192.168.2.* >> >> What does this error mean ( SIOCADDRT)? Thanks Kapil > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT : No such device
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]> 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 networking setup before I can setup 'route' ? You need to have the NICs bound to an ethernet device for route to work. Generally, ifconfig should show you whether or not a NIC is noticed by the kernel. You said that you insmod'ed them - did you receive any report that this may have not worked while doing it? sockios.h: /* Routing table calls. */ #define SIOCADDRT 0x890B /* add routing table entry */ #define SIOCDELRT 0x890C /* delete routing table entry */ #define SIOCRTMSG 0x890D /* call to routing system */ The SIOCADDRT is what operation is reporting the error. When you do an ifconfig eth0, do you see anything? Regards, Eliizabeth > The problem which I am having while setting up route is : route add > -net 192.168.2.0 netmask 255.255.255.0 eth0 SIOCADDRT : No such > device > > route add default gw 192.168.2.1 eth0 Network unreachable > > 192.168.2.1 is my gateway to the world and all the computers on the > LAN have to be assigned IP in the range of 192.168.2.* > > What does this error mean ( SIOCADDRT)? Thanks Kapil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT : No such device
"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 networking setup before I can setup 'route' ? You need to have the NICs bound to an ethernet device for route to work. Generally, ifconfig should show you whether or not a NIC is noticed by the kernel. You said that you insmod'ed them - did you receive any report that this may have not worked while doing it? sockios.h: /* Routing table calls. */ #define SIOCADDRT 0x890B /* add routing table entry */ #define SIOCDELRT 0x890C /* delete routing table entry */ #define SIOCRTMSG 0x890D /* call to routing system */ The SIOCADDRT is what operation is reporting the error. When you do an ifconfig eth0, do you see anything? Regards, Eliizabeth > The problem which I am having while setting up route is : route add > -net 192.168.2.0 netmask 255.255.255.0 eth0 SIOCADDRT : No such > device > > route add default gw 192.168.2.1 eth0 Network unreachable > > 192.168.2.1 is my gateway to the world and all the computers on the > LAN have to be assigned IP in the range of 192.168.2.* > > What does this error mean ( SIOCADDRT)? Thanks Kapil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SIOCADDRT: File exists
> 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 add -net 127.0.0.0 #route add -net 192.168.0.0 or whatever your network numbers are, the idea is, 2.2 kernels do this them selfs. In Debian 2.2 there is a new file: /etc/network/interfaces which is the new way, just look in the docs of I think netbase (/usr/share/doc/netbase). Hope this helps. - New things are always on the horizon.
Re: SIOCADDRT: Invalid Parameters
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 person was using the wrong orifice to communicate? > > Many thanks, > Jason. I'm using 2.2.15 with no problems. I seem to remember that there was some report recently that 2.2.14 had trashed some people's file systems, but don't take this as gospel. I installed 2.2.14 on my son's computer and the file system *was* trashed when he tried to boot after several weeks on The Other System, but I don't know if the kernel was responsible. Anthony -- Anthony Campbell - running Linux Debian 2.1 (Windows-free zone) Book Reviews: http://www.pentelikon.freeserve.co.uk/bookreviews/ Skeptical articles: http://www.freethinker.uklinux.net/ "To be forced by desire into any unwarrantable belief is a calamity." I.A. Richards
Re: SIOCADDRT: Invalid Parameters
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? Many thanks, Jason. > > 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? > --
Re: SIOCADDRT: Invalid Parameters
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 automatically. It should be save to leave that line out. MfG Viktor -- Viktor Rosenfeld E-Mail: mailto:[EMAIL PROTECTED] or: mailto:[EMAIL PROTECTED] HertzSCHLAG:http://www.informatik.hu-berlin.de/~rosenfel/hs/
Re: SIOCADDRT: Invalid Parameters
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/network says 127.0.0.0 but don't take that for gospel. > >Cheers, > Corey Popelier > http://members.dingoblue.net.au/~pancreas > Work Email: [EMAIL PROTECTED] > >On Mon, 12 Jun 2000, Mark wrote: > >> On boot up, when my system executes the network init script, it gives the >> error: >> >> SIOCADDRT: Invalid Parameters >> >> the network script contains: >> >> ifconfig lo 127.0.0.1 >> route add -net 127.0.0.1 lo >> >> It's crashing on the "route add" bit. Shouldn't it be "route add -host" >> instead of "-net"? 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? -- Mark Herrick - Liverpool - England mark at blacksky dot co dot uk Pick two: Good, Fast, Cheap __ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre. For further information visit- http://www.star.net.uk/stats.asp
Re: SIOCADDRT: Invalid Parameters
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 http://members.dingoblue.net.au/~pancreas Work Email: [EMAIL PROTECTED] On Mon, 12 Jun 2000, Mark wrote: > On boot up, when my system executes the network init script, it gives the > error: > > SIOCADDRT: Invalid Parameters > > the network script contains: > > ifconfig lo 127.0.0.1 > route add -net 127.0.0.1 lo > > It's crashing on the "route add" bit. Shouldn't it be "route add -host" > instead of "-net"? > > -- > Mark Herrick - Liverpool - England > mark at blacksky dot co dot uk > Pick two: Good, Fast, Cheap > > > > __ > This message has been checked for all known viruses by Star Internet > delivered > through the MessageLabs Virus Control Centre. For further information visit- > http://www.star.net.uk/stats.asp > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
Re: SIOCADDRT: Invalid argument
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 I use the command route, for example route add -net 127.0.0.0 I get danito >the message SIOCADDRT: Invalid argument. I use an ethernet SMC ultra and danito >it works fine, even when I get that message. The configuration of the danito >Kernel is OK. I would like to know what is going on. danito > danito > danito > danito >-- danito >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null danito > [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 3:03pm up 132 days, 2:57, 3 users, load average: 1.70, 1.64, 1.53
Re: SIOCADDRT: Invalid argument
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 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 the file gives the proper information. > -- Marcin Kurc Indiana Institute of Technology System Administrator http://me.indtech.edu http://www.indtech.edu
Re: SIOCADDRT: Invalid argument
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 the file gives the proper information. Sebastian Canagaratna Department of Chemistry Ohio NOrthern University Ada, OH 45810. > I use Debian 2.1 and I have changed my Kernel 2.0.36 to 2.2.4 and > when I use the command route, for example route add -net 127.0.0.0 I get > the message SIOCADDRT: Invalid argument. I use an ethernet SMC ultra and > it works fine, even when I get that message. The configuration of the > Kernel is OK. I would like to know what is going on. > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > >
Re: SIOCADDRT
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 to be pedantic, the loopback interface is supposed to be on a class A network, so the netmask should be 255.0.0.0 and the command is: ifconfig lo 127.0.0.1 route add -net 127.0.0.0 netmask 255.0.0.0 lo I wonder if kernel 2.2.x does not require loopback setted properly anymore... Niccolo Firenze - Italy -- Contro la Tariffa Urbana a Tempo - http://www.notut.org
Re: SIOCADDRT
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 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/network:
>#! /bin/sh
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0 netmask 255.255.255.0 lo
>#route add -net 127.0.0.0
> IPADDR=192.168.1.2
> NETMASK=255.255.255.0
> NETWORK=192.168.1.0
> BROADCAST=192.168.1.255
> GATEWAY=
> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
>#route add -net ${NETWORK}
> route add -net ${NETWORK} netmask 255.255.255.0 lo
> [ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
>
> I changed both lines and it seems to be okay. Thanks.
>
> Which script creates the file network?
>
> I had problems too with /etc/modules. modconf did not modify the wrong
> entries.
> So I removed /etc/modules and did a modconf.
>
> Hans Gubitz
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
> /dev/null
Re: SIOCADDRT
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 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: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/network:
>> #! /bin/sh
>> ifconfig lo 127.0.0.1
>> route add -net 127.0.0.0 netmask 255.255.255.0 lo
>> #route add -net 127.0.0.0
>> IPADDR=192.168.1.2
>> NETMASK=255.255.255.0
>> NETWORK=192.168.1.0
>> BROADCAST=192.168.1.255
>> GATEWAY=
>> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
>> #route add -net ${NETWORK}
>> route add -net ${NETWORK} netmask 255.255.255.0 lo
>> [ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
>>
>> I changed both lines and it seems to be okay. Thanks.
>>
>> Which script creates the file network?
>>
>> I had problems too with /etc/modules. modconf did not modify the wrong
>> entries.
>> So I removed /etc/modules and did a modconf.
>>
>> Hans Gubitz
>>
>> --
>> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
>> /dev/null
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
> /dev/null
Re: SIOCADDRT
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: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/network:
> #! /bin/sh
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0 netmask 255.255.255.0 lo
> #route add -net 127.0.0.0
> IPADDR=192.168.1.2
> NETMASK=255.255.255.0
> NETWORK=192.168.1.0
> BROADCAST=192.168.1.255
> GATEWAY=
> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
> #route add -net ${NETWORK}
> route add -net ${NETWORK} netmask 255.255.255.0 lo
> [ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
>
> I changed both lines and it seems to be okay. Thanks.
>
> Which script creates the file network?
>
> I had problems too with /etc/modules. modconf did not modify the wrong
> entries.
> So I removed /etc/modules and did a modconf.
>
> Hans Gubitz
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: SIOCADDRT
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/network:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0 netmask 255.255.255.0 lo
#route add -net 127.0.0.0
IPADDR=192.168.1.2
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
GATEWAY=
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
#route add -net ${NETWORK}
route add -net ${NETWORK} netmask 255.255.255.0 lo
[ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
I changed both lines and it seems to be okay. Thanks.
Which script creates the file network?
I had problems too with /etc/modules. modconf did not modify the wrong entries.
So I removed /etc/modules and did a modconf.
Hans Gubitz
RE: SIOCADDRT
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 works for me. 2) As for SIOCADDRT: your /etc/init.d/network (or is it networks) file has a line to add a route for local network traffic through the loopback interface. As of Kernel 2.2.0, you need to have a netmask on that line. Debian Slink is designed for 2.0.x kernels which don't really need this parameter. I have mailed the maintainers about this problem. Until this gets changed, change the line: route add -net 127.0.0.0 to: route add -net 127.0.0.0 netmask 255.255.255.0 lo Hope this helps, Bryan On 11-Oct-99 Bryan Scaringe wrote: > > - Begin Included Message - > > From [EMAIL PROTECTED] Mon Feb 8 02:33 EST 1999 > Date: Mon, 08 Feb 1999 07:18:41 + > From: Paul Rogers <[EMAIL PROTECTED]> > X-Accept-Language: en,ja,ko > MIME-Version: 1.0 > To: Linux Newbie > Subject: Start up Messages > Content-Transfer-Encoding: 7bit > X-Loop: [EMAIL PROTECTED] > X-Orcpt: rfc822;linux-newbie-outgoing > > Dear All > > Can any one tell me how to review the output generated on startup? I > know about DMesg but would like to see the messages from the point that > dmesg stops. I'm sure I've read here that by pressing before > (after?) the initial logon I am able to view the various messages, but I > can't remember what is. > > Secondly can anyone tell me / point me in the direction of any info as > to what the following startup message means? > > SIOCADDRT:invalid argument > > > Many thanks in advance > > > Paul > > > > - End Included Message - - End Included Message - --End of forwarded message-
RE: SIOCADDRT
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 works for me. 2) As for SIOCADDRT: your /etc/init.d/network (or is it networks) file has a line to add a route for local network traffic through the loopback interface. As of Kernel 2.2.0, you need to have a netmask on that line. Debian Slink is designed for 2.0.x kernels which don't really need this parameter. I have mailed the maintainers about this problem. Until this gets changed, change the line: route add -net 127.0.0.0 to: route add -net 127.0.0.0 netmask 255.255.255.0 lo Hope this helps, Bryan On 11-Oct-99 Bryan Scaringe wrote: > > - Begin Included Message - > > From [EMAIL PROTECTED] Mon Feb 8 02:33 EST 1999 > Date: Mon, 08 Feb 1999 07:18:41 + > From: Paul Rogers <[EMAIL PROTECTED]> > X-Accept-Language: en,ja,ko > MIME-Version: 1.0 > To: Linux Newbie > Subject: Start up Messages > Content-Transfer-Encoding: 7bit > X-Loop: [EMAIL PROTECTED] > X-Orcpt: rfc822;linux-newbie-outgoing > > Dear All > > Can any one tell me how to review the output generated on startup? I > know about DMesg but would like to see the messages from the point that > dmesg stops. I'm sure I've read here that by pressing before > (after?) the initial logon I am able to view the various messages, but I > can't remember what is. > > Secondly can anyone tell me / point me in the direction of any info as > to what the following startup message means? > > SIOCADDRT:invalid argument > > > Many thanks in advance > > > Paul > > > > - End Included Message - - End Included Message - --End of forwarded message-
Re: SIOCADDRT invalid argument
> "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 messages have something
Kai> to do with the serial ports. But I can´t get further.
The default /etc/init.d/network script contains lines to add routes to
your internal networks. ("route add -net ...") The 2.2.x kernels do
this automatically, and in fact complains about those lines.
Simply remove these lines, or if you may be going back to 2.0.x
kernels, make them conditional.
-tor
Re: SIOCADDRT: Invalid argument
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: > Hi, > > Booting Slink with Linux 2.2.5 kernel I get the message > SIOCADDRT: Invalid argument > after mounting the file systems. What does this mean? Looks like an error, > doesn't it? > > Armin > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > >
Re: SIOCADDRT error
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. From there, you find the April 1999 debian-user, and search for SIOCADDRT (using alt-f in netscape or / in lynx). You'll find it in the third page of debian-user for this month. You can find two specific fixes on that page, mine (http://www.debian.org/Lists-Archives/debian-user-9904/msg01303.html), and Wayne Topa's (http://www.debian.org/Lists-Archives/debian-user-9904/msg01522.html). -=- James Mastros -- "My friend Data: You see the world with the wonder of a child, and that makes you more human then any of us." -=- Lt. Tasha Yar, upon the occasion of her death.
Re: SIOCADDRT error on boot
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 though i get those error messages, my box is still working > perfectly. and i dont get any error messages on my syslog also. > could this be something w/ 2.2.4's new design ? Hi Chad! You´re right. 2.2.x sets the route in initializing the device via ifconfig Heute ist nicht alle Tage, ich komme wieder, keine Frage!!! Joerg
Re: SIOCADDRT error on boot
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-user about this. > > 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 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 > > perfectly. and i dont get any error messages on my syslog also. > > could this be something w/ 2.2.4's new design ? > > TIA, > > Chad > > > > On Fri, Apr 16, 1999 at 09:32:18PM -0400, Alec Smith wrote: > > > 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, > > > > > > > > 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 system we're moving to > > > > > another location, and I ran into a funny message. When the system > > > > > boots everything looks OK until It mounts the local filesystems. I > > > > > get this weird error, > > > > > "SIOCADDRT: Invalid argument" > > > > > twice, and then it moves on. I've looked at the > > > > > /etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems > > > > > and I still don't have a clue. What do I need to change to kill this > > > > > error? > > > > > Thanks, > > > > > Chris > > > > > > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- dyer
Re: SIOCADDRT error on boot
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 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 > perfectly. and i dont get any error messages on my syslog also. > could this be something w/ 2.2.4's new design ? > TIA, > Chad > > On Fri, Apr 16, 1999 at 09:32:18PM -0400, Alec Smith wrote: > > 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, > > > > > > 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 system we're moving to > > > > another location, and I ran into a funny message. When the system > > > > boots everything looks OK until It mounts the local filesystems. I > > > > get this weird error, > > > > "SIOCADDRT: Invalid argument" > > > > twice, and then it moves on. I've looked at the > > > > /etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems > > > > and I still don't have a clue. What do I need to change to kill this > > > > error? > > > > Thanks, > > > > Chris > > > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: SIOCADDRT error on boot
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 perfectly. and i dont get any error messages on my syslog also. could this be something w/ 2.2.4's new design ? TIA, Chad On Fri, Apr 16, 1999 at 09:32:18PM -0400, Alec Smith wrote: > 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, > > > > 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 system we're moving to > > > another location, and I ran into a funny message. When the system > > > boots everything looks OK until It mounts the local filesystems. I > > > get this weird error, > > > "SIOCADDRT: Invalid argument" > > > twice, and then it moves on. I've looked at the > > > /etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems > > > and I still don't have a clue. What do I need to change to kill this > > > error? > > > Thanks, > > > Chris > > >
Re: SIOCADDRT error on boot
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, > > 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 system we're moving to > > another location, and I ran into a funny message. When the system > > boots everything looks OK until It mounts the local filesystems. I > > get this weird error, > > "SIOCADDRT: Invalid argument" > > twice, and then it moves on. I've looked at the > > /etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems > > and I still don't have a clue. What do I need to change to kill this > > error? > > Thanks, > > Chris > > > > :/etc/fstab: > > /dev/hda4 / ext2defaults,errors=remount-ro 0 1 > > /dev/hda1 noneswapsw,pri=-2 0 0 > > /dev/md0/home ext2defaults,errors=remount-ro 0 1 > > /dev/hdd2 /home/usrsh ext2defaults,errors=remount- > > ro,usrquota,grpquota0 1 > > /dev/hdd1 noneswapsw,pri=-1 0 0 > > proc/proc procdefaults > > > > :/etc/init.d/mountall.sh: > > # > > # mountall.sh Mount all filsystems. > > # > > # Version: @(#)mountall.sh 1.0019-Jun-1998 [EMAIL PROTECTED] > > # Version: @(#)mountall.sh 1.1004-Mar-1999 [EMAIL PROTECTED] > > # > > ./etc/default/rcS > > > > # > > # Mount local filesystems in /etc/fstab > > # > > [ "$VERBOSE" != no ] && echo "Mounting local file systems..." > > #mount -avt nonfs,noproc > > mount -at nonfs,noproc > > # > > # Execute swapon command again, in case we want to swap to > > # a file on a now mounted filesystem > > # > > # TEMPORARILY DISABLED -you can swapon a file twice, kernel bug. > > #swapon -a 2>/dev/null > > > > :/proc/filesystems: > > ext2 > > minix > > msdos > > nodev proc > > nodev nfs > > iso9660 > > nodev autofs > > nodev devpts > > > > > > * > > Chris Brown [EMAIL PROTECTED] !!! HELP FIGHT SPAM !!! > > > > Join; www.cauce.org See; spam.abuse.net, spamsucks.com, www.cm.org > > > > > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > >
Re: SIOCADDRT error on boot
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 system we're moving to > another location, and I ran into a funny message. When the system > boots everything looks OK until It mounts the local filesystems. I > get this weird error, > "SIOCADDRT: Invalid argument" > twice, and then it moves on. I've looked at the > /etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems > and I still don't have a clue. What do I need to change to kill this > error? > Thanks, > Chris > > :/etc/fstab: > /dev/hda4 / ext2defaults,errors=remount-ro 0 1 > /dev/hda1 noneswapsw,pri=-2 0 0 > /dev/md0/home ext2defaults,errors=remount-ro 0 1 > /dev/hdd2 /home/usrsh ext2defaults,errors=remount- > ro,usrquota,grpquota0 1 > /dev/hdd1 noneswapsw,pri=-1 0 0 > proc/proc procdefaults > > :/etc/init.d/mountall.sh: > # > # mountall.sh Mount all filsystems. > # > # Version: @(#)mountall.sh 1.0019-Jun-1998 [EMAIL PROTECTED] > # Version: @(#)mountall.sh 1.1004-Mar-1999 [EMAIL PROTECTED] > # > ./etc/default/rcS > > # > # Mount local filesystems in /etc/fstab > # > [ "$VERBOSE" != no ] && echo "Mounting local file systems..." > #mount -avt nonfs,noproc > mount -at nonfs,noproc > # > # Execute swapon command again, in case we want to swap to > # a file on a now mounted filesystem > # > # TEMPORARILY DISABLED -you can swapon a file twice, kernel bug. > #swapon -a 2>/dev/null > > :/proc/filesystems: > ext2 > minix > msdos > nodev proc > nodev nfs > iso9660 > nodev autofs > nodev devpts > > > * > Chris Brown [EMAIL PROTECTED] !!! HELP FIGHT SPAM !!! > > Join; www.cauce.org See; spam.abuse.net, spamsucks.com, www.cm.org > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: SIOCADDRT error message
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 316 2486modem +61 8 364-9832 32S, 116E vk6lj =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Thu, 12 Nov 1998 [EMAIL PROTECTED] wrote: > I also get this error message on boot. The route command seems to be > broken, as the route manpage syntax will not add the loopback route > and generates this message. Don't know enough about it to tell exactly > what is broken (package-wise). > -- > Eddie Seymour, WB4MLE > E-Mail [EMAIL PROTECTED] > PGP KEYS D/H 0xB65DC61A RSA 0x935801A9 > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
