Comment 9 for bug 253740

Hi,
Am sorry I can't be of any more help with Intrepid. I gaveup on it sometime
back and now am back to hardy. It was consuming way too much of my time even
for the basic operations. Network manager for one is a nightmare. You can
mark this bug invalid if the other guys do not respond to it.
Cheers
A Grey given during life is better than Orchids on the grave....

On Thu, Nov 20, 2008 at 3:57 AM, Leann Ogasawara <email address hidden> wrote:

> Hi Everyone,
>
> @Eric, I noticed you mention you have a different wireless card and
> therefore using a differen driver than the original bug reporter. Even
> though you may be experiencing the same issue reported here it likely is
> hardware specific and you should open a separate bug report. However,
> before doing so you may also want try installing the linux-backports-
> modules-intrepid package to see if it helps as it has an updated compat-
> wireless stack.
>
> @Jon and @renfrew, I'm unsure of the specific hardware that you have,
> but it seems you at least have the same model. It would be good if one
> of you opened a new bug report as well and the other then subscribes to
> it.
>
> @Debian God, since you are the original bug reporter, can you confirm if
> this is still an issue with the final release of Intrepid? If the issue
> remains, Per the kernel team's bug policy, can you please attach the
> following information. Please be sure to attach each file as a separate
> attachment.
>
> * cat /proc/version_signature > version.log
> * dmesg > dmesg.log
> * sudo lspci -vvnn > lspci-vvnn.log
>
> For more information regarding the kernel team bug policy, please refer
> to https://wiki.ubuntu.com/KernelTeamBugPolicies .
>
> For those of you opening new bug reports (ie Eric, Jon, and renfrew),
> the above information would be appreciated in your new reports as well.
> Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> Keyboard freeze after some time
> https://bugs.launchpad.net/bugs/253740
> You received this bug notification because you are a direct subscriber
> of the bug.
>