hello,
i know that the 2.0.3.7 driver for the this card works...
but i have 2.4.7...i know the structure of driver code
changed some. can anyone help rewriting the 2.0.3.7
driver to work with 2.4.7....the >2.0.3.7 has been reported
not working, but my success at finding useful
info ends there...
i tried rewriting it myself...i cannot get it to insmod.
it just hangs...can anyone help? i am not very
knowledgeable of the scsi driver code ;-(
--sam
> i tried rewriting it myself...i cannot get it to insmod.
> it just hangs...can anyone help? i am not very
> knowledgeable of the scsi driver code ;-(
Umm the atp870u is supported in 2.2 and 2.4 by the default kernels.
On Sat, Jan 05, 2002 at 01:27:29AM +0000, Alan Cox wrote:
> > i tried rewriting it myself...i cannot get it to insmod.
> > it just hangs...can anyone help? i am not very
> > knowledgeable of the scsi driver code ;-(
>
> Umm the atp870u is supported in 2.2 and 2.4 by the default kernels.
something about 4 month ago I had a card like this one.
I put it in my desktop and couldn't load the module( no crash).
I don't remember the error but I can get it back into my desktop and
have some test with it. I was problably using 2.4.7 at this time (
vanilla compiled by me , not the debian one ).
Sam
Alan Cox wrote:
>> i tried rewriting it myself...i cannot get it to insmod.
>> it just hangs...can anyone help? i am not very
>> knowledgeable of the scsi driver code ;-(
>>
>
> Umm the atp870u is supported in 2.2 and 2.4 by the default kernels.
...so one would think...yes it is supported technically, and the atp870u
driver does exist...but the 2.4 one does not work, that is a known fact.
browsing the forums, it seems that people were complaining about
>2037 not working, but that the original one worked just fine.
some of the code has a different format in 2.4 than 2.2 and 2.0,
mostly the external stuff to load as modules...etc, but i can't get it
to work.
so i needed help porting the old one into the new 2.4 framework
if you will.
regards,
--sam
Alan Cox wrote:
>> i tried rewriting it myself...i cannot get it to insmod.
>> it just hangs...can anyone help? i am not very
>> knowledgeable of the scsi driver code ;-(
>>
>
> Umm the atp870u is supported in 2.2 and 2.4 by the default kernels.
...so one would think...yes it is supported technically, and the atp870u
driver does exist...but the 2.4 one does not work, that is a known fact.
browsing the forums, it seems that people were complaining about
>2037 not working, but that the original one worked just fine.
some of the code has a different format in 2.4 than 2.2 and 2.0,
mostly the external stuff to load as modules...etc, but i can't get it
to work.
so i needed help porting the old one into the new 2.4 framework
if you will.
regards,
--sam
> > Umm the atp870u is supported in 2.2 and 2.4 by the default kernels.
>
> ...so one would think...yes it is supported technically, and the atp870u
> driver does exist...but the 2.4 one does not work, that is a known fact.
Which tree, and what compiler
> some of the code has a different format in 2.4 than 2.2 and 2.0,
> mostly the external stuff to load as modules...etc, but i can't get it
> to work.
> so i needed help porting the old one into the new 2.4 framework
> if you will.
I think you need to work out why the newer one is failing on your specific
hardware. Standard Red Hat kernel....
aec671x_detect:
PCI: Found IRQ 10 for device 00:08.0
ACARD AEC-671X PCI Ultra/W SCSI-3 Host Adapter: 0 IO:d800, IRQ:10.
ID: 2 HP C1537A L105
ID: 5 IBM DSAS-3540 !WS47Y
ID: 7 Host Adapter
scsi0 : ACARD AEC-6710/6712/67160 PCI Ultra/W/LVD SCSI-3 Adapter Driver
V2.4+ac
Vendor: HP Model: C1537A Rev: L105
Type: Sequential-Access ANSI SCSI revision: 02
Vendor: IBM Model: DSAS-3540 !W Rev: S47Y
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 5, lun 0
SCSI device sda: 1056768 512-byte hdwr sectors (541 MB)
sda: sda1
Journalled Block Device driver loaded