adamw

The point of UUIDs is to avoid problems like the hda -> sda switch. That is caused by an upstream kernel change that we have no control over. Using UUIDs avoids it being a problem. It also solves problems like the /sd* enumeration changing if you boot with a USB drive connected, which happens on many motherboards.

Sorry, but we're not going to change it. There's already a comment above each UUID line to make it obvious which device it was initially created for, and as you noted it's easy to find the UUID of any given drive. If you don't like UUIDs you can switch back to /dev names or switch to labels, but we won't change the default.

Oh, I should note the sync steps for 2009 have changed a bit (they're easier). The new guide is:

http://wiki.mandriva.com/en/2009.0_Synchronization

Just in case you hadn't seen it already. I have tested this myself and it works, but there's always *something* that goes wrong whenever anyone else tries something, isn't there? :)

The best driver (usually) for VIA chipsets is openchrome. I try quite hard to keep an up to date and well working version of openchrome in the distro. I would recommend 2008 Spring or 2009. If you install 2008 Spring, also install the updated x11-driver-video-openchrome from /main/backports , it should work better in almost all circumstances. The Mandriva tools should automatically use the openchrome driver for the device.

As far as I'm aware, Mandriva and Fedora are rather better than most other distros for VIA graphics. Mandriva because I try and keep it up to date and working, and Fedora because one of the developers of the openchrome driver does the Fedora packaging for it. :)

If the driver is correctly loaded but doesn't work with the cam that can be tough to fix :\ I would Google the error message and see what you get.

It's not actually a problem. Just ignore it. It's unavoidable.

If you get it sorted do let me know if you can get sync up and running - so far I haven't had any external testing of the WM2003 sync stuff, only my own testing.

BTW, you can (or should be able to, I didn't test it yet either...) browse the device via Konqueror (KIO) in KDE 4 - the kde4-kio-rapip package does that. But you can't synchronize with KDE 4 Kmail etc. The problem is that neither opensync nor KDE folks have got around to writing an opensync KDE 4 plugin yet, so there's nothing I can do to make it work :(

David Batson is correct on what the package removal does. Viking, I suspect it was just removing all the *other* NVIDIA drivers, not the one you need. There are four different NVIDIA drivers - 71xx, 96xx, 173.xx and 177.xx (which is named 'current'). Your card will use 177.xx ('current'), so 71xx, 96xx and 173xx can all be safely removed. We have to ship all four on the live CD in order to support all available NVIDIA cards, but post-install, some can be removed.

Please file bugs for your other issues, particularly the boot issue. Thanks!

The issue is with updating from 3.x to 4.x, not 4.0 to 4.1.

We're currently doing internal tests on a 3.x -> 4.x migration script.

I've triaged the bug. Thanks.

Or someone decided to put it in the default install set...

I think Coherence has probably kicked in. If you're not using Elisa, just remove it and remove all Coherence-related packages, that should shift it. I'll try and make sure to check this for 2009.

viking: ...and while we're giving out "if I were you" advice, if I were you, I'd file a bug report on it, because I'm the only Mandriva 'developer' reading this forum and I don't maintain HAL. :)

I don't think it's actually intentional.

Do you have Elisa installed? If you install Elisa and run it, it starts up Coherence automatically...

consolehelper is the system Mandriva tools use for this. You can create a command that, when run as normal user, will automatically prompt for root's password and then run with root privileges. If X is active it will pop up a GUI password prompt, at a console it'll just ask for it at the console.

Did you file a bug?

I'm fairly sure RJ has done a 2008 Spring install direct on an i586 system...

Just update to latest Cooker, disabling it is handled better there. Splashy integration is still WIP.

That shouldn't be the case, the installer's supposed to work on i586.

One should work, anyway, and you can install from that.

Have you tried using the Mandriva network connection setup tool rather than wvdial directly?

Mandriva is proud to announce the release of Mandriva Linux 2009 Beta 2 'okapi'. This beta includes a completely new installer for the Free (and, in the final release, Powerpack) edition, and is testing the Fedora system-config-printer printer configuration tool as an alternative to printerdrake. The new beta also brings Firefox 3, OpenOffice.org 3.0 beta, and support for the ethernet adapter used in many new Eee (and other netbook) models. As always, Mandriva reminds you not to use pre-releases in any critical situation; install them only on a test system or partition, or in a virtual machine. Additionally, we strongly discourage using this pre-release to upgrade from any earlier release of Mandriva Linux, as the transition process from KDE 3 to KDE 4 is not yet fully implemented and you are likely to end up with an unusable system. Please make sure to read the Errata and Release Notes, and file any bugs not covered in those pages on Bugzilla.

OK, I just fixed up and updated the spe package in Cooker. I'll send the fixed version to /updates for 2008 and 2008 Spring. It should land there in a few hours, depends on your mirror.

I'll see if I can update the Mandriva package for you.

python(abi) would be a virtual provide: in Fedora, some package - probably python itself or python-core or something - would be set to Provides: python(abi) , for a particular reason in Fedora's Python packaging system. We don't use the same system, so nothing in Mandriva provides python(abi) . As dexter says, use the Mandriva package.

That's right.

The default option in the bootloader in Mandriva in fact points to the files /boot/vmlinuz (for the kernel itself) and /boot/initrd.img (for the initrd). These do not really exist. When you install a kernel package, it creates them as symlinks to itself. So the upshot is that the default option will always boot the most recently installed kernel. The explicit entries beneath it are there to make sure you can always explicitly boot any installed kernel you like.

To me this smells like two entirely different problems. Stuff not automounting is likely just a helper app not running or a bad config option in your desktop environment, but your optical drive issue smells very like a hardware failure to me. As David says, test it in a live CD, preferably of another distro / OS.

Yeah, the wireless adapter isn't in the list at all.

Is it an onboard thing or a PCI card or a USB stick or what?

PCLOS is a branch of Mandriva. They rebased off Mandriva 2007 a couple of years back but they've diverged quite a lot since then. What PCLOS is now is not Mandriva 2007 or Mandriva 2008 or any other kind of Mandriva, it's a distinct thing by itself.