If you get the error message 'SIOCADDRT: Invalid argument' at boot time:
That comes from the command 'route add -net 127.0.0.0' or something
similar normally placed in /etc/init.d/network.
You can just remove this line as routing to interfaces are done
automatically by the 2.2.x kernels. For more d
comment out the lines 'route add -net ' in /etc/init.d/network.
The 2.2.x kernel do the routing internally.
Sebastian Canagaratna [EMAIL PROTECTED] wrote:
> I am running slink. I recently decided to change the kernel
> from 2.0.36 to 2.2.2 from the .deb in slink.
>
> Ever since I have bee
Subject: Kernel 2.2.1
Date: Fri, May 14, 1999 at 11:07:11PM +0200
In reply to:R.Feenstra
Quoting R.Feenstra([EMAIL PROTECTED]):
> Hello again :)
>
> Is kernel 2.2.1 still regarded as Slink ?
Hope not! Kernel 2.2.1 had problems and AFAIR wasn't included with
slink. The kernel
>
> Hello again :)
>
> Is kernel 2.2.1 still regarded as Slink ?
>
Huh? slinks version number is 2.1, slink actualy ships 2.0.36 of the kernel.
Two completely separate version number schemes.
Slink should work fine with 2.2.x kernels though.
Yes I did compile with elf support.
> -Original Message-
> From: Paul Miller [SMTP:[EMAIL PROTECTED]
> Sent: Tuesday, March 16, 1999 8:04 PM
> To: Person, Roderick
> Cc: debian-user
> Subject: Re: Kernel 2.2.1 question.
>
> "Person, R
"Person, Roderick" wrote:
>
> Paul,
>
> Thanks for the reply. I kept getting the message that the kernel could not
> find bin_fmt-464c so I tried a trick I saw in LJ and placed alias
> bin_fmt-464c in /etc/conf.modules. No luck. I've compile the kernel 4 times
> now and still can't get it right.
"Person, Roderick" wrote:
>
> I compiled this kernel and I noticed that the vmlinuz image was not set as
> executable. So I chmod so it would be and I got a kernel panic. I compile
> again and tried to boot, leaveing it as not executable and got module load
> errors that left me only able to reboo
Subject: Kernel 2.2.1 question.
Date: Mon, Mar 15, 1999 at 12:56:23PM -0500
In reply to:Person, Roderick
Quoting Person, Roderick([EMAIL PROTECTED]):
> I compiled this kernel and I noticed that the vmlinuz image was not set as
> executable. So I chmod so it would be and I got a k
You need to add "netmask" to your route command. The 2.0.x kernel
series provided a default value, but 2.1.x no longer does this.
Another change is that the kernel now creates a route automaticly when
you bring up an interface (this doesn't seem to apply to the loopback
interface, tho). You may
Make sure that this is the case. I have a network card and since
upgrading
I get this error twice from the /etc/init.d/network twice. Once when I
try to establish a route for lonet
route add -net 127.0.0.0
and the next when try to establish my network
route add -net 131.151.188.0
however establ
> When my 2.2.1 boots up, I got the following error:
> SIOCARDDRT: Invalid Argument
>
Hah...Shao before U post any message or rather query on this list, please
do make a search for your question on the user list archives. Do go to
www.debian.org or any of the mirrors and there is a link to the a
Finally it now worked. After installing smbfsx I had another problem:
To identify myself to our NT-Server I used to use my username and
workgroup, worked fine with the old version.
But now I have so supply as the workgroup name the domain name to the
smbmount-2.1.x commandline. Doesn't make 100%
Hello,
This is a guess, I don't have access to my linux box now.
Probably your computer is trying to use the sfxload command to load sound
samples to your card. Maybe it is not finding the sfxload program (it is on
awe-drv package in section sound) or it is not fiding the samples file. In my
box
On Wed, Feb 10, 1999 at 01:27:27PM +, [EMAIL PROTECTED] wrote:
> smbmount //bodiam/courses /mnt/bodiam/courses
> -U ahus1 -f 700 -d 700 -u 1003
>
> but that doesn't seem to work any more.
>
> What can I do?
Install smbfsx, Kernel 2.2 needs a completely different smbmount with a
different s
*- On 9 Feb, Ed Cogburn wrote about "[SOLVED] Re: Kernel 2.2.1: SIOCADDRT:
Invalid argument ?"
> "Ralf G. R. Bergs" wrote:
>>
>> On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
>>
>> > route add -net 127.0.0.0
>> >
>&
"Ralf G. R. Bergs" wrote:
>
> On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
>
> > route add -net 127.0.0.0
> >
> > Its the route command thats generating the "SIOCADDRT: Invalid
> >argument". I'm up to date with potato, (I got the kernel deb from
> >there) so what could this
On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
> route add -net 127.0.0.0
>
> Its the route command thats generating the "SIOCADDRT: Invalid
>argument". I'm up to date with potato, (I got the kernel deb from
>there) so what could this be?
The kernel automatically sets the rout
*- On 9 Feb, Ed Cogburn wrote about "Kernel 2.2.1: SIOCADDRT: Invalid
argument ?"
>
>
> After upgrading to the 2.2.1 kernel, I now get an error during
> bootup. I narrowed it to /etc/init.d/network:
>
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
>
> Its the rou
On Thu, 4 Feb 1999, Chris Wong wrote:
> I'm having troubles. I've just compiled the 2.2.1 kernel, and everything
> seems to be okay when compiling. But, when I restart my machine, it
> complains when it loads my modules. It says that my
>
> /lib/modules/2.2.1/modules.dep is empty!
Most probable
> I'm having troubles. I've just compiled the 2.2.1 kernel, and everything
>seems to be okay when compiling. But, when I restart my machine, it
>complains when it loads my modules. It says that my
>
>/lib/modules/2.2.1/modules.dep is empty!
>
>That file should have info on my ip_alias, cdrom, and n
20 matches
Mail list logo
