Unknown error

Unknown error

[louisg00]

I'm running kernel-2.4.8-ac1 on RH beta and I'm this:

modprobe: modprobe: Can't locate module char-major-226
Did I forget a to compile a module?

Louis

Re: Unknown error

[Keith Owens]

On Sun, 12 Aug 2001 1:40:01 -0400, 
<louisg00@bellsouth.net> wrote:
>I'm running kernel-2.4.8-ac1 on RH beta and I'm this:
>
>modprobe: modprobe: Can't locate module char-major-226
>Did I forget a to compile a module?

2.4.8 says that device 228 is unassigned, but ...

  drivers/char/drm/drm.h:#define DRM_MAJOR       226
  drivers/net/wan/sdla_chdlc.c:#define WAN_TTY_MAJOR 226

Somebody has been naughty and used a code not assigned to them.

Re: Unknown error

[Alan Cox]

> On Sun, 12 Aug 2001 1:40:01 -0400, 
> <louisg00@bellsouth.net> wrote:
> >I'm running kernel-2.4.8-ac1 on RH beta and I'm this:
> >
> >modprobe: modprobe: Can't locate module char-major-226
> >Did I forget a to compile a module?
> 
> 2.4.8 says that device 228 is unassigned, but ...
> 
>   drivers/char/drm/drm.h:#define DRM_MAJOR       226
>   drivers/net/wan/sdla_chdlc.c:#define WAN_TTY_MAJOR 226
> 
> Somebody has been naughty and used a code not assigned to them.

The 2.4.8 tables are _completely_ out of date. 

The up to date tables say:

226 char        Direct Rendering Infrastructure (DRI)
                  0 = /dev/dri/card0		First graphics card
                  1 = /dev/dri/card1            Second graphics card 


Peter - was this dual issued, or do Sangoma need to be spanked. The obvious
place to put the sdla tty would I think be 229, since its not physically
possible to put one in an iSeries machine.

Re: Unknown error

[H. Peter Anvin]

Followup to:  <E15Vti5-0005ao-00@the-village.bc.nu>
By author:    Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> > On Sun, 12 Aug 2001 1:40:01 -0400, 
> > <louisg00@bellsouth.net> wrote:
> > >I'm running kernel-2.4.8-ac1 on RH beta and I'm this:
> > >
> > >modprobe: modprobe: Can't locate module char-major-226
> > >Did I forget a to compile a module?
> > 
> > 2.4.8 says that device 228 is unassigned, but ...
> > 
> >   drivers/char/drm/drm.h:#define DRM_MAJOR       226
> >   drivers/net/wan/sdla_chdlc.c:#define WAN_TTY_MAJOR 226
> > 
> > Somebody has been naughty and used a code not assigned to them.
> 
> The 2.4.8 tables are _completely_ out of date. 
> 
> The up to date tables say:
> 
> 226 char        Direct Rendering Infrastructure (DRI)
>                   0 = /dev/dri/card0		First graphics card
>                   1 = /dev/dri/card1            Second graphics card 
> 
> 
> Peter - was this dual issued, or do Sangoma need to be spanked. The obvious
> place to put the sdla tty would I think be 229, since its not physically
> possible to put one in an iSeries machine.
> 

226 is assigned to DRI.  I don't know anything about an "sdla tty"
unless it is in my post-Linus-prononucement queue, which I have yet to
deal with.

The current list is dated 3 June 2001 (I just noticed it wasn't up on
www.lanana.org; I just fixed that.)  It includes all registrations I
had received up to Linus' "no new majors" pronouncement -- it should
be included in both Linus' and your trees.

http://www.lanana.org/docs/device-list/devices.txt

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

Re: Unknown error

[Rogier Wolff]

Alan Cox wrote:
> > 2.4.8 says that device 228 is unassigned, but ...
> > 
> >   drivers/char/drm/drm.h:#define DRM_MAJOR       226
> >   drivers/net/wan/sdla_chdlc.c:#define WAN_TTY_MAJOR 226
> > 
> > Somebody has been naughty and used a code not assigned to them.

> 226 char        Direct Rendering Infrastructure (DRI)
>                   0 = /dev/dri/card0		First graphics card
>                   1 = /dev/dri/card1            Second graphics card 
> 
> 
> Peter - was this dual issued, or do Sangoma need to be spanked. The obvious
> place to put the sdla tty would I think be 229, since its not physically
> possible to put one in an iSeries machine.

Speaking of which... 

I always (try to) write my drivers to do:

#ifndef MY_MAJOR
#define MY_MAJOR xyz
#endif

This allows "test-compilation" with -Dtest_major , but is also
preparing for having a "majors.h" which defines ALL the major numbers
in one place. The place where it /completly/ obvious if two devices
are trying to use the same major.... 

			Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

unknown error

[Angel Tsankov]

Has anyone ever encountered error 4294967295 while using iptables?!

Unknown error.

[Justin Schoeman]

Hi again.

I was wondering if anybody could help me.  I am using kernel 2.6.17.8 
with iptables 1.3.5, and I get the following error:

iptables: Unknown error 4294967295

for this command:

/usr/local/sbin/iptables -A INPUT -j CONNMARK --save-mark

I see a large number of hits for the error message on google, mainly 
related to iptables 1.3.5, but I have not seen one thread with a 
conclusive solution.

Could anybody please give me some pointers on where to start looking? Is 
this an iptables bug, if so, what is the last good version.  If not, 
what else can I look for?

Thanks,

Justin

RE: Unknown error.

[Daniel Williams]

The bug is an error message mapping. 

So in other words the command is failing for a legitimate reason,
iptables is just not giving you the useful error message. Try 1.3.4 and
see what the error message is, I don't believe you will find much
different.

Daniel 

-----Original Message-----
From: netfilter-bounces@lists.netfilter.org
[mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of Justin
Schoeman
Sent: Friday, 11 August 2006 1:35 AM
To: netfilter@lists.netfilter.org
Subject: Unknown error.

Hi again.

I was wondering if anybody could help me.  I am using kernel 2.6.17.8 
with iptables 1.3.5, and I get the following error:

iptables: Unknown error 4294967295

for this command:

/usr/local/sbin/iptables -A INPUT -j CONNMARK --save-mark

I see a large number of hits for the error message on google, mainly 
related to iptables 1.3.5, but I have not seen one thread with a 
conclusive solution.

Could anybody please give me some pointers on where to start looking? Is

this an iptables bug, if so, what is the last good version.  If not, 
what else can I look for?

Thanks,

Justin

Re: Unknown error.

[Ming-Ching Tiew]

I don't think you can perform CONNMARK on the INPUT chain
of the filter table, try doing it on the mangle table :-

/usr/local/sbin/iptables -t mangle -A INPUT -j CONNMARK --save-mark

Cheers.
----- Original Message ----- 
From: "Justin Schoeman" <justin@expertron.co.za>
To: <netfilter@lists.netfilter.org>
Sent: Friday, August 11, 2006 1:34 AM
Subject: Unknown error.


> Hi again.
> 
> I was wondering if anybody could help me.  I am using kernel 2.6.17.8 
> with iptables 1.3.5, and I get the following error:
> 
> iptables: Unknown error 4294967295
> 
> for this command:
> 
> /usr/local/sbin/iptables -A INPUT -j CONNMARK --save-mark
> 
> I see a large number of hits for the error message on google, mainly 
> related to iptables 1.3.5, but I have not seen one thread with a 
> conclusive solution.
> 
> Could anybody please give me some pointers on where to start looking? Is 
> this an iptables bug, if so, what is the last good version.  If not, 
> what else can I look for?
> 
> Thanks,
> 
> Justin
> 

Re: Unknown error.

[Ming-Ching Tiew]

Cheers.
From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>


> 
> I don't think you can perform CONNMARK on the INPUT chain
> of the filter table, try doing it on the mangle table :-
> 
> /usr/local/sbin/iptables -t mangle -A INPUT -j CONNMARK --save-mark
> 

Hmm I issue the commands on the filter table and INPUT chain on my system,
it seems to work too. And therefore your error is likely due to iptables not 
compiled against the correct kernel source.

Re: Unknown error.

[Justin Schoeman]

OK - That one did it!  Got a meaningful error message, and realised that 
somehow I had not built the CONNMARK module ;-) .

Now, the next error, when I try to load a geoip match:

/usr/local/sbin/iptables -t mangle -A INPUT -m geoip --dst-cc ZA -j ACCEPT

I get:

iptables: Invalid argument

with the following in dmesg:

ip_tables: geoip match: invalid size 0 != 96

It seems like some critical piece of geoip /xt_tables integration is not 
in place... Is my analysis correct?  If so, is there a porting document 
somewhere covering the iptables updates since geoip last worked?

Thanks,

Justin

Bob Boucneau wrote:
> Hi Justin,
> 
> Should be fixed in current Netfilter.  This was a bug.
> 
> http://lists.netfilter.org/pipermail/netfilter-buglog/2006-April/000921.html
> 
> B
> 
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org
> [mailto:netfilter-bounces@lists.netfilter.org]On Behalf Of Justin Schoeman
> Sent: Thursday, August 10, 2006 11:35 AM
> To: netfilter@lists.netfilter.org
> Subject: Unknown error.
> 
> Hi again.
> 
> I was wondering if anybody could help me.  I am using kernel 2.6.17.8
> with iptables 1.3.5, and I get the following error:
> 
> iptables: Unknown error 4294967295
> 
> for this command:
> 
> /usr/local/sbin/iptables -A INPUT -j CONNMARK --save-mark
> 
> I see a large number of hits for the error message on google, mainly
> related to iptables 1.3.5, but I have not seen one thread with a
> conclusive solution.
> 
> Could anybody please give me some pointers on where to start looking? Is
> this an iptables bug, if so, what is the last good version.  If not,
> what else can I look for?
> 
> Thanks,
> 
> Justin
>