MISSING OPERATING SYSTEM

I am in the process of finishing yet another large recording project, from soup to nuts, all in 64studio. I must be the lucky one then, with my 2XSATA +1xIDE, being able to boot into 64studio. Sure, I had trouble when I added the IDE drive (Another PC I had blew up. and I canibalised the drive, which is a 160Gb 7200 Seagate - same as my other 2 drives, except that its IDE) The motherboard would not let me boot off the SATA after adding the IDE, which it previously did with no problems, so I created a small /boot partition on the IDE just for booting. Works well!

... And some other guy comes along, and has the decency to look here for help, it should be waiting for him! Thanks for everyone pitching in to help solve 64studio user's problems. That's what makes a Linux community great

This guy will never be heard of here again :P You're all sweet and try to help - even if it's a troll (popeyeray) that craps some thread. There's no better playground for a fanboy than the "adversary's" help forum.

Seriously. Most folks I've discussed my system with say 64 bit Linux is still quite rough around the edges... I'm on a different forum quite a bit, and I think I agree with their consensus. One thing to consider: the chipset I have is just barely 2 years old. In the Linux world where hardly any manufacturers offer drivers for Linux, and where the stability of the system rests on the quality of the early drivers, well, we should be happy if it can boot. I know, yours can't, I read the post, I'm sorry to hear that your SATA setup is causing you (and thousands of other Linux users) to suffer problems. Too many times I have bought systems that used uncommon chipsets, only to learn that the chipsets themselves were the most major issue. My current system uses ATI chipsets, and just that alone would be enough to fry me. Now add in the relative newness of 64 bit computing. And I'm using common old grunt IDE drives. You are using SATA, which is another hot topic in Linux realms right now... You've added one difficulty (64 bit Linux) to another difficulty (SATA). I'd say you could have researched the matter on any of a dozen Linux forums. Maybe you were a little bold, just throwing caution to the wind? Hmm? All in all, we are too advanced. To be fair, though, why not try to install a 32 bit version of 64S onto an IDE based system, just to clear your mind that Linux actually DOES support the stuff that is COMMON??

Funny , there was no version of M$ that would run on my amd-x64 machine with SATA drives when I bought it , but linux seems to run fine , & now dual boot between SuSE & studio64 . Poor popeyeray , fdisk /mbr , might have been quicker than restoring a backup - if you can now find it .

I had this problem the first time I installed 64 Studio. And I'm still having problems. However, I was able to successfully install 64 Studio, although I still can't boot to it, with the GRUB Loader, and I can still get access to Windows XP. When I first got this error, I reinstalled XP but then read on some other forums about GRUB installation and picked up that I should set up space for GRUB to be installed. When I reinstalled XP for the second time, I wiped out all partitions and then created a 128MB FAT16 partition to install GRUB on. Then I created a partition for XP, and then I partitioned the other space for the Linux OS, a swap area (5GB) and then left the rest alone for now. Installed XP, it boots fine. I install 64 Studio, making sure that I assign the 128MB partition with the /boot mount point and turn on the bootable flag. The swap area is assigned as a swap file area, non-bootable. The 64 Studio partition for me, right now in it's boot-failed state, has a Ext3 file system. After installation when it asks if you want to edit the MBR, do it but make sure that the screen shows that it recognizes XP first. Next time you boot, the GRUB loader should appear (although only for 5 seconds, it will be very quick) __________________________________________________________________________________________________ Desktop: DFI Lanparty nf4 Expert MOBO, AMD64 X2 2.4GHz, 2x 512MB DDR RAM, 300GB SATA HD (WindowsXP), 500GB SATA HD (Linux & Storage), 500GB SATA HD (Storage only) Laptop: 17" MacBook Pro, factory hardware defaults

Every linux distro I have installed on my new computer fails to boot. For some reason the wrong entries in /boot/grub/menu.lst are entered during install. eg root (hd1,0) needs to be changed to root (hd0,0) I have to boot from a live cd and edit this file.

And the reason I say that is because they are invariably the ones who never take the time to actually TRY to figure out a problem. They are also the same ones that constantly download one program after another because they can't figure it out and blame the software & fill their registry with bum entries that slow their systems down, instead of learning how their hardware actually works. I get the feeling that these people think computers run on magic and when things don't go right for them, they blame the magician (who is actually the programmer). So I say "yes, see you in 3 to 5 years, hope you learn how computers actually work by then"! It's ready for prime time (whatever time that actually is)...The problem lies between the keyboard and the chair, and programmers can only do so much to debug that problem...

Us linux folks includes you, my friend. The thing about nailing problems, is that the person that has the problem should put some effort towards fixing, or giving info to the right people. If you have a problem, and "Wait for support" your problem will take longer to fix. I had a problem initially, and after flogging the dead horse (or so it seemed) for two months, my problem was fixed, and I never looked back. Just my 2c worth.

http://64studio.com/node/314

Almost the same system as me. I have only 2 GB. Linux never needs any more. I had no problems. Sounds like you installed the boot loader in the wrong place.