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.
there's a number of ways to do it, and there's plenty webpages out there dealing with it.
I would go for grub. it's the most versatile boot manager. If it's a recent version of Suse it may even try to install grub for you.
It sounds as if you haven't even got suse installed yet.
Also read up about the MBR, Master boot record. The is the first 512bytes (that's all!) of the f¡rst harddisk where grub (or part of it) will need to go.
You'll notice I'm not giving you a personalised, exact, step by step guide to accomplishing what you want. And you may complain. But I've already written more in my answer than you have in your question. In any case, this all done by clues, trial and error and google.
A bit like life really. It´s no mere coincidence that "linux" and "life" share their first two letters :-D
ive been reading and most recommend that linux be the #1 drive as master
and xp be #2 drive as slave.
now this brings me to a brick wall because as i mentioned i have xp already on 1 of the drives and the jumper pins are (cable select on this xp already loaded drive)
so what do i do with the jumper pins with the new drive i want suse on? put a slave?master?
i also read linux cant tell cable select(for jumper pin).
i really dont feel like reformatting xp drive just cause jumper pins are at cable select.
new drive jumper pin settings are 16 heads (master)was how it came.
guide me ,, thanks all
ps. and this hitachi drive i wanna use for suse is driving me up the wall you can have (16 heads), (15 heads), (32gb clip), (auto spin disable)and for this 4 settings i can put jumper at master, slave, cable select, or forcedev1 present its a hitache drive,,o man. help
as it came was 16 heads,master for the jumper pins..
just stick the 30gb in as secondary master, slap the suse disc into the cdrom/dvd drive and install.
just make sure that when it comes time to partition your drive you select to manually partition.
and set /dev/hdb to be your root(/) partition.
Sorry to chime in after the fact on this one, but (for future information) the way I learned it (and the way it says in the Computer Repair Book I have) is that Cable Select is a replacement for the Master/Slave method. Taking only the Primary IDE channel (there are two channels, these are the connectors that are on the motherboard, NOT on the cable) into consideration, you should either have one hard drive set to Master, and one set to Slave, OR you should have BOTH drives set to Cable Select. In the case of Cable Select, the master drive goes on the top (black) connector, the slave drive goes on the middle (grey) connector, and the bottom (blue) plugs into your mobo. The Secondary IDE channel functions the same exact way.
There are exceptions though. On the first of the Cable Select systems (before it standardized with ATA-5) the middle connector was Master, and the top was Slave.
Cable select must be supported by your mobo, controller chip, and BIOS in order to use it though. Also, you must have a Cable Select Cable (the colors are a good give-a-way, but if there are no colors then you must look for pin 28 being disabled or it must be a 80 conductor (40-pin) cable for UDMA-3 and higher).
However, lonestar, if you have it working..... to hell with *proper* setup.
Originally posted by 0pal_t0ad thanks for the info, Volvogga!
how do you connect to the internet cable or adsl? and..umm...log off isn't the same as shutdown
We need to know more about your setup, are you using a router/connecting via Ethernet for example? If so, it shouldn't be that difficult.
No, logging off isn't the same as shutting down. When you log off, well, you'll just see a login screen. Any servers you have running will probably still be running. Shutting down is switching the machine off.
specs are windows xp installed right now (cable select) on a 40 gigHD
suse on 30 gig HD(slave)
p4 3.2C HT
p4c800-e deluxe mobo
1 gig ram
ati 9800 pro
lg dvd ram
now this mobo has onboard network card which im using
and it does connect to internet when i boot up with xp
but now that i have dual boot with suse and suse recognises the onboard network card but
it will not connect to the internet.
in SUSE when i go into YaST and into the network car configuration i see that it has detected
what i think its the onboard network card. name is ASUSTek 82547EI gigabit ethernet controller(LOM)
configured with DCHP.
i have dsl modem connected to D-LINK router 4 Port, (PC1) with suse connects to internet,
PC2 with windows ME connects to internet, and now this PC3 with dual boot(system specs above)WILL NOT
connect to internet with SUSE ,however it works fine with xp.
and in SUSE when i log out it gives me the option to turn system off , when i click on turn system off , it does its thing and says system is down , i manually have to press off button on front panel of PC case to cut off power.
As far as the power button goes, I have the same problem with FC3. I have been told that this is a relatively common problem, and it is a simple matter of the kernel or modules not interacting perfectly with your hardware. If you google the problem, there seem to be some workarounds out there. I haven't tried any of them, mainly because the problem is not that big a deal to me. Also, I have read that more often than not, the problem can be fixed by simply upgrading the kernel (another thing I have not done due to a slow internet connection).
As for your internet problem, I am not very good at networking, but I did a search on the model number you provided for your network card, and it came back with a site talking about an entire motherboard. This is the site I found that speaks of this mobo being compatible with Linux...
As you can see, it has your same network card. If you look towards the bottom of the page, it has a note that says that special drivers were needed to activate the network card. So it could be that Yast sees the network card, but doesn't have a driver for it as of yet. Intel provides the driver listed on that site (which surprised me). You can get it here...