[Bug 1248211] Re: After upgrade from 13.04 to 13.10 no auto mount, unable to shutdown/reboot from menu, empty network list, etc ...
This affects me too in exactly the same way. Based on my digging, there are more than a few people experiencing this particular combination of issues after the 13.10 upgrade (NM issues, User Account management unlock is greyed out, drive mounting/unmounting issues, shutdown/reboot issues). I've seen it suggested this may actually be a policykit issue, since these are all things that require elevated permissions and only occurs in the GUI. This particular system I'm on may have been upgraded more than once, but I'm not sure since I don't recall whether I did a clean install of 13.04 or upgraded from 12.10 (and more). So, it may be something that doesn't present unless you've gone through multiple chained upgrades. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248211 Title: After upgrade from 13.04 to 13.10 no auto mount, unable to shutdown/reboot from menu, empty network list, etc ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1248211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222718] Re: Using fglrx, chromium tabs not displaying titles
This issue isn't isolated to fglrx. See #16 and #18. # ubuntu-drivers list virtualbox-guest-dkms ** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1222718/+attachment/3889849/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222718 Title: Using fglrx, chromium tabs not displaying titles To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1222718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994926] Re: empathy accounts not stored
I believe this is a problem with AppArmor in 12.04. I've been using
this same setup for a while now, so I don't think it affects previous
versions.
In /etc/apparmor.d/tunables/home, HOME is rigidly defined as /home/.
I put home in /u01/home, it meant that the apparmor profile for
Telepathy was broken.
It looks like the original reporter has a home directory of
/home/JOHNNYPARK/mhouse, which is similar to my case.
This means that the apparmor profile in /etc/apparmor.d/usr.lib.telepathy:
/usr/lib/telepathy/mission-control-5 {
...
owner @{HOME}/.mission-control/ rw,
owner @{HOME}/.mission-control/**rw,
...
}
Won't cover home directories that don't fit the pattern of
/home/username
As a workaround for my case, I changed the HOMEDIRS definition to
@{HOMEDIRS}=/home/ /u01/home/ in /etc/apparmor.d/tunables/home.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994926
Title:
empathy accounts not stored
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/994926/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994926] Re: empathy accounts not stored
Unfortunately, being able to relocate home directories is very typical on *nix systems from my experience. The best possible case would be to somehow search /etc/passwd for home directories and only allow it to run out of those on a per-user basis. This isn't necessarily relevant to Empathy or Telepathy, rather a Ubuntu/apparmor design issue. After even further digging, it appears that instead of editing /etc/apparmor.d/tunables/home as I did, the correct way of handling this is to run sudo dpkg-reconfigure apparmor which will prompt you for additional home directory locations. Those get added to /etc/apparmor.d/tunables/home.d/ubuntu (which says it's automatically generated and therefore shouldn't be edited directly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994926 Title: empathy accounts not stored To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/994926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325346] Re: dump cannot dump ext4 partitions
Dump *will* now make dumps of an ext4 without complaining using dump v0.4b41-6 (Jaunty) Unfortunately, restoring the data shows that it's been corrupted somewhere in the process (either dump or restore). The data doesn't even remotely resemble the original. 100% reproducibility. Steps to reproduce: 1) Create an ext4 filesystem and mount on /mnt/test 2) Create a simple text file on the filesystem: /mnt/test/testfile.txt 3) dump -0f /mnt/backup/testbackup.dmp /mnt/test 4) mkdir /mnt/backup/test; cd /mnt/backup/test 5) restore -rf /mnt/backup/testbackup.dmp 6) inspect /mnt/backup/test/testfile.txt to see corrupted data. Dump should either correctly dump an ext4 or refuse to do so entirely. In the current state, it could be lulling admins into a false sense of security that their data is backed up. -- dump cannot dump ext4 partitions https://bugs.launchpad.net/bugs/325346 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 321444] Re: cursor with synergyc client is stuck in upper left corner
This fixes the issue for me as well. I can switch between pointstick, touchpad and Synergy without any obvious issues. -- cursor with synergyc client is stuck in upper left corner https://bugs.launchpad.net/bugs/321444 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 333821] Re: synergy client fails to move mouse in 9.04
I had the same problem with: Server: 1.3.1-4ubuntu2 (intrepid) (i386) Client: 1.3.1-5ubuntu1 (jaunty) (x86_64) I also tried it with 1.3.1-5ubuntu1 on both systems and 1.3.1-4ubuntu2 on both systems, with no change. I upgraded the server to Jaunty, which means I'm currently running: Server: 1.3.1-5ubuntu1 (jaunty) (i386) Client: 1.3.1-5ubuntu1 (jaunty) (x86_64) And the mouse operates as expected. This when combined with the comments above seems to suggest that something has changed in the mouse handling in Jaunty that breaks Synergy for any non-Jaunty/Jaunty combination, particularly where Jaunty is the client and possibly where Jaunty is the server. -- synergy client fails to move mouse in 9.04 https://bugs.launchpad.net/bugs/333821 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 333821] Re: synergy client fails to move mouse in 9.04
My earlier statement that Jaunty/Jaunty works correctly is incorrect. On my laptop (HP Elitebook 8530w), I have a Synaptics touchpad as well as a joystick. If I touch the joystick *at all* Synergy will start working as expected. I must have bumped the joystick during my last test. This appears that it is likely a duplicate of 321444. -- synergy client fails to move mouse in 9.04 https://bugs.launchpad.net/bugs/333821 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 321444] Re: cursor with synergyc client is stuck in upper left corner
This also affects me. I have an HP Elitebook 8530w with both a touchpad and a joystick (pointstick). I found that if I move the joystick Synergy will start working as expected. If I use the touchpad, Synergy stops working and reverts to being stuck in the upper left corner. If I kill/restart synergyc, it goes back to whatever state it was in before being killed. If I kill synergyc, touch the touchpad and restart synergyc, it will be stuck. If I kill synergyc, move the joystick and restart synergyc, it works normally. -- cursor with synergyc client is stuck in upper left corner https://bugs.launchpad.net/bugs/321444 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 206337] Re: [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system
Bryce, Interestingly, I just upgraded to intrepid last night to get around the annoying intrepid-nx-hardy keyboard mapping bug (reported by someone else already), so I was in a good place to test this tonight. The updates installed fine, the fglrx-installer (via System-Administration-Hardware Drivers) worked correctly and my original problem (150k interrupts per sec) appears to be resolved with these latest updates. Interrupts are now down in a range I consider to be quite sane when using the FGLRX driver. X.org.log confirms that its using the 8.54.3 driver, and glxgears went from 190fps to 1200fps (even though glxgears is not to be used as a benchmark ;-). Thanks for working on/fixing this! -- [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system
Alberto, In this case EnvyNG yields a broken installation because when Compiz loads (i.e., it uses 3D effects), you get a white screen instead of the expected 3D effects. After some digging, I found this to be because the fglrx kernel module isn't loading. The reason the kernel module isn't loading is because there's no device stanza in xorg.conf which contains fglrx. If I manually insmod /lib/modules/2.6.24-19-generic/IForgetTheExactPpathToTheEnvyNGVersionOf/fglrx.ko, I get 3D effects as expected. Note that I was careful to make sure that I wasn't loading a remnant of the older Hardware Drivers installed which is normally included in volatile/fglrx.ko. I don't have this same problem with the Hardware Drivers method of getting 3D effects. Unfortunately, my original problem is experienced with either the EnvyNG installed driver (I forget the exact version that ultimately got installed) or the Hardware Drivers installed driver. If I can find some time soon, I'll report it on the ATI bugtracker. -- [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system
I tried this back around 7/15. Unfortunately, the EnvyNG installer results in a broken installation. Based on my limited diagnosis, the kernel module won't load because there's no device stanza in xorg.conf which contains fglrx. Because the kernel module isn't loaded, I wind up with a white screen when Compiz loads. Once I rectified that situation (manually installing the module using insmod instead of modprobe), the original problem seems to still be unchanged. Since you have to specify the full path of the module when you use insmod, I'm fairly certain that I was using the correct envy- installed kernel module and not the normal restricted module. Thanks for trying though. -- [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system
My original system was a 32-bit Hardy running on 64-bit capable hardware, upgraded from Gutsy. I did a fresh 32-bit install of Hardy, fully updated -- no change. I did a fresh 64-bit install of Hardy, fully updated -- no change. I read something somewhere recently about people running 32 bit OS on 64-bit hardware and running into some issues which is why I decided to do the fresh install. The problem still remains without any notable change -- something is still generating about 150K interrupts per sec (based on output from 'vmstat 1'), normal system performance, 2D performance is excruciatingly slow, and 3D performance is fair but slower than expected. If I disable the FGLRX driver, interrupts, 2D performance and system performance go back to their expected levels, but obviously I lose any benefits of the direct rendering. All this confirms is that I can replicate the results with both 32-bit and 64-bit Hardy and that there's no legacy issues from my Gutsy-Hardy upgrade that are triggering it. -- [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system
It looks like that might not be a good comparison: 1) AGP vs PCIe 2) 32-bit vs 64-bit Unless those two things matter less than they appear to. -- [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 198138] Re: Installer/wget is unable to retrieve files via a proxy
This test is with the apt-cacher server still running on port ~ # wget http://apt-proxy.company.com:/ubuntu//dists/hardy/Release -O - wget: no response from server ~ # wget http://apt-proxy.company.com:8738/ubuntu//dists/hardy/Release -O - wget: Unable to connect to remote host (192.168.1.20): Connection refused This is with the apt-cacher server running on 8738 ~ # wget http://apt-proxy.company.com:8738/ubuntu//dists/hardy/Release -O - wget: no response from server This is via Apache (apt-cacher install sets up Alias /apt-cacher /usr/share/apt-cacher/apt-cacher.pl) ~ # wget http://apt-proxy.company.com:80/apt-cacher/ubuntu//dists/hardy/Release -O - | grep ^Suite: | cut -d' ' -f 2 hardy It appears to me that the problem isn't an endianness problem, but rather that the busybox implementation of wget had a regression between Gutsy and Hardy such that it no longer works with apt-cacher or apt- proxy since it doesn't believe it's getting a response from the server. I ran tcpdump on the server. I ran wget http://apt-proxy.company.com:8738/ubuntu//dists/hardy/Release -O - from the installer's busybox. The request from the client: GET /ubuntu//dists/hardy/Release HTTP/1.1 Host: apt-proxy.company.com User-Agent: Wget Connection: close Then there's an ack back to the client, and then a FIN/ACK back to the client. From an installed client, the request looks like this: GET /ubuntu//dists/hardy/Release HTTP/1.0 User-Agent: Wget/1.10.2 Accept: */* Host: apt-proxy.company.com:8738 Connection: Keep-Alive HTTP/1.1 200 OK Connection: Keep-Alive Accept-Ranges: bytes Content-Length: 65852 Content-Type: text/plain; charset=UTF-8 Last-Modified: Fri, 18 Apr 2008 16:46:10 GMT ... -- Installer/wget is unable to retrieve files via a proxy https://bugs.launchpad.net/bugs/198138 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 198138] Re: Installer/wget is unable to retrieve files via a proxy
It should also be noted that I found a new version of the netboot installer had been released. All of the above tests were performed booted from http://us.archive.ubuntu.com/ubuntu/dists/hardy/main /installer-sparc/20070308ubuntu39/images/sparc64/netboot/2.6/boot.img -- Installer/wget is unable to retrieve files via a proxy https://bugs.launchpad.net/bugs/198138 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 206337] Re: [fglrx] Using fglrx causes excessive hardware interrupts and an extremely slow system
There's no change. If anything, my system seems less responsive than before. The excessive interrupts are still occurring. AIGLX was disabled, as /var/log/Xorg.?.log went from: $ fgrep AIGLX /var/log/Xorg.1.log (==) AIGLX enabled (WW) AIGLX: 3D driver claims to not support visual 0x23 (WW) AIGLX: 3D driver claims to not support visual 0x24 (WW) AIGLX: 3D driver claims to not support visual 0x25 (WW) AIGLX: 3D driver claims to not support visual 0x26 (WW) AIGLX: 3D driver claims to not support visual 0x27 (WW) AIGLX: 3D driver claims to not support visual 0x28 (WW) AIGLX: 3D driver claims to not support visual 0x29 (WW) AIGLX: 3D driver claims to not support visual 0x2a (WW) AIGLX: 3D driver claims to not support visual 0x2b (WW) AIGLX: 3D driver claims to not support visual 0x2c (WW) AIGLX: 3D driver claims to not support visual 0x2d (WW) AIGLX: 3D driver claims to not support visual 0x2e (WW) AIGLX: 3D driver claims to not support visual 0x2f (WW) AIGLX: 3D driver claims to not support visual 0x30 (WW) AIGLX: 3D driver claims to not support visual 0x31 (WW) AIGLX: 3D driver claims to not support visual 0x32 (WW) AIGLX: 3D driver claims to not support visual 0x33 (WW) AIGLX: 3D driver claims to not support visual 0x34 (WW) AIGLX: 3D driver claims to not support visual 0x35 (WW) AIGLX: 3D driver claims to not support visual 0x36 (WW) AIGLX: 3D driver claims to not support visual 0x37 (WW) AIGLX: 3D driver claims to not support visual 0x38 (WW) AIGLX: 3D driver claims to not support visual 0x39 (WW) AIGLX: 3D driver claims to not support visual 0x3a (WW) AIGLX: 3D driver claims to not support visual 0x3b (WW) AIGLX: 3D driver claims to not support visual 0x3c (WW) AIGLX: 3D driver claims to not support visual 0x3d (WW) AIGLX: 3D driver claims to not support visual 0x3e (WW) AIGLX: 3D driver claims to not support visual 0x3f (WW) AIGLX: 3D driver claims to not support visual 0x40 (WW) AIGLX: 3D driver claims to not support visual 0x41 (WW) AIGLX: 3D driver claims to not support visual 0x42 (WW) AIGLX: 3D driver claims to not support visual 0x43 (WW) AIGLX: 3D driver claims to not support visual 0x44 (WW) AIGLX: 3D driver claims to not support visual 0x45 (WW) AIGLX: 3D driver claims to not support visual 0x46 (WW) AIGLX: 3D driver claims to not support visual 0x47 (WW) AIGLX: 3D driver claims to not support visual 0x48 (WW) AIGLX: 3D driver claims to not support visual 0x49 (WW) AIGLX: 3D driver claims to not support visual 0x4a (WW) AIGLX: 3D driver claims to not support visual 0x4b (WW) AIGLX: 3D driver claims to not support visual 0x4c (WW) AIGLX: 3D driver claims to not support visual 0x4d (WW) AIGLX: 3D driver claims to not support visual 0x4e (WW) AIGLX: 3D driver claims to not support visual 0x4f (WW) AIGLX: 3D driver claims to not support visual 0x50 (WW) AIGLX: 3D driver claims to not support visual 0x51 (WW) AIGLX: 3D driver claims to not support visual 0x52 (WW) AIGLX: 3D driver claims to not support visual 0x53 (WW) AIGLX: 3D driver claims to not support visual 0x54 (WW) AIGLX: 3D driver claims to not support visual 0x55 (WW) AIGLX: 3D driver claims to not support visual 0x56 (WW) AIGLX: 3D driver claims to not support visual 0x57 (WW) AIGLX: 3D driver claims to not support visual 0x58 (WW) AIGLX: 3D driver claims to not support visual 0x59 (WW) AIGLX: 3D driver claims to not support visual 0x5a (WW) AIGLX: 3D driver claims to not support visual 0x5b (WW) AIGLX: 3D driver claims to not support visual 0x5c (WW) AIGLX: 3D driver claims to not support visual 0x5d (WW) AIGLX: 3D driver claims to not support visual 0x5e (WW) AIGLX: 3D driver claims to not support visual 0x5f (WW) AIGLX: 3D driver claims to not support visual 0x60 (WW) AIGLX: 3D driver claims to not support visual 0x61 (WW) AIGLX: 3D driver claims to not support visual 0x62 (WW) AIGLX: 3D driver claims to not support visual 0x63 (WW) AIGLX: 3D driver claims to not support visual 0x64 (WW) AIGLX: 3D driver claims to not support visual 0x65 (WW) AIGLX: 3D driver claims to not support visual 0x66 (WW) AIGLX: 3D driver claims to not support visual 0x67 (WW) AIGLX: 3D driver claims to not support visual 0x68 (WW) AIGLX: 3D driver claims to not support visual 0x69 (WW) AIGLX: 3D driver claims to not support visual 0x6a (WW) AIGLX: 3D driver claims to not support visual 0x6b (WW) AIGLX: 3D driver claims to not support visual 0x6c (WW) AIGLX: 3D driver claims to not support visual 0x6d (WW) AIGLX: 3D driver claims to not support visual 0x6e (WW) AIGLX: 3D driver claims to not support visual 0x6f (WW) AIGLX: 3D driver claims to not support visual 0x70 (WW) AIGLX: 3D driver claims to not support visual 0x71 (WW) AIGLX: 3D driver claims to not support visual 0x72 (II) AIGLX: Loaded and initialized /usr/lib/dri/fglrx_dri.so (II) AIGLX: Suspending AIGLX clients for VT switch (II) AIGLX: Resuming AIGLX clients after VT switch (II) AIGLX: Suspending AIGLX clients for VT switch To: $ fgrep AIGLX /var/log/Xorg.0.log (**) Option AIGLX off (**)
[Bug 206337] Re: Using fglrx causes excessive hardware interrupts and an extremely slow system
I should add that it appears that the system referenced above is otherwise functional. Top reports the system is constantly 60% busy in %hi when X is on the active console. The remainder of the system feels like it's 60% or busier, like it's running a 500mhz Celeron instead of the actual 2.8ghz Celeron D. Compiz works and 3D performance is fair, but not as fast as I'd expect, and definitely slower than the Nvidia TI4400 I have in a similarly equipped machine. -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] [NEW] Using fglrx causes excessive hardware interrupts and an extremely slow system
Public bug reported: On an up-to-date Hardy install, when I enable the FGLRX driver using the restricted drivers manager and reboot, either X or FGLRX cause an excessive number of hardware interrupts on my system whenever it's the active console: [EMAIL PROTECTED]:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- cpu r b swpd free buff cache si sobibo in cs us sy id wa 4 0 0 572108 10032 22753200 15530 22797 126 95 3 1 1 1 0 0 572100 10032 22753200 0 02 81 100 0 0 0 1 0 0 572100 10032 22753200 0 0 24 146 100 0 0 0 1 0 0 572100 10040 22753200 0167 92 100 0 0 0 1 0 0 572100 10040 22753200 0 0 25 145 100 0 0 0 1 0 0 572100 10040 22753200 0 0 55805 247 98 2 0 0 2 0 0 572100 10040 22753200 0 0 152106 90 100 0 0 0 3 0 0 572100 10040 22753200 0 0 147587 122 100 0 0 0 1 0 0 572100 10040 22753200 0 0 151499 176 99 1 0 0 1 0 0 572100 10040 22753200 0 0 152357 25 100 0 0 0 1 0 0 572100 10040 22753200 0 0 152022 81 100 0 0 0 1 0 0 572100 10052 22753200 040 152170 107 100 0 0 0 1 0 0 572100 10052 22753200 0 0 80430 199 100 0 0 0 1 0 0 572100 10052 22753200 0 01 79 100 0 0 0 1 0 0 572100 10052 22753200 0 0 24 131 100 0 0 0 1 0 0 572100 10052 22753200 0 01 77 100 0 0 0 Around second 6, I switched from tty1 to tty7 (X server), and back to tty1 around second 13. You can see the number of hardware interrupts jump from around 100/s to 15/s whenever X is on the active console. Performance is also very noticeably degraded. I've compared this against another system with a slightly older, but still respectable 3D card and the in field never exceeds 1000. This system. The VESA driver doesn't experience this problem, but has other significant issues (like the color map gets all messed up when you switch to a text console and back). I've tried various options (noapic, pci=routeirq, irqpoll and others) without any improvement to the situation and with some the system locks up hard and needs to be hard-reset. I've also seen the same problem with this exact same system using Gutsy and Envy-installed FGLRX drivers. ** Affects: linux-restricted-modules-2.6.24 (Ubuntu) Importance: Undecided Status: New -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: Using fglrx causes excessive hardware interrupts and an extremely slow system
** Attachment added: lspci -vvnn http://launchpadlibrarian.net/12850088/lspci-vvnn.log -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: Using fglrx causes excessive hardware interrupts and an extremely slow system
** Attachment added: xorg.conf http://launchpadlibrarian.net/12850094/xorg.conf -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: Using fglrx causes excessive hardware interrupts and an extremely slow system
** Attachment added: dmesg.log http://launchpadlibrarian.net/12850100/dmesg.log -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: Using fglrx causes excessive hardware interrupts and an extremely slow system
** Attachment added: interrupts.log http://launchpadlibrarian.net/12850103/interrupts.log -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: Using fglrx causes excessive hardware interrupts and an extremely slow system
** Attachment added: uname.log http://launchpadlibrarian.net/12850105/uname.log -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 206337] Re: Using fglrx causes excessive hardware interrupts and an extremely slow system
** Attachment added: version_signature.log http://launchpadlibrarian.net/12850111/version_signature.log -- Using fglrx causes excessive hardware interrupts and an extremely slow system https://bugs.launchpad.net/bugs/206337 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 203947] [NEW] Installer hangs trying to install SILO boot loader
Public bug reported: Binary package hint: debian-installer Steps to reproduce: 1) Do a network install using http://us.archive.ubuntu.com/ubuntu/dists/hardy/main/installer-sparc/20070308ubuntu33/images/sparc64/netboot/2.6/boot.img 2) Go Back at an appropriate point and Switch to low priority 3) Partition drives normally (my normal config includes RAID drives, but I tested this with non-raided and met the same hang). 4) When the installer gets to the Install SILO Boot Loader step of the install, it hangs (possibly indefinitely). 5) From another console, I killed '/usr/bin/perl /usr/sbin/siloconfig', and the installer complained of the failure. 6) I then proceeded with finish installation without boot loader, at which point it hung again, 7) I listed the processes again and noticed that something launched the SILO installer again. I killed it again and it completed the install 8) Upon reboot, it doesn't look like SILO got installed correctly. This system doesn't have a CD-ROM, so I can't test the CD-ROM based installer to see if I have similar issues. Syslog is attached. Note in the attached syslog that I've killed the PID for '/usr/bin/perl /usr/sbin/siloconfig' after letting it sit for 5 minutes or so with no activity. You'll see several attempts along these lines. ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- Installer hangs trying to install SILO boot loader https://bugs.launchpad.net/bugs/203947 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 203947] Re: Installer hangs trying to install SILO boot loader
** Attachment added: syslog http://launchpadlibrarian.net/12739492/syslog -- Installer hangs trying to install SILO boot loader https://bugs.launchpad.net/bugs/203947 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 203947] Re: Installer hangs trying to install SILO boot loader
** Attachment removed: syslog http://launchpadlibrarian.net/12739492/syslog ** Attachment added: syslog http://launchpadlibrarian.net/12739551/syslog -- Installer hangs trying to install SILO boot loader https://bugs.launchpad.net/bugs/203947 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 194032] Re: Install hangs on SILO using a LDom on a T5220
Since my report (bug 203947) has been marked a duplicate of this one, I thought I'd chime in: I netbooted, chrooted into my mostly installed system and performed the following: apt-get --purge remove silo then: [EMAIL PROTECTED]:/# apt-get install silo Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: silo 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/179kB of archives. After this operation, 393kB of additional disk space will be used. Selecting previously deselected package silo. (Reading database ... 15512 files and directories currently installed.) Unpacking silo (from .../silo_1.4.13a+git20070930-1ubuntu1_sparc.deb) ... Setting up silo (1.4.13a+git20070930-1ubuntu1) ... SILO, the Sparc Improved LOader, sets up your system to boot Linux directly from your hard disk, without the need for a boot floppy or a net boot. Install a partition boot record to boot Linux from UUID=3cb47072-33de-49fd-aed6-d77ccea87723? [Yes] Creating small silo.conf and running silo. Config file error: Syntax error near line 1 in file /etc/silo.conf Error parsing silo config file /etc/silo.conf [EMAIL PROTECTED]:/# cat /etc/silo.conf partition=87723 root=UUID=3cb47072-33de-49fd-aed6-d77ccea87723 timeout=20 image=/vmlinuz label=Linux read-only image=/vmlinuz.old label=LinuxOLD read-only Note that SILO counts the lines in the config file starting at 0, so it looks like the problems with the auto-generated file are: 1) the root= line uses a UUID, and SILO doesn't understand UUIDs 2) vmlinuz lives in /boot/ if you don't have a separate /boot partition. So the correct path in this case would be /boot/vmlinuz If I again netboot/chroot, edit /etc/silo.conf, and change it to : partition=1 root=/dev/md0 timeout=20 image=/boot/vmlinuz label=Linux read-only image=/boot/vmlinuz.old label=LinuxOLD read-only My system will then boot. -- Install hangs on SILO using a LDom on a T5220 https://bugs.launchpad.net/bugs/194032 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 194032] Re: Install hangs on SILO using a LDom on a T5220
I noticed an omission in that last bit (should have waited to cut-n-paste instead of manually making the changes): partition=1 root=/dev/md0 timeout=20 image=/boot/vmlinuz label=Linux read-only initrd=/boot/initrd.img image=/boot/vmlinuz.old label=LinuxOLD read-only initrd=/boot/initrd.img.old -- Install hangs on SILO using a LDom on a T5220 https://bugs.launchpad.net/bugs/194032 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
This appears to resolve my issue. I was able to get past partitioning and RAID configuration on a system with the original partition layout: IDE1 master (hda) - 20.0 GB ST320413A #1 8.2 MB (do not use) #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid IDE2 master (hdc) - 20.0 GB ST320413A #1 8.2 MB (do not use) #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid /dev/md0 (hda2,hdc2 - ext3 - /) /dev/md1 (hda4,hdc4 - ext3 - /usr) /dev/md2 (hda5,hdc5 - ext3 - /tmp) /dev/md3 (hda6,hdc6 - swap) /dev/md4 (hda7,hdc7 - ext3 - /var) /dev/md5 (hda8,hdc8 - ext3 - /export) Thanks for working on the problem. -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
Somehow I over looked this in the syslog: Mar 4 15:21:39 main-menu[5516]: (process:5580): /lib/partman/choose_method/70dont_use/choices: Permission denied Mar 4 15:21:39 main-menu[5516]: (process:5580): Mar 4 15:21:39 main-menu[5516]: (process:5580): /lib/partman/active_partition/15method/do_option: Mar 4 15:21:39 main-menu[5516]: (process:5580): /lib/partman/active_partition/15method/do_option: 10: Mar 4 15:21:39 main-menu[5516]: (process:5580): /lib/partman/choose_method/70dont_use/choices: Permission denied Mar 4 15:21:39 main-menu[5516]: (process:5580): Mar 4 15:21:39 main-menu[5516]: (process:5580): mount: Mar 4 15:21:39 main-menu[5516]: (process:5580): Mounting /dev/hda4 on /mnt/tmpmount failed Mar 4 15:21:39 main-menu[5516]: (process:5580): : Invalid argument Mar 4 15:21:39 main-menu[5516]: INFO: Menu item 'partman-base' succeeded but requested to be left unconfigured. The Mounting /dev/hda4 on /mnt/tmpmount failed is similar to what I was receiving before. The Permission denied messages seem to be new. -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
Unfortunately, no improvement. The only difference I can identify is that I can no longer mark partition 1 as Do Not Use. I'm using this partition layout, which is similar to one I've tried above. IDE1 master (hda) - 20.0 GB ST320413A #1 8.2 MB F ext3 #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid IDE2 master (hdc) - 20.0 GB ST320413A #1 8.2 MB F ext3 #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid Note that since I can't mark partition 1 as Do Not Use, it's now an EXT3 and marked as Do Not Mount. When I select Configure software RAID, it gives me the usual Are you sure you want to do this? page, two progress bars quickly scroll across the page, and I receive the original The installer needs to remove ... message. Syslog is attached, but I can't identify anything seemingly related. None of the other debug files seem to contain anything different from before and/or pertaining to this. ** Attachment added: syslog http://launchpadlibrarian.net/12381669/syslog -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
Performing: chmod ugo+x /lib/partman/choose_method/70dont_use/choices gets rid of the Permission denied problem, but doesn't seem to fix the original problem. I've poked around a bit but am still unclear as to why it's even attempting to mount the unconfigured RAID components. -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198138] Re: Installer/wget is unable to retrieve files via a proxy
By default, apt-cacher can also be accessed via Apache2 (if you have it installed). As a workaround, you can set the mirror to: apt-cacher.company.com and /apt-cacher/ubuntu Although I didn't used to have to do this with Gutsy and prior. -- Installer/wget is unable to retrieve files via a proxy https://bugs.launchpad.net/bugs/198138 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 198106] [NEW] Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
Public bug reported: Binary package hint: ubiquity 1) Netbooted my Netra X1 from /ubuntu/hardy/main/installer-sparc/20070308ubuntu31/images/sparc64/netboot/2.6/boot.img 2) configured my two internal drives as follows: IDE1 master (hda) - 20.0 GB ST320413A #1 8.2 MB #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid IDE2 master (hdc) - 20.0 GB ST320413A #1 8.2 MB #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid 3) selected Configure software RAID 4) Confirmed Keep current partition layout and configure RAID? with Yes 5) There is a pause, and then I receive: [!!] Partition disks Failed to remove conflicting files The installer needs to remove operating system files from the install target, but was unable to do so. The install cannot continue. 6) Click continue, and I receive: [!!] Partition disks RAID configuration failure An error occurred while writing the changes to the storage devices RAID configuration has been aborted. 7) Click continue and it sends me back to the partitioner. I know for a fact that I've used this exact same configuration with Gutsy, and possibly as far back as Dapper. This is on a headless system, so I have to install via text mode and can't switch between consoles. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
I think this may actually be a debian-installer problem, but I'll leave it up to the experts to decide. -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
** Attachment added: hardware-summary http://launchpadlibrarian.net/12370210/hardware-summary ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
** Attachment added: partman http://launchpadlibrarian.net/12370206/partman -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
I did a save debug logs from the main menu. I found the following interesting: Mar 3 18:51:03 main-menu[27682]: (process:4769): mount: Mar 3 18:51:03 main-menu[27682]: (process:4769): Mounting /dev/hda1 on /mnt/tmpmount failed Mar 3 18:51:03 main-menu[27682]: (process:4769): : Invalid argument Mar 3 18:51:03 main-menu[27682]: (process:4769): mount: Mar 3 18:51:03 main-menu[27682]: (process:4769): Mounting /dev/hda1 on /mnt/tmpmount failed Mar 3 18:51:03 main-menu[27682]: (process:4769): : Invalid argument Mar 3 18:51:03 main-menu[27682]: INFO: Menu item 'partman-base' succeeded but requested to be left unconfigured. Mar 3 18:51:03 main-menu[27682]: DEBUG: resolver (libnewt0.52): package doesn't exist (ignored) Mar 3 18:51:03 main-menu[27682]: DEBUG: resolver (rdate-udeb): package doesn't exist (ignored) Mar 3 18:51:03 main-menu[27682]: INFO: Falling back to the package description for console-setup-udeb Mar 3 18:51:10 main-menu[27682]: INFO: Falling back to the package description for console-setup-udeb Mar 3 18:51:10 main-menu[27682]: INFO: Menu item 'save-logs' selected Note that /dev/hda1 is marked as Do Not Use. Why is it trying to mount it? ** Attachment added: syslog http://launchpadlibrarian.net/12370182/syslog -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
This (valid) partition layout also has problems: IDE1 master (hda) - 20.0 GB ST320413A #1 8.2 MB #2 641.6 MB f ext3 / #4 4.1 GB f ext3 /usr #5 510.0 MB f ext3 /tmp #6 3.1 GB f swap swap #7 5.1 GB f ext3 /var #8 6.6 GB f ext3 /export IDE2 master (hdc) - 20.0 GB ST320413A 20.0 GB FREE SPACE I get a warning about SILO being installed on an unknown partition, if I continue through that, I get the same error as above. Even this fails: IDE1 master (hda) - 20.0 GB ST320413A #1 8.2 MB f ext3 /mnt/t1 #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid IDE2 master (hdc) - 20.0 GB ST320413A #1 8.2 MB f ext3 /mnt/t2 #2 641.6 MB K raid #4 4.1 GB K raid #5 510.0 MB K raid #6 3.1 GB K raid #7 5.1 GB K raid #8 6.6 GB K raid Although, this time it's trying to mount /dev/hda6. (syslog attached) ** Attachment added: syslog http://launchpadlibrarian.net/12370538/syslog -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198106] Re: Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so.
And in case you're wondering, the reason I leave /dev/hda1 and /dev/hdc1 unconfigured is due to the fact that RAID volumes will overwrite the Sun disklabel. This configuration appears to work: IDE1 master (hda) - 20.0 GB ST320413A #1 131.6 MB f ext3 /boot #2 510.0 MB f ext3 / #4 4.1 GB f ext3 /usr #5 510.0 MB f ext3 /tmp #6 3.1 GB f swap swap #7 5.1 GB f ext3 /var #8 6.6 GB f ext3 /export IDE2 master (hdc) - 20.0 GB ST320413A 20.0 GB FREE SPACE Unfortunately, the install bombs out with an invalid release signature. With as unstable as the repositories have been lately in that regard, I'm not sure whether this is a d-i issue or just the flakiness of the repositories. Either way, that's a separate issue from what I reported above. -- Configure partitions for RAID1, received: The installer needs to remove operating system files from the install target, but was unable to do so. https://bugs.launchpad.net/bugs/198106 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 198138] [NEW] Installer/wget is unable to retrieve files via a proxy
Public bug reported: Binary package hint: debian-installer Installer is unable to retrieve files from apt-proxy/apt-cacher style proxies using hostname:port, despite the fact that the dialogs say that it's valid. 1) Netbooted from /ubuntu/hardy/main/installer-sparc/20070308ubuntu31/images/sparc64/netboot/2.6/boot.img 2) manually set apt-proxy.company.com: and /ubuntu/ at the prompt for which repository to use The problem seems to stem from the fact that the installer's version of wget appears to be hobbled in some fashion: This is from a running i386 Hardy system on the same network: [EMAIL PROTECTED]:~$ wget -q http://apt-proxy.company.com:/ubuntu//dists/hardy/Release -O - | grep ^Suite: | cut -d' ' -f 2 hardy So, the proxy is definitely working, and none of my other machines have problems accessing it. This is from the shell on the netbooted system: ~ # wget -q http://apt-proxy.company.com:/ubuntu//dists/hardy/Release -O - | grep ^Suite: | cut -d' ' -f 2 wget: no response from server ~ # wget -q http://192.168.1.20:/ubuntu//dists/hardy/Release -O - wget: no response from server It can get to the server from the netbooted system if I drop the port: ~ # wget -q http://192.168.1.20/ubuntu//dists/hardy/Release -O - wget: server returned error 404: HTTP/1.1 404 Not Found (note that port 80 is just a plain web sever, no Ubuntu packages, so the 404 is normal) ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- Installer/wget is unable to retrieve files via a proxy https://bugs.launchpad.net/bugs/198138 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 26119] Re: Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound
Hardy works for me running a netinstall with kernel 2.6.24-10-sparc64. I'll report back if it doesn't work after the installation is complete. -- Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound https://bugs.launchpad.net/bugs/26119 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153996] Re: libdb4.4 in gutsy breaks postgrey and subversion
I was experiencing the same problem, so I installed Daniel Haler's PPA version and about two weeks ago. It cured my immediate ills and had been running ever since without problems. Last night, I installed the version released into gutsy-proposed. My initial impression is that it also seems to fix the problem and not cause any problems with any other packages I use, although my testing is minimal at this point. I'll report again if I find the postgrey problem return or other issues. -- libdb4.4 in gutsy breaks postgrey and subversion https://bugs.launchpad.net/bugs/153996 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141526] Re: Sparc hangs on Booting Linux on Gutsy
This appears to have been resolved with kernel linux- image-2.6.22-13-sparc64 (2.6.22-13.40) and boot image 20070308ubuntu17 ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New = Fix Released -- Sparc hangs on Booting Linux on Gutsy https://bugs.launchpad.net/bugs/141526 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141526] Sparc hangs on Booting Linux on Gutsy
Public bug reported: Binary package hint: linux-source-2.6.22 I have a Sun Netra X1 that I wanted to test Gutsy on. When booting, it gets as far as Booting Linux and fails to continue to boot regardless of how long I wait -- I left it sitting like this overnight last night. Since this seems to affect both the netboot image as well as the regular kernel, It appears that this might be a kernel or kernel build issue, which is why I attached it to the 2.6.22 kernel. Please adjust if you believe otherwise. I notice this problem under two circumstances: 1) When I attempt to netboot from: http://us.archive.ubuntu.com/ubuntu/dists/gutsy/main/installer-sparc/20070308ubuntu12/images/sparc64/netboot/2.6/boot.img I receive: ok boot net Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED] File and args: Timeout waiting for ARP/RARP packet Timeout waiting for ARP/RARP packet Timeout waiting for ARP/RARP packet Timeout waiting for ARP/RARP packet 94b800 Remapping the kernel... done. OF stdout device is: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],3f8 Booting Linux... And it hangs indefinitely. 2) Since I couldn't get the Gutsy netboot image to work, I installed from the Feisty netboot image from: http://us.archive.ubuntu.com/ubuntu/dists/feisty/main/installer-sparc/20061102ubuntu26/images/sparc64/netboot/2.6/ Feisty installed and runs fine. Then I upgraded to Gutsy After the upgrade, upon booting into the 2.6.22 (linux- image-2.6.22-11-sparc64 package, version: 2.6.22-11.33) kernel, I receive: ok boot Boot device: disk0:3 File and args: SILO Version 1.4.13 boot: Allocated 8 Megs of memory at 0x4000 for kernel Uncompressing image... Loaded kernel version 2.6.22 Loading initial ramdisk (6616050 bytes at 0x6000 phys, 0x40C0 virt)... - Remapping the kernel... done. OF stdout device is: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],3f8 Booting Linux... And it hangs indefinitely. Selecting Linux-rescue from the Silo prompt gives identical output. If I manually select LinuxOLD (the 2.6.20 Feisty kernel from prior to the upgrade) at the Silo prompt, and it boots fine: ok boot Boot device: disk0:3 File and args: SILO Version 1.4.13 boot: LinuxLinuxOLD Linux-rescue LinuxOLD-rescue boot: LinuxOLD Allocated 8 Megs of memory at 0x4000 for kernel Uncompressing image... Loaded kernel version 2.6.20 Loading initial ramdisk (6595677 bytes at 0x6000 phys, 0x40C0 virt)... / Remapping the kernel... done. Booting Linux... Loading, please wait... * Setting preliminary keymap... ...done. [it continutes normally, so I snipped for brevity] ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Sparc hangs on Booting Linux on Gutsy https://bugs.launchpad.net/bugs/141526 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120426] Re: EATA driver/module does not load
I had the exact same problem yesterday. Ultimately, I found that the following workaround got my system to reboot correctly: 1) load the eata module from the busybox shell and wait 10s 2) exit from the shell and log in once the system has loaded 3) echo eata /etc/initramfs-tools/modules 4) echo eata /etc/modules 5) update-initramfs -k all -u My system: Asus P2B (P II 450) DPT PM3334UW RAID card ATAPI CDROM -- EATA driver/module does not load https://bugs.launchpad.net/bugs/120426 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49914] Re: initramfs/mdrun doesn't honor preferred minor when starting RAID volumes
Yes. The bug is present in Edgy.. I haven't tried upgrading to Feisty yet. I created a raid array: mdadm --create -l5 -n 14 /dev/md10 /dev/sd[bcdfghijklqrst]1 Added it to /etc/mdadm/mdadm.conf: [EMAIL PROTECTED]:/# cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md0 level=raid1 num-devices=2 UUID=75fa8aad:ebad7171:fab782c2:128dd001 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=4962386b:4220a6b0:52362aed:e8177a98 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=211c8f5b:d8854afd:33626b06:0fce6c77 ARRAY /dev/md3 level=raid1 num-devices=2 UUID=a389ea68:820de8ac:50f8d391:6a1e5bfc ARRAY /dev/md4 level=raid1 num-devices=2 UUID=4d4021dc:5a1d718e:c72beddc:a40274b6 ARRAY /dev/md5 level=raid1 num-devices=2 UUID=aaeb5e70:58768c4f:b218283e:86a35d4c ARRAY /dev/md10 level=raid5 num-devices=14 UUID=b68f200f:c99aa697:ec26162e:580f6e07 Rebuilt my initramfs (not sure if this is actually necessary or not): update-initramfs -k all -u Added it to /etc/fstab: [EMAIL PROTECTED]:/# fgrep export /etc/fstab UUID=378b2a0d-66f6-4228-9772-6edc387b2dad /export ext3defaults 0 2 But it still gets started as /dev/md6: [EMAIL PROTECTED]:/# cat /proc/mdstat Personalities : [raid1] [raid5] [raid4] md6 : active raid5 sdb1[0] sdt1[13] sds1[12] sdr1[11] sdq1[10] sdl1[9] sdk1[8] sdj1[7] sdi1[6] sdh1[5] sdg1[4] sdf1[3] sdd1[2] sdc1[1] 462172672 blocks level 5, 64k chunk, algorithm 2 [14/14] [UU] ... (md0-md5 pruned for brevity) While everything DOES gets started and mounted correctly using the UUIDs, if I set a RAID volume to start up as /dev/md10, it's my belief that it should remain there after rebooting even if it uses the UUIDs to start them. -- initramfs/mdrun doesn't honor preferred minor when starting RAID volumes https://bugs.launchpad.net/bugs/49914 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 26119] Re: Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound
The problem is still occurring in Feisty. -- Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound https://bugs.launchpad.net/bugs/26119 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
This appears to have resolved my problem also. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
My experience mirrors (pun intended) Jeff250's. If I boot with break=mount, and remove quiet splash, it drops to the shell, and about a second later, it discovers everything properly. At that point, I can exit the shell and the boot process will continue normally. If I don't boot with break=mount and I let it fail and drop me to the shell, nothing is ever discovered. This might be expected behavior in this circumstance. One of the odd things in the first case is that my ATA (not SATA) drives are discovered as /dev/sda and /dev/sdb according to /proc/mdstat, which reports that /dev/md1 is comprised of /dev/sda5 and /dev/sdb5. In the let it fail scenario, if I perform a udevd ; udevtrigger; [wait a few seconds] ; pkill udev it properly discovers them as /dev/hda and /dev/hdc and starts /dev/md1 with /dev/hda5 /dev/hdc5. Either way, once it's finished booting, /proc/mdstat reports the correct device names (/dev/hda* and /dev/hdc*). -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
Correction -- after booting in the break=mount scenario my ATA (not SATA) drives are still identified as /dev/sda and /dev/sdb according to /proc/mdstat: [EMAIL PROTECTED]:~# cat /proc/mdstat Personalities : [raid1] ... md1 : active raid1 sda5[0] sdb5[1] 497856 blocks [2/2] [UU] The same holds true for the let it fail and sleep 10 boot scenarios. I guess this is a new feature. I hadn't noticed this previously, since the Feisty system I've been working with most uses SATA, and SATA has always shown up as SCSI. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
Clarification -- two comments up, in the let it fail scenario, nothing is ever discovered should read: /dev/sda*, /dev/sdb*, /dev/hda* /dev/hdc* are never discovered regardless how long I wait. /dev/md1 does exist at this point. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
I tried adding /sbin/udevsettle --timeout=10 to the bottom of /usr/share/initramfs-tools/scripts/init-premount/udev, rebuilt my initrd, and it does seem to work on my system just as reliably as the sleep 10 method. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96430] Re: MASTER: Request for new-legacy nvidia drivers (9631)
Confirmed working for me -- my bug was marked as one of the dupes of this one. -- MASTER: Request for new-legacy nvidia drivers (9631) https://bugs.launchpad.net/bugs/96430 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
Sorry for the delay. We went away for the weekend. Attached is the requested information. The first one is a photo when it first drops to the busybox shell. ** Attachment added: Photo right after it drops to the busybox shell http://librarian.launchpad.net/7220867/mvc-143x.jpg -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
This photo is about two minutes after the first one, with ls -al /dev/hda* /dev/hdc* /dev/md* and cat /proc/mdstat ** Attachment added: Photo two minutes after it drops to shell, with additional information. http://librarian.launchpad.net/7220873/mvc-144x.jpg -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
ps.log ** Attachment added: ps.log from initial busybox http://librarian.launchpad.net/7220912/ps.log -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
** Attachment added: /etc/mdadm/mdadm.conf http://librarian.launchpad.net/7220921/mdadm.conf -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
I decided to include this, since it also seems to control how and which arrays are started up at boot. ** Attachment added: /etc/default/mdadm http://librarian.launchpad.net/7220924/mdadm -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
All, Please read this comment in another bug by Scott James Remnant. https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/83231/comments/25 This policy isn't clearly displayed anywhere obvious, they apparently want us all to open separate bugs for them to investigate, and they will determine if it's an actual duplicate or not. ** Also affects: udev (Ubuntu) Importance: Undecided Status: Unconfirmed -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Unconfirmed -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] boot-time race condition initializing md
Public bug reported: Binary package hint: mdadm I originally contributed some feedback to Bug #75681. It is currently reported as being fixed, but my problem still persists. The person that closed it recommended that we open new bugs if we're still having problems. I've reproduced my feedback here to save looking it up: == FWIW, I have the problem, exactly as described, with a IDE-only system. I attempted this with both an Edgy-Feisty upgrade (mid Februrary), and a fresh install of Herd5. I'm running straight RAID1 for all my volumes: md0 - hda1/hdc1 - /boot md1 - hda5/hdc5 - / md2 - hda6/hdc6 - /usr md3 - hda7/hdc7 - /tmp md4 - hda8/hdc8 - swap md5 - hda9/hdc9 - /var md6 - hda10/hdc10 - /export EVERY time I boot, mdadm complains that it can't build my arrays. It dumps me in the busybox shell where I discover that all /dev/hda* and /dev/hdc* devices are missing. I ran across a suggestion here: http://ubuntuforums.org/showpost.php?p=2236181postcount=5. I followed the instructions and so far, it's worked perfectly at every boot (about 5 times now). Other than just to post a me too, I thought my comments might help give a possible temporary workaround, as well as document the fact this isn't just a SATA problem. I just updated to the latest packages as of approximately 4/5/07 00:50 EDT, and nothing has changed. To fix it, I can follow the workaround here: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/75681/comments/60 (Boot with break=premount At the initramfs prompt: udevd --verbose --suppress-syslog /tmp/udev-output 21 udevtrigger ) or here: http://ubuntuforums.org/showpost.php?p=2236181postcount=5 (add 'sleep 10' after 'log_begin_msg Mounting root file system...' in usr/share/initramfs-tools/init) Either will allow me to boot (the latter without manual intervention). ** Affects: mdadm (Ubuntu) Importance: Undecided Status: Unconfirmed -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
This isn't fixed for me. I opened a new report (Bug # 103177) as requested by Scott James Remnant. My problem still has the exact same symptoms that I described above. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/75681 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
Here are the versions of the related packages currently installed on my system: dmsetup 1.02.08-1ubuntu10 libdevmapper1.02 1.02.08-1ubuntu10 libvolume-id0108-0ubuntu3 lvm-common none lvm2 none mdadm2.5.6-7ubuntu5 udev 108-0ubuntu3 volumeid 108-0ubuntu3 -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96816] Update breaks working xorg/compiz configuration on GeForce4 4400TI
Public bug reported: Binary package hint: xorg I had a working xorg/compiz/nvidia-glx configuration working properly prior to updates this evening. Among other things, I updated the following (and their related packages): compiz 1:0.3.6-1ubuntu8(old) 1:0.3.6-1ubuntu10(new) xserver-xorg 1:7.2-0ubuntu8(old) 1:7.2-0ubuntu9(new) nvidia-glx 1.0.9631+2.6.20.3-12.11(old) 1.0.9755+2.6.20.4-13.12(new) X now breaks saying that my card isn't supported in nvidia-glx, but rather I should be using nvidia-glx-legacy. The description for nvidia-glx-legacy (in deselect) says that it's for older Nvidia cards, like TNT, GeForce, and GeForce2, all of which are considerably older than my card. Regardless, I installed nvidia-glx- legacy to see if it would fix the problem. X now starts correctly, but when I log in, I don't have a window manager running. When manually started, Compiz craps out with an error: Xlib: extension GLX missing on display :0.0. /usr/bin/compiz.real: Root visual is not a GL visual /usr/bin/compiz.real: Failed to manage screen: 0 /usr/bin/compiz.real: No manageable screens found on display :0.0 Metacity will start correctly, but not automatically. lspci -v reports the following regarding my GeForce4 card: 01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4400] (rev a3) (prog-if 00 [VGA]) Subsystem: Micro-Star International Co., Ltd. Unknown device 8711 Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 16 Memory at f800 (32-bit, non-prefetchable) [size=16M] Memory at e800 (32-bit, prefetchable) [size=128M] Memory at f000 (32-bit, prefetchable) [size=512K] [virtual] Expansion ROM at f008 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 2.0 So, I have a number of problems here (some xorg, some not): 1) My completely working and surprisingly stable (for a beta) setup was broken with this update 2) X was left in an invalid state due to the update. 3) Compiz dies with no warning, leaving no window manager running. 4) X is incorrectly reporting that my card is supported by nvidia-glx- legacy, when it was previously working just fine with nvidia-glx and other documentation suggests that nvidia-glx should be used with my card. In fact, the 4200 and 4600 (little and big brothers to my card) supposedly work just fine with nvidia-glx. 5) When I try to turn off desktop effects via the preferences control panel, I'm only given cancel and enable at the dialog. Cancel just seems to cancel the dialog. Enable installs nvidia-glx, which we've already determined that X seems to believe doesn't work with my card. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- Update breaks working xorg/compiz configuration on GeForce4 4400TI https://launchpad.net/bugs/96816 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96816] Re: Update breaks working xorg/compiz configuration on GeForce4 4400TI
I did a little research here: http://www.nvidia.com/object/unix.html And it turns out that the 1.0-9755 binary driver no longer supports the ti 4400, whereas the 1.0-9633 binary driver does. So, it looks like X has a legitimate complaint there. However, that still leaves all of my other points, especially #5. -- Update breaks working xorg/compiz configuration on GeForce4 4400TI https://launchpad.net/bugs/96816 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49265] Re: Intel 440BX: 'hda: I/O error'
Rouben:
I can't confirm whether this is actually a duplicate of 26119, but it
sounds virtually identical. The problem is only with particular drives.
The Seagate ST320413A referenced below causes it, but neither a Seagate
ST320420A nor a Western Digital WDC WD400EB-00CPF0 do.
Paolo:
Assuming it's the same bug, yes, it still persists. This is on a Sun
Ultra 5 that's had the problem since it was first reported -- I can't
remember whether it started in Breezy or Dapper.
[EMAIL PROTECTED]:/etc# cat lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=6.10
DISTRIB_CODENAME=edgy
DISTRIB_DESCRIPTION=Ubuntu 6.10
[EMAIL PROTECTED]:/etc# cat /proc/ide/hda/model
ST320413A
---[partial dmesg]---
[ 36.653285] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 36.732586] hda: dma_intr: error=0x10 { SectorIdNotFound },
LBAsect=39102336, sector=39102336
[ 36.834668] ide: failed opcode was: unknown
[ 37.025125] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 37.104357] hda: dma_intr: error=0x10 { SectorIdNotFound },
LBAsect=39102336, sector=39102336
[ 37.206434] ide: failed opcode was: unknown
[ 37.397036] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 37.476233] hda: dma_intr: error=0x10 { SectorIdNotFound },
LBAsect=39102336, sector=39102336
[ 37.578311] ide: failed opcode was: unknown
[ 37.768906] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[ 37.848109] hda: dma_intr: error=0x10 { SectorIdNotFound },
LBAsect=39102336, sector=39102336
[ 37.950187] ide: failed opcode was: unknown
[ 38.000199] hda: DMA disabled
[ 38.094499] ide0: reset: success
Since my Sparc shows the exact same symptoms, it's likely a chipset
problem or related to particular drives.
--
Intel 440BX: 'hda: I/O error'
https://launchpad.net/bugs/49265
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49265] Re: Intel 440BX: 'hda: I/O error'
I probably should have included a bit more of the dmesg output. Here is
where it's the same. The above section immediately preceded this:
[ 38.303408] hda: task_in_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[ 38.399361] hda: task_in_intr: error=0x10 { SectorIdNotFound },
LBAsect=39167615, sector=39102336
[ 38.505605] ide: failed opcode was: unknown
[ 38.726907] hda: task_in_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[ 38.822800] hda: task_in_intr: error=0x10 { SectorIdNotFound },
LBAsect=39167615, sector=39102336
[ 38.929044] ide: failed opcode was: unknown
[ 39.150264] hda: task_in_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[ 39.246131] hda: task_in_intr: error=0x10 { SectorIdNotFound },
LBAsect=39167615, sector=39102336
[ 39.352381] ide: failed opcode was: unknown
[ 39.573516] hda: task_in_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[ 39.669469] hda: task_in_intr: error=0x10 { SectorIdNotFound },
LBAsect=39167615, sector=39102336
[ 39.775716] ide: failed opcode was: unknown
[ 39.870498] ide0: reset: success
[ 40.079414] hda: task_in_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[ 40.175304] hda: task_in_intr: error=0x10 { SectorIdNotFound },
LBAsect=39167615, sector=39102336
[ 40.281546] ide: failed opcode was: unknown
[ 40.331693] end_request: I/O error, dev hda, sector 39102336
[ 40.399265] Buffer I/O error on device hda, logical block 39102336
--
Intel 440BX: 'hda: I/O error'
https://launchpad.net/bugs/49265
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 26119] Re: Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound
I confirm that my earlier report about the Sparcs I'm using have the same problem in Edgy too. I reported it in slightly more detail in Bug # 49265 -- Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound https://launchpad.net/bugs/26119 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
FWIW, I have the problem, exactly as described, with a IDE-only system. I attempted this with both an Edgy-Feisty upgrade (mid Februrary), and a fresh install of Herd5. I'm running straight RAID1 for all my volumes: md0 - hda1/hdc1 - /boot md1 - hda5/hdc5 - / md2 - hda6/hdc6 - /usr md3 - hda7/hdc7 - /tmp md4 - hda8/hdc8 - swap md5 - hda9/hdc9 - /var md6 - hda10/hdc10 - /export EVERY time I boot, mdadm complains that it can't build my arrays. It dumps me in the busybox shell where I discover that all /dev/hda* and /dev/hdc* devices are missing. I ran across a suggestion here: http://ubuntuforums.org/showpost.php?p=2236181postcount=5. I followed the instructions and so far, it's worked perfectly at every boot (about 5 times now). Other than just to post a me too, I thought my comments might help give a possible temporary workaround, as well as document the fact this isn't just a SATA problem. -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75555] Re: Software Raid Setup with feisty herd1 alternate on amd64
I can confirm the same with Herd3. From my diagnosis, it appears that /dev/md? are missing or not generated properly in the initramfs. In the busybox shell, I proceeded to do: mknod /dev/md0 b 9 0 mknod /dev/md1 b 9 1 etc.. mdadm --run /dev/md0 /dev/hda1 /dev/hdc1 mdadm --run /dev/md1 /dev/hda5 /dev/hdc5 etc.. exit And then it proceeded to boot properly. I did all of that from memory, so I may not have all the commands exact. -- Software Raid Setup with feisty herd1 alternate on amd64 https://launchpad.net/bugs/7 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41787] Re: nppdf.so: undefined symbol: XtCalloc
Try this. Start Firefox from a command prompt: LD_PRELOAD=/usr/lib/libXt.so.6 /usr/lib/firefox/firefox That should temporarily fix the problem until you exit firefox. The problem appears to be that nppdf.so expects that libXt.so to already be loaded, which is bad practice. A hack that will work around the problem (but load more, possibly unnecessary libraries, depending on what you're doing), again at a command prompt: 1) sudo cp -a /usr/lib/firefox/firefox /usr/lib/firefox/firefox.old 2) sudo vi /usr/lib/firefox/firefox 3) search for: export LD_LIBRARY_PATH 4) change it to: export LD_LIBRARY_PATH LD_PRELOAD=/usr/lib/libXt.so.6 export LD_PRELOAD Save the file and make sure firefox is completely closed. When you start up Firefox the next time, you should find that Acrobat reader works, at least until an update comes out that overwrites the firefox script. -- nppdf.so: undefined symbol: XtCalloc https://launchpad.net/bugs/41787 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49509] Re: init script does not create requirred /var/run/mailscanner directory
To work around this bug, I put the following in /etc/default/mailscanner: [ ! -d /var/run/MailScanner ] mkdir /var/run/MailScanner chown postfix:postfix /var/run/MailScanner [ ! -d /var/lock/subsys/MailScanner ] mkdir -p /var/lock/subsys/MailScanner chown postfix:postfix /var/lock/subsys/MailScanner Obviously, you'll need to change the ownership appropriately if you're running something other than Postfix. This seemed like the lowest impact way to get my system to work correctly across reboots and MailScanner updates. It should also be transparent once this bug gets fixed. -- init script does not create requirred /var/run/mailscanner directory https://launchpad.net/bugs/49509 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49914] initramfs/mdrun doesn't honor preferred minor when starting RAID volumes
Public bug reported: On a Sun e420 during the install, I created my volumes as follows: /dev/sda1 /boot /dev/md0 /home (/dev/sd[ab]8) /dev/md1 / (/dev/sd[ab]2) /dev/md2 /usr (/dev/sd[ab]4) /dev/md3 swap (/dev/sd[ab]5) /dev/md4 /tmp (/dev/sd[ab]6) /dev/md5 /var (/dev/sd[ab]7) and completed the install. Upon reboot, my RAID volumes were started as: /dev/sda1 /boot /dev/md0 / /dev/md1 /usr /dev/md2 swap /dev/md3 /tmp /dev/md4 /var /dev/md5 /home apparently started in order of discovery (/dev/sda1 through /dev/sda8), not honoring the preferred minor or /etc/mdadm.conf, and rendering my system unbootable until I did some surgery. After the surgery, I patched to date (incl kernel 2.6.15-25) and did an event-free reboot. At this point, the raid volumes are: /dev/md0 /boot (/dev/sd[ab]1) /dev/md1 / (/dev/sd[ab]2) /dev/md2 /usr (/dev/sd[ab]4) /dev/md3 swap (/dev/sd[ab]5) /dev/md4 /tmp (/dev/sd[ab]6) /dev/md5 /var (/dev/sd[ab]7) /dev/md6 /home (/dev/sd[ab]8) I created two raid volumes mdadm -C -l5 -c64 -n6 -x0 /dev/md11 /dev/sd[cdefgh] mdadm -C -l5 -c64 -n6 -x0 /dev/md12 /dev/sd[ijklmn] As you can see, my RAID volume components do have the preferred minor listed correctly prior to rebooting (the array is still building here): [EMAIL PROTECTED]:~# mdadm -E /dev/sdc (d-h report similar) /dev/sdc: Magic : a92b4efc Version : 00.90.03 UUID : 71063e4f:f3a0c78b:12a4584b:a8cd9402 Creation Time : Thu Jun 15 15:21:36 2006 Raid Level : raid5 Raid Devices : 6 Total Devices : 6 Preferred Minor : 11 Update Time : Thu Jun 15 15:28:42 2006 State : clean Active Devices : 5 Working Devices : 6 Failed Devices : 1 Spare Devices : 1 Checksum : 54875fd8 - correct Events : 0.48 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 0 8 320 active sync /dev/sdc 0 0 8 320 active sync /dev/sdc 1 1 8 481 active sync /dev/sdd 2 2 8 642 active sync /dev/sde 3 3 8 803 active sync /dev/sdf 4 4 8 964 active sync /dev/sdg 5 5 005 faulty removed 6 6 8 1126 spare /dev/sdh my mdadm.conf is set correctly: [EMAIL PROTECTED]:~# cat /etc/mdadm/mdadm.conf DEVICE partitions DEVICE /dev/sd[cdefghijklmn] ARRAY /dev/md11 level=raid5 num-devices=6 UUID=71063e4f:f3a0c78b:12a4584b:a8cd9402 ARRAY /dev/md12 level=raid5 num-devices=6 UUID=456e8cd0:0f23591b:14a0ff9f:1a302d54 ARRAY /dev/md6 level=raid1 num-devices=2 UUID=4b33d5c5:80846d59:dba11e6d:814823f3 ARRAY /dev/md5 level=raid1 num-devices=2 UUID=76f34ac9:d74a2d9c:d0fc0f95:eab326d2 ARRAY /dev/md4 level=raid1 num-devices=2 UUID=0eed0b47:c6e81eea:3ed1c7a6:3ed2a756 ARRAY /dev/md3 level=raid1 num-devices=2 UUID=1d626217:4d20944a:5dbbcb0d:dd7c6e3d ARRAY /dev/md2 level=raid1 num-devices=2 UUID=102303be:19a3252d:48a3f79e:33f16ce1 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=30eedd12:b5b69786:97b18df5:7efabcbf ARRAY /dev/md0 level=raid1 num-devices=2 UUID=9b28e9d5:944316d7:f0aacc8b:d5d82b98 And yet when I reboot /dev/md11 is started as /dev/md7 and /dev/md12 is started as /dev/md8. [EMAIL PROTECTED]:~# cat /proc/mdstat Personalities : [raid1] [raid5] md8 : active raid5 sdi[0] sdn[6] sdm[4] sdl[3] sdk[2] sdj[1] 177832000 blocks level 5, 64k chunk, algorithm 2 [6/5] [U_] [] recovery = 0.0% (28416/35566400) finish=561.1min speed=10520K/sec md7 : active raid5 sdc[0] sdh[6] sdg[4] sdf[3] sde[2] sdd[1] 177832000 blocks level 5, 64k chunk, algorithm 2 [6/5] [U_] [] recovery = 0.0% (29184/35566400) finish=567.9min speed=10420K/sec md6 : active raid1 sda8[0] sdb8[1] 6474112 blocks [2/2] [UU] md5 : active raid1 sda7[0] sdb7[1] 14651200 blocks [2/2] [UU] md4 : active raid1 sda6[0] sdb6[1] 995904 blocks [2/2] [UU] md3 : active raid1 sda5[0] sdb5[1] 7815552 blocks [2/2] [UU] md2 : active raid1 sda4[0] sdb4[1] 4996096 blocks [2/2] [UU] md1 : active raid1 sda2[0] sdb2[1] 497920 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 120384 blocks [2/2] [UU] unused devices: none You'll notice that the preferred minor is set correctly: [EMAIL PROTECTED]:~# mdadm -E /dev/sdc /dev/sdc: Magic : a92b4efc Version : 00.90.03 UUID : 71063e4f:f3a0c78b:12a4584b:a8cd9402 Creation Time : Thu Jun 15 15:21:36 2006 Raid Level : raid5 Raid Devices : 6 Total Devices : 6 Preferred Minor : 11 Update Time : Thu Jun 15 15:28:42 2006 State : clean Active Devices : 5 Working Devices : 6 Failed Devices : 1 Spare Devices : 1 Checksum : 54875fd8 - correct Events : 0.48 Layout : left-symmetric Chunk Size : 64K Number
[Bug 49914] Re: initramfs/mdrun doesn't honor preferred minor when starting RAID volumes
This may possibly be an madm/mdrun problem, but I haven't had a chance to investigate whether it's the local-top/md script that's causing it, or if it's mdrun. -- initramfs/mdrun doesn't honor preferred minor when starting RAID volumes https://launchpad.net/bugs/49914 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
