-
Posts
1148 -
Joined
-
Last visited
Everything posted by lanefu
-
Yeah we ususlly ssh in on first boot so wouldn't see that. But yes its only cosmetic and you could just press enter and proceed as normal If you are particular about your system and avoiding changes you may want to freeze the kernel on your 21.02 install via armbian-config Add jira task https://armbian.atlassian.net/browse/AR-743
-
Monitor Resolutions on RockPro64
lanefu replied to rrowles2000's topic in Common issues / peer to peer technical support
4K is hard. I gave up on it. Try this conf but remove the screen section to make sure you're at least using the drm display driver https://raw.githubusercontent.com/armbian/build/master/packages/bsp/pinebook-pro/xorg.conf -
I want a stripped down board that has real 802.3af POE
-
Thanks @PetrozPL Added https://armbian.atlassian.net/browse/AR-735
-
usb dongles mapping to /dev
lanefu replied to gogoer's topic in Common issues / peer to peer technical support
I think udev is appropriate.. its a situation that could just as easily be needed on a x86 machine w/o device tree to enforce enumeration -
usb dongles mapping to /dev
lanefu replied to gogoer's topic in Common issues / peer to peer technical support
This is great! I had a similar problem to solve -
Yeah first run has a few distributed touchpoint.. kind of needs to be consolidated and more intuitive to manage as you describe.. I know many have interest in being able to bundle in cloud-init to the image.. and making the first-riun and first-login components a little more polished would help with that.
-
Doing this should probably trigger it. https://github.com/armbian/build/blob/master/lib/distributions.sh#L157 Also take a look at https://github.com/armbian/build/blob/master/lib/distributions.sh#L372-L379 Might be related to https://github.com/armbian/build/blob/master/packages/bsp/common/lib/systemd/system/armbian-firstrun-config.service#L9 Probably best to keep conversation here for now. Mostly we use issues in GitHub for major bugs / problems
-
if you wanted to build last stable release that would be code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } LIB_TAG=v21.02 .. but you probably just want to stick with building from MASTER and use "current" as your kernel branch. code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; }
-
Pine64 H64 does not boot from eMMC [solved]
lanefu replied to __Dirk__'s topic in Allwinner A64, H5 and H6
FYI The house-brand Ameridroid eMMC chips work without issue on my pineh64-b. Didn't make any adjustments to dts etc. Running kernel 5.10.21-sunxi64 https://ameridroid.com/products/emmc-5-1-module-blank?_pos=3&_sid=086ab1282&_ss=r -
Here's an example of adding RT patches to allwinner build. https://github.com/lanefu/build/commits/RTAttempt
-
yeah its a really weird error..I'll try switching to https://github.com/mar10/pyftpsync/
-
yeah... it seems like network issue.. or something. need @Igor to look on his side.. I read concurrency can cause problems.. so I made some adjustments so that it only does 2 sessions.. but still getting error
-
Yeah weird error message
-
maintenance complete
- 1 reply
-
1
-
Gonna patch and reboot forum server at 10PM my time. (US EAST) should be quick.. assuming no surprises
-
Didn't I do the 2nd one? maybe it was just the thread
-
Congratulations! Are you marrying S905X?
