Welcome, Guest. Please login or register.
April 24, 2014, 10:25:42 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
16  Assistance / Configuring Pardus / Re: What is the proper way to reconfigure X if it fails on: August 18, 2007, 21:39:04 PM
Yep, I'm talking about when X fails. I'm not lost when I'm working with Slackware, Arch and Fedora, but I've had a hard time figuring out why I can't recover Pardus in the same basic manner (probably also related to the fact that Pardus use KDE). Anyway the advantages with for example Arch is that you have full control over what you're doing; in Pardus I didn't so now I'm trying to figure out how it's designed.

I haven't solved the issue yet (I installed Fedora 64bit and haven't taken time to work on the Pardus installation any further), but I got this response which basically answers my question:


Thanks for your responses!
17  Assistance / Configuring Pardus / Re: Change of standard sound-card - REAL PLAYER on: August 18, 2007, 21:27:22 PM
OK, here's a follow up on the issue about RealPlayer not using the now selected default soundcard:

(Disclaimer: I suppose this works distribution independent, but if not I will edit this post when tested on Pardus. This works on Arch and Fedora for sure.)

1.) Edit as root "realplay" script in an editor of your choice. In Arch "realplay" is located at "/usr/bin/realplay"; in Fedora probably "/usr/local/bin/realplay".

2.) Look for these lines:
if [ -n "$LD_PRELOAD" ]; then
echo "Warning: LD_PRELOAD=\"$LD_PRELOAD\""

3.) Right after the above lines paste this:

4.) Search and make sure you have "libaoss.so.0.0.0" installed to "/usr/lib/libaoss.so.0.0.0", otherwise point to the right location. If your installation lack this library install "alsa-oss". Save and close the "realplay" script.

5.) Now open as user - not as root - the "~/.realplayerrc" (meaning it's located in your home folder). The first line you see is probably "[helix]"; anyway right below that line paste the following:

6.) Hopefully when you start RealPlayer it will now select ALSA default driver and device.

In Arch this works really well, so I hope it will be of use to my Pardus fellows. The issue with RealPlayer is that it uses the OSS driver - not a very great solution - but the "alsa-oss" package contains a program loader, aoss, which wraps applications written for OSS in a compatibility library, thus allowing them to work with ALSA. By the way: this also bring the buttons on the player interface to life!

My thanks for the tip mainly goes to shekharc. Great some have the brains I lack!
18  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 21, 2007, 19:56:59 PM
Yes I will, because there's probably no point in rolling back and forth as it is now, but I did it to be of some help to maybe understand why Pardus 2007.2 doesn't work with correct default "ati" driver.

The computer has to be up running several times a week, and is located in an office building not so far from me, so I'll find some time in my busy schedule to make another try, either going to console directly and see if I can load the "fglrx" driver or go through the install in "xorg=safe" mode and after that try to change driver. It looks like no updates have been released, at least not when checking it today.

Let's see happens and if my experience with this system can be of any help for others.
19  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 21, 2007, 17:45:54 PM
Thanks anyway Kavani for the effort! There might be crucial differences on a hardware level since your system in question is a laptop.

I did follow the suggestions given by Erkan Yilmaz and chose the "fglrx" driver instead of the "ati". It didn't get the window manager KDE to function, but the outcome was at least a bit different. Starting the "kdebase" service results in the following errors:

- can't find libXdmcp.so.6
- can't find libdl.so.2
- can't find libc.so.6

While searching through pisi I couldn't get any information but about the "libXdmcp" being installed and the others not being present, neither as installed neither in the repository, but I can't really evaluate this piece of information, since I don't know how these labraries are installed.

However I stopped "kdebase" service and decided to remove the whole kdebase package, and make a fresh install of it in case something had gone wrong. Unfortunately this didn't make any difference at all, the same missing libraries... or path.

All in all another piece of information... not that good though.

KDE isn't Gnome so here might be a lot of non common factors between Pardus and Fedora. Nevertheless - just as information - Fedora 7 doesn't suffer from this problem even though using the "ati" driver. Hence something must be possible to do to correct this issue... bug... or whatever, no matter if it's hardware or software related.

Off-topic: the person who use this system isn't so impressed when I tell him: "you see the base system works fine, it's just that we can't get the graphic-card to function". He laughs a says: "oh yes, I see it works perfectly well, it's just that it's useless!". At least he's not without a system since a configured Fedora 7 64-bit to have all the applications he had in Pardus and have access to partitions with saved data.
20  Assistance / Configuring Pardus / Re: Change of standard sound-card on: July 17, 2007, 18:06:53 PM
Maybe, but it feels a bit too pretentious to me. I'm in no way a Linux-guru!

I would like to add one important note about the asound.conf file:

- not all programs will use the default sound device, some are configured to always look for the "0"-device, which in this case doesn't change. Realplayer is such an annoying example of this (I've tried to change the file it saves in the user folder, because there's a very simple line deciding this, but for some reason it doesn't work; Realplayer simply make a new file which even makes it loose some functionality, but I'll look into it some more).
21  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 17, 2007, 16:27:15 PM
cartman, please see my response to Willem´s suggestion:

Because the RS482 has an ATI Radeon Xpress 200 integrated graphic-card

This can also be seen my original comment in another thread. I don't have any graphic-card installed in this system, if so I would have included that in the hardware specification, why it runs based on the integrated ATI Radeon Xpress 200. Besides that I clearly stated that no proprietary drivers are installed, neither for ATI neither for Nvidia [which I don't have any device for] (the bug referred to does just occur if proprietary drivers are used).

I can see why you thought about the possibility of a hardware conflict between the chipset and an eventual graphic-card, but "unfortunately" that doesn't apply to my situation.

Thanks anyway!

22  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 16, 2007, 23:15:30 PM
I tried to search Pardus bugzilla to see if a bug like this has been reported, but I can't find any exact reference to my hardware. On the other hand it might be related to some other ATI troubles reported in languages I don't understand.

I did however find a report by Erkan Yilmaz who obviously knows how to get Pardus 2007.2 to work on a system similar to mine, because in the report about something else (bug 6050) he includes the following specification:
My basic system information:
AMD Sempron(tm) Processor 3400+
ATI RS482 [Radeon Xpress 200]

Should I make a report? Or does anyone know Erkan Yilmaz and ask him about it?
23  Assistance / Configuring Pardus / Re: Change of standard sound-card on: July 15, 2007, 22:41:34 PM
That's of course a possibility Caraibes if you don't need more than one sound-card at a time. If you're running several applications and don't choose to configure something like Jack, or there's no fitting plug-in for it, you could face problems because one applications block another to access ALSA or OSS.

Hence the asound.conf file could be useful. I use it for example when using Skype simultaneously with some other ALSA or OSS dependent application. You might even record conversations this way in Audacity, or something down that line.

Fedora 7 has improved its handling of two or more sound-cards, at least I haven't run into the problems experienced in Fedora 5 based systems, when it could mess up the configuration totally when switching between different cards in the mixer. On another system though I've experienced a twist when using a USB-sound card: if the card is plugged in from boot it tend to in most cases blacklist the integrated one and select the USB-sound card as the one and only default sound-card. The easy and manual fix to this is to boot with the USB-sound card unplugged, and then plug it in when you're desktop is up running. To see these USB-sound cards in the mixer usually demands a asound.conf file as well which could be saved in the home directory.
24  Assistance / Configuring Pardus / Re: Change of standard sound-card on: July 15, 2007, 20:06:08 PM
Let's be constructive and helpful Smiley! Hence I here give an explanation of how to set a sound-card as default (if Pardus didn't configure it according to your preference):

kimtjik@df ~ $ cat /proc/asound/cards

In my case this gives the following output:

0 [NVidia         ]:      HDA-Intel - HDA NVidia
                                HDA NVidia at 0xfe020000 irq 50
1 [CMI8738MC6     ]: CMI8738-MC6 - C-Media PCI CMI8738-MC6
                                C-Media PCI CMI8738-MC6 (model 55) at 0x9c00, irq 90

As can be seen the 0 or default sound-card is NVidia, a integrated sound-card on the motherboard. I want instead C-Media, which is a Trust Digital 5.1 PCI sound-card, to be default. You do that by creating as root a simple text file called asound.conf like this:

kimtjik@df ~ $ su
df kimtjik # nano /etc/asound.conf

Then you just paste the following:

pcm.!default {
  type hw
  card CMI8738MC6
  ctl.!default {
  type hw
  card CMI8738MC6

This is based on my example, but it helps to notice what id to use for the card in accordance to the output of cat /proc/asound/cards. I used the simple text editor nano, however you can choose kwrite or anything similar.

Instead of having this thread ending without a solution, I thought this might become helpful for some until a GUI function eventually gets included in Pardus.
25  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 15, 2007, 17:07:20 PM
Here's the Xorg.0.log file. I wish you all a good read!

26  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 14, 2007, 20:11:24 PM
I've been a nice boy running a test on a different computer with the following specification:

AMD Athlon X2 3800+ (AM2)
Abit KN9 Ultra
2x 1GB Mushkin EM2 PC-6400
Gigabyte GeForce 7600GT Silent-Pipe II HDMI 256MB

I have been working in the garden today so I made it very simple: opened up Pisi package manager, searched for upgradable packages, selected all which did sum up to 303MB, applied and left to continue my work in the garden. The only hitch was that Pisi package manager become unresponsive when it had finished all tasks including updating the package tree. All in all it worked very well (still it uses a kernel labeled "beta", which I think isn't a good choice; you don't have to be like our beloved Slackware, but there's no need to push ahead and take risks [actual and how users might react]).

To sum it up: developers have to look into what went wrong what concerns ATI Radeon Xpress 200 (not a bleeding edge device), besides the continuing problem Klenje is facing. Still it worries me more that a working distro suddenly becomes nonworking, especially in view of the user base it's directed at.

I haven't solved anything, but maybe added a useful piece of information about compatibility differences.
27  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 14, 2007, 15:25:50 PM
I'll upload the Xorg.0.log today or tomorrow. I forgot my accounts so I couldn't get it uploaded yesterday.

I see what you say Klenje but even if there's some way of avoiding potential harmful dependencies, that's still not a good option, because frankly it gets to complicated to maintain for a simple user. That's something I would do on my test system, not on a system that has to be stable and be reliable. I won't be around in all eternity to fix the system.

So the bottom line is:
- if you make a first time install, OK then you could argue that if it doesn't work on your hardware, well try some other distro, because it's free
- but it's not a mature distro if "forced" upgrades breaks a already working system

If developers of Pardus don't view it as possible to make sure that the upgrade path is stable, then they should provide users with a locked repository to what ever version of Pardus did work. As it is now a re-installation of Pardus 2007.1 is a waste of time since there's no way to keep it 2007.1.

It's better for the developers to get this information about a failing release from a person like I who has a very positive view of Pardus.
28  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 14, 2007, 00:53:21 AM
I don't know if you're joking with me or not, are you? Because the RS482 has an ATI Radeon Xpress 200 integrated graphic-card.

I'll see if I can upload the Xorg.0.log somewhere so it might be checked. It's really huge and full of all kinds of errors.

29  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: July 13, 2007, 23:15:55 PM
Sorry for replying on my own post... but now I'm close to mad!!!

I thought I could get Pardus running not updated installed from 2007.1 CD and simply install some necessary software from the repository. But that's a huge NO NO! Now I got to know something new and this annoys me a lot in view of the problem I have at the moment: there's no way to use pisi to install a single package without it reporting that I need 126 dependencies! What kind of nonsense is that? Sorry for being impolite, but since I've spreading the words of Pardus for quite some time I think you should have some patience with me.

As it is now I'm busted. If I can't even install Skype or without being forced to install 126 dependencies and Audacity gives me 132, yes strangely enough both Skype and Audacity depends on a new kernel  Roll Eyes! To me this looks like developers have been overly confident in how well the system will run on all systems.

Sorry for being upset, but now it's a close call for me before I abandon Pardus. Probably not on my testing system at home though, but I will be silent and not promote Pardus before I know how this ends... a crashed system may put strains on a friendship you know! Sad
30  Assistance / Installing Pardus / 2007.1 worked very well... 2007.2 no success on: July 13, 2007, 22:39:55 PM
I made a post in the announcement section, maybe not the best place, but I thought if someone with the same hardware as mine noticed my post he/she could avoid a disastrous update process.

First the hardware specification in question:

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

This hardware has worked flawlessly from installation and onwards, based solely on 2007.1 stable. The repository has always been 2007 stable; no customized packages have been installed; no proprietary drivers have been installed.

Since Pardus seems to follow in the path of for example Gentoo and Arch, the 2007 stable obviously came to include what builds the 2007.2 stable once it was released. I hence thought it shouldn't change anything dramatically and as far as I can understand at this point there's no exclusive repository for 2007.1 alone. Nevertheless the update made the system unable to boot. Suddenly all kernels were useless and I couldn't even get to a command line, so the system was pretty messed up.

Here I would like to ask one thing: if 2007.2 is supposed to be a stable release, why was the kernel *.86 labeled "beta"?

I downloaded 2007.2 stable release and burned it to a disk to see whether it was the pisi package system that got it broken. Here comes the twist: 2007.2 can only boot and install on the system above with the added parameter "xorg=safe", but from there it's at least for me impossible to configure it use anything but VESA 800x600. Appropriate changes in xorg.conf doesn't just crash the X-server, but strangely enough it gets totally unable to boot. Very confusing.

The point of having Pardus on the system in question was that it should be easy for the owner to maintain. 2007.1 gave the impression that it was a good choice. Now I'm scared because without a doubt either the new kernel or some modules of 2007.2 aren't what they were in the 2007.1 release. If I can't "lock" the repository to the 2007.1 release - not how Pardus works as I see - I can never allow the system to be updated ever again... or I need to choose another distro.

If any of the developers has access to system based on the RS482 chipset I would appreciate if they could look into it.

Thanks for your time!
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!