video=ofonly

[Michael]

The QOTD I have today is when I use video=ofonly to get a display while 
logging in, would that negate an X installation from being able to 
access my framebuffer?  I am supposed to use the aty128fb but currently 
I cannot boot with that.

Sven, this is for you, I have compiled the  2.6.12-rc2 kernel twice and 
now I am going to take another stab at compiling the debian kernel.  So 
if you could email me with any instructions, I am at your disposal.

Another question for this list is I read a post on the internet from 
someone who compiled I2C support on their kernel, with an Open Firmware 
framebuffer, and r128 driver  I have no idea what I2C is, and I did 
compile a kernel both with and without it, neither one helped, but could 
someone tell me whether I need that or not?  Also I thought the only 
framebuffer that I could use with the r128 was the aty128fb, but what 
about  the OFfb, is that a possibility for me?
--Mike

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

PBG4 12" and "video=ofonly"

[Pander]

Hi all,

Booting PowerBook G4 12" without append="video=ofonly", is very very 
slow, even with 2.4.21-ben2


Are there any new fixes or work arounds for this?

Thanks,

Pander

Re: PBG4 12" and "video=ofonly"

[Thomas Seyrat]

On April 26, 16:57 (+0200), Benjamin Herrenschmidt wrote:
> > This resulted in a full-screen console with extreme slowness. One can
> > see the different lines wandering at different times e.s. if using
> Let me know if this helps:
[...]

  The console is still extremely slow (apparently once the
  console-screen.sh script has run), with this patch applied (BK tree).

-- 
Thomas Seyrat

Re: PBG4 12" and "video=ofonly"

[Benjamin Herrenschmidt]

On Fri, 2003-04-25 at 17:06, Georg Koss wrote:

> I compiled that 2.4.21-rc1 successfully and installed it without
> append="video=ofonly" in yaboot.conf.
> 
> This resulted in a full-screen console with extreme slowness. One can
> see the different lines wandering at different times e.s. if using


Let me know if this helps:

--- 1.18/drivers/video/riva/fbdev.c Sat Apr  5 16:53:54 2003
+++ edited/drivers/video/riva/fbdev.c   Sat Apr 26 16:56:50 2003
@@ -2069,6 +2069,14 @@
  
riva_set_dispsw(rinfo, disp);
  
+   if (disp->var.accel_flags & FB_ACCELF_TEXT) {
+   if (nomove)
+   disp->scrollmode = SCROLL_YNOMOVE;
+   else
+   disp->scrollmode = 0;
+   } else
+   disp->scrollmode = SCROLL_YREDRAW;
+
DPRINTK("EXIT, returning 0\n");
return 0;
  

Re: PBG4 12" and "video=ofonly"

[Georg Koss]

Hello again!

On Tue, Apr 22, 2003 at 07:45:19PM +0200, Benjamin Herrenschmidt wrote:
> On Mon, 2003-04-21 at 23:49, Georg Koss wrote:
> > 
> > Using PBG4 12" with Woody. It contains a Nvidia Geforce 420 Go graphic
> > adapter.

> 
> First, XFree CVS should fix the above problem. Then, if you get my
> "devel" tree, there are chances rivafb in there works for you...
> 
> Ben.

I compiled that 2.4.21-rc1 successfully and installed it without
append="video=ofonly" in yaboot.conf.

This resulted in a full-screen console with extreme slowness. One can
see the different lines wandering at different times e.s. if using
less  it takes about 5 seconds for the first line to reach the
top of the screen 8(.


THX again

-- 

M.f.G.

Georg Koss

mailto: [EMAIL PROTECTED]

Re: PBG4 12" and "video=ofonly"

[Matthias Schmidt]

* Georg Koss wrote:
> Hello all!
> 
> When I boot, I need the yaboot-option append="video=ofonly" for
> getting an usable console. Otherwhiles I get a small console in the
> center of my LCD which doesn't work proper.

Right.

> As I read, there is a problem after returning from XFree to console
> resulting in something that could be the console I get without the
> append="video=ofonly".
> 
> So my question is if there exists any possibility to get back to that
> video=ofonly behavior (sorry for my simple minded explanation).

If you boot without video=ofonly you'll get a unsuable console, but you
can use X without problems (start/quit/...).

Otherwise I haven't tested. You'll have to choose if you want to use
console or X properly.

-- 
Matthias Schmidt

Re: PBG4 12" and "video=ofonly"

[Benjamin Herrenschmidt]

On Mon, 2003-04-21 at 23:49, Georg Koss wrote:
> Hello all!
> 
> Using PBG4 12" with Woody. It contains a Nvidia Geforce 420 Go graphic
> adapter.
> When I boot, I need the yaboot-option append="video=ofonly" for
> getting an usable console. Otherwhiles I get a small console in the
> center of my LCD which doesn't work proper.
> 
> As I read, there is a problem after returning from XFree to console
> resulting in something that could be the console I get without the
> append="video=ofonly".
> 
> So my question is if there exists any possibility to get back to that
> video=ofonly behavior (sorry for my simple minded explanation).

First, XFree CVS should fix the above problem. Then, if you get my
"devel" tree, there are chances rivafb in there works for you...

Ben.

PBG4 12" and "video=ofonly"

[Georg Koss]

Hello all!

Using PBG4 12" with Woody. It contains a Nvidia Geforce 420 Go graphic
adapter.
When I boot, I need the yaboot-option append="video=ofonly" for
getting an usable console. Otherwhiles I get a small console in the
center of my LCD which doesn't work proper.

As I read, there is a problem after returning from XFree to console
resulting in something that could be the console I get without the
append="video=ofonly".

So my question is if there exists any possibility to get back to that
video=ofonly behavior (sorry for my simple minded explanation).

TIA for any advice &
  
-- 

M.f.G.

Georg Koss

mailto: [EMAIL PROTECTED]

Re: video=ofonly at first boot

[Chris Tillman]

On Tue, Nov 19, 2002 at 11:43:55AM -0800, Curtis Vaughan wrote:
> just finished installing Debian on an iBook, but at the reboot I can't 
> seem to be able to pass the video=ofonly line to the boot script. 
> Exactly what command do I need to provide at the boot prompt in order to 
> get it to boot right?
> 
> Curtis

You can add arguments after the boot image name at the boot: prompt, i.e.

boot: Linux video=ofonly

To fix it so that's not needed, add append="video=ofonly" to your 
/etc/yaboot.conf for the kernel image you are booting.

-- 
**
|Chris Tillman[EMAIL PROTECTED]  |
|  To HAVE, GIVE all TO all (ACIM)   |
**

video=ofonly at first boot

[Curtis Vaughan]

just finished installing Debian on an iBook, but at the reboot I can't 
seem to be able to pass the video=ofonly line to the boot script. 
Exactly what command do I need to provide at the boot prompt in order to 
get it to boot right?


Curtis

Re: video=ofonly

[Chris Tillman]

On Mon, Nov 11, 2002 at 09:33:29PM +0100, eskimo wrote:
> Hey hey all
> 
> I have a problem with the boot image for powermac 7200/75.
> I have a black screen when booting on the floppy, and I don't know how to add 
> the boot option video=ofonly.
> I have the perl patch but I have those errors:
> 
> ./patch-floppy-image.pl 'root=0200 load_ramdisk=1 prompt_ramdisk=1 
> video=ofonly' boot-floppy-hfs.img > boot-video-ofonly.img

> ./patch-floppy-image.pl: line 1: boot-floppy-hfs.img: command not found

It looks like you don't have perl installed? This is a perl script, 
line 1 is: 

#!/usr/bin/perl -w

Is your boot-floppy-hfs.img the one dated 16-May-2002 from the current
woody ftp archive? That one already has the arguments as you have listed,
including video=ofonly. You may need a version without that argument.

This has come up before on 7200s, and actually there are 2 versions of
the floppy image now being supplied (one with video=ofonly, one
without). But the changed version of boot-floppies hasn't been
released yet.

The patch script was made for the earlier version of the boot floppy,
and doesn't work for the current one (which has the video=ofonly argument
already). 

Two options: I can send a version of the patch script which will work
on the current floppy image (just checked it into CVS), or I can send
a version of the image which doesn't have the video=ofonly argument.
You would need to get perl on your machine in order to use the script.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  <http://www.debian.org/releases/stable/installmanual> |
|debian-imac: <http://debian-imac.sourceforge.net>   |
|Chris Tillman[EMAIL PROTECTED]  |
|  To Have, Give All to All (ACIM)   |
**

Re: video=ofonly

[Jason E. Stewart]

"eskimo" <[EMAIL PROTECTED]> writes:

> On Tuesday 12 November 2002 00:32, Jason E. Stewart wrote:
> > "eskimo" <[EMAIL PROTECTED]> writes:
> > > ./patch-floppy-image.pl: line 1: boot-floppy-hfs.img: command not found
> > > ./patch-floppy-image.pl: line 13: my: command not found
> > > ./patch-floppy-image.pl: line 18: my: command not found
> > > ./patch-floppy-image.pl: line 22: my: command not found
> > > ./patch-floppy-image.pl: line 23: syntax error near unexpected token `('
> > > ./patch-floppy-image.pl: line 23: `my $pad_len = $absolute_max_length -
> > > length( $maintain );'
> >
> > That looks suspiciously like you need to run with:
> >
> >   perl ./patch-floopy-image.pl
> >
> > and not just:
> >
> >   ./patch-floopy-image.pl
> >
> > the 'my: command not found' seems to indicate its using /bin/sh and
> > not /usr/bin/perl.
> >
> > jas.
> 
> 
> at the beginning of the script there's that
>  #!/usr/bin/perl -w 

Hmmm.. maybe your perl isn't in /usr/bin/perl?

> and i've tried what you said and i have this:
> 
> Scalar found where operator expected at ./patch-floppy-image.pl line 13, near 
> "$absolute_max_length"
> (Missing operator before  $absolute_max_length?)
> syntax error at ./patch-floppy-image.pl line 13, near "$absolute_max_length "
> Execution of ./patch-floppy-image.pl aborted due to compilation errors.

This is at least perl complaining that the script has syntax errors
and can't be run. 

Sorry, I don't have the script, so I can't help more.

jas.

Re: video=ofonly

[Jason E. Stewart]

"eskimo" <[EMAIL PROTECTED]> writes:

> ./patch-floppy-image.pl: line 1: boot-floppy-hfs.img: command not found
> ./patch-floppy-image.pl: line 13: my: command not found
> ./patch-floppy-image.pl: line 18: my: command not found
> ./patch-floppy-image.pl: line 22: my: command not found
> ./patch-floppy-image.pl: line 23: syntax error near unexpected token `('
> ./patch-floppy-image.pl: line 23: `my $pad_len = $absolute_max_length - 
> length( $maintain );'

That looks suspiciously like you need to run with:

  perl ./patch-floopy-image.pl

and not just:

  ./patch-floopy-image.pl

the 'my: command not found' seems to indicate its using /bin/sh and
not /usr/bin/perl.

jas.

video=ofonly

[eskimo]

Hey hey all

I have a problem with the boot image for powermac 7200/75.
I have a black screen when booting on the floppy, and I don't know how to add 
the boot option video=ofonly.
I have the perl patch but I have those errors:

./patch-floppy-image.pl 'root=0200 load_ramdisk=1 prompt_ramdisk=1 
video=ofonly' boot-floppy-hfs.img > boot-video-ofonly.img
./patch-floppy-image.pl: line 1: boot-floppy-hfs.img: command not found
./patch-floppy-image.pl: line 13: my: command not found
./patch-floppy-image.pl: line 18: my: command not found
./patch-floppy-image.pl: line 22: my: command not found
./patch-floppy-image.pl: line 23: syntax error near unexpected token `('
./patch-floppy-image.pl: line 23: `my $pad_len = $absolute_max_length - 
length( $maintain );'



what can I do.
What do I have to do ?

thanks for your help.

eskimo
___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Re: can I use video=imsttfb? [was: what is the video=ofonly kernel argument]

[Michel Lanners]

On   2 Oct, this message from Chris Tillman echoed through cyberspace:
> On Wed, Oct 02, 2002 at 05:19:41PM +0200, Vinai Kopp wrote:
[vmode/cmode list]
>> This list is wonderfull. Thanks!
> 
> This was listed under atyfb. So it probably won't be quite the same.

Yes, it will, vmode/cmode values are common among all framebuffer
drivers that work on Macs. Look in:

  /usr/src/linux/include/video/macmodes.h

for the full list. Obviously, not all driver/monitor combinations will
support all of them.

Cheers

Michel

-
Michel Lanners |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes|Ask Questions.  Make Mistakes.
L-1710 Luxembourg  |
email   [EMAIL PROTECTED]|
http://www.cpu.lu/~mlan| Learn Always. "

Re: can I use video=imsttfb? [was: what is the video=ofonly kernel argument]

[Chris Tillman]

On Wed, Oct 02, 2002 at 05:19:41PM +0200, Vinai Kopp wrote:
> On Wed, Oct 02, 2002 at 07:37:08AM -0700, Chris Tillman wrote:
> > On Wed, Oct 02, 2002 at 11:47:18AM +0200, Vinai Kopp wrote:
> > > 
> > > Now, would it be possible to specify this:
> > > 
> > >video=imsttfb:vmode:?,cmode:24
> > > 
> > > And what vmode would/could I specify?
> > > I am guessing this on what I read in the bootpromt howto and in
> > > imsttfb.c, but I could likely be dreadfully wrong. Any pointers in the
> > > right directions are very appreciated!
> > 
> > This is the 9600, right? According to macframebuffer.html which I
> > downloaded from somewhere, that should be and ATI Mach64 (you could
> > verify with cat /proc/pci). So then you should be using atyfb, not 
> > imsttfb:
> 
> Yes, this is the 9600/300 - great you remembered it :)
> 
> So I guess it is a imstty, isn't it?
> 

Looks like...

> > SYNTAX
> > 
> > video=x:vmode:vv,cmode:cc r
> > 
> > where x should be replaced with something appropriate for the frame 
> > buffer
> > of your video card or built-in video chipset, vv and cc should be replaced 
> > with
> > a vmode and cmode, respectively, that are supported by your monitor.  r is
> > optional, and can be replaced with an appropriate run-level.  See below for
> > examples of these values.
> 
> This list is wonderfull. Thanks!

This was listed under atyfb. So it probably won't be quite the same.

> > VMODE
> > 
> > vmode refers to both the screen size in pixels (horizontal x vertical) and 
> > the
> > refresh rate (in Hz).
> > 
> > vmode   size(pixels)refresh notes
> > -   --- -
> > 1   512 x 384   60 Hz   Interlaced NTSC
> > 2   512 x 384   60 Hz
> > 3   640 x 480   50 Hz   Interlaced PAL
> > 4   640 x 480   60 Hz   Interlaced NTSC
> > 5   640 x 480   60 Hz
> > 6   640 x 480   67 Hz
> > 7   640 x 870   75 Hz   Portrait
> > 8   768 x 576   50 Hz   Interlaced PAL
> > 9   800 x 600   56 Hz
> > 10  800 x 600   60 Hz
> > 11  800 x 600   72 Hz
> > 12  800 x 600   75 Hz
> > 13  832 x 624   75 Hz
> > 14  1024 x 768  60 Hz
> > 15  1024 x 768  72 Hz
> > 16  1024 x 768  75 Hz
> > 17  1024 x 768  75 Hz
> > 18  1152 x 870  75 Hz
> > 19  1280 x 960  75 Hz
> > 20  1280 x 1024 75 Hz
> > 
> > 
> > CMODE
> > 
> > cmode refers to the bit depth and will be either 8, 16, 24, or 32 (though 24
> > and 32 might actually produce the same result).  To convert bit depth into
> > number of colors simply find 2^(bit depth).  So an 8-bit display will have 
> > 2^8
> > or 256 colors, while a 24-bit display will have 2^24 or 16,777,216 colors
> > (millions of colors).  
> > 
> > This document is:  > href="http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043";>http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043
> 
> I'll try out the parameters tonight!
> 
> Thanks,
> -- 
> Vinai
> Registered Linux User #280755, Debian GNU/Linux  http://counter.li.org/
> Secure eMail with gnupg  http://www.gnupg.org/



-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|   |
|debian-imac:    |
|Chris Tillman[EMAIL PROTECTED]  |
|  To Have, Give All to All (ACIM)   |
**

Re: can I use video=imsttfb? [was: what is the video=ofonly kernel argument]

[Vinai Kopp]

On Wed, Oct 02, 2002 at 07:37:08AM -0700, Chris Tillman wrote:
> On Wed, Oct 02, 2002 at 11:47:18AM +0200, Vinai Kopp wrote:
> > 
> > Now, would it be possible to specify this:
> > 
> >video=imsttfb:vmode:?,cmode:24
> > 
> > And what vmode would/could I specify?
> > I am guessing this on what I read in the bootpromt howto and in
> > imsttfb.c, but I could likely be dreadfully wrong. Any pointers in the
> > right directions are very appreciated!
> 
> This is the 9600, right? According to macframebuffer.html which I
> downloaded from somewhere, that should be and ATI Mach64 (you could
> verify with cat /proc/pci). So then you should be using atyfb, not 
> imsttfb:

Yes, this is the 9600/300 - great you remembered it :)

# cat /proc/pci
[snip hostbridge and stuff]
  Bus  1, device  15, function  0:
Display controller: Integrated Micro Solutions Inc. IMS9129 [Twin
  turbo 128] (rev 1).
  IRQ 29.
  Master Capable.  Latency=32.  Min Gnt=8.Max Lat=8.
  Prefetchable 32 bit memory at 0x9000 [0x90ff]

# lspci -vv  01:0f.0
01:0f.0 Display controller: Integrated Micro Solutions Inc. IMS9129 
[Twin turbo 128] (rev 01)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- SERR-  SYNTAX
> 
> video=x:vmode:vv,cmode:cc r
> 
> where x should be replaced with something appropriate for the frame buffer
> of your video card or built-in video chipset, vv and cc should be replaced 
> with
> a vmode and cmode, respectively, that are supported by your monitor.  r is
> optional, and can be replaced with an appropriate run-level.  See below for
> examples of these values.

This list is wonderfull. Thanks!

> VMODE
> 
> vmode refers to both the screen size in pixels (horizontal x vertical) and the
> refresh rate (in Hz).
> 
> vmode   size(pixels)refresh notes
> -   --- -
> 1   512 x 384   60 Hz   Interlaced NTSC
> 2   512 x 384   60 Hz
> 3   640 x 480   50 Hz   Interlaced PAL
> 4   640 x 480   60 Hz   Interlaced NTSC
> 5   640 x 480   60 Hz
> 6   640 x 480   67 Hz
> 7   640 x 870   75 Hz   Portrait
> 8   768 x 576   50 Hz   Interlaced PAL
> 9   800 x 600   56 Hz
> 10  800 x 600   60 Hz
> 11  800 x 600   72 Hz
> 12  800 x 600   75 Hz
> 13  832 x 624   75 Hz
> 14  1024 x 768  60 Hz
> 15  1024 x 768  72 Hz
> 16  1024 x 768  75 Hz
> 17  1024 x 768  75 Hz
> 18  1152 x 870  75 Hz
> 19  1280 x 960  75 Hz
> 20  1280 x 1024 75 Hz
> 
> 
> CMODE
> 
> cmode refers to the bit depth and will be either 8, 16, 24, or 32 (though 24
> and 32 might actually produce the same result).  To convert bit depth into
> number of colors simply find 2^(bit depth).  So an 8-bit display will have 2^8
> or 256 colors, while a 24-bit display will have 2^24 or 16,777,216 colors
> (millions of colors).  
> 
> This document is:  href="http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043";>http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043

I'll try out the parameters tonight!

Thanks,
-- 
Vinai
Registered Linux User #280755, Debian GNU/Linux  http://counter.li.org/
Secure eMail with gnupg  http://www.gnupg.org/


pgp6Z4vRGghby.pgp
Description: PGP signature

Re: can I use video=imsttfb? [was: what is the video=ofonly kernel argument]

[Chris Tillman]

On Wed, Oct 02, 2002 at 11:47:18AM +0200, Vinai Kopp wrote:
> On Tue, Oct 01, 2002 at 10:51:39PM -0500, Michael Heironimus wrote:
> > On Tue, Oct 01, 2002 at 11:52:46PM +0200, Vinai Kopp wrote:
> > > I finally got the console to work using the "video=ofonly" kernel
> > > arguments.
> > > But what do they mean? I tried to figure it out looking at the fb/*
> > > sources, but they are a bit beyond my humble capabilities. Can it be
> > > explained to someone as ignorant as me?
> > 
> > I'm not a real expert either, but my understanding is that the ofonly
> > driver accesses the video in a generic Open Firmware manner, which gives
> > you no acceleration or other features but will work on pretty much any
> > OF Mac. Since it doesn't use any hardware-specific driver, you can use
> > it when your internal video is unsupported or when the drivers (or
> > hardware) is buggy, but you sacrifice any hardware-dependent features at
> > the same time. You also can't change resolutions on the fly, you're
> > limited to whatever OF thinks your video is set to (usually whatever it
> > was in the last time you booted to Mac OS).
> 
> Thanks for the awnser. That is about what I guessed it would be. :)
> 
> Now, would it be possible to specify this:
> 
>video=imsttfb:vmode:?,cmode:24
> 
> And what vmode would/could I specify?
> I am guessing this on what I read in the bootpromt howto and in
> imsttfb.c, but I could likely be dreadfully wrong. Any pointers in the
> right directions are very appreciated!

This is the 9600, right? According to macframebuffer.html which I
downloaded from somewhere, that should be and ATI Mach64 (you could
verify with cat /proc/pci). So then you should be using atyfb, not 
imsttfb:


SYNTAX

video=x:vmode:vv,cmode:cc r

where x should be replaced with something appropriate for the frame buffer
of your video card or built-in video chipset, vv and cc should be replaced with
a vmode and cmode, respectively, that are supported by your monitor.  r is
optional, and can be replaced with an appropriate run-level.  See below for
examples of these values.


VMODE

vmode refers to both the screen size in pixels (horizontal x vertical) and the
refresh rate (in Hz).

vmode   size(pixels)refresh notes
-   --- -
1   512 x 384   60 Hz   Interlaced NTSC
2   512 x 384   60 Hz
3   640 x 480   50 Hz   Interlaced PAL
4   640 x 480   60 Hz   Interlaced NTSC
5   640 x 480   60 Hz
6   640 x 480   67 Hz
7   640 x 870   75 Hz   Portrait
8   768 x 576   50 Hz   Interlaced PAL
9   800 x 600   56 Hz
10  800 x 600   60 Hz
11  800 x 600   72 Hz
12  800 x 600   75 Hz
13  832 x 624   75 Hz
14  1024 x 768  60 Hz
15  1024 x 768  72 Hz
16  1024 x 768  75 Hz
17  1024 x 768  75 Hz
18  1152 x 870  75 Hz
19  1280 x 960  75 Hz
20  1280 x 1024 75 Hz


CMODE

cmode refers to the bit depth and will be either 8, 16, 24, or 32 (though 24
and 32 might actually produce the same result).  To convert bit depth into
number of colors simply find 2^(bit depth).  So an 8-bit display will have 2^8
or 256 colors, while a 24-bit display will have 2^24 or 16,777,216 colors
(millions of colors).  

This document is: http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043";>http://www.jonh.net/cgi-bin/lppcfom/fom?file=1043

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  <http://www.debian.org/releases/stable/installmanual> |
|debian-imac: <http://debian-imac.sourceforge.net>   |
|Chris Tillman[EMAIL PROTECTED]  |
|  To Have, Give All to All (ACIM)   |
**

can I use video=imsttfb? [was: what is the video=ofonly kernel argument]

[Vinai Kopp]

On Tue, Oct 01, 2002 at 10:51:39PM -0500, Michael Heironimus wrote:
> On Tue, Oct 01, 2002 at 11:52:46PM +0200, Vinai Kopp wrote:
> > I finally got the console to work using the "video=ofonly" kernel
> > arguments.
> > But what do they mean? I tried to figure it out looking at the fb/*
> > sources, but they are a bit beyond my humble capabilities. Can it be
> > explained to someone as ignorant as me?
> 
> I'm not a real expert either, but my understanding is that the ofonly
> driver accesses the video in a generic Open Firmware manner, which gives
> you no acceleration or other features but will work on pretty much any
> OF Mac. Since it doesn't use any hardware-specific driver, you can use
> it when your internal video is unsupported or when the drivers (or
> hardware) is buggy, but you sacrifice any hardware-dependent features at
> the same time. You also can't change resolutions on the fly, you're
> limited to whatever OF thinks your video is set to (usually whatever it
> was in the last time you booted to Mac OS).

Thanks for the awnser. That is about what I guessed it would be. :)

Now, would it be possible to specify this:

   video=imsttfb:vmode:?,cmode:24

And what vmode would/could I specify?
I am guessing this on what I read in the bootpromt howto and in
imsttfb.c, but I could likely be dreadfully wrong. Any pointers in the
right directions are very appreciated!

greetings,
-- 
Vinai
Registered Linux User #280755, Debian GNU/Linux  http://counter.li.org/
Secure eMail with gnupg  http://www.gnupg.org/


pgpU9UmJZgeMm.pgp
Description: PGP signature

Re: what is the video=ofonly kernel argument

[Michael Heironimus]

On Tue, Oct 01, 2002 at 11:52:46PM +0200, Vinai Kopp wrote:
> I finally got the console to work using the "video=ofonly" kernel
> arguments.
> But what do they mean? I tried to figure it out looking at the fb/*
> sources, but they are a bit beyond my humble capabilities. Can it be
> explained to someone as ignorant as me?

I'm not a real expert either, but my understanding is that the ofonly
driver accesses the video in a generic Open Firmware manner, which gives
you no acceleration or other features but will work on pretty much any
OF Mac. Since it doesn't use any hardware-specific driver, you can use
it when your internal video is unsupported or when the drivers (or
hardware) is buggy, but you sacrifice any hardware-dependent features at
the same time. You also can't change resolutions on the fly, you're
limited to whatever OF thinks your video is set to (usually whatever it
was in the last time you booted to Mac OS).

-- 
Michael Heironimus

what is the video=ofonly kernel argument

[Vinai Kopp]

Hi!

after several weeks of trial and error I finally have a running woody
system on my 9600 Powermac! Yay! (Well - I didn't spend ALL my time on
this project, to be honest :)

Thanks to everybody who helped me along the way during the last couple
of months!

I finally got the console to work using the "video=ofonly" kernel
arguments.
But what do they mean? I tried to figure it out looking at the fb/*
sources, but they are a bit beyond my humble capabilities. Can it be
explained to someone as ignorant as me?

The next thing is setting up X, but I will start that tomorrow...

Thanks one more,
-- 
Vinai
Registered Linux User #280755, Debian GNU/Linux  http://counter.li.org/
Secure eMail with gnupg  http://www.gnupg.org/


pgpkVOtPfoq89.pgp
Description: PGP signature

Re: Floppy boot for powerpc: add video=ofonly?

[Chris Tillman]

On Sat, Feb 16, 2002 at 06:41:02PM -0500, Colin Walters wrote:
> On Sat, 2002-02-16 at 00:22, Chris Tillman wrote:
> Actually, I think the debian-safe option in the current b-f has the same
> problem.  We'll have to add some hackery to check whether video=ofonly
> was given, and output that to the generated yaboot.conf.

The current yaboot.conf has two images: install and install-safe,
which adds the argument. I think that's good enough.

Probably I should add something in the manual abbout it though.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  <http://www.debian.org/releases/woody/installmanual>  |
|   debian-imac (potato): <http://debian-imac.sourceforge.net>   |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**

Re: Floppy boot for powerpc: add video=ofonly?

[Colin Walters]

On Sat, 2002-02-16 at 00:22, Chris Tillman wrote:
> Many oldworld powerpc computers need the video=ofonly boot argument in
> order to use the installer. The hfs-boot-floppy image we currently
> provide does not supply this argument. 
> 
> I used a binary editor (beav) to add video=ofonly into the miBoot
> System.bin source file in boot-floppies, and verified that on my
> oldworld machines the modified file enables the floppy to work, where
> before the monitor couldn't sync up. (I replaced spaces in the file,
> and didn't change the file size).

The only issue I can think of is that while it might let the
boot-floppies work initially, the installed system won't have the
video=ofonly, so the user is left wondering why they don't have a
bootable system.

Actually, I think the debian-safe option in the current b-f has the same
problem.  We'll have to add some hackery to check whether video=ofonly
was given, and output that to the generated yaboot.conf.

Re: Floppy boot for powerpc: add video=ofonly?

[Daniel Jacobowitz]

On Fri, Feb 15, 2002 at 10:22:35PM -0700, Chris Tillman wrote:
> Many oldworld powerpc computers need the video=ofonly boot argument in
> order to use the installer. The hfs-boot-floppy image we currently
> provide does not supply this argument. 
> 
> I used a binary editor (beav) to add video=ofonly into the miBoot
> System.bin source file in boot-floppies, and verified that on my
> oldworld machines the modified file enables the floppy to work, where
> before the monitor couldn't sync up. (I replaced spaces in the file,
> and didn't change the file size).
> 
> It's my understanding that this argument would do no harm for any
> powerpc system, at least if it's just the installer boot we're talking
> about. If that's right, I'd like to commit the change to cvs so the
> hfs-boot-floppy image has that argument. Many systems would be enabled
> for floppy usage that otherwise wouldn't work.

Sounds like a good idea.  Go ahead; I don't remember any reason not to
do this.

(that's why I put the spaces in there in the first place!)

-- 
Daniel Jacobowitz   Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer

Floppy boot for powerpc: add video=ofonly?

[Chris Tillman]

Many oldworld powerpc computers need the video=ofonly boot argument in
order to use the installer. The hfs-boot-floppy image we currently
provide does not supply this argument. 

I used a binary editor (beav) to add video=ofonly into the miBoot
System.bin source file in boot-floppies, and verified that on my
oldworld machines the modified file enables the floppy to work, where
before the monitor couldn't sync up. (I replaced spaces in the file,
and didn't change the file size).

It's my understanding that this argument would do no harm for any
powerpc system, at least if it's just the installer boot we're talking
about. If that's right, I'd like to commit the change to cvs so the
hfs-boot-floppy image has that argument. Many systems would be enabled
for floppy usage that otherwise wouldn't work.
  
-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  <http://www.debian.org/releases/woody/installmanual>  |
|   debian-imac (potato): <http://debian-imac.sourceforge.net>   |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**