Hi all,

I'd like to adjust u-boot, but I couldn't find /etc/default/u-boot like in my PBP/Debian, how it works in Mobian?

lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mtdblock0    31:0    0    4M  0 disk
mtdblock1    31:1    0    32K  0 disk
mtdblock2    31:2    0  256K  0 disk
mmcblk1      179:0    0  58.2G  0 disk
|-mmcblk1p1  179:1    0  3.9M  0 part
|-mmcblk1p2  179:2    0    64K  0 part
|-mmcblk1p3  179:3    0    4M  0 part
|-mmcblk1p4  179:4    0    4M  0 part
|-mmcblk1p5  179:5    0    4M  0 part
|-mmcblk1p6  179:6    0  112M  0 part /boot/efi
`-mmcblk1p7  179:7    0  58.1G  0 part /
mmcblk1boot0 179:32  0    4M  1 disk
mmcblk1boot1 179:64  0    4M  1 disk
mmcblk1rpmb  179:96  0    16M  0 disk
zram0        252:0    0 322.9M  0 disk [SWAP]
zram1        252:1    0 322.9M  0 disk [SWAP]
zram2        252:2    0 322.9M  0 disk [SWAP]
zram3        252:3    0 322.9M  0 disk [SWAP]
zram4        252:4    0 322.9M  0 disk [SWAP]
zram5        252:5    0 322.9M  0 disk [SWAP]



is there anything i have do for the pinebook to see the nvme?

June 26, 2020  Friday

When will the next offering of PineTab open for 'Pre-Sales'   ?

 Do we know yet what operating system iy will ship with ?

      Thanks  !

Hey guys, wasn't sure exactly where to post this, but I suppose it is an Armbian on PineA64(+) issue?

I'm trying to use my PINEA64 as a chip flasher to install coreboot on the ROM chip of my Thinkpad X220, as of these guides:

https://tylercipriani.com/blog/2016/11/1...pberry-pi/

https://karlcordes.com/coreboot-x220/

These guides use a Raspberry Pi with Raspbian however. I'm using the PineA64+ with 2GB RAM with Armbian buster (Linux 5.4.43-sunxi64)

Although flashrom successfully recognises the chip

Quote:

Code:

sudo mkdir flashrom && cd flashrom
sudo git clone https://github.com/flashrom/flashrom.git
cd flashrom
sudo make
sudo make install

I have flashed versions from 20200615 to the latest nightly and they all have the same issue on my Braveheart Pinephone. On booting and entering 1234 the ap drawer is presented and then 2 seconds later the screen goes off . I then no longer have access to the phone. I can unlock it again but to a blank screen. Help ?????

Hi folks,

It seems some of us are having issues with the cellular network in our pinephones and I thought it would be useful if we can get a list of the combinations to try to look for what is the culprit

HTH

haveing a really hard time too get the mobiel internet working
 some have any tiips or  picure how too sett it up

Hello everone,

I just booted postmarketOS from my SD card and logged into it over SSH. I noticed that

Hi there, I recently received my PinePhone, and while I'm excited about the project, the phone itself is not totally usable, yet. I get that this has been established, while I admit I didn't read the fine print, my old phone still works for now and my PinePhone is something I'll ease into.

My questions are as follows:

1. Is it safe to assume my hardware will not need to be upgraded? I'm assuming all the updates from here on out will be software, and sometime — maybe in a few months, maybe a year — I'll be able to use my PinePhone as my primary phone. 
   
2. Realistically, when do you think the PinePhone will be more or less ready for prime time? Are we thinking 6 months? A year? Just curious. sorry if this has been addressed elsewhere.
   
3. If I'm going to dual boot, what other OS is the farthest along? I read that the next sound of PinePhones will ship with Postmarket OS, but PinePhone's position seems to be that UBports is the most stable right now. Someone on the forum said Mobian is working best for them.
   
4. Is there any reason not to run the bleeding-edge repos? At this point, if the phone is semi non-functional anyway, It seems the fastest way to get stability would be to move to the dev channel.
   

Got my first PBP a couple weeks ago - Manjaro KDE ... did the steps in the wiki for it:

https://wiki.pine64.org/index.php?title=...KDE_system


Everything was running fine..... until:  I got the debian image onto SD card and booted it.   The screen was immediately over bright, flickering rapidly & steadily, and had a vignette effect (darker soft band around the outer edges).    I booted Debian a couple more times and observed the same.   then I removed microSD and booted back to manjaro KDE and the same video effect persists! 

So, what do I do now?   did booting Debian jack the firmware or something?   Is this a coincidental manufacturers defect?