Hello,
I just switched to a self compiled 2.6.0-test4 kernel with devfs support on
my Debian unstable system. devfsd is running nicely without any complaints.
On my old 2.4.20 kernel I did not use devfs.
Now when I boot into the new 2.6 kernel it starts up but throws tons of
messages like
...
FATAL: Module /dev/ttyx0
FATAL: Module /dev/ttyx1
FATAL: Module /dev/ttyx2
FATAL: Module /dev/ttyx3
FATAL: Module /dev/ttyx4
FATAL: Module /dev/ttyx5
...
and it seems not to find alot of other /dev entries as well.
Googling around I did not find any hints about where this problem might
come from.
Any ideas what might be wrong?
TIA, Harry
> Any ideas what might be wrong?
Modprobe is too verbose when it comes to devfs failures.
This is known issue, and Rusty Russel has a patch for modutils, but he
hasn't merged it yet, I think (or has he?).
In message <[email protected]> you write:
>
> > Any ideas what might be wrong?
>
> Modprobe is too verbose when it comes to devfs failures.
> This is known issue, and Rusty Russel has a patch for modutils, but he
> hasn't merged it yet, I think (or has he?).
I've just released 0.9.14.
Cheers!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
Harry Brueckner wrote:
> ...
> FATAL: Module /dev/ttyx0
> FATAL: Module /dev/ttyx1
> FATAL: Module /dev/ttyx2
> FATAL: Module /dev/ttyx3
> FATAL: Module /dev/ttyx4
> FATAL: Module /dev/ttyx5
> ...
I had this, too. But it disappeared with test5-mm1 on my debian sid.
Try to update sysvinit. If that does not help, try with a newer kernel,
too.
claa. But it disappeared with test5-mm1 on my debian sid.
Try to update sysvinit. If that does not help, try with a newer kernel,
too.
claas