Displaying 7 results from an estimated 7 matches for "add_drv".
Did you mean:
add_dev
2005 Oct 11
7
dtrace: failed to initialize dtrace: DTrace device not available on system
I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error
dtrace: failed to initialize dtrace: DTrace device not available on system
the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional
2009 Jan 13
1
consolidating the NUT documentation on permissions, hotplug and udev
Arnaud et al,
I have been meaning to collect some of the documentation updates for
permission-related errors, and I was wondering if you would mind if we
moved the scripts/udev/README and scripts/hotplug/README files out of
scripts/ and into the docs/ directory (probably docs/permissions.txt).
We could also cover the *BSD /dev/usb* permission issues there, as
well.
Any thoughts on this?
--
-
2006 Sep 11
7
installing a pseudo driver in a Solaris DOM U and DOM U reboot
...ack we found is to pkgrm the driver and pkgadd the driver again
after a dom U restart.
Pseudo Driver installation is done the following way:
# pkgadd -d ... SUNWegcff
that adds
/etc/devlink.tab:
type=ddi_pseudo;name=ffmod ffmod\M0
/etc/minor_perm:
clone:ffmod 0600 root sys
and does
/usr/sbin/add_drv -v ffmod
/usr/sbin/devfsadm -i ffmod
# modinfo -c | grep ffmod
194 2 ffmod LOADED/INSTALLED
#
# ls -al /dev/*ff*
lrwxrwxrwx 1 root other 29 Sep 11 09:20 /dev/ffmodctl -> ../devi
ces/pseudo/ffmod@0:ctl
#
# ls -al devices/pseudo/ffmod@0:ctl
crw-...
2006 Sep 25
4
Can''t create a virtual nic
Howdy,
I just installed the crossbow snapshot from opensolaris.org, and bumped
into an issue when attempting to create a virtual nic:
$ dladm create-vnic -i 192.168.1.101 -d ni0 2
dladm: VNIC creation failed: No such file or directory (unknown
diagnostic)
When I truss the process, it looks like it''s failing when attempting to
open the vnic pseudo-device:
100878/1:
2006 Dec 07
6
cannot load kqemu modul on solaris 5.10 3/05
...usr/sbin/install -f /usr/kernel/drv/amd64 -m 755 -u root -g sys kqemu
new owner is root
kqemu installed as /usr/kernel/drv/amd64/kqemu
rm kqemu
/usr/sbin/install -f /usr/kernel/drv -m 644 -u root -g sys kqemu.conf
new owner is root
kqemu.conf installed as /usr/kernel/drv/kqemu.conf
rm -f /dev/kqemu
add_drv kqemu
devfsadm: driver failed to attach: kqemu
Warning: Driver (kqemu) successfully added to system but failed to attach
( cd /dev ; /usr/sbin/mknod kqemu c `/usr/bin/grep kqemu /etc/name_to_major | /usr/bin/awk ''{print $2}''` 0 )
-bash-3.00#
---
DMESG (same output on boot screen...
2013 Nov 09
3
usb ups on openindiana
...9;usb6da,3.0' + 'usb6da,3' +
'usbif6da,class3.0.0' + 'usbif6da,class3.0' + 'usbif6da,class3' +
'usbif,class3.0.0' + 'usbif,class3.0' + 'usbif,class3' + 'usb,device'
So this UPS has VendorID 06DA, ProductID 0003.
# rem_drv ugen
# add_drv -i '"usb6da,3.0"' -m '* 0666 nobody nobody' ugen
# dmesg | tail
...
Nov 9 15:42:10 n54l usba: [ID 912658 kern.info] USB 1.10 device
(usb6da,3) operating at low speed (USB 1.x) on USB 1.10 root hub:
input at 5, ugen0 at bus address 2
Nov 9 15:42:10 n54l usba: [ID...
2013 Nov 09
0
usb ups on openindiana
...; +
> 'usbif6da,class3.0.0' + 'usbif6da,class3.0' + 'usbif6da,class3' +
> 'usbif,class3.0.0' + 'usbif,class3.0' + 'usbif,class3' + 'usb,device'
>
>
> So this UPS has VendorID 06DA, ProductID 0003.
>
> # rem_drv ugen
> # add_drv -i '"usb6da,3.0"' -m '* 0666 nobody nobody' ugen
>
> # dmesg | tail
> ...
> Nov 9 15:42:10 n54l usba: [ID 912658 kern.info] USB 1.10 device
> (usb6da,3) operating at low speed (USB 1.x) on USB 1.10 root hub:
> input at 5, ugen0 at bus address 2
>
>...