What is Digg?49 Comments
- magamiako, on 11/01/2009, -1/+65I'm not exactly sure what's going on with this article here, as it tries to blame Windows 7 for the Iphone's woes on this chipset, but then clearly states it's a chipset problem.
1. Windows 7 and Windows Vista share the same driver model for USB. Therefore, if it worked in Vista, it will work on 7.
2. Intel provides the drivers for its system board devices. So I'm guessing if it is a software problem (blaming the OS), it can easily be fixed in drivers.
3. Microsoft is not at fault, no matter how much you want to blame them. They pretty much have nothing to do with whether or not Intel's chipset plays nice with Apple's device.
4. PS. I've been running 7 for almost a year now and syncing my iphone to it and have yet to experience any problems. - iiBeLiEvE, on 11/01/2009, -6/+50Buried for misleading title; it's not Windows 7, it's Intel.
- waydee, on 11/01/2009, -5/+34Call me a cynic but I'd bet on this being an iTunes problem, with every release that bloated piece of crap has just gotten worse.
- TheWindBlows, on 11/01/2009, -12/+38I would say the iPhone/iTunes is to blame. A USBFS of over 500 to 1000 times what any other device needs is needed for the iPhone with iTunes ( Why iPhone/iTunes sync'ing in linux with Virtualbox didn't work until Virtualbox and Linux kernel had that redone with a heavier, more flexible, approach ).
- waydee, on 11/01/2009, -0/+25That error code comes from iTunes.
- uncwidiot, on 11/01/2009, -1/+25Bluetooth drivers != USB drivers.
- HappyScrappy, on 11/01/2009, -0/+13What are you talking about? What do you mean a USBFS? What do you mean 500 to 1000 times what any other device needs? 500 to 1000 times larger? Faster?
- MerchantofPanic, on 11/01/2009, -5/+16Maybe its just Intel doing to Apple, what Apple is doing to Palm?
- apollyon, on 11/01/2009, -2/+12I would be surprised if USB hard drives and other hi-data-rate devices don't have issues with these PCs who use this chipset. If the manufacturers don't do full USB characterization on their P55 boards before releasing them to the public, there will be a lot more cross-company finger pointing going on. It comes down to the motherboard manufacturer and how well their engineers check for things like signal integrity and device failures and USB spec compatibility. It's not Microsoft's fault, and it certainly isn't the iPhone's fault. The iPhone is just the first to be reported because it's such a widely used device. And one used heavily by the early adopter crowd.
But, then again, this may be fixed in another month and the problems will only exist on these first P55 boards. If thats the case, then this will shortly be a non-issue. - kingatrock, on 11/01/2009, -1/+9lol owned.
- Grogtron, on 11/01/2009, -4/+11What, Intel has never written a buggy driver?
The real news is why does it take Intel so damn long to push out bug fixes.
Dugg down just because it's Engadget and not the source (plus, it's stupid). - TheWindBlows, on 11/01/2009, -0/+5The USB FS Buffer in Linux it used to be a max of 16K because pretty much every device tended to need much less than that. The iPhone comes along and can't sync until the buffer size is increased to 128K .
Now with more recent kernels 2.6.30 and beyond theres a completely different design thats made to be flexible. So a kernel module doesn't need to be recompiled just for iPhone/iTunes buffer needs.
I imagine this same issue is whats affecting the board and its driver. - SuicideMouse, on 11/01/2009, -3/+8If you know a lot more then name another Type of USB device that will have issues being reported.
- HappyScrappy, on 11/01/2009, -0/+5Well, if he's right and as he says below it's a problem with signal integrity, then plugging in a USB hub in between the host and the iPhone should fix the problem. Does anyone know, does it fix the problem?
- akwok, on 11/01/2009, -2/+6What does Windows 7 have to do with this at all? Are they implying that Windows XP, Vista, or for that matter, OSX on a P55 machine won't have these problems? Doesn't seem like it, since they straight up state that this should be fixed before Apple attempts to release their i5/i7 machines (on the P55 chipset)..
It's purely a hardware (driver) problem. Buried for unnecessary bias and sensationalism. - NeoTechni, on 11/01/2009, -1/+4we can only hope
- commenter01, on 11/01/2009, -0/+3so many questions! arrrgh!
- bipolarruledout, on 11/01/2009, -0/+3Because 16k should be enough for anybody?
- masterkenobi, on 11/01/2009, -3/+6Doesn't matter, Mac fanboys will still find a way to blame Microsoft. Oops I'm sorry, "M$".
- TheWindBlows, on 11/01/2009, -0/+2Actually in this case it was. The only benefit going over 16k as pointed out by kernel dev's is to help lazy user space developers. Other than that benefit it just makes things more bloated.
- Drizzit, on 11/01/2009, -1/+3It's a problem on the X58 as well.. I had to go out and buy a NEC chipset based USB card..
Both I believe use the ICH10R USB chipset. - InfernoX, on 11/01/2009, -5/+7Don't worry, it's written by one of those people that thinks a computer is the OS. (likely a mac user)
- JoeHague, on 11/01/2009, -1/+3Exactly what I was thinking.
The problem is the P55 chipset drivers. The only real connection to Windows 7 is the new PCs being sold with those Intel boards.
For anyone that's interested, I have 7 and my iPhone syncs without a problem.
I guess that's because I have an AMD board/ - bringitontimx, on 11/01/2009, -3/+5some of engadget's posts are so drivelish they resemble Fox news. i dont think you can get any more biased and partisan than engadget.
- magamiako, on 11/01/2009, -0/+1HappyScrappy:
There are lots of drivers in Windows, that when released by Microsoft with the OS, get the "Microsoft" naming tag. That doesn't mean the driver was provided by them, it just means that they released the driver with the OS.
However, if you install Intel's chipset software drivers, it will update some of the drivers for you to Intel's latest versions rather than the ones they provided Microsoft. - FriniK, on 11/02/2009, -0/+1i was just about to upgrade to that system.... :(
fixitfixitfixitfixitfixitfixitfixitfixitfixitfixitfixitfixitfixitfixitfixit - HappyScrappy, on 11/01/2009, -0/+1The article doesn't say anyhting about updating the drivers to Intel ones.
The USB drivers for the chipset are from MS. Period. - ehaugan, on 11/01/2009, -1/+2@Bluetooth drivers != USB drivers.
Considering my bluetooth receiver plugs into a USB port, I'd have beg to differ. - techdever, on 11/01/2009, -0/+1what the ...
- techdever, on 11/01/2009, -0/+1waydee wins the match
- crossmr, on 11/01/2009, -3/+3The title clearly says "Intel p55 to blame"
- Philbert, on 11/01/2009, -2/+2I guess that means my P35 is safe.
- InfernoX, on 11/02/2009, -1/+1conveniently preceded by "iphone and windows 7 don't play nice"
- doctordbx, on 11/01/2009, -5/+4Any article that starts with "The iPhone is one of the most wildly popular phones the world has ever seen" is going to be a load of *****. I'm not doubting the popularity of the iPhone, but do we really need the hyperbole?
- Spuy767, on 11/01/2009, -6/+3Especially considering the fact that no OS will ever be as ubiquitous as XP was.
- czarcasm, on 11/01/2009, -4/+1How dare you.
/Adam Carolla - OandA, on 11/01/2009, -11/+8the title says INTEL TO BLAME. pretty clear to me.
- apollyon, on 11/01/2009, -15/+11Yeah... The P55 chipset has seriously F***ed up USB. I think this is just the first report of many to come about that chipset and its USB woes.
I know a lot more... but am not at liberty to discuss. - HappyScrappy, on 11/01/2009, -7/+2MS writes the USB driver. Check for yourself in the device manager. Since USB controllers follow a standard called EHCI (created by Intel), they all use the same driver and are supposed to work the same. So MS can wrote one driver that is supposed to work with all of them. So yeah, MS has something to do with it.
Windows 7 works fine for me too. On my X58 chipset. - brodie7838, on 11/01/2009, -6/+1It's not *just* Windows, just as it's not *just* the chipset, but a combination of both, together that cause the problem.
You obviously don't have a P55 chipset so your setup doesn't fit this MO, so it doesn't mean a thing that you have no problems. - mjoe, on 11/01/2009, -8/+2who uses a P55? it's all about the X58
- macmcraeart, on 11/01/2009, -9/+3yeah my new classic and Windows 7 - 64 don't play nice either. I have my music library on an external HD and the sync is taking all day.
- DaviDTC, on 11/01/2009, -10/+4http://digg.com/microsoft/Wintel_7_machines_freeze ...
Oh, that's why you went with the blogspam. - sputnikv, on 11/01/2009, -7/+1considering that API and GTK+ toolkits force execute the assembly language independently from the CDS with the -OVERALL flag, there may be reason to use 9.1.1.1015 or later providing it doesn't yield any macro leaks
- abdhjops, on 11/01/2009, -11/+3ubiquitous OS? wow...someone's jumping the gun
- QQQQUUUU, on 11/01/2009, -13/+0I am sure democrats will fall for this one
- exspasticcomics, on 11/01/2009, -21/+4let the win7 related bugs begin...
- MikeOSX, on 11/01/2009, -19/+2"0xE8000065"... I thought we got rid of these type of messages with XP.
- ehaugan, on 11/01/2009, -26/+2Wrong. My Apple wireless bluetooth keyboard worked flawlessly on Windows Vista and no longer works in Windows 7.
© Digg Inc. 2009
— Content created and posted by Digg users is