02-20-2015
It may be possible, if you compile your USB controllers etc. drivers as modules. Then you could rmmod them and modprobe them to reload.
I know it's difficult to get a listing of a crash from the kernel after it's crashed, but it would be interesting to see it if you could manage a photograph.
Most USB controllers can't do this, I'm not surprised there are bugs or pitfalls. Perhaps there's something that needs to be done first, before you force it off.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello Friends ,
I have been reading some of the Sys Admin notes when i came across a term "Power Cycling"
Can anybody please explain what this means
Thank You (1 Reply)
Discussion started by: DPAI
1 Replies
2. UNIX for Advanced & Expert Users
I have a SCO UNIX 5.0.6. and a computer ATX.
My Question is:
How can i to power off my computer without to push the power button? :confused:
Please help me. :(
Thanks :) (1 Reply)
Discussion started by: vhabalos
1 Replies
3. AIX
I'm looking for a way - from the command line - to tell whether a given AIX system I have is a Power5, Power4 or Power6 machine - it seems like there would be an option to 'uname' but I couldn't find one.
Thanks! (3 Replies)
Discussion started by: thomn8r
3 Replies
4. Solaris
good evening everyone
i am getting this library problem with intel platform architec :confused:
after installing the entire sun-5.10 with a hard configuration intel945chipset core2dual processor & 2GB ram with disk sapace of 40gb.
after install the entire os my machine is rebooting... (1 Reply)
Discussion started by: ravinder singh
1 Replies
5. Shell Programming and Scripting
Hello all,
Working in KSH using Solaris, the default editor is VIM. So, per session, I run a small rc script which calls
export editor=emacs
This works for commands at the prompt. But if I cycle through command history (Using the up arrow) the command line editor defaults to VIM. How can I... (2 Replies)
Discussion started by: eggmatters
2 Replies
6. Shell Programming and Scripting
Hello,
I am experiencing an issue while downloading a few pages using wget. All of them work without a problem except one which is a page that does a tail on the log and as a result is constantly getting updated.
wget here seems to run endlessly and needs to be manually killed. I wanted to... (0 Replies)
Discussion started by: prafulnama
0 Replies
7. UNIX for Dummies Questions & Answers
Is there an easy way to setup a cross-over cable (USB-USB) between a linux box and a windows PC? My 2 machines are next to each other but I really do not want to keep transfering my files using my USB drive.
Thanks! (4 Replies)
Discussion started by: Xterra
4 Replies
8. IP Networking
HI all,
First post on the forum, and my first proper project on the Paspberry Pi, so sorry if this is in the wrong place.
I am trying to turn my Pi in to a 3G/4G Bonding router. I have been researching and trying this for a week or so now. The basic plan is to have up to 6 ZTE MF823 USB... (0 Replies)
Discussion started by: elliottlc
0 Replies
LEARN ABOUT FREEBSD
usbconfig
USBCONFIG(8) BSD System Manager's Manual USBCONFIG(8)
NAME
usbconfig -- configure the USB subsystem
SYNOPSIS
usbconfig [-u unit] [-a addr] [cmds...]
usbconfig [-d [ugen]<unit>.<addr>] [cmds...]
DESCRIPTION
The usbconfig utility is used to configure and dump information about the USB subsystem.
The options are as follows:
-u unit Limit device range to USB devices connected to the given USBUS unit.
-a addr Limit device range to the given USB device index. Should only be used in conjunction with the unit argument.
-d [ugen]<unit>.<addr>
Limit device range to USB devices connected to the given unit and address. The unit and address coordinates may be prefixed by the
lowercased word "ugen".
-h Show help and available commands.
When called without options, usbconfig prints a list of all available USB devices.
EXAMPLES
Show information about the device on USB bus 1 at address 2:
usbconfig -u 1 -a 2 dump_info
Dump HID descriptor for device on USB bus 1 at address 2:
usbconfig -u 1 -a 2 do_request 0x81 0x06 0x2200 0 0x100
Dump string descriptor at index Z for device on USB bus 1 at address 2:
usbconfig -u 1 -a 2 dump_string Z
Dump current configuration descriptor for device on USB bus 1 at address 2:
usbconfig -u 1 -a 2 dump_curr_config_desc
Dump device descriptor for device on USB bus 1 at address 2:
usbconfig -u 1 -a 2 dump_device_desc
Program the device on USB bus 1 at address 2 to suspend, resume, power off, go into power save, or power on:
usbconfig -u 1 -a 2 suspend
usbconfig -u 1 -a 2 resume
usbconfig -u 1 -a 2 power_off
usbconfig -u 1 -a 2 power_save
usbconfig -u 1 -a 2 power_on
Display a list of available quirk names:
usbconfig dump_quirk_names
See usb_quirk(4) for more information on quirks.
SEE ALSO
usb(4), usb_quirk(4)
BSD
January 6, 2010 BSD