Unofficial Austrumi Linux for English users forum golf & dvd

A Latvian and english Linux tiny operating system. used by golf & dvd lovers

You are not logged in.

Adverts

Adverts

#1 2009-05-04 15:00:17

georger
Guest

New here, question about dual-boot setup?

Hello from Canada

I'm new to trying Austrumi and I like it......I'm currently running Ubuntu Linux and I'd like to set up a dualboot arrangement.

I've been experimenting with this and have had no success so far. Ubuntu likes to install GRUB and Austrumi likes to install LILO. I find that either GRUB overwrites LILO or LILO overwrites GRUB so there's no having both?

How can I accomplish this on one hard drive please?

Thanks,
geo

 

2009-05-04 15:00:17

AdBot
Advertisements

#2 2009-05-04 20:27:12

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

If you use ubuntu and grub, you could use chainload+1 and copy livecd of autrumi into the grub menu(root partition).

Then the iso file of Austrumi will boot ok.

Austrumi is set up to hdinstall on Windows ntfs fat table(lilo in mbr), not with any other linux distros.

If you are not familiar with grub or chainload+1 please google grub wiki, chainload +1 howto, and iso file installation solutions.  Add grub menu will boot. The chainload +1 means you can just copy iso file in root partition, into ntfs fat table. Grub will read it and boot it from its menu(not from mbr)?

Basically, you need to understand grub and lilo from mbr, and chainload in root partition(not in mbr), and where ths iso file should reside to be booted?

Footnote:
With grub and lilo in mbr of the hdd zero track, each new linux distro has to be installed  in each new partition(physical or logical). With chainload +1, the menu is not in mbr, you load every Linux distro into the one root partition (Fat table) same as windows. The grub is just bootloader for files in the ntfs fat table in root partition only. Do not add partitions for Linux distros, when you chainload +1.

Offline

 

#3 2009-05-05 03:12:12

georger
Guest

Re: New here, question about dual-boot setup?

I'll look into it ASAP! Thanks!

geo

 

#4 2009-05-06 01:50:32

georger
Guest

Re: New here, question about dual-boot setup?

Here's my Grub menu.lst:

title        Ubuntu 8.10, kernel 2.6.27-11-generic
uuid        c4626f97-9cb2-4218-911d-9089cfb49aae
kernel        /boot/vmlinuz-2.6.27-11-generic root=UUID=c4626f97-9cb2-4218-911d-9089cfb49aae ro quiet splash
initrd        /boot/initrd.img-2.6.27-11-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
uuid        c4626f97-9cb2-4218-911d-9089cfb49aae
kernel        /boot/vmlinuz-2.6.27-11-generic root=UUID=c4626f97-9cb2-4218-911d-9089cfb49aae ro  single
initrd        /boot/initrd.img-2.6.27-11-generic

title        Ubuntu 8.10, kernel 2.6.27-7-generic
uuid        c4626f97-9cb2-4218-911d-9089cfb49aae
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=c4626f97-9cb2-4218-911d-9089cfb49aae ro quiet splash
initrd        /boot/initrd.img-2.6.27-7-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid        c4626f97-9cb2-4218-911d-9089cfb49aae
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=c4626f97-9cb2-4218-911d-9089cfb49aae ro  single
initrd        /boot/initrd.img-2.6.27-7-generic

title        Ubuntu 8.10, memtest86+
uuid        c4626f97-9cb2-4218-911d-9089cfb49aae
kernel        /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# 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/sdb1.
title        AUSTRUMI (on /dev/sdb1)
root        (hd1,0)
kernel        /boot/vmlinuz root=/dev/sdb1 ro vga = normal append ="rw 4 init=/boot/linuxrc
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title        AUSTRUMI-TEXT (on /dev/sdb1)
root        (hd1,0)
kernel        /boot/vmlinuz root=/dev/sdb1 ro append ="rw 3 init=/boot/linuxrc
savedefault
boot


I found that first I should partition my drives, and then I should install Austrumi on one drive FIRST and let it install LILO into the MBR. Then I should install Ubuntu on the second drive and it will install GRUB.

This works to let GRUB recognize them and not cause them to delete each other, fight over who takes over the computer.

Of course now Austrumi ceases to boot during the second stage, it seems to stall after it gets it's ip address and it goes no further, just sitting there (I watched it in text mode) and taking forever.

I can still boot into Austrumi from the CD and I even installed it on my USB memory stick to boot from successfully. But just not from the hard drive! Go figure!

I didn't get anywhere with chainload and I hate wasting my evenings in front of this damned idiot box computer, I just want the software to install and run without throwing a tantrum. Oh well!

Any thoughts please? Thanks.

 

#5 2009-05-06 09:07:35

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

Sorry, if you only have Ubuntu and Austrumi, use only Lilo. do not use Grub.

You will install lilo into mbr, boot on dos, boot ubuntu in another name.

Lilo I think can do many  operating systems? Over 100?

Lilo config is different from grub, and can not be merged(no room in mbr). Austrumi will install to Lilo from iso file once booted from cd. You need to look at a sample Lilo config file to see what Austrumi install into it? Then you can install Ubuntu into Lilo config file as well?

Offline

 

#6 2009-05-06 12:39:08

georger
Guest

Re: New here, question about dual-boot setup?

Yea unfortunately Ubuntu doesn't install with LILO and my wife prefers Ubuntu. Gotta keep my wife happy you know! :)

Keeping Autsrumi and Ubuntu on physically separate hard drives helps here I find but I'm having a problem.

When I do install Austrumi onto the hard drive, it only gets as far as Stage 2 and getting the network IP address, then everything halts and I can't even reboot the machine (Ctrl Alt Del), it says some directory is missing. :mad:

But I am able to successfully install Austrumi onto my 1 Gig memory stick and boot from it, even run the graphical user interface. :D

Why should there be any difference between installing to a USB memory stick and installing to a hard drive? Why is Austrumi choking on the hard drive? It can't be a lack of space, there's 100 Gig on the hard drive and 2 Gig of Ram on the machine.

I really do want to make this install of Austrumi work, but I cannot install and run Ubuntu under LILO, there simply is no provision made for it during the install process.

Help?

 

#7 2009-05-06 13:04:47

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

Austrumi probably installs on hd0,0? You try to install it on hd1,0?

Most of the distro use Lilo to install for dual boot with windows. Once you change that condition, the hdinstall script does not work anymore. You may need to change the Austrumi hdinstall script to fit your desire?

Offline

 

#8 2009-05-09 13:30:58

georger
Guest

Re: New here, question about dual-boot setup?

I wouldn't know how to change the install script. But I think I did manage to get Austrumi installed to the second hard drive. Please observe:

device     fs_type label    mount point    UUID
-------------------------------------------------------------------------------
/dev/sda1  ext3             /              5ddc3b7f-8762-4864-abff-063f9fcbbc26
/dev/sda5  swap             <swap>         d3af77d6-db11-43cc-955f-05ea3aaa4d32
/dev/sda6  ext3             /media/disk-1  02420a05-14e7-4e46-9ca1-47d205bd857b
/dev/sdb1  ext3    Austrumi (not mounted)  7312929e-61ad-4c4c-b53d-de64892b142a
/dev/sdb2  swap             <swap>         664cec0d-7cdb-4004-bc44-b19212eb6635
/dev/sdb3  ext3             /home          710e2ba2-fc7d-443d-9465-30e2d9f20241

In this map:
/dev/sda1 contains my Ubuntu installation
/dev/sdb1 contains my Austrumi installation

And if I use Gparted to see the partitions, I can see that /dev/sdb1 has 498.02 mB of stuff on it.

But in my Ubuntu /boot/grub/menu.lst file this is all that is listed:

# ## End Default Options ##

title        Ubuntu 8.10, kernel 2.6.27-11-generic
uuid        5ddc3b7f-8762-4864-abff-063f9fcbbc26
kernel        /boot/vmlinuz-2.6.27-11-generic root=UUID=5ddc3b7f-8762-4864-abff-063f9fcbbc26 ro quiet splash
initrd        /boot/initrd.img-2.6.27-11-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
uuid        5ddc3b7f-8762-4864-abff-063f9fcbbc26
kernel        /boot/vmlinuz-2.6.27-11-generic root=UUID=5ddc3b7f-8762-4864-abff-063f9fcbbc26 ro  single
initrd        /boot/initrd.img-2.6.27-11-generic

title        Ubuntu 8.10, kernel 2.6.27-7-generic
uuid        5ddc3b7f-8762-4864-abff-063f9fcbbc26
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=5ddc3b7f-8762-4864-abff-063f9fcbbc26 ro quiet splash
initrd        /boot/initrd.img-2.6.27-7-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid        5ddc3b7f-8762-4864-abff-063f9fcbbc26
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=5ddc3b7f-8762-4864-abff-063f9fcbbc26 ro  single
initrd        /boot/initrd.img-2.6.27-7-generic

title        Ubuntu 8.10, memtest86+
uuid        5ddc3b7f-8762-4864-abff-063f9fcbbc26
kernel        /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

I'm asking this same question on the Ubuntu help forums so hopefully I'll be able to get an answer that will help me make a nice dual-booting system.

I thought I had it all figured out just by first installing Austrumi, then installing Ubuntu afterwards, each on their own hard drive. But for other reasons, I ended up repeating the reinstall process and it didn't work as I thought it would.

 

#9 2009-05-09 18:30:28

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

Your idea may work if Austrumi was installed on hdd by itself(no lilo). And you can boot it. Then you can install Ubuntu grub to boot ubuntu?

When you have two ext3fs on sda1, then you are chainloading. Ubuntu grub has its own scripts.

There is a grub howto in Ubuntu community documentation that can help you straighten out you grub menu and list. Ubuntu grub uses automagic and debian notes.

Ubuntu grub boots Ubuntu only, you have to use ESC to get the menu list of other operating system scroll down and click Austrumi to boot.

I recommend doing grub with std grub versions. Ubuntu grub favours Ubuntu only, has to be installed last on the menu list to test boot others first.

Offline

 

#10 2009-05-17 04:28:11

georger
Guest

Re: New here, question about dual-boot setup?

Well now I recently received my Ubuntu 9.04 CD in the mail. So I retried all of this stuff again.

I set up the 40 gig drive at sda to be root for Ubuntu.
The 100 gig drive at sdb has an ext2 partition for Austrumi. Both are flagged to be bootable.

I booted from the Austrumi CD and ran the installer, pointing to sdb1 and it installed the first time! No error messages (funny that any error messages are in a foreign language, making it impossible to understand fully what has gone wrong but they appeared mostly whenever I tried to use the Austrumi formatter to control my hard drive).

Then I ran the Ubuntu 9.04 installer. This new version does a much better job at detecting and organizing GRUB because now GRUB lists the Austrumi installation on sdb1.

Unfortunately now, there is a new problem. Austrumi will only start in text mode. And it takes devilishly long to do so, nearly 10 minutes!!!!

The slow down begins once it boots to these points (I wrote them down):
udhcpc (1170): Lease of 192.168.2.3 obtained, lease time -1
deleting routers
adding dns 192.168.2.1
successfully obtained IP address via wired link (eth0)

At this point there is no cursor and it's about 10 minutes until it struggles to continue to:

Starting autofs daemons, mkdir: cannot create directory '/mnt/.auto': Read-only file system
root@localhost:~# /sbin/ldconfig:can't unlinkd /etc/ls.so.cache~ (Read-only file system)

After this it defaults to the command prompt mode.

If I try to start fvwm or X, I get a fatal error (I didn't feel like writing all of these error messages, I'd get writer's cramp if I did).

Also if I try to Ctrl+Alt+Del to reboot, I get the following message:
init: /dev/initctl:No such file or directory

Here is the content of my Ubuntu /boot/grub/menu.lst as the Ubuntu 9.04 installer wrote it (just the business end of it):

title        Ubuntu 9.04, kernel 2.6.28-11-generic
uuid        a85046d8-2f1c-4f30-993c-9b5626f77633
kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=a85046d8-2f1c-4f30-993c-9b5626f77633 ro quiet splash
initrd        /boot/initrd.img-2.6.28-11-generic
quiet

title        Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid        a85046d8-2f1c-4f30-993c-9b5626f77633
kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=a85046d8-2f1c-4f30-993c-9b5626f77633 ro  single
initrd        /boot/initrd.img-2.6.28-11-generic

title        Ubuntu 9.04, memtest86+
uuid        a85046d8-2f1c-4f30-993c-9b5626f77633
kernel        /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# 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/sdb1.
title        AUSTRUMI (on /dev/sdb1)
root        (hd1,0)
kernel        /boot/vmlinuz root=/dev/sdb1 ro vga = normal append ="rw 4 init=/boot/linuxrc
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title        AUSTRUMI-TEXT (on /dev/sdb1)
root        (hd1,0)
kernel        /boot/vmlinuz root=/dev/sdb1 ro append ="rw 3 init=/boot/linuxrc
savedefault
boot

So while it appears to have installed on sdb, something is still messed up (yet I can boot from the CD or the USB memory stick and everything purrs nicely).

The machine is no slug, it's a Dell Precision 370, 3.2GHz Pentium 4 (with hyperthreading), 2 Gig RAM, 128 Mb ATI FireGL V3100 card.

Help???

 

#11 2009-05-17 08:38:13

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

Thanks for the details. We all will learn from the Austrumi install script in hdinstall sequencing beyond vmlinux copied to drams first.

It now tries udhcp first to get network installed.

Then it does the autofs for cron jobs setup(read only fs setup). which stops all further install, meaning no x server. This is because of Ubuntu install, possibly using the same IP address? But, rather it never finished the TEXT(no ctl-alt-del file found) and then never booted the splash screen and vmlinux?

Since you come so far, Can you tell us why in this install, you have austrumi on ext2fs? Last time was ext3?

From what you described, your hdd install did not have splash screen to select english language in cheat codes or you selected text(run level3) in grub list?

Ubuntu was booted in memtest, single and quiet splash.

Austrumi is booted in text(install script), and ro vga=rw4 boot linuxrc. Is there something missing from the Debian added grub menu list??

Offline

 

#12 2009-05-17 10:32:51

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

Linuxrc is rescue mode which means you boot by floppy or cdrom.

Did your cdrom light up. You have to place the livecd of austrumi in the cdrom or dvd?

If you had copied the image=vmlinux on sdb1, then you can boot from it on hd1,0. by quiet splash. Same kind of list like Ubuntu?

Apparently, Austrumi only wrote two files on your hdd. Text and Linuxrc?

Offline

 

#13 2009-05-17 14:26:49

georger
Guest

Re: New here, question about dual-boot setup?

quote "Then it does the autofs for cron jobs setup(read only fs setup). which stops all further install, meaning no x server. This is because of Ubuntu install, possibly using the same IP address? But, rather it never finished the TEXT(no ctl-alt-del file found) and then never booted the splash screen and vmlinux?"

YES, correct. You have correctly followed what I have been attempting to explain.
-------------------------------------------------------------------------------------
quote "Since you come so far, Can you tell us why in this install, you have austrumi on ext2fs? Last time was ext3?"

I've been having difficulty getting the installer to work correctly. So this has been experimental.

The installer that is part of the boot CD for Austrumi appears to have difficulty in handling the hard drive.

Instead I use the Ubuntu LiveCd to run gparted and prepare these partitions before hand. Finally it seems that formatting the partition to "ext2" gave no error message. This is the reason for changing from "ext3".

I observed that when I tried installing into an ext3 format, it was unsuccessful, the only bit of the error message that was understandable was "finished with errors".

I also observed the same problem if I tried to install with format to "reiserfs". Error message sometimes would say "finished with errors".
-------------------------------------------------------------------------------------
quote "From what you described, your hdd install did not have splash screen to select english language in cheat codes or you selected text(run level3) in grub list?"

When I booted from the Austrumi CD, I selected English from the initial menu. From there the operating system copied itself into RAM and I operated the installer from the Graphical shell.

I didn't select any run level. And selecting "text" mode is about as fun as pulling teeth without painkillers so I would not choose to do that on my own. The machine did boot into Text mode by itself.
-------------------------------------------------------------------------------------
quote "Ubuntu was booted in memtest, single and quiet splash. Austrumi is booted in text(install script), and ro vga=rw4 boot linuxrc. Is there something missing from the Debian added grub menu list??"|

No, the grub menu list is unaltered and is just as the Ubuntu installer created. I really wouldn't know how to change it without asking someone.
-------------------------------------------------------------------------------------
quote "Apparently, Austrumi only wrote two files on your hdd. Text and Linuxrc?"

No, there appears to be 18 directories on the partition:
austrumi
bin
boot
dev
etc
home
lib
lost+found
media
mnt
opt
proc
root
sbin
sys
tmp
usr
var

Also 2 files outside of any of those directories:
ldlinux.sys
syslinux.cfg
-------------------------------------------------------------------------------------
Update: I have further information on this.....I've been trying to troubleshoot this and see what other progress I can make.

The error message I am receiving if I type X at the command prompt is:
"Fatal Server error: Cannot create lock file in /tmp/.txo-lock"

I get a similar type of error message if I type fvwm at the command prompt.

Also other error messages pertained to only having Read-only access to:
/mnt/.auto
/root/.fvwm
/etc/ld.so.cache

Guessing that maybe it was just a matter of disk permissions which were "messed up", I booted into Ubuntu in Root mode and simply tried setting all of the files and directories to be Root access read/write mode. Then I tried to reboot into Austrumi from the GRUB menu list.

When I tried this, I received messages during text boot (again I did not select text boot, it just did this by itself) to the effect that "Universal read/write permissions should not be enabled on /etc/sysconfig/autologin" (I'm recalling this message from memory, it was to this effect so I may not have quoted it 100% correctly).

I rebooted back into Ubuntu and changed the permission of /etc/sysconfig/autologin to exclude everything else except Root, then I tried to reboot again into Austrumi.

It still takes 10 minutes to leave the message "Successfully obtained IP address via wired link (eth0)" to finish trying to boot. I still get the message ""Fatal Server error: Cannot create lock file in /tmp/.txo-lock"" and Austrumi still tries to boot in text mode, never in graphics mode.

I did successfully install Austrumi to my 1Gig USB memory stick and it boots perfectly!

Why should the install process fail to do the same quality of installation with a hard drive? Where did it fail and how can I fix this?

 

#14 2009-05-17 15:01:20

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

I suspect that text file only did the cfg.

Then linuxrc should start the livecd and copy into all the zero length files and directories then boot Austrumi.

You can set the bios to boot from you USB key, and it may work, if you don't have floppy or cdrom/dvd?

Offline

 

#15 2009-05-18 06:39:22

georger
Guest

Re: New here, question about dual-boot setup?

Yea, I can boot from the USB key, no problem. I was hoping to be able to make the second hard drive boot Austrumi.

 

#16 2009-05-18 08:15:58

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

Austrumi has text verbose, after the splash screen cheat codes are selected. This shows you what it does to boot into drams.

So, instead of text and linuxrc, you have to install iso file in a partition to boot austrumi in any hdd or its own partition? iso file is not ext2/3? but it will boot after bootloader is finished.

Have fun, and let us know how you did it?

Offline

 

#17 2009-05-20 01:20:16

georger
Guest

Re: New here, question about dual-boot setup?

quote: ".....you have to install iso file in a partition to boot austrumi in any hdd or its own partition? iso file is not ext2/3? but it will boot after bootloader is finished."

Tried this....didn't work, now GRUB gives me error 15, file not found (in both graphics or text mode boot).

 

#18 2009-05-20 10:48:51

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

This is because you are chainloading ext files in Ubuntu grub. Iso file can not be chainloaded and file found.

To use iso file, you have to have a physical or logical partition to place the iso file. Then bios can boot it, if the grub in hdd mbr can point to it?

Its just for info. You need to redo ubuntu grub, which is a big job.

For others using grub in mbr, iso file can be copied into the next partition. Then you add it in the grub menu list.

Footnote:
Grub uses fdisk partition to boot each os. Linux considers ext file as a partition. So, grub partitions count both fdisk partition and ext files in consecutive order. Be careful when you count partition number in grub menu list.

Offline

 

#19 2009-05-20 12:31:48

georger
Guest

Re: New here, question about dual-boot setup?

In other words, I'll either make the Aspirin companies rich by continuing to try this, or I'd be better off just abandoning it (because I really don't have the time to turn it into a science experiment).

I think I'll abandon the effort and just boot off the USB stick when I want to use it.

Thanks.

 

#20 2009-05-20 14:46:11

atang1
Administrator
Registered: 2006-03-30
Posts: 2705

Re: New here, question about dual-boot setup?

In other words, Ubuntu makes it hard to boot grub with other operating system.

If you started with grub version 0.94-1.8 and install ubuntu according to grub rules, you can install all operating systems(vmlinux) that you like in grub. Not letting Ubuntu install other operating system the Ubuntu(debian) way(linuxrc).

To learn more about linuxrc to boot austrumi, you have to look at the source codes to see how it can boot the ext2fs in the hdd?

Offline

 

Adverts

Board footer

Powered by FluxBB
Hosted by PunBB-Hosting