On Sun, 2015-10-04 at 11:17 +0100, Ian Campbell wrote: > I agree, the URL suggests: > > CONFIG_REGULATOR_DEBUG=y > > CONFIG_REGULATOR_VIRTUAL_CONSUMER=y > > CONFIG_REGULATOR_USERSPACE_CONSUMER=y > > CONFIG_PWM_SUN4I=y > [...] > My best guess is that one of these has some sort of knock-on dependency > which causes something else to be enabled. I'm going to investigate > that possibility now...
Nope, it turns out PWM_SUN4I is already on in our config and the other three are independent and turn on nothing else, which was basically as expected since they are all virtual. SUN4I_PWM is a module, so it might be worth modprobing that (module will be pwm-sun4i it seems) to ensure it is loaded and see if that helps. I don't think it will though. > In the meantime: > > > Please send the boot log from Linux 4.1 (or 4.2, which just landed in > > unstable). > > Yes, please. > > It would also be useful/interesting to know which Allwinner A10 device > this was with. ... and the .config for your working self-built kernel would be useful for comparison too. As well as a dmesg from both the Debian kernel and that one. Given the self-built+working kernel was 3.16 based and the Debian one was 4.1 it may just be that 4.1 has a bug with the Ethernet, so trying 4.2 would indeed be wise too. Ian.
