Does anyone know how to get Linux (Debian, Manjaro, etc.) to cooperate with a NetBSD NIS server?

The only thing that doesn't work is user passwords.  Linux clients recognise NIS users but will not authenticate them.  I do not have this problem with NetBSD or Solaris clients.  Nobody else seems to run into this.

I can’t be the only n00b PinePhone-owner who’s not too excited about how my ordinary user can sudo with the PinePhone’s lockscreen PIN-code? This is the case in both Manjaro and Mobian. If one should be the victim of a brute force password attack, even a 16-20 digit numerical password is cracked before you can blink, and the attacker can log in as root with it. Numerical password is also a lot easier to see (few, big buttons) and memorize in a «over the shoulder password attack» than be an alphanumerical one with upprcase, lowercase and special characters.

I have actual enemies skilled in «pentesting» (cracking) who have subjected every aspect of my digital life to targeted attacks, often successfully, so my need for device security probably exceeds the average internet surfer, but even the typical average user with no personal enemies could get hurt by crackers who have the knowledge of this numerical password issue on Mobian and Manjaro. 

I’ve tried several guides found online, for setting privileges and demanding root passwd for sudo, but there aren’t as many n00bs posting these stupid questions about Mobian or ManjaroARM as there are people answering these questions about desktop Ubuntu. Please help! How to fix this on different distros respectively? Removing sudo privileges will permanently lock you out of root on Mobian because the only way to log in as root is sudo -i with the lockscreen PIN code, while on ManjaroARM that might be a solution. Please help!

New PinePhone user who is also relatively new to Linux as well.

I picked up a 512GB Samsung EVO Select SD and used Rufus in Win10 to restore the mobian-pinephone-phosh-20210517.img I downloaded from https://images.mobian-project.org/pinephone/ (parent of the "installer" folder).

The phone booted to the Mobius splash screen right away; which was a good sign... and indicated it was expanding the disk on first boot.

At some point (maybe after 15 minutes), the screen blanked (transitioned from the splash disk expansion screen)... you could still see the backlight was on... just no more messages echoed to the screen.

In case it was still busy, I left the phone alone to do its thing for about an hour... then powered it down.

I took the SD out of the phone and installed it back into my USB/SD card reader on my PC, brought up the disk manager, and confirmed the partitions had been expanded out to consume the entire disk... 8MB Unallocated, 504 MB Active Primary Partition, and a 476.41 GB Primary partition.

So as far as I can tell, the phone booted the SD image and expanded the disk like it said it was going to, and then went completely silent/blank... was I not patient enough waiting an hour for something to show on the screen, did I pickup an SD that was too big, should I have used the installer image, or is there a known issue here that I can take an action on to yield a successful boot?

In the mean time I also want to test this new SD... so I've used the Win10 Disk Manager to delete the two allocated partitions, created one large NTFS partition, and am in the process of copying a single 368GB (nvme backup) file to it... Windows suggested it was going to take ~80 minutes to copy the file @ 80 MB/s.... at the time of this writing 28% of the file has been written (~103GB) with a 55min ETA.

Hopefully the SD proves to be good... I post again (or maybe just update this post) with those results, and look forward to everyone's feedback and help.

EDIT: I think the SD is good...  The 368GB file copied successfully at a sustained 80GB/s second average (bounced between 79.6 and 80.6), I even mounted the backup image, browsed the folder structure, and opened a few random files to confirm their contents were read correctly.  I don't think my issue is that the SD is bad.

Hello,

 Since owning my rock64 (4GB version)  I had always problems compiling larger projects on the device itself.

I tried many things like an other ac-adapter, different micro-sdcards, compiling on USB, different host-images, compiling only on two cores than
one core, gcc-5, 6, 7, swap on,  nothing helped.

The compiler always runs in errors like "illegal instruction" or "memory fault" that were temporal as they disappeared at the next
try.

After playing around with the rockchip boot flow on the rockpro64 I got the idea to check the driver for the external memory interface.
All host-images I tried on the rock64 use the same driverfile "rk3328_ddr_786MHz_v1.13.bin", so I gave the rock64 an other try with
rk3328_ddr_333MHz_v1.13.bin at offset 0x8800 on the boot device.

After reboot I compiled the ayufan-kernel on the device itself with 4 cores on internal sdcard. Worked, no error like before.

Yesterday I took an external USB-HD with the source of palemoon compiled from USB, wrote the objectfiles to the internal sdcard, 4 cores, swap on. It took the whole night, but the build completed successfully. No error like before.

Can someone tell me the negative implications when using the 333MHz-version of this driver?
______________________
First Motion Products

Occasionally, the mobile connection icon vanishes from the dropdown and is gone from the preferences. Does anyone know what's causing this? Is the modem manager crashing? Is there an update or workaround that I can try?

In case anyone is still using their original Pinebook - I pulled mine out of storage couple days ago and installed Debian Sid on it. Everything is working fine so far, except Bluetooth, sound, and deep sleep. The only special thing I had to do is build kernel module separately for WiFi.

I used https://d-i.debian.org/daily-images/arm6...rd-images/ to create a Debian installer SD card. Generally installer worked, but letting it do it's own thing hands-off resulted in a system that's not bootable without an SD card. To make it bootable 16MiB free space is required in the beginning of the eMMC (I didn't try using SPI flash). So I partitioned eMMC manually, creating a single ext4 partition that starts at 16MiB mark and takes all of eMMC - I didn't want the hassle with any special partitioning. After that I went through the installation, and in the end installed u-boot-sunxi and ran `u-boot-install-sunxi64 /dev/mmcblk0` (make sure you got the right device number) to install u-boot. One thing to note though is I used u-boot-sunxi from experimental - it seems the version in Unstable is not yet able to boot from ext4 partitions. After that the system boots fine on its own, but doesn't have any WiFi. To get WiFi working I cloned https://github.com/Icenowy/rtl8723cs, installed basic build dependencies (build-essential, linux-headers-arm64), cd to the folder, `make && sudo make install && sudo modprobe 8723cs`. After that I installed the rest of the packages and got a full working system. For KDE Plasma QML not to glitch all the time I had to set QT_XCB_FORCE_SOFTWARE_OPENGL to 1 (I added `QT_XCB_FORCE_SOFTWARE_OPENGL=1` line to /etc/environment).

I am a new user in Linux and a new owner of a pinebook pro from Russia . How to fix booting after incorrect installation of Manjaro?

I received my Dock today, but it seems that it doesn't function properly, none of the ports are working including the VGA and HDMI. When I plug the dock into the laptop's type c port, I get a loud coil whine. This also happens if I plug power into the dock's power port. Has anybody else experienced similar issues? your help would be greatly appreciated. 
Thanks

Hello,

I have read in various forums / Twitter that Jolla and Pine64 have entered into a cooperation or that devices have been shipped.
Is there any news if the Pinephone will be a supported device at Jolla? Or will it remain a community device.

Surprisingly, the Pinephone runs very smoothly with Sailfish OS 4.
Apart from the well-known modem problem that affects all OSes, the rest runs stably.

Thanks to the community for their hard work.


A statement from Pine64 would be great here.

with friendly greetings
Steffen

I have a beta edition pinephone, using Manjaro Plasma. I am experimenting with a Nexdock, and getting poor results.

When I turned on the phone and plugged it in, they did connect, and the display was sort of shown on the Nexdock.  I got strange effects, though: sometimes the two displays seem to overlap, sometimes the phone display was shown at phone size in the upper left corner of the Nexdock, occasionally other strange stuff. 

I went into the settings and messed with them a bit. It showed the Nexdock display, and showed the phone (called it laptop, but the sizes made it obvious which was which).  After a bit the phone display went black, and the Nexdock display began to blink furiously if I moved the mouse pointer.  The earlier strangeness was intermittent, and now this is continuous.  The only way I can get out of the jam is to unplug and reboot the phone.  If I plug it back in and turn on the Nexdock, I'm back to black screen on the phone and blinky on the Nexdock.

If anyone has made this combo work, I'd appreciate some pointers.