Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Lilo Memory
- To: tlug@example.com
- Subject: Re: tlug: Lilo Memory
- From: pal <pal@example.com>
- Date: Sun, 20 Oct 1996 15:21:06 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- References: <m0vwiXe-000010C@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug
-------------------------------------------------------- tlug note from pal <pal@example.com> -------------------------------------------------------- > >>>>> "pal" == pal <pal@example.com> writes: > > pal> Hello Stephen I need the full 128MB . Sorry 64MB is not > pal> enough .I'm doing my work on my Linux Machine and BANG out of > pal> MEmory ;-<< This is the reason for the 128 > > Of course you need it; my sense of humor is not always appropriate. We'll live with it ;->> > > pal> I loaded the lilo.conf on my MBR of Hard Disk Could it be a > pal> Kernel Problem !! > > Could be, of course. As far as I know, however, it shouldn't be a > problem. My guess is that your BIOS is not reporting available memory > correctly, and both LILO and the kernel are making mistakes based on > incorrect value from BIOS. Mmmmmmmm Just surprised 64MB is recognized > > 1. Does your BIOS know about the 128MB at boot up (ie, in memory test)? yes > 2. Presumably Linux asks the CMOS (nonvolatile onboard RAM) about it. > Did you change the CMOS values? (I don't know about PCI, maybe PCI > is supposed to autodetect; the machine I have known and loved for > years is EISA-based, and you have to run a config program to tell > the machine about memory changes and stuff. At the time this was a > big improvement over flipping hardware jumpers which are invariably > located on the side of the motherboard which is bonded to the > chassis.... > CMOS menu is usually accessible by pressing DELETE or ESC or > something like that during boot-up. Depends on your BIOS. > 3. If you boot, say, DOS or Windows 95 can you use the memory? (Ie, > are you sure the hardware is correctly installed?) Don't use those at all ;->> > 4. Could there be a hardware conflict with a video card with a linear > frame buffer? Some of those cards want the buffer to live at a > certain address, or below a certain address. Could be it ...maybe an upgrade could be simpler but takes time ;->> thank leo ----------------------------------------------------------------- a word from the sponsor will appear below ----------------------------------------------------------------- The TLUG mailing list is proudly sponsored by TWICS - Japan's First Public-Access Internet System. Now offering 20,000 yen/year flat rate Internet access with no time charges. Full line of corporate Internet and intranet products are available. info@example.com Tel: 03-3351-5977 Fax: 03-3353-6096
- Follow-Ups:
- tlug: Compaq prolinea+SCSI
- From: Anil <anil@example.com>
- References:
- Re: tlug: Lilo Memory
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: Lilo Memory
- Next by Date: Re: tlug: Lilo Memory
- Prev by thread: Re: tlug: Lilo Memory
- Next by thread: tlug: Compaq prolinea+SCSI
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links