LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices

Reply
 
Search this Thread
Old 02-28-2007, 04:20 PM   #1
tuffstuff
LQ Newbie
 
Registered: Feb 2007
Distribution: Debian Etch
Posts: 29

Rep: Reputation: 15
Cool "Error loading operating system" trying to install sarge 3.1r4 on SATA via AMD64


I'm not sure what is causing my BIOS (assuming it;s my BIOS) to not detect my boot loader after a clean install with Sarge on my machine (AMD 64) but I have a couple of ideas. Being a newbie I'm very familiar with the nuances of Linux compatibility or of computing in general, So here we go....

I understand that Sarge is written for 32 bit systems. Running AMD 64, I'm concerned that Sarge will have difficulty with that chip. I'm told by some that 32 bit Linux will treat a 64 bit chip like it's a 32 bit chip, no problem. Is that true? I read about several folks using Etch, but to my understanding the stable version hasn't been released yet. As a newbie, will I have much difficulty running Etch? I'm thinking this could be part of my problem. I've read conflicting reports about Sarge's compatibility with SATA drives. The most resent post I read said, with confidence, that there weren't any issues with SATA drives and Debian. Can anyone else confirm that? If they aren't a problem any longer than perhaps there is conflict with GRUB and dual booting. I've installed Debian on the SATA drive and Windows XP (2002) on the Master IDE drive. Has anyone heard of this being a problem? When I installed Debian it did detect another OS, but didn't list is as Windows. I've checked my BIOS over and over, granted I didn't understand some of the menu options. Before I installed Sarge I was running SuSe 10.1 and although I didn't have windows listed in GRUB I used the BIOS and switched the disk priority to the Windows system, no problems.

Ok, so thats about all I've gathered. Any insight?

Last edited by tuffstuff; 02-28-2007 at 04:22 PM.
 
Old 02-28-2007, 04:31 PM   #2
pljvaldez
Guru
 
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Squeeze (x86)
Posts: 6,092

Rep: Reputation: 269Reputation: 269Reputation: 269
Sarge uses by default a 2.4.27 kernel and a 2.6.8 kernel if you type linux26 at the boot prompt. Etch has much better SATA support since it uses 2.6.18 by default. Since Etch will be the new stable any time now, I would use Etch.

As for the bootloader, you have to install it to the Master Boot Record of the first hard disk. So order your disks in BIOS to boot Windows. Then when you install Etch, put it on /dev/sdb. But put the bootloader on /dev/sda (or hd0, I forget the syntax of what the installer asks for), which is the first hard drive. This should give you a grub menu. If Windows isn't in it, you can fix that from inside Debian.
 
Old 03-01-2007, 02:13 PM   #3
tuffstuff
LQ Newbie
 
Registered: Feb 2007
Distribution: Debian Etch
Posts: 29

Original Poster
Rep: Reputation: 15
thanks for your help, I re-installed debian last night and watched it install grub very carefully. I noticed that it did install it on the first hard drive listed as hd0, or something like that. I'll go and reorder my BIOS to boot that drive first and see what happens. I was wrong when I said that Debian detected my windows OS. I didn't detect it. Does having debian intalled on a different disk keep it form detecting Windows?

-Thanks again
 
Old 03-01-2007, 02:47 PM   #4
pljvaldez
Guru
 
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Squeeze (x86)
Posts: 6,092

Rep: Reputation: 269Reputation: 269Reputation: 269
No idea, but it's easy to add. Be careful about reording the hard disks. If you installed Debian with the windows disk as hd0, then that means you put grub onto the windows disk. If you had the debian disk as hd0, the swapping to windows first will not boot grub since grub will be on the debian disk (now hd1). There's some mapping commands and stuff you can do with the /boot/grub/menu.lst file to make everything boot.

Once you get it to boot into Debian, post your /boot/grub/menu.lst file, the contents of /boot/device.map (or maybe it's /boot/grub/devices.map, I forget), and the output of the command fdisk -l (which you might have to run as root user). then we can get it all configured properly to dual boot your machine.
 
Old 03-05-2007, 02:51 PM   #5
tuffstuff
LQ Newbie
 
Registered: Feb 2007
Distribution: Debian Etch
Posts: 29

Original Poster
Rep: Reputation: 15
Ok, sorry about the delay. here's my fdisk -l info and my grub menu.lst (I hope...)

PHP Code:
debian:~# fdisk -l

Disk /dev/hda300.0 GB300090728448 bytes
255 heads
63 sectors/track36483 cylinders
Units 
cylinders of 16065 512 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1       26109   209720511   83  Linux
/dev/hda2   *       26110       36482    83321122+  83  Linux

Disk 
/dev/hdb19.9 GB19998918144 bytes
255 heads
63 sectors/track2431 cylinders
Units 
cylinders of 16065 512 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1   *           1        2328    18699628+  83  Linux
/dev/hdb2            2329        2431      827347+   5  Extended
/dev/hdb5            2329        2431      827316   82  Linux swap Solaris

Disk 
/dev/sda82.3 GB82348277760 bytes
255 heads
63 sectors/track10011 cylinders
Units 
cylinders of 16065 512 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          61      489951   82  Linux swap Solaris
/dev/sda2   *          62        3708    29294527+  83  Linux
/dev/sda3            3709       10011    50628847+  83  Linux

Disk 
/dev/sdf519 MB519962624 bytes
8 heads
55 sectors/track2308 cylinders
Units 
cylinders of 440 512 225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1               1        2309      507660+   6  FAT16 
and...

PHP Code:
# This is a divider, added to separate the menu items below from the Debian
# ones.
title        Other operating systems:
root


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hdb1.
title        Debian GNU/Linuxkernel 2.6.8-2-386 (on /dev/hdb1)
root        (hd1,0)
kernel        /boot/vmlinuz-2.6.8-2-386 root=/dev/hdb1 ro 
initrd        
/boot/initrd.img-2.6.8-2-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hdb1.
title        Debian GNU/Linuxkernel 2.6.8-2-386 (recovery mode) (on /dev/hdb1)
root        (hd1,0)
kernel        /boot/vmlinuz-2.6.8-2-386 root=/dev/hdb1 ro single 
initrd        
/boot/initrd.img-2.6.8-2-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hdb1.
title        Debian GNU/Linuxkernel 2.6.8-2-386 (on /dev/sda2) (on /dev/hdb1)
root        (hd1,0)
kernel        /boot/vmlinuz-2.6.8-2-386 root=/dev/sda2 ro 
initrd        
/boot/initrd.img-2.6.8-2-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hdb1.
title        Debian GNU/Linuxkernel 2.6.8-2-386 (recovery mode) (on /dev/sda2) (on /dev/hdb1)
root        (hd1,0)
kernel        /boot/vmlinuz-2.6.8-2-386 root=/dev/sda2 ro single 
initrd        
/boot/initrd.img-2.6.8-2-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda2.
title        Debian GNU/Linuxkernel 2.6.8-2-386 (on /dev/sda2)
root        (hd2,1)
kernel        /boot/vmlinuz-2.6.8-2-386 root=/dev/sda2 ro 
initrd        
/boot/initrd.img-2.6.8-2-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda2.
title        Debian GNU/Linuxkernel 2.6.8-2-386 (recovery mode) (on /dev/sda2)
root        (hd2,1)
kernel        /boot/vmlinuz-2.6.8-2-386 root=/dev/sda2 ro single 
initrd        
/boot/initrd.img-2.6.8-2-386
savedefault
boot 
I should explain what I've done since my last post: I installed debian to every disk on my machine (except my flash, sdf) in the hope of getting at least one to boot. I started with my SATA, than my secondary IDE drive and finally my primary IDE drive, which had the Windows partition on it. Windows is now gone, and I plan to put it back on once I get my SATA drive to boot properly. The machine now boots off the primary drive and grub will not boot the sda2 partition giving me an error. opps, I've just noticed that you've requested the contents of the device.map file, which I don't have here. I'll try to get that posted tonight.

-thanks

Last edited by tuffstuff; 03-05-2007 at 02:52 PM.
 
Old 03-05-2007, 04:18 PM   #6
pljvaldez
Guru
 
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Squeeze (x86)
Posts: 6,092

Rep: Reputation: 269Reputation: 269Reputation: 269
Looking at your menu.lst, it looks like you stuck with Sarge during your reinstall. I would recommend getting the Etch netinstall CD and trying it. I'm guessing your SATA controller is just too new for the 2.6.8 kernel in Sarge because everything looks correct to me...
 
Old 03-14-2007, 02:30 PM   #7
tuffstuff
LQ Newbie
 
Registered: Feb 2007
Distribution: Debian Etch
Posts: 29

Original Poster
Rep: Reputation: 15
Thumbs up

So, I've been wrestling with installing a working GRUB on any of my other disk drives other that my primary for weeks now, and I finally solved the problem. I diconnected both of my IDE drives and left my SATA drive connected, reinstalled Debian, my OS of choice!, and let the Debian installer do the GRUB work for me. With only one drive connected it installed GRUB on just that drive and not the primary IDE as before. I still do not know why I had so much trouble booting my SATA from my primary IDE MBR but I suppose it's water under the bride at this point. Thanks for all the help!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
SUCCESS STORY: "Error loading Operating System" at end of BIOS bootup ToBe LinuxQuestions.org Member Success Stories 13 11-27-2013 03:04 AM
"Error loading operating system" upon first reboot after install Unforgiver Linux - Newbie 4 01-03-2012 04:42 AM
"error loading operating system" gregmcavity Linux - Newbie 4 12-14-2006 09:05 PM
"Error loading operating system" in WinXP dual boot saskee Ubuntu 1 02-03-2006 03:24 PM
What is the source of "Error Loading Operating System"? fiservguy Fedora 1 02-18-2005 11:11 AM


All times are GMT -5. The time now is 06:58 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration