(almost) upstream uboot/atf
#11
i strongly advise against using this with the mrfixit debian. that debian kernel is built to work with firmware that works differently in important ways, using upstream firmware may not work at all. that said, the article was written assuming an aarch64 host (manjaro). the mrfixit debian is, i think, a 32 bit userland, so even there you'd have to cross-compile for aarch64. i have absolutely no clue how debian names its cross-compiler packages though.

cloning does work fine here, even though it takes a while and the progress output for http clones really isn't great Sad will have to do something about that eventually ...
  Reply
#12
(01-15-2020, 08:31 PM)dhivael Wrote: i strongly advise against using this with the mrfixit debian. that debian kernel is built to work with firmware that works differently in important ways, using upstream firmware may not work at all. that said, the article was written assuming an aarch64 host (manjaro). the mrfixit debian is, i think, a 32 bit userland, so even there you'd have to cross-compile for aarch64. i have absolutely no clue how debian names its cross-compiler packages though.

cloning does work fine here, even though it takes a while and the progress output for http clones really isn't great Sad will have to do something about that eventually ...

Gotcha. I'll have to work from my daniel scripted native Debian. I targeted a USB for an interim test - only to find the stock uBoot doesn't order this before the EMMc. Haven't cracked the case for the switch or anything, yet.
— Jeremiah Cornelius
"Be the first person not to do some­thing, that no one has thought of not doing before’’
— Brian Eno, "Oblique Strategies"
  Reply
#13
@dhivael I think I experienced error in your uboot.

When I power on my pbp usually nvme drive doesn't get initialized properly and is not visible by OS. It's a lottery. On 6-7 subsequent boots it is ok and visible by OS once.

I don't get that behaviour using other uboots.
  Reply
#14
that's odd. this one doesn't do anything with nvme, and it shouldn't matter once linux has started running. could this be another nvme power issue in disguise? if only we had an nvme drive here to try this out with Sad
  Reply
#15
(01-16-2020, 07:18 AM)dhivael Wrote: that's odd. this one doesn't do anything with nvme, and it shouldn't matter once linux has started running. could this be another nvme power issue in disguise? if only we had an nvme drive here to try this out with Sad

Power issue was the first thing that came to my mind but after I reverted to previous uboot I don't get that behaviour.

I really have no idea how to explain it  Confused 

I have also stressed the machine today to the absolute limits in terms of IO. Doing dd back and forth from emmc to nvme and the other way. Everything on battery and nothing wrong happened.
  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  How to boot Manjaro from NVME with uboot on eMMC as400 0 65 01-16-2020, 12:10 PM
Last Post: as400

Forum Jump:


Users browsing this thread: 1 Guest(s)