[Bug 558378] Re: lucid no longer boots after beta1 upgrades
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/43428774/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/43428775/AplayDevices.txt ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/43428776/ArecordDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/43428777/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/43428778/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.1.txt http://launchpadlibrarian.net/43428779/Card0.Codecs.codec.1.txt ** Attachment added: Card0.Codecs.codec.3.txt http://launchpadlibrarian.net/43428780/Card0.Codecs.codec.3.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/43428781/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43428782/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/43428783/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/43428784/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/43428785/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/43428786/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/43428787/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/43428788/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/43428789/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/43428790/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/43428791/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/43428792/WifiSyslog.txt -- lucid no longer boots after beta1 upgrades https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
** Attachment added: drm dmesg output not present in BootDmesg.txt http://launchpadlibrarian.net/43429945/dmesg_drm.txt -- lucid no longer boots after beta1 upgrades https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
@ Shaved Wookie: In a comment posted for bug #509273, you said: I get the third possibility (grub - blackscreen) with an Xpress 1250. Not sure how to try nonmodeset As we have the same graphic card and as you also experience black screen on boot, it would be great if could perform the following test: 1. Test lucid beta 1 with nomodeset option download lucid beta 1: http://cdimage.ubuntu.com/releases/10.04/beta-1/ nomodeset option: When you see the ubuntu menu proposing to Try Ubunutu wihtout installing, to install, check disk or cancel and boot from 1st hard drive, press F6 and check the option nomodeset. Then choose: Try Ubuntu report if it you experience a black screen on boot 2. Test lucid beta 2 with the exact same procedure If test 1 succeeds but test 2 fails, then this bug can be confirmed. -- lucid no longer boots after beta1 upgrades https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
** Description changed: - The laptop is a Samsung R20 equiped with ATI XPRESS 1250. + The laptop is a Samsung R20 equipped with ATI XPRESS 1250. Upgrade from karmic to lucid beta 1 succeeded and the system used to boot normally WITH nomodeset option. Using nomodeset, everything was working like a charm until I updated linux kernel and ati driver. Since then, the system won't boot, even with the option nomodeset. This bug report is sent from a beta1 live session. System fails to boot using daily-live produced after beta1 although the same boot parameters are used: nomodeset. + I just tested beta2 and it still fails. + + Here are some details of what happens: + 1. setting nomodeset option + 2. editing boot option, removing quiet and splash + 3. Selecting Try Ubuntu + 4. System begins to boot, lots of messages are printed on the screen + 5. After 2-3 seconds, screen goes black although disk activity continues + 6. Screen keeps being black and the computer is unusable I would be glad to help solve this bug by performing testing and giving as much information as needed. However, I will only be able to do these tests from live CD as I reinstalled karmic on my machine in order to have a working system. regards, ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 3992 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 3992 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: - Card hw:0 'SB'/'HDA ATI SB at 0xd000 irq 16' -Mixer name : 'Realtek ALC262' -Components : 'HDA:11c13026,2117144d,00100700 HDA:10ec0262,144dc511,0012' -Controls : 18 -Simple ctrls : 12 + Card hw:0 'SB'/'HDA ATI SB at 0xd000 irq 16' + Mixer name : 'Realtek ALC262' + Components : 'HDA:11c13026,2117144d,00100700 HDA:10ec0262,144dc511,0012' + Controls : 18 + Simple ctrls : 12 Date: Thu Apr 8 11:35:16 2010 DistroRelease: Ubuntu 10.04 LiveMediaBuild: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) MachineType: SAMSUNG ELECTRONICS CO., LTD. R19/R20/R21 Package: linux-image-2.6.32-16-generic 2.6.32-16.25 ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz nosplash -- nomodeset console-setup/layoutcode=fr console-setup/variantcode=oss ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Regression: Yes RelatedPackageVersions: linux-firmware 1.32 Reproducible: Yes RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux TestedUpstream: No Uname: Linux 2.6.32-16-generic x86_64 dmi.bios.date: 07/18/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 14SH dmi.board.name: R19/R20/R21 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr14SH:bd07/18/2007:svnSAMSUNGELECTRONICSCO.,LTD.:pnR19/R20/R21:pvr09SH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR19/R20/R21:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A: dmi.product.name: R19/R20/R21 dmi.product.version: 09SH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -- lucid no longer boots after beta1 upgrades https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
** Tags added: black-screen -- lucid no longer boots after beta1 upgrades https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
** Tags added: freeze modeset -- lucid no longer boots after beta1 upgrades https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
I actually managed to fix this issue on my machine by replacing nomodeset in the kernel line with radeon.modeset=0,so I'm not sure how much of a help it would be to you for me to test this... -- lucid no longer boots after beta1 upgrades https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
Shaved Wookie is right. Option nomodeset no longer works. Instead radeon.nomodeset must be used. Thank you. Changing description, title Marking bug #558641 as duplicate -- Please blacklist ATI XPRESS 1250 from Kernel mode-setting https://bugs.launchpad.net/bugs/558378 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 558378] Re: lucid no longer boots after beta1 upgrades
** Description changed: - The laptop is a Samsung R20 equipped with ATI XPRESS 1250. + Please add ati xpress 1250 to the kernel drm KMS blacklist. - Upgrade from karmic to lucid beta 1 succeeded and the system used to - boot normally WITH nomodeset option. Using nomodeset, everything was - working like a charm until I updated linux kernel and ati driver. Since - then, the system won't boot, even with the option nomodeset. + Testing has shown that KMS support for the ati xpress 1250 is + inadequate, often resulting in a regression where the system hangs + during boot up. Testers have found that booting with radeon.modeset=0 + restores the system functionality. This is why this particular video + card should be blacklisted. - This bug report is sent from a beta1 live session. - System fails to boot using daily-live produced after beta1 although the same boot parameters are used: nomodeset. - I just tested beta2 and it still fails. - + [initial bug report: symptoms of what happens when one tries to boot with kms enabled] Here are some details of what happens: - 1. setting nomodeset option - 2. editing boot option, removing quiet and splash - 3. Selecting Try Ubuntu - 4. System begins to boot, lots of messages are printed on the screen - 5. After 2-3 seconds, screen goes black although disk activity continues - 6. Screen keeps being black and the computer is unusable - - I would be glad to help solve this bug by performing testing and giving - as much information as needed. However, I will only be able to do these - tests from live CD as I reinstalled karmic on my machine in order to - have a working system. - - regards, + 1. setting nomodeset option + 2. editing boot option, removing quiet and splash + 3. Selecting Try Ubuntu + 4. System begins to boot, lots of messages are printed on the screen + 5. After 2-3 seconds, screen goes black although disk activity continues + 6. Screen keeps being black and the computer is unusable ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3992 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xd000 irq 16' Mixer name : 'Realtek ALC262' Components : 'HDA:11c13026,2117144d,00100700 HDA:10ec0262,144dc511,0012' Controls : 18 Simple ctrls : 12 Date: Thu Apr 8 11:35:16 2010 DistroRelease: Ubuntu 10.04 LiveMediaBuild: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) MachineType: SAMSUNG ELECTRONICS CO., LTD. R19/R20/R21 Package: linux-image-2.6.32-16-generic 2.6.32-16.25 ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz nosplash -- nomodeset console-setup/layoutcode=fr console-setup/variantcode=oss ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Regression: Yes RelatedPackageVersions: linux-firmware 1.32 Reproducible: Yes RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux TestedUpstream: No Uname: Linux 2.6.32-16-generic x86_64 dmi.bios.date: 07/18/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 14SH dmi.board.name: R19/R20/R21 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr14SH:bd07/18/2007:svnSAMSUNGELECTRONICSCO.,LTD.:pnR19/R20/R21:pvr09SH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR19/R20/R21:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A: dmi.product.name: R19/R20/R21 dmi.product.version: 09SH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Summary changed: - lucid no longer boots after beta1 upgrades + Please blacklist ATI XPRESS 1250 from Kernel mode-setting ** Changed in: linux (Ubuntu) Status: New = Confirmed ** Description changed: Please add ati xpress 1250 to the kernel drm KMS blacklist. Testing has shown that KMS support for the ati xpress 1250 is inadequate, often resulting in a regression where the system hangs during boot up. Testers have found that booting with radeon.modeset=0 restores the system functionality. This is why this particular video card should be blacklisted. + + As suggested by Brice Harrington in bug #542208, comment 17, it is + better to keep one report per chip. [initial bug report: symptoms of what happens when one tries to boot with kms enabled] Here are some details of what happens: 1. setting nomodeset option 2. editing boot option, removing quiet and splash 3. Selecting Try Ubuntu 4. System begins to boot, lots of messages are printed on the