The problem with Linux-land is that everything is covered up with hacks, band-aids, temp workarounds, and whatnot, all layered one upon the other in userland. There's udev, hal, and something else that are supposed to all "work together" to make managing devices "automatic". Some things read device info from /proc, some from /sys, others from /dev. But it doesn't always work, all the configs are written in XML, it's not manageable by non-programmers, and no one is really sure just what is happening.
FreeBSD has a nice, integrated, manageable, understandable setup:
*kernel detects hardware
*kernel attaches driver(s)
*kernel signals devd
*devd creates device nodes in /dev
*userland is notified and device becomes usable right away
The config file (/etc/devd.conf /etc/devfs.rules) are simple text files, easy to read, easy to understand, easy to edit. And everything just works.
Sorry, I just really, really, really dislike device management on Linux. It's all very hokey to me, hacked-together, and unusable to me.
Back to your problem: What are the permissions on /dev/ad4, and are there any errors shown in dmesg output?
Last edited by phoenix (2008-08-21 20:11:39)