Re: [newbie] Problem with SCSI Controller

2003-12-11 Thread Yvan Gutknecht
 On Tuesday 09 December 2003 01:55 am, Yvan Gutknecht wrote:
 
 YG  You are right, it looks like that, there just one problem. There is
 no
  unit YG  connected to my SCSI controller.
 YG
 
 I have to admit, I'm a little confused here - I've been following this
 thread 
 loosely (as I do most with anything SCSI in them, since I use SCSI myself)
 
 but I just don't understand why you would have a SCSI controller onboard
 if 
 you don't have any SCSI devices attached to it. Or did I miss something? 
 
 Wouldn't it be perfectly normal for you to get a timeout error since no
 device 
 can respond to the SCSI controllers queries? Just a thought...
 
It worked that way with Mandrake 7.0 and 8.0, now it shows these problems.

On some ocasions, when I boot into windows I connect a SCSI scanner or
another device to it. I don't use the SCSI card often under windows and never
under Linux. If I would never use it under windows I would just remove the card. 

If somebody can tell me how I can tell the Kernel to just ignore this card
(without being able to boot this kernel of course) then I think I would be
happy.



-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [newbie] Problem with SCSI Controller

2003-12-11 Thread Ronald J. Hall
On Thursday 11 December 2003 02:26 am, Yvan Gutknecht wrote:

YG  It worked that way with Mandrake 7.0 and 8.0, now it shows these
 problems. YG
YG  On some ocasions, when I boot into windows I connect a SCSI scanner or
YG  another device to it. I don't use the SCSI card often under windows and
 never YG  under Linux. If I would never use it under windows I would just
 remove the card. YG
YG  If somebody can tell me how I can tell the Kernel to just ignore this
 card YG  (without being able to boot this kernel of course) then I think I
 would be YG  happy.
YG
YG
YG

Okay, then why not just hook the scanner up and leave it there? I'm using a 
SCSI scanner (Umax Astra 1200) with my Linux setup and it works fine. Sane 
should be able to use what you've got - what model is it? Why not just use 
Linux for your scanning needs and dump Windoze all together... grin

-- 

   /\
 DarkLord
   \/


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [newbie] Problem with SCSI Controller

2003-12-09 Thread Ronald J. Hall
On Tuesday 09 December 2003 01:55 am, Yvan Gutknecht wrote:

YG  You are right, it looks like that, there just one problem. There is no
 unit YG  connected to my SCSI controller.
YG

I have to admit, I'm a little confused here - I've been following this thread 
loosely (as I do most with anything SCSI in them, since I use SCSI myself) 
but I just don't understand why you would have a SCSI controller onboard if 
you don't have any SCSI devices attached to it. Or did I miss something? 

Wouldn't it be perfectly normal for you to get a timeout error since no device 
can respond to the SCSI controllers queries? Just a thought...

-- 

   /\
 DarkLord
   \/


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [newbie] Problem with SCSI Controller

2003-12-08 Thread Yvan Gutknecht
 On Monday 01 Dec 2003 3:33 pm, Yvan wrote:
  Hello group,
 
  my PC has a SCSI-Controller Tekram DC390/AM53C974 V2.0f
  2000-12-20.
 
  I use the controller only when booting Windows, I don't use it with
  Mandrake. But Mandrake doesn't boot because of this controller.
 
 Certainly 9.1 has no problem with the DC390 - I have it.
 
  During booting I always got the following message:
 
  ...
  scsi: aborting command due to timeout : pid , scsi 1, channel 0, id
  0, lun 0 inquiry 00 00 00 ff 00
  SCSI host 1 abort (pid 7) timeout resetting
  ...
 
 Could be wrong, but it seems to me that it's not the controller that's 
 the problem, but the unit you have connected to it.  Try powering 
 down that unit if you can.
 
 Anne
 -- 
 Registered Linux User No.293302
 Have you visited http://twiki.mdklinuxfaq.org yet?
 


You are right, it looks like that, there just one problem. There is no unit
connected to my SCSI controller.

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


[newbie] Problem with SCSI Controller

2003-12-01 Thread Yvan
Hello group,

my PC has a SCSI-Controller Tekram DC390/AM53C974 V2.0f 2000-12-20.

I use the controller only when booting Windows, I don't use it with
Mandrake. But Mandrake doesn't boot because of this controller.

During booting I always got the following message:

...
scsi: aborting command due to timeout : pid , scsi 1, channel 0, id 0, lun 0
inquiry 00 00 00 ff 00
SCSI host 1 abort (pid 7) timeout resetting
...

this messages repeats all over again and Mandrake refuses to go further in
the boot process.

It's even more disturbing as I don't use this controller under Mandrake, but
I can't remove it because I need it for windows.

I am able to boot with an older kernel.

Is there any way I can tell Mandrake just to don't care about this
SCSI-controller?

Any help appreciated

Thank you
Yvan




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com


Re: [newbie] Problem with SCSI Controller

2003-12-01 Thread Anne Wilson
On Monday 01 Dec 2003 3:33 pm, Yvan wrote:
 Hello group,

 my PC has a SCSI-Controller Tekram DC390/AM53C974 V2.0f
 2000-12-20.

 I use the controller only when booting Windows, I don't use it with
 Mandrake. But Mandrake doesn't boot because of this controller.

Certainly 9.1 has no problem with the DC390 - I have it.

 During booting I always got the following message:

 ...
 scsi: aborting command due to timeout : pid , scsi 1, channel 0, id
 0, lun 0 inquiry 00 00 00 ff 00
 SCSI host 1 abort (pid 7) timeout resetting
 ...

Could be wrong, but it seems to me that it's not the controller that's 
the problem, but the unit you have connected to it.  Try powering 
down that unit if you can.

Anne
-- 
Registered Linux User No.293302
Have you visited http://twiki.mdklinuxfaq.org yet?



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com