Arch Linux not detecting Bela

jordanwhite

I've just unpacked my bela starter kit and tried to get it going. On my girlfriend's Windows machine I can get things working fine. On my own thinkpad running Arch Linux, neither bela.local nor 192.168.7.2 works. I've spent some time trying to get things happening (also using deepseek to try to get some help) to absolutely no avail. I looked at this thread, but it's for Kubuntu and I don't have the directory /etc/netplan which makes me somewhat skeptical that this would work.

Has anyone got experience getting a bela up and running on arch linux?

Thanks!
Jordan

giuliomoro

Do you see any new network interfaces one minute after you connect Bela?

jordanwhite

giuliomoro nothing at all, except that the bela gets power

giuliomoro

One question: why did you initially say

jordanwhite nothing at all, except that the bela gets power

giuliomoro

Does it show up as a composite device in lsusb ?

jordanwhite

giuliomoro nope

giuliomoro

Get dmesg -w running in a terminal and plug the board in. After about twenty seconds you should start seeing some sign of activity, do you get anything?

jordanwhite

yep!

[ 9721.605438] usb 1-1: new high-speed USB device number 9 using xhci_hcd
[ 9721.736628] usb 1-1: New USB device found, idVendor=1d6b, idProduct=0104, bcdDevice= 1.02
[ 9721.736646] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9721.736655] usb 1-1: Product: Bela
[ 9721.736661] usb 1-1: Manufacturer: Augmented Instruments Ltd
[ 9721.736666] usb 1-1: SerialNumber: __bela__
[ 9721.745904] rndis_host 1-1:1.0 usb1: register 'rndis_host' at usb-0000:00:14.0-1, RNDIS device, be:1a:b4:75:b4:0e
[ 9721.770258] cdc_ncm 1-1:1.2: MAC-Address: be:1a:b4:75:b4:11
[ 9721.770792] cdc_ncm 1-1:1.2 usb2: register 'cdc_ncm' at usb-0000:00:14.0-1, CDC NCM (NO ZLP), be:1a:b4:75:b4:11
[ 9721.776693] usb-storage 1-1:1.4: USB Mass Storage device detected
[ 9721.777351] scsi host1: usb-storage 1-1:1.4
[ 9721.778565] cdc_acm 1-1:1.5: ttyACM0: USB ACM device
[ 9721.780188] usb 1-1: Quirk or no altset; falling back to MIDI 1.0
[ 9721.829804] rndis_host 1-1:1.0 enp0s20f0u1: renamed from usb1
[ 9721.846134] cdc_ncm 1-1:1.2 enp0s20f0u1i2: renamed from usb2
[ 9722.802841] scsi 1:0:0:0: Direct-Access     Linux    File-Stor Gadget 0414 PQ: 0 ANSI: 2
[ 9722.803996] sd 1:0:0:0: Power-on or device reset occurred
[ 9722.808508] sd 1:0:0:0: [sdb] 137953 512-byte logical blocks: (70.6 MB/67.4 MiB)
[ 9722.808995] sd 1:0:0:0: [sdb] Write Protect is off
[ 9722.809014] sd 1:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 9722.809279] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9722.843290]  sdb:
[ 9722.843378] sd 1:0:0:0: [sdb] Attached SCSI removable disk

giuliomoro

Do you get anything with ls /dev/sdb after that?

jordanwhite

giuliomoro Just /dev/sdb itself

giuliomoro

so the device is recognised and made accessible.

When you look at your network interfaces you should see enp0s20f0u1 and enp0s20f0u1i2 , is that so?

jordanwhite

yes!

giuliomoro

You should be able to dhclient on either and that should get you an IP address from the board.

try e.g.:

sudo dhclient enp0s20f0u1i2

After a few seconds the interface should have an IP address, either 192.168.6.1 or 192.168.7.1 . At that point you should be able to ping 192.168.6.2 or ping 192.168.7.2 respectively and open in the browser http://192.168.6.2 or http://192.168.7.2 respectively. Note the .1 (the address of your computer on each network) vs .2 (the address of the board on each network).

jordanwhite

Yep, that has worked, thanks so much for your help and patience!

jordanwhite

giuliomoro I initially tried lsusb, then the second time remembered ip a - my mistake.