Mageia forum

The installation to the Thinkpad X200 from the Live DVD went fine and everything seems to work fine except the 3G modem.
Ericsson F3507g Mobile Broadband Minicard Composite Device is detected in hardware manager, but listed under "Unknown/other" and the configuration of corresponding network interface fails.
Also the hardware is not listed in networkmanager.
Latest kernel update to kernel 3.12.0-2.mga4 did not change anything in that subject.
In Mageia 3 it worked OK at least until kernel 3.10.16-1...

Hi all

Kde-64 HDD install from dvd [ 1858 packages ] total time = 30 minutes
Installer estimate varied from 43min at start to 1Hr20min during install
Hardware: Asus mobo: P8B75-M LX, 8G ram, Intel i5 4 core, Integrated Intel Graphics, Acer AL1916w monitor, Canon MP280 all in one printer / copier, usb connected.
System did not identify printer initially, however after installing task-printing-canon manually, printer identified and installed. Operates ok.
As expected a straight forward install to a very useable system.

A minor niggle with the printer and installer time estimation but I've had these with each install of Mageia

Again, well done to the Mageia Team

Hi all,

I installed M4B1 64b on 3 PC, one laptop Dell Latitude D630 and 2 home made desktop (Asus M4A77D AM2, PhenomII, Radeon HD4350 and Asus M2N32-SLI, Phenom 9550 GeForce 8400GS)
All went fine, congratulations, except some small details :
- For the 3 PC, the installer didn't detect the network, but it was easy to fix that in the summary page
- For the 2 desktops, there was no icon for the MCC, but it was in the laptop
- The MMC still can't set grub2, use of grub-customizer mandatory
- In the MCC/Installation software, I could see that the first drop down list was on "Graphic applications" I though it was decided the default value being "All".

Good job, ready for the release.

Lebarhon wrote:I could see that the first drop down list was on "Graphic applications" I though it was decided the default value being "All".

For completeness, where do you think that was decided?

Installed on 3 laptops of various vintages, Lenovo X200, X300, Itronix IX260+//Gobook 3 (x86 only)
Used install DVD images (x86 and x64)
Straight installs worked OK.
Upgrades--could never complete.

No fsck tools or editor in "rescue" filesystem ???
no shell access during install to fix or investigate anything during upgrade w/gui
no wifi--- could have been missing firmware? no telling, no shell/VT options.
one update almost worked but cratered due to not being able to replacefiles.
(about 1100 files, could not force from shell and resume install, no shell, borked system)

Did not try text-only mode if it exists.

Everything works great once installed and rebooted/updated of course, but upgrade from MGA3 borked in an unrecoverable fashion in all 3 cases.
Online update suggested, cauldron working nice once you can get it installed.

I'll take another pass with the liveCD when I get a chance (machines were imaged first)

doktor5000 wrote:For completeness, where do you think that was decided?

I can't remember for sure but it was probably discussed in the French forum (MLO) it was at the time of Mageia 2. I was convinced that when installing Mageia 3, rpmdrake was by default with the "All" filter, may be am I wrong?

Without doubt there are things discussed in the french forum as well as in the german, brazilian, greek (add ad libitum) forums - none of these discussions bear any fruit until matters are picked up/discussed/decided in the proper areas, namely developer team and/or council. In that case the matter/decision will be published in the matching mailing list.

In short: Therefore it is important to carry such matters forward from forums to bugzilla so that the people who are doing the job know about it.

Actually this feature has been added as requested by a Mandriva user: https://qa.mandriva.com/show_bug.cgi?id=36486
So if you open another bug report with proper reassoning, default could be changed back.

But there's also an impact on search speed and initial indexing of all available packages ...

doktor5000 wrote:

Lebarhon wrote:I could see that the first drop down list was on "Graphic applications" I though it was decided the default value being "All".

For completeness, where do you think that was decided?

It is very easy for the user to change that setting, simply set mode as desired and quit from the menu rather than the quit button on the bottom... it saves the preference.
(why file>quit and the quit button exhibit different behavior may be questionable, but that's how it has been as long as I can remember, perhaps Mandrake v6?)

The point is, all the experienced users know that, but majority of novices and new Mageia users will not notice that.
Question is always: Can't find that package/driver/whatever ...

doktor5000 wrote:The point is, all the experienced users know that, but majority of novices and new Mageia users will not notice that.
Question is always: Can't find that package/driver/whatever ...

I agree completely, just trotting out the ancient work around in case anyone Googles for the fix.

I'm still bummed out that urpmi got "dumbed down" so you really need ~an exact match to use it from the command line now, to the point that it is ~rediculous.
As I know it was intentional, there's no point putting in a bug report.

I have installed mentioned distro and I am very satisfied. All my remarks about nvidia driver in Mageia 3 are correct. Very good work.

No need to open a separate thread for only one sentence, i've merged this into one of the existing threads.

Hello,

Following a crash, I re-install M4B1 with the same USB stick than the first time (see above). No problem during the clean re-install.
After the reboot, in the connection screen (kdm) the system refused the user password. I opened a tty console with ALT+CTRL+F2, same problem, user and root passwords refused. I thought to a keyboard configuration problem because I have a qwertz layout (Swiss).
I re-did a clean install taking great care to the KB choice and passwords. Same behaviour in kdm, but I could connect under root in a tty console, I had a qwerty KB !! I changed it to qwertz with drakconf, I also created a new user with login and password made with only prints that are the same in all KB (login=dfg password=dfg). Back in kdm, I could connect the user dfg but not the original one, even trying with several KB layouts. In the tty console I deleted the users, re-create them (only two) with realistic login and password and now connection is OK.
But:
1- whatever the user is, the MCC is unreachable. The icon is in the taskbar and in the menu but don't start. The menu seems properly configured and drakconf present in /usr/bin.
2- If I open a Konsole with the menu, the KB is qwertz and a connexion under root is impossible :

Code: Select all

$ su -
Password :
su: cannot set groups: Operation not permitted
$


3- in a console tty, root connection is possible but the KB is azerty
4- in the KDE settings, the KB is qwertz

Is there something to test before filing a bug ?
thanks

I could solve point 2 with the command:

Code: Select all

# chmod u+s /usr/bin/su

to change rights for su from -rwxr-xr-x to -rwsr-xr-x

Since the beta came out of the 64 I have installed as SO principal in a notebook Samsung RV408 Intel with 8GB RAM and 1TB HDD dual boot W8 yet without fail but what worries me is that when I start with no W8 keeps me time and sometimes after work and then start with W8 Mageia nor is synchronized clock, does not always happen, but sometimes touches me manually correct the time on both systems, I have also noticed that sometimes it takes more than 90 seconds to shutdown and sometimes does it in 15 seconds.

Rest is very stable and does not yield any problems installing it immediately recognized all the hardware of the machine.

I look forward to the final version.


ESPAÑOL
Desde que salio la beta de 64 la tengo instalada como S.O. principal en una notebook Samsung RV408 Intel con 8Gb RAM y HDD 1Tb arranque dual con W8 por ahora sin ninguna falla pero lo que me inquieta es que cuando inicio con W8 no me mantiene la hora y a veces despues de trabajar en W8 y luego iniciar con Mageia el reloj tampoco esta sincronizado, no siempre pasa; pero algunas veces me toca corregir manualmente la hora en ambos sistemas; también he notado que a veces tarda mas de 90 segundos para apagarse y otras veces lo hace en 15 segundos.

De resto es muy estable y no dió ningún problema para instalar, reconoció de inmediato todo el hardware de la máquina.

Espero impaciente la versión final.