| From: Neil Bird <[EMAIL PROTECTED]> | Around about 09/07/06 22:44, D. Hugh Redelmeier typed ... | > I get an oops again (included at bottom of this message). | | Actually, the bottom of your oops [how did you grab the text for that?] | looks suspiciously similar to the ivtv+v4l problem I just asked about ...
My oops capture was from when I manually did a modprobe. It did not lock up the machine. So I just captured the output from dmesg(8). When I rebooted, the boot did hang. So I booted again, but chose a different kernel. That boot succeeded (the problematic modules are installed per-kernel, so they did not come into play with the other kernel). I them removed the rpms causing problems (rpm -e). Then my original kernel would boot with no problem (and no modules). There are other ways to skin this cat. For example, boot from a rescue CD and manually hide the bad module files. Then reboot with the original kernel. In theory, one could capture the log from a bad startup by using a serial console. You hook up a terminal (usually another computer running minicom(1)) through a serial cable, specify some magic boot parameters to the kernel (in grub.conf), and boot. The console chatter shows up on the terminal instead of the VGA screen. Very handy. But not handy enough that I've actually used it this millennium. _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
