I am trying to get a PCI SCSI card connected to a SCSI CD-ROM drive to work. I believe the devices are OK and I can see the card under PCI devices in hardware but cannot see any disk when one is in the drive.
I recall issues in the past about slots being an issue and also interrupts, SCSI address, and no doubt I have forgotten much more. Does anybody have time to help me get this working please?
Budgie2
Further to the above, the Yast Hardware Info shows the SCSI card under the PCI tab and describes it correctly but does not mention the attached drive.
I had installed the PCI SCSI card after the OS (12.3, 86x64, KDE) was installed and up to date. I thought perhaps there might be a detection problem so I tried a new installation of openSUSE 12.3 with the PCI SCSI card in place and this time the installation stalled. Is this possibly an address conflict? Very much in the dark here!
Budgie2
On Sun, 09 Jun 2013 15:56:01 +0000, Budgie2 wrote:
> Further to the above, the Yast Hardware Info shows the SCSI card under
> the PCI tab and describes it correctly but does not mention the attached
> drive.
>
> I had installed the PCI SCSI card after the OS (12.3, 86x64, KDE) was
> installed and up to date. I thought perhaps there might be a detection
> problem so I tried a new installation of openSUSE 12.3 with the PCI SCSI
> card in place and this time the installation stalled. Is this possibly
> an address conflict? Very much in the dark here!
>
> Budgie2
Might be useful to know what brand the card in question is. 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Hi Jim,
Sorry and yes of course. The card is DPT PM2144W and at present I have a TEAC SCSI CD-ROM attached, which is what it had in the machine which died. Once I get it working I plan to use it to read each of the old SCSI the RAID drives, one at a time, so I can recover my data.
As far as I have been able to determine it should use the modprobe eata-dma kernel module but what is loaded and shows on hardware info is modprobe eata. It also says Driver no. If you need the hardware info download file I could upload it for you if it would help!
The mobo is Asus P8H77-V LE with i5-3507K processor and 16 GB memory. Board is new and I have not tried to update BIOS which is presently version 0803.
Have not found any answers yet with google. Hope you can help.
Regards,
Budgie
On Mon, 10 Jun 2013 20:46:01 +0000, Budgie2 wrote:
> Hi Jim,
> Sorry and yes of course. The card is DPT PM2144W and at present I have a
> TEAC SCSI CD-ROM attached, which is what it had in the machine which
> died. Once I get it working I plan to use it to read each of the old
> SCSI the RAID drives, one at a time, so I can recover my data.
>
> As far as I have been able to determine it should use the modprobe
> eata-dma kernel module but what is loaded and shows on hardware info is
> modprobe eata. It also says Driver no. If you need the hardware info
> download file I could upload it for you if it would help!
>
> The mobo is Asus P8H77-V LE with i5-3507K processor and 16 GB memory.
> Board is new and I have not tried to update BIOS which is presently
> version 0803.
>
> Have not found any answers yet with google. Hope you can help.
What are the outputs of:
lsmod
and
lsscsi
?
I determined what you did as well about it needing the eata-dma kernel
module, eata was reported not to work with that card (but that was kernel
version 1.2.something). It may be that that particular controller is no
longer supported/available (I had thought DPT was bought/went out of
business years ago, looks like Adaptec bought them, and they’re now owned
by a company called PMC).
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Hi Jim,
I knew DPT had been swallowed by Adaptec but not the latest take over. Although DPT name disappeared Adaptec supported these cards for a while and probably re-badged them later.
Here is the result of lsmod:-
lsmod
Module Size Used by
lp 17760 0
parport_pc 37266 0
ppdev 17679 0
parport 46311 3 lp,parport_pc,ppdev
st 44369 0
af_packet 39587 0
fuse 87139 3
joydev 17378 0
bnep 19702 2
bluetooth 341895 7 bnep
xt_tcpudp 12885 2
xt_pkttype 12505 3
xt_LOG 17522 10
xt_limit 12712 10
ip6t_REJECT 12940 3
nf_conntrack_ipv6 14684 3
nf_defrag_ipv6 18262 1 nf_conntrack_ipv6
ip6table_raw 12684 1
ipt_REJECT 12542 3
iptable_raw 12679 1
xt_CT 12869 4
iptable_filter 12811 1
ip6table_mangle 12701 0
nf_conntrack_netbios_ns 12666 0
nf_conntrack_broadcast 12590 1 nf_conntrack_netbios_ns
nf_conntrack_ipv4 15013 3
nf_defrag_ipv4 12730 1 nf_conntrack_ipv4
ip_tables 27240 2 iptable_raw,iptable_filter
xt_conntrack 12761 6
nf_conntrack 98519 6 nf_conntrack_ipv6,xt_CT,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ipv4,xt_conntrack
ip6table_filter 12816 1
ip6_tables 27208 3 ip6table_raw,ip6table_mangle,ip6table_filter
x_tables 34060 15 xt_tcpudp,xt_pkttype,xt_LOG,xt_limit,ip6t_REJECT,ip6table_raw,ipt_REJECT,iptable_raw,xt_CT,iptable_filter,ip6table_mangle,ip_tables,xt_conntrack,ip6table_filter,ip6_tables
acpi_cpufreq 19572 0
mperf 12668 1 acpi_cpufreq
coretemp 13394 0
kvm 475491 0
crc32c_intel 12902 0
ghash_clmulni_intel 13260 0
aesni_intel 55441 0
ablk_helper 13598 1 aesni_intel
cryptd 16307 3 ghash_clmulni_intel,aesni_intel,ablk_helper
lrw 13287 1 aesni_intel
aes_x86_64 17256 1 aesni_intel
xts 12915 1 aesni_intel
gf128mul 14952 2 lrw,xts
eeepc_wmi 13152 0
asus_wmi 28310 1 eeepc_wmi
sparse_keymap 13891 1 asus_wmi
rfkill 26530 3 bluetooth,asus_wmi
pci_hotplug 35160 1 asus_wmi
snd_hda_codec_hdmi 40844 1
snd_hda_codec_realtek 82329 1
snd_hda_intel 42034 3
snd_hda_codec 147417 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 13603 1 snd_hda_codec
snd_pcm 110154 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_seq 69780 0
iTCO_wdt 13481 0
iTCO_vendor_support 13719 1 iTCO_wdt
snd_timer 29371 2 snd_pcm,snd_seq
snd_seq_device 14498 1 snd_seq
snd 91489 15 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device
wmi 19071 1 asus_wmi
lpc_ich 17062 0
mfd_core 13436 1 lpc_ich
sr_mod 22296 0
cdrom 46688 1 sr_mod
soundcore 15048 1 snd
r8169 67643 0
snd_page_alloc 18711 2 snd_hda_intel,snd_pcm
i2c_i801 22440 0
mei 79557 0
microcode 35785 0
pcspkr 12719 0
sg 36525 0
autofs4 42771 2
thermal 18712 0
i915 605629 3
drm_kms_helper 50840 1 i915
xhci_hcd 103975 0
drm 293115 4 i915,drm_kms_helper
i2c_algo_bit 13414 1 i915
button 13953 1 i915
video 19401 2 asus_wmi,i915
fan 13003 0
processor 44950 1 acpi_cpufreq
thermal_sys 24957 4 thermal,video,fan,processor
scsi_dh_emc 17259 0
scsi_dh_rdac 17409 0
scsi_dh_hp_sw 12895 0
scsi_dh_alua 17162 0
scsi_dh 14844 4 scsi_dh_emc,scsi_dh_rdac,scsi_dh_hp_sw,scsi_dh_alua
ata_generic 12911 0
ata_piix 35039 3
and here is the output from lsscsi:-
lsscsi
[0:0:0:0] disk ATA ST32000645NS 0004 /dev/sda
[0:0:1:0] cd/dvd HL-DT-ST DVDRAM GH24NS90 IN01 /dev/sr0
strange but I cannot see the eata module listed although Yast Hardware Info still gives the module as loaded.
Any other tests I can try?
Regards,
Budgie2
Hi Jim,
Have you given up on this one or just too busy?
Any ideas where I might find further help please.
Regards,
Budgie2
I can’t help you in detail but you probably need to mount it ie make it auto mount discs. Have a look through YAST. :sarcastic: I had to do this recently for a 1tb disc in a usb hub. I used a linux disc format and set to user. Think the facilities for that are in partitioning. Maybe auto mounting dvd’s is too.
It sometimes irk’s me that an install sorts this sort of thing out easily as linux recognises just about every controller known to man since the year dot - some looking around is needed if things are added later. My 6 bay hot swap unit comes up in the same place as a memory stick etc does in the desktop removable devices list lol! have to remember not to set it for removal. That’s where my home dir is.
On Sat, 15 Jun 2013 10:16:03 +0000, Budgie2 wrote:
> Hi Jim,
> Have you given up on this one or just too busy? Any ideas where I might
> find further help please.
> Regards,
> Budgie2
I haven’t given up, just got really busy with work-related projects, and
I knew this was going to take more concentrated effort - sorry, I should
have said something.
Let’s have a look at the output from “lspci -k” and see what driver it
thinks it is using. That might be enlightening. (Clip out the other
devices from the output, since those aren’t relevant)
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Hi Jim,
Your situation understood. Thanks for getting back to me.
Here is the snipped result of lspci -k after I have booted with card installed:
05:00.0 SCSI storage controller: Adaptec (formerly DPT) SmartCache/Raid I-IV Controller (rev 02)
One problem I have is that I cannot see the whole BIOS setting screen because the resolution shows only 1/4 of the screen. I had in mind to see if interrupts could be changed, thinking of possible conflicts.
How may I pan around this using keyboard? I asked the mobo supplier and all he could suggest was try a different monitor!
Hope this helps.
Regards,
Budgie2
On Sun, 16 Jun 2013 14:46:01 +0000, Budgie2 wrote:
> Here is the snipped result of lspci -k after I have booted with card
> installed:
>
>
> Code:
> --------------------
> 05:00.0 SCSI storage controller: Adaptec (formerly DPT)
> SmartCache/Raid I-IV Controller (rev 02)
> --------------------
Odd, there’s no driver mentioned.
There’s no “Kernel driver in use” line associated with this entry?
That would explain, I guess, why the drive isn’t being seen.
If you have different slots in the system, I seem to recall that on some
systems with PCI cards, you could force an interrupt change by changing
the slot. There was a reason, but I don’t recall at the moment why that
worked.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Hi Jim,
Thanks again. Tried another slot and still no driver loaded. There is only on more slot to try and I believe I have tried it once before with same result. Will check again though.
Is there anywhere else we can look for solution?
Grateful for all further suggestions.
Regards,
Budgie2
On Tue, 18 Jun 2013 22:36:01 +0000, Budgie2 wrote:
> Is there anywhere else we can look for solution?
The only other thoughts I have about where to ask would be on the mailing
list (where there tend to be more developers) or to start digging in the
Linux kernel mailing list and see if there’s any discussion of the card
there.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
do you have a terminator to end scsi bus?
Hi Jim,
what and where is “the mailing list” please?
Hi and thanks for the question. Yes, I believe termination is correct but will check again.
Still no joy with this but one more question. The card I have is a PCI card but comes from the 32 bit era. Could it be the PCI slots on new mobo are 64 bit and this is cause of problem or do 64 bit systems sort this out?
Budgie2