Skip to main content

SLED 10 falls down, finally stands up with KDE

I run Suse Linux Enterprise Desktop (SLED) 10 on my system at work. That system is a Boxx system built around an AMD Athlon 64 FX-55 (2.6 GHz socket 939) and an ASUS motherboard. When I first got my hands on it the machine was loaded with Suse 9.3 for AMD64. I proceeded to load Open Suse 10.1 and then SLED 10.

The SLED 10 installation was very smooth and uneventful. I "enhanced" the installation by following the directions on the Jem Report, "Hacking SUSE Linux Enterprise Desktop 10." I was able to pick up Java 5 as well as add development tools such as gcc that are not included in the base distribution from Novell. It should be noted I downloaded the SLED 10 DVD ISO from Novell, and installed from that. After installing the bits via the new repositories, I downloaded and installed the nVidia graphic driver from .

SLED 10 worked flawlessy until right before I left for Christmas holiday. I installed some new kernel updates that must have wiped out the older kernel it was replacing during the update, and consequently removed the nVidia driver as well. I found this out when I switched on the machine this past Monday, and the X system promptly crashed to a text prompt on start up.

People like to bash Windows, but I've never, and I mean absolutely never, had a problem like this with any version of Windows, and I've used Windows going back to version 1.03. If there was a problem with a graphics driver, Windows simply degraded to a 640 x 480 or 800 x 600 resolution screen with 16 colors, depending on the graphics chip in the system. That degraded mode still gave me control of the Windows system and made it easy to fix the graphics driver problem with the graphics tools (and I eventually always did).

This issue has happened more than once to me with Suse, and it's also happened with other distributions I've run, such as Fedora. This type of problem gives Linux in general a bad name, and makes you think twice about trusting an 'Enterprise' distribution such as SLED in an enterprise situation. I can understand this issue cropping up with a bleeding-edge distro like Open Suse (well, no, not really, after all this time), but it should never, absolutely never, happen to an 'Enterprise' distribution. The X server should be enhanced such that if it can't use the driver specified in the configuration file then it should attempt to run in a degraded mode, instead of just messily dying in front of the user.

Since I've been in this exact situation before, I knew what to do. I found the original nVidia shell file I'd originally used and re-ran it with the '--update' command-line switch. Sure enough, it downloaded and installed the latest nVidia graphic driver, and I was able to restart the X server.

Unfortunately something else got broken. I was able to log into the Gnome desktop, but something else had scuttled the Gnome window manager. I got the graphic desktop and the applications started up, but no window decorations around the applications. With growing anger I spent all of five minutes trying to find out why Gnome was broken. After five fruitless minutes, I logged back out and then changed my desktop to KDE. Then I logged back into a fully working KDE desktop.

I've included a few screenshots of KDE on SLED 10. For the most part it looks almost as good as KDE on Open Suse 10.2, but it's missing a few features I've really come to enjoy on KDE 3.5.5 and Open Suse 10.2. The Gnome window manager behavior has pretty much killed Gnome for me. From now on its nothing but KDE.

The following is a screen shot showing glxgears and the KDE terminal with some transparency.

Below, just your typical web browser shot showing my website of choice :)

And finally, a shot of Konquorer and the icon on the desktop showing the automatic mount of my slightly dated mini cruzer.

I plan on replacing SLED 10 some time next week with Open Suse 10.2 64 bit. And then I'm going to wait on the next version of SLED and see how it behaves.


Popular posts from this blog

cat-in-a-box channels greta garbo

So I'm sitting at my computer, when I start to notice a racket in back. I ignore it for a while until I hear a load "thump!", as if something had been dropped on the floor, followed by a lot of loud rattling. I turn around and see Lucy in the box just having a grand old time, rolling around and rattling that box a good one. I grab the GX1 and snap a few shots before she notices me and the camera, then leaps out and back into her chair (which used to be my chair before she decided it was her chair).

Just like caring for Katie my black Lab taught me about dogs, caring for Lucy is teaching me about cats. She finds me fascinating, as I do her. And she expresses great affection and love toward me without coaxing. I try to return the affection and love, but she is a cat, and she takes a bat at me on occasion, although I think that's just her being playful. She always has her claws in when she does that.

She sits next to me during the evening in her chair while I sit in mi…

vm networking problem fixed

Over the weekend I upgraded to Windows 8.1, then discovered that networking for the virtual machines wouldn't work. Then I tried something incredibly simple and fixed the problem.

Checking the system I noticed that three VMware Windows services weren't running; VMnetDHCP, VMUSBArbService, and VMwareNatService. VMware Player allows you to install, remove, or fix an existing installation. I chose to try fixing the installation, and that fixed the problem. The services were re-installed/restarted, and the virtual machines had networking again.

Once network connectivity was established there was exactly one updated file for Ubuntu 13.10, a data file. This underscores how solid and finished the release was this time. Every other version of every other Linux installation I've ever dealt with has always been succeeded by boatloads of updates after the initial installation. But not this time.

Everything is working properly on my notebook. All's right with the world.

sony's pivotal mirrorless move

I'm a died-in-the-wool technologist, even when it comes to photography. I have always been fascinated with the technology that goes into manufacturing any camera, from the lenses (optics) through the mechanical construction, the electronics involved, and especially the chemistry of the film and the sophistication of the digital sensor. It's amazing that the camera can do all it's asked of it, regardless of manufacturer.

Of all the types of cameras that I've really taken an interest in, contemporary mirrorless (again, regardless of manufacturer) are the most interesting because of the challenging problems the scientists and engineers have had to solve in order to build a compact but highly functional camera. In particular I've followed the sensor advances over the years and watched image quality climb (especially with μ4:3rds) to exceed film and rival one another such that there's very little difference any more as you move from the smaller sensors such as 4:3r…