We help IT Professionals succeed at work.

Problem with Reboot/Shut Down

Harry_Truman
Harry_Truman asked
on
576 Views
Last Modified: 2013-12-15
I've got a problem when I reboot or shutdown my Ubuntu VM. I'm running 7.04 in the most recent Parallels 3.0 on an Intel MacBook Pro, but I had the same problem happening on my Windows computer that I installed Linux on a few months ago.

The problem is that, during a reboot, the second that the OS begins unloading the display gets scrambled. It stays like that for the duration of the system shutting down and then the display goes back to normal (proper text) at BIOS. When I shutdown entirely, the process seems to stop somewhere along the way and the system never shuts down entirely; I'm forced to hit the power button.
Screenshot: http://ubuntuforums.org/attachment.php?attachmentid=45865&d=1192026032

I'm really not sure what's going on, I've never seen anything like this in my previous Ubuntu installs except for with 7.04, and I've not seen Windows/Mac/Linux do anything like this before. Can anyone point me in the right direction on this one?
Comment
Watch Question

Software Developer
CERTIFIED EXPERT
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Duncan RoeSoftware Developer
CERTIFIED EXPERT

Commented:
Ok I tried it and the corruption went away. I am not familiar with Ubuntu /etc rc scripts but the commands to look for are fbset (sets framebuffer resolution) and udevd (manages the udev /dev mount).
Before udev starts, you have the old-style /dev directory on the root device. This should have an entry for fb0:

crw-rw----  1 root video 29, 0 2007-10-13 17:15 /dev/fb0

As it happens, mine had that already. You should mknod it if it's not there (in case fbcon is a module)

Because udev hides the real /dev by doing a tmpfs mount of /dev, you may need to reboot with "init=/bin/bash" to access the "real" /dev. Once you have verified it contains fb0, alter your startup scripts so fbset is done before udevd and not done again after udevd.
(don't include the double quotes on the boot command line)
Duncan RoeSoftware Developer
CERTIFIED EXPERT

Commented:
Oh dear, not so good after all. If I go in and out of X, corruption reappears. If I issue halt or reboot commands fro an xterm, corruption is worse than previously.
I really think you want to get rid of framebuffer console.
In the interim, if you Ctrl-Alt-F6 back to a console before shutting down the system, corruption may not be so bad.

Author

Commented:
Yeah, I've noticed that anything I do outside of X really doesn't cause any issues.  I'll give it a shot and see what happens, at the very least I can just revert to a snapshot if anything gets worse...
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Duncan RoeSoftware Developer
CERTIFIED EXPERT

Commented:
I believe I identified the problem as being framebuffer so deserve credit. MushyPea posted a nice website about framebuffer with at least one useful observation: "If you don't care about a graphic boot then you don't need framebuffer" - true enough if you want to use X windows all the time.
I think I did the lion's share, but wouldn't object to a split.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.