11.3 on x64 not a good experience

After installing 11.3 my first problem was no Wacom support. This is a major problem for me as I’m a photographer. I saw other posts on the subject so was hopeful that someone would get on the case.

Yesterday I had a kernel update and after all the updates, I rebooted.

The splash screen appeared for a few seconds and then a black screen. No X11. No virtual ttys. I sshed in and found some updates still outstanding (why?) so I applied those and rebooted. Still got a black screen.

Sshed in again and saw messages (not errors) relating to Wacom tablet in the X11 logs. Unplugged the Wacom and rebooted. Bingo. Everything came up.

I plugged the Wacom back in, half hoping that maybe there had been updates in this area but it STILL doesn’t work.

What are the plans to get the Wacom software working again, please?

At the moment, GIMP crashes almost instantly if I try to use the Wacom tablet with it. Serious headache. I have a backlog of work that I need a working tablet for. I’ll need to switch distros if it doesn’t get fixed soon.

(Intel i7, 6 core, 12GB RAM, nVidia, Wacom Intuos 3)

The new kernel update (update to 2.6.34.4, version 3038) is a mind-numbing disaster that will send your blood pressure soaring into the stratosphere, and so far no one has any fixes for it other than to start all over and reinstall 11.3, being careful NOT to accept the kernel update. The symptoms you describe are repeated in this forum by the score, and there are hundreds more just like them scattered across the Web. Other symptoms: your bootloader will get trashed, either not appearing at all or only allowing you to boot into Windows, with all other choices removed.

I know this isn’t much help, but the only advice I have is to avoid it like the plague. Whoever is running the update database needs to remove this update and replace it with one that doesn’t completely hose formerly stable systems in a variety of unpleasant ways.

The tablet problem sounds unrelated, but given the unpredictable nature of the kernel update’s damage, there could be a connection.

It may be that your best path would be to revert to 11.2, which actually worked for the most part.

Mind numbing disaster ?

Sweeping generalisations are seldom accurate. You shouldn’t assume that your experience is typical for all. The only problem I had with the kernel update was to uninstall ndiswrapper, something I’ve never used, otherwise it went fine. There are others who found it as trouble free as I did.

Sweeping generalisations are seldom accurate?

Pretty sure that’s one also.

In general terms the update to 11.3 has been a good experience.
No new hardware has been needed.
All new versions of SW used are better.
Initial display driver problems were my own fault as reading set-up instructions carefully is not one of my virtues.
Network i/f has slowed down on 64 bit OS. 32 bit OS’s not problem.

AMD Phenom™ II X4 940, Linux 2.6.34.4-0.1-desktop x86_64, 4.5.1 (KDE 4.5.1) “release 296”

Well i’m using the same kernel as you 64 bit system without display problems.or any serious hangups.
I would suggest testing the wacom on another machine just to make sure it is working correctly. if so then it would be a driver issue on your system. :slight_smile:

later dinner is cooking and i hope not burning

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Agreed; I didn’t realize there had been any problems until seeing this
post and its response. I’m also a little skeptical about a kernel
disaster causing a boot loader problem (at least one that causes the boot
loader to not appear at all) since the boot loader comes BEFORE the kernel
in the boot process. Anyway, I imagine these are the exception more than
the rule. To the OP, it’s interesting you can SSH in without any TTYs
loading properly. While in there perhaps get the recent (since last
shutdown) output from your /var/log/messages file as well as the dmesg
output and post them here.

Good luck.

On 09/12/2010 07:36 AM, Raffles10 wrote:
>
> Mind numbing disaster ?
>
> Sweeping generalisations are seldom accurate. You shouldn’t assume that
> your experience is typical for all. The only problem I had with the
> kernel update was to uninstall ndiswrapper, something I’ve never used,
> otherwise it went fine. There are others who found it as trouble free as
> I did.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJMjTF5AAoJEF+XTK08PnB5klcP/idLy8DaTem6xqb+P7y82/PD
Rf2lk4LsPG5jXXreVJKIKEid29pi1x1UGzctESIYxzERYo5o0gGXMGYsgGlebZZH
BwDpyw8h9MxgUpOJEyoB+KCmxB/6tMr7OtXVpYatUAcEZ7u9SXswiIPha1M6LAox
B4zWIWNfn5ngDO/RF6xo3yTJ0bHhudidz7TlaghE5KDF87DejMDXs20+mxJjvG+7
WWLKwyDtsgihb9zC4p6XVnSlvB+OdXalDT9ySd2QO2r56UmuFjovPjlNKS1FmUsd
697/KHCJTZNSS8MtbXAyzLhwb3u3xMTp+dvHxEqSpvgFmCZLK+dwTtBHrWTmOKgr
9xyhr/7WnVhSSKHUiphAcm6/EOoWPdBQlnhh8tA+SIDsb0MQIKLKkhP8IvXWq2G5
5bFuKMIoTHaxBnGwJhtXgXUzebsU1wJAdeDvpAgjUqgWZp3eYsgDup+eM2ornE4v
AwuN1+qbhvMB+oQy7mM5tJ67I1Zhoh9kzmugAUVV4K/9h7NV8qXB7bhWfpHuCuWb
GlBr383pe3OYWWVScv0LXEjUvp+Vy6kILpHdQVHP2+F9FUlDnufT7xJExyeYPZ6U
X6D4Wp8CdSniJpa+/x0UVnvSuk5PcPfOS6Xp/TpRcLsT2xXE2u0Z0TVDfaTVC1Ht
DAJBGIjZVwEmszrOk4yX
=tqdJ
-----END PGP SIGNATURE-----