Walter Zambotti
-
Posts
22 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Walter Zambotti
-
-
Seems the fix is to use kernel 6.1.11 that comes with the desktop version and not 6.1.30 that comes with the minimal version.
-
it turns out this mystery video device (None-1) is provided by Kernel 6.1.30 and revertiong back to 6.1.11removes the device.
-
So I edited the boot.cmd file and added this line after each of the setenv bootarg ... lines :
setenv bootargs "${bootargs} video=None-1:d"recompiled with
sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scrchecked the lines had made it to boot.scr and rebooted.
But the None-1 video device still persists and xrandr still shows that device is being used by Xorg!!!
-
I am unable to configure Xorg to ignore (and stop using as its default) the None-1 video device causing me not to be able to display a desktop via the HMDI-1-1 device.
It has been suggested (https://ubuntu-mate.community/t/how-to-configure-xorg/26732/3) that I disable this device in the kernel, hopefully, via a kernel option such as :
video=None-1:d
Does anyone know where (which file) and how (specific method) I should do this?
-
Armbian 23.5 Ubuntu
Not sure what I touched but my OpenGL has reverted from the Mali-G52 hardware accelerated renderer back to the llvmpipe.
How can I changed this?
-
I have multiple n2s and I don't want them all to be called odroidn2.
What is the recommended way to change the hostname of an armbian system?
-
I noticed this on the download page for the Odroid N2/N2+:
On modern kernels adding “video=HDMI-A-1:1920x1080M@60D” to boot /boot/armbianEnv.txt (extraargs=) should force HDMI to 1080p instead of the 4K native resolution.
I'll check if that will also works with 2560x1440 monitors! -
-
I managed to get it going!
I suspected it was working so unplugged the HDMI cable from my QHD monitor and plugged it into a FHD and wala instant picture. Then I plugged it back into my QHD monitor and it was still displaying. I then used the display control to set the resolution to 2560x1440 and it still worked.
So the problem seems to be using QHD from boot. That doesn't work.
Seems like a firmware setting that should be changed.
I suspect it doesn't see a FHD single so assumes a 4K monitor instead.
-
Thanks I went into armbian-config but can't see any setting that would be relevant as GUI is already set to enabled!
I tried disabling and re-enabling but no difference. Blank screen!
-
I'm using the Odroid N2/N2+ 23.5 Jammy minimal image.
I then updated and upgraded successfully. I then attempted to install MATE via tasksel (which I installed) but that immediate fails with an apt package missing error. SO then I tried to install MATE manually by:
$ sudo apt install mate-desktop-environment mate-desktop-environement-extras
$ reboot
There didn't seem to be any display manger installed so I stalled lighdm
$ sudo apt install lightdm lighdm-gtk-greeter$ reboot
Then I noticed that Xserver was not installed (really, that's no a MATE dependency!!!)
$ sudo aqt install xserver-xorg
$ reboot
But the xserver was not starting and so I noticed xinit was not installed (really. why wouldn't this be a dependency of MATE or the xserver)
$ sudo apt install xinit
$ reboot
Now it boots and starts everything and then switches to console tty07 but is just a black screen. I can see from console tty01 that all the correct (I assume) processes have started but nothing but a black screen.
Xorg is running
lightdm session is running
lightdm-greeter-session is running
lightdm-gtk-greeter is running
But still no login screen (or mouse) is visible (just a blank screen)
I can see the ~/.Xauthority file is blank so don't know what has happened.
What else have I missed?
-
I suspect something is missing from the Armbian meson hardware/firmware, because if I boot two copies of Ubuntu then the KVM appears to operate correctly and if I boot two copies of Armbian I see neither system.
-
Hi have two N2s (an N2+ and N2). Both are connected to a Viewsonic 2560x1440 2 HDMI ports monitor where they both work well.
One system (N2+) is running Ubuntu 22.04 the other is running Armbian jammy 22.04.01 Kernel 6.0.13 #22.11.2.
I have purchased a ATEN CS22H 2 port HDMI/USB KIVM switch.
When I connect both systems to the monitor via the KVM I only get a picture from the Ubuntu system. The Armbian system is always black.
Can I force the kernel/firmware to be 2560x1440x60hz. I was looking at this post :Regarding forcing the kernel to be a fixed resolution but wasn't sure it was relevant.
I am able to connect to the Artmbian system via ssh if I need to.
Any suggestions welcome!
-
Using a Realtek 8821CU Bluetooth + Wifi USB adapter.
Working fine on stable build jammy with kernel 5.10.123. (current)
Using the Armbian->Config->System->Other and selecting the latest 5.15 kernel. System reboots and confirm kernel has been updated and chosen.
Wifi hotspots are all seen but fails to connect and repeatedly asks for password. Security is WAP2 personal.
Setting the kernel back to 5.10.current reverts to Wifi working as expected.
I will try the 5.17 kernel and report back.
I have seen this before on other Deb distros. From memory this is caused by a missing/outdated kernel encryption module or wpa_supplicant. However don't quote me. It was quite some time ago.
-
On 7/1/2022 at 6:07 PM, Werner said:
Use armbian-config tool to switch between kernels.
Thanks.
I saw the option and tried it. Nothing seemed to happen! It loads 92 packages then warns things can go go wrong and then prompts OK. So I OK'd but nothing happened!
I get the impression this allows you to switch between already installed kernels, assuming they are installed. But I don;t know really.
-
On 6/10/2022 at 1:11 AM, usual user said:
Ok, I went on to 5.19.0-rc1. I was able to skip a lot of mainline commits from tobetter's tree because they landed, and for the remaining WIP commits, I switched to more recent ones. Some of the WIP commits are already in staging and will land sooner or later.
[PATCH 012/130] arm64: dts: rockchip: Add sata nodes to rk356x landed [PATCH 018/130] arm64: dts: rockchip: add rk356x dwc3 usb3 nodes landed [PATCH 032/130] arm64: dts: rockchip: add rk356x sfc support landed [PATCH 046/130] clk: rockchip: Mark hclk_vo as critical on rk3568 landed [PATCH 048/130] arm64: dts: rockchip: enable otg/drd operation of usb_host0_xhci in rk356x landed [PATCH 049/130] usb: dwc3: reorder dwc-of-simple compatibles superseeded by enable-usb-support-on-rk356x.patch [PATCH 050/130] usb: dwc3: convert dwc3-of-simple to use match-data superseeded by enable-usb-support-on-rk356x.patch [PATCH 051/130] usb: dwc3: add rk3568 dwc3 support superseeded by enable-usb-support-on-rk356x.patch [PATCH 052/130] drm/rockchip: Refactor IOMMU initialisation landed [PATCH 053/130] drm/rockchip: Embed drm_encoder into rockchip_decoder landed [PATCH 054/130] drm/rockchip: Add crtc_endpoint_id to rockchip_encoder landed [PATCH 055/130] drm/rockchip: dw_hdmi: rename vpll clock to reference clock landed [PATCH 057/130] drm/rockchip: dw_hdmi: add rk3568 support landed [PATCH 059/130] drm/rockchip: dw_hdmi: add regulator support landed [PATCH 061/130] drm/rockchip: dw_hdmi: Use auto-generated tables superseeded by drm-rockchip-RK356x-VOP2-support.patch [PATCH 062/130] drm/rockchip: dw_hdmi: drop mode_valid hook superseeded by drm-rockchip-RK356x-VOP2-support.patch [PATCH 063/130] drm/rockchip: dw_hdmi: Set cur_ctr to 0 always superseeded by drm-rockchip-RK356x-VOP2-support.patch [PATCH 064/130] drm/rockchip: dw_hdmi: add default 594Mhz clk for 4K@60hz superseeded by drm-rockchip-RK356x-VOP2-support.patch [PATCH 066/130] arm64: dts: rockchip: rk356x: Add VOP2 nodes superseeded by drm-rockchip-RK356x-VOP2-support.patch [PATCH 067/130] arm64: dts: rockchip: rk356x: Add HDMI nodes superseeded by drm-rockchip-RK356x-VOP2-support.patch [PATCH 071/130] drm/rockchip: Make VOP driver optional landed [PATCH 072/130] drm: rockchip: Add VOP2 driver landed [PATCH 076/130] PCI: dwc: rockchip: add legacy interrupt support landed [PATCH 077/130] arm64: dts: rockchip: add rk3568 pcie2x1 controller superseeded by Add-rk3568-PCIe2x1-controller.patch [PATCH 079/130] dt-bindings: rockchip: Add Hardkernel ODROID-M1 board Signed-off-by: Dongjin Kim DT [PATCH 080/130] arm64: dts: rockchip: Add Hardkernel ODROID-M1 board Signed-off-by: Dongjin Kim DT [PATCH 083/130] phy: rockchip: Support pcie v3 superseeded by RK3568-PCIe-V3-support.patch [PATCH 084/130] PCI: rockchip-dwc: add pcie bifurcation superseeded by RK3568-PCIe-V3-support.patch [PATCH 085/130] arm64: dts: rockchip: rk3568: Add PCIe v3 nodes superseeded by RK3568-PCIe-V3-support.patch [PATCH 086/130] arm64: dts: rockchip: rk356x: Add HDMI audio nodes DT [PATCH 087/130] (DO NOT MERGE) ODROID-M1: add more peripherals Signed-off-by: Dongjin Kim DT [PATCH 088/130] (DO NOT MERGE) ODROID-M1: add sound devices nodes Signed-off-by: Dongjin Kim DTFor those who are interested, I have attached glmark2 logs. The performance is not yet overwhelming, only the basic functionalities have just landed. But the graphical desktop works pretty decently. So the fine-tuning season is open.
And with the hantro decoder wired up, hardware-accelerated video decoding of H.264 and VP8 works up to 1080p. See fluster-run.log for reference.
Went on to 5.19.0-rc2. And with the ir-receiver wired up, my RC-100 works out of the box.
Rant: Why doesn't editing allow spoilers to be created with sections of code?
glmark2-wayland-odroid-m1.log 23.95 kB · 2 downloads fluster-run.log 16.93 kB · 1 download
The glmark2 scores are disappointing. Those scores are lower than my N2 (non plus) at 600 plus/minus on X and mid 1300 plus/minus on Wayland.
-
I just (several days ago) installed Armbian 22.05 OdroidN2 Jammy XFCE. It uses kernel 5.10.
Then I noticed there is an alternative version 22.05 jammy XFCE with kernel 5.17.
Is it possible to update to the later kernel from the image I used without re-imaging and starting from scratch? I have already installed and setup a lot of other applications and data.
I can see i have packages linux-image-current-meson64/jammy (linux-dtb... & linux-headers...) installed.
On apt.armbian.com I found: (https://stpete-mirror.armbian.com/apt/pool/main/l/linux-5.17.5-meson64/) in the linux-5.17.5-meson64
Name Last modified
Parent Directory linux-5.17.5-meson64
linux-dtb-edge-meson64_22.05.1_arm64.deb2022-05-29 06:58
linux-headers-edge-meson64_22.05.1_arm64.deb2022-05-29 06:58
linux-image-edge-meson64_22.05.1_arm64.deb2022-05-29 06:58
Can I apt install these and expect the upgrade to correctly happen?
-
All it took was a reboot and it all worked correctly.
Call it teething problems!!!
-
Odroid N2. Armbian Ubuntu 22.04 kernel 5.10.123. xfce. Bluman 2.2.4
Adapter is Realtek rtl8821CU Wifi/Bluetooth. Drivers were present.
Device Sony SRS-X2.
The device is seen when searching but fails to pair. The only message is "bluetooth pairing failed." and "br-connection-already-connected"
I'm note sure by what already connected means. It definitely is not connected.
-
The simple answer turns out to be the selection of the correct frame number. Print function::variable does not set the frame number for you, and it must be manually set by frame #. Which in my example is 8!
-
So I'm trying to debug a 32 bit C compiler circa 1983 that only compiles in 32 bit. I have the compiler working in Linux Ubuntu 18.04 and later with multiverse (32 bit) support installed.
I thought to myself PI OS would have to be one the most popular used and supported 32 bit OS, so let's compile and debug the the 32 application in a complete 32 environment.
However on the PI OS 32 bit while I have managed to compile to compiler with no issues it doesn't execute and gets seg faults.
No problem I can debug it!
Except I can't because if I use the debugger via Geany or directly it complains it can't find variables higher up in the stack.
gdb $ where full (shows that the variable is known and is on scope) but
gdb $ print said_function::said_variable (complains it can't find the variable).
Topic on stackoverflow refers
https://stackoverflow.com/questions/64728124/linux-gdb-cannot-print-variable-in-stack
Unfortunately the question has bee closed (prematurely I believe) and so no one my answer the question there!Hence why I'm here!
(gdb) where full
#0 0xb6fbc1dc in strlen () from /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so
No symbol table info available.
#1 0x0001076c in WrStr (s=0x0) at ansifront.c:71 len = 213201
#2 0x00011698 in PrintTok (x=511) at ansifront.c:419 No locals.
#3 0x00011f78 in WrTQual (ts=0x31647 <mainstk+951>) at ansifront.c:646 No locals.
#4 0x00011fbc in WrTSpec (ts=0x31647 <mainstk+951>) at ansifront.c:654 No locals.
#5 0x0001ccc4 in WrNTSpec (tspec=0x31647 <mainstk+951>) at decl.c:561 type = 4 '\004'
#6 0x0001d0f0 in WrXDecl (vdecl=0xbefff128, isfdef=0) at decl.c:676 tsvdecl = {vd_var = 0x1d0fc <WrXDecl+636> "", vd_type = 0x0, vd_tspec = 0x31647 <mainstk+951>, vd_prev = 0x31647 <mainstk+951>}
#7 0x0001d9c0 in WrOSPLst (plst=0x3163b <mainstk+939>, fndecl=0x3160d <mainstk+893>) at decl.c:906 vdecl = {vd_var = 0x34098 <tmpstk+8> "winpath", vd_type = 0x0, vd_tspec = 0x31647 <mainstk+951>, vd_prev = 0x0} tlp = 0x31643 <mainstk+947> ilp = 0x34090 <tmpstk>
#8 0x0001e118 in RdGDecl () at decl.c:1084 params = 0x3163b <mainstk+939> isfunct = 1 needsimi = 0 '\000' tspec = 0x31605 <mainstk+885> vdecl = 0x3160d <mainstk+893>
#9 0x00013f34 in main (argc=1, argv=0xbefff2c4) at ansifront.c:1499 No locals.
(gdb) print RdGDecl::params
No symbol "params" in specified context.
(gdb) print params
No symbol "params" in current context.
(gdb)
Looking in the manual there is no mention of referencing variables in sub blocks other than mentioning that a block must be active in order to do this. 'where full' confirms this is the case on line #8.
Someone in the stackoverflow question mentioned something about stack frames and 8 byte. I assume they mean alignment.
Looking at the addresses for the variables on the stack they seems to be suspiciously non 8 byte alligned (params = 0x3163b is an odd value).
I have looked for a compiler option to enforce 8 byte stack alignment but could not find one.
Does anyone know of such an option?
Also if anyone feels my stackoverflow question was prematurely closed I would appreciate if you could leave some additional comments on that question, maybe asking for it to be re-opened (if you feel appropriate)!
Walter
Install MATE desktop to Minimal Image (blues)
in Beginners
Posted
The problem turns out to be the kernel version. The minimal image comes with 6.1.30 which provides a new video device (called None-1) and the desktop image comes with 6.1.11 which does not have this mystery video device. All working with the reverted kernel.