| 09:46 | gwelter | what's the status of esata on the i4pro in the mainline kernel? should it be working? I only get link reset errors: https://pastebin.com/CJrMhsTV |
| 09:47 | gwelter | the same esata drive is mounted with no problem on a dell laptop |
| 10:02 | jnettlet | gwelter, last I checked it worked fine. However it has been a while and it is possible that there have been regressions |
| 10:03 | gwelter | jnettlet, ok, so I should file a kernel bug report? |
| 10:04 | jnettlet | gwelter, I would recommend you try with a slightly older mainline kernel, like the last LTS so you have some idea if it is a long standing bug or a regression. |
| 10:05 | gwelter | jnettlet, I will try that, thx |
| 10:50 | gwelter | jnettlet, booted an image with kernel 4.8.6 and now the drive is recognized but it isn't stable: https://pastebin.com/PZiZSkEX |
| 12:14 | topi` | jnettlet: I'm not getting any picture on a DVI monitor.. so now I'm trying to boot from the Ignition image. Do you think the Ignition image will boot on the imx6q-hummingboard2-som-v15.dtb ? |
| 12:14 | jnettlet | topi`, using the 4.11 kernel? |
| 12:15 | jnettlet | topi`, it will boot but you won't have wifi or bt |
| 12:15 | topi` | ok |
| 12:15 | topi` | I just want to see that the board is alive after my sloppy soldering iron work :) |
| 12:15 | jnettlet | really the only differences with the 1.5 som are wifi, bt, eMMC (for older boards), and SPI-NOR which we don't populate by default |
| 12:16 | topi` | ok |
| 12:16 | topi` | OK the hardware works, I get to the Ignition red screen |
| 12:17 | topi` | any way to get a shell on Ignition image? |
| 12:17 | topi` | to check on /proc/partitions |
| 12:19 | jnettlet | ctrl+alt+f2 should work |
| 12:30 | jnettlet | topi, I am running a bit behind, but I am working on upstream stuff for the 1.5 som now |
| 12:31 | topi` | o, this monitor is stupid and dislikes the mode that HB switches to when using ctrl-alt-f2 |
| 12:31 | topi` | I hate monitors that are picky about the resolution |
| 12:31 | jnettlet | well like I said before hdmi -> dvi and the various resolutions are picky in general We have worked around it the best possible but failure is always an option :) |
| 12:31 | topi` | is the Ignition image just a very basic linux image? so that I can hack 1920x1080 into the uEnv.txt |
| 12:32 | jnettlet | I think it is a buildroot image. I would have though that 1080p would have been the default. |
| 12:50 | mhilt | Hi jnettlet -- any other thoughts on getting that parallel ov5640 driver working? I've not had much luck. |
| 12:52 | jnettlet | mhilt, I was looking over it last night. I think I need you to enable debug on all the drivers and send me the output to look over. |
| 12:53 | seb_ | hello |
| 12:55 | seb_ | how to boot on a hummingboard pro unfused through usb with a usb ftdi cable ? |
| 12:55 | seb_ | please |
| 12:57 | mhilt | okay jnettlet, do i just need to set the dmesg level to 7? or i guess, what should i change to get the debug? |
| 13:09 | jnettlet | mhilt, no you should set #define DEBUG at the top of the various driver files. Or enable dynamic debugging and enable the files on the kernel commandline. |
| 13:54 | topi` | I might have broken something. I flashed the sr-jessie image and the monitor doesn't detect anything on DVI... |
| 13:58 | topi` | but, oddly, I get image if I boot the "ignition.img" |
| 13:58 | topi` | but none of the other images i've tried... |
| 13:58 | topi` | makes me wonder |
| 14:21 | jnettlet | topi`, what does /sys/class/graphics/fb0/modes report? also dmesg. If the monitor isn't detected properly the driver is pretty noisy about it |
| 14:24 | topi` | I can't get to a console |
| 14:24 | topi` | I don't have the usb<>rs232 cable with me :( |
| 14:36 | vpeter | This is must-have equipment. No only one at a time :) |