On Monday 29 August 2011 14:15:59 Mike Tancsa wrote:
> On 8/27/2011 9:00 AM, Hans Petter Selasky wrote:
> > On Saturday 27 August 2011 14:59:50 Marcin Wisnicki wrote:
> >> On Sat, Aug 27, 2011 at 14:04, Hans Petter Selasky
wrote:
> >>> On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote:
>
On 8/27/2011 9:00 AM, Hans Petter Selasky wrote:
> On Saturday 27 August 2011 14:59:50 Marcin Wisnicki wrote:
>> On Sat, Aug 27, 2011 at 14:04, Hans Petter Selasky wrote:
>>> On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote:
Would it be possible to reinstate ability to power-cycle pa
On Sat, Aug 27, 2011 at 14:04, Hans Petter Selasky wrote:
> On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote:
>> Would it be possible to reinstate ability to power-cycle particular port
>> the way it was ~year ago ?
>
> This is still possible. There is a sysctl to disable this feature:
>
On Saturday 27 August 2011 14:59:50 Marcin Wisnicki wrote:
> On Sat, Aug 27, 2011 at 14:04, Hans Petter Selasky wrote:
> > On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote:
> >> Would it be possible to reinstate ability to power-cycle particular port
> >> the way it was ~year ago ?
> >
>
On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote:
> On Fri, 26 Aug 2011 08:55:52 +0200, Hans Petter Selasky wrote:
> > On Thursday 25 August 2011 21:56:43 Mike Tancsa wrote:
> >> On 8/25/2011 3:40 PM, Hans Petter Selasky wrote:
> >> > After 22nd of July, r223414:
> >> >
> >> > http://svn.
On Fri, 26 Aug 2011 08:55:52 +0200, Hans Petter Selasky wrote:
> On Thursday 25 August 2011 21:56:43 Mike Tancsa wrote:
>> On 8/25/2011 3:40 PM, Hans Petter Selasky wrote:
>> > After 22nd of July, r223414:
>> >
>> > http://svn.freebsd.org/changeset/base/223414
>>
>> That looks to be June 22nd ?
On 8/26/2011 2:55 AM, Hans Petter Selasky wrote:
>>
>> Any other tricks you can think of to reset the device short of
>> installing a HUB at each location ?
>
> No. Upgrading the modem firmware. Talking to the vendor about it.
Understood. I did some more testing with the version of the kernel I
On Thursday 25 August 2011 21:56:43 Mike Tancsa wrote:
> On 8/25/2011 3:40 PM, Hans Petter Selasky wrote:
> > After 22nd of July, r223414:
> >
> > http://svn.freebsd.org/changeset/base/223414
>
> That looks to be June 22nd ? In that case, I have that in my kernel already
>
> http://lists.freebsd
On 8/25/2011 3:40 PM, Hans Petter Selasky wrote:
>
> After 22nd of July, r223414:
>
> http://svn.freebsd.org/changeset/base/223414
That looks to be June 22nd ? In that case, I have that in my kernel already
http://lists.freebsd.org/pipermail/svn-src-stable-8/2011-June/005683.html
Any other tri
On Thursday 25 August 2011 21:40:25 Hans Petter Selasky wrote:
> On Thursday 25 August 2011 21:31:41 Mike Tancsa ppsupport wrote:
> > On 8/25/2011 3:02 PM, Hans Petter Selasky wrote:
> > > On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote:
> > >> I am having periodic problems with the odd u3g d
On Thursday 25 August 2011 21:31:41 Mike Tancsa ppsupport wrote:
> On 8/25/2011 3:02 PM, Hans Petter Selasky wrote:
> > On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote:
> >> I am having periodic problems with the odd u3g device that gets hung.
> >> If I try and reset it, it totally locks up a
On 8/25/2011 3:02 PM, Hans Petter Selasky wrote:
> On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote:
>> I am having periodic problems with the odd u3g device that gets hung.
>> If I try and reset it, it totally locks up and I need to do a reboot of
>> the box the recover. Apart from usbconfig
On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote:
> I am having periodic problems with the odd u3g device that gets hung.
> If I try and reset it, it totally locks up and I need to do a reboot of
> the box the recover. Apart from usbconfig reset are is there anything
> else I can do to recover
I am having periodic problems with the odd u3g device that gets hung.
If I try and reset it, it totally locks up and I need to do a reboot of
the box the recover. Apart from usbconfig reset are is there anything
else I can do to recover from such a situation ?
usbconfig -d 1.3 dump_info
ugen1.3:
Hm, ik DEVICEENUMERATE wasn't in my search. Thanks.
Nick
> On Thursday 25 June 2009 15:24:02 Nick Hibma wrote:
> > HPS,
> >
> > In FBSD7 I committed an ioctl on the ugen.c (some time ago) that
> > allowed for resetting the device. Not a port on the device, but the
> > device itself. This was a f
On Thursday 25 June 2009 15:24:02 Nick Hibma wrote:
> HPS,
>
> In FBSD7 I committed an ioctl on the ugen.c (some time ago) that allowed
> for resetting the device. Not a port on the device, but the device itself.
> This was a function that was unimplemented in libusb1 up to then. For
> example som
HPS,
In FBSD7 I committed an ioctl on the ugen.c (some time ago) that allowed
for resetting the device. Not a port on the device, but the device itself.
This was a function that was unimplemented in libusb1 up to then. For
example some Atmel devices need a reset after you uploaded the firmware
17 matches
Mail list logo
