pygmy_giant wrote:I don't understand the grumblers.
Because, for some things, the USB DOES NOT WORK. Simple as that. No matter how much power you throw it at, what firmware you use, what distro you run, how short your cables are, or any other factor whatsoever. I can provide examples of both keyboards and 3G modems that do not work. Ever. At all. Others have found the same with wireless sticks, webcam and custom devices that are FULLY USB COMPLIANT. They just don't work.
The USB might work for you, if you're lucky and using it only on certain devices. But it doesn't "just work". It's not a question of working better, but at all on those devices (which have no compatibility issues with Linux or anything else).
This does appear to be the case, but I see no problems on my system, so for me it does 'just work'
It was not acknowledged for months after reporting (check my thread history if you like). It isn't being rectified. There's one guy looking at it in his spare time and even the people who designed and built their own custom USB devices and who spotted the problem first can't help that much (they have provided full USB logs using expensive USB analyzers, that PROVE that USB packets sometimes just drop out of existence after being acknowledged by the RPi and still nothing close to a fix has surfaced because the "community" contains the same number of kernel hackers as any other project - i.e. very, very, very, very few, and even fewer with in-depth knowledge of the RPi and/or USB).
The problem appears to be with the Synopsis driver and additionally high interrupt latency on Linux, not anything provided by the Foundation or indeed the SoC supplier.
This non-acknowledgement of the problem and not having enough people "in the know" able to fix these things is the source of the complaints. Hell, I still haven't heard back if the perfectly-working 2Gb SD card that *I* had to send to the guy at Broadcom who sent it onto their driver-writer in Taiwan ever had any success in getting it to work on the RPi. It worked on DOZENS of other devices and has for years, but the RPi didn't even recognise it one time in 20 of trying. Without that card, I can't say that the problem it experienced was "fixed", because the other cards I have always worked.
The problem, as shown by the thread above and others, is acknowledged. Who did you send the card to at Brcm? There has been an SD card patch I believe. Whether it fixed that card I do no know.
It's certainly a big deal when you plan projects around having a USB-compatible device that actually isn't. When you set up whole electronics projects of your own that just need the RPi to sit into the middle and it doesn't recognise the hardware you're using (despite EVERYTHING else doing so). It's also a problem if, say, you're a school and randomly 10% of the things you try (or buy) to use with the RPi just don't work at all.
You planned (important?) projects around a new bleeding edge product released in order to find out bugs exactly like the ones being seen here prior to the full educational release?
This is a problem, that's been present on the forums and the kernel bug-tracker for months, and we're no closer to a fix *today* than we were when they were first reported. My RPi is in a box until there's a firmware update which states that this problem may be improved / fixed. It has been for weeks now. Without USB it's a bit useless for my projects. Hell, last week I put it into the attic because I can't do anything with it yet and all the associated hardware was in my way.
We are considerably closer to a solution than before. Not there yet though.
This is a problem. It's now been admitted. One person "on the team" has now said unofficially what they think the cause is. There's still no sign of a fix or even a suggestion as to what form the fix could take (reducing interrupt latency is a bit of a dark-art, especially in custom systems). In the meantime, people like me have been asking for months for someone to look into it and had non-working hardware in that time. Sure, if you want a device that views SD card contents on a HDMI TV, you could knock one up with a RPi. I have, after various faffing about with reporting SD card compatibility problems, done just that - including using a USB mouse and keyboard (of a particular model that *did* work). But USB is present on both models and still does not work for everyone, or for all the devices it should. As far as my project and some of the hardware I need to use are concerned, the USB port on the RPi doesn't exist, which brings everything to a grinding halt. And if the RPi had been sold without a USB port, I wouldn't have touched it for my project because of that.
How many months have you had you device? Two? Saying 'asking for months' seems an exaggeration given how long the devices have actually been available.
This device is not for you. Sell it. We are sorry its not for you, and the best people to fix the problem are working on it, and hopefully things will improve for the minority who are seeing problems. I'm finding it quite difficult to see what else can be done.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.