Re: Adding a driver
- From: John <jvasquez@xxxxxxxxxxxx>
- Date: Tue, 05 Feb 2008 08:32:36 -0800
Where does your driver binary live?
Have you got a driver.conf file? (You have to have one, even if it's empty.)
What does "isainfo -k" report?
/kernel/drv
isainfo -k reports, "i386".
What sort of device are you (5th parameter)?Its a PCI device, the 5th parameter is, "getcatds".
For some types of device, the /dev node is created automatically
as there are uniform naming rules for things like serial ports.
Otherwise, you'll need to add a line to /etc/devlink.tab to
cause your /dev link to be created, and that can be fiddly (it's
a very non-obvious format file).
Ok, I do have /etc/devlink.tab and made the following entry.
type=getcatds atds\NO
That should be a zero, not a capital 'o'.
It was, this was a typeo. I took a look at the devlink.tab and it was
a zero.
I presume that will give you /dev/atds0
thats what I'm looking for. Actually, its catds0
So right now, I'm stuck.
I don't know what else to try.
In my install file I do this to add an entry into the /etc/devlink.tab
echo ""type=getcatds\tcatds\\N0" >> /etc/devlink.tab
That is a 0 not a cap 'o'
Then I do this to start the driver
/usr/sbin/add_drv -m '* 0666 root sys' -i '"pci15e7,0756"' getcatds
then I get the message
devfsadm: driver failed to attach: getcatds
The getcatds driver is located in the \kernel\drv directory.
There is an entry, getcatds "pci15e7,0756" in /etc/driver_aliases
Any other ideas.
.
- Follow-Ups:
- Re: Adding a driver
- From: Andrew Gabriel
- Re: Adding a driver
- References:
- Adding a driver
- From: John
- Re: Adding a driver
- From: Andrew Gabriel
- Re: Adding a driver
- From: John
- Re: Adding a driver
- From: Andrew Gabriel
- Adding a driver
- Prev by Date: Re: /usr/local/lib - ln or LD_LIBRARY_PATH
- Next by Date: Re: Adding a driver
- Previous by thread: Re: Adding a driver
- Next by thread: Re: Adding a driver
- Index(es):
Relevant Pages
|