Mageia forum

Hi,
I sucessfully installed, and configured Mageia 2.0. Overcame problems with the printer support module, and both printer and scanner
and LAN and screen work ok.

I can play local videos, correctly, with both sound and video.

If I try to play a DVD, which I can do with VLC on Xp, either VLC blows up, or the DVD starts to play then VLC blows up.

It seems to me that in the old days, we installed libdvdcss. I still have a copy of this.

Please advise the way forward.

Warmly,

INDY

EDIT doktor5000: removed mail adress for privacy reasons

goprisko wrote:It seems to me that in the old days, we installed libdvdcss. I still have a copy of this.
EDIT doktor5000: removed mail adress for privacy reasons

Just install it from Mageia repos, no need for an old copy
You just need to enable tainted (and nonfree) repositories. Check https://wiki.mageia.org/en/Software_management

I had to do lots of RPM searching via the internet. Seems the Google RPM repository is now the most current.

I not only installed lib64dvdcss, but it seemed that I needed several other libraries too. including w64codecs.

Anyway, the chooser in RPMDRAKE doesn't seem to show the proper repositories for this sort of stuff, no matter how many I choose.
Same issue configuring Skype and VmWare View Client.

It's there, but hidden.

Seems there are issues.....

Not on topic, but important, regarding printing.

I could not get the Mageia 2 system to recognize my Samsung CLP-310 printer out of the box. Yes, I clicked on the install icon
in the hardware section, but that was insufficient. I had to manually install cups and hplip before the system noticed my printer when I
connected it. After that things went smoothly, and I was able to install the required packages.

This is a definite reversal of trend from Mdk 2010.2, where the necessary software was on the distbn disk, printer activation was enabled.

I also had issues installing MG2 from the 4 Gb distbn DVD. That install always created systems which failed to boot.

I could only successfully install MG2 using the LiveCD, and installing from it.

My hardware is a Zotac 890-GXITX-A-E mobo with the 890 NB/SB and a Phenom IIX4 915e

ONE THING I WANT TO EMPHASIZE.... AFTER NEARLY 10 YEARS WORKING WITH THE MDK LINE OF LINUX.. . .

TODAY, WITH MG2, I FINALLY HAVE A SYSTEM SUFFICIENTLY COMPLETE TO PERMIT MY COMPLETE MIGRATION AWAY FROM MsXp.

Also, why aren't you using LibreOffice 4?? I have been successfully using 4 for nearly 6 mths now, beginning with 2010.2.

INDY

INDY

INDY

Please, follow the golden rule: Only one problem per thread.

You should not search packages over the internet. dvdcss is provided by Mageia repos:

Code: Select all

[doktor5000@Mageia2 ~]$ urpmf -f -m --name dvdcss
Tainted Release:lib64dvdcss-devel-1.2.12-1.mga2.tainted.x86_64
Tainted Release:lib64dvdcss2-1.2.12-1.mga2.tainted.x86_64

For Skype, we have a MAQeia, and it's also provided via Mageia repos: viewtopic.php?f=36&t=1121

For software management in general you should read our wiki page: https://wiki.mageia.org/en/Software_management

For your printer, you may want to check viewtopic.php?f=24&t=1299
The printer popup may have some issues, yes, but installing it via MCC would have installed all necessary packages.

We cannot easily switch to Libreoffice4, policy is no major upgrades so software components within one distribution release,
the same as for Mandriva. Mageia 3 will have Libreoffice 4.

If it is, considering that I specifically enabled tainted release, tainted debug, and tainted backports. It
is most interesting that RPMDrake would not find the package.

But never fear, I found it using google. and,,,,, installed it.... and now I can play movies!!!!!

INDY

No MCC did not install the printer. On 2010.2, and earlier releases, the printer enabling function was clean and robust, but no more!

Also, why did MDK-MGA change established UNIX practice and shift from defining HDDs, FDs, and CDs as dev/hxx, dev/srx. or dev/fdx ??

Where did this UUID stuff come from? BTW, if you clone a partition, as I did, the UUID is cloned too. Thus you can have two partitions with identical
UUIDs, but different /dev/xxx IDs. I suggest you retreat to stuff we made bullet proof 40 years ago, and experiment where it doesn't hurt.

If this is too close to home, read my bio in www.publicresearchinstitute.org. I started on the IBM 1130 with 32 k of ferrite core memory, a single thread machine, that.
Then I graduated to the CDC 6600 cyber system, a 64bit super computer with 256 K works of ferrite core memory, housed in a building the size of grand central station in NYC.,

My current machine is 64bit, and has oodles more RAM than the CDC cyber. So, I saw UNIX Sys 3,V, HPUX and all the other flavors.

Take my word for it. Use the KISS principle. IF it's not broke, don't fix it. Get this distbn back to what works, is clean, clear, and simple.\

Then play around the edges.

INDY

"Real men program in C, Masochists do it in assembler, Wimps in C#"

goprisko wrote:Also, why did MDK-MGA change established UNIX practice and shift from defining HDDs, FDs, and CDs as dev/hxx, dev/srx. or dev/fdx ??

Where did this UUID stuff come from?

As BIOS's can be flaky and change device nodes and some people do change hard drives and cabling UUID's and/or labels make sense.

Enough troll feeding for today.