I recently purchased a EB-BJ700CBE battery from eBay, and can confirm the FAQ note:

Quote:There is a report that model "EB-BJ700CBE" might be incompatible

I have been getting this error message for a while when i issue
'sudo apt update && sudo apt full-upgrade -y':

E: The repository 'http://security.debian.org bullseye/updates Release' does not have a Release file.
N: Updating from such a repository can 't be done securely, and is therefore disabled by default.

So i would issue:

'sudo apt full-upgrade' instead and it seems to get done.

Am i missing out on anything this way?

This thread continues the thread I posted some time ago.  Forgive me if that's not good protocol.  That thread received no replies and since then I've done a lot of my own trial and error research making the content of this post quite different.  Also, being a little more familiar with this forum I thought it might fit better in this category.

My basic problem is that the computer keyboard switches from upper to lower case on its own while I'm trying to type, making it pretty useless, especially for any work that is case sensitive, like terminal commands.

I just want to share my progress:

First, I tried various installs like Fedora and Debian from microSD card and found the same faulty behavior.  I tried installing Arch but of course that was impossible due to all the CLI input needed.  Tried different DEs,  KDE, Cinnamon, Lumina, LXQt and Xfce with no luck.    For now I am using Fedora with Openbox.  That the problem still persists with an external USB keyboard tells me maybe it's not a keyboard hardware problem.  But what sort of problem is it then?
After much trial and error I noticed:
1.   " sudo udevadm trigger --subsystem-match=input --action=change "
would temporarily stop the problem.  But the problem could revert in a matter of seconds.
2.  " xev -event keyboard  "
from terminal indicated a shift key problem.  This seemed logical as the problem mainly involves constant back and forth switching between upper and lower case.
3.  Installing and running onboard gave me a clear visual image of this shift key problem. Onboard showed me that the computer was by itself constantly typing the shift key, often many times a minute.  I am unsure of the cause, but I pinpointed the problem to the right shift key.
4.  Disabling the right shift key with " xmodmap -e 'keycode 62=' " alleviated the problem.  Placing this code in autostart files for the user and desktop environments helped make the keyboard somewhat usable as can be seen by the fact I am using the PBP to type this.
However, besides not being able to use the right shift key, I am also not able to type uppercase V, B, or M keys.  I am able to type them using Caps Lock. 
Of course, the original problem persists before login when typing password, which can be tricky.  I haven't been able to figure out how to make these changes during boot, before the login window appears.

Perhaps with this information you can help me in getting to the root cause of the problem.  I think it would be in the interest of making a better Pinebook.

At the moment I have a rather crippled computer.

All help, hints, info much appreciated.
Kendew

For example, the meaning of each switch, how the sd and sim cards go in, information that is currently small/hard to read. Or would that be difficult/costly?

I was wondering if the serial connector on the mainboard is actually usable.
The answer is yes, it is. So with additional micro usb-uart adapter I have serial console accessible from outside.

It's not perfect since there is not much space inside. Even with such a small adapter you have to fight for every tenth of mm.
But it's better than opening the case everytime serial console is needed.

I've tried both the x86 and arm versions I found on the arch-linux wiki and they both gave me an error saying I do not have the correct architecture.  Where can I find a postgres that will work on PBP Manjaro?

Still confused about relationship btw Arch and Manjaro.

For the past week I've been trying to get this board to actually boot off a usb attached drive. Here's where I am:

- compiled my own u-boot following instructions here: https://forum.pine64.org/showthread.php?...9#pid55839
- tried so many ayufan and other u-boot (like https://forum.pine64.org/showthread.php?...+usb+3+3.0) I can't keep track anymore
- I have a seagate backup drive + usb 3.0 to sata interface, a JMS578/567 (sold officially by pine too?), and another weird Toshiba (Bus 002 Device 015: ID 0480:a00c Toshiba America Inc) usb 3.0 to sata interface
- upgraded firmware on the JMS578/567 from another SBC forum

There is no common theme among u-boot versions:
- some will power-cycle the usb 2.0 drive to death, some will only do it 2-3 times.
- Some will detect my seagate (external power) usb to sata interface, some won't.
- USB 2.0 is more likely to detect something connected to it, but it doesn't boot. It's just stuck before the point where it should say "Starting kernel...". While using Toshiba interface, the hard drive powers off after the kernel selection prompt.

Now here's the nut-kicker:
- I have a sandisk extreme usb 3.0 thumbdrive which *DOES* boot off of usb 3.0 with *some* u-boot versions. So that confirms usb 3.0 port is fine, and the image I'm trying to boot is also fine.

What I believe I ruled out:
- damaged HDD/SSD
- non-working usb to sata interfaces
- inadequate power supply to rockpro64: I can duplicate all of the above with a 12V 1.5A as well as a 12V 3.5A brick. I'm sure I can rig up a 12V 25A from a desktop power supply if that's going to make some of you obsessed people happy (IRC people kept pestering me about this being power related). On top of that, on a fully booted system (from sd card), anything I throw in the usb ports gets adequate power and works
- shit linux images; I'm able to boot the same image(s) off of the usb thumbdrive connected to usb 3.0
- usb port damage (I can see all devices connected to usb 3.0 A, both usb 2.0 ports, cannot test usb-c, no dongle/device)

I also tried a sata_sil24 compatible card; u-boot sees it but it doesn't go any further than that. Drives connected to the PCIe eSATA (Sonnet Tempo SATA E2P) do not power on while in u-boot, but they will power on and get discovered once a linux kernel is booted. I'm guessing u-boot inadequate sata_sil24 drivers?

I don't know much about grub, or uboot, or compiling my own kernels but I can follow directions.

I've been struggling with getting this window tiler to work https://github.com/kwin-scripts/kwin-tiling and thought maybe it's the meta-key? Maybe I'm hitting the wrong key? 

On mac (on my mac at least) it's esc. I've also tried alt, ctrl. What's the meta key here? Manjaro with Plasma

I don't know your country but in the US you get scam phones almost every day. On many phones you can block certain numbers or even block all unknown phone numbers. Is this possible in any distro? thanks

I noted that there's a call to action for people to develop things for the SOEdge, but I also noted that it's hard to determine where its niche is felt to be. That might make it difficult for chickens to provide eggs that others can consume. 

However, I was looking at the upstream Github for the BSP and wasn't immediately finding licensing information or what the difference between the full and Neural AI Stick BSPs is. Does anyone have this information readily available? Downloading 25 GB of BSP SDKs to compare them, for a board I don't have, isn't high on the "this is a fun way to get started" list.

But, more than anything, what do you (both PINE64 and the community) see as the most likely use cases and software to be run on them? That will help interested developers decide if it's a project where their $50-60 + time is going to be well spent by producing output that is going to continue to be useful to a community.

It's obvious that it is positionable for AI, but that's still a very wide range of uses (machine learning, speech, vision, language processing, robotics, expert systems, and more...) and associated software. I see a viable approach in bootstrapping a JeOS baseline image to validate functionality and performance, and then building images based on that for specific tasks.

I know that most buying the board will want to use Acuity with the Vivante NPUIP, but what sorts of things will people be doing with the NPU? What sorts of non-NPU things are people wanting to do?

I'm interested in hearing from the buyers and potential buyers of the SOEdge,of course. What do you want to see this become? Are you planning on basing a business model on using these boards? What do you need to be successful? As a hobbyist, what will make your life easier and save you time by already having common stuff in place?

I'm not explicitly volunteering to start putting some images together, partially because I don't have the hardware to test on right now, and partially because I don't know what would be useful to others. But I expect that anyone else who might want to build images for wider consumption than themselves will also want to know how to make them as useful as possible.