What in the world is the issue with every single test 2.6.0 kernel
having issues with:
FATAL: keybdev not found.
FATAL: mousedev not found.
Could someone please explain why they appear when the mouse and keyboard
Are properly detected and everything is working just fine. I've tried editing
the modprobe.conf.dist and modprobe.conf to no avail.
I saw the earlier message that it doesn't matter, but still shouldn't there
be a way to get rid of the annoying kernel boot messages?
Also in this 2.6.0-0.1.14 there seems to be a very significant delay in the load
of modules.
Thanks,
RaXeT
On Sat, 2003-12-20 at 15:30, raxet wrote:
What in the world is the issue with every single test 2.6.0 kernel
having issues with:
FATAL: keybdev not found.
FATAL: mousedev not found.
Could someone please explain why they appear when the mouse and keyboard
Are properly detected and everything is working just fine. I’ve tried editing
the modprobe.conf.dist and modprobe.conf to no avail.
I saw the earlier message that it doesn’t matter, but still shouldn’t there
be a way to get rid of the annoying kernel boot messages?
Also in this 2.6.0-0.1.14 there seems to be a very significant delay in the load
of modules.
Thanks,
RaXeT
are you using a usb keyboard and mouse??? try ps2
jason pearl wrote:
On Sat, 2003-12-20 at 15:30, raxet wrote:
What in the world is the issue with every single test 2.6.0 kernel
having issues with:
FATAL: keybdev not found.
FATAL: mousedev not found.
Could someone please explain why they appear when the mouse and keyboard
Are properly detected and everything is working just fine. I’ve tried editing
the modprobe.conf.dist and modprobe.conf to no avail.
I saw the earlier message that it doesn’t matter, but still shouldn’t there
be a way to get rid of the annoying kernel boot messages?
Also in this 2.6.0-0.1.14 there seems to be a very significant delay in the load
of modules.
Thanks,
RaXeT
are you using a usb keyboard and mouse??? try ps2
I'm bleeding edge ps2 died in my mind years ago :) So the answer is no!
RaXeT
lol thro ps2 in and im sure it will work
On Sat, 2003-12-20 at 17:50, RaXeT wrote:
I saw the earlier message that it doesn’t matter, but still shouldn’t there
be a way to get rid of the annoying kernel boot messages?
You must get worked up easily. However, if you simply cannot sleep at night until those messages from rc.sysinit go away, apply the attached patch to /etc/rc.d/rc.sysinit.
All the patch does is to comment out the loading of usb filesystem, keybdev and mousedev, which don't exist in 2.6 (they're all still supported, but they're compiled in now, at least keybdev/mousedev functionality is).
~spot --- Tom "spot" Callaway <tcallawa(a)redhat*com> LCA, RHCE Red Hat Sales Engineer || Aurora SPARC Linux Project Leader
"The author's mathematical treatment of the conception of purpose is novel and highly ingenious, but heretical and, so far as the present social order is concerned, dangerous and potentially subversive. Not to be published." -- Aldous Huxley's "Brave New World"
On Sat, 2003-12-20 at 16:30, raxet wrote:
What in the world is the issue with every single test 2.6.0 kernel
having issues with:
FATAL: keybdev not found.
FATAL: mousedev not found.
Initscripts haven't been updated for 2.6 yet. Thus, they're looking for keybdev and mousedev (which don't exist anymore in 2.6) and not finding them and thinking that it cannot initialize USB keyboard and mouse.
Don't worry about it.
~spot --- Tom "spot" Callaway <tcallawa(a)redhat*com> LCA, RHCE Red Hat Sales Engineer || Aurora SPARC Linux Project Leader
"The author's mathematical treatment of the conception of purpose is novel and highly ingenious, but heretical and, so far as the present social order is concerned, dangerous and potentially subversive. Not to be published." -- Aldous Huxley's "Brave New World"
raxet (maxer1@xmission.com) said:
What in the world is the issue with every single test 2.6.0 kernel having issues with:
FATAL: keybdev not found. FATAL: mousedev not found.
Those drivers are built in in the 2.6 build, so loading the modules fails. It's a harmless error, it will go away eventually.
Bill