Patch for memory holes on buggy motherboards

Patch for memory holes on buggy motherboards

Post by Scott Bark » Thu, 10 Oct 1996 04:00:00



I was having troubles with a "missing" 64k chunk of RAM on my motherboard. I
came up with a simple patch which fixed my problem. Now, I'm wondering if it's
worth my effort to create a boot-time parameter such as

memoryhole=start,size

How widespread is the problem of motherboards with memory holes? I really
don't want to go through the effort of hacking into the kernel unless it will
benefit a lot of people.

--
Scott Barker
Linux Consultant

http://www.cuug.ab.ca:8001/~barkers/   (under construction)

[ I try to reply to all e-mail within 3 days. If you don't   ]
[ get a response by then, I probably didn't get your e-mail. ]
[ Unsolicited commercial and junk e-mail will be proof-read for US$100 ]

"Nothing succeeds like the appearance of success."
   - Christopher Lasch

 
 
 

Patch for memory holes on buggy motherboards

Post by Pavel Mach » Sat, 12 Oct 1996 04:00:00



:  > I was having troubles with a "missing" 64k chunk of RAM on my motherboard. I
:  > came up with a simple patch which fixed my problem. Now, I'm wondering if it's
:  > worth my effort to create a boot-time parameter such as
:  >
:  > memoryhole=start,size
:  >
:  > How widespread is the problem of motherboards with memory holes? I really
:  > don't want to go through the effort of hacking into the kernel unless it will
:  > benefit a lot of people.

:  Go for it.  This is not only useful for memory holes due to the
: motherboard, but it could also be used to map out memory ranges of bad
: Simms.

Are you sure such thing is possible? I thing that when there's a buggy part on a simm
module, it belongs to THRASH - bugs probably will show in BIG space (3-rd bit buggy
each 256 byte through whole simm?). I'm not hardware specialist, but...

                                                                        Pavel
--
This looks like my little buggy signature...                   Pavel Machek
If you want more info about me http://novell.karlin.mff.cuni.cz/~pmac5296
will not give it to you :-). Use http://www.ms.mff.cuni.cz/~pmac5296 instead.

 
 
 

Patch for memory holes on buggy motherboards

Post by Stephen Obersk » Mon, 14 Oct 1996 04:00:00



> :  > I was having troubles with a "missing" 64k chunk of RAM on my motherboard. I
> :  > came up with a simple patch which fixed my problem. Now, I'm wondering if it's
> :  > worth my effort to create a boot-time parameter such as
> :  >
> :  > memoryhole=start,size
> :  >
> :  > How widespread is the problem of motherboards with memory holes? I really
> :  > don't want to go through the effort of hacking into the kernel unless it will
> :  > benefit a lot of people.

It would be very useful for ISA cards that insist on using a big chunk
of memory.

On my SCO Unix system, I'm using a Digiboard PC/XI multiport serial card
that uses 512K of memory at mem=0xF00000 (15M).

SCO supports a memory hole feature, which is the only way I can use this
card
on a 32M system.

In SCO land one puts a line like this in the /etc/default/boot file:

  DEFBOOTSTR=hd(40)unix mem=1m-15m,15872k-32m

Of course you also need BIOS support to map out the chunk of address
space
that the card has mapped into.

--

2827 FAX
Deterministic Software Ltd., 134 Morton Way, Brampton, Ontario L6Y 2P5
Canada

PGP key
        Always remember that you are unique.  Just like everyone else.

 
 
 

Patch for memory holes on buggy motherboards

Post by Inaky Perez Gonzale » Wed, 16 Oct 1996 04:00:00



Quote:> I was having troubles with a "missing" 64k chunk of RAM on my motherboard. I
> came up with a simple patch which fixed my problem. Now, I'm wondering if it's
> worth my effort to create a boot-time parameter such as

> memoryhole=start,size

> How widespread is the problem of motherboards with memory holes? I really
> don't want to go through the effort of hacking into the kernel unless it will
> benefit a lot of people.

   I've had pretty much problemas with that, and for me, personally,
would be a great advantage. Sometimes I thought of working it myself,
but I'm no kernel hacker at all, and got lost in the middle of the
code in the first three lines :(

    I'd really like to see that :) (anyway, thanks for just offering,
you're a great guy!)

        Cheers!

                Inaky Perez Gonzalez --  PGP pubkey fingerprint -

   http://peloncho.fis.ucm.es/~inaky -- AD 7B 30 D9 DD FF 3E 4C -
-----------------------------------------------------------------
The loneliness of the long distance runner .....

 
 
 

1. MS Office 2000 is buggy, buggy, buggy

My day today with MS Office 2000:

I'm a programmer and was asked to prepare documentations and a presentation,
something no programmer really likes. Well, I swore and thought, lets just
slap something together quickly with Word and Powerpoint... I was mistaken.

The g**m Word crashed on me five times. Each time, after restarting Word
again, I could not open the file I was working on previously. Word
complained: "File locked by <me>".

After a while, I found out that I actually have to

1) kill the (window-less) process WINWORD.EXE and
2) delete all hidden files starting with '~'

before I could go on and open the file again. Being a programmer, I wrote
myself a tool to do this automatically.

"Ease of use"? Yeah right, I can just see all the secretaries just opening
the taskmanager and killing processes...

Poor, poor, poor quality. Amazing what they get away with.

More issues:
- The graphical component (vector graphics) inside MS Word and Powerpoint is
a Joke. No, really. The behaviour is often illogical and unpredictable. It
also caused two of my five crashes. Scaling groups of objects does not work
properly. And so on. Pure pain - I wish I had Visio installed or some other
*professional* Graphics tool.
- Importing data from Word to powerpoint is error prone, to say the least.
Tables get scr*ed up.

As a bottomline, this will be the last presentation I prepared using MS
Office.

2. Thttpd woes

3. Buggy motherboard?

4. Are you a FROG?

5. Dual boot on buggy motherboard with 32GB limit

6. Reg. en_US.ISO8859-1 package

7. Buggy 3C574, or buggy administrator?

8. module? what's a module?

9. Recommended Patch Cluster for Solaris8 is BUGGY !!!!

10. Patch 108993-26 buggy?

11. Sun Ray 3.0 patch 118979-01 is buggy

12. WARNING: Buggy patch 101946-29

13. patch 109134 buggy ?