DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So grub legacy comes up, your able to boot voyager, but not debian. If that is true use the debian rescue cd to install grub2 to the debian partition ,and chainload from grub legacy, Your grub legacy might not be able to boot an ext3 that is formatted with a 256 anode size , some grub legacy versions can only handle a partitions formated with a 128 anode size, That might be the problem
It does not have the GUI, that would probably be why it is so small.
Also, I have been able to get into both installs (booting from external floppy) using smartbootmanager.
edit: it seems smartbootmanager should be ok as a replacement for supergrub disk as it has grub 1.98
update: all files found (plus many more).. also entering commands returned nothing.. it started the boot process.. currently thrashing the floppy drive. It seems you are trying to boot into an old voyage kernel, fwiw. I stopped it after about 5 minutes. [but as above, i can boot them w/ smartbootmanager]
I don't think smart btmgr has grub 1.98. It only chainload existing grub. We need to check first if installed debian works properly by bypassing grub in MBR. Please try again with supergrub2 disk.
if you can boot into Debian then as root run ' dpkg-reconfigure grub-pc '. dpkg will ask you a couple of questions so make sure you install grub to /dev/sda. Then it will run update-grub. Hopefully after that you can boot into all 3 of your Distros. If only Debian then run update-grub yourself and that should work.
hurry_hui; Thanks, yes the one posted before was so wrong. As noted, debian works when chainloading with the existing grub. So do i still need to use subergrub2disk ?? The reason i ask is i've had no luck yet getting it to make a boot floppy. It seems to be the same as smrtbtmgr?
@62chevy.. no, i've done that many times. I did it again. no it makes no change, although i have grub2 again now. And there are only 2 distros.
Sorry about that, had the wrong root partition number in my earlier post. are you now able to boot off your harddrive into voyager without using the floppy disk?
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
I do not know what the thing is supposed to look like, but if you have grub2 working, you could add a menu entry for your MS install to the 40_custom script file and it should work from there.
Some kind soul would have to supply the entry for you if you do not know it. I sure don't.
hurry_hui; Thanks, yes the one posted before was so wrong. As noted, debian works when chainloading with the existing grub. So do i still need to use subergrub2disk ?? The reason i ask is i've had no luck yet getting it to make a boot floppy. It seems to be the same as smrtbtmgr?
@62chevy.. no, i've done that many times. I did it again. no it makes no change, although i have grub2 again now. And there are only 2 distros.
Yes, you still need supergrub2 disk, apparently there is something missing in existing grub. Smart btmgr is just a bootmanager and requires bootloader like grub, lilo, or ntloader installed to root partition (or MBR) to operate properly.
If you have floppy you can use dd (linux) like below or rawrite / rawritewin for windows.
dd if=name_of_supergrub2_disk.iso of=/dev/fd0
(you need blank floppy to do this)
If you prefer USB you can use dd and/or unetbootin (having support for both linux and windows).
OK i have supergrub2disk working now. what exactly do i need to input?? because 'ls (hd0,1)/' returned 'error: no such partition' and 'linux /boot/...' returned "unknown command 'linux'".
@widget; there is no windows, i don't know where you got that idea.
@c.purple; still no. and it's voyage.
OK i have supergrub2disk working now. what exactly do i need to input?? because 'ls (hd0,1)/' returned 'error: no such partition' and 'linux /boot/...' returned "unknown command 'linux'".
...
You can try menu 'Detect any OS'. This should output kernels detected on harddisk.
If this cannot work properly we can try 'ls' to see available hdd and partition and then manually enter certain folders.
"unknown command 'menu'"
"unknown command 'Detect'"
ls: "(hd0) (fd0)"
ls (hd0): "error: unknown filesystem"
ls (hd0,0)/ls (hd0,1)/ ls (hd0,2): "error: no such partition"
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
Quote:
Originally Posted by sdfi
OK i have supergrub2disk working now. what exactly do i need to input?? because 'ls (hd0,1)/' returned 'error: no such partition' and 'linux /boot/...' returned "unknown command 'linux'".
@widget; there is no windows, i don't know where you got that idea.
@c.purple; still no. and it's voyage.
Well I got that idea from this in your boot info script results;
"unknown command 'menu'"
"unknown command 'Detect'"
ls: "(hd0) (fd0)"
ls (hd0): "error: unknown filesystem"
ls (hd0,0)/ls (hd0,1)/ ls (hd0,2): "error: no such partition"
Sorry for not being clear.
on supergrub menu there are followings:
Detect any OS
Detect any GRUB2 configuration file (grub.cfg)
Detect any GRUB2 installation (even if mbr is overwritten)
Detect loop bootable isos (in /boot-isos or /boot/boot-isos)
Enable GRUB2's LVM support
Enable GRUB2's RAID support
Enable GRUB2's PATA support (to work around BIOS bugs/limitations)
Enable GRUB2's USB support *experimental*
Enable serial terminal
List devices/partitions
-----------------------------------
select this menu to activate ata module
Enable GRUB2's PATA support (to work around BIOS bugs/limitations)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.