search for: _starting_

...status=1) > 2015-09-04T11:43:38.827185-04:00 linux-5048 upsdrvctl[1887]: Network UPS Tools - UPS driver controller 2.7.2.6_RTD I'm confused here - the Bash script, and the systemd service unit, are for _shutting down_ the system on power failure, but in the trace you are having a problem _starting_ the driver. > Is it possible the USB bus is going away before that can execute? I havn't tested with openSUSE 13.2 so there may be something in it which prevents the driver from connecting to the UPS. Perhaps with a more detailed trace using the upsdrvctl -D option it may be possible to...

...th the following messages: Junk at the beginning 49443303 Warning, flexibel rate not heavily tested! Ouch ... error while writing audio data: : Broken pipe I have googled for info on these errors - some have reported getting them while _exiting_ Asterisk, but none have claimed to see them while _starting_ Asterisk. Any ideas? Thanks a ton. --sk.

Hello Bob, > I had preferred the shutdown script method because it was a little more > straight-forward, and possibly more portable. This guide is meant to > help people get the UPS up and running, whatever their Linux distro. I > don't know how common the systemd implementation is across various Linux > distros. You will need to support Linux systems with and without

...tus=1) > 2015-09-04T11:43:38.827185-04:00 linux-5048 upsdrvctl[1887]: Network > UPS Tools - UPS driver controller 2.7.2.6_RTD I'm confused here - the Bash script, and the systemd service unit, are for _shutting down_ the system on power failure, but in the trace you are having a problem _starting_ the driver. > Is it possible the USB bus is going away before that can execute? I havn't tested with openSUSE 13.2 so there may be something in it which prevents the driver from connecting to the UPS. Perhaps with a more detailed trace using the upsdrvctl -D option it may be possible to s...

On 03/02/16 16:19, Ady via Syslinux wrote: > > That's not what common users are forced to deal with. Syslinux's binary > files in the wild come from different sources (official upstream > Syslinux, distros' packages, others). > > Since v.6+ (and possibly, even before it) a re-build might show some > inconsistencies between "the same version" of

> Hi, > > > Not being compatible with EFI/GPT is already a problem for the Perl > > variant. > > The relation of both is: > > isohybrid.in/.pl is being left behind. > http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/Makefile > has: > SCRIPT_TARGETS += isohybrid.pl # about to be obsoleted > > isohybrid.c replaces it feature-wise

..., xorriso from SYSLINUX > > - isohybrid.sh from SliTaz, no EFI/GPT support > > - iso2exe.c -> isohybrid.exe from SliTaz, no EFI/GPT support > > ---------------------------------------------------------------- Good _starting_ point for documentation. > > If somebody wants to assess the quality, i would propose to inspect > the resulting ISOs by xorriso >= 1.3.7 > > xorriso -indev image.iso \ > -report_el_torito plain \ > -report_system_area plain > > It knows El...

Hi Gordan, I wanted to let you know that today I decided to have a try for my GTX 680. Gigabite GTX 680 2048 MB GDDR5. I know that this particular card could be hard-moded to GRID K2 so VGA passthrough could work. Following instructions found on http://www.eevblog.com/forum/chat/hacking-nvidia-cards-into-their-professional-counterparts/420/ I just removed two resistors. Here is a screenshot

Hi Gordan, I wanted to let you know that today I decided to have a try for my GTX 680. Gigabite GTX 680 2048 MB GDDR5. I know that this particular card could be hard-moded to GRID K2 so VGA passthrough could work. Following instructions found on http://www.eevblog.com/forum/chat/hacking-nvidia-cards-into-their-professional-counterparts/420/ I just removed two resistors. Here is a screenshot