Has anybody else seen this error on trying to add the ANKA repository?
Today it has been repeatable for me , and I'm not sure if the package list is corrupted, or if there's a network issue?

Many thanks -- that's more or less what I thought; I just wasn't sure if the virtualbox stuff was needed by the guest system to access the virtual HDD or something like that.

I'm probably being totally dumb here, but I've not used virtualbox before.

To test out the new testing repositories for Pardus, I installed Pardus 2011.2 under virtualbox on my testbed box (currently running Siduction [a Debian Sid derivative]) and then added the testing repository.

However when I tried to update, it failed on the virtualbox kernel modules (said they need 2.6.3x). And now the virtual machine won't boot properly.

So the question is: Are the virtualbox modules needed on the guest system or can they be uninstalled before updating -- I don't plan on running a virtual box within a virtual box!

There may of course be other problems as even when booting with the old kernel, kwin crashed, but I'd like to eliminate the virtualbox packages as a source of the problems.

James

Actually ROSA (sometimes POCA)
is a Russian Mandriva derivative.

Lisa: Not great timing -- the release came out yesterday

As far as general purpose KDE distros go, my current favourite is Siduction [a fork of Aptosid, derived from Debian Sid].

For me Chakra is not a viable option as although I prefer the KDE desktop, I'm a developer on a GTK+ binding (Fortran) so their highly anti-gtk+ approach is a showstopper.

 A bit of a random thought here.

For me at any rate, the thing that distinguished Pardus from the rest of the pack was its configuration and management tools. What chance that another KDE distro could take them over and use them?

There is also the "World Clock" widget, which shows a world map and displays the time at the nearest major centre to the mouse pointer. It's part of the KDE plasma widgets (I think it needs Marble to be installed), so you should only need to right click on the desktop and then select "Add widget", then "TIme & Date" and the pick world clock.

I'm not sure if this is useful, but you could try power cycling (or running the auto-sync option in the menu since it's an analogue output) the monitor after the system has come up (or not turning it on until the login screen has has time to appear). On one system I have to do that to prevent a similar flashing -- however the hardware is not comparable (Intel graphics, LCD monitor with DVI connection -- but it is Pardus 2012.2), but it might be worth trying.

If you're really not getting any EDID info, then you could try giving explicit resolutions in /etc/X11/xorg.conf (however the only time I've encountered a true no-EDID monitor is on an old G3 iBook where Apple presumably couldn't be bothered to connect the necessary wires since they have a table of the capabilites based on the laptop model number).

That means it's not installed (maybe the defaults have changed). You first need to install the package "memtest86", either:
or from the package manager. Then as I recall when you choose "add" in the boot manager screen of the system settings it should be available.

As I recall [and I've not played with boot options recently] Pardus installs Memtest86+ by default but doesn't put it into the boot menu ("ls /boot" will show if it is installed). You can enable it in the control centre, and then choose memtest as the boot option.

BTW: My media station (a Zareason Media Station -- so made for Linux) did a similar thing last night where X-failed to exit properly on shutdown (just a black screen and no keyboard response). That machine is running Pardus 64 bit and until last night it's always behaved fine, if it repeats the misconduct I will need to investigate further.

KDE 4.6.3 is has now migrated from the devel to the testing repo.

Thanks for that pointer. I'll give it a go when I next get a chance to fiddle with that machine.

Thanks Atolboo & Lisa, however I think I've tried those and also using /etc/iftab and manually editing /etc/network/interfaces.

Right now problem #1 is getting everything to agree which interface is which. Once I'm there I might have a chance of getting the system to do what I want which is:

• One interface (let's say eth0) will get its IP address from the the outside server.
• The other will have a fixed 192.168.*.* address, and any machine connected to that side will get an IP address from this machine and NAT translation.

Currently I do have a Kubuntu machine that does this (I did have to manually edit /etc/network/interfaces to get it to work).

According to a recent discussion on one of the Ubuntu mailing lists, grub1 will not boot out of the box from ext4. Some distros (including Pardus) patch it to allow boot from Ext4, others don't.

Is there a convenient way (or even an inconvenient) way to get Pardus to set up the networking from the beginning without a re-install.

Why?:
I have a machine with 2 ethernet cards. After I installed the system, I got a new 1GB/s card that I used to replace the original 100MB/s PCI card, but now Pardus is totally confused about the identities of the cards with some things saying I've got eth1 & eth2 (including ifconfig) and others (including the network manager) saying it's eth0 and eth1. So far all my attempts to get it to do what I want have failed (and probably made things worse).

Also is it actually possible to get the dhcp server running with anything other than the default (useless) configuration, every time I start the dhcp service, it replaces the config file with a default version?