Language Selection

English French German Italian Portuguese Spanish

Installing openSUSE 10.2 on a Compaq laptop (Part 2)

Filed under
Reviews

In part 1, openSUSE got installed and configured on a Compaq Presario V2000 with an ATI Radeon Xpress 200M PCIE graphics chipset and a 32-bit CPU. Now it's time to go for the bling.

How easy is it to get the graphic goodness of Beryl going? Pretty dang easy.

Installing the ATI driver

The first step is getting ATI's proprietary "fglrx" driver installed. (Why do they call it "fglrx"? Maybe it's an acronym for "Free/GPL/Libre Releases X-rays." Who knows?) The openSUSE wiki has a how-to for that, too. The basic steps are as follows:

  • As a prerequisite, install the "gcc" and "kernel-source" packages.
  • Download the latest ATI Radeon driver from their web site (the filename's currently "ati-driver-installer-8.32.5-x86.x86_64.run").
  • As root, make it executable (with "chmod +x") and run it. Installation instructions are here; you may want to print them out. You're looking to make an rpm, or, as ATI calls it, "Generate A Distribution Specific Driver Package."

    The installer can run in GUI mode under KDE, or run in text mode from a console. I'd recommend running it outside of X Windows, in a console, for only one reason: its dialog box was too tall to fit on my screen. Besides, you need to be in a console at runlevel 3 in order to enable it using Sax2, anyway.

    After accepting the license agreement, choose the "Generate Distribution Specific Driver Package" option, and the installer will create an rpm for you (named something like "fglrx_7_1_0_SUSE102-8.32.5-1.i386.rpm"). Install the rpm (with "rpm -ivh").

  • The last step: if you're not already in a console without X Windows running, log out of X, choose "Console login" from the kdm login screen, and log in as root. Switch to runlevel 3 with "init 3". Then type

    sax2 -r -m 0=fglrx

    and Suse will configure xorg.conf to use the driver. Type "init 5" to get back into KDE, and it should now be using ATI's driver. You can verify that you are by running the command "fglrxinfo" at a bash prompt. (Accelleration should be enabled by default.)

(Whew. That was harder to write than it was to do!)

Installing Xgl and Beryl

Unless you specifically deselected them during installation, you probably already have Xgl and Compiz installed. Check with "rpm -q xgl" and "rpm -q compiz" at a bash prompt. If they're not installed, simply install them using your favorite package manager.

There's one change to make to /etc/X11/xorg.conf in order to use Xgl. You'll have to add a section that looks like this to the end. (Please ignore those < br / > tags; they're just a figment of your imagination.)

Section "Extensions"
    Option "Composite" "0"
EndSection

You enable Xgl by going to a bash prompt as root and running the command "gnome-xgl-switch --enable-xgl" and then restarting KDE.

Finally, there's one more configuration change to make. There's a "Translucency" option in KDE that's set by default to "on," which has to be turned off in order for compiz (and Beryl) to run correctly. It's in the KDE Control Center under Desktop > Window Behavior > Translucency. Uncheck the "Use translucency/shadows" box and restart KDE again. You should finally see compiz going, and have a desktop cube, which you can roll around by holding down Ctrl+Alt with one hand, and clicking on the desktop and moving the mouse, with the other.

Installing Beryl

Why not just stick with compiz? You can, of course, but beryl offers a whole lot more options.

By now you know the drill: the openSUSE wiki has a how-to for Beryl. If you're still using YaST to configure repos and install packages, the steps are as follows:

  • Add the following repo: http://software.opensuse.org/download/X11:/XGL/openSUSE_10.2/
  • Install these packages: beryl-core
    beryl-plugins
    emerald : window decorator
    emerald-themes
    aquamarine
    beryl-settings
    beryl-manager
    (You'll probably get updated Xgl and compiz packages along the way, through the Zen updater.)
  • Once again, restart KDE. Then pull up a console window, and, as your normal user, type

    > beryl-manager &

    You should at least see a red gemstone icon show up in your system tray -- that's Beryl-Manager. You may need to click on it, then click "Select Window Manager," and choose "Beryl." After that, you may need to click on "Reload Window Manager." If all goes well, you should see the screen flicker, the Beryl splash screen come up, and you're finally done.

    Well, almost. There's a ton of configuration options available in the "Beryl Settings Manager," and a bunch of window decorations/themes to choose from in the "Emerald Theme Manager." After all that work, you get to play around with it.

    Finally, putting symlinks to /usr/bin/beryl-manager and /usr/bin/beryl-xgl in ~/.kde/Autostart will make beryl start automagically every time you start KDE.

Conclusion

openSUSE is laptop-friendly, has an eye-pleasing KDE configuration, is well-documented and easy to install, and has most of the packages you'd expect from a modern Linux distro. Not everything is perfect, though.

The bad:

  • YaST's software management tools are both slow and clunky. No wonder a lot of people use the SMART package manager. (openSUSE also has hooks for YUM, and you can install APT.) It'd be nice for SMART to become the default package manager at some point in the future. (The Zen software updater works well, though.)
  • Speaking of software updates, it'd also be nice if openSUSE did what Fedora does, namely, move updated packages into their main repos as soon as they're stable. Six months is not a long time to wait, of course, but Fedora seems to be issuing updated packages almost daily.
  • That "kerry beagle" indexer sure seems to slow things down, especially right after you log into KDE. Fortunately, it can be permanently disabled.
  • So can the so-called "SUSE menu style" (aka "Kickoff") -- just right-click on the button and choose "Switch to KDE Menu Style". (OK, it's really not that bad, but simpler is better, IMO.)

The ugly:

  • The Novell/Microsoft patent agreement follows openSUSE around like the cloud of dirt and dust that follows the Peanuts character, Pig-Pen. What a horrendous lapse in judgment on Novell's part. There's really nothing else to say.

How-To's/FAQs:

The end!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

pigpen

"The Novell/Microsoft patent agreement follows openSUSE around like the cloud of dirt and dust that follows the Peanuts character, Pig-Pen."

lol I love that analogy. Big Grin

----
You talk the talk, but do you waddle the waddle?

just went thru a similar install...

A few weeks prior (right after openSuse 10.2 release) to a new little Compaq v6110us... Though my install was i386, not x86_64. Worked like a champ for me, other than I'm kind of a laptop rookie, and let ndiswrapper take a timely tool on myself.

Other than that, install was awesome!

Lots of this laptop Nvidia with related drivers.

-Pat

More in Tux Machines

Linux Devices, Tizen, and Android

Leftovers: OSS

  • SAP buys into blockchain, joins Hyperledger Project
  • foss-north speaker line-up
    I am extremely pleased to have confirmed the entire speaker line-up for foss north 2017. This will be a really good year!
  • Chromium/Chrome Browser Adds A glTF Parser
    Google's Chrome / Chromium web-browser has added a native glTF 1.0 parser. The GL Transmission Format, of course, being Khronos' "3D asset delivery format" for dealing with compressed scenes and assets by WebGL, OpenGL ES, and other APIs. There are glTF utility libraries in JavaScript and other web-focused languages, but Google adding a native glTF 1.0 parser appears to be related to their VR push with supporting VR content on the web. Their glTF parser was added to Chromium Git on Friday.
  • Sex and Gor and open source
    A few weeks ago, Dries Buytaert, founder of the popular open-source CMS Drupal, asked Larry Garfield, a prominent Drupal contributor and long-time member of the Drupal community, “to leave the Drupal project.” Why did he do this? He refuses to say. A huge furor has erupted in response — not least because the reason clearly has much to do with Garfield’s unconventional sex life. [...] I’ll unpack the first: open-source communities/projects are crucially important to many people’s careers and professional lives — cf “the cornerstone of my career” — so who they allow and deny membership to, and how their codes of conduct are constructed and followed, is highly consequential.
  • Hazelcast Releases 3.8 – The Fastest Open Source In-Memory Data Grid
  • SecureDrop and Alexandre Oliva are 2016 Free Software Awards winners
  • MRRF 17: Lulzbot and IC3D Release Line Of Open Source Filament
    Today at the Midwest RepRap Festival, Lulzbot and IC3D announced the creation of an Open Source filament. While the RepRap project is the best example we have for what can be done with Open Source hardware, the stuff that makes 3D printers work – filament, motors, and to some extent the electronics – are tied up in trade secrets and proprietary processes. As you would expect from most industrial processes, there is an art and a science to making filament and now these secrets will be revealed.
  • RApiDatetime 0.0.2

Security Leftovers

  • NSA: We Disclose 90% of the Flaws We Find
    In the wake of the release of thousands of documents describing CIA hacking tools and techniques earlier this month, there has been a renewed discussion in the security and government communities about whether government agencies should disclose any vulnerabilities they discover. While raw numbers on vulnerability discovery are hard to come by, the NSA, which does much of the country’s offensive security operations, discloses more than nine of every 10 flaws it finds, the agency’s deputy director said.
  • EFF Launches Community Security Training Series
    EFF is pleased to announce a series of community security trainings in partnership with the San Francisco Public Library. High-profile data breaches and hard-fought battles against unlawful mass surveillance programs underscore that the public needs practical information about online security. We know more about potential threats each day, but we also know that encryption works and can help thwart digital spying. Lack of knowledge about best practices puts individuals at risk, so EFF will bring lessons from its comprehensive Surveillance Self-Defense guide to the SFPL. [...] With the Surveillance Self-Defense project and these local events, EFF strives to help make information about online security accessible to beginners as well as seasoned techno-activists and journalists. We hope you will consider our tips on how to protect your digital privacy, but we also hope you will encourage those around you to learn more and make better choices with technology. After all, privacy is a team sport and everyone wins.
  • NextCloud, a security analysis
    First, I would like to scare everyone a little bit in order to have people appreciate the extent of this statement. As the figure that opens the post indicates, there are thousands of vulnerable Owncloud/NextCloud instances out there. It will surprise many just how easy is to detect those by trying out common URL paths during an IP sweep.
  • FedEx will deliver you $5.00 just to install Flash
    Bribes on offer as courier's custom printing service needs Adobe's security sinkhole

GNOME Extensions Website Has A New Look

Every GNOME Shell user will visit the official GNOME Shell Extensions website at least once. And if those users do so this weekend they’ll notice a small difference as the GNOME Shell Extensions website is sporting a minor redesign. This online repo plays host to a stack of terrific add-ons that add additional features and tweak existing ones. Read more