General :: Enter Some Keyboard Keys At Startup And Assuming That Won't Work?
Apr 19, 2011
this may not be the right place to ask this, but my sister has a macbook and the keyboard does not want to work. i have looked online and i see that the main cause of this problem is in Leopard (correct me if im wrong). So i was wondering if perhaps using linux would solve this problem or if the problem is more hardware related than os related.
Also, how would i go about booting into a linux cd? since u need to enter some keyboard keys at startup and assuming that won't work, is there another way?
I got Sun Type 5 Unix keyboard which uses mindin-8 connector, attached to a PC through a special adapter which converts it to USB. The keyboard's distinctive features are Control key in the middle row (swapped with Caps Lock which makes it a Unix layout - much more comfortable for the pinky) plus a whole bunch of extra Sun keys, including such useful ones as "Copy", "Paste", and volume control. (Sun Type 5 keyboard has very good feeling to its keys, much better than Type 7 one).Those extra keys work as expected with this adapter in Gnome on OpenIndiana (OpenSolaris previously), but aren't supported out of the box on Debian. Looking around I didn't find any good up to date tutorial how to enable them on Debian or any other Linux. Did anyone try to do it?
Neither Ubuntu's Unity or KDE respond to the function keys on a regular Apple USB keyboard. I can plug in a non-Apple keyboard and they work just fine. What needs to be changed or configure so that F1 and company on the Apple keyboard work as on other keyboards?
When I use the down arrow on my new keyboard it also does and enter key as well. When I use the left and right arrow keys and hold them it doesn't keep going. It just clicks once and I have to pressing it over and over again. Any one know the correct settings to setup my keyboard? It's a Logitech Illuminated Keyboard.
I'm trying to write a new keyboard layout. I'm testing using Debian Squeeze and Kubuntu 11.04, both with KDE. It is important to solve this issue with a keyboard layout as opposed to playing with xmodmap or scancodes and keycodes because I need to leave other keyboard layouts intact and usable. For the time being the new layout is called Noah, implemented as a variant of US English. If this is done more easily by making whole new layout that is not a variant of another then I am willing to go that route.
First off, I am trying to move the Caps Lock key to the current location of the "B" Key. This is my code (the unshown parts of the files have not been touched):
The problem is that this configuration is also affecting the US English layout. When I press "B" the keyboard gives a B _and_ a Caps Lock! So typing I get output like this: "keybOARD". How do I restrict the B key to being Caps Lock only in the Noah layout?
I am currently using xmodmap for remapping keys like Caps Lock on my keyboard.However, my keyboard has a bunch of keys on the top that are rarely used (Multimedia keyboard with buttons like Internet, Music, Next song, Mute etc)I want to remap these keys to specific commands (Not keys).
For example: Pressing the Internet button should fire up my Firefox (/usr/bin/firefox)(which happens only in Windows for me)Also I need to map a specific button to xkill.
I don't care if this is done in the bios or a kernel module or software. Is there any way at all to do make the 'fn' key act as 'control' and the 'control' key act as 'fn' in linux running on a macbook pro?
PS. You can do this with software in OSX with the application KeyRemap4MacBook.
I'm running Debian (both Sarge and Lenny, on different systems) under Gnome and have a number of thin client workstations that connect to a software application on an AIX server. I'm using gnome-terminal to provide terminal emulation for this software. Unfortunately, the emulation leaves something to be desired, and doesn't catch all of the F keys properly. It seems F1-F4 act as some form of escape key, exiting out of the software back to the command line, when they should be performing different functions in the software. F5 and F6 work as they should in the emulation. Is there a setting I can apply to my gnome-terminal launcher that will make this behave like it I want? The terminal should ideally match the behavior of a Link MC5 terminal (we have some of these old beasts still around, still crunching away), but alas, I don't know how to implement this.
I'm using the Readhat Linux Enterprise 5, and I encountered a problem about captured keyboard need your help. I log in after entering the required username and password using keyboard, but then the keyboard is captured, i.e., I can not enter anything using keyboard. Meanwhile the mouse works well all the time. I encountered this problem when I pressed some keys wrongly two days ago, but unfortunatelly I can not find out these exact keys I pressed.
Succeeded in connecting to internet using my wll phone. I can now connect using 'wvdial' command in root terminal. But I want to connect through terminal. I tried 'sudo wvdial' command. Then I am asked for my password. But I cannot type my password there. When I type, nothing appears on the terminal window. Ofcourse there's no problem with my keyboard.
I want to ssh, scp, git fetch, etc. without a password. I saw the previous questions, and closed ones regarding this issue, but the suggestion seems to be to use ssh keys. However, after setting up ssh keys, I am still asked for my password (it's not asking for my private key password; it's asking for my login password). How am I supposed to set this up so that it only uses my private key for authentication?
I've setup the .ssh/authorized_keys and am able to login with the new "user" using the pub/private key ... I have also added "user" to the sudoers list ... the problem I have now is when I try to execute a sudo command, something simple like:
$ sudo cd /root
it will prompt me for my password, which I enter, but it doesn't work (I am using the private key password I set)Also, ive disabled the users password using
$ passwd -l user
I am trying to harden my system ... the ultimate goal is to use pub/private keys to do logins versus simple password authentication. I've figured out how to set all that up via the authorized_keys file.Additionally I will ultimately prevent server logins through the root account. But before I do that I need sudo to work for a second user (the user which I will be login into the system with all the time).
For this second user I want to prevent regular password logins and force only pub/private key logins, if I don't lock the user via" passwd -l user ... then if i dont use a key, i can still get into the server with a regular password.But more importantly I need to get sudo to work with a pub/private key setup with a user whos had his/her password disabled.
1) I've adjusted /etc/ssh/sshd_config and set PasswordAuthentication no This will prevent ssh password logins (be sure to have a working public/private key setup prior to doing this
2) I've adjusted the sudoers list visudo and added
root ALL=(ALL) ALL dimas ALL=(ALL) NOPASSWD: ALL
3) root is the only user account that will have a password, I am testing with two user accounts "dimas" and "sherry" which do not have a password set (passwords are blank, passwd -d user)
The above essentially prevents everyone from logging into the system with passwords (a public/private key must be setup). Additionally users in the sudoers list have admin abilities. They can also su to different accounts. So basically "dimas" can sudo su sherry, however "dimas can NOT do su sherry. Similarly any user NOT in the sudoers list can NOT do su user or sudo su user.
So, for some reason the right side ENTER, period, semi colon, SHIFT, and UP, Down, Left arrow keys have all stopped working on my laptop. I just set up a dual boot with windows xp, and ubuntu.
I checked under the keys, and cleaned them, and no problem. This wouldn't be that bad of a sutuation, I could just re-map the keys. However, when my computer starts, and I enter Bios > Bootloader, I get stuck.
I can use home/end to move up and down, but no way to select which OS I want. I have to plug in a USB keyboard to get into my OS. I don't want to be carrying around a keyboard, otherwise I wouldn't have a laptop.
So, I either need a different bootloader which can use some other keys, or I need a way to remap the enter key all the way back at the bios, so I can trick it and enter my OS,
Edit: Actually, I'll probably need a new keyboard. Ubuntu is pretty good with battery life, so I could boot into ubuntu, then hibernate. So, I need a good key mapper for Ubuntu
After one of latest update I have problem with meta keys (like shift, ctrl and alt) in KDE. When I press one of this keys, it sometimes stays active after release and deactivates only after I press it again. It's annoying especially while I'm writing some code (php or html) and meta keys randomly stays active after release.
how can i control vlc via the keys above my keyboard(my english sucks and i have no idea what they are called, meta keys? multimedia keys? whatever)only MPlayer responds to them, not vlci opened vlc preferences window and in hotkeys page, i wanted to add the "PLAY KEY" to "PLAY/PAUSE" but it wouldn't even recognize the keys, nothing happens when i press them, but it would recognize something else ,like
I've been fiddling about with vortexbox (the one before 1.4 I think), for a while. This is a music ripping and server rpm setup using Fedora 11 as the base.
As it was on a test machine, decided to try changing the logical volume sizes of LogVol00 and LogVol02 to fit a few more cd's on 02 before getting a new pc (just to see how it works).
Logged on and opened up the graphic version of lvm (using gnome). Then selected the LogVol02 logical volume, select edit, changed name to LogVol02-Storage, saved and logged out. Rebooted vortexbox since then its been unable to start properly (is this a kernel panic?).
Read up a lot on lvm on the net, have access to Fedora 11 disk 1, so logged on. Eventually managed (I thought to) to change LogVol02-Storage to LogVol02 using lvrename.
However, still refuses to boot completely.
The message it gives is as follows (sort of): Welcome to Fedora Press '1' to enter interactive startup
Setting up Logical Volume Management: 3 logical volume(s) in volume group 'VolGroup00' now active
*** An error occurred during file system check. *** Droping you to a shell; the system will reboot when you leave the shell.
Give root password for maintenance (or type Control-D to continue):
Loving vortexbox appart from this. Will it be easier just to reinstall everything? If so, is there a way of listing all the changes I've done so I can reproduce (I'm thinking of just looking at all the commands I ran on the CLI).
Otherwise, is there a way of listing all of the commands I ran in terminal and piping them into a file so I can see what I need to do to rebuild after reinstalling?
I have tried several versions on my netbook and all fail to boot unless i hold down the enter (return) key on the keyboard then it will load slowly i have also tried meego which does the same thing but i want to use UNR 10:10 without having to sit holding the keyboard for 2 minutes.
Toshiba NB200 Windows 7 Installed too UNR 10:10 (have tried 9:10, 10:04 and 10:10)
I found this:Software.openSUSE.orgIt's supposed to make G keys work and make them programmable, but i don't know if it'll work for G11 keyboard...Did anyone manage to get the G11 macros to work in Linux?I'm using openSUSE 11.2. 64 bit.I tried searching in YAST for some drivers or something, but couldn't find anything...
I could not find any way to enable dead keys on my keyboard on Lubuntu 10.04 via gui.I created xorg.conf by using X -configure command and tried to add followings into /etc/X11/xorg.conf but it did not work.
Yesterday, after browsing for a while, my keyboard suddenly started to show different characters than typed. The keys are just typing different letters than pressed. For example, the j displays a 1, the k displays a 2, and so on. This only happens on the x server. On the terminal, before starting the x server, the keyboard works just fine.