[S.u.S.E. Linux] Microtek E-6 installation?
I've tried to get SuSE Linux 5.2 to recognize my Adaptec 1502AE controller card via YaST (using the install SCSI modules feature of the installation disk), but no matter what settings I try for the 'aha152x' it says they are incorrect. Can someone with a similar setup suggest parameters to try here. I tried (among others) 'aha152x=0x340,9,7' to no avail. My scanner is default set to SCSI device #6, and I've never changed this. I tried using insmod to install the aha152x, but all it keeps saying is 'device is busy'. This is surprising, since nothing else (as in YaST for instance) seems to acknowledge the existence of the device. Installing the SCSI kernel for aha152x did nothing to help either. On boot up I get the message 'SCSI devices:0'. Using YaST off the hard drive to 'install new hardware' only gives me a nasty red message "no SCSI device detected", and offers no set-up at all (as in a suggestion to install a module...).
From Win95 I can see that the card is on IRQ 9, with an I/O range of 0140-015F. Works fine in Win95, but I'm trying to become MS free.
Lawrence Sayre <lsayre@integrityonline13.com> -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hello Isayre, try this from the bash prompt - modprobe aha152x aha152x=0x340,9 To make sure it worked type - cat /proc/scsi/scsi This should list your attached devices. Beside model it should show Scanner 600 Hope this helps lsayre wrote:
I've tried to get SuSE Linux 5.2 to recognize my Adaptec 1502AE controller card via YaST (using the install SCSI modules feature of the installation disk), but no matter what settings I try for the 'aha152x' it says they are incorrect. Can someone with a similar setup suggest parameters to try here. I tried (among others) 'aha152x=0x340,9,7' to no avail. My scanner is default set to SCSI device #6, and I've never changed this.
I tried using insmod to install the aha152x, but all it keeps saying is 'device is busy'. This is surprising, since nothing else (as in YaST for instance) seems to acknowledge the existence of the device.
Installing the SCSI kernel for aha152x did nothing to help either. On boot up I get the message 'SCSI devices:0'.
Using YaST off the hard drive to 'install new hardware' only gives me a nasty red message "no SCSI device detected", and offers no set-up at all (as in a suggestion to install a module...).
From Win95 I can see that the card is on IRQ 9, with an I/O range of 0140-015F. Works fine in Win95, but I'm trying to become MS free.
Lawrence Sayre <lsayre@integrityonline13.com>
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi Edward; When I tried what you suggested, the response was: "Device or resource busy". I'm beginning to think that Linux has already installed something else on int#9? Since my SCSI scanner card must be jumpered for int#9 to work in Win95, is there a way in Linux to check what might be on int#9, and then check for an open int#, and move this to the open one, so #9 will be available for my scanner? Lawrence Sayre Edward Smith wrote:
Hello Isayre,
try this from the bash prompt - modprobe aha152x aha152x=0x340,9
To make sure it worked type - cat /proc/scsi/scsi This should list your attached devices.
Beside model it should show Scanner 600
Hope this helps
lsayre wrote:
I've tried to get SuSE Linux 5.2 to recognize my Adaptec 1502AE controller card via YaST (using the install SCSI modules feature of the installation disk), but no matter what settings I try for the 'aha152x' it says they are incorrect. Can someone with a similar setup suggest parameters to try here. I tried (among others) 'aha152x=0x340,9,7' to no avail. My scanner is default set to SCSI device #6, and I've never changed this.
I tried using insmod to install the aha152x, but all it keeps saying is 'device is busy'. This is surprising, since nothing else (as in YaST for instance) seems to acknowledge the existence of the device.
Installing the SCSI kernel for aha152x did nothing to help either. On boot up I get the message 'SCSI devices:0'.
Using YaST off the hard drive to 'install new hardware' only gives me a nasty red message "no SCSI device detected", and offers no set-up at all (as in a suggestion to install a module...).
From Win95 I can see that the card is on IRQ 9, with an I/O range of 0140-015F. Works fine in Win95, but I'm trying to become MS free.
Lawrence Sayre <lsayre@integrityonline13.com>
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
If it worked under Win 95 int 9 then it should work here also. To my knowlege Linux is not as of yet plug and pray. If you have plug and play bios though you may want to go into your bios and under your plug and play bios settings set int. 9 to legacy mode. Another thing you may want to check is the i/o your using are you shure it's 340 and not 140 mine is set at i/o 140 int 9. lsayre wrote:
Hi Edward;
When I tried what you suggested, the response was: "Device or resource busy". I'm beginning to think that Linux has already installed something else on int#9? Since my SCSI scanner card must be jumpered for int#9 to work in Win95, is there a way in Linux to check what might be on int#9, and then check for an open int#, and move this to the open one, so #9 will be available for my scanner?
Lawrence Sayre
Edward Smith wrote:
Hello Isayre,
try this from the bash prompt - modprobe aha152x aha152x=0x340,9
To make sure it worked type - cat /proc/scsi/scsi This should list your attached devices.
Beside model it should show Scanner 600
Hope this helps
lsayre wrote:
I've tried to get SuSE Linux 5.2 to recognize my Adaptec 1502AE controller card via YaST (using the install SCSI modules feature of the installation disk), but no matter what settings I try for the 'aha152x' it says they are incorrect. Can someone with a similar setup suggest parameters to try here. I tried (among others) 'aha152x=0x340,9,7' to no avail. My scanner is default set to SCSI device #6, and I've never changed this.
I tried using insmod to install the aha152x, but all it keeps saying is 'device is busy'. This is surprising, since nothing else (as in YaST for instance) seems to acknowledge the existence of the device.
Installing the SCSI kernel for aha152x did nothing to help either. On boot up I get the message 'SCSI devices:0'.
Using YaST off the hard drive to 'install new hardware' only gives me a nasty red message "no SCSI device detected", and offers no set-up at all (as in a suggestion to install a module...).
From Win95 I can see that the card is on IRQ 9, with an I/O range of 0140-015F. Works fine in Win95, but I'm trying to become MS free.
Lawrence Sayre <lsayre@integrityonline13.com>
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
You may have something here! I ran 'modprobe' using aha152x=0x140,9 and it seems to have worked. Now I just have to get the sane thing going! :) Thank you, Lawrence Sayre <lsayre@integrityonline13.com> Edward Smith wrote:
If it worked under Win 95 int 9 then it should work here also. To my knowlege Linux is not as of yet plug and pray. If you have plug and play bios though you may want to go into your bios and under your plug and play bios settings set int. 9 to legacy mode. Another thing you may want to check is the i/o your using are you shure it's 340 and not 140 mine is set at i/o 140 int 9.
lsayre wrote:
Hi Edward;
When I tried what you suggested, the response was: "Device or resource busy". I'm beginning to think that Linux has already installed something else on int#9? Since my SCSI scanner card must be jumpered for int#9 to work in Win95, is there a way in Linux to check what might be on int#9, and then check for an open int#, and move this to the open one, so #9 will be available for my scanner?
Lawrence Sayre
Edward Smith wrote:
Hello Isayre,
try this from the bash prompt - modprobe aha152x aha152x=0x340,9
To make sure it worked type - cat /proc/scsi/scsi This should list your attached devices.
Beside model it should show Scanner 600
Hope this helps
lsayre wrote:
I've tried to get SuSE Linux 5.2 to recognize my Adaptec 1502AE controller card via YaST (using the install SCSI modules feature of the installation disk), but no matter what settings I try for the 'aha152x' it says they are incorrect. Can someone with a similar setup suggest parameters to try here. I tried (among others) 'aha152x=0x340,9,7' to no avail. My scanner is default set to SCSI device #6, and I've never changed this.
I tried using insmod to install the aha152x, but all it keeps saying is 'device is busy'. This is surprising, since nothing else (as in YaST for instance) seems to acknowledge the existence of the device.
Installing the SCSI kernel for aha152x did nothing to help either. On boot up I get the message 'SCSI devices:0'.
Using YaST off the hard drive to 'install new hardware' only gives me a nasty red message "no SCSI device detected", and offers no set-up at all (as in a suggestion to install a module...).
From Win95 I can see that the card is on IRQ 9, with an I/O range of 0140-015F. Works fine in Win95, but I'm trying to become MS free.
Lawrence Sayre <lsayre@integrityonline13.com>
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (2)
-
esmith＠onlink.net -
lsayre＠integrityonline13.com