| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,810
» Latest member: katarina8
» Forum threads: 16,301
» Forum posts: 117,352
Full Statistics
|
| Latest Threads |
Battery connector dead
Forum: PinePhone Hardware
Last Post: mikeb
Yesterday, 02:24 PM
» Replies: 5
» Views: 2,710
|
Window Maker Live for Pin...
Forum: Linux on Pinebook Pro
Last Post: wdt
Yesterday, 11:36 AM
» Replies: 6
» Views: 666
|
curious iPhone user here
Forum: General Discussion of PinePhone Pro
Last Post: Kevin Kofler
01-14-2026, 06:27 PM
» Replies: 20
» Views: 9,058
|
performance wise which ip...
Forum: PinePhone Pro Hardware
Last Post: biketool
01-14-2026, 10:13 AM
» Replies: 1
» Views: 81
|
what stopped pinephone pr...
Forum: General Discussion of PinePhone Pro
Last Post: biketool
01-14-2026, 09:56 AM
» Replies: 1
» Views: 102
|
Setting up a Rock64 v3 fo...
Forum: Rock64 Tutorials
Last Post: MinimumJargon
01-14-2026, 07:06 AM
» Replies: 0
» Views: 44
|
What part is L2000 precis...
Forum: RockPro64 Hardware and Accessories
Last Post: jssfr
01-14-2026, 06:29 AM
» Replies: 0
» Views: 54
|
Fedora + Phosh for PinePh...
Forum: PinePhone Software
Last Post: tllim
01-14-2026, 12:22 AM
» Replies: 77
» Views: 201,846
|
Rock64 v3 Tx/RX and GPIO ...
Forum: Linux on Rock64
Last Post: MinimumJargon
01-13-2026, 07:22 PM
» Replies: 1
» Views: 62
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: jssfr
01-13-2026, 11:14 AM
» Replies: 2
» Views: 106
|
|
|
| 2GB Pine 64 only has 1GB |
|
Posted by: ChrisLane - 05-13-2016, 04:44 PM - Forum: System Memory
- Replies (15)
|
 |
Well unfortunately I have not yet heard back from the pine support team.
The Pine device that I received should have 2GB memory but unfortunately only appears to have 1GB.
Code: [chris@pine ~]$ cat /proc/meminfo
MemTotal: 1002164 kB
The box states that the device should be 2GB as well as the text on the board.
Any advice?
|
|
|
|
| Wireless mouse & kbd recognized but not working |
|
Posted by: thehamguy1 - 05-13-2016, 12:56 PM - Forum: Debian
- Replies (9)
|
 |
My wireless mouse and keyboard work on all 7 of my other Linux and Windows machines, and even on the Pine64 Android distro, but not in Debian. It's puzzling. Entering "lsusb" shows the dongle is recognized (listed as Bus 3 Device 2 in the top USB port, Bus 4 Device 2 in the bottom port). So the USB dongle is recognized but after that, no function. Obviously all my experience back in the CP/M OS days isn't going to help here...
|
|
|
|
My pine is ready to ship! What's the status on emulation? |
|
Posted by: pqueiro - 05-13-2016, 10:16 AM - Forum: Game Station Emulation
- No Replies
|
 |
I've been trying to keep up with things (both on KryPtAlIvIaN's Compatibility thread and on Recalbox's GitHub) but things are at the moment less than clear. As far as I can tell, there's scattered reports of various games working here and there, but not much else.
So the question is... what's the status?
My plan at the moment is to slap Ubuntu on it and try to build Retropie from source. I have no idea if this is going to work though.
Recalbox's fine folk seem to be converging on a working solution - should I hold off for that instead?
Thanks!
|
|
|
|
Snow-like noise in dark areas of video |
|
Posted by: RanTalbott - 05-13-2016, 07:27 AM - Forum: HDMI Port
- No Replies
|
 |
I'm using the latest 16.04 image (xubuntu-xenial-20160501-longsleep-pine64), and seeing some annoying noise in dark areas of the screen. Mostly (near-)black ones, but some dark blue ones.
The noise is small numbers of individual pixels flickering between the expected color and a light one (maybe the 1's or 2's complement?? It looks a little yellowish when it's on blue). I don't see it on a normal desktop display, except in the terminal emulator window while the "logout" popup is displayed.
It's not always present in blue areas of the screensavers, but does show up sometimes.
It's always there during video playbacks, with videos recorded using the XviD, DivX 5, and MPEG codecs (all the types I've tried). It also shows up in MJPEG streams from an Axis camera. So it doesn't seem likely to be a codec bug.
It looks like it's probably either a hardware or a video driver bug. Any suggestions on how to isolate it?
Thanks,
Ran
|
|
|
|
|