BcRich
July 6th, 2012, 10:01 PM
I'm using Ubuntu and Kubuntu 12.04 and luvin it! and also really like that there are regular security fixes available through update manager.
I'm also using the proprietary AMD Catalyst drivers.
The problem I'm having is that since I've upgraded to 12.04 there have been numerous updates to the x window system and the kernel. Not that I'm complaining about the updates (cause I think it's great that bugs are fixed so rapidly, even though I haven't experienced any major ones as of yet). The actual problem is that each time one of these components is updated X fails to start. I realize this has to do with the Catalyst driver, as I am booted into a CLI at which point I have to reinstall the AMD driver. Reboot and everything is fine. I then have to re-configure my Catalyst drivers (once in Ubuntu) to the previous setup (because I have two monitors running off two GPU's), This in turn requires two additional restarts. That's a total of 3 restarts, in case you weren't counting :)
Anyway, am I seriously the only person having this problem? Surely there must be alot of Ubuntu users out there running Catalyst on 12.04 experiencing this issue, or not?
Do you have any suggestions for me as to how I can avoid this issue, keep the Catalyst drivers and still obtain the security fixes (incl X and kernel updates)?
I suppose it wouldn't be such a big issue if the the kernel and X window system were updated at the same time. In other words not have an X update causing the graphics driver re-installation issue, then having a kernel update a few days later causing the same issue again. I imagine that all updates identified by Update Manager are from an official Ubuntu/ Canonical team? If so why are the updates not delivered in a more system-contextualized time-frame? Or perhaps they are?
This is not a complaint btw, I'm just curious and looking for a way of avoiding this problem I've been having.
I hope that people that are new to Ubuntu and using similar setups are not put off by this problem as expecting to boot up your computer as normal and being kicked to a CLI (I'd imagine) could be quite a challenge for a new comer.
Thanks if you can offer and comments or help :)
I'm also using the proprietary AMD Catalyst drivers.
The problem I'm having is that since I've upgraded to 12.04 there have been numerous updates to the x window system and the kernel. Not that I'm complaining about the updates (cause I think it's great that bugs are fixed so rapidly, even though I haven't experienced any major ones as of yet). The actual problem is that each time one of these components is updated X fails to start. I realize this has to do with the Catalyst driver, as I am booted into a CLI at which point I have to reinstall the AMD driver. Reboot and everything is fine. I then have to re-configure my Catalyst drivers (once in Ubuntu) to the previous setup (because I have two monitors running off two GPU's), This in turn requires two additional restarts. That's a total of 3 restarts, in case you weren't counting :)
Anyway, am I seriously the only person having this problem? Surely there must be alot of Ubuntu users out there running Catalyst on 12.04 experiencing this issue, or not?
Do you have any suggestions for me as to how I can avoid this issue, keep the Catalyst drivers and still obtain the security fixes (incl X and kernel updates)?
I suppose it wouldn't be such a big issue if the the kernel and X window system were updated at the same time. In other words not have an X update causing the graphics driver re-installation issue, then having a kernel update a few days later causing the same issue again. I imagine that all updates identified by Update Manager are from an official Ubuntu/ Canonical team? If so why are the updates not delivered in a more system-contextualized time-frame? Or perhaps they are?
This is not a complaint btw, I'm just curious and looking for a way of avoiding this problem I've been having.
I hope that people that are new to Ubuntu and using similar setups are not put off by this problem as expecting to boot up your computer as normal and being kicked to a CLI (I'd imagine) could be quite a challenge for a new comer.
Thanks if you can offer and comments or help :)