WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

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

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12861
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #15 on: January 07, 2021, 06:57:43 AM »
Xorg works now, and I can compile and build a few extensions but not many. I would think that for any extension its associated -dev extension would be available too, since they're mostly header files. Mirrors.tcz might be helpful too.

copied over

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12861
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #16 on: January 07, 2021, 06:58:21 AM »
And, correspondingly, Xfbdev wants libXfont.so to start ...
And Xvesa the same.

copied over

Offline andyj

  • Hero Member
  • *****
  • Posts: 942
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #17 on: January 08, 2021, 04:40:15 AM »
I saw this in the Slackware changelog:

Code: [Select]
k/kernel-source-5.10.5-noarch-1.txz: Upgraded.
       We'll turn off the silent stream feature as there's a known deadlock bug that
       remains in 5.10.5. Perhaps we'll restore it once that's patched... but we
       made it this far without the feature so I'll probably wait for a case to be
       made for it. Thanks to Petri Kaukasoina.
       Also build the intelfb module. This doesn't have anything to do with the
       lockups occurring on Intel systems, but we might as well provide the module.
       It remains blacklisted by default.
       FB_INTEL n -> m
       SND_HDA_INTEL_HDMI_SILENT_STREAM y -> n
       +FB_INTEL_DEBUG n
       +FB_INTEL_I2C y

Is this going to be a problem for TC 12?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10417
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #18 on: January 08, 2021, 09:24:17 AM »
# CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM is not set
The only barriers that can stop you are the ones you create yourself.

Offline andyj

  • Hero Member
  • *****
  • Posts: 942
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #19 on: January 10, 2021, 02:04:53 PM »
Good. For some reason I can't seem to find the kernel source or config files. Where would these be?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10417
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #20 on: January 11, 2021, 12:03:26 AM »
I think they aren't yet posted as we weren't sure if the modprobe error was to be fixed in kernel or not.
The only barriers that can stop you are the ones you create yourself.

Offline andyj

  • Hero Member
  • *****
  • Posts: 942
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #21 on: January 11, 2021, 05:02:50 AM »
I read it as a busybox issue. Did I misread that?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10417
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #22 on: January 11, 2021, 09:37:03 AM »
Denys blames kernel, kernel programmer blames busybox.
The only barriers that can stop you are the ones you create yourself.

Offline jazzbiker

  • Hero Member
  • *****
  • Posts: 518
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #23 on: January 11, 2021, 10:22:32 AM »
This "Module has invalid ELF header" messages are seen only in the initial console. The action, which will cause this messages in concole, in the terminal emulator under X don't show this messages. For example
Code: [Select]
tce-load -i wifi
performed before startx shows a lot of such messages, while started ubder Xfbdev in st executes smoothly.

What does this means? Messages are output device dependent? My guess is that they are emitted by kernel.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10417
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #24 on: January 11, 2021, 11:55:23 PM »
Yes, the message comes from the kernel. The point of contention is the mechanism.
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 #25 on: January 12, 2021, 12:29:02 PM »
Testing/playing with TC12_x64, all good until now (except already reported harmless "invalid ELF header" messages).
But I need to copy kmaps.tcz (for UK keyboard) and firmware-rtlwifi.tcz (for wifi rtl8723be) from TC11. And I write this from win10, because no minimal web-browser (yet) in TC12.

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 8789
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #26 on: January 12, 2021, 01:23:22 PM »
Hi nick65go
... because no minimal web-browser (yet) in TC12.
You should be able to get firefox using the following:
http://repo.tinycorelinux.net/11.x/x86/tcz/firefox_getLatest.tcz.info

Offline nick65go

  • Sr. Member
  • ****
  • Posts: 413
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #27 on: January 12, 2021, 01:45:00 PM »
I could try, but I am afraid that I will add/poluate a lot of tcz manualy imported from TC11.My undestranding is that firefox_getlatest.tcz only build firefox.* (tcz, dep) but will not download all dependency necesary for firefox.exe to run.
Maybe a simple (low dependency web-browser) solution will come in my mind.I already have in TC11_x64 the firefox 84.02 + its deps.

PS: If I remember correctly firefox from Alpinelinux has less dependencies (they adjust a text file from firefox folder...which list its dependencies; or I saw this in win10 when I manualy un-ziped firefox into an random folder and run it from there directly).
« Last Edit: January 12, 2021, 02:00:40 PM by nick65go »

Offline nick65go

  • Sr. Member
  • ****
  • Posts: 413
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #28 on: January 12, 2021, 03:28:44 PM »
Anyway. I manually add few tcz which are not yet in TC12 (gdk-pixbuf2.tcz, gamin.tcz) and firefox is running.

With this kernel version 5.10.3, for my CPU = AMD A6-6310 APU with AMD Radeon R4 Graphics, (core GCN 1.x or 2x?)
Is anything else that I can do to have amdpgu instead of radeon as video card driver?
because unfortunately radeon is detected/loaded first and not amdgpu.

Code: [Select]
tc@box:~$ lsmod | grep radeon
radeon                991232  0
drm_kms_helper        114688  1 radeon
ttm                    53248  1 radeon
drm                   286720  3 radeon,drm_kms_helper,ttm
backlight              12288  3 radeon,drm,video
Code: [Select]
Filesystem                Size      Used Available Use% Mounted on
/dev/loop4                8.5M      8.5M         0 100% /tmp/tcloop/firmware-amdgpu
/dev/loop32               3.1M      3.1M         0 100% /tmp/tcloop/graphics-5.10.3-tinycore64
/dev/loop33              64.0K     64.0K         0 100% /tmp/tcloop/xf86-video-amdgpu
but from dmesg
Code: [Select]
Linux version 5.10.3-tinycore64 (root@box) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #2021 SMP Mon Dec 28 16:17:51 UTC 2020
Command line: BOOT_IMAGE=/boot/tc12/vmlinuz64 tce=sda8/tce laptop pcie_aspm=force radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1
..
[drm] radeon kernel modesetting enabled.
radeon 0000:00:01.0: CIK support disabled by module param
no MTRR for c0000000,1000000 found   <-- is my UEFI buggy?

EDIT: even after I did
Code: [Select]
oot@box:/home/tc# modprobe amdgpu
root@box:/home/tc# modprobe -r radeon
root@box:/home/tc# lsmod | grep radeon
root@box:/home/tc# lsmod | grep amdgpu
amdgpu               3342336  0
gpu_sched              16384  1 amdgpu
drm_kms_helper        114688  1 amdgpu
ttm                    53248  1 amdgpu
drm                   286720  4 amdgpu,gpu_sched,drm_kms_helper,ttm
backlight              12288  3 amdgpu,drm,video

then Exit to console, and again startx, I have VESA not amdgpu driver (because Xorg is compiled with radeon in mind, not with amdgpu)
Code: [Select]
[  2940.013]     ABI class: X.Org Server Extension, version 10.0
[  2940.013] (==) Matched ati as autoconfigured driver 0
[  2940.013] (==) Matched modesetting as autoconfigured driver 1
[  2940.013] (==) Matched fbdev as autoconfigured driver 2
[  2940.013] (==) Matched vesa as autoconfigured driver 3
[  2940.013] (==) Assigned the driver to the xf86ConfigLayout
[  2940.013] (II) LoadModule: "ati"
[  2940.013] (WW) Warning, couldn't open module ati
[  2940.014] (EE) Failed to load module "ati" (module does not exist, 0)
« Last Edit: January 12, 2021, 03:47:22 PM by nick65go »

Offline xor

  • Hero Member
  • *****
  • Posts: 891
Re: Tiny Core 12.0 Alpha 1 Testing
« Reply #29 on: January 12, 2021, 09:49:40 PM »
http://forum.tinycorelinux.net/index.php/topic,24551.msg155804.html#msg155804

kernel 5.1x. AMDGPU Radeon

Quote
- AMDGPU DC display support for GCN 1.0 "Southern Islands" graphics processors. AMDGPU DC for GCN 1.0 was one of the lingering missing items that remained for potentially enabling AMDGPU support by default for GCN 1.0/1.1 era hardware in place of the Radeon DRM driver. The last apparent blocker though is the lack of analog output support with AMDGPU DC and so for that no default change has been made. Those with these aging Radeon HD 7000 series graphics cards and other select GCN 1.0/1.1 products can boot their kernel with "amdgpu.cik_support=1 amdgpu.si_support=1 radeon.cik_support=0 radeon.si_support=0" to enjoy the AMDGPU kernel driver by default that also means working Vulkan support, possible performance improvements, and just enjoying the more modern code-base.  https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.10-Feature-Recap

« Last Edit: January 12, 2021, 09:52:12 PM by xor »