Re: kern/71142; VESA 1024x768 @ the console

From: Ion-Mihai Tetcu (itetcu_at_people.tecnik93.com)
Date: 01/26/05

  • Next message: Joaquin Menchaca: "WPA and 802.11i?"
    Date: Wed, 26 Jan 2005 20:13:30 +0200
    To: Mervin McDougall <mcd_advisory@yahoo.com>
    
    

     [ newbies really isn't the place for this discussion ]

    On Wed, 26 Jan 2005 09:42:41 -0800 (PST)
    Mervin McDougall <mcd_advisory@yahoo.com> wrote:

    >
    > --- Nikolas Britton <freebsd@nbritton.org> wrote:
    >
    > > Ion-Mihai Tetcu wrote:
    > >
    > > >On Mon, 24 Jan 2005 23:42:47 -0600
    > > >Nikolas Britton <freebsd@nbritton.org> wrote:
    > > >
    > > >
    > > >
    > > >>I got tired of having to patch by hand all the
    > > systems I wanted this
    > > >>patch on and all the systems I patched but then
    > > updated with cvsup so I
    > > >>made a simple batch script to do it for me, this
    > > script will do steps
    > > >>1...9 (see below). all you have to do is paste it
    > > into a file and then
    > > >>run it as root (i.e. "sh vesa-patch-script"):
    > > >>
    > > >>
    > > >
    > > >Care to make it a port ? O should I do it for you
    > > put you as maintainer
    > > >or me if you don't have the time to spare ?
    > > >
    > > >
    > > >
    > > >
    > > Make what a port, you mean that hack I called a
    > > script? lol, I guess it
    > > could be, never made a port b4, but it would have to
    > > be redone as I'd
    > > never sign my name to it. It has no error control
    > > except for a cascading
    > > failure if the patch doesn't download or untar and
    > > it should include the
    > > patch to fix the mouse error. I think a better idea
    > > might be to redo it
    > > into a real script and post it to the PR?:
    > > http://www.freebsd.org/cgi/query-pr.cgi?pr=71142

     [ ... ]
     
    > This would be a good addition for persons who do
    > FreeBSD mobile.

    >From what I see the PR has a responsible (delphij@, cc'ed) which makes
    me believe it would be merged into the tree eventually. Now as I didn't
    follow the discussion from the beginning does anyone know about a time
    frame for that ? The port is easy / not time consumming to do but
    maintaining it in the long run isn't so I would like to know if it will
    be merged in the near future.

    > Or perhaps there should be an entire
    > port for mobile FreeBSD, for persons who want
    > applications and are using mobile computers... So it
    > would include everything from the Vesa hack to say
    > battery monitors and perhaps a little how to on how to
    > tweak freebsd for laptops :)

    You're welcome to do it :)

    There are several battery monitors or applets for kde and gnome and a
    "profiler" for different environments .

    -- 
    IOnut
    Unregistered ;) FreeBSD "user"
    _______________________________________________
    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: Joaquin Menchaca: "WPA and 802.11i?"

    Relevant Pages

    • partition/cd recognition problem hal GNOME 2.16 FreeBSD RELEASE 6.2
      ... FreeBSD elbereth.gateway.2wire.net 6.2-RELEASE FreeBSD ... 0xf0000000-0xf7ffffff,0xffa80000-0xffafffff irq 16 at ... fdc0: port ... perm devstat 0444 ...
      (freebsd-questions)
    • usb devices dont "wake up"
      ... Copyright 1992-2008 The FreeBSD Project. ... <ACPI PCI bus> on pcib0 ... port ... soft updates support ...
      (freebsd-questions)
    • Is FreeBSD ready for desktop (Mozilla Flash)
      ... monitor,, somehow the install fails to detect ... "Macromedia Flash plugin is not available for FreeBSD. ... I quote again "Install the www/linuxpluginwrapper port. ... servers, ...
      (comp.unix.bsd.freebsd.misc)
    • Re: Disappointing speed with ZFS
      ... This way the drives are utilized much more, and same goes for the CPU. ... Copyright 1992-2008 The FreeBSD Project. ... acpi0: on motherboard ... port 0x6000-0x60ff mem 0xe8000000-0xefffffff,0xe0400000-0xe040ffff irq 16 at device 0.0 on pci15 ...
      (freebsd-current)
    • ad0: FAILURE - READ_DMA
      ... FreeBSD complains about DMA problems. ... pci0: ... irq 16 at ... port 0xb800-0xb8ff mem ...
      (freebsd-questions)