| 1 |
On Thu, 2010-08-05 at 12:47 +1000, Rod wrote: |
| 2 |
> On 5/08/2010 11:10 AM, Dakota wrote: |
| 3 |
> > On 8/4/2010 8:19 PM, Bill Kenworthy wrote: |
| 4 |
> > |
| 5 |
> >> Is there a way to log the boot messages - dmesg after booting up doesnt |
| 6 |
> >> show module load failures and they scroll off the screen and I can find |
| 7 |
> >> what they are. |
| 8 |
> >> |
| 9 |
> >> BillK |
| 10 |
> >> |
| 11 |
> >> |
| 12 |
> >> |
| 13 |
> >> |
| 14 |
> >> |
| 15 |
> > /var/log/messages doesn't contain anything relevant? I thought that's |
| 16 |
> > where stuff like that got logged. |
| 17 |
> > Also, have you checked /var/log/kern.log? |
| 18 |
> > |
| 19 |
> > |
| 20 |
> |
| 21 |
> You'd possibly find that /var/log/everything/current is the Gentoo |
| 22 |
> logging location I have a symlink from there to /var/log/messages |
| 23 |
> |
| 24 |
> There is a backup of dmesg stored in /var/log/dmesg |
| 25 |
> |
| 26 |
> I use a combination of dmesg | less and /var/log/everything/current |
| 27 |
> and lsmod for module testing (if they load and don't load) |
| 28 |
> |
| 29 |
|
| 30 |
/var/log/everything was replaced by /var/log/messages in 2005 (and this |
| 31 |
system dates from ~2001 and was dd'd from a dell to the sony - dont you |
| 32 |
luv linux!) so I have the directory but nothing actually "current" in |
| 33 |
there. |
| 34 |
|
| 35 |
There is a dmesg file, same content as given by the dmesg command |
| 36 |
|
| 37 |
I think most (or all) the modules that errored were not found (I do load |
| 38 |
most modules manually) as over the years there have been problems with |
| 39 |
both order and loading when needed. Maybe time to clear them out and |
| 40 |
see if autoloading actually works now ... it doesnt on my mythbox but |
| 41 |
this system is a lot simpler. |
| 42 |
|
| 43 |
BillK |
Archives