[Bug 1448574] Re: Have to use nomodeset for install (new problem for new distro)
P1.70 04/21/2015 As I was saying before, this only happened since updating to 15.04 from 14.10. It has more to do with my television not specifying a resolution that is compatible with modeset. For example, it may say that it's 720p tops instead of 1280 x 720 but I'm not sure. I do know that it enjoys staying in a powered-on state while flipping the screen and its light on and off while making the power on and off sound when modeset doesn't work right. The television shows as a Samsung Electric Company 7" and is presently working at a resolution of 1360 x 768 and looks like crap at 1280 x 720. I'm not sure what has changed in the way that modeset functions, but this would be the second time this same issue has happened with this particular screen. Normally, I would say that it would be the screen at fault, but something in modeset was changed before that fixed the way it handled some of these screens that made it work perfectly. If someone could look at what changed that could make it have this problem, I would really appreciate it. Also, changed to confirmed as requested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448574 Title: Have to use nomodeset for install (new problem for new distro) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448574] Re: Have to use nomodeset for install (new problem for new distro)
** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448574 Title: Have to use nomodeset for install (new problem for new distro) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448574] [NEW] Have to use nomodeset for install (new problem for new distro)
Public bug reported: I haven't had this problem since around version 12.04 or before (can't recall which one precisely) where, during installation, I have to use nomodeset in order to get my Samsung television to stop turning on and off repeatedly during modeset problems. I would like to mention that my television doesn't support an automatic shutoff mode which would normally cause it to turn off in a powersave situation, so being able to do that would be considered a new feature to me (one maybe worth exploring later). However, this last distro of 15.04 seems to have brought back the old problems with modeset that were once fixed, brought back, fixed again, and now brought back once more. Unfortunately, I can't give a log of this error due to the nature of the problem causing no visuals and my system deleting any log files upon reboot of the live boot. So, all I can suggest is to look into what changed that would cause modeset to break like this and try to change it back or add-in the fix to the code that existed before, if possible. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 26 01:52:38 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3988] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- nomodeset Renderer: Software SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: X99 Professional dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd01/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Professional:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 26 01:33:12 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDELL Dell USB Wired Multimedia Keyboard KEYBOARD, id 8 inputDELL Dell USB Wired Multimedia Keyboard KEYBOARD, id 9 inputDELL DELL USB Laser Mouse MOUSE, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448574 Title: Have to use nomodeset for install (new problem for new distro) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
Relax, the bug is only sporadic and the slowdown on boot may be overcome with inode updates and defrags which may or may not occur automatically with the BTRFS file system. While it may happen with one system, it may not with another. While it may happen at one time with a system, it may not at another. It's based on how quickly boot occurs and whether or not lightdm loads before or after its dependencies which may or may not occur depending on how optimized the filesystem is as well as other factors. Using the computer will add, remove, and optimize files in the filesystem as time goes on. This scenario of having lightdm load properly was expected and is part of the bug in question. To simplify, lightdm is winning the race condition instead of losing. However, much like Global Thermonuclear War, the only way to truly win every time is not to play. Thus, the bug still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
I concur! Though, I think the problem is more-so that there is a race in the first place instead of a march which is what I'm hoping we can fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
Seven months have passed with no fix in place. I have removed the assigned user so that another may step-up in their place to resolve the issue. ** Changed in: lightdm (Ubuntu) Assignee: Dalmer Vieira (dalmer-vieira) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241929] Re: Lightdm Ubuntu 13.10 fails to start "intermittently" after cold boot or from shutdown/reboot.
*** This bug is a duplicate of bug 969489 *** https://bugs.launchpad.net/bugs/969489 ** This bug has been marked a duplicate of bug 969489 lightdm tries (and fails) to start too early? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241929 Title: Lightdm Ubuntu 13.10 fails to start "intermittently" after cold boot or from shutdown/reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1241929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
We need to apply a fix in the startup which performs a while statement to check if dependencies are not yet loaded. This will mitigate against problems with varying sleep times which may or may not work for users. Alternatively, having a list of dependencies to run inline may be a better option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241929] Re: Lightdm Ubuntu 13.10 fails to start "intermittently" after cold boot or from shutdown/reboot.
This bug is a duplicate of: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/969489 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410 This bug has not been resolved as of yet and has affected Ubuntu distributions ever since, at most, 12.10. Not sure before that. Though this problem hasn't been patched to check for dependencies to be loaded before lightdm, a workaround to add sleep 2 to the startup script has been mildly helpful to thwart the racing condition that occurs when this is loading. A while statement should be issued to determine if its dependencies are not loaded already and to pause until the while statement is no longer true. This will allow all users to not have to customize their wait time which might vary between boots and not work every time. Also, this bug affects my installation and hasn't been addressed in the past 3 revisions of Ubuntu. If someone would be so kind as to get this fixed for the next revision, it would be greatly appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241929 Title: Lightdm Ubuntu 13.10 fails to start "intermittently" after cold boot or from shutdown/reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1241929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059827] Re: Non trivial grub2 installs no longer fit in small embed areas
Sorry, I did get a little confused over the sectors thing. The 63rd LBA sector is the starting point for the 0MB boundary of partitions usually. I wasn't thinking straight. I'm used to using the MB settings for partitioning instead. Anyhow, the normal Grub2 install for any partition that's not BtrFS can fit into the MBR area with no problem normally. However, a larger area is required if you're going to use a BtrFS partition since the data on how to read such a partition in Grub2 makes the boot program a bit larger than the MBR size. Recall that I said Core.img is particularly large. I'll have to check on my installation to see where I had to start it at later. But it is a problem that should be addressed or at least warned about in the installation. As for the installation report, it should mention that Grub2 failed to install properly and should return to the partitioning step to address the issue. Highlighting the issue may also be beneficial to users. However, with newer hard drives, they utilize 4K sector sizes to increase capacity. This should be taken into account in case the 512b emulation ceases. It's known as Advanced Format and can be a pain in the rear if you're not already familiar with it. This will make 256 sectors equal to 1 MB instead. Anyhow, I'll be sure to check on how I've managed to install BtrFS and where my partitions start and end so that I can toss together a sort of guideline for failsafes. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to a duplicate bug report (1266195). https://bugs.launchpad.net/bugs/1059827 Title: Non trivial grub2 installs no longer fit in small embed areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1059827/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1059827] Re: Non trivial grub2 installs no longer fit in small embed areas
Sorry, I was talking about an MBR system, not a UEFI. Core.img is too large to fit into the first 64 sectors (starting from 0). And, so, the next best place to start would be the 127 - 128 boundary. Also known as the 2MB boundary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059827 Title: Non trivial grub2 installs no longer fit in small embed areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1059827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059827] Re: Non trivial grub2 installs no longer fit in small embed areas
Actually, Phillip, BtrFS requires 2MB for a Grub2 installation. So, while you are correct that it does start at 1MB, the partitioner does have an error in not including that the rules for BtrFS are different. The normal 1MB is a part of the normal MBR rules. Since Grub2 requires some extra installation space for the BtrFS partition information, GParted should warn when BtrFS is used and a partition is started less than 2MB from the beginning of the drive. For everything else, 1MB works fine. So, this would be a problem with the partitioner not realizing the rules are different and the installer not seeing that the partitioner made a mistake and that Grub2 can not be properly installed inside of the 1MB space for a BtrFS partition. Ext4 and other partitions that are not BtrFS have no problem with the 1MB start point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059827 Title: Non trivial grub2 installs no longer fit in small embed areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1059827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059827] Re: Non trivial grub2 installs no longer fit in small embed areas
There is no need to reformat with Ext4. If you wish to use BtrFS for the Boot partition, it's recommended. Just tell the partitioner to start at the 1MB boundary instead of the first sector. To reiterate, you need an empty 1MB at the beginning of your drive to write to. I would call this an error with the partitioner/Ubuntu Installer instead of Grub2. To do this properly, start GParted and format it using this method. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059827 Title: Non trivial grub2 installs no longer fit in small embed areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1059827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1128689] Re: Grub2 failed to install on /dev/sda during Ubuntu Installation
I've come to find that it's because Ubuntu doesn't include the files and work-around necessary to allow installation to btrfs filesystem. I recommend including a check/prompt to ensure that 1 MB exists at the beginning of the drive to allow the use of btrfs as the root file system as not having it results in an installation failure of Grub2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1128689 Title: Grub2 failed to install on /dev/sda during Ubuntu Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1128689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1128689] [NEW] Grub2 failed to install on /dev/sda during Ubuntu Installation
Public bug reported: All information pertaining to this error has been uploaded automatically. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubiquity 2.12.16 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 CasperVersion: 1.328 Date: Sun Feb 17 21:49:49 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) ProcEnviron: TERM=unknown PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal ubiquity-2.12.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1128689 Title: Grub2 failed to install on /dev/sda during Ubuntu Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1128689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024620] Re: Crash on Change User in Locked Screen
Well gdm it, if they repeated the process they would have exactly the info they need. It crashes on more than one system if you try to switch to guest while logged into another user and then back. It does it ever so often, so if it fails once, try it again. That should be enough info. Other than that, how do you suppose I retrieve a crash report from a system that won't boot properly after the crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024620 Title: Crash on Change User in Locked Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1024620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032900] Re: Display crash on user change
Eh, I'm not sure. But I'll go with it. ** Package changed: ubuntu => xserver-xorg-driver-ati -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032900 Title: Display crash on user change To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1032900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032900] [NEW] Display crash on user change
Public bug reported: After being logged in as a user, if another user decides to attempt to change user as guest instead of entering a password, the display will sometimes go black and fail to respond resulting in no signal to the monitor. The only known way of fixing the problem is by restarting the computer. If another display driver such as the ATI driver is used, this error results in the inability to start X and crashes upon entering the startx command. I believe that this error is the result of attempting to reset display parameters prior to bringing the display adapter back online on user change. The result would be issuing commands to an interface which was not yet available to receive commands. Ubuntu Version: 12.04 with proposed updates enabled The error can be recreated, but I can not seem to generate a program crash report to submit here. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032900 Title: Display crash on user change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1032900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024620] [NEW] Crash on Change User in Locked Screen
Public bug reported: GDM has crashed on me twice using the same system. The first time, my sister had changed the user while my screen had locked itself to utilize the guest account due to her not knowing my password. It crashed once I logged out of the guest account and I couldn't get startx to work at all upon reboot. The entire system would only boot into a terminal after that. I could not fix the system via recovery options either so no packages were damaged. And so, I reinstalled Ubuntu completely. The second time, I was simply using the lock screen to change users again. Upon clicking the change user button on the screen lock window, the system crashed entirely except for a small bar in the top-left corner. I could not reach the terminal from here meaning the entire system had crashed. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm (not installed) ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jul 13 23:57:10 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024620 Title: Crash on Change User in Locked Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1024620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573202/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573212/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573211/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573210/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573209/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] PulseSources.txt
apport information ** Attachment added: "PulseSources.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573208/+files/PulseSources.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] PulseSinks.txt
apport information ** Attachment added: "PulseSinks.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573207/+files/PulseSinks.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573206/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573205/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573204/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573203/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573201/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573200/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573199/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Card1.Codecs.codec.0.txt
apport information ** Attachment added: "Card1.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573198/+files/Card1.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573197/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573196/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573194/+files/ArecordDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573195/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573193/+files/AplayDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573192/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Re: Modeset code fixed with update in 10.10 regressed in 11.04
apport information ** Tags added: oneiric ** Description changed: This problem was fixed in 10.10 with an update. While not using nomodeset, sometime incorrect commands would be sent to the display causing errors such as entering low-power mode, flickering or simply going blank. In particular, my Samsung television enters a standby mode that is otherwise inaccessible by the consumer. It turns on and off repeatedly as a result of a command being sent by the display driver. Honestly, I didn't know it was possible, but you may want to look at the fix for 10.10 as the solution for 11.04 and maybe exploit this error to gain a little more functionality of HDMI televisions. I consider this bug a security vulnerability because it causes otherwise inaccessible functions of the display hardware to become accessible at the hardware level. --- Architecture: amd64 DistUpgraded: Fresh install DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Package: xorg 1:7.6+4ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Tags: natty ubuntu Uname: Linux 2.6.38-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. + ApportVersion: 1.23-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: d337z 1651 F pulseaudio + /dev/snd/controlC0: d337z 1651 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'Intel'/'HDA Intel at 0xfe7f8000 irq 46' +Mixer name : 'Analog Devices AD1988B' +Components : 'HDA:11d4198b,1043829b,00100300' +Controls : 48 +Simple ctrls : 26 + Card1.Amixer.info: + Card hw:1 'Generic'/'HD-Audio Generic at 0xfe8fc000 irq 47' +Mixer name : 'ATI R6xx HDMI' +Components : 'HDA:1002aa01,00aa0100,00100200' +Controls : 4 +Simple ctrls : 1 + Card1.Amixer.values: + Simple mixer control 'IEC958',0 +Capabilities: pswitch pswitch-joined penum +Playback channels: Mono +Mono: Playback [on] + CheckboxSubmission: 9d5cca6869ed5236252dad950b7a787d + CheckboxSystem: edda5d4f616ca792bf437989cb597002 + DistroRelease: Ubuntu 11.10 + MachineType: System manufacturer P5K Deluxe + NonfreeKernelModules: fglrx + Package: linux (not installed) + ProcEnviron: + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=B03631E63631ADEA loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 + RelatedPackageVersions: + linux-restricted-modules-3.0.0-12-generic N/A + linux-backports-modules-3.0.0-12-generic N/A + linux-firmware1.60 + Tags: oneiric + Uname: Linux 3.0.0-12-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 12/16/2008 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1005 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: P5K Deluxe + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd12/16/2008:svnSystemmanufacturer:pnP5KDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: P5K Deluxe + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AcpiTables.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2573191/+files/AcpiTables.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about
[Bug 754284] Re: Modeset code fixed with update in 10.10 regressed in 11.04
Problem still exists. ** Changed in: linux (Ubuntu) Status: Expired => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
Oops, forgot to attach... ** Attachment added: "The results of utilizing mdadm" https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/666577/+attachment/2098780/+files/mdadm%20results.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
As you wish. Attached are the files Examine, Detail and even Detail- Platform so you know specifically what I'm working with. Unfortunately, since my main RAID 5 array became corrupted, I decided it was time to consolidate both arrays into one so I won't be able to verify any fix of the code that may come about. You may be delighted to know that it is verified that dmraid does work with arrays not sharing drives with other arrays as it recognizes my single RAID 5 array flawlessly. So the bug is recognizing multiple arrays on shared drives. You also might be happy to hear that mdadm has difficulty with array names containing spaces. So that's a plus for dmraid. Also, the array shows in Disk Utility as inactive under Ubuntu (Live CD) but active under Fedora so there's that compatibility problem as well. But there you have it. One thing that has me twitching about my output here is the Detail- Platform file where it states that the Max Disks is 6. I wonder, if someone were to utilize a SATA port multiplier, if it would register a higher maximum or if it would assume that the # of on-board ports = # of Max Disks? That's something to test when I get the time and money to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Re: Modeset code fixed with update in 10.10 regressed in 11.04
So it hasn't been fixed and it still allows issuing of low-level commands to monitors which can eventually render them inoperable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Re: Modeset code fixed with update in 10.10 regressed in 11.04
apport information ** Tags added: apport-collected natty ubuntu ** Description changed: This problem was fixed in 10.10 with an update. While not using nomodeset, sometime incorrect commands would be sent to the display causing errors such as entering low-power mode, flickering or simply going blank. In particular, my Samsung television enters a standby mode that is otherwise inaccessible by the consumer. It turns on and off repeatedly as a result of a command being sent by the display driver. Honestly, I didn't know it was possible, but you may want to look at the fix for 10.10 as the solution for 11.04 and maybe exploit this error to gain a little more functionality of HDMI televisions. I consider this bug a security vulnerability because it causes otherwise inaccessible functions of the display hardware to become accessible at the hardware level. + --- + Architecture: amd64 + DistUpgraded: Fresh install + DistroCodename: natty + DistroRelease: Ubuntu 11.04 + DistroVariant: ubuntu + LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) + Package: xorg 1:7.6+4ubuntu3 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US:en + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 + Tags: natty ubuntu + Uname: Linux 2.6.38-8-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.23-1ubuntu6 + version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 + version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/754284/+attachment/2098657/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
Honestly, I don't know why or how it worked, but it did. I used the --examine --scan to see if it would even recognize the array. Once I realized it recognized it, I told it to scan and run the array. It told me there were no super blocks, but it loaded it right up and I was able to mount my array for use in the disk manager. Unfortunately, I was forced to use this method to actually recover my data from my degraded (and corrupted) RAID 5 array after my bios decided it didn't want to recognize it as existing anymore. But yeah, apparently mdadm can recognize and run degraded fakeraid Level 5 arrays as well. So, the answer to your question is no; I didn't have it create the array, I had it take the two working drives from my 3 drive array and run the arrays it found on them. We might look at this as a viable solution if it continues to work right. Would you like a screenshot or a verbose log of the examine results produced by mdadm as verification? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
I've done some investigating on my second array by poking around with mdadm. It seems that there was a slight offset with the partition allignment that COULD have been the problem. It was offset by 33280 bytes. mdadm seems to allow me to access both of the arrays correctly though. So I can't figure out what's different between the two programs' methods of access that causes one to work flawlessly in accessing both arrays and the other to completely fail to load either. So I have determined that the Linux kernel IS capable of reading the arrays. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737159] Re: dmraid-activate uses flawed logic to detect degraded condition
I believe the problem we're going to have with fixing this is determining how many disks were in the array to begin with. It requires reading specific data from the arrays descriptors and matching it to the drives listed. I would also recommend getting sector specific on the fix so that drives sharing multiple arrays won't bug when an already counted drive is counted again for another array. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737159 Title: dmraid-activate uses flawed logic to detect degraded condition -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762064] Re: Fake RAID partitions isn't accessible, because dmraid package is missing on installed Ubuntu 11.04 beta2 system, but LiveCD can use fakeraid, please don't remove dmraid package from /
Have you attempted to reinstall dmraid to verify that it is not present in the package or try running dmraid from the terminal? I'm having a similar issue, but mine is with dmraid installed and not recognizing my array right off the liveCD then freezing when it doesn't know how to handle it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762064 Title: Fake RAID partitions isn't accessible, because dmraid package is missing on installed Ubuntu 11.04 beta2 system, but LiveCD can use fakeraid, please don't remove dmraid package from /casper/filesystem .manifest-desktop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
dm-raid45 doesn't work correctly in 11.04 with the default module. It will not load my RAID arrays. I believe it may have difficulty distinguishing between the two RAID 5 arrays which both share 3 drives. As for the one I attempted to compile, that was back in 10.10 when the module still didn't work and I thought I might be able to rework some of the code to correct it. Before reworking, dmraid4-5 was giving me all sorts of compilation errors. I have not since tried to recompile dmraid. This error goes back to the late version 9.xx Ubuntu and hasn't been resolved since. On a slightly related note, Mr. Wood, I've noticed that many of the problems previously resolved in updates to 10.10 have returned in 11.04 which indicates to me that some modules here and there have, in fact, been reverted. So raid456 may very well be in the kernel, but, as you've stated, it isn't being used. I've also mentioned another error involving display hardware that could be taken advantage of as a security risk, but someone marked it as not important and not a risk. So I don't know what to think about some of the module issues at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
This bug also affects Ubuntu 11.04 currently in Beta production. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754274] Re: dmraid fails to start when 3 drives share 2 RAID-5 arrays
I would love to add it to the other bug and I tried, but I can't seem to find any setting that says "Also affects 11.04". So I had little choice but to create this new bug report for 11.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754274 Title: dmraid fails to start when 3 drives share 2 RAID-5 arrays -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Re: Modeset code fixed with update in 10.10 regressed in 11.04
Excuse me, but why have you changed the security vulnerability status to no when this bug allows direct, unauthorized access to the internal hardware settings of the monitor enough to literally power it on and off with commands through HDMI? Direct hardware access by anyone but the administrator should be considered a security concern by anyone's book. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754284] Re: Modeset code fixed with update in 10.10 regressed in 11.04
Sure, I'll give you the steps from both installed and CD-based. CD: Step 1: Turn on computer Step 2: Insert Ubuntu Live CD or DVD Step 3: Wait for menu Step 4: Press enter to use Live CD or DVD based Ubuntu Step 5: Observe as your screen goes blank, flickers or begins turning on and off depending on hardware. Installed: Step 1: Turn on computer Step 2: Select your Ubuntu installation Step 3: Observe as your screen goes blank, flickers or begins turning on and off depending on hardware. The issue I'm having is that the issue that was fixed in 10.10 with an update has been regressed in 11.04 so that incorrect commands are being sent to the display hardware and having different effects other than originally intended based upon what display hardware is being used. In particular, I'm using a Samsung Television connected through HDMI and it turns on and off repeatedly when nomodeset is not used whereas, while it did this with the original unmodified 10.10 installation as well, it was later fixed with an update. I don't know why the patch was regressed, but it needs to be added once again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/754284 Title: Modeset code fixed with update in 10.10 regressed in 11.04 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754274] Re: dmraid fails to start when 3 drives share 2 RAID-5 arrays
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754274 Title: dmraid fails to start when 3 drives share 2 RAID-5 arrays -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754274] [NEW] dmraid fails to start when 3 drives share 2 RAID-5 arrays
Public bug reported: Binary package hint: dmraid dmraid absolutely refuses to work at start when I have 3 hard drives sharing 2 RAID-5 arrays on my Intel ICH9R chipset. This error also occurs in 10.10 and 10.04. Phillip Susi had been working with me on this problem, but we haven't come to a solution in the programming as of yet. It is believed that the error exists in the RAID45 source module, but my programming is less that adequate to fix it. Original bug #666577 Displays as 3 partitions instead of 2 drives. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: dmraid 1.0.0.rc16-4.1ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 Date: Fri Apr 8 04:06:08 2011 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Beta 1 amd64 (20110329.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dmraid UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754274 Title: dmraid fails to start when 3 drives share 2 RAID-5 arrays -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
What I was attempting to compile above was the Ubuntu kernel from the sources provided by Synaptic. Once it hit the experimental Ubuntu dm- raid4-5 driver you mentioned, it errored very specifically on the dm- region-hash.c file. Looking at the compilation output, it seems that most, if not all of, the variables in the source were uninitialized or undefined prior to use. I don't know if it was the case, but I tried taking a look at the code myself to see if I could fix it by initializing the values with typeref or something, however I only really know bash and bat coding so it went horribly wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
What I'm trying to get at is that I'm pretty certain that the source of the leak is in the ubuntu patches. Specifically, ../ubuntu/dm-raid4-5/dm-region-hash.c Mr. Susi, if you could please take a look at my compilation output from above and see if that helps track the error, I would appreciate it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid hangs trying to start ICH9R RAID 5
Consider yourself verified. Also, see my previous comment about my attempt at recompiling my kernel and how it failed at the ../ubuntu/dm- raid4-5/dm-region-hash.c file. It's comment #5 to be exact. Dec 30 03:05:11 ubuntu kernel: [ 22.205128] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj. Dec 30 03:05:03 ubuntu kernel: [ 23.474918] hda-intel: IRQ timing workaround is activated for card #2. Suggest a bigger bdl_pos_adj. Dec 30 03:05:12 ubuntu kernel: [ 31.860004] eth0: no IPv6 routers present Dec 30 03:06:28 ubuntu kernel: [ 107.804182] device-mapper: table: 252:0: raid45: Invalid RAID device offset parameter Dec 30 03:06:28 ubuntu kernel: [ 107.804185] device-mapper: ioctl: error adding target to table Dec 30 03:09:03 ubuntu kernel: [ 263.086864] SysRq : Show Blocked State Dec 30 03:09:03 ubuntu kernel: [ 263.086868] taskPC stack pid father Dec 30 03:09:03 ubuntu kernel: [ 263.086900] dmraidD f192 0 3362 2816 0x Dec 30 03:09:03 ubuntu kernel: [ 263.086905] 880087935ce8 0086 8801 00015980 Dec 30 03:09:03 ubuntu kernel: [ 263.086909] 880087935fd8 00015980 880087935fd8 880078838000 Dec 30 03:09:03 ubuntu kernel: [ 263.086913] 00015980 00015980 880087935fd8 00015980 Dec 30 03:09:03 ubuntu kernel: [ 263.086917] Call Trace: Dec 30 03:09:03 ubuntu kernel: [ 263.086924] [] schedule_timeout+0x195/0x310 Dec 30 03:09:03 ubuntu kernel: [ 263.086929] [] ? process_timeout+0x0/0x10 Dec 30 03:09:03 ubuntu kernel: [ 263.086933] [] schedule_timeout_uninterruptible+0x1e/0x20 Dec 30 03:09:03 ubuntu kernel: [ 263.086936] [] msleep+0x20/0x30 Dec 30 03:09:03 ubuntu kernel: [ 263.086940] [] __dm_destroy+0x9a/0x150 Dec 30 03:09:03 ubuntu kernel: [ 263.086943] [] dm_destroy+0x13/0x20 Dec 30 03:09:03 ubuntu kernel: [ 263.086946] [] dev_remove+0x90/0x110 Dec 30 03:09:03 ubuntu kernel: [ 263.086950] [] ? dev_remove+0x0/0x110 Dec 30 03:09:03 ubuntu kernel: [ 263.086953] [] ctl_ioctl+0x1a5/0x250 Dec 30 03:09:03 ubuntu kernel: [ 263.086956] [] dm_ctl_ioctl+0x13/0x20 Dec 30 03:09:03 ubuntu kernel: [ 263.086960] [] vfs_ioctl+0x3d/0xd0 Dec 30 03:09:03 ubuntu kernel: [ 263.086963] [] do_vfs_ioctl+0x81/0x340 Dec 30 03:09:03 ubuntu kernel: [ 263.086967] [] ? do_page_fault+0x15e/0x350 Dec 30 03:09:03 ubuntu kernel: [ 263.086970] [] sys_ioctl+0x81/0xa0 Dec 30 03:09:03 ubuntu kernel: [ 263.086974] [] system_call_fastpath+0x16/0x1b Dec 30 03:09:03 ubuntu kernel: [ 263.086978] Sched Debug Version: v0.09, 2.6.35-24-generic #42-Ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid hangs trying to start ICH9R RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid fails on start with ICH9R under RAID 5
As requested sir, here is your metadata. ** Attachment added: "Metadata of RAID 2 (Darkness)" https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/666577/+attachment/1773416/+files/metadata.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid fails on start with ICH9R under RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid fails on start with ICH9R under RAID 5
Actually, I don't have the array itself divided into two volumes, I have the three drives divided into two raid 5 arrays. Darkness doesn't get used as much as it used to be my XP partition. However, I found that I used my Vista and, later, Win 7 more often so I removed XP and left it as a partition for backups. But I can understand how it would have difficulty with the two raid 5 arrays sharing the three drives. The reason I thought it was the metadata was because of some similar issues with Fedora. I've decided to try mdadm to see if it reads them correctly or not. Once dmraid can handle my dual raid arrays, I'll switch back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid fails on start with ICH9R under RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid fails on start with ICH9R under RAID 5
I've found the problem and a work-around. dmraid is incapable of handling metadata which is written into RAID arrays by Intel's Matrix program. dmraid errors on the metadata and crashes. If someone would be so kind as to code something into dmraid to either ignore or utilize the metadata, it would correct the problem many people are having and allow the raid arrays to be utilized. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid fails on start with ICH9R under RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid fails on start with ICH9R under RAID 5
I'm guessing nobody's going to be working on this anytime soon. For some reason, it's still having trouble identifying my isw drive. I think we might need to go about a different means of identifying and adapting to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666577 Title: dmraid fails on start with ICH9R under RAID 5 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666577] Re: dmraid fails on start with ICH9R under RAID 5
I'm compiling it using the source from synaptic. But this bug isn't about compilation errors; it's about the startup error. I only put the compilation error there as a point of reference should the source need to be looked at. -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 666577] Re: dmraid fails on start with ICH9R under RAID 5
Here is the output of dmraid from my terminal: er...@ubuntu:~$ sudo dmraid -ay - - WARN: locking /var/lock/dmraid/.lock NOTICE: /dev/sde: asr discovering NOTICE: /dev/sde: ddf1discovering NOTICE: /dev/sde: hpt37x discovering NOTICE: /dev/sde: hpt45x discovering NOTICE: /dev/sde: isw discovering DEBUG: not isw at 1000204884992 DEBUG: isw trying hard coded -2115 offset. DEBUG: not isw at 1000203803136 NOTICE: /dev/sde: jmicron discovering NOTICE: /dev/sde: lsi discovering NOTICE: /dev/sde: nvidia discovering NOTICE: /dev/sde: pdc discovering NOTICE: /dev/sde: sil discovering NOTICE: /dev/sde: via discovering NOTICE: /dev/sdd: asr discovering NOTICE: /dev/sdd: ddf1discovering NOTICE: /dev/sdd: hpt37x discovering NOTICE: /dev/sdd: hpt45x discovering NOTICE: /dev/sdd: isw discovering DEBUG: not isw at 1000204884992 DEBUG: isw trying hard coded -2115 offset. DEBUG: not isw at 1000203803136 NOTICE: /dev/sdd: jmicron discovering NOTICE: /dev/sdd: lsi discovering NOTICE: /dev/sdd: nvidia discovering NOTICE: /dev/sdd: pdc discovering NOTICE: /dev/sdd: sil discovering NOTICE: /dev/sdd: via discovering NOTICE: /dev/sdc: asr discovering NOTICE: /dev/sdc: ddf1discovering NOTICE: /dev/sdc: hpt37x discovering NOTICE: /dev/sdc: hpt45x discovering NOTICE: /dev/sdc: isw discovering DEBUG: isw metadata found at 320072932352 from probe at 320072932352 NOTICE: /dev/sdc: isw metadata discovered NOTICE: /dev/sdc: jmicron discovering NOTICE: /dev/sdc: lsi discovering NOTICE: /dev/sdc: nvidia discovering NOTICE: /dev/sdc: pdc discovering NOTICE: /dev/sdc: sil discovering NOTICE: /dev/sdc: via discovering NOTICE: /dev/sdb: asr discovering NOTICE: /dev/sdb: ddf1discovering NOTICE: /dev/sdb: hpt37x discovering NOTICE: /dev/sdb: hpt45x discovering NOTICE: /dev/sdb: isw discovering DEBUG: isw metadata found at 320072932352 from probe at 320072932352 NOTICE: /dev/sdb: isw metadata discovered NOTICE: /dev/sdb: jmicron discovering NOTICE: /dev/sdb: lsi discovering NOTICE: /dev/sdb: nvidia discovering NOTICE: /dev/sdb: pdc discovering NOTICE: /dev/sdb: sil discovering NOTICE: /dev/sdb: via discovering NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering DEBUG: isw metadata found at 320072932352 from probe at 320072932352 NOTICE: /dev/sda: isw metadata discovered NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering DEBUG: _find_set: searching isw_cjgjfegeba DEBUG: _find_set: not found isw_cjgjfegeba DEBUG: _find_set: searching isw_cjgjfegeba_Light DEBUG: _find_set: searching isw_cjgjfegeba_Light DEBUG: _find_set: not found isw_cjgjfegeba_Light DEBUG: _find_set: not found isw_cjgjfegeba_Light DEBUG: _find_set: searching isw_cjgjfegeba_Darkness DEBUG: _find_set: searching isw_cjgjfegeba_Darkness DEBUG: _find_set: searching isw_cjgjfegeba_Darkness DEBUG: _find_set: not found isw_cjgjfegeba_Darkness DEBUG: _find_set: not found isw_cjgjfegeba_Darkness DEBUG: _find_set: not found isw_cjgjfegeba_Darkness NOTICE: added /dev/sdc to RAID set "isw_cjgjfegeba" DEBUG: _find_set: searching isw_cjgjfegeba DEBUG: _find_set: found isw_cjgjfegeba DEBUG: _find_set: searching isw_cjgjfegeba_Light DEBUG: _find_set: searching isw_cjgjfegeba_Light DEBUG: _find_set: found isw_cjgjfegeba_Light DEBUG: _find_set: found isw_cjgjfegeba_Light DEBUG: _find_set: searching isw_cjgjfegeba_Darkness DEBUG: _find_set: searching isw_cjgjfegeba_Darkness DEBUG: _find_set: found isw_cjgjfegeba_Darkness DEBUG: _find_set: found isw_cjgjfegeba_Darkness NOTICE: added /dev/sdb to RAID set "isw_cjgjfegeba" DEBUG: _find_set: searching isw_cjgjfegeba DEBUG: _find_set: found isw_cjgjfegeba DEBUG: _find_set: searching isw_cjgjfegeba_Light DEBUG: _find_set: searching isw_cjgjfegeba_Light DEBUG: _find_set: found isw_cjgjfegeba_Light DEBUG: _find_set: found isw_cjgjfegeba_Light DEBUG: _find_set: searching isw_cjgjfegeba_Darkness DEBUG: _find_set: searching isw_cjgjfegeba_Darkness DEBUG: _find_set: found isw_cjgjfegeba_Darkness DEBUG: _find_set: found isw_cjgjfegeba_Darkness NOTICE: added /dev/sda to RAID set "isw_cjgjfegeba" DEBUG: set status of set "isw_cjgjfegeba_Darkness" to 16 DEBUG: set status of set "isw_cjgjfegeba_Light" to 16 Attached is the -rD information as well. ** Attachment added: "dmraid -rD" https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/666577/+attachment/1727621/+files/dmraid.isw.tar.lzma -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@l
[Bug 666577] Re: dmraid fails on start with ICH9R under RAID 5
Did you recompile or use a non-standard kernel than what came with Ubuntu? -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 666577] Re: dmraid fails on start with ICH9R under RAID 5
Well, I finished (sort of) and it wasn't pretty to say the least. Basically, it needs to have a few punctuations moved and needs to have the code refined quite a bit. There's also a problem with incompatible types in one of the declared variables. If someone that knows what they're doing would fix this for me, I would appreciate it. -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 666577] Re: dmraid fails on start with ICH9R under RAID 5
Okay, I'm going over the code now. I'm a novice so I might be wrong here. But, I've changed uint32_t to unsigned long int and I've added a LOT of semi-colons to void and struct statements. I think a number of structs could have been changed to typeref, but I'm not a programmer. If someone would go over this and double check for me, I would really appreciate it. I'll upload my changed dm-region-hash.c file later when I finish. -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 666577] Re: dmraid fails on start with ICH9R under RAID 5
Okay everyone, it goes deeper! I tried recompiling the Linux kernel to incorporate a few changes and to see if I could get dmraid to work correctly. The following is my result: ubuntu/built-in.o: In function `dm_rh_dec': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:527: multiple definition of `dm_rh_dec' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:535: first defined here ubuntu/built-in.o: In function `dm_rh_delay': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:673: multiple definition of `dm_rh_delay' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:687: first defined here ubuntu/built-in.o: In function `dm_rh_recovery_in_flight': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:661: multiple definition of `dm_rh_recovery_in_flight' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:675: first defined here ubuntu/built-in.o: In function `dm_rh_update_states': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:431: multiple definition of `dm_rh_update_states' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:437: first defined here ubuntu/built-in.o: In function `dm_rh_start_recovery': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:707: multiple definition of `dm_rh_start_recovery' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:708: first defined here ubuntu/built-in.o: In function `dm_rh_mark_nosync': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:393: multiple definition of `dm_rh_mark_nosync' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:395: first defined here ubuntu/built-in.o: In function `dm_region_hash_destroy': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:230: multiple definition of `dm_region_hash_destroy' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:235: first defined here ubuntu/built-in.o: In function `dm_rh_region_to_sector': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:118: multiple definition of `dm_rh_region_to_sector' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:122: first defined here ubuntu/built-in.o: In function `dm_rh_dirty_log': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:255: multiple definition of `dm_rh_dirty_log' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:260: first defined here ubuntu/built-in.o: In function `dm_rh_stop_recovery': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:697: multiple definition of `dm_rh_stop_recovery' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:698: first defined here ubuntu/built-in.o: In function `dm_rh_bio_to_region': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:124: multiple definition of `dm_rh_bio_to_region' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:128: first defined here ubuntu/built-in.o: In function `dm_rh_recovery_prepare': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:604: multiple definition of `dm_rh_recovery_prepare' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:619: first defined here ubuntu/built-in.o: In function `dm_rh_recovery_start': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:627: multiple definition of `dm_rh_recovery_start' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:642: first defined here ubuntu/built-in.o: In function `dm_rh_flush': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:667: multiple definition of `dm_rh_flush' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:681: first defined here ubuntu/built-in.o: In function `dm_rh_region_context': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:130: multiple definition of `dm_rh_region_context' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:134: first defined here ubuntu/built-in.o: In function `dm_region_hash_create': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:163: multiple definition of `dm_region_hash_create' drivers/built-in.o:/home/erick/Desktop/linux-source-2.6.35/drivers/md/dm-region-hash.c:167: first defined here ubuntu/built-in.o: In function `dm_rh_get_region_key': /home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:136: multiple definition of `dm_rh_get_reg
[Bug 666577] Re: dmraid fails on start with ICH9R under RAID 5
Update to messages: When I try to run ubuntu without the nodmraid option and quiet enabled, I receive a message "device-mapper: table 252:5: raid45: Invalid RAID device offset parameter". Something tells me that the problem isn't so much in dmraid itself as much as the RAID45 module. -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 666577] Re: dmraid fails on start with ICH9R under RAID 5
I mean that it failed to mount my raid arrays. Using sudo dmraid -ay only causes it to set there on the terminal with a blinking cursor doing nothing. I can type in it like it's waiting for something, but it's to no avail. As for ls /dev/mapper, it only shows the file control. -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 666577] Re: dmraid fails on start with ICH9R under RAID 5
-- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 666577] [NEW] dmraid fails on start with ICH9R under RAID 5
Public bug reported: Binary package hint: dmraid Description:Ubuntu 10.10 Release:10.10 PKG Version: 1.0.0.rc16-3ubuntu2 Expected: Raid to be recognized as RAID 5 array and the 3 partitions to be available for access by Ubuntu. Happened: udev-work[122]: inotify_add_watch(6, /dev/dm-4, 10) failed: no such file or directory Failed to mount my RAID 5 array created on Intel ICH9R chipset with 3 partitions on 3 drive RAID and 2 non-RAID drives with single partitions. Failed to verify packages for installation and installation stalled without using nodmraid option in GRUB2 and installing to non-raid drive. This bug is present in 10.04 as well. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: dmraid 1.0.0.rc16-3ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Date: Mon Oct 25 19:58:15 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: dmraid ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- dmraid fails on start with ICH9R under RAID 5 https://bugs.launchpad.net/bugs/666577 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 382559] Re: acpid
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27382160/Dependencies.txt ** Attachment added: "DpkgTerminalLog.txt" http://launchpadlibrarian.net/27382161/DpkgTerminalLog.txt -- acpid https://bugs.launchpad.net/bugs/382559 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 382559] [NEW] acpid
Public bug reported: Binary package hint: acpid Sadly, it affects Ubuntu-Desktop and Acpi capability ProblemType: Package Architecture: amd64 DistroRelease: Ubuntu 9.04 ErrorMessage: subprocess post-installation script returned error exit status 1 Package: acpid 1.0.6-9ubuntu4.9.04.3 SourcePackage: acpid Title: package acpid 1.0.6-9ubuntu4.9.04.3 failed to install/upgrade: subprocess post-installation script returned error exit status 1 Uname: Linux 2.6.28.9 x86_64 ** Affects: acpid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package -- acpid https://bugs.launchpad.net/bugs/382559 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 78081] Re: valgrind crashes on memcheck for a given program
Yeah, what they said...Ran it with Alleyoop to find memory leaks in liquidwar (25 of them by the way) and it crashed. ** Attachment added: "Valgrind crash involving memcheck" http://librarian.launchpad.net/6440738/_usr_lib_valgrind_x86-linux_memcheck.1000.crash -- valgrind crashes on memcheck for a given program https://launchpad.net/bugs/78081 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68349] Re: chromium crash during gaming
Ditto here, was blowing myself up on level 6, picked up the goodies left behind and "Poof!" ** Attachment added: "Poof! Screen went bye-bye." http://librarian.launchpad.net/6414959/_usr_games_chromium.1000.crash -- chromium crash during gaming https://launchpad.net/bugs/68349 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
