what is the output of rpm -qa | grep kernel ?

Keywords: (none) => NEEDINFO

rpm -qa | grep kernel
kernel-server-3.3.8-2.mga2-1-1.mga2
kernel-firmware-20120219-1.mga2
kernel-firmware-nonfree-20121030-1.mga2.nonfree
kernel-userspace-headers-3.3.8-2.mga2
kernel-server-devel-3.3.8-2.mga2-1-1.mga2
kernel-server-latest-3.3.8-2.mga2
nvidia-current-kernel-server-latest-295.71-1.mga2.nonfree
kernel-server-devel-latest-3.3.8-2.mga2
nvidia-current-kernel-3.3.8-server-2.mga2-295.71-1.mga2.nonfree

Only this combination is working, now I don't use kernel-server-3.4.45, because there are many problems with finding 3.3.8 in first message.

and previously what did you have ? 

you have to have the corresponding kernel-server-devel matching the kernel you have, witch seems not the case

next time please provide full logs I understand personnaly nothing with such cut

Now I'm writing version directly 3.3.8:
http://code.google.com/p/mageiaos/source/browse/branches/0.0.5/mod_names/02-base-core
http://code.google.com/p/mageiaos/source/browse/branches/0.0.5/mod_names/03-base-kernel-dkms
http://code.google.com/p/mageiaos/source/browse/branches/0.0.5/mod_names/05-base-x
If I'll change 3.3.8 -> 3.4.45 and change 295.71-1 -> latest version in repo, then I'll have errors, which I wrote in first comment.

How to reproduce (unionfs is requires and Mageia 2):
1) svn checkout https://mageiaos.googlecode.com/svn/branches/0.0.5/ mageiaos
2) to change 3.3.8 -> 3.4.45
3) to run script total.sh

I can't debug your work..
but it works fine in mga with real use

If it works fine in mga, it's does not means, that bug is not present.
It works fine in mga if to do update, because all problematic kernels are in updates. But I use new kernels directly (without update) and bug is present.

I installed recently a mga2 with the netinstall so directly kernel from core/updates and it was working fine (as you can test in a chroot)

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Sorry, I made the mistake to comment on this bug in a mail-exchange with Alex, instead of here.

I'll now paste what I said in this comment, and ÐлекÑей's reply in the next comment.

On 03/07/13 22:48, Marja van Waes wrote:
<snip>
> On 03/07/13 20:16, ÐлекÑей Ðогинов wrote:
<snip>
>> Next situation. You does not fix bugs if bugs is not present in
>> Mageia, but, for example, bug
>> https://bugs.mageia.org/show_bug.cgi?id=10650 don't allow to use new
>> kernels from Mageia and it's critical. How can I fix this situation?
>> To rebuild kernels and to put in MRC repo? To use kernels from ROSA,
>> because there is no bug in ROSA? I don't think Mageia is interested in
>> such my fix.
> 
> First of all, I have too little knowledge to understand the bug, sorry 
> about that.
> 
> Our triage guide tells us, that if there is a bug against an rpm 
> package, to choose that component:
> 
> "RPM package: Bugs about all Mageia RPMs (official repository, we don't 
> support third party ones)"
> https://wiki.mageia.org/en/Triage_guide#For_Component
> 
> So when you told to reproduce the bug while using the MageiaOS 
> repository, which isn't an official Mageia repository, that gave the 
> impression the bug is in MageiaOS and not in Mageia.
> 
> Can you reproduce it with just installing from Mageia directly, so 
> without MageiaOS?
> 
> If so, please add how to do that to the bug report.
> 
<snip>

CC: (none) => marja11, tmb

On 04/07/13 00:34, ÐлекÑей Ðогинов wrote:
>> Can you reproduce it with just installing from Mageia directly, 
>> so without MageiaOS?
> I'm sure If you'll build Mageia 2 with latest kernels and dkms from
> your repo, you'll see this bug. But who will build Mageia 2? I am not
> able. But to reproduce this bug with my scripts can any student and
> you Marja can also. It's easy.
>> Our kernel man, Thomas Backlund, recently had an invasive operation, 
>> btw, he has not fully recovered, yet.
> Thank's, Thomas, you very helps me. I need unionfs or aufs - Thomas
> added aufs in kernel and I have chance to build distros on Mageia 4
> based. Now I use kernel with unionfs. I wish you health.
>> One reason maybe is, that western people won't be fast to test a Russian 
>> distro for fear >that they'll get menus in Cyrillic
> I see you did not test my distro. No Cyrillic in menu. Cyrillic is
> only default in distro, but you can add in boot Menu additional
> parameter: language=english.
>> you might get irritated by how slow my brain works :-[
> I know you'll understand my scripts easy, I added many English
> comments. But for reproduce bug you must only change version of
> packages in lists of packages. I wrote in bugzilla full steps. Please,
> try.
>

(In reply to Marja van Waes from comment #10)
> On 04/07/13 00:34, ÐлекÑей Ðогинов wrote:
> >> Can you reproduce it with just installing from Mageia directly, 
> >> so without MageiaOS?
> > I'm sure If you'll build Mageia 2 with latest kernels and dkms from
> > your repo, you'll see this bug. But who will build Mageia 2? I am not
> > able. But to reproduce this bug with my scripts can any student and
> > you Marja can also. It's easy.

I intend to test your distro asap (it would help if there were 48 hours in a day). However, even if I'd manage to reproduce this bug using *mageaios* svn, that wouldn't mean a thing. We need someone who is capable *and* who has time to test with mageia.org software only.

Not a bug.

You are missing the matching driver updates in nonfree/updates that will work with 3.4 series kernels.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => INVALID

Marja, thank's for your comments and cares.
>You are missing the matching driver updates in nonfree/updates that will work >with 3.4 series kernels.
I used driver updates in nonfree/updates that must work with 3.4 series kernels, logs are in the first comment. Now I specially used packages version like comment 2, because else don't work.
to change 295.71-1 -> latest version in repo, of cause (comment 5)
This bug is about using latest kernel (even without dkms-nvidia96xx,
dkms-nvidia173, dkms-broadcom-wl, dkms-vboxadditions, dkms-virtualbox,
dkms-fglrx, dkms-nvidia-current) for Mageia 2.

Resolution: INVALID => FIXED

Well, as shown in other bugreports (like the one about radeon-firmware) you have a broken buildsystem / buildscripts

We have pushed so far four sets of 3.4 series kernel and their matching drivers and prebuilt kmods:

kernel-3.4.24-3.mga2.src.rpm
kernel-3.4.32-2.mga2.src.rpm
kernel-3.4.34-1.mga2.src.rpm
kernel-3.4.45-1.mga2.src.rpm

and everyone has passed full QA ensuring the drivers works regardless of using prebuilt modules or dkms packages.

So we _know_ they work.

So fix your scripts and you will have a lot less problems

Thomas, thank you for your work with bugs.