Hard lockup caused by ACX111 based PCI wireless adapter

[Dan Bishop]

I have a sitecom WL-121 wireless pci adaptor that has a texas instrument ACX111 chipset. If I remove it from my computer intrepid boots just fine, otherwise a hard lock-up occurs. By pressing ctrl+alt+F1 as many times as possible whilst X is starting, I've managed to get the output that can be seen in the attached photo. In a previous attempt one of the lines mentioned ACX111, unfortunately I did not get a photo.

I'm using the latest intrepid daily build and this problem has been present in intrepid for at least 2 months. I have been testing daily builds every other day and not one has booted with the wireless card in.

[Vlad V. Voronenkov (voronenkov)]

I had the same bug with ACX111-based card on Intrepid. My chipset is AMD780G with integrated video HD3200. The bug appeared on both i386 and x86_64 Intrepid installs. The problem was solved by installing proprietary video drivers fglrx from repository.

[J.F.K. (Donkey) (wrongurl)]

Greetings,

Vlad,I will continue to work on the driver issue.I am sure you probably know that unless some of these issues are resolved we will never have an truly open-source environment.It may be fine for us technically savvy types to enjoy a challenge however,I doubt we will win over those who prefer to plug and play....Microsoft 99.9% of market share Linux possibly 0.1% if they are lucky. What I think we need is more hardware rather than software people to do some reverse engineering on the propriatary issues.to wit Texas Instruments acx111 chipset.

Sure it may be old to the new kids on the block but I don't think everyone in the world has access to or can afford the latest whiz-bang computers.Fix the old problems before we jump to the new ones.

Jerry

Unencrypted electronic mail is not secure and may not be authentic. If you have any doubts as to the contents please telephone to confirm.

Jeremy(Jerry)
Barlock Engineering Canada Ltd.
Voice: 613-422-1948
Fax: [phone]

Private email: <email address hidden>

> Date: Sat, 14 Mar 2009 21:21:43 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 275771] Re: Hard lockup caused by ACX111 based PCI wireless adapter
>
> I had the same bug with ACX111-based card on Intrepid. My chipset is
> AMD780G with integrated video HD3200. The bug appeared on both i386 and
> x86_64 Intrepid installs. The problem was solved by installing
> proprietary video drivers fglrx from repository.
>
> --
> Hard lockup caused by ACX111 based PCI wireless adapter
> https://bugs.launchpad.net/bugs/275771
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: New
>
> Bug description:
> I have a sitecom WL-121 wireless pci adaptor that has a texas instrument ACX111 chipset. If I remove it from my computer intrepid boots just fine, otherwise a hard lock-up occurs. By pressing ctrl+alt+F1 as many times as possible whilst X is starting, I've managed to get the output that can be seen in the attached photo. In a previous attempt one of the lines mentioned ACX111, unfortunately I did not get a photo.
>
> I'm using the latest intrepid daily build and this problem has been present in intrepid for at least 2 months. I have been testing daily builds every other day and not one has booted with the wireless card in.

_________________________________________________________________
Chat with the whole group, and bring everyone together.
http://go.microsoft.com/?linkid=9650735

[Manoj Iyer (manjo)]

Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]