Hi all, I have run into a snafu in trying to set up a printer on my pinebook. All goes well until i get ask for a username and password. I tried the pine64/pine64 with no luck. I think that i read some where about a root password but am unable to find a source. Do i need a different password to install a printer? This is just a test as i am having problems on a linux mint printer install and needed to know the process.
Thanks for any help
IceMeister
I bought rock64 and now I am trying to prepare very minimal script that will build all steps from scratch. Intend is to publish it to buildroot repository later. But I have problem booting kernel. Some information what have I already done and where I am stuck.
1. tpl, spl and uboot are build from ayufan repository, branch "2017.09-rockchip-ayufan-1035-gd646df03ac", and "rock64-rk3328_defconfig", no changes have been made to the files. To create tpl/spl image I use these commands (this is flashed to 0x40). Note, no rockchip binary blobs anywhere!
2. then ATF is built, also from ayufan repository and "rk3328" as a platform. Generated BL31 is used to generate u-boot.itb (with make u-boot.itb from ayufan repo). That u-boot.itb is flashed to 0x200 on sdcard.
3. Kernel, no surprise here, it's from ayufan repo, "rockchip_linux_defconfig" used and "rockchip/rk3328-rock64" dts from in-tree, again no changes have been made.
4. Now sdcard image is generated with this config:
It's in mbr dos format (so no gpt). On rootfs there is extlinux, Image and dtb in /boot directory.
5. Toolchain is gcc 7.x and binutils 2.29.x.
Now logs,
Code:
<debug_uart> U-Boot TPL board init
configuring DDR parameters
LPDDR3
DRAM frequency: 800MHz
configuring DDR parameters
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2017.09 (Nov 11 2018 - 00:07:11)
setup_ddr_param 1
booted from SD
Trying to boot from MMC2
U-Boot 2017.09 (Nov 11 2018 - 00:07:11 +0100)
Model: Pine64 Rock64
DRAM: 4 GiB
MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=00000000000000000000000000000000
serial=0
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 10
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
205 bytes read in 36 ms (4.9 KiB/s)
1: rock64 linux-next
Retrieving file: /boot/Image
20054024 bytes read in 17452 ms (1.1 MiB/s)
append: earlyprintk earlycon=uart8250,mmio32,0xff130000 console=ttyS2,1500000n8 console=tty0 root=/dev/mmcblk0p1 rootwait
Retrieving file: /boot/rk3328-rock64.dtb
70953 bytes read in 29 ms (2.3 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Device Tree to 00000000fceed000, end 00000000fcf01528 ... OK
Starting kernel ...
And that's it. No more output and I am completaly out of ideas how to proceed.
u-boot properly boots, it finds my kernel and dtb, it loads it but it fails to boot it. Kernel and dtb are good, I downloaded slackware image for rock64 and replaced Image and dtb, and it started - I could see todays date and my build host in kernel message, so it's enough of a proof linux and dtb are generated properly.
Anybody got any idea what am I missing? I was thinking that it might be mbr instead of gpt or missing initrd, but slackware image doesn't use them as well. I would appreciate any advice or ideas how to proceed with that.
My Pinebook 11.6" 1080 just arrived and I thought it might be interesting to share my first impressions and maybe other can add theirs.
Unboxing
The Pinebook arrives with some slim but useful packaging. There is the Pinebook, the power adapter and some nice sticker with the Pinebook logo if you want to decorate yours.
The Pinebook arrived charged , in my case about 90% so you can start right away.
The Pinebook is white from the outside with logo or branding which makes it look really nice. My first test was to try a few keys on the keyboard and I actually like it. The layout for some keys is a bit unusual for some keys but in general what you expect. (e.g. the " key requires to press Fn as well as Shift, well..)
The touch-pad is on the smaller side, but I can say already that the later test showed that it is ok.
So that's all good. Let's turn it on.
]
First use
As mentioned, the battery comes charged to a degree so the first good thing is that it turns on in first place. Brownie points.
The display brightness on my device what set to somewhat 50% which made it very dark. So the very first thing was to change that in the Settings in Power management.
Once that's done it turns out that the dispaly is actually really nice. It seems not to reflect at all and my first use was outside in the sun, which was possible.
Given the high resolution of the display the all text is on the small side. There is a pinned thread in this forum that explains a few recommended setup changes. So this was my next step.
The speed of the laptop is ok. It is probably worth to turn of some of the more playful functions of the window manager like fade in/out or translucency, with that the Pnebook gives a more snappy impression. I intend to write up all configuration changes later.
One thing I noticed is that the compositor uses software rendering and not OpenGL in the standard setup. But I will only try at a later stage if OpenGL works as I manged to lock myself out of KDE by playing around with that on a different system.
So far my impression is very positive. The general speed is very usable and the Pinebook has a good feel to it.
The next step seems to be to actually install the system completely. There is an Icon on the desktop to do that. I will try this now.
I just got my rockpro64 2gb (board rev 2.1), and while it boots up fine, it isn't detecting my LSI HBA PCIe card.
lspci just gives no output at all, so I don't think it is simply a missing kernel module.
I'm using the debian stretch image off of the wiki.
I'm also getting errors in dmesg that may or may not be relevant:
[ 8.566853] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[ 16.581959] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[ 32.584126] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[ 64.586143] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[ 128.588049] cdn-dp fec00000.dp: [drm:cdn_dp_request_firmware] *ERROR* Timed out trying to load firmware
I did do an apt-get update/upgrade and rebooted, and the issue persists. uname -a output:
Linux chunk1 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 GNU/Linux
That kernel doesn't look terribly fresh...
I'll also go ahead and confess that while I'm quite comfortable with linux inside and out, I rarely use debian-based distros, so please do list complete instructions (typically I use Gentoo) or provide links if you want me to do something like run a custom kernel.
I recently received a wifi BT adapter from Edimax and I need some help installing the driver. apparently I have to actually make the driver from the files? the directions are so sparse for a dummy like me.
hello, I've recently received my Pinebook with the 1080 screen. all was going well until I dimmed the screen too far in the plasma settings window. Now my screen is black when it is on. during boot I see things as the boot sequence clearly is not affected by the plasma setting. How can I fix this without being able to see anything? This is with the original install.
If the slider goes all the way to the left does plasma actually go black or is there some weakness with my screen in this Pinebook?
