linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Kernel Error with i845G
@ 2002-09-25 19:29 Janek Neubert
  2002-09-28 15:44 ` Janek Neubert
  0 siblings, 1 reply; 2+ messages in thread
From: Janek Neubert @ 2002-09-25 19:29 UTC (permalink / raw)
  To: linux-kernel

Hi,

i have a bought an EPOX board (4G4A+) with Intel i845G chipset. While i was 
trying a 2.4.18 kernel, the machine stops after "Ok, booting the kernel ...". I 
have to use the lilo command mem=<memory without shared graphic ram>M in 
megabytes. All kernels newer than 2.4.3 cause this error. Since version 2.4.19, 
this solution is unusable. I think, this is a kernel problem, because i know 
from other people having the same problem, but other boards with i845G. I need 
the 2.4.19 to use my HPT372. Please help and finf the error.

I think the problem is a failure in the routine getting the size of memory from 
BIOS. Linux thinks, i have 640k!!! RAM. Only the mem-parameter can solve it.

Thx

janek

p.s. please send a cc to my email, i haven't subscribed this list


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Kernel Error with i845G
  2002-09-25 19:29 Kernel Error with i845G Janek Neubert
@ 2002-09-28 15:44 ` Janek Neubert
  0 siblings, 0 replies; 2+ messages in thread
From: Janek Neubert @ 2002-09-28 15:44 UTC (permalink / raw)
  To: linux-kernel

Janek Neubert schrieb:
 > Hi,
 >
 > i have a bought an EPOX board (4G4A+) with Intel i845G chipset. While i
 > was trying a 2.4.18 kernel, the machine stops after "Ok, booting the
 > kernel ...". I have to use the lilo command mem=<memory without shared
 > graphic ram>M in megabytes. All kernels newer than 2.4.3 cause this
 > error. Since version 2.4.19, this solution is unusable. I think, this is
 > a kernel problem, because i know from other people having the same
 > problem, but other boards with i845G. I need the 2.4.19 to use my
 > HPT372. Please help and finf the error.
 >
 > I think the problem is a failure in the routine getting the size of
 > memory from BIOS. Linux thinks, i have 640k!!! RAM. Only the
 > mem-parameter can solve it.


I have some more informations for you:

dmesg - output with mem=248M

Linux version 2.4.18 (root@server) (gcc version 2.95.4 20011002 (Debian
prerelease)) #7 SMP Fre Sep 27 23:01:22 CEST 2002
BIOS-provided physical RAM map:
   BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
   BIOS-e820: 00000000000a0000 - 000000000f7f0000 (reserved)
   BIOS-e820: 000000000f7f0000 - 000000000f7f3000 (ACPI NVS)
   BIOS-e820: 000000000f7f3000 - 000000000f800000 (ACPI data)
found SMP MP-table at 000f5b00
hm, page 000f5000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f0000 reserved twice.
hm, page 000f1000 reserved twice.
On node 0 totalpages: 63488
zone(0): 4096 pages.
zone(1): 59392 pages.
zone(2): 0 pages.
Intel MultiProcessor Specification v1.4
      Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 Unknown CPU [15:1] APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Processors: 1
...


Someone told me to post the output from the serial port. Sorry, i have used
minicom, cat and a null modem cabel, but there's no output.

When I use 256MB RAM, all works fine with mem=248M, if i use 512MB RAM and 
mem=504M, the maschine crashs after a full memory use like compiling a kernel.

Thx
janek
p.s. please send a cc to my email, i haven't subscribed this list


-- 
|Student of Computer Science, Chemnitz University of Technology
|Reichenhainer Str. 37/395, 09126 Chemnitz
|Telephon: (0177)2530625 URL: http://janek.eocom.de



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-09-28 15:40 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-25 19:29 Kernel Error with i845G Janek Neubert
2002-09-28 15:44 ` Janek Neubert

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).