[...]
> Exactly the same. Did you do anything different from using
> securyt/bioapi, securiy/bsp_upektfmess and security/pam_bsdbioapi
> and creating birdb.conf?
>
No, I didn't. It works out of the box.
--
Maxim Konovalov
___
freebsd-hackers@freebsd.or
Maxim Konovalov wrote:
On Tue, 26 Jun 2007, 15:40-0300, Patrick Tracanelli wrote:
Maxim Konovalov wrote:
On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote:
Hello all,
I have used the mentioned devices on FreeBSD 5.4 in the past, and
they worked just fine, but now I get problems with
On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote:
> Hello all,
>
> I have used the mentioned devices on FreeBSD 5.4 in the past, and
> they worked just fine, but now I get problems with the same device,
> on top of 6.2-STABLE and also 7.0-CURRENT.
>
[...]
Just for the record: the above m
On Tue, 26 Jun 2007, 15:40-0300, Patrick Tracanelli wrote:
> Maxim Konovalov wrote:
> > On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote:
> >
> > > Hello all,
> > >
> > > I have used the mentioned devices on FreeBSD 5.4 in the past, and
> > > they worked just fine, but now I get problems
Maxim Konovalov wrote:
On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote:
Hello all,
I have used the mentioned devices on FreeBSD 5.4 in the past, and
they worked just fine, but now I get problems with the same device,
on top of 6.2-STABLE and also 7.0-CURRENT.
[...]
Just for the re
Patrick Tracanelli wrote:
Fredrik Lindberg wrote:
This is _exactly_ the same device as you have been using in the past
with libtfmessbsp.so ?
No, not the same hardware, but same model/chipset.
Because if you try to use it with an unsupported device you'll get
the "unable to attach" message.
First of all, can you turn on more debugging in your "bbdm"?
# bbdm -b "{5550454b-2054-464d-2f45-535320425350}" -m filedb -c eksffa ;
echo $?
usb_set_debug: Setting debugging level to 3 (on)
usb_os_find_busses: Found /dev/usb0
usb_os_find_busses: Found /dev/usb1
usb_os_find_busses: Found /de
Fredrik Lindberg wrote:
Patrick Tracanelli wrote:
All threads purged from ugen1.1
All threads purged from ugen1.2
All threads purged from ugen1.3
Harmless, as far as I know.
What is this about "threads purged"? Also, the port want
libintl.so.6 while 6.2-STABLE has libintl.so.8. I have t
Patrick Tracanelli wrote:
All threads purged from ugen1.1
All threads purged from ugen1.2
All threads purged from ugen1.3
Harmless, as far as I know.
What is this about "threads purged"? Also, the port want libintl.so.6
while 6.2-STABLE has libintl.so.8. I have tried 1) linking .8 to .6
On Friday 22 June 2007 22:42, Patrick Tracanelli wrote:
> Hello all,
>
> I have used the mentioned devices on FreeBSD 5.4 in the past, and they
> worked just fine, but now I get problems with the same device, on top of
> 6.2-STABLE and also 7.0-CURRENT.
>
> From `usbdevs -v`, I get:
>
> Controller
First, you cross-posted to way too many lists, ports@ would probably
have been the most appropriate as this has nothing to do with FreeBSD
itself.
Believed it to be related to recent system changes.
All threads purged from ugen1.1
All threads purged from ugen1.2
All threads purged from ugen
Patrick Tracanelli wrote:
Hello all,
First, you cross-posted to way too many lists, ports@ would probably
have been the most appropriate as this has nothing to do with FreeBSD
itself.
All threads purged from ugen1.1
All threads purged from ugen1.2
All threads purged from ugen1.3
Harmless,
Hello all,
I have used the mentioned devices on FreeBSD 5.4 in the past, and they
worked just fine, but now I get problems with the same device, on top of
6.2-STABLE and also 7.0-CURRENT.
From `usbdevs -v`, I get:
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hu
13 matches
Mail list logo
