Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16528 - [kernel26] 2.6.31 + madwifi do not connect pppoe

Attached to Project: Arch Linux
Opened by Pawel (kraftman) - Thursday, 08 October 2009, 20:17 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 18 November 2009, 11:57 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Hi,

After upgrade to kernel 2.6.31.x and latest madwifi 0.9.4.4096-1 I can't connect to network. Card is working, but iwlist 'ath0 scan shows' less results then previous and it doesn't show the network I always connect to, which has the highest signal strange... I tried to use ath5k, but results are similar or even worse. I connect using PPPoE. Log shows something like this:

Bad one (2.6.31.3, madwifi 0.9.4.4096):

pppd[3082] Plugin rp-pppoe.so loaded.
pppd[3082] RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
pppd[3096] pppd 2.4.4 started by root, uid 0
pppd[3096] Timeout waiting for PADO packets
pppd[3096] Timeout waiting for PADO packets
pppd[3096] Timeout waiting for PADO packets
pppd[3096] Timeout waiting for PADO packets

Good one (2.6.30.6, madwifi 0.9.4.3952):

pppd[3085] Plugin rp-pppoe.so loaded.
pppd[3085] RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
pppd[3099] pppd 2.4.4 started by root, uid 0
pppd[3099] PPP session is 87
pppd[3099] Using interface ppp0
pppd[3099] Connect: ppp0 <--> ath0
pppd[3099] CHAP authentication succeeded
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 18 November 2009, 11:57 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see comments
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 09 October 2009, 01:06 GMT
  • Field changed: Summary (2.6.31 + madwifi do not connect pppoe → [kernel26] 2.6.31 + madwifi do not connect pppoe)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Tobias Powalowski (tpowa)
Probably this should be reported this to upstream (bugzilla or linux kernel mailing list), if not already reported. Thanks.
Comment by Pawel (kraftman) - Friday, 09 October 2009, 14:53 GMT
Thank you for your response, I will report this.
Comment by Pawel (kraftman) - Saturday, 10 October 2009, 15:58 GMT
Bug report is here:

http://madwifi-project.org/ticket/2351

What I found madwifi from repository detects networks only up to channel 10 and madwifi-hal-0.10.5.6-r4100-20090929 fixed my problem.
Comment by Pawel (kraftman) - Wednesday, 18 November 2009, 11:20 GMT
It is probably, because newer madwifi uses CRDA (Central Regulatory Domain Agent) and default is set to US where only channels 1-11 are available. I installed CRDA package, selected proper country and I can connect now (however, I don't use madwifi anymore, because this also fixed my "problem" with ath5k driver which is working great). I think this bug report can be marked as resolved or invalid. Thanks.

Loading...