Forum Replies Created
-
AuthorPosts
-
theguyonthecouch
ParticipantI had the same problem. I changed the keyboard layout to US using the config script and it still didn’t work. The trick is to run apt-get update and upgrade afterwards (when online, of course)…reboot…then your key map will be as configured (at least, that is what works for me every time).
theguyonthecouch
ParticipantHmm, I’d be very interested to see some PCAP captured with Wireshark so as to establish what the device is doing to cause the alert(s). I may power mine on later and capture some traffic to look for anomalous activity…
theguyonthecouch
ParticipantHmm, found out that if I did this step at the same time that I resized the partition and rebooted…it worked. Never seen that before…shrug. :)
theguyonthecouch
ParticipantHmm okay thanks. I tried again and am getting the same results (keymap isn’t being changed). I chose several different keyboard combos…wonder what I could be doing wrong? I haven’t had this issue in prior versions (using the same generic USB keyboard).
theguyonthecouch
Participant[quote=92775]Drugs are bad, mmmmkay?[/quote]
Thanks for your contribution.
theguyonthecouch
Participant[quote=92767]I ran into the English (UK) keyboard bit myself earlier tonight. I was able to fix it with raspi-config. Did you run it as superuser?[/quote]
Yes I ran it with sudo. Chose US UTF-8, I believe…which did you use? Also, are you using the new v3.0 version? Thanks!
theguyonthecouch
ParticipantAre you saving your configs? That was my issue: https://www.petrockblock.com/forums/topic/c64vice-joystick-config-help/
Also, I’ve found it helps to config J1 and J2 and keep them on at all times…theguyonthecouch
ParticipantFound the answer to my question and adding it here in case it helps anyone. It seems that you have to add the directory “/home/pi/.vice”. It doesn’t exist when VICE tries to write to it. Just add that directory and change the permissions appropriately. There is another thread talking about this a few versions back, but it was marked as fixed. I guess it was not fixed for version 2.6. :)
-
AuthorPosts