Screen rez post drive swappout

[Riff Gaffer]

Following some hardware maintenance, I had to swap my drives out earlier to test a drive. Initially I needed to change the PSU, and I wanted to test an old hard drive to ensure it was good - it seemed like an ideal opportunity since I'd got the case open

PSU swapped out ok (from a 600 to 750W), hard drive failed to respond, put the other drive(s) back in - raid 0(?, subject to conf, striped anyhow) and nothing.

I did adjust the bios to account for raid/lack of and it did prove problematic more than once. However, I'm back with an almost functional machine but screen res is very low - 1024, as opposed to the 1600 I'm used to.

I can't adjust it, but all else is going ok it seems (although I've not yet checked sound)

So... I've saved my home partition to a backup drive, but here are some relevant questions:

How do I restore my resolution? Drivers are the same as they were before I changed the drives

If I can't, then I'm ok starting from scratch but how do I efficiently save my data (free, can't pay for stuff) so that my new install "feels" the same?

What are good back up scenarios for future fail-planning?

TIA

[Seve]

Hello:

What version and arch of Fedora are you using?

What video drivers do you have installed ?

What if any, are the errors present in your /var/log/Xorg.0.log file ?

Seve

[Riff Gaffer]

Originally Posted by Seve

Hello:

What version and arch of Fedora are you using?

What video drivers do you have installed ?

What if any, are the errors present in your /var/log/Xorg.0.log file ?

Seve

Ok I'm a bit of a newbie so bear with me:

I'm using Fed 12 32bit, and I used Leigh's guide to install the drivers for an nvidia 7900GS - it worked perfectly until I swapped the drive out.

I've looked in the Xorg.0.log file and can't see any obvious errors but it's a bit wall of text - what should I look for? I also have a .bak version of the same but can't read it.

I noticed I've got some outstanding transactions but that halts saying my /boot partition is too small - is that related? If it's unrelated it'll need fixing anyhow, yes?

Cheers

Edited to add I'm ok with reinstalling from scratch if I can back up my data - such as Evolution mail etc, should that be a simpler option

[Seve]

Hello:

Your boot partition error is now or is likely to be a show stopper at some point in the future.

I believe that you need at least 500MB for a boot partition. Someone can either confirm that or at the very least check the Release Notes and or the Installation Guide
http://docs.fedoraproject.org/en-US/index.html and look for the partitioning guide or recommendations.

From a terminal you can run the following to glean out any / most reported errors

cat /var/log/Xorg.0.log | grep -i EE

cat /var/log/Xorg.0.log | grep -i WW

Given the /boot error that you have, it might be advisable to backup all the things that you need and do a fresh install.

Seve

[Riff Gaffer]

ok thanks.

I am unsure how my boot partition got so small - nothing has changed on the install itself so far as I can tell. Well, clearly it has or at least the system thinks that it has.

I can copy my home partition across and restore any subsequent data but any advice for saving my emails?

Thanks for your advice Seve

[Riff Gaffer]

ok I have some more info:

I learned a new trick:

package-cleanup --oldkernels

That got rid of a lot of guff from my boot partition and made enough space.

I'm not on a ridiculously high resoutlion for no obvious reason (I actually suspect my dearly beloved and very faithful 7900GS is going to the gfxcard graveyard in the sky) but I ran your suggested diagnostic and got this:

(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(II) config/hal: Adding input device ImPS/2 Generic Wheel Mouse
(**) ImPS/2 Generic Wheel Mouse: always reports core events
(**) ImPS/2 Generic Wheel Mouse: Device: "/dev/input/event4"
(II) ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons
(II) ImPS/2 Generic Wheel Mouse: Found scroll wheel(s)
(II) ImPS/2 Generic Wheel Mouse: Found relative axes
(II) ImPS/2 Generic Wheel Mouse: Found x and y relative axes
(II) ImPS/2 Generic Wheel Mouse: Configuring as mouse
(**) ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5
(**) ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE)
(**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
(**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
(II) ImPS/2 Generic Wheel Mouse: initialized for relative axes.
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) VESA(0): Unable to estimate virtual size
(WW) VESA(0): No valid modes left. Trying less strict filter...
(WW) VESA(0): Unable to estimate virtual size

---------- Post added at 03:56 PM CDT ---------- Previous post was at 03:00 PM CDT ----------

ok reverting to booting into an older kernel seems to have largely resolved that issue. I'm guessing the new kernel updated and the driver's aren't yet ready - judging by Leigh's guide thread.

ok so is there a way to make a specific kernel the default boot?