Re: [9fans] Problem of last update?

Re: [9fans] Problem of last update?

[erik quanstrom]

> aux/vga: vgactlw: <type radeon>: bad VGA control message "type radeon"
> ...
> rio: can't open display: initdisplay: /dev/draw/new: no frame buffer
> init: rc exit status: rio 23: display open

you need to add vgaradeon	+cur to your plan9.ini.
pull can be pretty antisocial.

- erik

Re: [9fans] Problem of last update?

[erik quanstrom]

On Wed Jan 27 08:08:42 EST 2010, quanstro@quanstro.net wrote:
> > aux/vga: vgactlw: <type radeon>: bad VGA control message "type radeon"
> > ...
> > rio: can't open display: initdisplay: /dev/draw/new: no frame buffer
> > init: rc exit status: rio 23: display open
>
> you need to add vgaradeon	+cur to your plan9.ini.
> pull can be pretty antisocial.

i'm sorry.  that's to your kernel configuration
file *not* plan9.ini.  you'll need to compile a
kernel, too.  evidently my mind is wandering
today.

- erik

Re: [9fans] Problem of last update?

[Pavel Klinkovsky]

> i'm sorry.  that's to your kernel configuration
> file *not* plan9.ini.  you'll need to compile a
> kernel, too.

Oh, thanks. Going to try...

Does it mean they removed the support of Radeon card from the kernel
in last update?

Pavel

Re: [9fans] Problem of last update?

[Pavel Klinkovsky]

> you need to add vgaradeon  +cur to your plan9.ini...
> ...i'm sorry.  that's to your kernel configuration
> file *not* plan9.ini.

This line is already present in the kernel configuration file.
Nevertheless, I rebuilt the kernel and the situation is a little bit
different...

aux/vga: short bios read 5 at c006f got -1

Well...

Pavel

[9fans] vgaradeon (was Re: Problem of last update?)

[Venkatesh Srinivas]

On Wed, Jan 27, 2010 at 08:07:12AM -0500, erik quanstrom wrote:
>> aux/vga: vgactlw: <type radeon>: bad VGA control message "type radeon"
>> ...
>> rio: can't open display: initdisplay: /dev/draw/new: no frame buffer
>> init: rc exit status: rio 23: display open
>
>you need to add vgaradeon	+cur to your plan9.ini.

I guess this brings up something else.

On 1/19, the Radeon driver made it into the Plan 9 distribution; anyone with
a Radeon R100 (7000, 7500, Mobility M6, M7), some R200 (8500, 9000) or
some R300s (9500, 9700) is encouraged to try them out, see if they feel faster
or work for you or whatnot.

The driver also has, disabled-by-default, hardware-accelerated fill and scroll
routines. If you wish to try them out, modify /sys/src/9/pc/vgaradeon.c to define
HW_ACCEL; I'd like to hear if they work on your card and if you can feel any
difference.

In the short term future, I hope to test the driver on a number of other cards
and add some PCI IDs/anything-else-needed, such as the R9600, 9800, and 9200/9250.
Longer-term, my goal is always support for more cards.

Take care,
-- vs

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[erik quanstrom]

> On 1/19, the Radeon driver made it into the Plan 9 distribution; anyone with
> a Radeon R100 (7000, 7500, Mobility M6, M7), some R200 (8500, 9000) or
> some R300s (9500, 9700) is encouraged to try them out, see if they feel faster
> or work for you or whatnot.
>
> The driver also has, disabled-by-default, hardware-accelerated fill and scroll
> routines. If you wish to try them out, modify /sys/src/9/pc/vgaradeon.c to define
> HW_ACCEL; I'd like to hear if they work on your card and if you can feel any
> difference.
>
> In the short term future, I hope to test the driver on a number of other cards
> and add some PCI IDs/anything-else-needed, such as the R9600, 9800, and 9200/9250.
> Longer-term, my goal is always support for more cards.

haven't gotten it to work with "atom" bios on the sb600
integrated chipset.

- erik

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[geoff]

Remember that, on the pc, you should always be able to revert to
monitor=vesa and indeed aux/vga attempts that if it can't recognise
your graphics controller, but it can fail if you're trying to use a
non-vesa resolution.  It even works on multiprocessors now.

	aux/vga -m vesa -p >/tmp/vesa

will generate a list of acceptable vesa modes, including resolutions,
in /tmp/vesa.  The redirection is necessary to avoid interacting with
the vga subsystem while dumping it.

My long-term goal is to eliminate all the vga drivers but vgavesa,
which make up about 10% of the pc kernel port by line count.  This may
not be possible due to currently-working graphics cards with broken
vesa bioses nor desirable because the native drivers are vastly faster
than the vesa driver (though I think we're closing that gap), but it's
worth attempting.  I've used the vesa driver on my usual plan 9
terminals and it's hard to see a difference in performance compared
with the native vga drivers.

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[erik quanstrom]

> My long-term goal is to eliminate all the vga drivers but vgavesa,
> which make up about 10% of the pc kernel port by line count.  This may
> not be possible due to currently-working graphics cards with broken
> vesa bioses nor desirable because the native drivers are vastly faster
> than the vesa driver (though I think we're closing that gap), but it's
> worth attempting.  I've used the vesa driver on my usual plan 9
> terminals and it's hard to see a difference in performance compared
> with the native vga drivers.

this is a great goal.

unfortunately, some of the machines i happen to have
have awful performance with the vesa driver.  in particular,
a scrolling window on my amd sb600 machine will essentially
lock up the machine.  you can't use the mouse to kill the
window.  :-(.  the nvidia driver (for different hardware
in the same machine) performs much better with a bargin
bin card.

also, is it possible to support resolutions greater than
1600x1200x16 with vesa?

- erik

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[Francisco J Ballesteros]

In parallels I have 1920x... using the vesa driver.


On Wed, Jan 27, 2010 at 7:09 PM, erik quanstrom <quanstro@coraid.com> wrote:
>> My long-term goal is to eliminate all the vga drivers but vgavesa,
>> which make up about 10% of the pc kernel port by line count.  This may
>> not be possible due to currently-working graphics cards with broken
>> vesa bioses nor desirable because the native drivers are vastly faster
>> than the vesa driver (though I think we're closing that gap), but it's
>> worth attempting.  I've used the vesa driver on my usual plan 9
>> terminals and it's hard to see a difference in performance compared
>> with the native vga drivers.
>
> this is a great goal.
>
> unfortunately, some of the machines i happen to have
> have awful performance with the vesa driver.  in particular,
> a scrolling window on my amd sb600 machine will essentially
> lock up the machine.  you can't use the mouse to kill the
> window.  :-(.  the nvidia driver (for different hardware
> in the same machine) performs much better with a bargin
> bin card.
>
> also, is it possible to support resolutions greater than
> 1600x1200x16 with vesa?
>
> - erik
>
>

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[geoff]

These drivers appear to be for pre-pci ([e]isa or vlb) vga cards:

vgaark2000pv.c
vgact65545.c
vgaet4000.c

I think that these are excellent candidates for removal.  Are any of
you still using these drivers?  If so, could you try using
monitor=vesa instead and see if that's acceptable, and let me know
privately either way.

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[Gorka Guardiola]

On Wed, Jan 27, 2010 at 6:36 PM,  <geoff@plan9.bell-labs.com> wrote:
>
> My long-term goal is to eliminate all the vga drivers but vgavesa,
> which make up about 10% of the pc kernel port by line count.  This may
> not be possible due to currently-working graphics cards with broken
> vesa bioses nor desirable because the native drivers are vastly faster
> than the vesa driver (though I think we're closing that gap), but it's
> worth attempting.  I've used the vesa driver on my usual plan 9
> terminals and it's hard to see a difference in performance compared
> with the native vga drivers.
>

The problem for me is that many times the vesa modes do not match
the native resolutions on flat screens. This is specially bad in laptops.
I may be wrong but as far as I understand this you
can only use with vesa the modes printed by aux/vga
which are the modes hardwired in the Bios, ¿am I wrong?. I know some
drivers in linux (like in my old vaio) rewrite this modes, would this
be a solution
for this problem?. I don't know nearly enough about vesa...
-- 
- curiosity sKilled the cat

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[ron minnich]

On Wed, Jan 27, 2010 at 3:30 PM, Gorka Guardiola <paurea@gmail.com> wrote:
> . I don't know nearly enough about vesa...


My worry is that, over time, neither will the graphics vendors. I
don't trust them not to screw this up ... why would they continue to
support it?

ron

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[erik quanstrom]

> My worry is that, over time, neither will the graphics vendors. I
> don't trust them not to screw this up ... why would they continue to
> support it?

so windows can display something before it's finished
probing hardware?

- erik

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[ron minnich]

On Wed, Jan 27, 2010 at 4:16 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>> My worry is that, over time, neither will the graphics vendors. I
>> don't trust them not to screw this up ... why would they continue to
>> support it?
>
> so windows can display something before it's finished
> probing hardware?


well that's good to know. If M$ needs it then we're good to go.

ron

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[erik quanstrom]

> well that's good to know. If M$ needs it then we're good to go.

always the optimist!

unfortunately, 2d performance appears to be taking a back
seat to fancy 3d accelerated stuff:

http://www.tomshardware.com/reviews/2d-windows-gdi,2539.html

- erik

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[Pavel Klinkovsky]

> Remember that, on the pc, you should always be able to revert to
> monitor=vesa

Thank you very much for your hint!
In vesa mode my plan9 lives again... ;-)

Pavel

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[arpunk]

> In the short term future, I hope to test the driver on a number of other cards
> and add some PCI IDs/anything-else-needed, such as the R9600, 9800, and 9200/9250.
> Longer-term, my goal is always support for more cards.

I have a RV280 Radeon 9200 card somewhere around.

Will it work right away or do I need to add some PCI IDs to the source?

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[arpunk]

> In the short term future, I hope to test the driver on a number of other cards
> and add some PCI IDs/anything-else-needed, such as the R9600, 9800, and 9200/9250.
> Longer-term, my goal is always support for more cards.

I have a RV280 Radeon 9200 card somewhere around.

Will it work right away or do I need to add some PCI IDs to the source?

Re: [9fans] vgaradeon (was Re: Problem of last update?)

[Pavel Klinkovsky]

> On 1/19, the Radeon driver made it into the Plan 9 distribution; anyone with
> a Radeon R100 (7000, 7500, Mobility M6, M7), some R200 (8500, 9000) or
> some R300s (9500, 9700) is encouraged to try them out, see if they feel faster
> or work for you or whatnot.

Mine does not work at all (see above).
My ThinkPad T30 has got 7500 one...

Pavel