I'm trying to get Talos working on my oldish Rock64 board. The PCB says, "ROCK64 V2.0 2017." The Talos devs have a distribution for ROCK64, and one of their engineers says he's got it running on a ROCK64 board. His says "V3 2019." His works, mine doesn't. But mine works just fine when it's running Ubuntu.

According to my packet sniffer, my ROCK64 never sends a DHCPDISCOVER packet. But it seems like the ROCK64 thinks it sent one, and it's waiting for a reply that never comes.

Does it seem likely that there's a hardware or firmware difference between V2 and V3 that's preventing the Talos Linux kernel from talking to the ethernet? Or does it seem more likely that I've messed up my network somehow?

I'm attaching two excerpts from the console log running Talos.

Attached Files

  dmesg1.txt (Size: 1.68 KB / Downloads: 424)
  dmesg2.txt (Size: 1.03 KB / Downloads: 414)

My keyboard is misaligned. nobody seems to know how to fix it including pine64 now that its out of warranty. so now I have a 150 dollar paper weight. As far as i know, nobody can service the pinephone. So now i'm in a creek without a paddle.

Anyone have any experiences (bad or good) with the IP67 rated water resistance of the Pinetime?

I'm used to not taking off my Galaxy Watch Active for pool/shower activities. I figure the Pinetime is ok for shower use or washing hands with sink water....but swimming probably not unless you're just using it at the side of the pool with a nice frosty beverage and not doing any kind of diving down underwater with it.  1 meter is not very deep.

I have 3 of em, so I guess if I did kill it I still have a Plan B and C watch.

Just tried Twister OS. Really like it even if the display brightness keys are not mapped. The Theme Chooser is nice. Sound played through the speakers at about 2% even when turned up to 100%. That's too bad. Anyone find a fix for this? TIA.

I've successfully installed openSUSE via their TumbleWeed netinstall aarch64 iso, via serial console that is, with the NVMe as / drive. GRUB appears on the PBP's screen, which then shuts down for the whole process. Upon reboot, the LUKS password must be typed blindly because of this. Also, no graphical desktop after booting, although panfrost seems to be loaded correctly. Otherwise the system is up and usable via serial console or SSH.

I've installed dtb-rockchip, but I can't seem to make either U-Boot or GRUB use the rk3399-pinebook-pro.dtb when booting. I guess this is the missing step in order to get graphics to show at all, but I'm not really comfortable yet in the ARM world, and I'm surely missing something.

This is with the following packages:

• Mesa 21.1
  
• Kernel 5.12.3-1-default
  

Apparently danielt's Debian installer is now mainstream enough it doesn't need it's own dedicated thread!

I'm trying to use this on my brand new PBP, but it kernel panics on startup on boot. I haven't modified the installation at all (yet).

The crash happens at T+13s, well into multiuser startup, and I've pasted the relevant bits blow (does this forum have an attach button? I can't find one). The reference to gpio-key-power looks suspicious.

The kernel version the installer used is linux-image-pinebookpro-arm64 (5.7.19-30-geadcd756eb47-1). Is this new, by any chance? Any ideas of workarounds?

I have the Manjaro Beta Edition. I'm trying to import my contacts into the phone book. I can tell it to import, I can navigate to a csv file of contacts, and I think I select the file, but then nothing happens and there are still no contacts.

What format does it want, and any idea what I'm doing wrong?

Hi,

I wanted to record some video using the PineBook Pro WebCam so I installed OBS from PacMan (Manjaro). When I started OBS, OBS reported "Failed to initialize video.  Your GPU may not be supported, or your graphics drivers may need to be updated." Am I missing a driver? Is there another video recorder I should use? TIA.

I just got my Pine phone with 3 gigs 32 gig internal I try putting an SD card in it and it won't recognize it and he will know what's going on?

I have a PmOS CE (V1.2a). The wiki says the update to 'V1.2b' is 'resistor R1318 changed to NC'. Means 'normally closed', like directly close the circuit with solder? This sounds doable? Maybe? Anyone done this themselves? Found R1318 on the schematic, not sure where that relates to in reality though...