I just downloaded & tried Xubuntu 12.04 alpha 2, since it has a more familiar primary desktop for me and the 3.2 kernel with various video & audio fixes (some backported from 3.3, if I read the release announcement correctly.  So far just running the LiveMedia - but it gives me what I want (aside from PCLinuxOS or something other than *buntu):  It's 64 bit. It's recent (3.x) kernel. Video works without fiddling. Audio works without fiddling around.  I plug in the external jack and the internal speakers go quiet, the externals get loud.  And the mixer has the separate controls for each.

As I said, I want(ed) to like Pardus, but I can fight with it almost working some of the time, or I can go with something I don't have to fight and use the machine for what I bought it for.  I choose to use the machine.  Perhaps if Pardus or its fork survive and have a release with a 3.2 or later kernel I might try again.

Thank you for time & effort.

Had been doing that.  And getting a bunch of stuff that never seemed to make any difference.  I still don't know what change between 'Not Working' 'Working' 'Not Working Again' and 'Working Again'.

Yep, the icon was in the tray.  Ihad thought it was simply a volume control as I had previously used a different set of controls.  The strange thing, though, is that I had not shut the machine off in all this time and Clementine was also still going, though I had thought I had closed it (what is it with programs that only phony-close? Kmix, I understand for the volume control, but Clementine?) and when I tried to play an mp3 with it, I got external audio.  THough I had NOT previously in this session.  It all feel rather random rather than properly deterministic.

I had expected that sudo kmix might be pointless, but it was the only thing that actually gave any result.  Thq quiet failure is a bit offputting. No maximizing or un-minimizing, nor even an "already running" message.  Mind, it has been several years since I've used KDE as some time ago I went to Xfce for PCLinuxOS and Xubuntu (I wanted 64 bits and it was, sadly, the only one that ran at all well on a different laptop).

I wnet with Pardus on this new laptop as it was one of the few things that didn't blackscreen on startup, though I see there is a work-around and possibly a fix for that, so I might go back and try something else yet. I want to like Pardus, if it behaves randomly, I don't need that frustration if something else works deterministically.

I just tried again and (very mild) aha: TWO dashes before reinstall.

But still:

vakko@caspian ~ $ sudo pisi it kmix --reinstall -y
Password:
Total size of package(s): 346.00 KB
Downloading 1 / 1
Package kmix found in repository pardus
kmix-4.6.5-55-p11-x86_64.pisi [cached]
Installing 1 / 1
kmix-4.6.5-55-p11-x86_64.pisi [cached]
Installing kmix, version 4.6.5, release 55
Running pre removal operations for kmix
Running post removal operations for kmix
Extracting the files of kmix
Configuring kmix package
Configured kmix
Installed kmix
vakko@caspian ~ $ kmix
vakko@caspian ~ $ sudo kmix
unnamed app(1948): KUniqueApplication: Cannot find the D-Bus session server:
"/usr/bin/dbus-launch terminated abnormally with the following error: No
protocol specified
Autolaunch error: X11 initialization failed.
"
"

unnamed app(1947): KUniqueApplication: Pipe closed unexpectedly.

vakko@caspian ~ $

And no kmix launch.

First the system says kmix is already there and will not be reinstalled, which makes me wonder about the reinstall option's utility.  However, removing kmix and installing it results in.. the same thing as earlier.  User sees it do nothing, root gets the D-Bus error message.

This:

vakko@caspian Documents $ kmix
vakko@caspian Documents $
vakko@caspian Documents $ /usr/bin/kmix
vakko@caspian Documents $
vakko@caspian Documents $ su
Password:
caspian Documents # kmix
unnamed app(1157): KUniqueApplication: Cannot find the D-Bus session server:
"Did not receive a reply. Possible causes include: the remote application
did not send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken."

unnamed app(1156): KUniqueApplication: Pipe closed unexpectedly.

caspian Documents #

Exactly as I'd feared, the working external sound stopped working after a simple re-start.  And I have no idea what incantation made it work in the first place.

Also: KMixer refuses to start. The icon bounces for several seconds then *poof* -nothing-.  I recall on initial intsall that all the file permissions were messed up - I couldn't even start KDE properly.  This makes me suspicious of Pardus itself.  That should simply Not Happen and I wonder what else is amiss.  Maybe it's just current frustration, but that does seem a very strange thing.

I had thought I'd tried the various PulseAudio controls, but it is possible I missed one.  Taking a break from this, I installed the 32-bit compatibility libraries (once I was told the simple method how) and as far as I can tell that's the only real change.  Again, I could be wrong.  But coming back to the audio issue, I tried the Mixer settings again and got to the audio control panel and plugged external speakers in while the [TEST] sound was playing. It came through the speakers.  To be sure, I then started mplayer to confirm things.  I am now getting audio through the external jack.   Though it does worry a me a bit.  When things seem to suddenly just start working I always wonder if they'll suddenly stop as well.

When I try to run Firestorm, this happens:

http://www.conmicro.com/~vakko/pardus/firestorm_startuplog.txt

The first is the result of ./firestorm > firestorm_startuplog.txt  and the second block of text is what I get in terminal that didn't get sent to the file.  And yes, despite the warning text the 32-bit stuff is installed. I even did a complete just to be sure of things.

As I understand it, they can build for 64, but choose not to as they have issue with the streaming audio.  This wouldn't bother me, personally, as I prefer to listen to any stream with another program and not fight the SL viewer over it.

I'll have a bit more to post later.  Thanks to Anglo, I installed the 32-bit compatibility stuff, but evidently Firestorm wants something not included there - or else wants something else that isn't a 32-bit issue but still is not around.  I'll be grabbing the output and uploading a file to be looked at in a few hours.

I've installed the 64-bit version of Pardus as I have 64-bit hardware.  For most software, this is fine.  Alas, there is no 64-bit version of Firestorm, the Second Life viewer (or any other Second Life viewer as far as I know) and I've been able to deal with this issue in other distributions by installing 32-bit compatibity libraries.  I've looked around in the Package Manager and not seen anything that appears to give 32-bit compatibility.  Am I missing something?  Or am I out of luck?

Anglo:  Uh, and that means, what, exactly?



As I posted, I've tried it in Win7 to confirm that the hardware does work.  The hardware works.  This is a software issue of some kind.

I've installed Pardus on a new laptop with the AMD A6 processor and while it's been rather nice, though naturally taking some getting used to, I've run into a problem that I cannot find a working solution to, myself.  I have it set up to dual boot (why not triple, I don't know, Pardus seemed to miss the PCLinuxOS install... but that's another/minor issue) with Windows 7 so I can and have confirmed that the hardware is working correctly.

If I try to use the external audio (headphone) jack, I get get no signal from that socket and audio keeps playing through the internal speakers.  I have tried settings in KMixer and alsamixer and it's as if the external jack simply does not exist.  If I saw it, I would have enabled it.

As such things are oft asked for, here is the lshw listing for that laptop:
http://www.conmicro.com/~vakko/pardus/hw_caspian_2011_january_27.html

And the results of 'lsmod | grep snd' :
http://www.conmicro.com/~vakko/pardus/lsmodgrepsnd.txt

Any suggestions or is there a page I've missed and should be reading?  Thank you.