microdoc Posted November 27, 2022 Posted November 27, 2022 I am new to arm devices. I'm trying to build a fully working armbian system for the pcduino8-uno which uses the Allwinner a83t/h8 soc. I know these are not the best, but I got it from amazon for $18 and it runs home assistant very well. I built a new u-boot which appears to initialize the hardware properly as it sees all the usb port as well as obtains an ip from my dhcp server. Using sun8i-a83t-allwinner-h8homlet-v2 as my starting point.. I built a new kernel from 6.1.0-rc6. Everything seems to work properly except the ethernet controller. I can use a usb ethernet dongle, but I would like to get the onboard working Dmesg shows " [ 1.594628] dwmac-sun8i 1c30000.ethernet: IRQ eth_wake_irq not found [ 1.594656] dwmac-sun8i 1c30000.ethernet: IRQ eth_lpi not found [ 1.594760] dwmac-sun8i 1c30000.ethernet: supply phy not found, using dummy regulator [ 1.595128] dwmac-sun8i 1c30000.ethernet: supply phy-io not found, using dummy regulator [ 1.595363] dwmac-sun8i: probe of 1c30000.ethernet failed with error -22 " I'm assuming something is incorrect in the ethernet driver. Any Ideas how to fix this ? Thanks 0 Quote
ning Posted November 28, 2022 Posted November 28, 2022 10 hours ago, microdoc said: I built a new kernel from 6.1.0-rc6 I think you are using debian official kernel, or build from it. I think you need to check the patches from armbian, cherry pick some to rebuild debian kernel. 0 Quote
microdoc Posted November 28, 2022 Author Posted November 28, 2022 Yes I am using debian but the kernel is built from kernel.org not debian, I have looked at patches but the ones I found for the pcduino8-uno are for 3.x kernel versions 0 Quote
SteeMan Posted November 28, 2022 Posted November 28, 2022 @microdoc Are you using Armbian (builds and/or build environment), or are you just posting here in the armbian forums looking for general guidance? 0 Quote
microdoc Posted November 28, 2022 Author Posted November 28, 2022 i'm using VERSION=22.11.0-trunk buster. I have made a discovery though, if i set my unifi switch port to 100m instead of 1000m it works fine.. So I'm guessing it's a timing issue, just not sure where to adjust that in the source. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.