Hi all,

Today my Comfast CF-9534X wifi adapter arrived and I followed these instructions for hotplugging it. The (kernel)drivers for the mt7921u chipset are where they should be; the adapter is recognised according to the lsusb command, but a modprobe mt7921u gives a FATAL result: Module mt7921u not found in directory /lib/modules/6.4.8-danctnix1-1-pinetab2.

Any of you happened to have a mt7921u.ko file on your 1-1kernel pinetab2 that I could borrow? Or is it just not in the image?

TIA!

Hi all,

I received my Pinetab two weeks ago. Had it plasma-bricked, reinstalled the image and did an update of all software immediately after. Everything (as advertised that is) works fine. But I got an issue now because it's booting when connected to a power source. No need to press the power button; it just boots.

Is there a setting in the UEFI that causes this problem, and if so, how can it be adjusted?

Thanks in advance!

I installed Debian Gnome then Phosh on a Lenovo Thinpad Tablet, and the user wants to autologin.
I was able to edit /etc/gdm3/daemon.conf to that effect but it doesn't work for the Phosh session.
I can't find anywhere on the internet information on how Phosh manages its session nor where the configuration files are.
Woud anybody here know ?

I have tried to update my sealed PineTime from 1.11 to 1.12 and 1.13, using nRF Connect.
I followed the istructions here:
https://wiki.pine64.org/wiki/Upgrade_Pin...Time_1.0.0

No luck, though. The watch still runs on 1.11.
Am I doing anything wrong? Thanks.

Hi All: @annerajb and I are porting Apache NuttX RTOS (Real-Time Operating System) to PinePhone Pro. And we welcome you to join us!

NuttX is a lighter, simpler alternative to Linux / Unix. NuttX Apps look very similar to Linux, because NuttX is compatible with POSIX.

Why NuttX? It's great for folks who are curious about the Bare Metal Internals of PinePhone Pro. And it might become a Daily Driver someday!

Today, NuttX Mainline boots on PinePhone Pro to the Serial Console. It runs simple Linux-like commands.

We seek your help to build up NuttX for PinePhone Pro:

- I2C Touch Input (@annerajb is working on this)
- Display Driver (VOP for RK3399, based on NuttX MIPI DSI)
- Touchscreen Apps (with LVGL and maybe Zig)
- 4G LTE Modem (SMS, Voice Calls, maybe a Feature Phone?)
- Sensors: Accelerometer, Light, Proximity, GPS, etc
- USB Host Controller (EHCI)
- Plus a whole bunch of other features (Similar to NuttX on PinePhone)

Please let us know if you'd like to contribute. The code for NuttX on PinePhone Pro is here.

I've documented the entire process of porting NuttX to PinePhone, it might speed things up for PinePhone Pro. Thanks!

(BTW I'm a Volunteer with the Apache NuttX Project Mgmt Committee)

I installed the rhino image file on the internal chip. It booted well enough, very showy compared to Mobian. (I have the PinePhone Keyboard installed.)

On reboot, the status panel was not present, neither was the virtual keyboard. I could not adjust the screen magnification from 100%, or add a Bluetooth mouse. With work, the Linux console could be quite usable. I did not have the knowledge of XFCE4 to recover the panel, virtual keyboard, or mouse.

This update command works:
$ pacstall -Up

With the help of these two references, the console is usable with the PinePhone Keyboard, and the combination has the symbol row working with the Pinecone Key.

ludgate's help on the console

Modify the two files as ludgate describes.

xnux's help on the console symbols

For the symbol row, make the file ppkb.map:

Not sure when I first read that the PT2 would be constructed to allow for expansion for, among other options, the capacity to install celular (LTE) data modules - but it was definitely something talked about as "in the plan." I was disappointed when I casually inquired about it when I was finally actually ordering my unit, and whoever was returning email at the time stated that no, there was no LTE. I went ahead with my order anyways, because I wasn't sure if that person really understood the question, or knew tne right answer. So I want to post this here publicly to see if any other forumers had any experience upgrading to LTE, or whether it's even possible. My cell carrier offers a special unlimited data tablet rate of $15/mo which is why it interests me so much.

I'm trying to install wasp-os without much success. It doesn't look like the project is very current, but it's an attractive alternative because everything is written in Python. I'm going to detail the steps I've taken and where it's going wrong.


I installed watchmate on my Linux system from the repositories. The repository version seems to be current. It works great, and I updated InfiniTime to version 1.13 without incident. Such an intuitive and easy to use program.


I installed the latest ARM gnu toolchain and added the 'bin' directory to my PATH environment variable.


I also used the following steps to download and build wasp-os. This is exactly what's shown in the installation guide and it works fine.

So im going to put this out there, but i think and im not a security researcher but would it be possible for somebody who is to go over the wifi and bluetooth code and look for any exploits that say might allow a hacker to access the wifi and or bluetooth chipset when the wifi or bluetooth is turned on and not connected to any network. 

I mean this as say when you turn the wifi or bluetooth on but dont connect to any network and use a hacking tool like airmong or something different in say kali or custom build tool that looks for signals in the air and allows the tool to connect to that wifi or bluetooth signal in the air and exploits that chipset to make a connection to that device. 

Also does for my knowledge right now when the wifi or bluetooth is turned off or it appears to be off, is the chips still on giving off a signal when it should be off, there might be a malfunction there that allows the chip to appear off when it is not.

Note: OS is arch. 

I thought i would bring these issues to the forum for somebody who is a security researcher to check them out. Thank you