Re: X problems in Stretch with AMD APU?

2017-08-21 Thread Greg Wooledge
On Sat, Aug 19, 2017 at 10:19:59PM +0200, Alle Meije Wink wrote:
> I have a home theatre PC with an AMD A6-3500 APU. Bit of an oldie but still
> plays everything fine. The drivers supplied by the Jessie repositories
> (including fglrx for hardware acceleration) worked fine.
> 
> But then I upgraded to Stretch and suddenly started without X. The debian
> supplied drivers don't seem to support the A6 any more?

Start with:

lspci -nn
dmesg | grep -i firmware

If there are any firmware loading errors, these would probably
indicate a need to install some non-free firmware packages
(e.g. firmware-amd-graphics).

Installing amd64-microcode probably wouldn't hurt either, though it
probably won't have an immediately noticeable effect on your graphics.



Re: X problems in Stretch with AMD APU?

2017-08-20 Thread Zoltán Herman
Hi Alle,

the 4.9 kernel already has amd graphics support, but it needs firmware,
others do not have to(perhaps mesa, opengl, opencl). The X window must be
on the radeon driver.

If I were upgrading then I would always install a new one and switch
off the old(or will be secondary hdd :)
(Even if I sacrifice three days)

systemctl status bluetooth ?

Greetings
Zoltán

2017-08-20 11:14 GMT+02:00 Alle Meije Wink :

> I'm running 4.11
>
> Got a bit further by removing the MESA libraries for GLX support. That
> removed many graphics applications and libraries. Then added
> xserver-xorg-core again and now X starts again.
>
> Some work to do because my (wireless USB) keyboard is not recognised in
> the x session but that should be doable. So it looks like it's OK again but
> not sure what the crucial step was...
>
> On 20 Aug 2017 00:54, "Zoltán Herman"  wrote:
>
>> And what kind of kernel is installed 4.9 or 4.11?
>> Check the kernel log to see if the firmware has been loaded.
>>
>> >>
>> I have a home theatre PC with an AMD A6-3500 APU. Bit of an oldie but
>> still plays everything fine. The drivers supplied by the Jessie
>> repositories (including fglrx for hardware acceleration) worked fine.
>>
>> But then I upgraded to Stretch and suddenly started without X. The debian
>> supplied drivers don't seem to support the A6 any more?
>>
>> I got everything working again 3 weeks ago by installing the proprietary
>> drivers (catalyst 15.9). But now X has gone again and the same catalyst
>> package refuses to install.
>>
>> The error message that the installer gives is that the X version is too
>> low for catalyst?
>>
>> Then I removed (--purge) xserver-xorg-core and reinstalled it. But when I
>> now start X it says 'no screens found'..
>>
>> Is there a way to get the AMD APUs off that generation working in Stretch
>> working again?
>>
>> Or to at least start X again (with a very low resolution, assuming basic
>> hardware)?
>> <<
>> Add non-free to sources.list
>> update
>> install firmware-amd-graphics
>> etc.
>> <<.
>>
>


Re: X problems in Stretch with AMD APU?

2017-08-20 Thread Alle Meije Wink
I'm running 4.11

Got a bit further by removing the MESA libraries for GLX support. That
removed many graphics applications and libraries. Then added
xserver-xorg-core again and now X starts again.

Some work to do because my (wireless USB) keyboard is not recognised in the
x session but that should be doable. So it looks like it's OK again but not
sure what the crucial step was...

On 20 Aug 2017 00:54, "Zoltán Herman"  wrote:

> And what kind of kernel is installed 4.9 or 4.11?
> Check the kernel log to see if the firmware has been loaded.
>
> >>
> I have a home theatre PC with an AMD A6-3500 APU. Bit of an oldie but
> still plays everything fine. The drivers supplied by the Jessie
> repositories (including fglrx for hardware acceleration) worked fine.
>
> But then I upgraded to Stretch and suddenly started without X. The debian
> supplied drivers don't seem to support the A6 any more?
>
> I got everything working again 3 weeks ago by installing the proprietary
> drivers (catalyst 15.9). But now X has gone again and the same catalyst
> package refuses to install.
>
> The error message that the installer gives is that the X version is too
> low for catalyst?
>
> Then I removed (--purge) xserver-xorg-core and reinstalled it. But when I
> now start X it says 'no screens found'..
>
> Is there a way to get the AMD APUs off that generation working in Stretch
> working again?
>
> Or to at least start X again (with a very low resolution, assuming basic
> hardware)?
> <<
> Add non-free to sources.list
> update
> install firmware-amd-graphics
> etc.
> <<.
>


X problems in Stretch with AMD APU?

2017-08-19 Thread Zoltán Herman
And what kind of kernel is installed 4.9 or 4.11?
Check the kernel log to see if the firmware has been loaded.

>>
I have a home theatre PC with an AMD A6-3500 APU. Bit of an oldie but still
plays everything fine. The drivers supplied by the Jessie repositories
(including fglrx for hardware acceleration) worked fine.

But then I upgraded to Stretch and suddenly started without X. The debian
supplied drivers don't seem to support the A6 any more?

I got everything working again 3 weeks ago by installing the proprietary
drivers (catalyst 15.9). But now X has gone again and the same catalyst
package refuses to install.

The error message that the installer gives is that the X version is too low
for catalyst?

Then I removed (--purge) xserver-xorg-core and reinstalled it. But when I
now start X it says 'no screens found'..

Is there a way to get the AMD APUs off that generation working in Stretch
working again?

Or to at least start X again (with a very low resolution, assuming basic
hardware)?
<<
Add non-free to sources.list
update
install firmware-amd-graphics
etc.
<<.


X problems in Stretch with AMD APU?

2017-08-19 Thread Alle Meije Wink
I have a home theatre PC with an AMD A6-3500 APU. Bit of an oldie but still
plays everything fine. The drivers supplied by the Jessie repositories
(including fglrx for hardware acceleration) worked fine.

But then I upgraded to Stretch and suddenly started without X. The debian
supplied drivers don't seem to support the A6 any more?

I got everything working again 3 weeks ago by installing the proprietary
drivers (catalyst 15.9). But now X has gone again and the same catalyst
package refuses to install.

The error message that the installer gives is that the X version is too low
for catalyst?

Then I removed (--purge) xserver-xorg-core and reinstalled it. But when I
now start X it says 'no screens found'..

Is there a way to get the AMD APUs off that generation working in Stretch
working again?

Or to at least start X again (with a very low resolution, assuming basic
hardware)?


squeeze, amd64 and X problems, perhaps nvidia related

2009-12-20 Thread Anders Lennartssson
Some experiences with squeeze on a laptop.

0) The problems below are (at least for me) tricky to debug. I'm
asking for hints
on how to obtain more information about what goes on so that I can make a
formal bug report.

1) I'm experiencing some bugs with X on a laptop, either at wakeup or suddenly
in the middle of a seemingly normal session. It does not really lock,
but it totally
borks my screen by replacing tiles of the original screen content on
other places
of the screen area so it does look somewhat of a caleidoscope image. The
replacing may continue for 5-10 seconds and the limits between different tiles
are somewhat fuzzy though. Sometimes the computer becomes extremeley
slow and the cursor moves now and then in short steps. On one occasion I
think it actually did lock, i.e. I think  that X did not accept any
input, and then I
had to shutdown by the power button.

2) In some instances I have been able to shutdown the computer by
painstakingly slow X moves. When it reboots everything is normal.

3) On other occasions I have been able to switch to a virtual terminal
where no image/text is shown. Nevertheless I have been able to log
in blindly as root and request a reboot.

4) A couple of times the same stuff has happened at wakeup. Interestingly,
after closing the lid, waiting a short while so that it goes to sleep again, and
opening the lid, the computer made a normal wakeup!

5) Further, the problem of non-existant screen output on virtual consoles
have occured at several other times. Apparently, the VTs do in fact
function but it without text it is difficult to use them.

6) The problems occur on my Dell M2400 laptop on which I run Debian
for amd64. I started out with lenny but several weeks ago I upgraded to
squeeze in order to get later versions of some packages.
I run nvidia stuff from sid. The problems were present both with nvidia
version 185.18.36-2. and the current 194.42-3. I am using kde and the
2.6.31 kernel
from sid from which uname -a reports:

Linux laptop 2.6.31-1-amd64 #1 SMP Sat Oct 24 17:50:31 UTC 2009 x86_64 GNU/Linux

but I have seen the problem with the squeeze kernel 2.6.30 as well.

The M2400 has a nvidia graphics card of type  FX370M card for which
lspci reports:

01:00.0 VGA compatible controller: nVidia Corporation Device 06fb (rev a1)

The nvidia packages installed are:
i   nvidia-glx                                       - NVIDIA binary Xorg driver
i   nvidia-glx-ia32                               - NVIDIA binary
driver 32bit libs
i   nvidia-kernel-2.6.30-2-amd64       - NVIDIA binary kernel module
for Linux 2.6.30-2-amd64
i   nvidia-kernel-2.6.31-1-amd64       - NVIDIA binary kernel module
for Linux 2.6.31-1-amd64
i A nvidia-kernel-common                 - NVIDIA binary kernel module
common files
i   nvidia-kernel-source                     - NVIDIA binary kernel
module source
i   nvidia-settings                              - Tool for
configuring the NVIDIA graphics driver
i   nvidia-xconfig                              - The NVIDIA X
Configuration Tool


7) With lenny there were not any of these problems. In order to get
X working and sleep/hibernate I had to use a backported 2.6.30 or 31
kernel from backports, and the nvidia drivers from sid. This suggests
that the problems I'm experiencing now are are related to the squeeze
configuration.

Anders


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: X problems

2007-06-22 Thread Jose Rodriguez
On Fri, 22 Jun 2007 05:30:11 +0200
Zach [EMAIL PROTECTED] wrote:

 On 6/21/07, Kamaraju S Kusumanchi [EMAIL PROTECTED]
 wrote:
 
  To enable hardware acceleration, In the Module section of
  xorg.conf you should load dri. So the corresponding stanza
  in /etc/X11/xorg.conf will look like
 
  Section Module
# bunch of load statements here
Load dri
# bunch of load statements here
  EndSection
 
So, does /var/log/Xorg.0.log tell you anything about DRI being
enabled or not? If not, you may want to try to use 16 bits depth,
I read somewhere it was needed to get the acceleration to work
with that card. Also, I believe too that the best way to proceed
is to take a careful look at the xorg.conf file from the Ubuntu
CD, I dont't think there's anything fundamentally different, must
be some settings here and there.


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



X problems

2007-06-21 Thread Zach

Greetings,

I recently tried out a fairly recent Ubuntu boot CD (just to test it -
no plans on switching from Debian which I love) and was surprised to
see that my X desktop looked so much better: it was brighter and even
in the gnome-term and xterm I tried the fonts seemed better contrast,
more crisp! I wonder what Ubuntu is doing that my  X.org didn't do? I
was running XFree86 before and also had same issues: my display was
noticeably less bright and same issue with fonts, X.org package did
automagically setup my /etc/X11/xorg.conf and everything seems to work
fine except these 2 issues could obviously be better. So my question
is HOW can I make my Debian X desktop look as nice as the one from the
Ubuntu CD? How do you adjust the brightness in X, is there some app to
do it? Or way to set it at X server level so it's always like that?
And what about the fonts? I am running Debian testing with 2.6.18
kernel on Dell Latitude C600 laptop. Also does anyone know how to
enable hardware acceleration for an ATI Rage Mobility M3 AGP 2x gfx
card? I tried playing an OpenGL game and it told me hardware accel.
was disabled.

Below is my /etc/X11/xorg.conf and info on my gfx card:

# /etc/X11/xorg.conf (xorg 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 /etc/X11/xorg.conf manual page.
# (Type man /etc/X11/xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section Files
FontPath/usr/share/fonts/X11/misc
FontPath/usr/X11R6/lib/X11/fonts/misc
FontPath/usr/share/fonts/X11/cyrillic
FontPath/usr/X11R6/lib/X11/fonts/cyrillic
FontPath/usr/share/fonts/X11/100dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/share/fonts/X11/75dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/share/fonts/X11/Type1
FontPath/usr/X11R6/lib/X11/fonts/Type1
FontPath/usr/share/fonts/X11/100dpi
FontPath/usr/X11R6/lib/X11/fonts/100dpi
FontPath/usr/share/fonts/X11/75dpi
FontPath/usr/X11R6/lib/X11/fonts/75dpi
# path to defoma fonts
FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
EndSection

Section Module
Loadbitmap
Loaddbe
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Loadint10
Loadrecord
Loadvbe
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  CoreKeyboard
Option  XkbRulesxorg
Option  XkbModelpc104
Option  XkbLayout   us
Option  XkbOptions  altwin:meta_win
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device  /dev/psaux
Option  ProtocolPS/2
Option  Emulate3Buttons true
EndSection

Section InputDevice
Identifier  Synaptics Touchpad
Driver  synaptics
Option  SendCoreEvents  true
Option  Device  /dev/psaux
Option  Protocolauto-dev
Option  HorizScrollDelta0
EndSection

Section Device
Identifier  ATI Technologies Inc Rage Mobility M3 AGP 2x
Driver  ati
BusID   PCI:1:0:0
EndSection

Section Monitor
Identifier  Dell Latitude C600 LCD
Option  DPMS
HorizSync   28-51
VertRefresh 43-60
EndSection

Section Screen
Identifier  Default Screen
Device  ATI Technologies Inc Rage Mobility M3 AGP 2x
Monitor Dell Latitude C600 LCD
DefaultDepth24
SubSection Display
Depth   1
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   4
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   8
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   15
Modes   1024x768 800x600 640x480
EndSubSection

Re: X problems

2007-06-21 Thread Andrew Sackville-West
On Thu, Jun 21, 2007 at 04:43:06PM -0400, Zach wrote:
 Greetings,
 
 I recently tried out a fairly recent Ubuntu boot CD (just to test it -
 no plans on switching from Debian which I love) and was surprised to
 see that my X desktop looked so much better: it was brighter and even
 in the gnome-term and xterm I tried the fonts seemed better contrast,
 more crisp! I wonder what Ubuntu is doing that my  X.org didn't do?

first thing I'd do is very closely read the xorg.conf and
/var/log/Xorg.0.log generated by *each* system and look for critical
differences. 

It could be something as simple as the dpi setting, for example. It
could also be a theme thing. THe default fonts, colors, etc could just
be a better setup for you. 

.02

A


signature.asc
Description: Digital signature


Re: X problems

2007-06-21 Thread Zach

On 6/21/07, Andrew Sackville-West [EMAIL PROTECTED] wrote:


first thing I'd do is very closely read the xorg.conf and
/var/log/Xorg.0.log generated by *each* system and look for critical
differences.

It could be something as simple as the dpi setting, for example. It
could also be a theme thing. THe default fonts, colors, etc could just
be a better setup for you.


Ok, do you know a general way to increase the screen brightness in X?
Most gfx drivers in Windows come with a way to change the brightness
but I have no driver for this so I guess X.org just picked something
generic. I remember when I had my old Nvidia card I could use 'nv' or
'nvidia' driver to get hardware acceleration working. Any idea how to
do so for my ATI card?

Zach


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




Re: X problems

2007-06-21 Thread Andrew Sackville-West
On Thu, Jun 21, 2007 at 04:58:06PM -0400, Zach wrote:
 On 6/21/07, Andrew Sackville-West [EMAIL PROTECTED] wrote:
 
 first thing I'd do is very closely read the xorg.conf and
 /var/log/Xorg.0.log generated by *each* system and look for critical
 differences.
 
 It could be something as simple as the dpi setting, for example. It
 could also be a theme thing. THe default fonts, colors, etc could just
 be a better setup for you.
 
 Ok, do you know a general way to increase the screen brightness in X?

[...]

I don't think so, unless the driver has it. man ati. also, maybe
ddccontrol would be useful

A


signature.asc
Description: Digital signature


Re: X problems

2007-06-21 Thread Kamaraju S Kusumanchi
Zach wrote:

 I remember when I had my old Nvidia card I could use 'nv' or
 'nvidia' driver to get hardware acceleration working. Any idea how to
 do so for my ATI card?
 

To enable hardware acceleration, In the Module section of xorg.conf you
should load dri. So the corresponding stanza in /etc/X11/xorg.conf will
look like

Section Module
  # bunch of load statements here
  Load dri
  # bunch of load statements here
EndSection

hth
raju

-- 
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/


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



Re: X problems

2007-06-21 Thread Zach

On 6/21/07, Kamaraju S Kusumanchi [EMAIL PROTECTED] wrote:


To enable hardware acceleration, In the Module section of xorg.conf you
should load dri. So the corresponding stanza in /etc/X11/xorg.conf will
look like

Section Module
  # bunch of load statements here
  Load dri
  # bunch of load statements here
EndSection


Hi Raju,

My /etc/X11/xorg.conf currently has:


Section Module
  
  Loaddri
  

Section DRI
  Mode0666
EndSection

What does the mode indicate? Could that be the problem? Maybe the game
I played was misdetecting, is there a quick way to verify that
hardware acceleration is working?

Zach


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




Re: X problems

2007-06-21 Thread Andrew Sackville-West
On Thu, Jun 21, 2007 at 11:20:20PM -0400, Zach wrote:
 
 What does the mode indicate? Could that be the problem? Maybe the game
 I played was misdetecting, is there a quick way to verify that
 hardware acceleration is working?

on my rig:

[EMAIL PROTECTED]:~$ grep -i dri /var/log/Xorg.0.log | grep /
-vi driver
(II) LoadModule: dri
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor=X.Org Foundation
(II) Loading extension XFree86-DRI
(EE) VIA(0): [dri] DRIScreenInit failed.  Disabling DRI.
(EE) MGA(1): Static buffer allocation failed, not initializing the DRI
(EE) AIGLX: Screen 0 is not DRI capable
(EE) AIGLX: Screen 1 is not DRI capable

pretty much says it all. Not sure what it looks like when it works.

A


signature.asc
Description: Digital signature


Re: More X Problems Today

2006-05-05 Thread Mark Crean
On Friday 05 May 2006 00:37, Bill Thompson wrote:
 On Thu, 4 May 2006 15:37:58 +0100

[snip]
 It has been said many times; If you can not afford to deal with problem
 like this DO NOT use unstable. From the comments above I can only
 assume that you do not understand the Debian release method of stable,
 testing, and unstable. Please review http://www.debian.org/releases/.


I understand the system perfectly well. That does not mean I agree to put duct 
tape over my mouth. 

:)

Fish


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



More X Problems Today

2006-05-04 Thread Rick Friedman
I'm running Debian Sid. This morning, I saw that quite a few X/Xorg packages 
were available to be upgraded. So, I went ahead and did the upgrades.

I use kdm as my login display manager. After the upgrade, X started fine. 
However, when any user would try to login, the screen would go black 
momentarily and then return to the kdm login screen. No user could login.

After checking the .xsession-errors file for each user, the following error 
was seen in all:

/etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or directory

I checked the /etc/X11 directory and corrected the problem by creating a 
symbolic link as follows:

ln -s Xsession.xfree86 Xsession

After this, users were able to logon as usual. 

Anyone else experiencing this??

Rick
-- 
Rick's Law: What cannot be imagined will be accomplished by a fool.


pgpT7fsZstax4.pgp
Description: PGP signature


Re: More X Problems Today

2006-05-04 Thread Florian Kulzer
On Thu, May 04, 2006 at 08:52:55 -0400, Rick Friedman wrote:
 I'm running Debian Sid. This morning, I saw that quite a few X/Xorg packages 
 were available to be upgraded. So, I went ahead and did the upgrades.
 
 I use kdm as my login display manager. After the upgrade, X started fine. 
 However, when any user would try to login, the screen would go black 
 momentarily and then return to the kdm login screen. No user could login.
 
 After checking the .xsession-errors file for each user, the following error 
 was seen in all:
 
 /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or directory
 
 I checked the /etc/X11 directory and corrected the problem by creating a 
 symbolic link as follows:
 
 ln -s Xsession.xfree86 Xsession
 
 After this, users were able to logon as usual. 
 
 Anyone else experiencing this??

I had the same problem this morning. I could not spend too much time on
investigating it, but it seems to me that there is some sort of
dependency loop which screws up the installation of the new version of
x11-common. I extracted /etc/X11/Xsession manually from the x11-common
.deb file and that fixed the kdm log-in. To be on the safe side I
aptitude-reinstalled x11-common, then all the other xorg packages which
had been upgraded today, and then x11-common once more. This worked
without errors and everything seems OK now. 

Maybe the problem is simply due to some new xorg packages which are
still missing to make the whole thing internally consistent again.

-- 
Regards,
  Florian


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



Re: More X Problems Today

2006-05-04 Thread Mark Crean
On Thursday 04 May 2006 13:52, Rick Friedman wrote:
 I'm running Debian Sid. This morning, I saw that quite a few X/Xorg
 packages were available to be upgraded. So, I went ahead and did the
 upgrades.

 I use kdm as my login display manager. After the upgrade, X started fine.
 However, when any user would try to login, the screen would go black
 momentarily and then return to the kdm login screen. No user could login.

 After checking the .xsession-errors file for each user, the following error
 was seen in all:

 /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or
 directory

 I checked the /etc/X11 directory and corrected the problem by creating a
 symbolic link as follows:

 ln -s Xsession.xfree86 Xsession

 After this, users were able to logon as usual.

[snip]

Same problem here and thanks a million for the fix which I didn't suss out. 
losing several hours of faffling around instead.

Just my 2 cents but I am getting a little desperate at the number of bog ups 
in Unstable at the moment. I don't want to leave the platform but if things 
continue like this I will have to. Like many folks perhaps, I am completely 
baffled by Debian's reluctance to get together a desktop iternation that is 
more up to date than Stable. It doesn't have to be rock solid, but there must 
be a better way than this.

:)


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



Re: More X Problems Today

2006-05-04 Thread Clive Menzies
On (04/05/06 15:37), Mark Crean wrote:
 On Thursday 04 May 2006 13:52, Rick Friedman wrote:
  I'm running Debian Sid. This morning, I saw that quite a few X/Xorg
  packages were available to be upgraded. So, I went ahead and did the
  upgrades.
 
  I use kdm as my login display manager. After the upgrade, X started fine.
  However, when any user would try to login, the screen would go black
  momentarily and then return to the kdm login screen. No user could login.
 
  After checking the .xsession-errors file for each user, the following error
  was seen in all:
 
  /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or
  directory
 
  I checked the /etc/X11 directory and corrected the problem by creating a
  symbolic link as follows:
 
  ln -s Xsession.xfree86 Xsession
 
  After this, users were able to logon as usual.
 
 [snip]
 
 Same problem here and thanks a million for the fix which I didn't suss out. 
 losing several hours of faffling around instead.
 
 Just my 2 cents but I am getting a little desperate at the number of bog ups 
 in Unstable at the moment. I don't want to leave the platform but if things 
 continue like this I will have to. Like many folks perhaps, I am completely 
 baffled by Debian's reluctance to get together a desktop iternation that is 
 more up to date than Stable. It doesn't have to be rock solid, but there must 
 be a better way than this.

If you install apt-listbugs and use aptitude to update your system, you
should avoid installing packages or dependencies which are broken.

FWIW the xorg upgrade is 'held' here without any intervention from me.

Regards

Clive

-- 
www.clivemenzies.co.uk ...
...strategies for business



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



Re: More X Problems Today

2006-05-04 Thread Rick Friedman
On Thu May 4 2006 10:01, Florian Kulzer wrote:
 I had the same problem this morning. I could not spend too much time on
 investigating it, but it seems to me that there is some sort of
 dependency loop which screws up the installation of the new version of
 x11-common. I extracted /etc/X11/Xsession manually from the x11-common
 .deb file and that fixed the kdm log-in. To be on the safe side I
 aptitude-reinstalled x11-common, then all the other xorg packages which
 had been upgraded today, and then x11-common once more. This worked
 without errors and everything seems OK now.

 Maybe the problem is simply due to some new xorg packages which are
 still missing to make the whole thing internally consistent again.

I followed your method of reparing the problem. First, I removed the symbolic 
link I had created and then did exactly what you described above. It worked 
like a charm. 

Rick
-- 
Rick's Law: What cannot be imagined will be accomplished by a fool.


pgptED7Dc6Kot.pgp
Description: PGP signature


Re: More X Problems Today

2006-05-04 Thread Florian Kulzer
On Thu, May 04, 2006 at 11:01:14 -0400, Rick Friedman wrote:
 On Thu May 4 2006 10:01, Florian Kulzer wrote:
  I had the same problem this morning. I could not spend too much time on
  investigating it, but it seems to me that there is some sort of
  dependency loop which screws up the installation of the new version of
  x11-common. I extracted /etc/X11/Xsession manually from the x11-common
  .deb file and that fixed the kdm log-in. To be on the safe side I
  aptitude-reinstalled x11-common, then all the other xorg packages which
  had been upgraded today, and then x11-common once more. This worked
  without errors and everything seems OK now.
 
  Maybe the problem is simply due to some new xorg packages which are
  still missing to make the whole thing internally consistent again.
 
 I followed your method of reparing the problem. First, I removed the symbolic 
 link I had created and then did exactly what you described above. It worked 
 like a charm. 

Good to know. It seems that we really picked exactly the wrong moment to
do the upgrade. A little later and apt-listbugs would have warned me
about the grave functionality bugs which have meanwhile been filed.
(#365948, #365967, #365988, #366007) An upload is already pending for
the fix.

-- 
Regards,
  Florian


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



Re: More X Problems Today

2006-05-04 Thread hendrik
On Thu, May 04, 2006 at 03:37:58PM +0100, Mark Crean wrote:
 On Thursday 04 May 2006 13:52, Rick Friedman wrote:
  I'm running Debian Sid. This morning, I saw that quite a few X/Xorg
  packages were available to be upgraded. So, I went ahead and did the
  upgrades.
 
  I use kdm as my login display manager. After the upgrade, X started fine.
  However, when any user would try to login, the screen would go black
  momentarily and then return to the kdm login screen. No user could login.
 
  After checking the .xsession-errors file for each user, the following error
  was seen in all:
 
  /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or
  directory
 
  I checked the /etc/X11 directory and corrected the problem by creating a
  symbolic link as follows:
 
  ln -s Xsession.xfree86 Xsession
 
  After this, users were able to logon as usual.
 
 [snip]
 
 Same problem here and thanks a million for the fix which I didn't suss out. 
 losing several hours of faffling around instead.
 
 Just my 2 cents but I am getting a little desperate at the number of bog ups 
 in Unstable at the moment. I don't want to leave the platform but if things 
 continue like this I will have to. Like many folks perhaps, I am completely 
 baffled by Debian's reluctance to get together a desktop iternation that is 
 more up to date than Stable. It doesn't have to be rock solid, but there must 
 be a better way than this.

I'm using testing/etch, which is more up-to-date than stable and doesn't 
seem to have many bog-ups.  Thanks to you brave souls that find the 
bog-ups on sid, of course.

-- hendrik


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



Re: More X Problems Today

2006-05-04 Thread toshiro

 I'm running Debian Sid. This morning, I saw that quite a few X/Xorg
 packages were available to be upgraded. So, I went ahead and did the
 upgrades.

 I use kdm as my login display manager. After the upgrade, X started fine.
 However, when any user would try to login, the screen would go black
 momentarily and then return to the kdm login screen. No user could login.

 After checking the .xsession-errors file for each user, the   
following error

 was seen in all:

 /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or
 directory

 I checked the /etc/X11 directory and corrected the problem by creating a
 symbolic link as follows:

 ln -s Xsession.xfree86 Xsession

 After this, users were able to logon as usual.

[snip]

Same problem here and thanks a million for the fix which I didn't suss out.
losing several hours of faffling around instead.

Just my 2 cents but I am getting a little desperate at the number of bog ups
in Unstable at the moment. I don't want to leave the platform but if things
continue like this I will have to. Like many folks perhaps, I am completely
baffled by Debian's reluctance to get together a desktop iternation that is
more up to date than Stable. It doesn't have to be rock solid, but   
there must

be a better way than this.


I don't think we should blame all Debian developers. The only real  
problems I've had with sid were related to x-server; all other parts  
of Debian are rock solid. Maybe the x-server Debian maintainers are  
new/unexperienced in that task?





Re: More X Problems Today

2006-05-04 Thread Joris Huizer

[EMAIL PROTECTED] wrote:




I don't think we should blame all Debian developers. The only real  
problems I've had with sid were related to x-server; all other parts  of 
Debian are rock solid. Maybe the x-server Debian maintainers are  
new/unexperienced in that task?





Managing something as big as X and providing packages (including the way 
X tools are split up in several package) doesn't sound like a trivial 
task to me



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




Re: More X Problems Today

2006-05-04 Thread L . V . Gandhi

On 5/4/06, Florian Kulzer [EMAIL PROTECTED] wrote:

On Thu, May 04, 2006 at 08:52:55 -0400, Rick Friedman wrote:
 I'm running Debian Sid. This morning, I saw that quite a few X/Xorg packages
 were available to be upgraded. So, I went ahead and did the upgrades.

 I use kdm as my login display manager. After the upgrade, X started fine.
 However, when any user would try to login, the screen would go black
 momentarily and then return to the kdm login screen. No user could login.

 After checking the .xsession-errors file for each user, the following error
 was seen in all:

 /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or directory

 I checked the /etc/X11 directory and corrected the problem by creating a
 symbolic link as follows:

 ln -s Xsession.xfree86 Xsession

 After this, users were able to logon as usual.

 Anyone else experiencing this??

I had the same problem this morning. I could not spend too much time on
investigating it, but it seems to me that there is some sort of
dependency loop which screws up the installation of the new version of
x11-common. I extracted /etc/X11/Xsession manually from the x11-common
.deb file and that fixed the kdm log-in. To be on the safe side I
aptitude-reinstalled x11-common, then all the other xorg packages which
had been upgraded today, and then x11-common once more. This worked
without errors and everything seems OK now.

Maybe the problem is simply due to some new xorg packages which are
still missing to make the whole thing internally consistent again.

I also faced the same problem. With Ricks soln, I could login.
However reinstalling only x11-common didn't help. I then reinstalled
kdm also. That also didn't help. I reverted back to Ricks soln.
However I would like to know the following so that I can follow your method.
1)how to extract /etc/X11/Xsession manually from the x11-common
2)How to identify the other xorg packages which had been upgraded today
TIA

--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042


Re: More X Problems Today

2006-05-04 Thread Florian Kulzer
On Thu, May 04, 2006 at 11:39:29 -0700, L.V.Gandhi wrote:
 On 5/4/06, Florian Kulzer [EMAIL PROTECTED] wrote:
 On Thu, May 04, 2006 at 08:52:55 -0400, Rick Friedman wrote:
  I'm running Debian Sid. This morning, I saw that quite a few X/Xorg 
 packages
  were available to be upgraded. So, I went ahead and did the upgrades.
 
  I use kdm as my login display manager. After the upgrade, X started fine.
  However, when any user would try to login, the screen would go black
  momentarily and then return to the kdm login screen. No user could login.
 
  After checking the .xsession-errors file for each user, the following 
 error
  was seen in all:
 
  /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or 
 directory
 
  I checked the /etc/X11 directory and corrected the problem by creating a
  symbolic link as follows:
 
  ln -s Xsession.xfree86 Xsession
 
  After this, users were able to logon as usual.
 
  Anyone else experiencing this??

[...]

 I also faced the same problem. With Ricks soln, I could login.
 However reinstalling only x11-common didn't help. I then reinstalled
 kdm also. That also didn't help. I reverted back to Ricks soln.
 However I would like to know the following so that I can follow your method.
 1)how to extract /etc/X11/Xsession manually from the x11-common
 2)How to identify the other xorg packages which had been upgraded today

First of all, I have now looked into this a bit more; I also read the
bug reports which I mentioned in my earlier post in more detail. There
are two nicer ways to fix this problem:

a) /etc/X11/Xsession.xfree86 is in fact /etc/X11/Xsession from
   x11-common, it just gets renamed by mistake. Therefore you can just
   rename it again and the problem should be solved.

b) Another possibility is to install x11-common with dpkg:

   dpkg --force-confmiss -i 
/var/cache/apt/archives/x11-common_1%3a7.0.16_i386.deb

   The force-confmiss option will make sure that the missing file is
   restored.

I hope you will now not need this anymore, but the information might be handy
for another time:

1) The command is dpkg-deb. In our case it would be something like

   dpkg-deb -X /var/cache/apt/archives/x11-common_1%3a7.0.16_i386.deb tempdir

   This will extract all files from the package to tempdir. The directory
   hierarchy is preserved, therefore you would find the missing file at
   tempdir/etc/X11/Xsession.

2) Aptitude keeps a log of all its (intended) operations. If you don't
   use aptitude you can check for new files in the package cache:

   find /var/cache/apt/archives/ -type f -mtime -2 | sed 's/.*\///;s/_.*$//'

   (-mtime -2 finds files which were modified less than 2 days ago.)

-- 
Regards,
  Florian


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



Re: More X Problems Today

2006-05-04 Thread David Baron
On Thursday 04 May 2006 22:25, Florian Kulzer wrote:
 On Thu, May 04, 2006 at 11:39:29 -0700, L.V.Gandhi wrote:
  On 5/4/06, Florian Kulzer [EMAIL PROTECTED] wrote:
  On Thu, May 04, 2006 at 08:52:55 -0400, Rick Friedman wrote:
   I'm running Debian Sid. This morning, I saw that quite a few X/Xorg
  
  packages
  
   were available to be upgraded. So, I went ahead and did the upgrades.
  
   I use kdm as my login display manager. After the upgrade, X started
   fine. However, when any user would try to login, the screen would go
   black momentarily and then return to the kdm login screen. No user
   could login.
  
   After checking the .xsession-errors file for each user, the following
  
  error
  
   was seen in all:
  
   /etc/kde3/kdm/Xsession: line46: /etc/X11/Xsession: No such file or
  
  directory
  
   I checked the /etc/X11 directory and corrected the problem by creating
   a symbolic link as follows:
  
   ln -s Xsession.xfree86 Xsession
  
   After this, users were able to logon as usual.
  
   Anyone else experiencing this??

 [...]

  I also faced the same problem. With Ricks soln, I could login.
  However reinstalling only x11-common didn't help. I then reinstalled
  kdm also. That also didn't help. I reverted back to Ricks soln.
  However I would like to know the following so that I can follow your
  method. 1)how to extract /etc/X11/Xsession manually from the x11-common
  2)How to identify the other xorg packages which had been upgraded today

 First of all, I have now looked into this a bit more; I also read the
 bug reports which I mentioned in my earlier post in more detail. There
 are two nicer ways to fix this problem:

 a) /etc/X11/Xsession.xfree86 is in fact /etc/X11/Xsession from
x11-common, it just gets renamed by mistake. Therefore you can just
rename it again and the problem should be solved.

My /etc/X11/Xsession.xfree86 is dated October 21, 2001! Locate, updated before 
upgrading, finds an Xsession file there so it was renamed. I doubt it is in 
use and I have not had the above described login problems. Easy enough to 
rename or simply make a copy under the other name. $KDEDIR/share/config/kdm 
has its own Xsession as does xdm.

My X problems have been the repeated customizing of xorg.conf. At least the 
thing backs up the existing one so I simply mv things around. The customized 
version has no ModulesPath's so will not work.

I had given up on Sid's KDE while everything was in flux with all those ...c2 
libraries and only a portion of the packages around. Maybe for KDE4, I will 
go back to Sid but now I compile my own KDE3.5.* from konstruct. A drawn 
out pain but usually easy and effective. There were a couple of missing icons 
at first which I found and copied from KDE3.4 before removing this.

I one time compiled my own Xorg. Never recovered from that experience. Went 
back to the saved /usr/X11R6. The compiled one did work but was not 
compatable with mach64 dri (this could have been fixed). FInally replaced the 
card instead of keeping no longer supported packages and xorg versions 
around.

Otherwize, Sid has been most solid. Occasionally--very occasionally--something 
stops working. Usually fixed quite quickly by the maintainers and oftimes can 
be done by myself as well beforehand. I use listbugs to avoid stuff with 
already flagged problems.

Another reason I may be 


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



Re: More X Problems Today

2006-05-04 Thread L . V . Gandhi

On 5/4/06, Florian Kulzer [EMAIL PROTECTED] wrote:


First of all, I have now looked into this a bit more; I also read the
bug reports which I mentioned in my earlier post in more detail. There
are two nicer ways to fix this problem:

a) /etc/X11/Xsession.xfree86 is in fact /etc/X11/Xsession from
   x11-common, it just gets renamed by mistake. Therefore you can just
   rename it again and the problem should be solved.

b) Another possibility is to install x11-common with dpkg:

   dpkg --force-confmiss -i 
/var/cache/apt/archives/x11-common_1%3a7.0.16_i386.deb

   The force-confmiss option will make sure that the missing file is
   restored.

I hope you will now not need this anymore, but the information might be handy
for another time:

1) The command is dpkg-deb. In our case it would be something like

   dpkg-deb -X /var/cache/apt/archives/x11-common_1%3a7.0.16_i386.deb tempdir

   This will extract all files from the package to tempdir. The directory
   hierarchy is preserved, therefore you would find the missing file at
   tempdir/etc/X11/Xsession.

2) Aptitude keeps a log of all its (intended) operations. If you don't
   use aptitude you can check for new files in the package cache:

   find /var/cache/apt/archives/ -type f -mtime -2 | sed 's/.*\///;s/_.*$//'

   (-mtime -2 finds files which were modified less than 2 days ago.)


Thanks for the explanation
--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042


Re: More X Problems Today

2006-05-04 Thread Michael M.

[EMAIL PROTECTED] wrote:


Just my 2 cents but I am getting a little desperate at the number of 
bog ups
in Unstable at the moment. I don't want to leave the platform but if 
things
continue like this I will have to. Like many folks perhaps, I am 
completely
baffled by Debian's reluctance to get together a desktop iternation 
that is
more up to date than Stable. It doesn't have to be rock solid, but  
there must

be a better way than this.


I don't think we should blame all Debian developers. The only real 
problems I've had with sid were related to x-server; all other parts 
of Debian are rock solid. Maybe the x-server Debian maintainers are 
new/unexperienced in that task?





I have yet to experience these problems with X that some people seem to 
be having.  Just lucky timing?  I've certainly done problem-free updates 
at the same time others have reported problems.  I don't know, but it 
does seem to me that most of the time it turns out that someone who has 
a problem has somewhere along the line done some customizing of the 
server set-up.  I tend to think it's not that the Debian maintainers are 
inexperienced, but that they can't account for every possible tweak any 
given user might have made to a complicated system like X when that 
system itself is going through a major reorganization and restructuring.


And I don't mean to imply that it's the user's fault.  Many people 
make little adjustments here and there to their set-ups -- that we can 
do that is one of the benefits of running a Linux OS in the first 
place.  Most of the time, this isn't a problem.  But when you're running 
a system that is fairly cutting-edge and apt to go through some major 
changes from time to time, it's worth remembering that the less 
standard your installation, the more likely it is you'll have problems 
when these changes hit.


At one extreme, you run Linux from Scratch and do all your own 
recompiling and dependency-satisfying and configure your heart out 
knowing that you have complete control over everything that happens on 
your computer; at the other, you stick only to official Debian apt 
sources, don't make any funny edits to configuration files, and use 
official tools that tell you exactly how your system wants to be set-up 
so that you can do a simple apt-get update  apt-get upgrade without 
worry.


Happiness lies somewhere in-between.  :-)

--
Michael M. ++ Portland, OR ++ USA
No live organism can continue for long to exist sanely under conditions of absolute 
reality; even larks and katydids are supposed, by some, to dream. --S. Jackson


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




Re: More X Problems Today

2006-05-04 Thread Bill Thompson
On Thu, 4 May 2006 15:37:58 +0100
Mark Crean [EMAIL PROTECTED] wrote:

 Just my 2 cents but I am getting a little desperate at the number of
 bog ups in Unstable at the moment. I don't want to leave the platform
 but if things continue like this I will have to. Like many folks
 perhaps, I am completely baffled by Debian's reluctance to get
 together a desktop iternation that is more up to date than Stable. It
 doesn't have to be rock solid, but there must be a better way than
 this.

It has been said many times; If you can not afford to deal with problem
like this DO NOT use unstable. From the comments above I can only
assume that you do not understand the Debian release method of stable,
testing, and unstable. Please review http://www.debian.org/releases/.

-- 
Bill Thompson
[EMAIL PROTECTED]


signature.asc
Description: PGP signature


Re: More X Problems Today

2006-05-04 Thread Bill Thompson
On Thu, 04 May 2006 12:41:11 -0300
[EMAIL PROTECTED] wrote:

 I don't think we should blame all Debian developers. The only real  
 problems I've had with sid were related to x-server; all other parts  
 of Debian are rock solid. Maybe the x-server Debian maintainers are  
 new/unexperienced in that task?

The Debian X Strike Force are much older, crustier, and vastly more
experienced than you or I. Please understand that the UNSTABLE release
is meant to have issues like this and should not be used for production
systems.

I for one think that there has been much to much complaining about the
recent x-org bugs, including insulting bug reports posted to the
tracking system, than the X team deserves. Unstable is where new and
untested packages enter the Debian release system. Occasionally an
unstable bug is going to occur that will bring down a system. I think
the X team has done a fine job of correcting the bugs and getting work
around information to the Unstable users.

-- 
Bill Thompson
[EMAIL PROTECTED]


signature.asc
Description: PGP signature


Re: More X Problems Today

2006-05-04 Thread Toshiro
  I don't think we should blame all Debian developers. The only real
  problems I've had with sid were related to x-server; all other parts
  of Debian are rock solid. Maybe the x-server Debian maintainers are
  new/unexperienced in that task?

 The Debian X Strike Force are much older, crustier, and vastly more
 experienced than you or I. 

Well, that's what you say, but the fact is that all the major problems I've 
ever experienced with sid were always related to x-server; their performance 
looks very poor to me.

 I for one think that there has been much to much complaining about the
 recent x-org bugs, including insulting bug reports posted to the
 tracking system, than the X team deserves. Unstable is where new and
 untested packages enter the Debian release system. 

If that's true, can you tell me the purpose of the experimental branch? 


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



Re: More X Problems Today

2006-05-04 Thread hendrik
On Thu, May 04, 2006 at 09:15:09PM -0300, Toshiro wrote:
   I don't think we should blame all Debian developers. The only real
   problems I've had with sid were related to x-server; all other parts
   of Debian are rock solid. Maybe the x-server Debian maintainers are
   new/unexperienced in that task?
 
  The Debian X Strike Force are much older, crustier, and vastly more
  experienced than you or I. 
 
 Well, that's what you say, but the fact is that all the major problems I've 
 ever experienced with sid were always related to x-server; their performance 
 looks very poor to me.
 
  I for one think that there has been much to much complaining about the
  recent x-org bugs, including insulting bug reports posted to the
  tracking system, than the X team deserves. Unstable is where new and
  untested packages enter the Debian release system. 
 
 If that's true, can you tell me the purpose of the experimental branch? 

I presume that's where the packages are constructed, where they are 
pretty well *guaranteed* to be broken.

-- hendrik


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



Re: More X Problems Today

2006-05-04 Thread Andrew Sackville-West
On Thu, May 04, 2006 at 04:50:10PM -0700, Bill Thompson wrote:
 On Thu, 04 May 2006 12:41:11 -0300
 [EMAIL PROTECTED] wrote:
 
  I don't think we should blame all Debian developers. The only real  
  problems I've had with sid were related to x-server; all other parts  
  of Debian are rock solid. Maybe the x-server Debian maintainers are  
  new/unexperienced in that task?
 
 The Debian X Strike Force are much older, crustier, and vastly more
 experienced than you or I. Please understand that the UNSTABLE release
 is meant to have issues like this and should not be used for production
 systems.
 
 I for one think that there has been much to much complaining about the
 recent x-org bugs, including insulting bug reports posted to the
 tracking system, than the X team deserves. Unstable is where new and
 untested packages enter the Debian release system. Occasionally an
 unstable bug is going to occur that will bring down a system. I think
 the X team has done a fine job of correcting the bugs and getting work
 around information to the Unstable users.

and given the size and complexity of the X system, their efforts are
laudable. Frankly, I'm amazed that it works at all, and am grateful
for the learning opportunity when it doesn't. Thanks for speaking up
on this Bill.

A


signature.asc
Description: Digital signature


Re: More X Problems Today

2006-05-04 Thread Joey Hess
Toshiro wrote:
 Well, that's what you say, but the fact is that all the major problems I've 
 ever experienced with sid were always related to x-server; their performance 
 looks very poor to me.

This just indicates that you haven't used sid long enough. After you've
used it ten years, you will probably be familiar with:

 - a ld-linux.so bug that makes it impossible to run any dynamically
   linked program
 - a buggy script that runs rm -rf $VAR/ , with $VAR not set..
 - a kernel upgrade that doesn't boot
 - a kernel upgrade that doesn't see your hard drive anymore

After that, minor issues with X are hardly noticeable.

If you can't handle each of those type of major, system crippling
problems at least once per ten years, then please consider running stable
or testing.

-- 
see shy jo


signature.asc
Description: Digital signature


X problems after dist-upgrade

2005-10-03 Thread Fred J.
Hello

I have bee struggling with this problem for a while
not, I would appreciate some help in fix it. I am not
able to boot into wdm or X.

I just did an #apt-get dist-upgrade from woody to the
testing tree. Also I upgrade to kernel 2.6.12-1-686
My system was working good but now I have a problem
with the wdm (window manager) and X. Which is what I
need fixed.
the system boots fine but does not show the wdm it
used to show before.

Thanks 


 # cat /etc/debian_version 
testing/unstable
#uname -a
Linux debian 2.6.12-1-686 #1 Tue Sep 27 12:52:50 JST
2005 i686 GNU/Linux
# cat /var/log/Xorg.0.log | grep '(EE)'
 (WW) warning, (EE) error, (NI) not implemented,
(??) unknown.
# startx

X Window System Version 6.8.2 (Debian 6.8.2.dfsg.1-7
20050908031534 David Nusinow [EMAIL PROTECTED])
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.12-1-686 i686 [ELF] 
Current Operating System: Linux debian 2.6.12-1-686 #1
Tue Sep 27 12:52:50 JST 2005 i686
Build Date: 08 September 2005
 Before reporting problems, check
http://wiki.X.Org
 to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.12-1-686
([EMAIL PROTECTED]) (gcc version 4.0.2
20050917 (prerelease) (Debian 4.0.1-8)) #1 Tue Sep 27
12:52:50 JST 2005 
Markers: (--) probed, (**) from config file, (==)
default setting,
 (++) from command line, (!!) notice, (II)
informational,
 (WW) warning, (EE) error, (NI) not implemented,
(??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Mon Oct  3
17:50:13 2005
(==) Using config file: /etc/X11/xorg.conf

Skipping
/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_clip.o:
 No symbols found
Skipping
/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_norm.o:
 No symbols found
Skipping
/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_xform.o:
 No symbols found
Skipping /usr/X11R6/lib/modules/libfb.a:fbmmx.o:  No
symbols found
Warning: font renderer for .pcf already registered
at priority 0
Warning: font renderer for .pcf.Z already registered
at priority 0
Warning: font renderer for .pcf.gz already
registered at priority 0
Warning: font renderer for .snf already registered
at priority 0
Warning: font renderer for .snf.Z already registered
at priority 0
Warning: font renderer for .snf.gz already
registered at priority 0
Warning: font renderer for .bdf already registered
at priority 0
Warning: font renderer for .bdf.Z already registered
at priority 0
Warning: font renderer for .bdf.gz already
registered at priority 0
Warning: font renderer for .pmf already registered
at priority 0
 waiting for X server to shut down 




__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com


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



Re: X problems after dist-upgrade

2005-10-03 Thread Kent West
Fred J. wrote:

Hello

I have bee struggling with this problem for a while
not, I would appreciate some help in fix it. I am not
able to boot into wdm or X.

I just did an #apt-get dist-upgrade from woody to the
testing tree. Also I upgrade to kernel 2.6.12-1-686
My system was working good but now I have a problem
with the wdm (window manager) and X. Which is what I
need fixed.
the system boots fine but does not show the wdm it
used to show before.

Do you mean display manager (GUI login screen) or window
manager/environment (wmaker vs KDE vs Icewm vs Gnome, etc)?

I'm assuming you mean display manager, since you specifically mention
wdm. You don't indicate if another display manager is starting or not.

I suggest you try:

dpkg-reconfigure wdm

or
dpkg-reconfigure xdm

or

dpkg-reconfigure gdm

Depending on what you have installed, one of these will probably let you
reset wdm as your display manager. If it's not available as a choice,
try reinstalling wdm:

apt-get install wdm

-- 
Kent West
Technology Support
/A/bilene /C/hristian /U/niversity


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



Re: No X - Problems with loading Nvidia module

2005-07-12 Thread David Roguin
I had the some problem last night.
I fixed it this morning, some how it broke when i upgrade somehting,
but i dont know.

That's the recipe:
note: i'm not sure if all the steps are necesary, that's because it
worked for me this way.

1. rmmod nvidia
2. apt-get remove --purge nvidia-kernel*
3. cd /usr/src
if you have any nvidia*deb in there remove it.
If you have modules/nvidia-kernel, remove the directory too.

Ok, so far, we clean up (i believe something needed to refresh, but i
don't know other way ;) )

5. module-assistant update
6. module-assistant auto-install nvidia
7. apt-get install nvidia-glx
8. modprobe nvidia
9. restart X.

Enjoy nvidia.

Regards

On 7/11/05, KS [EMAIL PROTECTED] wrote:
 Hi,
 
 I thought of restarting my machine after the browser was getting stuck
 at some websites since last night. On restarting, X couldn't start.  The
 error log indicated that the Nvidia module couldnot be loaded. Below are
 the last few lines from the XFree86 log:
 
 (II) Setting vga for screen 0.
 (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
 (==) NVIDIA(0): RGB weight 888
 (==) NVIDIA(0): Default visual is TrueColor
 (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
 (--) NVIDIA(0): Linear framebuffer at 0xE000
 (--) NVIDIA(0): MMIO registers at 0xFD00
 (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
 (EE) NVIDIA(0):  *** Aborting ***
 (II) UnloadModule: nvidia
 (EE) Screen(s) found, but none have a usable configuration.
 
 Fatal server error:
 no screens found
 
 
 My machine is running unstable:
 ~$ uname -a
 Linux gurh 2.6.11-1-686 #1 Mon Jun 20 22:00:38 MDT 2005 i686 GNU/Linux
 
 Any suggestions to how to get X working with nvidia module?
 
 Thanks in advance,
 /KS
 --
   KS
   [EMAIL PROTECTED]
 
 --
 http://www.fastmail.fm - Faster than the air-speed velocity of an
   unladen european swallow
 
 
 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 




No X - Problems with loading Nvidia module

2005-07-11 Thread KS
Hi,

I thought of restarting my machine after the browser was getting stuck
at some websites since last night. On restarting, X couldn't start.  The
error log indicated that the Nvidia module couldnot be loaded. Below are
the last few lines from the XFree86 log:

(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) NVIDIA(0): Linear framebuffer at 0xE000
(--) NVIDIA(0): MMIO registers at 0xFD00
(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0):  *** Aborting ***
(II) UnloadModule: nvidia
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found


My machine is running unstable:
~$ uname -a
Linux gurh 2.6.11-1-686 #1 Mon Jun 20 22:00:38 MDT 2005 i686 GNU/Linux

Any suggestions to how to get X working with nvidia module?

Thanks in advance,
/KS
-- 
  KS
  [EMAIL PROTECTED]

-- 
http://www.fastmail.fm - Faster than the air-speed velocity of an
  unladen european swallow


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



Re: X problems with kernel 2.6

2004-03-22 Thread Paul Mackinney
Ritesh Raj Sarraf declaimed:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 2.6.x kernels do:
 # modprobe mousedev;
 # modprobe psmouse;
 
Thanks a million. Since I was running without X, googling for the answer
as a previous correspondent suggested would have been difficult. Now I'm
off to read those 2.6.x docs...

:-) Paul
-- 
Paul Mackinney
[EMAIL PROTECTED]


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



Re: X problems with kernel 2.6

2004-03-22 Thread Kent West
Paul Mackinney wrote:

Thanks a million. Since I was running without X, googling for the answer
as a previous correspondent suggested would have been difficult. Now I'm
off to read those 2.6.x docs...
 

If you're not aware, there are text-mode web browsers (lynx is the best 
known one; links can be considered a variant; I think emacs has a 
browser mode, etc), so you don't need X to google. But perhaps you mean 
that googling in a GUI is easier than googling in text mode; I'd 
probably agree with you there.

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



Re: X-problems with a sony multisync 17se

2004-03-19 Thread urs . sonderegger
Thanks for your Inputs!

@Dave: I tried allready with several depth-parameters with no effect.

I think it's really the power-management wich makes these problems.
I tried another monitor yesterday and got the same troubles.
Now I play arount with PM-parameters in the ServerFlags of XF86Config-4 an
my BIOS.

I'll post the results later here.

'til then, sondi



Urs Sonderegger


Fon +41 71 226 12 16
Fax  +41 71 226 12 05
Web http://www.fhsg.ch/te

FHS Hochschule für Technik, Wirtschaft und Soziale Arbeit St.Gallen
Fachbereich Technik  Tellstrasse 2  Postfach 664  CH-9001 St.Gallen







X problems with kernel 2.6

2004-03-19 Thread Didier Caamano
Greetings:

I'm having a little bit of trouble starting X with kernel 2.6.4 from
unstable, I was using the standard kernel that comes with woody, then I
upgraded it using the normal method: apt-get install kernel-image.
With the old kernel X work flawlessly, but after the upgrade it start
having troubles with the mouse, the error is:
Cannot open /dev/psaux device does not exist, the thing is that it does,
cuz I went back to 2.4 and X worked just fine.

Is this just a bug that is being fixed or it is actually a problem in my
computer; any hint in how I can work with this problem will be
appreciated.

Well, have a nice day everyone,
Didier.



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



Re: X problems with kernel 2.6

2004-03-19 Thread Chris Metzler
On Fri, 19 Mar 2004 03:00:29 -0700
Didier Caamano [EMAIL PROTECTED] wrote:

 Is this just a bug that is being fixed or it is actually a problem in my
 computer; any hint in how I can work with this problem will be
 appreciated.

It's neither a bug nor a problem with your computer.  It's a
configuration change you need to make to run 2.6.

For more info, see the archives of this list.  Or, alternately, try
Google -- I googled on 2.6 kernel mouse /dev/psaux and got lots of
responses.

-c


-- 
Chris Metzler   [EMAIL PROTECTED]
(remove snip-me. to email)

As a child I understood how to give; I have forgotten this grace since I
have become civilized. - Chief Luther Standing Bear


pgp0.pgp
Description: PGP signature


Re: X problems with kernel 2.6

2004-03-19 Thread Ritesh Raj Sarraf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2.6.x kernels do:
# modprobe mousedev;
# modprobe psmouse;


HTH,
rrs

On Fri, 19 Mar 2004, Didier Caamano wrote:

 Date: Fri, 19 Mar 2004 03:00:29 -0700
 From: Didier Caamano [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: X problems with kernel 2.6
 Resent-Date: Fri, 19 Mar 2004 04:00:33 -0600 (CST)
 Resent-From: [EMAIL PROTECTED]

 Greetings:

 I'm having a little bit of trouble starting X with kernel 2.6.4 from
 unstable, I was using the standard kernel that comes with woody, then I
 upgraded it using the normal method: apt-get install kernel-image.
 With the old kernel X work flawlessly, but after the upgrade it start
 having troubles with the mouse, the error is:
 Cannot open /dev/psaux device does not exist, the thing is that it does,
 cuz I went back to 2.4 and X worked just fine.

 Is this just a bug that is being fixed or it is actually a problem in my
 computer; any hint in how I can work with this problem will be
 appreciated.

 Well, have a nice day everyone,
 Didier.



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


Ritesh Raj Sarraf   Email: rrs [EMAIL PROTECTED] researchut.com
Web: http://www.researchut.com  Phone: +91-9899655651
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFAW1E74Rhi6gTxMLwRApbdAJ9bQ+kL0jOUjaaD4U+LOPKv0ja9gwCgk+tw
WWw2KHM7e/4W/QDg/X7UYGk=
=kp5A
-END PGP SIGNATURE-


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



Re: X-problems with a sony multisync 17se

2004-03-18 Thread David
On Wed, Mar 17, 2004 at 04:36:57PM -0600, David wrote:
 On Wed, Mar 17, 2004 at 09:28:47PM +0100, [EMAIL PROTECTED] wrote:

  I have serious problems to start the X with my sony multisync 17se.

 My monitor is a Sony Multiscan 15 sf2

 I had a lot of identical blackouts when I was upgrading XFree.

One thing I forgot to mention (I think)..

I originally had my depth set to 24.  IIRC, I couldn't get a screen up
until I reduced the depth to 16.  If your depth is 24 or 32(?), you
might try dropping it to 16 and see what happens.  You can edit your
XF86Config-4 file, or, to just experiment, if you're starting up with
startx, you can specify the depth on the startx command line, I believe.


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



X-problems with a sony multisync 17se

2004-03-17 Thread sondi
hi!

I have serious problems to start the X with my sony multisync 17se.

My configuration is as follows:

Debian 24 from ftp.de.debian.org (woody)
XFree86 V4.4.0 (after I crashed with 4.1.0)

Graphic-Device: 3dLabs Oxygen VX1 (Glint Permedia V3) on PCI 1:0:0
Monitor: As described above.

It seems that everything is fine. No serious erroemessages in the XFree86.0.log
The startx seems to run and also the gdm. I looked after active processes
via
tty01 and there was a gdm-login waiting for login.

In fact my Screen keeps black like a starless night on tty07. It seems that
the
screen goes immediatly to suspend-mode when X is starting (the power-led
goes
off and only standby-led is on. All menue-functions on the controlpanel of
the
screen are disabled!?).

All my settings in XF86Config-4 are from original vendor-datasheets.
But i didn't set some clock modes. Could that sove my problems?
Does anybody have some clock-mode-parameters that work with this screen?
Is there a probe-tool available to get these parameters?

many thanks, sondi


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



Re: X-problems with a sony multisync 17se

2004-03-17 Thread Kenneth Macdoald Karlsen
On Wed, 2004-03-17 at 21:28, [EMAIL PROTECTED] wrote:
 hi!
 
 I have serious problems to start the X with my sony multisync 17se.
 
 My configuration is as follows:
 
 Debian 24 from ftp.de.debian.org (woody)
 XFree86 V4.4.0 (after I crashed with 4.1.0)
 
 Graphic-Device: 3dLabs Oxygen VX1 (Glint Permedia V3) on PCI 1:0:0
 Monitor: As described above.
 
 It seems that everything is fine. No serious erroemessages in the XFree86.0.log
 The startx seems to run and also the gdm. I looked after active processes
 via
 tty01 and there was a gdm-login waiting for login.
 
 In fact my Screen keeps black like a starless night on tty07. It seems that
 the
 screen goes immediatly to suspend-mode when X is starting (the power-led
 goes
 off and only standby-led is on. All menue-functions on the controlpanel of
 the
 screen are disabled!?).
 
 All my settings in XF86Config-4 are from original vendor-datasheets.
 But i didn't set some clock modes. Could that sove my problems?
 Does anybody have some clock-mode-parameters that work with this screen?
 Is there a probe-tool available to get these parameters?
 
 many thanks, sondi

Try:
 it may be helpful to enable more verbose output by using the XFree86
   command line options -verbose and -logverbose which can be used
   to set the verbosity level for the stderr and log file messages,

you can also try the command xf86config
dpkg-reconfigure x-window-system or xserver-xfree86
Kenneth
 


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



Re: X-problems with a sony multisync 17se

2004-03-17 Thread David
On Wed, Mar 17, 2004 at 09:28:47PM +0100, [EMAIL PROTECTED] wrote:

 I have serious problems to start the X with my sony multisync 17se.

 My configuration is as follows:

 Debian 24 from ftp.de.debian.org (woody)
 XFree86 V4.4.0 (after I crashed with 4.1.0)

Is this from some Debian package (if one exists) or is it compiled from
Xfree86 source?

 Graphic-Device: 3dLabs Oxygen VX1 (Glint Permedia V3) on PCI 1:0:0
 Monitor: As described above.

 In fact my Screen keeps black like a starless night on tty07. It seems that
 the
 screen goes immediatly to suspend-mode when X is starting (the power-led
 goes
 off and only standby-led is on. All menue-functions on the controlpanel of
 the
 screen are disabled!?).

My monitor is a Sony Multiscan 15 sf2

I had a lot of identical blackouts when I was upgrading XFree.  I have
an S3 chip in a rather old card.  I was using xserver-s3 (v3.3.6).  I
could never get XFree V4.2.1 from the package to work.  I don't recall
if I had these blackouts with the 4.2.1 package or not.  Seems I did.  I
finally downloaded the source and compiled my own, installing under
/usr/local.

I never did determine why my screen did black out like this.  I had
xserver-s3 v3.3.6, and packages from xfree 4.2.1 installed.  Some
modules from the wrong version could have been messing things up.

One thing you might do if you have this X installed in /usr/local.
After I got 4.3 going, a few programs, Pan, for one, would not start
because they were getting unresolved symbols in some of the modules.
Some of the dynamic links were going to the 4.3 libraries, and were
conflicting, so I added this line to my .bashrc:
   export LD_LIBRARY_PATH=/usr/local/X11R6/lib/
and now my X seems to work alright.  I had thought to install the
standard X 4.3 package from SID, but I'm afraid I'd break it, so I think
I'm going to leave this alone for a while.

 All my settings in XF86Config-4 are from original vendor-datasheets.
 But i didn't set some clock modes. Could that sove my problems?
 Does anybody have some clock-mode-parameters that work with this screen?
 Is there a probe-tool available to get these parameters?

xvidtune from the xbase-clients allows you to experiment with different
xmode settings.


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



X-problems: What do these two apps have in common?

2004-02-27 Thread David Baron
1. Netbeans Java-IDE, after recent upgrade including XFree86, immediately 
kicks out the session. One logs in again to a new X session. This is not the 
same as control/alt/bksp since in the 2.6.2 kernels, the mouse needs be 
exercised a bit before it starts working. A new session.

(Note that OpenOffice does not have this problem.)

2. KDE KPackage, GUI front end for apt-get, etc. This program still has a bug 
that when run as root, will not actively do anything and the work-around is 
to run as another user--it then requests a root login and works fine. Now ...

Run as root, aside from its bug, works 100%. No problem, simply go to a 
console shell to do anything active.

Run as other user, as soon as one starts browsing or tries to do anything, it 
kicks out the session. Again, a brand new login to a brand new session.

Run as a double-click on an associated .deb file, works without a hitch.

Any ideas?



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



Re: X-problems: What do these two apps have in common?

2004-02-27 Thread Nick Jacobs

--- David Baron [EMAIL PROTECTED] wrote:
 1. Netbeans Java-IDE, after recent upgrade including
 XFree86, immediately 
 kicks out the session. One logs in again to a new X
 session. This is not the 
 same as control/alt/bksp since in the 2.6.2 kernels,
 the mouse needs be 
 exercised a bit before it starts working. A new
 session.
 
 (Note that OpenOffice does not have this problem.)
 
 2. KDE KPackage, GUI front end for apt-get, etc.
 This program still has a bug 
 that when run as root, will not actively do anything
 and the work-around is 
 to run as another user--it then requests a root
 login and works fine. Now ...
 
 Run as root, aside from its bug, works 100%. No
 problem, simply go to a 
 console shell to do anything active.
 
 Run as other user, as soon as one starts browsing or
 tries to do anything, it 
 kicks out the session. Again, a brand new login to a
 brand new session.
 
 Run as a double-click on an associated .deb file,
 works without a hitch.
 
 Any ideas?

What's the message in your syslog? Is it:
gdm_slave_xioerror_handler: Fatal X error -
Restarting
:0 ?

If so, the problem could be similar to the one I
reported yesterday with subject Fatal X error: how to
diagnose?.
If it is the same problem then that narrows things
down a lot because we're using different kernels (mine
is 2.4.18-bf2.4). Does mplayer also kill your X
session?


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



Re: X-problems: What do these two apps have in common?

2004-02-27 Thread David Baron
On Friday 27 February 2004 10:10, you wrote:
 --- David Baron [EMAIL PROTECTED] wrote:
  1. Netbeans Java-IDE, after recent upgrade including
  XFree86, immediately
  kicks out the session. One logs in again to a new X
  session. This is not the
  same as control/alt/bksp since in the 2.6.2 kernels,
  the mouse needs be
  exercised a bit before it starts working. A new
  session.
 
  (Note that OpenOffice does not have this problem.)
 
  2. KDE KPackage, GUI front end for apt-get, etc.
  This program still has a bug
  that when run as root, will not actively do anything
  and the work-around is
  to run as another user--it then requests a root
  login and works fine. Now ...
 
  Run as root, aside from its bug, works 100%. No
  problem, simply go to a
  console shell to do anything active.
 
  Run as other user, as soon as one starts browsing or
  tries to do anything, it
  kicks out the session. Again, a brand new login to a
  brand new session.
 
  Run as a double-click on an associated .deb file,
  works without a hitch.
 
  Any ideas?

 What's the message in your syslog? Is it:
 gdm_slave_xioerror_handler: Fatal X error -
 Restarting

 :0 ?

Here is a section of the syslog for the shutdown I just reproduced:

Feb 27 11:57:19 d_baron kdm[912]: Server for display :0 terminated 
unexpectedly
Feb 27 11:57:21 d_baron kernel: atkbd.c: Unknown key released (translated set 
2,
 code 0x7a on isa0060/serio0).
Feb 27 11:57:21 d_baron kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
ac
cess hardware directly.
Feb 27 11:57:21 d_baron kernel: atkbd.c: Unknown key released (translated set 
2,
 code 0x7a on isa0060/serio0).
Feb 27 11:57:21 d_baron kernel: atkbd.c: This is an XFree86 bug. It shouldn't 
ac
cess hardware directly.
Feb 27 11:57:27 d_baron ypbind[619]: broadcast: RPC: Timed out.



 If so, the problem could be similar to the one I
 reported yesterday with subject Fatal X error: how to
 diagnose?.
 If it is the same problem then that narrows things
 down a lot because we're using different kernels (mine
 is 2.4.18-bf2.4). Does mplayer also kill your X
 session?

I do not have mplayer. I am, obviously, using kdm as a display/X-handler. 
There are two other entries here of note:

atkbd.c unknown key -- No keys were pressed to run netbeans nor were any 
pressed to restart until I typed my password to login. Note that this thing 
traps a lot of stuff. When I succumb to temptation and run uhic-hcd, a tap on 
the power switch will enable me to shut down. This is also flagged by 
atkbd.c. The shutdown is not a correct shutdown.

ypbind[619] broadcast: RPC: Timed out. I have one of these every 74 seconds. 
This was flagged on google (this time I checked) but no solutions. What is 
it. This is apparently harmless but might as well fix it :-) I think there is 
a bootup message relating to this as well.


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



ypbind (was: Re: X-problems: What do these two apps have in common?)

2004-02-27 Thread Derrick 'dman' Hudson
On Fri, Feb 27, 2004 at 12:13:13PM +0100, David Baron wrote:

| Feb 27 11:57:27 d_baron ypbind[619]: broadcast: RPC: Timed out.

| ypbind[619] broadcast: RPC: Timed out. I have one of these every 74 seconds. 
| This was flagged on google (this time I checked) but no solutions. What is 
| it. This is apparently harmless but might as well fix it :-) I think there is 
| a bootup message relating to this as well.

ypbind is part of the NIS system.  (NIS is Network Information System,
I think)  NIS was developed in the mid-80's by Sun to solve the
administrative problem of synchronizing /etc/passwd, /etc/group,
/etc/hosts, and /etc/services on many machines on a single network.  I
don't know anything beyond that, but if you aren't using NIS then you
certainly have no need for ypbind and can remove it.  (I don't know
what package its in, though)

HTH,
-D

-- 
In my Father's house are many rooms; if it were not so, I would have
told you.  I am going there to prepare a place for you.  And if I go and
prepare a place for you, I will come and take you to be with me that you
also may be where I am.
John 14:2-3
 
www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED]


signature.asc
Description: Digital signature


X problems with unstable

2003-08-31 Thread R Ransbottom
In installing xserver-common (4.2.1-10) on unstable I get a
note:
Note: not updating /etc/X11/Xwrapper.config; file does not exist.

This is followed by xserver-xfree86 (4.2.1-10) noting:
Note: not updating /etc/X11/X; file does not exist.
Note: not updating /etc/X11/XF86Config-4; file does not exist.

What should I read/do to get X going?

Thanks.

-- 
rir Live the dream.


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



Re: X problems with unstable

2003-08-31 Thread Marc Wilson
On Sat, Aug 30, 2003 at 08:44:34PM -0400, R Ransbottom wrote:
 What should I read/do to get X going?

You should read the BTS, like any other unstable user would.  This is
endlessly reported there, including workarounds.

-- 
 Marc Wilson | All of the true things I am about to tell you are
 [EMAIL PROTECTED] | shameless lies.  -- The Book of Bokonon / Kurt
 | Vonnegut Jr.


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



Re: X problems with unstable

2003-08-31 Thread Russell Shaw
R Ransbottom wrote:
In installing xserver-common (4.2.1-10) on unstable I get a
note:
Note: not updating /etc/X11/Xwrapper.config; file does not exist.
This is followed by xserver-xfree86 (4.2.1-10) noting:
Note: not updating /etc/X11/X; file does not exist.
Note: not updating /etc/X11/XF86Config-4; file does not exist.
What should I read/do to get X going?

Thanks.

man dpkg

Try the confmiss option.

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



Re: X problems with unstable

2003-08-31 Thread Robert Ian Smit
* R Ransbottom [EMAIL PROTECTED] [31-08-2003 02:30]:
 In installing xserver-common (4.2.1-10) on unstable I get a
 note:
 Note: not updating /etc/X11/Xwrapper.config; file does not exist.

A new version of that package is available. I am not sure if it
solves this issue though. The problem bit me on a clean install of
X. On my normal system I just upgraded to 4.2.1-11 from a somewhat
older version.

Bob


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



X problems after an upgrade with bunk packages

2003-08-02 Thread Joris Huizer
Hello everybody,

Today I did an upgrade using
apt-get upgrade
with the bunk packages in the /etc/apt/sources.list -
and it had a lot of upgrades for x in the bunk
packages. I never had problems with the bunk packages
before but... now suddenly the X isn't working anymore
!
I now removed the bunk packages urls from the
/etc/apt/sources.list but I don't know exactly what I
should downgrade.
I seem to remember there is a downloading log
somewhere but... I don't know where it is... 

Can someone tell me where this log file is - or, which
x programs to downgrade ?

Thanks for your help !

Joris Huizer

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


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



Re: X problems after an upgrade with bunk packages SOLVED

2003-08-02 Thread Joris Huizer

--- Joris Huizer [EMAIL PROTECTED] wrote:
 Hello everybody,
 
 Today I did an upgrade using
 apt-get upgrade
 with the bunk packages in the /etc/apt/sources.list
 -
 and it had a lot of upgrades for x in the bunk
 packages. I never had problems with the bunk
 packages
 before but... now suddenly the X isn't working
 anymore
 !
 I now removed the bunk packages urls from the
 /etc/apt/sources.list but I don't know exactly what
 I
 should downgrade.
 I seem to remember there is a downloading log
 somewhere but... I don't know where it is... 
 
 Can someone tell me where this log file is - or,
 which
 x programs to downgrade ?
 
 Thanks for your help !
 
 Joris Huizer

Sorry the problem had to do with the
/etc/X11/XFConfig-4 file which had been overwritten -
but I now solved it :-)



__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


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



Re: X problems, likely vertical refresh

2003-01-21 Thread Matthew Weier O'Phinney
-- Matthew Weier O'Phinney [EMAIL PROTECTED] wrote
(on Monday, 20 January 2003, 04:18 PM -0500):
 I just installed an ATI All-in-Wonder PCI VGA card in my machine, and
 I'm having a few problems with X.
 
 I'm using a Slimline flat-panel LCD monitor
snip 
 I'm getting some wierd behaviour, though. When I load X, I get a gray
 pattern that has vertical dark areas that then gradate out to vertical
 lighter areas. Once blackbox has loaded with my backdrop, it's not
 noticable ... until you start looking at apps, and start to notice that
 wherever there was a dark bar, any text/graphics overlying that area are
 darkened and defocussed along those vertical strips. It makes it
 difficult to read, to say the least.

I neglected to mention I'm using Xfree86 4.2.1 from Debian testing.

As a followup:
I tried a number of things, from using the gatos project ati.2 4.2.0
binaries with the debian 4.2.1 distribution (caused wierd flicker), to
installing 4.2.0 binaries from Xfree86.org and using the gatos
binaries... none of which worked. I decided to go back to my backups of
my /usr/X11R6 directory (made just before trying the gatos binaries --
when I was still having the problems with the vertical banding) -- and
lo and behold but it's working now. 

Not sure what to attribute it to, if anything -- just going to go with
it for now.

Thanks for the suggestions, all.

-- 
Matthew Weier O'Phinney
[EMAIL PROTECTED]


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




X problems, likely vertical refresh

2003-01-20 Thread Matthew Weier O'Phinney
I just installed an ATI All-in-Wonder PCI VGA card in my machine, and
I'm having a few problems with X.

I'm using a Slimline flat-panel LCD monitor, and I have a chart showing
Horizontal frequency and Vertical refresh rates. I've specified the
appropriate ranges in my /etc/X11/XF86Config-4 file. I've also specified
the ati driver for my video device. (I've attached the full
XF86Config-4 file below.)

I'm getting some wierd behaviour, though. When I load X, I get a gray
pattern that has vertical dark areas that then gradate out to vertical
lighter areas. Once blackbox has loaded with my backdrop, it's not
noticable ... until you start looking at apps, and start to notice that
wherever there was a dark bar, any text/graphics overlying that area are
darkened and defocussed along those vertical strips. It makes it
difficult to read, to say the least.

I hadn't noticed this behaviour on the same monitor with a different
graphics card (I've tried it with both an S3 Savage and an old NVidia
TNT card), so I'm wondering if it's specific to the ATI card. In
addition, I may have had it working previously with the ATI card -- but
I cannot find any settings that work correctly right now.

The settings available to the monitor are:
Res.Horiz(KHz)  Vertical(Hz)
640x400 31.47   70
640x400 31.47   70
640x480 31.47   59.9
640x480 37.972
640x480 37.86   75
800x600 35.16   56.3
800x600 37.88   60.3
800x600 48.09   72
800x600 46.975
1024x76848.36   60
1024x76856.48   70.1
1024x76860  75

/etc/X11/XF86Config-4:
### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) 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.)
#
# If you want your changes to this file preserved by dexconf, only make changes
# before the ### BEGIN DEBCONF SECTION line above, and/or after the
# ### END DEBCONF SECTION line below.
#
# To change things within the debconf section, run the command:
#   dpkg-reconfigure xserver-xfree86
# as root.  Also see How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz.

Section Files
FontPathunix/: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/Speedo
FontPath/usr/lib/X11/fonts/100dpi
FontPath/usr/lib/X11/fonts/75dpi
EndSection

Section Module
LoadGLcore
Loadbitmap
Loaddbe
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Loadspeedo
Loadtype1
Loadvbe
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc104
Option  XkbLayout us
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/input/mice
Option  Protocol  ImPS/2
Option  ZAxisMapping  4 5
EndSection

Section Device
Identifier  ATI Mach64 Rage 3d +DVD
Driver  ati
VideoRam8192
EndSection

Section Monitor
Identifier  flatpanel
HorizSync   30-60
VertRefresh 50-75
Option  DPMS
EndSection

Section Screen
Identifier  Default Screen
Device  ATI Mach64 Rage 3d +DVD
Monitor flatpanel
DefaultDepth16
SubSection Display
Depth   1
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   4
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   8
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   15
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   16
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth  

Re: X problems, likely vertical refresh

2003-01-20 Thread Egor Tur
Hi Matthew.
I have ATI All-in-Wonder Pro AGP card and I use driver from GATOS for
XFree86 version 4.1.x. This driver works fine for me (XVideo, TV tuner ...)

attachment: Pict0008.JPG


Re: Mouse / X problems UPDATE

2003-01-19 Thread Chris Owen
Hey, thanks Kent that's great.
(I have been following the list, honest!  Guess I missed that post 
though...)
:-)

Chris


Kent West wrote:

Chris Owen wrote:


I have now found a solution for this mouse problem in X: it seems gpm 
was the problem.  After uninstalling gpm, the PS/2 mouse now works 
correctly in X.  If anyone can tell me why this is, or whether 
there's a workaround which lets me keep gpm, that would be 
interesting (although to be honest I'm not that bothered about 
needing gpm...).

Thanks
Chris



From a posting earlier in the day (subj: MOUSE won't function):

gpm is a mouse driver for the text-only virtual console. For example, 
if you are not running X, and you only have text-only virtual consoles 
(hereafter referred to as VTs, for Virtual Terminals), and you need a 
mouse in your VTs, then you'd need to be running gpm. Or even if you 
are running X, but you occasionally need to pop out to a VT and need a 
mouse while there, you'd need gpm running.

Now, if you have X running, X needs a mouse. It has its own mouse 
driver built-in. This mouse driver conflicts with gpm, and having gpm 
running as well as X can cause the mouse to behave erratically, etc. 
For example, the mouse might generate some events, such as I've moved 
left, followed by I've moved up. If both gpm and the X mouse driver 
are reading the mouse port, it may be that gpm reads the left event, 
removing that event from the incoming data stream, and then it comes 
X's turn to read the mouse events, and it reads up, never getting a 
chance to read the left event because gpm took it. So the mouse 
behaviour in X was supposed to be left, then up, but turns out to be 
only up. Doh!

Thankfully, these two mouse drivers can be convinced to play nicely 
together. The way this is done is to tell gpm to not keep the incoming 
data to itself, but to repeat that incoming data, in a raw format. 
Both gpm and X normally read from the incoming mouse data port 
(whatever that is, perhaps /dev/psaux, perhaps /dev/ttyS0, etc). gpm 
can't repeat the data it reads back to that port, or next time it goes 
to read that port it'll just re-read what it read earlier, and 
loopity-loop. So instead it repeats the data to a special virtual 
port, called /dev/gpmdata. Then X needs to be configured to read its 
incoming mouse data, not from the normal port, but from the 
/dev/gpmdata port. Voila! gpm and X now get along just dandy.

So, you have two options.

1) Remove gpm, and just get the mouse working in X

2) Configure gpm to repeat the raw data (run gpmconfig and answer the 
questions), and configure X to read its mouse data from /dev/gpmdata.







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



Mouse / X problems

2003-01-18 Thread Chris Owen
Hi, if someone could help me get my X server + mouse running I'd be very 
grateful.

Hardware details:
Old AJP 5400 laptop (you won't have heard of it), 75MHz Pentium, 16MB RAM
Trackpad PS/2 mouse
Cirrus Logic 754x display chipset
800x600 LCD display
Debian 3.0r0

The story so far:
I used to have RetHat 6.0 going on this machine and X was fine, so I 
know it's possible.
1.  Started with XFree86-v4, as installed by default.  Chose the 
cirrus driver.  Debconf configuration didn't start X, error in log 
file about No screens found.
2.  Ran XFree86 -configure, this came up with an XF86Config.new which 
used the vesa driver.  With this, X comes up but mouse not working.
3.  After some unsuccessful mucking about, decided to try the XFree86-v3 
server, so uninstalled xserver-xfree86 and installed xserver-svga.
4.  dpkg-reconfigure xserver-svga produces an XF86Config which allows X 
to start, but still mouse problems.  The cursur does respond to mouse 
movements, but goes haywire, sticking, jumping and opening menus.
5.  xf86config-v3 produces an XF86Config which doesn't work at all, 
complains about lines such as Modes (null).
6.  I had saved off my old XF86Config which used to work under RH6.0, 
tried this but it chokes on the very first line; complains about Section 
Files, saying File section keyword expected.  Don't understand this 
at all, as the syntax here seems to be that same as the XF86Config files 
which do work, I even tried copying the Files section over but get the 
same error?
7.  Went back to dpkg-reconfigure xserver-svga, tried every one of the 
PS/2 protocols but they all behave the same way.  I'm quite sure the 
mouse is PS/2.  Also tried an external mouse plugged into the PS/2 port, 
and get same result.

I'm attaching XF86Config-RH6 (the old RH6.0 one which used to work), and 
the current XF86Config produced by dpkg-reconfigure.

Thanks a lot for any help

Chris




XF86Config-RH6
Description: application/java-applet


XF86Config
Description: application/java-applet


Re: Mouse / X problems UPDATE

2003-01-18 Thread Chris Owen
I have now found a solution for this mouse problem in X: it seems gpm 
was the problem.  After uninstalling gpm, the PS/2 mouse now works 
correctly in X.  If anyone can tell me why this is, or whether there's a 
workaround which lets me keep gpm, that would be interesting (although 
to be honest I'm not that bothered about needing gpm...).

Thanks
Chris

Chris Owen wrote:

Hi, if someone could help me get my X server + mouse running I'd be 
very grateful.

Hardware details:
Old AJP 5400 laptop (you won't have heard of it), 75MHz Pentium, 16MB RAM
Trackpad PS/2 mouse
Cirrus Logic 754x display chipset
800x600 LCD display
Debian 3.0r0

The story so far:
I used to have RetHat 6.0 going on this machine and X was fine, so I 
know it's possible.
1.  Started with XFree86-v4, as installed by default.  Chose the 
cirrus driver.  Debconf configuration didn't start X, error in log 
file about No screens found.
2.  Ran XFree86 -configure, this came up with an XF86Config.new which 
used the vesa driver.  With this, X comes up but mouse not working.
3.  After some unsuccessful mucking about, decided to try the 
XFree86-v3 server, so uninstalled xserver-xfree86 and installed 
xserver-svga.
4.  dpkg-reconfigure xserver-svga produces an XF86Config which allows 
X to start, but still mouse problems.  The cursur does respond to 
mouse movements, but goes haywire, sticking, jumping and opening menus.
5.  xf86config-v3 produces an XF86Config which doesn't work at all, 
complains about lines such as Modes (null).
6.  I had saved off my old XF86Config which used to work under RH6.0, 
tried this but it chokes on the very first line; complains about 
Section Files, saying File section keyword expected.  Don't 
understand this at all, as the syntax here seems to be that same as 
the XF86Config files which do work, I even tried copying the Files 
section over but get the same error?
7.  Went back to dpkg-reconfigure xserver-svga, tried every one of the 
PS/2 protocols but they all behave the same way.  I'm quite sure the 
mouse is PS/2.  Also tried an external mouse plugged into the PS/2 
port, and get same result.

I'm attaching XF86Config-RH6 (the old RH6.0 one which used to work), 
and the current XF86Config produced by dpkg-reconfigure.

Thanks a lot for any help

Chris






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



Re: Mouse / X problems UPDATE

2003-01-18 Thread Kent West
Chris Owen wrote:


I have now found a solution for this mouse problem in X: it seems gpm 
was the problem.  After uninstalling gpm, the PS/2 mouse now works 
correctly in X.  If anyone can tell me why this is, or whether there's 
a workaround which lets me keep gpm, that would be interesting 
(although to be honest I'm not that bothered about needing gpm...).

Thanks
Chris


From a posting earlier in the day (subj: MOUSE won't function):

gpm is a mouse driver for the text-only virtual console. For example, if 
you are not running X, and you only have text-only virtual consoles 
(hereafter referred to as VTs, for Virtual Terminals), and you need a 
mouse in your VTs, then you'd need to be running gpm. Or even if you are 
running X, but you occasionally need to pop out to a VT and need a mouse 
while there, you'd need gpm running.

Now, if you have X running, X needs a mouse. It has its own mouse driver 
built-in. This mouse driver conflicts with gpm, and having gpm running 
as well as X can cause the mouse to behave erratically, etc. For 
example, the mouse might generate some events, such as I've moved 
left, followed by I've moved up. If both gpm and the X mouse driver 
are reading the mouse port, it may be that gpm reads the left event, 
removing that event from the incoming data stream, and then it comes X's 
turn to read the mouse events, and it reads up, never getting a chance 
to read the left event because gpm took it. So the mouse behaviour 
in X was supposed to be left, then up, but turns out to be only up. Doh!

Thankfully, these two mouse drivers can be convinced to play nicely 
together. The way this is done is to tell gpm to not keep the incoming 
data to itself, but to repeat that incoming data, in a raw format. 
Both gpm and X normally read from the incoming mouse data port 
(whatever that is, perhaps /dev/psaux, perhaps /dev/ttyS0, etc). gpm 
can't repeat the data it reads back to that port, or next time it goes 
to read that port it'll just re-read what it read earlier, and 
loopity-loop. So instead it repeats the data to a special virtual 
port, called /dev/gpmdata. Then X needs to be configured to read its 
incoming mouse data, not from the normal port, but from the /dev/gpmdata 
port. Voila! gpm and X now get along just dandy.

So, you have two options.

1) Remove gpm, and just get the mouse working in X

2) Configure gpm to repeat the raw data (run gpmconfig and answer the 
questions), and configure X to read its mouse data from /dev/gpmdata.



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



X problems with two monitors

2002-09-24 Thread Andre Fassbender

Hello all,

i have two monitors (2x 1024x768) on my debian 3.0 with X 4.1.0.1 and WindowMaker 
0.80.0. I configured the xinerama mode and most all works properly. When i set a 
scaled backround picture its being resized to 2048x768 but the right monitor shows the 
same left part of the picture that the left monitor shows. 
Through a transparent window like Eterm the picture on the right side is correct so if 
i fullscreen the window on the right side the full picture is correct.

Has anyone else experienced this? How can i resolve this?

Thanks for your help,

Andre

--

Yoda of Borg are we: Futile is resistance. Assimilate you, we will!
-- NN

 


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




Re: remote X problems

2002-03-24 Thread David Wright


Okay, I figured out the problem. Seems the xbase-clients package needs 
to be installed. I don't quite understand why the packages of programs 
like xosview don't depend on this.



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




remote X problems

2002-03-23 Thread David Wright

Argh! I hate^H^H^H^H^H am having some trouble with X.

  $ ssh -l root foo.example.com
  foo# xosview 
Can't open display named

Yes, sshd_config on foo contains
  X11Forwarding yes
and ssh_config on my machine contains
  ForwardX11 yes
In fact, everyting works fine on many other machines I have set up at 
example.com.


The machines with a problem are those where I haven't installed X on 
foo. But you're not supposed to have to install X on a server if it 
always displays remotely. I don't want X on my servers. (This problem 
never occured with RedHat.)


I haven't been able to find any hint of what's going on any logs on the 
server or on the client. I do note that

  foo~# echo $DISPLAY
return nothing, whereas on machines where the X-forwarding works, I do 
get something. But

  foo# export DISPLAY=foo.example.com:0
doesn't help.

What do I have to do to get a machine without X to forward X output over 
ssh?




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




Re: remote X problems

2002-03-23 Thread Michel Loos
Em Sáb, 2002-03-23 às 22:10, David Wright escreveu:
 Argh! I hate^H^H^H^H^H am having some trouble with X.
 
$ ssh -l root foo.example.com
foo# xosview 
 Can't open display named
 


this should be

ssh -X [EMAIL PROTECTED]

Michel.
 Yes, sshd_config on foo contains
X11Forwarding yes
 and ssh_config on my machine contains
ForwardX11 yes
 In fact, everyting works fine on many other machines I have set up at 
 example.com.
 
 The machines with a problem are those where I haven't installed X on 
 foo. But you're not supposed to have to install X on a server if it 
 always displays remotely. I don't want X on my servers. (This problem 
 never occured with RedHat.)
 
 I haven't been able to find any hint of what's going on any logs on the 
 server or on the client. I do note that
foo~# echo $DISPLAY
 return nothing, whereas on machines where the X-forwarding works, I do 
 get something. But
foo# export DISPLAY=foo.example.com:0
 doesn't help.
 
 What do I have to do to get a machine without X to forward X output over 
 ssh?
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 



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



X-problems, please read

2002-03-23 Thread Iván Filpo
Hello i have a computer with a Gforce2gts 32 ddram, 1.3mhz athlon-tbird
computer , 256 mb of memory.

I have Debian woody installed using xf4 and Sometimes X crashes dont know
why?. And i have checked /var/log/X* and .xsession-errors. The /var/
file when i do tail the only error i see is: mouse protocol could not be
determined and in the .xsession errors i dont see anything like that.


Please if u have any ideas of how i can find what is causing X to crash
please let me know, or if u know what maybe causing X to crash please let me
know.


Thanks to all in advance



Re: remote X problems

2002-03-23 Thread David Wright


  ssh -X [EMAIL PROTECTED]

-X is the same as saying X11Forward = yes and root@ is the same as 
saying -l root. Doesn't help. (I did try, just to make sure.)



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




Re: ssh2 / X problems

2002-02-03 Thread shock
 Cameron Kerr ([EMAIL PROTECTED]) spake thusly:
 On Sat, 2 Feb 2002, shock wrote:
 
 Does it happen with any other user account?

it happens with all accounts.

 Try running the server in debug mode. This will likely tell you whats
 happening.

this results in output on both the client and server side.  Here's the
client side output:


[EMAIL PROTECTED]:~$ ssh2 server2
stephen's password:
Authentication successful.
debug: Ssh2ChannelSession/sshchsession.c:738/ssh_channel_session_child:
ssh_channel_session_child: now running as user 'stephen'
debug: Environment:
debug:   HOME=/home/stephen
debug:   USER=stephen
debug:   LOGNAME=stephen
debug:   PATH=/usr/bin:/bin:/usr/local/bin
debug:   MAIL=/var/spool/mail/stephen
debug:   SHELL=/bin/bash
debug:   SSH2_CLIENT=192.168.1.10 63545 192.168.1.99 22
debug:   TERM=xterm
debug:   DISPLAY=server2.exitwound.org:10.0
debug:   LANG=C
debug: Running /usr/X11R6/bin/xauth add server2.exitwound.org:10.0
MIT-MAGIC-COOKIE-1 1f55726ddb9304a5d35c0401fcca6961
debug: Running /usr/X11R6/bin/xauth add 192.168.1.99:10.0
MIT-MAGIC-COOKIE-1 1f55726ddb9304a5d35c0401fcca6961
Last login: Sun Feb 03 2002 12:45:27 -0600
Linux server2.exitwound.org 2.4.17-pre8 #7 SMP Fri Dec 14 11:49:44 CST
2001 i686 unknown
 
Most of the programs included with the Debian GNU/Linux system are
freely redistributable; the exact distribution terms for each program
are described in the individual files in /usr/share/doc/*/copyright
  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
No mail.
[EMAIL PROTECTED]:~$


and here's the server-side output


debug: SshAppCommon/sshappcommon.c:154/ssh_app_get_global_regex_context:
Allocating global SshRegex context.
sshd2: SSH Secure Shell 3.0.1 (non-commercial version) on
i686-pc-linux-gnu
debug: SshHostKeyIO/sshhostkeyio.c:220/ssh_host_key_read_keys: Host key
algorithms: ssh-dss
debug: Becoming server.
debug: Creating listener
debug: Listener created
debug: no udp listener created.
sshd2[21630]: Listener created on port 22.
sshd2[21630]: Daemon is running.
debug: Running event loop
sshd2[21630]: connection from 192.168.1.10
debug: Sshd2/sshd2.c:1062/new_connection_callback:
new_connection_callback
debug: Sshd2/sshd2.c:1214/new_connection_callback: Wrapping stream with
ssh_server_wrap...
debug: ssh_server_wrap: creating transport protocol
debug:
SshAuthMethodServer/sshauthmethods.c:118/ssh_server_authentication_initialize:
Added publickey to usable methods.
debug:
SshAuthMethodServer/sshauthmethods.c:118/ssh_server_authentication_initialize:
Added password to usable methods.
debug:
SshAuthMethodServer/sshauthmethods.c:133/ssh_server_authentication_initialize:
Added hostbased to usable methods.
debug: ssh_server_wrap: creating userauth protocol
debug: Ssh2Common/sshcommon.c:496/ssh_common_wrap: local ip =
192.168.1.99, local port = 22
debug: Ssh2Common/sshcommon.c:498/ssh_common_wrap: remote ip =
192.168.1.10, remote port = 63545
debug: SshConnection/sshconn.c:1889/ssh_conn_wrap: Wrapping...
debug: Sshd2/sshd2.c:1232/new_connection_callback: done.
debug: new_connection_callback returning
debug: Remote version: SSH-1.99-3.0.1 SSH Secure Shell (non-commercial)
debug: Major: 3 Minor: 0 Revision: 1
debug: Ssh2Transport/trcommon.c:1717/ssh_tr_negotiate: lang s to c: `',
lang c to s: `'
debug: Ssh2Transport/trcommon.c:1783/ssh_tr_negotiate: c_to_s: cipher
aes128-cbc, mac hmac-sha1, compression none
debug: Ssh2Transport/trcommon.c:1786/ssh_tr_negotiate: s_to_c: cipher
aes128-cbc, mac hmac-sha1, compression none
debug: Sshd2/sshd2.c:593/auth_policy_proc: user 'stephen' service
'ssh-connection' client_ip '192.168.1.10' client_port '63545' completed
''
debug: Sshd2/sshd2.c:901/auth_policy_proc: output: publickey,password
debug:
SshUnixUser/sshunixuser.c:1250/ssh_user_validate_secure_rpc_password:
not yet implemented
debug:
SshUnixUser/sshunixuser.c:1238/ssh_user_validate_kerberos_password:
kerberos support not compiled in
sshd2[21630]: User stephen's local password accepted.
sshd2[21630]: Password authentication for user stephen accepted.
debug: Sshd2/sshd2.c:593/auth_policy_proc: user 'stephen' service
'ssh-connection' client_ip '192.168.1.10' client_port '63545' completed
'password'
debug: Ssh2AuthServer/sshauths.c:335/success_completion_proc:
no_more_needed=TRUE
debug: Ssh2Common/sshcommon.c:291/ssh_common_special: Received
SSH_CROSS_STARTUP packet from connection protocol.
debug: Ssh2Common/sshcommon.c:341/ssh_common_special: Received
SSH_CROSS_ALGORITHMS packet from connection protocol.
debug: Ssh2Common/sshcommon.c:259/ssh_common_special: Received
SSH_CROSS_AUTHENTICATED packet from connection protocol.
sshd2[21630]: User stephen, coming from pappy.exitwound.org,
authenticated.
debug: Ssh2Common/sshcommon.c:718/ssh_common_new_channel: num_channels
now 1
debug: 

Re: ssh2 / X problems

2002-02-03 Thread shock
* Stephen E. Hargrove ([EMAIL PROTECTED]) spake thusly:
  Cameron Kerr ([EMAIL PROTECTED]) spake thusly:
  On Sat, 2 Feb 2002, shock wrote:
  
  Does it happen with any other user account?
 
 it happens with all accounts.

okay, i'm not really sure what's going on, but rebooting my client
machine corrected the problem.

thanks!
-- 
 ) ,_),_)
(-(__  |_  _  _ |/
 ) | |(_)(_ |\
( \_,
 ___
| http://www.exitwound.org: hard to find|
| http://www.buckowensfan.com : he's the man|
 ___
| He was a fiddler, and consequently a rogue.   |
| -- Jonathon Swift |
 ___
 -BEGIN GEEK CODE BLOCK-
| Version: 3.1  |
| GJ/IT d- s: a C+++$ UL P+++ L+++ E--- W++| 
| N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ |
| R tv+@ b+ DI D+ G++ e h r+++ y+++ |
 --END GEEK CODE BLOCK--



ssh2 / X problems

2002-02-02 Thread shock
I have two servers, and both have exactly the same configuration files.
I can ssh2 to one and fire up X applications.  However, the other
results in the following.  (Both servers have X forwarding enabled in
the ssh2_config file.)

[EMAIL PROTECTED]:~/bin/perlmonks$ ssh2 +x -v server2
debug: Connecting to server2, port 22...
debug: Ssh2/ssh2.c:1956/main: Entering event loop.
debug: Ssh2Client/sshclient.c:1330/ssh_client_wrap: Creating transport
protocol.
debug:
SshAuthMethodClient/sshauthmethodc.c:137/ssh_client_authentication_initialize:
Added publickey to usable methods.
debug:
SshAuthMethodClient/sshauthmethodc.c:137/ssh_client_authentication_initialize:
Added password to usable methods.
debug: Ssh2Client/sshclient.c:1362/ssh_client_wrap: Creating userauth
protocol.
debug: client supports 2 auth methods: 'publickey,password'
debug: Ssh2Common/sshcommon.c:496/ssh_common_wrap: local ip =
192.168.2.2, local port = 48245
debug: Ssh2Common/sshcommon.c:498/ssh_common_wrap: remote ip =
192.168.1.99, remote port = 22
debug: SshConnection/sshconn.c:1889/ssh_conn_wrap: Wrapping...
debug: Remote version: SSH-2.0-3.0.1 SSH Secure Shell (non-commercial)
debug: Major: 3 Minor: 0 Revision: 1
debug: Ssh2Transport/trcommon.c:1717/ssh_tr_negotiate: lang s to c: `',
lang c to s: `'
debug: Ssh2Transport/trcommon.c:1783/ssh_tr_negotiate: c_to_s: cipher
aes128-cbc, mac hmac-sha1, compression none
debug: Ssh2Transport/trcommon.c:1786/ssh_tr_negotiate: s_to_c: cipher
aes128-cbc, mac hmac-sha1, compression none
debug: Remote host key found from database.
debug: Ssh2Common/sshcommon.c:291/ssh_common_special: Received
SSH_CROSS_STARTUP packet from connection protocol.
debug: Ssh2Common/sshcommon.c:341/ssh_common_special: Received
SSH_CROSS_ALGORITHMS packet from connection protocol.
debug: server offers auth methods 'publickey,password'.
debug: SshConfig/sshconfig.c:2184/ssh2_parse_config: Unable to open
/home/stephen/.ssh2/identification
debug: Ssh2AuthClient/sshauthc.c:316/ssh_authc_completion_proc: Method
'publickey' disabled.
debug: server offers auth methods 'publickey,password'.
debug: Ssh2AuthPasswdClient/authc-passwd.c:95/ssh_client_auth_passwd:
Starting password query...
stephen's password:
debug: Ssh2Common/sshcommon.c:259/ssh_common_special: Received
SSH_CROSS_AUTHENTICATED packet from connection protocol.
Authentication successful.
debug: Ssh2Common/sshcommon.c:718/ssh_common_new_channel: num_channels
now 1
debug: Requesting X11 forwarding with authentication spoofing.
Last login: Sat Feb 02 2002 18:38:25 -0600
Linux server2.exitwound.org 2.4.17-pre8 #7 SMP Fri Dec 14 11:49:44 CST
2001 i686 unknown
 
Most of the programs included with the Debian GNU/Linux system are
freely redistributable; the exact distribution terms for each program
are described in the individual files in /usr/share/doc/*/copyright
  
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
No mail.
[EMAIL PROTECTED]:~$ xcalc
Error: Can't open display:
[EMAIL PROTECTED]:~$

Any thoughts on what I should do or where I should be looking?

Thanks!
-- 
 ) ,_),_)
(-(__  |_  _  _ |/
 ) | |(_)(_ |\
( \_,
 ___
| http://www.exitwound.org: hard to find|
| http://www.buckowensfan.com : he's the man|
 ___
| You could live a better life, if you had a|
| better mind and a better body.|
 ___
 -BEGIN GEEK CODE BLOCK-
| Version: 3.1  |
| GJ/IT d- s: a C+++$ UL P+++ L+++ E--- W++| 
| N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ |
| R tv+@ b+ DI D+ G++ e h r+++ y+++ |
 --END GEEK CODE BLOCK--



Re: ssh2 / X problems

2002-02-02 Thread Cameron Kerr
On Sat, 2 Feb 2002, shock wrote:

I have two servers, and both have exactly the same configuration files.
I can ssh2 to one and fire up X applications.  However, the other
results in the following.  (Both servers have X forwarding enabled in
the ssh2_config file.)

[snip debugging output]

Let's see, what are the symptoms?

The client is definately asking for X11-forwarding, but is not getting set
up. You don't appear to using OpenSSH at all, rather SSH2

The DISPLAY environment variable doesn't seem to be getting set to
anything at all.

You're using password authentication, as shown by the fact that you are
prompted for a password, which means its not using any limits placed on
your public key in its .ssh2/authorized_files.

This leaves a few things we have left to try out (I've just finished
reading SSH: The Definitive Guide, lets see what I can remember)

- The Compile Time compilation options
- The sshd2.config (name?)

Does it happen with any other user account?
Try running the server in debug mode. This will likely tell you whats
happening.

Cameron Kerr
-- 
[EMAIL PROTECTED]
http://homepages.paradise.net.nz/~cameronk/




diskless X problems

2002-01-30 Thread David Wright

I am trying to set up a diskless workstation (to centralize maintainance) but 
am having problems getting X sessions to work.

The system boots (from a floppy, then mounts root and /usr seperately over 
nfs), and I can login and work from a text console. The xdm login appears, but 
when I log in, something goes wrong. Sometimes I am logged right back out 
(auth.log shows pam_unix logging me in and out within a few seconds, and I 
can't find any log messages in between). Sometimes gnome begins to load, but 
then it dies with a message that x-session-manager crashed. Graphical login 
works fine on the system that I used as a template, and I have only made 
trivial changes to /etc (hostname, fstab). Is there someone out (perhaps with 
diskless X experience) who can give me a hint on how I need to change the gnome 
or X or sawfish configuration
to work disklessly?

The fact that the behaviour is not entirely reproducable also makes me suspect 
that running without swap might be a problem. Memory shouldn't be a problem -- 
this machine has 1 GB and I'm barely working it -- but is there some stuff one 
needs swap for anyway? Is there perhaps some kernel compile flag that disables 
swap attempts completely?



Re: diskless X problems

2002-01-30 Thread Henry House
On Wed, Jan 30, 2002 at 02:25:31AM -0800, David Wright wrote:
 I am trying to set up a diskless workstation (to centralize maintainance) but 
 am having problems getting X sessions to work.

I have done this as well.

 The system boots (from a floppy, then mounts root and /usr seperately over
 nfs), and I can login and work from a text console. The xdm login appears,
 but when I log in, something goes wrong. Sometimes I am logged right back
 out (auth.log shows pam_unix logging me in and out within a few seconds,
 and I can't find any log messages in between). Sometimes gnome begins to
 load, but then it dies with a message that x-session-manager crashed.
 Graphical login works fine on the system that I used as a template, and I
 have only made trivial changes to /etc (hostname, fstab). Is there someone
 out (perhaps with diskless X experience) who can give me a hint on how I
 need to change the gnome or X or sawfish configuration to work disklessly?

Sounds like the user's home directory or /tmp is not writable. 

 The fact that the behaviour is not entirely reproducable also makes me 
 suspect that running without swap might be a problem. Memory shouldn't be a 
 problem -- this machine has 1 GB and I'm barely working it -- but is there 
 some stuff one needs swap for anyway? Is there perhaps some kernel compile 
 flag that disables swap attempts completely?

Perhaps, but I doubt it.

-- 
Henry House
The attached file is a digital signature. See http://romana.hajhouse.org/pgp
for information.  My OpenPGP key: http://romana.hajhouse.org/hajhouse.asc.


pgp5oduBlL7kv.pgp
Description: PGP signature


nVidia and X problems

2002-01-18 Thread David Wright

I am using an AGP nVidia GeForce2 MX video card and am experiencing video 
problems. The screen, even in text mode, shows lots of flickering, horizontal 
lines.

The monitor is a 1600 x 1200 19 LCD; I can plug it into another machine and 
the image is beautiful, so I don't think the problem is in the monitor.

I have two new machines which each have this card, and both show this 
behaviour, so I don't think the problem is in the video card.

I suspect it is a driver problem. When I do lsmod, I see
af_packet
3c59x
rtc
unix
ide-disk
ide-probe-mod
ide-mod
ext2
no video card driver! My ATI radeon system at home shows
radeon
agpart
So could it be that I am using some generic driver and need to use the right 
one?

I don't need top 3D performance, so I would prefer not have have to deal with 
nVidia's closed-source drivers -- isn't there also an open-source driver from 
XFee86-4? (nv?) And shouldn't the kernel load agpart to use the AGP slot? How 
do I get it to do this stuff?

I have seen this with both testing and unstable.

Also, once I get proper video output, how do I configure a default window 
manager and gnome desktop for all users?

Thanks!



Re: nVidia and X problems

2002-01-18 Thread Benjamin Sommerfeld
On Fri, 18 Jan 2002, David Wright wrote:

 
 I am using an AGP nVidia GeForce2 MX video card and am experiencing video 
 problems. The screen, even in text mode, shows lots of flickering, horizontal 
 lines.
 
 The monitor is a 1600 x 1200 19 LCD; I can plug it into another machine and 
 the image is beautiful, so I don't think the problem is in the monitor.
 
 I have two new machines which each have this card, and both show this 
 behaviour, so I don't think the problem is in the video card.
 
 I suspect it is a driver problem. When I do lsmod, I see
   af_packet
   3c59x
   rtc
   unix
   ide-disk
   ide-probe-mod
   ide-mod
   ext2
 no video card driver! My ATI radeon system at home shows
   radeon
   agpart
 So could it be that I am using some generic driver and need to use the right 
 one?
 
 I don't need top 3D performance, so I would prefer not have have to deal with 
 nVidia's closed-source drivers -- isn't there also an open-source driver from 
 XFee86-4? (nv?) And shouldn't the kernel load agpart to use the AGP slot? 
 How do I get it to do this stuff?

I would suggest using the NVidia Drivers from the NVidia page. Although 
they are closed they really work well for me and kick your video 
acceleration to the limit! If you want to watch a movie in fullscreen mode 
for example you could get a problem with the xfree driver sometimes. 

the installation of these drivers is really no problem. just read the 
Readme form their homepage. 
default window-manager: look at the links 
/etc/alternatives/x-window-manager and /etc/alternatives/x-session-manager
they point to your default window managers. i think if you set the 
x-session-manager to gnome for instance, it should work for every user
use the commmand ln -s, if you want to make gnome your default for 
instance: ln -s /usr/bin/gnome-session /etc/alternatives/x-session-manager , 
before that you have to delete the 
old link of course. rm /etc/alternatives/x-session-manager 

 
 I have seen this with both testing and unstable.
 
 Also, once I get proper video output, how do I configure a default window 
 manager and gnome desktop for all users?
 
 Thanks!
 
 
 

-- 



Re: nVidia and X problems

2002-01-18 Thread Xavier Hubin
On Friday 18 January 2002 11:45, David Wright wrote:
 I am using an AGP nVidia GeForce2 MX video card and am experiencing video
 problems. The screen, even in text mode, shows lots of flickering,
 horizontal lines.

 The monitor is a 1600 x 1200 19 LCD; I can plug it into another machine
 and the image is beautiful, so I don't think the problem is in the monitor.

 I have two new machines which each have this card, and both show this
 behaviour, so I don't think the problem is in the video card.


I have also a AGP nVidia GeForce2 MX video card but i'm using the nVidia's 
closed-source drivers which works fine.

I experienced also flickering but i fixed it by updating manually in the 
XF86config-4 file the refrech rate given in my monitor documentation.
Be carfull with that! Be sure to put value given in your monito doc!!




 So could it be that I am using some generic driver and need to use the
 right one?

 I don't need top 3D performance, so I would prefer not have have to deal
 with nVidia's closed-source drivers -- isn't there also an 
open-source
 driver from XFee86-4? (nv?) And shouldn't the kernel load agpart to use
 the AGP slot? How do I get it to do this stuff?



i never succeeded to use the nv driver
 Thanks!

np



-- 
Xavier Hubin DMV
Faculty of Veterinary Medicine
Departement of Genetics
20 Bd de Colonster Bat. B43
4000  Liege, BELGIUM
e-mail: [EMAIL PROTECTED]



Re: nVidia and X problems

2002-01-18 Thread Paul 'Baloo' Johnson
On Fri, 18 Jan 2002, David Wright wrote:

 I don't need top 3D performance, so I would prefer not have have to
 deal with nVidia's closed-source drivers -- isn't there also an
 open-source driver from XFee86-4? (nv?) And shouldn't the kernel
 load agpart to use the AGP slot? How do I get it to do this stuff?

You get nVidia's drivers with the source and compile it yourself from
thier site.  The licence is strange and definately qualifies as
non-free.  This shouldn't be much of a problem unless you follow
perfectly in RMS's footsteps.

 Also, once I get proper video output, how do I configure a default
 window manager and gnome desktop for all users?

Install them.  I believe it'll prompt if you want to make it the
default.

You might also want to check your line wraps and crank them down to 72
columns, it appears your line wraps are not turned on right now...

-- 
Baloo



Re: nVidia and X problems

2002-01-18 Thread Paul 'Baloo' Johnson
On Fri, 18 Jan 2002, Xavier Hubin wrote:

 I experienced also flickering but i fixed it by updating manually in the
 XF86config-4 file the refrech rate given in my monitor documentation.
 Be carfull with that! Be sure to put value given in your monito doc!!

If they're not printed on the monitor, I *strongly recommend* checking
your monitor documentation if you still have it or going to
http://www.monitorworld.com/ and looking it up.  Write your refresh
rates, maximum resolution and color depth on the top or back of the
monitor in magic-marker.  This makes it much, much easier if you need to
reinstall X or for the next owner if you sell the monitor.

 i never succeeded to use the nv driver

I did, once, but it was fairly craptastic.  nVidia and XFree86, Inc
really need to team up on this one.  XF86 I'm sure has someone dying to
write decent drivers for nv, and nv's just sitting on the information
necissary for them to get it done right...

-- 
Baloo



Re: nVidia and X problems

2002-01-18 Thread Vaclav Hula
Hi,
On Fri, Jan 18, 2002 at 12:25:00PM +0100, Benjamin Sommerfeld wrote:
 the installation of these drivers is really no problem. just read the 
 Readme form their homepage. 
 default window-manager: look at the links 
 /etc/alternatives/x-window-manager and /etc/alternatives/x-session-manager
 they point to your default window managers. i think if you set the 
 x-session-manager to gnome for instance, it should work for every user
 use the commmand ln -s, if you want to make gnome your default for 
 instance: ln -s /usr/bin/gnome-session /etc/alternatives/x-session-manager 
 , before that you have to delete the 
 old link of course. rm /etc/alternatives/x-session-manager 

No. update-alternatives --config x-session-manager is correct way to
deal with alternatives.

Ax
-- 
/usr/lib/xscreensaver/attraction -root -glow -mouse -points 5 -threshold 200 \
-mode balls -size 20 -viscosity 0.99 -correct-bounce



Re: nVidia and X problems

2002-01-18 Thread Martin Atukunda
On Friday 18 January 2002 14:25, Benjamin Sommerfeld proclaimed:

 default window-manager: look at the links
 /etc/alternatives/x-window-manager and /etc/alternatives/x-session-manager
 they point to your default window managers. i think if you set the
 x-session-manager to gnome for instance, it should work for every user
 use the commmand ln -s, if you want to make gnome your default for
 instance: ln -s /usr/bin/gnome-session
 /etc/alternatives/x-session-manager , before that you have to delete the
 old link of course. rm /etc/alternatives/x-session-manager
much better to use the command update-alternatives

M.
-- 
Everybody has been saying that Linux is over because the dot-com boom is
over. But Linux predates the dot-com hype, said Jacques le Marois,
president of French Linux distributor MandrakeSoft.



Re: X problems

2001-10-14 Thread Ionel Mugurel Ciobîcă
On 12-10-2001, at 08h 27'18, Kurt Lieber wrote:
 I had a similar problem -- check to make sure you aren't also running gpm 
 (General Purpose Mouse interfaces)  It doesn't always play nicely with X.  
 
I know, it was the first think I checked. After that I looked at
IRQ. Everything seams fine. But it is not working.

Ionel



X problems

2001-10-12 Thread Ionel Mugurel Ciobîcă
I have a problem with the X server.

I have a new PC, with P IV on a Intel 850 chip set
with a PS2 mouse and keyboard.

I run Xfree 4.1.0.1-3 and kernel 2.4.10ac12.

My problem is that I can't use the mouse and sometime the
keyboard. The error is not reproducible. By simply restarting
X I can have a different behavior.

A kernel 2.2.x is not OK, the PS2 mouse is not detected at all.
The motherboard is too new.


Is someone using Debian on such computer? Do you had problems?
I would like to have any suggestions.


Ionel



Re: X problems

2001-10-12 Thread Kurt Lieber
I had a similar problem -- check to make sure you aren't also running gpm 
(General Purpose Mouse interfaces)  It doesn't always play nicely with X.  

You can check if gpm is started by doing 'ps ax |grep gpm'

hth

--kurt

 My problem is that I can't use the mouse and sometime the
 keyboard. The error is not reproducible. By simply restarting
 X I can have a different behavior.



Re: Emacs/X problems...

2001-09-01 Thread Joel Mayes
 Aaron == Aaron Traas [EMAIL PROTECTED] writes:

Aaron When I start emacs, using my trusty old .emacs file I've
Aaron been keeping and maintaining for years, The colors I've
Aaron selected aren't quite working right. Basically, I set the
Aaron background color to black, and that works, except or where
Aaron there's text. Each character taken up by something other
Aaron than whitespace has a white background. I've determined
Aaron it's something to do with X, as the same .emacs file works
Aaron beautifully when I export the display to my Solaris box.


G'day Aaron,

Are you using (set-face-... 'default ...) to set the colours?

I had the same problem with Emacs and fixed it by using
(set-(back|fore)ground-color) to my .emacs
-- 
Joel



Emacs/X problems...

2001-08-31 Thread Aaron Traas
I'm using Woody/testing, and XFree86 4.x. I'm using emacsen flavor of
Emacs20. 

When I start emacs, using my trusty old .emacs file I've been keeping
and maintaining for years, The colors I've selected aren't quite working
right. Basically, I set the background color to black, and that works,
except or where there's text. Each character taken up by something other
than whitespace has a white background. I've determined it's something
to do with X, as the same .emacs file works beautifully when I export
the display to my Solaris box. 

Does anyone know how to either:
A) Have emacs override X's configuration
-or-
B) What *global* file I'm supposed to edit to make X behave nicely?

Thanks!

--Aaron Traas



Re: Emacs/X problems...

2001-08-31 Thread Daniel Katz
 Aaron == Aaron Traas [EMAIL PROTECTED] writes:

Aaron I'm using Woody/testing, and XFree86 4.x. I'm using emacsen
Aaron flavor of Emacs20.

Aaron Basically, I set the background color to black, and that works,
Aaron except or where there's text. Each character taken up by
Aaron something other than whitespace has a white background.


Are you running KDE?  I saw behavior like this under KDE until I unset
the Apply fonts and colors to non-KDE apps checkbox in the control
center.  On my system, it's in the ControlCenter-LookFeel-Style
frame.  I run KDE 2.2, when I run KDE.  :-)

Dan



Re: Emacs/X problems...

2001-08-31 Thread Aaron Traas
Yes, I am running KDE 2.1.1, and that was the problem! Everything works
now. I did have to restart X to get this to work, however...

Thanks for your help!!

--Aaron

Daniel Katz wrote:
 
  Aaron == Aaron Traas [EMAIL PROTECTED] writes:
 
 Aaron I'm using Woody/testing, and XFree86 4.x. I'm using emacsen
 Aaron flavor of Emacs20.
 
 Aaron Basically, I set the background color to black, and that works,
 Aaron except or where there's text. Each character taken up by
 Aaron something other than whitespace has a white background.
 
 Are you running KDE?  I saw behavior like this under KDE until I unset
 the Apply fonts and colors to non-KDE apps checkbox in the control
 center.  On my system, it's in the ControlCenter-LookFeel-Style
 frame.  I run KDE 2.2, when I run KDE.  :-)



X Problems

2001-08-03 Thread David Tansey

I can't figure out just what package is causing this problem.

I noticed it first when i got branden's 4.1.0-pre5 X packages and
installed them. every once and a while the screen would just freeze. if
I Ctrl-Alt-F1 to a console and then return to the F7 (X) terminal it is
back to normal. After a few times of this (with the pre5 packages) X
would hard freeze the computer. After having that happen about twice
I just forced the removal of all the 4.1.0 packages i could find from
dpkg -l | grep 4.1.0-pre5 and reinstalled 4.0.3 from the unstable
repository. that worked wonderfully.

no i have the same problem with the unstable 4.1.0 debs! it has not hard

frozen on me. but it seems that the times when i have to switch to
console become more frequent as time goes on. and then the display just
showed a bunch of horizontal lines. (pinkish brown) and i could get to
my console, but that was also cursed by lines (blue).

So i wrote this email.

What can I do, and what package can i send a bug report on?

Thanks,
David

P.S.

I run a voodoo banshee (tdfx) card





Mouse and X problems

2001-05-28 Thread james
Hello 

I am trying to to install Debian GNU/Linux 2.2 rev 2 non US on to Compaq 
Professional Workstation 5000 (system outline below).

So far I have managed to successfully install the basic Debian system. But I 
need to recompile the kernel to take advantage the systemy?s dual processors on 
trying to do this I discovered that ?make? and ?xconfig? had not been installed.

I try to fix this by using ?tasksel -s? to upgrade the basic Debian system to a 
standard system (ok I admit it I dony?t want to spend time trawling through 
?dselect? looking for the right packages). During the install process I was 
given a number of new mouse options to choose from. I probably got this badly 
wrong because it seems to have led to the following problems:

Mouse problem-
On rebooting mouse cursor is now either stationary in the middle of the screen 
or shoots uncontrollably all over the screen with the slightest movement of the 
mouse.

Cany?t get ?man? pages-
Using the keyboard I managed to get an ?xterm? up but was unable to display any 
?man? pages the error message was ?man: can?t create a temporary filename: 
Permission denied? at the time I was logged in as root.

X became very unstable-
If I tried to run ?mc?, ?gmc? or ?xmseconfig? X would hang.

General X question-
Is there any method in which you can reboot a system with out it automatically 
booting X?

I would be very grateful if any one could give me a suggestion as to what to do 
next. 

Look forward to receiving any helpful pointers. 

James 

System Outline: 

Compaq Professional Workstation 5000

CPU
Processor- Intel Pentium Pro 
Number (SMP)- 2
Speed (Mhz)- 150

RAM
Quantity (MB)- 130.228
Type- 60-ns DIMMs (EDO) (ECC)

Buses
PCI slots- 3
ISA slots- 1
Combination slots PCI/ISA- 1

Hand Drives
Number- 2
Type- SCSI
Size (GB)- 1.91 (each)

CD-ROM
Type- SCSI
Manufacturer/Model- Hitachi CDR-7930

Mouse
Type- PS/2
Manufacturer/Model- Microsoft Wheel Mouse 
Buttons- 2 + wheel button

Video
Video Card- 3dfx Voodoo 3
RAM (MB)- 16


James Aitken
W: +44 (0) 20 8547 0470
H: +44 (0) 1322 404582
M: +44 (0) 7768 057306
E: [EMAIL PROTECTED]

-

Be passionate about your email
Just click here: http://another.com



Re: Mouse and X problems

2001-05-28 Thread ktb
On Mon, May 28, 2001 at 11:24:36AM +0100, [EMAIL PROTECTED] wrote:
 Hello 
 
 I am trying to to install Debian GNU/Linux 2.2 rev 2 non US on to Compaq 
 Professional Workstation 5000 (system outline below).
 
 So far I have managed to successfully install the basic Debian system. But I 
 need to recompile the kernel to take advantage the systemy?s dual processors 
 on trying to do this I discovered that ?make? and ?xconfig? had not been 
 installed.
 
 I try to fix this by using ?tasksel -s? to upgrade the basic Debian system to 
 a standard system (ok I admit it I dony?t want to spend time trawling through 
 ?dselect? looking for the right packages). During the install process I was 
 given a number of new mouse options to choose from. I probably got this badly 
 wrong because it seems to have led to the following problems:


Learn to use apt-get.  Make sure your /etc/atp/sources.list is pointed
in the direction you want and -
# apt-get install package_name

If you run into a situation where you don't know what package a program
is in use the web-site http://www.debian.org/distrib/packages

 Mouse problem-
 On rebooting mouse cursor is now either stationary in the middle of the 
 screen or shoots uncontrollably all over the screen with the slightest 
 movement of the mouse.
 

Switch to console ctrl+alt+F2 and kill gpm
# /etc/init.d/gpm stop

There is a known issue between gpm and X.  Some people have had some
success with running both.  Check the archives at the web-site or 
http://www.geocrawler.com/lists/3/Debian-Linux/199/0/
for more on that.

 Cany?t get ?man? pages-
 Using the keyboard I managed to get an ?xterm? up but was unable to display 
 any ?man? pages the error message was ?man: can?t create a temporary 
 filename: Permission denied? at the time I was logged in as root.


I took a quick look in the archives.  Try viewing them as a regular
user.  This might help to fix your 'viewing as root' -
http://www.geocrawler.com/archives/3/199/2000/5/0/3785023/

 X became very unstable-
 If I tried to run ?mc?, ?gmc? or ?xmseconfig? X would hang.
 
 General X question-
 Is there any method in which you can reboot a system with out it 
 automatically booting X?
 

Yes you are probably running xdm.  You can remove the package
# apt-get remove xdm
or
# /etc/init.d/xdm stop
Then use startx to start X.
kent

-- 
 From seeing and seeing the seeing has become so exhausted
 First line of The Panther - R. M. Rilke




X problems

2001-05-18 Thread harsha
hi,
   i was using a potato system. i did a dist-upgrade to woody. the upgrade went 
without a hitch but for X. some packages were of version 3.3.6-18. i tried 
removing 3.3.6-18 but said dependency problems. 

I have Riva TNT2 ULTRA card. downloaded the binary drivers from nvidia and 
installed them. 

i am a newbie so didn't know i how it is quite worked. so assumed that i could 
safely remove xserver-svga. but that left me with out X. i am not quite clear 
on how to solve this. 

another thing i found when i tried to run mplayer -vo xv it says that XVideo 
definton missing. could someone give me links as to what this is all about. i 
wanted to use xine. but for a fs mode one needs Xv. 

how can i get this working,

thanks is advance,
regards
harsha


-- 



Re: X problems

2001-05-18 Thread Jeffrin

Hello
 
 You can try this ...
   
 1. Add  deb http.us.debian.org/debian sid main  to your 
/etc/sources.list 2. apt-get update
 3. apt-get install xserver-xfree86
 4. Download nvidia's driver sources ( NVIDIA_GLX-0.9-769.tar.gz
  and NVIDIA_kernel-0.9-769.tar.gz ) and install the driver.
 5.Configure your card using the tool named xf86config

Changes to make in /etc/XF86config-4 

 6.Replace nv with nvidia in the Device section 
 7.In the Module section you  should have  Load glx  and should
   not have Load dri  Load GLcore

 8. Make sure you have a symlink named X in /etc/X11 pointed
   to /usr/X11R6/bin/XFree86


 
-Jeffrin

 
 



Re: X problems

2001-05-18 Thread Steve Gran
On Fri, 18 May 2001, harsha wrote:

 
 hi,
i was using a potato system. i did a dist-upgrade to woody. the upgrade 
 went without a hitch but for X. some packages were of version 3.3.6-18. i 
 tried removing 3.3.6-18 but said dependency problems. 
 
 I have Riva TNT2 ULTRA card. downloaded the binary drivers from nvidia and 
 installed them. 
 
 i am a newbie so didn't know i how it is quite worked. so assumed that i 
 could safely remove xserver-svga. but that left me with out X. i am not quite 
 clear on how to solve this. 
 
 another thing i found when i tried to run mplayer -vo xv it says that XVideo 
 definton missing. could someone give me links as to what this is all about. i 
 wanted to use xine. but for a fs mode one needs Xv. 
 
 how can i get this working,
 
 thanks is advance,
 regards
 harsha


The xserver thing is an upgrade problem - they went to v 4.x with Woody, and it 
uses some slightly different files.  dpkg -l  packages.list will give you a 
list of all your installed packages.  dpkg -r or apt-get remove all the x 
pavkages that are version 3.x, and rerun xf86config - this will give you a 
working config file and should let you run your xserver normally.  I'm not sure 
about your card, but I'm fairly sure that the drivers for it are supported 
directly by the newer kernels, and I'm also fairly sure that it's supported by 
the new version of X.

Good luck,
Steve




X Problems with newly added user

2001-04-13 Thread Stephen E. Hargrove
I've just added a new user to my system, and she can't fire up X.  When
she enters startx, it creates .Xauthority, and then craps out with

_IceTransSocketCreateListener: failed to bind listener
_IceTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_IceTransMakeAllCOTServerListeners: failed to create listener for local

** WARNING ** Cannot establish any listening sockets

I've read through several posts by searching goole.com and several man
pages on xauth, Xsecurity, xhosts, etc., but can't seem to get anywhere.
(As a side note, her DISPLAY environment variable isn't getting set
either.)

I need to get her up rather quickly, so any advice or pointers (or better
yet, solutions :) will be most welcome.

-- 
steve
*
Linux : http://exitwound.org
Mozart: http://mozart.sourceforge.net
Buck  : http://www.BuckOwensFan.com
*




X Problems

2001-03-29 Thread David Densmore
I installed a bunch of packages from sid because I wanted to run
gnapster-gtk 1.4.2-0.1.  I managed to get all of the packages installed
and configured, including Gnapster, but I broke X in the process.  When
I try to start X I get this message:

X: /etc/X11/X points back to X wrapper executable, aborting.

I also noticed that the package xserver-svga 3.3.6-38 is half configured
with the flags iF when I run dpkg -l.  I tried to configure it using
dpkg --configure xserver-svga and got this:

dpkg: error processing xserver-svga (--configure):
 subprocess post-installation script returned error exit status 10
Errors were encountered while processing:
 xserver-svga

Then I tried to remove it, then purge it and got the same message.
I can't get rid of it!

So my questions are why won't X start?  Why can't I remove the xserver-svga
package?  Are they the same problem or two different problems?  And how do
I fix this mess?

Is it because sid destroys things?  Is it wise to name a version after sid?

Thanks,
David



  1   2   >