ndiswrapper and ACX100

I have read numerous posts on this but am running out of ideas other
then getting a new wifi card. Have the dlink dwl-520+ PCI card - but am
unsuccessful installing it with ndiswrapper. Brand new install of
Mepis. Ndiswrapper is installed. I have ID'd the card (104c:8400) when
I run lspci - here is the output:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo
KT266/A/333]
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo
KT266/A/333 AGP]
0000:00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
0000:00:07.0 Network controller: Texas Instruments ACX 100 22Mbps
Wireless Interface
0000:00:08.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev
03)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA
Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus MasterIDE (rev 06)
0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 18)
0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 18)
0000:00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 18)
0000:01:00.0 VGA compatible controller: Silicon Integrated Systems
[SiS] 86C326 5598/6326 (rev 0b)

Yes, I also have a realtek ethernet NIC working fine but would like the
wifi to work - does anyone have a set of procedures for this under
ndiswrapper? It just will not start up successfully. Should it run out
of the box? thanks in advance - Bill

"Bill" <(E-Mail Removed)> writes:

>I have read numerous posts on this but am running out of ideas other
>then getting a new wifi card. Have the dlink dwl-520+ PCI card - but am
>unsuccessful installing it with ndiswrapper. Brand new install of
>Mepis. Ndiswrapper is installed. I have ID'd the card (104c:8400) when
>I run lspci - here is the output:
>0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo
>KT266/A/333]
>0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo
>KT266/A/333 AGP]
>0000:00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>RTL-8139/8139C/8139C+ (rev 10)
>0000:00:07.0 Network controller: Texas Instruments ACX 100 22Mbps
>Wireless Interface
>0000:00:08.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev
>03)
>0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA
>Bridge
>0000:00:11.1 IDE interface: VIA Technologies, Inc.
>VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus MasterIDE (rev 06)
>0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
>1.1 Controller (rev 18)
>0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
>1.1 Controller (rev 18)
>0000:00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
>1.1 Controller (rev 18)
>0000:01:00.0 VGA compatible controller: Silicon Integrated Systems
>[SiS] 86C326 5598/6326 (rev 0b)

>Yes, I also have a realtek ethernet NIC working fine but would like the
>wifi to work - does anyone have a set of procedures for this under
>ndiswrapper? It just will not start up successfully. Should it run out
>of the box? thanks in advance - Bill


Now tell us what you did to try to get ndiswrapper working?
What does "it will not start up successfully " mean?

On 3 Jan 2006 06:47:43 -0800
"Bill" <(E-Mail Removed)> wrote:

>Have the dlink dwl-520+ PCI card - but am
> unsuccessful installing it with ndiswrapper. Brand new install of
> Mepis.

I can verify that this card works fine in Mepis, using ndiswrapper, with no work on the part of the user other than using the Mepis Control Center to input the SSID and channel you wish to connect to, and WEP if you use it.

Look for the Mepis Control Center icon, it appears by default on the KDE panel. If you've removed KDE, simply open a terminal, su to root, then type in "oscenter"

I should also recommend the Mepis Lovers website. Very helpful for new users. I post there sometimes, and it'll probably get you quicker replies than usenet.
http://www.mepislovers.org/

Can you please provide specific steps as to doing anything with
ndiswrapper? I configured Control Center - infrastructure mode with
the network name = SSID (is this correct?) I don't see any opportunity
to put in a channel. Do you think the card will work with "live cd"
version? I did get the card going briefly last night playing with
ndiswrapper but then it locked up mepis completely. Currently not
using WEP. I must be making this way harder than it should be. Any
help here at all would be welcome - thanks, Bill

Mandeep Shergill wrote:
> On 3 Jan 2006 06:47:43 -0800
> "Bill" <(E-Mail Removed)> wrote:
>
> >Have the dlink dwl-520+ PCI card - but am
> > unsuccessful installing it with ndiswrapper. Brand new install of
> > Mepis.
>
> I can verify that this card works fine in Mepis, using ndiswrapper, with no work on the part of the user other than using the Mepis Control Center to input the SSID and channel you wish to connect to, and WEP if you use it.
>
> Look for the Mepis Control Center icon, it appears by default on the KDE panel. If you've removed KDE, simply open a terminal, su to root, then type in "oscenter"
>
> I should also recommend the Mepis Lovers website. Very helpful for new users. I post there sometimes, and it'll probably get you quicker replies than usenet.
> http://www.mepislovers.org/

"Bill" <(E-Mail Removed)> writes:

>Can you please provide specific steps as to doing anything with
>ndiswrapper? I configured Control Center - infrastructure mode with
>the network name = SSID (is this correct?) I don't see any opportunity
>to put in a channel. Do you think the card will work with "live cd"
>version? I did get the card going briefly last night playing with
>ndiswrapper but then it locked up mepis completely. Currently not
>using WEP. I must be making this way harder than it should be. Any
>help here at all would be welcome - thanks, Bill

Run
iwlist s
Do you get reports of Access Points. If you do your card is working.


>Mandeep Shergill wrote:
>> On 3 Jan 2006 06:47:43 -0800
>> "Bill" <(E-Mail Removed)> wrote:
>>
>> >Have the dlink dwl-520+ PCI card - but am
>> > unsuccessful installing it with ndiswrapper. Brand new install of
>> > Mepis.
>>
>> I can verify that this card works fine in Mepis, using ndiswrapper, with no work on the part of the user other than using the Mepis Control Center to input the SSID and channel you wish to connect to, and WEP if you use it.
>>
>> Look for the Mepis Control Center icon, it appears by default on the KDE panel. If you've removed KDE, simply open a terminal, su to root, then type in "oscenter"
>>
>> I should also recommend the Mepis Lovers website. Very helpful for new users. I post there sometimes, and it'll probably get you quicker replies than usenet.
>> http://www.mepislovers.org/

yes! However, I must use the command pump -i wlan0 to get connected.
(If I reboot, must do it again) Is there a way to automate this?

Bill wrote:
> yes! However, I must use the command pump -i wlan0 to get connected.
> (If I reboot, must do it again) Is there a way to automate this?

It will depend on your distro. I use SuSE 10.0 and set it up with YaST, which writes the appropiate
ifcfg-wlan0 in /etc/sysconfig/network. YMMV.

This may be picky but: (using Mepis latest version)
Finally got the ACX100 card working with WEP! I did have to add the
command pump -i wlan0 to .kde autostart under user login. For some
reason when I log in as root desktop is clean; when I login as "user"
kwifimanager starts with errors although wifi IS working. I cannot see
any difference with the way OS or control center is configured between
the 2 logins. Is there some way of making sure kwifimanager does NOT
start?
thanks in advance - Bill

Larry Finger wrote:
> Bill wrote:
> > yes! However, I must use the command pump -i wlan0 to get connected.
> > (If I reboot, must do it again) Is there a way to automate this?
>
> It will depend on your distro. I use SuSE 10.0 and set it up with YaST, which writes the appropiate
> ifcfg-wlan0 in /etc/sysconfig/network. YMMV.

Problem apparently resolved - the next day after a power down
kwifimanager is not popping up. However the wifi connection does take
some tinkering with to get going - or it takes perhaps a couple of
minutes to "sync" up? Does not come up right away from power up. If
anyone has thoughts to make this connection more reliable please share
- thanks.