linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* completely undiagnosable (for me) kernel boot problem
@ 2003-01-23  4:20 Sam Gendler
  2003-01-23  9:26 ` Denis Vlasenko
  0 siblings, 1 reply; 2+ messages in thread
From: Sam Gendler @ 2003-01-23  4:20 UTC (permalink / raw)
  To: 'linux-kernel@vger.kernel.org'

OK, I am most definitely not a kernel guru, but I have been using and
installing (and building) linux on a number of systems for many years now
and I've bumped into a wall.  I am pretty sure that this is a kernel issue,
not a distribution one, so don't flame me tooharshly. Please CC my email
address as well as the list with responses, as I am not a subscriber.  I did
search the archives, however.

I just bought a brand new Toshiba 2435-S255 laptop (2.4 Ghz Pentium 4, 512MB
RAM, CDR/DVD drive).  If I attempt to install what appears to be any distro
(I only have redhat handy, but I've tried many different versions), the boot
process (into the install kernel, not the main one) fails.  It successfully
uncompresses vmlinuz and initrd.img, then clears the screen and displays the
message "Uncompressing Linux... Ok, booting the kernel." and leaves a
blinking cursor two lines below.  Nothing ever happens subsequent to that.
I am fairly sure that it is NOT a 2.88MB image problem, as I installed
FreeDOS on the machine (wiping out XP, you'll be glad to know) and then ran
dosutils\autoboot, which apparently runs loadlin on top of DOS.  From what I
can tell after hours of searching the web and mailing lists for answers,
that should have worked if the BIOS was complaining about a 2.88MB boot
image.  Also, the same symptoms occur whether I boot from the net or the
CDR/DVD drive, so I don't think it is the device.  I don't know how to go
about finding out what is hanging the system, and I don't have a system
available to me on which I can comple a custom kernel.  This is the only
machine I have, and it now has nothing but freeDOS on it.  I could revert to
the original XP install, but I am loathe to do that unless I have to.

I have found absolutely no references to this particular laptop anywhere on
the net, especially in regard to linux installs.  I have posted to the
toshiba discussion boards and gotten no response.  An email similar to this
will be posted to RedHat shortly.

Thanks much for your time.

--sam

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

* Re: completely undiagnosable (for me) kernel boot problem
  2003-01-23  4:20 completely undiagnosable (for me) kernel boot problem Sam Gendler
@ 2003-01-23  9:26 ` Denis Vlasenko
  0 siblings, 0 replies; 2+ messages in thread
From: Denis Vlasenko @ 2003-01-23  9:26 UTC (permalink / raw)
  To: Sam Gendler, 'linux-kernel@vger.kernel.org'
  Cc: DragonK, W. Michael Petullo

On 23 January 2003 06:20, Sam Gendler wrote:
> the main one) fails.  It successfully uncompresses vmlinuz and
> initrd.img, then clears the screen and displays the message
> "Uncompressing Linux... Ok, booting the kernel." and leaves a
> blinking cursor two lines below.  Nothing ever happens subsequent to
> that.

Heh... you'll have to mess up with boot code. CCed to
DragonK <dragon_krome@yahoo.com> (he had similar 'no boot'
horror story, and was able to diagnose it).

> was complaining about a 2.88MB boot image.  Also, the same symptoms
> occur whether I boot from the net or the CDR/DVD drive, so I don't
> think it is the device.  I don't know how to go about finding out
> what is hanging the system, and I don't have a system available to me
> on which I can comple a custom kernel.  This is the only machine I
> have, and it now has nothing but freeDOS on it.

Thats strange. How did you managed to try network boot without
a second system available to you? Did you tried to copy kernel
to DOS partition and load it with loadlin or linld?

http://www.imtp.ilyichevsk.odessa.ua/linux/vda/linld/

A long time ago I said to "W. Michael Petullo" <mike@flyn.org>:
>> Since the kernel does not even peep an oops message, I'm not sure where
>> to start debugging.  Is anyone else having similar problems?
>
>If noone will send you a suggestion, I'm afraid you'll have to put debug 
>stores to video memory all over startup code.
>
>C example (assumes 1:1 address mapping)
>
>char *p = (char*)0x000b8000;  // color VGA text framebuffer
>p[(col+row*80)*2] = 'Z';      // character
>p[(col+row*80)*2+1] = 0x0f;   // attr (0x0f=white on black)
>
>You may try this first with booting kernel to be sure it works.
>Good luck.
--
vda

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

end of thread, other threads:[~2003-01-23  9:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-23  4:20 completely undiagnosable (for me) kernel boot problem Sam Gendler
2003-01-23  9:26 ` Denis Vlasenko

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).