LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-30-2010, 04:20 AM   #1
CoolC
LQ Newbie
 
Registered: May 2010
Location: Haarlem
Distribution: Slackware64 13.1
Posts: 8

Rep: Reputation: 0
Unhappy Problems after upgrade 13.0 -> 13.1


Hello! I recently tried upgrading for the first time in a decade or so (bad old experiences of upgrading redhat and windows caused me to always wipe earlier install). The upgrade itself completed without problems and I am like many others most happy with the overall quality of this latest release.

Unfortunately I've run into one major and a couple of minor issues:

The major problem is that my serial port Wacom Intous tablet doesn't work any more. I have the same config in xorg.conf as I used in 13.0 and neither kernel nor X seem to have any problems loading the driver/module. I have the xf86-input-wacom package included with the install. I use a custom kernel compiled from the 13.1 sources, with the same config as I used with 13.0 when my tablet was working.

This is the X config:
Quote:
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/ttyS0"
Option "Type" "stylus"
Option "Suppress" "4"
Option "Mode" "Absolute"
# Option "Threshold" "number"
Option "KeepShape" "on"
Option "BottomY" "7938"
Option "Twinview" "horizontal"
Option "TVResolution" "1680x1050,1280x1024"
Option "ScreenNo" "0"
EndSection
'

I get this error in Xorg.0.log:
Quote:
(**) Option "Device" "/dev/ttyS0"
(**) Option "SendCoreEvents"
(**) stylus: always reports core events
(**) Option "Mode" "Absolute"
(**) Option "Suppress" "4"
(**) Option "TVResolution" "1680x1050,1280x1024"
(**) Option "ScreenNo" "0"
(**) Option "KeepShape" "on"
(**) Option "BottomY" "7938"
(**) Option "Twinview" "horizontal"
(II) XINPUT: Adding extended input device "stylus" (type: STYLUS)
(**) Option "StopBits" "1"
(**) Option "DataBits" "8"
(**) Option "Parity" "None"
(**) Option "Vmin" "1"
(**) Option "Vtime" "10"
(**) Option "FlowControl" "Xoff"
(WW) stylus: Waited too long for answer (failed after 3 tries).
(WW) stylus: Waited too long for answer (failed after 3 tries).
(WW) stylus: Waited too long for answer (failed after 3 tries).
(II) stylus: serial tablet id 0x90.
(EE) Couldn't init device "stylus"
(II) UnloadModule: "wacom"
The tablet is not listed in /proc/bus/input/devices so I guess that's why X cannot initialize it but why is it not found?? There is nothing wrong with it physically. It was working fine prior to the upgrade, it's still plugged in fine and still detected in Ubuntu and Windows.

My minor problems are related to KDE.

1) I get kmix popping up at every login / startx, even when it's configured not to start. I've even tried disabling the "restore volumes at login" and it still pop up. Happens for both root and my user.

2) I have the taskbar as a separate panel at the top of my screen and used to have it set to auto-hide. After the upgrade however the panel interfere with programs set to fullscreen - the panel activate when moving the mouse in the upper part of the screen even if the program is on top of the panel. In effect it disables any mouse interaction in the upper 40-ish pixels of the program. I tried the different window-managing options like focus stealing prevention etc. but nothing seem to work except changing the panel to "windows can cover". It's an acceptable workaround but if possible to resolve the above I would like to return to auto-hide, if nothing else because it looks better

3) My final and smallest issue is actually not since the upgrade, I had it on 13.0 as well. The names of the workspaces / virtual desktops (we're still talking KDE) seem to reset at each login. The first one is always named "1" and the rest is called "Workspace 2", "Workspace 3" and "Workspace 4". I can change it temporarily but always reset on login.

If these 4 things can be fixed, I think I'll be running a perfect, flawless computer environment!
 
Old 05-30-2010, 05:39 AM   #2
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,845

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
Serial tablets seem to have lost support in the new xorg server. However, there is a patch for the xf86-input-wacom driver. You can find it scrolling down a bit here:

http://sourceforge.net/mailarchive/f...xwacom-discuss

You will have to recompile when done.
 
1 members found this post helpful.
Old 05-30-2010, 02:14 PM   #3
CoolC
LQ Newbie
 
Registered: May 2010
Location: Haarlem
Distribution: Slackware64 13.1
Posts: 8

Original Poster
Rep: Reputation: 0
Thank you! It looks like that's indeed the fault. Unfortunately I was still unable to get it working.

I compiled and installed with a SlackBuild file. Tried both sets of patches I found in the thread you linked and both give me the same error in xorg.log:

Quote:
(II) LoadModule: "wacom"
(II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so
dlopen: /usr/lib64/xorg/modules/input/wacom_drv.so: undefined symbol: gWacomSerialDevice
(EE) Failed to load /usr/lib64/xorg/modules/input/wacom_drv.so
(II) UnloadModule: "wacom"
(EE) Failed to load module "wacom" (loader failed, 7)
In the thread you linked it looks like it's still being modified for inclusion back into the driver so maybe I have to wait a while...
 
Old 06-01-2010, 02:13 PM   #4
CoolC
LQ Newbie
 
Registered: May 2010
Location: Haarlem
Distribution: Slackware64 13.1
Posts: 8

Original Poster
Rep: Reputation: 0
Question

I solved my KDE problems 1 & 3 by erasing my .kde dir and starting over with configuring the desktop... not an ideal solution but now those issues are gone anyway.

Now that I've run the new system for a while I've discovered two new problems I would like some help with;

A) My dvd-drive is detected twice at boot, so I get a duplicate drive. It can be temporarily fixed by ejecting the drive and injecting again. Then only one drive is seen, until the next boot. I guess udev or HAL is the culprit, but which config file specifically control cd/dvd drives? I've searched and cannot find...

B) Logging out / quitting KDE takes MUCH longer as a user then as root. Something like 2 seconds as root compared to almost a minute for users.
 
Old 06-01-2010, 05:47 PM   #5
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843Reputation: 843
Quote:
Originally Posted by CoolC View Post
A) My dvd-drive is detected twice at boot, so I get a duplicate drive. It can be temporarily fixed by ejecting the drive and injecting again. Then only one drive is seen, until the next boot. I guess udev or HAL is the culprit, but which config file specifically control cd/dvd drives? I've searched and cannot find...
Delete /etc/udev/rules.d/70-persistent-cd.rules and reboot your computer (the file will be automatically regenerated upon reboot). That *may* solve the issue entirely...if not then you'd need to further investigate how udev and HAL are detecting your drive...
 
Old 06-03-2010, 10:34 AM   #6
CoolC
LQ Newbie
 
Registered: May 2010
Location: Haarlem
Distribution: Slackware64 13.1
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by T3slider View Post
Delete /etc/udev/rules.d/70-persistent-cd.rules and reboot your computer (the file will be automatically regenerated upon reboot). That *may* solve the issue entirely...if not then you'd need to further investigate how udev and HAL are detecting your drive...
Argh. That only made it worse... now I've got three drives! Either that, or they are breeding!

Anyone else have a suggestion?

As a last resort I'm thinking of exkluding the drive from udev and going back to good ol' fstab config. But i'm not sure how to turn off udev handling of the drive.
 
Old 06-03-2010, 11:56 AM   #7
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by CoolC View Post
Argh. That only made it worse... now I've got three drives! Either that, or they are breeding!

Anyone else have a suggestion?

As a last resort I'm thinking of exkluding the drive from udev and going back to good ol' fstab config. But i'm not sure how to turn off udev handling of the drive.
Do you mean that after you rebooted, there are now three entries in /etc/udev/rules.d/70-persistent-cd.rules?
 
Old 06-03-2010, 02:40 PM   #8
CoolC
LQ Newbie
 
Registered: May 2010
Location: Haarlem
Distribution: Slackware64 13.1
Posts: 8

Original Poster
Rep: Reputation: 0
I've done some more testing now and I'm pretty certain the problem lies only with KDE and it's handling of devices.

I only see one device with lshw. I see only /dev/hda, no other similar devices. Also only have one mount-point in /media. I've enabled the dvd in fstab now (I decided I like a single mountpoint better anyway) and it made no difference at all. Still have multiple devices in KDE.

So, I tried a bit more and inserted different discs after each other, rebooted after a while. Both before and after reboot multiple discs can be seen as "inserted" at the same time! And it doesn't matter which one you try to mount, all works, but only one at a time. If you try to mount more than one an "unable to mount" error is unsurprisingly produced. When mounted the actual disc content is seen. When using fstab all the "virtual devices" correctly use the same mountpoint. Once in a while after ejecting or inserting a disc the list is cleared and only one device is seen (but two are seen again if you continue and insert a new disc).

I'd say it looks like KDE is incorrectly retaining the old data instead of clearing when inserting a new disc. Also, it must be on harddrive since it survive a reboot. Still don't know how to fix it though.

Last edited by CoolC; 06-03-2010 at 02:44 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
upgrade problems edgjerp Ubuntu 1 04-30-2008 06:37 AM
upgrade to 10.2 - problems RonS1938 Slackware - Installation 8 09-02-2006 01:47 AM
Upgrade Problems?! unihiekka SUSE / openSUSE 3 07-07-2006 11:25 AM
problems after upgrade giraf Debian 1 02-16-2006 08:23 AM
X problems after upgrade mc_03 Slackware 5 03-30-2004 08:06 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:51 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration