Re: [SLE] Tape drive isn´t recognized!
Ok, My Tape drive is a Sony SDT-9000 If I go to /proc/scsi/scsi appears Attached devices: none if mt -f /dev/st0 status appears mt: /dev/st0: No such device my version is SuSE Linux 9.0 (i586) Kernel 2.4.21-273-smp4G / i686 ----- Original Message ----- From: "Sheridan West" <sjwest01@yahoo.co.uk> To: "Joni Hoppen" <joni@fundacentro.sc.gov.br> Sent: Thursday, March 10, 2005 9:20 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni
You need ide-scsi, and stick it your boot process (there is a suse help tech note)
I cannot get a Travan tape device to work in Suse 9.2, it works fine in Suse 8.2. In the end I gave up and bought a dvd rw.
Your post is short on detail
--- Joni Hoppen <joni@fundacentro.sc.gov.br> wrote:
I am trying to install a tape drive but the system dont recognize in /dev/st0 when I installed it before on another computer with kde is was so simple. What can i do to make it works in text mode?
Joni
Send instant messages to your online friends http://uk.messenger.yahoo.com
Joni Hoppen a écrit :
Ok,
My Tape drive is a Sony SDT-9000
If I go to /proc/scsi/scsi appears Attached devices: none if mt -f /dev/st0 status appears mt: /dev/st0: No such device
my version is SuSE Linux 9.0 (i586) Kernel 2.4.21-273-smp4G / i686
Hello, There could be a lot of reasons for that. So I've a few questions : - do you have other peripherals on your scsi controller? I'll suppose that the reply is no since you've nothing in /proc/scsi/scsi. - is SCSI tape support compiled as module in your kernel ? - is the scsi driver for your controller loaded at boot ? - if so is module st loaded? - if not did you try : modprobe st ? and last but not least : are your SCSI terminators OK ? - What is the type of your SCSI controller ? After reply, I'll try to help you, I've a DDS2 SCSI tape working. Michel.
----- Original Message ----- From: "Sheridan West" <sjwest01@yahoo.co.uk> To: "Joni Hoppen" <joni@fundacentro.sc.gov.br> Sent: Thursday, March 10, 2005 9:20 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni
You need ide-scsi, and stick it your boot process (there is a suse help tech note)
I cannot get a Travan tape device to work in Suse 9.2, it works fine in Suse 8.2. In the end I gave up and bought a dvd rw.
Your post is short on detail
--- Joni Hoppen <joni@fundacentro.sc.gov.br> wrote:
I am trying to install a tape drive but the system dont recognize in /dev/st0 when I installed it before on another computer with kde is was so simple. What can i do to make it works in text mode?
Joni
Send instant messages to your online friends http://uk.messenger.yahoo.com
Hi My scsi controle is HP Raid but now a changed for another one pci who i was using in another computer with the same tape drive I am using the module LSI / Symbios Logic 53c810 is SCSI tape support compiled as module in your kernel ? yes - is the scsi driver for your controller loaded at boot ? yes the result of modprob /dev/st0 is modprobe: Can't locate module /dev/st0 how can i do to know if the module is loaded? ----- Original Message ----- From: "Catimimi" <catimimi@libertysurf.fr> To: "Suse" <suse-linux-e@suse.com> Sent: Thursday, March 10, 2005 10:54 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni Hoppen a écrit :
Ok,
My Tape drive is a Sony SDT-9000
If I go to /proc/scsi/scsi appears Attached devices: none if mt -f /dev/st0 status appears mt: /dev/st0: No such device
my version is SuSE Linux 9.0 (i586) Kernel 2.4.21-273-smp4G / i686
Hello,
There could be a lot of reasons for that. So I've a few questions : - do you have other peripherals on your scsi controller? I'll suppose that the reply is no since you've nothing in /proc/scsi/scsi. - is SCSI tape support compiled as module in your kernel ? - is the scsi driver for your controller loaded at boot ? - if so is module st loaded? - if not did you try : modprobe st ?
and last but not least : are your SCSI terminators OK ?
- What is the type of your SCSI controller ?
After reply, I'll try to help you, I've a DDS2 SCSI tape working.
Michel.
----- Original Message ----- From: "Sheridan West" <sjwest01@yahoo.co.uk> To: "Joni Hoppen" <joni@fundacentro.sc.gov.br> Sent: Thursday, March 10, 2005 9:20 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni
You need ide-scsi, and stick it your boot process (there is a suse help tech note)
I cannot get a Travan tape device to work in Suse 9.2, it works fine in Suse 8.2. In the end I gave up and bought a dvd rw.
Your post is short on detail
--- Joni Hoppen <joni@fundacentro.sc.gov.br> wrote:
I am trying to install a tape drive but the system dont recognize in /dev/st0 when I installed it before on another computer with kde is was so simple. What can i do to make it works in text mode?
Joni
Send instant messages to your online friends http://uk.messenger.yahoo.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Joni Hoppen a écrit :
Hi My scsi controle is HP Raid but now a changed for another one pci who i was using in another computer with the same tape drive
I am using the module LSI / Symbios Logic 53c810
is SCSI tape support compiled as module in your kernel ? yes - is the scsi driver for your controller loaded at boot ? yes
the result of modprob /dev/st0 is modprobe: Can't locate module /dev/st0
how can i do to know if the module is loaded?
Hi, No, don't type : # modprobe /dev/st0 but : modprobe st "st" is the name of the module for scsi tapes. If you are replied " Can't locate module st" i'll mean that this module is not compiled. Try and tell me. Michel. PS : I just remember that "cat /proc/scsi/scsi" lists the generic scsi devices. Do you've support for generic scsi devices in your kernet ? and is module "sg" loaded at boot ?
----- Original Message ----- From: "Catimimi" <catimimi@libertysurf.fr> To: "Suse" <suse-linux-e@suse.com> Sent: Thursday, March 10, 2005 10:54 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni Hoppen a écrit :
Ok,
My Tape drive is a Sony SDT-9000
If I go to /proc/scsi/scsi appears Attached devices: none if mt -f /dev/st0 status appears mt: /dev/st0: No such device
my version is SuSE Linux 9.0 (i586) Kernel 2.4.21-273-smp4G / i686
Hello,
There could be a lot of reasons for that. So I've a few questions : - do you have other peripherals on your scsi controller? I'll suppose that the reply is no since you've nothing in /proc/scsi/scsi. - is SCSI tape support compiled as module in your kernel ? - is the scsi driver for your controller loaded at boot ? - if so is module st loaded? - if not did you try : modprobe st ?
and last but not least : are your SCSI terminators OK ?
- What is the type of your SCSI controller ?
After reply, I'll try to help you, I've a DDS2 SCSI tape working.
Michel.
----- Original Message ----- From: "Sheridan West" <sjwest01@yahoo.co.uk> To: "Joni Hoppen" <joni@fundacentro.sc.gov.br> Sent: Thursday, March 10, 2005 9:20 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni
You need ide-scsi, and stick it your boot process (there is a suse help tech note)
I cannot get a Travan tape device to work in Suse 9.2, it works fine in Suse 8.2. In the end I gave up and bought a dvd rw.
Your post is short on detail
--- Joni Hoppen <joni@fundacentro.sc.gov.br> wrote:
I am trying to install a tape drive but the system dont recognize in /dev/st0 when I installed it before on another computer with kde is was so simple. What can i do to make it works in text mode?
Joni
Send instant messages to your online friends http://uk.messenger.yahoo.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Ok I did modprob st and appears that its ok "no message" I dont have this /etc/stinit.def ..... what can i do ? it still doesnt working in /dev/st0 the model drive is a Sony SDT- 9000 ----- Original Message ----- From: "Catimimi" <catimimi@libertysurf.fr> To: "Suse" <suse-linux-e@suse.com> Sent: Thursday, March 10, 2005 11:47 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni Hoppen a écrit :
Hi My scsi controle is HP Raid but now a changed for another one pci who i was using in another computer with the same tape drive
I am using the module LSI / Symbios Logic 53c810
is SCSI tape support compiled as module in your kernel ? yes - is the scsi driver for your controller loaded at boot ? yes
the result of modprob /dev/st0 is modprobe: Can't locate module /dev/st0
how can i do to know if the module is loaded?
Hi,
No, don't type : # modprobe /dev/st0
but :
modprobe st
"st" is the name of the module for scsi tapes.
If you are replied " Can't locate module st" i'll mean that this module is not compiled.
Try and tell me.
Michel.
PS : I just remember that "cat /proc/scsi/scsi" lists the generic scsi devices. Do you've support for generic scsi devices in your kernet ? and is module "sg" loaded at boot ?
----- Original Message ----- From: "Catimimi" <catimimi@libertysurf.fr> To: "Suse" <suse-linux-e@suse.com> Sent: Thursday, March 10, 2005 10:54 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni Hoppen a écrit :
Ok,
My Tape drive is a Sony SDT-9000
If I go to /proc/scsi/scsi appears Attached devices: none if mt -f /dev/st0 status appears mt: /dev/st0: No such device
my version is SuSE Linux 9.0 (i586) Kernel 2.4.21-273-smp4G / i686
Hello,
There could be a lot of reasons for that. So I've a few questions : - do you have other peripherals on your scsi controller? I'll suppose that the reply is no since you've nothing in /proc/scsi/scsi. - is SCSI tape support compiled as module in your kernel ? - is the scsi driver for your controller loaded at boot ? - if so is module st loaded? - if not did you try : modprobe st ?
and last but not least : are your SCSI terminators OK ?
- What is the type of your SCSI controller ?
After reply, I'll try to help you, I've a DDS2 SCSI tape working.
Michel.
----- Original Message ----- From: "Sheridan West" <sjwest01@yahoo.co.uk> To: "Joni Hoppen" <joni@fundacentro.sc.gov.br> Sent: Thursday, March 10, 2005 9:20 AM Subject: Re: [SLE] Tape drive isn´t recognized!
Joni
You need ide-scsi, and stick it your boot process (there is a suse help tech note)
I cannot get a Travan tape device to work in Suse 9.2, it works fine in Suse 8.2. In the end I gave up and bought a dvd rw.
Your post is short on detail
--- Joni Hoppen <joni@fundacentro.sc.gov.br> wrote:
I am trying to install a tape drive but the system dont recognize in /dev/st0 when I installed it before on another computer with kde is was so simple. What can i do to make it works in text mode?
Joni
Send instant messages to your online friends http://uk.messenger.yahoo.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Joni wrote regarding 'Re: [SLE] Tape drive isn´t recognized!' on Thu, Mar 10 at 10:17: [...message trimmed...] On a semi-unrelated note (yeah, I'm sort of hijacking this thread, but it's kinda related), I have this rule in my .procmailrc: # Suse-linux-english list :0 * ^[sS]ubject:.*\[SLE\] .lists.suse/ Why would that be missing these messages? Does procmail get screwed up when there's a weird char in the Subject line? I know that the thing between the n and t in the subject line is probably supposed to be an apostrophe, but it's showing up as a sideways-T (probably a problem with my charset). None the less, the weird char appears after the rule should have already matched, and these messages (just the messages from Joni) keep endeing up in my inbox rather than the list folder. All of the replies, though, end up in the list folder. Mutt is using the same regexp in a subject hook (to set my sender address when replying), and it catches the message just fine. Weird. Thanks for any hints on this... --Danny
* Danny Sauer <suse-linux-e.suselists@danny.teleologic.net> [03-10-05 11:37]:
On a semi-unrelated note (yeah, I'm sort of hijacking this thread, but it's kinda related), I have this rule in my .procmailrc:
# Suse-linux-english list :0 * ^[sS]ubject:.*\[SLE\] .lists.suse/
Why would that be missing these messages?
#1, do not use the "Subject:" to recognize SLE posts, use the ^X-Mailinglist:.*suse-linux-e or ^TO_.*suse-linux-e #2, procmail is case insensitive *unless* directed otherwise by the 'D' flag, ie: :0 D: -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery
* Danny Sauer <suse-linux-e.suselists@danny.teleologic.net> [03-10-05 11:37]:
On a semi-unrelated note (yeah, I'm sort of hijacking this thread, but it's kinda related), I have this rule in my .procmailrc:
# Suse-linux-english list :0 * ^[sS]ubject:.*\[SLE\] .lists.suse/
Why would that be missing these messages?
addendum to previous answer: the char combination "\[" has special meaning in procmail -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery
On Thursday 10 March 2005 04:25 pm, Patrick Shanahan wrote:
* Danny Sauer <suse-linux-e.suselists@danny.teleologic.net> [03-10-05 11:37]:
On a semi-unrelated note (yeah, I'm sort of hijacking this thread, but it's kinda related), I have this rule in my .procmailrc:
# Suse-linux-english list
:0 * ^[sS]ubject:.*\[SLE\] .lists.suse/
Why would that be missing these messages?
addendum to previous answer:
the char combination "\[" has special meaning in procmail
I'm not finding that meaning in the man pages - what's its special meaning? Are you confusing \[ with \<, perhaps? BTW, I use the subject line so the rule will catch replies inadvertently (or "advertently") sent directly to me. Perhaps I should add a rule for the header, though these messages about the tape drive are the first that weren't caught by the subject rule. I still think it has something to do with the accent char being used as an apostrophe, and that somehow breaking my old procmail (version 3.22 from 2001). --Danny
The Friday 2005-03-11 at 09:07 -0600, Danny Sauer wrote:
BTW, I use the subject line so the rule will catch replies inadvertently (or "advertently") sent directly to me.
Mine works. The list folder only has mail sent from the list server, ie, directly from suse. CC copies sent to me direct go to the dups folder. Direct mail goes to another folder. # mail sent to this address is lists related. { # Add a Reply-To to this mail list, and move to the correct file. :0f * ^X-Mailinglist: suse-linux-e | /usr/bin/formail -bfi "Reply-To:suse-linux-e@suse.com" :0 a: $HOME/Mail/lists/suse-linux-e ... more lists here # Get duplicates (cc'ed) :0: * ^TO_suse-linux-s@suse.com $HOME/Mail/lists/in_dups .... more dups for the rest of list. ... direct. :0: $HOME/Mail/lists/in_elresto }
Perhaps I should add a rule for the header, though these messages about the tape drive are the first that weren't caught by the subject rule. I still think it has something to do with the accent char being used as an apostrophe, and that somehow breaking my old procmail (version 3.22 from 2001).
My rule above works also with suse 7.3 -- Cheers, Carlos Robinson
Carlos E. R. wrote:
snip
Mine works. The list folder only has mail sent from the list server, ie, directly from suse. CC copies sent to me direct go to the dups folder. Direct mail goes to another folder.
# mail sent to this address is lists related. { # Add a Reply-To to this mail list, and move to the correct file. :0f * ^X-Mailinglist: suse-linux-e | /usr/bin/formail -bfi "Reply-To:suse-linux-e@suse.com" :0 a: $HOME/Mail/lists/suse-linux-e
... more lists here
# Get duplicates (cc'ed) :0: * ^TO_suse-linux-s@suse.com $HOME/Mail/lists/in_dups
.... more dups for the rest of list.
... direct.
:0: $HOME/Mail/lists/in_elresto }
Carlos!. Could I see the whole procmailrc of yours ?. How does one start procmail ? Erik
The Saturday 2005-04-16 at 08:29 +0200, Erik Jakobsen wrote:
Carlos!. Could I see the whole procmailrc of yours ?.
I'd have to edit it to keep my other addreses private. Why do you want it?
How does one start procmail ?
You don't. You simply create your .procmailrc for each user that wants to use it, and tell postfix or sendmail or whatever to use procmail for local delivery. Yast does it for you, in fact. -- Cheers, Carlos Robinson
On Sat, Apr 16, 2005 at 04:34:19PM +0200, Carlos E. R. wrote:
The Saturday 2005-04-16 at 08:29 +0200, Erik Jakobsen wrote:
Carlos!. Could I see the whole procmailrc of yours ?.
I'd have to edit it to keep my other addreses private. Why do you want it?
To see how you did it, but don't care.
How does one start procmail ?
You don't.
You simply create your .procmailrc for each user that wants to use it, and tell postfix or sendmail or whatever to use procmail for local delivery. Yast does it for you, in fact.
Thanks for the reply. Erik
The Sunday 2005-04-17 at 07:18 +0200, Erik Jakobsen wrote:
Carlos!. Could I see the whole procmailrc of yours ?.
I'd have to edit it to keep my other addreses private. Why do you want it?
To see how you did it, but don't care.
Well, I can show you some part, with the tricks I use: VERBOSE=off LOGFILE=$HOME/procmail.log :0fw | /usr/bin/spamc :0 a * ^X-Spam-Status: Yes $HOME/Mail/in_spam * ^Received: from pop.tiscali.es * polling pop.tiscali.es account **whatever** # Filter Mail only from the tiscali account. The exact rules # will depend on your case. # The "polling" header is added by "fetchmail" if you tell it to do so # (the "tracepolls" keyword) { :0 * ^Original-Recipient: rfc822;robin1.listas@tiscali.es # Separate list mails { # Add a Reply-To to this mail list, and move to the correct file. :0f * ^X-Mailinglist: suse-linux-e | /usr/bin/formail -bfi "Reply-To:suse-linux-e@suse.com" :0 a: $HOME/Mail/lists/suse-linux-e :0f * ^X-Mailinglist: suse-linux-s | /usr/bin/formail -bfi "Reply-To:suse-linux-s@suse.com" :0 a: $HOME/Mail/lists/suse-linux-s # No poner detras de 'suse-security', o no los ve. :0 * ^X-Mailinglist: suse-security-announce $HOME/Mail/lists/suse-security-announce :0f * ^X-Mailinglist: suse-security | /usr/bin/formail -bfi "Reply-To:suse-security@suse.com" :0 a: $HOME/Mail/lists/suse-security # ----------- Quitar los duplicados (enviados a la lista y directamente) :0: * ^TO_suse-linux-s@suse.com $HOME/Mail/lists/in_dups :0: * ^TO_suse-linux-e@suse.com $HOME/Mail/lists/in_dups :0: * ^TO_suse-security@suse.com $HOME/Mail/lists/in_dups ## ----------- el resto de las listas :0: $HOME/Mail/lists/in_elresto } # Other aliases. # The rest :0 $HOME/Mail/in_tiscali } That's about it, I think. -- Cheers, Carlos Robinson
The Thursday 2005-03-10 at 10:36 -0600, Danny Sauer wrote:
[...message trimmed...]
On a semi-unrelated note (yeah, I'm sort of hijacking this thread, but it's kinda related), I have this rule in my .procmailrc:
# Suse-linux-english list :0 * ^[sS]ubject:.*\[SLE\] .lists.suse/
Why would that be missing these messages? Does procmail get screwed up when there's a weird char in the Subject line? I know that the thing between the n and t in the subject line is probably supposed to
If you request this list FAQ: |Send mail to the following for info and FAQ for this list: | <suse-linux-e-info@suse...> | <suse-linux-e-faq@suse...> In Q3, A3.3), says: # if mail is from list put it in $MAILDIR/foo :0 * ^X-Mailinglist::.*suse-linux-e $MAILDIR/foo That's the rule to use for the list, not the subject line. -- Cheers, Carlos.
On Thu, 10 Mar 2005 13:16:39 -0300, Joni Hoppen <joni@fundacentro.sc.gov.br> wrote:
Ok
I did modprob st and appears that its ok "no message"
I dont have this /etc/stinit.def ..... what can i do ?
it still doesnt working in /dev/st0
the model drive is a Sony SDT- 9000
From what you have described, you either are having a hardware
You will likely need stinit at some point, but you have not gotten that far. You said /proc/scsi is not showing the drive. I assume dmesg and/or /var/log/boot.msg is not showing the drive either during the SCSI detect process. (Look for where your controller is detected.) That has to happen first, then the drive info (Manufacturer/Model) from that is used by stinit to create the /dev/st0 entry. problem, or the driver for your controller is not working right. Have you gone into your controllers bios and verified it can see the drive? Greg -- Greg Freemyer
Hi take a look at my boot.msg <6>i2o: Checking for PCI I2O controllers... <6>i2o: I2O controller on bus 0 at 17. <6>i2o: PCI I2O controller at 0xF0000000 size=134217728 <6>mtrr: Intel 450NX MMC detected. Write-combining disabled. <4>mtrr: your processor doesn't support write-combining <6>I2O: MTRR workaround for Intel i960 processor <6>i2o/iop0: Installed at IRQ10 <6>i2o: 1 I2O controller found and installed. <6>Activating I2O controllers... <6>This may take a few minutes if there are many devices <6>i2o/iop0: LCT has 3 entries. <6>I2O configuration manager v 0.04. <6> (C) Copyright 1999 Red Hat Software <6>I2O Block Storage OSM v0.9 <6> (c) Copyright 1999-2001 Red Hat Software. <6>i2o_block: registered device at major 80 <6>i2o_block: Checking for Boot device... <6>i2o_block: Checking for I2O Block devices... <6>i2ob: Installing tid 16 device at unit 0 <6>i2o/hda: Max segments 12, queue depth 8, byte limit 49152. <6>i2o/hda: Disk Storage: 52095MB, 512 byte sectors. <6>i2o/hda: Maximum sectors/read set to 96. <6>Partition check: <6> i2o/hda: i2o/hda1 i2o/hda2 i2o/hda3 < i2o/hda5 i2o/hda6 i2o/hda7 > <6>SCSI subsystem driver Revision: 1.00 <3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device i2o_block(80,6)) ... <4>for (i2o_block(80,6)) I see that can be the problem what do you thing about it? kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 Ats Joni ----- Original Message ----- From: "Greg Freemyer" <greg.freemyer@gmail.com> To: "Joni Hoppen" <joni@fundacentro.sc.gov.br> Cc: "Suse" <suse-linux-e@suse.com> Sent: Thursday, March 10, 2005 3:57 PM Subject: Re: [SLE] Tape drive isn´t recognized!
On Thu, 10 Mar 2005 13:16:39 -0300, Joni Hoppen <joni@fundacentro.sc.gov.br> wrote:
Ok
I did modprob st and appears that its ok "no message"
I dont have this /etc/stinit.def ..... what can i do ?
it still doesnt working in /dev/st0
the model drive is a Sony SDT- 9000
You will likely need stinit at some point, but you have not gotten that far.
You said /proc/scsi is not showing the drive.
I assume dmesg and/or /var/log/boot.msg is not showing the drive either during the SCSI detect process. (Look for where your controller is detected.)
That has to happen first, then the drive info (Manufacturer/Model) from that is used by stinit to create the /dev/st0 entry.
From what you have described, you either are having a hardware problem, or the driver for your controller is not working right.
Have you gone into your controllers bios and verified it can see the drive?
Greg -- Greg Freemyer
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thu, 10 Mar 2005 16:07:33 -0300, Joni Hoppen wrote:
Hi
take a look at my boot.msg
<6>i2o: Checking for PCI I2O controllers... <6>i2o: I2O controller on bus 0 at 17. <6>i2o: PCI I2O controller at 0xF0000000 size=134217728 <6>mtrr: Intel 450NX MMC detected. Write-combining disabled. <4>mtrr: your processor doesn't support write-combining <6>I2O: MTRR workaround for Intel i960 processor <6>i2o/iop0: Installed at IRQ10 <6>i2o: 1 I2O controller found and installed. <6>Activating I2O controllers... <6>This may take a few minutes if there are many devices <6>i2o/iop0: LCT has 3 entries. <6>I2O configuration manager v 0.04. <6> (C) Copyright 1999 Red Hat Software <6>I2O Block Storage OSM v0.9 <6> (c) Copyright 1999-2001 Red Hat Software. <6>i2o_block: registered device at major 80 <6>i2o_block: Checking for Boot device... <6>i2o_block: Checking for I2O Block devices... <6>i2ob: Installing tid 16 device at unit 0 <6>i2o/hda: Max segments 12, queue depth 8, byte limit 49152. <6>i2o/hda: Disk Storage: 52095MB, 512 byte sectors. <6>i2o/hda: Maximum sectors/read set to 96. <6>Partition check: <6> i2o/hda: i2o/hda1 i2o/hda2 i2o/hda3 < i2o/hda5 i2o/hda6 i2o/hda7 > <6>SCSI subsystem driver Revision: 1.00 <3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device i2o_block(80,6)) ... <4>for (i2o_block(80,6))
I see that can be the problem what do you thing about it? kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Ats Joni
I agree, that looks wrong. When you do a lsmod, do you even have the SCSI module loaded. I'm guessing no. So you need to get your controller recognized first, then you can start thinking about the tape drive. Did you say that you had tried a couple different controllers? Or you had just tried different tape drives. Greg -- Greg Freemyer
Greg Freemyer a écrit :
On Thu, 10 Mar 2005 16:07:33 -0300, Joni Hoppen wrote:
Hi
take a look at my boot.msg
<6>i2o: Checking for PCI I2O controllers... <6>i2o: I2O controller on bus 0 at 17. <6>i2o: PCI I2O controller at 0xF0000000 size=134217728 <6>mtrr: Intel 450NX MMC detected. Write-combining disabled. <4>mtrr: your processor doesn't support write-combining <6>I2O: MTRR workaround for Intel i960 processor <6>i2o/iop0: Installed at IRQ10 <6>i2o: 1 I2O controller found and installed. <6>Activating I2O controllers... <6>This may take a few minutes if there are many devices <6>i2o/iop0: LCT has 3 entries. <6>I2O configuration manager v 0.04. <6> (C) Copyright 1999 Red Hat Software <6>I2O Block Storage OSM v0.9 <6> (c) Copyright 1999-2001 Red Hat Software. <6>i2o_block: registered device at major 80 <6>i2o_block: Checking for Boot device... <6>i2o_block: Checking for I2O Block devices... <6>i2ob: Installing tid 16 device at unit 0 <6>i2o/hda: Max segments 12, queue depth 8, byte limit 49152. <6>i2o/hda: Disk Storage: 52095MB, 512 byte sectors. <6>i2o/hda: Maximum sectors/read set to 96. <6>Partition check: <6> i2o/hda: i2o/hda1 i2o/hda2 i2o/hda3 < i2o/hda5 i2o/hda6 i2o/hda7 > <6>SCSI subsystem driver Revision: 1.00 <3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device i2o_block(80,6)) ... <4>for (i2o_block(80,6))
I see that can be the problem what do you thing about it? kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Ats Joni
I agree, that looks wrong.
When you do a lsmod, do you even have the SCSI module loaded.
I'm guessing no. So you need to get your controller recognized first, then you can start thinking about the tape drive.
Did you say that you had tried a couple different controllers? Or you had just tried different tape drives.
Greg
Hi, You told be in your first reply that the scsi controller module was loaded at boot. It is not the case, what is the type of your SCSI controller ? I need this in order to tell you what module to modprobe. Michel.
participants (8)
-
Anders Johansson -
Carlos E. R. -
Catimimi -
Danny Sauer -
Erik Jakobsen -
Greg Freemyer -
Joni Hoppen -
Patrick Shanahan