[SOLVED] Slarm64 on the Pinebook 1080 - help with kernel?
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Cool! I will test this tonight. I spent the weekend rebuilding my build-box. I am guessing I corrupted the eMMC, because booting became unstable after a while. Now that I am done with that, I can try out what you were building this in the meantime.
Okay, I have been testing your new image. Everything seems to work fine with one tiny exception: I cannot get the bluetooth adapter to respond at all now. If I reboot into my usual desktop, the adapter works fine, but the blueman bug is still there. I cannot even check the blueman situation in the new image because the bluetooth adapter is not recognized at all. The fix might be a simple one, and so far that is the only issue I have detected.
I will back up the system I have on the eMMC and will try the setup option to install to the eMMC sometime this week. I will post here my findings.
Thanks for this, I appreciate the effort and was thrilled to see the image boot to a command prompt. That was exciting!
(the delay is me unlocking an encrypted drive during boot)
So I dropped those (all four) into the same directory on the new image you provided, and the bluetooth adapter was finally available via bluetoothctl. I still get the blueman bug in this image, but that is another thread already....
So, if we can figure out why we wind up wind missing firmware files, then I would consider this a success. Every other feature I have tested so far works fine, including screen brightness, which is something missing from half of the images on the Pine wiki for this machine.
Any clue how to bring in the extra firmware files?
(the delay is me unlocking an encrypted drive during boot)
So I dropped those (all four) into the same directory on the new image you provided, and the bluetooth adapter was finally available via bluetoothctl. I still get the blueman bug in this image, but that is another thread already....
So, if we can figure out why we wind up wind missing firmware files, then I would consider this a success. Every other feature I have tested so far works fine, including screen brightness, which is something missing from half of the images on the Pine wiki for this machine.
Any clue how to bring in the extra firmware files?
This one is a winner! 100% functionality on an SD card. Next, I will test the setup function to install to eMMC. I am prepping for that now, and will report back my findings here.
Next, I will test the setup function to install to eMMC. I am prepping for that now, and will report back my findings here.
The setup script does nothing and gives no errors. A look at /root/setup.sh shows that there is no mention of pinebook at all. Is this script only meant for other boards, or has pinebook support just not been added to the setup script yet? I am just curious. I only started to look at the script just now, I will have time to dig deeper later in the week.
The setup script does nothing and gives no errors. A look at /root/setup.sh shows that there is no mention of pinebook at all. Is this script only meant for other boards, or has pinebook support just not been added to the setup script yet? I am just curious. I only started to look at the script just now, I will have time to dig deeper later in the week.
After making that one change, the script runs, and it copies the system over to the eMMC as expected. However, the result will not boot. Powering on results in a black screen and not much else. I also noticed that uEnv.txt was not altered. No rootdev line was added, for example. So it seems like something is going wrong with the fix_config() function, perhaps?
Last edited by shelldweller; 02-17-2020 at 10:23 AM.
Reason: user agent switcher put a windows logo in my post. yucky. trying to fix that....
After making that one change, the script runs, and it copies the system over to the eMMC as expected. However, the result will not boot. Powering on results in a black screen and not much else. I also noticed that uEnv.txt was not altered. No rootdev line was added, for example. So it seems like something is going wrong with the fix_config() function, perhaps?
Thanks, for H3 there was no need to change the root device due to the fact that when removing the SDcard eMMC, it becomes mmсblk0. fixed
Thanks, for H3 there was no need to change the root device due to the fact that when removing the SDcard eMMC, it becomes mmсblk0.
Hmm, okay. That line is being set correctly in uEnv.txt now. But something is still wrong, and I am stumped. The SD card works fine, no problems there. The transfer works fine, I do not see any problems there.
The end result is still not booting at all. I see nothing on the screen, no u-boot messages, no error messages, just dark blankness.
I have been comparing the boot scripts on my working eMMC image (with the Arch kernel) to the boot scripts that the new image winds up with, and I see lots of differences, but I do not know enough to figure out what is important and what is extra code in there for other boards.
What really baffles me is that the SD card image boots just fine, but the eMMC transfer does not even try to boot. I cannot even tell if is booting without display output, or just not booting at all.
The next chance I have to play around with this, I will put something in rc.local on the eMMC to be able to tell if it is booting without display output or just not booting. More on that in another day or two.
I tried the first method of installing to eMMC listed in the README file, and I changed the block device as needed, and simplified a few steps for my setup. Here are the modified instructions that WORKED!
Code:
installation on a eMMC (for pinebook)
Flash the image to micro SD, then copy the .img file to micro SD filesystem.
Power up the board with micro SD and login.
Run below command for flashing to eMMC module
>>dd if=slarm64-current-*-base-rootfs-*-build-*.img of=/dev/mmcblk2 bs=1M
example : dd if=slarm64-current-*-xfce-rootfs-*-build-*.img of=/dev/mmcblk2 bs=1M
then edit 2 files in eMMC module:
>> mount /dev/mmcblk2p1 /media
>> echo "rootdev=/dev/mmcblk2p1" >> /media/boot/uEnv.txt
>> sed -i 's:mmcblk1p1:mmcblk2p1:' /media/etc/fstab
After done, power off board and remove micro SD. Then bootup with only eMMC module.
Now I am able to boot direclty from the eMMC. Very simple. I still do not know what is causing the setup script to result in an non-booting eMMC. However, with the above instructions, I am now where I need to be.
Thank you very much for all your help, I truly appreciate it. If you would like to figure out how to get the setup script to work, then I am willing to continue investigations. Otherwise, the image paired with the above instructions are satisfactory for my purposes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
