Welcome, Guest. Please login or register.
April 17, 2014, 13:17:11 PM
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
1  General / The Pub / The Humble Indie Bundle - support Linux friendly game developers on: May 05, 2010, 10:03:18 AM
I've not been around in a long time, since I got consumed by Arch. I give Pardus a spin once in a while even though becoming a very different user to how it was a couple of years ago.

No to the title. Are you interested in seeing more games developed for Linux? If so check out this offer: http://www.wolfire.com/humble

From cute to horror games. I did notice that the Penumbra download included a discount for the whole Penumbra collection and also one for pre orders of the their next project Amnesia.

Prove that we use Linux because it's better computing not because we're tight-fisted!
2  Assistance / Bugs / Re: Tasma was removed and KMixer seems to be gone on: November 24, 2007, 19:42:01 PM
The "it --reinstall" switch worked just fine. What this proves however is that there's a bug somewhere affecting an upgrade from 2007.2 to 2007.3. Not just KMix returned but other packages from the kdemultimedia package as well. No big deal, but it could be a show stopper for some.

Another thought: it surprises me to see that Skype still is of such a old version. Since 2007.3 is announced with fanfare I believe it would have been good to make sure such applications like Skype were up-to-date. The version of Skype in the repository has several flaws which has been corrected in later versions. Current Beta version 2.x, with support for webcams, works very well.
3  Assistance / Bugs / Re: Tasma was removed and KMixer seems to be gone on: November 24, 2007, 01:08:25 AM
That's sudo pisi it --reinstall kdemultimedia Also you can check package errors by sudo pisi check kdemultimedia
Perfect! I'll try that next time I go "visit" the computer in question.

I got some manual for CLI use of Pisi - yes I prefer CLI - but that option you suggest wasn't there. Probably should have stayed a couple of more minutes, so I could check whether a man-page would have explained it.

About repos: just standard Pardus repos.
4  Assistance / Bugs / Re: Tasma was removed and KMixer seems to be gone on: November 22, 2007, 20:46:59 PM
I had 5 minutes to my disposal today, so I went to where the computer in question is and tried to get KMix back. From command line I tried to figure out how to reinstall kdemultimedia (KMix should be a part of that package), but couldn't find any switch for it. Upgrade doesn't work, because Pisi simply returns a message about the package already being installed.

There is some switch to force an upgrade, isn't there? No system is infallible, so I hope there is. Remove kdemultimedia will for sure result in removing a whole lot of dependencies, which I could do, but it's so unnecessary hence leaving that as a last option.
5  Assistance / Installing Pardus / Re: 2007.1 worked very well... 2007.2 no success on: November 20, 2007, 12:14:46 PM
OK, it's time to make a closure of this thread. What's new?

I've had Pardus running without X for several months. Been thinkering from time to time, but didn't have any success in tracking down the problem. Because of the new Pardus release I thought it could be worth testing whether new xorg.server and driver packages would solve the issue. It did, or at least party, depending on what driver you prefer.

The "ati" driver behaves a bit odd still and doesn't accept anything else but 1024x768 (native resolution 1280x1024), but will still let the background have full resolution but within it setup a smaller monitor with the panels, if you understand what I mean. Besides that gamma and colors was far off. I didn't feel for wasting much time on it.

"fglrx" though works perfectly well. So I settled for that as for now. This system doesn't have to be a super secure only open source system anyway.

The bugs are nearly gone. I'm not a developer so I don't know whether newer versions of xorg.server combined with new drivers were the full answer.

6  Assistance / Bugs / Tasma was removed and KMixer seems to be gone on: November 20, 2007, 12:02:18 PM

Here I am again. I left Pardus running without X for some month. Yep, that's great fun and some nostalgia or flash-back of old times. I'll add specific information to another thread about X.

I made a system upgrade from command line yesterday, so now it's up-to-date with the new release. Here's some odd observations:
- Tasma was removed but could be reinstalled from the repository
- KMix is totally gone and I can't seem to find it in the repository either (I'm probably wrong here but after 15 minutes without being able to find it I gave up)
- Sound had to - that's nothing new really - be configured by "alsaconf" once more and then by "alsamixer" be adjusted

Nothing of real importance, but to get KMix back would be pretty nice.
7  Assistance / Installing Pardus / Re: problem with install-suggest pardus modify process on: September 04, 2007, 18:23:32 PM
Of course you could chain load, but personally I prefer to not do that. I'm not in such a hurry, but it doesn't look neat and I like when it loads straight ahead instead of it jumping from grub to grub.

Arch is possibly the one that change kernel the most, but on the other hand it nukes the old image and remakes it without changing its name, hence no need to edit menu.lst. For the others I don't upgrade kernels that often so some quick editing of the main grub once a month isn't a bit deal.

But that's me...
8  Assistance / Installing Pardus / Re: problem with install-suggest pardus modify process on: September 04, 2007, 16:55:28 PM
A tip if not certain about what to write in menu.lst:

If you already have grub installed on MBR of hda/sda there's no need to overwrite it as long as it's "alive", I mean it's controlled by an existing operating system.

If you already have another Linux system, which installed grub to MBR, then the clip & paste option is to simply let the other systems install grub on their own root partitions. In that way grub will be updated every time you change kernel, and you get an output of what to add to the grub residing on hda/sda. Like this:

- Mount the partition controlling grub on hda/sda (or the corresponding MBR you're using)
- cd to the menu.lst (boot/grub/menu.lst)
- open menu.lst in an editor of your choice
- now open up /boot/grub/menu.lst on your Pardus installation
- simply copy & paste the lines from Pardus' menu.lst to menu.lst controlled by grub on hda/sda


Pardus /boot/grub/menu.lst resides at sda10 and looks like this:

default 0
background 10333C
timeout 10
splashimage (hd0,9)/boot/grub/splash.xpm.gz

title Pardus 2007.2 []
root (hd0,9)
kernel (hd0,9)/boot/kernel- root=/dev/sda10 video=vesafb:off mudur=language:en quiet resume=/dev/sda5
initrd (hd0,9)/boot/initramfs-

title Pardus 2007.2 Beta []
root (hd0,9)
kernel (hd0,9)/boot/kernel- root=/dev/sda10 video=vesafb:off mudur=language:en quiet resume=/dev/sda5
initrd (hd0,9)/boot/initramfs-

title Pardus 2007.1 []
root (hd0,9)
kernel (hd0,9)/boot/kernel- root=/dev/sda10 video=vesafb:off mudur=language:en quiet resume=/dev/sda5
initrd (hd0,9)/boot/initramfs-

title Pardus 2007.1 Felis chaus
root (hd0,9)
kernel (hd0,9)/boot/kernel- root=/dev/sda10 video=vesafb:off mudur=language:en quiet resume=/dev/sda5
initrd (hd0,9)/boot/initramfs-

PClinuxOS resides on sda1, and controlles grub installed to mbr on sda, and looks like this:
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/usr/share/gfxboot/themes/pclinuxos/boot/message
default 1

title PCLinuxOS
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=PCLinuxOX root=/dev/sda1 acpi=on splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

title Fedora (
   root (hd0,6)
   kernel /vmlinuz- ro root=LABEL=/ rhgb quiet
   initrd /initrd-

title Fedora (2.6.20-2931.fc7xen)
   root (hd0,6)
   kernel /xen.gz-2.6.20-2931.fc7
   module /vmlinuz-2.6.20-2931.fc7xen ro root=LABEL=/ rhgb quiet
   module /initrd-2.6.20-2931.fc7xen.img

title Pardus 2007.2 []
   root (hd0,9)
   kernel (hd0,9)/boot/kernel- root=/dev/sda10 video=vesafb:off mudur=language:en quiet resume=/dev/sda5
   initrd (hd0,9)/boot/initramfs-

# (0) Arch Linux
title  Arch Linux
root   (hd0,11)
kernel /vmlinuz26 root=/dev/sda13 ro
initrd /kernel26.img

As can be seen I could easily copy the part marked in red from Pardus' menu.lst to the one called upon by grub on MBR. Thus you don't need to "know" about how to manually edit grub.
9  General / General topics / Re: English PardusWiki on: September 04, 2007, 16:27:09 PM
made: Ati drivers + HP 1600/2600n


hope those are ok   Cool
Good work Zinden!

I think it would be good to explain what some of these commands do, otherwise folks will blindly just repeat it but not learn how it works. For example:


sudo aticonfig --overlay-type=Xv

You could preferably add that the command above enables video acceleration.
10  Assistance / Configuring Pardus / Why isn't nvidia-settings... on: September 04, 2007, 01:52:15 AM
I booted into my Pardus installation, just to check how things are going. I did install Nvidia proprietary graphic-card drivers. So far so good.

I did though expect to find the "nvidia-settings" utility somewhere among the menus, but I haven't been able to spot it. It's installed and can be run from it's usual location at /usr/bin/. I couldn't though understand why it was hidden in that way.

The thing is that with the Nvidia driver gamma, contrast and brightness often have to be adjusted. The options from "Tasma" or equal controls aren't sufficient to get a perfect result; at least that's my experience. I run "nvidia-settings" and made necessary adjustments, so the screen got perfect. I continued to fiddle around a bit, and suddenly I realized that my adjustments had been reversed. Why? It looks like there's too many automatic scripts running, because it you open "Tasma" ---> "Peripherals" ---> "Display", the monitor automatically reverse to default. It's the first time ever I've noticed this in any Linux distribution.

I don't know if it's intentionally designed to be this way, or not. Either way it's not practical. And why should the monitor get reset to default automatically by opening "Display" in "Tasma", when there's a "Default" option already? And shouldn't the utility "nvidia-settings" preferably be more accessible, like in other distributions, because I'm not sure that a new user of Linux would know where to search?

That's all for now folks!


11  Assistance / Installing Pardus / Re: problem with install-suggest pardus modify process on: September 03, 2007, 22:55:12 PM
It's pretty hard to understand what's the meaning of what he's writing. It looks like he has a lot of boot-loaders installed.

If the issue isn't more than about the wrong partition being set as active, a easy fix would be to use GParted or Parted-magic, and simply set the correct partition active.

I wonder what boot-loader he has on hda? Could his post suggest that the first partition hosts Windows? If so the above could fix that.

There's probably some system installed controlling the boot-loader on hda2, hence if it's not working why not just take the Install-CD, boot from it directly to the root-partition, or chroot into the one that has to be fixed?

OK, it doesn't seem he was looking for answers, so I probably just wasted some space here.
12  General / General topics / Re: English PardusWiki on: September 03, 2007, 22:40:46 PM
Even though being a Swede I would say that the greatest need for Pardus is to get the English Wiki comprehensive and informative. Even the forum is to small to split up as it's doing now, at least in my view.

OK, I might not use Pardus as my main distribution, but I keep a close eye on it, since I think it's a very promising project. As for now it's hard to without some reservations recommend Pardus, not because of a technical quality issue (the issues I've seen will probably soon be solved), but because its documentation is very scars. If Pardus simply would have been a fork of some other distribution, for example like BLAG is more or less the same as a customized Fedora system, you could just say: "visit the mother-distribution's forum and you get all the answers you need". Pardus isn't like that, especially in view of how it's aiming at becoming one of the easiest GUI administrated distributions (that's my impression).

I'll have a month of vacation, and go as far as possible from any gadgets or computers I can. When I return I'll see if my limited knowledge can be of any use. I could at least add my posts about some configurations of sound-devices.
13  General / Wish list / Re: Language files for Firefox and Openoffice on: September 03, 2007, 22:17:09 PM
I'm writing this from Arch, but in this aspect I think Mozilla Firefox works just the same. Do you mean that if choosing to install a language from this link, https://addons.mozilla.org/en-US/firefox/browse/type:3, Firefox doesn't install it?

I've never encountered any issues doing that. When writing you just right-click with the mouse to open up a menu which among other things has a language selector; simply tick the box of the preferred language.

I prefer these extensions, but if it for some odd reason doesn't work you could install Google's tool bar.
14  General / Wish list / Re: Restricted Graphic drivers & Compiz Fusion "out of box" on: September 03, 2007, 22:09:14 PM
I can't speak for Pardus, but I have some general thoughts about this:

- proprietary drivers obviously aren't open-source and hence Linux developers can't fix theirs security vulnerabilities
- Pardus doesn't have a dedicated server edition, but in view of the above a critical system should never use proprietary drivers
- strictly put you don't even have the judicial right to include them, though some few do, or they wisely give you the offer while making the initial install to with a working Internet connection get them compiled

Neither ATI or Nvidia seem to be very keen on suing any distributions for violating the code of conduct for proprietary software - and why should they since selling hardware is their main focus - but few distributions choose to openly disregard it. As I said, I can't speak for Pardus. I don't how strict its developers are, both in terms it being proprietary software and security. In view of the situation I think it's a wise choice to let the user choose whether he/she wants to install these drivers, while doing the procedure as smooth and easy as possible.


15  General / General topics / Re: Pardus - Based on what distro? on: September 02, 2007, 16:11:33 PM
To begin with it was based on Gentoo, but as far as I can understand Pardus has from this original derivation become more than a fork, and instead I see how developers choose to come up with their own solutions with a lot of tools and scripts written in Python.

I might be wrong but what I see is a Gentoo base, but except from that a distribution with its own uniqueness.

(By the way: I'm a Swede as well. I don't use Pardus as my main distribution - I'm a Arch user - but I keep testing it and would like to see it become a bullet-proof alternative. It's one of the most polished and well organized distributions I've seen, so if it wouldn't have been for some odd issues I've experienced on ATI based chipset motherboards I would definitely install it as a first choice on more computers when folks ask me for advice.)
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!