Both of the drivers you've specified DO actually have support in the kernel for those devices.

"Atheros AR5006EG 802.11bg NIC (2.4GHz, PCI Express)" corresponds to:
Vendor 168c Device 001c Subvendor 168c Subdevice 3065

from drivers/net/wireless/ath5k/base.c:
static struct pci_device_id ath5k_pci_id_table[] __devinitdata = {
/* ... */
{ PCI_VDEVICE(ATHEROS, 0x001c), .driver_data = AR5K_AR5212 }, /* 5424 Condor (PCI-E)*/
/* ... */
};

from drivers/media/video/stk-webcam.c:
/* Some cameras have audio interfaces, we aren't interested in those */
static struct usb_device_id stkwebcam_table[] = {
        { USB_DEVICE_AND_INTERFACE_INFO(0x174f, 0xa311, 0xff, 0xff, 0xff) },
        { USB_DEVICE_AND_INTERFACE_INFO(0x05e1, 0x0501, 0xff, 0xff, 0xff) },
        { }                                     ^^^^^^
};
MODULE_DEVICE_TABLE(usb, stkwebcam_table);


That's why the kernel is loading those drivers. Where have you installed the external modules? If they're in /lib/modules/$(uname -r)/{updates,weak-updates,extra} they should be taking priority over in-kernel modules. If they're located under the /lib/modules/$(uname -r)/kernel hierarchy, then they're probably loaded in whichever order they appear in modules.pcimap or modules.usbmap, respectively.

If they are in {updates,weak-updates,extra} and are getting overridden by the in-kernel modules, that's a bug. Otherwise, you have an installation problem.

*ping*?

Closing due to lack of response.  Please reopen if the response is given.

i am sorry, but simply said ::

at least in my case are not those two modules working with my hw !!

i am not new in Linux and my workaround was as simple as can be ::

a) blacklist both problematic modules
b) download, unpack and compile modules for atheros and syntek webcam
c) copy compiled modules into /lib/modules/`uname -r`/foo && depmod -a
d) modprobe both modules manually .. since that times they are working

<< it is very nice, that *your* (joking !! take it easy) modules support whatever they support, but my devices NOT !!

regards by maki

The ath5k issue (ath5k driver not working properly with this particular hardware) is a duplicate of bug 421638; see bug 373098 for more info.

If the default stkwebcam driver does not work properly with your camera, please open a new bug and describe what exactly is not working and attach dmesg.

*** This bug has been marked as a duplicate of bug 421638 ***

Created attachment 265885 [details]
logs ..

excatly same behaviour in suse 11.1 ..

both ath5k as well as stkwebcam needs to be manually blacklisted and then compliled and installed stk11xxx and ath_pci .. 

request more info if needed ..

please don't scratch this bug !! investigate please.. i am convinced, that this bug is very important because can't be resolved by someone, who's new in Linux or not so geeky ..

# hwinfo --wlan
26: PCI 100.0: 0282 WLAN controller
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_168c_1c
  Unique ID: xFhm.UI_dUZts6z7
  Parent ID: _Znp.9ygNxLmzVeF
  SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: network
  Model: "Atheros AR5006EG 802.11bg NIC (2.4GHz, PCI Express)"
  Vendor: pci 0x168c "Atheros Communications Inc."
  Device: pci 0x001c "AR242x 802.11abg Wireless PCI Express Adapter"
  SubVendor: pci 0x168c "Atheros Communications Inc."
  SubDevice: pci 0x3065 "AR5006EG 802.11bg NIC (2.4GHz, PCI Express)"
  Revision: 0x01
  Driver: "ath_pci"
  Driver Modules: "ath_pci"
  Device File: ath0
  Features: WLAN
  Memory Range: 0xdc7f0000-0xdc7fffff (rw,non-prefetchable)
  IRQ: 19 (no events)
  HW Address: 00:15:af:17:03:7f
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484
  WLAN encryption modes: WEP40 WEP104 WEP128 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v0000168Cd0000001Csv0000168Csd00003065bc02sc00i00"
  Driver Info #0:
    Driver Status: ath5k is not active
    Driver Activation Cmd: "modprobe ath5k"
  Driver Info #1:
    Driver Status: ath_pci is active
    Driver Activation Cmd: "modprobe ath_pci"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #9 (PCI bridge)

There are two bug reports here.

(1) ath5k not working properly.

Sorry, madwifi is partially closed source driver and not supported by anyone. It is deprecated and unmaintained. You should not install nor use it. The recommended driver is ath5k.

If ath5k does not work for you, please fill a bug and describe what is wrong with the driver. Please make sure you don't have any closed source kernel module (like ath_pci, nvidia, fglrx, etc.) installed before you reproduce and report the bug with ath5k.

Also, please note that an average user is not expected nor supposed to compile a kernel module, her/his hardware should work out of box with the default drivers. If the default drivers have problems with the hardware, either we or upstream will try to fix them. This is the only way to solve your problem. We cannot support closed source modules and we will not ship them as they are believed to infringe the kernel license.

(2) stkwebcam not working properly.

Again, please fill a new bug, mention stkwebcam in the summary and describe what exactly does not work when you use that driver, append the logs, etc. If the driver really does not work with your hardware, it can be removed from the device table of the module but it has to be justified. For that, a description what is not working and the logs are really needed.

---
Closing as invalid, please report separate bugs for both issues.