** Tags added: valid-xorg-conf
--
Latest mod to xorg makes X unusable on Toshiba laptop
https://bugs.launchpad.net/bugs/152678
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Just to be sure, is this bug about: you can not have a virtual screen
size that allows you to pan around? Can you update the title and
description so it is moreclear what the problem is? Like expected
versus observed behaviour. Please try to be as concise, clear and
technically precise as
OK -- will do that. I've determined that my particular problem is caused by
this sequence:
1 -- editing xorg.conf to add the line Virtual 1600 1200 (or replacing with one
that is correct)
2 -- booting or restarting X -- gdm gives login, login results in a screen not
using the virtual size,
OK, have removed xorg.conf and rebooted. I'm running in a 1024x768 screen (it
looks like) and it feels like i'm wearing a straight jacket. I am attaching
the Xorg.0.log file that was generated on bootup from cold.
As this installation was upgraded during development, I've grabbed an
Modified the dpkg-reconfigure file and have booted with it. It does not
recognize the 'virtual' line. I'm adding the dpkg-reconfigure file to
the attachments. I'll wait until you let me know what actions will help
the most.
I see another Xorg.0.log generated on boot. Will attach that as well.
This is the Xorg.0.log generated when I booted with the xorg.conf
generated by the dpk-reconfigure command. At this point I still do not
have my 1600x1200 virtual display, and only have the default (24) depth.
I notice that the log file is shorter than the last. Do you want one
created when
A new xorg.conf is usually not generated, only if you use Screen and
Graphics or sudo dpkg-reconfigure -phigh xserver-xorg. Try without
one and attach the resulting Xorg.0.log. Then use dpkg-reconfigure to
generate one and add the Virtual line.
For the moment I am interested in what the
OK will try the 'intel' driver, and will try without any xorg.conf file. Yes,
I use the 'Screen and Graphics' gui. It's the only way that I can get the 1600
x 1200 display back. Without using it, I end up with my useable.xorg.conf
changed to the one you see. Hmmm... Is this a rational
Please also try without any xorg.conf. The xorg.conf is usually not
modified automatically. Do you use the Screen and Graphics GUI? It
will rewrite your xorg.conf...
--
Latest mod to xorg makes X unusable on Toshiba laptop
https://bugs.launchpad.net/bugs/152678
You received this bug notification
Have you tried the intel driver instead of i810?
--
Latest mod to xorg makes X unusable on Toshiba laptop
https://bugs.launchpad.net/bugs/152678
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Thanks for your report and prose. Which driver are you using? Can you
please attach conf and log files?
** Changed in: ubuntu
Assignee: (unassigned) = Tormod Volden (tormodvolden)
Status: New = Incomplete
--
Latest mod to xorg makes X unusable on Toshiba laptop
Sent tar.gzipped files in e-mail, attaching the various files here...
Xorg log file, useable.x.conf and x.conf that has been mangled. At this
point, the mangled x.conf file will run, but has lost all the color
depth entries except 24 (I have some reasons for using 16 fairly often)
and has nuked
here is the useable.xorg.conf that I write over the crippled one that it
thinks I shoujld use.
** Attachment added: useable.xorg.conf
http://launchpadlibrarian.net/10061745/useable.xorg.conf
--
Latest mod to xorg makes X unusable on Toshiba laptop
https://bugs.launchpad.net/bugs/152678
You
And lastly, from /var/log -- the tracks of what it thought it was doing.
This is from the last bootup.
What I must do in order to work, is to run the following script:
#!/bin/bash
#fix xorg.conf resolution --
#
sudo rm /etc/X11/xorg.conf.*
sudo cp /etc/X11/useable.xorg.conf /etc/X11/xorg.conf
After deleting the xorg.conf file and all the backups -- and the
xorg.conf.failsafe ones to try to force it to a useable state, leaving
only the hand-edited xorg.conf it smears X completely. Evidently
whatever changes have been made ignore the 'Virtual' keyword and attempt
to use the virtual size
OK here's my workaround. It's a pain in the fundament, but does get me going.
I reconfigure X to get the crippled xorg.conf file that lets me run. That
gets me going in the crippled 1024x768 screen. I copy a working xorg.conf file
from a working Feisty installation and write it over the
17 matches
Mail list logo
