| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,473
» Latest member: Samliams
» Forum threads: 16,196
» Forum posts: 116,875
Full Statistics
|
|
|
| Somehow broke sound, can someone help me out? |
|
Posted by: daid - 11-12-2017, 12:00 PM - Forum: Linux on Pinebook
- Replies (5)
|
 |
While updating some packages to the debian stable versions, I managed to break audio in the process.
Pulseaudio is running and shows output in the volume. So I'm assuming the problem is somewhere in alsa.
Can someone post the full output of "amixer -c0" of a working sound output of a pinebook 14"? I'm currently assuming it's one of those many settings that is wrong.
|
|
|
|
| rkflashtool -n does not recognize memory [RESOLVED] |
|
Posted by: toby - 11-11-2017, 10:00 PM - Forum: General Discussion on ROCK64
- Replies (6)
|
|
If there are threads on this topic, please let me know and I'll close this one.
I am trying to verify that the storage modules are at least recognized by the Rock62 board ( v2.0, 2017-0713).
I'm following the steps outlined here:
* http://files.pine64.org/doc/rock64/guide...o_eMMC.pdf
* https://github.com/fire219/sadie/blob/ma...x/sadie.sh
When I run the command `rkflashtool n`, it seems the board does not recognize the memory. I've tried four different memory modules - 32 GB eMMC sold by pine64 ( two different individual modules )
- 16 GB eMMC previously successfully running linux in a odroid C2
- 1GB microSD ( could not verify still good )
In each case, the output is as follows.
Code: sudo rkflashtool n
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
libusb: warning [darwin_transfer_status] transfer error: device not responding (value = 0xe00002ed)
libusb: error [submit_bulk_transfer] bulk transfer failed (dir = Out): pipe is stalled (code = 0xe000404f)
libusb: error [submit_bulk_transfer] bulk transfer failed (dir = In): pipe is stalled (code = 0xe000404f)
libusb: error [submit_bulk_transfer] bulk transfer failed (dir = In): pipe is stalled (code = 0xe000404f)
rkflashtool: info: Flash ID: 00 00 00 00 00
libusb: error [submit_bulk_transfer] bulk transfer failed (dir = Out): pipe is stalled (code = 0xe000404f)
libusb: error [submit_bulk_transfer] bulk transfer failed (dir = In): pipe is stalled (code = 0xe000404f)
libusb: error [submit_bulk_transfer] bulk transfer failed (dir = In): pipe is stalled (code = 0xe000404f)
rkflashtool: info: Flash Info:
Manufacturer: Samsung (0)
Flash Size: 0MB
Block Size: 0KB
Page Size: 0KB
ECC Bits: 0
Access Time: 0
Flash CS:
I would like to think this is an issue with MacOSx. I do not have any of the accessories ( serial console adapter, USB->eMMC Adaptor ), but I would expect at least one of the chips to be recognized....
Code: ProductName: Mac OS X
ProductVersion: 10.12.6
BuildVersion: 16G1033
Procedure that I've been following:
- Set memory module
- Try to set the jumper ( different combinations )
- Insert power cable
- Remove jumper
- Insert USB cable
- Hold Reset button
- Hold Recovery button
- Release Reset button
- Release Recovery button after 2-5 seconds ( I've experimented )
- Run `rkflashtoon n` in console
Solid Red,Blueish,....Green lights. No smoke.
Yeah, so, if you've gone down this path and found a solution, please let me know. 
|
|
|
|
TIP: Erase eMMC to Boot to SD |
|
Posted by: lnk - 11-11-2017, 08:43 AM - Forum: General Discussion on ROCK64
- No Replies
|
 |
When i want to just boot on your SD to install new os on eMMC with serial at boot: - Hit any key to stop autoboot
- write
-
- then
it will erase the first 1000 block on your eMMC so the rock64 will not be able to boot on it and will boot on SD
|
|
|
|
| [newbie] Why Rock64 can't run native ARM Linux distro out of the box |
|
Posted by: imjtrial@gmail.com - 11-11-2017, 05:55 AM - Forum: Linux on Rock64
- Replies (2)
|
|
Dear all,
why can't ARM SBC like Rock64 just run native ARM distro like openSUSE out of the box like x86 does?
Even Raspberry pi 3 can run openSUSE native ARM image. I have the impression that other native ARM images in future are not guaranteed.
May I know why this is the situation while ARM cpu has huge market share and ARM devices are everywhere....
Why so much effort has to put on OS layer....
Is could improve this and just have ARM SBC run any ARM distro out of the box like any junk x86 ones does.
Thanks
|
|
|
|
| ROS on Rock64 board? |
|
Posted by: DrPop - 11-10-2017, 11:43 PM - Forum: General Discussion on ROCK64
- Replies (3)
|
|
Having owned all three versions of the Pi plus Beaglebone Black, I'm now looking for something a little more powerful than a Pi 3 to run ROS for a robot build. I can't justify the cost of an Nvidia TX2 or something like that yet. I use Parallax Propeller chips to interface with the motors and sensors in real-time.
Two boards that have caught my interest are the ASUS Tinker Board and the Pine64 Rock64 Board.
Has anyone had ROS running on a Rock64 board, or is that a long way off?
Thanks for your time.
|
|
|
|
| How to backup to be able to recover from SD card failure |
|
Posted by: Dagremote - 11-10-2017, 06:56 PM - Forum: Ubuntu
- Replies (1)
|
|
Had a Pine64 running Ubuntu for 6 months without probs. After a reboot, the device did not start. Have a second pine so was able to mix and match things and determine that the SD card was the issue. The original Pine boots with a new SD card.
The 'bad' SD card mounts and is perfectly readable on Linux or Windows desktop system. Tried to format a new SD card and copy the contents from the bad SD card but no joy.
I understand that not all SD cards are high quality, and also that shit can happen ... so, the question is - how can we backup the SD card so we can recover from a bad SD card?
W.
|
|
|
|
| Resize video playback |
|
Posted by: Mick - 11-10-2017, 01:43 AM - Forum: Linux on Pinebook
- Replies (4)
|
 |
Hi,
I own my PineBook since few months yet, and I have not installed the 32 eMMC requested in the same order. But that's not the point  , just to say that I'm still working with the pre-installed linux distribution (xenial-mate, if I remember well).
Quite often I play video, either with the default media player or with vlc, and both have the same effect: video frame is always on top, and there is no way to resize it. The former is not a big inconvenience, the latter is though, since: - bigger video than the screen resolution are not visible
- player controlls (play, pause, stop, full-screen, etc.) are not accessible.
Any hint about this issue?
|
|
|
|
|
Has anyone tried dual-booting from a single SD Card yet? I'm hoping to find something that works on this platform that's similar to NOOBS Companion for the RPI, allowing me to easily jump back and forth between LibreELEC (KODI) and LAKKA. Anyone have any experience with this topic yet?
