02-23-2015
USB cycling problem
Thanks for the help,
The kernel doesn't crash, only the USB part does (not detecting new devices that are plugged in).
I thought of using modules as well, but then I have to get the sourcecode, recompile the kernel and on the next RPI upgrade the problem will reappear.
I think it is unavoidable that I will have to reboot each time this happens (which will probably be about once a day)
I always thought the advantage of Linux over windows was that you didn't have to reboot to resolve silly problems like this...
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
reboot
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system
SYNOPSIS
halt [-lnpq] [-k kernel]
reboot [-dlnpq] [-k kernel]
fasthalt [-lnpq] [-k kernel]
fastboot [-dlnpq] [-k kernel]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database.
The options are as follows:
-d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump
device has previously been specified with dumpon(8).
-k kernel
Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive
boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is
interrupted and a valid kernel booted. This may change in the future.
-l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on
whether halt or reboot was called.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
October 11, 2010 BSD