Welp, I was getting somewhat bored with my computer, so I decided that I would reinstall SuSE today. I finally got my dual-layer 32-bit/64-bit SuSE 10.1 DVD, so now I don't need to switch CDs every few minutes. That will be nice. Anyway, this time I plan to document the quirks that I run into as I attempt to get my laptop back to the state it was in before all of this mumbo jumbo.

First off, I was able to install SuSE earlier today.. Everything seemed to be going well up until I should have logged in the first time. The login screen never came--it just showed the 'busy' cursor for a few minutes. Then I restarted the computer and it did the same thing. Then I decided to reinstall again... just because I could. The same thing happened, even though I chose the GNOME setup that time (whereas I chose to use KDE the first time). Eventually it dawned on me that the 3D acceleration drivers I used before required that I share some of my real RAM with my video card. I thought it might be a good idea to try disabling that business and seeing how things went on only the dedicated video RAM. It worked. I logged into a great-looking GNOME setup and played around for a bit. I noticed that my synaptics touch pad thinger (mouse) wasn't responding too well, and I'm not really a big fan of GNOME to begin with. So I'm in the process of reinstalling SuSE for the third time today--this time with KDE. We'll see how things go this time.

The installation has finished, and now I'm working on getting my wireless to function. I had previously acquired the appropriate 64-bit drivers, so those weren't hard to get back. I installed the ndiswrapper package that came with SuSE 10.1, extracted the drivers, and installed them. My laptop locked up the first time I tried to modprobe the ndiswrapper system, but it works ok now. I can see the wireless network here on campus but I can't do anything with it yet.

I suppose my time is up for now, but I will continue this post later.

I've been using SuSE Linux 10.1 on my laptop ever since the day it was released, and I have to say that I'm quite satisfied with it. I'm usually a Slackware man, myself, but SuSE has become one of my new favorites.

Ever since I first started using Linux some 7 years ago, I've kept an eye on SuSE. I came really close to actually purchasing a boxed copy back around version 7.3 I think. This was mostly because SuSE is so visually appealing. Once openSuSE came about, I was super excited and downloaded the 5 CD set for version 10.0 immediately. To my disappointment, this version didn't play well with my brand new laptop. I didn't feel like finding out why, so I just gently tucked the CDs away in the drawer with all of my other Linux CDs. As soon as the 10.1 CD set was publicly released on May 11th, I grabbed a torrent to get all of the 5 CDs plus the non-OSS add-on CD.

The same day, I popped the first CD in and began the installation. To my surprise, SuSE 10.1 had no qualms with my Radeon 200M, whereas almost all distros that I had tried on this laptop up to this point would lockup once they did anything outside of the wonderful console (besides Fedora Core 5). SuSE 10.1 was 1 up on all the others, especially after seeing the splash screen. Absolutely beautiful. The installation went really smoothly. I opted for the KDE install, as I'm not a big fan of GNOME. And this is despite the fact that the folks at SuSE spent a lot of time and effort making GNOME mesh well with their distro.

Once the installation finished, I began tinkering around in my menus just to see what there was to see. I have to say that things are set up pretty intuitively in KDE to begin with (or maybe I've just been using it for a long time), but SuSE makes it even better. Device recognition is actually beyond my expectations for Linux. Just about anything I pop into a USB port will be recognized within seconds and I will be asked what I want to do with it. Even my HP All-In-One printer/scanner/copier works without a hitch!! This is the first scanner that I've had function in Linux! Excellent. My media reader doesn't seem to be compatible with Linux yet, but that's fine since I rarely use it anyway. I was able to get my Radeon to play well with the proprietary drivers from ATI, and my FPS jumped from around 100 to 1100 when running glxgears. Nice improvement.

One thing that did take a long time to figure out was my wireless. I had only played with wireless one other time in Linux and that was on some generic PCMCIA wireless card in a past roommate's laptop. That seemed to be simple enough to setup, with the help ndiswrapper. However, finding the correct drivers for my internal wireless adapter, and finding them in the 64-bit edition proved to be quite the runaround. Eventually, I was able to get in touch with someone who graciously emailed them to me as an attachment. To my disappointment, however, ndiswrapper didn't seem to do wireless with these drivers either!! Wow. I put wireless tinkering away for a while, but came back to it amidst my boredom. I came across some forum that had the answer to my quest: a file link. The drivers I had received through email were the correct drivers, only they were linked up to some other device identifier. All I needed to do was essentially make an alias of my device identifier and make it point to the identifier used by the drivers. As soon as I did this, ndiswrapper worked like a charm. I was able to see several wireless networks in my area. I did (and still do) have a problem connecting to certain access points, however. For some strange reason, I cannot figure out how to connect to my own wireless router, nor the university wireless. It's rather frustrating, but I can live with an ethernet cable.

Ahh, yes. Linux.