Re: [gentoo-user] grub hell

2007-11-16 Thread Jonathan R. Haws
Why not go Seamless with a VM?  That works great for me.   That way you 
can forget about the dual boot.  Just set the VM to run on startup and 
you can access any Windows program from within Gentoo.  Works great, 
speed is just as fast as when booting to XP.


http://ubuntuforums.org/showthread.php?t=433359highlight=seamless

Yes the how to is for ubuntu, but its the same across all platforms.  
The only difference really is setting up the bridge.  If you do it, make 
sure you set permissions correctly on the folder containing the 
seamlessshell.exe program (i gave everyone full control).


-jrh

maxim wexler wrote:

http://supergrub.forjamari.linex.org/

I use this cd image and it works like a treat. 




Not for me. Same problem: grub can get the HDs
straight. I quit. 


Not a great biggee; I only use XP for one proprietary
program that has yet to be linux-fied. I'll just tell
the BIOS to boot from that drive whenever I have to
use it again, which is rarely.

Outtahere,

-mw


  

Be a better pen pal. 
Text or chat with friends inside Yahoo! Mail. See how.  http://overview.mail.yahoo.com/
  


--
Jonathan R. Haws
Student Engineer
Space Dynamics Laboratory

[EMAIL PROTECTED]
(435)797-4629

--
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-16 Thread maxim wexler

--- Jonathan R. Haws [EMAIL PROTECTED]
wrote:

 Why not go Seamless with a VM?  That works great for
 me.   That way you 
 can forget about the dual boot.  Just set the VM to
 run on startup and 
 you can access any Windows program from within
 Gentoo.  Works great, 
 speed is just as fast as when booting to XP.
 

http://ubuntuforums.org/showthread.php?t=433359highlight=seamless
 

Sweet! Unfortunately the linux-side of the PC in
question is X-less. Installing X and virtualbox with
my 2.8 k/s phone line will take too long. 

Will it work in a frame buffer?

-mw


  

Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-16 Thread Billy Holmes
Jonathan R. Haws wrote:
 Why not go Seamless with a VM?  That works great for me.   That way
 you can forget about the dual boot.  Just set the VM to run on startup
 and you can access any Windows program from within Gentoo.  Works
 great, speed is just as fast as when booting to XP.

that has to be just about the best link I've come across in a long time.
thanks.
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-15 Thread maxim wexler
 http://supergrub.forjamari.linex.org/
 
 I use this cd image and it works like a treat. 
 

Not for me. Same problem: grub can get the HDs
straight. I quit. 

Not a great biggee; I only use XP for one proprietary
program that has yet to be linux-fied. I'll just tell
the BIOS to boot from that drive whenever I have to
use it again, which is rarely.

Outtahere,

-mw


  

Be a better pen pal. 
Text or chat with friends inside Yahoo! Mail. See how.  
http://overview.mail.yahoo.com/
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-14 Thread Mick
On Wednesday 14 November 2007, maxim wexler wrote:

 Thanks for the suggestions, I tried them all, but none
 of them worked.

 Every attempt at tab completion results in:

 Possible disks are: fd0 fd1 fd2 fd3 fd4 fd5 fd6 fd7
 hd0

 hd1 just doesn't appear(don't know what all those
 floppies is about). Any attempt to use it, whether by
 tab completion or by just entering it at the prompt,
 results in Error 21: Selected disk does not exist.

Well, you could take turns trying out all these fds.

 I know the drive is OK cause it boots when the boot
 order in the BIOS starts with the first drive.

Grub *should* be able to see what BIOS sees, but clearly this is not the case 
here.  Have you tried reinstalling Grub in the MBR?

 I think I'll try that old hack where you dd the boot
 sector to a floppy and copy it to C:\ in Windows. Then
 you write a .bat file? Details kinda hazy...

You'll need to reinstall grub for this solution to work, but install it in 
your Gentoo /boot partition, not the MBR.  (I have not tried it with the MBR 
image, but you could try that too - pls let me know if it works).  Then you 
dd this and copy it into your WinXP partition so that you can chainload it 
from NTLDR.  Finally, you'll have to edit the boot.ini file to point it to 
the boot image you just copied in your WinXP partition and you should be able 
to boot it . . . as long as NTLDR can see the drive in question.  :p  Well, 
it's worth giving it a shot I guess.

Good luck.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] grub hell

2007-11-14 Thread Hans-Werner Hilse
Hi,

On Wed, 14 Nov 2007 08:25:50 +
Mick [EMAIL PROTECTED] wrote:

  I know the drive is OK cause it boots when the boot
  order in the BIOS starts with the first drive.
 
 Grub *should* be able to see what BIOS sees, but clearly this is not the case 
 here.  Have you tried reinstalling Grub in the MBR?

That most likely won't help since what's installed there only stages
the real grub binaries which will be most likely the same ones.

From what maxim wrote so far it really looks like the BIOS moves the
entry for the HD on the first controller out of sight somehow. So
probably the BIOS feature of booting off the second controller is the
problem here. We can't solve this on the level of grub or the OS, so
the only option seems to be to properly install grub to the first HD.

I would start with a grub floppy disk or boot CD(-RW) and look what
devices that sees when booting. In order to have grub list disks, you
enter root ( and press TAB. The same goes for partitions after the
setting device and a comma (e.g. (hd0, + TAB).

If all devices are seen, then set root (as indicated above) to the
partition holding the grub stages (i.e. partition of /boot in Gentoo
or /lib/grub/i386-pc/). Then have grub write the MBR using 
setup (hd0). Note that this will overwrite the Windows MBR, which
will make it unbootable at that point. So better before doing that --
from Linux -- backup the MBR: 
dd if=/dev/hda of=/backup-mbr-hda bs=512 count=1 so you can write it
back later.

-hwh
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-14 Thread Mick
On Wednesday 14 November 2007, Hans-Werner Hilse wrote:
 Hi,

 On Wed, 14 Nov 2007 08:25:50 +

 Mick [EMAIL PROTECTED] wrote:
   I know the drive is OK cause it boots when the boot
   order in the BIOS starts with the first drive.
 
  Grub *should* be able to see what BIOS sees, but clearly this is not the
  case here.  Have you tried reinstalling Grub in the MBR?

 That most likely won't help since what's installed there only stages
 the real grub binaries which will be most likely the same ones.

Sure, unless something is corrupted in the Grub stages files?  I wasn't sure 
on the circumstances under which the IDE controller in question was fried.

 From what maxim wrote so far it really looks like the BIOS moves the
 entry for the HD on the first controller out of sight somehow. 

Are BIOS' that 'intelligent' these days?

 So 
 probably the BIOS feature of booting off the second controller is the
 problem here. We can't solve this on the level of grub or the OS, so
 the only option seems to be to properly install grub to the first HD.

/The only time that I have experience a similar problem was after a drive 
ribbon was hot unplugged mid-flight.  The controller was not fried, not was 
the drive, but it took sometime to get it going again.  Ultimately an 
investigation revealed that the jumpers at the back of the drives were not 
effective (cable select would just not work)./

 I would start with a grub floppy disk or boot CD(-RW) and look what
 devices that sees when booting. In order to have grub list disks, you
 enter root ( and press TAB. The same goes for partitions after the
 setting device and a comma (e.g. (hd0, + TAB).

 If all devices are seen, then set root (as indicated above) to the
 partition holding the grub stages (i.e. partition of /boot in Gentoo
 or /lib/grub/i386-pc/). Then have grub write the MBR using
 setup (hd0). Note that this will overwrite the Windows MBR, which
 will make it unbootable at that point. So better before doing that --
 from Linux -- backup the MBR:
 dd if=/dev/hda of=/backup-mbr-hda bs=512 count=1 so you can write it
 back later.

Alternatively, use a MS Windows installation CD, boot into Recovery Console 
and run fixmbr on the correct drive.  It will reinstall the NTLDR boot code 
in the MBR and you'll be able to natively boot it again.  If you mess up the 
MS Windows *partition* boot record because instead of hd0 you typed hd0,1 
then the command you want is fixboot.  I just hate reinstalling MS Windows - 
it feels sort of wasted time!  ;-)

HTH.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] grub hell

2007-11-14 Thread maxim wexler

 the only option seems to be to properly install grub
 to the first HD.

grub-install /dev/hda renders the PC completely
unusable

 
 I would start with a grub floppy disk or boot
 CD(-RW) and look what

Both drives are bootable provided I make a detour to
the BIOS and change the boot order.


 devices that sees when booting. In order to have
 grub list disks, you

dmesg reports ALL drives and appropriate partitions.

 enter root ( and press TAB. The same goes for
 partitions after the
 setting device and a comma (e.g. (hd0, + TAB).
 

Now this is really wierd. When I'm at the prompt using
the grub that appears when the PC boots, ie when the
second drive is given preference in BIOS, tab
completion reports only a string of fdn's followed by
hd0. But, when having booted and logged in, I issue
the grub command, tab completion reports possible
disks as hd0 and hd1 as it should. And it correctly
sees the unknown partition on /dev/hda and the four
linux partitions on /dev/hdc. But that's with
device.map like so: (fd0)  /dev/fd0
(hd0)  /dev/hda
(hd2)  /dev/hdc
   ^!?!?

 If all devices are seen, then set root (as indicated
 above) to the
 partition holding the grub stages (i.e. partition of
 /boot in Gentoo
 or /lib/grub/i386-pc/). Then have grub write the MBR
 using 
 setup (hd0). Note that this will overwrite the
 Windows MBR, which
 will make it unbootable at that point. So better

OK, this throws me. Isn't it supposed to be bootable?
As I said above installing grub to Win-mbr renders the
PC unusable. Can't recall the precise error message
but 
even the grub prompt isn't available.

 before doing that --
 from Linux -- backup the MBR: 
 dd if=/dev/hda of=/backup-mbr-hda bs=512 count=1
 so you can write it
 back later.

Thanks for the tip, a lot simpler than booting into
Win98 and running A:\fdisk /mbr.

There's more...

I followed the instructions here: 

http://gentoo-wiki.com/HOWTO_Dual_Boot_from_Windows_Bootloader_(NTLDR)_and_why

And, provided I'm booting from /dev/hda, I'm presented
with two choices, Gentoo and XP. XP boots OK but
gentoo halts at:

GRUB Loading stage1.5

GRUB loading, please wait...
Error 21

even though the boot routine is identical to the one
that WORKS when the second drive is given boot
preference.

-mw


  

Be a better sports nut!  Let your teams follow you 
with Yahoo Mobile. Try it now.  
http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-14 Thread Hans-Werner Hilse
Hi,

On Wed, 14 Nov 2007 13:27:49 -0800 (PST)
maxim wexler [EMAIL PROTECTED] wrote:

  the only option seems to be to properly install grub
  to the first HD.
 
 grub-install /dev/hda renders the PC completely
 unusable

Hm, yeah, that's why I generally distrust running grub from within an
booted OS: You can't be sure that the setting is anywhere near what
happens before the OS got loaded (e.g. no ACPI kicking in yet, BIOS
disk drivers...).

  I would start with a grub floppy disk or boot
  CD(-RW) and look what
 
 Both drives are bootable provided I make a detour to
 the BIOS and change the boot order.

Somehow I suspect that the BIOS gets something wrong when you change
the boot order. But that's just a suspicion. So my suggestion was to
change it to default (first HD first). Then check from a grub running
from floppy or CDRW what that can see. So you can try if my suspicion
is wrong, what might well be the case: That grub (from floppy or CD)
will only see one drive, too, if I'm wrong. Otherwise you know that I
was probably right and your only option then is to leave the BIOS boot
order untouched.

  devices that sees when booting. In order to have
  grub list disks, you
 
 dmesg reports ALL drives and appropriate partitions.

But that is what _Linux_ sees. Linux has its own drivers, working
completely independent from what the BIOS was doing before -- and
that's what a grub (at boot stage) has to rely on. So Linux' output
only tells us that generally:
- your drives are OK, the cabling too.
- your controllers are working.

But we need to make sure the BIOS initializes everything right. It
might not do so if boot order is changed (and from a certain point of
view, that might actually be a feature).

  enter root ( and press TAB. The same goes for
  partitions after the
  setting device and a comma (e.g. (hd0, + TAB).
 
 Now this is really wierd. When I'm at the prompt using
 the grub that appears when the PC boots, ie when the
 second drive is given preference in BIOS, tab
 completion reports only a string of fdn's followed by
 hd0. But, when having booted and logged in, I issue
 the grub command, tab completion reports possible
 disks as hd0 and hd1 as it should. And it correctly
 sees the unknown partition on /dev/hda and the four
 linux partitions on /dev/hdc. But that's with
 device.map like so: (fd0)  /dev/fd0
 (hd0)  /dev/hda
 (hd2)  /dev/hdc
^!?!?

It might be that the second HD is just (hd1). Grub doesn't necessarily
follow the kernel way of enumeration. But then again, don't rely on
what grub tells when run with an loaded OS.

  If all devices are seen, then set root (as indicated
  above) to the
  partition holding the grub stages (i.e. partition of
  /boot in Gentoo
  or /lib/grub/i386-pc/). Then have grub write the MBR
  using 
  setup (hd0). Note that this will overwrite the
  Windows MBR, which
  will make it unbootable at that point. So better
 
 OK, this throws me. Isn't it supposed to be bootable?

Oh, the Windows MBR is just giving control to the boot block of the
partition holding Windows, which itself then stages ntldr. So when I
said it'll make it unbootable, I was talking about the Windows MBR.
Grub should run anyway nevertheless, and then it should be able to give
control to the Windows partition boot block -- but I was just giving a
warning that what definately happens is that the Windows MBR is gone.

 There's more...
 
 I followed the instructions here: 
 
 http://gentoo-wiki.com/HOWTO_Dual_Boot_from_Windows_Bootloader_(NTLDR)_and_why
 
 And, provided I'm booting from /dev/hda, I'm presented
 with two choices, Gentoo and XP. XP boots OK but
 gentoo halts at:
 
 GRUB Loading stage1.5
 
 GRUB loading, please wait...
 Error 21
 
 even though the boot routine is identical to the one
 that WORKS when the second drive is given boot
 preference.

Personally, I don't see much difference, this approach shares similar
problems. Apropos problem, error 21 is Selected disk does not exist.
I think it might have happened because you probably switched drive
order again when doing the Linux based steps descibed in the link
you've give. When the MBR is written, it stores references to the stage
files. They might point to an invalid location if you change the boot
order back again. That's what I think why you're seeing this error.

Grub can perfectly from a floppy disk. See info grub (the full grub
documentation, the man page is crap) in order to learn how to create a
grub floppy disk (or CD/R(W)). You will then be able to set the BIOS
boot order to default and see what a freshly booted grub sees then.
From within the grub booted this way, you can order grub to setup
itself to an MBR or boot block. Basically, you have to set root, then
issue setup. The first takes the device of the stage files as
argument, the latter the target disk (or partition).

After being through this grub hell, at least will have learnt a lot
about broken BIOSes and different boot stages of today's PC 

Re: [gentoo-user] grub hell

2007-11-14 Thread maxim wexler
 Grub can perfectly from a floppy disk. See info
 grub (the full grub
 documentation, the man page is crap) in order to
 learn how to create a
 grub floppy disk (or CD/R(W)). You will then be able
 to set the BIOS
 boot order to default and see what a freshly booted

Arrgh! Now I learn this box won't boot from a floppy!

It bipasses the floppy completely unless I disable ALL
the drives except the floppy and then I get:

Invalid boot diskette: insert BOOT disk in A:\

Huh? Maybe it's because this is a Dell PIII and
requires a proprietary DOS boot disk. 

There seems to be two methods from what I can find on
the Web: copying menu.lst to /mnt/floppy/boot/grub and
copying /boot/grub/stage1 and /boot/grub/stage2 to a
floppy I tried them both without success.

Of course I can still boot the gentoo-install CD but
then I have to chroot to run grub which puts me back
in the hole. 

Now, I don't have a burner on the PIII, but I have one
on another box. Can someone suggest a method to burn a
grub-boot CD that won't leave me with a coaster -- got
plenty of those :(

-mw


  

Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-14 Thread W.Kenworthy
I came to this late and missed most of the thread so apologies if this
has been covered.

Did you mount /proc into /mnt/gentoo before chroot'ing? (see install
docs) This allows grub to correctly sense the drive map for writing
the boot sectors.

Some early MB's changed the drive map depending on what disk/media
(i.e., cdrom) you booted from so grub wrote a correct map at the time,
then the MB changed the mapping on the HD boot.  Fix was to
intelligently guess the correct drive and write it manually using grub.
A later bios update allowed some control at the bios level which made it
easier.

Billk


On Wed, 2007-11-14 at 18:36 -0800, maxim wexler wrote:
  Grub can perfectly from a floppy disk. See info
  grub (the full grub
  documentation, the man page is crap) in order to
  learn how to create a
  grub floppy disk (or CD/R(W)). You will then be able
  to set the BIOS
  boot order to default and see what a freshly booted
 
 Arrgh! Now I learn this box won't boot from a floppy!
 
 It bipasses the floppy completely unless I disable ALL
 the drives except the floppy and then I get:
 
 Invalid boot diskette: insert BOOT disk in A:\
 
 Huh? Maybe it's because this is a Dell PIII and
 requires a proprietary DOS boot disk. 
 
 There seems to be two methods from what I can find on
 the Web: copying menu.lst to /mnt/floppy/boot/grub and
 copying /boot/grub/stage1 and /boot/grub/stage2 to a
 floppy I tried them both without success.
 
 Of course I can still boot the gentoo-install CD but
 then I have to chroot to run grub which puts me back
 in the hole. 
 
 Now, I don't have a burner on the PIII, but I have one
 on another box. Can someone suggest a method to burn a
 grub-boot CD that won't leave me with a coaster -- got
 plenty of those :(
 
 -mw
 
 
   
 
 Get easy, one-click access to your favorites. 
 Make Yahoo! your homepage.
 http://www.yahoo.com/r/hs 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-14 Thread Novensiles divi Flamen


 Now, I don't have a burner on the PIII, but I have one
 on another box. Can someone suggest a method to burn a
 grub-boot CD that won't leave me with a coaster -- got
 plenty of those :(

 -mw

http://supergrub.forjamari.linex.org/

I use this cd image and it works like a treat. 

- Noven
-- 
-- Novensiles divi Flamen --
 Miles Militis Fons 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-13 Thread Sarpy Sam

   Get easy, one-click access to your favorites.
   Make Yahoo! your homepage.
   http://www.yahoo.com/r/hs
 
 
  do you have a space in between (hd1) and (hd0) in
  map (hd1) (hd0)
?

 space or no space makes no difference.

 The thing is, tab completion finds only hd0 which grub
 doesn't seem to realize is the SECOND drive. Using hd1
 gives error 21: Selected disk does not exist. Although
 it appears in device.map, dmesg, fdisk etc.

 Maybe it's a bug in grub.Gonna send a note to
 [EMAIL PROTECTED] see what happens.


I had something similar happen like this on a box I just recently
built.  I had two hard disks but the system could only see one.  It
turned out I had the jumpers on the hard drive set for cable select
and was using the proper cable but it was not reading right.  Once I
set the hard drives jumpers in a master/slave configuration the
computer could see both hard drives and everything worked fine.  Have
you messed with this stuff at all?  Trying different disc plugged in
using different cables into different points.  I don't know if it will
make a difference but if grub isn't seeing one of the drives I would
suspect the controller.
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-13 Thread Mick
On Tuesday 13 November 2007, maxim wexler wrote:
 --- Dan Farrell [EMAIL PROTECTED] wrote:
  On Mon, 12 Nov 2007 15:27:55 -0800 (PST)
 
  maxim wexler [EMAIL PROTECTED] wrote:
rootnoverify (hd1,0)
map (hd1)(hd0)
  
   Error 11: Unrecognized device string
  
   Press any key to continue...

 ___
_

   Get easy, one-click access to your favorites.
   Make Yahoo! your homepage.
   http://www.yahoo.com/r/hs
 
  do you have a space in between (hd1) and (hd0) in
  map (hd1) (hd0)
  ?

 space or no space makes no difference.

 The thing is, tab completion finds only hd0 which grub
 doesn't seem to realize is the SECOND drive. Using hd1
 gives error 21: Selected disk does not exist. Although
 it appears in device.map, dmesg, fdisk etc.

 Maybe it's a bug in grub.Gonna send a note to
 [EMAIL PROTECTED] see what happens.

I am not sure if you have tried this or not, but when you map one drive to 
another {say: map (hd0) (hd1)}, you also need to map the second drive to the 
first, instead of leaving it hanging.  So, the complete entry becomes:

map (hd0) (hd1)
map (hd1) (hd0)

If this doesn't work you may want to try the hide command.  Hide all the other 
bootable partitions but the one you intend to boot:

unhide (hd1,0)
hide (hd1,0)
rootnoverify (hd1,0)
map (hd0) (hd1)  --These two may or may not be
map (hd1) (hd0)  --needed with un/hide command
makeactive
chainloader +1

It is also a good idea to only have the bootable flag set with fdisk on the 
WinXP partition (Linux /boot doesn't need it anyway).

Finally, you could also try changing the device map from  (hd1) /dev/hdc to 
(hd2) /dev/hdc.

HTH.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] grub hell

2007-11-13 Thread maxim wexler
 I am not sure if you have tried this or not, but
 when you map one drive to 
 another {say: map (hd0) (hd1)}, you also need to map
 the second drive to the 
 first, instead of leaving it hanging.  So, the
 complete entry becomes:
 
 map (hd0) (hd1)
 map (hd1) (hd0)
 
 If this doesn't work you may want to try the hide
 command.  Hide all the other 
 bootable partitions but the one you intend to boot:
 
 unhide (hd1,0)
 hide (hd1,0)
 rootnoverify (hd1,0)
 map (hd0) (hd1)  --These two may or may not be
 map (hd1) (hd0)  --needed with un/hide command
 makeactive
 chainloader +1
 
 It is also a good idea to only have the bootable
 flag set with fdisk on the 
 WinXP partition (Linux /boot doesn't need it
 anyway).
 
 Finally, you could also try changing the device map
 from  (hd1) /dev/hdc to 
 (hd2) /dev/hdc.
 
 HTH.
 -- 
 Regards,
 Mick
 
Thanks for the suggestions, I tried them all, but none
of them worked.

Every attempt at tab completion results in:

Possible disks are: fd0 fd1 fd2 fd3 fd4 fd5 fd6 fd7
hd0

hd1 just doesn't appear(don't know what all those
floppies is about). Any attempt to use it, whether by
tab completion or by just entering it at the prompt,
results in Error 21: Selected disk does not exist.

I know the drive is OK cause it boots when the boot
order in the BIOS starts with the first drive.

I think I'll try that old hack where you dd the boot
sector to a floppy and copy it to C:\ in Windows. Then
you write a .bat file? Details kinda hazy...

-mw


  

Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread Mick
On Sunday 11 November 2007, maxim wexler wrote:
 Hi group,

 Previously I had a problem with hard drive that turned
 out was a faulty IDE controller, not the drive, not
 the cable.

 Now I can't use /dev/hdb but /dev/hdc is OK. So my set
 up is /dev/hda(WinXP) and /dev/hdc(gentoo), ie, WinXP
 is on the first IDE as master and gentoo is on the sec
 IDE also as master. hdd is the CDROM(sec IDE,slave),
 to complete the setup.

 So far I've tried every possible permutation of root,
 rootnoverify and map. I've tried installing the boot
 loader on /dev/hda and /dev/hdc. On hda nothing
 works(error 21). On hdc the boot menu appears and I
 can boot gentoo but not WinXP

 Error messages: selected disk does not exist, not
 found or not a block device, could not find device
 for boot. Sorry, I can't recall the exact context for
 these messages but this will give a flavor hopefully.

 I've tried changing the boot order in the BIOS.

 I can get gentoo to boot if I tell grub it's on
 (hd0,0)(?!?!) but WinXP won't boot unless I remove the
 HD w/gentoo on it and bypass grub altogether.

My guess is that you have incompatible jumper settings on the back of the 
drives.  Check these and make sure that they reflect what the BIOS sees.  
Also, check your /boot/grub/device.map for consistency.  Then use tab 
completion from the grub prompt to find devices and bootable partitions.

 fdisk can see both drives OK. Both drives appear in
 dmesg w/o errors. Both drives appear in the POST
 screen -- first drive as '0', second drive as '1'

 I've scoured the web for an answer and now must turn
 to the authorities on this list as a last resort.

If the above doesn't get you booting please post your grub.conf, along with 
fdisk -l.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] grub hell

2007-11-12 Thread Eric Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

maxim wexler wrote:
 Previously I had a problem with hard drive that turned out was a
 faulty IDE controller, not the drive, not the cable.

 Now I can't use /dev/hdb but /dev/hdc is OK. So my set up is
 /dev/hda(WinXP) and /dev/hdc(gentoo), ie, WinXP is on the first IDE
 as master and gentoo is on the sec IDE also as master. hdd is the
 CDROM(sec IDE,slave), to complete the setup.

 So far I've tried every possible permutation of root, rootnoverify
 and map. I've tried installing the boot loader on /dev/hda and
 /dev/hdc. On hda nothing works(error 21). On hdc the boot menu
 appears and I can boot gentoo but not WinXP

title=Windows XP
root=(hd0)
chainloader +1

 Error messages: selected disk does not exist, not found or not a
 block device, could not find device for boot. Sorry, I can't
 recall the exact context for these messages but this will give a
 flavor hopefully.
Are you sure you're selecting the correct disk?  Don't just assume
since it's hdc in Linux it's hd2, use tab-completion when you're
setting up grub.,  Have you tried using grub console
w/tab-completion?  Hit 'c' when you're booted to grub, and try

grub root (hd{hit tab to see what's there}
It's all the same syntax as grub.conf

 I've tried changing the boot order in the BIOS.

 I can get gentoo to boot if I tell grub it's on (hd0,0)(?!?!) but
 WinXP won't boot unless I remove the HD w/gentoo on it and bypass
 grub altogether.
Where is grub installed currently?  The easiest way I've gotten it to
work is to install over Window's MBR and use a chainloader +1 line to
chainload windows.


Lastly What partitions are marked as active/bootable?  I assume the xp
one is (hda), but what about hdc when you're trying to install grub
there?  Also, I don't _think_ you can have more than 1 active/bootable
disk.

 fdisk can see both drives OK. Both drives appear in dmesg w/o
 errors. Both drives appear in the POST screen -- first drive as
 '0', second drive as '1'
Again, this leads me to believe that grub is seeing the second disk as
hd1. Granted; you never said what you called it but that might be your
problem.


 Maxim


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHOE6laiVxdKlBO58RAm7EAJwPBUa7/9XPM67xdZ86Zj2X+f6gbwCZAWpP
Q2T5BCMz8etgm3Z5hQf8Ks0=
=osf+
-END PGP SIGNATURE-

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread maxim wexler

 My guess is that you have incompatible jumper
 settings on the back of the 
 drives.  Check these and make sure that they reflect
 what the BIOS sees.  
 Also, check your /boot/grub/device.map for
 consistency.  Then use tab 
 completion from the grub prompt to find devices and
 bootable partitions.

Both drives are set to master which the BIOS confirms.

Device map:

(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/hdc

is consistent.

Tab completion at the grub prompt only finds the
second drive which it insists on calling the first
contrary to device.map.

 If the above doesn't get you booting please post
 your grub.conf, along with 
 fdisk -l.

grub.conf:

#XP
title=XP
rootnoverify (hd0,0)
map (hd1)(hd0) 
makeactive 
chainloader +1
boot

(I used one 'map' command following Dan Farrell's
model but using two made no difference)

#Gentoo
title=Gentoo
root (hd0,0) 
kernel /vmlinuz root=/dev/hdc3
video=aty128fb:[EMAIL PROTECTED]
boot

Note: 

The entry for XP elicits:

Error 11 Unrecognized device string

no matter how I edit it using the 'e' command in grub.

Gentoo will not boot unless grub is told it's on the
FIRST drive contrary to device.map anything else and
grub reports disk does not exist

fdisk -l:


Disk /dev/hda: 6448 MB, 6448619520 bytes
255 heads, 63 sectors/track, 784 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id
 System
/dev/hda1   1 783 62894167
 HPFS/NTFS

Disk /dev/hdc: 122.9 GB, 122942324736 bytes
176 heads, 63 sectors/track, 21656 cylinders
Units = cylinders of 11088 * 512 = 5677056 bytes

   Device Boot  Start End  Blocks   Id
 System
/dev/hdc1   *   1   7   38776+  83
 Linux
/dev/hdc2   8  96  493416   82
 Linux swap / Solaris
/dev/hdc3  97   1066658600080   83
 Linux
/dev/hdc4   10667   2165660928560   83
 Linux

I've tried toggling the bootable flag on /dev/hda.
Didn't work.

As I mentioned before attempts to install grub to
/dev/hda fail completely forcing a reboot w/Win98 and
entering A:\fdisk /mbr after which XP boots but only
if the second drive is disabled. Installing to
/dev/hdc at least lets me boot gentoo.

Both drives pass smartctl tests.

grub is version 0.97

Don't know what else to add.

-mw

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread Dan Farrell
On Mon, 12 Nov 2007 09:52:49 -0800 (PST)
maxim wexler [EMAIL PROTECTED] wrote:

 grub.conf:
 
 #XP
 title=XP
 rootnoverify (hd0,0)
 map (hd1)(hd0) 
 makeactive 
 chainloader +1
 boot
 
 (I used one 'map' command following Dan Farrell's
 model but using two made no difference)

notice in my XP section I do
rootnoverify (hd1,0)
map (hd1) (hd0)

so the root is on the second hard drive in grub, but windows doesn't
know about the SATA controller and so must be 'tricked' into thinking
its on the first hard drive.  

In your grub.conf, you say the root is on (hd0,0) but then remap (hd1)
as (hd0).  Whereas the root partition for windows boot in my case is
the first hard drive listed after 'map', yours is the second  I suggest
you reverse this.  
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread maxim wexler

 In your grub.conf, you say the root is on (hd0,0)
 but then remap (hd1)
 as (hd0).  Whereas the root partition for windows
 boot in my case is
 the first hard drive listed after 'map', yours is
 the second  I suggest
 you reverse this.  

As I stated before, I've tried all the possibilities.

None of them work. In this case the error is #11:

Unrecognized device string.

BTW these are IDE drives, not SATA.

-mw













__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread Dan Farrell
On Mon, 12 Nov 2007 13:25:43 -0800 (PST)
maxim wexler [EMAIL PROTECTED] wrote:

  I've tried all the possibilities.

Except the working one.  Don't give up!

I don't mean to discount your reply but I am worried I expressed myself
poorly.  I think your configuration should look like:

rootnoverify (hd1,0)
map (hd1)(hd0)

Here, I'm telling GRUB that i want it to boot from the first
partitionon the second drive, but then act as if it's the first drive
for Windows (after grub boots).
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread maxim wexler
 
 rootnoverify (hd1,0)
 map (hd1)(hd0)

Error 11: Unrecognized device string

Press any key to continue...




  

Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs 
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread Dan Farrell
On Mon, 12 Nov 2007 15:27:55 -0800 (PST)
maxim wexler [EMAIL PROTECTED] wrote:

  
  rootnoverify (hd1,0)
  map (hd1)(hd0)
 
 Error 11: Unrecognized device string
 
 Press any key to continue...
 
 
 
 
   
 
 Get easy, one-click access to your favorites. 
 Make Yahoo! your homepage.
 http://www.yahoo.com/r/hs 


do you have a space in between (hd1) and (hd0) in
map (hd1) (hd0)
?
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-12 Thread maxim wexler

--- Dan Farrell [EMAIL PROTECTED] wrote:

 On Mon, 12 Nov 2007 15:27:55 -0800 (PST)
 maxim wexler [EMAIL PROTECTED] wrote:
 
   
   rootnoverify (hd1,0)
   map (hd1)(hd0)
  
  Error 11: Unrecognized device string
  
  Press any key to continue...
  
  
  
  
   


  Get easy, one-click access to your favorites. 
  Make Yahoo! your homepage.
  http://www.yahoo.com/r/hs 
 
 
 do you have a space in between (hd1) and (hd0) in
 map (hd1) (hd0)
   ?

space or no space makes no difference.

The thing is, tab completion finds only hd0 which grub
doesn't seem to realize is the SECOND drive. Using hd1
gives error 21: Selected disk does not exist. Although
it appears in device.map, dmesg, fdisk etc.

Maybe it's a bug in grub.Gonna send a note to
[EMAIL PROTECTED] see what happens.






  

Be a better sports nut!  Let your teams follow you 
with Yahoo Mobile. Try it now.  
http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] grub hell

2007-11-11 Thread Dan Farrell
On Sun, 11 Nov 2007 14:01:24 -0800 (PST)
maxim wexler [EMAIL PROTECTED] wrote:

 Hi group,
 
 Previously I had a problem with hard drive that turned
 out was a faulty IDE controller, not the drive, not
 the cable. 
 
 Now I can't use /dev/hdb but /dev/hdc is OK. So my set
 up is /dev/hda(WinXP) and /dev/hdc(gentoo), ie, WinXP
 is on the first IDE as master and gentoo is on the sec
 IDE also as master. hdd is the CDROM(sec IDE,slave),
 to complete the setup.
 
 So far I've tried every possible permutation of root,
 rootnoverify and map. I've tried installing the boot
 loader on /dev/hda and /dev/hdc. On hda nothing
 works(error 21). On hdc the boot menu appears and I
 can boot gentoo but not WinXP
 
 Error messages: selected disk does not exist, not
 found or not a block device, could not find device
 for boot. Sorry, I can't recall the exact context for
 these messages but this will give a flavor hopefully.
 
 I've tried changing the boot order in the BIOS.
 
 I can get gentoo to boot if I tell grub it's on
 (hd0,0)(?!?!) but WinXP won't boot unless I remove the
 HD w/gentoo on it and bypass grub altogether.
 
 fdisk can see both drives OK. Both drives appear in
 dmesg w/o errors. Both drives appear in the POST
 screen -- first drive as '0', second drive as '1'
 
 I've scoured the web for an answer and now must turn
 to the authorities on this list as a last resort.
 
 Maxim
 
 __
 Do You Yahoo!?
 Tired of spam?  Yahoo! Mail has the best spam protection around 
 http://mail.yahoo.com 


notice how I use the grub 'map' command here to make the windows hard
drive 'first' for Windows's sake.  

Here, the boot priority has probably been set in the kernel.  

http://spore.ath.cx/~dan/config/grub.conf.pascal

-- 
[EMAIL PROTECTED] mailing list