WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core 12.0 Alpha 1 Testing  (Read 1855 times)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10417
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #30 on: January 13, 2021, 12:00:30 AM »
The SI and CIK AMDGPU options are not enabled. The radeon module is what was intended for those cards, and gives them full functionality and less bugs. If you want amdgpu for some reason, you'll need a custom kernel.
The only barriers that can stop you are the ones you create yourself.

Offline nick65go

  • Sr. Member
  • ****
  • Posts: 413
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #31 on: January 13, 2021, 01:25:40 AM »
@curaga: Thanks for the clarification. It is not what I expected from a modern kernel 5.10.x, but at least now I know it is about kernel compile options that TC developers choose for their distribution.The radeon driver works OK (except insane default brightness). So I wanted to try/test amdgpu driver for my UEFI laptop, to see if it could have longer batery life, if not then better performance, etc.

Without radeon driver /dev/dri/card is not created by the kernel, so Xorg is not loading amdgpu.
Could you please copy/paste the few options from .config (for kernel) to be activated, so that amdgpu becoming default video driver?


Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12861
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #32 on: January 13, 2021, 03:20:25 AM »
Anyway. I manually add few tcz which are not yet in TC12 (gdk-pixbuf2.tcz, gamin.tcz) and firefox is running.

gdk-pixbuf2 was already in the tc-12.x repos, but gamin and firefox_getLatest (and kmaps) copied over
« Last Edit: January 13, 2021, 03:24:09 AM by Juanito »

Offline nick65go

  • Sr. Member
  • ****
  • Posts: 413
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #33 on: January 13, 2021, 03:45:39 AM »
Quote
gdk-pixbuf2 was already in the tc-12.x repos, but gamin and firefox_getLatest (and kmaps) copied over
maybe you are right, but now (13/01/2021 at 12:45 my time in Austria), they are not in http://tinycorelinux.net/12.x/x86_64/tcz/. looking from MS Windows10, so maybe just the list is not updated, but the tcz are in folder as invisible files.
« Last Edit: January 13, 2021, 03:50:01 AM by nick65go »

Offline nick65go

  • Sr. Member
  • ****
  • Posts: 413
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #34 on: January 13, 2021, 04:16:40 AM »
@xor: regarding "potentially enabling AMDGPU support by default for GCN 1.0/1.1 era hardware in place of the Radeon DRM driver."
from https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.10-Feature-Recap

it seams to me that my AMD A6-6310 APU [with AMD Radeon R4 Graphics] is type GCN 2.x (code CIK, or Sea Islands) acording to
https://www.x.org/wiki/RadeonFeature/#decoderringforengineeringvsmarketingnames
https://wiki.gentoo.org/wiki/AMDGPU#Kernel
https://wiki.archlinux.org/index.php/AMDGPU#Enable_Southern_Islands_(SI)_and_Sea_Islands_(CIK)_support



Offline nick65go

  • Sr. Member
  • ****
  • Posts: 413
Re: Tiny Core 12.0 Alpha 1 Testing; how to enable amdgpu CIK/SI?
« Reply #35 on: January 13, 2021, 05:42:22 AM »
The SI and CIK AMDGPU options are not enabled. The radeon module is what was intended for those cards, and gives them full functionality and less bugs. If you want amdgpu for some reason, you'll need a custom kernel.
find keywords AMDGPU (5 times) and RADEON (6 times) for kernel config in
https://git.alpinelinux.org/aports/tree/main/linux-lts/config-lts.x86_64
Code: [Select]
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set

CONFIG_DRM_RADEON=m
CONFIG_DRM_RADEON_USERPTR=y
CONFIG_DRM_AMDGPU=m
CONFIG_DRM_AMDGPU_SI=y
CONFIG_DRM_AMDGPU_CIK=y
# CONFIG_DRM_AMDGPU_USERPTR is not set
# CONFIG_DRM_AMDGPU_GART_DEBUGFS is not set

# ACP (Audio CoProcessor) Configuration
CONFIG_DRM_AMD_ACP=y

# Display Engine Configuration
CONFIG_DRM_AMD_DC=y
CONFIG_DRM_AMD_DC_DCN=y

CONFIG_HSA_AMD=y
Is anything else that I need to have options SI and CIK enabled for AMDGPU? Thanks in advance.
« Last Edit: January 13, 2021, 05:45:10 AM by nick65go »

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 8788
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #36 on: January 13, 2021, 07:24:40 AM »
Hi nick65go
In case you are not aware, kernel config files are not intended to be edited directly. Options interact. Use the command:
Code: [Select]
make menuconfigto make changes.

Select:
Device Drivers->Graphics support

And you will see the entries you need:



Offline GNUser

  • Hero Member
  • *****
  • Posts: 711
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #37 on: January 14, 2021, 11:45:56 AM »
I copied these extensions from my TCL11.1/tce/optional to TCL12.0/tce/optional and they work well:
gtk2.tcz
fuse.tcz
iproute2
iptables
openresolv
db
libdb
wireguard-tools

As I was expecting, I see that the linux kernel team now provides the  wireguard  kernel module:
Code: [Select]
TCL12$ tce-load -wi ipv6-netfilter-KERNEL
TCL12$ sudo modprobe ipv6
TCL12$ sudo modprobe wireguard # this works because the wireguard module is included in modules64.gz. Awesome!
I expect that by the time TCL12 is released, the TCL team will have separated out the wireguard kernel module into its own extension (wireguard-5.10.3-tinycore64.tcz). If that's the case, no changes will be needed to wireguard-tools.tcz.dep. If, on the other hand, the wireguard kernel module is part of TCL12 base system, then  wireguard-KERNEL.tcz  should be removed from  wireguard-tools.tcz.dep.

P.S. This post was made from TCL12 using firefox, a wifi connection, and a wireguard VPN connection.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10417
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #38 on: January 15, 2021, 01:03:45 AM »
It's small enough that probably it won't make sense to make an extension for it.
The only barriers that can stop you are the ones you create yourself.

Offline GNUser

  • Hero Member
  • *****
  • Posts: 711
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #39 on: January 15, 2021, 07:32:59 PM »
* the libffi and readline extensions have been updated - this will break a lot of extensions, so fallback libffi6 and readline7 extensions have been created.
I found three affected extensions so far among those I've copied over from TCL11.1 x86_64:
- libffi6.tcz should be appended to geany.tcz.dep and caja.tcz.dep
- readline7.tcz should be appended to gnupg.tcz.dep
« Last Edit: January 15, 2021, 07:43:27 PM by GNUser »

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12861
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #40 on: January 16, 2021, 03:14:32 AM »
I copied these extensions from my TCL11.1/tce/optional to TCL12.0/tce/optional and they work well:
gtk2.tcz
fuse.tcz
iproute2
iptables
openresolv
db
libdb
wireguard-tools

gtk2, fuse, iproute2, iptables and openresolve copied over - db was already there.

@curaga - do you mean add the wireguard module to the base or to wireguard-tools?

Offline $4dee25600200001001e

  • Full Member
  • ***
  • Posts: 114
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #41 on: January 16, 2021, 04:15:43 AM »
Although Vim is good, there are still a few people (mostly in countries that use hieroglyphics) who like vi, so I recommend adding Unicode support to BusyBox's vi. Note: BusyBox's vi editor does not support Unicode encoding.
« Last Edit: January 16, 2021, 04:18:29 AM by ONE »

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12861
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #42 on: January 16, 2021, 04:17:17 AM »
..but that will add bloat...

Offline $4dee25600200001001e

  • Full Member
  • ***
  • Posts: 114
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #43 on: January 16, 2021, 04:23:06 AM »
Ex-vi (also known as native vi) supports Unicode, but has a lot of problems, such as screen flickering, replacement mode...

Offline $4dee25600200001001e

  • Full Member
  • ***
  • Posts: 114
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #44 on: January 16, 2021, 04:25:43 AM »
..but that will add bloat...
You can do it as an extension, as a patch, but I won't or I'll do it, so more people can benefit from it.