FYI: X and Slackware-current changelog - Slackware

This is a discussion on FYI: X and Slackware-current changelog - Slackware ; I notice this remark in the -current changelog: Sat Nov 17 00:19:20 CST 2007 x/xf86-video-intel-2.2.0-i486-1.tgz: Upgraded to xf86-video-intel-2.2.0 x/xf86-video-sis-0.9.4-i486-1.tgz: Upgraded to xf86-video-sis-0.9.4. OK, now that that Samba fix is done, we can give you a working X server. :-) Evidently, ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: FYI: X and Slackware-current changelog

  1. FYI: X and Slackware-current changelog

    I notice this remark in the -current changelog:


    Sat Nov 17 00:19:20 CST 2007

    x/xf86-video-intel-2.2.0-i486-1.tgz: Upgraded to xf86-video-intel-2.2.0
    x/xf86-video-sis-0.9.4-i486-1.tgz: Upgraded to xf86-video-sis-0.9.4.
    OK, now that that Samba fix is done, we can give you a working X server. :-)
    Evidently, the HAL/D-Bus enabled X server, xf86-input-evdev, and one of HAL's
    ..fdi files aren't playing well together. After considering three possible
    workarounds, it was decided to disable D-Bus/HAL support in the X server for
    now. If you really want to play with X input hotplugging, it's easy enough to
    modify the source/x/x11/configure xorg-server configure file to enable D-Bus
    and HAL and run: ./x11.SlackBuild xserver xorg-server
    Xdmx remains gone per X build recommendations.
    x/xorg-server-1.4-i486-4.tgz: Recompiled without input hotplugging support.
    x/xorg-server-xnest-1.4-i486-4.tgz: Rebuilt.
    x/xorg-server-xvfb-1.4-i486-4.tgz: Rebuilt.
    xap/xscreensaver-5.04-i486-1.tgz: Upgraded to xscreensaver-5.04.



    I think, based on PV's comments I will upgrade all of my Slack 12 boxes
    to use the latest X that he has compiled. Also, this morning I noticed
    something on a Slack 12 box which points to something being amiss with
    D-Bus HAL, and appears to confirm his notice. That computer is a server
    and has 1G RAM and 2G swap. It is presently consuming 750M swap, with
    D-BUS claiming 16% of memory (according to top.) This seems excessive,
    especially since I closed out the main services temporarily. I'll check
    what happens when I stop X later (and upgrade X).

    Also, another system (laptop) with the i915 video chipset has
    stopped locking up after this new X was installed. I also upgraded the
    kernel to 2.6.23.8 on that machine, so it could be a combination of
    things, but at least it back to the stability that I am accustomed to
    having with Linux/Slackware.

    AFAIK, the changelog from today's -current, and Slackware 12 will allow
    wholesale migation to the other X, in total without breaking other
    applications, etc. I think this is true because there appears to be no
    library dependancy changes, etc. Also, my test with the laptop appears to
    confirm that nothing is broken.

    --
    Douglas Mayne

  2. Re: FYI: X and Slackware-current changelog

    On Sun, 25 Nov 2007 07:41:56 -0700, Douglas Mayne wrote:
    >
    > AFAIK, the changelog from today's -current, and Slackware 12 will allow
    > wholesale migation to the other X, in total without breaking other
    > applications, etc. I think this is true because there appears to be no
    > library dependancy changes, etc. Also, my test with the laptop appears to
    > confirm that nothing is broken.
    >


    The latest xorg-server seems to have an annoying bug on my laptop.
    The leds for the caps lock, number lock, and scroll lock won't turn
    on under X. If I switch to a vt, then the leds work, switch back to
    X, no lights. Caps lock etc. still toggle, just the lights don't
    turn on.

    There is a semi-usable patch available, but it is not the one xorg
    will be putting in xorg-server 1.4.1, supposedly.

    Brad

    (Patch follows)


    --- xorg-server-1.4/dix/devices.c.orig 2007-10-19 17:04:51.000000000 -0200
    +++ xorg-server-1.4/dix/devices.c 2007-10-23 17:50:38.000000000 -0200
    @@ -294,7 +294,17 @@ CoreKeyboardBell(int volume, DeviceIntPt
    static void
    CoreKeyboardCtl(DeviceIntPtr pDev, KeybdCtrl *ctrl)
    {
    +#ifdef XKB
    + if (!noXkbExtension) {
    + DeviceIntPtr dev = (DeviceIntPtr)
    + pDev->devPrivates[CoreDevicePrivatesIndex].ptr;
    +
    + if (dev && dev->key && dev->key->xkbInfo && dev->key->xkbInfo->kbdProc)
    + (*dev->key->xkbInfo->kbdProc)(dev, ctrl);
    + }
    +#else
    return;
    +#endif
    }

    /**


  3. Re: FYI: X and Slackware-current changelog

    On Sun, 25 Nov 2007 13:13:11 -0600, Bradley Reed wrote:

    > On Sun, 25 Nov 2007 07:41:56 -0700, Douglas Mayne wrote:
    >>
    >> AFAIK, the changelog from today's -current, and Slackware 12 will allow
    >> wholesale migation to the other X, in total without breaking other
    >> applications, etc. I think this is true because there appears to be no
    >> library dependancy changes, etc. Also, my test with the laptop appears to
    >> confirm that nothing is broken.
    >>

    >
    > The latest xorg-server seems to have an annoying bug on my laptop.
    > The leds for the caps lock, number lock, and scroll lock won't turn
    > on under X. If I switch to a vt, then the leds work, switch back to
    > X, no lights. Caps lock etc. still toggle, just the lights don't
    > turn on.
    >


    >

    Thanks for that info. I notice this bug on my desktop system, too. Do you
    know what slackware packages need to be rebuilt if this patch is applied?

    --
    Douglas Mayne

  4. Re: FYI: X and Slackware-current changelog

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On Sun, 25 Nov 2007 12:34:16 -0700, Douglas Mayne wrote:
    > On Sun, 25 Nov 2007 13:13:11 -0600, Bradley Reed wrote:
    >
    >> On Sun, 25 Nov 2007 07:41:56 -0700, Douglas Mayne wrote:
    >>>
    >>> AFAIK, the changelog from today's -current, and Slackware 12 will allow
    >>> wholesale migation to the other X, in total without breaking other
    >>> applications, etc. I think this is true because there appears to be no
    >>> library dependancy changes, etc. Also, my test with the laptop appears to
    >>> confirm that nothing is broken.
    >>>

    >>
    >> The latest xorg-server seems to have an annoying bug on my laptop.
    >> The leds for the caps lock, number lock, and scroll lock won't turn
    >> on under X. If I switch to a vt, then the leds work, switch back to
    >> X, no lights. Caps lock etc. still toggle, just the lights don't
    >> turn on.
    >>

    >
    >>

    > Thanks for that info. I notice this bug on my desktop system, too. Do you
    > know what slackware packages need to be rebuilt if this patch is applied?
    >


    I don't, but I hope it would just be xorg-server. I haven't tried
    rebuilding yet, in hopes xorg-server-1.4.1 would be released soon.
    It was due out on Nov 11th.

    Latest info at:
    http://www.x.org/wiki/Server14Branch

    Brad



    -----BEGIN PGP SIGNATURE-----

    iD8DBQFHSeCBkDp4KjYna1ARAirzAJoD89+wPlsDjIQLZTqjAY 2TL73yaACgq9yM
    FErgBHToPxbQIX7454urHRg=
    =cF8r
    -----END PGP SIGNATURE-----

  5. Re: FYI: X and Slackware-current changelog

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On Sun, 25 Nov 2007 13:13:11 -0600, Bradley Reed wrote:
    >
    > The latest xorg-server seems to have an annoying bug on my laptop.
    > The leds for the caps lock, number lock, and scroll lock won't turn
    > on under X. If I switch to a vt, then the leds work, switch back to
    > X, no lights. Caps lock etc. still toggle, just the lights don't
    > turn on.
    >


    A new xorg-server release was announced yesterday:

    http://lists.freedesktop.org/archive...er/031086.html

    Here is the tarball:

    http://xorg.freedesktop.org/archive/...4.0.90.tar.bz2
    MD5: bb16e969850dbb5d3805cb88d35656d0 xorg-server-1.4.0.90.tar.bz2
    SHA1: 7c492ac32bd83b521f5c016e4728fccf9cba55db
    xorg-server-1.4.0.90.tar.bz2

    I replaced the -current xorg-server-1.4.tar.bz2 with the new one,
    and rebuilt it with the x11.SlackBuild (it also needed Mesa source,
    so I rebuilt it too). I didn't need to make any changes to the
    SlackBuild.

    All the problems I noticed with the 1.4 version are fixed in the
    1.4.0.90 version

    Brad



    -----BEGIN PGP SIGNATURE-----

    iD8DBQFHYaN6kDp4KjYna1ARAneZAKCHSEqPNsZkwvvWH21gWi v5rjMZwgCfXUIO
    rDCkMVs+Q91DIbaB6czt6Zs=
    =k1fM
    -----END PGP SIGNATURE-----

  6. Re: FYI: X and Slackware-current changelog

    On Thu, 13 Dec 2007 15:26:19 -0600, Bradley Reed wrote:

    > -----BEGIN PGP SIGNED MESSAGE-----
    > Hash: SHA1
    >
    > On Sun, 25 Nov 2007 13:13:11 -0600, Bradley Reed wrote:
    >>
    >> The latest xorg-server seems to have an annoying bug on my laptop.
    >> The leds for the caps lock, number lock, and scroll lock won't turn
    >> on under X. If I switch to a vt, then the leds work, switch back to
    >> X, no lights. Caps lock etc. still toggle, just the lights don't
    >> turn on.
    >>

    >
    > A new xorg-server release was announced yesterday:
    >


    >
    > I replaced the -current xorg-server-1.4.tar.bz2 with the new one,
    > and rebuilt it with the x11.SlackBuild (it also needed Mesa source,
    > so I rebuilt it too). I didn't need to make any changes to the
    > SlackBuild.
    >
    > All the problems I noticed with the 1.4 version are fixed in the
    > 1.4.0.90 version
    >


    >

    Thanks for the notice. I did as you suggested and rebuilt mesa, then
    issued this command:

    ./x11.Slackbuild xserver xorg-server

    The following packages were created:

    /tmp/x11-build/xorg-server-xvfb-1.4.0.90-i486-4.tgz
    /tmp/x11-build/xorg-server-xnest-1.4.0.90-i486-4.tgz
    /tmp/x11-build/xorg-server-1.4.0.90-i486-4.tgz

    X is obviously a complex piece of software. The build process took
    about 30-45 minutes on a Celeron 1.4G with 256M ram. X.org's source (along
    with the Linux kernel) are amazing examples of the power of the free
    software model to manage very complex programming projects. The
    dependancies and inter-relations among all of the pieces appear to have
    fit together when I compiled this module because the compile achieved a
    working X server (and without recompiling the entire X series.) Thanks for
    the hint that Mesa was required because it appears that the X server
    includes from /tmp/Mesa-7.0.2 during the build process. I would have
    guessed that /usr/include/... and /usr/lib/... would be sufficient as
    defaults; however, I know next to nothing about X, though.


    I plan to check whether this fixes a "shift" key problem that has cropped
    up on another box since I replaced X last week. It appears that sometimes
    the shift key is not seen- or it could be that I am a bad typist


    --
    Douglas Mayne

  7. Re: FYI: X and Slackware-current changelog

    On 2007-12-14, Douglas Mayne wrote:
    > ... snip ... (and without recompiling the entire X series.) Thanks for
    > the hint that Mesa was required because it appears that the X server
    > includes from /tmp/Mesa-7.0.2 during the build process. I would have
    > guessed that /usr/include/... and /usr/lib/... would be sufficient as
    > defaults; however, I know next to nothing about X, though.



    This is due to the way the X/ series packages are compiled.
    They're built, but not installed, therefore, Mesa isn't actually
    present on the system as an installed package when the xorg-server
    package is built. Instead of having to install the Mesa package
    onto the development box, Pat told xorg-server to look for the
    Mesa includes and libraries in Mesa's $PKG directory from when it
    was built.

    -RW

  8. Re: FYI: X and Slackware-current changelog

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On Fri, 14 Dec 2007 09:27:36 -0700, Douglas Mayne wrote:
    > On Thu, 13 Dec 2007 15:26:19 -0600, Bradley Reed wrote:
    >
    >> A new xorg-server release was announced yesterday:
    >>

    > Thanks for the notice. I did as you suggested and rebuilt mesa, then
    > issued this command:
    >
    > ./x11.Slackbuild xserver xorg-server
    >
    > I plan to check whether this fixes a "shift" key problem that has cropped
    > up on another box since I replaced X last week. It appears that sometimes
    > the shift key is not seen- or it could be that I am a bad typist
    >


    Glad my post was of some use. Did the new xorg-server package fix
    your "shift" key problem?

    I haven't noticed any problems with the "shift" key here, at least
    nothing I can blame on xorg.

    Brad



    -----BEGIN PGP SIGNATURE-----

    iD8DBQFHZBN8kDp4KjYna1ARAgLgAJ987beveEXdnNzbFthlRe W25MkzdACfTBGc
    7xYyTElGciPHw1Evvi92sTA=
    =eNBL
    -----END PGP SIGNATURE-----

+ Reply to Thread