Baslinux mailing list

[baslinux AT lists.ibiblio.org]

Hi Sheldon,

I'm not sure how much i can help with the problems
you're having, but i can offer some info about GRUB:


--- On Sun, 9/7/08, baslinux AT lists.ibiblio.org <baslinux AT lists.ibiblio.org> 
wrote:

> From: baslinux AT lists.ibiblio.org <baslinux AT lists.ibiblio.org>
> Subject: Re: [BL] Promise UDMA controller not working with BL
> To: baslinux AT lists.ibiblio.org
> Date: Sunday, September 7, 2008, 7:37 AM

> > I downloaded it to C:\baslin\
> 
> I have no idea how grub works.  Can you try booting with
> loadlin?

If you have the DOS version of BL installed into a
C:\baslin\ directory, you should definitely be booting
it with loadlin ... but you have to boot into DOS first.
There should be  file called C:\baslin\bl.bat, and if
you boot into DOS then type "bl" it will boot BL.


I'm not quite sure how GRUB is working on your setup.
But here's a quick tutorial on how GRUB refers to drives
and partitions:
 
> > GRUB is installed to the MBR of an HD connected to
> > an IDE on the Promise controller.
> > (no HDs are connected to the IDEs on the motherboard,
> > but two CD-ROMs are)
> >
> > C:\boot\grub\menu.lst reads, in part:
> >
> > ----------------
> >
> > default 0
> > timeout 5
> >
> > title Windows
> > rootnoverify (hd0,0)
> > chainloader +1
> > makeactive
> > boot
> >
> > title DSL4x
> > root (hd0,0)
> > kernel /boot/linux24 quiet root=/dev/hde1
> fromhd=/dev/hde1 vga=normal
> > norestore dma frugal write
> > initrd /boot/minirt24.gz
> 
> I see you have DSL - if you boot to that you can make
> devices on the BL3 
> partition.
> 
> > title BL 3.5
> > root (hd0,0)
> > kernel /baslin/bzimavsp.431 root=/dev/hda7 rw
> 
> hda7 is a partition on the primary master (onboard
> controller, not Promise 
> card).  If your drive is plugged into the first Promise
> controller it is 
> hde.  You need to make devices hde, hde1 (etc. if you have
> more than one 
> partition) mknod /dev/hde b 33 0 mknod /dev/hde1 b 33 1
> etc.  You can do 
> this by plugging in the drive as hda and booting linux and
> adding those 
> devices or using DSL which I see in grub.


Sindi is right about the hde business. If your hard-drive
is the primary master on the motherboard, it's "hda" to
Linux. GRUB refers to this as "(hd0)".

The first partition of the primary master hard-drive
is "hda1" in Linux, and "(hd0,0)" in GRUB. Your GRUB
startup file /boot/grub/menu.lst is looking for that
to boot from.

So if you have to refer to your Promise-controller drive
as "hde" in Linux, then it's "(hd4)" in GRUB. If you
have to call the boot partition "hde1" in Linux, then
it needs to be "(hd4,0)" for GRUB.

Here is the correspondence:

physical drive:
Linux .. GRUB
a ...... 0
b ...... 1
c ...... 2
d ...... 3
e ...... 4
etc.

partition:
Linux .. GRUB
1 ...... 0
2 ...... 1
3 ...... 2
4 ...... 3
5 ...... 4
etc.


(BTW, i'm originally from Philly too!)


-monz