linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* quik/kernel interaction
@ 2000-08-07  1:32 Bill Jackson
  2000-08-08 20:46 ` Michel Lanners
  0 siblings, 1 reply; 2+ messages in thread
From: Bill Jackson @ 2000-08-07  1:32 UTC (permalink / raw)
  To: linuxppc-dev


i have tried to upgrade my kernel from 2.2.15 to 2.2.17(test 5 and benh)
or 2.4.0.  I am able to get the kernels to compile, but they won't
boot.  I have modified my quik.conf file and reran quik.  with any of
the new kernels I have made (I also made the existing 2.2.15 kernel), i
get the quik boot screen and select the kernel I wish to boot and the
screen goes to the "copying OF device tree....done", then says
'booting', but then it locks up.  i never get the actual  kernel to
load....at one point, i was getting a returning from prom_init message,
but I no longer get that message.  I also at one point got messages
"Initializing Fake screen" and "Failed to get address", followed by a
"returning from prom_init" message...but the kernel never actually
loads...I have /boot on /dev/sda2 and have tried everything I can think
of to fix this.  I have used multiple kernels as I thought the problem
was kernel related (first occured when I went to 2.4.0, that didn't
work, so I tried 2.2.17, that didn't work, so I got 2.2.17-benh, that
didn't work either).   Since all these kernels are displaying the same
problem, I think I am doing something wrong, but I don't know
what....any assistance/offers/ideas are greatly appreciated...


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

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

end of thread, other threads:[~2000-08-08 20:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-08-07  1:32 quik/kernel interaction Bill Jackson
2000-08-08 20:46 ` Michel Lanners

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