Xine barely starts up, and when I close xine, X crashes. The image xine
shows is wrong too. green and purple parts of the image are not aligned
properly. This is also the case for gxine (although X doesn't crash on
closing).

after the crash I found this line repeated three times in my Xorg.0.log:
(EE) FBDEV(0): FBIOBLANK: Invalid argument
followed by:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80b4444]
1: [0xb7fa3420]
2: /usr/lib/xorg/modules/extensions//libGLcore.so(XMesaResizeBuffers+0x29)
[0xb6c6f0c9]
3: /usr/lib/xorg/modules/extensions//libGLcore.so [0xb6c6faf0]
4: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c5052a]
5: /usr/bin/X(ResizeChildrenWinSize+0x1a9) [0x80763c9]
6: /usr/bin/X(miSetShape+0x28a) [0x813321a]
7: /usr/bin/X [0x813e497]
8: /usr/bin/X [0x813e8d4]
9: /usr/bin/X [0x814c03e]
10: /usr/bin/X(Dispatch+0x1ab) [0x80883fb]
11: /usr/bin/X(main+0x489) [0x8070229]
12: /lib/libc.so.6(__libc_start_main+0xd8) [0xb7dabdf8]
13: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x806f561]

Fatal server error:
Caught signal 11. Server aborting

I have slack current (24-04-2007), an nvidia card, and use fbdev (frame
buffer driver for my video card) right now. My kernel version is a git
pulled 2.6.21-rc7 kernel. I realize there are more variables here that may
be causing problems, but maybe running videos using fbdev is known to be
problematic?
I used to run the nvidia blob, but recently tested nouveau and was running
fbdev after that, Yet, I would like to be able to watch a movie once in a
while. Going back to nvidia now was problematic as well, possibly due to
the new kernel, or could the upgrade of X be causing problems?

Roel

lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host
Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
00:0a.0 Mass storage controller: Promise Technology, Inc. PDC20268
(Ultra100 TX2) (rev 02)
00:0b.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
00:0b.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
00:0c.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
00:0c.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
00:0c.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev
04)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/
VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/
A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev
74)
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX
5200] (rev a1)

Once upon a time,Wed, 25 Apr 2007 09:55:33 +0000 to be exact, Roel Kluin
wrote:

> nvidia problems

This problem is solved. My fault. I built qemu a while ago and linked gcc
to an older version of gcc, and forgot to correct it afterward. I built
my kernel later with the older version of gcc as well, and the
discrepancy with other packages may have caused the problems. I rebuilt
my kernel and .

Roel

On 2007-04-25, Roel Kluin <rjckluin@hot_nospam_mail.com> wrote:
>
> This problem is solved. My fault. I built qemu a while ago and linked gcc
> to an older version of gcc, and forgot to correct it afterward. I built
> my kernel later with the older version of gcc as well, and the
> discrepancy with other packages may have caused the problems. I rebuilt
> my kernel and .

Roel:

Have a look at this:
http://www.slackware.com/~alien/slackbuilds/gcc34/

Eric has built gcc and gcc-g++ 3.4.6 for -current. Essentially, you
install these packages, then install the stock gcc and gcc-g++ 4.1.2
packages from -current over the top of them. This should allow qemu
(and other apps that won't build on gcc4) to find gcc-3.4.6.

I've tested this with qemu and confirmed that it works fine, and at least
one other person has used it for another app.

RW

Once upon a time,Wed, 25 Apr 2007 22:51:45 +0000 to be exact, Robby
Workman wrote:

> Have a look at this:
> http://www.slackware.com/~alien/slackbuilds/gcc34/

I'll use that, thanks!

Roel

thanks again,

Also I noticed that gcc-g77 was renamed to gcc-gfortran (upgradepkg
hadn't removed my old gcc-g77-3.4.6 package)

Roel

On 2007-04-26, Roel Kluin <rjckluin@hot_nospam_mail.com> wrote:
>
> Also I noticed that gcc-g77 was renamed to gcc-gfortran (upgradepkg
> hadn't removed my old gcc-g77-3.4.6 package)


Yes, that's covered in UPGRADE.TXT on the mirror.

RW

Roel Kluin <rjckluin@hot_nospam_mail.com> wrote:
> Also I noticed that gcc-g77 was renamed to gcc-gfortran (upgradepkg
> hadn't removed my old gcc-g77-3.4.6 package)

No, gfortran is a wholly new product (Fortran-90/95 compiler) which
is meant for the gcc 4 family. G77 has been discontinued, so isn't
available anymore for that gcc.

There are actually two projects to replace g77, the official GNU one
(gfortran, http://gcc.gnu.org/wiki/GFortran) and the alternative g95
(http://www.g95.org), but neither has come to a real stable release
yet (the last time I looked, at least), daily snapshots are there.
G95 latest "stable" one is 0.9, from aug 2006) and gfortran essentially
refers to the gcc version it is meant FOR (4.2 being the latest) but
also itself mostly is daily snapshots.
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************