Welcome, Guest. Please login or register.
April 18, 2014, 05:05:16 AM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

  Show Posts
Pages: 1 2 [3] 4
31  Assistance / News & Announcements / Re: Pardus 2007.2 final is out on: July 13, 2007, 19:02:53 PM
Willem, it might so be... for some. However that upgrade procedure screwed up one system for me, so now I have to make a re-install.

DFI Infinity RS482 (it's a 939 socket)
AMD Athlon 3200+
GeiL Ultra-X PC-3200 512MB (BH-5)
WD Caviar 160GB Sata2

Another surprise to me was that the kernel from the stable repository was labeled "beta" which doesn't give a lot of confidence, and when it totally failed to even boot the system it didn't get better. The old kernels don't work either.

I don't post this here to make a lot of noise, but if you intend to have these kinds of overlaps similar to Gentoo or Arch it should work. A stable repository is supposed to be stable and don't make a mess out of a system which has worked perfectly up to the updates, and which to 100 % are according to the stable repository; no modified, no beta, no contributed packages just as no proprietary drivers are installed.

I don't have time for debugging and will simply be forced to make a fresh install and get this system up working before tomorrow morning; first I will rescue some data from Fedora which resides on the same system. And I who thought I would get some good rest at home tonight!  Undecided

Pardus is overall a very good system, but this failure was a disappointment.

Edit: I took the time to see if a fresh install of Pardus 2007.2 would be more successful. To make one thing clear: md5sum was correct and the integrity check while installing also passed. Nevertheless Pardus 2007.2 is either broken in relation to needed configuration for the hardware spec above, or it's not compatible in the first place. I make a separate thread about this.
32  Assistance / Configuring Pardus / What is the proper way to reconfigure X if it fails on: July 13, 2007, 01:48:01 AM
I hope I'm not annoying, but I decided to "bother" this forum with "all" questions I'm not able to find any answer to. I'm not always like  Huh? but sometimes!

Twice when doing some testing, to see how the system reacts, I've encountered X-server failures. Since changing monitor or something like that is a quite normal procedure I'm puzzled to how a recovery is solved in Pardus.

While installing Pardus a zorg script is used, right? And the service zorg is continuously used for configuration of Xorg? So what do you do if X fails? Are there any guidelines for how to rerun the zorg script? I wonder because the usual modifications of xorg.conf do squat; I've already tested several times with the exact right settings, but X still fails with a bunch of errors about non existing paths. I've changed and stopped and restarted zorg and so forth unfortunately without success or any hint about how to do this.

Since the developers of Pardus have chosen an unorthodox approach I tend to believe there's some useful documentation about this. Maybe it's just difficult to find it in English.

It's probably very simple and just me being stupid!
33  General / Wish list / An easy accesible option in Tasma to change default sound-card for the system on: July 12, 2007, 23:29:19 PM
Since it doesn't look like there's any easy configuration option in Pardus, I would suggest the developers to see what can be done. At least my question on this forum hasn't got a positive answer yet, so if such an option exists it isn't easy enough to find.

Overall: good work so far folks and I believe Pardus has a bright future!
34  Assistance / Configuring Pardus / Re: Change of standard sound-card on: July 12, 2007, 23:23:40 PM
If that's so maybe I should. For us with more than one sound-card it would be very neat.
35  Assistance / Configuring Pardus / Re: Change of standard sound-card on: July 06, 2007, 23:50:49 PM
Nobody knows?

Personally I'm usually working in Fedora, now 7 64bit, so I used to find among administration tools something down the line of "Sound-card detection", which gives me the possibility to not just detect but also set which one of them should be system default.

As you probably already guessed I feel more at home in Gnome. Nevertheless I expect to find something similar in KDE Pardus.
36  General / Wish list / Re: Package manager on: June 21, 2007, 12:37:12 PM
Perfect! When I get on that system I'll check it out. Thanks for your good work with Pardus!
37  General / Wish list / Package manager on: June 20, 2007, 13:35:03 PM
I'm thinking about folks who prefers a GUI instead of a command line, because many features of Pardus seem to be targeted at such users.

I might be mistaken, but I haven't figured out a way of getting the Package managers search function to not instantly search for every single letter I write. Of course such a auto-function could be useful but at its present stage it's more annoying than useful: one letter wait... second letter wait... and after some waiting you've managed to narrow it down to what you really searched for.

As I said, I might be mistaken in not knowing where to look for it, but such a switch for disabling auto-search would be welcomed, or if it actually exists make it more easily found.

Thanks for reading this,
38  Assistance / Software / Re: Pisi package Skype 1.4Beta on: June 19, 2007, 13:16:05 PM
I've looked through it and you're correct my files are pointing to the wrong location, so it shouldn't be a library problem.

When I wrote "it isn't too difficult to make the package" it should have been with "Wink", because it still feels a bit complicated for me to get all lines right especially since the process needs several prepared files. Honestly the documentation in English is more confusing than helping at this stage; one guide go through a lot of theoretical explanation without real practical implementation, another isn't ready, some are just a long list of commands not making any sense if you're not initiated. I'm not complaining, because I think Pardus has a lot of potential and therefore will eventually be more English oriented concerning documentation.

Let's see if I can figure out how to make use of the skype config file and point toward it as you suggest. I lack time and am usually working with Fedora at the moment, so there's a "risk" for this package to show up in a repository before I'm ready (if so I still want to take a look at the files to figure out how it all should have been done).

I'm using the Skype 1.4Beta in Fedora and even in this Beta stage it has a lot of improvements making it a candidate for the standard Pardus repository. DTMF tones are now working properly and even if configuration of sound isn't complete, it still is better and has more options than before. Sound quality also seems, eh sounds, to be better.
39  Assistance / Software / Re: Pisi package Skype 1.4Beta on: June 18, 2007, 09:04:33 AM
I get the following output:

/opt/skype/skype: /lib/libc.so.6: version `GLIBC_2.4' not found (required by /opt/skype/skype)
/opt/skype/skype: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `CXXABI_1.3.1' not found (required by /opt/skype/skype)
/opt/skype/skype: /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6: version `GLIBCXX_3.4.4' not found (required by /opt/skype/skype)

Skype sets the following requirements:
    *  Qt 4.2.1+
    * D-Bus 1.0.0
    * libsigc++ 2.0.2
    * libasound2 1.0.12

libasound2 as I understand it refers to alsa-lib, but I migjht be wrong. Whatever it looks more like it doesn't like the version of libsigc++ I have (2.0.16). Frankly I don't understand at all what "GLIBC_2.4", "CXXABI_1.3.1" and "GLIBCXX_3.4.4" mean, so I don't know even what to do.
40  Assistance / Software / Pisi package Skype 1.4Beta on: June 18, 2007, 01:26:01 AM

I've tried to make a pisi package of Skype 1.4Beta. It isn't too difficult to make the package even though the Pisi package documentation is spread all over; but I suppose the Wiki eventually will bring all pieces together.

My problem is that I can't solve the dependencies. The package itself installs correctly, but Skype still gets stuck not finding the right libraries even though I thought I got them all. It might be me thinking I've got the Pisi package right, but it's not, or something is different with this version of Skype.

Can any-one else provide me a package that work, or do you know if it soon will occur on some repository?
41  Assistance / Configuring Pardus / Change of standard sound-card on: June 17, 2007, 21:20:33 PM

I'm a bit puzzled, because I can't seem to find any GUI function included for changing of default sound-card. I have the integrated and PCI sound-card. Pardus installation process set the integrated as default, something I want to change. Logically something down this line should be included in Tasma, but when I look around in the section "Sound & Multimedia" I can't find any option for this. Changing hardware configuration here does exclusively deal with what sound architecture I choose like ALSA, OSS and so on, and even MIDI device.

I suppose I've missed something very fundamental here, or is this action really left to console and file editing?
42  Assistance / Software / [SOLVED]Is there any PISI package of Ekiga ready? on: May 15, 2007, 11:00:17 AM
I really would like to find a ready PISI package of Ekiga.

Maybe there is one in some alternative repository. If somebody knows, please, give me a link!

Appreciative of any help in this regard!

/Kimo Lee
43  Assistance / Configuring Pardus / Re: DTMF tones: is there any working solution for Pardus on: May 06, 2007, 23:41:07 PM
OK, I found a stupid but working solution... at least to some extent. It's totally manual and doesn't solve the real problem:

- since Skype creates the correct DTMF tone (I still need to test all of them) but fail to send the tone back over the Internet-connection, it's possible to simply pump up the volume and put the microphone close to a loudspeaker, and voila you get the DTMF tone to be sent and picked up!

I know, this is a clumsy and silly solution, but until anyone has a better one, preferably on a software level, I suppose I have to live with this one.  Grin
44  Assistance / Configuring Pardus / DTMF tones: is there any working solution for Pardus on: May 06, 2007, 21:57:53 PM
I'm back working on getting Pardus to work for an organization of volunteers. A previous IBM NetVista computer wasn't compatible, but a newer AMD 754 does work perfectly well besides a common acpi issue. Enough about that, now to my question:

Does anyone know about how to get DTMF tones to work in Skype? Or do you recommend another IP telephone solution?

It's crucial to find a solution. I know that the Skype developers have had a lot of problems concerning this in both linux and Mac.

Last: heads up for a good distro! It will get even better when Pardus gets a good manual in English. I think that would give the project a good boost.
45  Assistance / Bugs / Pardus works for a while and then fail to successfully boot on: February 23, 2007, 00:30:47 AM
Yep that's not difficult and I'm used to do that on slackware and I tested it now as well. Nevertheless it didn't change a thing.

I lack the time needed so I'll probably pass on this idea of using Pardus on this machine, which is a pity because it worked well and could have been easy to use.
Pages: 1 2 [3] 4

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!