Ubuntu system hangs after GRUB boot: no X gui.

Toggle sidebar Toggle sidebar
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
Gents:

Running Xeon.1240/z77a.gd55-BIOS1.2/nv430x2g/Auria-27"/24g ram/650W under Ubuntu 12.04x and GNOME recently installed & fully(?) updated.

After finishing build + software loading this system has been stable for 3 days, but many parts have worked fine much longer under various Linux versions. Initially I had tried to run an nv650, but BIOS would not support it; BSOD. Legacy nv430x2g has worked for months without issue.

This morning the system got-to GRUB displaying boot options, then refused to auto-boot into X-gui. Then, instead of X I got various text messages and N-curses screen options telling X had failed ... different complex messages on different re-boot tries. So I get to/past GRUB, but X-boot fails. I am feeling pretty lousy about this ... so I boot & run MEMTEST86 CD without issue. RAM and display look OKey. Again I re-boot.

Only this time I explicitly chose by "keytap" the 1st (of many!) expressed GRUB options: UBUNTU-generic.blablabla. That's default and what I always run. Strange how MINT still shows up on the GRUB menu even tho I wiped it out ... I think. Anyrate ...

... with that GRUB keytap choice of UBUNTU-generic the system now boots-into-X gui and the system behavior appears **normal**. I am running Electricsheep to keep it busy while I enter this report on my other box. I have no idea what happens with the new system if I tried to reboot ... but, I fear the worst. A quick look at the X.org log (in damn-your-eyes micro-type) rings-no-bell, but I don 't know if the failure events were captured and don't really know what to look for! There were **lots** of references to Nvidia ...

Anyrate such failure in a newly-built system is **not-OKey**. What could have caused the X-boot failure? Is this common ... GOOGLE says it's a tough task to de-bug X from text-mode if you get stuck there. Do I TRY to re-create failure? How do I start trouble shooting replace/modify whatever caused the failure?


 
Solution
ex_bubblehead
Then you need to go back to Windows my friend. Linux requires a more thorough knowledge of the low level ins and outs than does Windows. What I pointed you to is actually quite simple, if you make the effort to learn it.
Sort by date Sort by votes
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
My processor is a Xeon -- I have no onboard gfx.



 
Upvote 0 Downvote
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
eB:

I have read that page .. and the pages to which that page refer. I'll read them again ... there's not a snow-balls chance in hades of my understanding the code structures, or any of the convoluted tasks or how they relate to my boot issue. But, thanks for the suggestion.



 
Upvote 0 Downvote
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
Simple? I have needed to perform no such foolishness with GRUB since 2003 when I started with Linux. I reject byteboi elitism and assert: the OS will **operate the system**. That's the OS job for which I pay opportunity costs. You **do** know what they are, eh? UBUNTU 6 ->10 asked no such foolishness. A distro damned well will perform its assigned task or I will be rid of it!



 
Upvote 0 Downvote
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
GRUB is a snakepit if you didn't know already, but thanks for the RTFM **prod** eB. I love scanning shell-script gibberish on GOOGLE! My **boot** failures started to occur after an UPDATE MANAGER kernel update. Last year GOOGLE is littered with the broken bloody bodies of Ubuntu-ites seeing the same issue. Yes, I have **random** success booting out of GRUB, and I did a GRUB-MKCONFIG just to stir the pot ... indeed the non-existent MINT installations reported by GRUB vanished good-for-me ... but the barefoot behavior (bootless .. haha) continues.

System happens to be **UP** right now ... on one of the random successes ... and I'm poking around without much hope, Could well be the BIOS/graphics_card issue biting my *zz again somehow mediated by the kernel. Weird s*** happens in U_12.x! Mebby the only hope is to pay TD to flash BIOS.
 
Upvote 0 Downvote
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
Hummm... NV driver problem en?

While my system was booted UP I was prodding about and got an error message from NVIDIA saying I did not have a current driver. WOW! Mebby that's it, so I DLoaded the new driver and re-booted ...

...only to be greeted with a system that showed GRUB w/Debian splash, but mostly would not boot. I tried **recovery mode**, punched a few keys : and after cli **LOGIN and STARTX** was promptly informed X.org had a hissyfit! That the NVidia kernal module and Nvidia diver were not the same and the GUI would certainly not function with those different numbered code: NV Kernel mod(?) is 304.48 and the NVdriver is 304.88 ....

gawdbless the old dayz with a "sudo shutdown -h now" ... like RedHat 5..... or my ol' SGI IRIS mini! Anyrate looks like it's time to try a re-install and see if X.org can disentangle itself .. the 12.04 DVD install does prompt for an on-the-fly update and mebby that is dangerous! Thinking back, my current rock-solid U_10.04LTS took six-months to debug after I first installed it ... from what I can decode from GOOGLEing U_12.04 is worse .. much ,much worse.
 
Upvote 0 Downvote
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
I grabbed this error-message from a post at **stackoverflow.com** ; excepting the version numbers it's the same error message I get.

"...foo@bar-serv2:~/NVIDIA_CUDA-5.0_Samples/bin/linux/release$ nvidia-smi -a
NVIDIA: API mismatch: the NVIDIA kernel module has version 295.59,
but this NVIDIA driver component has version 304.54. Please make
sure that the kernel module and all NVIDIA driver components
have the same version...."
 
Upvote 0 Downvote
N

nss000

Distinguished
Apr 18, 2008
673
0
19,010
The error: "NVIDIA: API MISMATCH"

****************A solution syntax after boot fails: stuck in BSOD*************************

1) ctl-alt-F2 ... gives the CLI login prompt:
2) sudo apt-get-purge nvidia* ... gives screen gibberish signify nvidia driver removed.
3) sudo shutdown -h now ... allows a cold re-boot

Restarting, my systems displays GRUB, and boots into a GUI as instructed. Most everything seems to work, but I need to poke around. AFAICT there was **no** GRUB issue to the system boot failure ... "just" a video driver mismatch. Stupid ... computer :)

New DLoads ... whatever runs system display (NOT nv) it's OKey for Stellarium, Googleearth and electricsheep. Only a bit of "top-quarter" screen-trash upon reboot; disturbing though, and of-course I still get the Debian SPLASH not Ubuntu. But, that may be a price of admission to U_12.04. Almost frightening to believe this low-beta POC is fixed. I understand that with only 0.57% of the (shrinking) desktop PC market ambitious Canonical felt desperate ... they couldn't just make a better U_10.04LTS! No, of-course not ...

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom