How to install dcore

[kircanov]

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

[kircanov]

This is my last stage


any helps will welcome...

[patrikg]

Don't rename the file.
Syslinux conf file is named extlinux.conf.

[Stefann]

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:

Code: [Select]

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.

[Stefann]

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.

[Rich]

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:

Code: [Select]

cat /proc/cmdline

[Stefann]

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:

Code: [Select]

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.

[kircanov]

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:


any helps will welcome...

[Stefann]

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.

[kircanov]

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.

[Stefann]

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.

[patrikg]

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:

Code: [Select]

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.

Code: [Select]

root=/dev/ram0Can be also used.
or

Code: [Select]

root=/dev/ram