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.
I resized my Windows partition recently and afterwards I could not get a dual boot loader - I only get a command line interface starting "GRUB version 0.93 (636K lower / 1039182K upper memory). I tried repairing my MBR by running Window's restoration, but in the Setup process I get a blue screen that spits out some hex and pci.sys. Any ideas on what I can do? Thanks a lot for your help!
If your grub is not working you can always use a live cd and boot up that and repair grub from their. or you can boot up a windows disk and go into recovery console and issue a fdisk /mbr(Which I think will rewrite the current boot loader with a dos based one.) Then use the live cd to reinstall grub again. Those are the only two I know of unless I am reading your problem wrong.
Hey, thanks for your reply. I would have tried to reinstall MBR through a Windows Setup disk, but setup crashes out into that blue screen (spitting out hex and the pci.sys file) before I get an option to load the recovery console. Any suggestions?
Maybe -- I've seen the Windows setup routines crash when they encounter a partition type they don't understand. The most probably reason that the OP gets the GRUB command line interface is that GRUB can't find its root partition (usually the /boot partition of the Linux system, but otherwise / if there is no separate /boot partition). Fortunately, you can just enter the booting commands on GRUB's commnd line -- usually something like:
This assumes /boot is the first partition of the first hard drive (hda1 or sda1). If you know your Windows partition is hda2 (hd0,1) then you can usually boot Windows with:
To chainload the Windows boot loader and go on and boot into Windows. Once you've booted into Linux you may need to re-install GRUB so it knows where to look for the menu.lst and its other config files. What I'm guessing happened is that you moved these when you resized your Windows partition and GRUB now no longer knows where to look for them. You can also use a LiveCD to do this as suggested above.