On Tue, 17 Mar 2009 12:17:29 -0400, Michael Yang wrote: > On Tue, Mar 17, 2009 at 3:51 AM, Thorny <thorntreeh...@gmail.com> wrote: > >> On Mon, 16 Mar 2009 19:39:05 -0400, Michael Yang wrote: >> >> > After recent upgrade, my system becomes kind of mess up. >> > >> > My story is that I did a apt-get upgrade of some packages to >> > squeeze/sid by accident(I didn't change the 'testing' in my >> > source.list). So I downgrade most of packages back to dist lenny by >> > pinning packages except the kernel (2.6.24 kernel) and few packages. >> > Everything works well but the acpid. >> > >> > >> Michael, it probably would have been better to have left this in the >> other thread because it really is a continuation of your original >> problem and that way, others could have the full story. Remember I >> warned you that there were no guarantees with an APT pinning downgrade >> from a mixed system. >> >> Because you had that mixed system and what you tried (downgrade) is not >> really supported, this current problem could be related. > > > Sorry about that, Thorny. I posted this as a separate thread because I > thought it could be a different problem in lenny and I metioned what > happened in my case. Actually everything works fine after I downgrading > from my mixed system by pinning packages. Most of packages are > downgraded to lenny version and few still remains in testing version. > But the system is running very well without any problems. > > I have to admit that I did one more step after that. To get a pure lenny > dist, I performed a 'apt-get dist-upgrade' which upgrades the kernel as > well, from 2.6.24 to 2.6.26. That's when I found the problem of acpid. > Then I went back to .24 kernel, the problem still exists. That's why I > thought if it could be problems related to lenny dist. > > Okay, I follow your logic. However, it's always best to give all the information of what you did so anyone looking can have the whole picture when they are speculating about what might have happened.
Unfortunately, speculating is all I can do, I've never actually had to try that downgrade process, I just know in theory it sometimes can work. I expect it is somewhat dependent on the individual system, what software is on it and how it is configured. When doing supported upgrades, new configuration files are updated to what is needed for new versions but I doubt there is any mechanism to reverse any of those changes. Thus, I don't have any idea if that might have caused your problem. But, in theory, one is supposed to keep it pinned and upgrade (which is actually downgrade) until the system is back tracking the pure release version one wants. I have no idea if getting back to "most" of the packages is sufficient. From what you stated, you still have some packages at versions that aren't Lenny, are they at current Squeeze versions or are they at some transitional stage from when they were in Lenny when it was testing? (rhetorical question, don't need to answer here) I would argue that your statement, "But the system is running very well without any problems", isn't strictly correct, it isn't shutting down correctly, eh? Shutdown works correctly on my Latitude with a pure Lenny system but it is an older model laptop so that isn't definitive. I did a superficial google and there do seem to be some bugs reported with Acpi and D630. Several seem to relate to a runaway condition, when your system hangs do the fans go to full on, if so, you might want to search more intensively to see if there is any solution short of un-installing acpid, or figuring out anything about video driver. Hopefully, someone with a D630 will jump in here and tell if theirs is working with Lenny. If I get any more ideas to try, I'll get back to this thread. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
