Dave, have you tried disabling bluetooth? Intrepid works great for me in
terms of this issue, but with Hardy bluetooth seemed to have been a variable
with a definite effect on my suspend/resume issues.
On Mon, Dec 15, 2008 at 6:52 AM, DaveAbrahams d...@boostpro.com wrote:
@Leann,
I can't
Guys, you can't believe how happy I am with Intrepid. It feels very solid
and the display looks sharper too. But best of all, I'm now able to fully
trust the suspend/resume! I've tried all the previously failing scenarios
and more, and it works every time. Battery like is much better also.
I second that. I tested upgrading to the beta release when it first came
out, and the suspend/resume scenarios that previously failed were working
beautifully.
On Fri, Oct 24, 2008 at 8:20 PM, Seth Randall [EMAIL PROTECTED] wrote:
I've been running the Intrepid beta for a few weeks and
I installed the 2.6.27.2-generic kernel on Linux Mint 5 I my results are
similar to Daniel's. This is with OR without the USB hub and devices
plugged in. On resume, the screen is blank and it looks like the machine
locked up. But in fact, the OS is active. I had to fly blind, but I did a
Daniel, it's possible that what I'm seeing could be a different bug, but
based on my experience I would say its the same bug but that a dock triggers
slightly different/extra symptoms. The issue I'm seeing is reported by
others in the same threads as your total lockup issue.
I did experience the
I got riled up about Dave Abrahams saying that the linux-usb developers
wanted console debug info and pointed to a thread where the bug triage guy
was saying that nobody is reporting this issue. I was told to take a chill
pill, and that I can't expect the kernel devs to test Ubuntu-specific
You're right, of course. I owe my apologies to Alan Stern and the
developers. Sorry guys. Chill pill taken, Dave. :)
On Tue, Jul 29, 2008 at 7:47 AM, DaveAbrahams [EMAIL PROTECTED]
consulting.comwrote:
David, please take a chill pill. I agree the situation is a little
ridiculous, but it's
I'm sorry, but this is a little ridiculous. I read that thread, and this
guy, Alan Stern, is saying that nobody else is reporting this problem?? Has
he done the slightest bit of research into the issue?
I've been a developer for 19 years and I've seen this too many times. I'm
sorry, but its
I'm using a Dell m1330 (4GB ram, nvidia graphics, Dell wireless module)
and I'm seen this problem initially with 64-bit Hardy. After trying
everything suggested on the net, I installed 32-bit Hardy, and I'm
having the exact same symptoms. I don't have a dock, but I'm using a
USB hub that I have
