Hi all,

Having upgraded from kernel 2.4 to 2.6.6 using apt-get, I found that my mouse and NIC were not recognised. Having browesed the forums I have been able to get both working ok. However on launching any App where they must access eth0, they report no such device exists.
The following is a list of what I know:

1. /sbin/ifconfig - a : This shows eth0 and all appropriate info
2. /etc/modules.conf : shows 'alias eth0 8139too'
3. Can ping loopback Ip, own IP , and get web pages (have RH 9 server, this one to take its place)

The error messages have happened as launching the above programs as a standard user from the KDE menu. However as trying to launch them from the command line as su, this is the following error I get:

Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to server

(etherape:7080): Gtk-WARNING **: cannot open display:

Cany any one offer any ideas, or things to try.

TIA.

send in more info. (bootmessages, ..)
do you see your eth0 if you type "ifconfig" (-a). is your card loaded as module (/etc/modules)?
can you "ping xxx.xxx.xxx.xx" it?

sl mritch

Ummmm, thanks but have a good read of the message that I posted, the information you have asked is already listed!!

I hadnt tried the obvious, logging in as root and trying to launch the apps from the menu. This worked fine, so obviously a permission thing. Although still cant work out why I cant launch them from the command line as su when logged in as standard user, yet works from command line when logged in as Root. But will try running chmod for standard users (as I the only one) as I remember reading that its bad practice to remain logged on as root, as I try and su instead.

Thanks anyway.

you'r right. sorry.

Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to server

this means that the user has no permission to draw to the x server. try "xhost +" to grant everybody access to the server - just for testing. take a look at xauth to get it running more secure. if you conntact from an other machine be sure your x server isn't started with --nolisten tcp.

sl mritch

mritch, no probs - apologies if I came across like an ungratefull sod!

Will give it ago, I get the "refused error" message quite a bit, so may fix up other **experiances** having ATM

Thanks!

Sal