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