Ubuntu 12.04 + Sony SDM-P234 display

sudo mv -v /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
mv: cannot stat `/etc/X11/xorg.conf’: No such file or directory

Heh … read the next line “the above command may fail, but just carry on with the next command” :wink:

That line is only to backup an already existing xorg.conf IF IT EXISTS … if it doesn’t exist, the command will fai, but just carry on :wink:

Thanks and my apologies.
I’m back at the login screen and it’s refusing to reboot. Seems quite sluggish too, getting the Suspend / Shutdown menu to drop.
Would a REISUB be appropriate at this point?

Yeh, give it a shot.

Rebooted and logged in. I’m afraid screen is still unreadable at his point.

I can just about make out on the screen:

System program problem detected
Do you want to report the problem now
Cancel / Report problem…

OK, try this …

Reboot to recovery, then run:

sudo mv -v /etc/X11/xorg.conf /etc/X11/xorg.conf.broken

Reboot to recovery again, and run:

sudo dpkg-reconfigure xserver-xorg-video-intel

Then reboot (normally) to test.

[EDIT]

Oh, it would have been nice to know what it said the problem was

sudo mv -v /etc/X11/xorg.conf /etc/X11/xorg.conf.broken
File or directory does not exist

sudo dpkg-reconfigure xserver-xorg-video-intel
/sbin/ldconfig.real: Can’t create temprorary cache file /etc/ld.so.cache~: Read-only file system

Oh, it would have been nice to know what it said the problem was

I didn’t Mark. That’s al the message said - it was a popup on screen.

What’s the output from:

ls -a /etc/X11

and

ls -l ~/xorg.conf.new

?

ls -a /etc/X11
. fonts xorg.conf Xsession
… rgb.conf.failsafe Xsession
app-defaults X Xreset Xsession.options
cursor xinit Xreset.d Xwrapper.config
defaults-display-manager xkb Xresources

ls -l ~/xorg.conf.new
ls cannot access /root/xorg.conf.new: No such file or directory

Seems you’re logged onto a root prompt … what’s your username on the PC ?

[EDIT]

Ignore that … it’s ubuntu3 … correct ?

If so, what’s the output from:

ls -l /home/ubuntu3/xorg.conf.new

?

Does the command line prompt end with an # or an $ ?

Ignore that … it’s ubuntu3 … correct ?
Correct

ls -l /home/ubuntu3/xorg.conf.new
-rw-r–r-- 1 root root 5179 Jul 14 14:16 /home/ubunut3/xorg.conf.new

It’s in the wrong place, right ?

Does the command line prompt end with an # or an $ ?

#

OK, try this:-

mv -v /home/ubunut3/xorg.conf.new /etc/X11/xorg.conf

then run:

ls -a /etc/X11

If xorg.conf is listed in the output … reboot normally to test.


And remember …

sudo mv -v /etc/X11/xorg.conf /etc/X11/xorg.conf.broken

then rebooting will get you back to where you are now.

mv -v /home/ubunut3/xorg.conf.new /etc/X11/xorg.conf
mv: cannot move /home/ubuntu3/xorg.conf.new' to /etc/X11/xorg.conf’: Read-only file system

Sorry about this Mark

OK, somewhat baffled by that … how did you get to the root prompt ? … for some reason the file system seems to be getting mounted as read only ???

I booted into ‘Recovery’ mode and chose the option:
root Drop to root shell prompt

What happens if you run:

mount -o remount,rw /

then

mv -v /home/ubunut3/xorg.conf.new /etc/X11/xorg.conf

If that works … run:

touch /forcefsck

then reboot normally.

If it doesn’t work … tell me what the output from the first command was.

That all seemed to work fine. Move appeared to work, received:
/home/ubuntu3/xorg.conf.new' -> /etc/X11/xorg.conf’

Second and third prompts no output

OK, reboot normally:

reboot

or

shutdown -r now

it will run a file system check during the bootup, let it finish … and when it does, tell me if the screen is OK now.


Be Aware … if you EVER use the REISUB/REISUO trick, you MUST leave a few seconds between each keystroke.