| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dcore:upgrading_kernel_and_initrd [2016/05/30 11:25] – [dCore Initrd Updates] nitram | dcore:upgrading_kernel_and_initrd [2016/12/01 07:48] (current) – [dCore Kernel Updates] nitram |
|---|
| ==== dCore Kernel Updates ==== | ==== dCore Kernel Updates ==== |
| |
| As dCore kernel updates are rare there is no automated system to check and apply updates. Although the ''uname -a'' command is useful, it does not provide helpful information regarding dCore kernel updates. The latest dCore kernels can be manually downloaded from dCore's site ([[http://tinycorelinux.net/dCore/x86/release/|stable releases]], [[http://tinycorelinux.net/dCore/x86/release_candidates/|release candidates]]) using a web browser or wget. Depending on permissions of the directory, sudo may be needed. Example: | The kernel used by a dCore port is based on the most recent Tiny Core Linux kernel available when the port is prepared for release, not the Debian or Ubuntu release kernel. It is, however, rebuilt specifically for the dCore port with any custom configuration that may be required, such as systemd-related issues. The kernel config, patched source and READMEs can be found at http://tinycorelinux.net/dCore/x86/import/src/. As kernels provided by dCore have specifically been created to work with the applicable dCore port, ''sce-import'' should not be used to import a Debian or Ubuntu kernel to use with dCore. |
| | |
| | To keep the kernel compact, numerous kernel modules are prepared and provided separately, such as alsa-modules, bluetooth, graphics, touchscreen, netfilter, scsi, usb-serial, virtualbox, wireless, etc. To view available kernel modules run [[http://wiki.tinycorelinux.net/dcore:sce-searchprebuilt_command|sce-searchprebuilt]] or perform an [[http://wiki.tinycorelinux.net/dcore:sce-import_command|sce-import]] search using the -c (contains option) with the kernel version in use and the keyword 'tinycore', example, ''sce-import -cb 4.2.9-tinycore''. The -b option used in the example ensures any imported kernel modules are loaded at boot, which is recommended to enable the required functionality. If uncertain run ''uname -a'' or ''uname -r'' and confirm the dCore system's kernel version to ensure compatibility before importing modules. |
| | |
| | These older supported dCore ports use the 3.16.6 kernel: |
| | *dCore-jessie |
| | *dCore-trusty |
| | *dCore-wheezy |
| | |
| | More recent dCore ports use the 4.2.9 kernel, the same kernel version used in Tiny Core Linux v7: |
| | *dCore-stretch |
| | *dCore-xenial |
| | *dCore-yakkety |
| | |
| | To provide stability kernels are not updated during the lifespan of the dCore port. It is, therefore, not necessary to check for or apply kernel updates. Similar to most Linux distributions, users with newer hardware should consider utilizing the newest dCore port available. |
| | |
| | Current dCore kernel and associated initrd files, the only two files needed to get a working system, can be manually downloaded from dCore ports ([[http://tinycorelinux.net/dCore/x86/release/|stable releases]], [[http://tinycorelinux.net/dCore/x86/release_candidates/|release candidates]]) using a web browser or wget. Depending on permissions of the directory, sudo may be needed. Example: |
| <code Bash>wget http://tinycorelinux.net/dCore/x86/release/dCore-trusty/vmlinuz-trusty</code> | <code Bash>wget http://tinycorelinux.net/dCore/x86/release/dCore-trusty/vmlinuz-trusty</code> |
| |
| As dCore boots to RAM, manually updating the kernel is simple: | As dCore boots to RAM, manually replacing a kernel is simple: |
| *Download updated kernel. | *Download new kernel. |
| | *Recommend backing up old kernel. |
| *Replace the old kernel in dCore's boot directory. | *Replace the old kernel in dCore's boot directory. |
| *Recommend backing up old kernel. | *Reboot system to use the new kernel. |
| *Reboot system for the update to take effect. | |
| | Ensure the kernel and initrd files utilized are both from the same dCore port. Users upgrading to a newer dCore port will need to ensure the boot loader configuration file is appropriately updated. Updating to a new dCore port is essentially a new install, a fresh /tce directory should be utilized and any desired SCEs will need to be re-imported. |
| | |
| | **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** |
| |
| ==== dCore Initrd Updates ==== | ==== dCore Initrd Updates ==== |
| |
| Rapid dCore development may result in frequent initrd updates to provide bug fixes and add new features, particularly if tracking release candidates. Running the ''version -c'' command checks if running the latest release and ''version -r'' checks if running the latest release candidate. If a dCore system update is available, permission is requested to wget the latest dCore-*.gz and md5sum files to the boot directory specified in /etc/sysconfig/boot_path. Review the notes contained in /etc/sysconfig/boot_path to properly configure the file. Reboot to apply the update. | Rapid dCore development may result in frequent initrd updates to provide bug fixes and add new features, particularly if tracking release candidates. Running the ''version -c'' command checks if running the latest release and ''version -r'' checks if running the latest release candidate. If a dCore system update is available, permission is requested to wget the latest dCore-*.gz and md5sum files to the boot directory specified in /etc/sysconfig/boot_path. Review the comments in /etc/sysconfig/boot_path to properly configure the file. Reboot to apply the update. |
| |
| Usage options from the 'version –help' command: | Usage options from the 'version –help' command: |
| Reboot system to complete the update. | Reboot system to complete the update. |
| Usage: | Usage: |
| version List running dCore name and version. | version Display dCore name and version being utilized. |
| version -c Check if running the latest stable release, if different version | version -c Check if using the latest stable release, if different version |
| available prompted to download, wget latest stable release and | available prompted to download, wget latest stable release and |
| md5.txt file to directory specified in /etc/sysconfig/boot_path. | md5.txt file to directory specified in /etc/sysconfig/boot_path. |
| version -r Check if running the latest release candidate, if an update is | version -r Check if using the latest release candidate, if an update is |
| available prompted to download, wget latest release candidate and | available prompted to download, wget latest release candidate and |
| md5.txt file to directory specified in /etc/sysconfig/boot_path. | md5.txt file to directory specified in /etc/sysconfig/boot_path. |
| version -l List running dCore name and version. | version -l Display dCore name and version being utilized. |
| version -s See dCore version only. | version -s Display dCore version being utilized. |
| |
| Alternatively, initrd updates can be manually downloaded from [[http://tinycorelinux.net/ports.html|dCore ports.]] via web browser or wget. Depending on permissions of the directory, ''sudo'' may be needed. Example: | Alternatively, initrd updates can be manually downloaded from [[http://tinycorelinux.net/ports.html|dCore ports.]] via web browser or wget. Depending on permissions of the directory, ''sudo'' may be needed. Example: |
| <code Bash>wget http://tinycorelinux.net/dCore/x86/release/dCore-trusty/dCore-trusty.gz</code> | <code Bash>wget http://tinycorelinux.net/dCore/x86/release/dCore-trusty/dCore-trusty.gz</code> |
| |
| Similar to manually installing an updated dCore kernel, users wishing to manually update the initrd file may: | To manually update the initrd file: |
| *Download updated initrd file. | *Download updated initrd file. |
| *Replace the old initrd file in dCore's boot directory. | *Replace the old initrd file in dCore's boot directory. |
