This is a known bug - and has been for a month or so now at least. Partially due to removal of hidd binary from the Bluez-Utils package (obviously was removed to make way for alternative method of pairing using the bluetooth GUI - which is broken). But also i think partially due to the way the Logitech Dinovo dongle/set works.
When the dongle is not initialised as a bluetooth device - ie in bios, boot, install etc it simply emulates a usb keyboard / mouse and the set works (without any fancy features) perfectly - hence why it works in text mode installer. However, as soon as it is initialised as a bluetooth device it forces you to use bluetooth pairing to work - this applies to windows too - i delberatly did not install the windows bluetooth drivers for the dongle as it slowed my system to a crawl, but the keyboard/mouse worked fine.
If it's not going to work using the bluetooth method, i want an easier way of disabling bluetooth support...
This is a known bug - and has been for a month or so now at least. Partially due to removal of hidd binary from the Bluez-Utils package (obviously was removed to make way for alternative method of pairing using the bluetooth GUI - which is broken). But also i think partially due to the way the Logitech Dinovo dongle/set works.
When the dongle is not initialised as a bluetooth device - ie in bios, boot, install etc it simply emulates a usb keyboard / mouse and the set works (without any fancy features) perfectly - hence why it works in text mode installer. However, as soon as it is initialised as a bluetooth device it forces you to use bluetooth pairing to work - this applies to windows too - i delberatly did not install the windows bluetooth drivers for the dongle as it slowed my system to a crawl, but the keyboard/mouse worked fine.
If it's not going to work using the bluetooth method, i want an easier way of disabling bluetooth support...