From: Yousuf Khan on 31 Dec 2009 05:28 J.O. Aho wrote: > bbbl67(a)spammenot.yahoo.com wrote: >> Robert Tomsick wrote: > >>> I'd say that (given how easy BIOS upgrades usually are) it's worth a >>> shot. >> I've actually had very mixed results with BIOS upgrades, and when the >> mixed results were bad, they required the purchase of a new motherboard >> and processor! So I'll avoid them if I can. > > BIOS updates don't affect the CPU, only the motherboard. They do if you can't find a motherboard that supports your processor anymore. This has happened to me years ago, and not just once. > Don't forget that a motherboard may have a ROM with a backup BIOS, which can > be restored in case something would go wrong with a BIOS update, check the > motherboards manual to see if has a such and how to restore. This is a laptop, not a DIY desktop board designed for fiddling like this. A backup BIOS is a feature you'll only find in some desktop motherboards, definitely not all of them, and definitely not on most laptop boards. My laptop is out of warranty, and if anything goes wrong I won't be able to boot -- into anything. Yousuf Khan
From: Yousuf Khan on 31 Dec 2009 05:32 Jasen Betts wrote: > On 2009-12-30, bbbl67(a)spammenot.yahoo.com <bbbl67(a)spammenot.yahoo.com> wrote: >> Anyways, I ran through the steps of SuspendKernel debugging guide that >> Florian Diesch provided in this thread, and it looks like I'm the victim >> of this bug: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/386641 > > so switching to kernel 2.6.29 works for you? Well, that's the next thing I'm going to be trying. If it's even available for Ubuntu 9.10. > he also said using an older bios "F8" worked for him, have you tried that. That's irrelevant to me, I'm not using the same motherboard. In fact, this is happening on a laptop rather than a desktop. So it looks like it's more widespread than just on the one motherboard model. Yousuf Khan
From: Fredderic on 1 Jan 2010 12:40 On Wed, 23 Dec 2009 10:06:08 -0500, bbbl67(a)spammenot.yahoo.com wrote: > Has anyone got a stable system back after they've gone into standby > and/or hibernate modes? My systems just freeze when attempting to > come back from this mode usually. I've never been game to try it. This system was set up six years ago, when hibernate and standby were only just being talked about, as far as I'm aware. I have no idea what I'd need to do to retro-fit my system to use hibernate. Ubuntu itself came along sometime after... The Debian install disk I used, installed the latest 2.2 kernel, which I then upgraded to unstable to get the newer 2.4 kernel. Heck, I still use LILO, because GRUB wasn't a viable option at the time either, and so far I haven't seen any reason to change. The one use I'd have for hibernation, though, is if it's possible to swap to Windows and then come back to where I'd left off (it usually takes me an average half hour to shut down everything I've got running, any time I wish to run something that requires Windows). Although I suspect there might be issues doing that, with regards to the fact that I frequently access the Windows partition (it holds my media and general downloads storage locations). But yeah, if someone knows whether it'd be safe to use in that situation, and what I'd have to do to get things ready to give it a go, I'd be most interested. Fredderic
From: Yousuf Khan on 3 Jan 2010 21:09 Jasen Betts wrote: > On 2009-12-30, bbbl67(a)spammenot.yahoo.com <bbbl67(a)spammenot.yahoo.com> wrote: >> Anyways, I ran through the steps of SuspendKernel debugging guide that >> Florian Diesch provided in this thread, and it looks like I'm the victim >> of this bug: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/386641 > > so switching to kernel 2.6.29 works for you? I finally got a chance to try it out. I couldn't find a 2.6.29 kernel available for my distro, so I found a 2.6.28 kernel. And yes, it looks like that kernel works, both suspend and hibernate came back to life. Staying with a 2.6.28 kernel is not a totally viable option however, as my touchpad didn't work with it, so I had to attach an external mouse. > he also said using an older bios "F8" worked for him, have you tried that. I think the fact that both an older Linux kernel and Windows worked, while the current Linux kernel doesn't is proof that the problem lies with the kernel and not the BIOS. Yousuf Khan
From: ceed on 3 Jan 2010 21:47
On Sun, 03 Jan 2010 20:09:33 -0600, Yousuf Khan <bbbl67(a)yahoo.com> wrote: > Jasen Betts wrote: >> On 2009-12-30, bbbl67(a)spammenot.yahoo.com <bbbl67(a)spammenot.yahoo.com> >> wrote: >>> Anyways, I ran through the steps of SuspendKernel debugging guide that >>> Florian Diesch provided in this thread, and it looks like I'm the >>> victim of this bug: >>> >>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/386641 >> so switching to kernel 2.6.29 works for you? > > I finally got a chance to try it out. I couldn't find a 2.6.29 kernel > available for my distro, so I found a 2.6.28 kernel. And yes, it looks > like that kernel works, both suspend and hibernate came back to life. > > Staying with a 2.6.28 kernel is not a totally viable option however, as > my touchpad didn't work with it, so I had to attach an external mouse. > >> he also said using an older bios "F8" worked for him, have you tried >> that. > > > I think the fact that both an older Linux kernel and Windows worked, > while the current Linux kernel doesn't is proof that the problem lies > with the kernel and not the BIOS. > > Yousuf Khan The problem may be that there's been a BIOS update and that the newer kernels works with the newer version of the BIOS. I had that happen on one of my other (Samsung Q310) laptop. The original BIOS works with <2.6.30 kernels while the newer BIOS works flawlessly with 2.6.30>.. Shows that Linux is catching up with computer BIOS technology. It used to be that you need to purchase a laptop that had been around for a while to make sure it worked. Not so anymore. I have now several times the last 18 months purchased brand new models that just came out and have had Linux work without problems whatsoever. I did of course check he specs making sure they didn't come with ATI and certain Intel graphics adapters or other problematic components. I keep a shortlist of those around so I can weed out laptops which will likely have problems. What really surprise me though is that I purchased a netbook from little vendor specializing in Linux laptops and netbooks. I could never get wireless to work correctly with the preinstalled Ubuntu Netbook Remix. I was working with support for weeks and finally had to give up and return it. Others has the same problem. I can't believe that they didn't test that before they chose that model as their netbook offering. Oh well..... -- //ceed |