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.