View Full Version : Gutsy update crash
JIMW428
October 6th, 2007, 07:50 PM
I recently upgraded Fiesty to Gutsy and everything seemed to be going reasonably well until yesterday. I downloaded the most recent updates, and following installation I was instructed to reboot. After rebooting, a black screen appeared and began scrolling with instructions being executed.This occurred so rapidly that I was unable to gather any info. I then attempted to load the recovery version (Kernel 2.6.22-13 generic- (recovery)) with similar results. I then reverted to the previous versions with basically the same results.
I have Ubuntu installed on a dedicated drive. I ran a hard drive test and surface scan with no reported errors.
On the last screen that appears, everything reports "OK" except for the the top line:
[ 296.413587] hda_codec: unknown model for ALC883, trying auto-probe from BIOS
The last line that appears is a prompt "root@jim-intel-920:`# " with a flashing cursor
I don't have a clue what to do now
rickycodie
October 6th, 2007, 08:14 PM
this should be moved to the development forums.
gutsy is still beta you probably shouldn't be using it try fiesty.
in the mean time try this
sudo dpkg-reconfigure xserver-xorg
ryanVickers
October 6th, 2007, 08:33 PM
yes, and you should consider your self lucky it boots to a prompt :p
The update manager should never be used for distro upgrades!!!
MrFSL
October 6th, 2007, 08:52 PM
The update manager should never be used for distro upgrades!!!
This is incorrect or plain wrong! Why include this as an option of a proprietary update manager system if it isn't to be used?
I have used it no problems. I have used it and had problems. I have both had, and NOT had problems with CLI as well... - my point is, you had a problem upgrading - don't blame it on the GUI until you have determined that this was actually the issue.
ryanVickers
October 6th, 2007, 08:54 PM
I've just found that it tends to break stuff when doing a distro update. And, even if it does work, it's still not quite as complete as a full new install.
MrFSL
October 6th, 2007, 09:02 PM
've just found that it tends to break stuff when doing a distro update. And, even if it does work, it's still not quite as complete as a full new install.
This is one of the exact reasons why people discourage the use of Automatix - which you claim to use and in a previous post claimed to never have issues with.
:confused:
ryanVickers
October 6th, 2007, 09:05 PM
This is one of the exact reasons why people discourage the use of Automatix - which you claim to use and in a previous post claimed to never have issues with.
:confused:
yes, I use it and have had nothing but excellent results from it - I don't see what this has to do with the update manager unless you mean that by installing it it breaks updating distos? :-k
Edit: or possibly you mean that how I described the update manager for distros is what people find automatix does?...:-?
MrFSL
October 6th, 2007, 09:16 PM
I mean (quite plainly) that a large number of people have reported problems updating their distro and have tracked the problem back to automatix. So it does not surprise me that you are unable to update your distro in the standard manner since you in fact use automatix.
Thats all.
ryanVickers
October 6th, 2007, 09:18 PM
oh, I see. Thanks for clearing that up. But I still don't see the connection - how can it be so bad!? And if it is, why don't they fix it!?!?!!!!
MrFSL
October 6th, 2007, 09:29 PM
how can it be so bad!?
Read this: http://mjg59.livejournal.com/77440.html
why don't they fix it!?!?!!!!
A lot of people have asked that question... .. still waiting for an answer.
ronacc
October 6th, 2007, 09:43 PM
I have upgraded from fiesty to gutsy using update manager with no issues , I did it as soon as the gutsy repos opened, just changed sources and dist-upgraded.
ryanVickers
October 6th, 2007, 09:44 PM
I just don't trust it - I once upgraded from 6.06 to 6.10 and it really messed it up - and after taking all day too!](*,):evil::-x
MrFSL
October 6th, 2007, 09:45 PM
I have upgraded from fiesty to gutsy using update manager with no issues , I did it as soon as the gutsy repos opened, just changed sources and dist-upgraded.
Thank you. I see there was an new update manager not too long ago. I know that a lot of work goes into ensuring that update manager be bug free.
(Which is why I chose to post to begin with.)
JIMW428
October 6th, 2007, 10:09 PM
Thanks for hi-jacking my thread!
ryanVickers
October 6th, 2007, 10:11 PM
Your welcome :) I'm very good at that ;)
MrFSL
October 6th, 2007, 10:12 PM
sorry. My apologies. :(
JIMW428
October 6th, 2007, 10:20 PM
Your welcome :) I'm very good at that ;)
You're probably good at jerking off too! I was simply looking for help and information, not a lecture. If you're not interested in providing that, it's fine, just do it on your own dime and start your own thread.
ryanVickers
October 6th, 2007, 10:24 PM
I forgot what this is even about :p
Well, I guess that wasn't very nice was it? :(
Anyways, I don't think it was a hard drive/partition problem - I would, yes, reconfigure the X server, and, I don't know, I can't think right now! It feels like the answer is right in front of me, but I'm just blank for answers right now...
Edit: I guess what I'm thinking subconsciously is to do a "System restore", problem is, that's for windows :p
I'm still stuck.
ronacc
October 6th, 2007, 10:28 PM
ryan don't judge anything by the way 6.10 acted , it was a total disaster no mater how you got there . I upgraded first and then when it went release I did a fresh install trying to straighten it out and that was WORSE.
ryanVickers
October 6th, 2007, 10:31 PM
I know! By the looks of what I've read and my own experiences, I won't go into detail why, but it seems like this:
6.06: Awesome!
6.10: disaster! (it's why I almost switched back to windows ;))
7.04: More awesome - the best yet! (it's why I switched to linux)
7.10: Really good, buggier than a Vista CD in an ant farm :p
MrFSL
October 6th, 2007, 10:32 PM
The last line that appears is a prompt "root@jim-intel-920:`# " with a flashing cursor
Sounds like it is dropping you down to single mode.
If can please post the output of:
dmesg
and perhaps the contents of:
/var/log/messages
and
/var/log/syslog
If this is a Xserver issue then as well the contents of:
/var/log/Xorg.0.log
ronacc
October 6th, 2007, 10:47 PM
you could try another upgrade from the terminal apt-get update then apt-get dist-upgrade
youre at a root prompt so you shouldn't need sudo
ryanVickers
October 6th, 2007, 10:50 PM
Did you have video drivers installed - I suddenly think - because of how gusty is supposed to have effects by default - that this has something to do with not just X, but 3D, so you should definitely reconfigure X (verses the probably I had before ;))
atlfalcons866
October 6th, 2007, 11:19 PM
I know! By the looks of what I've read and my own experiences, I won't go into detail why, but it seems like this:
6.06: Awesome!
6.10: disaster! (it's why I almost switched back to windows ;))
7.04: More awesome - the best yet! (it's why I switched to linux)
7.10: Really good, buggier than a Vista CD in an ant farm :p
they dont call ubuntu release 6,10 edgy for a reason
ryanVickers
October 6th, 2007, 11:24 PM
they dont call ubuntu release 6,10 edgy for a reason
I think you mean something like "they don't call it edgy for no reason", but I get the point ;)
(what you said means they call it edgy for no reason :p)
ronacc
October 6th, 2007, 11:28 PM
I think the alc883 bit is a false lead , thats sound and it shouldn't kill the gui , several people are reporting sound problems .
question does it dump you into a root terminal every time or only in recovery mode ?
also you might want to install MC then you can get a console mode file-manager and browse around without a lot of typing. apt-get install mc then just type mc at the prompt.
JIMW428
October 6th, 2007, 11:37 PM
Did you have video drivers installed - I suddenly think - because of how gusty is supposed to have effects by default - that this has something to do with not just X, but 3D, so you should definitely reconfigure X (verses the probably I had before ;))
Reconfiguring x-server seems to have solved the problem. Thanks
vBulletin® v3.8.0 Release Candidate 2, Copyright ©2000-2009, Jelsoft Enterprises Ltd.