Re: kern/71142; VESA 1024x768; (Poor Console resolution on Compaq 2103US)

From: Nikolas Britton (freebsd_at_nbritton.org)
Date: 12/24/04

  • Next message: Mervin McDougall: "Re: kern/71142; VESA 1024x768; (Poor Console resolution on Compaq 2103US)" 
    Date: Fri, 24 Dec 2004 05:48:19 -0600
To: Mervin McDougall <mcd_advisory@yahoo.com>

    Disclaimer!!!: please note that this patch was never meant for newbies
    and that if you decide to use it you are basically on your own if you
    have any problems with it. This patch is very much still in alpha
    status, but it does work and if It breaks your system you can always
    back it out.

    >1. do I copy the patch exactly as is from the webpage?
    >
    >
    no, forget the patches from the webpage it's all messed up and you have
    to run it though scripts and edit it and stuff etc etc....
    -----------------------------
    Step 0: su to root.
    Step 1: cd into /tmp
    Step 2: fetch the patch: "fetch
    http://www.nbritton.org/uploads/current-vesa_patch.tar.gz"

    Alternate Source (these patches are from Deng XueFeng BTW):
    http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-08/att-2992/current-vesa_patch.tar.gz

    Step 3: Extract the files from the archive: "tar -zxvf curr*gz"
    Step 4: cd into /usr/src/sys/dev/syscons
    Step 5: patch the files: "patch
    </tmp/current-vesa_patch/current-syscons.diff" (make sure this applies
    cleanly, no error messages!)
    Step 6: cd into /usr/src/usr.sbin/vidcontrol (usr.sbin is not a typo)
    Step 7: Copy the file current-vidcontrol.1 here: "cp
    /tmp/current-vesa_patch/current-vidcontrol.1 ./vidcontrol.1"
    Step 8: Copy the file current-vidcontrol.c here: "cp
    /tmp/current-vesa_patch/current-vidcontrol.c ./vidcontrol.c"
    Step 9: while your in there rebuild vidcontrol: "make && make install &&
    make clean"
    Step 10: cd into /usr/src/sys/i386/conf
    (if you have never done this before then your kernel will be "GENERIC",
    if you have then you don't need me to explain what to do)
    Step 11: Add the kernel option for VESA support to your kernel: echo
    "options VESA" >> GENERIC
    Step 12: Add the kernel option for SC_PIXEL_MODE to your kernel: echo
    "options SC_PIXEL_MODE" >> GENERIC
    Step 13: config your kernel: config GENERIC
    Step 14: cd into ../compile/GENERIC
    Step 15: rebuild your kernel: "make depend && make && make install"
    Step 16: reboot
    (After FreeBSD reboots and loads you will see this message several times
    (ignore it) "vidcontrol: showing the mouse: Invalid argument")
    Step 17: login as root
    Step 18: Now change the video mode "vidcontrol MODE_279"
    (you should now have a console at 1024x768, if you don't you did
    something wrong.)
    Step 19: If everthing seems ok then add it to the /etc/rc.conf file:
    allscreens_flags="MODE_279"
    Step 20: reboot or do a "shutdown now"
    Step 21: login as a normal user, you're done, have fun :-), report any
    bugs your having to I think ether freebsd-current or freebsd-hackers
    mailing lists.

    you can also use "vidcontrol -i mode | grep G" to see a complete list of
    supported modes (this is a list of modes supported by your video card,
    not your monitor!) and if you want you can play with these other modes
    "vidcontrol MODE_modenumber"

    Also note that if you try to update your sources with cvsup it will
    overwrite the changes you made to the files so you will have to redo
    steps 0 though 8 again (this is how you can back out the changes if you
    have problems with it).

    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"

  • Next message: Mervin McDougall: "Re: kern/71142; VESA 1024x768; (Poor Console resolution on Compaq 2103US)"

    Relevant Pages

    • Re: kern/71142; VESA 1024x768; (Poor Console resolution on Compaq 2103US)
      ... This patch works better than the previous one that I ... > (if you have never done this before then your kernel ... > (After FreeBSD reboots and loads you will see this ... > mailing lists. ...
      (freebsd-newbies)
    • Re: RT patch acceptance
      ... judge the complexity of a design for that type of system. ... claim that you cannot judge the complexity of a kernel modification. ... Since the patch in question doesn't actually need that information to ... nanokernel's API up to date with additions to Linux's API that RT people ...
      (Linux-Kernel)
    • [RFC] Making percpu module variables have their own memory.
      ... Someone using the -rt patch found that one of the tracing options caused ... 64K for every CPU to cover all the per_cpu variables used in the kernel ... static void wakeup_softirqd_prio ...
      (Linux-Kernel)
    • Re: This is [Re:] How to improve the quality of the kernel[?].
      ... The -mm kernel already implements what your proposed PTS would do. ... If patch have no TS ID, ... Thus i can apply for example lguest patches and implement and test new ... How many open source projects use Bugzilla and how many use the Debian BTS? ...
      (Linux-Kernel)
    • Re: Documentation - how to apply patches for various trees
      ... >> explanation of the various kernel trees and how to apply their patches. ... +a patch to the kernel or, more specifically, what base kernel a patch for ... +and what new version the patch will change the source tree into. ...
      (Linux-Kernel)