Keyboard not working with GuixSD on Apple Macbook Air 6,2

Jessica Tallon wrote on 26 Apr 2015 10:22

Keyboard not working on laptop with guixSD

Recipients:(address . bug-guix@gnu.org)

Message-ID:87a8xv8fol.fsf@megworld.co.uk

Hey,
I have tried GuixSD (the x86_64-linux image) on my Macbook Air 6,2laptop. I unfortunately am not able to install it as my keyboard doesnot function. I know i doesn't require propriatory blobs for it to workas 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 Idon't think it's a driver issue. As I am not able to install it due tothis bug so I have not been able to test it with X as I don't believethe GuixSD image on the GNU Distribution page provides the X server.
Thanks,Jessica.

Ludovic Courtès wrote on 1 May 2015 22:26

Recipients:(name . Jessica Tallon)(address . jessica@megworld.co.uk)(address . 20433@debbugs.gnu.org)

Message-ID:87d22k9h7z.fsf@gnu.org

Hi,
Jessica Tallon <jessica@megworld.co.uk> skribis:

Toggle quote (5 lines)

> 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?

Toggle quote (7 lines)

> 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 theinstallation image’s prompt, to see if the Apple keyboard shows up?
If the Apple keyboard is actually seen as a USB keyboard, then I wouldexpect it to use the same USB HID driver that the external keyboard usesno?
Thanks for the report,Ludo’.

Ludovic Courtès wrote on 10 Jun 2015 10:12

control message for bug #20433

Recipients:(address . control@debbugs.gnu.org)

Message-ID:87oakohth7.fsf@gnu.org

tags 20433 moreinfo

Jessica Tallon wrote on 3 Dec 2015 00:57

Re: bug#20433: Keyboard not working on laptop with guixSD

Recipients:(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 20433@debbugs.gnu.org)

Message-ID:m2zixsqukt.fsf@tsyesika.se

Hey,
Sorry for my very late reply to this, It somehow slipped past me at the time.
Ludovic Courtès writes:

Toggle quote (10 lines)> Hi,>> Jessica Tallon <jessica@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 stilldoesn't work

Toggle quote (1 lines)

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

Yes.

Toggle quote (11 lines)>>> 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 hubBus 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 TechnologyBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Toggle quote (3 lines)

> 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.

Toggle quote (4 lines)

>> Thanks for the report,> Ludo’.

Thansk,Jessica.

Jessica Tallon wrote on 3 Dec 2015 14:05

bug#20433: Keyboard not working on laptop with guixSD

Recipients:(address . ludo@gnu.org)(address . bug-guix@gnu.org)

Message-ID:m24mfzheda.fsf@tsyesika.se

Hey,
I just checked in Trisquel as I was curious what driver was being usedthere and `lsusb -t` shows the driver to be usbhid module. I confirmedthis by unloading the module and verifying the keyboard stoppedworking.
I did then boot the guix 0.9 installation image again and lsmod doesshow that the module is infact loaded in guix but yet the keyboard doesnot work. I'm not sure what could be causing it.
Thanks,Jessica.

Ludovic Courtès wrote on 9 Dec 2015 15:02

Recipients:(name . Jessica Tallon)(address . tsyesika@tsyesika.se)(address . bug-guix@gnu.org)

Message-ID:877fknsot2.fsf@gnu.org

Hi!
Jessica Tallon <tsyesika@tsyesika.se> skribis:

Toggle quote (9 lines)

> 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 ifthere’s something else we’re missing?
Thanks in advance,Ludo’.

Jessica Tallon wrote on 13 Jan 2016 14:14

Recipients:(name . Ludovic Courtès)(address . ludo@gnu.org)

Message-ID:m2bn8pzkne.fsf@tsyesika.se

Ludovic Courtès writes:

Toggle quote (19 lines)> Hi!>> Jessica Tallon <tsyesika@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 andthe lsmod in the guix 0.9 image where it doesn't. I did try and lookwhat additional modules trisquel have to see if any stood out but noneof them did.
Let me know if there is any other debug info that would help.

Attachment: guix-lsmod-macbook

Attachment: trisquel-lsmod-macbook

Ludovic Courtès wrote on 13 Jan 2016 15:24

Recipients:(name . Jessica Tallon)(address . tsyesika@tsyesika.se)(address . 20433@debbugs.gnu.org)

Message-ID:874meh4kx3.fsf@gnu.org

Jessica Tallon <tsyesika@tsyesika.se> skribis:

Toggle quote (5 lines)

> 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:

Toggle snippet (37 lines)$ for i in $(cat trisquel-lsmod-macbook | cut -f1 -d ' ') ; do if ! grep -q $i guix-lsmod-macbook ; then echo $i ; fi ; donejoydevghash_clmulni_inteldm_multipathscsi_dhsnd_page_allocsnd_seq_midisnd_seq_midi_eventsnd_rawmidisnd_seqsnd_seq_deviceparport_pcppdevparportsquashfsoverlayfsnls_utf8isofsnls_iso8859_1raid10raid456async_raid6_recovasync_memcpyasync_pqasync_xorasync_txxorraid6_pqraid1raid0multipathlineardm_mirrordm_region_hashdm_log

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

Toggle quote (2 lines)

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

Does “dmesg” on Trisquel show anything about the Apple keyboard? Isthere anything similar on GuixSD?
Thanks for your help!
Ludo’.

Jessica Tallon wrote on 14 Jan 2016 10:32

Recipients:(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 20433@debbugs.gnu.org)

Message-ID:87egdkbj5k.fsf@tsyesika.se

Ludovic Courtès writes:

Toggle quote (10 lines)> Jessica Tallon <tsyesika@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 Ithink both see them on boot (though the trackpad is also listed as"Apple Keyboard / Trackpad" so it doesn't make it clear).

Toggle quote (3 lines)

> Thanks for your help!>> Ludo’.

Attachment: dmesg-guix-macbook

Attachment: dmesg-trisquel-macbook

--Thanks,Jessica

Ludovic Courtès wrote on 14 Jan 2016 10:55

Recipients:(name . Jessica Tallon)(address . tsyesika@tsyesika.se)(address . 20433@debbugs.gnu.org)

Message-ID:87pox4v62m.fsf@gnu.org

Jessica Tallon <tsyesika@tsyesika.se> skribis:

Toggle quote (15 lines)> Ludovic Courtès writes:>> Jessica Tallon <tsyesika@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 getin touch with someone more familiar with Apple hardware.
Thanks,Ludo’.

Ludovic Courtès wrote on 14 Jan 2016 10:56

retitle

Recipients:(address . request@debbugs.gnu.org)

Message-ID:87lh7sv60z.fsf@gnu.org

retitle 20433 Keyboard not working with GuixSD on Apple Macbook Air 6,2thanks

Jessica Tallon wrote on 14 Jan 2016 15:03

Re: bug#20433: Keyboard not working on laptop with guixSD

Recipients:(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 20433@debbugs.gnu.org)

Message-ID:87twmgjm1j.fsf@tsyesika.se

Ludovic Courtès writes:

Toggle quote (6 lines)

> 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 knowthere isn't Xorg on the 0.9.0 image. It does work perfectly in Grub.

Toggle quote (3 lines)

> 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 anythingelse, I'll keep trying.
--Thanks,Jessica.

Ricardo Wurmus wrote on 15 Jan 2016 21:50

Recipients:(name . Jessica Tallon)(address . tsyesika@tsyesika.se)

Message-ID:87egdi36ug.fsf@elephly.net

While comparing the output of dmesg I found it interesting that onGuixSD 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 tothe kernel boot parameters:
modprobe.blacklist=usbkbd
I’m just guessing here, but this seems the most probably cause to me.
~~ Ricardo

Ludovic Courtès wrote on 16 Jan 2016 14:54

Recipients:(name . Ricardo Wurmus)(address . rekado@elephly.net)

Message-ID:87ziw5bpfd.fsf@gnu.org

Ricardo Wurmus <rekado@elephly.net> skribis:

Toggle quote (7 lines)

> 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 loginto 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’.

Ludovic Courtès wrote on 16 Jan 2016 14:56

Recipients:(name . Ricardo Wurmus)(address . rekado@elephly.net)

Message-ID:87vb6tbpca.fsf@gnu.org

Ricardo Wurmus <rekado@elephly.net> skribis:

Toggle quote (6 lines)

> 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’.

Ricardo Wurmus wrote on 16 Jan 2016 15:43

Recipients:(name . Ludovic Courtès)(address . ludo@gnu.org)

Message-ID:87bn8l37pu.fsf@elephly.net

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

Toggle quote (11 lines)> Ricardo Wurmus <rekado@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 faras I understand “usbhid” should be sufficient.
~~ Ricardo

Ludovic Courtès wrote on 17 Jan 2016 22:15

Recipients:(name . Ricardo Wurmus)(address . rekado@elephly.net)

Message-ID:87lh7n52mo.fsf@gnu.org

Ricardo Wurmus <rekado@elephly.net> skribis:

Toggle quote (16 lines)> Ludovic Courtès <ludo@gnu.org> writes:>>> Ricardo Wurmus <rekado@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 theculprit?
Thanks,Ludo’.

Ludovic Courtès wrote on 20 Jan 2016 23:47

Re: guixsd on macbook

Recipients:(address . rennes@openmailbox.org)

Message-ID:87wpr3uav0.fsf@gnu.org

Hi,
rennes@openmailbox.org skribis:

Toggle quote (11 lines)> 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 keyboardappears to be a USB device.
Thanks,Ludo’.

rennes wrote on 21 Jan 2016 22:39

Recipients:(address . ludo@gnu.org)

Message-ID:725c99689cfdf2370c2ec12b2d48b436@openmailbox.org

On 2016-01-20 16:47, ludo@gnu.org wrote:

Toggle quote (27 lines)> Hi,> > rennes@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

Alex Kost wrote on 22 Jan 2016 00:13

Recipients:(address . rennes@openmailbox.org)

Message-ID:87bn8e1q74.fsf@gmail.com

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

Toggle quote (50 lines)> On 2016-01-20 16:47, ludo@gnu.org wrote:>> Hi,>>>> rennes@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 needto have a recent guix code.
-- Alex

rennes wrote on 29 Jan 2016 03:32

Recipients:(name . Alex Kost)(address . alezost@gmail.com)

Message-ID:9f5c7fc59b529a4497b0b7c76152b9d9@openmailbox.org

hi,
On 2016-01-22 00:13, Alex Kost wrote:

Toggle quote (58 lines)> rennes@openmailbox.org (2016-01-22 00:39 +0300) wrote:> >> On 2016-01-20 16:47, ludo@gnu.org wrote:>>> Hi,>>> >>> rennes@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.

Alex Kost wrote on 29 Jan 2016 09:46

Recipients:(address . rennes@openmailbox.org)

Message-ID:87bn84ydqk.fsf@gmail.com

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

Toggle quote (64 lines)> hi,>> On 2016-01-22 00:13, Alex Kost wrote:>> rennes@openmailbox.org (2016-01-22 00:39 +0300) wrote:>>>>> On 2016-01-20 16:47, ludo@gnu.org wrote:>>>> Hi,>>>>>>>> rennes@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

rennes wrote on 29 Jan 2016 18:22

Recipients:(name . Alex Kost)(address . alezost@gmail.com)

Message-ID:0937a749008ec37bdc867c29abc5ba81@openmailbox.org

On 2016-01-29 09:46, Alex Kost wrote:

Toggle quote (75 lines)> rennes@openmailbox.org (2016-01-29 05:32 +0300) wrote:> >> hi,>> >> On 2016-01-22 00:13, Alex Kost wrote:>>> rennes@openmailbox.org (2016-01-22 00:39 +0300) wrote:>>> >>>> On 2016-01-20 16:47, ludo@gnu.org wrote:>>>>> Hi,>>>>> >>>>> rennes@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!.

Ludovic Courtès wrote on 5 Feb 2016 14:36

Re: bug#20433: Keyboard not working on laptop with guixSD

Recipients:(name . Ricardo Wurmus)(address . rekado@elephly.net)

Message-ID:8737t7jn3x.fsf@gnu.org

ludo@gnu.org (Ludovic Courtès) skribis:

Toggle quote (24 lines)> Ricardo Wurmus <rekado@elephly.net> skribis:>>> Ludovic Courtès <ludo@gnu.org> writes:>>>>> Ricardo Wurmus <rekado@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 athttp://lists.gnu.org/archive/html/help-guix/2016-01/msg00118.html andfixed in cc023e3. The fix will be in 0.9.1.
Closing the bug.
Thanks,Ludo’.

Ludovic Courtès wrote on 5 Feb 2016 14:36

control message for bug #20433

Recipients:(address . control@debbugs.gnu.org)

Message-ID:871t8rjn3g.fsf@gnu.org

close 20433 0.9.1

Your comment

This issue is archived.

To comment on this conversation send email to 20433@debbugs.gnu.org

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date