Re: KDE Themes Missing?

[Pat C]

I was able to get KDM working by switching a value in one of the config 
files from true to false so that it would force KDM to start.  Worked great 
except for the fact that my keyboard didn't work...

I looked online and it seems like it's a fairly common problem.  I just 
decided to turn off the graphical login and just use the console and startx. 
 It's easy and probably less CPU intensive.  Thanks for the help. :)


From: [EMAIL PROTECTED] (Lennart Sorensen)
To: Sven Krahn <[EMAIL PROTECTED]>
CC: debian-amd64@lists.debian.org, Pat C <[EMAIL PROTECTED]>
Subject: Re: KDE Themes Missing?
Date: Wed, 19 Jan 2005 12:44:15 -0500
On Wed, Jan 19, 2005 at 06:38:29PM +0100, Sven Krahn wrote:
> On Wed, 19 Jan 2005 15:30:55 +, Pat C <[EMAIL PROTECTED]> 
wrote:
> > So my debian system is awesome.  I'm using KDE and I love the new KDE 
3.3
> > setup.  However, I can't seem to be able to change the graphical login 
when
> > the computer starts up.  It's this plain drab Debian logo and two 
boxes.  I
>
> If you prefer the standard console login just de-activate xdm
> (unfortunately, 'apt-get remove xdm' has too many dependencies
> (complete KDE) which will be affected as well) in /etc/init.d/ by (as
> root)
>
> # update-rc.d -f xdm remove
> # echo xdm hold | dpkg --set-selections

Why not just: apt-get install kdm, and when it asks, say you want kdm as
the default display manager.  Or change /etc/X11/default-display-manager
file to have the right name.  That is what the init.d files for xdm, kdm
and gdm look at to decide which one of them should actually start.
Len Sorensen

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: pure64 & -ftrapv

[Adam Warner]

[As a followup to Kaare who demonstrated via email that `I think we safely
can assume that "-ftrapv" might not be our most reliable tool right now...']

Here's one example of how overflow can be detected via x86-32/64 inline
assembly: 

Regards,
Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

AMD64 patch for flavio's fglrx debs

[Peter Nelson]

Here's a patch I've made against flavio's latest fglrx packages to 
generate amd64 debs.  I *think* it does the right thing placing the 
32bit drivers in /emul/ia32-linux/usr/X11R6/lib/ and the 64bit ones in 
/usr/X11R6/lib/, with the correct diversions.  It works for me, but I 
don't have any real games to test the 32bit compatability with.

As a side note, module-assistant kicks ass.
-Peter
diff -ur old/fglrx-installer-8.8.25/debian/control 
fglrx-installer-8.8.25/debian/control
--- old/fglrx-installer-8.8.25/debian/control   2004-12-26 17:25:50.0 
-0500
+++ fglrx-installer-8.8.25/debian/control   2005-01-19 18:01:41.0 
-0500
@@ -6,7 +6,7 @@
 Standards-Version: 3.6.1
 
 Package: fglrx-driver
-Architecture: i386
+Architecture: amd64 i386
 Depends: ${shlibs:Depends}, xserver-xfree86 (>= ${XVERSION}), xserver-xfree86 
(<< ${XVERSIONMAX})
 Recommends: fglrx-kernel
 Description: Video driver for the ATI graphics accelerators
@@ -28,7 +28,7 @@
 
 Package: fglrx-driver-dev
 Section: non-free/devel
-Architecture: i386
+Architecture: amd64 i386
 Depends: fglrx-driver
 Description: Video driver for the ATI graphics accelerators (devel files)
  Video driver for the ATI Radeon and FireGL graphics accelerators.
@@ -37,7 +37,7 @@
  and the FGLRXGAMMA extension interface library.
 
 Package: fglrx-kernel-src
-Architecture: i386
+Architecture: amd64 i386
 Depends: debconf, debhelper (>= 4), kernel-package, make
 Recommends: fglrx-driver
 Description: Kernel module source for the ATI graphics accelerators
@@ -46,7 +46,7 @@
  This package provides the kernel module build environment.
 
 Package: fglrx-control-qt3
-Architecture: i386
+Architecture: amd64 i386
 Depends: ${shlibs:Depends}, fglrx-driver
 Conflicts: fglrx-control-qt2
 Description: Control panel for the ATI graphics accelerators
@@ -55,7 +55,7 @@
  This package provides the control panel comnpiled for Qt3.
 
 Package: fglrx-sources
-Architecture: i386
+Architecture: amd64 i386
 Recommends: fglrx-driver, libqt3-mt-dev, xlibs-dev
 Description: Source code for the ATI graphics accelerators control panel
  Video driver for the ATI Radeon and FireGL graphics accelerators.
diff -ur old/fglrx-installer-8.8.25/debian/postrm 
fglrx-installer-8.8.25/debian/postrm
--- old/fglrx-installer-8.8.25/debian/postrm2004-03-22 03:35:44.0 
-0500
+++ fglrx-installer-8.8.25/debian/postrm2005-01-19 20:51:23.0 
-0500
@@ -15,6 +15,16 @@
 
 case "$1" in
 remove)
+   if [ `arch` = 'x86_64' ]; then
+   dpkg-divert --remove --package fglrx-driver \
+   --divert /usr/share/fglrx/diversions/emul/libGL.so.1.2 \
+   --rename /emul/ia32-linux/usr/X11R6/lib/libGL.so.1.2
+
+   if [  -d /usr/share/fglrx/diversions/emul ]; then
+   rmdir /usr/share/fglrx/diversions/emul || true
+   fi
+   fi
+
dpkg-divert --remove --package fglrx-driver \
--divert /usr/share/fglrx/diversions/libGL.so.1.2 \
--rename /usr/X11R6/lib/libGL.so.1.2
diff -ur old/fglrx-installer-8.8.25/debian/preinst 
fglrx-installer-8.8.25/debian/preinst
--- old/fglrx-installer-8.8.25/debian/preinst   2004-03-22 03:35:30.0 
-0500
+++ fglrx-installer-8.8.25/debian/preinst   2005-01-19 20:51:38.0 
-0500
@@ -20,6 +20,16 @@
dpkg-divert --add --package fglrx-driver \
--divert /usr/share/fglrx/diversions/libGL.so.1.2 \
--rename /usr/X11R6/lib/libGL.so.1.2
+
+   if [ `arch` = 'x86_64' ]; then
+   if [ ! -d /usr/share/fglrx/diversions/emul ]; then
+   mkdir -p /usr/share/fglrx/diversions/emul || true
+   fi
+
+   dpkg-divert --add --package fglrx-driver \
+   --divert /usr/share/fglrx/diversions/emul/libGL.so.1.2 \
+   --rename /emul/ia32-linux/usr/X11R6/lib/libGL.so.1.2
+   fi
 ;;
 
 upgrade)
diff -ur old/fglrx-installer-8.8.25/debian/rules 
fglrx-installer-8.8.25/debian/rules
--- old/fglrx-installer-8.8.25/debian/rules 2005-01-18 15:50:14.0 
-0500
+++ fglrx-installer-8.8.25/debian/rules 2005-01-19 20:42:38.0 -0500
@@ -46,7 +46,12 @@
 
 # These file names don't always match XVERSION+PVERSION:
 # look on the driver info page and update accordingly.
-RPMNAME := fglrx_$(subst .,_,$(XVERSION))-$(PVERSION)-1.i386.rpm
+ifeq ($(shell arch),x86_64)
+   RPMNAME := fglrx64_$(subst .,_,$(XVERSION))-$(PVERSION)-1.x86_64.rpm
+else
+   RPMNAME := fglrx_$(subst .,_,$(XVERSION))-$(PVERSION)-1.i386.rpm
+endif
+
 PATCHDIR := debian/patches-$(PVERSION)
 
 # Package names
@@ -107,11 +112,23 @@
dh_installdirs
 
# Create the directories to install into
+   # the amd64 package includes 32bit compatability libraries
+ifeq ($(shell arch),x86_64)
dh_installdirs -p$(PKG_driver) \
+   emul/ia32-linux/usr/X11R6/lib \
+   emul/ia32-linu

Re: Argh! bzflag2 gets stuck (gcc-3.4)

[Jacob]

now this is a problem worth testing, :-)

where exactly does it get stuck?
a crash or just a freeze? does it take out X or can you kill the ps and
all is well?

Because if this doesn't work then what's next? XQF, and go back to
living without "game spy"? I think not.

On Wed, 2005-19-01 at 23:19 +0100, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi folks,
> 
> The new bzflag2 doesn't work for me. It just gets stuck.
> 
> If I download and build the sources from sourceforge,
> then it works.
> 
> 
> Regards
> 
> Harri
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFB7tz/UTlbRTxpHjcRAmJ8AJsF7BzEg8dp5WY25YquXLGKcVg/JwCfSguj
> Q/IEAuLkZSfE1mWzV5CjMNw=
> =lL2G
> -END PGP SIGNATURE-
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Argh! bzflag2 gets stuck (gcc-3.4)

[Harald Dunkel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
The new bzflag2 doesn't work for me. It just gets stuck.
If I download and build the sources from sourceforge,
then it works.
Regards
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB7tz/UTlbRTxpHjcRAmJ8AJsF7BzEg8dp5WY25YquXLGKcVg/JwCfSguj
Q/IEAuLkZSfE1mWzV5CjMNw=
=lL2G
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New ATI fglrx drivers work with AMD64

[Frederik Schueler]

Hi,

On Tue, Jan 18, 2005 at 02:04:56PM +, Jean-Luc Coulon (f5ibh) wrote:
> quick and drity :just build the package with alien then install the  
> .deb with --force-overwrite...

Looking into the .rpm, this procedure WILL break your system.

the /usr/lib/libGL.so.1.2 will be replaced by a 32bit one, while the 64bit
one will be stored in /usr/X11R6/lib64/libGL.so.1.2 where no app will
ever look for it.

The correct locations are:

libGL.so (libc6,x86-64) => /usr/lib/libGL.so
libGL.so (libc6) => /emul/ia32-linux/usr/lib/libGL.so

as ldconfig -p | grep libGL.so shows on a sane system.

just --force-overwrite'installing a deb created by alien from the rpm
will break your OpenGL subsystem.


Using --force-overwrite as a magic bullet on every occasion, like more 
and more people on this list seem to think of it, is a very bad
development. 
Please help fixing buggy packages, filing bugs and patches, instead of
beating things into shape with a sledge hammer.


Kind regards
Frederik Schueler

-- 
ENOSIG


pgpr1loSdMiw2.pgp
Description: PGP signature

Re: atlas3 extensions for sse2, sse, 3dnow?

[Egon Willighagen]

On Wednesday 19 January 2005 07:37 pm, Kurt Roeckx wrote:
> On Wed, Jan 19, 2005 at 07:17:22PM +0100, Egon Willighagen wrote:
> > After reading the debian/README.Debian I ran debian/rules build_record...
> >
> > I think I saw some failing tests there, but not sure... and I don't want
> > to start calculations when the outcome is not correct...
>
> atlas3-base contains a file
> /usr/share/doc/atlas3-base/test_results.gz with the test results
> and nothing in it seems to have failed.

Indeed. But does that also include SSE2 tests?

As requested int he debian/README.Debian in the source package, I've sent my 
build_record results to the maintainer, and will await response... If that 
does not help, I'll report a wishlist bug...

Egon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: atlas3 extensions for sse2, sse, 3dnow?

[Kurt Roeckx]

On Wed, Jan 19, 2005 at 07:17:22PM +0100, Egon Willighagen wrote:
> 
> After reading the debian/README.Debian I ran debian/rules build_record...
> 
> I think I saw some failing tests there, but not sure... and I don't want to 
> start calculations when the outcome is not correct...

atlas3-base contains a file
/usr/share/doc/atlas3-base/test_results.gz with the test results
and nothing in it seems to have failed.


Kurt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: atlas3 extensions for sse2, sse, 3dnow?

[Egon Willighagen]

On Wednesday 19 January 2005 07:10 pm, Kurt Roeckx wrote:
> On Wed, Jan 19, 2005 at 11:39:02AM +0100, Egon Willighagen wrote:
> The atlas3 package itself builds perfectly but those 3 packages
> only seem to be build on i386.

Indeed, that's what the debian/control* files in the source package confirm...

> Note that on amd64 sse is the default but atlas3 seems to be
> selecting -mfpmath=387 during build.
>
> I suggest you file a wishlist bug on the atlas3 package.

After reading the debian/README.Debian I ran debian/rules build_record...

I think I saw some failing tests there, but not sure... and I don't want to 
start calculations when the outcome is not correct...

> > On [1] is links to a nice graph, but I would like to see the list of
> > packages that fail to build, and preferably the reason why. Is such
> > information on the last 3% available somewhere?
>
> www.buildd.net should also have a list of package that are in
> Failed state and those that are in dep-wait.

Ah, nice overview. Thanx.

Egon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: atlas3 extensions for sse2, sse, 3dnow?

[Kurt Roeckx]

On Wed, Jan 19, 2005 at 11:39:02AM +0100, Egon Willighagen wrote:
> 
> Hi all,
> 
> where can I see the status of the packages:
> - atlas3-3dnow
> - atlas3-sse
> - atlas3-sse2
> 
> (I would like to speed up my r-base calculations some more...)

The atlas3 package itself builds perfectly but those 3 packages
only seem to be build on i386.

Note that on amd64 sse is the default but atlas3 seems to be
selecting -mfpmath=387 during build.

I suggest you file a wishlist bug on the atlas3 package.

> On [1] is links to a nice graph, but I would like to see the list of packages 
> that fail to build, and preferably the reason why. Is such information on the 
> last 3% available somewhere?

www.buildd.net should also have a list of package that are in
Failed state and those that are in dep-wait.


Kurt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: USB mouse stops working intermittently with dmesg errors: drivers/usb/input/hid-core.c: input irq status -84 received

[Ernest jw ter Kuile]

On Wednesday 19 January 2005 04:48, Nick Hemsley wrote:
> When I am using a microsoft usb wheel mouse optical, the mouse
> freezes randomly. The mouse will stay frozen until I unplug/replug it.
>
> dmesg reports a truckload of this message:
> drivers/usb/input/hid-core.c: input irq status -84 received


Yep, same here since last weeks upgrade to 2.6.10. Though here the mouse 
doesn't freeze, but reacts a bit slow at times.

I have a usb Logitech mouse, so apparently it's not hardware related.

also unplugging and replugging resolves.

Goswin: thanks for link to bug report. I was looking for that.

Ernest.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KDE Themes Missing?

[Lennart Sorensen]

On Wed, Jan 19, 2005 at 06:38:29PM +0100, Sven Krahn wrote:
> On Wed, 19 Jan 2005 15:30:55 +, Pat C <[EMAIL PROTECTED]> wrote:
> > So my debian system is awesome.  I'm using KDE and I love the new KDE 3.3
> > setup.  However, I can't seem to be able to change the graphical login when
> > the computer starts up.  It's this plain drab Debian logo and two boxes.  I
> 
> If you prefer the standard console login just de-activate xdm
> (unfortunately, 'apt-get remove xdm' has too many dependencies
> (complete KDE) which will be affected as well) in /etc/init.d/ by (as
> root)
> 
> # update-rc.d -f xdm remove
> # echo xdm hold | dpkg --set-selections

Why not just: apt-get install kdm, and when it asks, say you want kdm as
the default display manager.  Or change /etc/X11/default-display-manager
file to have the right name.  That is what the init.d files for xdm, kdm
and gdm look at to decide which one of them should actually start.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KDE Themes Missing?

[Sven Krahn]

On Wed, 19 Jan 2005 15:30:55 +, Pat C <[EMAIL PROTECTED]> wrote:
> So my debian system is awesome.  I'm using KDE and I love the new KDE 3.3
> setup.  However, I can't seem to be able to change the graphical login when
> the computer starts up.  It's this plain drab Debian logo and two boxes.  I

If you prefer the standard console login just de-activate xdm
(unfortunately, 'apt-get remove xdm' has too many dependencies
(complete KDE) which will be affected as well) in /etc/init.d/ by (as
root)

# update-rc.d -f xdm remove
# echo xdm hold | dpkg --set-selections

X (and KDE) will then be started by 'startx'.

I personally use 'autologin' in inittab to automatically login with my
standard user, have a small script in .bash_profile giving me the
choice to start KDE with X.org or XFree86 or remain in the console,
and after 10 seconds launches KDE as the default. This way, I end up
in the graphical environment after booting the machine (and without
any further interaction after switching the power on), but I still
have the choice... (this is a bit off-topic, so drop me a note if you
want the details of this set up).

> tried changing the login using the control panel but that didn't work.  I
> noticed I didn't have any themes installed when I go to the themes section
> so I thought maybe I could download some.  I got two off of the alioth

Themes are provided in 'kdeartworks', check if you have installed this package.

As a side note, I recently experienced when installing the
'kwin-baghira' package (gcc-3.4) that this theme did not show up in
the control center. Downloading and installing the sources from
baghira.sourceforge.net however worked fine for me (if you like the
Mac OS X style you should have a look at the baghira theme,
particularly combined with the transparency and shadowing provided by
the X.org server... but that's a different issue).

> server (.deb) but they still don't show up in the list.  Are themes
> installed in another directory that I'm not aware of?  Thank you!

Not sure what exactly you did, but just downloading the .deb is not
sufficient, you must also install it

# dpkg -i .deb

However, the standard Debian way would be to use apt-get, e.g. like

# apt-get install kdeartworks

This should arrange everything for you.

-- 
Best regards / Mit den besten Grüssen
Sven Krahn

Re: X server can't display 1280x1024 with mga (G550) and LCD Samsung 193P

[Ralf Schmitt]

Arnaud ESPANEL wrote:
Hi,
I already post this in debian-user (2 days ago, no answer for the 
moment), but the issue is not clear for me and may be related to amd64 
arch.

I used to work with a CRT IIYAMA monitor at 1280x1024. Recently, i
switched to a Samsung 193P LCD monitor, and couldn't get 1280x1024
anymore :
X starts normally, but the screen remains black and displays a message
indicating it looks for an analog or digital signal.
I only managed to get 1024x768, 800x600 and 640x480.
The monitor/video card seem to work well, as win98 works correctly at
1280x1024 with the 193P.
(see below for more details on my configuration/log)
I suspect a misconfiguration or an issue with the mga driver...
Any ideas?
I had the same problem (with a different system: xorg running on 
freebsd, g550, and a hyundai LCD). I got it working after copying 
modelines from a knoppix generated X config.

- Ralf
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: hello

[cs]

Hello,

Our Customer Support e-mail address has changed: please use [EMAIL PROTECTED] 
instead. 

Thank you,

Web Ideas International Team
___
Web Ideas International, Inc.
#110, 4335 Pheasant Ridge Drive NE
Suite 224, Blaine MN 55449, U.S.A.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: X server can't display 1280x1024 with mga (G550) and LCD Samsung 193P

[Jacob]

It's not the best solution if it works but have you tried eliminating
the range on the monitor refresh rates? try forcing either 75 or 60 as
the vertical rate. you shouldn't need to but perhaps it picking a bad
mode.

On Wed, 2005-19-01 at 08:57 +0100, Arnaud ESPANEL wrote:
> The problem you mentionned below deal with some type of hardware 
> acceleration (DRI and HAL) ; it should not avoid the display to work at 
> 1280x1024. Furthermore, i got the same errors when using working 
> resolution (1024x768) and everything run fine...
> 
> Jacob wrote:
> > 1.) there is a problem with your MGA driver, may require a reinstall
> > (II) Loading sub module "mga_hal"
> > (II) LoadModule: "mga_hal"
> > (WW) Warning, couldn't open module mga_hal
> > (II) UnloadModule: "mga_hal"
> > (EE) MGA: Failed to load module "mga_hal" (module does not exist, 0)
> > (==) MGA(0): Matrox HAL module not loaded - using builtin mode setup
> > instead
> > 
> > 2) again another mga error
> > drmOpenDevice: minor is 0
> > drmOpenDevice: node name is /dev/dri/card0
> > drmOpenDevice: open result is -1, (Unknown error 999)
> > drmOpenDevice: open result is -1, (Unknown error 999)
> > drmOpenDevice: Open failed
> > drmOpenDevice: minor is 0
> > drmOpenDevice: node name is /dev/dri/card0
> > drmOpenDevice: open result is -1, (Unknown error 999)
> > drmOpenDevice: open result is -1, (Unknown error 999)
> > drmOpenDevice: Open failed
> > [drm] failed to load kernel module "mga"
> > (II) MGA(0): [drm] drmOpen failed
> > (EE) MGA(0): [drm] DRIScreenInit failed.  Disabling DRI.
> > 
> > try reinstalling the MGA stuff, if you can clear these errors it may fix
> > things for you
> > 
> > 
> > On Tue, 2005-18-01 at 22:04 +0100, Arnaud ESPANEL wrote:
> > 
> >>Hi,
> >>
> >>I already post this in debian-user (2 days ago, no answer for the 
> >>moment), but the issue is not clear for me and may be related to amd64 
> >>arch.
> >>
> >>I used to work with a CRT IIYAMA monitor at 1280x1024. Recently, i
> >>switched to a Samsung 193P LCD monitor, and couldn't get 1280x1024
> >>anymore :
> >>X starts normally, but the screen remains black and displays a message
> >>indicating it looks for an analog or digital signal.
> >>I only managed to get 1024x768, 800x600 and 640x480.
> >>The monitor/video card seem to work well, as win98 works correctly at
> >>1280x1024 with the 193P.
> >>(see below for more details on my configuration/log)
> >>
> >>I suspect a misconfiguration or an issue with the mga driver...
> >>Any ideas?
> >>
> >>Configuration :
> >>Linux no2 2.6.8-10-amd64-k8 #1 Sun Jan 9 18:25:28 CET 2005 x86_64 GNU/Linux
> >>Graphic card : Matrox G550
> >>Monitor : Samsung 193P (max res = [EMAIL PROTECTED])
> >>Monitor and video card are connected with DVI ports.
> >>
> >>(See below for XF86Config-4 and the corresponding XFree86.0.log)
> >>
> >>Best regards,
> >>Arnaud
> >>
> >>
> >>XF86Config-4
> >># XF86Config-4 (XFree86 X Window System server configuration file)
> >>#
> >># This file was generated by dexconf, the Debian X Configuration tool, using
> >># values from the debconf database.
> >>#
> >># Edit this file with caution, and see the XF86Config-4 manual page.
> >># (Type "man XF86Config-4" at the shell prompt.)
> >>#
> >># This file is automatically updated on xserver-xfree86 package upgrades
> >>*only*
> >># if it has not been modified since the last upgrade of the xserver-xfree86
> >># package.
> >>#
> >># If you have edited this file but would like it to be automatically updated
> >># again, run the following commands as root:
> >>#
> >>#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
> >>#   md5sum /etc/X11/XF86Config-4 >/var/lib/xfree86/XF86Config-4.md5sum
> >>#   dpkg-reconfigure xserver-xfree86
> >>
> >>Section "Files"
> >> FontPath"unix/:7100"# local font server
> >> # if the local font server has problems, we can fall back on these
> >> FontPath"/usr/lib/X11/fonts/misc"
> >> FontPath"/usr/lib/X11/fonts/cyrillic"
> >> FontPath"/usr/lib/X11/fonts/100dpi/:unscaled"
> >> FontPath"/usr/lib/X11/fonts/75dpi/:unscaled"
> >> FontPath"/usr/lib/X11/fonts/Type1"
> >> FontPath"/usr/lib/X11/fonts/CID"
> >> FontPath"/usr/lib/X11/fonts/Speedo"
> >> FontPath"/usr/lib/X11/fonts/100dpi"
> >> FontPath"/usr/lib/X11/fonts/75dpi"
> >>EndSection
> >>
> >>Section "Module"
> >> Load"GLcore"
> >> Load"bitmap"
> >> Load"dbe"
> >> Load"ddc"
> >> Load"dri"
> >> Load"extmod"
> >> Load"freetype"
> >> Load"glx"
> >> Load"int10"
> >> Load"record"
> >> Load"speedo"
> >> Load"type1"
> >> Load"vbe"
> >> Load"xtt"
> >>EndSection
> >>
> >>Section "InputDevice"
> >> Identifier"Generic Keyboard"
> >> Driver"keyboard"
> >> Option"CoreKeyboard"
> >> Option"XkbRules""xfree86"
> >> Option"XkbModel""pc104"
> >>   

KDE Themes Missing?

[Pat C]

So my debian system is awesome.  I'm using KDE and I love the new KDE 3.3 
setup.  However, I can't seem to be able to change the graphical login when 
the computer starts up.  It's this plain drab Debian logo and two boxes.  I 
tried changing the login using the control panel but that didn't work.  I 
noticed I didn't have any themes installed when I go to the themes section 
so I thought maybe I could download some.  I got two off of the alioth 
server (.deb) but they still don't show up in the list.  Are themes 
installed in another directory that I'm not aware of?  Thank you!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: atlas3 extensions for sse2, sse, 3dnow?

[Daniel van Eeden]

http://packages.qa.debian.org/atlas3
http://ftp.belnet.be/linux/debian-amd64/buildd-logs/

Op wo, 19-01-2005 te 11:39 +0100, schreef Egon Willighagen:
> Hi all,
> 
> where can I see the status of the packages:
> - atlas3-3dnow
> - atlas3-sse
> - atlas3-sse2
> 
> (I would like to speed up my r-base calculations some more...)
> 
> On [1] is links to a nice graph, but I would like to see the list of packages 
> that fail to build, and preferably the reason why. Is such information on the 
> last 3% available somewhere?
> 
> Egon
> 
> 1. http://www.debian.org/ports/amd64/
> 
> 
-- 
Daniel van Eeden <[EMAIL PROTECTED]>


smime.p7s
Description: S/MIME cryptographic signature

Re: NVidia Programs

[Ed Murray]

Hi Jacob,
Thanks for your response. I got it working. I just needed an entry for
my TV display in the X config.

Regards
Ed.


On Tue, 2005-01-18 at 15:08 -0800, Jacob wrote:
> I'm using a 5200FX on an ASUS board and nvtv works.
> 
> I am using my own kernel and the NVIDIA 6629 drivers from NVIDIA.com
> 
> On Wed, 2005-19-01 at 09:17 +1100, Ed Murray wrote:
> > I have just set up a new AMD64 System. I am new to the Debian-AMD64
> > build though the system is running extremely well. It installed quickly
> > and so far I am having very little trouble with it. I have (I think)
> > properly installed the NVidia drivers. All OpenGL programs are so far
> > running correctly. In addition nvidia-settings is also running
> > correctly. 
> > 
> > However when I try to run nvtv I am getting a segfault:
> > nvtvd[8089]: segfault at  rip  rsp
> > 007fb498 error 14
> > I also getting a segfault with nvclock.
> > I am using a Geforce FX 5700LE on a ABIT AV8 motherboard. The system is
> > otherwise rock solid.
> > Can anybody confirm that these programs functioning correctly on the
> > AMD64 System? 
> > 
> > nvtv0.4.7-1
> > nvidia-kernel-2.6.101.0.6629+1-1+1
> > nvidia-kernel-common1.0.6629+1
> > nvidia-glx  1.0.6629+1-1
> > 
> > 
> > Also can anybody confirm that TV out will work with this card or similar
> > on this platform.
> > 
> > Regards
> > Ed Murray
> > 
> > 
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New ATI fglrx drivers work with AMD64

[Jan Kreuzer]

Hi
here is a qucik description how i got the new fglrx working in 64-bit
and 32-bit chroot:

1)Installed a chroot as stated in
https://alioth.debian.org/docman/vi...o.html#id274243
 2) used alien to convert the driver to a tgz and upacked them to a temp
directory
 3) copied the contents of (driverdir)/usr/X11R6/lib64
to /usr/X11R6/lib64
 4) copied the contents of (driverdir)/usr/X11R6/lib into my chroot
(/var/chroot/sid-ia32/usr/X11R6)
 5) build the kernel module
 6) did a mount -o bind /dev /var/chroot/sid-ia32/dev and a
mount -t tmpfs tmpfs /var/chroot/sid-ia32/dev/shm
to make the 32-bit component of the driver happy
 7) fired up X, tested glxinfo = ok, tested glxinfo32 (fromchroot) = ok
 8) fired up nwn = ok
 9) fired up doom3 = crash :(


Maybe this helps 

P.S.: Please CC me, as i am not on the list (only reading through
archives)

Cheers Jan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

atlas3 extensions for sse2, sse, 3dnow?

[Egon Willighagen]

Hi all,

where can I see the status of the packages:
- atlas3-3dnow
- atlas3-sse
- atlas3-sse2

(I would like to speed up my r-base calculations some more...)

On [1] is links to a nice graph, but I would like to see the list of packages 
that fail to build, and preferably the reason why. Is such information on the 
last 3% available somewhere?

Egon

1. http://www.debian.org/ports/amd64/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Latest kicker freezing randomly

[Rafael Rodríguez]

Hi. I'm using the latest kde in pure64, and kicker freezes randomly upon
pressing the "K" menu button.

Anyone having the same problem?

Regards,

Rafael Rodríguez


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Man page problem in the pvm_dev package

[Andreas Jochens]

On 05-Jan-18 14:01, Per Bojsen wrote:
> *** Regarding Re: Man page problem in the pvm_dev package; Kurt Roeckx
> <[EMAIL PROTECTED]> adds:
> 
> Kurt> Could please report this to the debian BTS?  This seems to be a
> Kurt> general problem.
> 
> I would, but reportbug segfaults on me.  I had this problem early in
> December but it went away again around December 14 after a libc
> update.  I'm using the gcc-3.4 archive.  Is anyone else seeing
> segfaults with reportbug?

Yes. It seems to be a problem of python2.3 and gcc-4.0. I do not have
a fix for this yet.

Regards
Andreas Jochens


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New ATI fglrx drivers work with AMD64

[Lorenzo Milesi]

> (WW) fglrx(0): ***
> (WW) fglrx(0): * DRI initialization failed!  *
> (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
> (WW) fglrx(0): * 2D acceleraton available (MMIO) *
> (WW) fglrx(0): * no 3D acceleration available*
> (WW) fglrx(0): * *

I'm getting this error too.
But I have enabled Radeon DRI in kernel, as well as agp for the nvidia
chip (I have the /dev/agpgart)
any idea?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: X server can't display 1280x1024 with mga (G550) and LCD Samsung 193P

[Arnaud ESPANEL]

The problem you mentionned below deal with some type of hardware 
acceleration (DRI and HAL) ; it should not avoid the display to work at 
1280x1024. Furthermore, i got the same errors when using working 
resolution (1024x768) and everything run fine...

Jacob wrote:
1.) there is a problem with your MGA driver, may require a reinstall
(II) Loading sub module "mga_hal"
(II) LoadModule: "mga_hal"
(WW) Warning, couldn't open module mga_hal
(II) UnloadModule: "mga_hal"
(EE) MGA: Failed to load module "mga_hal" (module does not exist, 0)
(==) MGA(0): Matrox HAL module not loaded - using builtin mode setup
instead
2) again another mga error
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
[drm] failed to load kernel module "mga"
(II) MGA(0): [drm] drmOpen failed
(EE) MGA(0): [drm] DRIScreenInit failed.  Disabling DRI.
try reinstalling the MGA stuff, if you can clear these errors it may fix
things for you
On Tue, 2005-18-01 at 22:04 +0100, Arnaud ESPANEL wrote:
Hi,
I already post this in debian-user (2 days ago, no answer for the 
moment), but the issue is not clear for me and may be related to amd64 
arch.

I used to work with a CRT IIYAMA monitor at 1280x1024. Recently, i
switched to a Samsung 193P LCD monitor, and couldn't get 1280x1024
anymore :
X starts normally, but the screen remains black and displays a message
indicating it looks for an analog or digital signal.
I only managed to get 1024x768, 800x600 and 640x480.
The monitor/video card seem to work well, as win98 works correctly at
1280x1024 with the 193P.
(see below for more details on my configuration/log)
I suspect a misconfiguration or an issue with the mga driver...
Any ideas?
Configuration :
Linux no2 2.6.8-10-amd64-k8 #1 Sun Jan 9 18:25:28 CET 2005 x86_64 GNU/Linux
Graphic card : Matrox G550
Monitor : Samsung 193P (max res = [EMAIL PROTECTED])
Monitor and video card are connected with DVI ports.
(See below for XF86Config-4 and the corresponding XFree86.0.log)
Best regards,
Arnaud
XF86Config-4
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades
*only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 >/var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86
Section "Files"
FontPath"unix/:7100"# local font server
# if the local font server has problems, we can fall back on these
FontPath"/usr/lib/X11/fonts/misc"
FontPath"/usr/lib/X11/fonts/cyrillic"
FontPath"/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/CID"
FontPath"/usr/lib/X11/fonts/Speedo"
FontPath"/usr/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/75dpi"
EndSection
Section "Module"
Load"GLcore"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"speedo"
Load"type1"
Load"vbe"
Load"xtt"
EndSection
Section "InputDevice"
Identifier"Generic Keyboard"
Driver"keyboard"
Option"CoreKeyboard"
Option"XkbRules""xfree86"
Option"XkbModel""pc104"
Option"XkbLayout""fr"
EndSection
Section "InputDevice"
Identifier"Configured Mouse"
Driver"mouse"
Option"CorePointer"
Option"Device""/dev/psaux"
Option"Protocol""ImPS/2"
Option"Emulate3Buttons""true"
Option"ZAxisMapping""4 5"
EndSection
Section "InputDevice"
Identifier"Generic Mouse"
Driver"mouse"
Option"SendCoreEvents""true"
Option"Device""/dev/input/mice"
Option"Protocol""ImPS/2"
Option"Emulate3Buttons""true"
Option"ZAxisMapping""4 5"
EndSection
Section "Device"
Identifier"Matrox Graphics, Inc. MGA G550 AGP"
Driver"mga"
EndSection
Section "Monitor"