[Newark] Diagnosing problems at boot

[Robert Roworth]

Just booted up and every thing was ok, don't know what happened. I'm saving all the advice just in case. Also the previous kernel does come up on the boot menu so I can boot from that if any more problems arise.

Thanks all for such a swift response.   Bob 

--- On Wed, 29/10/08, Steve Caddy <steve.m.caddy at ntlworld.com> wrote:

> From: Steve Caddy <steve.m.caddy at ntlworld.com>
> Subject: [Newark] Diagnosing problems at boot
> To: newark at mailman.lug.org.uk
> Date: Wednesday, 29 October, 2008, 9:08 AM
> This one is mainly for Bob, who was asking about USB
> problems at boot after a
> kernel upgrade.
> 
> I'm not sure if this email list accepts attachments or
> not, but it's worth
> giving this a go (if it doesn't work, we'll try
> something else):
> 
> You need to dump your last set of boot messages to a text
> file, using this
> command line:
> 
> cd ; dmesg > dmesg.txt
> 
> This performs 3 operations... first it sets the current
> directory to be your
> home directory (just in case it wasn't anyway), then it
> retrieves the boot
> messages using dmesg, and then it redirects the output to a
> file called
> dmesg.txt. You should then be able to find the resulting
> dmesg.txt file in
> your home area, and attach it to an email to this list.
> 
> Regards
> 
> Steve
> 
> -- 
> Steven M Caddy, MEng
> ------------------------------------------------------
> Email: steve.m.caddy at ntlworld.com
> 
> _______________________________________________
> Newark mailing list
> Newark at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/newark