|
This is exactly what happened for me when
I moved to FC3. The console is
detecting that a framebuffer was initialized and
tries to grab it for its use. The
old method of adding video=vc:0-0 to your boot command
line to prevent this doesn’t seem to work with the FC kernel. Someone else posted a work around that
fixed the problem for me. You can
try adding vga=792 to your boot command line. I think it will only work if you have
another video card installed that has a framebuffer. All this does is make the console grad
the video card’s framebuffer
instead of ivtv-fb. -----Original Message----- Hi John, I seem to be having an issue that is different from
that described in that thread though. It seems that if I try to force the
ivtv module to load during startup the workstation freezes. What I am seeing is the boot process will get to the
line "/sbin/modprobe ivtv" (in rc.local) and start to display the
debug info that is normally put into the dmesg log (but without carrige
returns?) and then hangs up? I suspect that this is from the autoloading of ivtv-fb
module. I took out the line telling linux to autoload the ivtv-fb module from
the modprobe.conf and tried to load the two modules individually (via command
line) before starting X. When I do it that way it seems to execute the
"/sbin/modprobe ivtv" without issue but when I issue the
"/sbin/modprobe ivtv-fb" command I get the above described system
hangup. The strange thing is that this only happens when I
call the the "/sbin/modprobe ivtv-fb" from the rc.local, if I
execute that from a terminal window while running X-windows it seems to execute
ok? A couple of questions: is there anything else that I should have done? Since the machine locks up I can't get the messages
out of the /var/log/dmesg log to send you, any ideas of what I can do to
capture this? dave |
