Deleting the xorg.conf, it still fails. Here's the log with it deleted
and nv.ids gone.
** Attachment added: xorg log without an xorg.conf and without nv.ids
http://launchpadlibrarian.net/28602254/Xorg.0.log
--
karmic alpha2 candidate doesn't boot up on Studio XPS 1340
Hi Robert:
I've removed the nv.ids from /usr/share/xserver-xorg/pci (if there was
more that your package does, i'll add your package on too - it's just
harder to test from a PPA behind a network requiring proxy
authentication).
Still have failures, here's the Xorg.0.log from that scenario:
**
Ahh its ok, that should have the same effect. How about if you delete
/etc/X11/xorg.conf entirely? xorg.conf is going away real soon now, if
it works without it great, if not a simple little patch in the detection
logic for xserver to match 10DE 086x pci id's to vesa will do it.
--
karmic alpha2
** Package changed: xserver-xorg-video-nv (Ubuntu) = xorg-server
(Ubuntu)
--
karmic alpha2 candidate doesn't boot up on Studio XPS 1340
https://bugs.launchpad.net/bugs/385658
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Actually this is the same problem that was resolved in 9.04
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/304445
So this is a regression
--
karmic alpha2 candidate doesn't boot up on Studio XPS 1340
https://bugs.launchpad.net/bugs/385658
You received this bug notification because
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27754972/Dependencies.txt
** Attachment added: GdmLog.txt
http://launchpadlibrarian.net/27754973/GdmLog.txt
** Attachment added: GdmLogOld.txt
http://launchpadlibrarian.net/27754974/GdmLogOld.txt
** Attachment added:
Here's my failsafe .tar. It's far more informative than any of that
ubuntu-bug stuff (since the ubuntu-bug stuff was done when I booted with
VESA forcefully)
** Attachment added: failsafeX-backup-090610123126.tar
http://launchpadlibrarian.net/27755009/failsafeX-backup-090610123126.tar
--
7 matches
Mail list logo
