[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
Tom Holy, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/570011/comments/24 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570011 Title: Modesetting fails if large screen monitor attached at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/570011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
This is no longer a problem in Maverick alphas (daily build from 2010-08-26). -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
This is no longer a problem in Maverick alphas (daily build from 2010-08-26). -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
I should have also added: it still is a problem in Lucid, if I turn KMS back on. -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
Yet another update. It turns out that compositing proved not to be the culprit; things got bad faster if compositing was on, but eventually it happens anyway even if compositing was off. I was teaching recently and the display on my laptop was fine, but the display that the class saw was weaving in a slow samba dance. A bit embarassing. Had to reboot to fix it. I now think the real culprit is kernel mode setting. I added a file /etc/modprobe.d/radeon.conf with the following line: options radeon modeset=0 Since I added this, I have not seen wiggling displays. It is back to being a bit more like my previous experiences: I frequently have to restart X if I want the monitor to be recognized at its highest resolution. However, at least the display itself works, and the machine is more stable than with KMS on. -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
I have now installed Lucid on a new hard drive, and with a bit more experience I can amplify this report a bit. It turns out that this largescreen monitor also fails even if the monitor is connected after the boot process, IF compositing is turned on. The only reliable way to get the monitor to work is to first turn desktop effects off. However, if I turn desktop effects off (in Kubuntu's SystemSettings-desktop) and then reboot with the monitor connected, this is not sufficient to fix the boot problem: I still get the wiggly lines on the kdm login screen (and thereafter). I wonder if specific problems during booting might have something to do with compositing being on at some point during the process, before my own configuration turns it off? I think the reason I didn't notice this extra twist when I was trying the live CD is that compositing must have been auto-disabled; I have noticed that happening frequently on its own. I now just turn off desktop effects all the time and wait to connect the monitor until after I have logged in. These steps appear to work around the problem. -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
** Tags added: regression-release ** Tags removed: regression-proposed -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
** Tags added: kubuntu -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
** Package changed: xorg (Ubuntu) = xserver-xorg-video-ati (Ubuntu) -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
** Changed in: xorg (Ubuntu) Status: New = Confirmed -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
apport information
** Tags added: apport-collected
** Description changed:
I have a Thinkpad T60. If I boot from the RC1 live CD, graphical
modesetting seems to work well if the external monitor is not connected
at boot time. If I then plug in the monitor, I can then switch to a new
resolution (1920x1080) from the old resolution (1400x1050). Switching
back and forth multiple times seems to work well, in the 10 minutes I've
been playing with the system.
However, if I boot with the monitor connected, then the resolution is
set to 1024x768 on both screens, and when I try to set the resolution to
something more useful, eventually the entire screen starts flickering
with weird horizontal lines on the laptop's monitor, and the external
monitor display wiggles around rapidly. The display is not usable under
such circumstances. External monitor: Dell S2409W
Apparent workaround: boot with monitor disconnected, and then after
logging in, connect the external monitor.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3084 F knotify4
ubuntu 3127 F kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 17'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,17aa2025,00100200'
Controls : 20
Simple ctrls : 11
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
79HT43WW-1.02'
Mixer name : 'ThinkPad EC 79HT43WW-1.02'
Components : ''
Controls : 2
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 14
Mono: Playback 14 [100%] [on]
Date: Sun Apr 25 22:11:40 2010
HotplugNewDevices:
HotplugNewMounts:
LiveMediaBuild: Kubuntu 10.04 Lucid Lynx - Release Candidate i386
(20100419.1)
MachineType: LENOVO 2623D7U
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/khostname.seed
boot=casper initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to
cancel.
dmi.bios.date: 04/18/2006
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ET60WW (1.05a)
dmi.board.name: 2623D7U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr79ET60WW(1.05a):bd04/18/2006:svnLENOVO:pn2623D7U:pvrThinkPadT60:rvnLENOVO:rn2623D7U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2623D7U
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
+ ---
+ Architecture: i386
+ DistroRelease: Ubuntu 10.04
+ DkmsStatus: Error: [Errno 2] No such file or directory
+ LiveMediaBuild: Kubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427)
+ MachineType: LENOVO 2623D7U
+ Package: xorg 1:7.5+5ubuntu1
+ PackageArchitecture: i386
+ PccardctlIdent:
+ Socket 0:
+no product info available
+ PccardctlStatus:
+ Socket 0:
+no card
+ ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/khostname.seed
boot=casper initrd=/casper/initrd.lz quiet splash --
+ ProcEnviron:
+ LANGUAGE=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
+ Tags: lucid lucid
+ Uname: Linux 2.6.32-21-generic i686
+ UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
+ dmi.bios.date: 04/18/2006
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 79ET60WW (1.05a)
+ dmi.board.name: 2623D7U
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Available
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias:
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in xorg. When reporting bugs in the future please use apport, either via the appropriate application's Help - Report a Problem menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu = xorg (Ubuntu) ** Tags removed: needs-upstream-testing resume suspend -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
Please execute the following command in a terminal after booting with the monitor plugged in: apport-collect 570011 This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to Change Non-Private data as it will be adding information to your bug report. Thanks in advance! ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570011] Re: Modesetting fails if large screen monitor attached at boot
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/45420554/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/45420555/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/45420556/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/45420557/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/45420558/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/45420559/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/45420560/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/45420561/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/45420562/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/45420563/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/45420564/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/45420565/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/45420566/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/45420567/ProcModules.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/45420568/RfKill.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/45420569/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/45420570/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/45420571/WifiSyslog.txt -- Modesetting fails if large screen monitor attached at boot https://bugs.launchpad.net/bugs/570011 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
