Modules linked in: gpio_ir_recv lz4 lz4_compress ssv6051(+) mali snd_soc_rk3228 lzo zram sch_fq_codel ip_tables autofs4 WARNING: CPU: 0 PID: 359 at drivers/net/wireless/rockchip_wlan/ssv6xxx/smac/init.c:1471 ssv6xxx_dev_probe+0x2b8/0x1c70 () ssv6xxx_dev_probe(): ssv6200 device found ! ssv6xxx_set_sdio_clk:set sdio clk 25000000Hz (generic_wifi_init_module ) from (do_one_initcall+0xa0/0x1f8) (initWlan ) from (generic_wifi_init_module+0x20/0x1000 ) (ssvdevice_init ) from (initWlan+0x40/0x8c ) (sta_cfg_set ) from (ssvdevice_init+0xf4/0x12c ) (warn_slowpath_null) from (sta_cfg_set+0xc0/0x220 ) Modules linked in: lz4 lz4_compress ssv6051(+) mali snd_soc_rk3228 lzo zram sch_fq_codel ip_tables autofs4 WARNING: CPU: 3 PID: 359 at drivers/net/wireless/rockchip_wlan/ssv6xxx/ssvdevice/ssvdevice.c:169 sta_cfg_set+0xc0/0x220 () redirect to /lib/firmware/ssv6051-wifi.cfg I just reverted the config the wifi is not turning on again! This is what I get from dmesg | grep ssv So, is this a thing you've noticed before? Actually, this might not be true. Well, after I remove the emmc from overlays, that is. When I select rk3229, the wifi doesn't work. There is something wrong, I think, with the rk322x-config. Is this an entirely new problem or may have something to do with video and whatnot?Ģ. usr/lib/arm-linux-gnueabihf/libgbm.so.1.0.0 The following changes from packaged state files were detected: For the sake of it, I decided to take a look at armbianmonitor -v and got "It appears you may have corrupt packages.", pointing to "a symptom of filesystem corruption caused by SD cards or eMMC dying", which makes that first suggestion of yours to remain true, but also that it could be "burning the OS image to the installation media went wrong", which I don't think to be the case. I am now with 2 errors but I think they're unrelated to any of these events:ġ. All went ok! And I am still happily using the minimal image you compiled for me + lubuntu. Some of the entries on the enxynos were right or interesting, so I merged them on the armsoc config and so far so good. So, in order to avoid it, I allowed downgrades and then upgraded them.
#MXQ PREPARE IDB FAIL INSTALL#
Some of the stuff there I had newer versions and the install would just stop. I also had to change one thing on the install media framework: allow downgrades. I manage to play quake 1 and 2 (tho I had to add some params, LD_LIBRARY_PATH=/opt/gl4es LIBGL_GL=15 LIBGL_FB=3 LIBGL_MIPMAP=3 LIBGL_FORCENPOT=1 LIBGL_FPS=1 LIBGL_POTFRAMEBUFFER=1 LIBGL_FORCE16BITS=1 quake2)
#MXQ PREPARE IDB FAIL UPDATE#
The rest will update and upgrade just fine.ĭoing this, I am able to run some stuff. I took some time to replay back exactly as I was investigating it myself! And got to some findings similar to yours: the only thing I need to set as hold is the xserver-xorg-video-armsoc.
Hi ! Thanks for all the help and ways to fix and/or bypass these issues! I will ask the high towers what happened, maybe fix the lightdm greeter thing and ask for a stable image rebuild.
#MXQ PREPARE IDB FAIL DOWNLOAD#
The stable image from the download page include nf file which should not be there! Curiously a freshly built image by me instead does not include that file, which should be there only on mainline images. I will update the media framework in the next days to include the apt-mark commands automatically, so this further step won't be needed.Įdit: ah, another thing about /etc/X11/ directory. This is not exactly tested, because I'm headless right now, so if you feel comfortable enough, it may be a wise idea to start from a fresh system. If you start from a fresh system, just run the apt-mark hold commands after installing the media framework and you should be fine enough. The install the media framework packages manually:Īnd finally mark the packages as hold, so apt upgrade won't try to update them:Īpt-mark hold kodi kodi-addon-dev kodi-bin kodi-data kodi-tools-texturepackerĪpt-mark hold ffmpeg libavutil56 libpostproc55 libswscale5 libavutil-dev libpostproc-dev libswresample3 libavresample4 libswscale-dev libavcodec58 libavcodec-dev libavresample-dev libavformat-dev libavfilter7 libavfilter-dev libavdevice58 libavdevice-dev However, to try to get back the media framework situation, first uninstall the wrong armsoc driver: It is unclear to me why it tries to install packaged Kodi instead of keeping the one from media-framework, but probably I made some mess with versioning. I don't know why, but it tries to install armsoc-exynos as a dependency of Kodi. If apt is lamenting issues about armsoc, that's because of a previous package upgrade. I just tried to install the lightdm-autologin-greeter and uninstall lightdm-gtk-greeter and, after a reboot, it looks like it works:Īpt install lightdm-autologin-greeter & apt remove lightdm-gtk-greeter Made some further investigation and it seems that lightdm-gtk-greeter is the great offender: the package in Ubuntu Focal seems to be broken for armhf architecture:
0 kommentar(er)
