@Chris Halse Rogers: My laptop has been for warranty at Dell for almost
3 weeks, but as soon as it's back I'll test the Beta2.
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Chris Halse Rogers: Problem isn't fixed in the 2.6.32-20 kernel. System
doesn't boot (take a look at #561497).
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
We've had other reports of GeForce 6100 cards failing to boot with the
same problem. Given that disabling acceleration works, I think we
should quirk off acceleration by default on these cards, too. Then at
least you'll be able to boot properly.
--
Screen corruption on startup
@Marius Vasilescu: Your problem is different - that image is a classic
badly-driven display problem - could you please test the most recent
2.6.32-19 kernel, as there have been some fixes for that sort of
problem, and then file a new bug? Thanks.
@windexh8er: Your problem is *also* different,
Confirmed that noveau.fakeparam=yes is a valid workaround for same
video corruption on Dell Latitude D620 with the following line from an
lspci:
VGA Compatible controller: nVidia Corporation G72M [Quadro NVS
110M/GeForce Go 7300] (rev A1)
This bug is still apparent in beta 2.
--
Screen
Hi.
Booting with a false parameter like nouveau.fakeparam=yes works fine.
System now starts an shows a beautiful lucid desktop.
Yours sincerely
Mike (ZeroBeat)
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of
Lucid Beta1 (live CD) / Dell Inspiron 1520 / GeForce 8400M GS
blacklist=vga16fb nouveau.noaccel=1 params didn't work for me,
actually it did not change a thing.
After choosing the 'Try Ubuntu without changes on the system', the
keyboard stopped responding (not even the caps lock key worked).
I'm sorry, I did some more testing and the keyboard worked. It switched
between terminals, but the display didn't show it. For instance,
ctrl+alt+f2, sudo reboot, enter, enter = reboots the system. I was
mislead by the fact that caps lock LED didn't work after switching with
ctrl+alt+f2 (num lock
** Also affects: xserver-xorg-video-nouveau (Ubuntu Lucid)
Importance: High
Status: Confirmed
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Tags removed: needs-xorglog
** Tags removed: needs-lspci-vvnn
** Changed in: xorg (Ubuntu)
Status: Incomplete = Confirmed
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: xorg (Ubuntu) = xserver-xorg-video-nouveau (Ubuntu)
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Upstream is suspicious that vga16fb is part of the problem. Could you
please re-try the beta, adding “blacklist=vga16fb” as a boot option
rather than “nomodeset”? Thank you!
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Confirmed = Incomplete
--
Screen corruption on
** Attachment added: Xorg log from attempt with blacklist=vga16fb
http://launchpadlibrarian.net/41669856/Xorg.0.log.old
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Added blacklist=vga16fb as a boot option. This didn't help. System
still behaves the same. Screen becomes corrupted instead of showing the
desktop. I am attaching the dmesg and X org log file from the attempt.
** Attachment added: dmesg file from attempt with blacklist=vga16gb as boot
option
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided = High
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a
And you still can't switch virtual terminals?
I see that the same GPU lockup occurs in your dmesg (although it is much
less noisy about it, so vga16fb might be doing *something* there).
It would be nice if the X driver could continue in this case. I'll
bring this upstream.
--
Screen
Does booting with blacklist=vga16fb nouveau.noaccel=1 work correctly?
You won't get a nice transition from plymouth to X with that but X
should work with nouveau and it will help narrow down where the problem
is.
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received
Adding blacklist=vga16fb nouveau.noaccel=1 works. Desktop is up and
running. I'm using FireFox now to update the comment.
The transition from the splash (plymouth? Ubuntu with the dots
underneath) to desktop wasn't an issue. Screen went black for a couple
of seconds and then desktop appeared.
** Attachment added: Xorg log for blacklist=vga16fb nouveau.noaccel=1
http://launchpadlibrarian.net/41682024/Xorg.0.log
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
maybe the same bug like mine (take a look at #542639)
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
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
** Tags added: lucid
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
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
Hi D.,
Please attach the output of `lspci -vvnn` and `dmesg`, and attach your
/var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this
issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.
[This is an automated message. Apologies if it has
Here are the requested log files. Note that these files were only able
to be collected after a successful boot to the desktop. The failed boot
did not provide any opportunity to collect the files. I've included
both Xorg.0.log and Xorg.0.log.old.
** Attachment added: Xorg log file
** Attachment added: Xorg log from failed startup
http://launchpadlibrarian.net/41524692/Xorg.0.log.old
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: dmesg of successful startup
http://launchpadlibrarian.net/41524803/dmesg
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: dmesg of failed startup
http://launchpadlibrarian.net/41524854/dmesg.0
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: output of lspci -vvnn command after successful startup
http://launchpadlibrarian.net/41524982/lspci.out
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Additional info
Adding nomodeset as a boot option allows X to startup and I'm able to test out
the beta.
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
28 matches
Mail list logo
