Ubuntu 13.04 Ad-hoc disallowed for Asus/Acer netbooks #5

Closed
glamrock opened this Issue Jul 17, 2013 · 8 comments

Comments

Projects
None yet
6 participants
Collaborator

glamrock commented Jul 17, 2013

Granted, this isn't our issue per se, but there is currently an incompatibility with Ubuntu 13.04 (Raring Ringtail). The Broadcom drivers don't allow for ad-hoc mode at all, and there is currently no patch. Affected devices include various Asus and Acer netbooks (including Asus Eee PC 1225B).

Collaborator

westbywest commented Jul 17, 2013

Could you specify which broadcom driver in particular (i.e. take output of 'lsmod | sort' and trim it), and which kernel you've observed this problem on? There may be alternate drivers available.

Collaborator

hawkinswnaf commented Jul 17, 2013

@technosopher and I were discussing this offline today. I will
investigate whether the "new" driver implicitly or explicitly disables ibss.

On 07/17/2013 01:22 PM, Ben West wrote:

Could you specify which broadcom driver in particular (i.e. take output
of 'lsmod | sort' and trim it), and which kernel you've observed this
problem on? There may be alternate drivers available.


Reply to this email directly or view it on GitHub
#5 (comment).

Collaborator

eighthave commented Jul 17, 2013

Shouldn't this bug report/discussion be happening on the redmine?

I believe the old open source b43 driver has working adhoc mode. And I think
some broadcom drivers do support adhoc somewhat, but some definitely do not
have any usable support.

This is definitely not an issue in commotion-mesh-applet. NetworkManager
tries to handle it somewhat, but its not easy to do even there, where its a
more natural place for it.

On 07/17/2013 01:32 PM, hawkinswnaf wrote:

@technosopher and I were discussing this offline today. I will
investigate whether the "new" driver implicitly or explicitly disables ibss.

On 07/17/2013 01:22 PM, Ben West wrote:

Could you specify which broadcom driver in particular (i.e. take output
of 'lsmod | sort' and trim it), and which kernel you've observed this
problem on? There may be alternate drivers available.


Reply to this email directly or view it on GitHub
#5 (comment).


Reply to this email directly or view it on GitHub:
#5 (comment)

PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81

Collaborator

westbywest commented Jul 17, 2013

If redmine is the proper venue, indeed yes, gotta mova on over. Besides, my understanding is that b43 is considered a legacy chipset now. Can look up the actual Broadcom chipsets where this problem occurs?

Agreed, bug reports should be done via Redmine. Our current practice is to use Github just for pull request discussions.

Also agree w/ .hc/eighthave, chipset driver incompatibilities w/ IBSS are out of our hands. Sadly, many netbooks, including our own fleet of Asus, do not support ad-hoc, and haven't since I started working at OTI :(

Also, just wanted to say thanks Griffin for finding this issue, which we have failed so far to document anywhere at all :)

It's good to know which hardware works and which doesn't...we should start a list!

Collaborator

glamrock commented Jul 17, 2013

Actually, @technosopher found the bug, but I wanted to make sure it was
documented. Most of the testing netbooks in the office are susceptible,
and the hardware is really common. Good to get more eyes on it.

@hawkinsw and Jordan are working on some possible fixes right now.

technosopher was assigned Oct 3, 2013

Collaborator

technosopher commented Jan 4, 2014

Linux client now includes enough checks and warnings for incompatible drivers that I think this issue can be designated "dealt with," if not completely resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment