Testers etc: new inxi/pinxi feature: -E/--bluetooth

General system
1

Going through some of the oldest issue/feature requests of inxi, next in line is bluetooth report, which looks/behaves similar to -n advanced networking report.

As always:

pinxi -U

if you have pinxi installed already, that being the development version of inxi, and
cd /usr/local/bin && sudo wget -O pinxi smxi.org/pinxi && sudo chmod +x pinxi
to install it.

All feedback, posted samples of the output, appreciated since I want to get this one out the door within a day or two to meet certain distro freeze deadlines.

I just discovered an oddity, in some cases, installed bluetooth fails to show at all, or register as present, until I ran:

connmanctl enable bluetooth

pinxi -Eay
Bluetooth:
  Device-1: Broadcom BCM2045B (BDC-2.1) type: USB driver: btusb v: 0.8 
  bus ID: 1-1.4:6 chip ID: 0a5c:217f class ID: fe01 serial: <filter> 
  Report: ID: hci1 state: up running bt-v: 2.0 lmp-v: 3.0 sub-v: 4203 
  hci-v: 3.0 rev: 2ec address: <filter> 
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park 
  link-mode: slave accept 
  Device-2: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8 
  bus ID: 2-1.1:4 chip ID: 0a5c:21e8 class ID: fe01 serial: <filter> 
  Report: ID: hci0 state: up running bt-v: 2.1 lmp-v: 4.0 sub-v: 220e 
  hci-v: 4.0 rev: 1000 address: <filter> 
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff 
  link-mode: slave accept

## using -y1 single key: value pair per line mode:
pinxi -Eay1
Bluetooth:
  Device-1: Broadcom BCM2045B (BDC-2.1)
    type: USB
    driver: btusb
      v: 0.8
    bus ID: 1-1.4:6
    chip ID: 0a5c:217f
    class ID: fe01
    serial: <filter>
    Report: 
      ID: hci1
      state: up running
      bt-v: 2.0
      lmp-v: 3.0
        sub-v: 4203
      hci-v: 3.0
        rev: 2ec
      address: <filter>
      Info: 
        acl-mtu: 1021:8
        sco-mtu: 64:1
        link-policy: rswitch hold sniff park
        link-mode: slave accept
  Device-2: Broadcom BCM20702A0 Bluetooth 4.0
    type: USB
    driver: btusb
      v: 0.8
    bus ID: 2-1.1:4
    chip ID: 0a5c:21e8
    class ID: fe01
    serial: <filter>
    Report: 
      ID: hci0
      state: up running
      bt-v: 2.1
      lmp-v: 4.0
        sub-v: 220e
      hci-v: 4.0
        rev: 1000
      address: <filter>
      Info: 
        acl-mtu: 1021:8
        sco-mtu: 64:1
        link-policy: rswitch sniff
        link-mode: slave accept
2 Likes
2

what is about this one?

aur/inxi-perl-git r3749.05e55f8b-1 (+1 0.01) 
    Pinxi, development branch of inxi, a full featured CLI system information tool
3

pinxi -U is easy to run, and to me, using a git pull is kind of overkill to install a file. But the inxi-perl-git works fine too I believe since all it does is grab the file from github, exactly like pinxi -U does, or wget smxi.org/pinxi, they all get the data from the same place. I guess the package will put the files in the right places too? /usr/bin and wherever it puts the pinxi.1 man page? Don’t know if it gz’s up the man as pinxi/inxi does. Each to their own, I like to keep it simple. The advantage to using the package I think though I don’t know how it works exactly is that in theory if will always keep your pinxii version up to date? I assume that’s what it does.

For myself, I prefer one command that always works on all systems, since I install pinxi a lot, and always update it using -U, so I don’t have to think about it or wonder which system I’m on to update to current. But that’s just me, other people prefer using things like AUR.