GNU bug report logs - #20433
Keyboard not working with GuixSD on Apple Macbook Air 6,2

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 20433 in the body.
You can then email your comments to 20433 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jessica Tallon <jessica <at> megworld.co.uk>
To: bug-guix <at> gnu.org
Subject: Keyboard not working on laptop with guixSD
Date: Sun, 26 Apr 2015 10:22:20 +0200

Hey,

I have tried GuixSD (the x86_64-linux image) on my Macbook Air 6,2
laptop. I unfortunately am not able to install it as my keyboard does
not function. I know i doesn't require propriatory blobs for it to work
as I have a trisquel live image and it works great on that.

It's an internal USB which shows up in lsusb as:

     Bus 001 Device 008: ID 05ac:828f Apple, Inc.

I have tried plugging in an external USB keyboard which works fine so I
don't think it's a driver issue. As I am not able to install it due to
this bug so I have not been able to test it with X as I don't believe
the GuixSD image on the GNU Distribution page provides the X server.

Thanks,
Jessica.

Message #8 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jessica Tallon <jessica <at> megworld.co.uk>
Cc: 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Fri, 01 May 2015 22:26:56 +0200

Hi,

Jessica Tallon <jessica <at> megworld.co.uk> skribis:

> I have tried GuixSD (the x86_64-linux image) on my Macbook Air 6,2
> laptop. I unfortunately am not able to install it as my keyboard does
> not function. I know i doesn't require propriatory blobs for it to work
> as I have a trisquel live image and it works great on that.

Is it version 0.8.1 of the image?

The keyboard doesn’t work in the installation image itself, right?

> It's an internal USB which shows up in lsusb as:
>
>      Bus 001 Device 008: ID 05ac:828f Apple, Inc.
>
> I have tried plugging in an external USB keyboard which works fine so I
> don't think it's a driver issue.

Could you plug in that USB keyboard and then run ‘lsusb’ at the
installation image’s prompt, to see if the Apple keyboard shows up?

If the Apple keyboard is actually seen as a USB keyboard, then I would
expect it to use the same USB HID driver that the external keyboard uses
no?

Thanks for the report,
Ludo’.

Message #13 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: Jessica Tallon <tsyesika <at> tsyesika.se>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Thu, 03 Dec 2015 00:57:06 +0100

Hey,

Sorry for my very late reply to this, It somehow slipped past me at the time.

Ludovic Courtès writes:
> Hi,
>
> Jessica Tallon <jessica <at> megworld.co.uk> skribis:
>
>> I have tried GuixSD (the x86_64-linux image) on my Macbook Air 6,2
>> laptop. I unfortunately am not able to install it as my keyboard does
>> not function. I know i doesn't require propriatory blobs for it to work
>> as I have a trisquel live image and it works great on that.
>
> Is it version 0.8.1 of the image?
I have tested it today with the 0.9.0 install image, the keyboard still
doesn't work

> The keyboard doesn’t work in the installation image itself, right?
Yes.

>
>> It's an internal USB which shows up in lsusb as:
>>
>>      Bus 001 Device 008: ID 05ac:828f Apple, Inc.
>>
>> I have tried plugging in an external USB keyboard which works fine so I
>> don't think it's a driver issue.
>
> Could you plug in that USB keyboard and then run ‘lsusb’ at the
> installation image’s prompt, to see if the Apple keyboard shows up?
>
The full output of lsusb on the installation image is:

Bus 001 Device 008:  ID 05ac:828f Apple, Inc.
Bus 002 Device 002:  ID 05ac:8406 Apple, Inc.
Bus 002 Device 001:  ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005:  ID 05ac:0291 Apple, Inc.
Bus 001 Device 004:  ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 hub
(part of BCM2046 Bluetooth)
Bus 001 Device 009:  ID 04d9:0169 Holtek Semiconductor, Inc.
Bus 001 Device 003:  ID 0951:1665 Kingson Technology
Bus 001 Device 001:  ID 1d6b:0002 Linux Foundation 2.0 root hub


NB: one of the apple devices will be the trackpad, another probably the
webcam.

> If the Apple keyboard is actually seen as a USB keyboard, then I would
> expect it to use the same USB HID driver that the external keyboard uses
> no?
I suspect so too although I'm not entirely sure.

>
> Thanks for the report,
> Ludo’.

Thansk,
Jessica.

Message #16 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jessica Tallon <tsyesika <at> tsyesika.se>
To: ludo <at> gnu.org
Cc: bug-guix <at> gnu.org
Subject: bug#20433: Keyboard not working on laptop with guixSD
Date: Thu, 03 Dec 2015 14:05:05 +0100

Hey,

I just checked in Trisquel as I was curious what driver was being used
there and `lsusb -t` shows the driver to be usbhid module. I confirmed
this by unloading the module and verifying the keyboard stopped
working.

I did then boot the guix 0.9 installation image again and lsmod does
show that the module is infact loaded in guix but yet the keyboard does
not work. I'm not sure what could be causing it.

Thanks,
Jessica.

Message #19 received at submit <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jessica Tallon <tsyesika <at> tsyesika.se>
Cc: bug-guix <at> gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Wed, 09 Dec 2015 15:02:17 +0100

Hi!

Jessica Tallon <tsyesika <at> tsyesika.se> skribis:

> I just checked in Trisquel as I was curious what driver was being used
> there and `lsusb -t` shows the driver to be usbhid module. I confirmed
> this by unloading the module and verifying the keyboard stopped
> working.
>
> I did then boot the guix 0.9 installation image again and lsmod does
> show that the module is infact loaded in guix but yet the keyboard does
> not work. I'm not sure what could be causing it.

Weird.  Could you compare the two lsmod outputs entirely, to see if
there’s something else we’re missing?

Thanks in advance,
Ludo’.

Message #22 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jessica Tallon <tsyesika <at> tsyesika.se>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Jessica Tallon <tsyesika <at> tsyesika.se>, bug-guix <at> gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Wed, 13 Jan 2016 14:14:29 +0100

[Message part 1 (text/plain, inline)]

Ludovic Courtès writes:
> Hi!
>
> Jessica Tallon <tsyesika <at> tsyesika.se> skribis:
>
>> I just checked in Trisquel as I was curious what driver was being used
>> there and `lsusb -t` shows the driver to be usbhid module. I confirmed
>> this by unloading the module and verifying the keyboard stopped
>> working.
>>
>> I did then boot the guix 0.9 installation image again and lsmod does
>> show that the module is infact loaded in guix but yet the keyboard does
>> not work. I'm not sure what could be causing it.
>
> Weird.  Could you compare the two lsmod outputs entirely, to see if
> there’s something else we’re missing?
>
> Thanks in advance,
> Ludo’.

Sure, I have attached both the lsmod on trisquel where it does work and
the lsmod in the guix 0.9 image where it doesn't. I did try and look
what additional modules trisquel have to see if any stood out but none
of them did.

Let me know if there is any other debug info that would help.

[guix-lsmod-macbook (application/octet-stream, attachment)]

[trisquel-lsmod-macbook (application/octet-stream, attachment)]

Message #25 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jessica Tallon <tsyesika <at> tsyesika.se>
Cc: 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Wed, 13 Jan 2016 15:24:24 +0100

Jessica Tallon <tsyesika <at> tsyesika.se> skribis:

> Sure, I have attached both the lsmod on trisquel where it does work and
> the lsmod in the guix 0.9 image where it doesn't. I did try and look
> what additional modules trisquel have to see if any stood out but none
> of them did.

The list of modules present and Trisquel and missing on GuixSD is:

--8<---------------cut here---------------start------------->8---
$ for i in $(cat trisquel-lsmod-macbook | cut -f1 -d ' ') ; do if ! grep -q $i guix-lsmod-macbook ; then echo $i ; fi ; done
joydev
ghash_clmulni_intel
dm_multipath
scsi_dh
snd_page_alloc
snd_seq_midi
snd_seq_midi_event
snd_rawmidi
snd_seq
snd_seq_device
parport_pc
ppdev
parport
squashfs
overlayfs
nls_utf8
isofs
nls_iso8859_1
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
raid1
raid0
multipath
linear
dm_mirror
dm_region_hash
dm_log
--8<---------------cut here---------------end--------------->8---

However, I don’t see anything related to keyboards or human interface
devices.

> Let me know if there is any other debug info that would help.

Does “dmesg” on Trisquel show anything about the Apple keyboard?  Is
there anything similar on GuixSD?

Thanks for your help!

Ludo’.

Message #28 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: Jessica Tallon <tsyesika <at> tsyesika.se>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Thu, 14 Jan 2016 10:32:55 +0100

[Message part 1 (text/plain, inline)]

Ludovic Courtès writes:
> Jessica Tallon <tsyesika <at> tsyesika.se> skribis:
>
>> Sure, I have attached both the lsmod on trisquel where it does work and
>> the lsmod in the guix 0.9 image where it doesn't. I did try and look
>> what additional modules trisquel have to see if any stood out but none
>> of them did.
>
> Does “dmesg” on Trisquel show anything about the Apple keyboard?  Is
> there anything similar on GuixSD?

Sure, I've attached both dmesgs to this email. I've had a look and I
think both see them on boot (though the trackpad is also listed as
"Apple Keyboard / Trackpad" so it doesn't make it clear).

> Thanks for your help!
>
> Ludo’.

[dmesg-guix-macbook (application/octet-stream, attachment)]

[dmesg-trisquel-macbook (application/octet-stream, attachment)]

[Message part 4 (text/plain, inline)]

--
Thanks,
Jessica

Message #31 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jessica Tallon <tsyesika <at> tsyesika.se>
Cc: 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Thu, 14 Jan 2016 10:55:13 +0100

Jessica Tallon <tsyesika <at> tsyesika.se> skribis:

> Ludovic Courtès writes:
>> Jessica Tallon <tsyesika <at> tsyesika.se> skribis:
>>
>>> Sure, I have attached both the lsmod on trisquel where it does work and
>>> the lsmod in the guix 0.9 image where it doesn't. I did try and look
>>> what additional modules trisquel have to see if any stood out but none
>>> of them did.
>>
>> Does “dmesg” on Trisquel show anything about the Apple keyboard?  Is
>> there anything similar on GuixSD?
>
> Sure, I've attached both dmesgs to this email. I've had a look and I
> think both see them on boot (though the trackpad is also listed as
> "Apple Keyboard / Trackpad" so it doesn't make it clear).

Both appear to detect the keyboard correctly, no noticeable difference.

So you only tested the keyboard at the console, right?

I’m running out of ideas. :-/  It would be nice if we could get
in touch with someone more familiar with Apple hardware.

Thanks,
Ludo’.

Message #36 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: Jessica Tallon <tsyesika <at> tsyesika.se>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Thu, 14 Jan 2016 15:03:20 +0100

Ludovic Courtès writes:
> Ludovic Courtès writes:
>
> Both appear to detect the keyboard correctly, no noticeable difference.
>
> So you only tested the keyboard at the console, right?

That's correct, I only tested them via the console. As far as I know
there isn't Xorg on the 0.9.0 image. It does work perfectly in Grub.

> I’m running out of ideas. :-/  It would be nice if we could get
> in touch with someone more familiar with Apple hardware.

I'm not sure what to do either. Let me know if you think of anything
else, I'll keep trying.

--
Thanks,
Jessica.

Message #39 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Jessica Tallon <tsyesika <at> tsyesika.se>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Fri, 15 Jan 2016 21:50:31 +0100

While comparing the output of dmesg I found it interesting that on
GuixSD the keyboard is identified as “USB HIDBP”:

    input: USB HIDBP Keyboard 05ac:820a as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/input/input5

whereas it is just a regular HID device on Trisquel:

    input: HID 05ac:820a as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/input/input4
    hid-generic 0003:05AC:820A.0003: input,hidraw0: USB HID v1.11 Keyboard [HID 05ac:820a] on usb-0000:00:14.0-3.1/input0

Also note, that on Trisquel this is followed by a “hid-generic” line,
indicating that the generic HID driver is dealing with the keyboard.
There is no such line in the GuixSD log.

As I had no idea what HIDBP means I searched around and found this:

    https://www.kernel.org/doc/menuconfig/drivers-hid-usbhid-Kconfig.html

    USB HIDBP Keyboard (simple Boot) support

    Say Y here only if you are absolutely sure that you don't want
    to use the generic HID driver for your USB keyboard and prefer
    to use the keyboard in its limited Boot Protocol mode instead.

    This is almost certainly not what you want.  This is mostly
    useful for embedded applications or simple keyboards.

    To compile this driver as a module, choose M here: the
    module will be called usbkbd.

    If even remotely unsure, say N.

And:

    USB Human Interface Device (full HID) support

    Say Y here if you want full HID support to connect USB keyboards,
    mice, joysticks, graphic tablets, or any other HID based devices
    to your computer via USB, as well as Uninterruptible Power Supply
    (UPS) and monitor control devices.

    You can't use this driver and the HIDBP (Boot Protocol) keyboard
    and mouse drivers at the same time. More information is available:
    <file:Documentation/input/input.txt>.

    If unsure, say Y.

    To compile this driver as a module, choose M here: the
    module will be called usbhid.

So, using HIDBP is probably wrong and might very well be the cause.
Looking at the module names again I searched the logs for “usbkbd” and,
yes, the GuixSD logs contain this line:

    usbcore: registered new interface driver usbkbd

This line is absent in the Trisquel dmesg log.

I’d suggest blacklisting the “usbkbd” kernel module by adding this to
the kernel boot parameters:

    modprobe.blacklist=usbkbd

I’m just guessing here, but this seems the most probably cause to me.

~~ Ricardo

Message #42 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Jessica Tallon <tsyesika <at> tsyesika.se>, 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Sat, 16 Jan 2016 14:54:14 +0100

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> I’d suggest blacklisting the “usbkbd” kernel module by adding this to
> the kernel boot parameters:
>
>     modprobe.blacklist=usbkbd
>
> I’m just guessing here, but this seems the most probably cause to me.

I realized that this option is honored by kmod’s ‘modprobe’ command,
which we use, but not by our initrd code, and (gnu system linux-initrd)
has “usbkbd” among the modules that it always loads.

Commit 7ba903b changes our code to honor ‘modprobe.blacklist’ as well.

Jessica: To test what Ricardo suggests, you would have to somehow login
to your laptop (over SSH or using a different keyboard) and do:

  sudo guix pull

  ;; Edit configuration.scm to add ‘kernel-arguments’ to the config:
  ;; (operating-system
  ;;    …
  ;;    (kernel-arguments '("modprobe.blacklist=usbkbd")))

  sudo guix system reconfigure /path/to/configuration.scm

HTH!

Ludo’.

Message #45 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Jessica Tallon <tsyesika <at> tsyesika.se>, 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Sat, 16 Jan 2016 14:56:05 +0100

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> So, using HIDBP is probably wrong and might very well be the cause.
> Looking at the module names again I searched the logs for “usbkbd” and,
> yes, the GuixSD logs contain this line:
>
>     usbcore: registered new interface driver usbkbd

Do you think we should remove usbkbd from (gnu system linux-initrd)?
Is there another module we should load instead?

Thanks,
Ludo’.

Message #48 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Jessica Tallon <tsyesika <at> tsyesika.se>, 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Sat, 16 Jan 2016 15:43:57 +0100

Ludovic Courtès <ludo <at> gnu.org> writes:

> Ricardo Wurmus <rekado <at> elephly.net> skribis:
>
>> So, using HIDBP is probably wrong and might very well be the cause.
>> Looking at the module names again I searched the logs for “usbkbd” and,
>> yes, the GuixSD logs contain this line:
>>
>>     usbcore: registered new interface driver usbkbd
>
> Do you think we should remove usbkbd from (gnu system linux-initrd)?
> Is there another module we should load instead?

I don’t know why one would want to use “usbkbd” and thus HIDBP.  As far
as I understand “usbhid” should be sufficient.

~~ Ricardo

Message #51 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Jessica Tallon <tsyesika <at> tsyesika.se>, 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Sun, 17 Jan 2016 22:15:27 +0100

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> Ludovic Courtès <ludo <at> gnu.org> writes:
>
>> Ricardo Wurmus <rekado <at> elephly.net> skribis:
>>
>>> So, using HIDBP is probably wrong and might very well be the cause.
>>> Looking at the module names again I searched the logs for “usbkbd” and,
>>> yes, the GuixSD logs contain this line:
>>>
>>>     usbcore: registered new interface driver usbkbd
>>
>> Do you think we should remove usbkbd from (gnu system linux-initrd)?
>> Is there another module we should load instead?
>
> I don’t know why one would want to use “usbkbd” and thus HIDBP.  As far
> as I understand “usbhid” should be sufficient.

Looking at the description you pasted, I agree with you.
I’ve removed usbkbd loading in commit b153f9f.

Jessica, could you confirm one way or another that usbkbd is the
culprit?

Thanks,
Ludo’.

Message #54 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: rennes <at> openmailbox.org
Cc: help-guix <at> gnu.org, 20433 <at> debbugs.gnu.org
Subject: Re: guixsd on macbook
Date: Wed, 20 Jan 2016 23:47:31 +0100

Hi,

rennes <at> openmailbox.org skribis:

> I've finished installing correctly GuixSD on macbook. There are some
> issue with touchpad.
>
> If anyone has problems with the keyboard when boot guixsd, fix with
> the following commands:
>
> rmmod usbhid
> rmmod usbkbd
>
> or use an external usb keyboard.

Interesting!  We were discussing this at <http://bugs.gnu.org/20433>,
and it seems that only ‘usbkbd’ was at fault.

Could you check if removing ‘usbkbd’ alone is enough?

I would expect ‘usbhid’ to be required since the internal keyboard
appears to be a USB device.

Thanks,
Ludo’.

Message #57 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: rennes <at> openmailbox.org
To: ludo <at> gnu.org
Cc: help-guix <at> gnu.org, 20433 <at> debbugs.gnu.org
Subject: Re: guixsd on macbook
Date: Thu, 21 Jan 2016 15:39:10 -0600

On 2016-01-20 16:47, ludo <at> gnu.org wrote:
> Hi,
> 
> rennes <at> openmailbox.org skribis:
> 
>> I've finished installing correctly GuixSD on macbook. There are some
>> issue with touchpad.
>> 
>> If anyone has problems with the keyboard when boot guixsd, fix with
>> the following commands:
>> 
>> rmmod usbhid
>> rmmod usbkbd
>> 
>> or use an external usb keyboard.
> 
> Interesting!  We were discussing this at <http://bugs.gnu.org/20433>,
> and it seems that only ‘usbkbd’ was at fault.
> 
> Could you check if removing ‘usbkbd’ alone is enough?
> 
> I would expect ‘usbhid’ to be required since the internal keyboard
> appears to be a USB device.
> 
> Thanks,
> Ludo’.


Hi Ludo,

is correct, removing 'usbkbd'.

I only use 'rmmod usbhid' to reload the module of the internal keyboard.

i test configuring from the scratch the machine and it´s working:

(operating-system
  (host-name "antelope")
  (timezone "Europe/Paris")
  (locale "en_US.UTF-8")
  (kernel-arguments '("modprobe.blacklist=usbkbd"))
.....


if i reconfigure:

  sudo guix system reconfigure /path/to/configuration.scm

is not working.


regards

Message #60 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: Alex Kost <alezost <at> gmail.com>
To: rennes <at> openmailbox.org
Cc: ludo <at> gnu.org, help-guix <at> gnu.org, 20433 <at> debbugs.gnu.org
Subject: Re: guixsd on macbook
Date: Fri, 22 Jan 2016 02:13:35 +0300

rennes <at> openmailbox.org (2016-01-22 00:39 +0300) wrote:

> On 2016-01-20 16:47, ludo <at> gnu.org wrote:
>> Hi,
>>
>> rennes <at> openmailbox.org skribis:
>>
>>> I've finished installing correctly GuixSD on macbook. There are some
>>> issue with touchpad.
>>>
>>> If anyone has problems with the keyboard when boot guixsd, fix with
>>> the following commands:
>>>
>>> rmmod usbhid
>>> rmmod usbkbd
>>>
>>> or use an external usb keyboard.
>>
>> Interesting!  We were discussing this at <http://bugs.gnu.org/20433>,
>> and it seems that only ‘usbkbd’ was at fault.
>>
>> Could you check if removing ‘usbkbd’ alone is enough?
>>
>> I would expect ‘usbhid’ to be required since the internal keyboard
>> appears to be a USB device.
>>
>> Thanks,
>> Ludo’.
>
>
> Hi Ludo,
>
> is correct, removing 'usbkbd'.
>
> I only use 'rmmod usbhid' to reload the module of the internal keyboard.
>
> i test configuring from the scratch the machine and it´s working:
>
> (operating-system
>   (host-name "antelope")
>   (timezone "Europe/Paris")
>   (locale "en_US.UTF-8")
>   (kernel-arguments '("modprobe.blacklist=usbkbd"))
> .....
>
>
> if i reconfigure:
>
>   sudo guix system reconfigure /path/to/configuration.scm
>
> is not working.

Did you do "guix pull" before reconfiguring?  Support for
"modprobe.blacklist" arguments was added several days ago, so you need
to have a recent guix code.

-- 
Alex

Message #63 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: rennes <at> openmailbox.org
To: Alex Kost <alezost <at> gmail.com>
Cc: ludo <at> gnu.org, help-guix <at> gnu.org, 20433 <at> debbugs.gnu.org
Subject: Re: guixsd on macbook
Date: Fri, 29 Jan 2016 03:32:30 +0100

hi,

On 2016-01-22 00:13, Alex Kost wrote:
> rennes <at> openmailbox.org (2016-01-22 00:39 +0300) wrote:
> 
>> On 2016-01-20 16:47, ludo <at> gnu.org wrote:
>>> Hi,
>>> 
>>> rennes <at> openmailbox.org skribis:
>>> 
>>>> I've finished installing correctly GuixSD on macbook. There are some
>>>> issue with touchpad.
>>>> 
>>>> If anyone has problems with the keyboard when boot guixsd, fix with
>>>> the following commands:
>>>> 
>>>> rmmod usbhid
>>>> rmmod usbkbd
>>>> 
>>>> or use an external usb keyboard.
>>> 
>>> Interesting!  We were discussing this at <http://bugs.gnu.org/20433>,
>>> and it seems that only ‘usbkbd’ was at fault.
>>> 
>>> Could you check if removing ‘usbkbd’ alone is enough?
>>> 
>>> I would expect ‘usbhid’ to be required since the internal keyboard
>>> appears to be a USB device.
>>> 
>>> Thanks,
>>> Ludo’.
>> 
>> 
>> Hi Ludo,
>> 
>> is correct, removing 'usbkbd'.
>> 
>> I only use 'rmmod usbhid' to reload the module of the internal 
>> keyboard.
>> 
>> i test configuring from the scratch the machine and it´s working:
>> 
>> (operating-system
>>   (host-name "antelope")
>>   (timezone "Europe/Paris")
>>   (locale "en_US.UTF-8")
>>   (kernel-arguments '("modprobe.blacklist=usbkbd"))
>> .....
>> 
>> 
>> if i reconfigure:
>> 
>>   sudo guix system reconfigure /path/to/configuration.scm
>> 
>> is not working.
> 
> Did you do "guix pull" before reconfiguring?  Support for
> "modprobe.blacklist" arguments was added several days ago, so you need
> to have a recent guix code.


apologies for my late reply, i test run "guix pull" before 
reconfiguring, and its don`t working.

For the moment i use the first option, configuring from the scratch.

Thanks in advance.

Message #66 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: Alex Kost <alezost <at> gmail.com>
To: rennes <at> openmailbox.org
Cc: help-guix <at> gnu.org, 20433 <at> debbugs.gnu.org
Subject: Re: guixsd on macbook
Date: Fri, 29 Jan 2016 11:46:43 +0300

rennes <at> openmailbox.org (2016-01-29 05:32 +0300) wrote:

> hi,
>
> On 2016-01-22 00:13, Alex Kost wrote:
>> rennes <at> openmailbox.org (2016-01-22 00:39 +0300) wrote:
>>
>>> On 2016-01-20 16:47, ludo <at> gnu.org wrote:
>>>> Hi,
>>>>
>>>> rennes <at> openmailbox.org skribis:
>>>>
>>>>> I've finished installing correctly GuixSD on macbook. There are some
>>>>> issue with touchpad.
>>>>>
>>>>> If anyone has problems with the keyboard when boot guixsd, fix with
>>>>> the following commands:
>>>>>
>>>>> rmmod usbhid
>>>>> rmmod usbkbd
>>>>>
>>>>> or use an external usb keyboard.
>>>>
>>>> Interesting!  We were discussing this at <http://bugs.gnu.org/20433>,
>>>> and it seems that only ‘usbkbd’ was at fault.
>>>>
>>>> Could you check if removing ‘usbkbd’ alone is enough?
>>>>
>>>> I would expect ‘usbhid’ to be required since the internal keyboard
>>>> appears to be a USB device.
>>>>
>>>> Thanks,
>>>> Ludo’.
>>>
>>>
>>> Hi Ludo,
>>>
>>> is correct, removing 'usbkbd'.
>>>
>>> I only use 'rmmod usbhid' to reload the module of the internal
>>> keyboard.
>>>
>>> i test configuring from the scratch the machine and it´s working:
>>>
>>> (operating-system
>>>   (host-name "antelope")
>>>   (timezone "Europe/Paris")
>>>   (locale "en_US.UTF-8")
>>>   (kernel-arguments '("modprobe.blacklist=usbkbd"))
>>> .....
>>>
>>>
>>> if i reconfigure:
>>>
>>>   sudo guix system reconfigure /path/to/configuration.scm
>>>
>>> is not working.
>>
>> Did you do "guix pull" before reconfiguring?  Support for
>> "modprobe.blacklist" arguments was added several days ago, so you need
>> to have a recent guix code.
>
>
> apologies for my late reply, i test run "guix pull" before
> reconfiguring, and its don`t working.

Since a system is configured from root, you also need to run "guix pull"
as root.  Did you do it, did you just run "guix pull" from your user?

-- 
Alex

Message #69 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: rennes <at> openmailbox.org
To: Alex Kost <alezost <at> gmail.com>
Cc: help-guix <at> gnu.org, 20433 <at> debbugs.gnu.org
Subject: Re: guixsd on macbook
Date: Fri, 29 Jan 2016 18:22:53 +0100

On 2016-01-29 09:46, Alex Kost wrote:
> rennes <at> openmailbox.org (2016-01-29 05:32 +0300) wrote:
> 
>> hi,
>> 
>> On 2016-01-22 00:13, Alex Kost wrote:
>>> rennes <at> openmailbox.org (2016-01-22 00:39 +0300) wrote:
>>> 
>>>> On 2016-01-20 16:47, ludo <at> gnu.org wrote:
>>>>> Hi,
>>>>> 
>>>>> rennes <at> openmailbox.org skribis:
>>>>> 
>>>>>> I've finished installing correctly GuixSD on macbook. There are 
>>>>>> some
>>>>>> issue with touchpad.
>>>>>> 
>>>>>> If anyone has problems with the keyboard when boot guixsd, fix 
>>>>>> with
>>>>>> the following commands:
>>>>>> 
>>>>>> rmmod usbhid
>>>>>> rmmod usbkbd
>>>>>> 
>>>>>> or use an external usb keyboard.
>>>>> 
>>>>> Interesting!  We were discussing this at 
>>>>> <http://bugs.gnu.org/20433>,
>>>>> and it seems that only ‘usbkbd’ was at fault.
>>>>> 
>>>>> Could you check if removing ‘usbkbd’ alone is enough?
>>>>> 
>>>>> I would expect ‘usbhid’ to be required since the internal keyboard
>>>>> appears to be a USB device.
>>>>> 
>>>>> Thanks,
>>>>> Ludo’.
>>>> 
>>>> 
>>>> Hi Ludo,
>>>> 
>>>> is correct, removing 'usbkbd'.
>>>> 
>>>> I only use 'rmmod usbhid' to reload the module of the internal
>>>> keyboard.
>>>> 
>>>> i test configuring from the scratch the machine and it´s working:
>>>> 
>>>> (operating-system
>>>>   (host-name "antelope")
>>>>   (timezone "Europe/Paris")
>>>>   (locale "en_US.UTF-8")
>>>>   (kernel-arguments '("modprobe.blacklist=usbkbd"))
>>>> .....
>>>> 
>>>> 
>>>> if i reconfigure:
>>>> 
>>>>   sudo guix system reconfigure /path/to/configuration.scm
>>>> 
>>>> is not working.
>>> 
>>> Did you do "guix pull" before reconfiguring?  Support for
>>> "modprobe.blacklist" arguments was added several days ago, so you 
>>> need
>>> to have a recent guix code.
>> 
>> 
>> apologies for my late reply, i test run "guix pull" before
>> reconfiguring, and its don`t working.
> 
> Since a system is configured from root, you also need to run "guix 
> pull"
> as root.  Did you do it, did you just run "guix pull" from your user?


Thanks Alex,

now works!.

Message #72 received at 20433 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Jessica Tallon <tsyesika <at> tsyesika.se>, 20433 <at> debbugs.gnu.org
Subject: Re: bug#20433: Keyboard not working on laptop with guixSD
Date: Fri, 05 Feb 2016 14:36:02 +0100

ludo <at> gnu.org (Ludovic Courtès) skribis:

> Ricardo Wurmus <rekado <at> elephly.net> skribis:
>
>> Ludovic Courtès <ludo <at> gnu.org> writes:
>>
>>> Ricardo Wurmus <rekado <at> elephly.net> skribis:
>>>
>>>> So, using HIDBP is probably wrong and might very well be the cause.
>>>> Looking at the module names again I searched the logs for “usbkbd” and,
>>>> yes, the GuixSD logs contain this line:
>>>>
>>>>     usbcore: registered new interface driver usbkbd
>>>
>>> Do you think we should remove usbkbd from (gnu system linux-initrd)?
>>> Is there another module we should load instead?
>>
>> I don’t know why one would want to use “usbkbd” and thus HIDBP.  As far
>> as I understand “usbhid” should be sufficient.
>
> Looking at the description you pasted, I agree with you.
> I’ve removed usbkbd loading in commit b153f9f.
>
> Jessica, could you confirm one way or another that usbkbd is the
> culprit?

That adding ‘hid-apple’ solves the problem was confirmed at
<http://lists.gnu.org/archive/html/help-guix/2016-01/msg00118.html> and
fixed in cc023e3.  The fix will be in 0.9.1.

Closing the bug.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.