How does this kernel differ from ayufan’s kernels?
Fantastic MrFixit, Have been looking forward to this. Thank you very much for all the hard work!
Quote: How does this kernel differ from ayufan’s kernels?
That's actually what I was wondering about as well at this point. They're both based on Debian stretch and feature-wise they are largely the same as well as far as I can tell.
PinePhone (BH 2GB + CE 3GB) // RockPro64 4GB (rev. 2.1) - OMV NAS // PineH64 3GB (model B) - off-prem OMV NAS // Pine64-LTS 2GB (rev. 1.2 + Playbox) - Domotics server
I just tested this image yesterday and was happy to see that is worked quite well. It resolved the PCIe issues I had where previews versions would tell me the connected disks have table issues and can't be mounted.
I still need to play around with it but so far this is the best image I found for what I want out of the RP board.
Thank you all for your feedback! To address the kernel question - there's actually a large amount of differences, but the primary difference I would outline is that I have taken the time to back port a lot of commits from later kernels or from mainline. There's also different configs - and therefore different modules and drivers included. Additionally, ayufan's builds use a different partitioning table than I am using.
Different builds will work better for different users, so I always encourage you to try both to determine what best fits your needs.
05-21-2019, 01:27 PM
(This post was last modified: 05-21-2019, 01:28 PM by Mentaluproar.)
I have mine running a prerelease build openmediavault build from ayufan and switched APT to debian testing so I could do time machine backups over samba. I had a few incidents where the drives would unmount themselves but it hasn’t happened in a while so I’m guessing it’s fixed. Ayufan lists backporting mainline fixes too.
I use mine to host Plex, time machine backups, drive a few 3D printers, running homebridge and as a dumping ground for big files me and my roommates want to keep but not take up space on our portable devices. How would your kernel compare to ayufans in such a use case?
I’m not trying to be a dick. I’m genuinely curious. There can never be too much attention on supporting hardware, but when there are two different solutions created by two different developers rather than two developers working on one unified solution, there must be some technological differences.
06-01-2019, 11:49 AM
(This post was last modified: 06-01-2019, 12:13 PM by pbut5.
Edit Reason: Extra info
)
Still not working for me.
No pcie card detected on boot and no network when there's a card in the pcie slot.
And with card in the pcie slot it seems to lockup after boot (my keyboard doesn't work when plugged directly into the rockpro so cannot login and no cursor at the login prompt).
edit:
Also a custom built kernel keeps crashing on armbian with a card in the pcie slot. Without a card in the slot it appears to boot and work ok.
What I'm looking for is GCC with NEON support .
And, not a cross compiler, so must run on the RockPro64.
Reason: LPCnet and the FreeDV project.
Any pointers please?
And yes, I loaded mrfixit2001's Debian minimal image on 1st June 2019
Alan B
