I'm trying to automount the following device with 0666 permissions:
lsusb -vvv
Bus 001 Device 094: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6014 FT232H Single HS USB-UART/FIFO IC
bcdDevice 9.00
iManufacturer 1 FTDI
iProduct 2 C232HM-DDHSL-0
iSerial 3 FTVWEM02
bNumConfigurations 1
To achieve this I created the following udev rule in /etc/udev/rules.d
SUBSYSTEM=="usb", ATTR{idVendor}=="0403", ATTR{idProduct}=="6014", MODE="0666", RUN+="/usr/bin/touch /tmp/udev-test.txt"code here
As you can see I verify the functionality of the rule with a test file. The file is always created on the connection of the USB device.
-rw-r--r-- 1 root root 0 Oct 20 09:56 udev-test.txt
That should mean that the rule is functioning... however it never gets the permissions right.
When running ls -l /dev/ttyU* I get the following result:
crw-rw---- 1 root dialout 188, 0 Oct 20 09:56 /dev/ttyUSB0
Strangely enough if I run chmod from the command line as root, I can always change the permissions of the device. I would like that to happen on every plug-in automatically. Could you please help me?
I'm running Scientific Linux 7
Linux version 4.7.5-1.el7.elrepo.x86_64 (mockbuild#Build64R7) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Sat Sep 24 11:54:29 EDT 2016
The topics I already searched through:
Udev rule is not being applied - solution not working
https://stackoverflow.com/questions/34116854/udev-created-my-symblic-link-to-my-device-but-permission-not-set
Change ttyUSB permissions using udev - if I add KERNEL=="ttyUSB*" or KERNEL=="ttyUSB0" the rule is not working anymore
Run script with udev after USB plugged in on RPi
Related
I am currently trying to get the OpenThread code lab simulation (found here) working, but unfortunately I am stuck at the chapter "Manage the network with OpenThread Daemon". All the other chapters worked like a charm, but I cannot start the daemon in the last one.
As I am completely new to this topic there might be something obvious I just don't see. Does someone know how to fix this?
OS: macOS Monterey 12.6.3
I created the daemon with ./script/cmake-build posix -DOT_DAEMON=ON and tried running it with sudo ./build/posix/src/posix/ot-daemon -v 'spinel+hdlc+forkpty:///build/simulation/examples/apps/ncp/ot-rcp?forkpty-arg=2'.
The response is always the same:
Feb 18 11:20:08 ./build/posix/src/posix/ot-daemon[9798] <Info>: Running OPENTHREAD/thread-reference-20200818-2319-gafbb2d579; POSIX; Feb 18 2023 10:39:37
Feb 18 11:20:08 ./build/posix/src/posix/ot-daemon[9798] <Info>: Thread version: 4
Feb 18 11:20:08 ./build/posix/src/posix/ot-daemon[9798] <Critical>: 49d.18:22:23.835 [C] Platform------: Init() at hdlc_interface.cpp:151: InvalidArgument
I am running the latest Proxmox (6.3-3 at this time, fully updated) and attempting to passthrough the onboard GPU on my Core i7 4770 CPU to a Windows 10 VM. I have already enabled iommu on the system and also told grub to not let the system claim the device by adding intel_iommu=on video=efifb:off to the grub kernel options. I've verified IOMMU is actually available by checking dmesg
# dmesg | grep -e DMAR -e IOMMU -e AMD-Vi
[ 0.007556] ACPI: DMAR 0x00000000D88C33C8 0000B8 (v01 INTEL HSW 00000001 INTL 00000001)
[ 0.083595] DMAR: IOMMU enabled
[ 0.180445] DMAR: Host address width 39
[ 0.180446] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.180449] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
[ 0.180449] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.180451] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008020660462 ecap f010da
[ 0.180452] DMAR: RMRR base: 0x000000d8842000 end: 0x000000d884efff
[ 0.180452] DMAR: RMRR base: 0x000000db000000 end: 0x000000df1fffff
[ 0.180454] DMAR-IR: IOAPIC id 8 under DRHD base 0xfed91000 IOMMU 1
[ 0.180454] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.180455] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.180831] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 0.874497] DMAR: No ATSR found
[ 0.874527] DMAR: dmar0: Using Queued invalidation
[ 0.874531] DMAR: dmar1: Using Queued invalidation
[ 1.026818] DMAR: Intel(R) Virtualization Technology for Directed I/O
I've also added the iGPU (and associated audio device) to blacklist to prevent the host OS from claiming it:
# cat /etc/modprobe.d/blacklist.conf
blacklist snd_hda_intel
blacklist snd_hda_codec_hdmi
blacklist i915
# cat /etc/modprobe.d/vfio.conf
options vfio-pci ids=8086:0412 disable_vga=1
Finally, I setup a new Windows 10 VM on my host along with the q35 chipset and uEFI (OVMF) BIOS as this is apparently the most "compatible" way to pass through hardware. I've also got an external screen plugged into the HDMI port of my Proxmox host. I understand when the VM boots up, I should see this screen come to life. The qemu config file of the VM is below:
agent: 1
balloon: 0
bios: ovmf
boot: order=virtio0;ide2;net0
cores: 4
efidisk0: local-1tb-nvme-thinpool:vm-118-disk-1,size=4M
hostpci0: 00:02,pcie=1,x-vga=1
ide2: none,media=cdrom
machine: q35
memory: 4096
name: VFIOtest
net0: virtio=52:D7:02:CA:B6:2E,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=cd9d41e9-d8c2-465e-94dc-798aa8e517e2
sockets: 1
virtio0: local-1tb-nvme-thinpool:vm-118-disk-0,backup=0,discard=on,size=60G
vmgenid: 2cb8ce5e-5dda-4870-9cf3-774bb025057f
Once I've done that I can boot the VM. As soon as I boot the VM, the screen goes to standby indicating no signal. I can however then RDP into the system and I see that the Intel HD Graphics 4600 is visible in device manager. So I installed the latest drivers from the Intel website. Unfortunately, the device will not start and shows an exclamation mark next to it. The Device Status shows
Windows has stopped this device because it has reported problems. (Code 43)
Unfortunately, the code 43 error just means something is wrong, it isn't very specific on what is causing this.
Not too sure what to try from this point on - any assistance on where to continue fixing this would be useful.
Code 43 is a NVIDIA specific error; you will need a way to mask the true CPU by using the FancyId parameter. Here is a link to a video that covers some of the process revolving around the error you are seeing.
Can you edit the original post to contain your grub config file? There are some more recent changes to Proxmox 6.3 that might need to be reconfigured; there are almost no articles about setting up passthrough on 6.3.
I found it came down to setting the CPU model during VM creation. Changing it after VM creation does nothing so something must be set during creation. None of the other guides worked for me so I solved the problem and made my own guide https://elijahliedtke.medium.com/home-lab-guides-proxmox-6-pci-e-passthrough-with-nvidia-43ccfb9424de
i installed gem5 simulator on ubuntu 14.04. then i used the youtube guide (https://www.youtube.com/watch?v=gd_DtxQD5kc) to run gem5 in full system mode in ARM architecture. first i downloaded arm-system-2011-08.tar.bz2 as mentioned in the video then i run below command:
build/ARM/gem5.opt configs/example/fs.py --disk-image=/home/morteza/full_system_images/disks/arm-ubuntu-natty-headless.img --kernel=/home/morteza/full_system_images/binaries/vmlinux.arm.smp.fb.2.6.38.8
but i encountered this output. can abybody please help me?
p.s: i added --kernel option and rename bootloader in /fulls_system_image/binaries from boot.arm to boot_emm.arm because of some errors about not finding bootloader and kernel. this is my final output which i brought hereunder. i' ll appreciate if anybody tell what is the problem.
OUTPUT:
gem5 Simulator System. http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.
gem5 compiled Jan 3 2020 05:49:20
gem5 started Jan 3 2020 17:16:17
gem5 executing on morteza-pc, pid 2499
command line: build/ARM/gem5.opt configs/example/fs.py --disk-image=/home/morteza/full_system_images/disks/arm-ubuntu-natty-headless.img --kernel=/home/morteza/full_system_images/binaries/vmlinux.arm.smp.fb.2.6.38.8
warn: Can only correctly generate a dtb for VExpress_GEM5_V1 platforms, unless custom hardware models have been equipped with generation functionality.
Global frequency set at 1000000000000 ticks per second
warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (512 Mbytes)
info: kernel located at: /home/morteza/full_system_images/binaries/vmlinux.arm.smp.fb.2.6.38.8
warn: Bootloader entry point 0x80000000 overriding reset address 0
system.vncserver: Listening for connections on port 5900
system.terminal: Listening for connections on port 3456
0: system.remote_gdb: listening for remote gdb on port 7000
info: Using bootloader at address 0x80000000
info: Using kernel entry physical address at 0x80008000
warn: DTB file specified, but no device tree support in kernel
**** REAL SIMULATION ****
warn: Existing EnergyCtrl, but no enabled DVFSHandler found.
info: Entering event queue # 0. Starting simulation...
warn: Device system.membus.badaddr_responder accessed by read to address 0x10009018 size=4
gem5.opt: build/ARM/cpu/simple/atomic.cc:418: virtual Fault AtomicSimpleCPU::readMem(Addr, uint8_t*, unsigned int, Request::Flags, const std::vector<bool>&): Assertion `!pkt.isError()' failed.
Program aborted at tick 30500
--- BEGIN LIBC BACKTRACE ---
build/ARM/gem5.opt(_Z15print_backtracev+0x15)[0x1d505e5]
build/ARM/gem5.opt(_Z12abortHandleri+0x36)[0x1d5a796]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f41e3962330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f41e1eacc37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f41e1eb0028]
/lib/x86_64-linux-gnu/libc.so.6(+0x2fbf6)[0x7f41e1ea5bf6]
/lib/x86_64-linux-gnu/libc.so.6(+0x2fca2)[0x7f41e1ea5ca2]
build/ARM/gem5.opt(_ZN15AtomicSimpleCPU7readMemEmPhj5FlagsImERKSt6vectorIbSaIbEE+0x538)[0x1e4eca8]
build/ARM/gem5.opt(_ZN17SimpleExecContext7readMemEmPhj5FlagsImERKSt6vectorIbSaIbEE+0x21)[0x1e5c5b1]
build/ARM/gem5.opt(_Z13readMemAtomicI11ExecContextjESt10shared_ptrI9FaultBaseEPT_PN5Trace10InstRecordEmRT0_5FlagsImE+0x64)[0x1972e14]
build/ARM/gem5.opt(_ZNK10ArmISAInst27LOAD_IMM_AY_PN_SN_UN_WN_SZ47executeEP11ExecContextPN5Trace10InstRecordE+0x12d)[0x14f95cd]
build/ARM/gem5.opt(_ZN15AtomicSimpleCPU4tickEv+0x428)[0x1e4da58]
build/ARM/gem5.opt(_ZN10EventQueue10serviceOneEv+0xa1)[0x1d55f51]
build/ARM/gem5.opt(_Z9doSimLoopP10EventQueue+0x38)[0x1d65fc8]
build/ARM/gem5.opt(_Z8simulatem+0xaae)[0x1d66dfe]
build/ARM/gem5.opt[0x1dbbd3d]
build/ARM/gem5.opt[0xe08e85]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x45f7)[0x7f41e3579be7]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x80d)[0x7f41e357b63d]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x48d8)[0x7f41e3579ec8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x80d)[0x7f41e357b63d]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x48d8)[0x7f41e3579ec8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x80d)[0x7f41e357b63d]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x48d8)[0x7f41e3579ec8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x80d)[0x7f41e357b63d]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7f41e357b772]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x563e)[0x7f41e357ac2e]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x80d)[0x7f41e357b63d]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x48d8)[0x7f41e3579ec8]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x80d)[0x7f41e357b63d]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7f41e357b772]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x79)[0x7f41e35755a9]
--- END LIBC BACKTRACE ---
Aborted (core dumped)
I downloaded OpenNI SDK2 sources x64, compiled and tried to run Samples, but wasnt successful.
100 INFO New log started on 2013-10-27 00:03:47
130 INFO --- Filter Info --- Minimum Severity: VERBOSE
166 VERBOSE No override device in configuration file
182 VERBOSE Configuration has been read from './OpenNI.ini'
190 VERBOSE OpenNI 2.2.0 (Build 32)-Linux-x86 (Oct 26 2013 21:13:04)
197 VERBOSE Using './OpenNI2/Drivers' as driver path
208 VERBOSE Looking for drivers in drivers repository './OpenNI2/Drivers'
933 INFO New log started on 2013-10-27 00:03:47
950 INFO --- Filter Info --- Minimum Severity: VERBOSE
966 VERBOSE Initializing USB...
1074 INFO USB is initialized.
4274 INFO New log started on 2013-10-27 00:03:47
4292 INFO --- Filter Info --- Minimum Severity: VERBOSE
4304 VERBOSE Initializing USB...
4366 INFO USB is initialized.
15321 VERBOSE Trying to open device by URI '(NULL)'
15367 ERROR Can't open default device - none found
Couldn't open device
DeviceOpen using default: no devices found
lsusb gets this
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 058f:b002 Alcor Micro Corp.
Bus 001 Device 004: ID 045e:00f0 Microsoft Corp.
Bus 002 Device 003: ID 046d:c312 Logitech, Inc. DeLuxe 250 Keyboard
Bus 002 Device 007: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 002 Device 004: ID 1c7a:0603 LighTuning Technology Inc.
Bus 002 Device 009: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
Bus 002 Device 008: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
Bus 002 Device 010: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
I also tried some libfreenect examples with kinect a it worked without any problem.
I add some line to SimpleRead main.cpp file
Array<DeviceInfo> dev_info;
OpenNI::enumerateDevices(&dev_info);
printf("Number of devices %d \n",dev_info.getSize());
which writes out 0.
Output of
lsmod | grep gspca_kinect is void
What could be possibly wrong?
I'm on Ubuntu 64bit v13.04, Kinect is "Kinect for Xbox", using USB2
I am adding this answer because #Brian Tompsett's link is broken. There is an easy workaround to this while compiling libfreenect: just ensure you turn on the flag -DBUILD_OPENNI2_DRIVER=ON when calling cmake during libfreenect's build.
After installing, head over to
/home/$(whoami)/path/to/libfreenect/build/lib/OpenNI2-FreenectDriver
and copy libFreenectDriver.so* to your downloaded OpenNI2 Bin directory, i.e.: /path/to/OpenNI2/Bin/x64-Release/
Check if your installation is okay by testing the precompiled NiViewer. Depending on the rules you configured in your udev folder, you might need to run NiViewer with root.
Good luck!
(Answered by the OP in an edit, see Question with no answers, but issue solved in the comments (or extended in chat) )
The OP wrote:
According to OpenNI forum topic
new OpenNI SDK2 doesnt support Kinect device. Anyway, there is a link to OpenKinect drivers "hacked" to work with OpenNI SDK2
#Calorified 's answer worked for me.
In addition, make sure to update the OpenNI.ini file, e.g. to run the OpenNI sample apps in OpenNI2/Samples/Bin or the NiTE sample apps in /path/to/NiTE*/Samples/Bin.
For example, I was using the 32-bit OpenNI version 2.2:
I copied the libFreenectDriver.so* to /path/to/OpenNI2/Tools (there is no bin/x64-release folder in this OpenNI version).
In OpenNI2/Samples/Bin, edit the file OpenNI.ini
Under the [Drivers] section, at the end of the file, add the line: Repository=/path/to/OpenNI2/Tools (where you put the libFreenectDriver.so file). Below is my edited OpenNI.ini file. I used a relative path, but an absolute path will also work.
#/path/to/OpenNI2/Samples/Bin/OpenNI.ini
[Log]
; 0 - Verbose; 1 - Info; 2 - Warning; 3 - Error. Default - None
Verbosity=3
LogToConsole=0
LogToFile=0
[Device]
;Override=""
[Drivers]
; Location of the drivers specified by a relative path based on OpenNI's shared library or an absolute path.
; Path separator "/" can be used to be portable for any platforms.
; Default - OpenNI2/Drivers
Repository=../../Tools
You'll have to do the same thing for the NiTE samples. The samples should run now.
Without updating the OpenNI.ini I always get the error DeviceOpen using default: no devices found
*ps. libfreenect installation will put the libFreenectDriver.so in /usr/local/lib/OpenNI2-FreenectDriver/
Im linking to a remote linux machine. I want to be able to view the files/ directories on this machine using a GUI. I run xming and ssh and putty.I then stried to start the windows manager. THe output is below.
What is happening here, it seems xterm is not available. But I can run emacs so there must be some windows manager present. Can I use that instead?
Running startx --help
[root#foo ~]# startx --help
xauth: creating new authority file /root/.serverauth.6094
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-194.11.1.el5 x86_64 Red Hat, Inc.
Current Operating System: Linux ten2 2.6.18-238.1.1.el5 #1 SMP Tue Jan 4 13:32:19 EST 2011 x86_64
Build Date: 01 September 2010
Build ID: xorg-x11-server 1.1.1-48.76.el5_5.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 20 18:57:05 2011
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Multiple symbols for level 1/group 1 on key <I5F>
> Using XF86Sleep, ignoring XF86Standby
> Warning: Symbol map for key <I5F> redefined
> Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server
xinit: No such file or directory (errno 2): no program named "xterm" in PATH
Specify a program on the command line or make sure that /usr/bin
is in your path.
waiting for X server to shut down FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing.
Running startx without the help flag results in a different error message. Why is this?
Running startx
[root#foo ~]# startx
xauth: creating new authority file /root/.serverauth.5375
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-194.11.1.el5 x86_64 Red Hat, Inc.
Current Operating System: Linux foo 2.6.18-238.1.1.el5 #1 SMP Tue Jan 4 13:32:19 EST 2011 x86_64
Build Date: 01 September 2010
Build ID: xorg-x11-server 1.1.1-48.76.el5_5.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 20 18:39:23 2011
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Multiple symbols for level 1/group 1 on key <I5F>
> Using XF86Sleep, ignoring XF86Standby
> Warning: Symbol map for key <I5F> redefined
> Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server
localuser:root being added to access control list
No profile for user 'root' found
waiting for X server to shut down FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing.
That's probably because of xterm command in .xinitrc - this file contains application which should be started with X server, typically there are commands there to start window manager or desktop environment like KDE or Gnome. But often it defaults to twm + xterm.