It seems Sheldon Hearn wrote: > > The only thing that bit me was that I used wd0 and wd2 with the older > driver, whereas the newer driver automatically decided to use ad0 and > ad1. This is "expected" behaviour, but it's something for other weenies > to watch out for. :-)
I warned about that in the anounce :) > Sadly, cdcontrol still doesn't work with the newer driver and my > braindead Creative Labs Infra36 CDROM drive. My older quad speed HITACHI > still works. I noticed that the error message has changed, though. I > used to get > > cdcontrol> play > cdcontrol: Input/output error > > Now I get > > cdcontrol> play > cdcontrol: Unknown error: 84 Hmm, you could try to enable the debug in atapi-all.c & atapi-cd.c and mail me the output of that. The unknown error is because the new driver doesn't translate the atapi errors to errno errors yet. > I guess no amount of programmer cleverness is going to get around crap > hardware. Still, if you want me to try things with the hardware I've > got, I'm happy to try. I'd offer you shell access, but South African > connectivity isn't the best. :-) :) lets see what we can do before that, I still have alot of little things I need to get in there, this is just to get people banging on the driver to get feedback early in the development cycle. -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
