-
Posts
14414 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Igor
-
I hope you flashed u-boot from armbian-install ? U-boot package does not update u-boot automatically.
-
Unisoc UWE5621DS on RK3566 device? calling Orange Pi experts
Igor replied to dieselnutjob's topic in Off-topic
It works with Armbian too. Just two years ago it was not in good condition -
Package `base-files` 25.* not built for trixie
Igor replied to Zoom's topic in Software, Applications, Userspace
Solved. -
Cubieboard 1 - No display output when booting Debian 12 image
Igor replied to Shakai2's topic in Allwinner sunxi
Check this thread -
Armbian 25.5.1 Noble Gnome can not open remote dosktop
Igor replied to 唐志's topic in Software, Applications, Userspace
Gnome uses Wayland and there some features don't work ... switch to X, where you will loose some functions, but remote desktop will work. FYI: https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277 -
Armbian Newsletter Coordination Meeting
Igor commented on Michael Robinson's event in Community Calendar
@Contributor/Maintainer In case you are avail.- 2 comments
-
1
-
- Frequently asked question
- Other/unspec
-
(and 2 more)
Tagged with:
-
https://github.com/armbian/build/pull/8334
-
We don't provide anything lighter then Gnome and there are some weird desktops in the build system, which most likely don't assemble as they are abandoned for a long time. I am not a Desktop guru ... perhaps someone else could give you other suggestions. I think Gnome is still the safest way, even it might eat more. But our Gnome is at least more or less vanilla, so no (Ubuntu) stuff coming with it.
-
This needs to be enabled: https://github.com/armbian/os/pull/332 As we started with a model without HDMI port, this was simply overlooked. Build with: ./compile.sh ENABLE_EXTENSIONS="v4l2loopback-dkms,mesa-vpu" That I don't know how it works if at all. Wayland is troublesome even on 1st class x86 hardware. Update: will rebuild images later today with mesa extension enabled.
-
I'm more concerned about what version 5 might break. Still, I don't think anyone makes Facebook account in order to login to Armbian forums 😄 and GitHub is not far from those I am afraid By the end of the day, this would be a symbolic gesture that works against practical ways. I think most of people uses Google login connector. Do we have any stats for that?
-
If this worked for you, I propose to open a PR, so there is a GitHub record of your work. Add it here https://github.com/armbian/build/tree/main/patch/kernel/archive/sunxi-6.12 Here you also need to pay attention to add to series* files.
-
Not supported by forum software. Keeping Facebook and Google operational requires constant attention and adjustement, while others worked so far without troubles.
-
Added instructions for joining your home lab: https://docs.armbian.com/WifiPerformance/#adding-a-new-device
-
FYI. HDMI out is broken on those board at the moment. Try to access the board remotely. We don't have people to maintain those old boards.
-
True. Also on most computers we have eth0 Not just eth Devices naming is a cosmetic thing from the outside / user perspection, while it has consistency issue from the inside and currently breaks initial (default netplan) configuration. Our job is not to tell user how to configure his network, but that network devices gets up at first boot. Now they do. Job done.
-
I just found one weird setting on R6S. Can you provide what is in this file: cat /etc/udev/rules.d/70-persistent-net.rules Reference for what to do: https://github.com/armbian/build/pull/8325
-
From the picture - I can only guess that kernel package was somehow not upgraded properly as kernel image files are missing. Perhaps they were removed by accident or there was some disk / file system troubles involved. @Chris007 Try hints from here: https://docs.armbian.com/User-Guide_Troubleshooting/
-
To be more precise - parameters that are provided to that driver. If driver would be the problem, both NICs would be down. You need to find / create correct settings (device tree), based on schematics. This forum (search) can provide plenty of resources and hints how to do this. Someone from community (with the device so testing can be done) has to sacrifice afternoon or more to get this in operation.
-
With logs, we could see if this is NIC not recognized or network stack problem. Community supported target are often not having anyone behind https://docs.armbian.com/User-Guide_Board-Support-Rules/
-
It's a progress! This or similar problem was seen / reported on H3 too.
-
It is possible that broken patch removal is already a solution.
-
What is the latest version of the RTL8189FS driver?
Igor replied to Kevin Hoang's topic in Beginners
They will provide you new drivers only if you will pay them to do that for you. End users, including this project, can do nothing about - we have negative budget and can only do best-effort work to keep those drivers at least operational with recent kernels: https://github.com/armbian/build/tree/main/patch/misc while bulk of the patches goes directly to the Git of specific driver. What you are hoping exceeds ability of amateur maintainers, those few people that are actually looking into the code and fix bugs that are made by kernel API changes. HW vendor is usually long gone from there - their development capacity is also limited and they are focused into current products. FYI -
Cubieboard 1 - No display output when booting Debian 12 image
Igor replied to Shakai2's topic in Allwinner sunxi
A10 / A20 hdmi support was reported as broken and bug was recorded https://armbian.atlassian.net/browse/AR-2674 some time ago. -
Here some troubles are expected ... Can you try manual steps to install docker by follow: https://github.com/armbian/configng/blob/main/tools/modules/software/module_docker.sh#L26-L56 installing packages, adding to group, adding docker bridge. This might reveal more. BTW. My F3 died - waiting for replacement.