Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore x86_64 => Topic started by: kircanov on September 07, 2024, 01:04:57 PM
-
I'm new to this.. Can someone explain the dcore installation procedure to me in detail. I create a VM on Proxmox with a 10GB disk, I boot the installation through netboot.xyz, I select dcore. Now how to create a partition and how much. How to copy boot and from where? Also cat /etc/fstabsudo doesn't work, with mount /mnt/sr0 I don't see files. Can anyone describe a full installation with netboot.xyz and Proxmox.
-
Hi kircanov
Welcome to the forum.
I've never used dcore so the best I can offer is the Wiki:
https://wiki.tinycorelinux.net/doku.php?id=dcore:welcome
This appears to be the section that covers installation options.
https://wiki.tinycorelinux.net/doku.php?id=dcore:installations
-
I have visited these links and can tell that many installation steps are missing. It's more like they're just main commands. There is no TC support on the internet, much less on the official site, I just can't figure it out. That's why I asked in detail if anyone has been in Linux for a long time and knows how to install dCore on proxmox via netboot.xyz. I found some commands but I can't understand what is the size of the partition that I create through fdisk. Admittedly, I don't have much experience with fdisk under a terminal. I found a link for VM installation in VirtualBox, but I'm not using CDROM, I'm using netboot. Otherwise, I want to try dCore with a desktop because it supports packages from ubuntu and debian, and the size is small to use more images on my home proxmox server.
-
Hi kircanov
I took a quick look at:
http://tinycorelinux.net/dCore/x86_64/release/dCore-stretch64/
It sounds like you just want the files needed for booting.
That would be the kernel:
http://tinycorelinux.net/dCore/x86_64/release/dCore-stretch64/vmlinuz-stretch64
And the initrd. You mentioned you want a desktop, which should be in here:
http://tinycorelinux.net/dCore/x86_64/release/dCore-stretch64/dCorePlus-stretch64.gz
Sorry, can't help with proxmox or netboot.xyz. I only run on real
hardware booting from local storage.
-
Hi kircanov
... I can't understand what is the size of the partition that I create through fdisk. ...
Personally, I avoid using fdisk myself. I see no reason to memorize or lookup
cryptic commands for a task I don't perform very often, especially since I use
a desktop.
If I need to do any partition operations, I use gparted. I have no interest in
dealing with cylinders, heads, sectors, or blocks on that level if I don't have to.
While it is still your responsibility to point gparted at the correct device, options
like sizing, format type, labels, partition flags, etc are at least easy to specify.
-
Thanks for quickly replay @Rich, but the problem is location of netboot installer location..
i need to copy /boot from the netboot drive (which i don't know which one it is) and i don't know how to find what that drive is. For now I can create partition /dev/sda1 and /dev/sda2 (swap) but I don't know how to find the boot from the netboot install to copy it to /etc/sda1/boot. then the rest I guess should be easy with tce-setdrive and sce-import -b xorg-all for desktop. The problem is that I don't know where the netboot installation is. And it's not under /mnt/sr0.
-
I lost almost all day without success... I tried also CD-ROM steps, copping the boot files from installation media URL: http://www.tinycorelinux.net/dCore/x86_64/release/dCore-stretch64/ so i don't know how to setup boot path from HDD. I have used this steps from URL https://brianlinkletter.com/2016/05/how-to-install-dcore-linux-in-a-virtual-machine/ but probably dCore-stretch use les files and commands not response. Finally here is my screen after reboot...
Great respect to Rich (Administrator), but here we need someone who good understand dCore because this is dCore forum section.
-
When netbooting the ordinary way of doing this should be using nfs.
I have done this successful in picore.
So the boot order will be:
1. kernel
2. initrd
3. root via nfs.
Here are my kernel args list from my old nfs mount in picore:
console=ttyAMA0,115200 root=/dev/ram0 elevator=deadline rootwait nortc loglevel=3 noembed tz=CET-1CEST,M3.5.0,M10.5.0/3 kmap=qwerty/sv-latin1 lang=sv_SE showapps bcm2708.boardrev=0x2 bcm2708.serial=0x1234560b nfsmount=10.42.0.1:/home/patrik/picore/ tce=nfs/tce8
-
Looks like we don't understand each other... I'm booting a system via netboot but where to look for the source files from netboot..
if i try 'ls /mnt'
i only get 'sr0' but there are no files inside there, and when i can't find the source, i can't copy kernel, initrd, root...etc.
And as for dCore-stretch64, you have a problem with repository, because nothing downloads, updates...
-
That service looks like it provides files via http, aka they are not mounted or available after boot anywhere.
-
but here we need someone who good understand dCore because this is dCore forum section.
in the absence of of *someone who good understand dCore* (and can explain it! ;- )
perhaps??
the other topics/post in `dCore forum section.`
can provide a/some insight ?
of those who previously tried to use/understand dcore ...
-
If I understand correctly there is no way to install via netboot. So the Tiny dCore system is located in RAM memory, so until I want to install it, I will need to download the necessary boot files from the official site via WGET. vmlinuz, dCore-[os].gs, boot, etc.. If possible link from CD or USB installation source. But it is not .ISO format, but unpacked. Can someone provided source from Bionic or Buster.
Thank you...
-
Hi kircanov
... I will need to download the necessary boot files from the official site via WGET. vmlinuz, dCore-[os].gs ...
That's vmlinuz-[os] and dCore-[os].gz.
... Can someone provided source from Bionic or Buster.
You can find the bionic, buster, focal, and stretch directories here:
http://tinycorelinux.net/dCore/x86_64/release/
-
anyway but i can't manage to install and boot dCore from local harddisk.
here are the steps I use (CD installation) disk 6gb (783):
sudo fdisk /dev/sda
SDA1
n
p
1
1
553
SDA2
n
p
1
554
783
a
1
t
2
82 --- (linux snap partition)
w
sudo mkfs.ext4 /dev/sda1
sudo rebuildfstab
mount /mnt/sda1
sudo mkdir /mnt/sda1/boot
mount /mnt/sr0
ls /mnt/sr0
sudo cp -p /mnt/sr0/* /mnt/sda1/boot
Install a bootloader
----------------------------------
sce - import e2fsprogs
sce - load e2fsprogs
sudo e2label /dev/sda1 "dCore"
sudo rebuildfstab
sudo mkdir /mnt/sda1/boot/extlinux
sce-import extlinux
sce-load extlinux
sudo extlinux --install /mnt/sda1/boot/extlinux
sudo dd if=/usr/lib/EXTLINUX/mbr.bin of=/dev/sda
Create a bootloader configuration file
-------------------------------------------------- --------
cd /mnt/sda1/boot/extlinux
sudo vi extlinux.conf
default dCore
label dCore
kernel /boot/vmlinuzbuster64
append initrd=/boot/dCorebuster64.gz tce=sda1
tce-setdrive
selected /mnt/sda1
backup
sudo poweroff
removing CD image and starting the VM but without success
-
Is this write off your settings ?
So you missed some part in the syslinux conf file.
Shouldn't it be "initrd" on one line and "append" on another line with more kernel args like root=/dev/sda1 and so on.
Something like this:
TIMEOUT 30
DEFAULT tinycore
MENU TITLE Boot Menu
LABEL tinycore
MENU LABEL Tiny Core
LINUX /boot/vmlinuzbuster64
INITRD /boot/dCorebuster64.gz
APPEND root=/dev/sda1 tce=sda1
-
hello patrikg
i am little confused with syslinux conf, in my case i have extlinux.conf... i try renamed extlinux.conf to syslinux.conf with your update, but still no success to boot from drive.
my extlinux directory looking like this:
ldlinux.conf ->(my ex extlinux.conf)
ldlinux.sys
ldlinux.c32
my ldlinux.conf
TIMEOUT 30
DEFAULT tinycore
MENU TITLE Boot Menu
LABEL tinycore
MENU LABEL Tiny Core
LINUX /boot/vmlinuzbuster64
INITRD /boot/dCorebuster64.gz
APPEND root=/dev/sda1 tce=sda1
-
This is my last stage
(https://hostnetcorp.com/TC-sCore-hdd-no-boot.PNG)
any helps will welcome...
-
Don't rename the file.
Syslinux conf file is named extlinux.conf.
-
Is this write off your settings ?
So you missed some part in the syslinux conf file.
Shouldn't it be "initrd" on one line and "append" on another line with more kernel args like root=/dev/sda1 and so on.
Something like this:
TIMEOUT 30
DEFAULT tinycore
MENU TITLE Boot Menu
LABEL tinycore
MENU LABEL Tiny Core
LINUX /boot/vmlinuzbuster64
INITRD /boot/dCorebuster64.gz
APPEND root=/dev/sda1 tce=sda1
Root=xxxxx is not a bootcode that I am aware of.
Can at least not find it at the homepage faq and also not in the book.
-
Additionally….
You already have it working from cd?
In text mode?
Why not “while running from cd” try to start x and a desktop, like flwm. Download the necessary packages from the package manager.
Also install the install tool
Than install on harddisk using the tiny core install tool.
That works like a charm and makes sure you have all recommended settings.
I basically did the same t9 get mine working.
- did took me significant effort to get the first working.
- but once I had it working making new disk and usb bootable drives was super easy.
When in textmode you can I think also just run the install tool in textmode. It’s just that the gui version works more convenient, more self explaining.
You will need to download the package though by using the apps browser which is also “not super easy” in textmode.
-
Hi Stefann
root= is a boot code:
https://mjmwired.net/kernel/Documentation/kernel-parameters.txt#3749
... Can at least not find it at the homepage faq ...
Those "boot codes" are for Tinycore. Any boot code the kernel does not recognize
gets ignored. if you look at /etc/init.d/tc-config you'll find that it deals with its own
boot codes by parsing /proc/cmdline.
Enter this command and you'll see which boot codes were used on your system:
cat /proc/cmdline
-
Hi Stefann
root= is a boot code:
https://mjmwired.net/kernel/Documentation/kernel-parameters.txt#3749
... Can at least not find it at the homepage faq ...
Those "boot codes" are for Tinycore. Any boot code the kernel does not recognize
gets ignored. if you look at /etc/init.d/tc-config you'll find that it deals with its own
boot codes by parsing /proc/cmdline.
Enter this command and you'll see which boot codes were used on your system:
cat /proc/cmdline
Holy moly…. What an about endless list….. pfff….
But ehhh… than using the root=xxx bootcode I consider extremely sad. The full idea of tinycore running in ram with kernel mounted from compressed file is gone than.
-
finally i installed it somehow and now it boots from harddisk but no desktop. I think it downloads files for x86 Come on some help with the desktop.
What I did:
I made an xdesk file as an extension
the file contains this:
Xprogs
xorg-all
wbar
flwm
midori
then i import it
sce-import -lb /xdesk
I check if the extension is there
cat /etc/sysconfig/tcedir/sceboot.lst
should be displayed
xdesk
then it remains to add it to boot desktop=flwm
the thigh should look like this:
append initrd=/boot/dCorebuster64.gz tce=sda1 desktop=flwm
this is the error i am getting:
(https://hostnetcorp.com/TC-sCore-desktop-error.PNG)
any helps will welcome...
-
If it boots from harddisk you van put the tinycore or coreplus iso on the disk and boot the kernel from there by modifying the extlinux.conf.
You could not do that on the cd as that was read only I guess.
What I try to say: you are now manually trying to reconstruct the tinycore suite from the textbased basic core. That is of course possible by adding the correct apps but is quite painful. Using the “preconfigured iso” brings less trouble.
And with that said, please check again on whether you are sure you want to use bootcode root=xxx. As I mentioned earlier I feel doing throws the main advantage of tinycore in the bin.
-
If it boots from harddisk you van put the tinycore or coreplus iso on the disk and boot the kernel from there by modifying the extlinux.conf.
You could not do that on the cd as that was read only I guess.
What I try to say: you are now manually trying to reconstruct the tinycore suite from the textbased basic core. That is of course possible by adding the correct apps but is quite painful. Using the “preconfigured iso” brings less trouble.
And with that said, please check again on whether you are sure you want to use bootcode root=xxx. As I mentioned earlier I feel doing throws the main advantage of tinycore in the bin.
Dude, I'm installing dCore.iso, I'm not trying to install Tinycore. You seem to have misunderstood what I am asking for help with. First I have 64 bit dCore installed. When I tried to add a desktop GUI, the 64-bit system simply downloaded files and files from the 32-bit system, and the error is that it cannot start because there is a problem with files and paths.
-
If it boots from harddisk you van put the tinycore or coreplus iso on the disk and boot the kernel from there by modifying the extlinux.conf.
You could not do that on the cd as that was read only I guess.
What I try to say: you are now manually trying to reconstruct the tinycore suite from the textbased basic core. That is of course possible by adding the correct apps but is quite painful. Using the “preconfigured iso” brings less trouble.
And with that said, please check again on whether you are sure you want to use bootcode root=xxx. As I mentioned earlier I feel doing throws the main advantage of tinycore in the bin.
Dude, I'm installing dCore.iso, I'm not trying to install Tinycore. You seem to have misunderstood what I am asking for help with. First I have 64 bit dCore installed. When I tried to add a desktop GUI, the 64-bit system simply downloaded files and files from the 32-bit system, and the error is that it cannot start because there is a problem with files and paths.
A.. got that wrong. I now better understand the whole thread.
Pardon me. I was just trying to help. It can be a steep learning curve to enter the eco system.
-
Hi Stefann
root= is a boot code:
https://mjmwired.net/kernel/Documentation/kernel-parameters.txt#3749
... Can at least not find it at the homepage faq ...
Those "boot codes" are for Tinycore. Any boot code the kernel does not recognize
gets ignored. if you look at /etc/init.d/tc-config you'll find that it deals with its own
boot codes by parsing /proc/cmdline.
Enter this command and you'll see which boot codes were used on your system:
cat /proc/cmdline
Holy moly…. What an about endless list….. pfff….
But ehhh… than using the root=xxx bootcode I consider extremely sad. The full idea of tinycore running in ram with kernel mounted from compressed file is gone than.
I was only using root as example of what command line kernel args and bootcodes.
root=/dev/ram0Can be also used.
or
root=/dev/ram