05-03-2014
Thanks for your suggestions,
Quote:
Originally Posted by
RudiC
When does it get stuck? During the "BIOS" part of the boot, or the linux part?
get stuck on bios status. Ubuntu does not come alive..
Quote:
Originally Posted by
hicksd8
Either:
1. Look in the PC BIOS to see if there's a setting (which may allow the machine to boot without a keyboard)
or
2. Buy another keyboard.
I will check once again bios settings.
All the best
Boris
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
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
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
LEARN ABOUT CENTOS
vpddecode
VPDDECODE(8) System Manager's Manual VPDDECODE(8)
NAME
vpddecode - VPD structure decoder
SYNOPSIS
vpddecode [OPTIONS]
DESCRIPTION
vpddecode prints the "vital product data" information that can be found in almost all IBM and Lenovo computers. Available items are:
o BIOS Build ID
o Box Serial Number
o Motherboard Serial Number
o Machine Type/Model
Some systems have these additional items:
o BIOS Release Date
o Default Flash Image File Name
Note that these additional items are not documented by IBM, so this is guess work, and as such should not be blindly trusted. Feedback
about the accuracy of these labels is welcome.
OPTIONS
-d, --dev-mem FILE
Read memory from device FILE (default: /dev/mem)
-s, --string KEYWORD
Only display the value of the VPD string identified by KEYWORD. KEYWORD must be a keyword from the following list: bios-build-id,
box-serial-number, motherboard-serial-number, machine-type-model, bios-release-date. Each keyword corresponds to an offset and a
length within the VPD record. Not all strings may be defined on all VPD-enabled systems. If KEYWORD is not provided or not valid,
a list of all valid keywords is printed and vpddecode exits with an error. This option cannot be used more than once. Mutually
exclusive with --dump.
-u, --dump
Do not decode the VPD records, dump their contents as hexadecimal instead. Note that this is still a text output, no binary data
will be thrown upon you. ASCII equivalent is displayed when possible. This option is mainly useful for debugging. Mutually exclu-
sive with --string.
-h, --help
Display usage information and exit
-V, --version
Display the version and exit
FILES
/dev/mem
AUTHOR
Jean Delvare
SEE ALSO
biosdecode(8), dmidecode(8), mem(4), ownership(8)
dmidecode February 2007 VPDDECODE(8)