Yes, I need to get the code MFC'd anyway, sorry, I just am constantly
fighting fires lately it seems :(
I'll try to get on it.
Jack
On Mon, Feb 22, 2010 at 11:46 AM, Mike Tancsa wrote:
>
> Hi Jack,
>Any chance on MFC'ing this version of the em driver ? I have another
> MB that does not
On Mon, 22 Feb 2010, Renato Botelho wrote:
I've already had this problem in the past and seems it's back now.
I use a Sun Type 7 USB keyboard. When my box is booting, and
FreeBSD menu shows up, I cannot press any key to go for a
single boot for example.
ugen1.1: at usbus1, cfg=0 md=HOST spd=F
Hi Jack,
Any chance on MFC'ing this version of the em driver ? I have
another MB that does not work with RELENG_8, only HEAD. Its an Intel
branded server motherboard with two onboard NICs. S3420GPC. One of
the em nics shows up on RELENG_8, but not both.
em1 shows up on RELENG_8, but
On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
But nothing at all when it hasn't initialised properly.
Hi,
If you get no "ums_intr_callback()" printouts at all in the failing case, and
you are running 9-current, I guess that your KWM switch has some special
requirements on the USB programmin
Hi Chris,
Instead of re-plugging the mouse, you can run:
usbconfig -u X -a Y reset
To manually re-enumerate the USB device at ugenX.Y.
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsu
On Monday 22 February 2010 18:45:04 Chris Hedley wrote:
> On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
> > On Monday 22 February 2010 17:52:25 Chris Hedley wrote:
> >> On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
> >>> Hi,
> >>>
> >>> What is printed to dmesg when you enable debugging?
> >>>
On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
On Monday 22 February 2010 17:52:25 Chris Hedley wrote:
On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
Hi,
What is printed to dmesg when you enable debugging?
sysctl hw.usb.ums.debug=15
Is the attached information okay? I tried it twice, fi
On Monday 22 February 2010 17:52:25 Chris Hedley wrote:
> On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
> > Hi,
> >
> > What is printed to dmesg when you enable debugging?
> >
> > sysctl hw.usb.ums.debug=15
>
> Is the attached information okay? I tried it twice, first after a switch
> using the
On 07/10/2009 07:38, John Marshall wrote:
access with gssapi auth from a client succeeded.
Perhaps George Mamalakis could test the _spnego case?
Guys,
I am terribly sorry to tell you that I just now saw this
conversation(!?!! 4 months later !!!). This is due to the fact that at
that time I w
On Mon, 22 Feb 2010, Hans Petter Selasky wrote:
Hi,
What is printed to dmesg when you enable debugging?
sysctl hw.usb.ums.debug=15
Is the attached information okay? I tried it twice, first after a switch
using the KVM (where the mouse didn't work) and second when unplugging the
receiver a
I've already had this problem in the past and seems it's back now.
I use a Sun Type 7 USB keyboard. When my box is booting, and
FreeBSD menu shows up, I cannot press any key to go for a
single boot for example.
ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.1: at usbus0, cfg=0
On Monday 22 February 2010 14:41:18 Chris Hedley wrote:
> I wasn't sure whether this question was better asked on this list or the
> freebsd-usb one; but since I'm already subscribed here, I figured it was a
> good place to start.
>
> I'm having a lot of problems getting the ums (USB mouse) driver
I wasn't sure whether this question was better asked on this list or the
freebsd-usb one; but since I'm already subscribed here, I figured it was a
good place to start.
I'm having a lot of problems getting the ums (USB mouse) driver to
initialise the mouse correctly. The only time it'll do so
13 matches
Mail list logo
