From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Michal Jaegermann <michal@harddata.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 kernels - "attempt to access beyond end of device"
Date: Thu, 1 Mar 2001 00:07:45 MET-1 [thread overview]
Message-ID: <C291BF3C67@vcnet.vc.cvut.cz> (raw)
On 28 Feb 01 at 15:47, Michal Jaegermann wrote:
> > > I have more checks to make before I will be fully satisfied but
> > > this looks like it.
> > ...
> > > System Performance Setting [Optimal, Normal]
> > ...
> >
> > Try BIOS 1006. AFAIK 1005D changed some VIA values for 'optimal'.
>
> Is that important here? IDE drives in question were not connected to
> on-board controller but the Promise one. Results seem to indicate
> that this 'optimal' was important here anyway.
VIA host-bridge, not VIA-IDE... It is important even if you use Promise
only - look back through archives, there must be something really wrong
with this motherboard.
> > And 1006 contains newer Promise BIOS - but I did not notice any difference:
> > Windows98 still do not boot if I connect harddisk to /dev/hdh :-(
>
> There is at this moment Windows98 installation on /dev/hde1 and it boots
> so far. It got installed and it was booting regardless with these
> "other" BIOS seetings.
Connect UDMA2 CDROM to hda and UDMA2 IDE to hdg. And then look how Win98
lockup after they print 'Starting Win98...'. But that's offtopic for
linux-kernel.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2001-02-28 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 0:07 Petr Vandrovec [this message]
2001-03-01 12:22 ` 2.4 kernels - "attempt to access beyond end of device" Thomas Molina
-- strict thread matches above, loose matches on Subject: below --
2001-02-28 22:54 Petr Vandrovec
2001-02-28 22:47 ` Michal Jaegermann
2001-02-27 2:10 Michal Jaegermann
2001-02-27 23:36 ` Michal Jaegermann
2001-02-28 20:46 ` Michal Jaegermann
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=C291BF3C67@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@harddata.com \
/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