support is based on kernel…so see the table you mention for 4.19
the debian itself is only a base-system (no x-server, no dhcp/dns-server & no hostapd atm)
5.x has no LTS at the moment so it’s not listed in the table…most time i don’t find the time to merge all features in the main-branch because the merge-window of next kernel-version starts/rc1 is out before and i need to port the drivers to this new version which takes some time…also in 5.x i have spend much time for testing/debugging phylink-patches on bpi-r2 and bpi-r64
mostly i have ported all drivers (hdmi,wifi,poweroff) in the first week after rc1 is out…you can test them separately or merging these together to have a all-feature kernel
mhm, i’ve seen i forgot to set filesystem-label so it may cause problems installing newer kernel using my build.sh, have fixed this…
How to stop get random mac on every boot? Because my provider want me to have static MAC to enter network and then I need to get DHCP IP address.
I have these lines in /etc/network/interfaces
auto wan
allow-hotplug wan
iface wan inet dhcp
hwaddress ether 6c:3b:6b:48:b7:8c
but problem is that it try to obtain IP from DHCP before these lines applied and of course no internet connection until I manually ssh to box and run - dhclient wan. After it - all goes well.
this file is an example for devicetree-overlay, but you have to configure uboot to use separate dts and this overlay which is not trivial, so as a start just change the dts itself which is the easiest way
Yes, compiled on x86 linux and booted success. Also found that your kernel lacks some module to get pptp vpn to work - ppp_async so edited .config file and recompiled it again. May be you can put this in your debian buster distro by default?
Also interesting for which purposes - eth0/eth1? First I was think I can give eth0 local IP and all lanX interfaces will reply to this IP… but no… was make br0 and put all lanX interfaces to it…
just say me the config-options needed…i don’t wanted an all-yes-config so i activated only the options needed by me and the people reported options to me. but this is kernel-related, not image-related.
eth0/eth1 are the (internal) cpu-ports between SOC and Switch, lanX/wan are the (physical/external) dsa-ports of the switch where you put your rj45-jack in. CPU-POrts have to only be set “up” without any other config. IP-configuration has to be done on dsa-ports (lanx). if all lan-ports need to be in same lan-segment, they have to be bridged and get 1 IP-address. if you use different lan-segments (like me) you can give any lan-port another IP-adress
Yes, need all lan ports to be in one network like other router this do out-of-box. I don’t ask about all-yes but CONFIG_SOME_MODULE=m - will be great and slim and don’t need to waste hour time to google - what the heck is logs says and found that it need module that not present…
p.s. also found if I choose deb package on kernel compile - it give kernel wrong names. If I choose pack - all names correct.
everybody needs another “some_module” and figuring out which module can be needed by somebody and its depencies will waste my time it is a basic kernel where everyone can add stuff he needs and maybe tell me what’s needed additional to it. but i don’t want to add modules/builtin-function nobody needs
for naming-issue you mean the file of deb/tar.gz? or inside the file?
deb is designed to install multiple kernels so the uImage has the version-number appended and change uEnv.txt on install
for naming-issue you mean the file of deb/tar.gz? or inside the file?
inside. because deb is simplier way to install and tar.gz file need to be unpacked manually to corresponding folders. don’t know for which reason this is because system have mounted boot and root folders - why not make same structure in tar.gz file… or may be some script with these BPI2-BOOT BPI2-ROOT folders that rename files/folders to some old…
compiling it now, let’s see what’s happen.