David Batson

I installed the Java updates anyway without any problems I am aware of. However, see the following: http://forum.mandriva.com/viewtopic.php?t=115562

This works on my T42 ThinkPad in Mandriva 2009.1 KDE Powerpack edition. http://forum.mandriva.com/viewtopic.php?p=688521#688521

I have been following this issue on four different forums. I have read lengthy threads on the MandrivaUser.de forum and on forum.mandriva.com (International), as well as shorter threads on forum.mandriva.com (French), and Mandrivausers.org. When you read all that has been said, you get a much better idea of what transpired. "you've flat out called a few of them liars, without valid reason" Wobo contacted Anne at Mandriva by telephone offering MandrivaUser.de members to man the Mandriva booth at LinuxTag after Mandriva decided not to attend the booth themselves (MandrivaUser.de members had manned their own booth at previous LinuxTag events, but did not this year because Mandriva S.A. was to have their own booth). He was told she would contact him by the next day with a reply in the affirmative or not. Wobo has not heard from Anne since. This is a lie no matter how you cut it. A common one, but nevertheless a lie. Wobo was told that Mandriva did book a hotel for him in Berlin for Linuxtag (on the day before Mandriva cancelled), and they would give him the specifics later. He never heard again about this hotel room. Rightly wobo wonders why he was never given any specifics when they told him the room was already booked. While the room might have been booked, evidence points to the contrary. To the best of my knowledge, wobo was never even told which hotel was supposedly booked. The whole episode looks shady when you consider "Nov. 2008 --> Mandriva (Vanessa Wall) asks wobo for help in organizing and operating a company stand at the Linuxtag 2009 in Berlin.", and Mandriva continued to maintain the event was on until June 19th - yet important event planning details were never given to wobo, such as hotel reservations details, and information that the CEO was going to attend. This information that the CEO was to attend did not come out until Mandriva said they were cancelling because the CEO had broken his leg and could not attend. Wobo got the shaft when he did not receive replies to requests for necessary information. Wobo was told to book his own train ticket, and that he would be reimbursed (but has not been to date AFAIK). As things stood, if wobo did not go to LinuxTag on his own, I believe his train ticket would have been forfeit. Wobo got the shaft because he was going to attend LinuxTag whether Mandriva S.A. did or not. Wobo had to make a last minute hotel booking, perhaps not where he would have chosen, and not at the rate he could have gotten if he had made the reservation some weeks in advance on his own. EDIT: Wobo's real beef is that Mandriva did not communicate with him so that he could make his own plans in a timely manner. Requests for necessary information was ignored. Guaranteed replies never came.

http://www.kde-apps.org/content/show.php?content=33257 I haven't tried kima in 2009.1, but I did use it in 2007.1 and 2008.1.

I had a faulty fan assembly on my T42 ThinkPad after it was about 3 years old. The fan did run, but apparently not fast enough or else it was clogged. My T42 was under warranty, and the shop replaced it. Problem solved. I used kima to monitor my temp. settings. I understand imsensors does this as well, but I believe I like kima better. In my case it was the GPU that was overheating, not so much the CPU. This I found out with kima. My laptop actually shutdown when the GPU reached about 98 deg. C. (a safety feature). Other things that can cause a laptop to run hot (esp. the base) is the WLAN card and the Hard Drive. They (someone) does make cooling bases for laptops so that your legs don't burn. My wife's nephew had one for his Sony laptop.

Here is a followup thread on the German forum MandrivaUser.de: Opinion MandrivaUser.de (Google translation into English) Original: http://www.mandrivauser.de/viewtopic.php?id=25967&p=1

Wobo did attend the LinuxTag event at his own expense. Featured this year at LinuxTag were French Linux companies. Wobo states that many of their products were running on Mandriva at the event. Mandriva S.A. had paid 4200 Euros for a booth at LinuxTag and were on the program to be there. Mandriva put up on The Official Mandriva Blog, the day before, on June 18th, that they would be at LinuxTag and would be happy to answer questions. They pulled out the next day on Friday, June 19th, only stating that they would not attend because the CEO had broken his leg. They also removed their blog post on Friday. Wobo (aided by MandrivaUser.de forum members) offered to fill in and man the booth in their steed. Mandriva S.A. said they would decide the next day, but wobo never heard again from them about it. Wobo had been manning a MandrivaUser.de booth at LinuxTag for the last several years, so he knows the drill. Unfortunately, these events transpired too late to arrange for a MandrivaUser.de booth this year. LinuxTag attendees who were not privy to the above news expected Mandriva to be at the event. When they discovered the booth Mandriva had paid for being occupied by other sponsors, naturally questions were raised. Wobo along with some others from MandrivaUser.de were at the facility wearing their shirts with the MandrivaUser.de logo on it. Many asked wobo directly why Mandriva was a no show. He gave the official answer that the CEO had broken his leg, so Mandriva decided to cancel. Many (including myself) find this answer a bit thin. Sure, the CEO might have broken his leg (which apparently is true), but why couldn't Mandriva use other employees man the booth and answer questions. As wobo said, no one knew the CEO was slated to attend until he cancelled. Of course questions abound with "what really happened". Many, especially the reporters, are waiting for an update on this hot story. Many asked wobo personally to fill them in on any developments. He told them he would, so he obliged. Wobo is operating in the open, not behind closed doors. If anyone at Mandriva S.A. gave a care, they would have been communicating with wobo. Mandriva S.A. should have been on the lookout for any fallout from the sudden decision to withdraw from LinuxTag at the last minute. Mandriva really needs a PR person. I honestly believe if Adam W. was still at Mandriva, events would have unfolded differently. Adam W. understands PR. Apparently no one else at Mandriva S.A. does. Mandriva S.A. has had more than a week to "set the record straight", but they are playing the ostrich, and waiting for the tempest to blow over. I also find it oddly coincidental that Mandriva decides to do website maintenance today. Hmmm. http://translate.google.com/translate?hl=e...3D25899%26p%3D6 Sorry, Mandriva S.A. shot themselves in the leg. Wobo did not pull the trigger.

Wobo did not make a lone decision here. This a consensus statement of MandrivaUser.de forum members discussed in a 6-page forum thread. http://translate.google.com/translate?hl=e...3D25899%26p%3D6

Sorry for the typo, wobo. I edited my initial post to correct it.

The following repercussions stem from Mandriva SA's last minute pullout from LinuxTag and virtual cutoff of communication with wobo (Admin. MandrivaUser.de) with whom they were collaborating with. I must say that IMO, Mandriva SA really dropped the ball here. Public Statement of MandrivaUser.de

That was fixed for Powerpack users by an update to gstreamer-fluendo. See following bug report. https://qa.mandriva.com/show_bug.cgi?id=48191

If you are using Mandriva 2009.1 Powerpack edition, there is an update to the gstreamer-fluendo codec in the restricted repositories that fixes the issue of MP3's not playing in Amarok. If you add the restricted repositories, make sure they are the 2009.1 repositories. You may need to edit the URL (from 2009.0 to 2009.1) to the restricted repositories in Configure Media. If you are not using the Powerpack edition, install phonon-xine to be able to play MP3's in Amarok.

You can try changing some settings in MCC > Hardware > Sound Configuration. You can also look for possible problems there.

This does not make any sense. Formatting a hard drive has nothing to do with the BIOS. Even partitioning the hard drive will not affect the BIOS. Are you saying you get no BIOS or manufacturer splash screen when you turn on your computer after it has been shut off (cold start)? If you boot up a Live CD such as Mandriva One you don't see anything on the display? Do you at any time see anything on the display?

Some computers, especially laptops have a hardware mute button. Make sure yours isn't muted. Check your volume control settings, there are several. Star > Sound & Video > PulseAudio Volume Control. Star > Sound & Video > KMix Sound Mixer (or applet on taskbar). Configure Desktop > Multimedia. Maybe disable pulse audio for a check. You can do this from MCC > Hardware > Sound Configuration. Try some headphones to check sound output there. http://wiki.mandriva.com/en/2009.1_Errata#..._Dimension_4550

I discovered today that the restricted repositories added to 2009.1 were 2009.0 on my system. An mdkonline update fixes this, but only if done before the restricted repositories are added. I had to manually edit Restricted and Restricted Updates in Configure Media on my system. https://qa.mandriva.com/show_bug.cgi?id=51614 [moved from Installing Mandriva by spinynorman]

See my post here that should help some in the meantime. I have the ATI Mobiliy Radeon 9600. https://mandrivausers.org/index.php?showtop...st&p=617173

Looks like what I just read on Fedora 11 bugs this morning. https://fedoraproject.org/wiki/Common_F11_b...n_Thinkpad_X41T

I tried the following suggestions from https://fedoraproject.org/wiki/Common_F11_bugs in Mandriva 2009.1 and they help quite a bit for speeding up 2D rendering for me. That means that browser and application windows write to the screen quite a bit faster. I can move windows around the screen with much less lag. There is a third option that I did not try, add Option "AccelDFS" "off" to xorg.conf.

I am in the same boat. Unfortunately, I do not have the option to change video cards in my laptop. :sad:

See my posts and the two links in it below. Unfortunately your ATI card has been moved into legacy status by ATI. https://mandrivausers.org/index.php?showtopic=86363&hl=

I disagree about Canon. Canon only supports certain models in Linux. Fortunately I happened to buy one (by accident). I have the Canon PIXMA MP600. I found Linux drivers for it on Canon Australia's website. Both the Printer and Scanner work quite well with Canon's drivers using CUPS.

Actually X Server 1.6 and later are not supported by the ATI Catalyst 3 driver. Unless you stick with a distro released before Feb. 2009, that uses X Server 1.5 or earlier, you will not be able to use the ATI propriatary driver with the Radeon 9700. This situation is going to be true of all the up-to-date distros. If you want to use the propriatary ATI driver, you might want to use Mandriva 2008.1, which has been heralded as one of the best Mandriva releases. Myself, I am using the open source driver on 2009.1 PWP, just like you. I do miss the propriatary ATI driver. Hopefully the open source driver will improve soon (speed wise). http://support.amd.com/us/gpudownload/linu...mp;lang=English http://www.phoronix.com/scan.php?page=news...m&px=NzExOQ

I have been getting occasional hard freezes with 2009.1 PWP. Mouse and keyboard totally unresponsive. Magic keys don't work. Have to do a hard reset to get the computer back. Never had these problems with 2008.1 or with Windows XP, Vista, or 7 RC1. No virtual machines here. No 3D desktop effects, no 3D apps or games. Only internet browsing and using ordinary Mandriva tools. One person suggested that it might be the radeon driver for my ATI Mobility Radeon 9600 causing the problem. I really don't know what is causing this.

Got it installed. After installing the kernel headers and a couple of dependencies, I was able to install the Phoronix Test Suite (206 deps). After it was installed, I found it in the kmenu under Tools > System Tools. I opened the app and found that I still had to install any tests that I wanted to run. I installed one test from within the app and ran it. So far, so good.