grub issue

[michael miller]

uname -a & cat /proc/cmdline yield the same (correct) result in normal &
failed boots.  I'll try comparing the lsmod and log files in both
situations.  I'm usually cold starting when I see this problem.  There
is one thing that I could try.  My cpu has built in graphics, but I am
using an external graphics card so I can run two monitors.  I'll try
removing the graphics card and running off the cpu graphics to see if
the problem still occurs.  It's intermittent, so it may be a few days
before I know if that fixes the problem.

MikeO
n Tue, 2012-10-23 at 12:54 -0400, Michael ODonnell wrote:
> 
> Hmmmm, semi-repeatable failures to boot all the way up to
> a GUI-based login?
> 
> My first guess might be:
> 
>  - Maybe your graphics subsystem couldn't be initialized.
> 
>       Maybe your adapter has problems after a warm boot?
> 
>       Maybe driver not allowing enough time for initialization?
> 
>       Maybe compare output from "lsmod" for each case?
> 
>       See previous suggestions about /var/log/Xorg.0.log and friends.
> 
> Another (rather less probable) shot-in-the-dark guess:
> 
>  - Maybe GRUB is intermittently loading the wrong kernel or
>    handing it the wrong commandline.
> 
>       Are we sure you're running the same kernel in both situations?
> 
>       Maybe compare output from "uname -a" and "cat /proc/cmdline"
>       for each case?
> 
> I only mention that because the sort-of-cyclic nature you
> described made me think it's just barely possible you're
> enjoying some variant of this little bit of GRUB hell:
> 
>    https://duckduckgo.com/?q=GRUB_SAVEDEFAULT+GRUB_DEFAULT
>  
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/