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!
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!
FS#30717 - [linux] 3.4.X r8712u wireless card fails to connect
Attached to Project:
Arch Linux
Opened by Pierpaolo Valerio (gondsman) - Tuesday, 17 July 2012, 06:59 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 17 September 2012, 08:06 GMT
Opened by Pierpaolo Valerio (gondsman) - Tuesday, 17 July 2012, 06:59 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 17 September 2012, 08:06 GMT
|
DetailsDescription:
I use a D-link DWA-131 wireless stick with the r8712u driver. I have problems when I'm connecting to https sites (both with browsers or cli programs). Even if I try to download something with wget from a https website it fails repeatedly giving the error "SSL3_GET_RECORD: decryption failed or bad record mac". It is definitely a probelm with the r8712u module, as using wired network works fine and also using the lts kernel (3.0 branch) doesn't show any problem. Logs don't show anything wrong with the firmware loading or any other message related to this module. Let me know if I can provide any additional information. Reported on linux 3.4.4 (I also tried compiling linux 3.5rc7 from AUR with the same results) I use networkmanager to connect (if that can help) |
This task depends upon
Comment by Jelle van der Waa (jelly) -
Saturday, 21 July 2012, 18:05 GMT
Please inform the kernel maintainers ( upstream)
Comment by Pierpaolo Valerio (gondsman) -
Monday, 23 July 2012, 11:55 GMT
I just reported the bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=45071
Comment by Pierpaolo Valerio (gondsman) -
Monday, 17 September 2012, 07:06 GMT
The bug is now solved upstream, this bug can be closed.