Bluetooth device not connecting | Fedora 40 |

Hello - first time on Fedora and the forums. I’ve been using Ubuntu for a while but I’m still a linux beginner for the most part.

The problem: I just installed Fedora 40 alongside Windows 10. The only issue I’m having in Fedora is that one specific bluetooth device, a Corsair Katar Wireless Pro mouse, won’t connect via bluetooth - I just get a window saying “The setup of KATAR PRO Wireless has failed.” Same error when I try this on the live ISO used for installation. This mouse does connect successfully on a linux mint ISO as well as on the Windows 10 partition. Other mice and keyboards connect just fine on Fedora, so it seems like it’s just between Fedora and this one mouse.

My rudimentary troubleshooting consisted of:

  • watching journalctl -f - when the connection error shows, in red text this shows up:
    fedora bluetoothd[5814]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error

  • attempting to connect manually via bluetoothctl as per this article - eventually leads to
    [KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: yes,
    ~15 seconds of waiting, then
    [KATAR PRO Wireless]# Failed to pair: org.bluez.Error.AuthenticationFailed

  • checking systemctl status bluetooth. At the bottom, lots of red text;
    Jul 09 18:08:40 fedora bluetoothd[5814]: profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error Jul 09 18:08:40 fedora bluetoothd[5814]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error Jul 09 18:08:50 fedora bluetoothd[5814]: profiles/deviceinfo/dis.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error Jul 09 18:08:50 fedora bluetoothd[5814]: profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely > Jul 09 18:08:50 fedora bluetoothd[5814]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely > Jul 09 18:08:50 fedora bluetoothd[5814]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely > Jul 09 18:08:50 fedora bluetoothd[5814]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely > Jul 09 18:08:50 fedora bluetoothd[5814]: profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error Jul 09 18:08:50 fedora bluetoothd[5814]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error Jul 09 18:10:32 fedora bluetoothd[5814]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error

OS:
Fedora 40 (KDE Plasma 6.1.1)
Kernel 6.9.7-200.fc40.x86_64

Device:
Zenbook UX3402ZA_Q409ZA 1.0 (laptop)
12th Gen Intel i5-1240P (16) @ 4.400GHz
Intel Alder Lake-P GT2 [Iris Xe Graphics]
8GB ram

The internal radio seems to be a “Intel Corp. AX211” according to lsusb, if that helps. Please let me know if I can provide any other info or format things better :slight_smile:

I can only make a couple comments here.
First there have been some issues reported with the AX211 chipset and bluetooth. This may be a factor in your issue and might be related to the inability to configure the device. The report you provided seems that the information the system receives from the mouse may not be in the hid database or not in the expected format so the device cannot be configured and the system gives up on it.

Secondly, I am confused by users who wish to use a bluetooth keyboard or mouse. Since the bluetooth is not active until the OS has already loaded it seems difficult to use those devices either with the bios or early in the boot process. Thus an additional mouse or keyboard seems required under many conditions.

Personally I use both keyboard and trackball that are wireless. I use the logitech unifying receiver so the devices are configured by the dongle and do not rely on bluetooth. In well over ten years I have never had an issue with either mouse or trackball.

If you search the linux hardware database for your mouse you might be able to find some information – either pro or con.

1 Like

Welcome to :fedora:

Here are some things you can try to see what’s happening to the device while you connect it:

Some hardware troubleshooting with dmesg:
dmesg | grep -i bluetooth

Check the logs:
journalctl -u bluetooth -f

We can use bluetoothctl to try to pair it manunally and get other info, but let’s try these first and see what happens.

You can paste the results here in </> preformatted text for us.


This might be a long shot, but try installing:

As it brings support for many corsair devices. Not sure what module Ubuntu/Mint is shipping for it to work, but this might be worth the try

Thanks for the reply - this laptop, as a generic “office”/work laptop, seems to be ripe with plenty of odd/proprietary hardware things. I waited almost a year for the first fix to be created so that the internal speakers would work in Ubuntu haha

Using bluetooth for the mouse frees up my one USB port, which can be handy when I’m carrying minimal stuff with me. For the time being, this is the “one machine” that does everything for me.

Searching the database, the closest match seems to be specifying using the mouse’s USB dongle as opposed to bluetooth. I assume that’s a very different case.

I forgot to include that the USB dongle of this mouse seemed to have died a while ago - though I never saw any change in bluetooth function.

As a laptop it handles the other issues I mentioned with the bluetooth mouse since the built in trackpad handles that.
:+1:

1 Like

dmesg | grep -i bluetooth

Ran this with sudo right after getting the error message; output below.

    5.763523] Bluetooth: Core ver 2.22
[    5.763551] NET: Registered PF_BLUETOOTH protocol family
[    5.763553] Bluetooth: HCI device and connection manager initialized
[    5.763557] Bluetooth: HCI socket layer initialized
[    5.763562] Bluetooth: L2CAP socket layer initialized
[    5.763567] Bluetooth: SCO socket layer initialized
[    5.838638] Bluetooth: hci0: Device revision is 0
[    5.838644] Bluetooth: hci0: Secure boot is enabled
[    5.838646] Bluetooth: hci0: OTP lock is enabled
[    5.838647] Bluetooth: hci0: API lock is enabled
[    5.838648] Bluetooth: hci0: Debug lock is disabled
[    5.838650] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    5.838652] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    5.840670] Bluetooth: hci0: DSM reset method type: 0x00
[    5.897841] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[    5.897861] Bluetooth: hci0: Boot Address: 0x100800
[    5.897863] Bluetooth: hci0: Firmware Version: 46-14.24
[    6.597682] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.597686] Bluetooth: BNEP filters: protocol multicast
[    6.597692] Bluetooth: BNEP socket layer initialized
[    7.380501] Bluetooth: hci0: Waiting for firmware download to complete
[    7.380782] Bluetooth: hci0: Firmware loaded in 1448178 usecs
[    7.380983] Bluetooth: hci0: Waiting for device to boot
[    7.396815] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    7.396822] Bluetooth: hci0: Device booted in 15638 usecs
[    7.398172] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[    7.399846] Bluetooth: hci0: Applying Intel DDC parameters completed
[    7.402760] Bluetooth: hci0: Firmware timestamp 2024.14 buildtype 1 build 81454
[    7.402762] Bluetooth: hci0: Firmware SHA1: 0xdfd62093
[    7.406739] Bluetooth: hci0: Fseq status: Success (0x00)
[    7.406747] Bluetooth: hci0: Fseq executed: 00.00.02.41
[    7.406755] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[    7.490084] Bluetooth: MGMT ver 1.22
[   12.708644] Bluetooth: RFCOMM TTY layer initialized
[   12.708652] Bluetooth: RFCOMM socket layer initialized
[   12.708656] Bluetooth: RFCOMM ver 1.11
[ 1978.200819] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[ 1979.319966] hid-generic 0005:276D:3010.0002: input,hidraw1: BLUETOOTH HID v1.00 Mouse [BT5.1 Mouse] on c4:bd:e5:72:ee:84

journalctl -u bluetooth -f

the message displayed immediately after getting the connection error:

fedora bluetoothd[5814]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error

I would try to do more troubleshooting based off of these results, but even with some googling I don’t quite understand what these mean yet haha

Installing that driver seemed successful but no joy with connecting to bluetooth. Exploring the supported devices, it seems that there’s some recent discussion on the Katar Pro Wireless, but it isn’t actually supported yet anyways.

Run bluetoothctl with more detailed logging:

sudo bluetoothctl -d

-d doesn’t seem to be a valid option. Did you mean something else? I’m on bluetoothctl version 5.76 if it matters at all.

If it helps, below is the output of bluetoothctl while I attempt to pair via GUI, up until the point that it gives me the “setup … failed” error.

Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# [CHG] Controller C4:BD:E5:72:EE:84 Discovering: yes
[bluetooth]# [NEW] Device FC:58:FA:91:13:73 E7
[bluetooth]# [NEW] Device D8:6C:7C:DA:77:42 KATAR PRO Wireless
[bluetooth]# [CHG] Device D8:6C:7C:DA:77:42 RSSI is nil
[bluetooth]# [CHG] Device FC:58:FA:91:13:73 TxPower is nil
[bluetooth]# [CHG] Device FC:58:FA:91:13:73 RSSI is nil
[bluetooth]# [CHG] Controller C4:BD:E5:72:EE:84 Discovering: no
[CHG] Device D8:6C:7C:DA:77:42 Connected: yes
[KATAR PRO Wireless]# [NEW] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000a
        00001801-0000-1000-8000-00805f9b34fb
        Generic Attribute Profile
[KATAR PRO Wireless]# [NEW] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b
        0000180a-0000-1000-8000-00805f9b34fb
        Device Information
[KATAR PRO Wireless]# [NEW] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b/char000c
        00002a29-0000-1000-8000-00805f9b34fb
        Manufacturer Name String
[KATAR PRO Wireless]# [NEW] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b/char000e
        00002a50-0000-1000-8000-00805f9b34fb
        PnP ID
[KATAR PRO Wireless]# [NEW] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010
        0000180f-0000-1000-8000-00805f9b34fb
        Battery Service
[KATAR PRO Wireless]# [NEW] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010/char0011
        00002a19-0000-1000-8000-00805f9b34fb
        Battery Level
[KATAR PRO Wireless]# [NEW] Descriptor (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010/char0011/desc0013
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: yes
[KATAR PRO Wireless]# [DEL] Device FC:58:FA:91:13:73 E7
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: no
[CHG] Device D8:6C:7C:DA:77:42 Connected: no

Or, the output of sudo bluetoothctl devices?

Device FC:58:FA:91:13:73 E7
Device D8:6C:7C:DA:77:42 KATAR PRO Wireless

So… I got it to connect and work properly… once.

I’m still at a complete loss as to what caused it, but I just attempted to pair the Katar mouse as normal via the GUI and it followed through and worked as it should. Then I selected to forget the device and attempting to pair again yielded the original error result. I’ve been unable to get it paired again so far.

Some things I did beforehand, in chronological order;

  • booted to a Kubuntu ISO, in which an attempt to pair the Katar led to a similar failed result; paired a few other random peripherals successfully
  • booted back to Fedora and tried a wired USB mouse (this mouse wasn’t functional on a different Fedora 40 installation+laptop). This mouse worked on the current machine in question.
  • Paired some bluetooth headphones that I hadn’t tried pairing before - successful, audio working
  • Paired the Katar mouse as usual, started working

While it was connected, bluetoothctl was continually showing the below message (repeating every, 30 seconds?). I hadn’t noticed any disconnecting.

[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: no
[CHG] Device D8:6C:7C:DA:77:42 Connected: no
[CHG] Device D8:6C:7C:DA:77:42 Connected: yes
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: yes

Below was the only red line when I checked systemctl status bluetooth;

Jul 11 11:11:48 fedora bluetoothd[997]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters

My bad. It was late. . .

Try to pair it manually :

bluetoothctl

power on
agent on
default-agent
scan on
pair D8:6C:7C:DA:77:42
connect D8:6C:7C:DA:77:42

No problem; results below. I turned on the mouse (in the way that immediately sends it into pairing mode) right after issuing scan on.

Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# Default agent request successful
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller C4:BD:E5:72:EE:84 Discovering: yes
[bluetooth]# [CHG] Device FC:58:FA:91:13:73 RSSI: 0xffffffc3 (-61)
[bluetooth]# [CHG] Device FC:58:FA:91:13:73 TxPower: 0x0004 (4)
[bluetooth]# [NEW] Device D8:6C:7C:DA:77:42 KATAR PRO Wireless
pair D8:6C:7C:DA:77:42C:7C:DA:77:42
Attempting to pair with D8:6C:7C:DA:77:42
[CHG] Device D8:6C:7C:DA:77:42 Connected: yes
[KATAR PRO Wireless]# [NEW] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000a
        00001801-0000-1000-8000-00805f9b34fb
        Generic Attribute Profile
[KATAR PRO Wireless]# [NEW] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b
        0000180a-0000-1000-8000-00805f9b34fb
        Device Information
[KATAR PRO Wireless]# [NEW] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b/char000c
        00002a29-0000-1000-8000-00805f9b34fb
        Manufacturer Name String
[KATAR PRO Wireless]# [NEW] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b/char000e
        00002a50-0000-1000-8000-00805f9b34fb
        PnP ID
[KATAR PRO Wireless]# [NEW] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010
        0000180f-0000-1000-8000-00805f9b34fb
        Battery Service
[KATAR PRO Wireless]# [NEW] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010/char0011
        00002a19-0000-1000-8000-00805f9b34fb
        Battery Level
[KATAR PRO Wireless]# [NEW] Descriptor (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010/char0011/desc0013
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: yes
connect D8:6C:7C:DA:77:42nect D8:6C:7C:DA:77:42
Attempting to connect to D8:6C:7C:DA:77:42
[KATAR PRO Wireless]# Connection successful
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: no
[CHG] Device D8:6C:7C:DA:77:42 Connected: no
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# [DEL] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000a
        00001801-0000-1000-8000-00805f9b34fb
        Generic Attribute Profile
[bluetooth]# [DEL] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b/char000c
        00002a29-0000-1000-8000-00805f9b34fb
        Manufacturer Name String
[bluetooth]# [DEL] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b/char000e
        00002a50-0000-1000-8000-00805f9b34fb
        PnP ID
[bluetooth]# [DEL] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service000b
        0000180a-0000-1000-8000-00805f9b34fb
        Device Information
[bluetooth]# [DEL] Descriptor (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010/char0011/desc0013
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
[bluetooth]# [DEL] Characteristic (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010/char0011
        00002a19-0000-1000-8000-00805f9b34fb
        Battery Level
[bluetooth]# [DEL] Primary Service (Handle 0x0000)
        /org/bluez/hci0/dev_D8_6C_7C_DA_77_42/service0010
        0000180f-0000-1000-8000-00805f9b34fb
        Battery Service
[bluetooth]# [DEL] Device D8:6C:7C:DA:77:42 KATAR PRO Wireless
[bluetooth]# 
[KATAR PRO Wireless]# Connection successful
[KATAR PRO Wireless]# [CHG] Device D8:6C:7C:DA:77:42 ServicesResolved: no
[CHG] Device D8:6C:7C:DA:77:42 Connected: no
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationCanceled

Remove the Device

sudo bluetoothctl
remove D8:6C:7C:DA:77:42

Power Cycle the Bluetooth Adapter

power off
power on

Try Pairing Again


pair D8:6C:7C:DA:77:42

If that does not work:

Ensure you have the latest updates for BlueZ and other related Bluetooth packages.


sudo dnf update bluez bluez-libs bluez-utils

Added ubuntu-transition

Pairing was sadly unsuccessful. The update showed “nothing to do”, as well as “no match” for bluez-utils.

Also tried downgrading bluez from 5.76 to 5.73 with no luck. Will be trying old kernels and possibly other ISOs to see if any patterns show up

1 Like

If it works on another Distro, would be good to update this thread, and maybe we can guage why it works there and not here.

1 Like

Would ISOs be comparable? I haven’t installed any other distros so far, but I’ve tried a few ISOs [kernel, bluetoothctl (=BlueZ?) version];

Successful pairing to the Katar:

  • Ubuntu 22.04.4 [6.5.0-18-generic, 5.64]
  • Mint 21.3 Cinnamon [5.15.0-91-generic, 5.64]

Unsuccessful in pairing:

  • Ubuntu 24.04 [6.8.0-31-generic, 5.72]
  • Kubuntu 24.04 [6.8.0-31-generic, 5.72]
  • I also tried pairing the Katar on a different laptop with Fedora 40 (installed alongside Windows 11); similar failure (kernel 6.9.6-200.fc40 - didn’t get the bluetoothctl version yet, wasn’t actually my laptop)

I (jankily, not really knowing how) installed BlueZ 5.64 and tried a few commands to connect the Katar. Got something new this time, asking to accept pairing;

[bluetooth]# trust D8:6C:7C:DA:77:42
[CHG] Device D8:6C:7C:DA:77:42 Trusted: yes
Changing D8:6C:7C:DA:77:42 trust succeeded
[bluetooth]# connect D8:6C:7C:DA:77:42
Attempting to connect to D8:6C:7C:DA:77:42
[CHG] Device D8:6C:7C:DA:77:42 WakeAllowed: yes
[CHG] Device D8:6C:7C:DA:77:42 Connected: yes
Connection successful
Request authorization
[agent] Accept pairing (yes/no): yes
[KATAR PRO Wireless]# pair D8:6C:7C:DA:77:42
Attempting to pair with D8:6C:7C:DA:77:42
[CHG] Device D8:6C:7C:DA:77:42 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
[CHG] Device D8:6C:7C:DA:77:42 Connected: yes
Request authorization
[agent] Accept pairing (yes/no): yes

however, after sending “yes” multiple times, it seems to be sending me in circles until the mouse shows the LED code that indicates a failed pairing (although bluetoothctl sometimes doesn’t give the authentication failed error). I’m just about out of ideas at this point unfortunately. Maybe I needed to install the older BlueZ in a more “correct” way (it was a near complete guess as to how I got it to work)?

1 Like

I’ll have to dig around, but Maybe worthy to ask on

If they have ideas while I thumb around too. Just link this thread and short description.

1 Like

Extremely meticulous work, would be to post the logs from dmesg --follow from the Distros that worked? maybe they produce something we can guage ?