Re: Logitech unified wireless

2013-10-19 Thread Brad Rogers
On Thu, 17 Oct 2013 17:17:56 +0200 Gareth de Vaux wrote: Hello Gareth, >I do need to redo the pairing on each boot in the OS though. Admittedly, I've only rebooted a couple since installing solaar, but have not had to re-pair my keyboard and mouse with the receiver. -- Regards _ /

Re: Logitech unified wireless

2013-10-18 Thread Catherine Gramze
On Thu, 17 Oct 2013 17:17:56 +0200 Gareth de Vaux wrote: > > I could use the keyboard/mouse in the BIOS from the start fine. > I do need to redo the pairing on each boot in the OS though. > > If anyone's interested: >snip Odd. Once paired using my Mac my mouse and keyboard have remained paired

Re: Logitech unified wireless

2013-10-17 Thread Gareth de Vaux
On Wed 2013-10-16 (13:04), Dan Ritter wrote: > > Ran into this today too (with the logitech mk520 keyboard/mouse), > > seems like you need to unpair/pair the devices on each reboot? > > No, once programmed the pairing ought to continue until > reprogrammed. Keyboards paired this way should be usab

Re: Logitech unified wireless

2013-10-16 Thread Dan Ritter
On Tue, Oct 15, 2013 at 05:18:38PM +0200, Gareth de Vaux wrote: > On Mon 2013-10-14 (07:18), Dan Ritter wrote: > > There's a utility called solaar which can reprogram Logitech > > mice and keyboards to use a plugged-in receiver; it's at > > http://pwr.github.io/Solaar/index.html > > Ran into this

Re: Logitech unified wireless

2013-10-15 Thread Gareth de Vaux
On Mon 2013-10-14 (07:18), Dan Ritter wrote: > There's a utility called solaar which can reprogram Logitech > mice and keyboards to use a plugged-in receiver; it's at > http://pwr.github.io/Solaar/index.html Ran into this today too (with the logitech mk520 keyboard/mouse), seems like you need to u

Re: Logitech unified wireless

2013-10-14 Thread Dan Ritter
On Sun, Oct 13, 2013 at 02:05:17PM -0500, Catherine Gramze wrote: > I ran into a snag getting this set up on my new computer. I found a gem > of info online, telling me I had to use a USB 2 port and not a USB 3 > port, but it still wouldn't work. > > I finally figured out it was a pairing problem,