Jump to content

Astralix

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Astralix

    NanoPC T4

    Hey! Just installed a fresh copy of the current Armbian for the NanoPC T4 and run into a few troubles. 1) There are quite a few options missing from the armbian-config, for instance WiFi setup. However, eth0 works. 2) I also cannot get the eDP display working. WOuld it be possiibler to add the missing dts contend by overlay or has it to be included into the u-boot? 3) For HDMI I only have a small 800x480 screen that is also not detected correctly. However connecting it to my linux PC does work fine. SO how to modify startup to correctly set the HDMI to that specific resolution? 4) I could modify the system to pull the rootfs from the PCIe SSD and every file is moved there. but any time I pull the SD card, the old Frinedlyarm u-boot starts. I cannot get the Armbian u-boot to run instead and the installer option is missing from armbian-config. What can I do to support? Is there any premature code I could test? Regards!
  2. Hi @AnArmbianUser! There are two acceleration systems, 2D/3D graphics and video. I did not focus on these, as I am using the desktop only for controlling the unit. I will investigate on the graphics system around end of January, as till then the most needed features of the project itself are implemented. As it is an amateur radio, there is no primary focus on graphics acceleration. But I really would appreciate, if all the GPU and VPU stuff would work in a modern kernel 4.1x.y more or less out of the box. It is so easy to get all the needed licenses for legal use of the CoDecs but it is so hard to get the licensed code from the company who manufactures the iMX SOC... Whichever company that might be tomorrow, or next week Regards Ulrich
  3. So, it looks like I have an update on that... I do not know why the old and the not so old version of armbian simply used the HDMI as a default display, while the other two versions fail. But it seems, that the issue is the presence of /dev/fb0 and /dev/fb1 and the missing /dv/fb. I added a new configuration file /etc/X11/xorg.conf.d/99-hdmi_fb0.conf Section "Device" Identifier "main" driver "fbdev" Option "fbdev" "/dev/fb0" EndSection That forces the x-server to use /dev/fb0 and the additional OLD doesn't interfere anymore. So at least one issue is solved.
  4. Hi there! I am new to this forum, so hopefully I am at the right place to open my discussion. We use our own made iMX6DL based board to run a semi-professional amateur radio. We choose armbian as it worked almost out of the box, but we use a kernel 4.11+ probably 4.12+ next week with some small extra drivers for an SPI OLED and some special keyboard drivers. However these modifications are not relevant for the issue I have, but I should mention, that I added the etnaviv kernel drivers and all related things to activate HDMI. We have not fully encountered the way to merge in our BSP to armbian, however I found the very instructional videos in the other topic and I'll prepare for that in the next weeks. Til then we provide update-images for our users, later we move to "apt update && apt upgrade". Now here's my issue... The armbian driver set before 5.30 (4 weeks ago) worked fine and we had a desktop on the HDMI, as long as you 1) start the unit with a switched on HDMI monitor connected and 2) never turn off that monitor, as that results in a blank screen. Two weeks ago, we tried an armbian upgrade (yes we disabled the BSP package upgrade, as we provide our own.) and HDMI was working, but the screen stays black. Pressing ENTER revealed that the text console works, but X11 refuses to start. It detected the monitor and such but then failed with almost no in-depth error information. So we reset to our initial image and worked on our radio software and on Monday this week I tried again to upgrade. Lucky me, this time, the HDMI worked after the upgrade. Unfortunately yesterday we did another upgrade to (if I am correct) 5.31 and now the HDMI stays black again, only working as a text console. "startx" just confirms a fine monitor but then fails. We do need the desktop working, as that is one option to use the box as an amateur radio and control it via the chromium browser. We currently do not need any 2D / 3D acceleration. I have to mention, that the unit also has an OLED running as a framebuffer device but that is not mapped to any console, so the x server should not take over its control (it should run the amateur radio control while the user can use the armbian desktop at will) [ 1211.676] (II) modeset(0): Output HDMI-1 connected [ 1211.676] (II) modeset(0): Using exact sizes for initial modes [ 1211.676] (II) modeset(0): Output HDMI-1 using initial mode 1280x720 +0+0 [ 1211.676] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. [ 1211.677] (==) modeset(0): DPI set to (96, 96) [ 1211.677] (II) Loading sub module "fb" [ 1211.677] (II) LoadModule: "fb" [ 1211.679] (II) Loading /usr/lib/xorg/modules/libfb.so [ 1211.680] (II) Module fb: vendor="X.Org Foundation" [ 1211.681] compiled for 1.18.4, module version = 1.0.0 [ 1211.681] ABI class: X.Org ANSI C Emulation, version 0.4 [ 1211.681] (II) UnloadModule: "fbdev" [ 1211.681] (II) Unloading fbdev [ 1211.682] (II) UnloadSubModule: "fbdevhw" [ 1211.682] (II) Unloading fbdevhw [ 1211.682] (==) Depth 24 pixmap format is 32 bpp [ 1211.740] Require OpenGL version 2.1 or later. [ 1211.740] (EE) modeset(0): Failed to initialize glamor at ScreenInit() time. [ 1211.740] (EE) Fatal server error: [ 1211.740] (EE) AddScreen/ScreenInit failed for driver 0 [ 1211.741] (EE) [ 1211.741] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. So why does the current update fail on that fbdev while the last one did not? Would appreciate any help that gets the desktop back onto the HDMI and as a bonus, the makes the Desktop steady working even the HDMI monitor is switched off or disconnected? Astralix
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines