Re: best framebuffer for YD 3.0.1 on 604e?

From: !David Stoltenberg (w3bg0d_at_d31337m3.mindspring.com)
Date: 11/16/03

  • Next message: Randy Borden: "Oh damn, I deleted the OS."
    Date: Sun, 16 Nov 2003 15:19:21 GMT
    
    

    stefan isaacs wrote:

    >
    > So perhaps I should try the platinum fb again in the kernel arguments when
    > I boot her up?

    In my experience, the kernel arguments only affect -

    1) how much vram is recognized by the OS as available for both console
    video and XFree86 video, and

    2) the resolution(s)/drivers for console video.

    One of the offshoots of this is if the kernel doesn't recognize/support
    your video card, but XFree86 does [= is the case for my box, might be
    the case for you] you need to tell BootX to use ofonly (either check the
    'No video driver' box or specify video=ofonly as an arg) . . . and then
    rely on XFree86 to call the applicable driver. Sometimes you have to be
    pretty explicit in the XF86Config file to get reliability established.

    In my case, I need to set the resolution I want to define for linux on
    the MacOS side, boot with video=ofonly, and then from the command line,
    get a failsafe XF86Config file going via the video config utility
    invoked from the console command line as root.

    In YDL 3 (Sirius), it's > /usr/share/redhat-config-xfree86/xconf.py; the
    redhat-stuff in /usr/share seems to drive most of the config functions
    and most of them seem to work even in non-gnome/kde windowmanagers or
    console command line environments. So I use xconf.py to generate a
    failsafe XF86Config and then tweak it to explicitly define the BusID
    where my vid card lives, and making sure there's a [drivername].o for
    fbdev to detect and hand off to in /usr/X11R6/lib/modules/drivers/video/.

    Section "Device"
            Identifier "Videocard0"
            VendorName "Videocard vendor"
            BoardName "Generic OF compatible"
             Option "fbdev" "/dev/fb0"
             Driver "fbdev"
             BusID "0:14:0"
    EndSection

    For you, this shouldn't be an issue, since IIRC video=platinumfb works
    and is supported in YDL 3 (sigh, must be nice), but if it isn't and your
    screen turns black after a couple dozen lines of activity info at boot,
    you should probably do video=ofonly, get the BusID out of dmesg, and
    rely on a failsafe XF86Config plus fbdev combo to hand off to
    /usr/X11R6/lib/modules/drivers/video/platinum.o (I think that's the
    path, I'm not in linux at the moment).

    > nb. off to try the platinumfb drivers again..

    Good luck !

    D.


  • Next message: Randy Borden: "Oh damn, I deleted the OS."

    Relevant Pages

    • Video blank problem (not X)
      ... After the kernel is read the screen goes blank. ... system continues to boot normally, ... Changing the video card to a spare PCI one resolves the ...
      (comp.os.linux.hardware)
    • Re: Anyone using an Intel D915GAV Motherboard?
      ... The 'workaround' was type some 'whatever' kernel in the ... > search google/archives for intel 815 video headless mouse keyboard. ... There is a kernel panic at boot time. ... I think its a video problem. ...
      (Fedora)
    • Re: headlest setup
      ... fedora does not boot nor echos anything to the terminal console. ... Is there any particular reason why you can't just leave a video card in that ... isn't there a dummy video driver in the kernel stil? ...
      (Fedora)
    • Proposed update of the i386 boot document
      ... THE LINUX/I386 BOOT PROTOCOL ... the Linux kernel uses a rather complicated boot ... may not even support a command line. ... low memory touched by the boot loader -- as low as possible, ...
      (Linux-Kernel)
    • Re: [2.6.25-rc1] jerky mouse cursor and randoooom key repeats
      ... By this I mean that given a specific kernel configuration I can boot it ... # AX.25 network device drivers ...
      (Linux-Kernel)