Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!wantree.com.au!usenet From: ahunt@wantree.com.au (Andrew Hunt) Newsgroups: comp.unix.bsd.freebsd.misc Subject: matcd driver problem Date: 5 Oct 1995 06:21:47 GMT Organization: Wantree Development Lines: 25 Message-ID: <44vthr$1fq@vector.wantree.com.au> NNTP-Posting-Host: dialin11.wantree.com.au X-Newsreader: WinVN 0.92.6+ Has anyone seen the following problem with the 'matcd' cdrom driver during bootup: Oct 5 09:50:59 numbat /kernel: After reading status byte, bus didn't go idle 27 f 230 Oct 5 09:50:59 numbat /kernel: matcd3: Next status byte is ff Oct 5 09:50:59 numbat /kernel: matcd3: get_stat: After reading status byte, bus didn't go idle ff f 2 It seems like the driver is expecting to get 0xff back from the status register, but its getting 0x0f instead. I've tryed recompiling the driver with debug information, but this doesn't tell me very much. The interface card is a recently bought Creative Labs Sound Blaster/16. The model number on the card is CT2660. The drive works fine under DOS and windows. Any pointers or suggestions would be appretiated. Regards Andrew Hunt