LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 01-10-2017, 03:10 PM   #1
hifi100
Member
 
Registered: Sep 2016
Location: India
Distribution: Lubuntu 20.04
Posts: 340

Rep: Reputation: Disabled
Debian and Tiny Core dual boot


Hi,

I have installed Debian and Tiny core. I want to add a menu entry in Debian's grub for Tiny Core linux.

I tried running update-grub2 but it didnt detect Tiny Core....

Code:
# fdisk -l

Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x63ce231e

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1  *         2048  48828219  48826172 23.3G 83 Linux
/dev/sda2        48828416 213960703 165132288 78.8G 83 Linux
/dev/sda3       213960704 234440703  20480000  9.8G 83 Linux
sda3 is my Tiny Core partition.
 
Old 01-10-2017, 05:15 PM   #2
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,389

Rep: Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083
Did you install the bootloader for Tiny Core to it's partition? You can boot Debian and mount sda3 and check the /boot/grub/grub.cfg file and if Tiny Core is using Grub2, just copy it's entry to the Debian grub.cfg file to test boot it. If it boots, copy the entry to /etc/grub.d/40_custom and update grub again.
 
Old 01-10-2017, 11:53 PM   #3
hifi100
Member
 
Registered: Sep 2016
Location: India
Distribution: Lubuntu 20.04
Posts: 340

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by yancek View Post
Did you install the bootloader for Tiny Core to it's partition? You can boot Debian and mount sda3 and check the /boot/grub/grub.cfg file and if Tiny Core is using Grub2, just copy it's entry to the Debian grub.cfg file to test boot it. If it boots, copy the entry to /etc/grub.d/40_custom and update grub again.
I did install Tiny Core's boootloader on /dev/sda but after reboot I got operating system not found. Then I booted with the Debian CD, entered into the the rescue mode and reinstalled grub.

Code:
$ su
Password: 
root@debian:/home/deb# mount /dev/sda3 /mnt/
root@debian:/home/deb# cd /mnt/
root@debian:/mnt# ls
lost+found  tce
root@debian:/mnt# cd tce
root@debian:/mnt/tce# ls
boot  mydata.tgz  optional
root@debian:/mnt/tce# cd boot
root@debian:/mnt/tce/boot# ls
core.gz  extlinux  vmlinuz
root@debian:/mnt/tce/boot#
This is my Tiny Core partition. Which file do I need to copy and what grub entry do I need to add to /etc/grub.d/40_custom ?

Last edited by hifi100; 01-11-2017 at 12:20 AM.
 
Old 01-11-2017, 07:26 AM   #4
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,389

Rep: Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083
Quote:
I did install Tiny Core's boootloader on /dev/sda but after reboot I got operating system not found.
That means you installed the Tiny Core boot code over the Debian code in the MBR. Is this an older MBR system or UEFI? I think it would have been simpler to install the Tiny Core bootloader to it's partition (sda3) which would have enabled you to update grub from Debian. In your initial post, you indicate you ran 'update-grub2'. Does that mean you are able to boot the installed Debian? If so, why are you using the Debian CD? If you ran 'update-grub2' from the CD, that won't accomplish anything. If you have Debian Grub code in the MBR now, try putting the entry below in grub.cfg and rebooting. Do NOT update grub before rebooting. If it fails, delete the entry, if it works move it to 40_custom and run update-grub2.

Quote:
menuentry "Tiny Core" {
set root='hd0,msdos3'
linux /boot/vmlinuz append loglevel=3
initrd /boot/core.gz
}
If that fails, you will probably need to post more details and you can do that by googling and downloading and runn the 'bootinfoscript' or going to the site below and downloading and burning boot repair to a CD and rebooting the CD and selecting the option to 'Create BootInfo Summary' and not try any repairs. You can then post a link to the output here.

https://help.ubuntu.com/community/Boot-Repair
 
2 members found this post helpful.
Old 01-11-2017, 07:40 AM   #5
jamison20000e
Senior Member
 
Registered: Nov 2005
Location: ...uncanny valley... infinity\1975; (randomly born:) Milwaukee, WI, US( + travel,) Earth( I wish,) END BORDER$!◣◢┌∩┐ Fe26-E,e...
Distribution: any GPL that works well on my cheapest; has been KDE or CLI but open... http://goo.gl/NqgqJx &c ;-)
Posts: 4,393
Blog Entries: 3

Rep: Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436
I've had to do the same with Fatdog64 and Debian...
 
Old 01-11-2017, 07:50 AM   #6
hifi100
Member
 
Registered: Sep 2016
Location: India
Distribution: Lubuntu 20.04
Posts: 340

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by yancek View Post
That means you installed the Tiny Core boot code over the Debian code in the MBR. Is this an older MBR system or UEFI? I think it would have been simpler to install the Tiny Core bootloader to it's partition (sda3) which would have enabled you to update grub from Debian. In your initial post, you indicate you ran 'update-grub2'. Does that mean you are able to boot the installed Debian? If so, why are you using the Debian CD? If you ran 'update-grub2' from the CD, that won't accomplish anything. If you have Debian Grub code in the MBR now, try putting the entry below in grub.cfg and rebooting. Do NOT update grub before rebooting. If it fails, delete the entry, if it works move it to 40_custom and run update-grub2.



If that fails, you will probably need to post more details and you can do that by googling and downloading and runn the 'bootinfoscript' or going to the site below and downloading and burning boot repair to a CD and rebooting the CD and selecting the option to 'Create BootInfo Summary' and not try any repairs. You can then post a link to the output here.

https://help.ubuntu.com/community/Boot-Repair
This is a mbr system. After I installed from the tiny core iso I was left with a non booting system so I used the Debian disk and used its rescue menu to reinstall grub. Yes I can boot Debian.

Code:
menuentry "Tiny Core" {
set root='hd0,msdos3'
linux /boot/vmlinuz append loglevel=3
initrd /boot/core.gz
}
Tried adding this to /boot/grub/grub.cfg but I get
Code:
error: 'file/boot/vmlinuz not found
error: you need to load the kernel first
The boot repair cd is 613 MB it will take some time on my slow connection. I am downloading it now. I will write back after I create a live usb.

Thanks a lot for your reply.
 
Old 01-11-2017, 07:53 AM   #7
jamison20000e
Senior Member
 
Registered: Nov 2005
Location: ...uncanny valley... infinity\1975; (randomly born:) Milwaukee, WI, US( + travel,) Earth( I wish,) END BORDER$!◣◢┌∩┐ Fe26-E,e...
Distribution: any GPL that works well on my cheapest; has been KDE or CLI but open... http://goo.gl/NqgqJx &c ;-)
Posts: 4,393
Blog Entries: 3

Rep: Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436
Search about /etc/grub.d/40_custom
 
Old 01-11-2017, 08:34 AM   #8
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,450

Rep: Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056
linux /tce/boot/vmlinuz append loglevel=3
 
Old 01-11-2017, 08:50 AM   #9
hifi100
Member
 
Registered: Sep 2016
Location: India
Distribution: Lubuntu 20.04
Posts: 340

Original Poster
Rep: Reputation: Disabled
Here is my boot info http://paste.ubuntu.com/23782040/

Last edited by hifi100; 01-11-2017 at 08:53 AM.
 
Old 01-11-2017, 09:13 AM   #10
hifi100
Member
 
Registered: Sep 2016
Location: India
Distribution: Lubuntu 20.04
Posts: 340

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
linux /tce/boot/vmlinuz append loglevel=3
The PC hanged completely due to kernel panic.
 
Old 01-11-2017, 09:15 AM   #11
beachboy2
Senior Member
 
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 20 MATE, MX-19.3, antiX, EndeavourOS
Posts: 3,323
Blog Entries: 17

Rep: Reputation: 1262Reputation: 1262Reputation: 1262Reputation: 1262Reputation: 1262Reputation: 1262Reputation: 1262Reputation: 1262Reputation: 1262
hifi100,

If you feel nervous before clicking on "Recommended Repair", then backup all your personal data before proceeding.

https://help.ubuntu.com/community/Boot-Repair

Recommended Repair has always worked fine for me in the past.

As it states in the above link:

Warning: the default settings are the ones used by the "Recommended Repair". Changing them may worsen your problem.
 
Old 01-11-2017, 09:21 AM   #12
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,952

Rep: Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148
Quote:
Originally Posted by hifi100 View Post
The PC hanged completely due to kernel panic.
go into your /boot directory for your tiny and see what kernel files you have to use. it maybe named something other than vmlinuz.

Code:
make bzImage

then

cp bzImage vmlinuz

Tiny Core Linux how to make vmlinuz
 
Old 01-11-2017, 09:27 AM   #13
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,450

Rep: Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056
also
linux /tce/boot/vmlinuz append loglevel=3
initrd /tce/boot/core.gz
 
Old 01-11-2017, 09:45 AM   #14
hifi100
Member
 
Registered: Sep 2016
Location: India
Distribution: Lubuntu 20.04
Posts: 340

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
also
linux /tce/boot/vmlinuz append loglevel=3
initrd /tce/boot/core.gz
Code:
menuentry "Tiny Core" {
set root='hd0,msdos3'
linux /tce/boot/vmlinuz append loglevel=3
initrd /tce/boot/core.gz
}
^^ I am getting CLI. X wont start. startx says command not found

Recommended repair did nothing.
 
Old 01-11-2017, 09:50 AM   #15
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,952

Rep: Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148Reputation: 2148
Quote:
Originally Posted by hifi100 View Post
Code:
menuentry "Tiny Core" {
set root='hd0,msdos3'
linux /tce/boot/vmlinuz append loglevel=3
initrd /tce/boot/core.gz
}
^^ I am getting CLI. X wont start. startx says command not found

Recommended repair did nothing.
you must be missing xinit that has startx in it. In other words, xinit is not installed on whatever system you got that error message in.

Last edited by BW-userx; 01-11-2017 at 09:52 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Tiny rugged mini-PC runs Linux on dual-core 1.6GHz Atom LXer Syndicated Linux News 0 08-03-2013 02:41 AM
LXer: Tiny Pico-ITX board packs dual-core Atom punch LXer Syndicated Linux News 0 04-09-2013 10:50 PM
LXer: Tiny Core Linux 4.2 Introduces Tiny Core Plus LXer Syndicated Linux News 0 12-27-2011 09:30 AM
LXer: Tiny home theater PC has dual-core Via CPU, IR remote LXer Syndicated Linux News 0 10-14-2011 08:42 PM
Fedora Core 3 and Debian 3.0 r4 dual-boot problem norus Linux - Newbie 5 03-17-2005 03:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 01:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration