Board index Linux Setup

Problem with 2.2.2: SIOCARDDRT: invalid argument

Problem with 2.2.2: SIOCARDDRT: invalid argument

Post by Tuan Pham-Din » Tue, 02 Mar 1999 04:00:00



        Hi,
        After uppgrading to kernel 2.2.2, I get this message at boot

SIOCARDDRT: invalid argument
SIOCARDDRT: invalid argument

        I have traced it to the command "route add -net ..." in my
/etc/init.d/network file. I have upgraded the netbase package (which
contaain /sbin/route) of my debian system 2.1 (not yet officially
released) to the version 3.12-2 of the potato branch (still unstable).
Yet, the same error persits.
        Has anyone got this kind of error. Are there a version of
route which fixed it ? If so, where ?

        By the way, /sbin/route --version yields
net-tools 1.50
route 1.96 (1999-01-01)
+NEW_ADDRT +RTF_IRTT +RTF_REJECT -I18N
AF: (inet) +UNIX +INET -INET6 +IPX +AX25 +NETROM +ATALK -ECONET -ROSE
HW:  +ETHER +ARC +SLIP +PPP +TUNNEL +TR +AX25 +NETROM +FR -ROSE +ASH +SIT +FDDI -HIPPI +HDLC/LAPB

        Thank for any help.

 
 
 
Top

Problem with 2.2.2: SIOCARDDRT: invalid argument

Post by Darren Gre » Sat, 06 Mar 1999 04:00:00


Go to www.linuxhq.com/change22.html

In the network section it tells about what needs to be
done....although does not tell what file.

Basically...go into your /etc/init.d directory and edit the network
file.  In there you will see some lines that are adding routes.  In
hte newer kernel....route are added by default.  So....either remove
those lines....or you add the complete settings.  That web page will
explain more,

Darren


-->I've got the exactly the same problem with my debian box... It's debian
-->2.0 with 2.2.2 kernel. The network card is 3Com EtherLinkXL. If anyone
-->figured out how to fix this problem, I'm also interested to know how.
-->Thanks :-)
-->
-->
-->----------------------------------------------------------
-->Makoto Kamei

-->WWW page at http://biology.anu.edu.au/~kamei

 
 
 
Top

Problem with 2.2.2: SIOCARDDRT: invalid argument

Post by Makoto Kam » Sun, 07 Mar 1999 04:00:00


I've got the exactly the same problem with my debian box... It's debian
2.0 with 2.2.2 kernel. The network card is 3Com EtherLinkXL. If anyone
figured out how to fix this problem, I'm also interested to know how.
Thanks :-)

----------------------------------------------------------
Makoto Kamei

WWW page at http://biology.anu.edu.au/~kamei

 
 
 
Top

1. `Invalid argument' problems with mount_ext2fs


I've never gotten that message when _mounting_ an ext2fs filesystem.  But
during boot-up, I get this:

wd1s4: raw partition size != slice size
wd1s4: start 846720, end 2128895, size 1282176
wd1s4c: start 846720, end 947519, size 100800



No error messages here during mount.

Now, I cd /mnt/usr, and do an ls:

-snip-

ls: ix86-linuxaout: Invalid argument
ls: libexec: Invalid argument
ls: man: Invalid argument
ls: openwin: Invalid argument
ls: sbin: Invalid argument
ls: share: Invalid argument
ls: src: Invalid argument





This seems related to the message I was getting on bootup:

wd1s4: raw partition size != slice size
wd1s4: start 846720, end 2128895, size 1282176
wd1s4c: start 846720, end 947519, size 100800

Maybe when I did fdisk in Linux on these partitions, it did something
off-the-wall that FreeBSD's mount_ext2fs didn't understand.  I don't think
it could be the inode density I've used when formatting my Linux /usr
partition (in this case /mnt/usr).

It probably also depends on the version of FreeBSD you are using.  What
doess uname -sr give you?

FreeBSD 4.0-CURRENT
^^^^^^^^^^^^^^^^
This is what I'm running right now.

I think that ext2fs hasn't been maintained as well as it used to.  Or, in
may case, maybe I did something slightly off the wall in Linux that may be
acceptable to the Linux kernel, but FreeBSD doesn't recognize what I've
done.

Donn

2. FORTRAN random number generator in fort77 (RedHat4.1)

3. Problem: ioctl FIBMAP: Invalid argument

4. Solaris PPP Problem

5. HELP: "DIP tty: set_disc(1): Invalid Argument" problems with SLIP!

6. A ray of light ... (was Re: NCR53c810 SCSI problem in Slackware 2.2)

7. DIP problem: mode SLIP gives SETD: Invalid argument

8. Gateway2000 Matrox MGA Video Card

9. Problem with TCPDUMP ( it says : "tcpdump: socket: Invalid argument" ??!!

10. Problem: DIP: tty: set_disc(1): Invalid argument

11. new filesystem problems: "fdisk: can't write fdisk partition table: Invalid argument"

12. Problems installing on PB G3 - "Mount Failed - Invalid Argument"

13. Problem with TCPDUMP ( it says : "tcpdump: socket: Invalid argument" ??!!


All times are UTC
Board index