Hello, I am rather new to sdc's. I have used Pi's for kipper but that is about it.
Got a second hand Rock64 yesterday. As far as I have been able to tell I need to jump pins 20 and 21 to bypass SPI-flash to boot from SD. Was not able to boot into debian. I ended up flashing the SD card with Armbian to try and install u-boot. I was able to boot onto the sd card with armbian. So I know the rock64 isn't bricked.
The dilema I currently see myself in is that I only have 1 sd card and I do not see how I would install an OS without having a second sd card and a usb sd card reader. Am I wrong? I am hoping to not have to go out and buy an extra sd card and reader I don't really want to buy an emmc module either.
I was planning to run the rock64 off the sd card. Would it be possible to achieve what I want with the serial console?
Hi there,
Been a quiet PBP user since july 2021, really love my pinebook and enjoy it (using manjaro).
Lately I have an issue with the power button.
Symptoms:
It seemed that it won't boot properly, despite no recent OS/FW updates and topped-up battery.
It would boot into a certain state where the LCD is lit up and a flashing '_' is flashing at top left corner, as expected.
Then, the flashing is halted, then continues until shutdown. The PBP reboots, ad infinitum.
From time to time it did load GUI to show the mouse pointer before resetting, rarely loading the login screen.
Another thing is that shutting down resulted in reboot. Long press on power button did shut it down for good though.
Lately otherwise it ususally make it into login without turning off.
Making a long story short, in the rare cases I managed to log in I got constant power-off dialogs popping at me.
That's a typical journal log I get on the machine (reverse order):
Code:
Oct 12 18:08:27 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:07:44 PinebookPro root[4904]: PowerButton pressed
Oct 12 18:07:44 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:07:28 PinebookPro root[4902]: PowerButton pressed
Oct 12 18:07:28 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:07:17 PinebookPro root[4897]: PowerButton pressed
Oct 12 18:07:17 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:06:44 PinebookPro root[4892]: PowerButton pressed
Oct 12 18:06:44 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:05:58 PinebookPro root[4879]: PowerButton pressed
Oct 12 18:05:58 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:05:26 PinebookPro root[4876]: PowerButton pressed
Oct 12 18:05:26 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:04:36 PinebookPro root[4873]: PowerButton pressed
Oct 12 18:04:36 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:03:28 PinebookPro root[4862]: PowerButton pressed
Oct 12 18:03:28 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:03:10 PinebookPro root[4859]: PowerButton pressed
Oct 12 18:03:10 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:02:56 PinebookPro root[4857]: PowerButton pressed
Oct 12 18:02:56 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:02:31 PinebookPro root[4855]: PowerButton pressed
Oct 12 18:02:31 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:02:07 PinebookPro root[4851]: PowerButton pressed
Oct 12 18:02:06 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:01:35 PinebookPro root[4844]: PowerButton pressed
Oct 12 18:01:35 PinebookPro systemd-logind[520]: Power key pressed short.
Oct 12 18:00:57 PinebookPro root[4831]: PowerButton pressed
Oct 12 18:00:57 PinebookPro systemd-logind[520]: Power key pressed short.
Well you get the idea. That's really annoying.
I could probably remap the power button? But I do fear that the underlying condition will kill the power button altogether one day, and I wont be able to properly power the device on.
I took a look at the schematics. I guess that something is pulling the CPU power line, but not the PMIC one? Or is the PMIC less sensitive to that signal?
If it's the first issue that it's not a keyboard issue, and I have no clue what issue it is.
I might be able to sense the proper test points later, but I'd rather ask here first if anyone had such an issue or have any insight into this issue (I couldn't find such thing in the forum or elsewhere).
I own a pinephone. Mobian is installed in some outdeated version. I want to flash a new version of mobian but none of my computers recognizes the phone when booted with jumpdrive. tow boot seems to be installed. Booting while pressing the volume up button also does not show the devoce as mass storage. Any idea is appreciated.
(10-11-2024, 05:47 AM)sfb Wrote: As descriebed in the headline.
I own a pinephone. Mobian is installed in some outdeated version. I want to flash a new version of mobian but none of my computers recognizes the phone when booted with jumpdrive. tow boot seems to be installed. Booting while pressing the volume up button also does not show the devoce as mass storage. Any idea is appreciated.
edit: I put the image on SD and installed from there. But still I wonder why the pp isn't recognized as mass storage?
Bought a pinephone and the keyboard a few years ago, havent really used it in the past year and would like to get some money for it. UK Based and am probably going to list on ebay for auction soon but thought id post here first if anyone is looking for one. Thanks!
Do you wish there was an easy hands-free way to interact with your PP's touch GUI while sitting in front of your desktop system?
Would you like to compose, read, and send SMSs and IMs using your full size keyboard? Interact with your mobile apps using your desktop's mouse, and screen?
Is there a way to cut and paste between your phone and Desktop?
Maybe you would like to initiate and end hands-free or speakerphone calls without touching your phone?
These and more are all possible using VNC to remotely interact with the GUI of your Pinephone.
Let's start with your Pinephone; mine is running Mobian but the instructions should work for other distros; use your system's package installer. (this is for systems running Weyland for video, x11(and mir/surfaceflinger) uses a different VNC server)
Code:
sudo apt install wayvnc
once wayvnc is installed the way I run it is with a launch script I keep in my home directory, I named my script V (the 0.0.0.0 allows incoming connections from outside localhost)
Code:
#! /bin/bash
wayvnc 0.0.0.0
make our script V executable
Code:
chmod +x V
launch manually on the pinephone's shell console like this
Code:
./V
The VNC server on your phone is now waiting for a client to connect, as configured is not secured and is unencrypted.
This setup when run on your Weyland video server Pinephone will let your login when the VNC server is running on your PP without any security or password config on either side. The VNC server script above is launched and killed manually so it is not running all of the time in this config, you save precious battery when mobile. If you wanted you could make a desktop entry to give you a GUI launcher for the sell script, just kill that shell window to kill the server.
Now install the VNC viewer GUI on your desktop Linux machine(other OSs also have VNC client software)
Code:
sudo apt instal tigervnc-viewer
Now in this insecure home LAN setup just run ./V on your Pinephone, then set the phone's LAN IP address in the tigervnc-viewer GUI running on your desktop system and click connect; a window with your PP's interactive GUI will appear on your desktop machine.
In options I recommend reviewing the cut/paste options in tigervnc-viewer Input tab, clicking the 'show dot when no cursor' in the also in Input tab so you have a way to see your mouse in some server configs, as well as ensuring that in the Security tab the encryption and authentication options including none as in my example are to your preference.
This is all you need to remote control your phone via desktop; it is a near perfect way to interact with your Weyland Pinephone. This setup also works if you are using the PP as your wifi(or USB cable or Bluetooth) tether hotspot just be sure to update the PP's IP address. This quick tryout setup is only viable in a situation where the phone and laptop are on a private WLAN with no possibility of other users, any other situation where the VNC server is running gives all users who can scan the network for open VNC port free GUI access to your PP with no barriers. It is easy to set a user name and password as well as encryption for the connection, a secure setup requires editing a .conf file on your PP with username and password as well as generating an RSA key. see https://github.com/any1/wayvnc
If you have trouble with cut/paste showing boxes rather than text it is a font matching problem and I have solved this by using the on-phone web browser for some non-English languages rather than my desktop's; there are better ways to solve the problem though.
VIew the wayvnc git for secure setup and running instructions https://github.com/any1/wayvnc
I find that if I am doing heavy interaction with my PP while in my office VNC, an SSH session, as well as Filezilla to move files around makes everything so easy I rarely need to touch my charging PP except to wake it up if it goes into standby mode and disconnects from the WLAN.
I also notice that PS doesn't exist in the datasheet for the SC7A20, that pin is NC, although finding an English version was slightly hard, maybe there are different versions?
I used this as a reference for a custom board using it, before I was able to find an english datasheet, figuring that the pinecil is probably the most famous trusted application and whatever it does is probably right, but I'm having some issues getting it to work... Any advice?
Is this an old version of the schematic or something? I also just now noticed it says BMA223, which I apparently glossed over thinking it was a part of the package code, but actually that's a completely different accelerometer chip, so something funny seems to be occuring.
The SC7A20 needs CS pulled high, as far as I can tell from the other datasheet, and on my boards, the chip doesn't seem to be responding to an I2C scan.
The little scissors assembly thing has broken on two of the keys on my PBPro keyboard (ISO / UK version)
One normal-sized one and the backspace key. It feels like the sort of thing that could be replaced, if I can source the assembly. I think in both cases it's the lugs that hold the switch into the keyboard side that have snapped off (so the scissors attaches to the key, just not the keyboard).
Does anyone know if it's possible to obtain them without buying a new keyboard? (the Pine64 store does sell US versions but not the ISO ones).
Anyone wanna buy a mostly linux but totally locked down 10" ereader for $100 used.
Or the same thing new for $399.
No?
Or would you like to buy a system where:
- the code is free if you wanna see if you can get black and white 30fps no flicker animation?
- you want to syncthing it with your life
- you want to rsync it with your life
- you want to load all of your information ... pdf's ebooks... over wifi or usb or (pray they add a sd card) ...
- you want to run your email client
- your browser
- your calendar
- your any one of 65k debian packages applications
- you want to solder a SD card port on it (if it doesnt come with one, I will pay $50 for the first person who does...my old remarkable had that hack)
- you want to crack the screen and be able to buy a new screen and make it work (again praying we can open/repair it)
- you want to VNC viewer to become a screen extension of your desktop?
- you want to add a bt keyboard and a bt mouse with a roller and probably (distro is X11) alt scroll wheel to zoom in and out and use this is a yes, I can sit on the beach and earn a living while getting a tan.
- (you see where this is going?)
- basically...you want to do anything with this...you can.
(try that with a competitive product)
So, OP 9+ is worth $150? kb elip is worth $150...what trash and I going to sell to get that extra $100.
You guys rock. I'm challenging myself to become the first order once it hits the store.
Bill
Ok, so I downloaded PINENOTE_MAIN-V1R2 - Schematic-20210824.pdf. It looks like it has:
- SD card slot?? lots of mentions about SD switches and stuff. Really hoping that's there and that the speed is decent.
- USB 3.0 could be faster but isnt a slouch.
- and I saw on that schmatic...JTAG ports!!!!...I pray they are document which may prevent me from bricking another device when I flash it wrong! Such a valuable feature if it's there. A $25 JTAG "resurrection spell"!
I'm looking for a open source NAS solution and it proves surprisingly difficult, especially on the more budget minded side of things. Got a ton of drives I have to load into something and open hardware would be preferred. Helios64 would be ideal if not for the minor problem of it not being produced anymore and unavailable on the second hand market (which I consider proof of a good design). PINE64 NAS Case with ROCKPro64 sounds like a decent alternative but again, it's not in store. I dont see anything that would hint it's comeback, even though this stuff seems like a fairly easy project with key components available already and a niche. I'd love Pine to pick up the Helios64 project, even if it comes with a proper markup, or at least to sell a decent case (better yet one for more than 2 drives). But if anyone has any other solutions I'm very interested to hear them.
thanks for this nice board. So far I have a working NAS setup with a Quartz64 model A, using the Startech 8 port SATA board plugged into the PCIe slot.
I am now trying to switch between battery powered "low power" mode and the "regular" 12V power supply. I know from reading the Wiki
that the PCIe slot is powerd down while using the battery.
Now comes the challenge: how to properly reengage the PCIe slot when switching back from battery mode to the "fully powered" mode?
So far I tried:
- unmount all drives before disconnecting the 12V main power supply
- remove the PCIe slot via "echo 1 > /sys/bus/pci/devices/0000:00:00.0/remove"
- switch off the 12V supply
So far so good. The system keeps on running, the NIC is still powered, everything seems to work as expected, I am still logged in via ssh after disconnecting the 12V supply.
Now, when I reengage the 12V supply, I try to resurrect the PCIe bus via
echo 1 > /sys/bus/pci/rescan
This makes the PCEe bridge reappear. But the SATA-controller plugged into the slot is not reinitialized. I tried also
root@nas:~# lspci
00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
01:00.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch
02:01.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch
02:02.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch
02:03.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch
02:04.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch
03:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)
42:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)
81:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)
c0:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)
I would be kind of cool (for power-saving reasons) if it would be possible to dynamically switch between battery and 12V main power supply. Is there any knowledge in this forum how to achieve this?
