But the error is too widely spread it seems. Sorry, my bad, wasn’t very clear: the device never worked on openSUSE, will get a laptop today with a Windows 10 just to rule out a defective product. Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3įakeMoth-PC:/home/fakemoth # hcitool scanįakeMoth-PC:/home/fakemoth # hciconfig hci0 upĬan't init device hci0: Operation not supported (95)įakeMoth-PC:/home/fakemoth # bluetoothctlĪny ideeas, any experience with this? I read about recompiling the kernel but it is overkill, isn’t there some module or something I can just load? Thanks! TX bytes:368 acl:0 sco:0 commands:30 errors:0įakeMoth-PC:/home/fakemoth # hciconfig -a hci0įeatures: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87 RX bytes:574 acl:0 sco:0 events:30 errors:0 So the device works and it’s a Cambridge chip, but:īD Address: 00:1A:7D:DA:71:11 ACL MTU: 679:9 SCO MTU: 48:16 Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)Īctive: active (running) since Sun 10:02:40 EEST 30min agoĪug 02 10:02:40 FakeMoth-PC systemd: Starting Bluetooth service.Īug 02 10:02:40 FakeMoth-PC bluetoothd: Bluetooth daemon 5.48Īug 02 10:02:40 FakeMoth-PC bluetoothd: Starting SDP serverĪug 02 10:02:40 FakeMoth-PC bluetoothd: Bluetooth management interface 1.14 initializedĪug 02 10:02:40 FakeMoth-PC systemd: Started Bluetooth service.įakeMoth-PC:/home/fakemoth # dmesg | grep Bluetoothġ6.667986] Bluetooth: HCI device and connection manager initializedġ6.667989] Bluetooth: HCI socket layer initializedġ6.667990] Bluetooth: L2CAP socket layer initializedġ6.667992] Bluetooth: SCO socket layer initializedĢ2.211247] Bluetooth: BNEP (Ethernet Emulation) ver 1.3Ģ2.211248] Bluetooth: BNEP filters: protocol multicastĢ2.211251] Bluetooth: BNEP socket layer initializedīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supplyīus 001 Device 005: ID 1532:006c Razer USA, Ltdīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub This is like the third piece of s… bought (at least is Bluetooth 5.0, if it would work) and I am out of ideas… Was running Leap 15.1 with the latest stable 5.7 kernel, but I upgraded to 15.2 with the 5.3 kernel, my Vega 64 wouldn’t run on 4.x versions. It seems to be more a "workaround solution" or "quick and dirty job" for just a basic support for keyboard and mouse.Īccording to me, there is no guaranty for the future regarding the support of bluetooth in FreeBSD.Hello, need some help with a Bluetooth dongle, just can’t make it work. so I always found that strange and "wobbly". This is not basically the goal of Netgraph to manage bluetooth. Netgraph modules are intended first to create/manage virtual network devices (for advanced users) The current support is very basic, through 'netgraph' modules. there is no real support of Bluetooth in FreeBSD, and this isn't a priority. To setup 'virtual_oss' you should find help on GoogleĪnyway. I don't know if it supports high definition audio, but basic audio can work I haven't personally tried, but from what I have read this is working, and it seems that even under Linux, bluetooth audio is handled by 'virtual_oss' This firmware layer is included in audio/virtual_oss the FreeBSD handbook is not totally false, but may be incompleteīase system can associate devices, but it requires an additional audio "firmware layer"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |