Re: System Dead after updates (or upgrade)
As for the graphics: do you ever get to the KDE splash screen or do you just get the kubuntu one before you are thrown into command line?
I had this graphics driver issue and in my case I had the kubuntu splash screen on start up, but when it tried to load the Xserver I only got garbage on the screen (curiously enough, the mouse pointer was there, in the shape of an "x").
If you get the KDE splash screen (and the proper login screen in the first place), that means Xserver is running and it is not a graphics problem.
You can check whether your graphics chip is supported on the ATI website. My card is only 2 years old and is no longer supported...
As for internet: when you start the command line from grub (i.e. press esc on startup) you can select console/terminal/command line (whatever it is called) and the same with networking. Select the command line with networking and then you should be fine. Generally I would not expect that to work with WLAN, so get a wired connection.
But as liquidator says, you should have internet from a wired connection already.
Of course you can't get any GUI applications from the command line, but you can update packages with apt-get.
In case your Xserver is working and you get to the login screen where you can, for example select the desktop you want, it's probably a KDE problem.
You can test that by installing a lightweight desktop environment (like 'icewm') and starting that - if it works you might consider removing and reinstalling KDE completely.
You can install icewm from the command line with apt-get
(the '-s' is for a dry simulation run to see if there are conflicts; remove it if you are actually installing it)
I recommend having a lightweight desktop installed as a backup anyway, in case KDE breaks (happened to me before). So you can at least use a web browser and email (and actually everything else, only it does not look so pretty).
Also, did you have any non-standard/experimental repositories in your sources.list (the repository file of apt-get; '/etc/apt/sources.list')? This caused some conflicts, when I upgraded...
As for the graphics: do you ever get to the KDE splash screen or do you just get the kubuntu one before you are thrown into command line?
I had this graphics driver issue and in my case I had the kubuntu splash screen on start up, but when it tried to load the Xserver I only got garbage on the screen (curiously enough, the mouse pointer was there, in the shape of an "x").
If you get the KDE splash screen (and the proper login screen in the first place), that means Xserver is running and it is not a graphics problem.
You can check whether your graphics chip is supported on the ATI website. My card is only 2 years old and is no longer supported...
As for internet: when you start the command line from grub (i.e. press esc on startup) you can select console/terminal/command line (whatever it is called) and the same with networking. Select the command line with networking and then you should be fine. Generally I would not expect that to work with WLAN, so get a wired connection.
But as liquidator says, you should have internet from a wired connection already.
Of course you can't get any GUI applications from the command line, but you can update packages with apt-get.
In case your Xserver is working and you get to the login screen where you can, for example select the desktop you want, it's probably a KDE problem.
You can test that by installing a lightweight desktop environment (like 'icewm') and starting that - if it works you might consider removing and reinstalling KDE completely.
You can install icewm from the command line with apt-get
Code:
apt-get install -s icewm
I recommend having a lightweight desktop installed as a backup anyway, in case KDE breaks (happened to me before). So you can at least use a web browser and email (and actually everything else, only it does not look so pretty).
Also, did you have any non-standard/experimental repositories in your sources.list (the repository file of apt-get; '/etc/apt/sources.list')? This caused some conflicts, when I upgraded...
Comment