Re: bluetooth not working in recent current

2016-05-25 Thread Graham Menhennitt 

On 26/05/2016 7:24 AM, Maksim Yevmenkin wrote:



can you also please try to start it manually and see where it stops?
i.e. something like

# sh -x /etc/rc.d/bluetooth start ubt0

Thanks for responding. The output of that command is below. I'll do some
more diagnosis when I get home tonight.

+ /usr/sbin/hccontrol -n ubt0hci reset
+ return 1
so, "reset" command failed :( can you please tell me which exact
broadcom device you have, i.e. vendor id and product id? some broadcom
devices may require firmware download. you said it was working before,
can you please tell if you had to download firmware before? i.e. use
ubtbcmfw ? are you dual booting between freebsd and windows (or
linux)?



dmesg shows:

 ubt0:  on 
usbus6

usbconfig dump_device_desc shows:
 ugen6.2:  at usbus6, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x00e0  
  bDeviceSubClass = 0x0001
  bDeviceProtocol = 0x0001
  bMaxPacketSize0 = 0x0040
  idVendor = 0x0a5c
  idProduct = 0x200a
  bcdDevice = 0x0001
  iManufacturer = 0x0001  
  iProduct = 0x0002  
  iSerialNumber = 0x0003  <2035B001>
  bNumConfigurations = 0x0001


No, I don't dual boot anything. I have never loaded firmware - maybe it 
happened automatically in the past, but I've never used ubtbcmfw explicitly.

Thanks for your help,
Graham

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: bluetooth not working in recent current

2016-05-25 Thread Maksim Yevmenkin 
Graham,

>> can you also please try to start it manually and see where it stops?
>> i.e. something like
>>
>> # sh -x /etc/rc.d/bluetooth start ubt0
>
> Thanks for responding. The output of that command is below. I'll do some
> more diagnosis when I get home tonight.

thanks a lot

[...]

> + /usr/sbin/hccontrol -n ubt0hci reset
> + return 1

so, "reset" command failed :( can you please tell me which exact
broadcom device you have, i.e. vendor id and product id? some broadcom
devices may require firmware download. you said it was working before,
can you please tell if you had to download firmware before? i.e. use
ubtbcmfw ? are you dual booting between freebsd and windows (or
linux)?

thanks!
max
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: bluetooth not working in recent current

2016-05-25 Thread Graham Menhennitt 
On 26/05/2016 01:56 AM, Maksim Yevmenkin wrote:
> Hi Graham
>
> On Tue, May 24, 2016 at 1:31 AM, Graham Menhennitt
>  wrote:
>> I've been running 11-current AMD64 on this machine for about a year. It
>> has a bluetooth dongle that has worked correctly up until a week ago. I
>> updated to the latest source around then, so I presume that's what broke it.
> can you please make sure that /etc/rc.d/bluetooth ran? it is usually
> called from devd(8) in response to ubt(4) device arrival.
>
> can you also please try to start it manually and see where it stops?
> i.e. something like
>
> # sh -x /etc/rc.d/bluetooth start ubt0

Hi Max.

Thanks for responding. The output of that command is below. I'll do some
more diagnosis when I get home tonight.

Thanks,

Graham

# sh -x /etc/rc.d/bluetooth start ubt0
+ . /etc/rc.subr
+ : 32606
+ export RC_PID
+ [ -z '' ]
+ _rc_subr_loaded=YES
+ SYSCTL=/sbin/sysctl
+ SYSCTL_N='/sbin/sysctl -n'
+ SYSCTL_W=/sbin/sysctl
+ PROTECT=/usr/bin/protect
+ ID=/usr/bin/id
+ IDCMD='if [ -x /usr/bin/id ]; then /usr/bin/id -un; fi'
+ PS='/bin/ps -ww'
+ /bin/ps -ww -p 32606 -o 'jid='
+ JID=0
+ _rc_namevarlist='program chroot chdir env flags fib nice user group
groups prepend'
+ _rc_subr_loaded=:
+ name=bluetooth
+ desc='Bluetooth setup script'
+ rcvar=''
+ start_cmd=bluetooth_start
+ stop_cmd=bluetooth_stop
+ required_modules='ng_bluetooth ng_hci ng_l2cap ng_btsocket'
+ load_rc_config bluetooth
+ local _name _rcvar_val _var _defval _v _msg _new _d
+ _name=bluetooth
+ false
+ [ -r /etc/defaults/rc.conf ]
+ debug 'Sourcing /etc/defaults/rc.conf'
+ . /etc/defaults/rc.conf
+ rc_info=NO
+ rc_startmsgs=YES
+ rcshutdown_timeout=90
+ early_late_divider=FILESYSTEMS
+ always_force_depends=NO
+ apm_enable=NO
+ apmd_enable=NO
+ apmd_flags=''
+ ddb_enable=NO
+ ddb_config=/etc/ddb.conf
+ devd_enable=YES
+ devd_flags=''
+ kldxref_enable=NO
+ kldxref_clobber=NO
+ kldxref_module_path=''
+ powerd_enable=NO
+ powerd_flags=''
+ tmpmfs=AUTO
+ tmpsize=20m
+ tmpmfs_flags=-S
+ varmfs=AUTO
+ varsize=32m
+ varmfs_flags=-S
+ populate_var=AUTO
+ cleanvar_enable=YES
+ local_startup=/usr/local/etc/rc.d
+ script_name_sep=' '
+ rc_conf_files='/etc/rc.conf /etc/rc.conf.local'
+ zfs_enable=NO
+ gptboot_enable=YES
+ gbde_autoattach_all=NO
+ gbde_devices=NO
+ gbde_attach_attempts=3
+ gbde_lockdir=/etc
+ geli_devices=''
+ geli_tries=''
+ geli_default_flags=''
+ geli_autodetach=YES
+ root_rw_mount=YES
+ root_hold_delay=30
+ fsck_y_enable=NO
+ fsck_y_flags=''
+ background_fsck=YES
+ background_fsck_delay=60
+ netfs_types='nfs:NFS smbfs:SMB'
+ extra_netfs_types=NO
+ hostname=''
+ hostid_enable=YES
+ hostid_file=/etc/hostid
+ nisdomainname=NO
+ dhclient_program=/sbin/dhclient
+ dhclient_flags=''
+ background_dhclient=NO
+ synchronous_dhclient=NO
+ defaultroute_delay=30
+ defaultroute_carrier_delay=5
+ netif_enable=YES
+ netif_ipexpand_max=2048
+ wpa_supplicant_program=/usr/sbin/wpa_supplicant
+ wpa_supplicant_flags=-s
+ wpa_supplicant_conf_file=/etc/wpa_supplicant.conf
+ firewall_enable=NO
+ firewall_script=/etc/rc.firewall
+ firewall_type=UNKNOWN
+ firewall_quiet=NO
+ firewall_logging=NO
+ firewall_logif=NO
+ firewall_flags=''
+ firewall_coscripts=''
+ firewall_client_net=192.0.2.0/24
+ firewall_simple_iif=ed1
+ firewall_simple_inet=192.0.2.16/28
+ firewall_simple_oif=ed0
+ firewall_simple_onet=192.0.2.0/28
+ firewall_myservices=''
+ firewall_allowservices=''
+ firewall_trusted=''
+ firewall_logdeny=NO
+ firewall_nologports='135-139,445 1026,1027 1433,1434'
+ firewall_nat_enable=NO
+ firewall_nat_interface=''
+ firewall_nat_flags=''
+ dummynet_enable=NO
+ ip_portrange_first=NO
+ ip_portrange_last=NO
+ ike_enable=NO
+ ike_program=/usr/local/sbin/isakmpd
+ ike_flags=''
+ ipsec_enable=NO
+ ipsec_file=/etc/ipsec.conf
+ natd_program=/sbin/natd
+ natd_enable=NO
+ natd_interface=''
+ natd_flags=''
+ ipfilter_enable=NO
+ ipfilter_program=/sbin/ipf
+ ipfilter_rules=/etc/ipf.rules
+ ipfilter_flags=''
+ ipnat_enable=NO
+ ipnat_program=/sbin/ipnat
+ ipnat_rules=/etc/ipnat.rules
+ ipnat_flags=''
+ ipmon_enable=NO
+ ipmon_program=/sbin/ipmon
+ ipmon_flags=-Ds
+ ipfs_enable=NO
+ ipfs_program=/sbin/ipfs
+ ipfs_flags=''
+ pf_enable=NO
+ pf_rules=/etc/pf.conf
+ pf_program=/sbin/pfctl
+ pf_flags=''
+ pflog_enable=NO
+ pflog_logfile=/var/log/pflog
+ pflog_program=/sbin/pflogd
+ pflog_flags=''
+ ftpproxy_enable=NO
+ ftpproxy_flags=''
+ pfsync_enable=NO
+ pfsync_syncdev=''
+ pfsync_syncpeer=''
+ pfsync_ifconfig=''
+ tcp_extensions=YES
+ log_in_vain=0
+ tcp_keepalive=YES
+ tcp_drop_synfin=NO
+ icmp_drop_redirect=NO
+ icmp_log_redirect=NO
+ network_interfaces=auto
+ cloned_interfaces=''
+ sppp_interfaces=''
+ ppp_enable=NO
+ ppp_program=/usr/sbin/ppp
+ ppp_mode=auto
+ ppp_nat=YES
+ ppp_profile=papchap
+ ppp_user=root
+ hostapd_enable=NO
+ syslogd_enable=YES
+ syslogd_program=/usr/sbin/syslogd
+ syslogd_flags=-s
+ syslogd_oomprotect=YES
+ altlog_proglist=''
+ inetd_enable=NO
+ inetd_program=/usr/sbin/inetd
+ inetd_flags='-wW -C

[belated] call for testing: replacement ath3k firmware upload tool

2016-05-25 Thread Adrian Chadd 
hiya,

I wrote a replacement ath3k bluetooth firmware upload tool, based on
the ath3k driver in linux. all the driver does is inject the "right"
firmware / config combination into the bluetooth chips.

https://github.com/erikarn/ath3k

I'd like to land this in -HEAD before 11, as it enables all of the
AR30xx series chips and figures out the right config to inject based
on the reported config. Some just need firmware, some need board
configurations, some need both.

I've been using this for a couple years now, and others have been
using it whenever they ask why their atheros bluetooth doesn't work.

Thanks!


-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

[belated] call for testing: replacement ath3k firmware upload tool

2016-05-25 Thread Adrian Chadd 
hiya,

I wrote a replacement ath3k bluetooth firmware upload tool, based on
the ath3k driver in linux. all the driver does is inject the "right"
firmware / config combination into the bluetooth chips.

https://github.com/erikarn/ath3k

I'd like to land this in -HEAD before 11, as it enables all of the
AR30xx series chips and figures out the right config to inject based
on the reported config. Some just need firmware, some need board
configurations, some need both.

I've been using this for a couple years now, and others have been
using it whenever they ask why their atheros bluetooth doesn't work.

Thanks!


-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: bluetooth not working in recent current

2016-05-25 Thread Maksim Yevmenkin 
Hi Graham

On Tue, May 24, 2016 at 1:31 AM, Graham Menhennitt
 wrote:
> I've been running 11-current AMD64 on this machine for about a year. It
> has a bluetooth dongle that has worked correctly up until a week ago. I
> updated to the latest source around then, so I presume that's what broke it.

can you please make sure that /etc/rc.d/bluetooth ran? it is usually
called from devd(8) in response to ubt(4) device arrival.

can you also please try to start it manually and see where it stops?
i.e. something like

# sh -x /etc/rc.d/bluetooth start ubt0

thanks!
max
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: AHCI/ADA regression?

2016-05-25 Thread Kenneth D. Merry 
On Wed, May 25, 2016 at 14:36:59 +0200, Gary Jennejohn wrote:
> On Wed, 25 May 2016 08:15:11 +0200
> Gary Jennejohn  wrote:
> 
> > On Tue, 24 May 2016 15:10:41 -0400
> > "Kenneth D. Merry"  wrote:
> > 
> > > Can you send full dmesg output from the working kernel?
> > >   
> > 
> > I'll give it a try and hope that the mail server doesn't strip it ==>
> > dmesg.boot.gz.
> > 
> > > It looks like you have some ATAPI devcies on your machine (signature 
> > > eb14).
> > > They would likely be attaching to the da(4) driver if they are disks, and
> > > that is a different code path.
> > >   
> > 
> > The one and only ATAPI device is cd0.
> > 
> 
> OK, it appears that one of the ATA fixes ken@ recently committed
> fixed my problem also.

Great!  I'm glad it's working!

> I'm now at r300677 and booting succeeds.
> 
> I guess the ATAPI DVD drive was the culprite.

It was most likely the Samsung hard drive.  This drive is the exact same
model that Alex Petrov also had problems with:

ada1 at ahcich2 bus 0 scbus2 target 0 lun 0
ada1:  ATA8-ACS SATA 2.x device
ada1: Serial Number S0MUJ1KP317818
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 476938MB (976771055 512 byte sectors)

It claims to support Read Log, but actually doesn't.

The change I checked in in revision 300640 will only send a Read Log (and
additional SMR probe steps) to drives that claim they're SMR drives.  Any
non-SMR drives should get the same probe as before.

Ken
-- 
Kenneth Merry
k...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: AHCI/ADA regression?

2016-05-25 Thread Gary Jennejohn 
On Wed, 25 May 2016 08:15:11 +0200
Gary Jennejohn  wrote:

> On Tue, 24 May 2016 15:10:41 -0400
> "Kenneth D. Merry"  wrote:
> 
> > Can you send full dmesg output from the working kernel?
> >   
> 
> I'll give it a try and hope that the mail server doesn't strip it ==>
> dmesg.boot.gz.
> 
> > It looks like you have some ATAPI devcies on your machine (signature eb14).
> > They would likely be attaching to the da(4) driver if they are disks, and
> > that is a different code path.
> >   
> 
> The one and only ATAPI device is cd0.
> 

OK, it appears that one of the ATA fixes ken@ recently committed
fixed my problem also.

I'm now at r300677 and booting succeeds.

I guess the ATAPI DVD drive was the culprite.

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"