public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Roland Mas <roland.mas@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Drivers *dropped* between releases? (sis5513.c)
Date: Sat, 03 Apr 2004 00:39:14 +0200	[thread overview]
Message-ID: <406DEB92.2020400@inet6.fr> (raw)
In-Reply-To: <87n05uw1zb.fsf@mirexpress.internal.placard.fr.eu.org>

Roland Mas wrote the following on 04/02/04 22:37 :

>Hi,
>
>Just got myself a new El Cheapo PC, motherboard is an "ASRock K7S8X".
>IDE chipset is SiS746FX.  Tried installing Debian (latest beta3 of the
>installer, based on kernel 2.4.25) on it, but I couldn't: the IDE
>detection code would load the sis5513 module,
>

Good.

> then sort of hand for
>various amounts of time (during which the loggers complained about
>"hda: lost interrupt" and "hdc: lost interrupt").  Eventually, a
>timeout would be reached, but the hard drive (hda) woud still not be
>usable, and the CD-ROM drive (hdc) wouldn't be usable anymore (after
>having been used as a source for loading the modules).
>
>  
>

Less good.

>  I've looked around a bit, and it seems that sis5513.c has seen a
>change between 2.4.21 and 2.4.22 removing support for the SiS746
>chipset.  Well, removing lines mentionint it, at least, but I'm not
>enough of a guru to see what it should change.
>
>  
>

The driver uses 2 ways of finding SiS Ide chips :
- by northbridge PCI ids, which is what was always used historically 
(and so you had to manually add each known SiS northbridge to a table),
- by probing the controller directly (avoids depending on a lazy coder 
to add entries in a table to make your chip work).

When the last was added, some PCI ids were removed from the table (being 
superfluous).

The very fact that the sis5513.c outputs something in your log means 
that it has found something to handle, so the detection routine 
(whichever it is) works.

I think there's a common problem with SiS chips : interrupt handling. I 
believe it is the source of your problem. I may find time to hack on this.

You could try to remove PCI cards and/or disable VGA IRQ in the bios. On 
one of my SiS-based systems for example adding a PCI card can make it 
unbootable.

Regards,

-- 
Lionel Bouton - inet6
---------------------------------------------------------------------
   o              Siege social: 51, rue de Verdun - 92158 Suresnes
  /      _ __ _   Acces Bureaux: 33 rue Benoit Malon - 92150 Suresnes
 / /\  /_  / /_   France
 \/  \/_  / /_/   Tel. +33 (0) 1 41 44 85 36
  Inetsys S.A.    Fax  +33 (0) 1 46 97 20 10
 


  reply	other threads:[~2004-04-02 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 20:37 Drivers *dropped* between releases? (sis5513.c) Roland Mas
2004-04-02 22:39 ` Lionel Bouton [this message]
     [not found] <1GDM3-6G3-5@gated-at.bofh.it>
     [not found] ` <1GFEd-8b8-15@gated-at.bofh.it>
2004-04-03  8:19   ` Roland Mas
2004-04-03  8:40     ` Lionel Bouton
     [not found] <1GOHw-6te-9@gated-at.bofh.it>
     [not found] ` <1GOHw-6te-11@gated-at.bofh.it>
     [not found]   ` <1GOHw-6te-7@gated-at.bofh.it>
     [not found]     ` <1GP0Q-6Fz-9@gated-at.bofh.it>
2004-04-04 15:51       ` Roland Mas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=406DEB92.2020400@inet6.fr \
    --to=lionel.bouton@inet6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland.mas@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox