How to use wifi and touch screen in Dell Latitude ST? (BionicPup32)

[TerryH]

This is just my guess, but that wifi card utilizes the SDIO bus. I think it's a kernel related issue that it just isn't being identified. It is above me to advise how to proceed. Maybe post in the bionicpup32 thread and peebee or someone with kernel experience may assist.

A couple of websites regarding SDIO wifi cards:
https://askubuntu.com/questions/1170776 ... ot-working
https://www.silabs.com/community/wirele ... ction-ajSx

[bigpup]

Could try to use the windows driver.

Puppy Linux has the ability to use a windows driver by using ndiswrapper.

menu->Setup->Internet Connection Wizard->Wired or wireless LAN->Network Wizard->Load Module->Ndiswrapper Tab

Read the info on what it needs from Windows and provide it.

[ironsniper1]

tried using ndis wrapper but all the drivers I tried didn't work or it would throw an error, I will have to reinstall puppy to get back to getting it to work again

[bigpup]

In that Windows device info program.
If you double click on the dell 1535c entry.
It should provide more info.

[ironsniper1]

In that Windows device info program.
If you double click on the dell 1535c entry.
It should provide more info.

it doesn't tell you stuff like chipset or anything like that its all very basic info

[ironsniper1]

okay i got puppy reinstalled and went to the terminal and did the dmesg command and check out the highlighted section



also running this command

dmesg | grep -i sdio

i get this

Code: Select all

mmc0: error -110 whilst initialising SDIO card
mmc0: error -110 whilst initialising SDIO card
mmc0: error -110 whilst initialising SDIO card
mmc0: error -110 whilst initialising SDIO card

[bigpup]

Bluetooth support, is another issue to track down, but not the big one to fix.

Did you have the USB WIFI adapter plugged in when you did these terminal commands?
If yes.
Run them with the USB WIFI adapter not plugged in.

Puppy does not handle multiple WIFI devices. It only wants to see one.

I would try some of the other versions of Puppy.
Xenialpup 7.5
ScPup

[mikewalsh]

that sounded a bit rude, every place I look online about this card every site has said it has the same atheros chipset so I don't know what to tell you, it works on windows 7 but windows 7 is a dog on this thing, now maybe the issue is because its a wireless and a Bluetooth card in one I don't know

@ ironsniper1:-

You may have hit the nail on the head there, about it being wifi AND Bluetooth combined.

My new Compaq tower I acquired back in January is the first desktop I've ever had with built-in wifi. This is no issue for me since I use the Gigabit ethernet anyway, but I've tried many times, with different Pups, to see if I can get it to work.

In every Pup where I've tried it, the card is recognised - the drivers are apparently present - it connects for a split-second, then invariably disconnects. This card, too, is also a Bluetooth card.....which doesn't function either..!

So perhaps this one, too, needs a different version of the driver to function as it should. It's something I really need to look into, one of these days.

------------------------

@bigpup :- Y'know, I have a nasty suspicion that the relevant driver for the card in question is going to have to be one that simultaneously supports both the wireless connection, AND the Bluetooth functionality, at the same time....given that they apparently inhabit the same chipset. Whether they can operate independently of each other, at the same time (or whether, in fact, they both use some of the same parts of the chip's internal circuitry), I wouldn't even care to speculate on.

I really don't see, however, what else it could be.

(*shrug*)


Mike.

[ironsniper1]

Bluetooth support, is another issue to track down, but not the big one to fix.

Did you have the USB WIFI adapter plugged in when you did these terminal commands?
If yes.
Run them with the USB WIFI adapter not plugged in.

Puppy does not handle multiple WIFI devices. It only wants to see one.

I would try some of the other versions of Puppy.
Xenialpup 7.5
ScPup

i did not have the USB wireless plugged in as this is a fresh install

[ironsniper1]

that sounded a bit rude, every place I look online about this card every site has said it has the same atheros chipset so I don't know what to tell you, it works on windows 7 but windows 7 is a dog on this thing, now maybe the issue is because its a wireless and a Bluetooth card in one I don't know

@ ironsniper1:-

You may have hit the nail on the head there, about it being wifi AND Bluetooth combined.

My new Compaq tower I acquired back in January is the first desktop I've ever had with built-in wifi. This is no issue for me since I use the Gigabit ethernet anyway, but I've tried many times, with different Pups, to see if I can get it to work.

In every Pup where I've tried it, the card is recognised - the drivers are apparently present - it connects for a split-second, then invariably disconnects. This card, too, is also a Bluetooth card.....which doesn't function either..!

So perhaps this one, too, needs a different version of the driver to function as it should. It's something I really need to look into, one of these days.

------------------------

@bigpup :- Y'know, I have a nasty suspicion that the relevant driver for the card in question is going to have to be one that simultaneously supports both the wireless connection, AND the Bluetooth functionality, at the same time....given that they apparently inhabit the same chipset. Whether they can operate independently of each other, at the same time (or whether, in fact, they both use some of the same parts of the chip's internal circuitry), I wouldn't even care to speculate on.

I really don't see, however, what else it could be.

(*shrug*)


Mike.

I'll be honest I don't really care about Bluetooth I would be happy with just the wireless working if anyone knows a half-height mini PCI-e wireless card that works on Linux let me know if it's cheap enough I am willing to buy it

[bigpup]

I found this trying to get it to work in Ubuntu Linux.
Bionicpup32 8.0 has the ath6kl driver and firmware.

WLAN not working

It is an ‘Atheros Wireless WLAN BT 1535C Half MiniCard’.

The chip of this WLAN card is: “Atheros AR6x02/AR6003 NWF WLAN”.

Driver needed ath6kl

Thanks to Patrick and kvalo i get the card to work:
In a terminal:

Code: Select all

rmmod sdhci_pci
rmmod sdhci
modprobe sdhci debug_quirks=0x2
modprobe sdhci_pci

DO NOT DO THIS GRUB part FOR PUPPY.
This is just some info to have.
To enable it on startup edit “/etc/default/grub” and change “GRUB_CMDLINE_LINUX_DEFAULT” to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash sdhci.debug_quirks=0x20"

If this works.
That grub stuff we will have to try to modify for Puppies boot loader.

[ironsniper1]

Code: Select all

rmmod sdhci_pci
rmmod sdhci

i cant remember the exact error but I do get an error when I run those commands

[bigpup]

Nothing is ever simple and easy with WIFI, when dealing with a computer manufactures(Dell), specific part.
3rd party hardware, no problems.

Kind of need to know the error!

[ironsniper1]

Nothing is ever simple and easy with WIFI.

Kind of need to know the error!

Code: Select all

rmmod: ERROR: Module sdhci_pci is builtin.

[bigpup]

That is kind of saying that command not needed. What it does is already done.

What about after you did all the other commands?

[ironsniper1]

That is kind of saying that command not needed. What it does is already done.

What about after you did all the other commands?

nothing happens I just get that error

[bigpup]

Go to the network connection program you use and see if the wlan(WIFI) device is now showing.

[ironsniper1]

Nope nothing shows up

[mikewalsh]

@ironsniper1 :-

I'm curious, I have to admit. Why the insistence on getting an internal card functional, when there are plenty of USB 'nano'-sized wifi dongles around these days that are extremely Linux-friendly..?

Or is it the fact that you would have one USB port permanently occupied, and not available for other purposes? That, I can identify with, I confess; although my new HP desktop has USB ports coming out of its ears, and I also have a 7-port hub plugged into one, giving me a total of 13 available ports, my nearly 20-yr old Dell Inspiron 1100 lappie is another matter entirely.....just two ports in total!

That old girl, however, has the advantage of what's called a PCMCIA , or "CardBus" slot under the hard drive caddy.....from which I run a "period" wifi card that would have been on the market at the time it was being manufactured. Which means I have one USB port for an external hard drive, and the other supplies a powered hub for peripherals.....

---------------------------------

The driver issue mystifies me, too; even if the Bluetooth is non-functional, I would have thought, upon reflection, that at least the wifi portion of that card would 'kick-in'.....especially given that Bionic's kernel has the requisite drivers available. Dell always were known for using unconventional components in their machines, and they kept changing them so frequently; in Windows, of course, every manufacturer supplies a driver for their device OOTB when you buy it, all ready to go...

Curious.


Mike.

[ironsniper1]

@ironsniper1 :-

I'm curious, I have to admit. Why the insistence on getting an internal card functional, when there are plenty of USB 'nano'-sized wifi dongles around these days that are extremely Linux-friendly..?

Or is it the fact that you would have one USB port permanently occupied, and not available for other purposes? That, I can identify with, I confess; although my new HP desktop has USB ports coming out of its ears, and I also have a 7-port hub plugged into one, giving me a total of 13 available ports, my nearly 20-yr old Dell Inspiron 1100 lappie is another matter entirely.....just two ports in total!

That old girl, however, has the advantage of what's called a PCMCIA , or "CardBus" slot under the hard drive caddy.....from which I run a "period" wifi card that would have been on the market at the time it was being manufactured. Which means I have one USB port for an external hard drive, and the other supplies a powered hub for peripherals.....

---------------------------------

The driver issue mystifies me, too; even if the Bluetooth is non-functional, I would have thought, upon reflection, that at least the wifi portion of that card would 'kick-in'.....especially given that Bionic's kernel has the requisite drivers available. Dell always were known for using unconventional components in their machines, and they kept changing them so frequently; in Windows, of course, every manufacturer supplies a driver for their device OOTB when you buy it, all ready to go...

Curious.


Mike.

you hit the nail on the head, only one working usb port,now it does come with a stand which i posted a link to earlier in the thread which gives it a ethernet port and three more usb ports but none of that works and i doubt i could get them to work, all though talking about has given me an idea i am going to try when i get home

[ironsniper1]

can i use ndis wrapper to install drivers for the LAN7500 chipset which is in the stand and controls the USB ports and ethernet port of the stand

I also found this, it seems my card should work with the bluetooth

https://web.archive.org/web/20120114071 ... ers/ath6kl

[ironsniper1]

hey everyone i found this https://forums.linuxmint.com/viewtopic.php?t=185387 i am getting the same error though it is a error -32 and not a -110 is there a way for me to do this on puppy to see if it will fix my issue?

[perdido]

hey everyone i found this https://forums.linuxmint.com/viewtopic.php?t=185387 i am getting the same error though it is a error -32 and not a -110 is there a way for me to do this on puppy to see if it will fix my issue?

First I would check the

Code: Select all

rfkill list

to verify the card is not blocked.

You can skiplist the ath3k module by editing /etc/rc.d/MODULESCONFIG by adding it, with a space on either side, to to the line beginning SKIPLIST=
Then either run depmod in terminal & restart X, or reboot.

You can also force load a module by adding a module to the line ADDLIST= in that same MODULESCONFIG file.
-------------------
I would not be concerned about reloading the bluetooth module later until you get the wifi working.
Its also a good idea to make a backup of any system file you modify.

[ironsniper1]

hey everyone i found this https://forums.linuxmint.com/viewtopic.php?t=185387 i am getting the same error though it is a error -32 and not a -110 is there a way for me to do this on puppy to see if it will fix my issue?

First I would check the

Code: Select all

rfkill list

to verify the card is not blocked.

You can skiplist the ath3k module by editing /etc/rc.d/MODULESCONFIG by adding it, with a space on either side, to to the line beginning SKIPLIST=
Then either run depmod in terminal & restart X, or reboot.

You can also force load a module by adding a module to the line ADDLIST= in that same MODULESCONFIG file.
-------------------
I would not be concerned about reloading the bluetooth module later until you get the wifi working.
Its also a good idea to make a backup of any system file you modify.

i did go ahead and black list the module for the Bluetooth and now it no longer shows an error in dmesg but I have no way to test it

EDIT i don't know if this means anything but it showed up when I ran dmesg command in the terminal

Code: Select all

device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:0e:18.0: SDHCI controller found [8086:0807] (rev 1)
sdhci-pci 0000:0e:18.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:0e:18.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:0e:18.0: Will use DMA mode even though HW doesn't fully claim to support it.
mmc0: SDHCI controller on PCI [0000:0e:18.0] using DMA
sdhci-pci 0000:0f:19.0: SDHCI controller found [8086:0808] (rev 1)
sdhci-pci 0000:0f:19.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:0f:19.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:0f:19.0: Will use DMA mode even though HW doesn't fully claim to support it.
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
mmc1: SDHCI controller on PCI [0000:0f:19.0] using DMA
sdhci-pci 0000:10:1a.0: SDHCI controller found [8086:0812] (rev 1)
sdhci-pci 0000:10:1a.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:10:1a.0: Will use DMA mode even though HW doesn't fully claim to support it.
sdhci-pci 0000:10:1a.0: Will use DMA mode even though HW doesn't fully claim to support it.
random: fast init done
mmc2: SDHCI controller on PCI [0000:10:1a.0] using ADMA

[perdido]

hey everyone i found this https://forums.linuxmint.com/viewtopic.php?t=185387 i am getting the same error though it is a error -32 and not a -110 is there a way for me to do this on puppy to see if it will fix my issue?

First I would check the

Code: Select all

rfkill list

to verify the card is not blocked.

You can skiplist the ath3k module by editing /etc/rc.d/MODULESCONFIG by adding it, with a space on either side, to to the line beginning SKIPLIST=
Then either run depmod in terminal & restart X, or reboot.

You can also force load a module by adding a module to the line ADDLIST= in that same MODULESCONFIG file.
-------------------
I would not be concerned about reloading the bluetooth module later until you get the wifi working.
Its also a good idea to make a backup of any system file you modify.

i did go ahead and black list the module for the Bluetooth and now it no longer shows an error in dmesg but I have no way to test it, almost want to try the same for the wireless to see if that does anything

What is it that you have no way to test?

You can run

Code: Select all

lspci

in terminal and see if it shows your atheros device. The device should at least show up even if it is hard blocked with no drivers installed. Look for a line similar to Qualcomm Atheros in the output.

You can run

Code: Select all

lsmod

to see which drivers are loaded.
The atheros driver in my compaq shows up as ath 15930 1 ath5k

[ironsniper1]

First I would check the

Code: Select all

rfkill list

to verify the card is not blocked.

You can skiplist the ath3k module by editing /etc/rc.d/MODULESCONFIG by adding it, with a space on either side, to to the line beginning SKIPLIST=
Then either run depmod in terminal & restart X, or reboot.

You can also force load a module by adding a module to the line ADDLIST= in that same MODULESCONFIG file.
-------------------
I would not be concerned about reloading the bluetooth module later until you get the wifi working.
Its also a good idea to make a backup of any system file you modify.

i did go ahead and black list the module for the Bluetooth and now it no longer shows an error in dmesg but I have no way to test it, almost want to try the same for the wireless to see if that does anything

What is it that you have no way to test?

You can run

Code: Select all

lspci

in terminal and see if it shows your atheros device. The device should at least show up even if it is hard blocked with no drivers installed. Look for a line similar to Qualcomm Atheros in the output.

You can run

Code: Select all

lsmod

to see which drivers are loaded.
The atheros driver in my compaq shows up as ath 15930 1 ath5k

lspci

Code: Select all

00:00.0 Host bridge: Intel Corporation Device 4110 (rev 04)
00:02.0 VGA compatible controller: Intel Corporation Device 4102 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Medfield Serial IO I2C Controller #3 (rev 03)
01:01.0 Display controller: Intel Corporation Moorestown External Displays (rev 01)
03:10.0 System peripheral: Intel Corporation Moorestown SC DMA (rev 01)
05:11.0 Communication controller: Intel Corporation Moorestown SPI Ctrl 1 (rev 01)
07:12.0 Communication controller: Intel Corporation Moorestown I2C 0 (rev 01)
08:13.0 Communication controller: Intel Corporation Moorestown I2C 1 (rev 01)
09:14.0 Communication controller: Intel Corporation Moorestown I2C 2 (rev 01)
0b:15.0 Audio device: Intel Corporation Moorestown Audio Ctrl
0c:16.0 USB controller: Intel Corporation Moorestown USB Ctrl (rev 01)
0d:17.0 USB controller: Intel Corporation Moorestown OTG Ctrl (rev 01)
0e:18.0 SD Host controller: Intel Corporation Moorestown SD Host Ctrl 0 (rev 01)
0f:19.0 SD Host controller: Intel Corporation Moorestown SD Host Ctrl 1 (rev 01)
10:1a.0 SD Host controller: Intel Corporation Moorestown SPI Ctrl 2 (rev 01)
11:1b.0 SATA controller: Intel Corporation Device 0816 (rev 01)

lsmod

Code: Select all

Module                  Size  Used by
iptable_filter          1379  0
ip_tables               9725  1 iptable_filter
fan                     3614  0
uvcvideo               69280  0
videobuf2_vmalloc       4033  1 uvcvideo
snd_hda_codec_idt      36275  1
snd_hda_codec_generic    50044  1 snd_hda_codec_idt
snd_hda_codec_hdmi     31587  1
snd_hda_intel          19237  0
videobuf2_memops        1057  1 videobuf2_vmalloc
videobuf2_v4l2          9718  1 uvcvideo
btusb                  26068  0
snd_hda_codec          69124  4 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_hdmi,snd_hda_codec_generic
btrtl                   4480  1 btusb
videobuf2_core         24501  2 uvcvideo,videobuf2_v4l2
snd_hda_core           40317  5 snd_hda_intel,snd_hda_codec,snd_hda_codec_idt,snd_hda_codec_hdmi,snd_hda_codec_generic
btbcm                   5687  1 btusb
videodev              106761  3 uvcvideo,videobuf2_core,videobuf2_v4l2
snd_seq_dummy            975  0
snd_seq_oss            23811  0
snd_pcm_oss            33925  0
btintel                 6048  1 btusb
snd_mixer_oss          12136  1 snd_pcm_oss
media                  15939  2 uvcvideo,videodev
bluetooth             302865  4 btrtl,btintel,btbcm,btusb
snd_seq_midi            4063  0
snd_seq_midi_event      4484  2 snd_seq_midi,snd_seq_oss
snd_pcm                68521  5 snd_pcm_oss,snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
snd_rawmidi            15049  1 snd_seq_midi
gma500_gfx            143858  3
rfkill                  8235  1 bluetooth
i2c_algo_bit            4877  1 gma500_gfx
pcspkr                  1459  0
sg                     25733  0
snd_seq                39339  6 snd_seq_midi_event,snd_seq_dummy,snd_seq_midi,snd_seq_oss
drm_kms_helper        100076  1 gma500_gfx
snd_seq_device          2516  4 snd_seq,snd_rawmidi,snd_seq_midi,snd_seq_oss
snd_timer              15776  2 snd_seq,snd_pcm
ci_hdrc_pci             1949  0
syscopyarea             2990  1 drm_kms_helper
ci_hdrc                16254  1 ci_hdrc_pci
snd                    44952  13 snd_pcm_oss,snd_hda_intel,snd_mixer_oss,snd_seq,snd_hda_codec,snd_hda_codec_idt,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_seq_oss,snd_pcm
sysfillrect             3258  1 drm_kms_helper
phy_generic             3304  1 ci_hdrc_pci
sysimgblt               2031  1 drm_kms_helper
soundcore               4417  1 snd
fb_sys_fops             1034  1 drm_kms_helper
i2c_designware_pci      3130  0
drm                   230387  4 gma500_gfx,drm_kms_helper
i2c_designware_core     8255  1 i2c_designware_pci
hid_ntrig               7043  0
wmi                     6299  0
battery                11202  0
ac                      3880  0

[perdido]

lspci indicates your card is not recognized. You have already established that it works. Your pcie sdio device should show up in the lspci output. Mine do.

lsmod indicates there are some bluetooth drivers that are loaded that are not associated with your card.

btusb 26068 0
btbcm
btintel 6048 1 btusb
bluetooth 302865 4 btrtl,btintel,btbcm,btusb

rfkill 8235 1 bluetooth

rfkill is disabling the bluetooth entry that is representing the following 4 modules (drivers): btrtl,btintel,btbcm,btusb
That could be disabling the card prior to loading wifi drivers.

Try adding those 4 drivers to the SKIPLIST in /etc/rc.d/MODULESCONFIG
reboot
look at lspci and lsmod to see if the card is showing


Additionally you can force the ath6k_core and ath6kl_sdio module to load by adding them to the /etc/rc.d/MODULESCONFIG
How to do that:
Put them into the line ADDLIST= in the same format as the SKIPLIST= line.
Make sure the ADDLIST= line is not commented out with #

What could be the worst thing that could happen? Nothing, so worth a shot.
Remember we are just trying to get wifi working for now, if and after that is working we can force load the ath3k.ko and see what happens with the bluetooth
As a matter of fact it may be necessary to force load the ath3k driver in order to get the wifi driver loaded but probably is not. Keep that in mind if the card is still not showing after adding those 4 drivers to SKIPLIST, etc.
Sometimes drivers have to be loaded in a certain order.

Here is a little additional info just because. These drivers have ~probably been colliding with the ath3k.ko module in some way or another and since you only have an atheros device thay are not needed.
the btintel.ko is a linux driver to support intel usb devices. Not needed, you have an atheros
the btbcm.ko is a linux driver to support Broadcom usb devices. Not needed.
the btusb.ko is a generic driver to support usb bluetooth usb devices. Not needed
the btrtl.ko is a linux driver to support Realtek usb devices. Not needed

Further along after wifi is up try removing ath3k from the SKIPLIST= line
That driver can also be force loaded using ADDLIST= if necessary after the other bluetooth drivers are disabled, if wanted.

[ironsniper1]

lspci indicates your card is not recognized. You have already established that it works. Your pcie sdio device should show up in the lspci output. Mine do.

lsmod indicates there are some bluetooth drivers that are loaded that are not associated with your card.

btusb 26068 0
btbcm
btintel 6048 1 btusb
bluetooth 302865 4 btrtl,btintel,btbcm,btusb

rfkill 8235 1 bluetooth

rfkill is disabling the bluetooth entry that is representing the following 4 modules (drivers): btrtl,btintel,btbcm,btusb
That could be disabling the card prior to loading wifi drivers.

Try adding those 4 drivers to the SKIPLIST in /etc/rc.d/MODULESCONFIG
reboot
look at lspci and lsmod to see if the card is showing


Additionally you can force the ath6k_core and ath6kl_sdio module to load by adding them to the /etc/rc.d/MODULESCONFIG
How to do that:
Put them into the line ADDLIST= in the same format as the SKIPLIST= line.
Make sure the ADDLIST= line is not commented out with #

What could be the worst thing that could happen? Nothing, so worth a shot.
Remember we are just trying to get wifi working for now, if and after that is working we can force load the ath3k.ko and see what happens with the bluetooth
As a matter of fact it may be necessary to force load the ath3k driver in order to get the wifi driver loaded but probably is not. Keep that in mind if the card is still not showing after adding those 4 drivers to SKIPLIST, etc.
Sometimes drivers have to be loaded in a certain order.

Here is a little additional info just because. These drivers have ~probably been colliding with the ath3k.ko module in some way or another and since you only have an atheros device thay are not needed.
the btintel.ko is a linux driver to support intel usb devices. Not needed, you have an atheros
the btbcm.ko is a linux driver to support Broadcom usb devices. Not needed.
the btusb.ko is a generic driver to support usb bluetooth usb devices. Not needed
the btrtl.ko is a linux driver to support Realtek usb devices. Not needed

Further along after wifi is up try removing ath3k from the SKIPLIST= line
That driver can also be force loaded using ADDLIST= if necessary after the other bluetooth drivers are disabled, if wanted.

this command just gives me a list of commands I can use and does not work

Code: Select all

rfkill 8235 1 bluetooth

[ironsniper1]

lspci indicates your card is not recognized. You have already established that it works. Your pcie sdio device should show up in the lspci output. Mine do.

lsmod indicates there are some bluetooth drivers that are loaded that are not associated with your card.

btusb 26068 0
btbcm
btintel 6048 1 btusb
bluetooth 302865 4 btrtl,btintel,btbcm,btusb

rfkill 8235 1 bluetooth

rfkill is disabling the bluetooth entry that is representing the following 4 modules (drivers): btrtl,btintel,btbcm,btusb
That could be disabling the card prior to loading wifi drivers.

Try adding those 4 drivers to the SKIPLIST in /etc/rc.d/MODULESCONFIG
reboot
look at lspci and lsmod to see if the card is showing


Additionally you can force the ath6k_core and ath6kl_sdio module to load by adding them to the /etc/rc.d/MODULESCONFIG
How to do that:
Put them into the line ADDLIST= in the same format as the SKIPLIST= line.
Make sure the ADDLIST= line is not commented out with #

What could be the worst thing that could happen? Nothing, so worth a shot.
Remember we are just trying to get wifi working for now, if and after that is working we can force load the ath3k.ko and see what happens with the bluetooth
As a matter of fact it may be necessary to force load the ath3k driver in order to get the wifi driver loaded but probably is not. Keep that in mind if the card is still not showing after adding those 4 drivers to SKIPLIST, etc.
Sometimes drivers have to be loaded in a certain order.

Here is a little additional info just because. These drivers have ~probably been colliding with the ath3k.ko module in some way or another and since you only have an atheros device thay are not needed.
the btintel.ko is a linux driver to support intel usb devices. Not needed, you have an atheros
the btbcm.ko is a linux driver to support Broadcom usb devices. Not needed.
the btusb.ko is a generic driver to support usb bluetooth usb devices. Not needed
the btrtl.ko is a linux driver to support Realtek usb devices. Not needed

Further along after wifi is up try removing ath3k from the SKIPLIST= line
That driver can also be force loaded using ADDLIST= if necessary after the other bluetooth drivers are disabled, if wanted.

blocked all of those and added the ones we want and still no wifi

also there is this under lsmod

[perdido]

blocked all of those and added the ones we want and still no wifi

also there is this under lsmod

Please be more specific. Did you check for devices using

Code: Select all

lspci

Did you try to ADDLIST the ath3k driver as suggested if the lspci output did not show the atheros device?

If you have done both of those then check the output of

Code: Select all

rfkill list

There should be nothing either soft blocked or hard blocked.
---------------------