Re: [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Christopher, Am 21.05.2018 um 15:58 schrieb Christopher M. Penalver: > Michael Schmitz: > > 1) To clarify, you tested the 64-bit variant (not 32-bit)? Correct. > 2) Is using the nv driver still a usable WORKAROUND? > Sorry, didn't try that (is it even possible without installing from that image?). Cheers, Michael > ** Description changed: > > Binary package hint: xserver-xorg-video-nouveau > > Expectation: Default Xorg driver should work with no video artifacts. > > Observation: Bad screen flicker with default Xorg driver. > > Details: I installed the 10.04 beta from CD on Wednesday (incidentially, > compliments for the smooth install). Already upon installation, the > display did flicker badly whenever the CD was read or even the mouse > moved. Flicker did already start at the initial splash screen. The > system was fully responsive otherwise. On reboot post-installation, gdm > came up OK but with the same flicker problems. The 'Monitors' control > panel only offered the 2048x1536 resolution at 80 Hz with no other > options. Tried to install and use one of the non-free nvidia drivers, > this failed because the nouveau kernel module was loaded always and > could not be unloaded (drm loads nouveau before framebuffer console > init. as near as I can make out). With nvidia-current unable to load, > - the X server could not use the 'nvidia' driver. Switching xorg.conf to > - use the 'nv' driver results in a much better screen display (only > - occasional flicker) although the driver only supports 2048x1536 at 60 > - Hz. 1600x1200@85 Hz is useable. > + the X server could not use the 'nvidia' driver. > > Kernel message buffer excerpt: > [4.777915] [drm] Initialized drm 1.1.0 20060810 > [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 > [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 > (level, low) -> IRQ 22 > [4.807783] nouveau :00:0d.0: setting latency timer to 64 > [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 > [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card > (0x04c000a2) > [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image > from PROM > [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found > [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image > from PRAMIN > [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid > [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found > [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 > [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found > [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration > Block version 3.0 > [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 > 10 2 > [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 > tag 0xff > [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 > tag 0x07 > [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 > tag 0xff > [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 > tag 0xff > [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 > tag 0xff > [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 > 0023 > [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 > 942b0003 > [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at > offset 0xD9C9 > [4.854591] [drm] nouveau :00:0d.0: === misaligned reg > 0x0060081D === > [4.854648] [drm] nouveau :00:0d.0: === misaligned reg > 0x0060081D === > [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at > offset 0xDB17 > [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at > offset 0xDB18 > [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at > offset 0xDC9A > [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at > offset 0xDCE3 > [4.861274] lp0: using parport0 (interrupt-driven). > [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. > [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. > [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM > [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) > [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0 > [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: > initialised FIFO 0 > [4.868896] [dr
Re: [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Hi Christopher, still the same problem as before. Cheers, Michael Am 18.05.2018 um 16:58 schrieb Christopher M. Penalver: > Michael Schmitz, to confirm this is still a problem in Ubuntu, could you > please test http://cdimage.ubuntu.com/daily-live/current/ and advise to > the results? > > ** Project changed: nouveau => xserver-xorg-video-nouveau (Ubuntu) > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Status: New => Incomplete > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Importance: Undecided => Low > > ** Tags removed: needs-apport-collect > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/549256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Will do - fortunately, I still have that PC. Give me a few days though. Cheers, Michael Am 18.05.2018 um 16:58 schrieb Christopher M. Penalver: > Michael Schmitz, to confirm this is still a problem in Ubuntu, could you > please test http://cdimage.ubuntu.com/daily-live/current/ and advise to > the results? > > ** Project changed: nouveau => xserver-xorg-video-nouveau (Ubuntu) > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Status: New => Incomplete > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Importance: Undecided => Low > > ** Tags removed: needs-apport-collect > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/549256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578657] [NEW] spanish keyboard not accentuating vowels
Public bug reported: I've already added the Spanish language keyboard to unity and the keyboard indicator at the top indicates the Spanish keyboard and I do get Ñ and ñ however when I go to accentuate a vowel áéíóú it's not working the normal process is that I press the apostrophe key (in the us keyboard it would be two keys toward the right from "L") then select the vowel to be accentuated. however you're not supposed to see anything until the vowel is selected. what is happening instead is that I'm getting an apostrophe right away when I press the tilde key. NOTE0: I've tested also other variants of the Spanish layout with similar success.. NOTE1: I have installed cinnamon also and when I login to cinnamon it works, so I'm only experiencing the issue in unity. NOTE2: I'm very proficient with computers and have successfully done this many times. NOTE3: I'm working on a fairly clean setup of Ubuntu 16.04 LTS I've only added Cinnamon and the Intel Drivers to the system and google chrome system is also up to date. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: 16.04 keyboard language layout ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578657 Title: spanish keyboard not accentuating vowels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1578657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Christopher, I finally got around to test a recent daily build of trusty (dowloaded on Jan 15th) and the issue still persists. It does start with the splash screen on boot. Even worse, after clicking the 'Try Ubuntu' button, the system locked up hard within less than half a minute (when switching away from the selection screen). DVD activity ceased, and I had to power down the system to get it to restart (the reset switch failed to work). For that reason, I could not run the apport-collect command you gave below. Is there some way to collect the necessary information while booting to a console instead of X, or chrooting into the live system image? Cheers, Michael Michael Schmitz, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xserver-xorg-video-nouveau REPLACE-WITH-BUG-NUMBER Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided = Low ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/549256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Chris, I'll do a test on the live system today - will that be sufficient? Regards, Michael On Thu, Jan 9, 2014 at 2:25 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Michael Schmitz, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xserver-xorg-video-nouveau REPLACE-WITH-BUG-NUMBER Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided = Low ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-video-nouveau System: Description: Ubuntu lucid (development branch) Release: 10.04 (beta 1) Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu4 (or one of its kernel module dependencies) Maybe related: #425372 Expectation: Default Xorg driver should work with no video artifacts. Observation: Bad screen flicker with default Xorg driver. Details: I installed the 10.04 beta from CD on Wednesday (incidentially, compliments for the smooth install). Already upon installation, the display did flicker badly whenever the CD was read or even the mouse moved. Flicker did already start at the initial splash screen. The system was fully responsive otherwise. On reboot post-installation, gdm came up OK but with the same flicker problems. The 'Monitors' control panel only offered the 2048x1536 resolution at 80 Hz with no other options. Tried to install and use one of the non-free nvidia drivers, this failed because the nouveau kernel module was loaded always and could not be unloaded (drm loads nouveau before framebuffer console init. as near as I can make out). With nvidia-current unable to load, the X server could not use the 'nvidia' driver. Switching xorg.conf to use the 'nv' driver results in a much better screen display (only occasional flicker) although the driver only supports 2048x1536 at 60 Hz. 1600x1200@85 Hz is useable. The main board is a dual Athlon X2 AMD M2N68-AM Plus with onboard nVidia graphics chipset. I append partial dmesg and lspci output. If there is any other information that could be of help, let me know. -- Michael Kernel message buffer excerpt: [4.777915] [drm] Initialized drm 1.1.0 20060810 [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 [4.807779] nouveau :00:0d.0: PCI INT A - Link[LMC9] - GSI 22 (level, low) - IRQ 22 [4.807783] nouveau :00:0d.0: setting latency timer to 64 [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card (0x04c000a2) [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PROM [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PRAMIN [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block version 3.0 [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 10 2 [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 tag 0xff [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 tag 0x07 [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 tag 0xff [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 tag 0xff [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 tag 0xff [4.854581
[Bug 668013] Re: Unity icons crash window manager on mouse-over
Same on Thinkpad X31. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668013 Title: Unity icons crash window manager on mouse-over -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604854] [NEW] dbus is not started by upstart when the machine-id file is empty
Public bug reported: Binary package hint: dbus Release: Ubuntu 10.04 LTS dbus version: 1.2.16-2ubuntu4 Maybe related: #288596 During installation, the /var/lib/dbus/machine-id file presumably was initialized with no contents. After booting, gdm does not start up due to dbus not running. dbus can be started manually using dbus-daemon --system --fork from a root shell, and gdm starts normally afterwards. Apparently, the pre-start script in /etc/init/dbus.conf does not properly handle the case where machine-id is present but invalid. The relevant command in the pre-start script is dbus-uuidgen --ensure, my guess is that dbus-uuidgen --ensure exits with error failing to validate the UUID, and this causes dbus not starting from upstart. Not sure what the correct strategy would be in this case - an empty UUID file is clearly going to fail and hence should be removed before dbus- uuidgen --ensure runs. [ ! -s /var/lib/dbus/machine-id ] rm -f /var/lib/dbus/machine-id* might do it, perhaps. -- Michael ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- dbus is not started by upstart when the machine-id file is empty https://bugs.launchpad.net/bugs/604854 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 549256] [NEW] [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Public bug reported: Binary package hint: xserver-xorg-video-nouveau System: Description:Ubuntu lucid (development branch) Release:10.04 (beta 1) Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu4 (or one of its kernel module dependencies) Maybe related: #425372 Expectation: Default Xorg driver should work with no video artifacts. Observation: Bad screen flicker with default Xorg driver. Details: I installed the 10.04 beta from CD on Wednesday (incidentially, compliments for the smooth install). Already upon installation, the display did flicker badly whenever the CD was read or even the mouse moved. Flicker did already start at the initial splash screen. The system was fully responsive otherwise. On reboot post-installation, gdm came up OK but with the same flicker problems. The 'Monitors' control panel only offered the 2048x1536 resolution at 80 Hz with no other options. Tried to install and use one of the non-free nvidia drivers, this failed because the nouveau kernel module was loaded always and could not be unloaded (drm loads nouveau before framebuffer console init. as near as I can make out). With nvidia-current unable to load, the X server could not use the 'nvidia' driver. Switching xorg.conf to use the 'nv' driver results in a much better screen display (only occasional flicker) although the driver only supports 2048x1536 at 60 Hz. 1600x1...@85 Hz is useable. The main board is a dual Athlon X2 AMD M2N68-AM Plus with onboard nVidia graphics chipset. I append partial dmesg and lspci output. If there is any other information that could be of help, let me know. -- Michael Kernel message buffer excerpt: [4.777915] [drm] Initialized drm 1.1.0 20060810 [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 [4.807779] nouveau :00:0d.0: PCI INT A - Link[LMC9] - GSI 22 (level, low) - IRQ 22 [4.807783] nouveau :00:0d.0: setting latency timer to 64 [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card (0x04c000a2) [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PROM [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PRAMIN [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block version 3.0 [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 10 2 [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 tag 0xff [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 tag 0x07 [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 tag 0xff [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 tag 0xff [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 tag 0xff [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023 [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003 [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at offset 0xD9C9 [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at offset 0xDB17 [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at offset 0xDB18 [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at offset 0xDC9A [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at offset 0xDCE3 [4.861274] lp0: using parport0 (interrupt-driven). [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0 [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: initialised FIFO 0 [4.868896] [drm] nouveau :00:0d.0: Initial CRTC_OWNER is 0 [4.868901] [drm] nouveau :00:0d.0: Saving VGA fonts [4.908706] [drm] nouveau :00:0d.0: DCB type 4 not known [4.908710] [drm] nouveau :00:0d.0: Detected a VGA connector [4.909936] [drm] nouveau :00:0d.0: Setting dpms mode 3 on vga encoder (output 0) [5.037394] [drm] nouveau :00:0d.0: allocated 2048x1536 fb: 0x49000, bo f67bb400 [5.037515] fb0: nouveaufb frame buffer device [5.037517] registered
[Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/42121477/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/42121478/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42121479/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/42121480/Lspci.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/42121481/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/42121482/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/42121483/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/42121484/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/42121485/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/42121486/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/42121487/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/42121488/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/42121489/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/42121490/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/42121491/Xrandr.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/42121492/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/42121493/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/42121494/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/42121495/xkbcomp.txt -- [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver https://bugs.launchpad.net/bugs/549256 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 163929] Re: freezes when wireless enabled (using the restricted Broadcom driver in feisty)
I was hopeful that this would have been fixed on Hardy Heron, but the problem persisted. -- Michael On Wed, Sep 24, 2008 at 2:07 AM, Michael Nagel [EMAIL PROTECTED] wrote: is this still an issue with more recent releases? ** Changed in: ubuntu Status: New = Incomplete -- freezes when wireless enabled (using the restricted Broadcom driver in feisty) https://bugs.launchpad.net/bugs/163929 You received this bug notification because you are a direct subscriber of the bug. -- freezes when wireless enabled (using the restricted Broadcom driver in feisty) https://bugs.launchpad.net/bugs/163929 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 163929] freezes when wireless enabled (using the restricted Broadcom driver in feisty)
Public bug reported: Everything freezes (i.e., can't even move the mouse) after random intervals of use when the wireless is enabled. There have been periods when it worked fine for a number of hours, but more often it freezes within the first few minutes. Disabling the wireless prevents freezes. The computer is running the first release of feisty fawn on a Dell Inspiron 1501. Thus the machine is using the broadcom driver that is supplied as a Restricted Driver (firmware for Broadcom 43xx chipset family). Reinstalling the OS has not helped. There are many wireless networks present usually at the machine resides in a university apartment complex. ** Affects: ubuntu Importance: Undecided Status: New -- freezes when wireless enabled (using the restricted Broadcom driver in feisty) https://bugs.launchpad.net/bugs/163929 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
