Re: Extra text modes via vidcontrol...
Quoting Kazutaka YOKOTA (yok...@zodiac.mech.utsunomiya-u.ac.jp): [snip, snip] Are you sure you enabled options VM86 in the kernel configuration file and loaded the vesa module by the boot loader? Hmmm ... When I added options VM86 to my kernel config file I get: su-2.02# config BANTU BANTU:135: unknown option VM86 Unknown option used - it is VERY important that you do make clean make depend before recompiling Kernel build directory is ../../compile/BANTU bantu.cl.msu.edu:dervish uname -a FreeBSD bantu.cl.msu.edu 4.0-CURRENT FreeBSD 4.0-CURRENT #19: Thu Jun 3 13:54:15 EDT 1999 r...@bantu.cl.msu.edu:/usr/src/sys/compile/BANTU i386 I did get splash screen to work with the default 320x200 bmp files ... The files I'm working with are from http://advocacy.freebsd.org/ammunition/splash.html #;^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor derv...@bantu.cl.msu.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Extra text modes via vidcontrol...
Are you sure you enabled options VM86 in the kernel configuration file and loaded the vesa module by the boot loader? Hmmm ... When I added options VM86 to my kernel config file I get: su-2.02# config BANTU BANTU:135: unknown option VM86 Unknown option used - it is VERY important that you do make clean make depend before recompiling Kernel build directory is ../../compile/BANTU Umm, this means that your source tree is not as current as it should be, in order to be called 4.0-CURRENT. The VM86 option was added to the -CURRENT branch long before 3.0-RELEASE! How are you updating your source tree in /usr/src? bantu.cl.msu.edu:dervish uname -a FreeBSD bantu.cl.msu.edu 4.0-CURRENT FreeBSD 4.0-CURRENT #19: Thu Jun 3 13:54 :15 EDT 1999 r...@bantu.cl.msu.edu:/usr/src/sys/compile/BANTU i386 I did get splash screen to work with the default 320x200 bmp files ... The files I'm working with are from http://advocacy.freebsd.org/ammunition/splash.html Good! Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Extra text modes via vidcontrol...
Kazutaka YOKOTA yok...@zodiac.mech.utsunomiya-u.ac.jp writes: su-2.02# config BANTU BANTU:135: unknown option VM86 Unknown option used - it is VERY important that you do make clean make depend before recompiling Kernel build directory is ../../compile/BANTU Umm, this means that your source tree is not as current as it should be, in order to be called 4.0-CURRENT. The VM86 option was added to the -CURRENT branch long before 3.0-RELEASE! How are you updating your source tree in /usr/src? VM86 is no longer an option. Remove it, and everything will be fine. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Extra text modes via vidcontrol...
Quoting Dag-Erling Smorgrav (d...@flood.ping.uio.no): Kazutaka YOKOTA yok...@zodiac.mech.utsunomiya-u.ac.jp writes: su-2.02# config BANTU BANTU:135: unknown option VM86 Unknown option used - it is VERY important that you do make clean make depend before recompiling Kernel build directory is ../../compile/BANTU Umm, this means that your source tree is not as current as it should be, in order to be called 4.0-CURRENT. The VM86 option was added to the -CURRENT branch long before 3.0-RELEASE! How are you updating your source tree in /usr/src? VM86 is no longer an option. Remove it, and everything will be fine. Noted. thanxs ... DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no #;^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor derv...@bantu.cl.msu.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Extra text modes via vidcontrol...
On 02-Jun-99 Kazutaka YOKOTA wrote: 3. The video card doesn't support required graphics modes. Run 'vidcontrol -i mode' and see if the 320x200 256 color mode is supported. The vga driver in FreeBSD may not be able to support all video modes, if the video card's BIOS is not as compatible as it should be. I have a somewhat related question for you: I cannot set many extended text modes (80x60, 80x50, 132x50, etc.) even though they are listed in the output from `vidcontrol -i mode`. My card is a Matrox Millenium G200 AGP if that is any help. Any suggestions for getting all those modes to work? These text modes with more than 25 lines require 8x8 font which is not loaded to the kernel by default. You can load one of 8x8 font files in /usr/share/syscons/fonts via `vidcontrol -f _font_file_name_'. You can automatically load font at boot time by editting /etc/rc.conf.local (3.1-RELEASE or later) or /rc/rc.conf (3.0-RELEASE or earlier includeing 2.2.X). Duh.. Is this documented anywhere? It might be nice if the vidcontrol man page mentioned that certain modes required certain fonts, for instance. Also, do you know of any chipsets that just don't 'work' with the VESA support for large splash screens? We have a bunch of ATI Rage3D cards at my school that won't load any splash screen above 320x200 even though they support VESA 2.0 and contain lots of video modes in their tables. I don't have such list. It is chipset, but BIOS that matters. Are you sure you enabled options VM86 in the kernel configuration file and loaded the vesa module by the boot loader? Yep, but I just checked the ouput of 'vidcontrol /dev/ttyv0 -i mode' and even with VM86 and VESA compiled into the kernel, the only 8-bit graphics mode is 320x200.. blech. Guess all these cards just have crappy BIOS's. Would you tell me more about the bitmap file you are attempting to load? Just a plain ol' 640x480x8 BMP. It does load fine on my workstation with a Matrox G200 and on one of the servers at work that has a Cirrus chip. Kazu --- John Baldwin jobal...@vt.edu -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc Power Users Use the Power to Serve! - http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Extra text modes via vidcontrol...
3. The video card doesn't support required graphics modes. Run 'vidcontrol -i mode' and see if the 320x200 256 color mode is supported. The vga driver in FreeBSD may not be able to support all video modes, if the video card's BIOS is not as compatible as it should be. I have a somewhat related question for you: I cannot set many extended text modes (80x60, 80x50, 132x50, etc.) even though they are listed in the output from `vidcontrol -i mode`. My card is a Matrox Millenium G200 AGP if that is any help. Any suggestions for getting all those modes to work? Also, do you know of any chipsets that just don't 'work' with the VESA support for large splash screens? We have a bunch of ATI Rage3D cards at my school that won't load any splash screen above 320x200 even though they support VESA 2.0 and contain lots of video modes in their tables. Kazu --- John Baldwin jobal...@vt.edu -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc Power Users Use the Power to Serve! - http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Extra text modes via vidcontrol...
3. The video card doesn't support required graphics modes. Run 'vidcontrol -i mode' and see if the 320x200 256 color mode is supported. The vga driver in FreeBSD may not be able to support all video modes, if the video card's BIOS is not as compatible as it should be. I have a somewhat related question for you: I cannot set many extended text modes (80x60, 80x50, 132x50, etc.) even though they are listed in the output from `vidcontrol -i mode`. My card is a Matrox Millenium G200 AGP if that is any help. Any suggestions for getting all those modes to work? These text modes with more than 25 lines require 8x8 font which is not loaded to the kernel by default. You can load one of 8x8 font files in /usr/share/syscons/fonts via `vidcontrol -f _font_file_name_'. You can automatically load font at boot time by editting /etc/rc.conf.local (3.1-RELEASE or later) or /rc/rc.conf (3.0-RELEASE or earlier includeing 2.2.X). Also, do you know of any chipsets that just don't 'work' with the VESA support for large splash screens? We have a bunch of ATI Rage3D cards at my school that won't load any splash screen above 320x200 even though they support VESA 2.0 and contain lots of video modes in their tables. I don't have such list. It is chipset, but BIOS that matters. Are you sure you enabled options VM86 in the kernel configuration file and loaded the vesa module by the boot loader? Would you tell me more about the bitmap file you are attempting to load? Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
