Sponsored Content
Top Forums UNIX for Dummies Questions & Answers USB port is disabled using BIOS, I want to enable it Post 302308207 by tarunicon on Friday 17th of April 2009 11:11:14 AM
Old 04-17-2009
hi gydave .
.well i couldnt figure out did u forget the password or was it disabled by the administrator ...well in case if u did forget it ..first switch off the computer and remove all power cables, your computer shouldnt be connected to any power source in any which way ..u will need a screw driver to open ur cpu cabinet and in there u will see a CMOS battery ....something like a big button cell (flat,circular,mettalic) ...it might be mounted horizontally or it might be mounted vertically depending on the motherboard ...u can remove the battery by a simple flick..the battery would come out easily or it might be fastened by some hinges .....remove the CMOS battery for about 120 seconds and place it back again the way it was put in .....restart the comp. try entering the bios ...the bios will give a warning stating all cmos settings not found ....u need to set the bios settings to default configuration settings ...system will now boot without bios password ....(P.S. DO THIS IF AND ONLY IF U KNOW YOUR WAY AROUND MOTHERBOARDS AND CPU CABINETS)
there is another solution around this ..there are several bios password cracking softwares ....but since these manipulate the bios i would advice "extreme caution" while using any software ....
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to enable a disabled Unix account on HP-UX

I am very new to Unix. We have a Unix user account that was disabled due to multiple tries with an invalid password. How to enable the account? (1 Reply)
Discussion started by: kajap
1 Replies

2. Solaris

disabled telnet now need port 23 or port 22

we disabled telnet on solaris 9 via previous a thread. We use CMS (call management system) supervisor which used port 23 (telnet). We cannot use telnet via local directive and it was shut down as stated when we shut down telnet in the inetd file. I cannot now log into the CMS box since port 23 is... (3 Replies)
Discussion started by: panzerkw
3 Replies

3. Solaris

network on solaris 10, through usb port...(urgent)

hi all, I have been trying to setup network on solaris10 from a long time but am unable to do so.. I tried it with the ethernet card i have(dfe -520tx) but since i was not able to find drivers for that particular device, i thought of using the usb mode to run network.. However am not able... (0 Replies)
Discussion started by: wrapster
0 Replies

4. UNIX for Advanced & Expert Users

how to watch the usb port

I want to watch the USB ports. If any device is connected to the USB port I want to take the name of the device and I want to log the device name. how to watch all the USB ports. How to find the device is connected in which usb port. (1 Reply)
Discussion started by: ungalnanban
1 Replies

5. Solaris

How to enable hba port of a two port hba card

Hi, i have a two port hba card in solaris 10 system one of which is disabled. How to enable and configure the other port. ---------- Post updated at 08:17 AM ---------- Previous update was at 03:40 AM ---------- please help :( (7 Replies)
Discussion started by: rishiraaz
7 Replies

6. Solaris

How to enable Serial port on ILOM, when Network Port is enabled in parallel

Hi Everyone, In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies

7. HP-UX

Enable ftp port

Hi Experts, Need your help in enabling the ftp port in HP-UX box. Is there any command/config file that needs to be changed? Also is it possible to open it only for few selected IPs only? (9 Replies)
Discussion started by: sai_2507
9 Replies

8. UNIX for Dummies Questions & Answers

Restarting/Resetting a USB Port?

Hello All, So I have been running into an issue with a USB Modem where if someone ends their dialin connection abruptly from the other side the modem gets stuck and I found that the only way to fix it is to either unplug the USB Modem and plug it back in, or just reboot. I'd rather not reboot... (5 Replies)
Discussion started by: mrm5102
5 Replies

9. Solaris

Cabling and adapters to communicate to service processor serial port from Windows PC with USB port.

Hello, I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build. The first part is what confuses me -the cabling. I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies

10. Shell Programming and Scripting

USB port events linstening

Hi everybody! :) I am a complete newbie. :D Is it possible to write a script (shell or python) to listen to usb port event and to notify me every time an usb storage key is plugged or ejected? I want it to echo the device to mount (eg. /dev/sdb). I wrote an udev rule wich runs a script after... (1 Reply)
Discussion started by: manuhexadec
1 Replies
APMD(8) 																   APMD(8)

NAME
apmd - Advanced Power Management (APM) daemon SYNOPSIS
apmd [ -TVWciqv ] [ -P program ] [ -T seconds ] [ -c seconds ] [ -p percent ] [ -v level ] [ -w percent ] DESCRIPTION
apmd is an monitoring daemon for the Advanced Power Management (APM) subsystem. The APM subsystem consists of power-management hardware, firmware usually referred to as the APM BIOS and a driver in the operating system kernel. The daemon can execute a program (usually a shell script) when events are reported by the APM subsystem, and will log, via syslogd(8), certain changes in power status. When the available battery power becomes very low it can alert the user. When the APM subsystem notifies the daemon of a pending suspend or standby request, apmd will run a proxy program, log the event, sync(2) data to the disk and then tell the APM subsystem to continue its operation. Preparations for power management events are made mainly by the proxy program specified using the -P option. The proxy program is invoked with one or two arguments: start Invoked when the daemon starts. stop Invoked when the daemon stops. standby ( system | user ) Invoked when the APM subsystem reports that standby has been initiated. The second parameter indicates whether firmware ("system") or software ("user") was the originator of the event. The "standby" mode conserves power but leaves the machine able to respond almost immediately to user activity. Most laptops can't stay in standby mode on battery power for more than a few hours or a day. Normally, nothing special needs to be done to prepare for "standing by". suspend ( system | user ) Invoked when the APM subsystem reports that suspension has been initiated. The second parameter indicates whether firmware ("sys- tem") or software ("user") was the originator of the event. The "suspend" mode aggressively conserves power. Usually this involves shutting off power to all devices except the CPU core and memory, which are put into a very low power mode. Most laptops can stay suspended, using battery power alone, for several days. ("Hibernation" is a kind of super-suspend, where all that state is written to disk and the machine uses no power. Hibernation is treated like suspension by the APM subsystem.) Before suspending, PCMCIA devices may need to be disabled using cardctl(8), and some modular device drivers may need to be unloaded if they have not been designed to support power management. resume ( suspend | standby | critical ) Invoked when the APM subsystem reports that computer has resumed normal operation. The second parameter indicates the kind of event from which the system is resuming. (A "critical" suspend is a suspension that the APM subsystem performs in an emergency. Some kernels do not pass this event to user space. If apmd receives the event, it acknowledges the event and exits immediately without logging or running the proxy program.) When resuming, PCMCIA devices may need to be re-enabled using cardctl(8), and some modular drivers may need to be reloaded. Note that in the case of a critical suspend, the system state may not have been completely saved. change power Invoked when the APM subsystem reports a change in power status, such as a switch from mains to battery power. change battery Invoked when the APM subsystem reports that the charge of one or more batteries is low. A few minutes of battery power may remain. change capability Invoked when the APM subsystem reports some change in power management capabilities. It may have been caused by operation of a set- up utility, or by the installation or removal of devices. apmd emits various messages, most of which are self-explanatory. Battery status log entries contain three fields, separated by commas. The first field indicates how full the battery is as a percentage of its capacity. The second field indicates whether the battery is charging, not charging, or discharging. When possible, apmd adds in parentheses its estimate of the rate of charging or discharging. The third field indicates how much time the battery can or could be used to power the computer. This information is provided by the APM sub- system. When possible, apmd adds in parentheses its own estimate of the battery life (if discharging) or of the time required to charge the battery fully (if charging). OPTIONS
-P program, --proxy program Specifies the proxy program to execute when events are received. See above for information about the arguments supplied to this program. -T [seconds] , --proxy-timeout [seconds] Sets a time-out for the proxy. Without this option (or with this option and a negative argument) apmd waits indefinitely for the proxy to finish. If the proxy enters an infinite loop or wait then the machine may appear to have crashed. If this option is given a positive integer argument then apmd will wait only that many seconds for the proxy to finish, after which it will log a warning, kill the proxy, and continue processing the event. The default is 30 seconds. -V, --version Prints the version of the apmd program. -W, --wall In addition to logging low battery status (as determined either by the -w level or by the firmware) using syslog(2), apmd will, given this option, also use wall(1) to alert all users. This is most useful if syslogd(8) is not set up to write ALERT messages to all users. If both methods are used, more warnings will be made during the critical time period. -c [seconds] , --check [seconds] Controls how many seconds to wait for an event. Without this option (or with this option and a negative argument) apmd waits indef- initely for an event. If this option is given a positive integer argument then apmd will wait only that many seconds before check- ing the battery level and possibly sending out a warning, calling the proxy or making an entry in the log. The default is 30 sec- onds. -i, --ignore-bios-battery-low Causes apmd to ignore a LOW BATTERY signal sent by the APM subsystem. Some firmware signals a low battery at the wrong time. Note that LOW BATTERY events may still be generated by apmd itself based on the warning level. -p percent, --percentage percent Controls how often the battery status is logged. A new line is printed each time the battery content changes by percent_change if logging is enabled. The default is 5. Use a value greater than 100 to disable periodic logging of the battery level. -q, --quiet-bios-battery-low Causes apmd not to generate a warning when a LOW BATTERY signal is received from the APM subsystem. The firmware on some machines produces an audible warning when power is about to be used up, so an extra warning may not be needed. -v [level] , --verbose [level] The daemon can generate messages of varying degrees of unimportance. Each message is assigned one of the priority levels defined for the syslogd(8) subsystem, ranging from 0 (EMERG, least unimportant) to 7 (DEBUG, most unimportant). This option sets the threshold level above which messages are suppressed. Without an argument it increments the threshold by 1, thus making apmd more verbose. The default is 5 (NOTICE). -w percent, --warn percent When the battery is not being charged and the battery content falls below the specified percent of capacity, and no such event has yet occurred in the current discharge cycle, apmd will log a warning at the ALERT log level to syslog(2) and generate a LOW BATTERY event. If the -W or --wall option was given, the daemon will also use wall(1) to alert all users of impending doom. The default warning level is 10. Use a negative value to disable this feature. -h, --help Causes apmd to print a brief command summary and exit. BUGS
This daemon supports all APM events described in the APM BIOS specification version 1.2; however it fails to support some of the advanced features of APM 1.2, such as reporting the conditions of multiple batteries. (Multiple batteries are currently treated as if they were just one large one.) Estimates of charge and discharge rates and times can be very inaccurate. There is no interaction yet with ACPI support as found in newer PC hardware. FILES
/dev/apm_bios Device through which apmd communicates with the Linux APM driver. /proc/apm APM driver status information /etc/apmd_proxy Proxy program that is run if none is specified. /etc/apm/apmd_proxy Proxy program that is run if none is specified. (Debian) AUTHOR
This program was written by Rik Faith (faith@cs.unc.edu) and may be freely distributed under the terms of the GNU General Public License. There is ABSOLUTELY NO WARRANTY for this program. The current maintainer is Avery Pennarun (apenwarr@worldvisions.ca). SEE ALSO
apm(1), xapm(1), cardctl(8), syslogd(8). January 2004 APMD(8)
All times are GMT -4. The time now is 06:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy