Ralph,
I see now what you are saying. I went to the Dasha project page. I tried my wiki login and it failed so should I sign up for an account there as well?
This is all getting quite monotonous...
I now have a login for the CentOS forums, one for the wiki, one for each mail list (devel and docs), and now I am to register again for the Dasha project?
Is there no way to unify this to a single login across the whole site?
While the logins are the same for the forums and the lists, the wiki had to be different (wiki wants camel case). Not to mention if I am working one the wiki or the forum I have to login seperately. Then add to that if I want to login now to the dasha... do I have to login yet again?
I am sorry I do not wish to complain really... I just wish to offer that this seems like a large amount of work to ask a contributor.
If it cannot be helped for now, that is just the way it is. I just though it might be worth asking about.
Dear David,
I see now what you are saying. I went to the Dasha project page. I tried my wiki login and it failed so should I sign up for an account there as well?
This is all getting quite monotonous...
I now have a login for the CentOS forums, one for the wiki, one for each mail list (devel and docs), and now I am to register again for the Dasha project?
Is there no way to unify this to a single login across the whole site?
We are currently working on a LDAP based single sign on for Website ver. 2. Will hopefully happen this year ;)
Best Regards Marcus
1. So now the question is, should I create an account on dasha? 2. If so should I use the wiki style login or the forum/lists login? 3. Does it even matter?
Dear David.
- So now the question is, should I create an account on dasha?
- If so should I use the wiki style login or the forum/lists login?
- Does it even matter?
I would suggest to use the same username as in the Wiki (when time comes we have to merge/dupe them, otherwise)
Best Regards Marcus
Marcus Moeller wrote:
I would suggest to use the same username as in the Wiki (when time comes we have to merge/dupe them, otherwise)
Thanks Marcus, I created the account (DavidDreggors) on the Dasha site.
The main Dasha wiki page says:
"Anyone can submit a driver for inclusion into the dasha images. In order to do so, create an account for yourself here and send an email to the centos-developers mailing list ( link ) with details of the driver you would like to get included. You will then get an svn account where you can directly import the drivers and the associated Makefiles and config scripts required to make it build. "
I have the account and have already sent the request here. Is there anything else I need to do?
How/what do I have to do once I get the svn account? What files do I need to upload?
I have already sent this list the spec and src.rpm. The source code us not changed from the snapshot downloaded from snapshots.madwifi-project.org.
The driver is an RPM of the latest snapshot of madwifi. I do not own the source code I just created the rpm and used it on a fresh install here on my laptop.
The need for this driver is for anyone using a laptop (or other) that has the Atheros AR5007EG wireless card. The stock ath5k kernel module does not support this card.
Currently the only module that works well is madwifi. I have tried the kmod-ath5k from the elrepo-testing repo, which does work, but locks your machine up solid when bringing down the interface. Not a good solution yet.
On Mon, 11 May 2009, David Dreggors wrote:
Marcus Moeller wrote:
I would suggest to use the same username as in the Wiki (when time comes we have to merge/dupe them, otherwise)
Thanks Marcus, I created the account (DavidDreggors) on the Dasha site.
The main Dasha wiki page says:
"Anyone can submit a driver for inclusion into the dasha images. In order to do so, create an account for yourself here and send an email to the centos-developers mailing list ( link ) with details of the driver you would like to get included. You will then get an svn account where you can directly import the drivers and the associated Makefiles and config scripts required to make it build. "
I have the account and have already sent the request here. Is there anything else I need to do?
How/what do I have to do once I get the svn account? What files do I need to upload?
I have already sent this list the spec and src.rpm. The source code us not changed from the snapshot downloaded from snapshots.madwifi-project.org.
The driver is an RPM of the latest snapshot of madwifi. I do not own the source code I just created the rpm and used it on a fresh install here on my laptop.
The need for this driver is for anyone using a laptop (or other) that has the Atheros AR5007EG wireless card. The stock ath5k kernel module does not support this card.
Currently the only module that works well is madwifi. I have tried the kmod-ath5k from the elrepo-testing repo, which does work, but locks your machine up solid when bringing down the interface. Not a good solution yet.
David, please report details about your hardware to the existing Red Hat bug-report at:
ath5k module freezes when interface is brought down https://bugzilla.redhat.com/show_bug.cgi?id=499999
We have to get this fixed upstream and once it is, we will have a working kmod-ath5k in the same effort :-)
Besides as far as I have tested, the madwifi solution (for newer Atheros hardware) replaces some of the other wireless infrastructure and thus breaks other wireless drivers and is impossible to package properly for RHEL/CentOS.
Dag Wieers wrote:
David, please report details about your hardware to the existing Red Hat bug-report at:
ath5k module freezes when interface is brought down https://bugzilla.redhat.com/show_bug.cgi?id=499999
We have to get this fixed upstream and once it is, we will have a working kmod-ath5k in the same effort :-)
Done, I just submitted a comment on that bug.
Besides as far as I have tested, the madwifi solution (for newer Atheros hardware) replaces some of the other wireless infrastructure and thus breaks other wireless drivers and is impossible to package properly for RHEL/CentOS.
Was unaware of that, can you give examples of the libraries/modules that get overwritten (for rollback/restore purposes)?
I have not seen any issues yet that I am aware of but once we get a fix for kmod-ath5k and I go back to that driver... I might?
will installing the kmod-ath5k after a removal of madwifi-hal-snapshot.rpm fix this?
On Mon, 11 May 2009, David Dreggors wrote:
Dag Wieers wrote:
Besides as far as I have tested, the madwifi solution (for newer Atheros hardware) replaces some of the other wireless infrastructure and thus breaks other wireless drivers and is impossible to package properly for RHEL/CentOS.
Was unaware of that, can you give examples of the libraries/modules that get overwritten (for rollback/restore purposes)?
The problem is not that they may or may not get overwritten, the problem is that if you have a set of modules that use the original mac80211 and cfg80211 kernel modules, and the new madwifi that use modified (newer?) mac80211 and cfg80211 modules, depending on which mac80211 and cfg80211 modules you have loaded, only one set of wireless drivers may work.
I have not seen any issues yet that I am aware of but once we get a fix for kmod-ath5k and I go back to that driver... I might?
You may not if you only have one wireless chipset that you use. People using a USB wireless stick because they have problems with their atheros, might not get the original drivers to work because of the above mess that was created.
Dag Wieers wrote:
On Mon, 11 May 2009, David Dreggors wrote:
Dag Wieers wrote:
Besides as far as I have tested, the madwifi solution (for newer Atheros hardware) replaces some of the other wireless infrastructure and thus breaks other wireless drivers and is impossible to package properly for RHEL/CentOS.
Was unaware of that, can you give examples of the libraries/modules that get overwritten (for rollback/restore purposes)?
The problem is not that they may or may not get overwritten, the problem is that if you have a set of modules that use the original mac80211 and cfg80211 kernel modules, and the new madwifi that use modified (newer?) mac80211 and cfg80211 modules, depending on which mac80211 and cfg80211 modules you have loaded, only one set of wireless drivers may work.
People using a USB wireless stick because they have problems with their atheros, might not get the original drivers to work because of the above mess that was created.
Well that's no good. Not sure if you got my email, I added a bug submission to upstream as you asked. They have now assigned someone to the bug.
On Tue, 12 May 2009, David Dreggors wrote:
Dag Wieers wrote:
On Mon, 11 May 2009, David Dreggors wrote:
Dag Wieers wrote:
Besides as far as I have tested, the madwifi solution (for newer Atheros hardware) replaces some of the other wireless infrastructure and thus breaks other wireless drivers and is impossible to package properly for RHEL/CentOS.
Was unaware of that, can you give examples of the libraries/modules that get overwritten (for rollback/restore purposes)?
The problem is not that they may or may not get overwritten, the problem is that if you have a set of modules that use the original mac80211 and cfg80211 kernel modules, and the new madwifi that use modified (newer?) mac80211 and cfg80211 modules, depending on which mac80211 and cfg80211 modules you have loaded, only one set of wireless drivers may work.
People using a USB wireless stick because they have problems with their atheros, might not get the original drivers to work because of the above mess that was created.
Well that's no good. Not sure if you got my email, I added a bug submission to upstream as you asked. They have now assigned someone to the bug.
I saw it, we need more people to test the ath5k module with their hardware and report back so it is apparent this is a general problem.
-
Dag Wieers -
David Dreggors -
Marcus Moeller