Testers appreciated for new inxi/pinxi feature: bluetooth!!! yes, finally!

[h2-1]

I'm slowly going through old inxi issues and feature requests, next up is now more or less working and debugged:

pinxi -E or pinxi --bluetooth

As usual: pinxi -U
to update pinxi if you already have it installed, or:

Code: Select all

cd /usr/local/bin && sudo wget -O pinxi smxi.org/pinxi && sudo chmod +x pinxi

Note that -Ea adds the Report: line, and the -x, -xx, and -xxx options work pretty much the same as on -A, -G, and -n.

-E most closely corresponds to -n, with the Device-x/HCI, similar to Device-x/IF lines of -n.

I actually debated making -E/-e, but inxi is running out of letters for single character options.

IF bluetooth date is found, -F will show -E, pretty much the same as -R, which only shows if raid data is actually there for -F.

Note that the HCI part needs hciconfig, which is allegedly deprecated, but since this was one reason I never did the feature when it was originally requested in 2016, and since all the distros are still shipping bluez hci tools, I figured, let's get it out the door, and if either bluez is developed more actively again, which would be nice to see since hciconfig is a nice tool, or if a reasonably sane replacement is found, I can just map the HCI fields to the values of a new tool at some point, but I couldn't find one that actually works as expected and required on the command line.

Any feedback, samples, etc, appreciated.

Code: Select all

pinxi  -Eay
Bluetooth:
  Device-1: Broadcom BCM2045B (BDC-2.1) type: USB driver: btusb v: 0.8 
  bus ID: 1-1.4:3 chip ID: 0a5c:217f class ID: fe01 serial: CCAF78E56A76 
  Report: id: hci0 state: up running bt-v: 2.0 lmp-v: 3.0 sub-v: 2ec 
  address: CC:AF:78:E5:6A:76 
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park 
  link-mode: slave accept

Or using -y1 so the structure is more clear:

Code: Select all

Bluetooth:
  Device-1: Broadcom BCM2045B (BDC-2.1)
    type: USB
    driver: btusb
      v: 0.8
    bus ID: 1-1.4:3
    chip ID: 0a5c:217f
    class ID: fe01
    serial: CCAF78E56A76
    Report: 
      id: hci0
      state: up running
      bt-v: 2.0
      lmp-v: 3.0
        sub-v: 2ec
      hci-v: 3.0
        rev: 4203
      address: CC:AF:78:E5:6A:76
      Info: 
        acl-mtu: 1021:8
        sco-mtu: 64:1
        link-policy: rswitch hold sniff park
        link-mode: slave accept

[Jerry3904]

BTW: have you had any testing on Raspberry Pi? I see an error on our respin and will get it to you if interested.

[h2-1]

Make sure with ARM that you are using current inxi version, there were some ARM errors on inxi 3.0 I think, most are fixed. For a while I had some ssh access to arm devices, but I don't anymore, but always with arm use current inxi, never distro frozen pool inxi, I just did a bunch of stuff for arm too to deal with some android issues, I think that was part of 3.2 dev process. ARM is a pain because there are pretty much no standards on how boards report themselves, it's almost literally a case by case basis, so most of inxi arm support is empirical, board by board.

note that the best supported boards are the ones I got long term ssh access to, but most of the arm fixes seem to be fairly consistent, a lot of the android stuff I did applies also to other soc type arm devices.

If you see errors with current inxi, which is 3.2.02 right now, soon to be 3.3.00, then yes, let me know, arm errors are often easy to fix.

note one thing I can't get fixed without ongoing ssh access to the device is the rasberry pi wifi, which is running off an mmcblk device, which I have no idea how to get get data about, inxi can only handle mmc block devices, as of yet have not been able to solve the issue of things like networking running on an mmc device, that requires a prolonged ssh access so I can figure out how to deal with that particular situation, which appears to be fairly unique to rasberry pi 3, not sure if it exists in v4, and it didn't in v2 boards.

[oops]

Hello,
Here it is:

Code: Select all

./pinxi -U
./pinxi  --version
pinxi 3.3.00-01 (2021-01-28)

...

$ ./pinxi  -Eayz
Bluetooth:
  Device-1: Micro Star Bluetooth EDR Device type: USB driver: btusb v: 0.8 
  bus ID: 5-1:3 chip ID: 0db0:a97a class ID: e001 
  Report: ID: hci0 state: up running bt-v: 1.2 lmp-v: 2.1 sub-v: 12e7 
  hci-v: 2.1 rev: 12e7 address: <filter> 
  Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park 
  link-mode: slave accept service-classes: rendering, capturing 

user1-mx@mx-eepc:/home/user1/test/pinxi_inxi
$ ./pinxi  -Eay1z
$ ./pinxi  -Eay1z
Bluetooth:
  Device-1: Micro Star Bluetooth EDR Device
    type: USB
    driver: btusb
      v: 0.8
    bus ID: 5-1:3
    chip ID: 0db0:a97a
    class ID: e001
    Report: 
      ID: hci0
      state: up running
      bt-v: 1.2
      lmp-v: 2.1
        sub-v: 12e7
      hci-v: 2.1
        rev: 12e7
      address: <filter>
      Info: 
        acl-mtu: 310:10
        sco-mtu: 64:8
        link-policy: rswitch hold sniff park
        link-mode: slave accept
        service-classes: rendering, capturing

[h2-1]

Looking good, I wax racing debian next stable freeze date, which is in a week or two, so this needed to be in sid quite soon, hopefully it will make it.

[caprea]

Many thanks for the new feature, h2-1
This is on thinkpad

Code: Select all

$ pinxi  -Eay
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus ID: 3-11:4 
  chip ID: 8087:07dc class ID: e001 
  Report: id: hci0 state: up running pscan iscan bt-v: 2.1 lmp-v: 4.0 
  sub-v: e00 hci-v: 4.0 rev: e00 address: CC:3D:82:1C:F4:D9 
  Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff 
  link-mode: slave accept service-classes: rendering, capturing, audio 

and here's the desktop with a bluetooth usb adapter

Code: Select all

$  pinxi  -Eay
Bluetooth:
  Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8 
  bus ID: 3-9.1:6 chip ID: 0a5c:21e8 class ID: fe01 serial: 5CF3709CB82B 
  Report: ID: hci0 state: up running pscan iscan bt-v: 2.1 lmp-v: 4.0 
  sub-v: 220e hci-v: 4.0 rev: 1000 address: 5C:F3:70:9C:B8:2B 
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff 
  link-mode: slave accept service-classes: rendering, capturing, audio