linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Kysilka <goldenfish@bsys.cz>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [aty128fb]  fbset -a not working
Date: Thu, 13 Apr 2006 05:44:51 +0200	[thread overview]
Message-ID: <20060413034451.GA2846@prog3> (raw)


   Hi,

i have ATI Rage128 AGP card.
I was testing framebuffer. Switching resolution in one console working.
Switching all consoles do not working. Only aktual console is switched.

modprobe aty128fb
chvt 1
fbset

mode "640x480-60"
    # D: 25.171 MHz, H: 31.463 kHz, V: 59.930 Hz
    geometry 640 480 640 480 8
    timings 39729 48 16 33 10 96 2
    rgba 8/0,8/0,8/0,0/0
endmode

fbset -a 800x600-100 -depth 32

mode "800x600-100"
    # D: 67.490 MHz, H: 62.491 kHz, V: 99.985 Hz
    geometry 800 600 800 600 32
    timings 14817 216 0 14 7 64 4
    hsync high
    vsync high
    accel true
    rgba 8/16,8/8,8/0,8/24
endmode

chvt 2
fbset

mode "640x480-60"
    # D: 25.171 MHz, H: 31.463 kHz, V: 59.930 Hz
    geometry 640 480 640 480 8
    timings 39729 48 16 33 10 96 2
    rgba 8/0,8/0,8/0,0/0
endmode

Error is independent with color depth end resolution. intelfb and matroxfb
driver working with this feature correctly.

 
less /var/log/kernel.log

Apr 13 05:22:15 prog3 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 19
Apr 13 05:22:15 prog3 kernel: aty128fb: Found Intel x86 BIOS ROM Image
Apr 13 05:22:15 prog3 kernel: aty128fb: Rage128 BIOS located
Apr 13 05:22:15 prog3 kernel: aty128fb: Rage128 TF Ultra AGP [chip rev 0x4] 32M 128-bit SDR SGRAM (1:1)
Apr 13 05:22:15 prog3 kernel: Console: switching to colour frame buffer device 80x30
Apr 13 05:22:15 prog3 kernel: fb0: ATY Rage128 frame buffer device on Rage128 TF Ultra AGP
Apr 13 05:22:15 prog3 kernel: aty128fb: Rage128 MTRR set to ON

goldenfish@prog3:~$ lspci -s "01:00.0" -nv
0000:01:00.0 0300: 1002:5446
        Subsystem: 1787:0100
        Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 19
        Memory at f0000000 (32-bit, prefetchable) [size=64M]
        I/O ports at 9800 [size=256]
        Memory at ff820000 (32-bit, non-prefetchable) [size=16K]
        Expansion ROM at ff800000 [disabled] [size=128K]
        Capabilities: <available only to root>

For testing and another information contact me. I am subscribed in the list.

  thanks
   Pavel Kysilka
    programmer http://www.bsys.cz/


________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Server.

http://www.nod32.com


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

             reply	other threads:[~2006-04-13  3:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13  3:44 Pavel Kysilka [this message]
2006-04-14  0:16 ` [aty128fb] fbset -a not working Antonino A. Daplas

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=20060413034451.GA2846@prog3 \
    --to=goldenfish@bsys.cz \
    --cc=linux-fbdev-devel@lists.sourceforge.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).