Searching testing people for hdmi + wifi in Kernel 4.16

Hi,

we search people for testing new function before they get merged into main-branch to find out bugs.

Sourcecode (HDMI):

Sourcecode (WIFI):

compiled Kernel: https://drive.google.com/drive/folders/1dJPz1REuIQiVfY4XliGOmGSZVDgT80Yc

how to install new kernel: https://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:kernel#compiled_414x

regards Frank

1 Like

previous discussion: Hdmi in uboot and linux

some info about (e.g. how to set resolution in uenv.txt) in my wiki: http://www.fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:hdmi

tested resolutions

working:

not working:

I have uploaded combined kernel (hdmi+wlan)…

driver is also ported to 4.14 in branch 4.14-hdmi

Please give us the following information:

  • kernel used (4.14/4.16)
  • operation system (debian/ubuntu with version)
  • resolutions and frequency (vsync)
  • adapters used (dvi/vga) if any
  • tested function (fbconsole/xorg)
  • problems

1024x600 Not working As the version 4.4 do the same.7080B70B4495D6546D8D5B26FDB88C6Fbut 1280x800 Works fine.

1 Like

Do you use 1024x600 direct (hdmi-hdmi,without adapter)? Does this resolution work with other client on same monitor? What is your vsync (hz)

Yes just HDMI to HDMI cable,if I use [email protected] ,it results more strange mode([email protected]). At Windows I can manually set the resolution and it works fine. At Linux PC ,it is plug and play. At my raspberry Pi …it just output 512x600,without tear.

you set it via uEnv.txt (video=) or how do you set it?

I set it via uEnv.txt

I’ve tested usin HDMI connection:

640x480 both 75 and 60 Hz - Ok (fb and Xorg)

800x600 both 75 and 60 Hz - Not Ok, Monitor detects resolution as 400x600, image is broken

1024x768 both 75 and 60 Hz - Ok

1280 [email protected] -Ok

[email protected] - Ok

[email protected] - Ok

[email protected](native, selected by default) - Ok

I cant test VGA as I don’t have VGA cable. :frowning:

P.S. Tested on both 4.16, and 4.14 (frank’s 4.14-hdmi branch) kernels

1 Like

I’ve tested [email protected]: It’s don’t works. Resolution detects as 256x600 image is broken, and looks very similar to @tinylib’s photo.

New photo by Alexander Ryabchenko New photo by Alexander Ryabchenko

@Ryder.Lee any idea how to fix the resolution and the hsync-problem?

kernel used 4.16
operation system debian/stretch)
resolutions and frequency (vsync) fbconsole [email protected]
xorg 1920x1080 & 1600x1200 & 1680x1050 & ......60Hz
adapters used no
tested function fbconsole & xorg
problems

hdmi no

but

[    6.447454] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/[email protected]/mdio-bus/[email protected][0]' - status (0)
[    6.468859] gpio gpiochip0: Persistence not supported for GPIO 33
[    6.515841] mdio_bus dsa-0.0: GPIO lookup for consumer reset
[    6.531183] mdio_bus dsa-0.0: using lookup tables for GPIO lookup
[    6.531197] mdio_bus dsa-0.0: lookup for GPIO reset failed
[    6.727284] of_get_named_gpiod_flags: can't parse 'link-gpios' property of node '/[email protected]/mdio-bus/[email protected]/ports/[email protected]/fixed-link[0]'
[    6.778947] of_get_named_gpiod_flags: can't parse 'reset-gpios' property of node '/[email protected]/mdio-bus/[email protected]/ports/[email protected][0]'

at times

[  584.701629] ata1.00: exception Emask 0x10 SAct 0x4 SErr 0x280100 action 0x6 frozen
[  584.709355] ata1.00: irq_stat 0x08000000, interface fatal error
[  584.715429] ata1: SError: { UnrecovData 10B8B BadCRC }
[  584.720659] ata1.00: failed command: READ FPDMA QUEUED
[  584.725913] ata1.00: cmd 60/00:10:00:97:f0/01:00:0e:00:00/40 tag 2 ncq dma 131072 in
[  584.725913]          res 40/00:10:00:97:f0/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
[  584.741911] ata1.00: status: { DRDY }
[  584.745646] ata1: hard resetting link
[  594.742279] ata1: softreset failed (1st FIS failed)
[  594.747259] ata1: hard resetting link
[  604.742492] ata1: softreset failed (1st FIS failed)
[  604.747466] ata1: hard resetting link
[  639.741993] ata1: softreset failed (1st FIS failed)
[  639.746974] ata1: limiting SATA link speed to 3.0 Gbps
[  639.752232] ata1: hard resetting link
[  644.752017] ata1: softreset failed (1st FIS failed)
[  644.756992] ata1: reset failed, giving up
[  644.761068] ata1.00: disabled
[  644.764188] ata1: EH complete
[  644.767351] sd 0:0:0:0: [sda] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.767355] sd 0:0:0:0: [sda] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.767369] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x28 28 00 0e f0 97 00 00 01 00 00
[  644.775686] sd 0:0:0:0: [sda] tag#7 CDB: opcode=0x2a 2a 00 0e e7 98 38 00 00 08 00
[  644.775700] print_req_error: I/O error, dev sda, sector 250058808
[  644.784030] print_req_error: I/O error, dev sda, sector 250648320
[  644.791706] Buffer I/O error on dev sda2, logical block 7, lost async page write
[  644.819362] sd 0:0:0:0: [sda] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.827704] sd 0:0:0:0: [sda] tag#5 CDB: opcode=0x28 28 00 0e f0 98 00 00 01 00 00
[  644.829333] sd 0:0:0:0: [sda] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.829337] sd 0:0:0:0: [sda] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.829348] sd 0:0:0:0: [sda] tag#8 CDB: opcode=0x28 28 00 0e f0 97 00 00 00 08 00
[  644.829353] print_req_error: I/O error, dev sda, sector 250648320
[  644.829476] sd 0:0:0:0: [sda] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.829486] sd 0:0:0:0: [sda] tag#10 CDB: opcode=0x28 28 00 0e f0 97 00 00 00 08 00
[  644.829490] print_req_error: I/O error, dev sda, sector 250648320
[  644.835470] print_req_error: I/O error, dev sda, sector 250648576
[  644.843789] sd 0:0:0:0: [sda] tag#9 CDB: opcode=0x2a 2a 00 10 67 98 00 00 00 10 00
[  644.852204] sd 0:0:0:0: [sda] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.856161] sd 0:0:0:0: [sda] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.856175] sd 0:0:0:0: [sda] tag#12 CDB: opcode=0x28 28 00 19 ad cb 80 00 00 70 00
[  644.856182] print_req_error: I/O error, dev sda, sector 430820224
[  644.858398] sd 0:0:0:0: [sda] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.858410] sd 0:0:0:0: [sda] tag#14 CDB: opcode=0x28 28 00 19 ad cb 80 00 00 08 00
[  644.858416] print_req_error: I/O error, dev sda, sector 430820224
[  644.858534] sd 0:0:0:0: [sda] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  644.858544] sd 0:0:0:0: [sda] tag#16 CDB: opcode=0x28 28 00 19 ad cb 80 00 00 08 00
[  644.858549] print_req_error: I/O error, dev sda, sector 430820224
[  644.859843] print_req_error: I/O error, dev sda, sector 275224576
[  644.866066] sd 0:0:0:0: [sda] tag#6 CDB: opcode=0x2a 2a 00 16 2b 9f 58 00 00 98 00
[  644.867328] print_req_error: I/O error, dev sda, sector 430740952
[  644.874453] Buffer I/O error on dev sda2, logical block 3145728, lost async page write
[  644.874476] Buffer I/O error on dev sda2, logical block 3145729, lost async page write
[  644.882403] Aborting journal on device sda2-8.
[  644.888601] Buffer I/O error on dev sda2, logical block 3153953, lost async page write
[  644.894900] Buffer I/O error on dev sda2, logical block 15237120, lost sync page write
[  645.034724] Buffer I/O error on dev sda2, logical block 3153956, lost async page write
[  645.034759] JBD2: Error -5 detected when updating journal superblock for sda2-8.
[  645.034768] EXT4-fs error (device sda2) in ext4_reserve_inode_write:5764: Journal has aborted
[  645.034768] EXT4-fs error (device sda2) in ext4_reserve_inode_write:5764: Journal has aborted
[  645.035001] EXT4-fs (sda2): Remounting filesystem read-only
[  645.042915] Buffer I/O error on dev sda2, logical block 12582913, lost async page write
[  645.050726] EXT4-fs (sda2): ext4_writepages: jbd2_start: 4095 pages, ino 5637663; err -30
[  645.059194] Buffer I/O error on dev sda2, logical block 12582928, lost async page write
[  645.097110] Buffer I/O error on dev sda2, logical block 12582944, lost async page write
[  645.113025] EXT4-fs warning (device sda2): ext4_end_bio:323: I/O error 10 writing to inode 5637663 (offset 0 size 0 starting bloc
k 31274641)
[  645.133573] Buffer I/O error on device sda2, logical block 17296
[  645.245352] EXT4-fs error (device sda2): ext4_find_entry:1437: inode #4196067: comm aptitude: reading directory lblock 0
[  645.264372] EXT4-fs (sda2): previous I/O error to superblock detected
[  668.108211] scsi_io_completion: 26 callbacks suppressed
[  668.108234] sd 0:0:0:0: [sda] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  668.137783] sd 0:0:0:0: [sda] tag#9 CDB: opcode=0x28 28 00 10 68 99 20 00 00 08 00
[  668.153399] print_req_error: 29 callbacks suppressed
[  668.153404] print_req_error: I/O error, dev sda, sector 275290400
[  668.180684] EXT4-fs warning (device sda2): htree_dirblock_to_tree:978: inode #786443: lblock 0: comm aptitude: error -5 reading d
irectory block
[  668.202310] sd 0:0:0:0: [sda] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  668.219044] sd 0:0:0:0: [sda] tag#10 CDB: opcode=0x28 28 00 16 ed 7c 80 00 00 48 00
[  668.235188] print_req_error: I/O error, dev sda, sector 384662656
[  668.249973] sd 0:0:0:0: [sda] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[  668.266886] sd 0:0:0:0: [sda] tag#11 CDB: opcode=0x28 28 00 16 ed 7c 98 00 00 08 00
[  668.283209] print_req_error: I/O error, dev sda, sector 384662680

IMG_20180604_142304

Sata-issue seems to be this: SATA Kernel 4.14 failed command: IDENTIFY DEVICE

Need pcie-patch…https://github.com/garywangcn/bpi-r2_lede/blob/bpi-r2-on-lede-v1/target/linux/mediatek/patches-4.9/0073-mtk-pcie-bug-fix.patch

i’ve seen the others,but currently no idea how to fix. These should not occour in 4.14…4.16 is no longtime and will be end-of-life soon

I’ve tested VGA agapter - same results. X*600 resolutions don’t work.

can you please test [email protected] over vga and look at the hsync?

@jofri can you please try last 4.16-main for the sata-issue? i have removed the pcie-nodes and re-added them with the patch-file i’ve used for 4.14 (which seems to fix that issue), not much changes, but maybe it’s enough

Actually, X * 600 are not standard DMT or CEA HDMI resolutions but DVI.

HDMI spec:

tmp

MT7623 HW could support these DVI resolutions but I’m not sure whether the related functionality has been implemented or not.

Hi, I’ve testet [email protected] over vga, and I got hsync 48kHz

strange that it does not work in my tests…or only partial after killing xorg first time

@Ryder.Lee can you explain the values for hsync-start and hsync-end because these do not match the expected values

I don’t get your points (hsync-start and hsync-end because these do not match the expected values) ?

tmp