Getting Started with openSUSE
From openSUSE
| Doc. v1.11 openSUSE 10.3
| This page is a work in progress and is not complete. |
- Maintainer: sgt-d / mailto:sgt-d@sodpit.com?subject=Getting_Started_with_openSUSE
- Status: 20071206 1.11 Rough Draft
Introduction
This page is designed to familiarize you with basic configuration and software management in openSUSE 10.3 and help with many common customizations.
This document attempts to address the most common problems and most frequently asked questions that occur in #suse (on IRC) so that helpers don't have to keep repeating themselves.
This page also includes several CLI applications that will help greatly if you ever have problems with your X server and you still need assistance on IRC in #suse.
Document Conventions
[KEY] - This indicates a key or key combination that you need to press on your keyboard.
Online Resources
Live Support (IRC)
Official Sites
- openSUSE Main Page
- Get openSUSE 10.3
- openSUSE Concepts
- openSUSE HOWTO's
- Frequently Asked Questions (FAQ)
- Restricted Formats (MP3, Encrypted DVD, MPEG-4, etc)
- Package Search (Official)
- Package Search (Webpin)
Video Drivers
Search Sites
More Sites
- sgt-d's openSUSE 10.3 Help Page
- Spin Ink
- Packman
- Guru's RPM Site
- PlanetSUSE
- suse-irc
- IRC Channel Rules
- IRC Channels
- IRC For Newbies
Blogs
Download/Install
Download
| References: |
Installation
|
| References: |
Screenshots
Shameless plugs and screenshots... for anyone that wants to know what openSUSE CAN look like...
System Management
|
| References: |
Here are a few common ways to open YaST to manage your system:
 | If you are using the KDE Desktop Environment:
You will be prompted for the root password to continue. |
 | If you are using the GNOME Desktop Environment:
Now you can directly run the modules presented in the overview.
You will be prompted for the root password and a new Control Center will open. |
Create a Desktop "Link to Application" and set the "command" to this:
kdesu /sbin/yast2
Run Command:
[Alt]+[F2] (Run): kdesu yast2
Teminal:
|
su -c 'yast2' |
|---|
See the YaST Section (below).
Community Repositories
YaST -> Software -> Community Repositories
Adding Community Repositories in openSUSE allows you to install software that was not included with the original media.
Consider adding some (or all) of these repositories:
Main Repository OSS Main Repository Non-OSS Main Update Repository Packman Repository VideoLan Repository openSUSE Build Service - KDE: Backports ATI or NVIDIA Repositories
Software Repositories
YaST -> Software -> Software Repositories
Adding Software Repositories in openSUSE allows you to install software that was not included with the original media.
As you add repositories, they are set to "auto-refresh". This option will increase the load time of YaST Software Management and YaST Online Update. To speed up the start times for these modules, uncheck "auto refresh" for the repositories that aren't used often. If you do this, you will need to manually refresh these repositories occasionally.
Add Software Repositories
|
| References: |
To add Software Repositories in YaST:
Open YaST Software Repositories and click the "Add" button.
Enter the repository.
Click "finish".
Here is a list of some of the more common software repositories:
Main Repositories
Other Repositories
- CyberOrg 10.3 (Stable)
- CyberOrg Factory (Unstable)
- Helions8 (PMount)
- KDE3
- KDE4 10.3 (Stable)
- KDE4 Factory (Unstable)
- NVIDIA
- Packman 10.2 (*)
- Packman 10.3
- Tilda
- VideoLan (VLC)
- Wine
- X11:XGL
(*) Packman 10.2 should not be used with openSUSE 10.3
Software Management
YaST -> Software -> Software Management
You should always attempt to install software first with YaST Software Management.
If that fails, try the openSUSE Software Search.
Finally, if you can't find what you are looking for, consider installing the package with an RPM or DEB file. Try to use a supported version for your architecture, otherwise use a generic RPM.
If all else fails, you may have to build packages from source.
Filters
The "Filter" selector is located near the top left of YaST Software Management.
The "Patterns" filter allows us to look at the available software in the same view that was seen during the installation of openSUSE.
The "Package Groups" filter is a similar, but more detailed view of all of the available software in openSUSE.
The "Languages" filter allows you to install localized versions of software.
The "Repositories" filter allows you to easily see what software each repository contains. Optionally you can use the "Secondary Filter" to narrow down your search.
The "Search" filter is the default filter for YaST Software Management. The default options are "Name" and "Summary". If you are trying to find a specific package that might be included in another package, you might also want to check the "RPM Provides" option. The "Search Mode" selector offers some nice features, including "Use Wild Cards". Wild Cards allows you to search for specific things, example:
Only check "Name" in the "Search In" section Set "Search Mode" to "Use Wild Cards" In the "Search" field type: *kde*4 Click the Search button
As you can see in the results, this brings back almost all of the KDE4 software.
The "Installation Summary" filter can be used to see what is or is not installed on your system. If you check the "Keep" option, the list will refresh to show all of the software that is currently installed on your system (via YaST or RPM). Current packages will be shown with black text, packages that can be updated will be shown in blue, and packages that could be downgraded (not normally recommended) would be shown in red. You can scroll through this list and easily spot software that can be updated (blue).
Package Manager Cleanup
Occasionally and over time the package manager databases become very unoptimized and cause YaST Software Manager to load extremely slow. This becomes more obvious after major system updates, such as a complete update for KDE, for example.
This section will help you optimize your package manager databases.
|
| References: |
Zypper Database Cleanup CLI:
|
|
su -c 'sqlite3 /var/cache/zypp/zypp.db vacuum' |
|---|
Zypper Database Cleanup Script (run as root):
|
|
#!/bin/sh sqlite3 /var/cache/zypp/zypp.db vacuum |
|---|
Zypper Database Reset CLI:
|
|
su -c 'rm /var/cache/zypp/zypp.db ; zypper refresh' |
|---|
Zypper Database Reset Script (run as root):
|
|
#!/bin/sh rm /var/cache/zypp/zypp.db zypper refresh |
|---|
RPM Database Cleanup Script (run as root):
|
|
#!/bin/sh echo Cleaning RPM Database (takes time)... rpm --rebuilddb for fn in /var/cache/zypp/zypp.db \ /var/lib/rpm/Packages \ /var/lib/rpm/Filemd5s \ /var/lib/rpm/Dirnames \ /var/lib/rpm/Basenames do cp $fn $fn.new |
|---|
Online Update
YaST -> Software -> Online Update
Use the Online Update tool to periodically check for critical/important system updates.
VT Switching
VT Switching is a very simple concept that everyone should know when using Linux.
Basically, VT Switching allows you to switch between several different (and already running) terminals on your system.
The common term "VT Switching" refers to both text terminals (TTY / "teletype") and video terminals (VT).
Generically speaking, VT's are all possible types of "virtual terminals".
In a default installation, openSUSE comes with six text terminals (TTY) and six video terminals (VT).
If you boot openSUSE in verbose mode, the text that scrolls by is on TTY1. When graphics mode starts you are automatically switched to VT7.
Write down these key combinations now please:
[Ctrl]+[Alt]+[F1] = TTY1
[Ctrl]+[Alt]+[F7] = VT7
Now try both of the key combinations, one at a time.
What you should have seen: When you switched to TTY1, that was "text mode" and offered a login screen. When you switched to VT7 it put you back on your running X session.
As you saw, TTY1 was allowing you to login. You could login on TTY1 as a normal user, or as root.
Hint: You cannot use "su" as a login name.
Anyway, you could login on TTY1 as root, and TTY2 as a normal user.
 |
Note: VT10 is reserved for kernel logging. |
Video Drivers
One of the first things you will probably want to do in openSUSE is install drivers for your video card. Compiz Fusion will come later :p
NVIDIA Video Drivers
To install NVIDIA drivers manually, please visit the Official NVIDIA Page or http://x.sodpit.com/nvidia.htm.
References
|
| References: |
NVIDIA 1-Click Installers
| Warning ! | Make a backup copy of your xorg.conf before doing anything else. |
Backup your xorg.conf:
|
|
su -c 'cp /etc/X11/xorg.conf /etc/X11/xorg.SAVEME' |
|---|
Current NVIDIA Drivers (supports most new cards):
Legacy NVIDIA Drivers (supports older cards):
NVIDIA Settings/Tweaks
Ok, time for some tweaks...
Enable Compositing, RenderAccel and AddARGBGLXVisuals:
|
|
su -c 'nvidia-xconfig --composite --render-accel --add-argb-glx-visuals' |
|---|
NVIDIA users should disable XGL using this command (even if you are running KDE):
Disable XGL:
|
|
su -c 'gnome-xgl-switch --disable-xgl' |
|---|
Make sure that Display Manager returns "Xorg":
|
|
grep "DISPLAYMANAGER_XSERVER" /etc/sysconfig/displaymanager |
|---|
AIGLX
NVIDIA users can optionally enable AIGLX:
|
|
Note: This example uses "kate", you can use your favorite editor. |
|
|
su -c 'kate /etc/X11/xorg.conf' |
|---|
Search xorg.conf for this section:
Section "ServerLayout"
Inside the ServerLayout section, add one new line:
Option "aiglx" "true"
Example (warning, this is for reference ONLY):
Section "ServerLayout" Identifier "Layout[all]" Screen 0 "Screen0" 1280 0 Screen 1 "Screen1" LeftOf "Screen0" InputDevice "Keyboard[0]" "CoreKeyboard" InputDevice "Mouse[1]" "CorePointer" Option "Clone" "off" Option "Xinerama" "off" Option "aiglx" "true" EndSection
Save and exit kate (or your editor), then restart X.
|
|
Note: You must Restart X for changes to take effect. |
Restarting X can be done by logging out of KDE or Gnome and then logging back in. Optionally you can close all running applications and hit [Left-Ctrl]+[Left-Alt]+[Backspace].
|
| References: |
ATI Video Drivers
For anyone with newer ATI cards... you should try the ATI 8.433/7-11 Drivers first. If you have any problems you can always try the older drivers.
The older ATI 8.40.4 Drivers will work better for older hardware and are also listed on this page in case anyone still needs them.
References
|
| References: |
| Warning ! | Make a backup copy of your xorg.conf before doing anything else. |
Backup your xorg.conf:
|
|
su -c 'cp /etc/X11/xorg.conf /etc/X11/xorg.SAVEME |
|---|
ATI 8.433/7-11 or later Drivers
Some people are now reporting that the new ATI 8.433/7-11 Drivers support AIGLX and work well with openSUSE and compositing.
This section will help you install the ATI 8.433/7-11 Drivers, disable XGL and enable AIGLX, among other things.
If you have problems with this version, if you have older hardware, or if you simply want the older ATI 8.40.0 Drivers that use XGL, please click here.
More Help With This ATI Version
Disable XGL:
|
|
su -c 'gnome-xgl-switch --disable-xgl' |
|---|
Make sure that Display Manager reports "Xorg":
|
|
grep "DISPLAYMANAGER_XSERVER" /etc/sysconfig/displaymanager |
|---|
Run ATI Config:
|
|
su -c 'aticonfig --initial --input=/etc/X11/xorg.conf --force' |
|---|
Verify xorg.conf
Now we need to verify some things in xorg.conf.
Edit your xorg.conf (as root):
|
|
su -c 'kate /etc/X11/xorg.conf' |
|---|
Make sure that all of the bold lines below are in your xorg.conf:
This xorg.conf example was taken directly from CyberOrg's Blog:
Section "Module" Load "dbe" Load "type1" Load "freetype" Load "extmod" Load "glx" Load "dri" EndSection
Section "ServerFlags" Option "AllowMouseOpenFail" "on" Option "IgnoreABI" "on" Option "AIGLX" "true" EndSection
Section "Device" Identifier "aticonfig-Device[0]" Driver "fglrx" Option "FSAAEnable" "off" Option "Capabilities" "0×00000000" Option "VideoOverlay" "on" Option "OpenGLOverlay" "off" Option "FSAAScale" "0" Option "XAANoOffscreenPixmaps" "true" EndSection
Section "Extensions" Option "DAMAGE" "true" Option "Composite" "true" EndSection
|
|
Note: You must Restart X for changes to take effect. |
ATI 8.40.4 Drivers
These are the older ATI 8.40.4 drivers, and older installation methods for anyone that still needs them.
For these drivers you should use XGL and FRGLX as shown below.
Enable XGL using this command (even if you are running KDE):
|
|
su -c 'gnome-xgl-switch --enable-xgl' |
|---|
Make sure that Display Manager reports "XGL":
|
|
grep "DISPLAYMANAGER_XSERVER" /etc/sysconfig/displaymanager |
|---|
Switch to FGLRX:
|
|
su -c 'SaX2 -r -m 0=fglrx' |
|---|
|
|
Note: You must Restart X for changes to take effect. |
Desktop Effects
Ok, time for some eye candy!
If you are using NVIDIA 169 drivers, Compiz Fusion may not work initially.
If you have problems, try this command:
|
|
LIBGL_ALWAYS_INDIRECT=1 compiz --no-libgl-fallback --replace ccp& emerald --replace& |
|---|
If that works for you, also do this:
|
|
cat ~/.config/compiz/compiz-manager LIBGL_ALWAYS_INDIRECT=1 COMPIZ_OPTIONS="--no-libgl-fallback --only-current-screen --ignore-desktop-hints --replace" |
|---|
Hit [Ctrl] + [D] when done, then restart your window manager.
References
|
| References:
Chronological order, newest to oldest... |
Compiz Fusion (Official)
|
| References: |
Notice: If you followed ALL of the instructions (above) for NVIDIA -OR- ATI cards, your system *should* be ready for Compiz Fusion.
Select the version of Compiz Fusion that you want to install, KDE or Gnome:
| | If you are using the KDE Desktop Environment: 
|
| | If you are using the GNOME Desktop Environment: 
|
If you want Compiz Fusion to automatically load with KDE/Gnome, click here to install the compiz-manager package.
Compiz Fusion Git (Development)
|
| References: |
Notice: If you followed ALL of the instructions (above) for NVIDIA -OR- ATI cards, your system *should* be ready for Compiz Fusion.
If this is the first time you are installing Compiz Fusion, you are in the wrong place.
This package is UNSTABLE. Do NOT use it unless you know what you are doing.
Notice: This next step may not be required for Compiz Fusion Git...
If you want Compiz Fusion to automatically load with KDE/Gnome, click here to install the compiz-manager package.
Screenlets
Notice: For Screenlets to look correct, you must be using "Compositing" with your video driver, but you do not have to use a Compositing Manager (such as Compiz Fusion).
If you followed ALL of the instructions (above) for NVIDIA and ATI cards, Compositing *should* already be working correctly.
|
| References: |
Installation
Install Screenlets via YaST Software Management after adding the the Packman 10.3 Repository.
Or, from the command line:
|
|
su -c 'zypper ar http://ftp.skynet.be/pub/packman/suse/10.3/ "Packman 10.3"' su -c 'zypper in screenlets' |
|---|
Optionally, install my Screenlets Starter Package.
Usage
Screenlets Manager:
screenlets-manager
Launch Screenlets Manually:
~/.screenlets/CPU_Meter/CPU_MeterScreenlet.py
~/.screenlets/Orloj/OrlojScreenlet.py
To automatically start Screenlets when KDE starts, add links like the two shown directly above to this folder:
~/.kde/Autostart
Problems
If you are not using the compositing extension for your video drivers you will see black backgrounds and/or borders when using Screenlets.
SuperKaramba
SuperKaramba is a tool that allows you to easily create interactive eye-candy on your KDE desktop.
|
| References: |
Installation
SuperKaramba is available in YaST Software Management inside the "kdeutils3-extra" package.
| Warning ! | Do NOT use the "kde4-superkaramba" package as it does not support transparency under KDE3. |
Or, from the command line:
|
|
su -c 'zypper in kdeutils3-extra' |
|---|
Optionally, install my SuperKaramba Themes (includes Microchip Theme).
Usage
Example:
superkaramba ~/Documents/skthemes/microchip/Super_Cybertron_Light.theme
To automatically start SuperKaramba when KDE starts, add a link like the one shown directly above to this folder:
~/.kde/Autostart
Problems
If you do not have transparency when using SuperKaramba themes... you probably ignored the warning (above) and installed the "kde4-superkaramba" package instead of the correct package for KDE3, "kdeutils3-extra". Try again.
GKrellM
GKrellM is a single process stack of system monitors which supports applying themes to match its appearance to your window manager, Gtk, or any other theme.
|
| References: |
Installation
Install GKrellM via YaST Software Management.
Or, from the command line:
|
|
su -c 'zypper in gkrellm' |
|---|
KSensors
|
| References: |
KSensors is a nice lm-sensors frontend for the K Desktop Environment.
lm-sensors provides tools for monitoring the hardware health of Linux systems containing hardware health monitoring hardware such as the LM78 and LM75.
Installation
Install KSensors via YaST Software Management.
Or, from the command line:
|
|
su -c 'zypper in ksensors' |
|---|
To detect additional hardware monitors:
|
|
su -c 'sensors-detect' |
|---|
Customizations
Grub Wallpaper
If you don't care for the default Grub wallpaper in openSUSE, this section will help you change it!
The WakeUp.jpg image that I mention in my instructions below was 800x600 but it didn't display properly at bootup. Originally it had too high of a color depth, or maybe the file size was just too large (I don't know because it's almost impossible to find details or specifications for Grub for openSUSE, and every site says something different) so I opened it in Gimp and saved it as a new file, but then moved the detail slider down to 50%. This made the image a little less detailed and it also reduced the size from 600kb to maybe 75kb. After I did this, Grub displayed the image perfectly.
Mileage may vary.
Here are the steps I used to update the /boot/message file (type: cpio) with my new wallpaper:
mkdir ~/bin/cpio mkdir ~/bin/cpio/work cd ~/bin/cpio/work cp /boot/message . cpio -idv < message mv message ../message-old cp ~/Documents/wallpaper/WakeUp.jpg back.jpg ls | cpio -ov > ../message cd.. su cp message /boot/message exit
Reboot the computer to test your new Grub Wallpaper!
KDE/Gnome Login Screen
|
| References: |
Tilda
Tilda is a customizable (including transparency) terminal that can be bound to a hotkey that opens similar to game consoles such as Quake.
|
| References: |
Add the Tilda Repository, then install Tilda:
|
|
su -c 'zypper ar http://download.opensuse.org/repositories/home:/lowks/openSUSE_10.3/ "tilda"' su -c 'zypper in tilda' |
|---|
Yakuake
Yakuake is another customizable (including transparency) terminal that can be bound to a hotkey that opens similar to game consoles such as Quake.
|
| References: |
The newest version is in the KDE Backports repository.
Add the KDE Backports repo, then install Yakuaka:
|
|
su -c 'zypper ar http://download.opensuse.org/repositories/KDE:/Backports/openSUSE_10.3/ "KDE Backports"' su -c 'zypper in yakuake' |
|---|
Graphical User Interface (GUI)
Konqueror File Browser
Tip: Konqueror's left bar has options, switching different views.
kfmclient openProfile filemanagement
YaST
You can start the YaST GUI with this command:
/sbin/yast2
YaST Problems
If you have major problems using YaST in Gnome, switch from the Gtk interface to the Qt interface.
To switch YaST from Gtk to Qt Open the /etc/sysconfig/yast2 file as root:
|
|
su -c 'kate /etc/sysconfig/yast2' |
|---|
Change WANTED_GUI="auto" to WANTED_GUI="qt", save the file and exit.
Then restart YaST.
Command Line Interface (CLI)
CLI Commands
To get to a command line, open a terminal such as konsole or xterm, or switch to TTY1.
All of the CLI examples shown here assume that you are already in a terminal window or logged in on a TTY.
Start/Stop/Restart X
Init (Traditional Method)
Stop X server:
|
|
su -c 'init 3' |
|---|
Start X server:
|
|
su -c 'init 5' |
|---|
RCXDM (New Method)
Stop X server:
|
|
su -c 'rcxdm stop' |
|---|
Start X server:
|
|
su -c 'rcxdm start' |
|---|
Restart X server:
|
|
su -c 'rcxdm restart' |
|---|
Zypper
Zypper is the command line interface for "YaST Software Management" (YSM) and "YaST Software Repositories" (YSR). Similar to YSM and YSR, Zypper must be run as root:
Examples
Get help:
|
|
su -c 'zypper -h' |
|---|
To add a repository:
|
|
su -c 'zypper ar http://repository_address_here "name / alias for this repo"' |
|---|
To install a package:
|
|
su -c 'zypper in irssi' |
|---|
RPM
The "rpm" command allows you to install, upgrade or remove RPM's from the system.
Examples
Get help:
|
|
rpm --help |
|---|
Install an RPM:
|
|
su -c 'rpm -ivh filename.rpm' |
|---|
Upgrade an RPM:
|
|
su -c 'rpm -Uvh filename.rpm' |
|---|
Uninstall an RPM:
|
|
su -c 'rpm -e PackageName.rpm' |
|---|
|
|
Note: the name of the package is case sensitive. |
How to query the RPM Database:
|
|
rpm -qa |
|---|
To check the author of an RPM:
|
|
rpm -q --qf '%{PACKAGER}\n' package_name_here
|
|---|
CLI Applications
Command Line Interface (CLI) applications are extremely helpful, especially if you are having problems with graphics mode (X server). Some CLI applications allow you to use ICQ
System
YaST
You can use YaST in CLI:
|
|
yast |
|---|
Editors
vi
pisses me off
To save and exit: +qw [Enter]
To quit without saving: :q [Enter]
joe
is ok
nano
old school
pico
ancient
IRC/Communications
| Warning ! | Only run these programs as a normal user... NOT as root. |
licq, irssi, bitchx
Licq
You should run Licq one time in GUI mode to set everything up. For some reason, the initial setup doesn't save in CLI mode.
Only proceed after you have setup your account in GUI mode.
To start Licq in CLI mode type:
|
|
licq -p console |
|---|
To get online:
/status online
For help:
/help
To get back to GUI mode:
|
|
licq -p kde-gui |
|---|
Website:
http://licq.org/
Irssi
Start Irssi:
|
|
irssi -n sgt-d -c irc.opensuse.org |
|---|
Get going...
/msg nickserv identify goodtry /join #suse
Website:
http://irssi.org/
BitchX
Start BitchX:
|
|
bitchx sgt-d irc.opensuse.org |
|---|
Get going...
/msg nickserv identify goodtry /join #suse
Website:
http://bitchx.com/
Web Browsers
Here are some CLI web browsers... very handy if you ever have problems with X.
Links
Links works with both the mouse and keyboard.
Command:
|
|
|---|