| 1 |
On 08/05/2010 03:54 AM, Neil Bothwick wrote: |
| 2 |
> On Thu, 05 Aug 2010 08:19:29 +0800, Bill Kenworthy wrote: |
| 3 |
> |
| 4 |
>> Is there a way to log the boot messages - dmesg after booting up doesnt |
| 5 |
>> show module load failures and they scroll off the screen and I can find |
| 6 |
>> what they are. |
| 7 |
> |
| 8 |
> Set rc_logger="YES" in /etc/rc.conf to have the boot sequence logged |
| 9 |
> to /var/log/rc.log. This is for BL2, BL1 has a similar setting. |
| 10 |
> |
| 11 |
> It gives this output here |
| 12 |
> |
| 13 |
> rc boot logging started at Tue Aug 3 17:39:35 2010 |
| 14 |
> |
| 15 |
> * Setting system clock using the hardware clock [UTC] ... |
| 16 |
> [ ok ] |
| 17 |
> * Loading module fuse ... |
| 18 |
> [ ok ] |
| 19 |
> * Loading module rfcomm ... |
| 20 |
> [ ok ] |
| 21 |
> * Loading module kvm-intel ... |
| 22 |
> [ ok ] |
| 23 |
> * Autoloaded 3 module(s) |
| 24 |
> ... |
| 25 |
> |
| 26 |
> You can also increase the size of the dmesg ring buffer, which was |
| 27 |
> discussed on this list last month. |
| 28 |
> |
| 29 |
> |
| 30 |
|
| 31 |
After booting try Shift-PageUp. Hopefully your not booting to run level |
| 32 |
5, if you are you need to get to the alternate terminal with all the |
| 33 |
messages on it. Try Shift-PageUp before and after logging in. The |
| 34 |
buffer isn't that big and I'd like to know how it can be increased so I |
| 35 |
can go back to earlier messages, but I haven't found that out yet. |
| 36 |
|
| 37 |
The Shift-PageUp may get you back far enough to see the message that |
| 38 |
scrolled by. |
Archives