10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
I need to update a setting in the BIOS on our SCO Openserver 5.0.7 system and all I can bring up about it says I need to create a dos bootable disk of some sort. The problem is that it doesn't seem like dos is loading up fully. I created the dos bootable thumb drive on a Windows PC using Rufus... (7 Replies)
Discussion started by: hometrics
7 Replies
2. Ubuntu
I have a problem with a brand new Dell laptop. BioLinux was installed on it without making the necessary changes on BIOS. The installation was completed successfully but the BIOS system cant find the OS after rebooting the machine.
I have tried to modify the BIOS setting with no luck this far. I... (7 Replies)
Discussion started by: Xterra
7 Replies
3. Debian
okay,i made a grave mistake in installing the base bare bones install of debian.
here i have edited this from the original.
this morning when i got home from work i did some searching and then just shut the system down via the mechanical off on switch. waited a few minutes and then restarted... (0 Replies)
Discussion started by: cowLips
0 Replies
4. IP Networking
Hello
I am communicating with two devices using my computer over UDP protocol. The application is running fine. When I monitored the UDP traffic using Wireshark software, I found that there were too many Checksum errors.
Please find attached the png file showing this error. I am about to... (0 Replies)
Discussion started by: AustinCann
0 Replies
5. Hardware
Hi friends,
I hope you are doing well. Can you please tell me which part of the motherboard contains the BIOS software, name that exact location. And could please give me the names of the firmwares for atleast 5 archetictures, like sun sparc, ibm power, hp alpha etc.
Looking forward to your... (0 Replies)
Discussion started by: gabam
0 Replies
6. Shell Programming and Scripting
Why I get bad replace when using eval?
$ map0=( "0" "0000" "0")
$ i=0
$ eval echo \${map$i}
0000
$ a=`eval echo \${map$i}` !!!error happens!!!
bash: ${map$i}: bad substitution
How to resolve it ?
Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies
7. SCO
I'm on SCO 5.07. Just installed mini tape. Getting CMOS/GPNV checksum error when I turn on the machine and have to go into bios. I just hit f10 and I continue. When loading SCO and it get to the mini tape I get Warning: SCSI boot options ignored: Bad paremeter count. It's a QIC 80.
When in bios if... (2 Replies)
Discussion started by: Mike Gomes
2 Replies
8. Solaris
Hello,
I'm brand new to Sun/Solaris.
I have a Sun Blade 150, with SunOS 5.8.
I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies
9. Solaris
I am using solaris 10
how to get the bios version?
thanks (4 Replies)
Discussion started by: melanie_pfefer
4 Replies
10. Windows & DOS: Issues & Discussions
Does anyone know a good driver site. If you've heard of driverguide.com or driversearch.com please do not reccomend them because I already know them. I need to know where to get Motherboard drivers for a homemade computer. If there is any info that you need to know feel free to make a reply.
:) (5 Replies)
Discussion started by: computek
5 Replies
SMAPI(4) BSD/i386 Kernel Interfaces Manual SMAPI(4)
NAME
smapi -- System Management Application Program Interface driver
DESCRIPTION
Many IBM Thinkpad laptops utilize a special software interface known as SMAPI (System Management Application Program Interface). This inter-
face controls various aspects of the system including:
o System Interface (the BIOS can store system information such as the system identifier),
o System Configuration (where devices such as the display can be configured),
o Power Management (software can interact with the SMAPI BIOS for Power Management control).
Client software must locate a ``header image'' stored in the F000 segment in the Thinkpad ROM (read-only memory), which resides at the
16-byte boundary. This is considered the ``Entry Point'' for the service.
The ``header image'' stores information like:
o signature,
o SMAPI version (major and minor),
o header image length,
o checksum information (which verifies the image),
o an Information Word (used to identify the BIOS service level),
o Real Mode Entry Point (where clients using the Real/V86 mode for the far-call value),
o and finally a 16-bit/32-bit Protected Mode Entry Point: base code address which specifies the BIOS physical address. The client must
prepare a 64 kilobyte selector for this BIOS).
To invoke the SMAPI BIOS, a far-call must be used on the entry point specified in the header file. All other information should be stored in
the client data area. The client is required to prepare both an input and output parameter in a data area of its own. This area can be
``informed'' by pushing those pointers into its stack before the far-calls.
The SMAPI BIOS uses the stack and data areas with the selector during a BIOS invocation, thus the caller must define the same privilege area
as the BIOS.
The parameter structure will be made up by using the input and output fields prepared by the caller. The input field will specify the func-
tion request to the BIOS. The BIOS will then drop a return value into the output field. These fields are made up of three parts. The first
holds parameters, function numbers, and return codes. The next will contain an offset in hexadecimal. Finally a length field which is com-
prised of Byte, Word, or Double Word.
SEE ALSO
IBM Thinkpad 560/560E Technical Reference, 06J0536 S76H-7587-01.
IBM Thinkpad 560Z Technical Reference, xxxxxxx xxxx-xxxx-xx.
IBM Thinkpad 600 Technical Reference, xxxxxxx xxxx-xxxx-xx.
IBM Thinkpad 760XD/760XL/765D/765L Technical Reference, 06J0537 S30H-2433-02.
IBM Thinkpad 770 Technical Reference, 05L1739 S05L-1739-00.
AUTHORS
The smapi driver was written by Matthew N. Dodd <mdodd@FreeBSD.org>. This manual page was written by Tom Rhodes <trhodes@FreeBSD.org> and
Matthew N. Dodd <mdodd@FreeBSD.org>.
BSD
April 1, 2003 BSD
07-17-2010
