Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Does anyone here have experience installing opensuse 10.3 on a ga-p35-dq6 mobo? I have 5 HDD of which 4 (7200rpm) in a raid-10 config (ICH9), containing 3 more or less equally sized partitions (c:\ with vista-x64 on it, d:\music and e:\user). The fifth hdd (PATA) contains two partitions (non-raid), also equally sized and is used for backup purposes mainly (5400rpm).
Yast-diskpart lists the HDD as following:
/dev/mapper/pdc-djifcdah 232GB (BIOS-raid)
/dev/mapper/pdc-djifcdah_part1 116GB (DM-raid)
/dev/mapper/pdc-djifcdah_part2 116GB (DM-raid)
/dev/sda 149GB samsung-hd160hj
/dev/sda1 99.3GB linux native
/dev/sda2 97.6 GB linux native
/dev/sda3 101GB linux native
/dev/sdb 149GB samsung-hd160hj
/dev/sdb1 99.3GB linux native
/dev/sdb2 97.6 GB linux native
/dev/sdb3 101GB linux native
/dev/sdc 149GB samsung-... etc.
/dev/sdc1 74.5GB fat16
/dev/sdc2 74.5GB fat16
/dev/sdd 149GB samsung-hd... etc
/dev/sdd1 74.5GB fat16
/dev/sdd2 74.5GB fat16
/dev/sde 232.8GB Maxtor-stm...etc
I suspect I would need to load a module when I start the installation? is that true? and if so which module would be appropriate? or am I missing something else here?
/dev/sde could be sacrificed , but I definitely need to keep my vista installation and the other partitions on the raid-10, so any suggestions would be very welcome, thanks in advance
Yes, that's the mobo.
And I agree with you, it seems Yast doesn't interpret the partition tables the right way or the tables have changed in some obscure manner ? I think that is pretty disturbing...
Vista boots just fine. The samsung disks are not formatted with a linux filesystem, well, at least I did not do that. They were originally ntfs formatted.
After reboot following the aborted linux install however, the raid was degraded, two disks had been reverted to non-raid (after post, that message was displayed) and had to be rebuilt, fortunately that went fine, so the situation is again like I described previously (and as I wanted it to be pffff).
I am a bit confused now because the samsung disks are in fact connected to the Intel ICH9 and the maxtor to the gigabyte raid controller, weird? The raid is controlled through the Intel matrix storage console (ver 7.6) Or did I misinterpret that?
Could it be that the Yast installation system changes something during
the installation setup? Maybe the Yast partitioning program does when it reads the partition tables? That is what I suspect, but I haven't found any information on Yast yet, pointing out that way. That's why I didn't proceed installing, I am currently making a full backup of all vista partitions, when that is done, I can safely give it a try ;-)
Do I understand correctly that I will not be able to install linux on the drives attached to the Jmicron controller? Or at least not without rearranging all of the drives?
Actually I did consider HW-Raid, but my budget won't allow it just yet... you know christmas and all..
The system is now almost ready for the linux install attempt.
I am curious enough to try some fiddling around with the raid disks even if it screws up Vista, everything is backed up now so there are no drawbacks there from my point of view.
Linux has been my main OS since about 10 years now and I am curious to see how it will perform on this mobo with 2GB ram and an E6850 cpu. I do have some doubts about the graphics performance (HD2600XT) but I am gonna try it anyway, I'll inform you regarding my progress,
I have read about some recommendations of using AHCI, this is supposed to be preferred bij linux? Any insights on that?
Well, Opensuse installed just fine on the maxtor. With the raid re-connected, grub caused some problems (which I expected);
Manually removing the first line ( : " root(hd4,0) " ) from the options given when grub fails (in a non fatal manner), solved the problem.
Now I can boot linux, using the boot-menu (F12) and select the maxtor. When I want to boot vista, I have to do a cold-(re)boot, well for the time being I can live with that I suppose.
When I try a soft-reboot from linux to boot Vista, the raid disks and -config are not properly recognized by the controller. After a cold-reboot this does not happen, Vista boots fine in that case. Anyway, a partly successful installation I would say, I contacted Gigabyte about this issue and now await their response, to be continued?
this is at the edge of my ken but I have noticed that there is a problem on Yast2 under suse 10.3 and there is a patch available from Nuvell to cure a loop back error.
Don't have a raid array but have managed to get a maxtor external drive to boot up on suse 10.3.Had to create a separate directory to house the boot options. Ignore this if I am stating the obvious. The above achieved more by luck than judgment. Why do you want vista-it's more cost than delivery.
Having spent so much money on proprietary software there is a feeling of reluctance about giving it up. The money was spent in the first place because the software came with the computer... this is actually why I dithered for 18 months before changing. I had to give up Works, Publisher, Myst etc.
Another reason may be that the computer is a gift and the software is needed to interoperate with unenlightened freinds or collegues. (Reason I have skype installed).
It seems to need repeating that GRUB doesn't support RAID boots, and so the boot partition cannot be on a raid volume. In this case, drivers need to be available to support the fakeraid on the board. Note that true HW raid will show up as a single drive to linux.
You have a good observation about Vista. The disproportionate investment in an OS used on 90% of the system, but used only 10% of the time, is a little odd. OTOH: that 10% could be to play some online game which does not have a linux client.
Last edited by Simon Bridge; 12-21-2007 at 08:59 AM.
Thanks for the links Simon, it looks indeed similar to adding linux to the NT boot loader, I should be able to get that to work, I'll let you know.
The main reason for purchasing Vista is keeping my windhoze knowledge up to date, so I bought it with my new pc. My kids are used to playing their games on ms-windows so for them its easier as well. Later on they will be taught how to handle linux so they can decide for themselves what to use. So from my point of view it was a good investment regardless of all the drawbacks of Vista.
The main reason for purchasing Vista is keeping my windhoze knowledge up to date,
This I can appreciate - I kept a WinXP Home license for the same reason (last I'd used windows it was Win98)... only I discovered that it was more painful moving from nix to win than the original shift in the other direction.