Framebuffer console not working with Trident Cyberblade/XP (tridentfb)

• Previous message: Tom Davis: "Re: SIGSTOP and Interrupted System Call"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: 29 Jan 2005 16:27:42 -0800

Hi all,

i've been using VESAfb for past few years on my laptop, and it works
fine (TV out and all, althoug not in X but that's another story I
guess)... Now I've wanted to use TridentFB in stead, because of
"AdvanceMame" which does not support VESAfb.

I've compiled tridentfb support, and played around with the kernel
options ... here's my config (I've also tried without the vga= option)

-- /etc/lilo.conf --
<snip>
vga=791
image = /boot/vmtest
root = /dev/hda4
label = test
read-only
append="reboot=b acpi=noirq pci=biosirq lapic resume=/dev/hda2
idebus=66 \
video=tridentfb:1024x768,bpp=16,memsize=16384,fp,noaccel"
<snip>
-- /etc/lilo.conf --

-- .config --
<snip>
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_TRIDENT=y
CONFIG_FB_TRIDENT_ACCEL=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
<snip>
-- .config --

-- dmesg fb stuff --
<snip>
tridentfb: Trident framebuffer 0.7.8-NEWAPI initializing
PCI: Found IRQ 11 for device 0000:01:00.0
tridentfb: framebuffer size = 16384 Kb
tridentfb: 0000:01:00.0 board found
Console: switching to colour frame buffer device 128x48
tridentfb: fb0: Trident frame buffer device 1024x768-16bpp
<snip>
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel i815 Chipset.
agpgart: Maximum main memory to use for agp memory: 262M
agpgart: AGP aperture is 64M @ 0xf0000000
<snip>
-- dmesg fb stuff --

-- lspci -v --
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/XP
(rev 63) (prog-if 00 [VGA])
Subsystem: Toshiba America Info Systems: Unknown device 0001
Flags: bus master, 66Mhz, medium devsel, latency 8, IRQ 11
Memory at fc000000 (32-bit, non-prefetchable) [size=32M]
Memory at fbc00000 (32-bit, non-prefetchable) [size=4M]
Memory at f8000000 (32-bit, non-prefetchable) [size=32M]
Memory at f7ff8000 (32-bit, non-prefetchable) [size=32K]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [80] AGP version 2.0
Capabilities: [90] Power Management version 2
-- lspci -v --

-- uname -a --
Linux lapdjeez 2.6.10 #19 Sun Jan 23 02:07:11 CET 2005 i686 unknown
-- uname -a --

I get a heavily flickering console on boot, and it's divided in two
columns, splitting the screen in halve and on both sides same output.
I've also tried setting some new fbmodes : fbset "1024x768-70" and the
likes, but this just made my screen go a like a flashbulb, waaaaah !!

Is there anything else I could try for my setup ?
Any comments much appreciated.

bye,
Gert

• Previous message: Tom Davis: "Re: SIGSTOP and Interrupted System Call"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]