<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Christian Krog Madsen &#187; Installation</title>
	<atom:link href="http://christian.krog-madsen.dk/category/installation/feed/" rel="self" type="application/rss+xml" />
	<link>http://christian.krog-madsen.dk</link>
	<description>Opinions, thoughts and tips</description>
	<lastBuildDate>Sat, 17 Jul 2010 11:34:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Recovering from a bad initrd image</title>
		<link>http://christian.krog-madsen.dk/2009/05/11/recovering-from-a-bad-initrd-image/</link>
		<comments>http://christian.krog-madsen.dk/2009/05/11/recovering-from-a-bad-initrd-image/#comments</comments>
		<pubDate>Mon, 11 May 2009 21:16:55 +0000</pubDate>
		<dc:creator>Christian Krog Madsen</dc:creator>
				<category><![CDATA[Installation]]></category>
		<category><![CDATA[OpenSUSE 11.1]]></category>

		<guid isPermaLink="false">http://www.krog-madsen.dk/wp/2009/05/11/recovering-from-a-bad-initrd-image/</guid>
		<description><![CDATA[When Linux is booted by the boot loader, it will first load the kernel image (usually /boot/vmlinuz) into memory, followed by the initial boot ramdisk (usually /boot/initrd). If for some reason the initrd image has been corrupted, booting may fail. &#8230; <a href="http://christian.krog-madsen.dk/2009/05/11/recovering-from-a-bad-initrd-image/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>When Linux is booted by the boot loader, it will first load the kernel image (usually /boot/vmlinuz) into memory, followed by the initial boot ramdisk (usually /boot/initrd). If for some reason the initrd image has been corrupted, booting may fail. The following procedure can be used to re-generate the initrd image.</p>
<ol>
<li>Make sure the BIOS is set to boot from the optical drive</li>
<li>Insert the OpenSUSE install DVD into the optical drive.</li>
<li>Boot the machine</li>
<li>Select the menu option &#8220;Rescue System&#8221;</li>
<li>When prompted to login, type &#8220;root&#8221;</li>
<li>Mount the Linux root partition, typically something like &#8220;mount -t ext3 /dev/sda1 /mnt&#8221;</li>
<li>If the Linux /boot area is on a separate partition, also mount that into the root partition, f.ex. &#8220;mount -t ext3 /dev/sda2 /mnt/boot&#8221;</li>
<li>Bind the rescue system&#8217;s /dev to the mounted root filesystem with &#8220;mount &#8211;bind /dev /mnt/dev&#8221; &#8211; this will make sure all your device nodes are correct</li>
<li>Chroot to the mounted root filesystem with &#8220;chroot /mnt&#8221;</li>
<li>Mount proc and sys: &#8220;mount /proc&#8221; and &#8220;mount /sys&#8221;</li>
<li>Re-generate initrd image with &#8220;mkinitrd&#8221;</li>
<li>Remove DVD and reboot</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://christian.krog-madsen.dk/2009/05/11/recovering-from-a-bad-initrd-image/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installing ATI graphics drivers on OpenSUSE 10.2</title>
		<link>http://christian.krog-madsen.dk/2007/04/06/installing-ati-graphics-drivers-on-opensuse-102/</link>
		<comments>http://christian.krog-madsen.dk/2007/04/06/installing-ati-graphics-drivers-on-opensuse-102/#comments</comments>
		<pubDate>Fri, 06 Apr 2007 10:12:12 +0000</pubDate>
		<dc:creator>Christian Krog Madsen</dc:creator>
				<category><![CDATA[Hardware Devices]]></category>
		<category><![CDATA[Installation]]></category>

		<guid isPermaLink="false">http://www.krog-madsen.dk/wp/2007/04/06/installing-ati-graphics-drivers-on-opensuse-102/</guid>
		<description><![CDATA[To get 3D graphics acceleration on ATI Radeon X1xxx series graphics cards, ATI&#8217;s proprietary driver must be installed. Ideally, it should be a simple exercise: download the driver from ATI and follow their installation instructions. However, using the automated installer, &#8230; <a href="http://christian.krog-madsen.dk/2007/04/06/installing-ati-graphics-drivers-on-opensuse-102/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>To get 3D graphics acceleration on ATI Radeon X1xxx series graphics cards, ATI&#8217;s proprietary driver must be installed. Ideally, it should be a simple exercise: download the <a href="http://ati.amd.com/support/drivers/linux/linux-radeon.html">driver</a> from ATI and follow their <a href="https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_8.35.5-inst.html">installation instructions</a>.  However, using the automated installer, I got error messages saying file atiogl_a_dri.so could not be found. Installation reported successful completion, but although the fglrx driver was installed and everything was OK in 2D, there was no 3D acceleration.</p>
<p>The correct way to install the ATI driver is documented in the <a href="http://en.opensuse.org/Howto/ATI_Driver">ATI HOWTO</a>. Basically, you have to build a distribution-specific package and then install that using rpm. At the end you should have full 3D acceleration as witnessed by running fglrxinfo:<br />
<code><br />
ckm@zeus:~&gt; fglrxinfo<br />
display: :0.0  screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Mobility Radeon X1400<br />
OpenGL version string: 2.0.6400 (8.35.5)<br />
</code><br />
Check that you get the same result both as root and a normal user. If you get permission problems with a normal user, edit /etc/X11/xorg.conf, find the section labelled &#8220;DRI&#8221; and change the Mode line to:<br />
<code><br />
Mode 0666<br />
</code><br />
Save the file and restart X.</p>
]]></content:encoded>
			<wfw:commentRss>http://christian.krog-madsen.dk/2007/04/06/installing-ati-graphics-drivers-on-opensuse-102/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Installing OpenSUSE 10.2 on a T60 Thinkpad</title>
		<link>http://christian.krog-madsen.dk/2007/04/06/installing-opensuse-102-on-a-t60-thinkpad/</link>
		<comments>http://christian.krog-madsen.dk/2007/04/06/installing-opensuse-102-on-a-t60-thinkpad/#comments</comments>
		<pubDate>Fri, 06 Apr 2007 08:53:58 +0000</pubDate>
		<dc:creator>Christian Krog Madsen</dc:creator>
				<category><![CDATA[Installation]]></category>
		<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://www.krog-madsen.dk/wp/2007/04/06/installing-opensuse-102-on-a-t60-thinkpad/</guid>
		<description><![CDATA[A while back I got a new Lenovo T60 Thinkpad. Of course it can pre-installed with WinXP taking up all of the harddrive except for the 4gb hidden recovery partition. Installation The setup I wanted was a dual-boot with OpenSUSE &#8230; <a href="http://christian.krog-madsen.dk/2007/04/06/installing-opensuse-102-on-a-t60-thinkpad/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>A while back I got a new Lenovo T60 Thinkpad. Of course it can pre-installed with WinXP taking up all of the harddrive except for the 4gb hidden recovery partition.</p>
<p><strong>Installation</strong></p>
<p>The setup I wanted was a dual-boot with OpenSUSE as the default OS and WinXP as an option. I decided to keep the recovery partition, create a small FAT32 partition for easy sharing of files between the OS&#8217;es and split the remaining disk into two equally sized partitions for Linux and Windows.</p>
<p>At the time, OpenSUSE 10.2 had just been released, so I figured this would be a good chance to try it out (I am still using 10.1 on my stationary PC). When I started installation for the first time, the installer reported that the filesystem in the Windows partition had been uncleanly unmounted and therefore it could not safely resize the partition. This happened because the WinXP installation was somehow broken so all attempts to install updates would hang the machine. Well, this was easy to fix, so I booted WinXP and shut down without allowing it to install updates. Points to SUSE for detecting the filesystem inconsistency!</p>
<p>On the next attempt the Windows filesystem was successfully resized and the remaining partitions were created. However, after completing the partitioning, the installer reported errors reading from the drive&#8230; The error message mentioned something about SATA. Not quite sure what to do about this, I tried rebooting and repeating the installation steps. Same result.</p>
<p>Realizing that the SATA controller was probably causing the problem, I rebooted and went looking for settings in the BIOS. Under SATA I found a setting for SATA mode set to AHCI. I changed this to Compatibility and restarted the installation.</p>
<p>This time, the installation worked like a charm. All of my hardware was detected automatically.</p>
<p><strong>First impressions</strong></p>
<p>One of the first things you notice coming from 10.1 is that the Gnome/KDE menu has been changed from the traditional program groups into a Windows-ish menu with your favourite applications, a Beagle-driven search field and some system-related icons. I have rather mixed feelings about this new style of menu.</p>
<p><img src="http://localhost/km/wp-content/uploads/2007/04/startmenu.png" alt="New start menu in Gnome" /></p>
<p>The search facility is useful in that it finds applications, documents, recently visited web pages, etc. Generally it is quick and the presentation is clean. However, once you launch an application, the search window remains. Soon, you will have a whole bunch of Beagle windows open on your desktop. To me, it would make more sense to close the window once an icon is activated.</p>
<p>When you want to browse to an application rather than search, you have to click the More applications button. First problem here is if you do not want to use the mouse, you have to hit Tab eight times to get to the button! Once you have the application browser window open, you will find a huge number of icons (ok &#8211; depending on how many applications you installed) sorted into nine groups. Rather confusingly, the individual elements of the Gnome Control Center have been included as individual applications. Maybe I am just stuck in the old way of doing things, but I find it to be illogical.</p>
<p>On the positive side, I really like the NetworkManager applet, which makes it a breeze to switch between wired and wireless networks. I am not sure if it was included in 10.1, but I have not used it before. It automatically lists available wireless networks with their signal strength and security setting. It also manages VPN connections, though apparently only <a href="http://openvpn.net/">OpenVPN</a> and Cisco type VPNs &#8211; not PPTP, L2TP or IPSec.</p>
<p>As with most Linux distributions, OpenSUSE comes somewhat crippled in terms of media capabilities. No DVD or MP3 playback and no or limited 3D graphics acceleration. Fortunately, the fabulous <a href="http://www.softwareinreview.com/cms/content/view/60/">Jem Report</a> will have you playing all your favourite DVDs, MP3s and WMA files in no time and have 3D acceleration for your games or perhaps 3D desktop effects with <a href="http://www.go-compiz.org/index.php?title=Main_Page">Compiz</a>.</p>
<p>Compared with 10.1, the package management applications work much better. YaST is still takes a long time loading the package database, but it has been markedly improved. The Zen updater also seems to be more robust in this release.</p>
<p>All in all, OpenSUSE 10.2 has been a pleasant experience so far.</p>
]]></content:encoded>
			<wfw:commentRss>http://christian.krog-madsen.dk/2007/04/06/installing-opensuse-102-on-a-t60-thinkpad/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Updated OpenSUSE 10.1 images available</title>
		<link>http://christian.krog-madsen.dk/2006/10/13/updated-opensuse-101-images-available/</link>
		<comments>http://christian.krog-madsen.dk/2006/10/13/updated-opensuse-101-images-available/#comments</comments>
		<pubDate>Fri, 13 Oct 2006 18:54:56 +0000</pubDate>
		<dc:creator>Christian Krog Madsen</dc:creator>
				<category><![CDATA[Installation]]></category>

		<guid isPermaLink="false">http://www.krog-madsen.dk/wp/2006/10/13/updated-opensuse-101-images-available/</guid>
		<description><![CDATA[Update: The remastered CD/DVD images are now definitely on the OpenSUSE download page. Today it was announced that a &#8220;remastered&#8221; version of the OpenSUSE 10.1 CD images is available for download. This new set of CD&#8217;s includes all security patches &#8230; <a href="http://christian.krog-madsen.dk/2006/10/13/updated-opensuse-101-images-available/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><em><strong>Update</strong></em>:  <em>The remastered CD/DVD images are now definitely on the OpenSUSE <a title="OpenSUSE download" href="http://en.opensuse.org/Released_Version">download page</a>.</em><br />
Today it was <a target="_blank" title="Announcement in the OpenSUSE mailing list" href="http://lists.opensuse.org/opensuse-announce/2006-10/msg00001.html">announced </a>that a &#8220;remastered&#8221; version of the OpenSUSE 10.1 CD images is available for download. This new set of CD&#8217;s includes all security patches that have been released since the original images were made available. The similarly updated non-OSS DVD version will be available sometime next week.</p>
<p>Users who have already installed OpenSUSE do not need the new version, as all the patches should already have been installed through online update. Users doing a fresh install of OpenSUSE, however, should definitely get the new images to avoid the <a title="Problem with online update" href="http://www.krog-madsen.dk/wp/2006/07/15/when-updating-the-updater-fails/">problems with libzypp</a> (online update) that were present in the original images.<br />
The OpenSUSE <a title="OpenSUSE download" href="http://en.opensuse.org/Released_Version">download page</a> does not yet mention the update, nor does the news on opensuse.org. Perhaps they are waiting for the DVD image. Unless you are in a rush, you might want to postpone the download until next week.</p>
]]></content:encoded>
			<wfw:commentRss>http://christian.krog-madsen.dk/2006/10/13/updated-opensuse-101-images-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trouble with 1920&#215;1200 resolution</title>
		<link>http://christian.krog-madsen.dk/2006/09/10/trouble-with-1920x1200-resolution/</link>
		<comments>http://christian.krog-madsen.dk/2006/09/10/trouble-with-1920x1200-resolution/#comments</comments>
		<pubDate>Sat, 09 Sep 2006 22:07:15 +0000</pubDate>
		<dc:creator>Christian Krog Madsen</dc:creator>
				<category><![CDATA[Hardware Devices]]></category>
		<category><![CDATA[Installation]]></category>

		<guid isPermaLink="false">http://www.krog-madsen.dk/wp/2006/09/10/trouble-with-1920x1200-resolution/</guid>
		<description><![CDATA[Today, I replaced my Lacie 19&#8243; CRT with an awesome Dell 2407 WFP LCD widescreen connected via DVI to a GeForce4 MX graphics card. After booting, everything was fine until I reached the xdm login screen. Somehow the display was &#8230; <a href="http://christian.krog-madsen.dk/2006/09/10/trouble-with-1920x1200-resolution/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Today, I replaced my Lacie 19&#8243; CRT with an awesome <a title="Dell 2407 WFP at dell.com" href="http://accessories.us.dell.com/sna/productdetail.aspx?c=us&#038;l=en&#038;s=dhs&#038;cs=19&#038;sku=320-4335">Dell 2407 WFP</a> LCD widescreen connected via DVI to a GeForce4 MX graphics card. After booting, everything was fine until I reached the xdm login screen. Somehow the display was garbled, so the text was barely readable. It seemed like the rows of pixels were offset seemingly randomly to the left or right by up to about 0.4cm.</p>
<p>At first, I thought it was just because X remembered the setup from the CRT screen, which supports a much higher refresh rate (85Hz compared to 60Hz on the flatpanel). Setting the monitor type and resolution in SaX did not help, though.</p>
<p>The solution was to install the Nvidia binary only drivers, combined with a custom modeline (though I am not sure this is strictly necessary). There is a special <a title=" Nvidia Installer HOWTO for SUSE LINUX users" href="http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html">Howto for installing on SUSE</a>. Alternatively, just FTP to download.nvidia.com and grab the files in /novell/sle10/i586 (or x86_64 if you are on a 64bit CPU). There are three versions of the nvidia kernel module, so be sure to get the one matching your kernel (&#8216;uname -r&#8217; in a console will display your kernel version &#8211; you should look for default or smp at the end of the string).</p>
<p>For the modeline, I checked the X startup log (/var/log/Xorg.0.log). When the open source Nvidia driver (nv) loads, it dumps the information read from the display via <a title="EDID in Wikipedia" href="http://en.wikipedia.org/wiki/EDID">EDID</a>, Among other things, this dump gives the allowed frequence ranges and display timings. This is what I came up with:</p>
<blockquote><p>ModeLine &#8220;1920&#215;1200&#8243; 154.0  1920 1968 2000 2080  1200 1203 1209 1235</p></blockquote>
<p>This line goes in /etc/X11/xorg.conf in the section labelled Modes. Also, in the Screen section, &#8220;1920&#215;1200&#8243; should be the first mode in each of the subsections.<br />
For the changes to take effect, X needs to be restarted. Either reboot the machine or do an &#8216;init 3&#8242; to go into console-only mode and then an &#8216;init 5&#8242; to start X again.</p>
<p>With the new driver, the display came up correctly. Next problem was that the text was really, really small. This is because the DPI of the new panel is much higher than the old CRT. Fixing this is easy: Open up Desktop > Control Center > Fonts. Click &#8216;Details&#8217; and set resolution to 94 dots per inch. This is also a good time to adjust the font rendering setup. I seem to get the best results with Subpixel smoothing and Full hinting, but that is probably a matter of taste.</p>
]]></content:encoded>
			<wfw:commentRss>http://christian.krog-madsen.dk/2006/09/10/trouble-with-1920x1200-resolution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ink is flowing!</title>
		<link>http://christian.krog-madsen.dk/2006/07/12/ink-is-flowing/</link>
		<comments>http://christian.krog-madsen.dk/2006/07/12/ink-is-flowing/#comments</comments>
		<pubDate>Wed, 12 Jul 2006 21:32:41 +0000</pubDate>
		<dc:creator>Christian Krog Madsen</dc:creator>
				<category><![CDATA[Hardware Devices]]></category>
		<category><![CDATA[Installation]]></category>

		<guid isPermaLink="false">http://krog-madsen.dk/wp/archives/3</guid>
		<description><![CDATA[As reported in the original post about my installation of OpenSUSE, my Canon iP4200 winprinter was detected during the initial install. When I tried to print, though, nothing happened, as I had suspected.After a bit of googling, I found a &#8230; <a href="http://christian.krog-madsen.dk/2006/07/12/ink-is-flowing/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>As reported in the <a title="First looks - OpenSUSE 10.1 Installation" href="http://krog-madsen.dk/wp/archives/1">original post</a> about my installation of OpenSUSE, my Canon iP4200 winprinter was detected during the initial install. When I tried to print, though, nothing happened, as I had suspected.After a bit of googling, I found a post by <a title="Printing" href="http://owlfish.com/weblog/2006/04/08042006.html#22:57:21">Colin Stewart</a> linking to some binary-only drivers released by Canon. Looking a bit more, I found the driver in Canon Europe&#8217;s <a title="Canon Europe" href="http://software.canon-europe.com/software/canon_print_filter_for_linuxs24302.asp?model=">software center</a> along with an installation guide. The guide even covers SUSE 10!<br />
The driver works through the CUPS printing system, so you must have that installed to use the driver. CUPS is on the OpenSUSE installation medium and can be installed via the Package Manager. Chances are that you already have it installed.</p>
<p>The Canon driver comes with two RPMs that need to be installed (as root!):</p>
<blockquote><p># <span class="green">rpm -ivh cnijfilter-common-2.60-x.i386.rpm<br />
# </span><span class="green">rpm -ivh cnijfilter-ip4200-2.60-x.i386.rpm</span></p></blockquote>
<p>Now, CUPS shoud be restarted to read the new driver definitions.</p>
<p>After the RPMs are installed, the iP4200 driver appears when you add a new printer through the Yast2 configuration tool. Start Yast2, select Hardware and Printer. Add a new directly connected printer, select USB as the connection method, select a device (probably /dev/usb/lp0), enter a queue name. Next, you must select the printer model. Click on Canon in the left list, then you should be able to find &#8220;iP4200&#8243; in the right list. In case it is not there, manually select a PPD file and enter &#8220;/usr/share/cups/model/canonip4200.ppd&#8221;. Go to the final step of the wizard, where you will find a test button. Click it to have a test page printed (remember to turn on your printer!). With a bit of luck you will soon see a piece of paper adorned with the OpenSUSE logo emerge from your printer.</p>
<p>Canon printers already have a lot of selling points (and I for one am extremely pleased with my iP4200), but Linux support is a major factor when considering which printer to buy. In the past I have almost always rebooted into Windows when I wanted to print something. No more!</p>
]]></content:encoded>
			<wfw:commentRss>http://christian.krog-madsen.dk/2006/07/12/ink-is-flowing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>First looks &#8211; OpenSUSE 10.1 Installation</title>
		<link>http://christian.krog-madsen.dk/2006/07/07/first-looks/</link>
		<comments>http://christian.krog-madsen.dk/2006/07/07/first-looks/#comments</comments>
		<pubDate>Fri, 07 Jul 2006 21:17:29 +0000</pubDate>
		<dc:creator>Christian Krog Madsen</dc:creator>
				<category><![CDATA[Hardware Devices]]></category>
		<category><![CDATA[Installation]]></category>

		<guid isPermaLink="false">http://localhost/km/?p=6</guid>
		<description><![CDATA[Slick! &#8212; that is the best word I can find to describe the installation procedure in OpenSUSE 10.1. Today, almost all desktop Linux distributions have a graphical installer which hides most of the gory details of installing an operating system. &#8230; <a href="http://christian.krog-madsen.dk/2006/07/07/first-looks/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Slick! &#8212; that is the best word I can find to describe the installation procedure in OpenSUSE 10.1. Today, almost all desktop Linux distributions have a graphical installer which hides most of the gory details of installing an operating system. OpenSUSE&#8217;s installer is certainly one of the best I have tried, and its ability to auto-detect hardware is superb. In my mind, installing OpenSUSE is easier than installing Windows, since almost all the hardware is configured automatically, and you do not need to run a bunch of CDs to install special drivers for your devices.</p>
<p>I installed from the DVD edition. For some reason, I had disabled booting from the DVD drive, so the first step was to enter the BIOS and enable booting off the DVD. After restarting, the nice blue graphical installer appeared. All through the installation, a list on the left side shows the steps you have completed and the ones that remain.</p>
<p><a title="View full size" href="http://localhost/km/wp-content/uploads/2006/08/install.jpg"><img id="image6" alt="Installation screenshot" title="Installation screenshot" src="http://localhost/km/wp-content/uploads/2006/08/install_thumb.jpg" /><br />
</a><em>Installation screenshot<br />
</em><br />
Partitioning the harddrive(s) can be rather daunting, since if you mess up here, you may loose data on existing partitions. The installer proposes a number of setups that will work fine if you are installing on a fairly standard machine. You can also choose your own partition scheme. My rig is definitely non-standard with multiple disks and partition types, so I went for manual partitioning. I deleted my existing Fedora partitions and created new OpenSUSE partitions. I went with ReiserFS journalling filesystem instead of ext3 &#8211; not really sure what the pros and cons are, but ReiserFS seems to be the default for OpenSUSE, whereas ext3 was the default for Fedora.</p>
<p>Package selection comes with the standard package groups that cover the major scenarios for use, like development, servers, games etc. Sensible defaults are provided, so most users should probably stick with the package groups. Advanced users may choose to customize their setup by selecting individual packages from the enormous repertoire included on the DVD. Some versions of OpenSUSE ship with a collection of packages containing non-open source software, like an Adobe Flash Player plugin, RealPlayer and Sun&#8217;s Java JDK. These are definitely nice to have, so one should be sure to select the right download from<a title="OpenSUSE.org" href="http://www.opensuse.org"> opensuse.org</a>.</p>
<p>During the installation SAX auto-detected my graphics card and monitor and decided on a resolution of 1280&#215;1024@89 Hz! This is better than what I have managed to get it to do in Windows, where I am limited to 1152&#215;864@85Hz. Awesome! In the early versions of Linux setting up X could be tricky business. I remember messing with scanlines trying to get the best resolution and frequency out of my monitor. None of that these days &#8212; it just does the job and asks you to confirm. Perfect!</p>
<p>The installation even auto-detected my winprinter, a Canon iP4200. I suspect it may just have read the device descriptor from the USB bus, though. Traditionally, printers have been one of the Achilles&#8217; heels of Linux distributions, because the cheap so-called winprinters have all used proprietary protocols, leaving you stuck with the manufacturer&#8217;s Windows-only drivers. With the growing acceptance of Linux, some manufacturers have started either opening their protocols or publishing closed source drivers. Canon, however, have a reputation as being very uncooperative when it comes to printers. Stay tuned for a new post, when I have tested the printer.</p>
<p>In all, the installation took about 1 hour and left me with a modern operating system, an attractive graphical user interface, a full-featured <a title="OpenOffice.org" href="http://www.openoffice.org">office suite</a>, a very capable <a title="The GIMP" href="http://www.gimp.org/">image manipulation program</a>, a <a title="Inkscape" href="http://www.inkscape.org/">vector graphics program</a>, a full suite of software development tools, and much much more.</p>
<p><a title="Click to see full size" href="http://localhost/km/wp-content/uploads/2006/08/desktop.jpg"><img alt="Desktop" id="image8" src="http://localhost/km/wp-content/uploads/2006/08/desktop_thumb.jpg" /><br />
</a><em>My new OpenSUSE Gnome desktop after some UI customization. Note that the transparent left panel is not using xgl.</em><a title="Click to see full size" href="http://localhost/km/wp-content/uploads/2006/08/desktop.jpg"><br />
</a></p>
]]></content:encoded>
			<wfw:commentRss>http://christian.krog-madsen.dk/2006/07/07/first-looks/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
