Results 1 to 4 of 4
Hi guys,
Ive upgraded my system from pentium 4 to Athlon 64 dual core, after booting the new system with the old HD (fairly straight forward), I wanted to upgrade ...
- 12-19-2011 #1Just Joined!
- Join Date
- Aug 2005
- Posts
- 5
Linux shutdown unexpectedly after apt-get
Hi guys,
Ive upgraded my system from pentium 4 to Athlon 64 dual core, after booting the new system with the old HD (fairly straight forward), I wanted to upgrade some packages. After running apt-get the system suddenly shuts down. This repeated on every boot.
Thinking this had something to do with the new system migration, I've decided to reinstall Debian squeeze (was a good time to upgrade anyhow, as I wanted a 64 bit system), so I got the netinst cd and again, when apt-get is run (from the install system this time), the machine shuts itself down!
Any help is appreciated here
-Ishay Peled
- 12-20-2011 #2Just Joined!
- Join Date
- Nov 2011
- Location
- New Zealand
- Posts
- 79
Sounds strange to be honest. What happens if you use aptitude instead of apt-get?
- 12-31-2011 #3Just Joined!
- Join Date
- Oct 2009
- Posts
- 1
well, you need find out what is the exact problem. What you can do is, have a live CD (ubuntu) and boot up. try "apt-get update " and see. If it works, then you need to check out your distro. Debian has a lot of distros which are suitable for AMD systems. try one of them. cheers
- 01-01-2012 #4Just Joined!
- Join Date
- Mar 2011
- Location
- pittsburgh
- Posts
- 44
So when you say shutdown, do you mean switching to init run level 0 (i.e. killing processes cleanly, and powering off the machine) or it just turns off as if the power cord was pulled?
If it is switching to run level 0 I would first runand see if apt-get has become a symlink to halt or shutdown. As dumb as that sounds I have encountered a similar issue after family members did full version updates on Ubuntu installs.Code:ls -l /usr/bin | grep apt
And either way, I would have a look at the logs. If memory serves your package manager should have its own log file.
nixblog makes a great suggestion also, try using aptitude to see what the results are.
Try installing raw DEB packages with dpgk.
If dpkg works you might get away with removing apt-get which is a front end to dpgk and then reinstalling it with dpgk to hopefully clean up whatever corruption or bad configuration is causing this odd issue.


2Likes
Reply With Quote
