From: Steven Hanley <sjh@svana.org>
To: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: bad vidmode on debian install
Date: Wed, 8 Nov 2000 01:06:10 +1100 [thread overview]
Message-ID: <20001108010609.A26617@wibble.net> (raw)
All
Anyway trying to upgrade form non debian dist to debian (potato) on my
7220/200, as it is old world I used the hfs floppy image. Anyway it boots
fine but then the video mode is at a frequency such that no text is clear
and it is moving around on the screen a bit (like running X i modes a
machine cant handle)
So I think, all I need to do is type the command line in somewhere to set it
to a vidmode I know works on the machine.
However this alas does not seem to work, there is some data that flashes up
in 80x25 before the vidmode switch on booting any kernel wether it be off
floppy or through bootx into the current ydl install. And looking in
arch/ppc/boot/misc.c this seems to be useful and interesting information
including a bit that should wait for 5 seconds for me to enter command line
arguments. Howevedr the information flashes past so fast I cant even read
it. I am then on booting off the debian install floppy put into this
unusable video mode.
I tried changing the #defined CMDLINE in misc.c to have the appropriate
vidmode command, but then I noticed on a simple makevmlinux the make process
didnt even enter the boot directory and compile the changed misc.c (all this
is using a 2.2.18pre18 from paul's ppc.samba.org from yesterday)
What I want to know is what is the official (tm) way in which I am supposed
to put a command line that will actually be used into the kernel for booting
off the debian hfs rescue floppy. I made the image I wanted fine and gzipped the
vmlinux and placed it on the floppy but due to there being no setting of
video mode it still boots into an unreadable text frame buffer.
I assume rdev is specific to i386 and compressed images. I notice the floppy
uses a simple gzipped vmlinux, not a compressed ppc zImage even.
I assume it may help me to know for future reference how to set the kernel
command line if I am no longer using bootx and thus wil be unable to just
leave the command line there.
Thanks
See You
Steve
--
sjh@wibble.net http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-11-07 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 14:06 Steven Hanley [this message]
2000-11-07 14:08 ` bad vidmode on debian install Olaf Hering
2000-11-07 22:46 ` Steven Hanley
2000-11-07 23:04 ` jpgarcia
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=20001108010609.A26617@wibble.net \
--to=sjh@svana.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.net \
/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;
as well as URLs for NNTP newsgroup(s).