Hello,
I am having serious problems with my Intrepid (8.10) system after an attempt to install a 2nd hard disk went terribly wrong (installing the ext3 filesystem on the disk did not complete - I have disconnected the drive). I have a number of files I'd like to recover, after which I'm OK with reinstalling Kubuntu if necessary.
I have searched several forums, including this one, but found nothing that seemed to apply.
The motherboard is an ASUS X8V-X with a dual-core processor, ATI AGP video card with the stock Kubuntu drivers. I'm running KDE 4.2.2, fully patched.
After rebooting, I get to the default 8.10 desktop but get no login window. Mouse movement is jerky as if the processor is 100% occupied with other processes. I have done the following:
1) get into the grub bootup menu and choose the latest kernel in rescue mode.
2) fschk the file system (it's OK)
3) clean to try and reclaim space (in case an error log has totally occupied the disk)
4) xfix to try and fix an XORG problems.
It seems to me I need to boot into a root console at this point to try and fix a config file, but I don't know what would need fixing.
Can anybody suggest what I should be doing next? While I usually don't operate in console mode, I'm not particularly afraid of it.
Thanks in advance,
Frank Alviani
I am having serious problems with my Intrepid (8.10) system after an attempt to install a 2nd hard disk went terribly wrong (installing the ext3 filesystem on the disk did not complete - I have disconnected the drive). I have a number of files I'd like to recover, after which I'm OK with reinstalling Kubuntu if necessary.
I have searched several forums, including this one, but found nothing that seemed to apply.
The motherboard is an ASUS X8V-X with a dual-core processor, ATI AGP video card with the stock Kubuntu drivers. I'm running KDE 4.2.2, fully patched.
After rebooting, I get to the default 8.10 desktop but get no login window. Mouse movement is jerky as if the processor is 100% occupied with other processes. I have done the following:
1) get into the grub bootup menu and choose the latest kernel in rescue mode.
2) fschk the file system (it's OK)
3) clean to try and reclaim space (in case an error log has totally occupied the disk)
4) xfix to try and fix an XORG problems.
It seems to me I need to boot into a root console at this point to try and fix a config file, but I don't know what would need fixing.
Can anybody suggest what I should be doing next? While I usually don't operate in console mode, I'm not particularly afraid of it.
Thanks in advance,
Frank Alviani
Comment