aic7xxx 6.1.5 in kernel 2.4.3 doesn't recognize Yamaha CDRW

[Andreas M. Kirchwitz]

Hello!

In case somebody is interested ...

The new Adaptec SCSI host-adapter driver "aic7xxx 6.1.5" in
Linux kernel 2.4.3 (compiled on a RedHat 7.0 system) doesn't
recognize my Yamaha CRW4416S CD-ReWriter. It also outputs some
error messages saying "request_module[scsi_hostadapter]:
Root fs not mounted".

It worked fine with the old aic7xxx 5.x driver in kernel 2.4.2.

After fetching the new aic7xxx 6.1.11 driver from
http://people.FreeBSD.org/~gibbs/linux/ and applying
the patch to a vanilla 2.4.3 kernel source tree,
everything was fine again. The error messages disappeared
and my Yamaha CD-ReWriter was recognized.

Looks like the aic7xxx 6.1.5 driver shipped with kernel 2.4.3
isn't a good choice. ;-)

Excerpt from /var/log/messages with vanilla Linux kernel 2.4.3
and built-in aic7xxx 6.1.5 driver:

  Apr 11 22:03:51 lakai kernel: SCSI subsystem driver Revision: 1.00
  Apr 11 22:03:51 lakai kernel: request_module[scsi_hostadapter]: Root fs not mounted
  Apr 11 22:03:51 lakai kernel: request_module[scsi_hostadapter]: Root fs not mounted
  Apr 11 22:03:51 lakai kernel: request_module[scsi_hostadapter]: Root fs not mounted
  Apr 11 22:03:51 lakai kernel: PCI: Found IRQ 9 for device 02:0b.0
  Apr 11 22:03:51 lakai kernel: PCI: The same IRQ used for device 01:00.0
  Apr 11 22:03:51 lakai kernel: PCI: The same IRQ used for device 02:09.0
  Apr 11 22:03:51 lakai kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, 
Rev 6.1.5
  Apr 11 22:03:51 lakai kernel: 
  Apr 11 22:03:51 lakai kernel: aic7870: Single Channel A, SCSI Id=7, 16/255 
SCBs
  Apr 11 22:03:51 lakai kernel:
  Apr 11 22:03:51 lakai kernel:   Vendor: IBM   Model: DCAS-34330Rev: S65A
  Apr 11 22:03:51 lakai kernel:   Type:   Direct-Access  ANSI SCSI 
revision: 02
  Apr 11 22:03:51 lakai kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
  Apr 11 22:03:51 lakai kernel: scsi0:0:0:0: Tagged Queuing enabled.  Depth 8
  Apr 11 22:03:51 lakai kernel: (scsi0:A:0): 10.000MB/s transfers (10.000MHz, offset 
15)
  Apr 11 22:03:51 lakai kernel: SCSI device sda: 8467200 512-byte hdwr sectors (4335 
MB)
  Apr 11 22:03:51 lakai kernel:  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 
sda12 >

Excerpt from /var/log/messages with aic7xxx 6.1.11 patch applied
to vanilla kernel 2.4.3 source tree:

  Apr 12 00:00:52 lakai kernel: SCSI subsystem driver Revision: 1.00
  Apr 12 00:00:52 lakai kernel: PCI: Found IRQ 9 for device 02:0b.0
  Apr 12 00:00:52 lakai kernel: PCI: The same IRQ used for device 01:00.0
  Apr 12 00:00:52 lakai kernel: PCI: The same IRQ used for device 02:09.0
  Apr 12 00:00:52 lakai kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, 
Rev 6.1.11
  Apr 12 00:00:52 lakai kernel: 
  Apr 12 00:00:52 lakai kernel: aic7870: Single Channel A, SCSI Id=7, 16/255 
SCBs
  Apr 12 00:00:52 lakai kernel:
  Apr 12 00:00:52 lakai kernel:   Vendor: IBM   Model: DCAS-34330Rev: S65A
  Apr 12 00:00:52 lakai kernel:   Type:   Direct-Access  ANSI SCSI 
revision: 02
  Apr 12 00:00:53 lakai kernel:   Vendor: YAMAHAModel: CRW4416S  Rev: 1.0f
  Apr 12 00:00:53 lakai kernel:   Type:   CD-ROM ANSI SCSI 
revision: 02
  Apr 12 00:00:53 lakai kernel: scsi0:0:0:0: Tagged Queuing enabled.  Depth 253
  Apr 12 00:00:53 lakai kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
  Apr 12 00:00:53 lakai kernel: (scsi0:A:0): 10.000MB/s transfers (10.000MHz, offset 
15)
  Apr 12 00:00:53 lakai kernel: SCSI device sda: 8467200 512-byte hdwr sectors (4335 
MB)
  Apr 12 00:00:53 lakai kernel:  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 
sda12 >
  Apr 12 00:00:53 lakai kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 5, 
lun 0
  Apr 12 00:00:53 lakai kernel: (scsi0:A:5): 8.333MB/s transfers (8.333MHz, offset 15)
  Apr 12 00:00:53 lakai kernel: sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 
cdda tray


Regards,
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] fix emu10k1 init breakage in 2.2.18

[Andreas M. Kirchwitz]

Juri Haberland wrote:

 >>> 2.2.18 broke the emu10k1 driver when compiled into the kernel.
 >> 
 >> Is there also a fix available to make the bass and treble settings
 >> work again in mixer applications (for example, Gnome mix 1.2.0)?
 > 
 > Yes, put something like "EXTRA_CFLAGS += -DTONE_CONTROL" into the
 > Makefile in drivers/sound/emu10k1/

Ah, TONE_CONTROL... yeah, that's it. Do you know the reason why
bass/treble controls are disabled by default? Aren't they stable
enough for production use?

I'm just wondering why anybody wants to have this turned off. ;-)

Greetings from Berlin to Berlin ... Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] fix emu10k1 init breakage in 2.2.18

[Andreas M. Kirchwitz]

Juri Haberland wrote:

  2.2.18 broke the emu10k1 driver when compiled into the kernel.
  
  Is there also a fix available to make the bass and treble settings
  work again in mixer applications (for example, Gnome mix 1.2.0)?
  
  Yes, put something like "EXTRA_CFLAGS += -DTONE_CONTROL" into the
  Makefile in drivers/sound/emu10k1/

Ah, TONE_CONTROL... yeah, that's it. Do you know the reason why
bass/treble controls are disabled by default? Aren't they stable
enough for production use?

I'm just wondering why anybody wants to have this turned off. ;-)

Greetings from Berlin to Berlin ... Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] fix emu10k1 init breakage in 2.2.18

[Andreas M. Kirchwitz]

Mikael Pettersson wrote:

 > 2.2.18 broke the emu10k1 driver when compiled into the kernel.
 > The problem is that 2.2.18 now implements 2.4-style module_init,
 > so emu10k1 ended up being initialised twice when built non-modular,
 > which rendered it dysfunctional. The fix is to remove the now
 > obsolete explicit init calls. Patch below. Please apply.

Is there also a fix available to make the bass and treble settings
work again in mixer applications (for example, Gnome mix 1.2.0)?
This is (now, was) one of the biggest advantages of this card to have
control over bass and treble settings. 

It worked for the early 2.2.18pre patches, but stopped working in
the latest ones (including final 2.2.18).

Greetings, Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] fix emu10k1 init breakage in 2.2.18

[Andreas M. Kirchwitz]

Mikael Pettersson wrote:

  2.2.18 broke the emu10k1 driver when compiled into the kernel.
  The problem is that 2.2.18 now implements 2.4-style module_init,
  so emu10k1 ended up being initialised twice when built non-modular,
  which rendered it dysfunctional. The fix is to remove the now
  obsolete explicit init calls. Patch below. Please apply.

Is there also a fix available to make the bass and treble settings
work again in mixer applications (for example, Gnome mix 1.2.0)?
This is (now, was) one of the biggest advantages of this card to have
control over bass and treble settings. 

It worked for the early 2.2.18pre patches, but stopped working in
the latest ones (including final 2.2.18).

Greetings, Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/