Welcome, Guest. Please login or register.
April 21, 2014, 10:35:29 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 ... 5 6 [7] 8 9 ... 11
91  General / General topics / Short Article on Pardus in Linux Journal on: July 15, 2010, 16:58:59 PM
There's a short article/review of Pardus 2009.2 in Linux Journal

92  Assistance / Software / q(t)emu -- does it need hardware accelerated graphics? on: July 15, 2010, 02:06:11 AM
I've just installed qemu and qtemu on my Pardus box, and then used it to install xubuntu (maverick) as a virtual machine.

Though it worked (apart from the fact I could only get Lilo to work), it is incredibly slow (1 hour+ and it hasn't finished booting & logging in). My first guess is that the problem might be that the video card/monitor combination that I have (Nvidia 5200, 1680x1050 screen) needs the nouveau driver (Nvidia 173 won't go above 1600 in the X direction with the digital output).

Can anyone confirm/deny this?

System:  Athlon Xp 2600+, 3Gb Ram, IDE disks
Virtual image has 20GB disk, uses 1Gb ram.
93  Assistance / Software / Re: 2009.2 PPracer unplayable on: June 10, 2010, 19:03:49 PM
Btw, when writing this post why is every word underlined in red?

That flags a supposed spelling error. If your language settings are not for English, then most English words will be flagged.
94  Assistance / Hardware / Re: X-insanity on ASUS Pundit P1-PH1 on: June 09, 2010, 18:52:54 PM
.......... or is it only fit to throw off a high cliff (no tall buildings round here).
My opinion is that this calls for a Bugreport @ http://bugs.pardus.org.tr/ Wink
I did already a search with "Ati rs400" with 0 bugs found ( I think that's the translation of Zarro Boogs)

My concern there is whether trying the flgrx (hope I got that right) driver has screwed the "card" -- it was giving the right resolution before, and further checking says that the current version is only for r500 and above.
95  Assistance / Hardware / X-insanity on ASUS Pundit P1-PH1 on: June 09, 2010, 03:00:08 AM
I've been trying to get Pardus up and running on an ASUS Pundit P1-PH1 with Intel P4 3GHz processor and Radeon graphics, and the X configuration has been driving me nuts. The worst is it's inconsistent.

The relevant lines from lspci -v are:
01:05.0 VGA compatible controller: ATI Technologies Inc RS400 [Radeon Xpress 200] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 81c8
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at d0000000 (32-bit, prefetchable) [size=256M]
I/O ports at ee00 [size=256]
Memory at fddf0000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at fdd00000 [disabled] [size=128K]
Capabilities: <access denied>
The monitor is a 1680x1050 ASUS LCD.

The first problem's not a Pardus one: No matter what I try I can't get anything out of the DVI output.

When I installed the 2009.2 Beta, things were OK (but slow, glxgears gave 1-200 fps) until I tried installing and enabling the fglrx driver, at which point I lost X altogether. After a number of unsuccessful attempts to fix it, I reinstalled with the final release and then the "fun" started.

The first few attempts X remained resolutely unavailable.
Eventually I was able to get X started but only 1024x768 resolution (stretched to fill the screen).
I tried telling it the capability of the monitor, and desired resolution, but it remained 1024x768 in "system settings".
Tried specifying alternative drivers (ati, radeon, radeonhd) with no success.
Returned to default (F4 - probe again on the boot screen) and respecified the monitor & resolution.
This time it came up with 1400x1050, not stretched but with big black bands at each side (and vertically displaced) [I have attached the current xorg.conf renamed as xorg.txt].

Has anybody else had any success with this piece of junk, or is it only fit to throw off a high cliff (no tall buildings round here).

96  Assistance / Software / Re: rekonq WebKit KDE-Browser on: May 23, 2010, 00:49:44 AM
I was able to install it from the repositories (I didn't actually notice if it was contrib or testing) yesterday [Friday evening US Mountain time zone].
I've had better results with the Pardus build than the Ubuntu one which kept handing when pressing "back" on pages within the BBC News site.
97  General / The Pub / Re: New Ubuntu 10.04 on: May 12, 2010, 16:09:22 PM
One thing no-one seems to have commented on yet: The boot screen colour is getting close to the Pardus colour!

Actually the new (K)ubuntu boot screen lacks a proper progress monitor unlike the old one, the Pardus screen and many others.
98  Assistance / Installing Pardus / Re: Grub: menu.lst not updating on: April 22, 2010, 22:40:48 PM
  •   just before the 2009.1 release
You mean Pardus 2009.1 RC

  • Unable to boot AMD Athlon XP CPUs.
Where is this coming from Huh? (because this would be very strange.)
It's a regular every day CPU.

I forget the  exact timeline now, but I think that the RC came out with the problem kernel, and there was then a fairly frantic exchange as it became clear that the problem was on pretty mainstream hardware. If you really want to check it out look for bug 11939 http://bugs.pardus.org.tr/show_bug.cgi?id=11939. In essence the devs produced a number of test kernels to try to isolate the problem (these were only installed by a small number of users [2 or 3 as I recall]) and the version numbers of these were then reused in the actual release and the version that was released re-used the version number of one of the tests that didn't work (and I had left that lying around).
99  Assistance / Installing Pardus / Re: Grub: menu.lst not updating on: April 22, 2010, 16:44:26 PM
3) 2009.1 produced a new boot menu but the Pardus entry won't boot (I've not yet had a chance to investigate properly what it's done as the machine has now decided that it won't boot from CD [any CD so it's not just a marginal burn])

I've managed to figure this one out. The good news is it's unlikely to affect anybody else to the extent of unbootability:
The rescue system creates a menu.lst entry not for the latest kernel it finds on the disk, but rather for the one matching the 2009.1 original release. However on my system  that was one of the test kernels generated to track down a major kernel bug
  •   just before the 2009.1 release (for the release the developers reset the build numbers). Moral: don't leave defective development kernels lying around!
  • Unable to boot AMD Athlon XP CPUs.
100  Assistance / Installing Pardus / Re: Grub: menu.lst not updating on: April 21, 2010, 16:32:33 PM
Not good so far.
1) The 2009 CD left the boot list unchanged (and failed to exit properly -- python syntax error).
2) After renaming menu.lst & grub.conf 2009 left grub with nothing.
3) 2009.1 produced a new boot menu but the Pardus entry won't boot (I've not yet had a chance to investigate properly what it's done as the machine has now decided that it won't boot from CD [any CD so it's not just a marginal burn])

I'll probably have to wait for the weekend to see if it's just a loose IDE cable or a failed drive.
101  Assistance / Installing Pardus / Grub: menu.lst not updating on: April 18, 2010, 19:38:51 PM
On my "test-bed" machine, I have 3 different distros installed. Originally Chakra (Arch), Mandriva and Pardus.  I then replaced Mandriva with Sidux, and that replaced grub with grub2. At this stage no major problem, it detected Chakra & Pardus (though Sidux became the default boot).

However following the recent Pardus kernel update, things start to come unravelled:
Not unexpectedly, the grub2 loader from Sidux didn't spot the update. So I figured: "try to install grub from Pardus", but grub-install still only has the older Pardus kernel listed (and still lists the Mandriva boot options).

Is there a way to get menu.lst to update (other than entering all the details manually via the system settings) to include the latest Pardus kernel (even if I have to manually add the Sidux one).

102  Assistance / Software / Re: Archive tag in pspec.xml on: April 06, 2010, 16:52:25 PM
When I looked yesterday on the main indi page, it hadn't been updated to reflect the release of 0.6.1. Just removing the Pardus package and doing a configure-make-install process would force the removal of kdeedu (kstars).

I'll try to modify the pspec.xml for the new release -- that should be a bit easier than messing with svn or snapshot builds.
103  Assistance / Software / Archive tag in pspec.xml on: April 05, 2010, 22:32:28 PM
I have a need to build a package for the latest SVN of indilib (an astronomical telescope control library) because of a bug in the driver for my telescope in the current release, that is supposed to be fixed in the upcoming version.

I think most of what I need to do is reasonably clear, but I'm not sure whether it's possible to directly specify an SVN download in the <Archive> tag of pspec.xml, (an alternative is to use the daily(?) development tarball.).

The Archive tag in the current pspec.xml is:
<Archive sha1sum="70b6a4cf4447874a0cf65dd8ece2d77dc397826d" type="targz">mirrors://sourceforge/indi/libindi0_0.6.tar.gz</Archive>

The url of the snapshot is:

The svn checkout is:
svn co https://indi.svn.sourceforge.net/svnroot/indi indi

What do I need to put into the Archive tag?
104  Assistance / Configuring Pardus / Not getting domain from DHCP on: March 30, 2010, 21:15:17 PM
When I connect to a network from my Pardus machine, it does not appear to pick up the domain name, though the network recognizes the system as belonging to it (e.g. it allows me to connect to machines that can only be accessed from inside the network). I do not see the same issue with Kubuntu.

For example:
ssh myuser@box1
works in Kubuntu but not Pardus, while:
ssh myuser@box1.site.edu

works with either.

Is this:
a) A design feature
b) A configuration error, or
c) a bug?

 If (c) then do you have any suggestions which package to file against?
105  General / Tips and tricks / Building gimp 2.7.1 on Pardus on: March 30, 2010, 02:17:02 AM
As the development version of gimp is getting a significant amount of attention, I thought it would be worth giving a quick rundown of what's needed.

First a few caveats:

1) The 2.7.0 tarball on ftp.gimp.org is too old to include many of the interesting things like the single window mode, so don't bother with it.

2) This was done on a box running 2009-testing so it is possible that there may be (different) version issues, with 2009.1.

3) gimp 2.7 is in development, things may be broken, it's not a good idea to rely on it as your only graphics editor.

Step 1: Ensure that you have a development environment installed (and I may have missed a few things here, if you find such please add them as replies, but everything not explicitly listed as needing to be built is in either the main or the contrib repositories):
sudo pisi it gcc make autoconf automake gnome-build git libgnomeui libpthread-stubs

Step 2: Remove your current gimp installation (you can restore it later)
sudo pisi rm babl
Keep a note of all the dependencies that were also removed.
N.B. It may be possible to avoid this step but the configure scripts got confused about babl & gegl versions until I did it.

Step 3: Get the sources you need:
The current tarballs for babl & gegl on ftp.gimp.org work as of this posting, so download those & unpack them.
For the gimp itself you need the latest git version. To download this use:
git clone git://git.gnone.org/gimp

Step 4: Make sure pkg-config will be able to find the libraries etc:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH

Step 5: Build babl:
cd <where you unpacked babl>
sudo make install

Step 6: Build gegl (same formula in the gegl directory)

Step 7: Build gimp:
cd <where you downloaded the gimp git sources>
./autogen.sh  # You may get a warning that libtool is possibly too new -- it's not.
sudo make install
The executable is /usr/local/bin/gimp-2.7

Step 8 (optional): Add gimp-data-extras.
git clone git://git.gnone.org/gimp-data-extras
cd gimp-data-extras
At least with the 2009-testing version you will need to edit autogen.sh as it doesn't know about automake 1.11, the quick & dirty way is just to replace "automake-1.10" with "automake-1.11" everywhere it occurs.
sudo make install

Step 9: Restore the distribution gimp (optional)
sudo pisi it gimp ...
Where the ellipsis represents anything else that was removed in step 2 and is not a dependency of gimp (e.g. extra plugins, translations etc.)

It is always possible that at some stage the git versions of babl & gegl may be needed.
Pages: 1 ... 5 6 [7] 8 9 ... 11

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