A tale of 2 monitors and 3 KDE Linux distros

The computer I run my 3d printer on is an old Pentium 4 computer. It is a while since I distro-hopped and I decided after a year of running Mageia Linux it was time for a change. I am now a KDE convert; all my desktops run KDE.
On a side note, if you want to run a 3d printer on an older computer I totally recommend Mageia. It
runs both printrun (aka pronterface) and slic3r with no issues.

It was the weekend and I thought I would spend some time to backup and install something. Probably Debian based and definitely KDE.
I chose Mint KDE because I had heard glowing reports on various podcasts (Mint-cast, Linux Luddites etc).
At the same time I chose to add a second monitor to my computer because my eyes have been tired recently.
I took the computer and installed Mint KDE 14.10. with no issues. The computer has 2 drives, a 120GB that once was the Windows XP location, and a 250GB drive that I added to dual boot with XP. I chose the 120GB drive and let it use the whole hard drive.
The computer used to have two monitors, and and so I already had the video card and monitor available. I added the video card and rebooted, and everything looked good.
OK, now to add that second monitor. When I rebooted I got a blank screen for 1.5 minutes or so then magically I saw the screens. One good and one blank.
I played around for a bit with the screen settings then it dawned on me – the bios!
I went into the bios settings and modified the setting so it would use the PCI express slot first.
I rebooted and both screens now had an image. Only thing is the image was stretched to a weird combination of max resolutions.
I went to the screen set up and tried but there were no settings to change, at least that I could see. That was when I vaguely remembered Mint had given me this issue before.
Once I got the monitors working I was informed that GL had a problem and that here would be no fancy rotating cube and that the combined resolution would need to be less that a particular size.
I tried clicking Firefox and a few other items and found that not necessarily that Mint ran slow but that there was no bouncing cursor (by default) to indicate to wait and that something was happening. The other thing was that it crashed several times.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s