# Cannot use Model01 on mac osx lock screen (continues on 10.14.2)

**URL:** <https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368>\
**Category:** Help and Getting Started\
**Created:** [December 31, 2018, 11:09pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368 "2018-12-31T23:09:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![rosskevin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rosskevin/32/999_2.png) [@rosskevin](https://community.keyboard.io/u/rosskevin)\
**Post date:** [December 31, 2018, 11:09pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/1 "2018-12-31T23:09:00Z")

</div>

I have had this problem on both of my Model01’s since I got them. I cannot use the keyboard to type in my password, so I have to grab my laptop from my stand, disconnect it (it is out of reach) and set it down to type on the laptop keyboard, then reconnect.

Once completed with login - no problems - most of the time.

After the 10.4.2 update, I found that after unlocking with my fingerprint today - twice - the Model01 was non-responsive. I had to reboot both times to get the keyboard to respond.

Is this a known issue? Any workarounds?

---

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [January 1, 2019, 3:41pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/2 "2019-01-01T15:41:59Z")

</div>

Both of these issues should be fixed in the latest factory firmware from git. The firmware version some (most?) Model01s shipped with had an incomplete implementation of the boot report protocol (the protocol OSX expects the keyboard to talk on the lock screen), more recent versions properly support it, and the OSX lock screen along with it.

I would strongly recommend updating your firmware to the latest version. The `Model01-Firmware` repository is a good place to start:

> **[keyboardio/Model01-Firmware](https://github.com/keyboardio/Model01-Firmware)**
>
> The "standard" Keyboardio Model 01 Firmware sketch. - keyboardio/Model01-Firmware

---

<div class="post-metadata">

**Author:** ![rosskevin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rosskevin/32/999_2.png) [@rosskevin](https://community.keyboard.io/u/rosskevin)\
**Post date:** [January 1, 2019, 3:49pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/3 "2019-01-01T15:49:46Z")

</div>

I flashed mine about 1 week ago and the arduino editor had me update libraries. Is there something else I need to do to get my custom layout/libraries using the latest?

---

<div class="post-metadata">

**Author:** ![rosskevin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rosskevin/32/999_2.png) [@rosskevin](https://community.keyboard.io/u/rosskevin)\
**Post date:** [January 1, 2019, 3:50pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/4 "2019-01-01T15:50:31Z")

</div>

Or perhaps I need to rebase mine based on the upstream repo?

---

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [January 1, 2019, 3:51pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/5 "2019-01-01T15:51:25Z")

</div>

What version of the libraries are you using? As in, what’s the version of the board bundle the IDE tells you? (You’ll need the 1.9x-betas)

---

<div class="post-metadata">

**Author:** ![rosskevin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rosskevin/32/999_2.png) [@rosskevin](https://community.keyboard.io/u/rosskevin)\
**Post date:** [January 1, 2019, 3:56pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/6 "2019-01-01T15:56:24Z")

</div>

I’m not sure where to look for that. I have nothing updatable in the library manager and I have the following url in the preferences:

`https://raw.githubusercontent.com/keyboardio/boardsmanager/master/package_keyboardio_index.json`

---

<div class="post-metadata">

**Author:** ![rosskevin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rosskevin/32/999_2.png) [@rosskevin](https://community.keyboard.io/u/rosskevin)\
**Post date:** [January 1, 2019, 4:00pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/7 "2019-01-01T16:00:26Z")

</div>

Perhaps the setup is updated and I need to start over? It looks different but I don’t recall. I set this up initially quite long ago.

---

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [January 1, 2019, 4:01pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/8 "2019-01-01T16:01:24Z")

</div>

That URL is correct. You can see what version you have installed by going “Tools -\> Board -\> Boards manager”, and selecting the “Contributed” type:

 ![Screenshot%20from%202019-01-01%2016-59-26](https://canada1.discourse-cdn.com/flex031/uploads/keyboard/original/2X/0/03e2e178c1eb553bf066b9e6a86f58c730a90c07.png)

---

<div class="post-metadata">

**Author:** ![rosskevin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rosskevin/32/999_2.png) [@rosskevin](https://community.keyboard.io/u/rosskevin)\
**Post date:** [January 1, 2019, 4:05pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/9 "2019-01-01T16:05:48Z")

</div>

I didn’t have a hardware directory…I just cloned it into the arduino home dir. Not sure when that was added but I see it now in the readme.

My current board manager is 1.22.0. I have updated it and will flash again and update this shortly. Thank you for the assistance.

---

<div class="post-metadata">

**Author:** ![rosskevin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rosskevin/32/999_2.png) [@rosskevin](https://community.keyboard.io/u/rosskevin)\
**Post date:** [January 1, 2019, 4:52pm UTC](https://community.keyboard.io/t/cannot-use-model01-on-mac-osx-lock-screen-continues-on-10-14-2/2368/10 "2019-01-01T16:52:30Z")

</div>

I had to start over with a new fork, evidently the code I was using was far outdated.

I’m all setup with a new fork of the `keyboardio/Model01-Firmware` and I cannot get the firmware uploaded. Similar to [Normal flashing won't work, port lost and keyboard crashed](https://community.keyboard.io/t/normal-flashing-wont-work-port-lost-and-keyboard-crashed/1375/15?u=rosskevin), I get no `Prog` light when plugging in, though I can see the keyboard type change in the system preferences.

My old layout is still working (typing on it now), but I cannot connect to port to upload. I have rebooted just to be sure. Unplugging/replugging doesn’t light up `Prog`, but unplugging/press `Prog`/replugging will light it up, but I still get the dreaded error message.

```auto
Arduino: 1.8.5 (Mac OS X), Board: "Keyboardio Model 01"

WARNING: Category 'Debug' in library Kaleidoscope-Hardware-Virtual is not valid. Setting to 'Uncategorized'
Sketch uses 24770 bytes (86%) of program storage space. Maximum is 28672 bytes.
Global variables use 1407 bytes (54%) of dynamic memory, leaving 1153 bytes for local variables. Maximum is 2560 bytes.
Couldn't find a Board on the selected port. Check that you have the correct port selected. If it is correct, try pressing the board's reset button after initiating the upload.

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

```

What am I missing here - clearly the board is plugged in and operating normally with old firmware.
