I somehow managed to be ignorant that ath_pci was madwifi until now.
Is not loading a driver when one is available the intended behavior, or
is it indeed a bug?
I would imagine that at the very least there is meant to be a
notification that there is a proprietary driver available when the
interfa
Actually, you shouldn't just remove the blacklist since that will allow
both drivers to be loaded. You should instead exchange module names in
the blacklist file, either ath5k _or_ ath_pci, depending on which driver
you want loaded.
--
[Jaunty] Jockey doesn't display ath5k
https://bugs.launchpad.
You can enable madwifi in system -> admin -> hardware drivers again.
Removing the blacklist file will work fine as well, of course.
--
[Jaunty] Jockey doesn't display ath5k
https://bugs.launchpad.net/bugs/323830
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It seems this bug may be related: (jockey and madwifi tools may be
interfering with each other?)
"/etc/modprobe.d/madwifi.conf stops Atheros wifi modules from loading"
https://bugs.launchpad.net/ubuntu/+source/madwifi-tools/+bug/359820
--
[Jaunty] Jockey doesn't display ath5k
https://bugs.launch
I'm in the process of searching bugs regarding this, but I think It may
be relevant here:
In the process of upgrading, upon reboot, I had no wireless
connectivity. (Making it a bit difficult to research a solution). After
a bit of prodding it was obvious that ath_pci was not loaded for my
adapter
This bug was fixed in the package jockey - 0.5-0ubuntu5
---
jockey (0.5-0ubuntu5) jaunty; urgency=low
* Add debian/watch.
* Add bzr-builddeb configuration.
* data/handlers/fglrx.py: Enable again, 2:8.600-0ubuntu1 works on Jaunty
now.
* Merge bug fixes from trunk:
- Fix
The handler I added to jockey won't display ath5k separately, but the
madwifi handler points out that this is an alternative for the free
ath5k. Enabling/disabling madwifi will disable/enable ath5k.
** Changed in: jockey (Ubuntu)
Status: In Progress => Fix Committed
--
[Jaunty] Jockey doe
** Changed in: jockey (Ubuntu)
Status: Triaged => In Progress
--
[Jaunty] Jockey doesn't display ath5k
https://bugs.launchpad.net/bugs/323830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
This bug was fixed in the package module-init-tools - 3.7~pre9-2
---
module-init-tools (3.7~pre9-2) jaunty; urgency=low
* Moved ath_pci blacklist to /etc/modprobe.d/blacklist-ath_pci.conf
for better jockey support.
-LP: #323830
-- Tim GardnerWed, 18 Mar 2009 15:45:43
+
Uploaded module-init-tools_3.7~pre9-2
** Changed in: module-init-tools (Ubuntu)
Importance: Undecided => Medium
Status: New => Fix Released
Target: None => ubuntu-9.04-beta
** Changed in: module-init-tools (Ubuntu)
Status: Fix Released => Fix Committed
--
[Jaunty] Jockey
Whoops, I meant /etc/modprobe.d/blacklist-ath_pci.conf . The .conf
suffix matters now.
Discussing this with Tim on IRC, I think the easiest solution will be to
just ship this in a separate conffile in m-i-t. This avoids introducing
brittle code in m-i-t to maintain this as a non-conffile.
--
[Ja
Currently m-i-t blacklists it in the main
/etc/modprobe.d/blacklist.conf. That's impractical, since if jockey
would modify that conffile, we'd break automatic upgrades.
Ideally l-r-m or m-i-t would ship a separate modprobe.d/blacklist-
ath_pci, which jockey can then fiddle with.
** Also affects:
This is related to bug 290264.
** Changed in: jockey (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
Status: New => Triaged
--
[Jaunty] Jockey doesn't display ath5k
https://bugs.launchpad.net/bugs/323830
You received this bug notification because you are a member of Ubuntu
Bug
13 matches
Mail list logo
