Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: Gary2003
6 hours ago
» Replies: 5
» Views: 4,995
|
Unable to make or recieve...
Forum: General Discussion on PinePhone
Last Post: tracyanne
Today, 02:09 AM
» Replies: 0
» Views: 366
|
Brand new sealed Pinetime...
Forum: General Discussion on PineTime
Last Post: elver
09-10-2025, 06:41 AM
» Replies: 0
» Views: 1,097
|
Call recording?
Forum: PinePhone Pro Software
Last Post: biketool
09-09-2025, 04:14 AM
» Replies: 7
» Views: 7,677
|
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: Frank23t
09-08-2025, 10:30 PM
» Replies: 4
» Views: 2,914
|
more mobile linux on redd...
Forum: General Discussion on PinePhone
Last Post: biketool
09-08-2025, 12:03 PM
» Replies: 2
» Views: 2,619
|
Anyone selling a Pinebook
Forum: Pinebook Hardware and Accessories
Last Post: ams
09-08-2025, 09:26 AM
» Replies: 2
» Views: 2,954
|
Having trouble reading MP...
Forum: Getting Started
Last Post: Alex92
09-05-2025, 08:49 PM
» Replies: 1
» Views: 4,030
|
Special keys stopped work...
Forum: General Discussion on PineNote
Last Post: cheepeero
09-05-2025, 07:32 PM
» Replies: 0
» Views: 3,149
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
09-04-2025, 12:52 PM
» Replies: 20
» Views: 11,116
|
|
|
IRC and Discord Chat Restructure for 2019+ |
Posted by: Luke - 02-10-2019, 04:44 PM - Forum: Community and Events
- No Replies
|
 |
A little bit of community chat maintenance. With all the new gear coming this year - and with brand new categories of gear being introduced - the IRC and Discord have been updated to reflect this and to accommodate the growing line of PINE64 devices. The current list of channels attempts to strike a balance between granularity (I don't really want to have one channel per device) and having everything discussed in one or two channels as it was until now. We'll see how it plays out.
The IRC and Discord chats have now all been bridged, and IRC logging has been updated to include the new channels.
We currently have the following channels:
- #pine64
- #rock64
- #pinebook
- #pinephone
- #cube
- #offtopic
Quick Overview of the Channels
- #pine64 is where you connect to by default in IRC, and the channel is concerned with discussion on Pine A64 (+)/ LTS, SOPine, Clusterboard and Pine H64
- #rock64 is concerned with discussion on Rock64 and RockPro64
- #pinebook concerns the Pinebook, Pinebook Pro and PineTab
- #pinephone is solely meant for the PinePhone Dev / end-user product
- #cube is for discussing CUBE IP-Camera
- #offtopic is an unloggedchannel for off topic conversation
Suggestions welcome.
|
|
|
HDD filesystem corruption at reboot / poweroff (DietPi) |
Posted by: WrongWorld - 02-10-2019, 04:17 PM - Forum: Linux on Rock64
- Replies (1)
|
 |
I am not sure if I should go to the DietPi forum, or if my issue is not specific about DietPi and I am in the right place. Anyway...
My setup consists of a Rock64 4G board connected to a WDLabs Pi drive. I have replaced the HDD cable delivered by (the now defunct) WDLabs with another interfaced with USB3. The WDLabs Pi drive has no SATA connector, see here. I have verified that the USB driver used for the disk is not UAS, in fact the HDD drive is using the usb-storage driver:
Code: [ 2.745235] usb-storage 5-1:1.0: USB Mass Storage device detected
[ 2.749781] scsi host0: usb-storage 5-1:1.0
[ 2.753639] usbcore: registered new interface driver usb-storage
To test the above setup I have used a DietPi distro, which has always performed well on my Raspberries, copied to an SD card and updated with the latest release (6.21.1), to which I have applied the ayufan kernel 4.4.132-1075. Once the test was over, I patched the SPI to enable the USB boot, and then I restarted from scratch transferring the DietPi image directly on the HDD, using Rufus on a Windows machine. The DietPi partitioning scheme, therefore, has been replicated faithfully on the HDD, and indeed after the initial boot the /dev/sda7 partition (root) is properly extended to the maximum size of the disk (314 GB).
Differently from other Rock64 users, until now I haven't experienced any problem with the HDD while the system is running, thanks probably to the particular HDD I am using that was engineered specifically for the Raspberry environment. True, this host is only running Pi-hole, NUT and the Unifi Controller (+ MongoDB) right now, so the system load is not very high at the moment, but the performance is quite good except for the boot, where it takes ~50 seconds from the power on to present the login prompt.
My problem is instead with the reboot / poweroff actions, where 50% of the times the EXT4 filesystem is left in a dirty state, and where I have already experienced the loss / corruption of the /boot/dietpi directory, as well as the /boot/dietpi.txt file, to the point I have to boot the system from an SD card to repair / restore the partition. I have the suspect either the ayufan kernel, and/or the DietPi code dealing with its "ramdrive" are not giving enough time to the HDD to flush any pending writes, or even worst it cuts the power before the HDD is in a safe state. I'd say I am biased toward DietPi, as it's its files which are corrupted most of the times, while the rest of the HDD is sane (minus the fact EXT4 filesystem is in a dirty state). Probably not having /boot on a separate partition in this particular distro is not helping as much to avoid troubles, but this is just my opinion.
So: what am I doing wrong?
Have I forgotten to tune some parameters to better deal with the HDD? Did I make a mistake by putting the DietPi image directly on the HDD? Or is there really an issue on the Rock64, or on the DietPi distro? I have patched the shutdown sequence of the dietpi-ramdrive service to pause for 2 seconds and then run again the sync command to have the HDD some more time to flush any pending write, but it didn't cure the issue. I will try nevertheless to report all the above to the DietPi maintainer (Fourdee), but any hint would be very appreciated, thanks in advance.
|
|
|
Cant update package libgl1-mesa-dri |
Posted by: scalextrix - 02-10-2019, 06:33 AM - Forum: Linux on Rock64
- Replies (2)
|
 |
Hi Just trying to keep my board updated with the Ubuntu releases, Im seeing a package in apt that I cant seem to upgrade:
> The following packages have been kept back:
> libgl1-mesa-dri
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
I tried apt-get --with-new-pkgs and after that failed also dist-upgrade, but the package still isnt installed...?
|
|
|
Hi!. Hi there! |
Posted by: bigbertha - 02-08-2019, 10:30 PM - Forum: General Discussion on ROCK64
- No Replies
|
 |
Just wanted to make a quick post and say hello. I just got my Rock64 and have flashed the Android images. Sad to say Im dissapointed its all android TV and not a normal Android interface. Have had to sideload several apps that play store says I can't have. I bought this as a replacement for my rk3188 tv stick running KK. Funny story about that stick. It had a broadcom wifi chip with an external antenna I broke off and couldnt get a signal and my soldering skills suck So... similar hardware had the Realtek rtl8188eu chip. I just flashed it with a dif image that used the realtek and bought a usb dongle that was rtl8188eu (etv) and it worked very well. Glad I could pull that little wifi gem out and keep it in use with my new board!!!! Not super proficient in Linux but have been a regular Ubuntu user for 10 years and Am up for any testing.
|
|
|
PB charge current |
Posted by: machinehum - 02-07-2019, 01:55 PM - Forum: General Discussion on Pinebook
- Replies (2)
|
 |
Does anyone know the charge current of the PB? Is this set it SW or HW and has anyone tried to change it? I don't want to stress the battery beyond it's max C rating but it would be cool to get a higher charge current.
|
|
|
hardware-accelerated video transcoding (Plex) on Rock64 |
Posted by: mdr - 02-07-2019, 10:45 AM - Forum: Linux on Rock64
- Replies (2)
|
 |
Hi everybody,
I have a Rock64 board which had been lying around for a while, but I now seriously want to deploy as a NAS/Media server replacement for my ageing Synology DS414. Therefore my entry on the forums here 
My goal is to run OpenMediaVault as NAS solution. On top of that run Plex Media Server and possibly a few docker containers. I've been testing several images to see which works best for me:
- ayufan's OMV image, with Plex as plugin (or docker)
- Armbian Stretch with Plex installed via Softy
- for testing purposes: another x86 machine with own OMV installation and Plex in docker, but that's beyond the scope of this forum
OMV works perfectly on the NAS with ayufan's build, but the issue is with Plex video transcoding, Obviously the ARM CPU isn't suitable for that but I understood that the Rockchip RK3328 should have hardware encoding/decoding/transcoding capabilities. Plex supports it on Ubuntu, but OMV requires Debian. Since one is based on the other I'm hoping that can be made working.
But before I spend an inordinate amount tyring to get this working (and I'm not a sysadmin): has anybody got hardware accelerated video to work already on Rock64/Linux? I've searched the forum but couldn't find a recent answer to this.
If it works, some pointers how this is done would be MUCH appreciated. If doesn't work, that answer is also helpful because it would save me a lot of time. Thanks in advance!
|
|
|
PINEBOOK USB PORTS too SHort? |
Posted by: mindwave - 02-07-2019, 09:42 AM - Forum: Pinebook Hardware and Accessories
- Replies (1)
|
 |
Team,
I'm not new to PS's laptops or FOSS.
The idea of the Pinebook is awesome, the Pinebook Pro could be a game changer for many folks.
I have had my Pine book for more than a few weeks, but scheduling, holidays and life started to crowd out some other projects so I "queued it up" and have reached the point where I want to start writing on it.
Unfortunately I spend my daily hours in a hospital with stooped amounts of WIFI security, so far I cant get the Pinebook on the guest network, which Im ok with.
After all that's why God created USB memory keys right?
Sneaker-net!
Imagine my surprise when The USB key wouldn't go in less than 1/8 of an inch. Unsurprisingly the PB wont read it.
Tried 3 different keys, same thing. This started on the RIGHT port, because of AC, but one of them is pretty slim, so I moved it left.
same issue.
2 sandisk 32GB Duo's (USB(a) on one end Micro USB on th other) and a Sandisk Cruzer Glide 16GB
nothing really notable abouyt any of them
any ideas?
Im sure I haven't pushed them in as hard as I coiuld but just didn't think much more force should be needed.
Thanks
j
|
|
|
|