[Bug 1410033] [NEW] nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build
Public bug reported: lsb_release -rd: Description:Ubuntu 14.04.1 LTS Release:14.04 nvidia-331-updates: Installed: 331.113-0ubuntu0.0.4 Candidate: 331.113-0ubuntu0.0.4 Version table: *** 331.113-0ubuntu0.0.4 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted amd64 Packages 100 /var/lib/dpkg/status 331.38-0ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages expected no errors during the update process, received errors and update failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-lowlatency 3.13.11.11 Uname: Linux 3.13.0-43-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Mon Jan 12 22:46:48 2015 InstallationDate: Installed on 2012-08-24 (871 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-08-22 (144 days ago) modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1410033 Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1410033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
Are there any other tests which would be helpful for me to perform? Any other information which may be of use? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
I continue to experience brief locks which are enough to set the kill system responsiveness and set the clock back, but not enough to trigger a watchdog event. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
Aaaand, we just got official: itdept@toolbox:/var/log/apache2$ uname -a Linux toolbox 3.10.0-031000rc5-generic #201306082135 SMP Sun Jun 9 01:36:22 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux itdept@toolbox:/var/log/apache2$ dmesg | tail -n 43 [963607.136016] [ cut here ] [963607.136028] WARNING: at /home/apw/COD/linux/kernel/watchdog.c:245 watchdog_overflow_callback+0x9a/0xc0() [963607.136028] Watchdog detected hard LOCKUP on cpu 1 [963607.136028] Modules linked in: btrfs raid6_pq zlib_deflate xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c reiserfs radeon ttm snd_hda_codec_realtek drm_kms_helper snd_hda_intel drm snd_hda_codec ext2 snd_hwdep snd_pcm i2c_algo_bit snd_timer snd microcode soundcore snd_page_alloc i2c_piix4 shpchp ppdev serio_raw mac_hid parport_pc lp parport hid_generic usbhid hid 8139too 8139cp pata_atiixp pata_acpi sata_sil [963607.136028] CPU: 1 PID: 1013 Comm: kworker/1:2 Not tainted 3.10.0-031000rc5-generic #201306082135 [963607.136028] Hardware name: /D101GGC , BIOS GC11010N.86A.0313.2006.0915.1840 09/15/2006 [963607.136028] Workqueue: events od_dbs_timer [963607.136028] 81a3bf80 88007bc87c18 816c192c 88007bc87c58 [963607.136028] 81044c70 880078064000 [963607.136028] 88007bc87d80 88007bc87ef8 88007bc87cb8 [963607.136028] Call Trace: [963607.136028][] dump_stack+0x19/0x1b [963607.136028] [] warn_slowpath_common+0x70/0xa0 [963607.136028] [] warn_slowpath_fmt+0x46/0x50 [963607.136028] [] watchdog_overflow_callback+0x9a/0xc0 [963607.136028] [] __perf_event_overflow+0x9c/0x220 [963607.136028] [] ? perf_event_update_userpage+0x24/0x110 [963607.136028] [] perf_event_overflow+0x14/0x20 [963607.136028] [] p4_pmu_handle_irq+0x14b/0x220 [963607.136028] [] perf_event_nmi_handler+0x21/0x30 [963607.136028] [] nmi_handle.isra.0+0x59/0x80 [963607.136028] [] default_do_nmi+0x58/0x230 [963607.136028] [] do_nmi+0x90/0xd0 [963607.136028] [] end_repeat_nmi+0x1e/0x2e [963607.136028] [] ? acpi_os_write_port+0x1e/0x30 [963607.136028] [] ? acpi_os_write_port+0x1e/0x30 [963607.136028] [] ? acpi_os_write_port+0x1e/0x30 [963607.136028] <> [] do_drv_write+0x58/0x70 [963607.136028] [] acpi_cpufreq_target+0x201/0x250 [963607.136028] [] ? ns_to_timeval+0x12/0x40 [963607.136028] [] __cpufreq_driver_target+0x46/0x50 [963607.136028] [] dbs_freq_increase+0x42/0x70 [963607.136028] [] od_check_cpu+0x61/0xd0 [963607.136028] [] dbs_check_cpu+0x17d/0x1a0 [963607.136028] [] od_dbs_timer+0x11d/0x180 [963607.136028] [] process_one_work+0x174/0x490 [963607.136028] [] worker_thread+0x11b/0x370 [963607.136028] [] ? manage_workers.isra.20+0x160/0x160 [963607.136028] [] kthread+0xc0/0xd0 [963607.136028] [] ? flush_kthread_worker+0xb0/0xb0 [963607.136028] [] ret_from_fork+0x7c/0xb0 [963607.136028] [] ? flush_kthread_worker+0xb0/0xb0 [963607.136028] ---[ end trace c17c28981e217b1c ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
I have experienced at least one symptom over the weekend (network unresponsiveness) with no logged information. The only observable behavior is that several auto-refreshing web services fail to obtain a response from the server. Wait, breaking news... Add one more symptom. SSH froze, so I began pinging the server and received 'Destination Host Unreachable' for 288 pings, with 5:30 in clock drift and nothing logged to dmesg - or any other log for that matter. ** Tags removed: kernel-fixed-upstream ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
** Changed in: linux (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/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
As noted, I have been running with `apic=debug` in order to boot past a KP tied to my use of `notsc clocksource=acpi_pm`. I have not had any indications of issues for five (5) days (gradually drifting clock, occasional unresponsiveness to ping, CPU hard lock messages in dmesg), so I'm leaning toward 'fixed upstream'. That said, I cannot boot without apic=debug set, so I'll leave it to you to decide if this is truly 'fixed upstream'. Please let me know if there is any further testing I can perform which may be of assistance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
Kernel panic on boot for ACPI timer. KP informed me to boot with apic=debug. My dmesg is attached. ** Attachment added: "dmesg with apic=debug" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+attachment/3702454/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
Has now occurred with acpi_pm, however there is no log entry for a CPU hard lock. System became unresponsive for ~7 minutes. Testing with clocksource=acpi_pm set at boot, and we'll see if the results are the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
Preliminary results suggest no fix, but there's a hiccup: [104371.521583] Clocksource tsc unstable (delta = 468697105616 ns) [104371.548267] Switching to clocksource acpi_pm That's nearly 8 minutes of lost time, with no other indication of a CPU lock. Because of this very issue, my /etc/default/grub previously contained: GRUB_CMDLINE_LINUX="notsc clocksource=acpi_pm" Unbeknownst to me, his had been auto-commented as part of the 3.10 installation. Now that we're back on acpi_pm, we'll see what happens. It would make sense that the tsc issue and my hard locks are tied to the same cause, but as I understand tsc is unstable for Pentium D and should be avoided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
Installed and waiting, but it could be days (weeks?) before the problem manifests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] Re: Random CPU hard locks on Intel D101GGC w/12.04 Server
The given apport-collect command does not seem to work, even with sudo. ** Changed in: linux (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/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189565] [NEW] Random CPU hard locks on Intel D101GGC w/12.04 Server
Public bug reported: itdept@toolbox:~$ lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 itdept@toolbox:/var/log$ apt-cache policy linux linux: Installed: (none) Candidate: 3.2.0.45.54 Version table: 3.2.0.45.54 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 3.2.0.23.25 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages itdept@toolbox:/var/log$ apt-cache policy linux-generic-lts-quantal linux-generic-lts-quantal: Installed: 3.5.0.32.39 Candidate: 3.5.0.32.39 Version table: *** 3.5.0.32.39 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status Following a clean install of 12.04 Server, I was experiencing seemingly random 'hard LOCKUP's on my machine. The computer would become unresponsive for several minutes at a time, and something like this would show up in dmesg: [1509353.540014] [ cut here ] [1509353.540014] WARNING: at /build/buildd/linux-lts-quantal-3.5.0/kernel/watchdog.c:242 watchdog_overflow_callback+0x9a/0xc0() [1509353.540014] Hardware name: [1509353.540014] Watchdog detected hard LOCKUP on cpu 1 [1509353.540014] Modules linked in: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs radeon snd_hda_codec_realtek snd_hda_intel snd_hda_codec ttm snd_hwdep drm_kms_helper snd_pcm drm snd_timer snd ext2 soundcore i2c_algo_bit i2c_piix4 snd_page_alloc serio_raw shpchp microcode mac_hid ppdev parport_pc lp parport hid_generic usbhid 8139too hid 8139cp sata_sil pata_atiixp [1509353.540014] Pid: 21317, comm: kworker/1:0 Tainted: GW 3.5.0-30-generic #51~precise1-Ubuntu [1509353.540014] Call Trace: [1509353.540014][] warn_slowpath_common+0x7f/0xc0 [1509353.540014] [] warn_slowpath_fmt+0x46/0x50 [1509353.540014] [] watchdog_overflow_callback+0x9a/0xc0 [1509353.540014] [] __perf_event_overflow+0x9c/0x220 [1509353.540014] [] ? perf_event_update_userpage+0x24/0x110 [1509353.540014] [] perf_event_overflow+0x14/0x20 [1509353.540014] [] p4_pmu_handle_irq+0x125/0x210 [1509353.540014] [] perf_event_nmi_handler+0x21/0x30 [1509353.540014] [] nmi_handle.isra.0+0x51/0x80 [1509353.540014] [] default_do_nmi+0x58/0x240 [1509353.540014] [] do_nmi+0x90/0xd0 [1509353.540014] [] end_repeat_nmi+0x1a/0x1e [1509353.540014] [] ? acpi_os_write_port+0x1e/0x30 [1509353.540014] [] ? acpi_os_write_port+0x1e/0x30 [1509353.540014] [] ? acpi_os_write_port+0x1e/0x30 [1509353.540014] <> [] do_drv_write+0x2d/0x70 [1509353.540014] [] acpi_cpufreq_target+0x251/0x2a0 [1509353.540014] [] __cpufreq_driver_target+0x42/0x50 [1509353.540014] [] dbs_check_cpu+0x28f/0x330 [1509353.540014] [] do_dbs_timer+0xa1/0x110 [1509353.540014] [] process_one_work+0x127/0x470 [1509353.540014] [] worker_thread+0x165/0x370 [1509353.540014] [] ? manage_workers.isra.29+0x130/0x130 [1509353.540014] [] kthread+0x93/0xa0 [1509353.540014] [] kernel_thread_helper+0x4/0x10 [1509353.540014] [] ? flush_kthread_worker+0xb0/0xb0 [1509353.540014] [] ? gs_change+0x13/0x13 [1509353.540014] ---[ end trace 31bbfa84b207ef07 ]--- Following installation of a BIOS update, the logged lockups are less frequent (twice in 20 days, as opposed to several times per day) and far more brief (haven't caught one in progress since, as opposed to being unable to do anything but wait for 5-10 minutes per occurrence) but are still occurring. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "output of "ubuntu-bug linux"" https://bugs.launchpad.net/bugs/1189565/+attachment/364/+files/apport.linux-image-3.5.0-30-generic.PBCuIZ.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189565 Title: Random CPU hard locks on Intel D101GGC w/12.04 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824133] Re: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824133 Title: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/824133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824133] [NEW] package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
Public bug reported: This compilation issue is tied to the linux-lowlatency ppa managed by bogani. The issue exists only in the recent kernel 3.0.0 releases. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: nvidia-current 270.41.06-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Aug 10 13:59:27 2011 DistUpgraded: Log time: 2011-05-05 14:33:50.559728 DistroCodename: natty DistroVariant: ubuntu ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) PackageVersion: 270.41.06-0ubuntu1 SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build UpgradeStatus: Upgraded to natty on 2011-05-05 (96 days ago) version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 version.ia32-libs: ia32-libs 20090808ubuntu13 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 7.10.2-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty needs-reassignment regression-update ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824133 Title: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/824133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306371] Re: wireless signal strength reported as extremely high when it should be extremely low
Ubuntu 8.10, 2.6.27-9-generic, fully updated as of Mon Dec 8 18:47:22 CST 2008 -- wireless signal strength reported as extremely high when it should be extremely low https://bugs.launchpad.net/bugs/306371 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 306371] [NEW] wireless signal strength reported as extremely high when it should be extremely low
Public bug reported: This can be observed both through iwlist and NM. A wireless network's signal strength is the difference between the signal level and the noise level in dBm. This is one of the current networks listed through use of 'iwlist ath0 scanning': Cell 03 - Address: 00:19:2F:A0:53:50 ESSID:"" Mode:Master Frequency:2.422 GHz (Channel 3) Quality=195/70 Signal level=-156 dBm Noise level=-95 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s Extra:bcn_int=100 The quality is being reported as 195/70, but in reality should effectively be 0. In cases where the signal strength is one less than the noise level (ex. signal=-96dBm, noise=-95dBm), the signal is reported as 255/70 and the Network Manager will indicate full signal strength for the access point. Methinks the 255 is a dead giveaway... ** Affects: ubuntu Importance: Undecided Status: New -- wireless signal strength reported as extremely high when it should be extremely low https://bugs.launchpad.net/bugs/306371 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 257985] [NEW] Pressing mute button on Thinkpad R61 causes microphone to mute/unmute
Public bug reported: Description:Ubuntu 8.04.1 Release:8.04 This bug appears in the standard Volume Control applet. When using the keyboard mute/unmute button, the Microphone playback mute status is controlled along with the Master and PCM mute status. This means that if the Microphone has been independently muted, it will be unmuted if the keyboard mute/unmute button is used to mute then unmute the Master and PCM. The Microphone playback was muted so the sound of typing would not play through my headphones. I needed to speak with someone, so I pressed the mute button on my keyboard. This muted the Master and PCM playback, as was expected. When I finished my conversation I pressed the same button to unmute Master and PCM playback. Microphone playback was automatically unmuted. I expected the Microphone to remain muted. I had expected the mute/unmute button would only change the mute status of the Master playback. ** Affects: ubuntu Importance: Undecided Status: New -- Pressing mute button on Thinkpad R61 causes microphone to mute/unmute https://bugs.launchpad.net/bugs/257985 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 244699] [NEW] "Downloads Complete" dialog box in Firefox 3.0 covers the virtual desktop selector
Public bug reported: Description:Ubuntu 8.04.1 Release:8.04 firefox: Installed: 3.0+nobinonly-0ubuntu0.8.04.1 Candidate: 3.0+nobinonly-0ubuntu0.8.04.1 Version table: *** 3.0+nobinonly-0ubuntu0.8.04.1 0 500 http://us.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 3.0~b5+nobinonly-0ubuntu3 0 500 http://us.archive.ubuntu.com hardy/main Packages gnome: Installed: (none) Candidate: 1:2.20.2.2 Version table: 1:2.20.2.2 0 500 http://us.archive.ubuntu.com hardy/universe Packages xorg: Installed: 1:7.3+10ubuntu10 Candidate: 1:7.3+10ubuntu10 Version table: *** 1:7.3+10ubuntu10 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status Whenever a download completes in Mozilla Firefox 3, a notification slides up the bottom right-hand corner of the screen. This obscures the virtual desktop selector, which is more than a minor nuisance. I am unsure of whether this should be classified as a Firefox 3.0 issue (should be more selective of where it draws the notification), a GNOME issue (should be more restrictive of where it allows things to be drawn), or an X.org issue (shouldn't allow things to 'cover' layers at the top). That's for someone a bit wiser than me to decide! A more pleasant behavior would be for the notification to be drawn either from the top of the lower menu bar (if one exists), or to be drawn from the base of the Firefox 3.0 window. ** Affects: ubuntu Importance: Undecided Status: New -- "Downloads Complete" dialog box in Firefox 3.0 covers the virtual desktop selector https://bugs.launchpad.net/bugs/244699 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
Re: [Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
Unfortunately, even with working DRI you won't be seeing any desktop effects. Those effects require very specific off-screen rendering functionality of which Mach64 cards are not capable. You will, however, see a fairly drastic boost in more 'general' OpenGL functionality. Your situation brings up another reason why this bug isn't likely to be closed anytime soon: Mach64 DRI seems to be hit or miss with results being insignificant to most users. As for additional tips... no clue, really. In my /etc/X11/xorg.conf I have the following changed, and I really have no clue if it makes a difference (meaning I'm too lazy to test, sorry!): (In Section ServerLayout make sure the following is commented out if it exists) #Option "AIGLX" "False" (The following section may need to be added if it is not present, but I believe it's there by default in newer Ubuntus) Section "DRI" Mode 0666 EndSection For more rigorous (and involved) instructions, check for earlier posts from me in the bug notes. There are instructions for replacing libGL in the case that it is the culprit. However, I really am hoping the DRM modules were all that needed to be compiled... -Philip On Wed, Mar 12, 2008 at 5:19 PM, Roland Arendes <[EMAIL PROTECTED]> wrote: > Your hint seems to have brought me one step further. I compiled both > modules successfully, rebooted, and now have some lines in the Xorg.log > that indicate that DRI should work - > > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 8, (OK) > drmOpenByBusid: Searching for BusID pci::01:00.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 8, (OK) > drmOpenByBusid: drmOpenMinor returns 8 > drmOpenByBusid: drmGetBusid reports pci::01:00.0 > (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 > (II) AIGLX: Loaded and initialized /usr/lib/dri/mach64_dri.so > (II) GLX: Initialized DRI GL provider for screen 0 > Atom 4, CARD32 4, unsigned long 4 > > However, enabling Desktop effects does not work. As you guessed, I have > a 1024x768 TFT LCD with 8megs of RAM. I moved to 16bits beforehand. > > [EMAIL PROTECTED]:/var/log$ glxinfo | grep direct > Locking assertion failure. Backtrace: > #0 /usr/lib/libxcb-xlib.so.0 [0xb7c61767] > #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x31) [0xb7c618b1] > #2 /usr/lib/libX11.so.6 [0xb7cf7421] > #3 /usr/X11R6/lib/libGL.so.1(__glXInitialize+0x596) [0xb7f2d3cc] > #4 /usr/X11R6/lib/libGL.so.1 [0xb7f29fc8] > #5 /usr/X11R6/lib/libGL.so.1(glXChooseVisual+0x29) [0xb7f2b124] > #6 glxinfo [0x8049448] > #7 glxinfo [0x8049b23] > #8 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7db5450] > #9 glxinfo [0x8048d51] > direct rendering: No (If you want to find out why, try setting > LIBGL_DEBUG=verbose. > > -- > DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 > https://bugs.launchpad.net/bugs/34590 > You received this bug notification because you are a direct subscriber > of the bug. > -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 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
Re: [Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
I may be off on the dependencies (only the Linux kernel headers, GCC & make stuffs, and git, I believe), but you should be able to get by in Feisty and Hardy with minimal building from sources. From what I can tell nothing needs to be compiled except mach64.ko, and drm.ko needs a recompilation. The instructions are fairly straight-forward (assuming you've already apt-get'd the aforementioned stuffs): (terminal) git clone git://anongit.freedesktop.org/git/mesa/drm cd drm/linux-core make mach64.o (that's not a typo, and this builds drm.ko & mach64.ko) sudo cp *.ko /lib/modules//kernel/drivers/char/drm/ sudo depmod -n (reboot and glxinfo | grep "direct") Oh yeah, and make sure your default bit depth is right ahead of time. [EMAIL PROTECTED] is the best you can hope for with 8MB. I don't think you can do much of anything with 4MB. When the kernel is officially updated, a simple depmod will not suffice. You will need to recompile the mach64.ko module. It doesn't take long. May as well update the sources, anyhow. Can someone confirm these instructions from a fresh(er) install, and, more specifically, post a definitive list for apt-get prior to building? -Philip On Mon, Mar 10, 2008 at 6:01 PM, Roland Arendes <[EMAIL PROTECTED]> wrote: > I second that. Just trying to get my old laptop with an ATI mach64 > mobility to work in DRI mode in hardy alpha 6, but no chance. mach64.ko > is still missing and I'm not able to compile the rather old snapshots > from http://dri.freedesktop.org/snapshots/ due to compilation problems > with the hardy kernel. > > Any idea when this will be fixed for hardy? There isn't much time left. > > -- > DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 > https://bugs.launchpad.net/bugs/34590 > You received this bug notification because you are a direct subscriber > of the bug. > -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 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
Re: [Bug 97172] Re: Fix for DWL-650 Rev P1 (hostap_cs)
Daniel, This is no longer a bug. The card works fine in Linux kernel 2.6.22 or newer. -Philip On Feb 6, 2008 9:09 AM, Daniel Holbach <[EMAIL PROTECTED]> wrote: > To get your fix included in Ubuntu, try transforming it into a debdiff > (http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submitting > it for review (http://wiki.ubuntu.com/SponsorshipProcess). > > Setting to 'incomplete' for now. > > ** Changed in: hostap (Ubuntu) > Status: New => Incomplete > > -- > Fix for DWL-650 Rev P1 (hostap_cs) > https://bugs.launchpad.net/bugs/97172 > You received this bug notification because you are a direct subscriber > of the bug. > -- Fix for DWL-650 Rev P1 (hostap_cs) https://bugs.launchpad.net/bugs/97172 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
Re: [Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
In Gutsy all you need to compile is the mach64.ko DRM module (git'd from freedesktop.org), as all of the other modules are compiled 'correctly'. It is possible this is all that matters in Hardy, as well. The main reason nothing can realistically be done about this bug (which pains me!) is the fact that mach64.ko is not part of the Linux kernel source. While X.org moves to DRI2, we could see this resolved. Presently, mach64.ko (DRI/DRM for Mach64) is not considered to be a 'secure' module. I have no idea why this is. -Philip Barton On Dec 1, 2007 9:38 PM, jotronic <[EMAIL PROTECTED]> wrote: > I couldn't really follow the howto and got stuck at the " Package > xserver-xorg-video-ati backported from gutsy and compiled with --enable- > dri ". However, I just installed the "Hardy" - Alpha and of course no > DRI support for mach64. Is this Bug beeing ignored? > > -- > DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 > https://bugs.launchpad.net/bugs/34590 > You received this bug notification because you are a direct subscriber > of the bug. > -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 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 157351] Network Manager reports "no network connection" even when a PPP connection is active
Public bug reported: Binary package hint: network-manager Disclaimed: I use my cell phone to connect to the Internet via PPP, using the "Modem Connection" option within Manual Configuration. When the connection to the Internet is established, either by opening "Manual Configuration" and checking the "Modem Connection" option or by selecting "Dial Up Connections"->"Connect to ppp0 via Modem" the connection is established and quit usable. I can see that my routing table has been correctly updated, can browse web pages, use SSH, apt- get, etc... but Network Manager still reports "No network connection", and applications that depend on Network Manager reporting the existence of a connection refuse to function normally. Pidgin is one example: it will simply show "Waiting for network connection" in its status area and refuse to attempt connecting to any services. If this is normal/expected behavior for Network Manager, please re- assign this bug to Pidgin. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Network Manager reports "no network connection" even when a PPP connection is active https://bugs.launchpad.net/bugs/157351 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
Re: [Bug 123292] Re: info regarding firmware for DWL-650 Rev. P1
I've created a udev rule which works quite well for this card. It is
attached. It depends on the firmware being saved in /lib/firmware// as prism2-pm010102.hex and prism2-rf010804.hex.
At present this works for me. I don't know how many cards out there need
the same firmware files and depend on prism2_srec, but rules could be
created for them fairly easily following the same pattern.
I do not know if there is a better way to get `uname -r` into udev than how
I'm doing it. It did not appear to be one of the ENV{} variables...
-Philip
On 10/10/07, Philip Barton <[EMAIL PROTECTED]> wrote:
>
> There is a firmware loading script for hostap which can be viewed here:
>
> http://pyramid.metrix.net/svn/Pyramid/dist/sbin/hostap_fw_load
>
> As I understand, this came as an example with the source prior to the
> hostap driver being included with the kernel sources. prism2_srec is still
> the utility that is used when fw_primary and fw_secondary are specified in
> /etc/network/interfaces, I believe.
>
> I hope this information is of some use... Every time I switch my wireless
> to roaming mode, my /etc/network/interfaces entries for fw_primary and
> fw_secondary are deleted. It's quite a pain!
>
> Is this something that can be implemented with udev rules?
>
> -Philip
>
> On 9/18/07, Philip Barton <[EMAIL PROTECTED]> wrote:
> >
> > Martin, I hope I can provide some useful information to you!
> >
> > * Is this associated with a particular kernel module?
> > >
> > Yes! hostap_cs.ko is the module in question.
> >
> > * I wouldn't like to modify /etc/network/interfaces, because that would
> > > make the setup incompatible with network-manager. Usually they should
> > > be
> > > put into /lib/firmware//, and the kernel module should
> > > load them automatically. If that works, it would be much preferable.
> > > If
> > > it doesn't work, I can also do the modification of the interfaces
> > > file.
> > >
> > I understand... I have no clue how the firmware is being handled by
> > hostap_cs, though, or if it is even handling the firmware! What I do know
> > is that there are many revisions of the firmware, and any of them can be
> > used with varying degrees of stability. Since every firmware version has
> > its version number in its filename, I have no idea whether hostap_cs is
> > looking for a default firmware filename before using the filenames specified
> > in /etc/network/interfaces.
> >
> > Despite lacking a default filename, I went ahead and put the firmware
> > files I had been using in /lib/firmware//, rebooted, and...
> > nothing. I will do some digging within hostap and hostap_cs for more info.
> >
> > Thanks!
> >
> > -Philip Barton
> >
> > On 9/18/07, Martin Pitt < [EMAIL PROTECTED] > wrote:
> > >
> > > Thank you for that information, but I need some more, I'm afraid:
> > >
> > > * Is this associated with a particular kernel module?
> > >
> > > * I wouldn't like to modify /etc/network/interfaces, because that
> > > would
> > > make the setup incompatible with network-manager. Usually they should
> > > be
> > > put into /lib/firmware//, and the kernel module should
> > > load them automatically. If that works, it would be much preferable.
> > > If
> > > it doesn't work, I can also do the modification of the interfaces
> > > file.
> > >
> > > --
> > > info regarding firmware for DWL-650 Rev. P1
> > > https://bugs.launchpad.net/bugs/123292
> > > You received this bug notification because you are a direct subscriber
> > >
> > > of the bug.
> > >
> >
> >
>
--
info regarding firmware for DWL-650 Rev. P1
https://bugs.launchpad.net/bugs/123292
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
Re: [Bug 123292] Re: info regarding firmware for DWL-650 Rev. P1
There is a firmware loading script for hostap which can be viewed here: http://pyramid.metrix.net/svn/Pyramid/dist/sbin/hostap_fw_load As I understand, this came as an example with the source prior to the hostap driver being included with the kernel sources. prism2_srec is still the utility that is used when fw_primary and fw_secondary are specified in /etc/network/interfaces, I believe. I hope this information is of some use... Every time I switch my wireless to roaming mode, my /etc/network/interfaces entries for fw_primary and fw_secondary are deleted. It's quite a pain! Is this something that can be implemented with udev rules? -Philip On 9/18/07, Philip Barton <[EMAIL PROTECTED]> wrote: > > Martin, I hope I can provide some useful information to you! > > * Is this associated with a particular kernel module? > > > Yes! hostap_cs.ko is the module in question. > > * I wouldn't like to modify /etc/network/interfaces, because that would > > make the setup incompatible with network-manager. Usually they should be > > put into /lib/firmware//, and the kernel module should > > load them automatically. If that works, it would be much preferable. If > > it doesn't work, I can also do the modification of the interfaces file. > > > I understand... I have no clue how the firmware is being handled by > hostap_cs, though, or if it is even handling the firmware! What I do know > is that there are many revisions of the firmware, and any of them can be > used with varying degrees of stability. Since every firmware version has > its version number in its filename, I have no idea whether hostap_cs is > looking for a default firmware filename before using the filenames specified > in /etc/network/interfaces. > > Despite lacking a default filename, I went ahead and put the firmware > files I had been using in /lib/firmware//, rebooted, and... > nothing. I will do some digging within hostap and hostap_cs for more info. > > Thanks! > > -Philip Barton > > On 9/18/07, Martin Pitt < [EMAIL PROTECTED] > wrote: > > > > Thank you for that information, but I need some more, I'm afraid: > > > > * Is this associated with a particular kernel module? > > > > * I wouldn't like to modify /etc/network/interfaces, because that would > > make the setup incompatible with network-manager. Usually they should be > > > > put into /lib/firmware//, and the kernel module should > > load them automatically. If that works, it would be much preferable. If > > it doesn't work, I can also do the modification of the interfaces file. > > > > -- > > info regarding firmware for DWL-650 Rev. P1 > > https://bugs.launchpad.net/bugs/123292 > > You received this bug notification because you are a direct subscriber > > of the bug. > > > > -- info regarding firmware for DWL-650 Rev. P1 https://bugs.launchpad.net/bugs/123292 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
Re: [Bug 123292] Re: info regarding firmware for DWL-650 Rev. P1
Martin, I hope I can provide some useful information to you! * Is this associated with a particular kernel module? > Yes! hostap_cs.ko is the module in question. * I wouldn't like to modify /etc/network/interfaces, because that would > make the setup incompatible with network-manager. Usually they should be > put into /lib/firmware//, and the kernel module should > load them automatically. If that works, it would be much preferable. If > it doesn't work, I can also do the modification of the interfaces file. > I understand... I have no clue how the firmware is being handled by hostap_cs, though, or if it is even handling the firmware! What I do know is that there are many revisions of the firmware, and any of them can be used with varying degrees of stability. Since every firmware version has its version number in its filename, I have no idea whether hostap_cs is looking for a default firmware filename before using the filenames specified in /etc/network/interfaces. Despite lacking a default filename, I went ahead and put the firmware files I had been using in /lib/firmware//, rebooted, and... nothing. I will do some digging within hostap and hostap_cs for more info. Thanks! -Philip Barton On 9/18/07, Martin Pitt <[EMAIL PROTECTED] > wrote: > > Thank you for that information, but I need some more, I'm afraid: > > * Is this associated with a particular kernel module? > > * I wouldn't like to modify /etc/network/interfaces, because that would > make the setup incompatible with network-manager. Usually they should be > put into /lib/firmware//, and the kernel module should > load them automatically. If that works, it would be much preferable. If > it doesn't work, I can also do the modification of the interfaces file. > > -- > info regarding firmware for DWL-650 Rev. P1 > https://bugs.launchpad.net/bugs/123292 > You received this bug notification because you are a direct subscriber > of the bug. > -- info regarding firmware for DWL-650 Rev. P1 https://bugs.launchpad.net/bugs/123292 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 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
The reason you won't see it in Gutsy is that Mach64's DRM module is not within the vanilla kernel sources. You can confirm this by checking git.kernel.org. For the current kernel release, the link is http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.22.y.git;a=tree;f=drivers/char/drm;hb=HEAD. None of the source files there are related to Mach64. The best course of action would likely be to lobby the dri.freedesktop.org maintainers to submit Mach64 DRM sources to the Linux kernel maintainers to be included as 'EXPERIMENTAL'. Once Mach64 sources are included with the Linux kernel sources, you can likely expect to see the module included in Ubuntu. -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 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 123292] info regarding firmware for DWL-650 Rev. P1
Public bug reported: Binary package hint: restricted-manager THIS IS NOT A BUG... but it does fall within the goals of this project. This is just some information regarding a device that needs firmware loaded as the last leg for full support in Ubuntu: The D-Link DWL-650 Rev. P1. This PCMCIA wireless card is correctly recognized in Linux kernel 2.6.22, but not prior. As such, it works in Gutsy Gibbon but still requires firmware. The firmware is available at http://www.red-bean.com/~proski/firmware/. The file archive that contains the necessary firmware is latest- prism.tar.bz2, and the two files needed are pm010102.hex and rf010804.hex. The final setup is to change the wlan interface, which in my case looks like this: auto wlan0 iface wlan0 inet dhcp fw_primary /lib/firmware/dwl-650/pm010102.hex fw_secondary /lib/firmware/dwl-650/rf010804.hex Following a reboot, the card works 100%. Additional info that may be useful is the output of lspcmcia -vvv: Socket 1 Device 0: [hostap_cs] (bus ID: 1.0) Configuration: state: on Product Name: D-Link DWL-650 Wireless PC Card RevP ISL37101P-10 A3 Identification: manf_id: 0x000b card_id: 0x7110 function: 6 (network) prod_id(1): "D-Link" (0x1a424a1c) prod_id(2): "DWL-650 Wireless PC Card RevP" (0x6ea57632) prod_id(3): "ISL37101P-10" (0xdd97a26b) prod_id(4): "A3" (0x56b21f52) -Philip ** Affects: restricted-manager (Ubuntu) Importance: Undecided Status: New -- info regarding firmware for DWL-650 Rev. P1 https://bugs.launchpad.net/bugs/123292 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 97172] Re: Fix for DWL-650 Rev P1 (hostap_cs)
This is fixed as of Linux kernel 2.6.22. This card still requires that firmware be loaded, but there's nothing Ubuntu can do about that while remaining within their policies. -- Fix for DWL-650 Rev P1 (hostap_cs) https://bugs.launchpad.net/bugs/97172 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 122381] NetworkManager crashed with signal 5
Public bug reported: Binary package hint: network-manager No exact steps to reproduce, but if it is of any help I had just finished applying a set of updates via apt-get, and was moving on to install a kernel update via the Update Manager. I had Firefox and Pidgin running at the time. That probably didn't help at all. Sorry. ProblemType: Crash Architecture: i386 CoreDump: Date: Sun Jun 24 10:58:17 2007 Disassembly: DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/sbin/NetworkManager NonfreeKernelModules: cdrom Package: network-manager 0.6.5-0ubuntu4 PackageArchitecture: i386 ProcCmdline: /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid ProcCwd: / ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin LANG=en_US.UTF-8 SHELL=/bin/bash Registers: Signal: 5 SourcePackage: network-manager Stacktrace: StacktraceTop: ThreadStacktrace: Title: NetworkManager crashed with signal 5 Uname: Linux Othniel 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux UserGroups: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash need-i386-retrace -- NetworkManager crashed with signal 5 https://bugs.launchpad.net/bugs/122381 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 122381] Re: NetworkManager crashed with signal 5
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/8210598/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/8210599/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/8210600/ProcStatus.txt -- NetworkManager crashed with signal 5 https://bugs.launchpad.net/bugs/122381 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 122377] Re: evince crashed with SIGSEGV
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/8210583/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/8210584/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/8210585/ProcStatus.txt -- evince crashed with SIGSEGV https://bugs.launchpad.net/bugs/122377 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 122377] evince crashed with SIGSEGV
Public bug reported: Binary package hint: evince I was unaware that the Document Viewer was even trying to open, so I have no further information for you. Sorry! ProblemType: Crash Architecture: i386 CoreDump: Date: Tue Jun 26 12:19:21 2007 Disassembly: DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/evince NonfreeKernelModules: cdrom Package: evince 0.9.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: /usr/bin/evince /tmp/undmap.pdf ProcCwd: /home/pbarton ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Registers: Signal: 11 SourcePackage: evince Stacktrace: StacktraceTop: ThreadStacktrace: Title: evince crashed with SIGSEGV Uname: Linux Othniel 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash need-i386-retrace -- evince crashed with SIGSEGV https://bugs.launchpad.net/bugs/122377 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
Re: [Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
the version you are compiling is geared towards either x.org 6.9 or 7.0, the newer versions (used in 7.04 and such) are for x.org 7.2. you could search around at freedesktop.org for a list of things that have changed in the architecture, as well as specifics for the mach64 driver. -Philip On 5/16/07, Alvaro Pintos Pena <[EMAIL PROTECTED]> wrote: > > Thanks audiophyl! > > But finally I could compile the driver mach64-20060403-linux.i386 and > now I have the 3D acceleration :) > > anyway, which is the diffrence between this version of the driver and > the other? > > -- > DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 > https://bugs.launchpad.net/bugs/34590 > You received this bug notification because you are a direct subscriber > of the bug. > -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 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
Re: [Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
The main problem I can see with what you're trying is that you're using sources that area over one year old. "mach64-20060403-linux.i386" = 3rd of April, 2006. Check http://ubuntuforums.org/showthread.php?p=2399695#post2399695 for more current information (this may not work with 6.10, but does work with 7.04) -Philip On 5/15/07, Alvaro Pintos Pena <[EMAIL PROTECTED]> wrote: > > Ralf, very thanks for your help. > > I did most removed the linux/config.h entry from various files but now I > have another problem that I couldn't revolv it: > > /usr/src/mach64-20060403-linux.i386/drm/linux-core/drm_stub.c:51: error: > size of array 'type name' is negative > > In the log appears the complete problem. Very thanks again for your help > > ** Attachment added: "log mach64 compile" > http://librarian.launchpad.net/7649730/dri.log > > -- > DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 > https://bugs.launchpad.net/bugs/34590 > You received this bug notification because you are a direct subscriber > of the bug. > -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 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 111190] hotkey: "volume down" is non-functional for sony vaio pcg-fx210
Public bug reported: Binary package hint: hotkey-setup The hotkey for turning the volume down is not recognized on a Sony Vaio PCG-FX210 (and likely other PCG-FX models). The keypress is: Shift + 0xae >From dmidecode: Sony Corporation PCG-FX210(UC) 01 Thanks, -Philip Barton ** Affects: hotkey-setup (Ubuntu) Importance: Undecided Status: Unconfirmed -- hotkey: "volume down" is non-functional for sony vaio pcg-fx210 https://bugs.launchpad.net/bugs/90 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 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
The instructions given in the OP won't (and shouldn't) work in Feisty Fawn due to changes in the structure of X.org. As I understand, there are security concerns regarding the mach64.ko DRM module needed for enabling DRI. Of course, there are security concerns with binary blobs, but it's much easier to install some of those! Enabling DRI with Mach64-based graphics seems to be an important enough topic to have garnered 101 posts and more than 53,000 views at http://ubuntuforums.org/showthread.php?t=7200. Maybe it could be considered more than a "wishlist" item... especially since working code exists and has existed for quite some time. Might I propose this solution: Build mach64.ko along with the rest of the DRM modules (/lib/modules/$KERNEL/kernel/drivers/char/drm/), but blacklist it in /etc/modprobe.d/blacklist along with an explanation regarding the security concerns. That would make Ubuntu secure by default, but allow the functionality to be easily enabled for those who aren't as concerned with the security implications. As a side note, the security concerns don't appear to be well documented. By this, I mean that I can't seem to find anything other than "there are security concerns" as an explanation. That sure doesn't help to get the point across! :) -Philip Barton -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 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 99153] Typo in "Distribution Upgrade" window
Public bug reported: The "Distribution Upgrade" window that has popped up in order for the update of OpenOffice to happen (Feisty Beta) is telling me that it is "*Runing* partial upgrade". This should be "*Running* partial upgrade". Not a show stopper, but it's definitely nice to have spelling correct. This should be "Running" in all English locales. ProblemType: Bug Architecture: i386 Date: Fri Mar 30 14:46:10 2007 DistroRelease: Ubuntu 7.04 Uname: Linux othniel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Typo in "Distribution Upgrade" window https://launchpad.net/bugs/99153 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97172] Fix for DWL-650 Rev P1 (hostap_cs)
Public bug reported: I have detailed my whole account of getting my card to work at: http://sin613.blogspot.com/2007/02/i-win.html http://sin613.blogspot.com/2007/02/i-win-again.html The quick summary is that hostap_cs.c is missing the correct device IDs for this card, but has a similar ID labeled as being the correct card. I e-mailed Jouni Malinen (maintainer) regarding the problem and received the following response: On Mon, Feb 26, 2007 at 10:59:08PM -0600, Phil Barton wrote: > I'm not sure if you are the person I need to contact regarding this, but I > have found that hostap_cs.c needs a small change in order to work with the > D-Link DWL-650 Rev P1 PCMCIA card. Specifically, device 000B 7110 needs to > be recognized (I don't know if 000B 7100 is the right device for revisions > of this card earlier than P1, and orinoco_cs lists this device 000B 7100 as > a "SonicWALL Long Range Wireless Card"). Thanks for reporting this. It looks like DWL-650 Rev P1 id was lost when Host AP driver was converted to use the new pcmcia mechanism for selecting the driver. I submitted the attached patch to add it back. It has been over a month now, and several kernel revisions later the support for this device is still broken. Perhaps Ubuntu could assist in setting things straight... Jouni also forwarded the patch that would fix this to me, which I can send to anyone who is interested. It's a rather simple fix. -Philip Barton ** Affects: hostap (Ubuntu) Importance: Undecided Status: Unconfirmed -- Fix for DWL-650 Rev P1 (hostap_cs) https://launchpad.net/bugs/97172 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97172] Re: Fix for DWL-650 Rev P1 (hostap_cs)
** Attachment added: "Patch from Jouni Malinenfor hostap_cs.c" http://librarian.launchpad.net/7029591/hostap_dwl650_revp.patch -- Fix for DWL-650 Rev P1 (hostap_cs) https://launchpad.net/bugs/97172 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90013] Re: [apport] gaim crashed with SIGSEGV
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/6640813/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/6640814/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/6640815/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/6640816/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/6640817/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/6640818/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/6640819/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/6640820/ThreadStacktrace.txt -- [apport] gaim crashed with SIGSEGV https://launchpad.net/bugs/90013 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90013] [apport] gaim crashed with SIGSEGV
Public bug reported: Binary package hint: gaim don't know how to reproduce... gaim just wouldn't finish starting (buddy list was all white instead of showing any buddies) and then crashed. ProblemType: Crash Architecture: i386 Date: Mon Mar 5 22:09:12 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gaim Package: gaim 1:2.0.0+beta6-1ubuntu1 PackageArchitecture: i386 ProcCmdline: gaim ProcCwd: /home/pbarton ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gaim StacktraceTop: ?? () ?? () ?? () ?? () ?? () from /lib/tls/i686/cmov/libpthread.so.0 Uname: Linux othniel 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: gaim (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] gaim crashed with SIGSEGV https://launchpad.net/bugs/90013 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68291] Solution for working tdfx_drv.so + 3D (i386)
Hello everyone, I just finished upgrading to Edgey Eft last night and have a working install with a Voodoo Banshee. I did have to use the alternate install, but the solution was rather simple: 1) Start using "recovery mode" 2) run "wget ftp.debian.org/debian/pool/main/x/xserver-xorg-video-tdfx/xserver-xorg-video-tdfx_1.3.0-1_i386.deb" (it is possible this will work with amd64, i just don't have a 64 bit machine to try it on) 3) run "dpkg-deb --extract xserver-xorg-video-tdfx_1.3.0-1_i386.deb temp" 4) run "mv /usr/lib/xorg/modules/drivers/tdfx_drv.so /usr/lib/xorg/modules/drivers/tdfx_drv.so.bak" 5) run "cp temp/usr/lib/xorg/modules/drivers/tdfx_drv.so /usr/lib/xorg/modules/drivers/tdfx_drv.so" 6) run "nano /etc/apt/sources.list" 7) Look for the section regarding enabling the "universe" repository, as this repository contains libglide3 (libglide3 is for Voodoo3 and newer, Voodoo2 users need libglide2), which you will need for 3D acceleration. You will need to uncomment two lines, then Ctrl+O (write out) and Ctrl-X (exit) 8) run "apt-get update" 9) run "apt-get install libglide3" (or libglide2, note #7) 10) run "apt-get upgrade" (you may as well do this now instead of when you restart) 11) run "reboot" That should be it. You're using the 1.3.0 tdfx_drv.so instead of the 1.2.1, but it has the correct symbols being exported so things work correctly. The only problem with 1.2.1 is the "getsecs" symbol not being exported, which is confirmable if you had tailed /var/log/gdm/(whatever the log file is). The error does not show in the Xorg log. I imagine that the newer Xorg will be used for Feisty, and it's entirely possible that a fixed Xorg will be delivered to users of Edgy. It's less than optimal to be using a different version of the driver, but in this case it is necessary as tdfx_drv.so is just plain broken (for *all* distributions using the 1.2.1 version). -Philip -- GDM Restarts after Desktop loads while using tdfx driver https://launchpad.net/bugs/68291 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63796] Solution for working tdfx_drv.so + 3D (i386)
*** This bug is a duplicate of bug 68291 *** Hello everyone, I just finished upgrading to Edgey Eft last night and have a working install with a Voodoo Banshee. I did have to use the alternate install, but the solution was rather simple: 1) Start using "recovery mode" 2) run "wget ftp.debian.org/debian/pool/main/x/xserver-xorg-video-tdfx/xserver-xorg-video-tdfx_1.3.0-1_i386.deb" (it is possible this will work with amd64, i just don't have a 64 bit machine to try it on) 3) run "dpkg-deb --extract xserver-xorg-video-tdfx_1.3.0-1_i386.deb temp" 4) run "mv /usr/lib/xorg/modules/drivers/tdfx_drv.so /usr/lib/xorg/modules/drivers/tdfx_drv.so.bak" 5) run "cp temp/usr/lib/xorg/modules/drivers/tdfx_drv.so /usr/lib/xorg/modules/drivers/tdfx_drv.so" 6) run "nano /etc/apt/sources.list" 7) Look for the section regarding enabling the "universe" repository, as this repository contains libglide3 (libglide3 is for Voodoo3 and newer, Voodoo2 users need libglide2), which you will need for 3D acceleration. You will need to uncomment two lines, then Ctrl+O (write out) and Ctrl-X (exit) 8) run "apt-get update" 9) run "apt-get install libglide3" (or libglide2, note #7) 10) run "apt-get upgrade" (you may as well do this now instead of when you restart) 11) run "reboot" That should be it. You're using the 1.3.0 tdfx_drv.so instead of the 1.2.1, but it has the correct symbols being exported so things work correctly. The only problem with 1.2.1 is the "getsecs" symbol not being exported, which is confirmable if you had tailed /var/log/gdm/(whatever the log file is). The error does not show in the Xorg log. I imagine that the newer Xorg will be used for Feisty, and it's entirely possible that a fixed Xorg will be delivered to users of Edgy. It's less than optimal to be using a different version of the driver, but in this case it is necessary as tdfx_drv.so is just plain broken (for *all* distributions using the 1.2.1 version). -Philip -- X doesn't launch with voodoo 5 5500 https://launchpad.net/bugs/63796 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
