public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Allum <mallum@xblox.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiple kernels OOPS at boot on Fujitsu pt510 ( AMD DX100 CPU ) - ksymoops output attached
Date: Fri, 01 Mar 2002 18:25:43 +0000	[thread overview]
Message-ID: <3C7FC7A7.1030405@xblox.net> (raw)
In-Reply-To: <E16gqxM-0004LV-00@the-village.bc.nu>

Its booting !!!!

I tried to build a 2.4.1kernel, but it had problems with my newer ld so 
I tried again with a 2.4.17 following Alans instructions.

I passed mem=6 and it booted. I then expeimented upping this value and 
it still boots when I pass mem=32m ( the actual amount of ram in the 
machine ). So I guess it was just a problem of the box lieing about its 
memory.

Many thanks for all you help, its really appreciated.

  -- Matthew Allum

Alan Cox wrote:

>>Id really appreciate some help on this matter. Theres plenty of these 
>>510's on ebay at the moment going very cheapy ( 100$) and they'd make 
>>nice wireless 'web pads'.
>>
>
>I have a somewhat older beast (Fujitsu Stylistic 1000) which is somewhat
>older and a little lower spec that I've been playing with a fair bit getting
>Xfce + scribble etc running on with no problem.
>
>Generally when you get a crash very early you want to check
>	-CPU type the kernel was built with - your oops isnt an illegal
>	 instruction so thats not it
>	-Disabling APM support
>	-Disabling PnpBIOS support (-ac tree only)
>	-Using mem=fooM where foo is a bit under what is fitted in case
>	 the box lies about memory availability
>
>That generally gets successes. You might also want to do a test boot 
>with mem=6M in case the machine has something funky like a 15-16Mb Vesa
>local bus magic hole in the address map.
>
>Definitely looks a fun toy
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>




  reply	other threads:[~2002-03-01 18:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 14:44 Multiple kernels OOPS at boot on Fujitsu pt510 ( AMD DX100 CPU ) - ksymoops output attached Matthew Allum
2002-03-01 14:54 ` Richard B. Johnson
2002-03-01 15:52   ` Zwane Mwaikambo
2002-03-01 17:50     ` Richard B. Johnson
2002-03-02  3:53       ` Juan Quintela
2002-03-01 17:36 ` Alan Cox
2002-03-01 18:25   ` Matthew Allum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-01 18:12 Torrey Hoffman
2002-03-01 19:22 ` Richard B. Johnson
2002-03-01 20:04 Torrey Hoffman

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=3C7FC7A7.1030405@xblox.net \
    --to=mallum@xblox.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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