CUPS client problem

2006-11-30 Thread Nicolas de Sereville

Hello,

I have a new laptop (Dell D620, with etch freshly installed) from my new 
job and I am trying to print using CUPS. The situation is the following, 
at work there are two different networks: xxx.xxx.10.xxx (let's call it 
'internal') and xxx.xxx.20.xxx (let's call it 'external'). The cups 
print server is a machine on the internal network and my laptop is 
connected on the external network. I am not seeing any printers whereas 
when my laptop was on the internal network CUPS could detect 
automatically all the available printers. Do you have any idea of what I 
am missing?


I tried to add the name of the CUPS server in /etc/cups/client.conf but 
then when I go to "Desktop/Administration/Printings" I obtain the 
message: "The CUPS server could not be contacted"


Any help would be welcomed,
Cheers,
Nicolas


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




Re: [SOLVED] Re: permissions with udev/pmount?

2004-12-29 Thread Nicolas de Sereville
Hi,
Andrea Vettorello wrote:
On Wed, 29 Dec 2004 11:05:11 +0100, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

Hi,
Thank you to H.S. and Andrea! It is now working. The point is that while
trying to understand my problem I erased me from the "hal" group. After
adding me back to this group, everything is working smooth ;-) When I
plug in my stick, my archos or my camera the icon is automatically
appearing on the desktop.
Here are some informations of my configuration if it can help somebody else:
1) I belong to the "plugdev" and "hal" group
2) I have installed:
dpkg -l hal '*dbus*' 'gnome-vol*' hotplug pmount | grep ^ii
ii  hal0.4.2-5Hardware Abstraction Layer
ii  dbus-1 0.22-3 simple interprocess messaging system
ii  dbus-glib-10.22-3 simple interprocess messaging system
(GLib-b
ii  python2.3-dbus 0.22-3 simple interprocess messaging system
(Python
ii  gnome-volume-m 1.1.2-5GNOME daemon to auto-mount and manage
media
ii  hotplug0.0.20040329-1 Linux Hotplug Scripts
ii  pmount 0.4.4-1mount removable devices as normal user
3) In gnome-volume-properties, I set the three following options:
"Mount removable drives when hot plugged"
"Mount removable media when inserted"
"Browse removable media when inserted"
4) udev rule for my camera:
BUS="scsi", KERNEL="sd*", SYSFS{vendor}="PENTAX  ",
SYSFS{model}="DIGITAL_CAMERA  ", NAME="gyp-ca-%k",
SYMLINK="gyp-ca-usb%n", MODE="0660", GROUP="hal"
5) /etc/fstab line for my camera
/dev/gyp-ca-usb1/media/camara   autorw,user,noauto,sync
0  0
6) /media/camera has been created before by hand
Thanks again for your useful help!
Nico
   

There's a typo in your /etc/fstab (/media/camara instead of
/media/camera), 

you're right, I mixed english (camera) and spanish (camara)
and i'm not sure you need to be in the hal group to
get gnome-volume-manager working...
 

you are also right, I erased me from the "hal" group and it is working 
smoothly.

Thanks for pointing out that to me,
Nico

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



[SOLVED] Re: permissions with udev/pmount?

2004-12-29 Thread Nicolas de Sereville
Hi,
Thank you to H.S. and Andrea! It is now working. The point is that while 
trying to understand my problem I erased me from the "hal" group. After 
adding me back to this group, everything is working smooth ;-) When I 
plug in my stick, my archos or my camera the icon is automatically 
appearing on the desktop.

Here are some informations of my configuration if it can help somebody else:
1) I belong to the "plugdev" and "hal" group
2) I have installed:
dpkg -l hal '*dbus*' 'gnome-vol*' hotplug pmount | grep ^ii
ii  hal0.4.2-5Hardware Abstraction Layer
ii  dbus-1 0.22-3 simple interprocess messaging system
ii  dbus-glib-10.22-3 simple interprocess messaging system 
(GLib-b
ii  python2.3-dbus 0.22-3 simple interprocess messaging system 
(Python
ii  gnome-volume-m 1.1.2-5GNOME daemon to auto-mount and manage 
media
ii  hotplug0.0.20040329-1 Linux Hotplug Scripts
ii  pmount 0.4.4-1mount removable devices as normal user

3) In gnome-volume-properties, I set the three following options:
"Mount removable drives when hot plugged"
"Mount removable media when inserted"
"Browse removable media when inserted"
4) udev rule for my camera:
BUS="scsi", KERNEL="sd*", SYSFS{vendor}="PENTAX  ", 
SYSFS{model}="DIGITAL_CAMERA  ", NAME="gyp-ca-%k", 
SYMLINK="gyp-ca-usb%n", MODE="0660", GROUP="hal"

5) /etc/fstab line for my camera
/dev/gyp-ca-usb1/media/camara   autorw,user,noauto,sync 
0  0

6) /media/camera has been created before by hand
Thanks again for your useful help!
Nico
H. S. wrote:
Apparently, _Nicolas de Sereville_, on 28/12/04 08:33,typed:
I installed the kernel 2.6.9 through "apt-get install 
kernel-image-2.6.9-1-k7", but nothing is changing. When I plug in my 
stick and camera, the devices nodes are created in /dev but the 
devices are not mounted, neither as a user nor as root (which used to 
work a few days ago!). I don't remember having changed anything apart 
from upgrading the system.

The versions of some packages are given here:
ii  dbus-1 0.22-3 simple interprocess messaging system
ii  udev   0.050-2/dev/ management daemon
ii  hotplug0.0.20040329-1 Linux Hotplug Scripts
ii  hal0.4.2-5Hardware Abstraction Layer
ii  gnome-volume-m 1.1.2-5GNOME daemon to auto-mount and 
manage media

Reading the man pages of pmount it seems that a few conditions should 
be verified, which I think is the case:
The mount will succeed if all of the following conditions are met:

-  is a block device in /dev/
-  is not handled by /etc/fstab (if it is, pmount calls
 '/bin/mount ' to handle this transparently; supplying a 
label is not
 allowed in this case)
-  is not already mounted according to /etc/mtab and 
/proc/mounts
- if the mount point already exists, there is no device already 
mounted at it
 and the directory is empty
-  is removable (i. e. on USB or FireWire bus, or
 /sys/block/drive/removable == 1)
-  is not locked (see below)

However when I use pmount in a terminal as a normal user ("pmount"), 
it tells me:
zsh: permission denied: pmount.

Can someone having udev/hal/hotplug/gnome-volume-manager running 
check the permission of the pmount file. I have:
-rwSr--r--  1 root plugdev 22K 2004-12-16 19:24 /usr/bin/pmount

I tried to make executable this file for everybody and then I can 
pmount manually the device (pmount /dev/gyp-cl-usb /stick) but it 
doesn't work automatically when I insert my stick.

Well as you can see I am stuck, so any ideas are welcomed!
Nico


Hi,
Sorry I couldn't reply earlier, been a but visiting people over the 
holidyas :)

Regarding your USB icon problem, I would suggest you check
1) You are 'hal' and 'plugdev' group member.
2) you have installed:
$> COLUMMNS=150 dpkg -l hal *dbus* gnome-vol* hotplug pmount | grep ^ii
ii  hal0.4.2-2Hardware Abstraction Layer
ii  dbus-1 0.22-3 simple interprocess messaging system
ii  dbus-glib-10.22-3 simple interprocess messaging system 
(GLib-b
ii  python2.3-dbus 0.22-3 simple interprocess messaging system 
(Python
ii  gnome-volume-m 1.1.2-4GNOME daemon to auto-mount and 
manage media
ii  hotplug0.0.20040329-1 Linux Hotplug Scripts
ii  pmount 0.4.3-1mount removable devices as normal user

3) that log messages appear in /var/log/syslog since the time you plug 
in the USB stick till you plug it out. Why don't you list them here?

4) that you have options set to mount removable devices when plugged 
in or inserted:
$> gnome-volume-properties

Other than that, I guess there is a bug at present in pmount which 
will delete your mount pont in /media when you unplug your USB stick. 
There is a bug report about this. It is #286936 in http://debian.org/Bugs

GL,
->HS


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



Re: permissions with udev/pmount?

2004-12-28 Thread Nicolas de Sereville

Andrea Vettorello wrote:
On Tue, 28 Dec 2004 15:46:34 +0100, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

   

[...]
 

Hi, thank you for your help,
I reinstalled the "pmount", "gnome-volume-manager" and
"gnome-desktop-environement" packages. Now I have:
ls -l /usr/bin/pmount
-rwsr-xr--  1 root plugdev 22K 2004-12-16 19:24 /usr/bin/pmount*
But the icon of my stick is still not appearing when I plug it in.
However I can pmount it manually with:
pmount /dev/gyp-cl-usb /stick
with the following warning:
Warning: device /dev/gyp-cl-usb is already handled by /etc/fstab,
supplied label is ignored
The devices nodes are well created and the permissions are the following:
ls -l /dev/gyp*
brw-rw  1 root hal  8, 0 2004-12-28 15:35 /dev/gyp-cl-sda
lrwxrwxrwx  1 root root   10 2004-12-28 15:35 /dev/gyp-cl-usb -> gyp-cl-sda
Am I missing something? Which logs can I check to see what's wrong with
pmount? Is it a problem of the gnome-volume-manager?
   

Do you have all the needed packages ("udev" "hal" "fam" etc.)? Also,
look in /etc/udev/rules.d for a symlink to /etc/udev/hal.rules...
Andrea
 

I reinstalled the "udev" and "hal" packages and I have the "fam" package:
ii  fam2.7.0-6File Alteration Monitor
It doesn't change anything, the icons still don't appear :-(
Also,
ls -l /etc/udev/rules.d
total 1,0K
lrwxrwxrwx  1 root root  19 2004-12-28 17:02 cd-aliases.rules -> 
../cd-aliases.rules
-rw-r--r--  1 root root 843 2004-12-26 00:14 gyp_udev.rules
lrwxrwxrwx  1 root root  13 2004-12-28 17:02 udev.rules -> ../udev.rules
lrwxrwxrwx  1 root root  12 2004-12-28 17:02 z_hal-plugdev.rules -> 
../hal.rules

But now I manage to get automatically an icon for my camera and stick 
when I start an Xsession as root! :-) So I guess I have a problem of 
groups or permission.

Any ideas of what I can further check?
Now I will make a detail comparison of the logs when I am root or not.
Thank you,
Nico

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



Re: permissions with udev/pmount?

2004-12-28 Thread Nicolas de Sereville

Andrea Vettorello wrote:
On Tue, 28 Dec 2004 14:33:56 +0100, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

Hi,
H. S. wrote:
   

Apparently, _Nicolas de Sereville_, on 24/12/04 05:13,typed:
 

[...]
 

However when I use pmount in a terminal as a normal user ("pmount"), it
tells me:
zsh: permission denied: pmount.
Can someone having udev/hal/hotplug/gnome-volume-manager running check
the permission of the pmount file. I have:
-rwSr--r--  1 root plugdev 22K 2004-12-16 19:24 /usr/bin/pmount
I tried to make executable this file for everybody and then I can pmount
manually the device (pmount /dev/gyp-cl-usb /stick) but it doesn't work
automatically when I insert my stick.
Well as you can see I am stuck, so any ideas are welcomed!
Nico
   

ls -l /usr/bin/pmount
-rwsr-xr--  1 root plugdev 22520 2004-12-16 19:24 /usr/bin/pmount*
Try reinstalling the "pmount" package, your permissions are strange,
missing execution bit...
Andrea
 

Hi, thank you for your help,
I reinstalled the "pmount", "gnome-volume-manager" and 
"gnome-desktop-environement" packages. Now I have:
ls -l /usr/bin/pmount
-rwsr-xr--  1 root plugdev 22K 2004-12-16 19:24 /usr/bin/pmount*

But the icon of my stick is still not appearing when I plug it in. 
However I can pmount it manually with:
pmount /dev/gyp-cl-usb /stick
with the following warning:
Warning: device /dev/gyp-cl-usb is already handled by /etc/fstab, 
supplied label is ignored

The devices nodes are well created and the permissions are the following:
ls -l /dev/gyp*
brw-rw  1 root hal  8, 0 2004-12-28 15:35 /dev/gyp-cl-sda
lrwxrwxrwx  1 root root   10 2004-12-28 15:35 /dev/gyp-cl-usb -> gyp-cl-sda
Am I missing something? Which logs can I check to see what's wrong with 
pmount? Is it a problem of the gnome-volume-manager?

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



Re: permissions with udev/pmount?

2004-12-28 Thread Nicolas de Sereville
Hi,
H. S. wrote:
Apparently, _Nicolas de Sereville_, on 24/12/04 05:13,typed:
Hi list,
I have the following problem using debian sid (kernel 2.6.8-1). I am 
trying to get an icon automatically when I plug in my usb stick or 
camera. I use udev / hal / gnome-volume-manager. As a normal user the 
links in /dev are created following the udev rules file, but the 
device is not mounted (pmount problem?) and hence doesn't appear on 
my desktop.

Starting a X session as root, everything is working correctly. My usb 
stick and camera are detected, mounted and a nice icon appears on the 
desktop.

So I guess I have a problem of permissions or groups for a normal 
user but I cannot figure out what? Following a few recent threads 
concerning this topic in the archives I made me member of the 
"plugdev" and "hal" (necessary?) group, and the device node in /dev 
are created in the "hal" group.

Any help will be very apreciated!
Nico
A few technical information:
1- udev rules for my usb stick:
   BUS="usb", KERNEL="sd*", SYSFS{product}="USB Mass Storage Device", 
NAME="gyp-cl-%k", SYMLINK="gyp-cl-usb%n", MODE="0660", GROUP="hal"

2- /etc/fstab information:
   /dev/gyp-cl-usb /media/stickautorw,user,noauto,sync 
0   0

I was having a similar problem and filed a bug report (I was using 
Sarge and kernel 2.6.9). You can find the complete bug reports on 
http://www.debian.org/Bugs/ by find a bug with the number 286579.

In Sid, using kernel 2.6.9 (2.6.9-1-686-smp to be more precise), I can 
see the icon when I insert a USB stick in Inspiron 5160 Dell laptop. I 
would suggest try this new version of the kernel.
I installed the kernel 2.6.9 through "apt-get install 
kernel-image-2.6.9-1-k7", but nothing is changing. When I plug in my 
stick and camera, the devices nodes are created in /dev but the devices 
are not mounted, neither as a user nor as root (which used to work a few 
days ago!). I don't remember having changed anything apart from 
upgrading the system.

The versions of some packages are given here:
ii  dbus-1 0.22-3 simple interprocess messaging system
ii  udev   0.050-2/dev/ management daemon
ii  hotplug0.0.20040329-1 Linux Hotplug Scripts
ii  hal0.4.2-5Hardware Abstraction Layer
ii  gnome-volume-m 1.1.2-5GNOME daemon to auto-mount and manage 
media

Reading the man pages of pmount it seems that a few conditions should be 
verified, which I think is the case:
The mount will succeed if all of the following conditions are met:

-  is a block device in /dev/
-  is not handled by /etc/fstab (if it is, pmount calls
 '/bin/mount ' to handle this transparently; supplying a label 
is not
 allowed in this case)
-  is not already mounted according to /etc/mtab and /proc/mounts
- if the mount point already exists, there is no device already mounted 
at it
 and the directory is empty
-  is removable (i. e. on USB or FireWire bus, or
 /sys/block/drive/removable == 1)
-  is not locked (see below)

However when I use pmount in a terminal as a normal user ("pmount"), it 
tells me:
zsh: permission denied: pmount.

Can someone having udev/hal/hotplug/gnome-volume-manager running check 
the permission of the pmount file. I have:
-rwSr--r--  1 root plugdev 22K 2004-12-16 19:24 /usr/bin/pmount

I tried to make executable this file for everybody and then I can pmount 
manually the device (pmount /dev/gyp-cl-usb /stick) but it doesn't work 
automatically when I insert my stick.

Well as you can see I am stuck, so any ideas are welcomed!
Nico

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



Re: permissions with udev/pmount?

2004-12-24 Thread Nicolas de Sereville
Hi HS,
Thank you for your response and all your previous posts on this topic 
which helped me a lot!

I will hence try with a 2.6.9 kernel. However, reading all the bug 
report I didn't manage to understand if it is normal that everything 
works as the "root" user or not?

Thanks again,
Nico
H. S. wrote:
Apparently, _Nicolas de Sereville_, on 24/12/04 05:13,typed:
Hi list,
I have the following problem using debian sid (kernel 2.6.8-1). I am 
trying to get an icon automatically when I plug in my usb stick or 
camera. I use udev / hal / gnome-volume-manager. As a normal user the 
links in /dev are created following the udev rules file, but the 
device is not mounted (pmount problem?) and hence doesn't appear on 
my desktop.

Starting a X session as root, everything is working correctly. My usb 
stick and camera are detected, mounted and a nice icon appears on the 
desktop.

So I guess I have a problem of permissions or groups for a normal 
user but I cannot figure out what? Following a few recent threads 
concerning this topic in the archives I made me member of the 
"plugdev" and "hal" (necessary?) group, and the device node in /dev 
are created in the "hal" group.

Any help will be very apreciated!
Nico
A few technical information:
1- udev rules for my usb stick:
   BUS="usb", KERNEL="sd*", SYSFS{product}="USB Mass Storage Device", 
NAME="gyp-cl-%k", SYMLINK="gyp-cl-usb%n", MODE="0660", GROUP="hal"

2- /etc/fstab information:
   /dev/gyp-cl-usb /media/stickautorw,user,noauto,sync 
0   0

I was having a similar problem and filed a bug report (I was using 
Sarge and kernel 2.6.9). You can find the complete bug reports on 
http://www.debian.org/Bugs/ by find a bug with the number 286579.

In Sid, using kernel 2.6.9 (2.6.9-1-686-smp to be more precise), I can 
see the icon when I insert a USB stick in Inspiron 5160 Dell laptop. I 
would suggest try this new version of the kernel.

GL,
->HS


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



Re: permissions with udev/pmount?

2004-12-24 Thread Nicolas de Sereville
A complement of information once is inserted my usb key:
12:37 [EMAIL PROTECTED] ~% ll /dev/gyp*
brw-rw  1 root hal  8, 16 2004-12-24 12:38 /dev/gyp-cl-sdb
lrwxrwxrwx  1 root root10 2004-12-24 12:38 /dev/gyp-cl-usb -> 
gyp-cl-sdb

I hope this can help.
Nico
Nicolas de Sereville wrote:
Hi list,
I have the following problem using debian sid (kernel 2.6.8-1). I am 
trying to get an icon automatically when I plug in my usb stick or 
camera. I use udev / hal / gnome-volume-manager. As a normal user the 
links in /dev are created following the udev rules file, but the 
device is not mounted (pmount problem?) and hence doesn't appear on my 
desktop.

Starting a X session as root, everything is working correctly. My usb 
stick and camera are detected, mounted and a nice icon appears on the 
desktop.

So I guess I have a problem of permissions or groups for a normal user 
but I cannot figure out what? Following a few recent threads 
concerning this topic in the archives I made me member of the 
"plugdev" and "hal" (necessary?) group, and the device node in /dev 
are created in the "hal" group.

Any help will be very apreciated!
Nico
A few technical information:
1- udev rules for my usb stick:
   BUS="usb", KERNEL="sd*", SYSFS{product}="USB Mass Storage Device", 
NAME="gyp-cl-%k", SYMLINK="gyp-cl-usb%n", MODE="0660", GROUP="hal"

2- /etc/fstab information:
   /dev/gyp-cl-usb /media/stickautorw,user,noauto,sync 
0   0

3- installed packages:
   ii  dbus-1  0.22-3   simple 
interprocess messaging system
   ii  udev 0.048-3  /dev/ management 
daemon
   ii  hotplug0.0.20040329-1 Linux Hotplug Scripts
   ii  hal0.4.2-4   Hardware 
Abstraction Layer
   ii  gnome-volume-m 1.1.2-5  GNOME daemon to auto-mount 
and manage media



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



permissions with udev/pmount?

2004-12-24 Thread Nicolas de Sereville
Hi list,
I have the following problem using debian sid (kernel 2.6.8-1). I am 
trying to get an icon automatically when I plug in my usb stick or 
camera. I use udev / hal / gnome-volume-manager. As a normal user the 
links in /dev are created following the udev rules file, but the device 
is not mounted (pmount problem?) and hence doesn't appear on my desktop.

Starting a X session as root, everything is working correctly. My usb 
stick and camera are detected, mounted and a nice icon appears on the 
desktop.

So I guess I have a problem of permissions or groups for a normal user 
but I cannot figure out what? Following a few recent threads concerning 
this topic in the archives I made me member of the "plugdev" and "hal" 
(necessary?) group, and the device node in /dev are created in the "hal" 
group.

Any help will be very apreciated!
Nico
A few technical information:
1- udev rules for my usb stick:
   BUS="usb", KERNEL="sd*", SYSFS{product}="USB Mass Storage Device", 
NAME="gyp-cl-%k", SYMLINK="gyp-cl-usb%n", MODE="0660", GROUP="hal"

2- /etc/fstab information:
   /dev/gyp-cl-usb /media/stickautorw,user,noauto,sync 
0   0

3- installed packages:
   ii  dbus-1  0.22-3   simple interprocess 
messaging system
   ii  udev 0.048-3  /dev/ management 
daemon
   ii  hotplug0.0.20040329-1 Linux Hotplug Scripts
   ii  hal0.4.2-4   Hardware 
Abstraction Layer
   ii  gnome-volume-m 1.1.2-5  GNOME daemon to auto-mount 
and manage media

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



Re: ATI 3D acceleleration and dpkg-divert

2004-10-15 Thread Nicolas de Sereville
Hi!
Just for closing this thread. I finally got 3d acceleration and OpenGL 
working well following the installation method from
http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html. 
Celestia and Tuxracer are running smooth.

Thanks to everybody
Nico
Nicolas de Sereville wrote:
Hi!
A big thanks to everybody who spare some time helping me. I now have 
the 3D acceleration working! My error was very stupid... As suggested 
by Wim, when removing my previous installation, the "dpkg --purge 
fglrx" command left some files that I did not erased, so I had a mix 
within new and old files. Deleting the directory and compiling again 
the kernel module was just fine.
Also, I tried with two options: DRM compiled in th kernel and without 
DRM. The results are the same.

However, I have some problem with OpenGL. Celestia is crashing with 
the error: "Unable to resolve GL/GLX symbols - please check your GL 
library installation." and the tuxracer is not well running. When 
racing I can see a lot of "flashing triangles".
Is there some files I can check to see if OpenGL is well installed?
Anyway, I will try now this method 
(http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html) 
to see if it resolves my OpenGL problem.

Thanks again for the help, it's really nice to know that in this 
community, when you have a problem you can surely resolve it with the 
help of the list!

Nico
Nicolas de Sereville wrote:
Hi list,
I have an Ati 9600XT graphical card and I want to get 3D acceleration 
with the propriatary drivers (fglrx). I am using debian Sid with the 
last xserver version (4.3.0.dfsg.1-7).

Following the "ATI Radeon Linux How-To", I managed to get the 3D 
acceleration with the previous xserver version (4.3.0.dfsg.1-6) but 
overwriting the MESA libGL library with the ATI one, through a "dpkg 
--force-overwrite -i fglrx.deb". Everything worked well but I had a 
lot of troubles upgrading the xserver due to the libGL library. So I 
decided to make use of "dpkg-divert" as suggested on this web page 
(http://g-tec.co.at/ati_alt.html):

dpkg-divert --package fglrx --add /usr/X11R6/lib/libGL.so.1.2
dpkg -i fglrx_4.3.0-4.12_i386.deb
Everything went well (no complain about the libGL library) but when 
running "fglrxinfo", I obtain the following output showing that I am 
not using the ATI libGL library:

display: :0.0  screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4
So my question is (sorry for the long introduction): is there a way, 
using dpkg-divert, to specify which libGL library should be used (the 
ATI one) in order to have the 3D acceleration working?

Thank in advance,
Nico



--
:-----:
: Nicolas de SEREVILLE:
: I.E.E.C (Institut d'Estudis Espacials de Catalunya) :
: Campus UAB - Falcutat de Ciencies   :
: Torre C-5 - parell -  2a planta :
: E-08193 Bellaterra, :
: SPAIN   :
: :
: Tel : +34 93 581 43 59  :
: Fax : +34 93 581 43 63  :
: Web : http://www.ieec.fcr.es:
:-:

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



installation CUPS + LexmarkZ55

2004-10-09 Thread Nicolas de Sereville
Hi,
It is my first try to install the above printer with CUPS on USB. I 
followed the instructions to install the propriatary driver 
(http://www.linuxprinting.org/lexmark-faq.html#s_15) and then I followed 
this thread: http://lists.debian.org/debian-user/2002/07/msg00877.html

1) I installed the following packages: cupsys, cupsys-bsd, cupsys-client 
and foomatic-bin, foomatic-db-engine, foomatic-filter.
2) I installed the foomatic-lexmark-kit, run the install and 
lexmarkinstall scripts where it generated a ppd file (the one forme the 
Z53 model)
3) ls -l /dev/usb/lp0 -> crw-rw-rw-  1 lp sys 180, 0 2002-03-14 22:54 
/dev/usb/lp0
4) I copied this ppd file to  /usr/share/cups/model/Lexmark
5) I restarted cups
6) I added my printer through the user interface.
7) I modified the /etc/cups/printers.conf so that "DeviceURI test:/dev/null"
8) I restarted cups
9) I try to print a test page and 

... of course, as a first try it doesn't work! So I read the logs and I 
can see the line:
"D [09/Oct/2004:13:56:00 +0200] [Job 10] sh: /usr/local/lexmark/z53/z53: 
No suchfile or directory" which doesn't exist since I have the Z55 model 
running with the Z53 ppd file.
I made a symlink of /usr/local/lexmark/z53/z53 to 
/usr/local/lexmark/z55/lexmarkz55 which seems to be the Z55 driver, but 
now the error is:
"D [09/Oct/2004:13:05:58 +0200] [Job 9] Gtk-WARNING **: cannot open 
display:"

I can see the jobs in the queue with a "plq" but they are not coming out 
to the printer. So as you see I am stuck. Does anyone have some ideas 
that I can try?

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



Re: ATI 3D acceleleration and dpkg-divert

2004-09-21 Thread Nicolas de Sereville
Hi!
Andrea Vettorello wrote:
On Tue, 21 Sep 2004 15:33:01 +0200, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

Hi!
   

[...]
 

# dpkg -S /usr/X11R6/lib/libGL.so.1.2
diversion by fglrx from: /usr/X11R6/lib/libGL.so.1.2
diversion by fglrx to: /usr/X11R6/lib/libGL.so.1.2.distrib
fglrx, xlibmesa-gl: /usr/X11R6/lib/libGL.so.1.2
So the *.a libraries come from the xlibmesa-gl-dev package, whereas the
libGL.so.1.2 is diverted. What I could test is to rename them
temporarely and see if I can run tuxracer (after googling I could not
find any description of my problem) and celestia.
From the diversion of the libGL.so.1.2 library, I can see the
/usr/X11R6/lib/libGL.so.1.2.distrib file but cannot find it? is it a
real file?
   

$ dpkg -S /usr/X11R6/lib/libGL.so.1.2
xlibmesa-gl: /usr/X11R6/lib/libGL.so.1.2
$ file /usr/X11R6/lib/libGL.so.1.2
/usr/X11R6/lib/libGL.so.1.2: ELF 32-bit LSB shared object, Intel
80386, version 1 (SYSV), stripped
I would say yes...
 

I obtain the same aprt form the "stripped" and "not stripped":
# file /usr/X11R6/lib/libGL.so.1.2
/usr/X11R6/lib/libGL.so.1.2: ELF 32-bit LSB shared object, Intel 80386, 
version
1 (SYSV), not stripped

I guess I didn't explain well but I was thinking of the file 
/usr/X11R6/lib/libGL.so.1.2.distrib. I can not find it.

Nico

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



Re: ATI 3D acceleleration and dpkg-divert

2004-09-21 Thread Nicolas de Sereville
Hi!
However, I have some problem with OpenGL. Celestia is crashing with the
error: "Unable to resolve GL/GLX symbols - please check your GL library
installation." and the tuxracer is not well running. When racing I can
see a lot of "flashing triangles".
Is there some files I can check to see if OpenGL is well installed?
Anyway, I will try now this method
(http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html) 
to see if it resolves my OpenGL problem.
   

Maybe this helps:
ls -l /usr/X11R6/lib/libGL*
lrwxrwxrwx  1 root root 12 2004-09-19 20:47
/usr/X11R6/lib/libGL.so.1 -> libGL.so.1.2
-rwxr-xr-x  1 root root 798590 2004-07-16 17:23 /usr/X11R6/lib/libGL.so.1.2
lrwxrwxrwx  1 root root 13 2004-09-18 23:20
/usr/X11R6/lib/libGLU.so.1 -> libGLU.so.1.3
-rw-r--r--  1 root root 500480 2004-09-06 13:16 /usr/X11R6/lib/libGLU.so.1.3
Try finding out where those libGL*.a files on your system come from
with dpkg -S . Maybe that is causing problems. I only have
these and everything works fine (as far as I can tell, haven't
actually tried tuxracer yet). Maybe it's even in the ATI FAQ?
ok, I obtain the following from my home directory:
# dpkg -S /usr/X11R6/lib/libGL.a
xlibmesa-gl-dev: /usr/X11R6/lib/libGL.a
# dpkg -S /usr/X11R6/lib/libGL.so.1
xlibmesa-gl-dev: /usr/X11R6/lib/libGL.so.1
# dpkg -S /usr/X11R6/lib/libGL.so.1.2
diversion by fglrx from: /usr/X11R6/lib/libGL.so.1.2
diversion by fglrx to: /usr/X11R6/lib/libGL.so.1.2.distrib
fglrx, xlibmesa-gl: /usr/X11R6/lib/libGL.so.1.2
So the *.a libraries come from the xlibmesa-gl-dev package, whereas the 
libGL.so.1.2 is diverted. What I could test is to rename them 
temporarely and see if I can run tuxracer (after googling I could not 
find any description of my problem) and celestia.

From the diversion of the libGL.so.1.2 library, I can see the 
/usr/X11R6/lib/libGL.so.1.2.distrib file but cannot find it? is it a 
real file?

I will let you know as soon as I can test
Nico
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: ATI 3D acceleleration and dpkg-divert

2004-09-21 Thread Nicolas de Sereville
Hi!
A big thanks to everybody who spare some time helping me. I now have the 
3D acceleration working! My error was very stupid... As suggested by 
Wim, when removing my previous installation, the "dpkg --purge fglrx" 
command left some files that I did not erased, so I had a mix within new 
and old files. Deleting the directory and compiling again the kernel 
module was just fine.
Also, I tried with two options: DRM compiled in th kernel and without 
DRM. The results are the same.

However, I have some problem with OpenGL. Celestia is crashing with the 
error: "Unable to resolve GL/GLX symbols - please check your GL library 
installation." and the tuxracer is not well running. When racing I can 
see a lot of "flashing triangles".
Is there some files I can check to see if OpenGL is well installed?
Anyway, I will try now this method 
(http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html) 
to see if it resolves my OpenGL problem.

Thanks again for the help, it's really nice to know that in this 
community, when you have a problem you can surely resolve it with the 
help of the list!

Nico
Nicolas de Sereville wrote:
Hi list,
I have an Ati 9600XT graphical card and I want to get 3D acceleration 
with the propriatary drivers (fglrx). I am using debian Sid with the 
last xserver version (4.3.0.dfsg.1-7).

Following the "ATI Radeon Linux How-To", I managed to get the 3D 
acceleration with the previous xserver version (4.3.0.dfsg.1-6) but 
overwriting the MESA libGL library with the ATI one, through a "dpkg 
--force-overwrite -i fglrx.deb". Everything worked well but I had a 
lot of troubles upgrading the xserver due to the libGL library. So I 
decided to make use of "dpkg-divert" as suggested on this web page 
(http://g-tec.co.at/ati_alt.html):

dpkg-divert --package fglrx --add /usr/X11R6/lib/libGL.so.1.2
dpkg -i fglrx_4.3.0-4.12_i386.deb
Everything went well (no complain about the libGL library) but when 
running "fglrxinfo", I obtain the following output showing that I am 
not using the ATI libGL library:

display: :0.0  screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4
So my question is (sorry for the long introduction): is there a way, 
using dpkg-divert, to specify which libGL library should be used (the 
ATI one) in order to have the 3D acceleration working?

Thank in advance,
Nico


--
:-----:
: Nicolas de SEREVILLE:
: I.E.E.C (Institut d'Estudis Espacials de Catalunya) :
: Campus UAB - Falcutat de Ciencies   :
: Torre C-5 - parell -  2a planta :
: E-08193 Bellaterra, :
: SPAIN   :
: :
: Tel : +34 93 581 43 59  :
: Fax : +34 93 581 43 63  :
: Web : http://www.ieec.fcr.es:
:-:

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



Re: ATI 3D acceleleration and dpkg-divert

2004-09-20 Thread Nicolas de Sereville
Hi,
Rob Sims wrote:
On Sunday 19 September 2004 10:53 am, Nicolas de Sereville wrote:
 

Following the "ATI Radeon Linux How-To", I managed to get the 3D
acceleration with the previous xserver version (4.3.0.dfsg.1-6) but
overwriting the MESA libGL library with the ATI one, through a "dpkg
--force-overwrite -i fglrx.deb". Everything worked well but I had a
lot of troubles upgrading the xserver due to the libGL library. So I
decided to make use of "dpkg-divert" as suggested on this web page
(http://g-tec.co.at/ati_alt.html):
   

 

dpkg-divert --package fglrx --add /usr/X11R6/lib/libGL.so.1.2
dpkg -i fglrx_4.3.0-4.12_i386.deb
   

Where does /usr/X11R6/lib/libGL.so.1 point now?  On my system, it keeps 
getting set to the diverted library.
 

ll /usr/X11R6/lib/libGL* gives:
-rw-r--r--1 root root 666K 2004-09-06 13:16 libGL.a
lrwxr-xr-x  1 root root12 2004-09-18  17:41 libGL.so -> libGL.so.1.2*
lrwxr-xr-x  1 root root12 2004-09-20  22:19 libGL.so.1 -> libGL.so.1.2*
-rwxr-xr-x  1 root root 780K 2004-07-16 17:23 libGL.so.1.2*
-rw-r--r--1 root root 651K 2004-09-06 13:16 libGLU.a
lrwxr-xr-x  1 root root   13 2004-09-18   17:41 libGLU.so -> libGLU.so.1.3
lrwxr-xr-x  1 root root   13 2004-09-18   17:41 libGLU.so.1 -> libGLU.so.1.3
-rw-r--r--1 root root 489K 2004-09-06 13:16 libGLU.so.1.3
-rw-r--r--1 root root  31K 2004-09-06  13:16 libGLw.a
How can I recognize a diverted library? After a "find / -name 'libGL*'" 
I can only see these libraries.

Nico

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



Re: ATI 3D acceleleration and dpkg-divert

2004-09-20 Thread Nicolas de Sereville
Hi,
Wim De Smet wrote:
Hi,
On Mon, 20 Sep 2004 10:54:46 +0200, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

Hi,

Wim De Smet wrote:
   

Hi,
On Mon, 20 Sep 2004 01:13:55 +0200, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

(WW) fglrx(0): Kernel Module version does *not* match driver.
   

I missed this one. Did you compile the kernel driver again after
installing a new version? Maybe the old module is still loaded en you
need to unload it first.
 

By "kernel module", do you mean AGP? Anyway I did not compile anything
from the kernel after installing the new version of the fglrx drivers.
   

You need to recompile the "fglrx" module. You can find the scripts for
it in /lib/modules/fglrx, although there may be a problem there if you
didn't purge this directory since the last time you compiled something
in it. I would suggest removing this directory, reinstalling your
generated .deb, then going into this folder and build a new kernel
module. (by going into the build_mod dir and running 'sh make.sh')
 

Ah! it may be that point! When I desinstalled the previous "fglrx" 
package to upgrade the xserver, it told me that some files could not be 
erased. But i reinstall the new .deb file and compiled the driver 
anyway, so I may have a mismatch between old and new files Will try 
what you suggest as soon as  I go home and let you know.

Thanks,
Nico

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



Re: ATI 3D acceleleration and dpkg-divert

2004-09-20 Thread Nicolas de Sereville
Hi,
David Baron wrote:
On Monday 20 September 2004 06:30, [EMAIL PROTECTED] 
wrote:
 

(WW) fglrx(0): Kernel Module version does *not* match driver.
   

The "DRM" must be compiled against the kernel. There will be a means of 
telling the make which kernel and which module(s) to make.

First, untar the kernel source.
Create a "linux" symlink from the /usr/src to the kernel source head 
directory.
Then, copy the system config from boot to the linux src folder as .config.
make oldconfig.
Then, start the kernel compile. Make is enough. You do not have to go through 
the whole mess. Once it starts doing CC compilations, you can stop it. What 
this does is makes sure all the .h files are where they are needed.
Now compile the DRM--you may need to give it the path the the linux src 
folder.
Finally, copy the resulting  .ko file to the appropriate /lib/modules/ . 
folder. Reboot.

A good WIKI can be found here:
http://dri.sourceforge.net/cgi-bin/moin.cgi/Building#head-08d485086c70c4b931535491f1ccad21181d731f
I used the DRM from this CVS for my ATI rage pro mach64 card but the 
instructions should be similar for a different source such as flgr. The "make 
World" from this CVS would not compile successfully but apparently was not 
needed--stuff from Sid was enough.

 

Thank you for all this information! I reread the method I followed to 
install the propriatary driver fglrx (http://g-tec.co.at/ati_alt.html) 
and I found just before the "Notes about 2.6.x kernels" section that 
"DRM" was not supported by the ATI drivers. In my case and my actual 
kernel, "DRM" is compiled. So I am a little bit lost. I remember having 
read on the web (was not abble to find the web page again...) that one 
way for making work the 3D acceleration was using the ATI propriatary 
drivers *or* DRM/DRI *or* the gatos project. Am I right? So if I 
understand well, you suggest to install DRM/DRI and not the propriatary 
drivers.

Ithink I will try first to deal with the propriatary drivers and 
recompile my kernel without the DRM activated. It may take some time 
since I am not very used to do that yet!

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



Re: ATI 3D acceleleration and dpkg-divert

2004-09-20 Thread Nicolas de Sereville
Hi,
Wim De Smet wrote:
Hi,
On Mon, 20 Sep 2004 01:13:55 +0200, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

(WW) fglrx(0): Kernel Module version does *not* match driver.
   

I missed this one. Did you compile the kernel driver again after
installing a new version? Maybe the old module is still loaded en you
need to unload it first.
 

By "kernel module", do you mean AGP? Anyway I did not compile anything 
from the kernel after installing the new version of the fglrx drivers.

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



Re: ATI 3D acceleleration and dpkg-divert

2004-09-19 Thread Nicolas de Sereville
Hi,
Wim De Smet wrote:
Hi,
On Sun, 19 Sep 2004 22:23:23 +0200, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

Hi,

Wim De Smet wrote:
   

Hi,
On Sun, 19 Sep 2004 18:53:58 +0200, Nicolas de Sereville
<[EMAIL PROTECTED]> wrote:
 

Hi list,
I have an Ati 9600XT graphical card and I want to get 3D acceleration
with the propriatary drivers (fglrx). I am using debian Sid with the
last xserver version (4.3.0.dfsg.1-7).
[install stuff...]

   

Are you sure the user you're running fglrxinfo with has access to
opengl (eg member of group video) and that you have the ATI kernel
module installed?

 

Running the "groups" command shows that the user belongs to the video
group. Also, the fglrx  module is loaded (I can see it with lsmod). I
think my problem is more related to the instalation procedure and the
use of dpkg-divert since I managed to have 3d acceleration with the
former version of the xserver but overwriting the libGL library.
   

Sounds good, but just to be sure check your xfree startup log. I had
this fail a while back because of AGP support problems. I can't help
you much with dpkg-divert, but as I recall from trying to change
things myself the manpages aren't very helpfull and I'm doubtfull if
they are correct.
 

Well, looking at the logs from XFree86.0.log, I can see the following:
... ...
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 3.9.0
(II) fglrx(0): Date: May 11 2004
(II) fglrx(0): Desc: ATI Fire GL DRM kernel module
(WW) fglrx(0): Kernel Module version does *not* match driver.
(EE) fglrx(0): incompatible kernel module detected - HW accelerated 
OpenGL will
not work
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xe0912000 at 0x4024f000
(WW) fglrx(0): ***
(WW) fglrx(0): * DRI initialization failed!  *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available*
(WW) fglrx(0): * *
... ...

which doesn't sound good. I just installed the driver from the ATI 
webpage (after running the alien command). Maybe a problem when 
compiling the driver, but I took care using the same version of gcc 
(2.95) that I used for compiling my kernel.

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



ATI 3D acceleleration and dpkg-divert

2004-09-19 Thread Nicolas de Sereville
Hi list,
I have an Ati 9600XT graphical card and I want to get 3D acceleration 
with the propriatary drivers (fglrx). I am using debian Sid with the 
last xserver version (4.3.0.dfsg.1-7).

Following the "ATI Radeon Linux How-To", I managed to get the 3D 
acceleration with the previous xserver version (4.3.0.dfsg.1-6) but 
overwriting the MESA libGL library with the ATI one, through a "dpkg 
--force-overwrite -i fglrx.deb". Everything worked well but I had a lot 
of troubles upgrading the xserver due to the libGL library. So I decided 
to make use of "dpkg-divert" as suggested on this web page 
(http://g-tec.co.at/ati_alt.html):

dpkg-divert --package fglrx --add /usr/X11R6/lib/libGL.so.1.2
dpkg -i fglrx_4.3.0-4.12_i386.deb
Everything went well (no complain about the libGL library) but when 
running "fglrxinfo", I obtain the following output showing that I am not 
using the ATI libGL library:

display: :0.0  screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4
So my question is (sorry for the long introduction): is there a way, 
using dpkg-divert, to specify which libGL library should be used (the 
ATI one) in order to have the 3D acceleration working?

Thank in advance,
Nico

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



Re: [SOLVED] keyboard not working after upgrade

2004-09-02 Thread Nicolas de Sereville
Hi, my keyboard is working again!
Let me explain what I did. After switching off the Xserver by ssh'ing I 
was able to use my keyboard at the console. Then after installing icewm, 
I "startx" and was able to use my keyboard in this environment so the 
problem was related to KDM/KDE. I then tried to use GDM and KDE and I 
was able to enter my login and password in the GDM greeting screen, so 
it was KDM related stuff. Then I played with the KDM configuration files 
and could not obtain anything so I did an "apt-get distupgrade" (i am 
running unstable and not testing as stated in my first message). And 
everything is now working. I can log in KDM without any problem!

Thank you very much for the help
Nico

Kent West wrote:
Nicolas de Sereville wrote:
I am running debian testing (kernel 2.6.6) and yesterday I upgraded 
some packages (vim, xemacs, *kdm*, ...). Now my keyboard is not 
working anymore when kdm asks me for the user and password. I can use 
the keyboard to choose the OS I want to boot from lilo, but when the x 
session begins it stops working. I can only enter in my box from 
another computer through ssh.

(==) ServerLayout "Server Layout"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "ATI Graphics Adapter"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "es"
(**) XKB: layout: "es"
(**) Mouse1: Buttons: 5
(II) Keyboard "Keyboard1" handled by legacy driver
 

I would suggest ssh'ing in, and shutting down kdm ("/etc/init.d/kdm 
stop"). Does your keyboard work at the console now? If not, I'd disable 
kdm temporarily (about a dozen ways to do this) and reboot; does your 
keyboard work at the console?

If the keyboard works at the console, you know the problem is either X- 
or KDE/KDM-related.   I'd then take KDE/KDM out of the picture, and 
start X with a different wm/environment, such as icewm (just create a 
"~/.xinitrc" with the single line "icewm" (you may need to "apt-get 
install icewm") and start X with "startx"). Does the keyboard work? If 
so, you know the problem is KDE/KDM-related; if not, you know the 
problem is X-related.

You can reconfigure X with "dpkg-reconfigure xserver-xfree86". I assume 
you're wanting the "es" (Spanish?) layout? Most US-ian keyboards are 
PC104 instead of PC105. I'm not sure what that "legacy driver" thing is.

Let us know the results of these tests.

--
:-:
: Nicolas de SEREVILLE:
: I.E.E.C (Institut d'Estudis Espacials de Catalunya) :
: Edifici Nexus, 201  :
: C/ Gran Capita 2-4  :
: E-08034 Barcelona,  :
: SPAIN   :
: :
: Tel : +34 93 205 85 23  :
: Fax : +34 93 280 63 95  :
: Web : http://www.ieec.fcr.es:
:-:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: keyboard not working after upgrade

2004-09-01 Thread Nicolas de Sereville
Kent West wrote:
Nicolas de Sereville wrote:
I am running debian testing (kernel 2.6.6) and yesterday I upgraded 
some packages (vim, xemacs, *kdm*, ...). Now my keyboard is not 
working anymore when kdm asks me for the user and password. I can use 
the keyboard to choose the OS I want to boot from lilo, but when the x 
session begins it stops working. I can only enter in my box from 
another computer through ssh.

(==) ServerLayout "Server Layout"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "ATI Graphics Adapter"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "es"
(**) XKB: layout: "es"
(**) Mouse1: Buttons: 5
(II) Keyboard "Keyboard1" handled by legacy driver
 

I would suggest ssh'ing in, and shutting down kdm ("/etc/init.d/kdm 
stop"). Does your keyboard work at the console now? If not, I'd disable 
kdm temporarily (about a dozen ways to do this) and reboot; does your 
keyboard work at the console?
OK, I shut down kdm as you suggested after ssh'ing. Unfortunately I 
cannot check if the keyboard work since I am at work and my box is at 
home. I will let you know tonight when I go home. By disabling kdm 
temporarily, do you mean that after reboot X is not started? If so, how 
can I achieve it?

If the keyboard works at the console, you know the problem is either X- 
or KDE/KDM-related.   I'd then take KDE/KDM out of the picture, and 
start X with a different wm/environment, such as icewm (just create a 
"~/.xinitrc" with the single line "icewm" (you may need to "apt-get 
install icewm") and start X with "startx"). Does the keyboard work? If 
so, you know the problem is KDE/KDM-related; if not, you know the 
problem is X-related.
It sounds very logical. I installed icewm to make the checks tonight.
You can reconfigure X with "dpkg-reconfigure xserver-xfree86". I assume 
you're wanting the "es" (Spanish?) layout? Most US-ian keyboards are 
PC104 instead of PC105. I'm not sure what that "legacy driver" thing is.
Yes I am in Spain with a spanish keyboard. My /etc/X11/XF86Config-4 file 
was generated by the ATI driver to have 3D acceleration and the TV-out 
enabled. Instead of "dpkg-reconfigure xserver-xfree86", I guess I can 
reconfigure X with the ATI tools. Anyway, my keyboard used to work 
before yesterday without any problem.


Let us know the results of these tests.
Thank you very much for your ideas and I will let you know as soon as 
possible.

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



keyboard not working after upgrade

2004-09-01 Thread Nicolas de Sereville
Hi!
This is the first time I write to this list and I am quite a newbie with 
debian. Here is my problem.

I am running debian testing (kernel 2.6.6) and yesterday I upgraded some 
packages (vim, xemacs, *kdm*, ...). Now my keyboard is not working 
anymore when kdm asks me for the user and password. I can use the 
keyboard to choose the OS I want to boot from lilo, but when the x 
session begins it stops working. I can only enter in my box from another 
computer through ssh.

I guess it is related to the xserver but I cannot figure how. I put in 
attachment the logs from the XFree server but I don't know enough to see 
from where comes the problem.

Also, from the /var/log/syslog I can see the followings error concerning 
*kdm*:
Sep  1 10:17:04 novae kdm_config[1795]: Unrecognized key 
'GreeterPosFixed' in section [X-*-Greeter] at /etc/kde3/kdm/kdmrc:31
Sep  1 10:17:04 novae kdm_config[1795]: Unrecognized key 'GreeterPosX' 
in section [X-*-Greeter] at /etc/kde3/kdm/kdmrc:32
Sep  1 10:17:04 novae kdm_config[1795]: Unrecognized key 'GreeterPosY' 
in section [X-*-Greeter] at /etc/kde3/kdm/kdmrc:33
Sep  1 10:17:12 novae kdm_greet[1890]: Can't open default user face

I know it is related to the position of the greeting box but it seems to 
suggest that new version of *kdm* cannot undersand well the older 
configuration files (during the upgrade I told apt-get to keep the old 
configuration files). Could it be related to my problem?

Any help will be very apreciated, thanx,
Nico

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-6 20040707142024 [EMAIL PROTECTED])
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.23 i686 [ELF] 
Build Date: 07 July 2004
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.6 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002 
(Debian prerelease)) #1 Tue Jun 1 23:59:25 CEST 2004 T
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/XFree86.0.log", Time: Wed Sep  1 10:17:04 2004
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Server Layout"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "ATI Graphics Adapter"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "es"
(**) XKB: layout: "es"
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to 
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(++) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.2
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.4
XFree86 Server Extension : 0.2
XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x800028e4, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 10de,01e0 card 147b,1c00 rev c1 class 06,00,00 hdr 80
(II) PCI: 00:00:1: chip 10de,01eb card 10de,0c17 rev c1 class 05,00,00 hdr 80
(II) PCI: 00:00:2: chip 10de,01ee card 10de,0c17 rev c1 class 05,00,00 hdr 80
(II) PCI: 00:00:3: chip 10de,01ed card 10de,0c17 rev c1 class 05,00,00 hdr 80
(II) PCI: 00:00:4: chip 10de,01ec card 10de,0c17 rev c1 class 05,00,00 hdr 80
(II) PCI: 00:00:5: chip 10de,01ef card 10de,0c17 rev c1 class 05,00,00 hdr 80
(II) PCI: 00:01:0: chip 10de,0060 card 147b,1c00 rev a4 class 06,01,00 hdr 80
(II)