Professional Web Applications Themes

[PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT - FreeBSD

Hi, I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati mobility radeon 9600. Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does not work, 90x60 is the highest resolution I can get for now. It looks like I'm not the only one having this problem with ati chipsets: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w ww/db/text/2005/freebsd-questions/20050123.freebsd-questions I saw this posting: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht ml Unfortunately I'm not a programmer and have no ... to very poor patching skills. It looks to me, that in this posting(s) a "few" patches are grouped together to enable vesa 1024x768. 1) Has someone applied this patches? 2) As ...

  1. #1

    Default [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Hi,

    I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati
    mobility radeon 9600.
    Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does
    not work, 90x60 is the highest resolution I can get for now.
    It looks like I'm not the only one having this problem with ati
    chipsets:
    http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w
    ww/db/text/2005/freebsd-questions/20050123.freebsd-questions


    I saw this posting:
    http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht
    ml

    Unfortunately I'm not a programmer and have no ... to very poor patching
    skills.
    It looks to me, that in this posting(s) a "few" patches are grouped
    together to enable vesa 1024x768.

    1) Has someone applied this patches?
    2) As the patch(es) is/are on the entire page, I don't know how to
    separate them. Would someone mail me as an attachment the different
    patches and tell me how I should apply them:
    for example, mail me patch1, patch2, patch3
    and the explanation how to patch them:
    cd /usr/src
    patch < ~/patch1
    patch < ~/patch2 ...etc

    In advance, many thanks!
    Didier







    Didier Guest

  2. #2

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Didier Wiroth wrote:
     

    I think the newest and probably best (?) patch was prepared by Xin Li
    (org) who is also committer. I sent this email to him
    (or she? - sorry about that) in case he has some comments. Beware that
    he said he experienced some problems with previous version of the patch.

    I haven't tested this version of the patch myself but it at least
    compiles.

    It's available at http://people.freebsd.org/~delphij/vesa/
    in files syscons.diff.20050215 and vidcontrol.diff.20050215

    You would apply them with:

    cd /usr/src/sys/dev/syscons
    patch < /path/syscons.diff.20050215
    cd /usr/src/usr.sbin/vidcontrol
    patch </path/vidcontrol.diff.20050215
    make clean
    make all
    make install

    You need also to rebuild and reinstall the kernel. You must have
    'options SC_PIXEL_MODE' in your kernel config. You also need to have
    VESA available - you can load it with kldload vesa or include it in the
    kernel with 'options VESA'.

    After reboot with the new kernel you should be able to get list of all
    VESA and standard modes your card support with 'vidcontrol -i mode'. To
    be able to use them as your console mode you need to have the
    appropriate font loaded. The font resolution is seen in vidcontrol
    output in the 'font' column. To load the font 8x8 you can use
    'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To
    set the mode use 'vidcontrol MODE_$num' where $num is the mode number
    (first column in 'vidcontrol -i mode' output).

    HTH

    Michal


    Michal Guest

  3. #3

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Michal Mertl wrote:
     
    >
    >
    > I think the newest and probably best (?) patch was prepared by Xin Li
    > (org) who is also committer. I sent this email to him
    > (or she? - sorry about that) in case he has some comments. Beware that
    > he said he experienced some problems with previous version of the patch.
    >
    > I haven't tested this version of the patch myself but it at least
    > compiles.
    >
    > It's available at http://people.freebsd.org/~delphij/vesa/
    > in files syscons.diff.20050215 and vidcontrol.diff.20050215
    >
    > You would apply them with:
    >
    > cd /usr/src/sys/dev/syscons
    > patch < /path/syscons.diff.20050215
    > cd /usr/src/usr.sbin/vidcontrol
    > patch </path/vidcontrol.diff.20050215
    > make clean
    > make all
    > make install
    >
    > You need also to rebuild and reinstall the kernel. You must have
    > 'options SC_PIXEL_MODE' in your kernel config. You also need to have
    > VESA available - you can load it with kldload vesa or include it in the
    > kernel with 'options VESA'.
    >
    > After reboot with the new kernel you should be able to get list of all
    > VESA and standard modes your card support with 'vidcontrol -i mode'. To
    > be able to use them as your console mode you need to have the
    > appropriate font loaded. The font resolution is seen in vidcontrol
    > output in the 'font' column. To load the font 8x8 you can use
    > 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To
    > set the mode use 'vidcontrol MODE_$num' where $num is the mode number
    > (first column in 'vidcontrol -i mode' output).
    >
    > HTH
    >
    > Michal
    >
    >[/ref]


    I feel like I am missing a lot here. I want to display 132 characters per
    line on my console. I am not running X Windows and it is not a notebook.
    I am running 5.3-RELEASE-p5 #0.

    What is this SC_PIXEL_MODE and where may I find doentation on it? I
    don't find it in /usr/src/sys/i386/conf/NOTES.

    To "rebuild and reinstall the kernel", after editing my
    /usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I
    'make buildkernel' and then 'make installkernel' or is there something
    else I'm missing?

    I note that some of the messages are posted to multiple mailing lists,
    and I suspect that as I only read org I'm not seeing
    the entire story.

    Jay O'Brien
    Rio Linda, California USA
    Jay Guest

  4. #4

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Jay O'Brien wrote: 
    > >
    > >
    > > I think the newest and probably best (?) patch was prepared by Xin Li
    > > (org) who is also committer. I sent this email to him
    > > (or she? - sorry about that) in case he has some comments. Beware that
    > > he said he experienced some problems with previous version of the patch.
    > >
    > > I haven't tested this version of the patch myself but it at least
    > > compiles.
    > >
    > > It's available at http://people.freebsd.org/~delphij/vesa/
    > > in files syscons.diff.20050215 and vidcontrol.diff.20050215
    > >
    > > You would apply them with:
    > >
    > > cd /usr/src/sys/dev/syscons
    > > patch < /path/syscons.diff.20050215
    > > cd /usr/src/usr.sbin/vidcontrol
    > > patch </path/vidcontrol.diff.20050215
    > > make clean
    > > make all
    > > make install
    > >
    > > You need also to rebuild and reinstall the kernel. You must have
    > > 'options SC_PIXEL_MODE' in your kernel config. You also need to have
    > > VESA available - you can load it with kldload vesa or include it in the
    > > kernel with 'options VESA'.
    > >
    > > After reboot with the new kernel you should be able to get list of all
    > > VESA and standard modes your card support with 'vidcontrol -i mode'. To
    > > be able to use them as your console mode you need to have the
    > > appropriate font loaded. The font resolution is seen in vidcontrol
    > > output in the 'font' column. To load the font 8x8 you can use
    > > 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To
    > > set the mode use 'vidcontrol MODE_$num' where $num is the mode number
    > > (first column in 'vidcontrol -i mode' output).
    > >
    > > HTH
    > >
    > > Michal
    > >
    > >[/ref]
    >
    >
    > I feel like I am missing a lot here. I want to display 132 characters per
    > line on my console. I am not running X Windows and it is not a notebook.[/ref]

    It doesn't matter. I only saw the most complaints from notebook owners
    who didn't have text mode console covering all LCD surface.
     

    man syscons(4). It's also mentioned in NOTES although not the NOTES you
    were looking at. Don't forget that on 5.x there are two conf directories
    - one platform independent in /sys/conf and other in /sys/$ARCH/conf.
    Common (platform independent) options like this one are
    in /sys/conf/NOTES.
     

    No, that's the way to do it.
     

    I'm afraid that's quite possible. Please go search the archives.
     

    Michal Mertl

    Prague, Bohemia, Czech Republic :-)

    Michal Guest

  5. #5

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Michal Mertl wrote:
     
    >>
    >>
    >>I feel like I am missing a lot here. I want to display 132 characters per
    >>line on my console. I am not running X Windows and it is not a notebook.[/ref]
    >
    >
    > It doesn't matter. I only saw the most complaints from notebook owners
    > who didn't have text mode console covering all LCD surface.
    >

    >
    >
    > man syscons(4). It's also mentioned in NOTES although not the NOTES you
    > were looking at. Don't forget that on 5.x there are two conf directories
    > - one platform independent in /sys/conf and other in /sys/$ARCH/conf.
    > Common (platform independent) options like this one are
    > in /sys/conf/NOTES.
    >[/ref]


    Thanks! Now that I see that it is perhaps not required for my system, that
    is not a laptop, is it possible that I don't need this at all? Is it
    definitely needed to support 132 character terminal mode, or is just
    needed for laptops?

     
    >
    >
    > No, that's the way to do it.
    >

    >
    >
    > I'm afraid that's quite possible. Please go search the archives.
    >

    >
    >
    > Michal Mertl
    >
    > Prague, Bohemia, Czech Republic :-)
    >[/ref]

    It is wonderful to be a part of a caring community that spans the
    world, without concern for international borders. Fortunately for
    me, everyone uses english; I'm stuck with only one language (plus
    international morse code, but that's another story).

    Jay O'Brien
    Rio Linda, California, USA
    Jay Guest

  6. #6

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Jay O'Brien wrote: 
     
    > >
    > >
    > > It doesn't matter. I only saw the most complaints from notebook owners
    > > who didn't have text mode console covering all LCD surface.
    > >
    > > 
    > >
    > >
    > > man syscons(4). It's also mentioned in NOTES although not the NOTES you
    > > were looking at. Don't forget that on 5.x there are two conf directories
    > > - one platform independent in /sys/conf and other in /sys/$ARCH/conf.
    > > Common (platform independent) options like this one are
    > > in /sys/conf/NOTES.
    > >[/ref]
    >
    >
    > Thanks! Now that I see that it is perhaps not required for my system, that
    > is not a laptop, is it possible that I don't need this at all? Is it
    > definitely needed to support 132 character terminal mode, or is just
    > needed for laptops?[/ref]

    There's no standard VGA 132 character text mode. It's either provided by
    VESA or emulated using some graphics mode. Newer graphics hardware
    stopped supporting extended text modes. If you want such modes you need
    to emulate them (render the characters using lots of small dots instead
    of just writing characters to the adapter which renders them for you).
    Support for this functionality is included in syscons/vga driver when
    you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar
    graphics mode 800x600 dots with 4 bits (16) of color information per
    pixel which can be run on old plain VGA with 256KB of memory.

    The patches we are talking about add support for rendering the
    characters in any graphics mode your card supports (through VESA) with 
    of colours) for a text mode console. You can't use any graphics there
    but the textual resolution will be bigger. There also isn't support for
    using simultaneously more than 16 (or is it 15?) different colors for
    characters even when milions are technically possible.
     

    Yes, it really is great. Not the English though. I'd prefer Czech but
    I'm afraid it's a lost battle :-).

    Michal

    Michal Guest

  7. #7

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Michal Mertl wrote: 
    > of colours) for a text mode console. You can't use any graphics there
    > but the textual resolution will be bigger. There also isn't support for
    > using simultaneously more than 16 (or is it 15?) different colors for
    > characters even when milions are technically possible.
    >[/ref]

    Thanks for the explanation, it is appreciated. I tried the process and
    encountered errors. Here's what happened:

    patch </tmp/syscons.diff.20050215 this went fine.
    patch </tmp/vidcontrol.diff.20050215 returned errors as shown below:

    ////////////////////////////////////////////////////////////

    # patch </tmp/vidcontrol.diff.20050215 Hmm... Looks like a unified diff to me...
    The text leading up to this was:
    --------------------------
    |Index: vidcontrol.1
    |================================================= ==================
    |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v
    |retrieving revision 1.55
    |diff -u -r1.55 vidcontrol.1
    |--- vidcontrol.1 2 Mar 2003 21:04:21 -0000 1.55
    |+++ vidcontrol.1 17 Jan 2005 05:27:25 -0000
    --------------------------
    Patching file vidcontrol.1 using Plan A...
    Hunk #1 succeeded at 11.
    Hunk #2 succeeded at 88.
    Hunk #3 succeeded at 297.
    Hunk #4 succeeded at 532.
    Hmm... The next patch looks like a unified diff to me...
    The text leading up to this was:
    --------------------------
    |Index: vidcontrol.c
    |================================================= ==================
    |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v
    |retrieving revision 1.48
    |diff -u -r1.48 vidcontrol.c
    |--- vidcontrol.c 13 Jan 2005 03:59:44 -0000 1.48
    |+++ vidcontrol.c 17 Jan 2005 05:27:25 -0000
    --------------------------
    Patching file vidcontrol.c using Plan A...
    Hunk #1 succeeded at 24.
    Hunk #2 succeeded at 48.
    Hunk #3 succeeded at 66 with fuzz 1.
    Hunk #4 failed at 187.
    Hunk #5 succeeded at 223.
    Hunk #6 failed at 239.
    Hunk #7 failed at 257.
    Hunk #8 failed at 297.
    Hunk #9 failed at 332.
    Hunk #10 succeeded at 348 with fuzz 2.
    Hunk #11 failed at 377.
    Hunk #12 failed at 419.
    Hunk #13 failed at 507.
    Hunk #14 failed at 572.
    Hunk #15 failed at 669.
    Hunk #16 failed at 722.
    Hunk #17 failed at 743.
    Hunk #18 failed at 806.
    Hunk #19 succeeded at 891.
    Hunk #20 failed at 900.
    Hunk #21 failed at 933.
    Hunk #22 succeeded at 950 with fuzz 2.
    Hunk #23 failed at 962.
    Hunk #24 failed at 985.
    Hunk #25 failed at 1035.
    Hunk #26 failed at 1050.
    Hunk #27 succeeded at 1148.
    Hunk #28 succeeded at 1173.
    Hunk #29 succeeded at 1217.
    Hunk #30 succeeded at 1234.
    19 out of 30 hunks failed--saving rejects to vidcontrol.c.rej
    done

    ////////////////////////////////////////////////////////////

    Not being a c programmer, I can't understand what the
    vidcontrol.c.rej file is trying to tell me. It is a 29K file.

    As I recalled a previous email telling someone to go ahead
    anyway, I went ahead with make clean and that went ok. Then I
    did make all and here's the results:

    ////////////////////////////////////////////////////////////

    make all cc -O -pipe -c /usr/src/usr.sbin/vidcontrol/vidcontrol.c
    /usr/src/usr.sbin/vidcontrol/vidcontrol.c: In function `video_mode':
    /usr/src/usr.sbin/vidcontrol/vidcontrol.c:500: error: `_VESA_800x600_DFL_COLS' undeclared (first use in this function)
    /usr/src/usr.sbin/vidcontrol/vidcontrol.c:500: error: (Each undeclared identifier is reported only once
    /usr/src/usr.sbin/vidcontrol/vidcontrol.c:500: error: for each function it appears in.)
    /usr/src/usr.sbin/vidcontrol/vidcontrol.c:505: error: `_VESA_800x600_DFL_FNSZ' undeclared (first use in this function)
    /usr/src/usr.sbin/vidcontrol/vidcontrol.c:509: error: `_VESA_800x600_DFL_ROWS' undeclared (first use in this function)
    *** Error code 1

    Stop in /usr/src/usr.sbin/vidcontrol.

    ////////////////////////////////////////////////////////////

    I did not do a make install.

    Guidance will be appreciated. Thanks!

    Jay O'Brien
    Rio Linda, California, USA

    Jay Guest

  8. #8

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Jay O'Brien píše v ne 10. 04. 2005 v 15:21 -0700: 
    > > of colours) for a text mode console. You can't use any graphics there
    > > but the textual resolution will be bigger. There also isn't support for
    > > using simultaneously more than 16 (or is it 15?) different colors for
    > > characters even when milions are technically possible.
    > >[/ref]
    >
    > Thanks for the explanation, it is appreciated. I tried the process and
    > encountered errors. Here's what happened:
    >
    > patch </tmp/syscons.diff.20050215 this went fine.
    > patch </tmp/vidcontrol.diff.20050215 returned errors as shown below:
    >
    > ////////////////////////////////////////////////////////////
    >
    > # patch </tmp/vidcontrol.diff.20050215 Hmm... Looks like a unified diff to me...
    > The text leading up to this was:
    > --------------------------
    > |Index: vidcontrol.1
    > |================================================= ==================
    > |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v
    > |retrieving revision 1.55
    > |diff -u -r1.55 vidcontrol.1
    > |--- vidcontrol.1 2 Mar 2003 21:04:21 -0000 1.55
    > |+++ vidcontrol.1 17 Jan 2005 05:27:25 -0000
    > --------------------------
    > Patching file vidcontrol.1 using Plan A...
    > Hunk #1 succeeded at 11.
    > Hunk #2 succeeded at 88.
    > Hunk #3 succeeded at 297.
    > Hunk #4 succeeded at 532.
    > Hmm... The next patch looks like a unified diff to me...
    > The text leading up to this was:
    > --------------------------
    > |Index: vidcontrol.c
    > |================================================= ==================
    > |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v
    > |retrieving revision 1.48
    > |diff -u -r1.48 vidcontrol.c
    > |--- vidcontrol.c 13 Jan 2005 03:59:44 -0000 1.48
    > |+++ vidcontrol.c 17 Jan 2005 05:27:25 -0000
    > --------------------------
    > Patching file vidcontrol.c using Plan A...
    > Hunk #1 succeeded at 24.
    > Hunk #2 succeeded at 48.
    > Hunk #3 succeeded at 66 with fuzz 1.
    > Hunk #4 failed at 187.
    > Hunk #5 succeeded at 223.
    > Hunk #6 failed at 239.
    > Hunk #7 failed at 257.
    > Hunk #8 failed at 297.
    > Hunk #9 failed at 332.
    > Hunk #10 succeeded at 348 with fuzz 2.
    > Hunk #11 failed at 377.
    > Hunk #12 failed at 419.
    > Hunk #13 failed at 507.
    > Hunk #14 failed at 572.
    > Hunk #15 failed at 669.
    > Hunk #16 failed at 722.
    > Hunk #17 failed at 743.
    > Hunk #18 failed at 806.
    > Hunk #19 succeeded at 891.
    > Hunk #20 failed at 900.
    > Hunk #21 failed at 933.
    > Hunk #22 succeeded at 950 with fuzz 2.
    > Hunk #23 failed at 962.
    > Hunk #24 failed at 985.
    > Hunk #25 failed at 1035.
    > Hunk #26 failed at 1050.
    > Hunk #27 succeeded at 1148.
    > Hunk #28 succeeded at 1173.
    > Hunk #29 succeeded at 1217.
    > Hunk #30 succeeded at 1234.
    > 19 out of 30 hunks failed--saving rejects to vidcontrol.c.rej
    > done
    >
    > ////////////////////////////////////////////////////////////
    >
    > Not being a c programmer, I can't understand what the
    > vidcontrol.c.rej file is trying to tell me. It is a 29K file.
    >
    > As I recalled a previous email telling someone to go ahead
    > anyway, I went ahead with make clean and that went ok. Then I
    > did make all and here's the results:[/ref]

    You haven't read the thread in the archives carefully enough, have you?

    Here is what I wrote (privately to the original poster but I explained
    the error to the mailing list too):
     



    Michal

    Michal Guest

  9. Moderated Post

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Removed by Administrator
    Jay Guest
    Moderated Post

  10. #10

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Jay O'Brien wrote: 
    >
    > Yes, but unfortunately I didn't comprehend.

    > >[/ref]
    >
    > I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48.
    > Now all hunks failed. The results are below.[/ref]

    I don't know. The text before the line starting with "Patching" is taken
    from the patch file. The patch program doesn't retrieve any files. So I
    think you either used bad files to patch or bad patchfile.

    You need to have the original files. To check they're correct you can
    use md5 utility.

    md5 vidcontrol.c
    MD5 (vidcontrol.c) = 1068e5a6aff863e2bc7a0c02098d43b1
    md5 vidcontrol.1
    MD5 (vidcontrol.1) = 080d2b84f2e3914090279fee6e5f2406
    md5 vidcontrol.diff.20050215
    MD5 (vidcontrol.diff.20050215) = 67ae12fe2a4fecae1bb7adb141efe021

    You need to see the same strings.

    Then command 'patch < /path/to/vidcontro.diff.20050215' must work.

    Michal

    Michal Guest

  11. #11

    Default Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT

    Michal Mertl wrote:
     
    >>I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48.
    >>Now all hunks failed. The results are below.[/ref]
    >
    >
    > I don't know. The text before the line starting with "Patching" is taken
    > from the patch file. The patch program doesn't retrieve any files. So I
    > think you either used bad files to patch or bad patchfile.
    >
    > You need to have the original files. To check they're correct you can
    > use md5 utility.
    >
    > md5 vidcontrol.c
    > MD5 (vidcontrol.c) = 1068e5a6aff863e2bc7a0c02098d43b1
    > md5 vidcontrol.1
    > MD5 (vidcontrol.1) = 080d2b84f2e3914090279fee6e5f2406
    > md5 vidcontrol.diff.20050215
    > MD5 (vidcontrol.diff.20050215) = 67ae12fe2a4fecae1bb7adb141efe021
    >
    > You need to see the same strings.
    >
    > Then command 'patch < /path/to/vidcontro.diff.20050215' must work.
    >
    > Michal
    >[/ref]

    Michal,

    The md5 results for vidcontrol.diff.20050215 are the same as yours. The other
    files, however, are different. I first did
    fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.c
    fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.1
    to get the files. I now see this doesn't get the correct files. Rather, it gets
    files marked up for the web. Obviously that was a big problem.

    Then, using WinXP Pro and Mozilla, I downloaded the files again from
    http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/
    and I moved them to the FreeBSD machine using WS_FTP Pro.
    Different md5 results again.

    I found that now the first hunk of the patch on vidcontrol.1 failed.

    After much file comparing, I found the differences in the files. The "$FreeBSD"
    line near the beginning of each file had "/repoman/r/ncvs/" in front of
    src/user.sbin/... and when I edited those characters out, the md5 results were
    the same as yours, and the patch completed without errors. I found that the
    vidcontrol.c file would patch ok without editing out those characters, but the
    vidcontrol.1 file would error in hunk #1 if "/repoman/r/ncvs/" was present.

    I rebuilt the kernel with SC_PIXEL MODE and VESA. When it rebooted, I got
    16 lines of "vidcontrol: showing the mouse: Invalid argument" which I see
    from a google search is a common problem.

    Whenever I select a mode with more than 80 characters the screen goes black.
    I loaded cp837-8x8 font, but no change.

    I have the following in /etc/rc.conf, to set up 80x50, could it be the problem?
    font8x8="iso08-8x8"
    font8x14="iso08-8x14"
    font8x16="iso08-8x16"
    scrnmap="iso-8859-1_to_cp437"
    allscreens_flags="-m on 80x50 white black"

    Or perhaps this that I have now in /etc/ttys?
    ttyv0 "/usr/libexec/getty Pc" cons50 on secure
    # Virtual terminals
    ttyv1 "/usr/libexec/getty Pc" cons50 on secure
    ttyv2 "/usr/libexec/getty Pc" cons50 on secure
    ttyv3 "/usr/libexec/getty Pc" cons50 on secure
    ttyv4 "/usr/libexec/getty Pc" cons50 on secure
    ttyv5 "/usr/libexec/getty Pc" cons50 on secure
    ttyv6 "/usr/libexec/getty Pc" cons50 on secure

    At least now I can see what MAY be possible; vidcontrol -i mode returns a
    screenful of fonts to try. Tomorrow I'll identify which ones work and
    which ones don't.

    What next?

    Jay O'Brien
    Rio Linda, California, USA










    Jay Guest

Similar Threads

  1. Support for FreeBSD?
    By little-devil in forum Macromedia Flash Flashcom
    Replies: 0
    Last Post: September 19th, 04:27 PM
  2. What is Freebsd 5.3 safe mode ?
    By John Palmer in forum FreeBSD
    Replies: 3
    Last Post: February 22nd, 10:55 AM
  3. freebsd and oracle 9i support
    By Didier in forum Oracle Server
    Replies: 5
    Last Post: November 4th, 10:48 PM
  4. Informix support on freeBSD for PHP
    By Geoff Geertsen in forum PHP Development
    Replies: 0
    Last Post: August 15th, 11:05 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139