I think I messed up.
HP Pavilion dv5035nr, 1.5GB RAM, 74GB drive, ATI Radeon Xpress 200M. Kubuntu 8.04, kernel 2.6.24.18, KDE 3.5something.
I was noticing horribly slow performance while on battery power. I set the Battery Monitor to CPU Policy of Performance, but it still reported 800MHz instead of 1.6GHz. I last installed an ATI proprietary driver but things were working fine while plugged in. I noticed in System Settings for Display that the LCD was detected as type "Plug n Play". I tried changing that to "LCD 1280x800" which is the native resolution. When I rebooted, the resolution was 1024x768. Squished and ugly. So I went back into System Settings and changed it back to "Plug n Play" and rebooted.
And kaboom. Here's what happens:
1. Message on screen says "Starting up..."
2. Kubuntu banner comes up with progress bar that turns blue as it goes across the screen.
3. "Starting K Display Manager kdm" appears for a second...
4. Screen flicks to some seriously screwed up colors then flicks back to kdm start messages.
5. Screen flicks to black with grey with an "X" cursor in the middle for a second then flicks back to kdm start messages.
6. Screen flicks to black for a microsecond and then back to messages which stop.
I hit Ctrl+Alt+F1 to get to a log in and that's where I am now. I have Windows XP MCE and openSUSE 11 available from System Commander.
I obviously corrupted the crap out of something. I don't have access to a network right now so I can't do any "apt-get"s or anything to reinstall something.
=Where do I start with what logs or files whose contents you wonderful geniuses need to see to get me back to working? :-)
Update: I just typed "start x" for the heck of it ad here's what I get:
...(stuff)
(==) log file: "/var/log/Xorg.0.log", time and date
(==) Using config file: /etc/X11/xorg.conf"
(WW) fglrx: no matching Device section for instance (BusID PCI:1:5:0) found
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7f6e420]
2: /usr/bin/X11/X(InitOutput+0x6fc) [0x80aa12c]
3: /usr/bin/X11/X(main+0x296) [0x8074526]
4. /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d01450]
5: /usr/bin/X11/X(FontFileCompleteXLFD+0x201) [0x8073a91]
Fatal server error:
Caught signal 11. Server aborting
giving up.
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server error.
and back to prompt. I have a backup (done with Ghost 14 while booted under XP) from before I did a bunch of updates and messing around with bluetooth (almost got KitchenSync to connect to my Nokia 6126 but that's another story) so worst comes to worst, I can do a restore to that point and try again.
Still, I'd appreciate any help/advice anyone can give me on what's going on here and what happened. How can I try to fix the sluuuuuuuugish performance while on battery without trying different things? Performance is fine while plugged in. It's just while on battery that it's unbearable.
Any way I can try to get back up and running with what I've got or should I just chuck it and try restoring and going again?
HP Pavilion dv5035nr, 1.5GB RAM, 74GB drive, ATI Radeon Xpress 200M. Kubuntu 8.04, kernel 2.6.24.18, KDE 3.5something.
I was noticing horribly slow performance while on battery power. I set the Battery Monitor to CPU Policy of Performance, but it still reported 800MHz instead of 1.6GHz. I last installed an ATI proprietary driver but things were working fine while plugged in. I noticed in System Settings for Display that the LCD was detected as type "Plug n Play". I tried changing that to "LCD 1280x800" which is the native resolution. When I rebooted, the resolution was 1024x768. Squished and ugly. So I went back into System Settings and changed it back to "Plug n Play" and rebooted.
And kaboom. Here's what happens:
1. Message on screen says "Starting up..."
2. Kubuntu banner comes up with progress bar that turns blue as it goes across the screen.
3. "Starting K Display Manager kdm" appears for a second...
4. Screen flicks to some seriously screwed up colors then flicks back to kdm start messages.
5. Screen flicks to black with grey with an "X" cursor in the middle for a second then flicks back to kdm start messages.
6. Screen flicks to black for a microsecond and then back to messages which stop.
I hit Ctrl+Alt+F1 to get to a log in and that's where I am now. I have Windows XP MCE and openSUSE 11 available from System Commander.
I obviously corrupted the crap out of something. I don't have access to a network right now so I can't do any "apt-get"s or anything to reinstall something.
=Where do I start with what logs or files whose contents you wonderful geniuses need to see to get me back to working? :-)
Update: I just typed "start x" for the heck of it ad here's what I get:
...(stuff)
(==) log file: "/var/log/Xorg.0.log", time and date
(==) Using config file: /etc/X11/xorg.conf"
(WW) fglrx: no matching Device section for instance (BusID PCI:1:5:0) found
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7f6e420]
2: /usr/bin/X11/X(InitOutput+0x6fc) [0x80aa12c]
3: /usr/bin/X11/X(main+0x296) [0x8074526]
4. /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d01450]
5: /usr/bin/X11/X(FontFileCompleteXLFD+0x201) [0x8073a91]
Fatal server error:
Caught signal 11. Server aborting
giving up.
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server error.
and back to prompt. I have a backup (done with Ghost 14 while booted under XP) from before I did a bunch of updates and messing around with bluetooth (almost got KitchenSync to connect to my Nokia 6126 but that's another story) so worst comes to worst, I can do a restore to that point and try again.
Still, I'd appreciate any help/advice anyone can give me on what's going on here and what happened. How can I try to fix the sluuuuuuuugish performance while on battery without trying different things? Performance is fine while plugged in. It's just while on battery that it's unbearable.
Any way I can try to get back up and running with what I've got or should I just chuck it and try restoring and going again?
Comment