Have you tried running is as root?
You might need to look at the permissions to your keyboard
Have you tried running is as root?
You also need to ensure that your AUR package rules files for UDEV has been correctly installed where it should (on my debian box: /etc/udev/rules.d/). This file is named:
Code: Select all
udevadm control --reload-rules
So considering the case first of all I'm impressed how close this is to the original. Colors are spot on. Structure of paint is very close, only slightly different but not in a bad way. Btw your F62 is even heavier than the original! All in all this is more than I ever wished for. Considering the mold line.. hmm, the inside doesn't matter, and the outside artifact is only on a small area and visible only in certain light/angle... but I guess the fix would be the paint? If only the paint or first layer would fill the line, it would be invisible.
What about the 2nd ("the early bird"?) round - the cases are already in production and will not be fixed?
Good to know. I think I will be there for the second round.Ellipse wrote: ↑11 Feb 2020, 22:54Thanks TheLagMaker for your detailed review and notes on the xwhatsit Linux configuration.
I have asked the factory to look into the issue of the lines on some of the cases.
webwit is correct that the molds were designed so that the F62 and F77 molds could be shared. The molds used in this project cost more than a luxury car (!) so we have to save on costs where possible.
I hope they can remove this line for the final round in the secondary/finishing operations before powdercoating.
Thank you for clarifying it. I thought I had hunted down everything "brand-new related" on your site, but obviously missed on this. I am in the process of writing an even more longer review in a french speaking forum. I will take this into account, and link to the photo.Regarding the beige color, having examined and restored dozens of original Model F keyboards over the years I have found that different runs of Model F keyboards have slightly different beige colors (including the early powdercoated plastic F122 cases). The beige color I approved is close to one of my original F77 keyboards (as shown in the home page of the project web site with the caption "can you guess which one is the original and which is the reproduction?").
I fully second that !I would say that the off-white/beige finish is my favorite of all the Model F color options!
I have that directory but no such file, so that may be the problem.
/etc/udev/rules.d/ is the standard in Debian, this may not be the case in other distros. I have the PKGBUILD file of the AUR under my nose. Have a look in /usr/lib/udev/rules.d/ : you should find it there. Then reload udev with the command I suggested you previously. If you still cannot access your device, try copyingdaphnis wrote: ↑13 Feb 2020, 17:00I have that directory but no such file, so that may be the problem.
Thanks! And that smaller space corresponds to the Small - Pre 7/2013 space bar from Unicomp?
Yeah I did, fully seated in the tabs but that key hit ever so slightly. I actually solved it by stuffing some notebook paper into the tabs which gave the key clearance, while also getting rid of the spacebar rattle. Now it feels great, even though one could call it a bodge fix. It's probably just a slight issue with tolerances with my unit.Ellipse wrote: ↑27 Feb 2020, 06:17Mattr did you install the space bar inside the space bar tabs? Or is it resting on top? Sometimes by mistake the space bar does not "catch" inside one or both of the metal tabs and it is difficult to see after the keys have been installed.
The space bar wire should not be in contact with any key. I have found that sometimes the wire needs small bending adjustments for some keyboards to optimize performance - this can change the ease and sound of pressing the space bar. Too much change can cause it to become stuck though.
correct space bar.jpg
tentator wrote: ↑07 Feb 2020, 11:25relax my friend, usually it's a communication problem, you were focussing on latest trunk of the firmware, but I anyway can tell you that the documentation is having a broken link towards the utility:
https://github.com/dmaone/CommonSense/b ... r/releases
and even when checking here:
I still see 188.8.131.52.
So maybe you have to update a couple of things or you can point me towards a link of where the version 184.108.40.206 is and maybe we sort it out?
Also unclear to me: what would a different version of the utility do in the context of the macro? define it better.. so that I should remove the macro and recreate it again with an updated utility?