Hello to the list. Have been fighting this problem for several weeks now, trying to get my scanner working in 7.1 Am running the 2.4.7 mantel kernel. Have an Artec A6000C plus. The scanner is supported. Originally tried to set it up with the scsi card that was supplied by Artec. That was a dtc3181e. Followed directions from the Sane site on setting it up. Wouldn't work. Bottom line.... pulled that card out and obtained an Adaptec AVA 1505/1515/152x. Now, I have been led to believe that the only difference between the AVA and the AHA card is that the AHA card is for an ATC board. Anyway, I cannot load the aha152x module. When I do a modprobe of the card with or without parms I get a message "Hint: insmod errors can be caused by incorrect module parameters, including invalid IO of IRQ parameters" Have tried every combination of parms that I could think of. Windoze id's the card address as "0340-035F, IRQ 9" The aha152x is loaded in the kernel as a module. Have also tried loading it at the command line, "linux aha152x=0x340,9" and as an append statement in lilo, and in /etc/modules conf with an options statement: "alias scsi_hostadapter aha152x" "options aha152x aha152x=0x340,9" Back in the beginning of Sept. there was an exchange re: the aha1542c. A statement was made that the parms for thewse cards are Boot parms, not Module parms. What is the difference and how would that effect how it loads. Very confusing and very frustrating, I am sure that it is probably just a matter of incorrect syntax. Somebody help me out here? Bob S.
On Sunday 09 December 2001 22:15 pm, Bob Stia wrote:
Hello to the list.
Have been fighting this problem for several weeks now, trying to get my scanner working in 7.1 Am running the 2.4.7 mantel kernel.
Have an Artec A6000C plus. The scanner is supported. Originally tried to set it up with the scsi card that was supplied by Artec. That was a dtc3181e. Followed directions from the Sane site on setting it up. Wouldn't work. Bottom line.... pulled that card out and obtained an Adaptec AVA 1505/1515/152x. Now, I have been led to believe that the only difference between the AVA and the AHA card is that the AHA card is for an ATC board. Anyway, I cannot load the aha152x module.
When I do a modprobe of the card with or without parms I get a message "Hint: insmod errors can be caused by incorrect module parameters, including invalid IO of IRQ parameters" Have tried every combination of parms that I could think of. Windoze id's the card address as "0340-035F, IRQ 9"
The aha152x is loaded in the kernel as a module. Have also tried loading it at the command line, "linux aha152x=0x340,9" and as an append statement in lilo, and in /etc/modules conf with an options statement: "alias scsi_hostadapter aha152x" "options aha152x aha152x=0x340,9"
Back in the beginning of Sept. there was an exchange re: the aha1542c. A statement was made that the parms for thewse cards are Boot parms, not Module parms. What is the difference and how would that effect how it loads.
Very confusing and very frustrating, I am sure that it is probably just a matter of incorrect syntax. Somebody help me out here?
Bob S.
If your card truely will operate with the aha152x driver and it truely is at that address and irq, then try: modprobe aha152x aha152x=0x0340,9 That's the proper command. If it doesn't work, then something isn't set up right. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 12/09/01 23:21 + +----------------------------------------------------------------------------+ "It is impossible to enjoy idling thoroughly unless one has plenty of work to do."
I just bought a new scsi card today. The card, of course, came with a
CD with Windows drivers and no clue as to how to make the card work
with Linux. Nevertheless, I got it working, using the "brute force"
method, and this might work for you too (Bob).
cd into directory /lib/modules/2.4.4-4GB/kernel/drivers/scsi/
then type "ls" and you'll get something like this:
. aic7xxx g_NCR5380.o pci2220i.o sparcsi.o
.. aic7xxx_old.o gdth.o ppa.o st.o
3w-xxxx.o atp870u.o ide-scsi.o ppscsi.o sym53c416.o
53c7,8xx.o dc395x_trm.o imm.o psi240i.o sym53c8xx.o
AM53C974.o dmx3191d.o in2000.o qla1280.o t128.o
BusLogic.o dpt_i2o.o initio.o qla2x00.o t348.o
NCR53c406a.o dtc.o ips.o qlogicfas.o t358.o
a100u2w.o eata.o megaraid.o qlogicfc.o tmscsim.o
aacraid.o eata_dma.o ncr53c8xx.o qlogicisp.o u14-34f.o
advansys.o eata_pio.o onscsi.o scsi_debug.o ultrastor.o
aha152x.o epsa2.o osst.o seagate.o vpi0.o
aha1542.o epst.o pas16.o sg.o wd7000.o
aha1740.o fdomain.o pci2000.o sim710.o
As root, modprobe each module (leave off the trailing ".o") until you
find one that works (if the driver is wrong, you'll get an immediate
error message). I got lucky on the 14th attempt. Not very scientific,
but it works.
- Robert Storey
On Sun, 9 Dec 2001 23:25:26 -0500
Bruce Marshall
On Sunday 09 December 2001 22:15 pm, Bob Stia wrote:
Hello to the list.
Have been fighting this problem for several weeks now, trying to get my scanner working in 7.1 Am running the 2.4.7 mantel kernel.
Have an Artec A6000C plus. The scanner is supported. Originally tried to set it up with the scsi card that was supplied by Artec. That was a dtc3181e. Followed directions from the Sane site on setting it up. Wouldn't work. Bottom line.... pulled that card out and obtained an Adaptec AVA 1505/1515/152x. Now, I have been led to believe that the only difference between the AVA and the AHA card is that the AHA card is for an ATC board. Anyway, I cannot load the aha152x module.
When I do a modprobe of the card with or without parms I get a message "Hint: insmod errors can be caused by incorrect module parameters, including invalid IO of IRQ parameters" Have tried every combination of parms that I could think of. Windoze id's the card address as "0340-035F, IRQ 9"
The aha152x is loaded in the kernel as a module. Have also tried loading it at the command line, "linux aha152x=0x340,9" and as an append statement in lilo, and in /etc/modules conf with an options statement: "alias scsi_hostadapter aha152x" "options aha152x aha152x=0x340,9"
Back in the beginning of Sept. there was an exchange re: the aha1542c. A statement was made that the parms for thewse cards are Boot parms, not Module parms. What is the difference and how would that effect how it loads.
Very confusing and very frustrating, I am sure that it is probably just a matter of incorrect syntax. Somebody help me out here?
Bob S.
If your card truely will operate with the aha152x driver and it truely is at that address and irq, then try:
modprobe aha152x aha152x=0x0340,9
That's the proper command. If it doesn't work, then something isn't set up right.
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 12/09/01 23:21 + +----------------------------------------------------------------------------+
On Sunday 09 December 2001 11:25 pm, Bruce Marshall wrote:
On Sunday 09 December 2001 22:15 pm, Bob Stia wrote:
Have been fighting this problem for several weeks now, trying to get my scanner working in 7.1 Am running the 2.4.7 mantel kernel.
If your card truely will operate with the aha152x driver and it truely is at that address and irq, then try:
modprobe aha152x aha152x=0x0340,9
That's the proper command. If it doesn't work, then something isn't set up right.
Bruce, Thank You. Proper command in my case was "modprobe aha152x aha152x=0x0340" No IRQ requirement. Now all I have to do is set the scanner up properly. Thanks again. Robert, Appreciated your input. Problem solved. Bob S.
participants (3)
-
Bob Stia
-
Bruce Marshall
-
Robert Storey