![](https://seccdn.libravatar.org/avatar/aea1d8248292e6482742234c5cb514de.jpg?s=120&d=mm&r=g)
Felix Miata wrote:
I used to have Matrox cards that had the same limited compatibility with VESA and framebuffer as older Matrox cards. They were AGP G400s.
There is no x64-PCI-E nor AGP slot. There are PCI-E-x4 slots available (2 I think, and maybe (not sure if space allows a 64-bit PCI-X slot.
If it's not too much trouble to fit a gfxcard in a slot, I'd give it a try.
AFAIK, they don't make PCI-E-x4 slot cards and i've never seen a PCI-X card either (It's slower than a PCI-E-x4 slow in terms of bandwidth!
Even with *buntu's Grub 1.98, vga=791
I'm using vga = 0x30A -- I did a vga = ask and 0x30a was the best of the bunch...
As I can imagine. Using 0x30A on a G400 here I hit https://bugzilla.novell.com/show_bug.cgi?id=259577 which is marked fixed but isn't. To get 0x30A's full 132x43 to stick all the way through the init process and on the vttys requires replacing CONSOLE_FONT="lat9w-16.psfu" with CONSOLE_FONT="lat9w-08.psfu" in /etc/sysconfig/console.
--- Maybe that's why my kernel got this during the last boot: /etc/init.d/boot.localfs: line 23: /usr/sbin/iptables: No such file or directory Cannot open font file lat1-08.psfu.gz /etc/init.d/boot.localfs: line 26: /bin/unicode-start: No such file or directory /etc/init.d/boot.localfs: line 27: /usr/sbin/modprobe: No such file or directory Checking file systems... Hmm... iptables in in /sbin, so is modprobe.... guess it needs some symlinks. where did unicode-start go? ... The font is there, it just didn't come up in the right order. ARG!!.. That's why I just want to know why I can't put the mount's in the first step... then it can boot everything else in parallel. Just to figure out what to put in that bug
required what ended up being 20 months with kernel devs in https://bugzilla.kernel.org/show_bug.cgi?id=7513 filed the year before. Some of what's in the kernel bug may be of use to you if you want to futz with framebuffer and/or BIOS modes on MGA any more.
I don't WANT to use a frame-buffer -- it's less readable and slower.
How can you tell BIOS modes are any faster or slower? Here all the BIOS modes on MGA and Intel seem slower than the framebuffer modes. To me all the smaller framebuffer fonts are superior to whatever psfu fonts openSUSE replaces the smaller BIOS fonts with. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org