Search:

Well, then. That's too bad. I've got no idea, why restarting X should work, but nothing else will quite do it.

I'd say, do the full update and investigate more. One question, though: why is it you...

(On a side note: please attach the full logs in the future, not the diffed output; having both files we can use our own tools to diff/view them.)

Please compare one more time the kernel module on...

Which system? Remember, you only check for the driver version to see if it differs between the two systems. If it is the same version, we may pretty much ignore the driver.

Do you do anything before restarting X? Do you issue "xinput set-int-prop" before restarting X every time?

In any case: check the Xorg.0.log right after booting and right after restarting X. What...

Okay, good.
You can check the driver version by searching for "wacom" in the kernel log:


dmesg | grep -i wacom

Explanation: the output of dmesg is piped to the filter program grep which will...

Well, the very fact that you've got something to attach shows that the files are different -- and they probably should not be. I've only checked the last attachment, the differences in...

What do you mean when you say "it didn't work"? The steps I outlined only help you to understand if our assumptions are correct.
Do the configuration files of the two systems differ? Are there...

I have to admit that I lost the overview. You've copied things here and there which attributes to a lot of confusion.

Let's start all over again, shall we?

These are the known facts:
1. the...

The live CD is a complete system, including all configuration files. If the touchscreen does work when the live system is running, you should investigate the /etc directory. I'm not sure if 9.10...

You say it worked before rebooting. I assume you didn't play with the settings after completing the install. Please boot the live CD and check if it works. If it does, then check out the xorg.conf...

For those who wouldn't like to switch to a tiling window manager (for obvious reasons) could use the python script "stiler" --> http://aur.archlinux.org/packages.php?ID=25038

You can bind the...

Open the file /boot/grub/menu.lst with your favorite editor. Somewhere in the middle of the file there should be a line that starts with "kernel /boot/"... This is the kernel line that I meant. There...

You're welcome!
I'm not so familiar with Ubuntu anymore since I moved to Arch, hence my answer was a bit blurry...
If you ever feel like learning more about configuration of your system just the...

I'm on Arch64 and use Openbox without GNOME. To start Openbox I had to add following line in ~/.xinitrc


exec openbox-session

If there are any other lines starting with "exec" then just add #...

I tried to do so several times, but there was a problem with the server for quite a while. Will try it again now.

Edit:
I still get a database error when I try to edit the title and submit. :(

This was simple: the daemon script /etc/rc.d/smbnetfs was moving error messages to /dev/null. By removing the piping to /dev/null in the script (after making a backup) I could see the error and the...

Hi,
I'm running Arch Linux on a notebook and want to connect to a server running FreeBSD. In the LAN there are only Windows PCs which all have access to the shared directories on the server. I may...

I have had the same problem until yesterday when I decided to boot with the kernel option "acpi_osi=" (without the quotes). This will clear the OS identifier string that is sent to the BIOS normally...

The sudo command cannot pipe the standard output to a file. Try to use "tee" (Wikipedia: http://en.wikipedia.org/wiki/Tee_(command)) in the following way:


echo value | sudo tee file

"Good news, everyone..."

Playing with the options explained here http://www.columbia.edu/~ariel/acpi/acpi_howto.txt I finally managed to get it done!

I added the boot option acpi_osi= to my...

I'm having similar issues. In my thread I described all methods I tried. Could be that one of these works for you. None worked for me, though...

http://ubuntuforums.org/showthread.php?t=922401

...

Does anyone of you know another way to single down the cause of this problem to a certain source? Or can I obtain the source of the acpi packages somewhere?

Is there anything else I could provide as info? Or a workaround that I haven't mentioned yet? That's the only issue left on my laptop.

I used method 2 but I just entered wrong key codes. So just now I performed method 1 again and it worked like a charm! Now I can adjust my volume without locking up the X-session.

Thanks a lot!...

(Actually, Chinese is a very simple language. No grammar to learn, I picked it up in half a year or so. But reading takes a bit longer...)


我用的是海尔a680，也是sis...