Hi antiX friends
I am trying to install M8.5 on old laptops, vaio sony pcg-fx776 with pentium III, 2 usb ports and 128k ram
and IBM thinkPad A20m with pentium I, one usb port and 64k ram.
Both laptops without internal CD unit, do not work. Both with other distros working, Vaio(puppy and knoppix), IBM(slitaz and knoppix).
In both I am using the procedure Boot from iso on hard-disk, because it looks easy.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.mepis.com/index.php/Installation_Tips"
linktext was:"http://antix.mepis.com/index.php/Installation_Tips"
====================================
Both laptops are giving the msg problem:
Can not find antiX filesystem, sorry.
Dropping you to a (very limited) shell
Press reset button to quit.
In both I tryed with 686 and 486.
I hope someone could help me.
By the way I will try to install using the very more complicated procedure:
Plop boot manager, usb 1.1, antiX M8.5 procedure for install
plop-boot-manager-usb-1-1-antix-m8-5-procedure-for-install-t2647.html
regards in advance
Lorue
topic title: problems with Boot from iso on hard-disk
-
loruePosts: 13
- Joined: 26 Sep 2010
-
wayne128Posts: 51
- Joined: 05 Sep 2010
#2
hi Lorue
Welcome to antiX forum
regarding your installation issue, i briefly look at the link in your post, i think the example given assumed that the grub is installed in second disk drive (sdb1) first partition, therefore the grub menu entry is (hd1,5).
I assume your already take care of amending the (hd1,5) to appropriate syntax suitable for your internal drive.
If there is only one drive in your computer, the grub entry should read (hd0,y) for first drive.
may be you could post your partition information and /bot/grub/menu.lst so that others can help you with the installation issue?
Welcome to antiX forum
regarding your installation issue, i briefly look at the link in your post, i think the example given assumed that the grub is installed in second disk drive (sdb1) first partition, therefore the grub menu entry is (hd1,5).
I assume your already take care of amending the (hd1,5) to appropriate syntax suitable for your internal drive.
If there is only one drive in your computer, the grub entry should read (hd0,y) for first drive.
may be you could post your partition information and /bot/grub/menu.lst so that others can help you with the installation issue?
-
loruePosts: 13
- Joined: 26 Sep 2010
#3
Hi Wayne128, thank you for your answer.
On the link shows"You will need a spare partition on your hard drive".
I understand I will need two partiton, first where to place de antiX.iso and second where to install when I run the installation process.
Here is the menu.lst
regards
Lorue
On the link shows"You will need a spare partition on your hard drive".
I understand I will need two partiton, first where to place de antiX.iso and second where to install when I run the installation process.
Here is the menu.lst
Code: Select all
default 0
timeout 30
color cyan/blue white/blue
# For booting KNOPPIX from : /dev/hda2
#
title KNOPPIX
root (hd0,1)
kernel /boot/vmlinuz root=/dev/sda2 rootwait lang=us apm=power-off vga=791 nomce loglevel=0 quiet rw
# For booting SliTaz from : /dev/hda1
#
title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.30.6-slitaz)
root (hd0,0)
kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/hda1
# For booting antiX from : /dev/hda6
#
title antiX
root (hd0,5)
kernel /antiX/vmlinuz vga=791 fromhd=/dev/sda6 fromiso=/antiX/antiX-M8.5-686.iso en xres=1024x768
initrd /antiX/initrd.gz
boot
Lorue
Last edited by lorue on 28 Sep 2010, 13:46, edited 1 time in total.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#4
Add rootdelay=20 to the kernel line and see if that works.
You could also try removing the fromhd=/dev/sda6 entry or changing it to fromhd=/dev/hda6
You could also try removing the fromhd=/dev/sda6 entry or changing it to fromhd=/dev/hda6
-
loruePosts: 13
- Joined: 26 Sep 2010
#5
Hi Anticapitalista
I just verify on IBM ThinkPad and again the same problem.
Here is the menu.lst
regards
Lorue
I just verify on IBM ThinkPad and again the same problem.
Here is the menu.lst
I hope I could know results later on Sony Vaio, because right now I haveing problems with Grub (error 15) and have to modify using UUID.title antiX
root (hd0,5)
#kernel /antiX/vmlinuz vga=791 fromhd=/dev/sda6 fromiso=/antiX/antiX-M8.5-686.iso en xres=1024x768
kernel /antiX/vmlinuz fromhd=/dev/hda6 fromiso=/antiX/antiX-M8.5-686.iso en xres=800x600 rootdelay=20
initrd /antiX/initrd.gz
boot
regards
Lorue
-
oldhogheadPosts: 516
- Site Admin
- Joined: 01 Oct 2007
#6
You have:
maybe try:
cheers,
ohh
Code: Select all
title antiX
root (hd0,5)
#kernel /antiX/vmlinuz vga=791 fromhd=/dev/sda6 fromiso=/antiX/antiX-M8.5-686.iso en xres=1024x768
kernel /antiX/vmlinuz fromhd=/dev/hda6 fromiso=/antiX/antiX-M8.5-686.iso en xres=800x600 rootdelay=20
initrd /antiX/initrd.gz
bootCode: Select all
title antiX
#kernel /antiX/vmlinuz vga=791 fromhd=/dev/sda6 fromiso=/antiX/antiX-M8.5-686.iso en xres=1024x768
kernel (hd0,5) /antiX/vmlinuz fromhd=/dev/hda6 fromiso=/antiX/antiX-M8.5-686.iso en xres=800x600 rootdelay=20
initrd (hd0,5) /antiX/initrd.gz
bootohh
-
loruePosts: 13
- Joined: 26 Sep 2010
#7
Hi Wayne, anticapitalista and oldhoghead
On the IBM thinkpad, I did the last test with (hd0,5) and still do not work, the problem continue.
Just before the error msg there is a comment:
EXT2-fs warning:maximal mount count reached, running e2fsck is recommended
VFS:Mounted root (ext2 filesystem) on device 1:0
Total memory availabre:58444kb, memory free: 35592kb
can not find antiX file system, sorry
I do not know which parameters do I have to use to run e2fsck
I use gparted and shows sda6 inside of a extended partition, and the other partitions looks well. maybe sda6 has to be a primary partition. I decide to use fdisk to modify partitions.
I use fdisk /dev/hda but at the begining shows the msg:
Device contains neither a valid DOS partition table, nor SUN, SGI or OSF disklabel.
And if I want to print the partition table (p) it do not show the list of partitions, only the header of the disk. Why does gparted shows everything well and fdisk do not??, how do I fix the partition table??
Maybe that is the problem.
regards
Lorue
On the IBM thinkpad, I did the last test with (hd0,5) and still do not work, the problem continue.
Just before the error msg there is a comment:
EXT2-fs warning:maximal mount count reached, running e2fsck is recommended
VFS:Mounted root (ext2 filesystem) on device 1:0
Total memory availabre:58444kb, memory free: 35592kb
can not find antiX file system, sorry
I do not know which parameters do I have to use to run e2fsck
I use gparted and shows sda6 inside of a extended partition, and the other partitions looks well. maybe sda6 has to be a primary partition. I decide to use fdisk to modify partitions.
I use fdisk /dev/hda but at the begining shows the msg:
Device contains neither a valid DOS partition table, nor SUN, SGI or OSF disklabel.
And if I want to print the partition table (p) it do not show the list of partitions, only the header of the disk. Why does gparted shows everything well and fdisk do not??, how do I fix the partition table??
Maybe that is the problem.
regards
Lorue
-
loruePosts: 13
- Joined: 26 Sep 2010
#8
Hi antiX friends
I have fix the difference between gparted and fdisk reorginizing the partitions and now is OK.
Now I just try to install again antiX (486,686) from ISO on HDD and I recieved again the same msgs.
""can not find antiX file system, sorry...." in the same place.
I decided to install trying the procedure plop-boot-manager-usb-1-1-antix-m8-5-procedure-for-install-t2647.html
As the idea of steps 1 to 11 is to copy the antiX directory, I used the other distros installed in the machine to did it.
Then I continue from step 12, it looks well but again I am receiving the msgs
""can not find antiX file system, sorry....", in the same place. I tryed with 686 and 486.
I want to comment, at the same time I just install Puppy in this machine, starting with Lupu5.1.1, it looks well for the live-USB, but when I try to made the full installation, Puppy do not recognice the HDD. Then I had to do a Puppy downgrade to puppy-4.3.1/special-puppies/pup-431-k2.6.21.7-scsi-intel_modems.iso and finally I could install. details:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.murga-linux.com/puppy/viewtopic.php?p=455119"
linktext was:"http://www.murga-linux.com/puppy/viewto ... 7601205574"
====================================
Could it be posible anti X is not recognicing something in my machine?? The HDD??
Thank you and regards
Lorue
I have fix the difference between gparted and fdisk reorginizing the partitions and now is OK.
Now I just try to install again antiX (486,686) from ISO on HDD and I recieved again the same msgs.
""can not find antiX file system, sorry...." in the same place.
I decided to install trying the procedure plop-boot-manager-usb-1-1-antix-m8-5-procedure-for-install-t2647.html
As the idea of steps 1 to 11 is to copy the antiX directory, I used the other distros installed in the machine to did it.
Then I continue from step 12, it looks well but again I am receiving the msgs
""can not find antiX file system, sorry....", in the same place. I tryed with 686 and 486.
I want to comment, at the same time I just install Puppy in this machine, starting with Lupu5.1.1, it looks well for the live-USB, but when I try to made the full installation, Puppy do not recognice the HDD. Then I had to do a Puppy downgrade to puppy-4.3.1/special-puppies/pup-431-k2.6.21.7-scsi-intel_modems.iso and finally I could install. details:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.murga-linux.com/puppy/viewtopic.php?p=455119"
linktext was:"http://www.murga-linux.com/puppy/viewto ... 7601205574"
====================================
Could it be posible anti X is not recognicing something in my machine?? The HDD??
Thank you and regards
Lorue
-
rokytnjiPosts: 4,164
- Joined: 20 Feb 2009
#9
Hi lorue. Give me a few minutes and I will boot up my IBM A22m with AntiX 8.5 dual boot with Puppy Dingo 4. I installed Antix 8.5 with CDROM drive on 256MB of Ram on the A22m.
Will give you my /boot/grub/menu.lst in case it will help. Be back later.
Happy Trails, Rok
Will give you my /boot/grub/menu.lst in case it will help. Be back later.
Happy Trails, Rok
-
rokytnjiPosts: 4,164
- Joined: 20 Feb 2009
#10
Just noticed your cdroms are shot and you are trying to boot from iso which I have not had to do. I tried to use PLOP on this IBMA22m to boot from USB 1.1 but I failed miserably. dolphin_ oracle was able to successfully do it though. I added his method to the wiki. Anyhows. This is my readouts for successful installs via a cdrom drive on a IBM a22m.
Notice my UUID entries after #####End Default Options##### in menu
I run a seperate /home partition with my AntiX install. Puppy Dingo 4 sits on its own partition. Run a swap partition also of 722MB. Wish I could be of more help with the can't find file system with boot from iso. I had the same problem using a Plop boot floppy with USB 1.1. Like I said. dolhin_oracle jumped that hurdle. My install was all cdrom on this laptop.
Happy Trails, Rok
Edit: throwing in what gparted shows as how my gear is partitioned up. Just a thought. You already have Puppy going in the iBM. Right? You can use Puppy live pendrive with puppy pfix=ram boot option and use gparted in puppy to make your partitions as dolphin_oracle suggests and use rox file manager in puppy for copying files and urxvt in puppy for making directories. Instead of systemrescue pendrive. Just a thought is all.
Code: Select all
timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1
gfxmenu /boot/grub/message
title antiX at hda1, kernel 2.6.32-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=/dev/hda1 nomce quiet nosplash vga=791 acpi=force
initrd /boot/initrd.img-2.6.32-1-mepis-smp
boot
title Puppy
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5 acpi=force
### 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=3585475c-f005-4fa8-872c-8cb0444650e4 ro
# kopt_2_6=root=UUID=3585475c-f005-4fa8-872c-8cb0444650e4 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 2.6.34-stevo
root (hd0,0)
kernel /boot/vmlinuz-2.6.34-stevo root=UUID=3585475c-f005-4fa8-872c-8cb0444650e4 ro nosplash quiet
initrd /boot/initrd.img-2.6.34-stevo
title Debian GNU/Linux, kernel 2.6.34-stevo (init-3)
root (hd0,0)
kernel /boot/vmlinuz-2.6.34-stevo root=UUID=3585475c-f005-4fa8-872c-8cb0444650e4 ro nosplash quiet 3
initrd /boot/initrd.img-2.6.34-stevo
title Debian GNU/Linux, kernel 2.6.32-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=UUID=3585475c-f005-4fa8-872c-8cb0444650e4 ro nosplash quiet
initrd /boot/initrd.img-2.6.32-1-mepis-smp
title Debian GNU/Linux, kernel 2.6.32-1-mepis-smp (init-3)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=UUID=3585475c-f005-4fa8-872c-8cb0444650e4 ro nosplash quiet 3
initrd /boot/initrd.img-2.6.32-1-mepis-smp
title Debian GNU/Linux, kernel memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
### END DEBIAN AUTOMAGIC KERNELS LIST
Notice my UUID entries after #####End Default Options##### in menu
Code: Select all
root@biker:/home/harry# fdisk -l
Disk /dev/hda: 20.0 GB, 20003880960 bytes
255 heads, 63 sectors/track, 2432 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf048567a
Device Boot Start End Blocks Id System
/dev/hda1 * 1 660 5301418+ 83 Linux
/dev/hda2 2341 2432 738990 82 Linux swap / Solaris
/dev/hda3 661 1329 5373742+ 5 Extended
/dev/hda4 1330 2340 8120857+ 83 Linux
/dev/hda5 661 1329 5373711 83 Linux
Partition table entries are not in disk order
Happy Trails, Rok
Edit: throwing in what gparted shows as how my gear is partitioned up. Just a thought. You already have Puppy going in the iBM. Right? You can use Puppy live pendrive with puppy pfix=ram boot option and use gparted in puppy to make your partitions as dolphin_oracle suggests and use rox file manager in puppy for copying files and urxvt in puppy for making directories. Instead of systemrescue pendrive. Just a thought is all.
-
loruePosts: 13
- Joined: 26 Sep 2010
#11
Hi again Roky
Yes I read the Dolphin Oracle procedure on
plop-boot-manager-usb-1-1-antix-m8-5-procedure-for-install-t2647.html
and it do not work for me. The proccess send again the same msg.
""can not find antiX file system, sorry...." in the same place.
I will study your information to use it on my laptop, I hope it will work
thank you and regards
Lorue
Yes I read the Dolphin Oracle procedure on
plop-boot-manager-usb-1-1-antix-m8-5-procedure-for-install-t2647.html
and it do not work for me. The proccess send again the same msg.
""can not find antiX file system, sorry...." in the same place.
I will study your information to use it on my laptop, I hope it will work
thank you and regards
Lorue
-
rokytnjiPosts: 4,164
- Joined: 20 Feb 2009
#12
Hey lorue. I just read this
From
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/can-t-find-antix-filesystem-t2690-15.html"
linktext was:"antix.freeforu ms.org/can-t-find- ... 90-15.html"
====================================
Might work with PLOP. Maybe? Need to boot Antix onto some other computer to try this out though.Inspiration struck.... With some thanks to something I got on a Mepis forum
So i just ran the antiX installer pointed it to the 2GB flash.... Installed grub to flash too.... edited menu.lst so it looked at the UUID rather than /dev/sdx....
And away we go.... __{{emoticon}}__
Thing is I have a new HDD coming in a few days but ummm its a really useful thing to have.... I can now carry my OS in my pocket....
I can't see any problem with doing it this way but if anyone has any comment Ill take it on board __{{emoticon}}__
Thanks all
From
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/can-t-find-antix-filesystem-t2690-15.html"
linktext was:"antix.freeforu ms.org/can-t-find- ... 90-15.html"
====================================
-
wayne128Posts: 51
- Joined: 05 Sep 2010
#13
OK, here I took some interest on booting iso from Harddisk without burning DVD/CD , and decided to try it onto one old laptop with antiX installed on hard disk just to experiment.
When I read the instruction that you linked I worried a bit of not able to follow in term of not understanding what each step does.
I did some checks on other forums, and found this tutorial, it explains the meaning of each step which suit my study and experiment.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://g33kgrrl.wordpress.com/2009/06/29/make-a-gnu-linux-livepartition/"
linktext was:"http://g33kgrrl.wordpress.com/2009/06/2 ... partition/"
====================================
So now here is my starting point:
nec@antiX1:~$ su
Password:
root@antiX1:/home/nec# cat /boot/grub/menu.lst
timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1
gfxmenu /boot/grub/message
title antiX at hda5, kernel 2.6.32-1-mepis-smp
root (hd0,4)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=/dev/hda5 nomce quiet nosplash vga=791
initrd /boot/initrd.img-2.6.32-1-mepis-smp
boot
title pclos lxde chainload to hda1
root (hd0,0)
chainloader +1
title salix chainload to hda7
root (hd0,6)
chainloader +1
so you see, I have antiX installed on hda5, pclos lxde on hda1 and Salix on hda 7.
Note that I used very simple chainloading for pclos ( which use grub installer) and Salix ( which use Lilo installer).
Now I follow the above tutorial
step 1 to 6 to create a 2G partition format with ext3.
9: then I downloaded antiX-M8.2.iso ( just for testing purpose on iso boot from HDD so I will not confused with already installed antiX M8.5). and I save it at /home/nec/Downloads
10, 11 showed
root@antiX1:/home/nec# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a7daf
Device Boot Start End Blocks Id System
/dev/hda1 * 1 765 6144831 83 Linux
/dev/hda2 766 893 1028160 82 Linux swap / Solaris
/dev/hda3 894 1530 5116702+ 83 Linux
/dev/hda4 1531 9729 65850466+ 5 Extended
/dev/hda5 1532 3442 15350107+ 83 Linux
/dev/hda6 3443 4687 10000431 83 Linux
/dev/hda7 * 4688 5962 10241406 83 Linux
/dev/hda8 5963 7874 15358108+ 83 Linux
/dev/hda9 7875 8129 2048256 83 Linux
root@antiX1:/home/nec#
Now I have a hda9 which is 2G partition. hda8 is reserved for other multi boot OS.
12, 13, 14 I follow exactly
15, follow all but change the path to /home/nec/Downloads/antiX-M8.2.iso
16, 17,18, 19 I follow and see that antiX-M8.2.iso has the kernel and initrd at /boot directory
missing step 20 but no problem, it is not important
21, 24: here i used what is available : leafpad and made changes to the menu.lst with additional three lines as below:
title antiX M8.2 virtual liveCD
kernel (hd0,8)/boot/vmlinuz livecd=livecd initrd=initrd.gz root=/dev/hda8 vga=791
initrd (hd0,8)/boot/initrd.gz
after this I save the grub stanza.
Now I am ready for testing. Quit, reboot.. hope for the best...
and.. I couldn't be happier.. antiX-M8.2 booted up!! __{{emoticon}}__
I shall be playing one to two more other OS to see if the same procedure will work so that I will save some DVD/CD __{{emoticon}}__ __{{emoticon}}__
Perhaps this might help you a bit.
When I read the instruction that you linked I worried a bit of not able to follow in term of not understanding what each step does.
I did some checks on other forums, and found this tutorial, it explains the meaning of each step which suit my study and experiment.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://g33kgrrl.wordpress.com/2009/06/29/make-a-gnu-linux-livepartition/"
linktext was:"http://g33kgrrl.wordpress.com/2009/06/2 ... partition/"
====================================
So now here is my starting point:
nec@antiX1:~$ su
Password:
root@antiX1:/home/nec# cat /boot/grub/menu.lst
timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1
gfxmenu /boot/grub/message
title antiX at hda5, kernel 2.6.32-1-mepis-smp
root (hd0,4)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=/dev/hda5 nomce quiet nosplash vga=791
initrd /boot/initrd.img-2.6.32-1-mepis-smp
boot
title pclos lxde chainload to hda1
root (hd0,0)
chainloader +1
title salix chainload to hda7
root (hd0,6)
chainloader +1
so you see, I have antiX installed on hda5, pclos lxde on hda1 and Salix on hda 7.
Note that I used very simple chainloading for pclos ( which use grub installer) and Salix ( which use Lilo installer).
Now I follow the above tutorial
step 1 to 6 to create a 2G partition format with ext3.
9: then I downloaded antiX-M8.2.iso ( just for testing purpose on iso boot from HDD so I will not confused with already installed antiX M8.5). and I save it at /home/nec/Downloads
10, 11 showed
root@antiX1:/home/nec# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a7daf
Device Boot Start End Blocks Id System
/dev/hda1 * 1 765 6144831 83 Linux
/dev/hda2 766 893 1028160 82 Linux swap / Solaris
/dev/hda3 894 1530 5116702+ 83 Linux
/dev/hda4 1531 9729 65850466+ 5 Extended
/dev/hda5 1532 3442 15350107+ 83 Linux
/dev/hda6 3443 4687 10000431 83 Linux
/dev/hda7 * 4688 5962 10241406 83 Linux
/dev/hda8 5963 7874 15358108+ 83 Linux
/dev/hda9 7875 8129 2048256 83 Linux
root@antiX1:/home/nec#
Now I have a hda9 which is 2G partition. hda8 is reserved for other multi boot OS.
12, 13, 14 I follow exactly
15, follow all but change the path to /home/nec/Downloads/antiX-M8.2.iso
16, 17,18, 19 I follow and see that antiX-M8.2.iso has the kernel and initrd at /boot directory
missing step 20 but no problem, it is not important
21, 24: here i used what is available : leafpad and made changes to the menu.lst with additional three lines as below:
title antiX M8.2 virtual liveCD
kernel (hd0,8)/boot/vmlinuz livecd=livecd initrd=initrd.gz root=/dev/hda8 vga=791
initrd (hd0,8)/boot/initrd.gz
after this I save the grub stanza.
Now I am ready for testing. Quit, reboot.. hope for the best...
and.. I couldn't be happier.. antiX-M8.2 booted up!! __{{emoticon}}__
I shall be playing one to two more other OS to see if the same procedure will work so that I will save some DVD/CD __{{emoticon}}__ __{{emoticon}}__
Perhaps this might help you a bit.
-
loruePosts: 13
- Joined: 26 Sep 2010
#14
Hi Wayne
Thank you for your information __{{emoticon}}__
Now is my turn to work studying your comments and Rocy's comment __{{emoticon}}__
regards
Lorue
Thank you for your information __{{emoticon}}__
Now is my turn to work studying your comments and Rocy's comment __{{emoticon}}__
regards
Lorue
-
wayne128Posts: 51
- Joined: 05 Sep 2010
#15
ok, so I thought just update here. I tried another one with failure, LinuxMint9. I am yet to understand why. __{{emoticon}}__
However I have one more success. __{{emoticon}}__
Salix just had beta release on kde-iso, so I download to hard disk , create sda11 to boot and copy the stanza here, it might be useful for me later to refer to. Salix has kernel and initrd at different directory as shown below.
title salix kde virtual liveCD at hda11
kernel (hd0,10)/kernels/hugesmp.s/bzImage livecd=livecd initrd=initrd.img root=/dev/sda11 vga=791
initrd (hd0,10)/isolinux/initrd.img
After I boot this virtual liveCD , I install it on partition6, sda6 and below is the chainloader Stanza.
title salix kde poorman chainload at sda6
root (hd0,5)
chainloader +1
sound like I can save a lot of DVD/CD, especially if I am testing beta/rc/etc. __{{emoticon}}__
However I have one more success. __{{emoticon}}__
Salix just had beta release on kde-iso, so I download to hard disk , create sda11 to boot and copy the stanza here, it might be useful for me later to refer to. Salix has kernel and initrd at different directory as shown below.
title salix kde virtual liveCD at hda11
kernel (hd0,10)/kernels/hugesmp.s/bzImage livecd=livecd initrd=initrd.img root=/dev/sda11 vga=791
initrd (hd0,10)/isolinux/initrd.img
After I boot this virtual liveCD , I install it on partition6, sda6 and below is the chainloader Stanza.
title salix kde poorman chainload at sda6
root (hd0,5)
chainloader +1
sound like I can save a lot of DVD/CD, especially if I am testing beta/rc/etc. __{{emoticon}}__