| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Giving away a Pinebook Pr...
Forum: Pinebook Hardware and Accessories
Last Post: tuxifan
8 hours ago
» Replies: 0
» Views: 22
|
Armbian images available
Forum: Linux on RockPro64
Last Post: Shraunfnq
Yesterday, 10:16 AM
» Replies: 61
» Views: 114,429
|
Bare metal on Pinephone P...
Forum: PinePhone Pro Software
Last Post: alain
08-19-2025, 07:58 AM
» Replies: 0
» Views: 109
|
Seeking Contributors: Apa...
Forum: PinePhone Pro Software
Last Post: geometrylitegame12
08-19-2025, 01:38 AM
» Replies: 4
» Views: 4,014
|
Pinephone Pro wont boot t...
Forum: General Discussion of PinePhone Pro
Last Post: KC9UDX
08-18-2025, 06:15 PM
» Replies: 5
» Views: 308
|
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: Kevin Kofler
08-18-2025, 04:30 PM
» Replies: 8
» Views: 585
|
fixing the ppkb mainboard...
Forum: PinePhone Pro Accessories
Last Post: Jite
08-18-2025, 02:57 PM
» Replies: 2
» Views: 157
|
Are there plannes to crea...
Forum: PinePhone Pro Hardware
Last Post: biketool
08-18-2025, 04:12 AM
» Replies: 5
» Views: 1,028
|
Pinephone pro stuck while...
Forum: PinePhone Pro Hardware
Last Post: Supervisor
08-16-2025, 06:40 PM
» Replies: 2
» Views: 209
|
Compatible U.S. carriers ...
Forum: General Discussion on PinePhone
Last Post: Zebulon Walton
08-15-2025, 07:34 PM
» Replies: 2
» Views: 256
|
|
|
| Article: (Possibly) LVGL in WebAssembly with Zig Compiler |
|
Posted by: lupyuen - 05-30-2023, 12:25 AM - Forum: PinePhone Software
- No Replies
|
 |
Zig Compiler works great for compiling C Libraries into WebAssembly. Can we preview an LVGL App in the Web Browser… With WebAssembly and Zig Compiler?
Let’s find out! In this article we’ll…
(1) Run a Zig LVGL App on PinePhone (with Apache NuttX RTOS)
(2) Explain how Zig works with WebAssembly (and C Libraries)
(3) Compile LVGL Library from C to WebAssembly (with Zig Compiler)
(4) Test it with our LVGL App (in Zig)
(5) Render Simple LVGL UIs (in Web Browser)
(6) Later we might render LVGL UI Controls (with Touch Input)
Check out the article…
(Possibly) LVGL in WebAssembly with Zig Compiler
![[Image: lvgl3-title.png]](https://lupyuen.codeberg.page/images/lvgl3-title.png)
|
|
|
|
| Complete noob to the Pinephone 64, cannot set time and date. |
|
Posted by: gordr - 05-29-2023, 10:12 PM - Forum: General Discussion on PinePhone
- Replies (11)
|
 |
My new Pinephone 64 arrived today. I finally was able to do the Setup routine; it's not at all intuitive. I was able to make a call, so it connects with the network (Koodo in Alberta, Canada) OK. But I cannot get it to "see" the right time and date. Got the region set to America/Canada/Edmonton, so the time zone ought to be MOuntain Daylight time. Phone thinks it's something 3:15 A.M. on May 22, 2022. I know that ain't right. I have time/date set to automatic, so should it be pulling that off the cell tower? Changing time/date to "manual" didn't work, because I cannot make the wheels on that slot-machine display move in any sort of rational fashion by using the touch screen. I plugged in a keyboard via the hub, and was able to type letters and numbers into some fields, but the rolling number boxes for time/date are impervious to that. And my couple of hours of fruitless groping ran the battery down from 98% to 38%, so I have it on charge again.
It's running on the software that was on it when it came out of the box. No update as yet.
|
|
|
|
How do I compile an arbitrary kernel for U-Boot? |
|
Posted by: Valenoern - 05-29-2023, 09:39 PM - Forum: Linux on RockPro64
- Replies (3)
|
|
I have been trying to get a DVD drive to work with the RockPRO64, but for some reason the kernel is not properly operating the drive and the open/close button does not work.
I researched the problem, and it seems like this is a general problem with the Linux kernel or its modules on multiple architectures — some versions of the "linux" package in Manjaro/Arch properly provided CD drive support and some did not. So, now I simply have to compile kernels from source until I get the right one. [2]
The only problem is, after a week or so of trying to compile kernels and comb through source code for rockpro U-Boot packages I still have no idea how to compile a kernel for U-Boot that actually boots. I have tried "mkimage" and putting a regular compiled kernel stripped of debug information into mkimage, but the kernel always fails to boot and restarts the CPU. I read and re-read the documentation for the U-Boot packages and saw that I'm apparently supposed to have a kernel tree with "make uImage" or "make pImage", but none of the kernel.org trees had this so I'm not sure where to get this source tree. [1]
I am also confused where the blobless package "uboot-rockpro64-foss" finds the kernel if it does not install one to /boot, or in any case where my kernel is on disk after I boot into a Manjaro partition.
How do I compile a kernel from source into an "Image" file loaded by extlinux.conf?
Is that even the same kernel that loads when I boot my eMMC and run "uname -a" to describe the kernel? How do I compile and use a new one?
[1] edit 6/07: so, apparently new kernel trees have "make Image". I tried this with kernel version 6.4.0-rc4 and it did not boot past what seems to be the Secondary Program Loader (SPL).
[2] edit 6/17: well now I feel really stupid. The problem with the DVD drive was that I kept trying to plug it into a USB 2.0 port and it really needed a USB 3.0 port. I just never figured this out because I always had something else in the single one the ROCKPro has.
That said, it would still probably be helpful to people to know how to compile a kernel, so I will still test it if anybody figures out how. I have already been messing with creating distro images for a while now.
|
|
|
|
| Star64: a first benchmark |
|
Posted by: Der Geist der Maschine - 05-29-2023, 01:00 PM - Forum: Getting Started
- No Replies
|
 |
In these days, I play around with different kernel configs and patches. While doing so, I collected data about the star64's speed.
Build time Fishwaldo's kernel 5.15.107:
Code: $ make pine64_star64_defconfig
$ time make -jX Image modules starfive/jh7110-pine64-star64.dtb
or
Code: $ make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- pine64_star64_defconfig
$ time make -jX ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- Image modules starfive/jh7110-pine64-star64.dtb
Star64 4 cores (armbian 23.05, gcc 12.02.0) DOB 2023 - $130
Code: -j1: real 214m51.028s user 201m28.062s sys 12m31.241s
-j2: real 112m56.549s user 211m41.069s sys 12m18.304s
-j3: real 79m05.656s user 222m08.494s sys 12m28.384s
-j4: real 67m08.530s user 241m20.833s sys 13m57.011s
Lenovo G510 laptop i7-4700 2.4GHz 4 cores (8 threads) (debian 12, gcc 12.02.0) DOB 2014 - $754
Code: -j1: real 50m59.833s user 46m39.686s sys 4m14.694s
-j2:
-j3:
-j4: real 13m41.123s user 49m35.922s sys 4m22.633s
[we would probably get a little bit more when utilizing threads]
Apple imac7 desktop core2 extreme X7900 2 cores 2.8GHz (debian 12, gcc 12.02.0) DOB 2007, $10 from craigslist
Code: -j1: real 70m26.178s user 63m19.755s sys 6m34.567s
-j2: real 41m11.000s user 67m12.281s sys 7m27.264s
We have it that a 9 year old laptop is 4.91 times faster than the star64 and a 16 year old desktop is is 1.63 times faster than the star64 (real time on max number of cores).
Note, that is the OOB (out of box) experience for most of us. The star64 should be faster with additional investments for eMMC or NvME drives.
As of today, the graphics experience is quite frustrating, see https://forum.pine64.org/showthread.php?...pid=117576. That should eventually change.
|
|
|
|
| Followed the blog post to install Fedora: PBP not booting anymore |
|
Posted by: koenigs - 05-29-2023, 03:54 AM - Forum: General Discussion on Pinebook Pro
- Replies (6)
|
 |
Hi guys,
So I had Manjaro installed on my eMMC for a while now and I wanted to switch to Fedora.
I went to the official Wiki which redirects us to a blog post from 2021 which I followed.
I flashed the firmware to the micro SD Card
Code: $ sudo spi-flashing-disk --target=pinebook-pro-rk3399 --media=/dev/sdc1
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdc1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdc1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/sdc1 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
= Writing idbloader.img for pinebook-pro-rk3399 .... on media /dev/sdc1
348+0 records in
348+0 records out
178176 bytes (178 kB, 174 KiB) copied, 0.00409355 s, 43.5 MB/s
= Writing u-boot FIT image for pinebook-pro-rk3399 .... on media /dev/sdc1
2042+0 records in
2042+0 records out
1045504 bytes (1.0 MB, 1021 KiB) copied, 0.217239 s, 4.8 MB/s
umount: /tmp/fw: not mounted.
rmdir: failed to remove '/tmp/fw': Directory not empty
I didn't really pay attention to the error messages at the beginning nor at the end, I just saw that some data was copied to the micro SD card so I thought it was fine.
Then I opened the case of my Pinebook Pro, disabled the eMMC using the switch 24 (I should have just removed the eMMC actually).
Then I tried to boot with the micro SD card inserted and... absolutely nothing happened even after pluging in the DC barrel.
Now even with the micro SD card removed and the switch 24 enabled my PBP won't boot.
I tried to check the content of the micro SD card with my other laptop (I'm on Fedora) but I'm not able to mount it.
Code: $ sudo mount /dev/sdc1 /run/media/koenigs/sdcard
mount: /run/media/koenigs/sdcard: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
I don't even understand what went wrong actually, I didn't enter any command to flash the SPI with the firmware from the micro SD card, it just didn't do anything so I didn't even get the opportunity to try it...
Is there any way I can recover from the situation?
I'm a bit worried I screwed my SPI, it seems a bit tricky and risky to follow this procedure so I'd like to avoid it if possible.
Thanks for your answers
EDIT: I understand what I did wrong, I flashed the firmware to the partition sdc1
Code: $ sudo spi-flashing-disk --target=pinebook-pro-rk3399 --media=/dev/sdc1
I should have done it to the card card's disk scd instead
Code: $ sudo spi-flashing-disk --target=pinebook-pro-rk3399 --media=/dev/sdc
But my PBP is still not booting after fixing the micro SD card.
Did I screw my SPI??? 
|
|
|
|
Star64: Armbian Installation |
|
Posted by: Der Geist der Maschine - 05-29-2023, 01:07 AM - Forum: Getting Started
- Replies (5)
|
|
There are quite a few possible variants of the installation process. Below instructions do not require a serial console. All steps are performed on a linux pc and not on the star64.
Code: schaecsn@pc:~ mkdir riscv && cd riscv
Download armbian from the bottom of this page https://www.armbian.com/star64/, e.g. Armbian Sid CLI or Armbian Sid XFCE desktop.
dd armbian onto a micro sd card. For me, a micro sd card is /dev/sdb. YMMV:
Code: schaecsn@pc:~/riscv$ xzcat Armbian_23.5.0-trunk.231_Star64_sid_edge_5.15.0.img.xz | sudo dd of=/dev/sdb status=progress
Above image does not boot from the micro sd card - it misses a device tree for the star64.
Even with a device tree, armbian's kernel shuts down all usb ports, e.g. keyboard and mouse. For all this to work, use Fishwaldo's kernel. It can be compiled on a Linux PC.
Install a cross-compiler. That is distribution dependent. On Debian, that would be
Code: schaecsn@pc:~/riscv$ sudo apt-get install libncurses-dev libssl-dev bc flex bison make gcc gcc-riscv64-linux-gnu
Download Fishwaldo's kernel
Code: schaecsn@pc:~/riscv$ git clone https://github.com/Fishwaldo/Star64_linux linux
schaecsn@pc:~/riscv$ cd linux
Configure this kernel (CONFIG_SECCOMP is needed by armbian's default systemd service chrony)
Code: schaecsn@pc:~/riscv/linux$ make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- pine64_star64_defconfig
schaecsn@pc:~/riscv/linux$ scripts/config -e CONFIG_SECCOMP
schaecsn@pc:~/riscv/linux$ scripts/config -d CONFIG_SECCOMP_CACHE_DEBUG
Apply possible patches:
Crosscompile the kernel
Code: schaecsn@pc:~/riscv/linux$ make -j4 ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- bindeb-pkg
Above step creates these files and directories
Code: schaecsn@pc:~/riscv/linux$ ls -lad ../linux-image-5.15.107-15659-g7943fd6427b0-dirty_5.15.107-15659-g7943fd6427b0-dirty-1_riscv64.deb arch/riscv/boot/Image debian/linux-image/lib/modules/5.15.107-15659-g7943fd6427b0-dirty/ debian/linux-image/usr/lib/linux-image-5.15.107-15659-g7943fd6427b0-dirty
-rw-r--r-- 1 schaecsn staff 19734212 May 28 22:47 ../linux-image-5.15.107-15659-g7943fd6427b0-dirty_5.15.107-15659-g7943fd6427b0-dirty-1_riscv64.deb
-rwxr-xr-x 1 schaecsn staff 26410944 May 28 22:45 arch/riscv/boot/Image
drwxr-xr-x 3 schaecsn staff 4096 May 28 22:46 debian/linux-image/lib/modules/5.15.107-15659-g7943fd6427b0-dirty/
drwxr-xr-x 4 schaecsn staff 4096 May 28 22:46 debian/linux-image/usr/lib/linux-image-5.15.107-15659-g7943fd6427b0-dirty
The correct way to install Fishwaldo's kernel / modules / device tree would be to run this command on a booted star64 system
Code: sudo dpkg -i linux-image-5.15.107-15659-g7943fd6427b0-dirty_5.15.107-15659-g7943fd6427b0-dirty-1_riscv64.deb
I'm not awfully familiar with armbian. For some reason, the generated deb does not correctly install itself into the /boot directory. On top of this, we can't boot the current armbian installation as it misses a device tree, anyway.
A workaround is a manual installation of the kernel / modules / device tree.
Find an empty directory, say /mnt/tmp and mount the micro sd card on it:
Code: schaecsn@pc:~/riscv/linux$ sudo mount /dev/sdb1 /mnt/tmp
Remove symbolic links of the kernel and device tree directory on the micro sd card (there is no need to make changes to the module directory as the old and new module directory names differ)
Code: schaecsn@pc:~/riscv/linux$ sudo rm /mnt/tmp/boot/Image /mnt/tmp/boot/dtb
Copy over our kernel / modules / device tree on the micro sd card
Code: schaecsn@pc:~/riscv/linux$ sudo rsync -avzH debian/linux-image/usr/lib/linux-image-5.15.107-15659-g7943fd6427b0-dirty /mnt/tmp/boot/dtb
schaecsn@pc:~/riscv/linux$ sudo rsync -avzH arch/riscv/boot/Image /mnt/tmp/boot/
schaecsn@pc:~/riscv/linux$ sudo rsync -avzH debian/linux-image/lib/modules/5.15.107-15659-g7943fd6427b0-dirty /mnt/tmp/lib/modules
Fix a typo of the device tree name in extlinux
Code: schaecsn@pc:~/riscv/linux$ sudo sed -i s/jh7110-star64-pine64.dtb/jh7110-pine64-star64.dtb/ /mnt/tmp/boot/extlinux/extlinux.conf
Done
Code: schaecsn@pc:~/riscv/linux$ sudo umount /dev/sdb1
Next boot the micro sd card on the star64.
Code: schaecsn@192.168.0.216's password:
____ _ __ _ _
/ ___|| |_ __ _ _ __ / /_ | || |
\___ \| __/ _` | '__| '_ \| || |_
___) | || (_| | | | (_) |__ _|
|____/ \__\__,_|_| \___/ |_|
Welcome to Armbian 23.05.0-trunk Bookworm with bleeding edge Linux 5.15.107-15659-g7943fd6427b0-dirty
No end-user support: built from trunk
System load: 54% Up time: 0 min
Memory usage: 1% of 7.73G IP: 192.168.0.216
CPU temp: 50°C Usage of /: 23% of 7.2G
RX today: 44.0 MiB
[ 0 security updates available, 12 updates total: apt upgrade ]
Last check: 2023-05-21 15:22
Last login: Sun May 21 15:23:30 2023 from 192.168.1.231
schaecsn@star64:~$
Tuning after a first boot:
Code: [ 21.771962] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852bu_fw.bin not found
This firmware blob for bluetooth comes from armbian-firmware-full. Install it
Code: schaecsn@star64:~$ sudo apt-get remove armbian-firmware
schaecsn@star64:~$ sudo apt-get install armbian-firmware-full
Possibly install GPU firmware as described in https://forum.pine64.org/showthread.php?tid=18301
Our integration of the kernel / module / device tree shortcuts the package management and armbian kernel / modules / device tree updates may overwrite our own versions.
My first try was deinstalling armbian's kernel / modules / device tree package. That turned out to have disadvantages. Packages that modify initrd trigger commands which come with the kernel package and fail updating the initrd.
For now, I can only suggest to manually copy over our kernel / modules / device tree whenever armbian overwrites them with its own versions.
On the long, armbian should better support the star64 and custom kernel / modules /device trees should not be necessary, anymore.
I was also playing around with ubuntu's riscv port. There, custom kernels can be installed with dpkg -i linux-image*.deb. They hook themselves up to grub and peacefully co-exist with the vanilla kernel.
Please post corrections and possible improvements (in particular on how to better make our own kernel co-exist with the package management).
|
|
|
|
| No Video Out on PBP on all major distros |
|
Posted by: misha64 - 05-28-2023, 12:45 AM - Forum: Linux on Pinebook Pro
- Replies (9)
|
|
Sad reality, but video out on pinebook pro was regressed on all major distros
this includes default factory os manjaro
Found some info that kernel patches needed to allow video out were dropped since were hard to maintain
I guess with years interest for PBP dropped, as well as support for basic functionality from developers.
For example, cannot believe that in 2019 there was mrfixit debian build with all the working functionality that you could easily flash to sd card, while now 4 years later you cannot connect pbp to external monitor or tv
Any suggestions how to make it work again would be appreciated
|
|
|
|
| What File Manager Options Are There For The Pinephone? |
|
Posted by: pinephoneuser22 - 05-27-2023, 07:48 PM - Forum: PinePhone Software
- Replies (7)
|
|
What i would like to do is view documents on the Pinephone and sort then into folders which i would then transfer back to a laptop for further management. The included file manager in Phosh Portfolio does not allow easy moving and sorting of documents. Are there other file managers that are phone friendly that provide the described workflow? I have thousands of documents to sort and doing some of this on the Pinephone when i am traveling without my laptop would help save time.
|
|
|
|
| RXDP from Win10 to Armbian on Rock64 |
|
Posted by: Transportsicherung - 05-27-2023, 06:11 AM - Forum: Linux on Rock64
- No Replies
|
|
Hi,
i dont know much about Linux but i tryed anythink i could find, but with no sucsess...
I want to use Windows XRDP Remote to connect but it only works with root. Why
This is the log from XRDP and Sesman, firstr try is a user, second try is root
Quote:xrdp:
[20230524-20:56:31] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.1.145 port 49328
[20230524-20:56:31] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20230524-20:56:31] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20230524-20:56:31] [ERROR] SSL_read: I/O error
[20230524-20:56:31] [ERROR] libxrdp_force_read: header read error
[20230524-20:56:31] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20230524-20:56:31] [ERROR] [MCS Connection Sequence] receive connection request failed
[20230524-20:56:31] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20230524-20:56:31] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20230524-20:56:31] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20230524-20:56:31] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20230524-20:56:31] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20230524-20:56:31] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.1.145 port 49329
[20230524-20:56:31] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20230524-20:56:31] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20230524-20:56:31] [INFO ] Connected client computer name: DELLG515SE
[20230524-20:56:31] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20230524-20:56:31] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20230524-20:56:31] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000407]
[20230524-20:56:31] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [de] options []
[20230524-20:56:31] [INFO ] TLS connection established from ::ffff:192.168.1.145 port 49329: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[20230524-20:56:31] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20230524-20:56:31] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
[20230524-20:56:31] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20230524-20:56:31] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20230524-20:56:31] [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
[20230524-20:56:31] [INFO ] Loading keymap file /etc/xrdp/km-00000407.ini
[20230524-20:56:31] [WARN ] local keymap file for 0x00000407 found and doesn't match built in keymap, using local keymap file
[20230524-20:56:43] [INFO ] connecting to sesman ip 127.0.0.1 port 3350
[20230524-20:56:43] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20230524-20:56:43] [INFO ] sesman connect ok
[20230524-20:56:43] [INFO ] sending login info to session manager, please wait...
[20230524-20:56:43] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20230524-20:56:43] [INFO ] login successful for display 10
[20230524-20:56:43] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20230524-20:56:43] [INFO ] started connecting
[20230524-20:56:43] [INFO ] lib_mod_connect: connecting via UNIX socket
[20230524-20:59:54] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.1.145 port 49873
[20230524-20:59:54] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20230524-20:59:54] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20230524-20:59:54] [ERROR] SSL_read: I/O error
[20230524-20:59:54] [ERROR] libxrdp_force_read: header read error
[20230524-20:59:54] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20230524-20:59:54] [ERROR] [MCS Connection Sequence] receive connection request failed
[20230524-20:59:54] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20230524-20:59:54] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20230524-20:59:54] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20230524-20:59:54] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20230524-20:59:54] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20230524-20:59:54] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.1.145 port 49874
[20230524-20:59:54] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20230524-20:59:54] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20230524-20:59:54] [INFO ] Connected client computer name: DELLG515SE
[20230524-20:59:54] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20230524-20:59:54] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20230524-20:59:54] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000407]
[20230524-20:59:54] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [de] options []
[20230524-20:59:54] [INFO ] TLS connection established from ::ffff:192.168.1.145 port 49874: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[20230524-20:59:55] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20230524-20:59:55] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
[20230524-20:59:55] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20230524-20:59:55] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20230524-20:59:55] [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
[20230524-20:59:55] [INFO ] Loading keymap file /etc/xrdp/km-00000407.ini
[20230524-20:59:55] [WARN ] local keymap file for 0x00000407 found and doesn't match built in keymap, using local keymap file
[20230524-21:00:03] [INFO ] connecting to sesman ip 127.0.0.1 port 3350
[20230524-21:00:03] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20230524-21:00:03] [INFO ] sesman connect ok
[20230524-21:00:03] [INFO ] sending login info to session manager, please wait...
[20230524-21:00:03] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20230524-21:00:03] [INFO ] login successful for display 10
[20230524-21:00:03] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20230524-21:00:03] [INFO ] started connecting
[20230524-21:00:03] [INFO ] lib_mod_connect: connecting via UNIX socket
[20230524-21:00:04] [INFO ] lib_mod_log_peer: xrdp_pid=2133 connected to X11rdp_pid=2591 X11rdp_uid=0 X11rdp_gid=0 client_ip=::ffff:192.168.1.145 client_port=49329
[20230524-21:00:04] [INFO ] connected ok
[20230524-21:00:04] [ERROR] SSL_write: I/O error
[20230524-21:00:04] [ERROR] xrdp_sec_send_fastpath: xrdp_fastpath_send failed
[20230524-21:00:04] [ERROR] xrdp_rdp_send_fastpath: xrdp_sec_send_fastpath failed
[20230524-21:00:04] [ERROR] libxrdp_set_pointer: xrdp_rdp_send_fastpath failed
[20230524-21:00:04] [INFO ] lib_mod_log_peer: xrdp_pid=2564 connected to X11rdp_pid=2591 X11rdp_uid=0 X11rdp_gid=0 client_ip=::ffff:192.168.1.145 client_port=49874
[20230524-21:00:04] [INFO ] connected ok
[20230524-21:00:05] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20230524-21:00:05] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
sesman:
20230524-20:56:43] [INFO ] Socket 8: AF_INET6 connection received from ::1 port 33556
[20230524-20:56:43] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20230524-20:56:43] [INFO ] ++ created session (access granted): username test2, ip ::ffff:192.168.1.145:49329 - socket: 12
[20230524-20:56:43] [INFO ] starting Xorg session...
[20230524-20:56:43] [INFO ] Starting session: session_pid 2134, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff:192.168.1.145:49329 - socket: 12, user name test2
[20230524-20:56:43] [INFO ] [session start] (display 10): calling auth_start_session from pid 2134
[20230524-20:56:43] [ERROR] sesman_data_in: scp_process_msg failed
[20230524-20:56:43] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20230524-20:56:44] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20230524-20:56:54] [WARN ] Timed out waiting for X server on display 10 to startup
[20230524-20:56:54] [INFO ] Session started successfully for user test2 on display 10
[20230524-20:56:54] [INFO ] Starting the xrdp channel server for display 10
[20230524-20:56:54] [INFO ] Session in progress on display 10, waiting until the window manager (pid 2151) exits to end the session
[20230524-20:56:54] [WARN ] Timed out waiting for X server on display 10 to startup
[20230524-20:56:54] [ERROR] There is no X server active on display 10
[20230524-20:56:54] [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
[20230524-20:56:54] [WARN ] Window manager (pid 2151, display 10) exited quickly (0 secs). This could indicate a window manager config problem
[20230524-20:56:54] [INFO ] Calling auth_stop_session and auth_end from pid 2134
[20230524-20:56:54] [INFO ] Terminating X server (pid 2152) on display 10
[20230524-20:56:54] [INFO ] Terminating the xrdp channel server (pid 2437) on display 10
[20230524-20:56:54] [INFO ] X server on display 10 (pid 2152) returned exit code 1 and signal number 0
[20230524-20:56:54] [INFO ] xrdp channel server for display 10 (pid 2437) exit code 0 and signal number 0
[20230524-20:56:54] [INFO ] cleanup_sockets:
[20230524-20:56:54] [INFO ] ++ terminated session: username test2, display :10.0, session_pid 2134, ip ::ffff:192.168.1.145:49329 - socket: 12
[20230524-21:00:03] [INFO ] Socket 8: AF_INET6 connection received from ::1 port 45346
[20230524-21:00:03] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20230524-21:00:03] [INFO ] ++ created session (access granted): username root, ip ::ffff:192.168.1.145:49874 - socket: 12
[20230524-21:00:03] [INFO ] starting Xorg session...
[20230524-21:00:03] [INFO ] Starting session: session_pid 2574, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff:192.168.1.145:49874 - socket: 12, user name root
[20230524-21:00:03] [INFO ] [session start] (display 10): calling auth_start_session from pid 2574
[20230524-21:00:03] [ERROR] sesman_data_in: scp_process_msg failed
[20230524-21:00:03] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20230524-21:00:04] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20230524-21:00:04] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20230524-21:00:04] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20230524-21:00:04] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20230524-21:00:04] [INFO ] Session started successfully for user root on display 10
[20230524-21:00:04] [INFO ] Starting the default window manager on display 10: /etc/xrdp/startwm.sh
[20230524-21:00:04] [INFO ] Session in progress on display 10, waiting until the window manager (pid 2590) exits to end the session
[20230524-21:00:04] [INFO ] Starting the xrdp channel server for display 10
|
|
|
|
|
