A horrific start with openSUSE 11.1 December 21, 2008Posted by NAyK in Confessions, Firefox, First Impressions, Linux, OpenSUSE, openSUSE 11.1, samba, Ubuntu, Windows, Working on Linux, Working with Linux.
In the past 24-hours with the latest openSUSE 11.1, I’ve had a horrific experience. And while I’ve not given up on the distribution, I’m putting down my experiences here neither as a call for help nor as a rant to keep people away. Rather, an honest approach spreads honest knowledge… and hopefully I will be proved wrong, and others will not make the same “mistakes?” I made. What follows is a quick historical recount of my experiences with openSUSE and also my current trauma.
Believe it or not, I love openSUSE and have been using it since the 9.3 days. Of course I was, and still remain, a novice. Which means I enjoy installing the new openSUSE, I try to get it working on my machine/s and then, after using it for a few weeks/days… I go back to windows, waiting for the next openSUSE release. I know this just reveals that I am a shallow linux user, without much knowledge of the system, but sadly, that IS me.
I think openSUSE 10.2 was one of my best Linux experience, it really improved from my traumatic experience with openSUSE 10/10.1. I eventually used 10.2 a lot, for a few months, as my primary distribution, and the only reason why I returned to Windows was because I needed Dreamweaver and Photoshop for important (read official web-designing). I did try the linux solutions, but I didn’t have the guts to invest company time and pages on my experiments.
Anyway… openSUSE 10.3 was quite traumatic as well, and when openSUSE 11 was released, I knew openSUSE would only improve. And it did. But then they had started promoting KDE 4 and while I liked it, I couldn’t use it everyday and shifted back to KDE 3.5. However by then it was too difficult to commit entirely to a Linux distro and I went back to Windows primarily, with occasional Linux visits.
One of the chief problems was that I wasn’t able to access my Linux files with explorerFS (the Windows based linux files viewer). I don’t know what happened, but once openSUSE could only be access FROM openSUSE, I couldn’t invest doing too much work in openSUSE in fear that I would waste too much time going back and forth.
I also was upset that I couldn’t access my Windows files from openSUSE when Windows was hibernated. This, is obviously for my safety, yet PCLinux allows this and it is really a useful feature. Still… that’s no excuses… just a reality.
Anyway… in time I suddenly realised that my openSUSE 11 started having problems with the audio. I couldn’t keep the speakers on without a feedback sound. Something like a mic feedback. I didn’t have the time to fix, so I waited for the new openSUSE 11.1
My horrific experience with openSUSE 11.1
downloading: I was one of the first people to start downloading openSUSE 11.1 (right to the minute it was released). I was waiting for it to allow me to download, kept refreshing the page, and when I got the direct ISO link I was delighted. In 2.5 hours I had the entire DVD on my disk, and another .5 hours I had the add-on disk.
burning and media testing: because I did the download in windows, I also burned the iso in windows (i usually prefer KDE). I then had to do a mediacheck in the openSUSE installation, and thankfully there were no problems in the DVD.
installation: The installation began and went quite smoothly… except I wasn’t able to connect to the internet because I am connected through wifi and I am not able to connect to my internet through the ethernet. Don’t ask me why… I called the Bell tech-support and their help wasn’t that great on this matter. (also I was running out of time, and wanted to get started, so I started without network configuration). The openSUSE installation is so swanky and cool (as always) that I didn’t pay attention to the new changes that may have been made. It’s just that things went so smoothly, I had no cause for complaint. I in fact used most of the default settings (I usually play around with the settings to get exactly what I need), because things were just going so well. The whole process took about an hour (the actual installation was about 35 minutes).
getting started: when I had my new KDE 4.1 desktop on my computer, I connected to the wifi connection without problems… which was great (openSUSE has always had a good wifi recogniser). And then got cracking with the updates (two security updates) and configuration.
desktop Configuration: that’s where things started getting buggy. I tried changing the desktop wallpaper, and when I changed it… nothing happened. Then I tried again… and the window crashed. hmmm? Anyway, thinking it was a KDE4 glitch… or a bug… I thought about reporting it… but I had to register as a new user and I wasn’t in the mood to do that… so I went to the KDE 3.5 session. and tried changing the desktop wallpaper there… and even there I had some problems, but I was able to change to one of the default pictures. I had tried installing my own picture… using firefox images right click set as desktop, but that didn’t work.
multimedia codecs: I then did the one-click install for all the multimedia codecs… and hoped I would be able to watch avi files. I wasn’t. I then had to install VLC player to view the avi files I had. Anyway… I didn’t want to get too picky… so I went to sleep with an imperfectly configured openSUSE. (ps I was able to go back to windows, as the grub recognised the windows booting).
The next day…
Boot configuration: the next day I started by configuring the boot… because I wanted to make windows the default. using YAST. Then I restarted and…
BAAM… no operating system! whaat?
I restarted again, and again, no operating system.
I was not concerned, thinking that perhaps the GRUB got messed up, so I tried to repair install using my openSUSE dvd. But when I tried fixing the GRUB, the entire C drive partition was unrecognisable. I wasn’t able to use or mount it. Hmmm.
Another try: I was a little concerned (though not that much because I had my important files backed up, but I didn’t have everything backed up, and I DIDN’T want to do a fresh Windows install because I would lose some preloading programmes). Still… I thought of a workaround. I tried using Ubuntu 8.04 to install and get Windows back… but even there the C drive was unregnisable. (I didn’t install Ubuntu as a result)
OK now I was worried… I returned to openSUSE disk and tried to install just the openSUSE installation, but it told me that the openSUSE root did not exist. Hmmm.
In effect, I was without a computer… with no windows or linux. Only solution, install linux again… I did that… and have found that I can’t access the C drive of windows… only the D and E (thankfully).
And now I have to repair my Windows installation… and hopefully that will be enough (I really don’t want to reinstall my Windows).
Ending… (or pause)… so that’s it… this is NOT a rant… just an experience-tale. To perhaps show my lack of experience.
I’m writing this from my second installation of openSUSE 11.1… and also on Konqueror because the Firefox is not working. What-the-heck? Something must be wrong… but I can’t imagine what.
Anyway, it’s back to repairing Windows and I hope I will return to tell a happier tale.
HOW-TO fix “Timeout on Server” in openSUSE 11 June 27, 2008Posted by NAyK in How-To, Linux, OpenSUSE, samba, Software, Windows, Working on Linux, Working with Linux.
Tags: network, settings
1. The problem was that I had attempted to connect to my office network like the openSUSE 10.2 days, and instead found that SAMBA (smb://) was giving me problems and not allowing me to even see my network.
2. I thought it was a KDE4 problem so I installed KDE3.5, and stopped the firewall, and instantly I was able to browse my network through SMB.
3. All good, I thought, until I got the dreaded “Timeout on Server” message when I tried to reaccess the server. I do remember seeing this message in the past, openSUSE 10.2, but was able to fix it by removing the firewall or by restarting openSUSE or even by waiting for a long time. No such luck this time, I had the server timeout message going on for a few days.
4. Internet help, didn’t seem to directly deal with my problem. Neither did the Forums (yes I was desperate). But I did come across a very extensive HOW-TO fix SAMBA from a famous “Swerdna” in the site: http://www.swerdna.net.au/linhowtolanprimer.html#nicwin
5. The HOW-TO was very difficult to follow through verbatum, especially because I am not a systems administrator. But still I trudged along and installed everything I should, and made a few minimal changes.One of the significant changes I made was that in the samba configuration file I replaced workgroup = WORKGROUP to workgroup = NAMEOFMYWORKGROUP (ie. the actual name of my workgroup)
6. I still did not have any luck and kept getting the timeout message.
7. In the Swerdna HOW-TO,however, there were two commands, “rcnmb restart” and “rcsmb restart” (without quotes) as “su” users.This restarts SAMBA.
8. I suddenly had a brainwave and instead of typing my loggin-password details (for my office network as) NAMEOFMYWORKGROUP/myname and PASSWORD I now typed myname and PASSWORD.
9. It worked. the SAMBA configuration had already put my Workgroup name in the settings, so my password was simpler and I guess the restarting of the SAMBA helped as well.
10. So far, my network has worked even though I have restarted my computer, which is a good sign. Now I have to see whether it will work with the SAMBA configured Firewall back on.
11. (latest update: I got the Firewall started and like Swerdna advised did the settings as I should. I realised that I couldn’t browse my network from SMB, it said that my firewall prevented me to, but I could directly access it using my IP address (which I got from my network administrator. So things are still good!).
On to more openSUSE adventures…