I found out that all i had to do was to send a picture message direct to my email address,though i might have to print it out first before i can use it(A4 size). Robert
On Wed, 2006-03-01 at 18:44 +0000, robert wrote:
I found out that all i had to do was to send a picture message direct to my email address,though i might have to print it out first before i can use it(A4 size). Robert
That costs money/credit/free messages. Bluetooth is free (after hardware costs) and allows pictures to go both ways. I found it to be a bit of a pain to get working, but it's handy once you get used to it.
On 1 Mar 2006, at 7:35 pm, Richard Brooklyn wrote:
On Wed, 2006-03-01 at 18:44 +0000, robert wrote:
I found out that all i had to do was to send a picture message direct to my email address,though i might have to print it out first before i can use it(A4 size). Robert
That costs money/credit/free messages. Bluetooth is free (after hardware costs) and allows pictures to go both ways. I found it to be a bit of a pain to get working, but it's handy once you get used to it.
http://usefulinc.com/software/gnome-bluetooth
I found this useful when I used gnome ^^^ It may have now been added into gnome, but it was a separate project before.
Cheers
Dave
Whoops...breakage
I have been stuck at home with man flu today, So I spent the morning getting one of my favourite games working..Enemy Territory.
It's always been a bit of an uphill battle on a 64bit machine..after getting segfaults as libGL loaded, I ran the main binary against strace and discovered that if I put a symlink called libnvidia-tls.so.1 in /usr/lib32/i686 pointing to /usr/lib32/nvidia/libnvidia-tls.so.1.0.7667 then all was well.
Or so I thought....For other reasons I rebooted the machine later and X failed to start (didn't catch the error dump)...removed the link and rebooted...still no go.
apt-get remove nvidia-glx followed by apt-get install nvidia-glx followed by a reboot got me going again...but only for one boot. If I reboot again X will fail to load with the error log below, until I once again remove and reinstall the nvidia-glx package.
The only other thing I have done today is remove nvidia-glx and replaced it with nvidia-glx-legacy to see if an earlier driver version solved the original segfault problem...it didn't so I removed the legacy driver and put the original back.
I am struggling to understand what can be broken to allow X to start only once.
* Only the end of the error log here, mail me if you want to see more, but I can't see much of any relevance before this bit
(II) NVIDIA(0): Setting mode "1280x1024" (II) Loading extension NV-GLX (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (**) Option "dpms" (**) NVIDIA(0): DPMS enabled (II) Loading extension NV-CONTROL (==) RandR enabled Symbol __glXgetActiveScreen from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! Symbol __glXgetActiveScreen from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Initializing extension GLX (**) Option "CoreKeyboard" (**) Generic Keyboard: Core Keyboard (**) Option "Protocol" "standard" (**) Generic Keyboard: Protocol: standard (**) Option "AutoRepeat" "500 30"
*** If unresolved symbols were reported above, they might not *** be the reason for the server aborting.
Fatal server error: Caught signal 11. Server aborting
Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information.
On Wed, 2006-03-01 at 21:46 +0000, Wayne Stallwood wrote:
Whoops...breakage
Just to add there is no difference in the log file from a successful start to a failed one up until the
*** If unresolved symbols were reported above, they might not *** be the reason for the server aborting.
Fatal server error: Caught signal 11. Server aborting
bit..The unresolved symbols bits etc are still there even when it works.
Strange huh ?
In place of the error on the working turn I get....
(**) Option "XkbRules" "xorg" (**) Generic Keyboard: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Generic Keyboard: XkbModel: "pc105" (**) Option "XkbLayout" "gb" (**) Generic Keyboard: XkbLayout: "gb" (**) Option "CustomKeycodes" "off" (**) Generic Keyboard: CustomKeycodes disabled (**) Option "Protocol" "ImPS/2" (**) Configured Mouse: Device: "/dev/input/mice" (**) Configured Mouse: Protocol: "ImPS/2" (**) Option "CorePointer" (**) Configured Mouse: Core Pointer (**) Option "Device" "/dev/input/mice" (**) Option "Emulate3Buttons" "true" (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Configured Mouse: ZAxisMapping: buttons 4 and 5 (**) Configured Mouse: Buttons: 5 (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE) (II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other) (II) Configured Mouse: ps2EnableDataReporting: succeeded 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
What NVidia card have you got? I find that if a game fucks up big time, the driver fails to load until the machine is cold booted, saying that the extra power socket on my FX 5950 Ultra is disconnected...
On Wed, 2006-03-01 at 22:06 +0000, Richard Brooklyn wrote:
What NVidia card have you got? I find that if a game fucks up big time, the driver fails to load until the machine is cold booted, saying that the extra power socket on my FX 5950 Ultra is disconnected...
Old and ancient MX 440
Yes I have seen that too, but this is different. The machine will fail to come back after one boot even if I don't run the game. Cold boots vs warm boots seem to make no difference, only reinstalling nvidia-glx fixes it (for one boot)
It's really really weird to say the least !!!
Wayne Stallwood wrote:
Whoops...breakage
I am struggling to understand what can be broken to allow X to start only once.
You mean X starts after you install the nvidia driver? Then a reboot and it no longer starts X?
If so then this may be a udev issue with the nvidia driver. I had something similar with FC2/3?.
Just a thought.
Cheers
On Thu, 2006-03-02 at 02:39 +0000, David Simon Cooper wrote:
You mean X starts after you install the nvidia driver? Then a reboot and it no longer starts X?
Almost, If I install the driver and then reboot X will work...but on the next boot (or if I just restart X) it will fail.
If so then this may be a udev issue with the nvidia driver. I had something similar with FC2/3?.
Hmmm interesting but in the error log I can see it talking to the card so I don't think it is udev...I will look into that anyway.