[Bug 383814] Re: Jaunty: Intel 4965 to WPA Enterprise Loses Connection
Actually, I've been using Karmic successfully on my University network for a while now. I am under the impression that this bug is no longer present. I had all kinds of problems with 9.04 and even 8.10. Hardy has always worked well for me, and Karmic seems to have fixed all the problems I noticed in versions in between. Remy, if you haven't already tried 9.10 Karmic, I suggest you grab a LiveCD and give it a shot. -- Jaunty: Intel 4965 to WPA Enterprise Loses Connection https://bugs.launchpad.net/bugs/383814 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 383814] [NEW] Jaunty: Intel 4965 to WPA Enterprise Loses Connection
Public bug reported: I'm running Jaunty 9.04 on a Dell Inspiron 1520 with Intel 4965 wireless chip. I try to connect to my university's WPA enterprise network, and occasionally a connection will be established, but it tends to fail (signal goes to zero, nm-applet tries to re-establish) within a minute if data is being sent or received. The connection is more stable if it is idle. Hardy 8.04.2 works flawlessly. I will post dmesg when I have anything relevant to report. ** Affects: ubuntu Importance: Undecided Status: New -- Jaunty: Intel 4965 to WPA Enterprise Loses Connection https://bugs.launchpad.net/bugs/383814 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 332387] Re: Intel 4965 Wireless LAN association problems
I encounter this problem in Ubuntu Jaunty when associating with my school's WPA Enterprise network. -- Intel 4965 Wireless LAN association problems https://bugs.launchpad.net/bugs/332387 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 321393] [NEW] system does not resume from sleep
Public bug reported: When I put my system to sleep, it goes into S3 just fine. When I open the lid to resume the system, it begins to wake, but the screen does not come back on, and the power button is not responsive to force a shutdown of the system. I have to hold the power-off button for a hard reset. I'm running Intrepid 8.10 amd64 on a Dell Inspiron 1520. Core 2 T7500 nVidia 8400M (Beta 180.11 driver) Kernel: 2.6.27-9-generic It doesn't appear to have logged anything to my system log about trying to wake up. Please let me know if there's any information I can provide. ** Affects: ubuntu Importance: Undecided Status: New -- system does not resume from sleep https://bugs.launchpad.net/bugs/321393 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 321393] Re: system does not resume from sleep
Further, this never occurred with my i686 installation of Hardy. I will be installing an amd64 version of 8.04 to test this, and if it fails to work properly, I will test an i686 version of both 8.04 and 8.10 to see what is affected. -- system does not resume from sleep https://bugs.launchpad.net/bugs/321393 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 227844] Re: shutdown hangs (sometimes) - Hardy 64 - ASUS P5LD2 SE
I experience this problem frequently in Intrepid. Dell Inspiron 1520 Core 2 Duo T7500 nVidia 8400M GS Intel 4965 AGN Tested video driver 177 and 180 (beta). Recently replaced wireless chip. Any other questions, just ask. -- shutdown hangs (sometimes) - Hardy 64 - ASUS P5LD2 SE https://bugs.launchpad.net/bugs/227844 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 308053] Re: iwlagn: cannot allocate SKB buffers
Please disregard my posts. My problems extended to Windows XP and Vista. The chip has been replaced with an identical version, and my problem has been resolved. -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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 308053] Re: iwlagn: cannot allocate SKB buffers
I've been having problems with the iwlagn module. I'm actually using Hardy 8.04.1, and I presume an update that was committed to Intrepid has been sent to Hardy as well. The LiveCD had no problems, and my disk install of Hardy had worked flawlessly for a long time. It is only recently that this has occurred, and it seems related to this thread: http://ubuntuforums.org/showthread.php?t=962070 There is a workaround that was suggested for Intrepid that the users in that thread were unable to use successfully due to the fact that the iwl4965 module was removed from Intrepid in favor of iwlagn. Being on Hardy, I still have the iwl4965 module, so issuing the command to unload iwlagn and iwl4965 then re-load iwl4965 has so far resolved my issues: sudo modprobe -r iwlagn iwl4965 ; sudo modprobe iwl4965 Without the proper module, this command does not function properly. If Intrepid (and presumably Jaunty) were to include iwl4965, then this workaround could be applied. -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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 308053] Re: iwlagn: cannot allocate SKB buffers
The relevant dmesg output I get when this occurs is as follows: [ 3603.194199] wlan0: No ProbeResp from current AP 00:0f:34:8f:98:d5 - assume out of range [ 3603.939973] wlan0: No STA entry for own AP 00:0f:34:8f:98:d5 [ 3606.456102] wlan0: No STA entry for own AP 00:0f:34:8f:98:d5 [ 3609.478726] wlan0: No STA entry for own AP 00:0f:34:8f:98:d5 [ 3616.213511] wlan0: Initial auth_alg=0 [ 3616.213531] wlan0: authenticate with AP 00:0f:34:8f:98:d5 [ 3616.290410] wlan0: authenticate with AP 00:0f:34:8f:98:d5 [ 3616.446937] wlan0: authenticate with AP 00:0f:34:8f:98:d5 [ 3616.607757] wlan0: authentication with AP 00:0f:34:8f:98:d5 timed out I'm not entirely certain if this is due to SKB buffers, but this occurs on a fairly regular basis. Running the workaround above allows the adapter to reconnect, but I cannot stay connected long enough to transfer a full CD image. -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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 234114] Re: Stopmotion dies with segmentation fault
bjoernen, please provide details. I tried updating synaptic to see if 0.6.2 was available. Nope. I downloaded the 0.6.2 version from homepage, but only .deb file offered is i386. Used dpkg -i --force-architecture to install. Error indicates that libqt4-gui is not up to date. There is no official update to 4.4.0 in synaptic. Tried --force-all flag, and installed but failed to run. Tried forcing i386 version of 0.6.0, which caused error indicating that it was unable to find libSDL_image. Gave up. Please help. -- Stopmotion dies with segmentation fault https://bugs.launchpad.net/bugs/234114 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 234114] Re: Stopmotion dies with segmentation fault
Can anyone confirm if this problem affects i386 binaries? If not, has anyone tried i386 binaries on an amd64 machine? -- Stopmotion dies with segmentation fault https://bugs.launchpad.net/bugs/234114 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 149214] Re: [Gutsy] Intel 4965AGN wireless connection dies
Same problem for me. This is far better since someone pointed out the sudo rmmod iwl4965 sudo modprobe iwl4965 fix. I've since made a shell script to make this easier to manage, but it's pretty aggravating to have my connection drop out. My dmesg: [ 198.492970] wlan0: associated [ 198.492977] wlan0: CTS protection enabled (BSSID=00:1b:2b:6a:a4:11) [ 198.498844] iwl4965: TX Power requested while scanning! [ 198.498851] iwl4965: Error setting Tx power (-11). [ 198.500188] iwl4965: TX Power requested while scanning! [ 198.500194] iwl4965: Error setting Tx power (-11). [ 200.840893] iwl4965: Microcode SW error detected. Restarting 0x200. [ 208.977140] wlan0: deauthenticate(reason=3) [ 209.590098] ADDRCONF(NETDEV_UP): wlan0: link is not ready -- [Gutsy] Intel 4965AGN wireless connection dies https://bugs.launchpad.net/bugs/149214 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 136282] Re: screen brightness doesn't return to proper level
For the OP, you have to set the dim brightness by to 0% in order for it to be fully bright. I have a related problem, however, in that if I set it to 0% and then dim it manually, it will dim to full-bright when idle. This is counter-intuitive. -- screen brightness doesn't return to proper level https://bugs.launchpad.net/bugs/136282 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 96841] Re: en-hypervisor-3.0-amd64 cannot load Nvidia using Ubuntu restricted driver
*** This bug is a duplicate of bug 107814 *** https://bugs.launchpad.net/bugs/107814 I'm experiencing the same problem in Gutsy with Xen 3.1. There's supposed to be a Xen-compiled restricted driver, but I can't find a way to force it. -- en-hypervisor-3.0-amd64 cannot load Nvidia using Ubuntu restricted driver https://bugs.launchpad.net/bugs/96841 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
