Havin_it

Had a look at my syslog from this morning's boot (this is before changing xorg.conf any further). Couple of pertinent items:

Apr 28 14:16:32 localhost kernel: mice: PS/2 mouse device common for all mice 
Apr 28 14:16:32 localhost kernel: input: AT Translated Set 2 keyboard on isa0060/serio0 
Apr 28 14:16:32 localhost kernel: input: PS/2 Generic Mouse on isa0060/serio4

...

Apr 28 14:16:32 localhost kernel: usb 2-1: new low speed USB device using uhci_hcd and address 3 
Apr 28 14:16:32 localhost kernel: usbcore: registered new driver hiddev 
Apr 28 14:16:32 localhost kernel: input: USB HID v1.10 Mouse [Wireless Mouse Wireless Mouse] on usb-0000:00:1d.1-1 
Apr 28 14:16:32 localhost kernel: usbcore: registered new driver usbhid 
Apr 28 14:16:32 localhost kernel: drivers/usb/input/hid-core.c: v2.0:USB HID core driver 
Apr 28 14:16:32 localhost kernel: usbcore: registered new driver usbmouse 
Apr 28 14:16:32 localhost kernel: drivers/usb/input/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver 
Apr 28 14:16:32 localhost kernel: ts: Compaq touchscreen protocol output 
Apr 28 14:16:32 localhost kernel: usbcore: registered new driver usblp

Don't know what if anything can be determined from this, but I'll look again after I've applied the changes in your config, ac.

Uh-oh. Feel like I just went into hyperspeed reading that lot

Given the issues with ksynaptics, I can't help thinking the driver rather than the XOrg might be the real problem.

Anyhoo, kernel-building is a little out of my league at the mo', but I guess if I could establish that that's what I'd need to do (without actually doing it), I could admit defeat and move on with my life. But for now I'll try a bit more config hacking just for the hell of it....!

Never thought of checking lsmod for synaptics ... will have to check on that too.

Thanks ac, looks like good info - will try out the configs shortly (might have a look at this nano first ;) ) and report.

Can I ask a couple of clarifications/expansions on the above?

1 - You mention both devices use "driver" "mouse" under XOrg but the config shows otherwise. Are you currently back with XFree86?

2 - My config file doesn't have the '-4' suffix - is this relevant, if so how?

3 - Do you know what the config entries for the pad mean? I guess the '-Edge' ones are defining its area, but what about FingerLow/High, ZAxisMapping, SHMConfig, VertScrollDelta? Can't find man pages for the driver so I'm a bit lost on it all.

Thanks again for the input, I _really_ appreciate it.

PS - Do you work on MEPIS? :deal: I have heard of it as "a Knoppix that doesn't suck for HD install" - accurate? I've briefly tried Knoppix 3.7 on this box (not installed) but I don't recall having better results with the pad. Might have another go, to refresh my memory.

Well, just learned the hard way that the "SynapticsMouse1" can't be made "CorePointer" - X puked on that boot saying there was no Synaptics pad detected or something.

God I hate Vi.

Okay, here's the new conf I hacked together from my old one and the one ac_dispatcher posted in the linked thread.

Section "InputDevice"
   Identifier "Mouse1"
   Driver "mouse"
   Option "Protocol" "ExplorerPS/2"
   Option "Device" "/dev/mouse"
   Option "ZAxisMapping" "6 7"
EndSection

Section "InputDevice"
   Identifier "SynapticsMouse1"
   Driver "synaptics"
   Option "Protocol" "ImPS/2"
   Option "Device" "/dev/psaux"
   Option "ZAxisMapping" "4 5"
   Option "MaxSpeed" "0.12"
   Option "MinSpeed" "0.06"
   Option "BottomEdge" "4200"
   Option "SHMConfig" "on"
   Option "LeftEdge" "1700"
   Option "FingerLow" "25"
   Option "MaxTapTime" "180"
   Option "MaxTapMove" "220"
   Option "FingerHigh" "30"
   Option "VertScrollDelta" "100"
   Option "UpDownScrolling" "on"
   Option "TopEdge" "1700"
   Option "RightEdge" "5300"
   Option "AccelFactor" "0.0010"
EndSection

...

Section "ServerLayout"
   Identifier "layout1"
   InputDevice "Keyboard1" "CoreKeyboard"
   InputDevice "Mouse1" "CorePointer"
   InputDevice "SynapticsMouse1" "AlwaysCore"
   Screen "screen1"
   Screen "screen2" RightOf "screen1"
   #Option "Xinerama"
EndSection

Both mice are still working at this stage, but ksynaptics is still dead. The Hardware panel is still showing one mouse only, but now it's a PS/2 Generic Mouse.

It doesn't seem to matter what I do to the xorg.conf, but the synaptics configs there are still over my head so I can't be sure of anything. Can anyone help? Ideas about where the problem might lie would be great.

Thanks to ac_dispatcher, Item #1 is nailed. Adding the boot option above has restored sensitivity to the pad so I don't have to jab it at finger-breaking force before achieving a click. Progress!

Still no joy with the scroller, though. Is there anyone with a working scroll-function on their pad that can post their xorg.conf for comparison?

All other symptoms/files/readouts described above are unchanged, BTW. Anything else I should be looking at?

EDIT: The last line was not true. The second config (the ALPS one) is now gone from the xorg.conf, so I'm gonna try replacing it from the backup, plus to change the device reference to /dev/psaux. Pray for me...

Okay guys, I DL'd the driver package at

http://web.telia.com/~u89404340/touchpad/

and I'll install it and see what happens. Backing up my xorg.conf and removing the USB mouse in case things go haywire.

EDIT: No, hang on. This is just the same driver I've already got installed, isn't it? The driver (iif I understand) is already there at /usr/X11R6/lib/modules/input/synaptics_drv.o

So I'll just go ahead and add the boot line above and see what happens.

Thanks ... is that the same if using GRUB?

UPDATE:

I have had a small sliver of progress with this. I dropped to shell (Ctrl+F1) and used Fn+F5 to do the screen swap. This, actually works! Display swaps to the TV, and stays there.

UNFORTUNATELY: If I then Ctrl+F7 back to where I was, it bounces back to the LCD. So still not much hope of playing any video through it.

It does lend weight, I think, to the idea that correct XOrg configuration is what's missing. How I wish there was a readable (to the average idiot) guide to xorg.conf stuff. The whole X server paradigm's just alien to me as a Windows refugee...

Still hoping for any tips on what a config for TV output *should* look like. I can post the current stuff if it's any help.

Maybe the problem is... that it isn't a Synaptics touchpad? (It's an ALPS)

And here's some information about device files, if it helps:

/dev/mouse is a symlink to /dev/input/mice

There's also /dev/mouse1, which is another symlink to /dev/input/mice

/dev/input also contains (as well as 'mice') the files mouse0 and mouse1.

Please help me make sense of this, I've no idea which bits are wrong or odd because it's all 'odd' to me!

Hi, thanks for the reply.

I installed the ksynaptics package and opened it up, but don't like what I see. All the controls are greyed out, and in the 'detected information' panel I have the following:

XFree86 version: any

Synaptics driver version: none

bad - no driver installation detected!

bad - X Shared memory unaccessible!

That can't be good.

When I go to drakconf > Hardware > Mouse, the mouse is defined as Universal > Any PS/2 & USB Mice. If I change it to Synaptics Touchpad, both the mouse and the touchpad lose control, any use of either kicks the cursor to the corner of the screen and just jerks around crazily. (This happens with or without the USB mouse connected) So that's not so good.

I also looked in Hardware > Hardware and what's defined under 'Mouse' is, oddly enough, this: (copied from right pane)

Connection
Bus: ‎isa

Vendor ID: ‎0002

Device ID: ‎0008

Features
Emulated wheel: ‎No

Misc
Vendor: ‎

Description: ‎AlpsPS/2 ALPS TouchPad

Module: ‎mouse0

That's it - just one entry, for a touchpad.

Just for fullness, these are the mouse entries from /etc/X11/xorg.conf (which is a symlink to XF86Config):

Section "InputDevice"
   Identifier "Mouse1"
   Driver "mouse"
   Option "Protocol" "ExplorerPS/2"
   Option "Device" "/dev/mouse"
   Option "ZAxisMapping" "6 7"
EndSection

Section "InputDevice"
   Identifier "SynapticsMouse1"
   Driver "synaptics"
   Option "Protocol" "auto-dev"
   Option "Device" "/dev/input/mice"
   Option "MaxSpeed" "0.12"
   Option "MinSpeed" "0.06"
   Option "BottomEdge" "4200"
   Option "SHMConfig" "on"
   Option "LeftEdge" "1700"
   Option "FingerLow" "25"
   Option "MaxTapTime" "180"
   Option "MaxTapMove" "220"
   Option "FingerHigh" "30"
   Option "VertScrollDelta" "100"
   Option "TopEdge" "1700"
   Option "RightEdge" "5300"
   Option "AccelFactor" "0.0010"
EndSection

I note that there's a lot more config information for the touchpad entry, though I'm not sure what that means.

Can anyone figure out what's going on?

'ning all,

This troublesome device is attached to a Toshiba Satellite A30-104 (sadly, a model not covered by the Linux-laptop sites) and, while it does work, it's temperamental.

Item 1: Just updated Mdk 10.1 to the new kernel 2.6.11-6mdk from thac's RPMs. Since then, the pad seems less responsive both to dragging and tapping. It feels like the sensitivity went down by about 40%, which is baaaaaad. (On a sidenote, I use a USB wireless mouse which doesn't seem affected. It's always worked well, and even in tandem with the touchpad which I hear often doesn't happen.)

Item 2: In Windows the pad has a vertical scroll-wheel functionality when dragging at the right-hand side of the pad. This is really useful, and I'd love to be able to use it in Linux too if it's supported.

So basically I'd like to learn how to configure this device. I guess I am off to a good-ish start if it works at all, but I don't know the first thing about what to do next. I've only found a couple of topics here about touchpads and XOrg configuration seems to be involved, but what does it all mean?

Any noobie guides and detailed info about this configuration task gratefully accepted.

SORTED!

Painfully simple actually. I just went into RPMDrake (had forgotten 'urpmi kernel' wasn't enough information!) and installed the kernel and source. Sound instantly restored, and ndiswrapper perfectly non-b0rked!

Thacs again, thank ;)

I've found further evidence of problems, after a look at the ALSA website FAQ. One of the first things one is told to look at is the files

/proc/asound/version

/proc/asound/cards

These files are actually empty! That can't be good. I guess I need to sort out this kernel issue first. Can anyone advise on how to do that?

Crapola. I can't even get WINE up and running. I can install, but the first thing I was to install - IE6 - fails because it can't get a net connection.

Not loving this so far. I'm gonna uninstall everything and await guidance, this one is beyond me.

Anyone?

Hi, thanks for replying!

Winetools doesn't seem to want to install for me. URPMI complains about unsatisfied Xdialog, the version of Xdialog in my main repo doesn't satisfy it. Any idea how to deal with this?

'ning all,

I tried out Crossover Office v3 a while ago, and found Dreamweaver MX and Fireworks installed perfectly. I never got around to using them heavily, or installing the other Studio MX apps, but the experience was positive.

Now I'm looking to setup the whole Studio - DW, FW, Flash and Freehand - as part of my ongoing "can I live without Windows" experiment. Before I roll up my sleeves and get stuck in, I'm appealing for any advice that might save me some wasted effort.

CXoffice made installing everything really easy, and if I understand correctly the graphical installer (including the invaluable 'you-need-this-first-here's-where-to-download-it' tips) are what distinguishes it from the basic WINE. Is this correct / is there more?

I'm quite prepared to cough up for this proprietary app (it's not too dear really) if it saves me weeks of config hell. In your experience, is that what awaits me with WINE?

Also, I came across a program called Xwine, installed it and it seems to run OK though I've not really done anything with it (in case doing so makes later jobs harder). Does anyone have feedback about the usability/stability of this app?

I hope this isn't too generalised - but I guess that's the nature of it, general best-practice info seeking. Hope someone can 'contribute' (pun not intended - I won't be looking to install that hunk o' sh*t)

[moved from Software by spinynorman]

Okeydokey. Kernel-source too?

(Wanna be cautious here because I use ndiswrapper and the kernel-source is a factor in that. Don't want to lose network at a crucial stage...)

EDIT: I went ahead with 'urpmi kernel' but get 'Everything already installed.' I am currently using the warwick Uni mirror - might try switching to your main repo and see if that helps.

Hi all,

When I did the first upgrade to KDE3.4 using thac's RPMs, ALSA apparently was upgraded to 1.0.6a and at that point I lost sound.

I've continued to upgrade from thac's repository (plus the usual MDK ones) ever since, and am currently up-to-date, and the problem remains.

thac told me that he now has ALSA at version 1.0.8, and indeed when I checked, all the packages with alsa in the title are version 1.0.8.x - yet, on startup, it still shows:

Starting ALSA 1.0.6a....[OK]

Any idea how I can troubleshoot this? I remember when I first installed MDK 10.0 CE I didn't have any sound for ages, but I learned that a simple settings change in KMix fixed it. Unfortunately, when I look at KMix now I haven't a clue what it all means.

Thanks in advance...

Haven't been in Linux for about a week (had piles of work to do on Windows) but will go try immediate! Thanks for the tip, thac. Hope that sorts it.

I did - nobody replied :(

This was at the time of the first round of 3.4 RPMs, I posted in this thread about it too but nobody answered that either :(

I thought this was the place to report issues with these RPMs?

Apart from the other issues encountered, I have lost sound with ALSA 1.0.6a.

Does anyone know how to fix this, or if there's a way to roll back to the earlier ALSA? This is really annoying

I seem to recall from Mandrake install-time that there's a package already called 'git'. Can anyone confirm?

Well, it would be a shame if he didn't after all these shenanigans.

I must admit, after reading more of the backstory to this (thank you El Reg), I have a tad less sympathy for McVoy, though probably a bit more for Linus.

The business reasons McVoy cited for pulling the plug (which are not without merit of course, refer to my previous) would probably have come to pass soon anyway, and it becomes clearer that Linus was well aware of this as he was 'looking' for an alternative solution. He wanted to jump before he got pushed, which Tridgell ended up doing before McVoy got around to it. I can understand his anger, both on those grounds and because McVoy and he are childood friends, but yes, his friendship may well have blinded him to the problems he was storing up when Larry 'sold' him BK in the first place.

Still not wholly sure how I feel about Tridgell's actions. I concede that he had the right to do this (hey, I like Samba too) but I do think he knew full well how McVoy felt about him doing it which makes it a morally ambiguous move.

I'd like to know, what are the benefits of interoperability with BK anyway? (DISCLAIMER: I know slightly less than zero about the full spec of BK)

If no OSS community would willingly use it by default (which seems to be the consensus around here), what circumstances remain in which there are any proprietary BK servers worth talking to? If a proprietary-software business uses it, because they like the improvements over whatever OSS alternatives exist, surely they're gonna shell out a few bucks more to volume-license the same company's clients under a whole-bundle discount and get the support and guarantees that a business needs?

Okay, what's the bigger picture I'm not seeing this time?