Comment 17 for bug 560306
Revision history for this message
| Jiri Grönroos (jiri-gronroos) wrote | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I have no problem in RC, signal stays even after Plymouth has finished. I have resolution of 1368x768 (as opposed to 800x600 in Alphas). I did not change anything (parts, cables) on my system.
Rafael, I only have one monitor and one cable connected at once. The first thing I tried was to change the cable but the signal was lost even with another DVI cable. The cable has always been connected to the upper output in GPU (which is to say DVI-0) although I've tried DVI-1 with similiar symptoms. I also plugged two cables into both DVI outputs at once (although only one of the cables had monitor in another end connected) but the signal was still lost after Plymouth.
I did not try to include Tim's linux-firmware_
Robert, I've tried to boot many daily builds without "quiet splash" but it had no effect (no matter how I put the cables).
I'm able to provide all files from /var/log/ from a successful RC live session as from installed system. I'm not able to provide dmesg from failed boot attempts. Now I'm using Ati's fglrx. Could this be a race condition somewhere?