Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,195
» Latest member: realrebbit01
» Forum threads: 16,381
» Forum posts: 117,591

Full Statistics

Latest Threads
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 64
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,348
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 239
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 1,965
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 103
Default password
Forum: PineTab Hardware
Last Post: dissimilar_goose
08-20-2026, 05:02 AM
» Replies: 0
» Views: 143
New SlateOS features
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:47 PM
» Replies: 0
» Views: 202
SlateOS for PineTime
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:33 PM
» Replies: 2
» Views: 455
How to install Android on...
Forum: General
Last Post: winpkr
08-14-2026, 01:36 AM
» Replies: 2
» Views: 3,717
Newbie questions
Forum: General Discussion on PineTime
Last Post: TouchuvGrey
08-13-2026, 08:09 PM
» Replies: 0
» Views: 301

 
  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


  Current Situation With Setup and Carrier Activation With Tracfone Verizon T-Mobile
Posted by: pinephoneuser22 - 05-26-2023, 08:40 PM - Forum: General Discussion on PinePhone - No Replies

There is a lot of dated information on this forum and elsewhere. The information below is current as of this posting.

I bought a Pinephone beta edition within the past few weeks and had multiple hurdles before i had a working phone. The included version of Manjaro OS is dated so upgrading the OS is mandatory. Found that the JumpDrive tool can be useful to erase and prepare the internal eMMC storage from a laptop. I was able to use a MacBook Pro with macOS to make boot microSDs and manage things, did not need Linux. Current versions of Mobium, PostMarketOS, and Manjaro do not need a boot manager installed such as Tow-Boot, they will install on their own and boot. Mobium and PostMarketOS have Tow-Boot functionality at boot with the correct button combination which exposes the eMMC storage as a USB device. It would be good workflow if this functionality can be extended to the external microSD so one can perform complex file management from a laptop. Be careful inserting and removing SIM cards, the slot is delicate. Expect to do a lot of microsSD and SIM card inserting until you find out how to make things work.

The swapping of an activated SIM card from another phone does not work with Tracfone anymore, calls are blocked although one can receive text messages. When attempting to make a call you will get a pre-recorded message saying something like the phone device does not match the activated SIM. With any further calls nothing happens. Tracfone support looked up the phone IMEI and said the carrier that permits the Pinephone is T-Mobile. Tracfone said that in order to use Tracfone service one must use a T-Mobile SIM and they will accommodate the SIM. They said that Tracfone still uses T-Mobile as one of their service carriers until sometime next year ( probably until contracts run out and then Verizon only). Verizon acquired Tracfone a few years ago, so Verizon is not permitting the Pinephone on their network.

At a local T-Mobile store, the rep used a test SIM to see if the phone could connect to the T-Mobile network. It took around 10 minutes for the phone to finally connect. During troubleshooting i rebooted the phone, rep checked settings, rep explained that data must be turned on in order to get everything working. The phone has current version of Mobian with Phosh. I will note that PostMarketOS with Phosh is also good. Manjaro with Plasma had some show-stopper bugs athough the UI has some good design ideas that should be migrated to Phosh, such as showing apps as a single list, hiding the search app box, closing apps with a close button, and more. After that i paid for a service plan, inserted the T-mobil SIM card and.... phone does not recognize the SIM card, get question mark icon. Took the phone home, played around a bit and the phone starts recognizing the SIM and working, no explanation. I will likely have to change phone numbers as the number assigned is already getting junk calls and texting. T-mobile has low cost pre-paid plans and do not require any information to be provided for service except a PIN number that is used to make payments for service. Although i do not have the need for this kind of anonymity currently, the information may be useful to others.


  Charging woes
Posted by: Barugon - 05-26-2023, 02:39 PM - Forum: General Discussion of PinePhone Pro - Replies (2)

I have Mobian installed on my PPP and when I plug in the USB, it often doesn't come up with the charging indicator. I have to unplug it and then plug it in again for the indicator to come up. Then, after a few minutes, I'll hear a click sound and the charging indicator will be off again. Does anyone else have this issue? Is there some work-around?


  Phosh Updating - Battery Charge Indicator - Jittery Settings - Display Usability
Posted by: ArchiMark - 05-26-2023, 10:29 AM - Forum: PinePhone Pro Software - Replies (4)

Hi,

Have Manjaro Phosh Beta 30 installed on PPP (with keyboard). Overall, works pretty good.

Have a few issues I would appreciate input on.

1. Phosh Updating

I see there is now Phosh Beta 32 available.

Do I need to update via new image file or can it be done using Pacman or ?

If can be done either way, is there advantage to doing it one way or the other?


2. Battery Charge Indicator

I use Keyboard unit with the PPP, what percentage  should I see next to battery icon? (100% or 200%)


3. Jittery Display - Settings

Most of the time, the display looks OK. However, when I try to change the display settings, the settings window is very jittery (jumpy looking). As a result, I can not change the display settings!

I have similar issue with changing setting preferences in Firefox browser and think it happened in some other situations.

Any way to fix thing this? This is a big problem in usability of PPP.


4. Display Usability

In some situations there is too much space above and below a window or app. This is really impacts usability of display when you use PPP with Keyboard and display is in landscape orientation.

Any ways to improve this?


Thank you for any and all input.

Mark


  Star64: 4GB on 8GB boards
Posted by: Der Geist der Maschine - 05-25-2023, 10:40 PM - Forum: Getting Started - Replies (4)

I have 8 GB of physical memory and I get that on Fishwaldo's image.

When using his kernel, modules and device tree from https://github.com/Fishwaldo/Star64_linux on Armbian https://www.armbian.com/star64/, I get only 4 GB of physical memory.


Code:
root@star64:/usr/src/linux# dmesg | grep Memory
[    0.000000] Memory: 2970040K/4192256K available (10967K kernel code, 7217K rwdata, 4096K rodata, 2189K init, 405K bss, 435784K reserved, 786432K cma-reserved)


Note, in these early days, Fishwaldo's kernel is a must-have way superior over other kernels.

I have not familiarized myself with the ins and outs of the boot process and don't understand where it fails on Armbian and perhaps other distributions.

The easiest workaround is setting the memory requirements to 8GB in the device tree


Code:
root@star64:/usr/src/linux# git diff
diff --git a/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dtsi b/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dtsi
index a6517cb4178a..d39e1377db73 100755
--- a/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dtsi
+++ b/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dtsi
@@ -47,7 +47,7 @@ cpus {

        memory@40000000 {
                device_type = "memory";
-              reg = <0x0 0x40000000 0x1 0x0>;
+              reg = <0x0 0x40000000 0x2 0x0>;
        };

        reserved-memory {


After applying above patch, rebuild the device tree as usual:


Code:
root@star64:/usr/src/linux# make starfive/jh7110-pine64-star64.dtb
root@star64:/usr/src/linux# cp arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dtb /boot/dtb/starfive/jh7110-star64-pine64.dtb
root@star64:/usr/src/linux# reboot


This patch against Fishwaldo's kernel gives me 8 GB of memory on Armbian:


Code:
root@star64:/usr/src/linux# dmesg | grep Memory
[    0.000000] Memory: 7100836K/8386560K available (10967K kernel code, 7217K rwdata, 4096K rodata, 2189K init, 405K bss, 499292K reserved, 786432K cma-reserved)


  Pinephone and open source firmware for baseband
Posted by: justneedsomedatathanks - 05-25-2023, 08:47 PM - Forum: General Discussion on PinePhone - Replies (9)

Hi,

I recently came across these tweets related to the Pinephone: https://nitter.net/GrapheneOS/status/161...83084547#m

Twitter link: https://twitter.com/GrapheneOS/status/16...8783084547

I wanted to know whether Pine64 still markets the Pinephone as having open source firmware in the baseband, and whether the company sticks by this claim, and if so, the reasoning behind it.

I can't see the original tweets by what is purportedly Pine64 staff, so I don't know a lot about this. I also couldn't find pages where Pine64 advertises the Pinephone as doing this.


  USB-C connector Overheated and melted
Posted by: nickbenjones - 05-25-2023, 10:08 AM - Forum: PinePhone Hardware - Replies (2)

Hello, Postmarket os 22, pinephone daily driver now for over a year now. Plugged in my phone, while the phone was running, this morning to a USB-A to USB-C charge cable and the usb connector started melting down. Melted the back cover, the battery is ok, but the cable and usb-c side board is toast. The cable and power brick are both anker brand. Voltage and ripple on power brick seems more than reasonable, so I am ruling that out. Is this a common failure? Any idea on cause? I have never had anything like this happen before with any phone. Any guidance would be great

Cheers!

[Image: BPvRnyc]

[Image: BPvRnyc]


  Very slow GbE when receiving, fast sending
Posted by: unixpoet - 05-25-2023, 09:51 AM - Forum: General Discussion on Quartz64 - Replies (3)

I received my Quartz64 a little while ago and have been experimenting a bit. The network is extremely slow when receiving data, but does the usual 940 Mbit/s full saturation for 1 gigabit when sending. Please see below iperf3 outputs. 10.0.0.201 is my Quartz64 model A and 10.0.0.4 is a pretty powerful amd64 Linux workstation.

-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 10.0.0.4, port 32952
[  5] local 10.0.0.201 port 5201 connected to 10.0.0.4 port 32954
[ ID] Interval          Transfer    Bitrate
[  5]  0.00-1.00  sec  110 MBytes  926 Mbits/sec                 
[  5]  1.00-2.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  2.00-3.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  3.00-4.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  4.00-5.00  sec  112 MBytes  942 Mbits/sec                 
[  5]  5.00-6.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  6.00-7.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  7.00-8.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  8.00-9.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  9.00-10.00  sec  112 MBytes  941 Mbits/sec                 
[  5]  10.00-10.00  sec  308 KBytes  885 Mbits/sec                 
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval          Transfer    Bitrate
[  5]  0.00-10.00  sec  1.09 GBytes  940 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201 (test #2)
-----------------------------------------------------------
Accepted connection from 10.0.0.4, port 54688
[  5] local 10.0.0.201 port 5201 connected to 10.0.0.4 port 54704
[ ID] Interval          Transfer    Bitrate        Retr  Cwnd
[  5]  0.00-1.00  sec  1.17 MBytes  9.81 Mbits/sec  41  2.83 KBytes     
[  5]  1.00-2.00  sec  827 KBytes  6.78 Mbits/sec  23  2.83 KBytes     
[  5]  2.00-3.00  sec  1.37 MBytes  11.5 Mbits/sec  48  2.83 KBytes     
[  5]  3.00-4.00  sec  2.42 MBytes  20.3 Mbits/sec  53  2.83 KBytes     
[  5]  4.00-5.00  sec  1.24 MBytes  10.4 Mbits/sec  37  2.83 KBytes     
[  5]  5.00-6.00  sec  2.25 MBytes  18.9 Mbits/sec  102  2.83 KBytes     
[  5]  6.00-7.00  sec  1.12 MBytes  9.42 Mbits/sec  95  2.83 KBytes     
[  5]  7.00-8.00  sec  3.08 MBytes  25.9 Mbits/sec  234  2.83 KBytes     
[  5]  8.00-9.00  sec  3.11 MBytes  26.1 Mbits/sec  73  2.83 KBytes     
[  5]  9.00-10.00  sec  3.48 MBytes  29.2 Mbits/sec  72  2.83 KBytes     
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval          Transfer    Bitrate        Retr
[  5]  0.00-10.00  sec  20.1 MBytes  16.8 Mbits/sec  778            sender


Look at all those retransmits! I've verified that the cable and switch port and everything else in the setup are otherwise fine. This happens in both Arch and Plebian. Did I receive a bad board, should I submit an RMA? Or is there something else going on here?


  PineTab2 shipping
Posted by: GloriousCoffee - 05-25-2023, 03:06 AM - Forum: General Discussion on PineTab - Replies (17)

Hi!

I've ordered a PineTab2 a few days ago. The article title says shipping will occur mid-may, which we've passed. Will the order be included in the next planned shipment, or would I have to wait until next batch is produced? And if so, what time frame should I be expecting?


  PD resets during heat up tip [Pinecil V2]
Posted by: Neitron4ik - 05-24-2023, 12:27 PM - Forum: General Discussion on Pinecil - Replies (2)

Strange power behaviour of chain: Baseus 100W GAN Charger + Pinecil V2(+short tip).
After pressing button to heat up the solder tip, Pinecil starts heating, and in some moment Charger resets TypeC output, I press again it tries to heat up again and resets again, and after several tries, it reach threshold temperature and after that I can solder easily. Seems not enough power, and charger detects power peaks and resets output.
This is 100W charger from Baseus:  https://www.aliexpress.com/item/1005003117435688.html , I am using 100W TypeC cable.
I tried other cables, doesnt help. I tried to limit power in Pinecil's "advanced seting" to 65 to 50 W to 40W - doesnt help.
I tried to disconnect all other consumers, and remain only Pinecil connected to this Charger - doesnt help.
This Baseus charges my 65W Lenovo laptop easily.

Is there ideas what to check? Maybe some other advanced settings to try? Huh