this is little bit offtopic of pine forums, but i think it interests some users. other kind of 2fa/mfa.

because of possible privacy issues, data collection and locking to close platforms, like google play and apple store, i don't usually like 2fa or mfa. two-factor-authentication or multi-factor-authentication is additional required policy for many services to getting in.

i found by coincidence a reasonable alternative, which can be used for 2fa/mfa systems. essentially, it has no privacy or data collection issues (assuming of usage). it is totp https://en.wikipedia.org/wiki/Time-based...e_password . it is based on time and correct timezone.

i initiated this on some services already, but i don't name those here, because of advertising. quite often, it is called an "authenticator app".

also hardware based totp devices are available, but might be cumbersome to be activated for service.

in debian, there is a package "oathtool". which can used by following, note -b is for base32.

Hello,

I am new to Linux (except Ubuntu) and to this forum; my PinePhone is my first "smart" phone (at age 70!) so my questions will likely be elementary.  Thanks for your patience.

My problem is that the virtual keys don't produce audible tones when touched so that I can't use it for automated phone systems ("Press 1 Now" for example).  I've looked everywhere I can think of in Settings including Sound, Tweaks, Mobile Settings and Keyboard to no avail.

Thanks in advance.

p.s. The application is 'Calls'.

Highlights for March:
- move from lightdm to systemd based autologin
- fixes in ngfd and volume settings slider

http://nemomobile.net/pages/nemomobile-in-march-2023/

This post is mainly to share my tests result, but I have two questions:

- Did someone managed to boot from this SSD? Boot from Intel 660p 2 TB works fine but not this one?

- I noticed that my tests on the Intel 660p 2 TB are slower than before any idea why?
I am using Armbian with linux kernel 5.15.93-rockchip64 #23.02.2, we might get better results on linux kernel v4?

Note: The RP64 has a PCIe NVMe v2.0 x4 (not a v3.0) the speed is limited and not representative of the SSD real performance.


WRITE
sync; dd if=/dev/zero of=tempfile bs=512 count=1024 oflag=dsync; sync; rm tempfile
524288 bytes (524 kB, 512 KiB) copied, 0.720266 s, 728 kB/s

sync; dd if=/dev/zero of=tempfile bs=1M count=1024; sync; rm tempfile
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 3.60083 s, 298 MB/s

sync; dd if=/dev/zero of=tempfile bs=1G count=4 oflag=dsync; sync
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 15.6034 s, 275 MB/s

READ
dd if=tempfile of=/dev/null bs=512 count=2048
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0285999 s, 36.7 MB/s
dd if=tempfile of=/dev/null bs=1M count=1024
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.00752 s, 535 MB/s
dd if=tempfile of=/dev/null bs=2M count=2048
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 7.23786 s, 593 MB/s


[b]sync; sudo sysctl vm.drop_caches=3
hdparm -tT --direct /dev/nvme0n1[/b]
Timing O_DIRECT cached reads:   1096 MB in  2.00 seconds = 548.08 MB/sec
Timing O_DIRECT disk reads: 1714 MB in  3.00 seconds = 570.76 MB/sec

sync; sudo sysctl vm.drop_caches=3
hdparm -Tt /dev/nvme0n1


Timing cached reads:   2472 MB in  2.00 seconds = 1235.97 MB/sec
Timing buffered disk reads: 1484 MB in  3.00 seconds = 494.27 MB/sec

I have playing around with gokrazy, a unikernal project for the RPi, and very interested to see if such a project is feasible with your new upcoming Star64 Risc-V SBC.  I have some assembly code that initialises the Pi, and first step would be porting this over.  Is the Star64 documented well enough for such a project, I know that the Pi benefits from being around for a long time.  I can see 4+1 cores? (JH7110 has 6 no?) and already keen to find some documentation in preparation for your launch.

Hi all

I can't seem to work out, is it required/recommended to install the package "libdrm-pinebookpro" or is the functionality/fixes that this provides now included in the mainline libdrm package?

I have been having some issue with OpenGL objects within a programme (Mixxx DJ software Waveform display) causing some problems.

Thanks in advance.

hacknix

I'm trying to change from the bullseye repository to the bookworm, and I'm getting an error about the repository being unsigned. In /etc/apt/sources.list.d/mobian.list

I changed

deb http://repo.mobian-project.org/ bullseye main non-free

to

deb http://repo.mobian-project.org/ bookworm main non-free

but now when I run

apt update

I get

Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://repo.mobian-project.org bookworm InRelease [32.4 kB]
Err:2 http://repo.mobian-project.org bookworm InRelease
  The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
Reading package lists... Done
W: GPG error: http://repo.mobian-project.org bookworm InRelease: The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
E: The repository 'http://repo.mobian-project.org bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Does anyone know what might cause this?

My WiFi/Bluetooth daughter board just arrived today for my PINE A64-LTS V2 that I've been integrating into a project.  I've been using the SBC with a wired Ethernet connection for weeks (although that had its own challenges, I eventually had to limit it to 10/100) and finally now I'm trying to get wireless going.  Unfortunately, I cannot get it to work after several hours of troubleshooting and I'm hoping someone out there has some ideas.

First, the basics... Issuing uname -a produces this:

Hello,

Can anyone please tell me the length of the DC plug? I know the outer diameter is 5.5 mm and the inner diameter is 2.1 mm, but I can't find the length (or even a part number for J11 that I could check, since there's no BOM published).

I'm used to seeing an update around the 15th of each month on the Pine64 blog. Are those not happening anymore?

Are the updates somewhere else?