In the first post on this subject, I unpacked the new Samsung laptop and went through the Windows 7 Home Premium installation and configuration. To be perfectly honest, this is an exceptionally nice sub-laptop, even when running Windows - it is fast, the keyboard and touchpad are comfortable, the screen is very readable and has good resolution, and although booting and shutting down Windows is noticeably slow, using the recommended "sleep/resume" is very fast, and I haven't had any problems with that yet either. The next step is to prepare it for Linux installation, and then to actually install Linux on it - in this case that will be openSuSE 12.1 KDE.
So, what needs to be "prepared" for Linux installation? As I mentioned in a previous post about setting up Windows/Linux dual-boot systems, the first thing to do is create the Windows Recovery Media, if your system wants/needs/requires that (i.e. did not come with recovery media included). In addition to that, you might want to make a backup of the finished Windows installation, because if you subsequently need to restore from the "Recovery Media", the notebook will be put back to the original factory configuration, and you will have to slog through the "First Startup and Configuration" procedure again.
Next comes the disk partitioning - you have to have a place to install Linux. In the case of this Samsung notebook that will be a little easier than with some other systems, because the Samsung installation procedure for Windows gave me the choice of either using the entire available space on the disk for one large C: driver, or splitting the available space between a C: and a D: drive. By choosing to split the space, what I was actually doing was dividing the available space between Windows and Linux - Windows will get the C: drive, of course, and Linux will be put in place of the D: drive. If you are just installing Linux for the first time, and you only want to "stick your toes in the water", you can make the D: partition relatively small, just enough to contain a Linux root partition and a Linux swap area. I have routinely installed Linux distributions in a 4GB root partition, but if you want a bit of room to install additional software and working space, I would recommend something like 8GB-16GB. The swap space should be at least the size of the memory in the computer, so in this Samsung I will make that 4GB, which means making D: at least 20GB is enough. At the other extreme, if you know that you will be primarily using Linux, and you are only keeping Windows around for backward compatibility, you can easily reduce the C: partition to something like 64GB, and give the rest to D: (eventually for Linux). Anything within these two extremes is of course perfectly acceptable, and although experience can help determine a reasonable range, the exact distribution is always going to depend heavily on the particular size of disk and amount of memory you have.
There are a number of ways to manage disk partitioning under Linux, any one of which is vastly superior to the nearly useless Windows. I prefer GParted, because it gives me a graphical interface, and it can control pretty much every aspect disk management, including create/delete/resize of Primary and Extended partitions, lots if different types of filesystems (including NTFS), and set the flags associated with disk partitions. It is included on the Live distributions of Ubuntu and Linux Mint (and various others), and on various dedicated administration and disk recovery Live media including its own Parted Magic, the well-known System Rescue CD and others. I always have Ubuntu and Mint live USB sticks handy, so I just boot one of them to run GParted; if you don't have one, I can say that it is never a bad idea to have a Parted Magic or System Rescue CD around.
When I ran GParted on the Samsung after completing the Windows installation, the disk looked like this:

There you can see the first partition is 100MB for the Windows bootloader, the second partition covers most of the disk (404GB) that I gave to C:, the third partition is actually an Extended partition which contains only the 40GB that I gave to D:, and the fourth partition is 21GB for the Samsung Recovery Solution. Another nice feature of the Samsung installation procedure can be seen here - not only did it let me split the disk for C: and D:, it also put D: in an Extended Partition, rather than using all four available Primary Partitions for its own installation. This makes it a bit easier to re-allocate the D: area for Linux.
So, at this point all I have to do is select /dev/sda5, which is the NTFS logical partition within the extended partition, and delete it. As I am fairly picky about how/where my partitions get allocated, and the exact sizes, I would then go ahead and create a 36GB ext4 partition and a 4GB Linux Swap within the /dev/sda3 Extended Partition, but you certainly could just shut down at this point, and let openSuSE/Fedora/Ubuntu/Mint/whatever automatically allocate the necessary partitions during installation, and they would make reasonable choices.
Once the disk partitioning is done, you are ready to install Linux. In this case I am going to install openSuSE 12.1, so I go to the openSuSE Download web page, and get the Live KDE image. I generally use the 64-bit version whenever possible (which is just about always these days), so I download that ISO image. There are links on the openSuSE download page to information on how to burn the ISO image to CD, and how to convert it to a Live USB image.
Once you have a bootable CD or USB stick, you're ready to take on what can be one of the trickiest parts of the procedure - figuring out how to boot it. If you are installing from CD, you have the problem that most netbooks and sub-notebooks don't have a built-in CD/DVD drive, so you have to boot from a USB CD/DVD drive. If you are installing from a USB stick, you have to boot from that - which is generally NOT exactly the same as booting from a USB CD drive. In general, when you first power on a system it goes through a power-on self-test (POST) sequence. During this time you can hit some key to tell it that you want to select the device to boot from, but exactly what key that is varies between systems, and there might even be more to it than that. Here are a few quick notes:
- Samsung uses ESC on most of its systems
- HP uses F9 on most of its systems
- Fujitsu uses F12 on most of its systems
- Acer uses F12 on most of its systems, but you often need to go into the BIOS to enable it
There are, of course, other variations; I can't remember what either Lenovo or Dell use, and there are plenty of others I have never tried. In general, look at the screen during POST for a hint about what is possible. If all else fails, you can try going into BIOS setup and change the boot priority, to put things like "USB CD", "USB Disk" and "USB Floppy" ahead of the hard disk drive. Oh, just to keep thing interesting, there are occasionally other weird variations and limitations. This Samsung 305U, for example, will only boot from a USB stick when it is initially powered on, and specifically NOT when it is "rebooting" from either Windows or Linux. So if you are up and running, and want to go back to a USB boot for some reason, you have to shutdown and power off, then start again, you can't simply "reboot". Sigh.
When you boot the openSuSE installation disk, you will get a menu which lets you select the Live image, the Installer, or a couple of other debug/startup options. If you boot the Live image it will bring up a full Linux system, running only from memory and the installation media, where you can try it out, check device support (see, for example, if wireless networks are found), and generally get the feel of Linux on your system before installing. If you then decide to go ahead and install, there is an "Install" icon on the desktop which will start the installation procedure. Alternatively you can choose "Install" from the boot menu and it will go directly into the installation procedure, without completely bringing up Linux and all of its associated services, which can be a bit faster.
The installation procedure then goes through only a few screens, as follows:
- Language/Keyboard selection: If you have a non-U.S. keyboard, this is the place to define it. This option frequently gets overlooked because it is a small box at the top of the window, and the rest of the window is filled with the Software License Agreement.

- Clock and Time Zone selection: Click on a region to get an enlarged map (Europe or whatever), and then your specific location. Note that if you have a steady hand and sufficient patience you can select the specific location directly from the first world map.

- Disk Partitioning: There are several important choices packed in this screen. First, it will examine the disk drive and propose a layout based on the free space that it finds, so if you just left the extended partition empty after deleting D: above, it will propose a root, a home and a swap partition within that area. If this is good enough for you, just click Next and move on. If for whatever reason this isn't what you want, there are a couple of options. The simplest is if you don't want a separate /home partition, perhaps to save disk space or make things a bit simpler. Just un-check the box for that, and it will update the proposal. If you want even more control, you can click "Edit Partition Setup" and make changes to the proposed layout, or click "Create Partition Setup" and make whatever you want.

- Create New User: It will not let you create a user with no password. This is a good thing.

- Summary and Confirmation: This shows everything that either you have specified or openSuSE has assumed, so you can confirm it all.

- Last Chance: One more time, just to be absolutely sure. Click "Install", and you're off.

Installation takes 15 minutes or less, and then prompts you to either reboot or continue testing. You're done!
jw











Talkback
Hi Jaimie Watson
Happy New Year to you. All the best for 2012. I was very impressed with your article, and found it complete. By the way, I am also the owner of a Samsung R540 Laptop.
Here is some other experience I had with SUSE. I had tried SUSE on another Desktop system which also had 2 versions of UBUNTU, Fedora and Debian (both 32bit and 64bit software). Suse installs just fine, but assumes it is the only Linux on the system, and replaces the MBR with one of it's own, ignoring the other Linux systems. This mbr action during installation blocked the access to the other Linuxes.
If SUSE is being used with any Windows version and SUSE is the only other system, there is absolutely no problem. I have multiple Linux versions simply because I do some software development, and my software has to run on the mentioned versions.
No, I do not currently have SUSE installed anywhere for the reason I mentioned. I will however, install it on the laptop as it is a stable and full functional version, with all the features that a business person would want.
@Leslie Satenstein - Sorry for the delay, I had overlooked this comment. I agree with your comment about the difficulty of installing openSuSE along with other Linux distributions. It is even more frustrating because the installation summary/confirmation window specifically says "Boot from MBR: disabled", but then it goes right ahead and installs its own GRUB to the MBR. It is not too difficult to repair, because openSuSE still uses legacy GRUB, and the boot menu config file is very easy to update, but it is still irritating.
Thanks for reading and commenting.
jw
I'm a little puzzled, I thought SuSe 12.1 had adopted Grub2. Nevertheless, the menu.lst file is still present.
On my own computer, I seem to have achieved an unexpected result when installing SuSe 12.1 as one of five Linux Distros on a Windows 7 Starter Samsung Netbook.
Initially, the SuSe boot screen shows Windows and a selection of Suse options. Selecting Windows brings up the choice of Windows itself and NeoSmart Linux. Selecting NeoSmart linux brings up the Ubuntu 11.04 boot menu which was in place before the Suse installation. This boot menu appears to keep itself up to date and does also have the Suse entries of and, of course, Windows again.
I believe, in the past, I might have used NeoSmart EasyBCD to gain access to Ubuntu, after installing SuSe 11 which still does use Grub, in order to regain access to all the Linux distros by updating and reinstalling the Unbuntu 11.04 Grub2 boot loader.
Interestingly, although Linux disk utilities shows three primary partitions and one extended partition containing six Linux partitions and the swap partition. Windows disk manager shows ten primary partitions.
The problem is not installing openSUSE, that is rather straighforward, but the problem is fixing the samsung specific issues, like the Fn-keys, screen resolution, suspend/hybernate etc.
@smspvdm - My experience indicates that your information is out of date. On the Samsung notebook described in this post, and on various other Samsung systems which I own and have openSuse installed on (N150 Plus, NF310 and P-580), the Fn-Keys work, the screen resolution is exactly right when the installation is complete, no adjustment or fiddling required, and both suspend and hibernate work flawlessly. There were other serious issues with this system, described in subsequent blog posts, with the wireless networking and display brightness, but the issues you list are not a problem.
@Moley - I had not noticed your comment, sorry. That is one of the strangest set of symptoms that I have ever heard of, it would be very interesting to figure out exactly how you got there, and exactly what it means. The only thing that doesn't surprise me is that Windows disk manager doesn't understand the partitioning, I have seen that myself and it was one of the reasons I quit looking at that.
Thanks to both for reading and commenting.
jw
@watson: Apparently not so. I recently purchased a new Samsung RV720, hoping to run openSUSE 12.1 on it. The problems with it are that the screenresolution won't go beyond something like 800x600, probably because the nouveau drivers don't support the NVIDIA GeForce GT 520M CUDA chip. Also screen brightness and volume adjustment keys (Fn) do not work.
Of course, these are showstoppers for me, so we reluctantly run windows 7 on it now. Fortunately, all our other computer happily run openSUSE!! :D
@smspvdm - Wow, that is really bad news. I assumed from the fact that the Fn-keys work just fine on four different Samsung laptop/netbooks, from four different lines, that the general problem had been taken care of now. Obviously I was wrong, sorry about that. As for the display problem, I should have known enough to keep my foot out of my mouth, that is always very dependent on the specific graphic chip and driver combination. It sounds as if you are plenty experienced enough to know how to use the nv driver if you wanted to. Anyway, I am in the same position, indirectly, as my partner is using our latest Samsung 305U with Windows 7, reluctantly.
Thanks for reading and commenting.
jw
Jamie,
I just wanted to report that as of yesterday most of the issues with the Samsung RV720 have been fixed. I have installed the latest 3.3-rc4 kernel in openSUSE 12.1 (there is a repo for that), and now the nouveau driver is able to use the correct resolution. Also suspend and volume-Fn keys work. So the only issue still is the brightness Fn key.
B.T.W. Keep up the good work!
@smspvdm - This is great news, thanks very much. I will give this a test this weekend. I will be quite pleased if it works on the 305U as well, because I still really like that little thing.
Thanks for reading and commenting.
jw
We are making Turkish internet marketing products such us promosyon and flash bellek. Your publications are realy good. I am following your new researches with my group.