Sponsored Content
Special Forums Hardware Linux not booting when keyboard is unplugged Post 302922382 by agentrnge on Friday 24th of October 2014 09:49:01 AM
Old 10-24-2014
There is also typically a BIOS option for "Press F1 to continue on error" Something like that. Disable that function, so that its not sitting there waiting for you to hilariously press F1 (on the non-existant keybaord) to ack the error that there is no keyboard. That's what I've always done on any headless servers.
This User Gave Thanks to agentrnge For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Linux 7.2, Keyboard Problem!

I recently tried to install Linux 7.2 on my home PC (Compaq), and it did not recognise my keyboard. I could not proceed with the installation as I could not type anything. I installed 6.2 and it worked fine???????????. I was wondering if anybody has encountered this problem (very frustrating). ... (4 Replies)
Discussion started by: camerja1
4 Replies

2. UNIX for Dummies Questions & Answers

booting up in Redhat Linux 7.1

When I created the redhat installation, I configured it to boot directly into GNOME, but now I want it to boot into the shell login screen. How can I change that? Thanks. (1 Reply)
Discussion started by: dangral
1 Replies

3. Solaris

Dual booting Linux and Solaris

Ok, so I'm a bit new to the whole Unix/Linux thing, but I'm no stranger to dual booting... However, the problem that I am having is that I am unable to create a dual boot with Unix (in this case I's using Sun Solaris 9.0 x86) and for linux either RH 9 or Mandrake 9.1, but for the purpose of just... (1 Reply)
Discussion started by: AndroidI6
1 Replies

4. Linux

Booting Linux from an USB stick

I got Puppy linux and installed it on a usb stick. In the BIOS i selected to boot from USB-FDD but it goes to my HD and ignores the USB stick, What going on ?? (2 Replies)
Discussion started by: perleo
2 Replies

5. UNIX for Dummies Questions & Answers

A Big Problem in LINUX Booting

i have some problem in linux booting will u please help me the problem is i was using federo core 1 on my system everything was fine i made one entry in /etc/fstab file for accessing E drive of WINDOWS XP in that i had given file system as VFAT after rebooting system it was not... (1 Reply)
Discussion started by: great_indian
1 Replies

6. Linux

Changing default keyboard layout in Linux

Hi I have Fedora linux with XFCE desktop. I want to use Indic lanquage in that. I have installed unicode devnagri fonts. But I am not able to change my default keyboard layout. How can I change default keyboard layout in XFCE or through command line. Thanks NeeleshG (0 Replies)
Discussion started by: neel.gurjar
0 Replies

7. Ubuntu

Problem while booting linux

Hi all, We are using linux Redhat 9. While booting the server, it says /proc not mounted and it says "Segmentation fault" and doesn't continue with booting. Basically, it started while we inserted a pen drive and removed it without mounting and un mounting it. After removing the pen drive &... (1 Reply)
Discussion started by: mjdarm
1 Replies

8. Filesystems, Disks and Memory

Problem booting a linux (RAID5)

Hello, we have a problem with our system, a machine with a RAID5: - We can boot the system from CD only, if we try to boot from hard-disk the GRUB seems to be "freezed". What is the difference, why we can boot from CD if something is wrong? - Allways we retreive an error like: "raid array is... (6 Replies)
Discussion started by: aristegui
6 Replies

9. Debian

Linux booting options

Here is my question, a few years back I was sitting in an airplane and saw the movie display for all the passengers in the back of all the seats boot up. You could see the all too familiar boot-up-scrolling text that we are all used to with Linux. But probably only a few other folks on the plane... (2 Replies)
Discussion started by: caleb8
2 Replies
xpaaccess(3)							SAORD Documentation						      xpaaccess(3)

NAME
XPAAccess - return XPA access points matching template (XPA 2.1 and above) SYNOPSIS
#include <xpa.h> int XPAAccess(XPA xpa, char *template, char *paramlist, char *mode, char **names, char **messages, int n); DESCRIPTION
The XPAAccess routine returns the public access points that match the specified second argument template and have the specified access type. A template of the form "class1:name1" is sent to the XPA name server, which returns a list of at most n matching XPA servers. A connection is established with each of these servers and the paramlist string is passed to the server as the data transfer request is initiated. If an XPA struct is passed to the call, then the persistent connections are updated as described above. Otherwise, temporary connections are made to the servers (which will be closed when the call completes). The XPAAccess() routine retrieves names from at most n XPA servers that match the specified template and that were checked for access using the specified mode. The return string contains both the class:name and ip:port. If a given server returned an error or the server call- back sends a message back to the client, then the message will be stored in the associated element of the messages array. NB: if speci- fied, the name and messages arrays must be of size n or greater. The returned message string will be of the form: XPA$ERROR error-message (class:name ip:port) Note that names of matching registered access points are always returned but may not be valid; it is not sufficient to assume that the returned number of access points is the number of valid access points. Rather, it is essential to check the messages array for error mes- sages. Any string in the messages array is an error message and indicated that the associated access point is not available. For example, assume that a server registers a number of access points but delays entering its event loop. If a call to XPAAccess() is made before the event loop is entered, the call will timeout (after waiting for the long timeout period) and return an error of the form: XPA$ERROR: timeout waiting for server authentication (XPA:xpa1) The error means that the XPA access point has been registered but is not yet available (because events are not being processed). When the server finally enters its event loop, subsequent calls to XPAAccess() will return successfully. NB: This routine only works with XPA servers built with XPA 2.1.x and later. Servers with older versions of XPA will return the error mes- sage: XPA$ERROR invalid xpa command in initialization string If you get this error message, then the old server actually is ready for access, since it got to the point of fielding the query! The xpaaccess program, for example, ignores this message in order to work properly with older servers. The third argument for XPAAccess() is the type of access and can be any combination of: type explanation ------ ----------- g xpaget calls can be made on this access point s xpaset calls can be made on this access point i xpainfo calls can be made on this access point The mode string argument is of the form: "key1=value1,key2=value2,..." The following keywords are recognized: key value default explanation ------ -------- -------- ----------- ack true/false true if false, don't wait for ack from server (after callback completes) The ack keyword is not very useful, since the server completes the callback in order to return the data anyway. It is here for completion (and perhaps for future usefulness). SEE ALSO
See xpa(7) for a list of XPA help pages version 2.1.14 June 7, 2012 xpaaccess(3)
All times are GMT -4. The time now is 06:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy