Thread: Jmicron problem
View Single Post

   
  #2 (permalink)  
Old 02-21-2008, 05:36 AM
Robby Workman
 
Posts: n/a
Default Re: Jmicron problem

On 2007-09-26, occam@internode.razoron.net <occam@internode.razoron.net> wrote:
> In Slackware 12, the default huge kernel is configures with both
> CONFIG_BLK_DEV_JMICRON=y and CONFIG_PATA_JMICRON=m. This leads to
> large number of errors "hda: cdrom_pc_intr: The device appears
> confused (ireason=0x01)." and spurious messages eg that a new audio CD
> has been detected.
> Googling has told me that this can depend on having two (competing?)
> handlers for Jmicron, through which the (PATA) drive is connected.
> Since both are created in the stock Slackware kernel there must be a
> reason for it, and my obvious solution of compiling a new kernel with
> one handler (which one?) eliminated may cause other problems.
> The other solution is to get rid of the pata_jmicron module in some
> way.
> Any advice on which way to go?



echo "blacklist pata_jmicron" >> /etc/modprobe.d/blacklist

RW
Reply With Quote