01:54 | mhilt_ | @jnettlet -- I purchased a parallel ov5640 that has the oscillator on the module |
01:55 | mhilt_ | i2c works, but the driver still appears to fail to load |
05:01 | jnettlet | mhilt_, can you post the messages from dmesg? |
14:52 | topi` | Artox: I upgraded my HB-gate to stretch, and now I got these odd network names like enx1234567890 instead of "eth0" etc |
14:53 | Humpelstilzchen | topi`: you can disable them in cmdline |
14:53 | topi` | Humpelstilzchen: I'd rather get them working as they do on PC platform |
14:53 | topi` | see: |
14:53 | topi` | E: ID_NET_NAME_MAC=enxe03f49b159c0 |
14:53 | topi` | E: ID_NET_NAME_ONBOARD=eno1 |
14:53 | topi` | E: ID_NET_NAME_PATH=enp0s25 |
14:53 | topi` | what I only get from udevadm on HB, is that ID_NET_NAME_MAC |
14:53 | topi` | the other two are entirely missing |
14:54 | topi` | try udevadm info -e | grep -A15 ^P.*eth0 and you'll see what I mean |
14:55 | vpeter | topi`: I think this is normal - ethernet names has been changed. |
14:59 | vpeter | Try adding net.ifnames=0 to boot parameters to get ethX back? |
14:59 | topi` | vpeter: yeah, and I agree that the old skool "eth0, eth1" naming scheme has problems, and i'd like to get ID_NET_NAME_PATH working on the HB |
14:59 | topi` | or ONBOARD names |
15:00 | vpeter | some reading http://www.linuxquestions.org/questions/debian-26/debian-testing-stretch-what%27s-the-point-to-rename-eth0-wlan0-at-boot-4175581508/ |
15:00 | topi` | but the ethernet does not sit on a PCI bus on the HB... |
15:00 | vpeter | I was thinking wtf few months back when upgraded Ubuntu :( |
15:01 | Humpelstilzchen | vpeter: you are not alone.. |
15:02 | vpeter | After few days when whole sw was set up I just ignore this. Let's use enp5s0 then :) |
15:03 | topi` | can be slightly difficult to remember, but then "ip a" will show the names |
15:04 | topi` | anyways, it used to be like this on Solaris for many, many yerars |