[SOLVED] antiX 13.1 and Blag 140k in dual boot

taigarden · posted: 2013-09-17 14:40

I am trying to have antiX 13.1 i386 and Blag 140k i686 in dual boot. AntiX is in sda, with grub installed in same disk, and it is working fine. Blag was installed in the second physical hard drive sdb, with its grub in it. Blag is a Fedora derivative, so I think it uses grub2. When I finished Blag installation, and did the first reboot, I had just the usual antiX boot entries. I did update-grub in antiX but grub legacy did not discover Blag. So, I will need to add manually a boot stanza for Blag in the menu.lst file of antiX.
Can someone provide me with a typical boot stanza in the format of grub legacy in order to obtain an entry to boot Blag 140k? Thank you.

rokytnji · posted: 2013-09-17 14:57

Hand edit AntiX /boot/grub/menu.lst to chainload Blag. This can be done through antixcc.

A example of a grub 2 entry on my shop computer with dual drives and grub 2 but what yours should look like

Code: Select all

title Blag
rootnoverify (hd1,0)
chainloader +1

Blag is installed in /dev/sda1 on hard drive number number 2, hence the hd1,0.

taigarden · posted: 2013-09-17 15:43

Thank you rokytnji. I will use you suggested boot stanza and post the result.

taigarden · posted: 2013-09-18 00:09

No, It didn't work. I had"Error 13: Invalid or unsupported executable format".

I also tried:

Code: Select all

Title Blag
rootnoverify (hd1,0)
kernel /boot/grub/core.img
savedefault
boot

But the new error was that" /boot/grub/core.img" doesn't exist

And after that I also tried:

Code: Select all

Title Blag
rootnoverify (hd1,0)
configfile /boot/grub/menu.lst
savedefault
boot

And again I obtained te error that" /boot/grub/menu.lst" doesn't exist

Then, using gparted I found the following information about files in sdb:

(1) Boot partition:
Partition: /dev/sdb1/
File type:: ext4
Mount point: /media/sdb1
Options: boot

(2) The rest of the disk:
Partition: /dev/sdb2
File type: lvm2 pv
Mount point: VolGroup
Options: lvm

I have no previous experience with"lvm2 pv files".

Please advice. Thank you.

rokytnji · posted: 2013-09-18 00:19

I have no previous experience with"lvm2 pv files".

Me neither. To show my quadbooter which is what I went by

Code: Select all

timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message
title AntiX  at sda1, kernel 3.3.5-antix.1-486-smp
kernel /boot/vmlinuz-3.3.5-antix.1-486-smp root=/dev/sda1 nomce quiet nosplash nouveau.modeset=0 vga=791
initrd /boot/initrd.img-3.3.5-antix.1-486-smp
boot

title Semplice GNU/Linux, with Linux 3.2.0-3-486
rootnoverify (hd1,1)
chainloader +1

title Vector STD Gold 7 at /dev/sda2
rootnoverify (hd0,1)
chainloader +1

title Puppy Linux 529 frugal in sdb1 dir macpup529frugal
rootnoverify (hd1,0)
kernel /macpup529frugal/vmlinuz pmedia=atahd psubdir=macpup529frugal
initrd /macpup529frugal/initrd.gz

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro
# kopt_2_6=root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro nosplash quiet

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(single-user) single
# altoptions=(init-3) 3

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title      Debian GNU/Linux, kernel 3.5.2-antix.1-486-smp
root      (hd0,0)
kernel      /boot/vmlinuz-3.5.2-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro
initrd      /boot/initrd.img-3.5.2-antix.1-486-smp

title      Debian GNU/Linux, kernel 3.5.2-antix.1-486-smp (init-3)
root      (hd0,0)
kernel      /boot/vmlinuz-3.5.2-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro 3
initrd      /boot/initrd.img-3.5.2-antix.1-486-smp

title      Debian GNU/Linux, kernel 3.3.5-antix.1-486-smp
root      (hd0,0)
kernel      /boot/vmlinuz-3.3.5-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro
initrd      /boot/initrd.img-3.3.5-antix.1-486-smp

title      Debian GNU/Linux, kernel 3.3.5-antix.1-486-smp (init-3)
root      (hd0,0)
kernel      /boot/vmlinuz-3.3.5-antix.1-486-smp root=UUID=009157e5-dcf1-465a-ae33-6fb9cf5c3b38 ro 3
initrd      /boot/initrd.img-3.3.5-antix.1-486-smp

title      Debian GNU/Linux, kernel memtest86+
root      (hd0,0)
kernel      /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

Semplice and Vector use grub 2. Puppy bootloader installed to /home in Puppy. AntiX grub installed to mbr and controlling everybody on 2 ide hard drives.

rokytnji · posted: 2013-09-18 01:02

Hmmm. though I know nothing about Blag. 1st I would make sure os-prober is installed in Blag.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://hedayatvk.wordpress.com/2011/02/25/automatically-adding-other-distributions-to-fedora-grub-using-os-prober/"
linktext was:"http://hedayatvk.wordpress.com/2011/02/ ... os-prober/"
====================================

Then tell Blag to install grub to mbr to replace AntiX grub in mbr. Then run os-prober in Blag and cross my fingers. Then run update-grub in Blag to be double sure. Might work. Might not. Heck if I know though. I have to experiment myself and make bad decisions to gain experience to make good decisions later.

There should be a os-prober in AntiX. Lets check

Code: Select all

$ apt-cache policy os-prober
os-prober:
  Installed: 1.58
  Candidate: 1.58
  Version table:
 *** 1.58 0
        500 http://ftp.us.debian.org/debian/ wheezy/main i386 Packages
        100 /var/lib/dpkg/status

yep but I don't need it on this single boot M&A Companion Netbook I am posting from.

Code: Select all

$ inxi -Fxz
System:    Host: biker Kernel: 3.7.10-antix.3-486-smp i686 (32 bit, gcc: 4.7.3) 
           Desktop: IceWM 1.3.7 Distro: antiX-13_386-full Luddite 01 June 2013
Machine:   System: manda product: Intel powered classmate PC version: Gen 1.5L
           Mobo: N/A model: N/A Bios: American Megatrends version: CM94515A.86A.0024.2008.0715.1716 date: 07/15/2008
CPU:       Single core Intel Core CPU N270 (-HT-) cache: 512 KB flags: (nx pae sse sse2 sse3 ssse3) bmips: 3191.79 
           Clock Speeds: 1: 800.00 MHz 2: 1333.00 MHz
Graphics:  Card: Intel Mobile 945GSE Express Integrated Graphics Controller bus-ID: 00:02.0 
           X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@53.3hz 
           GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 1.4 Mesa 8.0.5 Direct Rendering: Yes
Audio:     Card: Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 
           Sound: Advanced Linux Sound Architecture ver: k3.7.10-antix.3-486-smp
Network:   Card: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller 
           driver: r8169 ver: 2.3LK-NAPI port: ec00 bus-ID: 01:00.0
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 63.3GB (39.6% used) 1: id: /dev/sda model: KingSpec_KSD size: 63.3GB 
Partition: ID: / size: 59G used: 24G (43%) fs: ext2 
Sensors:   System Temperatures: cpu: 63.0C mobo: N/A 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 98 Uptime: 52 min Memory: 259.5/2015.1MB Runlevel: 5 Gcc sys: 4.7.2 
           Client: Shell (bash 4.2.37) inxi: 1.9.14

taigarden · posted: 2013-09-18 01:53

rokytnji, thank you for your two posts. It will take some time for me to process both. Anyway, the hardware in which I have antiX 13.1 i386 and Blag 140k i686 is for experimenting and learning.
Actually I was considering to install in the second Hard Drive of my legacy hardware some of the Distros you are using, and you gave me some hints regarding compatibility with antiX for multiple boot.
I just learned today that Blag 140k is a bit dormant and a little old, so I will eventually substitute it for a newer Linux. But still, I am a little stubborn, and I will try to boot Blag in dual boot with antiX. Regards.

Dave · posted: 2013-09-18 04:08

I am not sure if this it he case, but if I a reading this right it seems that blag's grub is in the mbr of the second disk. However you are trying to run the os on the second disk really from the mbr of first. If this is the case would grub not have to be installed to the root partition of the blag install on the second disk... not the mbr of the second disk? Please correct me if I am wrong thinking this.

rokytnji · posted: 2013-09-18 04:14

I had assumed he knew to install grub to root on secondary installs Dave.

Thanks for bringing the point up. I had not even thought of that. All my secondary installs went to root. Not the mbr. Puppy is just different because it runs in root and boot/grub/menu.lst in frugal ends up in root/home. Kinda strange but I am used to it
since I am a Macpup team member also.

male · posted: 2013-09-18 09:28

If you are not familiar with lvm, then why did you install in this environment?

How is the grub of antiX appeal to the files of the grub of Blag, if they lie in an encrypted partition?

Please spending of antiX as root

Code: Select all

dpkg --list | grep grub
dpkg --list | grep os-prober
fdisk -lu
parted -l

If the Grub boot antiX the Blag, then its corresponding files must previously in an unencrypted
/boot
Partition to be established.

Example sdb:

sdb1 > /boot
sdb2 > lvm with /

Which can be already outdated ... __{{emoticon}}__

taigarden · posted: 2013-09-18 13:48

Dave wrote:I am not sure if this it he case, but if I a reading this right it seems that blag's grub is in the mbr of the second disk. However you are trying to run the os on the second disk really from the mbr of first. If this is the case would grub not have to be installed to the root partition of the blag install on the second disk... not the mbr of the second disk? Please correct me if I am wrong thinking this.

(1) Yes, Blag's grub is in the mbr of the second disk (sdb1).
(2) Yes, I'm trying to run the os on the second disk from the mbr of the first.

taigarden · posted: 2013-09-18 13:58

male wrote:If you are not familiar with lvm, then why did you install in this environment?

How is the grub of antiX appeal to the files of the grub of Blag, if they lie in an encrypted partition?

(1) I opted to let Blag's installer run with automatic defaults using the entire second hard drive. I wasn't aware that the system will take the format lvm. My mistake.
(2) I am not aware about an encrypted partition.
(3) Tonight, or at most tomorrow, I will make the verifications that you suggested and will post the outputs.
Thank you.

taigarden · posted: 2013-09-18 14:01

rokytnji wrote:I had assumed he knew to install grub to root on secondary installs Dave.

Blag's installer gave the option to install grub in the mbr of the second hard drive (sdb) and I took that.

Dave · posted: 2013-09-18 14:43

Ok then I would suggest to look up how to install grub from blag to another device. That way you can install blag's grub to the root partition of the blag install. If it is not possible you may need to install blag again and choose install to root partition instead of install to mbr.

Another option would be to use super grub disk to install grub to the root partition of blag.

Dave

taigarden · posted: 2013-09-18 15:24

Dave wrote:Ok then I would suggest to look up how to install grub from blag to another device. That way you can install blag's grub to the root partition of the blag install. If it is not possible you may need to install blag again and choose install to root partition instead of install to mbr.

Another option would be to use super grub disk to install grub to the root partition of blag.

Dave

Since I can not access Blag system, I might opt to use super grub disk to install grub to the root partition of Blag.

There are two versions of super grub disk:

(a) Super GRUB Disk, which uses grub legacy.
(b) Super GRUB2 Disk, which uses grub2.

Which one do you suggest?
Thank you.