mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: really mason_at_soo_dot_com <lnx-kern@Sophia.soo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.2-pre1 oddness under X
Date: Sun, 23 Dec 2001 16:04:19 -0500	[thread overview]
Message-ID: <20011223160419.A22752@Sophia.soo.com> (raw)
In-Reply-To: <20011223144800.A22538@Sophia.soo.com> <Pine.LNX.4.33.0112231457070.5312-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0112231457070.5312-100000@coffee.psychology.mcmaster.ca>; from hahn@physics.mcmaster.ca on Sun, Dec 23, 2001 at 02:58:38PM -0500

Thanks Vojtech and Mark, this is good to know and gives
me more confidence messing around with this box... er,
not that i'd stop in any case...

On Sun, Dec 23, 2001 at 08:53:14PM +0100, Vojtech Pavlik wrote:
> Good, then. In theory your IDE should operate well if you did this,
> eventhough you run the 37 MHz PCI. Other devices may not like this
> still, though.
>
> > i thot it
> > was only relevant to PIO modes?  Shows how little i
> > know abt the IDE drivers.
>
> It is relevant to all PIO, DMA and UDMA modes.

The funny thing still is that i get this error regardless
of whether i overclock, underclock, or leave as is using
kernel 2.5.2-pre1, when i start X:

Inconsistency detected by ld.so: dynamic-link.h: 62: elf_get_dynamic_info: Assertion `! "bad dynamic tag"' failed!

X eventually starts, minus the Sawfish window manager.

Everything's fine from kernel version 2.5.1 down.  If it
is indeed disk corruption of some kind, i guess i better 
run an older kernel and fsck.

On Sun, Dec 23, 2001 at 02:58:38PM -0500, Mark Hahn wrote:
> overclocking is always invalid.  some software is generous
> enough to let you actually compensate for you botching the config.
> in this case, the driver *must* have the actual PCI clock,
> since the ide timings are derived from it (and *not* overclockable).
>
> otoh, you're overclocking, therefore don't mind bogosity,
> so probably *want* overclocked ide timings.

b


  parent reply	other threads:[~2001-12-23 21:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-22 21:46 really mason_at_soo_dot_com
2001-12-22 22:24 ` Pierre Rousselet
2001-12-23 14:11   ` Jens Axboe
2001-12-23 17:08     ` really mason_at_soo_dot_com
2001-12-23 19:42       ` Vojtech Pavlik
2001-12-23 19:48         ` really mason_at_soo_dot_com
2001-12-23 19:53           ` Vojtech Pavlik
     [not found]           ` <Pine.LNX.4.33.0112231457070.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-23 21:04             ` really mason_at_soo_dot_com [this message]
2001-12-24 14:03               ` Jens Axboe
2001-12-24 20:36                 ` really mason_at_soo_dot_com
2001-12-24 20:44                   ` really mason_at_soo_dot_com
2001-12-23 20:37       ` Ryan Cumming

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=20011223160419.A22752@Sophia.soo.com \
    --to=lnx-kern@sophia.soo.com \
    --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

Powered by JetHome