Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Interests

Contact Methods

  • Website URL

Recent Profile Visitors

8287 profile views
  1. I'm currently finishing the last features for builders, like : the ability to provide a list of packages to uninstall before generating the image; limiting the desktops selection menus to the ones supported by Armbian and the architecture; parsing the distribution info from configuration files. I also went back to a clean Armbian fork, https://github.com/Miouyouyou/build/tree/desktop , so that pull requests are 'doable'. I still need to re-arrange the changes into specific branches to make pull requests "nicer" and also : add documentation for the new features; remove the whole debug messages mess; refactor a good part of the new code.
  2. I thought about it and I guess this could be implemented by aggregating the information provided in custom/boards_families and custom/boards . That could also be implemented by just created a folder, then creating symlinks to in the right places, though, Git symlinks might pose some issues on some Windows systems.
  3. @JMCC The current system actually supports "appgroups", which should provide enough flexibility in regards to Hardware acceleration packages and multimedia apps. The appgroups can also contain additional packages depending on the selected board and Desktop Environment.
  4. Greetings, I'm currently modifying the Armbian build system, making it easier to add new desktop environments and application groups. This architecture is subject to heavy modifications until it is merged with the current Armbian build system. A repository with the modified build system is available here : https://github.com/Miouyouyou/armbian-desktop Currently, I only tested adding Ubuntu Focal + XFCE and application groups, since I had to make sure that the postinst and create_desktop_package.sh were actually aggregated correctly, now that they're split into multiple files, and, for comparison, we only have such scripts for XFCE. Also : the current list of packages for XFCE include unrelated packages (like neverball), added to test the packages files aggregation; there's a lot of debug messages added here and there, in order to have an overview of the current build state. The actual packages list for other desktop environments and distributions, along with the scripts, still have to be added. (They're currently empty) That said, I'd like to have a few maintainers test (quickly) the new architecture, in order to check if there isn't any obvious feature missing. So, here's how to add a desktop environment with the new architecture : Adding a desktop environment Currently, only official repositories are supported. Let's say that you want to add that new desktop environment "superduperde", that is now available on official on Debian/Ubuntu repositories. First, focus on one specific distribution like focal (Ubuntu) or buster (Debian). In our example, will take focal. We'll create our first configuration 'full', which should provide the DE along with all its specific apps, widgets and the kitchen sink. Create the directory config/desktop/focal/environments/superduperde/config_full Create the file config/desktop/focal/environments/superduperde/config_full/packages Open the packages file, add the list of packages for apt. Then select it in the configuration menu, or pass the following variables to ./compile.sh : BUILD_DESKTOP="yes" RELEASE="focal" DESKTOP_ENVIRONMENT="superduperde" DESKTOP_ENVIRONMENT_CONFIG_NAME="config_full" Then test the resulting image ! Adding an appgroup Appgroups are roughly the same. Let's say that you want to add remotecontrol to the appgroups for Ubuntu focal : Create the directory config/desktop/focal/appgroups/remotecontrol Create the file config/desktop/focal/appgroups/remotecontrol/packages Open the packages file, add the list of packages for apt. Tale a look at https://github.com/Miouyouyou/armbian-desktop#the-architecture-added-to-the-build-system, for a more detailed documentation of the new architecture, and how to add special packages files for specific boards, and desktop configurations, along with specific debian/postinst and armbian/create_desktop_packages.sh files. What needs to be quickly tested : Modifying an existing desktop environment (gnome, kde, ...). Adding a new desktop environment or window manager (mate-desktop, i3, fluxbox, ...) Adding a new appgroup Bonus points for adding a desktop environment with Wayland support (but remember that default installations come with terrible OpenGL support on most boards !)
  5. If you're doing a simple copy (with Thunar, Nautilus, Dolphin or the simple cp command) there's no synchronisation mechanism, so it's either Replace All or Skip All, meaning it will replace every file present at the destination, or skip the copy of any file being present at the destination, regardless of its other attributes. What you're looking for is a synchronisation software, like 'rsync'. Though, you should try your hands with this software using a few dummy folders, since synchronisation softwares can be complex. Rsync allow you to synchronise two folders, with options like "copy the files not present", or "only replace files that are more recent", ... And can also do that through the network.
  6. Well, to add the "Virtual Framebuffer" driver, you'll have to reconfigure and recompile the Linux kernel using the armbian build tools, and ensure that CONFIG_FB_VIRTUAL is set to 'y (* compiled within the kernel)' or 'm' (compiled as a loadable module) when configuring the kernel... If you're not familiar with these tools, and you have no idea what "recompiling a kernel" means, the $3 Dummy HDMI plug might be WAY better for the time being. Even more due to the fact that I'm not sure that it will solve TeamViewer problem entirely. I just think so, since the virtual framebuffer can be used for "off-screen rendering purposes", so TeamViewer should be able to use it to read/write pictures into the framebuffer, and then send it through the network... Edit : Yes, you'll need to follow the guide you mentioned, if you want to reconfigure and recompile a custom kernel for your board.
  7. Note that the serial console clock changes to 1500000n8 when it boots, so be sure that the serial console receiver also reads at that speed, else you might not see any log after booting.
  8. I guess that you could always try to recompile your kernel and enable the "Virtual Framebuffer" driver ( CONFIG_FB_VIRTUAL=y ) and see how it goes. This should create a virtual /dev/fbX node... If you don't plug your monitor on startup, this one should be /dev/fb0 . Else, you'll have to play with udev to either force vfb to /dev/fb0 or the rockchip driver to /dev/fb1.
  9. Is it possible to get the patched .dts file at least ? This way, we could create a patch and integrate it to the armbian build tree.
  10. Here's the (very late) pull request : https://github.com/armbian/build/pull/2149
  11. Here's the patch : https://gist.githubusercontent.com/Miouyouyou/31d7d4ff0a2d5b8941d746ee6248f8b1/raw/a9ea4692642f1c59bfa6d562b9d35e25e5ce7123/drivers-staging-rtl8723bs-Initialize-structures-corr.patch While the kernel drivers doesn't generate any BUG now, the connection still fails in one way or another, since hostapd appears to be unable to setup wlan0 correctly. Or maybe it's just my hostapd.conf that's badly setup... Give it a try and tell me how it goes. From 48646460655b36cb616c7ad05f66f63631bfe1d8 Mon Sep 17 00:00:00 2001 From: "Miouyouyou (Myy)" <myy@miouyouyou.fr> Date: Fri, 14 Aug 2020 09:27:49 +0200 Subject: [PATCH] drivers: staging: rtl8723bs: Initialize structures correctly This avoids a BUG when freeing the ressources in nl80211_send_station . Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr> --- drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c index 2fb80b6eb..aef9cd888 100644 --- a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c +++ b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c @@ -2384,7 +2384,7 @@ void rtw_cfg80211_indicate_sta_assoc(struct adapter *padapter, u8 *pmgmt_frame, DBG_871X(FUNC_ADPT_FMT"\n", FUNC_ADPT_ARG(padapter)); { - struct station_info sinfo; + struct station_info sinfo = {0}; u8 ie_offset; if (GetFrameSubType(pmgmt_frame) == WIFI_ASSOCREQ) ie_offset = _ASOCREQ_IE_OFFSET_; -- 2.28.0
  12. Ok, that clearly seems to be a badly initialized structure issue. Changing struct station_info sinfo; by struct station_info sinfo = {0}; in drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c : rtw_cfg80211_indicate_sta_assoc remove the BUG calls on a client connection. Now, I'll have to test it in a real environment, to check if the Wifi connection works and is stable. I'll post a clean patch tomorrow.
  13. I'm trying to understand the issue, but it seems rather bizarre. Basically, when freeing the station_info structure in nl80211_send_station, kfree is called with a somewhat valid pointer, but then kfree (SLUB version) trips when calling PageCompound on the page of the provided pointer. My best bet is that the structure isn't initialized correctly, leading some fields to be initialized with garbage values. However, it seems strange that everything goes without any bug until that specific point.
  14. Just tried it today, but without network though. It boots correctly. There's no desktop, obviously, since it's a minimal image. But I was able to log-in as root, add a user, reboot a few times and log-in as the user. Could you tell us what's happening actually ? No Tinkerboard led ? Stays red without any activity ? It boots without HDMI ? An error message appears ?
  15. Thanks for testing ! I guess we can include this patch in the next release, then.
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines