OracleSolaris 11.2 -- adding driver to system, attach fails

Asked Jul 07 '15 at 19:05

Active Jul 07 '15 at 19:05

Viewed 665 times

I'm learning Solaris and writing a simple driver; currently I implemented basic entry points, i.e. _init, _info, _finit, *attach, *detach. It compiles and links with no issues, then I copy it to /usr/kernel/drv/amd64/ and call:

% add_drv mydrv
Jul   7 22:54:16 ezhost mydrv: NOTICE: mydrv: _info called
devfsadm: driver failed to attach: mydrv
Warning: Driver (mydrv) successfully added to system but failed to attach
Jul   7 22:54:16 ezhost mydrv: NOTICE: mydrv: _init called

Currently what I do in my _attach routine is:

ddi_get_instance ddi_soft_state_zalloc ddi_get_soft_state

and return DDI_SUCCESS

Not much, but probably when the drivers gets loaded in memory, the system (devfsadm) expects to creates some entries in devfs, however my driver doesn't register any character device nodes, and as result fails?

asked Jul 07 '15 at 19:05

Mark

6,052
8
61
129

1

Do you have a `/usr/kernel/drv/drivername.conf` file? – Andrew Henle Jul 07 '15 at 19:14
1

Have you created a conf file so your device will attach to a `pseudo` bus? – myaut Jul 07 '15 at 19:16
Andrew + myaut -- I do have /usr/kernel/drv/mydrv.conf, however it is empty, I don't know what should be in there. – Mark Jul 07 '15 at 19:18
2

@Mark: Try this: `name="mydrv" parent="pseudo" instance=0;` – myaut Jul 07 '15 at 19:22
@myaut, thanks! I do see my device in /devices/pseudo/mydrv@0 It means in solaris, a driver needs to be attached at least to pseudo bus? – Mark Jul 07 '15 at 19:30
1

Do you see your driver listed with `dtrace -l` after it's loaded? Using `dtrace` might give you some insight into what's happening. – Andrew Henle Jul 07 '15 at 21:50
@Andrew, thanks for pointing at dtrace, very useful tool indeed. – Mark Jul 08 '15 at 13:34

OracleSolaris 11.2 -- adding driver to system, attach fails

0 Answers0