Hi.
rt2860sta? That doesn't seem to be shipped with ubuntu anymore.
(and rt28xxpci/lib worked fine last time I checked)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only:
Did test on 5 PCs. 2 had 64 bit. The 2 with 64 bit had problems with
rt2800pci and compiling rt2860sta had the same problem. Now here is the
thing i also tried 32 bit and on 2 pcs it did not work. It started working
after upgrading 3 days ago. Only one worked out of the box. I am writing
from an
Hello Luis,
Unfortunately, I no longer have this wireless card.
As this bug is fixed, maybe there is another problem.
Feel free to open a new bug report and don't hesitate to indicate that
the problem looks the same as this one but with a newer kernel.
--
You received this bug notification
Thank you will do that when I get to work. 4 full hours working every
possible scenario and still it did not work. Your bug report is exactly
what is happening. Now my question is, is this only 64 bit?
On Nov 25, 2013 5:21 AM, Matthieu Baerts matt...@gmail.com wrote:
Hello Luis,
According to Wolfgang, this issue was only affected 64 bits users.
But your problem is certainly not exactly the same as this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
Thanks friend. Just tested with a live flash drive of ubuntu 13.10 32 bit.
The wifi card works perfectly.
I then installed ubuntu on the pc 32 bit again and it worka out of the
box.
The problem is 64bit specific I see.
On Nov 25, 2013 7:56 AM, Matthieu Baerts matt...@gmail.com wrote:
According
Annoying :-/
Then don't forget to link your new bug report with this one :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only: regression: kernels =2.6.34: rt2800pci: load
This is back. Using 13.10 64 Bit am having this issue:
[5.955844] ieee80211 phy0: rt2800_load_firmware: Error - PBF system
register not ready
[6.771242] ieee80211 phy0: rt2800_load_firmware: Error - PBF system
register not ready
[7.574555] ieee80211 phy0: rt2800_load_firmware: Error
If I do a workaround mentioned
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/673440/comments/8
I get the following error while using the rt2860sta module
ERROR!!! NICLoadFirmware failed, Status[=0x0001]
!!! rt28xx Initialized fail !!!
NICLoadFirmware: MCU is not ready
Not only that
Hello,
It seems that this bug is still not fixed because my kernel (version 2.6.39 but
2.6.38 on natty too) loads a wrong driver for my RT2860 wireless card
(rt2800pci instead of rt2860). The crash has been fixed but the it loads the
wrong firmare.
It's not a problem for most encryptions used
@Matthieu, your issue is different from the topic of this bug. It
belongs on a separate bug report, and since you've already opened a new
bug it can be addressed there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 2.6.35-28.49
---
linux (2.6.35-28.49) maverick-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #726796
[ Colin Ian King ]
* SAUCE: Dell All-In-One: Remove need for Dell module alias
[ Manoj Iyer ]
*
** Tags added: verification-needed-maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware
Error with ralink
** Tags added: verification-done
** Tags removed: verification-needed-maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only: regression: kernels =2.6.34: rt2800pci: load
Accepted linux into maverick-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: linux (Ubuntu Maverick)
Just tested: Bug is fixed in 2.6.35-28-generic #49 from proposed. :-)
@Seth:
There is another severe bug in this driver for rt3090 hardware that we have
identified a fix for in linux-next. It looks like it should be cherry-picked
for natty. Details in bug 662288. Maybe you could take a look?
@Wolfgang:
Great, glad that we were finally able to get it taken care of! Thanks
for all your help.
Andy's the guy to get something into natty, so I'll be sure to bring bug
662288 to his attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The error handline patch has been merged into the wireless-next tree.
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-
next-2.6.git;a=commit;h=d76dfc612b40b6a9de0a3fe57fe1fa3db7a1ae3b
I've put up some test builds with all patches backported at the
following location for
Attaching v3 of the skb_pad() error checking patch, backported from the
version currently in wireless-next.
** Patch added: 0003-rt2x00-Check-for-errors-from-skb_pad-calls-v3.patch
@Seth
Looks good to go now. Tested your new test build in station mode and ad-
hoc mode on my [1814:0781] (rt2800pci).
Thanks,
Wolfgang
** Changed in: linux (Ubuntu Maverick)
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
SRU Request:
Impact: A regression was introduced between lucid and maverick that
causes firmware loading to fail with the RaLink RT2860 wireless adapter
on amd64.
Fix: The following patches backported from upstream address this issue.
The first two are included in =2.6.38-rc1, the third is
Hi
Have installed Pardus 2011 64 bit version and have had no problems with the
RaLink RT2860..
Not being a code writer only a computer user, how come it works OK in
Pardus KDE 4.6 ?
perhaps you could look at their code implementation for the problem with
the Ralink RT2860
chris
--
You
Okay, looks like we're (finally) close to getting the error handling
patch upstream. I'll get maverick SRU patches ready to be submitted as
soon as I get the final okay from Ivo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Seth
I tested the error path and entry-skb = NULL turns out to be absolutely needed
before returning, otherwise there will also be a hard panic.
Moving padding to the start looks good to me. The only thing changing the skb
length afterwards is guaranteed to do so by multiples of 32 bits.
Maybe
@Wolfgang:
Thanks again for testing. The unlikely() might make sense. It's actually
a hint to the compiler to allow it to optimize certain code paths that
have an extremely probability of not being taken (90%+ or so), which
would seem to be the case here, although I get the idea that this
@Seth
Probably what I ought to do is prepare a patch against mainline and get
some review from the wireless maintainers to answer some of these
lingering questions. I'll plan to do that early next week before I do
any more patches agains maverick.
Great. That is best. We want the same
Hi Seth,
Sorry for the lateish response. Great that you are backporting my patch.
Be aware that I don't have that much C/kernel/WLAN knowledge beyond this
patch (my first).
The usb drivers use REGISTER_TIMEOUT32(entry-skb-len), evidently
basing the timeout value on the length of the data
** Changed in: linux (Ubuntu Maverick)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only: regression: kernels =2.6.34: rt2800pci: load
@Wolfgang:
The usb drivers use REGISTER_TIMEOUT32(entry-skb-len), evidently
basing the timeout value on the length of the data written. Based on
that it would now be REGISTER_TIMEOUT32(entry-skb-len + padding_len).
Yes, I overlooked that, thanks for pointing it out.
However, that time seems
** Changed in: linux
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware
This bug was fixed in the package linux - 2.6.38-1.27
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: linux (Ubuntu Maverick)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added:
linux-headers-2.6.35-25-generic_2.6.35-25.44+lp659143v1_amd64.deb
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659143/+attachment/1808408/+files/linux-headers-2.6.35-25-generic_2.6.35-25.44%2Blp659143v1_amd64.deb
--
You received this bug notification because
** Attachment added:
linux-image-2.6.35-25-generic_2.6.35-25.44+lp659143v1_amd64.deb
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659143/+attachment/1808429/+files/linux-image-2.6.35-25-generic_2.6.35-25.44%2Blp659143v1_amd64.deb
--
You received this bug notification because you
I've attached debs for a test build with my backports of Wolfgang's
patches. Please let me know whether or not these packages fix the issue.
** Changed in: linux (Ubuntu Maverick)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Wolfgang:
Looks like both of these patches hit mainline as of 2.6.38-rc1. I'll
take a look to see if they can be included in a maverick SRU.
One question about the patches though. In the first patch skb_pad() is
called without checking the return value. I'm not all that familiar with
the
** Also affects: linux (Ubuntu Maverick)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only: regression: kernels =2.6.34: rt2800pci:
Moving to fix committed for Natty as the patches have hit mainline in
v2.6.38. Review and testing is still required for acceptance into
Maverick.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Committed
** Changed in:
Instructions in comment #16 worked for me, thanks Wolfgang!
This is my device, a RT3090 as well, apparently the same as Phil's:
04:00.0 Network controller: RaLink RT3090 Wireless 802.11n 1T/1R PCIe
Subsystem: Lite-On Communications Inc Device 6632
Flags: bus master, fast devsel,
OK, so you did see the firmware load error with one kernel. I think what
happened on the other was the same phenomenon as I described in bug
662389. Perhaps caused by rebooting instead of a cold start. There is no
reason to believe those two almost identical kernels would behave
differently with
** Description changed:
+ [UPDATE Dec 16, 2010]
+ My fix is in linux-next. See comment 16.
+
UPSTREAM:
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2010-November/002310.html
HARDWARE:
RaLink RT2860 [1814:0781]
rt2x00_set_chip: Info - Chipset detected - rt:
My fix for this firmware loading issue:
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=412b31334b831a8c2909afaca017c5a236ac2dd0
along with the the needed preparation patch:
Thank you for your help Wolfgang!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/659143
Title:
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with
ralink [1814:0781]
--
Doesn't seem to fix the RT3090 here. If I force modprobe to load the
rt2800pci or rt2x00pci driver, the card will scan for networks quite
happily, but won't establish a connection (WPA encrypted, pre-shared
password mode).
If I go back to blacklisting rt2800pci et al, then the (insanely buggy)
Hi Phil
Three things:
First, your card scans, so it does not have this bug (firmware loading)
anymore, or never had it anyway. Good.
Second, please make doubly sure that only one driver can bind to the card per
boot. This might be the source of strange problems from what I have seen.
What I'd
P.S. sudo modprobe -v rt2800pci is right for your hardware, too.
rt2x00pci is just a component shared with other drivers, not a driver by
itself. It will be pulled in automatically along with a lot of other
shared components (about 7 or 8).
--
You received this bug notification because you are a
OK, I renamed the driver, then rebooted and modprobed rt2800pci. This
had the nice side-effect of kicking the other laptop off the WiFi, and
I couldn't get it to associate.
rmmod -rv rt2800pci followed by modprobe -v rt2860sta got me a Kernel
Panic. When the laptop rebooted, the BIOS threw up
Please file a new report by typing ubuntu-bug linux in a terminal
window.
rmmod -rv rt2800pci followed by modprobe -v rt2860sta got me a Kernel
Panic.
Did it panic on unloading rt2800pci or on loading rt2860sta?
That sounds a bit like bug 662288. Although there there was an immediate freeze
on
Did it panic on unloading rt2800pci or on loading rt2860sta?
That sounds a bit like bug 662288.
On loading rt2860sta after unloading rt2800pci.
Anyway, we need a trace of that panic. Maybe comment 15 of bug 662288
can help you get one.
Might be a bit hard when the machine locks solid after
You might want to take a look at bug 594866; that's the thread where I
originally reported my issues, and exactly describes what was happening
with the RT3090 in my MSI U230 netbook. No errors relating to firmware
loading, but I can't connect to the WLAN... Load rt2860sta instead (by
blacklisting
commit 412b31334b831a8c2909afaca017c5a236ac2dd0
Author: Wolfgang Kufner wolfgang.kuf...@gmail.com
Date: Mon Dec 13 12:39:39 2010 +0100
rt2x00: Fix firmware loading regression on x86_64.
Commit 6175ddf06b6172046a329e3abfd9c901a43efd2e changes the way
memcpy_toio() works for
Hi Wolfgang,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the
** Changed in: linux
Assignee: (unassigned) = Wolfgang Kufner (wolfgangkufner)
--
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with
ralink [1814:0781]
https://bugs.launchpad.net/bugs/659143
You received this bug notification because you are a member of Ubuntu
Just tried on lucid:
linux-backports-modules-compat-wireless-2.6.35-2.6.32-25-generic_2.6.32-25.24_amd64
This backported rt2800pci works perfectly fine in ad hoc WEP mode (21.3
Mbits/sec with iperf).
--
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with
ralink
Above configuration (comment #12) also works in infrastructure mode with
WPA2 (iperf 5Mbit/s).
--
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with
ralink [1814:0781]
https://bugs.launchpad.net/bugs/659143
You received this bug notification because you are a member of
Tried natty desktop live 20101112.1:
64bit shows the load firmware error. 32 bit does not.
--
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with
ralink [1814:0781]
https://bugs.launchpad.net/bugs/659143
You received this bug notification because you are a member of
** Also affects: linux
Importance: Undecided
Status: New
--
64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with
ralink [1814:0781]
https://bugs.launchpad.net/bugs/659143
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am going to undupe this, because I worry it might not be effective to have
the more detailed bug report the duplicate.
Also: https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Still, bug #594866 quite likely imho might have the same root cause. It
does have all the ingredients from the
** Description changed:
- UPSTREAM:
+ UPSTREAM:
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2010-November/002310.html
HARDWARE:
RaLink RT2860 [1814:0781]
rt2x00_set_chip: Info - Chipset detected - rt: 2872, rf: 0003, rev: 0200.
SYMPTOM:
Syslog says:
58 matches
Mail list logo
