Richard-
i posted some additional comments on your bug report. it appears from reading
the bugzilla report and the thread you referred me to that we are having the
same exact problem. interestingly, the problem alerted me to others. the nogui
option informed of issues with cpuspeed and some other modprobe issues. i am
wondering did you ever have this problem:
modprobe: FATAL: module mousedev not found
it perplexes me because my mouse has worked since installing (and still does).
i am assuming i must make a modprobe entry. do you know what that entry should
be? and why is this reporting an error if the mouse works? if you can help me
with this too that would be great; if not, hopefully we can work this other
problem out together and get our systems up and running again. thanks...
mark.
--- Richard Ayer III <rwa1(a)cec.wustl.edu> wrote:
I've been having the same problem since 2.6.3-1.106; it's now
happens with
every version of the kernel that I try to use.
Take a look at bug #117658, which I posted a few hours ago. See if you have
anything to add to that. You can also look at the 'system crash' thread that
I started on the list on 2/26/04. From that thread, a temporary 'workaround'
is to arrow to the kernel version you want to boot, hit 'e', arrow down one
and hit 'e' again, change 'rhgb' to 'nogui', hit 'enter'
and then hit 'b' to
boot. The change is only for that boot (i.e., you have to redo it every time
unless you changed it in grub.conf). See if you get the other problem I
describe in the bug report after doing the above.
Richard Ayer III
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you�re looking for faster
http://search.yahoo.com