mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bhoward@hale.org
To: James Mayer <james.mayer@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [bug] 2.4.19-pre4-ac2 hang at boot with ALI15x3 chipset support
Date: Wed, 27 Mar 2002 17:37:15 -1000 (HST)	[thread overview]
Message-ID: <m16qQix-0014LaC@malasada.lava.net> (raw)
In-Reply-To: <86387368@toto.iv>

>> > After adding printk calls to alim15x3.c, it seems to hang during the
>> > pci_write_config_byte(isa_dev, 0x79, tmpbyte | 0x02) call on line 588.
>> 
>> Does it work if you comemtn that line out ?

James> No, if the line is commented out I get:

James> hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
James> hda: drive not ready for command

I ran into this as well under various kernels including 2.4.18.  Try
adding:
    append="idebus=50"

to the lilo stanza for your kernel.

It seems even after I amputated the offending "write" that causes the
lockup, the bus speed was being set to 33MHz instead of 50Mhz.  The
above solved the problem for me.

I don't need to specifically set idebus in the 2.5.7 version of the
driver so I assume something has been corrected in more recent
releases.

For anyone else trying to configure the pcg-c1mrx or pcg-c1mv, I'm
updating linux configuration document as I work through the
setup of the various devices:
    http://hale.org/~bhoward/issue_7/pcg-c1mrx.html

						Bruce

       reply	other threads:[~2002-03-28  3:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86387368@toto.iv>
2002-03-28  3:37 ` bhoward [this message]
2002-03-29  1:08   ` James Mayer
     [not found] <124088188@toto.iv>
2002-03-29 10:01 ` bhoward
2002-03-27 23:38 James Mayer
2002-03-27 23:52 ` Brian D Heaton
2002-03-27 23:59 ` Andre Hedrick
2002-03-28  0:04 ` Alan Cox
2002-03-28  0:21   ` James Mayer
2002-03-28  0:30     ` Andre Hedrick

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=m16qQix-0014LaC@malasada.lava.net \
    --to=bhoward@hale.org \
    --cc=james.mayer@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®