Thanks everyone for the help, or at least for moral support ;-) Vivek, you are correct (I wish someone had pointed out loader.conf earlier). I finally discovered loader.conf last night and managed to figure out what I need to do.
As stated earlier, I had found the device is supported by uftdi driver. I was able to copy the uftdi.ko from my freeBSD 6.2-Release box, put it in /boot/kernel, and then modify /boot/loader.conf to load it. The device now properly comes up as /dev/ttyU0 and works great! (it is, IIRC, loaded as a ucom device as noted by the system.log) this is *very* good news for me, as I was hoping to get this going fast and not need to rebuild the flash image or kernel ;-) "mount -uw /" is my best friend. Now I just need to do some crontab work... -Chris --- Vivek Khera <[EMAIL PROTECTED]> wrote: > On Dec 17, 2007, at 7:49 PM, Chris Buechler wrote: > > >> on my other (recently setup) BSD system, which is: FreeBSD 6.2- > >> RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 > >> I see in /usr/src/sys/dev/usb that uftdi.c and "usbdevs" contain a > >> definition for this device. > > > > I'm not sure exactly what kernel change would be necessary to add > > this. What does it show up as in dmesg on a stock FreeBSD system? > > The driver needed depends on the device. I have one which requires > the uplcom driver loaded (I pull it in as a module in /boot/ > loader.conf) Others may require umct, uvscom, or just ucom. I > suppose some might require some other driver, too. The man page for > ucom list all the additional drivers you may need. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
