Access wifi on laptop

[vjp...@at.biostrategist.dot.dot.com]

I'v run sev versions of Linux on this machine and they find the WIFI right
away, but nothing I do (drivers & al) gets it to work with XP. Any ideas?


--
Vasos Panagiotopoulos panix.com/~vjp2/vasos.htm
---{Nothing herein constitutes advice. Everything fully disclaimed.}---

[gfre...@aol.com]

On Tue, 4 Apr 2023 00:12:19 -0000 (UTC),
vjp...@at.BioStrategist.dot.dot.com wrote:

>I'v run sev versions of Linux on this machine and they find the WIFI right
>away, but nothing I do (drivers & al) gets it to work with XP. Any ideas?

Start with the obvious, did you bump the switch and turn off the
radio? Then go to the network tab in control panel and see if the
system sees the adapter.

[AugustA]

On Tue, 4 Apr 2023 00:12:19 -0000 (UTC)

vjp...@at.BioStrategist.dot.dot.com wrote:

VABDDC> I'v run sev versions of Linux on this machine and they find the WIFI right
VABDDC> away, but nothing I do (drivers & al) gets it to work with XP. Any ideas?

My T60 Thinkpad has both a software switch and hardware switch. I find that XP can't "find" the wifi even if the software switch is OFF, but several distros of Linux seemed to ignore the software setting but still find the wifi.

[Paul]

On 4/3/2023 8:12 PM, vjp...@at.BioStrategist.dot.dot.com wrote:
> I'v run sev versions of Linux on this machine and they find the WIFI right
> away, but nothing I do (drivers & al) gets it to work with XP. Any ideas?

It helps if you tell us the make and model of laptop,
and since there can be variants, what the make and model
of Wifi is.

Using the laptop name, helps to track down "troublesome" designs,
where the laptop manufacturer is at fault. It isn't always
possible to track down an issue purely by Wifi make and model.

Wifi modules tend to sit in a socketed interface, with coax cables
leading to the radio outputs. A person can change out a Wifi module,
with another one. This is a mistake on certain Intel platforms, because
the BIOS has been designed to "blacklist" foreign Wifi modules and
prevent them from working. This is part of an Intel "branding strategy"
for their higher end platforms.

Of course, this is not the case with yours, as Linux detects it.
And if the chip select had been turned off at BIOS level,
it might not be detectable after that.

Intel does this on designs, where most of the parts are made
by Intel. Intel Wifi module, being part of that. They get fancy
names like Centrino or Ultrabook. If the machine had a Realtek Ethernet
chip and an Atheros (Qualcomm) Wifi, there would be no such tricks involved.
It would just work.

Paul

[vjp...@at.biostrategist.dot.dot.com]

Vostro 3560 Had wifi on Win7, replaced with xp, no wifi,
ran linux of DVD, wifi still there, now strangely (maybe bad reception) last
time even linux didn't have wifi

I have run a number of Dell Wifi driver packages

Maybe so many they confused each other

[Paul]

On 4/6/2023 3:36 PM, vjp...@at.BioStrategist.dot.dot.com wrote:
> Vostro 3560 Had wifi on Win7, replaced with xp, no wifi,
> ran linux of DVD, wifi still there, now strangely (maybe bad reception) last
> time even linux didn't have wifi
>
> I have run a number of Dell Wifi driver packages
>
> Maybe so many they confused each other

Are there any USB3 devices present in the room ?

USB3 equipment can emit interference at 2.5GHz (1/2 of 5GHz data rate).
This can conflict with 2.4GHz Wifi. The 5GHz flavor of Wifi is unaffected.

For example, a USB3 hard drive connected to a USB3 port
on a computer, can cause electrical interference to Wifi.
It can also cause wireless keyboard or wireless mouse to malfunction.

Paul

[vjp...@at.biostrategist.dot.dot.com]

Dell Vostro 3560

wifi works on CAELinux & w7but not xp or reactos
reactos also can't see the USA ports

[Paul]

On 4/16/2023 12:15 PM, vjp...@at.BioStrategist.dot.dot.com wrote:
> Dell Vostro 3560
>
> wifi works on CAELinux & w7but not xp or reactos
> reactos also can't see the USA ports
>
>

https://www.dell.com/community/Vostro/Vostro-3560-replacement-for-Wireless-1703/td-p/8179917

Vostro 3560 replacement for Wireless 1703

I would like to replace my Dell Wireless 1703 802.11b/g/n card

It's under the keyboard/palmrest. Service manual here:

https://www.dell.com/support/home/en-us/product-support/product/vostro-3560/docs

Computers like this, they can use more than one Wifi module in production.
The 1703 gives me "3119" as an ID. I am using the above discussion thread,
as evidence of one possible module.

ATHR.DeviceDesc.3096 = "Dell Wireless 1515 Wireless-N Adapter"
ATHR.DeviceDesc.0203 = "DW1525 (802.11n) WLAN PCIe Card"
ATHR.DeviceDesc.30A1A = "Dell Wireless 1502 802.11b/g/n"
ATHR.DeviceDesc.30ABA = "Dell Wireless 1702 802.11b/g/n"
ATHR.DeviceDesc.3118 = "Dell Wireless 1506 802.11b/g/n (2.4GHz)"
ATHR.DeviceDesc.3119 = "Dell Wireless 1703 802.11b/g/n (2.4GHz)" <===
ATHR.DeviceDesc.946x = "Dell Wireless 1901 802.11a/b/g/n (2.4GHz and 5GHz)"
ATHR.DeviceDesc.946xT = "Dell Wireless 1601 802.11 a/g/n Adapter"
ATHR.DeviceDesc.956x = "Dell Wireless 1705 802.11b/g/n (2.4GHZ)"
ATHR.DeviceDesc.946xY = "Dell Wireless 1601 802.11 a/g/n Adapter"
ATHR.DeviceDesc.956xA = "Dell Wireless 1707 802.11b/g/n (2.4GHZ)"
ATHR.DeviceDesc.946xA = "Dell Wireless 1802 802.11a/b/g/n Adapter"

%ATHR.DeviceDesc.3119% = ATHR_DEV_OS61_3119.ndi, PCI\VEN_168C&DEV_0032&SUBSYS_02091028

168c Atheros Communications Inc.

AR9485 Wireless Network Adapter xp3264-10.0.0.260-whql.zip

https://drivers.softpedia.com/get/NETWORK-CARD/Atheros/Atheros-WLAN-Driver-1000260-for-XP.shtml

*******

Using Linux, verify hardware using

lspci <=== look for 168C:0032 as evidence AR9485 is present
lsusb

Atheros is a preferred Linux Wifi, in that Linux drivers have
been available for some time. Atheros was bought by Qualcomm,
which is why the driver distribution is not the same as it
used to be. (Broadcom Wifi also works, but it is much more
painful to get working under Linux, using blacklist entries.)

The Softpedia driver for WinXP should be OK, but is only going to work
if you actually have an Atheros module present.

And this is only a basic driver. The setup will still likely
use "Wireless Zero Configuration" in the OS, for setup
and configuring the device, once the basic driver is present.

https://kb.netgear.com/20021/Enabling-Wireless-Zero-Config-WZC-on-Windows-XP

Some drivers in the distant past, had custom panels for
setting up the Wifi. When the WinXP feature was available,
the driver packages could be slimmed down. and then it is up
to the WZC process, to finish the installation details (SSID and
so on).

Paul