From: Marko Kreen <marko@l-t.ee>
To: Ronny Buchmann <ronny-lkml@vlugnet.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.4.22 / HPT372N
Date: Thu, 11 Sep 2003 15:34:18 +0300 [thread overview]
Message-ID: <20030911123418.GA6798@l-t.ee> (raw)
In-Reply-To: <200309091406.56334.ronny-lkml@vlugnet.org>
On Tue, Sep 09, 2003 at 02:06:56PM +0200, Ronny Buchmann wrote:
> Marko Kreen wrote:
> > Now we did some experimenting with it and no BIOS settings seem
> > to affect the FREQ numbers. (Lower CPU/mem speed, 50/25 AGP/PCI speed.)
> > The FREQ still stays fixed at 85.
> >
> > Motherboard is EP-4PDA2+.
> >
> > Any idea how to remove the overclocking? Otherwise it seems
> > like driver bug to me.
> What bios version do you use? Have you tried a CMOS reset?
BIOS is 6/20/2003.
Yes, we did CMOS reset, because the board 'played dead' for a
while. After staying without battery it woke up again.
HPT acts still same. I looked BIOS changelog, did not saw
anything related to overclocking.
> I have the same motherboard but a different problem with the hpt chip, only
> the first channel is recognized. (see
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97824)
I saw something like that too - when disk was in second channel,
it did not crash because it did not detect anything.
> part from dmesg (klogd) output
> ---
> Sep 7 23:50:17 bserv kernel: HPT366: IDE controller at PCI slot 02:00.0
> Sep 7 23:50:17 bserv kernel: HPT366: chipset revision 6
> Sep 7 23:50:17 bserv kernel: HPT366: not 100%% native mode: will probe irqs
> later
> Sep 7 23:50:17 bserv kernel: hpt: HPT372N detected, using 372N timing.
> Sep 7 23:50:17 bserv kernel: FREQ: 82 PLL: 35
"FREQ: 82" is pretty high as the limit is 85.
I replaced "< 0x55" with "<= 0x55" in hpt366.c and the driver
did not crash, but it also did not detect cdrom - only thing
behind it ATM - so I did not bother messing with it further.
> Currently the driver provided by highpoint
> (http://www.highpoint-tech.com/hpt3xx-opensource-v131.tgz) is working ok for
> me (apart from it's lack of s.ma.r.t. support).
>
> Did you try this?
Now I tried - that one also did not detect cdrom. I cant
experiment further as the machine needs to go to production
soon. ATM I disabled onboard HPT, and put in separate IDE
controller (HPT370) to get needed IDE channel.
My conclusions:
1) Motherboard is overclocked by manufacturer - so in the future
I intend to stay away from EPOX.
2) HPT372n support in Linux is beta (as documented...)
--
marko
next prev parent reply other threads:[~2003-09-11 12:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 12:06 [OOPS] 2.4.22 / HPT372N Ronny Buchmann
2003-09-11 12:34 ` Marko Kreen [this message]
2003-09-12 9:41 ` Ronny Buchmann
2003-09-12 10:48 ` Alan Cox
2003-09-12 12:32 ` Ronny Buchmann
2003-09-12 12:46 ` Alan Cox
2003-09-12 12:58 ` Bartlomiej Zolnierkiewicz
2003-09-12 14:24 ` Ronny Buchmann
2003-09-12 14:42 ` Bartlomiej Zolnierkiewicz
2003-09-12 15:26 ` Ronny Buchmann
2003-09-12 16:35 ` Bartlomiej Zolnierkiewicz
2003-09-12 20:32 ` Ronny Buchmann
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 19:07 Marko Kreen
2003-09-04 21:46 ` Alan Cox
2003-09-05 14:54 ` Marko Kreen
2003-09-05 21:51 ` Alan Cox
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=20030911123418.GA6798@l-t.ee \
--to=marko@l-t.ee \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ronny-lkml@vlugnet.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