On Wed, 16 May 2001, Nico Schottelius wrote:
> I attached the problem occured with parport and devfs. I don't exactly
> know where the problem in the parport source is. If someone has a
> patch for it, I will test it.
>
> [...]
>
> # make our own device out of /dev
> flapp:/ # mknod /lp0 c 6 0
On Wed, 16 May 2001, Nico Schottelius wrote:
I attached the problem occured with parport and devfs. I don't exactly
know where the problem in the parport source is. If someone has a
patch for it, I will test it.
[...]
# make our own device out of /dev
flapp:/ # mknod /lp0 c 6 0
Hmm..seems you are exactly right!
Sorry for that wrong though!
Nico
Philip Blundell wrote:
> >I attached the problem occured with parport and devfs.
> >I don't exactly know where the problem in the parport source
> >is. If someone has a patch for it, I will test it.
>
> I don't think this is
>I attached the problem occured with parport and devfs.
>I don't exactly know where the problem in the parport source
>is. If someone has a patch for it, I will test it.
I don't think this is a bug. You need to load the `lp' module.
p.
-
To unsubscribe from this list: send the line
Hello!
I attached the problem occured with parport and devfs.
I don't exactly know where the problem in the parport source
is. If someone has a patch for it, I will test it.
Nico
# Loading the parport and parport_pc modules for my parallelport
flapp:/home/user/nico/gpm-1.19.3 # modprobe
Hello!
I attached the problem occured with parport and devfs.
I don't exactly know where the problem in the parport source
is. If someone has a patch for it, I will test it.
Nico
# Loading the parport and parport_pc modules for my parallelport
flapp:/home/user/nico/gpm-1.19.3 # modprobe
Hmm..seems you are exactly right!
Sorry for that wrong though!
Nico
Philip Blundell wrote:
I attached the problem occured with parport and devfs.
I don't exactly know where the problem in the parport source
is. If someone has a patch for it, I will test it.
I don't think this is a bug.
I attached the problem occured with parport and devfs.
I don't exactly know where the problem in the parport source
is. If someone has a patch for it, I will test it.
I don't think this is a bug. You need to load the `lp' module.
p.
-
To unsubscribe from this list: send the line unsubscribe
On Tuesday 23 January 2001 10:25, Andris Pavenis wrote:
> On Friday 12 January 2001 13:35, Andris Pavenis wrote:
> > On Saturday 06 January 2001 15:28, Andris Pavenis wrote:
> > > Noticed following devfs related problems with kernel version 2.4.0 on
> > > one Pentium 2
Raphael wrote:
> I'm using ROCK Linux, which is built with devfs, originally Kernel
> 2.4.0-test9. This problem occurs, when I want to boot some Kernel after
> 2.4.0-test9, whereas building and installing the Kernel never is a problem.
>
> I enabled devfs support as well as the mounting of devfs
Hi there,
I'm using ROCK Linux, which is built with devfs, originally Kernel
2.4.0-test9. This problem occurs, when I want to boot some Kernel after
2.4.0-test9, whereas building and installing the Kernel never is a problem.
I enabled devfs support as well as the mounting of devfs at bootup in
Hi there,
I'm using ROCK Linux, which is built with devfs, originally Kernel
2.4.0-test9. This problem occurs, when I want to boot some Kernel after
2.4.0-test9, whereas building and installing the Kernel never is a problem.
I enabled devfs support as well as the mounting of devfs at bootup in
Raphael wrote:
I'm using ROCK Linux, which is built with devfs, originally Kernel
2.4.0-test9. This problem occurs, when I want to boot some Kernel after
2.4.0-test9, whereas building and installing the Kernel never is a problem.
I enabled devfs support as well as the mounting of devfs at
13 matches
Mail list logo
