Werner reacted to dolphs in Switching SUNXI-DEV to 5.8.y (h3-h5-h6/megous)
OK I took a closer look in the patch directory ( which I should have done earlier ) .
Yet I found these patches ( below ), but till now I was convinced flag " EXTRAWIFI=no " would bypass these.
Anyway after removing these two I succeeded to build my first 5.8 image ( with most patches )
:~/armbian/output/images$ ls -l total 674496 -rw-rw-r-- 1 root root 792723456 Jul 17 08:53 Armbian_20.08.0-trunk_Orangepioneplus_buster_dev_5.8.0-rc5_minimal.img -rw-rw-r-- 1 root sudo 137 Jul 17 08:53 Armbian_20.08.0-trunk_Orangepioneplus_buster_dev_5.8.0-rc5_minimal.img.sha -rw-rw-r-- 1 root sudo 19667 Jul 17 08:53 Armbian_20.08.0-trunk_Orangepioneplus_buster_dev_5.8.0-rc5_minimal.img.txt
___ ____ _ ___ / _ \| _ \(_) / _ \ _ __ ___ _ | | | | |_) | | | | | | '_ \ / _ \_| |_ | |_| | __/| | | |_| | | | | __/_ _| \___/|_| |_| \___/|_| |_|\___| |_| Welcome to Armbian buster with Linux 5.8.0-rc5-sunxi64 No end-user support: built from trunk System load: 0.00 0.00 0.00 Up time: 1:50 Memory usage: 9 % of 986MB IP: 192.168.10.122 CPU temp: 51°C Usage of /: 18% of 3.5G
:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to email@example.com, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms.
root@orangepioneplus:~# lsmod Module Size Used by rfkill 32768 1 snd_soc_hdmi_codec 20480 0 snd_soc_core 180224 1 snd_soc_hdmi_codec snd_pcm_dmaengine 20480 1 snd_soc_core snd_pcm 114688 3 snd_soc_hdmi_codec,snd_soc_core,snd_pcm_dmaengine snd_timer 45056 1 snd_pcm snd 81920 4 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd zstd 16384 4 sunxi_cir 20480 0 sunxi_cedrus 36864 0 rc_core 53248 2 sunxi_cir videobuf2_dma_contig 24576 1 sunxi_cedrus v4l2_mem2mem 32768 1 sunxi_cedrus videobuf2_memops 20480 1 videobuf2_dma_contig videobuf2_v4l2 28672 2 sunxi_cedrus,v4l2_mem2mem dw_hdmi_cec 16384 0 dw_hdmi_i2s_audio 16384 0 videobuf2_common 53248 3 sunxi_cedrus,videobuf2_v4l2,v4l2_mem2mem videodev 249856 4 sunxi_cedrus,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem mc 53248 5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem panfrost 65536 0 sun8i_ce 28672 0 gpu_sched 32768 1 panfrost display_connector 20480 0 crypto_engine 20480 1 sun8i_ce zram 36864 3 realtek 24576 1 i2c_mv64xxx 24576 0 dwmac_sun8i 28672 0 mdio_mux 16384 1 dwmac_sun8i
This means now things drill down to go thru the patches which need to be either removed or updated for kernel 5.8 ( and u-boot )
Werner reacted to IgorS in Mainline kernel DRM problems on OrangePi
Finally good news!
Today (2020-07-14) for ubuntu bionic becomes available mesa update, following packages:
libegl-mesa0 libegl1-mesa libgbm1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglx-mesa0 mesa-va-drivers mesa-vdpau-drivers
After that, xfce desktop on orangepi2e starts to work flawlessly with kernel 5.4.xx (in my case 5.4.51) again.
Exact versions of packages:
igor@orangepiplus2e:~/trash/mesa$ dpkg -l | grep 'mesa\|libgbm1' ii libegl-mesa0:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:armhf 20.0.8-0ubuntu1~18.04.1 armhf transitional dummy package ii libgbm1:armhf 20.0.8-0ubuntu1~18.04.1 armhf generic buffer management API -- runtime ii libgl1-mesa-dri:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:armhf 20.0.8-0ubuntu1~18.04.1 armhf transitional dummy package ii libglapi-mesa:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the GL API -- shared library ii libglx-mesa0:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 8.4.0-1 armhf Miscellaneous Mesa GL utilities ii mesa-va-drivers:armhf 20.0.8-0ubuntu1~18.04.1 armhf Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:armhf 20.0.8-0ubuntu1~18.04.1 armhf Mesa VDPAU video acceleration drivers
Werner got a reaction from David-L in Modules ds290 missing in kernel 4.19.62
May have been removed while merging upstream config. I'll take a look.
Aight there are two options for you:
- Replace the legacy with the current kernel which contains this module or
- Use the build script to create your own legacy kernel package which then will be up-to-date as well
Werner reacted to PittPC in SimpNAS Beta Released!
1. The install.sh script now installs the debian backports version of smartmontools which doesn't depend on Python 2 and is a much newer version. This also sped up the install process a bit.
2. Added single disk support OS/Data
3. Updated the update system, dashboard now shows the latest version, when you choose updates it ill now show the changes between the installed version and the current.
4. We added Rescan disks button to add volume in setup as well as add volume in the main web ui app.
5. The system no longer reboots after setup it now directs you directly to the login screen.
Werner reacted to Kyra in Switch kernel from legacy (rk3399) to current (rockchip64) on NanoPi M4 V2
I advise sticking with the legacy kernel until the stability issues with the current kernels (specific to the NanoPi M4 V2) have been resolved.
Werner reacted to guidol in SimpNAS Beta Released!
how about to "not touch" the network configuration?
Some dont like to have the system changed by an "additional" app like SimpNAS.
Pihole also doesnt change the network configuration.
armbian is normally using networkmanager and Iam personally like the old fashioned way of the /etc/network/interfaces because I dont like to run a service for every little OS puzzle part. Inlikeca short process-list in htop/top
some of my non-armbian ARM systems use pnly under 32MB for bootup.
So maybe add a option "let network as it is" and DONT TOUCH the ssh access, because thats for the most the way to access their device (no TTL-RS232)
Why ist SSH disabled? Doesnt systemd networkd work together with OpenSSH-server?
Werner got a reaction from mhc in About Building Armbian
That cannot be answered by a simple yes or no. It depends.
Let's take the 5.4 example.
If you follow the current branch it leads us to megi's orangepi-5.4 branch. If you check the Makefile (https://github.com/megous/linux/blob/orange-pi-5.4/Makefile)
you will notice that the actual version of this branch is 5.4.18. But when you compile the kernel it is actually 5.4.47 or something like that.
This means these patches come from Armbian. If you check the patch directory for your board family (https://github.com/armbian/build/tree/master/patch/kernel/sunxi-current)
you can see that the upstream patches are added here. If you need a very specific kernel version remove or rename the patches you do not need.
That was a quite easy example to get what you want.
On other sources, vanilla for example, it is a bit tougher. You would need to specify a commit at which point you want to use the sources.
Sometimes a board is fixed to a specific commit or kernel version because it is known that newer version of the same kernel branch are known to be broken and (as most of the times) nobody has time or resources to deal with it.
Werner reacted to sfx2000 in Armbian-NG, armbian's little brother project
In personal experience - it's generally doable... and it's really the makefiles for externals like device drivers that are the devils to be solved.
In any event - cross-builds produce the same performance as native - ARM on X86, MIPS on ARM, ARM on ARM...
For most folks - LEDE/OpenWRT has solved that particular problem...
Werner reacted to balbes150 in Armbian-NG, armbian's little brother project
Please contact the administration to move this topic to the TV box section. I would like to (as far as possible) continue this direction (native Armbian build directly on ARM devices). For skeptics. Recently, I completely moved the LivreELEC build to the ARM platform (i.e. the entire process of creating LE images and Addons now takes place on ARM rk3399\s922x devices). My dream is (perhaps) to try to transfer the ArmbianTV build completely to the ARM platform and get rid of the x86 dependency.
Werner reacted to sfx2000 in Help me to setup a Wifi AP via command line
** Network Manager CLI **
$ nmcli device status DEVICE TYPE STATE CONNECTION enp1s0 ethernet connected Wired connection 1 wlp2s0 wifi disconnected -- lo loopback unmanaged --
to check radio
$ nmcli radio WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled
Let's see what's out there... scan for AP's
$ nmcli dev wifi list SSID MODE CHAN RATE SIGNAL BARS SECURITY MYSSID Infra 11 54 Mbit/s 100 ▂▄▆█ WPA2 MYSSID Infra 132 54 Mbit/s 100 ▂▄▆█ WPA2 SOMEOTHERSSID Infra 52 54 Mbit/s 49 ▂▄__ WPA2 MYSSID Infra 149 54 Mbit/s 45 ▂▄__ WPA2 MYSSID Infra 11 54 Mbit/s 42 ▂▄__ WPA2 SOMEOTHERSSID Infra 1 54 Mbit/s 27 ▂___ WPA2
Now, let's connect to WiFi (note, one must be root or sudo access)
Connecting to an open AP
$ nmcli device wifi connect <SSID|BSSID> For a password protected AP, see below
$ nmcli device wifi connect <SSID|BSSID> password <password>
To set up a device as an AP - this assumes that WLAN0 is the wireless interface...
$ nmcli dev wifi hotspot ifname wlan0 <SSID> password "<password>"