Tiny Core Base > piCore Test Releases
piCore-12.0alpha1
aus9:
some minor feedback for arm7l not aarch64.
1) I use a distro to flash the image using dd and that distro automounts freshly created or installed media.
It detects 2 partitions but thinks it should be called piCore11. As sdcards do look the same and I now have a few, I inserted aarch64 which says piCore64_12 and my original 11x says its piCore11.
2) Key generation is really fast, relative to 11x arm7
but I have to press the enter key to get a prompt, do we need an exit command?
I am still so new to this key gen stuff.....I am never too sure how long to wait but
--- Code: ---filetool.sh -b
cat /opt/.filetool.lst
# shows 8 keys in backup which I think is right
--- End code ---
trivia.....hold shift page up works. keg gen seems to use this order, not sure if the string change
rsa.......dsa......ecdsa......ed<string>
3) using ssh commands
--- Code: ---tce-load -w -i Xorg Xlibs flwm aterm wbar nano
cat /mnt/mmcblk0p2/tce/onboot.lst
openssh.tcz
Xorg.tcz
flwm.tcz
aterm.tcz
wbar.tcz
nano.tcz
--- End code ---
on RPi
--- Code: ---startx
--- End code ---
-> gives me a desktop
WOOHOO
oops forgot to expand p2
aus9:
expanded parttiton2 complete, firefox working as I am typing on it ATM
If I open aterm, file:///home/tc/.Xdefaults looks correct. white foreground on black bg
If I run a download thru Apps, aterm opens but shows black foreground on black bg
any clues where to change?
2) I have only one RPi (a 4) first sound check is good
--- Code: ---speaker-test -D default:Headphones
--- End code ---
aus9:
I am normally on ethernet but just tested wifi on arm7l, it works as I type with eth cable pulled.
I have wifi, so this is a casual remark in case the kernel can be tweaked?
--- Code: ---dmesg | grep 509
[ 0.000000] Memory: 3848180K/4050944K available (10240K kernel code, 725K rwdata, 2736K rodata, 2048K init, 851K bss, 137228K reserved, 65536K cma-reserved, 3264512K highmem)
[ 1.194504] Asymmetric key parser 'x509' registered
[ 1.487415] Loading compiled-in X.509 certificates
[ 57.397279] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 57.442509] WARNING: CPU: 2 PID: 2179 at crypto/rsa-pkcs1pad.c:539 pkcs1pad_verify+0x158/0x174
[ 57.442630] [<c064306c>] (public_key_verify_signature) from [<c06448cc>] (x509_check_for_self_signed+0xcc/0x128)
[ 57.442641] [<c0644800>] (x509_check_for_self_signed) from [<c0643cc0>] (x509_cert_parse+0x178/0x1c8)
[ 57.442651] [<c0643b48>] (x509_cert_parse) from [<c064454c>] (x509_key_preparse+0x20/0x1a4)
[ 57.442662] [<c064452c>] (x509_key_preparse) from [<c0641fac>] (asymmetric_key_preparse+0x60/0x90)
[ 57.443101] cfg80211: Problem loading in-kernel X.509 certificate (-22)
--- End code ---
A search of "problem loading etc" which may be completely irrelevant as its a diff distro suggests that a kernel had to change.
bug as reported = EFI: Problem loading in-kernel X.509 certificate
https://bugzilla.redhat.com/show_bug.cgi?id=1075966
That reporter ....reported as they wanted
--- Quote ---Flawless/Clean boot with no warnings/errors
--- End quote ---
I don't see EFI but I do see Problem loading in-kernel X.509 certificate
so suggest it in case it helps a future kernel re-compile?
As I have a desktop, ca-certificates is loaded by recursive dep of xorg-server
Rich:
Hi Paul_123
Emphasis mine:
--- Quote from: Paul_123 on August 28, 2020, 12:39:25 PM --- ... Also, from your above example. this is not correct.
--- Code: ---export CFLAGS="gcc -march=armv8-a+crc -mtune=cortex-a72 -Os -pipe"
export CXXFLAGS="g++ -march=armv8-a+crc -mtune=cortex-a72 -Os -pipe -fno-exceptions -fno-rtti"
--- End code ---
CFLAGS should not include the compiler reference
--- Code: ---export CFLAGS="-march=armv8-a+crc -mtune=cortex-a72 -Os -pipe"
export CXXFLAGS="-march=armv8-a+crc -mtune=cortex-a72 -Os -pipe -fno-exceptions -fno-rtti"
--- End code ---
...
--- End quote ---
I can attest to the fact that including a compiler reference in the flags can cause problems. I recently ran into this problem (again)
while trying to run configure for a package from a build script. Running it from the command line it ran fine. That made it easy to
pinpoint the culprit in the build script.
I did notice this in the configure help:
--- Code: ---tc@E310:~/BuildTCZs/Setxkbmap/setxkbmap$ ./configure --help
`configure' configures setxkbmap 1.3.2 to adapt to many kinds of systems.
----- Snip -----
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
LIBS libraries to pass to the linker, e.g. -l<library>
CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
CPP C preprocessor
--- End code ---
They list CPPFLAGS but not CXXFLAGS , so I added this to my build script:
--- Code: ---CPPFLAGS=$CXXFLAGS
--- End code ---
mortegai:
Missing bc for aarch64.
To recompile the kernel for aarch64 bc is needed, and the extension bc.tcz does not exist for that arch.
Please, could you create it?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version