Red Hat Bugzilla – Bug 232885
HSDPA Performance with Sierra MC8755
Last modified: 2010-10-22 09:46:55 EDT
We have some ThinkPads T60 and X60 with internal MiniPCI UMTS / HSDPA Card.
The Card is a Sierra MC8577 (USB Id 1199:6804). In RHEL5 there is a sierra
Kernel Module which supports this card in general but Lenovo has it's own
Product ID (6804). In Fedora 7 with Kernel vmlinuz-2.6.20-1.2986.fc7 there is a
newer Sierra Module that supports the card fine. Without the sierra Module we
can use the card with the usb-serial Kernel Module but only with about 40 KB/s
in Downlink. With the Sierra Module on Fedora 7 we get 140 - 150 KB/s!
Might be this changeset:
Created attachment 154851 [details]
Update driver to 1.0.5
Created attachment 154852 [details]
Patch to add device ID
Patch based on upstream.
Created attachment 160592 [details]
Test kernel with proposal applied patch
Hello, I built and attached the test kernel package with applied patch to solve
the problem. Could you please test the package on target machine and report
here if the bug is solved?
Hans-Gerd, your comments are not automatically posted to BZ when entered in
I'll forward your message to BZ for you:
i tested your kernel on my x60. I get about 140 KB/s when downloading a
file, about 45 KB/s when uploading and ping round trip times from 140 ms.
The lsmod shows that the sierra module is loaded. So I think it's all
This event sent from IssueTracker by navid
See also bug 247884.
Created attachment 198981 [details]
Ivan's bigger backport after a review turnaround
Ivan neglected to attach the patch which I acked, so doing it now. However,
now that I looked at option.c for bug 249660, I think we should be a bit more
proactive with the port. The original Kevin's driver had a few issues such
as the use of -EINPROGRESS, since fixed.
Created attachment 199081 [details]
Same as before, but with few more IDs removed
On second thought, Ivan had a good idea. The current sierra wants to be too
modern with dynamic URBs and everything. It's a bridge too far.
> Ivan neglected to attach the patch which I acked, so doing it now. However,
> now that I looked at option.c for bug 249660, I think we should be a bit more
> proactive with the port. The original Kevin's driver had a few issues such
> as the use of -EINPROGRESS, since fixed.
Is it necessary to attach posted patch here? I'm a newbie in Red Hat.
*** Bug 247884 has been marked as a duplicate of this bug. ***
Created attachment 249401 [details]
The proposed patch
Hello, I would like to ask you to test again a test kernel package. We found
some issue that had to be solved. So we need to know if the current solution
works well. Could you please test this kernel package and report a feedback?
You can find it on:
Thanks a lot.
Ivan, the customer now requires the device to work on T61 so I had to add the
correct USB IDs to the patch for USB_DEVICE(0x1199, 0x6813).
With this tiny modification to your patch, the customer's feedback was positive.
Thank you Navid, I will send a corrected patch into mailing-list.
Created attachment 279781 [details]
Final patch posted into kernel mailing list
Do we have access to hardware for testing?
Jay, I have a T61 here in EMEA available for testing.
QE ack for RHEL5.2 then.
You can download this test kernel from http://people.redhat.com/dzickus/el5
this bug has been tagged for inclusion in the RHEL5.2 release notes. please post
the necessary content for it. thanks!
the RHEL5.2 release notes will be dropped to translation on April 15, 2008, at
which point no further additions or revisions will be entertained.
a mockup of the RHEL5.2 release notes can be viewed at the following link:
please use the aforementioned link to verify if your bugzilla is already in the
release notes (if it needs to be). each item in the release notes contains a
link to its original bug; as such, you can search through the release notes by
Thanks Ivan. release note add to "Driver Updates => Network".
Please advise (before April 15) if any further revisions are required. thanks!
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.