Jump to content

Armbian for Amlogic S9xxx kernel 5.x


balbes150

Recommended Posts

10 hours ago, balbes150 said:

You do not have 3 GB, this is a fraud of the seller.

Maybe... so 4 *512 KB ICs, but then why bother marking the ICs with different part-numbers?

And what about the U-Boot? It reports:


U-Boot 2015.01-ga4d8f5c-dirty (Dec 07 2017 - 19:23:54)

DRAM:  3 GiB

Why bother faking that? Who's ever gonna look at it? 

Is it possible to replace the boot loader with a "good" one?

Burning tool 2.1.2 can't do it, even if I short the 2 ROM IC legs. Is there a better tool?

 

 

@Nuno CruzYour machine seem the same as mine, how much RAM do you see in Armbian?

 

 

Link to comment
Share on other sites

Hello,

I installed the armbian image on an sd card (Armbian_19.11.3_Aml-g12_xenial_legacy_5.3.0_desktop_20191126) then I inserted into my H96pro+ box(amlogic s912) and booted. the linux installation process started (creating user name, password...).

 I logged to my user account but at the end there is no GUI interface (the linux stay in text mode).

Please help me to log into the GUI interface/ 

Link to comment
Share on other sites

6 hours ago, Amoren said:

Hello,

I installed the armbian image on an sd card (Armbian_19.11.3_Aml-g12_xenial_legacy_5.3.0_desktop_20191126) then I inserted into my H96pro+ box(amlogic s912) and booted. the linux installation process started (creating user name, password...).

 I logged to my user account but at the end there is no GUI interface (the linux stay in text mode).

Please help me to log into the GUI interface/ 

 

I've seen various X problems when moving up through the builds. It can be down to kernel, dtb etc.
If X is crashing according to fbdev in /var/log/Xorg.log, its probably the kernel or dtb (also after startx).

If lightdm gtk greeter consumes 100% on 1 cpu, try to change the greeter - take some tips from https://cialu.net/how-to-solve-failed-to-start-session-with-lightdm-and-xfce/
Disabling selinux at boot fixes a lot of strange issues.

At the end of the day, it seems to be better to move onto a different armbian build or back to a good one, particularly kernel files and modules.

Edited by dbsharpe
omision
Link to comment
Share on other sites

On 1/8/2020 at 4:10 AM, joq3 said:

Is it possiblee to install Armbian to an Amlogic S905Y2 box? More specifically the A95X Plus?

I'm trying to install it on X96S with S905Y2...

I have 2 versions, the 2g/16gb and 4g/32g.

 

in the 2g version i could boot into armbian (used the default dtp, tryed to change for many but only worked on the ugoo default). But no bluetooth and no wifi. This one come with wifi chip RTL8723BS

 

in the 4g version the armbian load, but when ask for the root password my keyboard isn't working. I tried 3 keyboard on USB but no one worked. It remains still waiting for the root login. This version came with the wifi "Ampack AP6255", but i couldn't start armbian to test,... don't know what to do for USB to work with the keyboard and couldn't find a solution online.

 

Images from both X96S chips (armbian worked on 2g)

https://imgur.com/a/wVUvD8O

Link to comment
Share on other sites

On 1/8/2020 at 12:35 AM, Shinjin said:

Thanks!

Could you tell me what Armbian version and what dtb file you are using?

Don't remember the image version, the dtb was auto selected and based on the board name that I have in the installation it's kharas vim2

Link to comment
Share on other sites

Hi all,

 

thanks @balbes150 for the great effort on porting armbian to this "cheap" TV boxes.

I need a headless linux box, and I have a minx NEO U1 that I don't use much anymore, ergo Armbian!

So I basically need a linux box with LAN connection, don'r really care about HDMI or graphics.

I've read around the forum, and dispite being a popular box, the neo u1 is not discussed much in the armbian.

Apparently I already have multiboot set up (I was using libreElec in the box in the past),  I made it working open/libreELEC many years ago. so much time ago that I can't find the USBnor dtb files I was using.

Anyway, the box boot up fine the Armbian_19.11.3 (server) image with almost any *gxbb* dtb.

 

I think the right dtb it could be the meson-gxbb-p201.dtb, I have no error, the system can detect 2Gb of RAM, and from ifconfig and dmesg I would say that eth0 interface is up, but unfortunately the ethernet network doesn't really work...

The system clearly sees the ethernet port as something logs in dmesg when I plug/remove the cable but it never picks up an IP address (at least not an IPv4 one) from the router DHCP server. I'm sure the router/cable are OK, as any other machine gets an IP correctly with the same cable/port/router.

 

Curiously with meson-gxbb-p200.dtb I have error some PHY LAN-related error (I haven't collected the debug info, but I can if that could be helpful).

I don't have a serial cable to USB to log in UART mode.

I've tried p200 since in the libreELEC github devicetree there is a gxbb_p200_2G_minix_neo_u1.dts, and it inherit the LAN from gxbb_p200_2G.dts. So if I follow/fix the error I have using the meson-gxbb-p200.dtb I may solve my LAN issue.  

 

Does anyone have this box and was successful on booting up with a working LAN? (and or have an idea what I could change to make LAN working)

 

Cheers

 

EDIT: I've checked the LAN connection with Android and it works (I actually wasn't sure about that)

 

EDIT2: I've tried to play around with dts files, modify/compile, but I came to the realisation that the ethernet support for the mason family (at least gxbb) is completely broken! I'm so surprised that the lima driver kind of works, while the ethernet hardware is kind of unsupported! I gave a try to the wifi then, after setting up the firmwares files and configure wpa_supplicant and changing the interfaces... I still don't have wlan0 in the possible interfaces, although the brcmfmac module load without errors.

I was thinking to swap the on board u-boot with more recent version, but I can't mount the mmc, as I can only see the mmcblck0 device and non its partitions! So unfortunate.  Last resort fo me, is try to load a u-boot from usb. I've found some handwaving instruction in this forum,  but I don't think I fully understand it.

Anyway, do you think that swapping the u-boot may solve some of the board issues?

 

Link to comment
Share on other sites

Hello, I installed the armbian linux (h96pro s912 box) on a sd card. It runs very well.

Now I want to install it to the emmc nand of my box but there is no option to do this 

on the armbian settings app (blue screen).

Any other option to install it to the emmc nand flash?

Link to comment
Share on other sites

On 1/13/2020 at 11:59 AM, 79bass said:

Anyway, do you think that swapping the u-boot may solve some of the board issues?

You should only use the DTB that are included in the image you are using. If you need to change something in them, you need to use the DTB from the image as the basis.

 

 

Link to comment
Share on other sites

Quote

Nand flash is not supported in recent linux kernel. If you have emmc, in the root folder you'll find install.sh to do what you want.

Can u please tell  me what version do support nand flash installation?

Link to comment
Share on other sites

20 hours ago, Amoren said:

Can u please tell  me what version do support nand flash installation?

You can try to search older 3.14 based version of Balbes work, but I don't think the images are still available. You may look here:

 

Link to comment
Share on other sites

First up... THANK YOU SO MUCH! to you @balbes150

I bought the original H1 variant 'H96 Pro Stick' (an Amlogic S912 in stick form!) as soon as it came out direct from GearBest on a special deal for £35!
The original Android 7.1.2 firmware was bad, but SuperCeleron over at FreakTab made a decent 'full-android' and 'android-TV' OS that i have tweaked myself. That was it for development on my board, and that almost 3 years ago now.

I had once, way back then tried this before, and after trying 10ish random dtb.img's for S9xx i would get past login, but it would always get this repeated text across the screen that would stay there and i never did get to the desktop.
I am now typing from an 11 year old 32-bit Intel Atom NetBook with 1GB ram! :'(
It is my 'PC' ...and honestly... i can do more from my 64-bit OnePlus 5T in Termux (Arch/Debian/Ubuntu proot) than this old thing.
I know the S912 is good for Linux in multi-core benchmarking... so all this time later... i tried again....
And with the newer documentation you have now... it was alot easier than last time! and it worked... first time too!
FINALLY I get to try out Armbian!!!! :D
So thank you very much for your work all these years, it is appreciated!
The rom i got was Ubuntu and it runs fast! no long wait times for apps to open up! a much needed 64-bit PC i have needed all this time!!

 

Just one question please (or anyone else out there reading this essay!)
As the case with alot of devices... wifi & bluetooth is not working. I found a website from a guy who used my H1 H96 stick and he forked your 4.9 kernel sometime back & modified it for crypto-mining purposes, so it has alot of documentation. On his GitHub it has my wifi & bluetooth drivers.
How do i add them into this rom?????

ONCE AGAIN... A MASSIVE THANK YOU!!!!!!!! :D

Edited by scott90420
me dumb.
Link to comment
Share on other sites

Hello Balbes,

 

thank you very much for your beautiful builds :thumbup:

I have one question: I have some older Ubuntu 18.04 build with 5.1.0-aml-s905 kernel and I want to compile media_build drivers to apply a patch for my dvb-card which works only partially (dvb-s works, dvb-s2 not, seems to be a common problem for dvb-adapters of this type). As far as I understand, I need a kernel source (or kernel headers) to be able to compile. Where I can get them for my kernel version (or do some other headers/source will do for compilation?). Unfortunately I don't know much about linux tinkering - I can follow instructions but I'm not able to overcome the unexpected problems and don't really understand what do I do mostly. What I did try - I have installed kernel-package and linux-source packages (which were 4.15.0 -  but I have 5.1.0 kernel and need same source, right?) and run make oldconfig && make prepare. After that I run build inside media_build and of course the compilation failed, it can't find time.h, features.h etc. inspite of the fact that they are present in /usr/include and build_essentials (and all other prerequisites) are installed

 

It would be great if you could give me a couple of tips how to compile media_build in your distros.

Link to comment
Share on other sites

1 hour ago, chpasha said:

As far as I understand, I need a kernel source (or kernel headers) to be able to compile.

In the network repository is a new kernel 5.3 5.4 version and headers for them, try to take them there.

Link to comment
Share on other sites

39 minutes ago, balbes150 said:

In the network repository is a new kernel 5.3 5.4 version and headers for them, try to take them there.

what do you mean with "network repository"? your new builds on yandex disc or your Build-Armbian repo on github?

Link to comment
Share on other sites

Hi guys, been a whole week now i have waited for a reply ^^

I dont expect to be answered right away but over a week now and others are being answered before me?!?

I dont need my hand to be held, just need some general steps i need to take please OR point me to some documentation and i will do it all myself.

PLEASE! ANYONE?!??

So, again....
Thank you for the distro, only problem is wifi doesnt work, could ANYONE please tell me roughly what i need to do next to get wifi (i have my devices wifi & bluetooth drivers) how do i add them????

Been a whole week since i got Armbian now, and i am still unable to use it as i cannot download anything.

I cannot find any documentation here, Github, MXQ project or Freaktab on 'adding drivers'. (if there is none, perhaps that should be added. I dont mind contributing by writing it up myself as i NEED the info anyway as i will be doing it on my device).

 

Until someone helps me, i cannot use Armbian, so please any help is truly appreciated, thanks.

Link to comment
Share on other sites

13 hours ago, scott90420 said:

(i have my devices wifi & bluetooth drivers) how do i add them????

These drivers are from another (non-compatible) kernel, if you ask such questions, then you do not add any (you need to be a system programmer to write these drivers again).

Link to comment
Share on other sites

Thank you @balbes150 for the quick reply AND the great work you do.
So... basically adding wifi is pretty much a no then :'( 

Shame, i have no ethernet as its a s912 stick, not box.

I will have to buy a USB to ethernet cable then.

 

One more thing:

I really like this project and would like to, in a small way, contribute.

 

Idea:

I successfully burned my USB via an android app called 'EtchDroid' (open source - F-Droid).

This had me thinking, i want to make a native android Armbian tool, no PC needed, it will:

  1. Extract DTB IMG from the device.
  2. Burn the distro IMG to USB/SD card, like EtchDroid.

It will work via a terminal app (whilst booted) and also available as a Magisk/TWRP flashable ZIP too, so it can be also be used via recovery (in case bricked/boot-looping)

I have found on GitHub an Amlogic DTB tool.

I have the AML_autoscript & AML_autoscript.zip.

 

So...

I am currently trying to work out how to apply the AML_autoscript.zip via recovery/magisk and not the stock 'Update' apps we have on our boxes. Question:

  1. Do you have any ideas for this??
  2. Where/what does the AML_autoscript.zip change and how does it do it?

 

THANK YOU SO MUCH BALBES150 YOUR TIME, EFFORT & EXPERTISE IS REALLY APPRECIATED!!!

I really think Armbian will be more accessible to the masses if it was in an app like i am trying to make here, it can be on F-Droid, PlayStore, APKmirror etc so it reaches a larger audience.

And also takes care of the only 'trial-and-error' part of this whole process, finding the right DTB IMG.
Making it COMPLETELY noob-friendly and available to those without PC's just like the popular 'nix-on-droid' apps are, apart from this is native Linux, and not just proot/chroot.
What'cha think???

Link to comment
Share on other sites

hi I am new in this forum, and I need someone more experienced than me to solve the problem of the my tv box (leelbox s1) (A53 Cortex S905X)  practically I cannot start his wlan0 because it cannot be seen by any of the image files in this link https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ!35ACSCjQ than to try other images from this forum ... but there is no way ... the driver of my wlan0 card is RTL871X ... someone tells me how can I solve ??? thank you. 

Link to comment
Share on other sites

Hi all,

I have a p212 board (Scishion v88 Pro, 1GB RAM), running the Armbian_20.02.0-rc1.037_Aml-s9xxx_buster_current_5.5.0-rc6_20200205.img.xz image, with LXDE installed. I have one problem with it - when I switch the TV input to the box, and the graphic desktop is active, the box hangs - connected SSH clients freeze and tv shows "no signal". If a text TTY is currently active (ctrl+alt+f1), this doesn't happen.

I managed to get a syslog error logged when the system hangs, which I have included below. It doesn't matter if TV has CEC enabled or not. It looks like I may be able to work this around by disabling CEC on the box, but how do I do it? Also, would switching to another kernel fix the problem? Or maybe using the "desktop" image? It's really annoying and I haven't found anyone complaining about such a problem. Thanks in advance!

Feb 09 12:54:49 mediabox kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Feb 09 12:54:49 mediabox kernel: rcu:         0-....: (1 GPs behind) idle=142/1/0x4000000000000002 softirq=29693/29694 fqs=2624 
Feb 09 12:54:49 mediabox kernel:         (t=5250 jiffies g=82217 q=18322)
Feb 09 12:54:49 mediabox kernel: Task dump for CPU 0:
Feb 09 12:54:49 mediabox kernel: irq/36-dw_hdmi_ D    0   280      2 0x00000028
Feb 09 12:54:49 mediabox kernel: Call trace:
Feb 09 12:54:49 mediabox kernel:  dump_backtrace+0x0/0x1e0
Feb 09 12:54:49 mediabox kernel:  show_stack+0x14/0x20
Feb 09 12:54:49 mediabox kernel:  sched_show_task+0x17c/0x1a8
Feb 09 12:54:49 mediabox kernel:  dump_cpu_task+0x40/0x4c
Feb 09 12:54:49 mediabox kernel:  rcu_dump_cpu_stacks+0x94/0xd0
Feb 09 12:54:49 mediabox kernel:  rcu_sched_clock_irq+0x7e4/0xa50
Feb 09 12:54:49 mediabox kernel:  update_process_times+0x2c/0x68
Feb 09 12:54:49 mediabox kernel:  tick_sched_handle.isra.18+0x3c/0x50
Feb 09 12:54:49 mediabox kernel:  tick_sched_timer+0x48/0x98
Feb 09 12:54:49 mediabox kernel:  __hrtimer_run_queues+0x118/0x1a8
Feb 09 12:54:49 mediabox kernel:  hrtimer_interrupt+0xe4/0x238
Feb 09 12:54:49 mediabox kernel:  arch_timer_handler_phys+0x2c/0x38
Feb 09 12:54:49 mediabox kernel:  handle_percpu_devid_irq+0x80/0x140
Feb 09 12:54:49 mediabox kernel:  generic_handle_irq+0x24/0x38
Feb 09 12:54:49 mediabox kernel:  __handle_domain_irq+0x60/0xb8
Feb 09 12:54:49 mediabox kernel:  gic_handle_irq+0x50/0xa0
Feb 09 12:54:49 mediabox kernel:  el1_irq+0xcc/0x180
Feb 09 12:54:49 mediabox kernel:  mutex_spin_on_owner+0xb8/0xd0
Feb 09 12:54:49 mediabox kernel:  __mutex_lock.isra.11+0x35c/0x500
Feb 09 12:54:49 mediabox kernel:  __mutex_lock_slowpath+0x10/0x18
Feb 09 12:54:49 mediabox kernel:  mutex_lock+0x30/0x38
Feb 09 12:54:49 mediabox kernel:  dw_hdmi_cec_enable+0x1c/0x58
Feb 09 12:54:49 mediabox kernel:  dw_hdmi_cec_enable+0xbc/0x108 [dw_hdmi_cec]

 

Edited by mbop
Link to comment
Share on other sites

I tried to disable CEC by appending hdmitx=cec0 to the kernel commandline in uEnv.txt, but that didn't fix it. Another kernel stack trace I managed to capture:

Feb 09 14:49:19 mediabox kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Feb 09 14:49:19 mediabox kernel: rcu:         0-....: (5246 ticks this GP) idle=cbe/1/0x4000000000000002 softirq=27973/27973 fqs=2620 
Feb 09 14:49:19 mediabox kernel:         (t=5250 jiffies g=57945 q=9048)
Feb 09 14:49:19 mediabox kernel: Task dump for CPU 0:
Feb 09 14:49:19 mediabox kernel: irq/36-dw_hdmi_ D    0   278      2 0x0000002a
Feb 09 14:49:19 mediabox kernel: Call trace:
Feb 09 14:49:19 mediabox kernel:  dump_backtrace+0x0/0x1e0
Feb 09 14:49:19 mediabox kernel:  show_stack+0x14/0x20
Feb 09 14:49:19 mediabox kernel:  sched_show_task+0x17c/0x1a8
Feb 09 14:49:19 mediabox kernel:  dump_cpu_task+0x40/0x4c
Feb 09 14:49:19 mediabox kernel:  rcu_dump_cpu_stacks+0x94/0xd0
Feb 09 14:49:19 mediabox kernel:  rcu_sched_clock_irq+0x7e4/0xa50
Feb 09 14:49:19 mediabox kernel:  update_process_times+0x2c/0x68
Feb 09 14:49:19 mediabox kernel:  tick_sched_handle.isra.18+0x3c/0x50
Feb 09 14:49:19 mediabox kernel:  tick_sched_timer+0x48/0x98
Feb 09 14:49:19 mediabox kernel:  __hrtimer_run_queues+0x118/0x1a8
Feb 09 14:49:19 mediabox kernel:  hrtimer_interrupt+0xe4/0x238
Feb 09 14:49:19 mediabox kernel:  arch_timer_handler_phys+0x2c/0x38
Feb 09 14:49:19 mediabox kernel:  handle_percpu_devid_irq+0x80/0x140
Feb 09 14:49:19 mediabox kernel:  generic_handle_irq+0x24/0x38
Feb 09 14:49:19 mediabox kernel:  __handle_domain_irq+0x60/0xb8
Feb 09 14:49:19 mediabox kernel:  gic_handle_irq+0x50/0xa0
Feb 09 14:49:19 mediabox kernel:  el1_irq+0xcc/0x180
Feb 09 14:49:19 mediabox kernel:  mutex_spin_on_owner+0x50/0xd0
Feb 09 14:49:19 mediabox kernel:  __mutex_lock.isra.11+0x35c/0x500
Feb 09 14:49:19 mediabox kernel:  __mutex_lock_slowpath+0x10/0x18
Feb 09 14:49:19 mediabox kernel:  mutex_lock+0x30/0x38
Feb 09 14:49:19 mediabox kernel:  dw_hdmi_cec_enable+0x1c/0x58
Feb 09 14:49:19 mediabox kernel:  dw_hdmi_cec_enable+0xbc/0x108 [dw_hdmi_cec]
Feb 09 14:49:19 mediabox kernel:  __cec_s_phys_addr+0x184/0x270
Feb 09 14:49:19 mediabox kernel:  cec_s_phys_addr+0x44/0x60
Feb 09 14:49:19 mediabox kernel:  cec_notifier_set_phys_addr.part.9+0x50/0x68
Feb 09 14:49:19 mediabox kernel:  cec_notifier_set_phys_addr_from_edid+0x5c/0x70
Feb 09 14:49:19 mediabox kernel:  dw_hdmi_get_edid+0x68/0xf0
Feb 09 14:49:19 mediabox kernel:  dw_hdmi_update_power+0xc0/0x1878
Feb 09 14:49:19 mediabox kernel:  dw_hdmi_setup_rx_sense+0x48/0x98
Feb 09 14:49:19 mediabox kernel:  dw_hdmi_top_thread_irq+0x2c/0x50
Feb 09 14:49:19 mediabox kernel:  irq_thread_fn+0x28/0x88
Feb 09 14:49:19 mediabox kernel:  irq_thread+0x13c/0x1d0
Feb 09 14:49:19 mediabox kernel:  kthread+0x120/0x128
Feb 09 14:49:19 mediabox kernel:  ret_from_fork+0x10/0x18

 

Link to comment
Share on other sites

Hi,

 

I've just setup armbian to run from sdcard on a NexBox a95x-B7N (s905x, 2G Ram, 8G Rom).

 

Running a minimal install for desktop (server image + Xorg, openbox and tools I use installed manually).

 

My issue is the X server runs at 1080p while hooked via HDMI to a 1440p@60 display (Dell P2416D).

xrandr does not detect any higher resolution than 1080p, and the edid doesn't show any either:

 

~$ edid-decode  /sys/devices/platform/soc/d0100000.vpu/drm/card0/card0-HDMI-A-1/edid
EDID version: 1.3
Manufacturer: DEL Model a0c3 Serial Number 808797781
Made in week 43 of 2015
Digital display
Maximum image size: 53 cm x 30 cm
Gamma: 2.20
DPMS levels: Standby Suspend Off
RGB color display
First detailed timing is preferred timing
Display x,y Chromaticity:
  Red:   0.6533, 0.3310
  Green: 0.2958, 0.6210
  Blue:  0.1484, 0.0517
  White: 0.3134, 0.3291
Established timings supported:
  720x400@70Hz 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz
  640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
  640x480@75Hz 4:3 HorFreq: 37500 Hz Clock: 31.500 MHz
  800x600@60Hz 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz
  800x600@75Hz 4:3 HorFreq: 46900 Hz Clock: 49.500 MHz
  1024x768@60Hz 4:3 HorFreq: 48400 Hz Clock: 65.000 MHz
  1024x768@75Hz 4:3 HorFreq: 60000 Hz Clock: 78.750 MHz
  1280x1024@75Hz 5:4 HorFreq: 80000 Hz Clock: 135.000 MHz
Standard timings supported:
  1280x800@60Hz 16:10
  1680x1050@60Hz 16:10 HorFreq: 64700 Hz Clock: 119.000 MHz
  1920x1200@60Hz 16:10 HorFreq: 74000 Hz Clock: 154.000 MHz
  1152x864@75Hz 4:3 HorFreq: 67500 Hz Clock: 108.000 MHz
  1600x1200@60Hz 4:3 HorFreq: 75000 Hz Clock: 162.000 MHz
  1280x1024@60Hz 5:4 HorFreq: 64000 Hz Clock: 108.000 MHz
  1920x1080@60Hz 16:9
Detailed mode: Clock 241.500 MHz, 527 mm x 296 mm
               2560 2608 2640 2720 hborder 0
               1440 1443 1448 1481 vborder 0
               +hsync -vsync 
               VertFreq: 59 Hz, HorFreq: 88786 Hz
Serial number: 6RC2C5AJ05FU
Monitor name: DELL P2416D
Monitor ranges (GTF): 49-86Hz V, 29-113kHz H, max dotclock 280MHz
Has 1 extension blocks
Checksum: 0x1d (valid)

CTA extension block
Extension version: 3
31 bytes of CTA data
  Video data block
    VIC  16 1920x1080@60Hz 16:9 (native) HorFreq: 67500 Hz Clock: 148.500 MHz
    VIC   5 1920x1080i@60Hz 16:9  HorFreq: 33750 Hz Clock: 74.250 MHz
    VIC   4 1280x720@60Hz 16:9  HorFreq: 45000 Hz Clock: 74.250 MHz
    VIC   3 720x480@60Hz 16:9  HorFreq: 31469 Hz Clock: 27.000 MHz
    VIC   2 720x480@60Hz 4:3  HorFreq: 31469 Hz Clock: 27.000 MHz
    VIC   7 1440x480i@60Hz 16:9  HorFreq: 15734 Hz Clock: 27.000 MHz
    VIC  22 1440x576i@50Hz 16:9  HorFreq: 15625 Hz Clock: 27.000 MHz
    VIC   1 640x480@60Hz 4:3  HorFreq: 31469 Hz Clock: 25.175 MHz
    VIC   6 1440x480i@60Hz 4:3  HorFreq: 15734 Hz Clock: 27.000 MHz
    VIC  17 720x576@50Hz 4:3  HorFreq: 31250 Hz Clock: 27.000 MHz
    VIC  18 720x576@50Hz 16:9  HorFreq: 31250 Hz Clock: 27.000 MHz
    VIC  21 1440x576i@50Hz 4:3  HorFreq: 15625 Hz Clock: 27.000 MHz
    VIC  19 1280x720@50Hz 16:9  HorFreq: 37500 Hz Clock: 74.250 MHz
    VIC  20 1920x1080i@50Hz 16:9  HorFreq: 28125 Hz Clock: 74.250 MHz
    VIC  31 1920x1080@50Hz 16:9  HorFreq: 56250 Hz Clock: 148.500 MHz
    VIC  32 1920x1080@24Hz 16:9  HorFreq: 27000 Hz Clock: 74.250 MHz
  Audio data block
    Linear PCM, max channels 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 1.0.0.0
  Speaker allocation data block
    Speaker map:
      FL/FR - Front Left/Right
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 148.500 MHz, 527 mm x 296 mm
               1920 2008 2052 2200 hborder 0
               1080 1084 1089 1125 vborder 0
               +hsync +vsync 
               VertFreq: 60 Hz, HorFreq: 67500 Hz
Detailed mode: Clock 74.250 MHz, 527 mm x 296 mm
               1920 2008 2052 2200 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced 
               VertFreq: 60 Hz, HorFreq: 33750 Hz
Detailed mode: Clock 74.250 MHz, 527 mm x 296 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync 
               VertFreq: 60 Hz, HorFreq: 45000 Hz
Detailed mode: Clock 27.000 MHz, 527 mm x 296 mm
                720  736  798  858 hborder 0
                480  489  495  525 vborder 0
               -hsync -vsync 
               VertFreq: 59 Hz, HorFreq: 31468 Hz
Detailed mode: Clock 197.000 MHz, 527 mm x 296 mm
               2048 2400 2616 2752 hborder 0
               1152 1187 1192 1195 vborder 0
               -hsync +vsync 
               VertFreq: 59 Hz, HorFreq: 71584 Hz
Checksum: 0x4d (valid)

 

Yet, I know for a fact the monitor works perfectly at 1440p over HDMI (linux desktop connected to it works at proper resolution).

 

What am I missing ?

Any hardware limitations I am not aware of ?

Any hints where to look at or how to setup the resolution at2560x1440@60 ?

 

Thanks a lot !

Link to comment
Share on other sites

2 hours ago, ElTeide said:

Any hints where to look at or how to setup the resolution at2560x1440@60 ?

 

You could try adding it manually. Here and example:
 

Add display resolution
----------------------
cvt 2560 1440 60                                                                                           Select the display resolution you want
# 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz
Modeline "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync

xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync         Add resolution, everything after Modeline from cvt is copied after newmode

xrandr --addmode HDMI-1 2560x1440_60.00                                                                    Add the new resolution to your display

xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync && xrandr --addmode HDMI-1 2560x1440_60.00 

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines