adamw

ian: no, that's not it, the upgrade procedure is a special case, it doesn't follow the update repository rules. It's just that there were some bugs in the initial release of the in-line update feature that could lead to problems like this (incomplete upgrades) - usually disk space or mirror issues. See my announcement thread about it in the official forums.

tyme: I was simplifying a bit. The auto mirror selection and aria2 magic makes it a bit more complex than I explained. But basically, yes, that's one of the improvements that's coming when we re-open the feature.

tyme: actually, if you want modern, maintained sound servers - basically one, Pulse. Plus Jack, which can work together with Pulse and is more for high-end audio applications than general desktop use. But Pulse has finally killed off arts and esound and the other pretenders. We are getting closer to having a vaguely rational audio stack, which has never happened before.

I've actually started to quite like the Awesome Bar lately. Often I'll read a story and then forget exactly where it was, but with the awesome bar, I can just remember two of the more unusual words from the headline, type them in, and it finds it. Useful.

gspca is included in the official kernel now so there's no need for an external package. Can you describe the problem in a little more detail? 'not working' is not very informative. Thanks.

Sounds like Pulse failed to start up for some reason.

dexter: you can report them (check they're not dupes first). KDE 3 will be dropped for 2009 Spring, but if they have time, the KDE team will try and fix major issues with KDE 3 in 2009 as updates.

Some people have had problems; I've not got it pinned down yet but I'm fairly sure you can get a problem either if you don't have enough disk space (you need plenty of space on at least the partitions containing /usr and /var) or if the mirror used for the upgrade is overly busy (resulting in some packages not being downloadable and hence a partial upgrade). In either case you'd wind up with half the packages updated and half not. You can usually resolve this by booting the semi-upgraded system, logging in at a console, and running 'urpmi --auto-update -v'. Mostly it seems to be working for people, though.

User configuration shouldn't affect sound output, no...can you try 'alsamixer'? It'd be useful to know if that shows the correct channels for the card. If it just shows PulseAudio, try 'alsamixer -c0' or 'alsamixer -c1'.

Do you have xorg-x11-100dpi-fonts installed?

On keyboard keys, that's KDE 4 again:

http://wiki.mandriva.com/en/2009.0_Errata#...ported_in_KDE_4

they work fine in KDE 3, GNOME, and Xfce.

I'm trying to work out a fix for this, with one of our KDE guys. We have a KDE 4.1 port of kmilo built now, but it doesn't seem to be working yet.

That's how the online upgrade is supposed to work :) It respects your existing packages and configuration.

If you want to add KDE 4, install 'task-kde4'.

javaguy: you're likely suffering: http://wiki.mandriva.com/en/2009.0_Errata#..._not_created.29

there's a workaround there.

Ahhh, KDE 4. :)

KDE 4 is the answer to questions 1 and 2. Namely, it can't put devices on the desktop (as far as I'm aware) and you're always going to get the 'handles' because icons on the desktop are plasmoids, like everything ELSE on the desktop. Welcome to the brave new world.

You could create a folderview plasmoid for /media , I guess. That would work much like the ~/Desktop folderview we create by default. As most things that get auto-mounted get auto-mounted in /media , you'd see them show up in the folderview.

lspci is not much use. Can you please provide the output of:

lspcidrake -v

it may also be interesting to test booting with kernel-linus and kernel-tmb , and see if it works with either of those, for comparison purposes.

tyme: the hdd vs. ssd speed issue is rather more nuanced than most people think - don't just trust me, see Linus' take on it! - http://torvalds-family.blogspot.com/2008/1...intel-ssds.html - but it's also just the case that the model in the Aspire One sucks, too. It's a poor piece of hardware. If you look around forums dedicated to the Aspire it's a pretty notorious issue among owners of it.

tek: not really, there's still no practical general-purpose quantum computers around. It's a lot easier to build a special-purpose quantum encryption system (still bloody hard) than it is to build a general-purpose quantum computer powerful enough to crack existing encryption schemes.

And, haven't these people ever heard the phrase "hostage to fortune"? Sheesh.

You don't really need to bother downgrading anything but mandriva-release packages. None of the other changes are major or unstable, you can just go ahead and keep them.

The mirror list isn't hardcoded into any package. When repos are added it basically just asks api.mandriva.com to provide repositories for whatever version it identifies itself as (according to /etc/product.id). This wasn't updated for 2009 release until a couple of hours after Fred sent the initial announcement to Cooker and the forums, though it was already fixed before I sent the announcement to all other sites, and the official PR still hasn't been issued yet. So yes, we're sorry about that, but it will only affect the earliest of early adopters. I think everyone affected is likely reading this thread or the one on the official forum. :)

Mandriva 2009 runs fine on the Aspire (either Windows or Linux Aspire). We have one in Paris for testing.

The SSD in the Linux version is known to be very slow, so don't buy it expecting amazing performance. It's slower than a regular hard disk in most ways.

The reason being, btw, that g77 / f77 was replaced by gfortran in gcc 4.0. In general you should try to build stuff with gfortran now, and only fall back on the old g77 if you can't.

You can't uninstall ndiswrapper - it's in the kernel. Well, you can uninstall the userspace stuff, but then all you have is a broken ndiswrapper. =)

Once you switch to ndiswrapper in drakconnect, you can't switch back to the native driver using drakconnect - it's a limitation of how drakconnect's written. To switch back you have to poke /etc/modprobe.conf manually. If you post your /etc/modprobe.conf I'll post the necessary changes to switch back to the native driver, if you wanted to try that. Otherwise, to get it working with ndiswrapper, try the Wiki workaround.

My thoughts on this are here:

http://blogs.gnome.org/otte/2008/10/03/scary/

in the comments.

There were some RAID-related bugs fixed with post-release updates for 2008 Spring, as I recall. Perhaps you could try doing a network install? That way, the install will use the latest updated packages, not the original release ones.

Reiver's right. Xandros is doing rather well at the moment, thanks to the Eee deal. Be interesting to see how long they hold onto it, though.

Blank page in the AP list is known:

http://wiki.mandriva.com/en/2009.0_Errata#...less_connection

there's a workaround there (use the console version).

How exactly does it fail to install the dkms package, for the native driver? what's the error?