I am running Vmware vm with Ubuntu 18 OS on a Window 10 system. A USB bluetooth device is plug in this Machine. Now I want to control this bluetooth device in Ubuntu 18 VM, but failed.
In Ubuntu VM, I can get bluetooth hardware info through:
# hcitool scan
Scanning ...
70:EF:00:D0:AE:05 ****
3C:CD:57:2C:94:4F ****
14:DE:39:E5:B2:F8 ****
48:01:C5:06:DC:A2 ****
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root#turnbig:~# lshw | grep Blue -C 10
*-usb:1
description: USB hub
product: VMware Virtual USB Hub
vendor: VMware, Inc.
physical id: 2
bus info: usb#2:2
version: 1.00
capabilities: usb-1.10
configuration: driver=hub slots=7 speed=12Mbit/s
*-usb
description: Bluetooth wireless interface
product: Virtual Bluetooth Adapter
vendor: VMware
physical id: 1
bus info: usb#2:2.1
version: 1.00
serial: 000650268328
capabilities: bluetooth usb-2.00
configuration: driver=btusb speed=12Mbit/s
But when i try to connect to other BT devices, it failed with "Device 3C:CD:57:2C:94:4F not available", 3C:CD:57:2C:94:4F is a target bluetooth device to connect:
# bluetooth
bluetooth = on
# bluetoothctl
[NEW] Controller 44:AF:28:F5:2B:D3 ***** [default]
Agent registered
[bluetooth]# info 3C:CD:57:2C:94:4F
Device 3C:CD:57:2C:94:4F not available
[bluetooth]# connect 3C:CD:57:2C:94:4F
Device 3C:CD:57:2C:94:4F not available
I can connect to this BT device through host machine (Window 10)
thanks for any comment.
Question fixed, original solution is post here.
To use a USB bluetooth from VMware guest OS, we can not share bluetooth to guest, we should connect the removeable bluetooth device to guest directly.
is it possible to have opengl|Es 3.0 or above with these system configuration:
Dell Inspiron 1464
processor - Intel® Core™ i3 CPU M 350 # 2.27GHz × 4
graphics - Intel® Ironlake Mobile
os Type - 64 bit
when i run glxinfo i have output as:
GLX version: 1.4
OpenGL version string: 2.1 Mesa 10.3.2
OpenGL shading language version string: 1.20
i did also use launchpad to get opengl 3.0
sudo add-apt-repository ppa:oibaf/graphics-drivers
but got this response from glxinfo:
GLX version: 1.4
OpenGL version string: 2.1 Mesa 10.3.2
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 10.3.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
i do find on some places that intel ironlake mobile graphics do not support opengl 3.0 fully, as i have also intall all the intel graphics drives in my other OS windows7 to get opengl 3.0 but it still says 2.1 only, while it showing some of the features of 3.0 and 3.1 but not fully.
https://software.intel.com/en-us/forums/topic/281262
the image in this link shows the exact case of mine in Windows 7.(i could not able to post the image but you'll surely get the proper picture of the problem from the link's image)
Mesa utils also says that it supports opengl 3.0 from 8.0 but totally depends on the system graphical support.
i needs opengl 3.0 very badly, can some one please give any idea regarding this.
i did see
http://stackoverflow.com/questions/14123895/opengl-glsl-3-3-on-an-hd-graphics-4000-under-ubuntu-12-04
http://stackoverflow.com/questions/21565680/how-to-enable-opengl-3-3-using-mesa-10-1-on-ubuntu
and many other links like these but could not get any solution.
i have already tried AMD catalyst drivers (15.7, 14.12, 12.1, 13.1)but not supported i.e they were all installed fglrx but when i ran aticonfig or amdconfig they says no supported adapters, and they are giving same opengl 2.1 response.
lspci -v | grep VGA result:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller])
lspci -v result:
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller])
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 1800 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at f0605800 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel driver in use: mei_me
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI])
Subsystem: Dell Device 0434
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f0606000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f0600000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: c0000000-c01fffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: c0400000-c08fffff
Prefetchable memory behind bridge: 00000000f0700000-00000000f07fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI])
Subsystem: Dell Device 0434
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at f0606400 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Capabilities: <access denied>
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
Subsystem: Dell Device 0434
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06) (prog-if 01 [AHCI 1.0])
Subsystem: Dell Device 0434
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 41
I/O ports at 1818 [size=8]
I/O ports at 180c [size=4]
I/O ports at 1810 [size=8]
I/O ports at 1808 [size=4]
I/O ports at 1820 [size=32]
Memory at f0605000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
Subsystem: Dell Device 0434
Flags: medium devsel, IRQ 10
Memory at f0606800 (64-bit, non-prefetchable) [size=256]
I/O ports at 1840 [size=32]
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
Subsystem: Dell Device 0434
Flags: fast devsel, IRQ 18
Memory at f0604000 (64-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: intel ips
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Subsystem: Dell Device 0434
Flags: bus master, fast devsel, latency 0, IRQ 40
I/O ports at 2000 [size=256]
Memory at f0710000 (64-bit, prefetchable) [size=4K]
Memory at f0700000 (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at c0400000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: r8169
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Intel Corporation Device 8086
Flags: bus master, fast devsel, latency 0
lspci -nnk result:
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 12)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: i915
00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: mei_me
00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06)
Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 [8086:3b4c] (rev 06)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 06)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a6)
00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller [8086:3b09] (rev 06)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller [8086:3b29] (rev 06)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06)
Subsystem: Dell Device [1028:0434]
00:1f.6 Signal processing controller [1180]: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32] (rev 06)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: intel ips
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
Subsystem: Dell Device [1028:0434]
Kernel driver in use: r8169
ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
ff:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2d11] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
ff:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d12] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
ff:02.3 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d13] (rev 02)
Subsystem: Intel Corporation Device [8086:8086]
Well i have tried these unsuccessful options..
installs almost all intel and AMD drives.
upgrade to ubuntu 14.10 and install intel driver installation deb as it
supports only ubuntu 14.10 and a fedora version.
installs propriatery drivers(iobaf) many times , but as i says 15.04 i have
also upgrade to ubuntu 15.04 and tried it again, no success.
My processor is ironalake Arrandale, 2.26 GHz Core i3 350 M.
Intel HD Graphics.
https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units
http://ark.intel.com/products/43529/Intel-Core-i3-350M-Processor-3M-Cache-2_26-GHz
I don't think that it's possible to have Opengl 3.0 with these configuration, either in windows or in linux.
If someone finds any solution regarding that then kindly share it here, it would be very helpful.
for now i am using ubuntu 15.04 as it goes good with my AndroidStudio with NDk support, and i am using my Android Device to have opengl 3.0 support as my system can't give it to Genymotion which i wanted to run for Opengl 3.0 support.
I am hoping that you're able to help me I am trying to understand how use the /proc file system or profile settings. I am trying to write a script which pulls the temp of the CPU and a list of peripherals attached to a SUSE device. This would be using native functionality rather than a tool. Is there a path of sorts to the variable for temp of the CPU and a list of attached devices?
Hopefully it makes sense.
Regards
QuinsUK
To get temp use "sensors":
$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +63.0°C (high = +105.0°C, crit = +105.0°C)
Core 1: +60.0°C (high = +105.0°C, crit = +105.0°C)
or look at the /sys/class/hwmon/
$ cd /sys/class/hwmon/hwmon0/device/
{ cat temp3_label; cat temp3_input; }
Core 1
58000
For attached devices:
lspci - List PCI:
$ lspci
00:00.0 Host bridge: Intel Corporation 82G35 Express DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
lsscsi - List scsi devices:
$ lsscsi
[3:0:0:0] disk ATA ST3500418AS CC38 /dev/sda
[4:0:0:0] cd/dvd SONY DVD RW DRU-190A 1.63 /dev/sr0
lsusb - List usb buses and device details:
$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
hwinfo — all at once
Objective
I'm trying to programmatically find out on which physical slot a particular PCIe device is connected. The premise is that I have the PCI-ID of a card that is surely occupying a slot, and the solution would be finding out which one.
Note that I'm only interested in working on the PCI Express bus, although the device identification/enumeration process I think is the same as the old PCI.
Attempt
The SMBIOS contains information about the motherboard slots available. It is possible to examine this information from the linux command line:
$ sudo dmidecode -t slot
# dmidecode 2.11
SMBIOS 2.7 present.
Handle 0x003A, DMI type 9, 17 bytes
System Slot Information
Designation: PCIEX16_1
Type: x16 PCI Express x16
Current Usage: In Use
Length: Short
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:03:02.0
Handle 0x003B, DMI type 9, 17 bytes
System Slot Information
Designation: PCIEX16_2
Type: x8 PCI Express x8
Current Usage: In Use
Length: Short
ID: 2
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:04:02.2
Handle 0x003C, DMI type 9, 17 bytes
System Slot Information
Designation: PCIEX16_3
Type: x16 PCI Express x16
Current Usage: In Use
Length: Short
ID: 3
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:05:03.0
However, I can't find any device in the PCI bus (lspci) that has a PCI ID of 0000:03:02.0, 0000:04:02.2 or 0000:05:03.0. What I know by manual inspection is the following:
Card 0000:03:00.0 is in the first slot. The PCI bridge appears to be 0000:00:02.0
Card 0000:04:00.0 is in the second slot. The PCI bridge appears to be 0000:00:02.2
Card 0000:05:00.0 is in the third slot. The PCI bridge appears to be 0000:00:03.0
So a pattern emerges here. From the SMBIOS structure, the bus number is the one given to the card that is plugged in but the device/function numbers are the same as the corresponding PCI bridge.
Is this pattern just a coincidence in my motherboard or there is a rationale behind? It is an Asus motherboard, with an AMI BIOS. I've read that some BIOSes do not provide accurate information about their slots so I would like to know how much generality I can achieve.
Any hint or pointer to reference documentation is also greatly appreciated.
You may find the lspci command helpful. Here's a sample output:
# lspci -v -t
-[0000:00]-+-00.0 Intel Corporation 5500 I/O Hub to ESI Port
+-01.0-[01]--+-00.0 Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
| \-00.1 Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
+-03.0-[02]--+-00.0 Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
| \-00.1 Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
+-07.0-[04]----00.0 LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator]
+-09.0-[05]----00.0 LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator]
+-14.0 Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers
+-14.1 Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers
+-14.2 Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers
+-1a.0 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4
+-1a.1 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5
+-1a.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2
+-1c.0-[03]----00.0 LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator]
+-1d.0 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1
+-1d.1 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2
+-1d.7 Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1
+-1e.0-[06]----03.0 Matrox Electronics Systems Ltd. MGA G200eW WPCM450
+-1f.0 Intel Corporation 82801IB (ICH9) LPC Interface Controller
\-1f.2 Intel Corporation 82801IB (ICH9) 2 port SATA Controller [IDE mode]
I'm having a builddroot assembled busybox distribution running on my micro.
It all works well so far but I realized one thing. When I boot my box up and
I do an lsusb I see this:
# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 003: ID 12d1:14ac Huawei Technologies Co., Ltd.
Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
Composite Device
and I have following links:
ttyUSB0 ttyUSB1 ttyUSB2 ttyUSB3
buyt none of those links seem to go to Device 0004 but if I replug the
CP210x device, I get this:
# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 003: ID 12d1:14ac Huawei Technologies Co., Ltd.
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
Composite Device
and these links:
ttyUSB0 ttyUSB1 ttyUSB2 ttyUSB3 ttyUSB4
and now ttyUSB4 is linking to my Device 005 why do I need to replug my
device in order to get a working symlink? That's not what I want? :(
How can I fix this? The cp210x module is compiled into the kernel (not
attached as a separate module) - any suggestions?
This for some reason just stop happening probably due to the fact that we're only using one usb device now. Inodes would have been a solution but got never implemented in our system.