M0062 Ethernet not discovered
-
Hi,
I have a VOXEL 2 and the M0062-2 shield on top of it.
The documentation is a little sparse on this module, hence why i ask here.Is there anything i have to do in order to enable the Ethernet port?
lsusb shows two hubs, but nothing else.
It is not showing up at all when it is connected.Best
Kasper -
Hi,
I have a VOXEL 2 and the M0062-2 shield on top of it.
The documentation is a little sparse on this module, hence why i ask here.Is there anything i have to do in order to enable the Ethernet port?
lsusb shows two hubs, but nothing else.
It is not showing up at all when it is connected.Best
Kasper -
@ksl no, and that Ethernet port would have been tested prior to shipment. Is Ethernet networking not working? Are you plugging in an Ethernet device when you type lsusb?
@Moderator,
I did a little more digging and came a bit further, but I have two different problems now.Firstly I can see the Ethernet adapter using lsusb. That said, it never registers as connected and no communication runs over it.
I have isolated the eth. adapter on the board by having a USB Ethernet adapter on the USB port. This works and get and ip etc.
This is using your release image for the VOXEL 2 board.
The second problem (and what started this) is that I am building my own image, when doing this i only get the root hubs
The build is your base image, from the documentation, to validate this was not changes on my end. The physical setup is as above. In this scenario nothing is showing up on though.Best
Kasper -
@Moderator,
I did a little more digging and came a bit further, but I have two different problems now.Firstly I can see the Ethernet adapter using lsusb. That said, it never registers as connected and no communication runs over it.
I have isolated the eth. adapter on the board by having a USB Ethernet adapter on the USB port. This works and get and ip etc.
This is using your release image for the VOXEL 2 board.
The second problem (and what started this) is that I am building my own image, when doing this i only get the root hubs
The build is your base image, from the documentation, to validate this was not changes on my end. The physical setup is as above. In this scenario nothing is showing up on though.Best
Kasper@ksl
This may or may not related, but we have found some few physical ports are a little hard to insert an RJ45 cable at first. Be sure you are fully inserted in the jack and even try it a few times. Once the jack and mating cable have been used a few times, the initial tight tolerances should start to loosen allowing for an easier RJ45 cable insertion.
But, as Moderator mentioned, all of these were indeed tested at our facility prior to shipping including making a network connection.
Hope that helps! -
@ksl
This may or may not related, but we have found some few physical ports are a little hard to insert an RJ45 cable at first. Be sure you are fully inserted in the jack and even try it a few times. Once the jack and mating cable have been used a few times, the initial tight tolerances should start to loosen allowing for an easier RJ45 cable insertion.
But, as Moderator mentioned, all of these were indeed tested at our facility prior to shipping including making a network connection.
Hope that helps!@Vinny I will give that a try, otherwise I heard from my college that he might have had one that stopped working at some point.
That said, this was mainly to validate that our own kernel build worked as the one shipped in the SDK, Any idea about what could stop the extra devices from being detected?Best
Kasper -
@Vinny I will give that a try, otherwise I heard from my college that he might have had one that stopped working at some point.
That said, this was mainly to validate that our own kernel build worked as the one shipped in the SDK, Any idea about what could stop the extra devices from being detected?Best
Kasper@ksl Possebly related to this, when i build my own kernel, i get:
[ 23.886763] 8188eu: disagrees about version of symbol module_layout [ 23.917344] 8821cu: disagrees about version of symbol module_layout [ 23.940321] 88XXau: disagrees about version of symbol module_layout [ 23.950527] q6_pdr_dlkm: disagrees about version of symbol module_layout [ 24.037974] q6_pdr_dlkm: disagrees about version of symbol module_layout [ 24.159403] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.166971] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.232182] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.331171] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.453120] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.460695] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.469246] pinctrl_wcd_dlkm: disagrees about version of symbol module_layout [ 24.477432] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.588591] swr_dlkm: disagrees about version of symbol module_layout [ 24.595719] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.604323] hdmi_dlkm: disagrees about version of symbol module_layout [ 24.611722] stub_dlkm: disagrees about version of symbol module_layout [ 24.620298] wcd_core_dlkm: disagrees about version of symbol module_layout [ 24.627745] wcd_core_dlkm: disagrees about version of symbol module_layout [ 24.635146] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.642687] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.650231] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.657966] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.780032] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.868200] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.978382] swr_dlkm: disagrees about version of symbol module_layout [ 24.986022] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.994470] voxl_fsync_mod: disagrees about version of symbol module_layout [ 25.016775] voxl_gpio_mod: disagrees about version of symbol module_layout [ 25.025231] voxl_platform_mod: disagrees about version of symbol module_layout -
@ksl Possebly related to this, when i build my own kernel, i get:
[ 23.886763] 8188eu: disagrees about version of symbol module_layout [ 23.917344] 8821cu: disagrees about version of symbol module_layout [ 23.940321] 88XXau: disagrees about version of symbol module_layout [ 23.950527] q6_pdr_dlkm: disagrees about version of symbol module_layout [ 24.037974] q6_pdr_dlkm: disagrees about version of symbol module_layout [ 24.159403] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.166971] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.232182] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.331171] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.453120] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.460695] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.469246] pinctrl_wcd_dlkm: disagrees about version of symbol module_layout [ 24.477432] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.588591] swr_dlkm: disagrees about version of symbol module_layout [ 24.595719] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.604323] hdmi_dlkm: disagrees about version of symbol module_layout [ 24.611722] stub_dlkm: disagrees about version of symbol module_layout [ 24.620298] wcd_core_dlkm: disagrees about version of symbol module_layout [ 24.627745] wcd_core_dlkm: disagrees about version of symbol module_layout [ 24.635146] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.642687] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.650231] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.657966] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.780032] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.868200] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.978382] swr_dlkm: disagrees about version of symbol module_layout [ 24.986022] snd_event_dlkm: disagrees about version of symbol module_layout [ 24.994470] voxl_fsync_mod: disagrees about version of symbol module_layout [ 25.016775] voxl_gpio_mod: disagrees about version of symbol module_layout [ 25.025231] voxl_platform_mod: disagrees about version of symbol module_layout@ksl
This problem was linked to: https://forum.modalai.com/topic/3329/voxl2-kernel-rebuild-gpio-sysfs-does-not-work/5So it seems that if the kernel is build in debug mode the Voxl kerne modules are not rebuild and the
disagrees about version of symbol module_layoutwill happen.
I would be good that this is either documented in the kenel build guide or even better, that this is corrected so that the kernel can be build and run in debug mode. -
@ksl
This may or may not related, but we have found some few physical ports are a little hard to insert an RJ45 cable at first. Be sure you are fully inserted in the jack and even try it a few times. Once the jack and mating cable have been used a few times, the initial tight tolerances should start to loosen allowing for an easier RJ45 cable insertion.
But, as Moderator mentioned, all of these were indeed tested at our facility prior to shipping including making a network connection.
Hope that helps! -
@Vinny Any update on the difference of the debug and perf build would be appreciated.
Best
Kasper -
Hi @ksl
Sorry, this is not my specialty. I am HW team, not SW.
You might be best at this point to start a new thread specifically with this issue of debug vs perf so new eyes get on it.
Thanks!@ksl , if the issue is only with the debug build, could you just use a regular perf build of the Kernel?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login