Hi Thomas ! Trying to understand why I can't use the same xorg configuration for kernel-rt as for kernel-server I explored a little. I told in previous bug reports (bug 8515 bug 9120 ) that though the dkms nvidia module is built during the installation of the realtime kernels... when booting, the system freezes when starting X needing to use magic keys to stop (Alt+Syst+R S E I U O ) I looked for differences between the two sources... and couldn't find the explanation. What could be useful to discover the reason why the system freezes ? Nevertheless : as a side I found that this useful patch : ata-prefer-ata-drivers-over-ide-drivers-when-both-are-built.patch is missing in kernel-rt (if it's not present we need to add an option in grub : rdloaddriver=pata_xxx ) I looked at cauldron source : this patch is missing too for kernel-rt : this will lead to the problem we encountered with all the first kernels in Mageia2 and that is no more present in Mageia3. Hope this may help Philippe
CC: (none) => tmbWhiteboard: (none) => MGA2 CAULDRON KERNEL-
I think my comment was not clear, mixing several things The first point I discovered is about this patch (part of mageia bundled patches): ata-prefer-ata-drivers-over-ide-drivers-when-both-are-built.patch which resolves : bug 6310 (the last updated kernels for Mageia2 don't need anymore the workaround : adding the kernel option "rdloaddriver=pata_xxx" xxx being via or amd or jmicron or piix) the Cauldron's Kernels are OK too, with this patch But if the kernel-rt have not this patch (neither in updates for Mageia2 nor in Cauldron), the bug 6310 will reappear, only for kernel-rt inside Mageia3... Maybe would it be more clear to open several bugs for kernel-rt ?
Whiteboard: MGA2 CAULDRON KERNEL- => MGA2 CAULDRON KERNEL-RT
no need for several bugreports for the ata-prefer-ata-drivers-over-ide patch
Hi Thomas I meant use this bug report as a tracker and open different bug reports linked to it to be clearer one about this ata-ide.patch one about the x problem other about other things I may find but if this one can be used for all purposes about Kernel-rt it's OK Regards Philippe
some investigations about the x problem If I modify the xorg.conf file, (which works well for server-kernels) only replacing nvidia by nouveau in the Section "Device" Section "Device" Identifier "device1" VendorName "nVidia Corporation" BoardName "NVIDIA GeForce 6100 to GeForce 360" Driver "nvidia" I get no freeze for Kernel-rt (but I loose some useful features that can only be provided by the proprietary driver) I don't know where to look for an explanation ... or to find a message (the xorg.log is useless : only shortened) could there be something near what happens in bug 8863 (bad initrd-xx.img) ?
> The first point I discovered is about this patch (part of mageia bundled > patches): > ata-prefer-ata-drivers-over-ide-drivers-when-both-are-built.patch > which resolves : bug 6310 > > (the last updated kernels for Mageia2 don't need anymore the workaround : > adding the kernel option "rdloaddriver=pata_xxx" xxx being via or amd or > jmicron or piix) > > the Cauldron's Kernels are OK too, with this patch > > But if the kernel-rt have not this patch (neither in updates for Mageia2 nor > in Cauldron), the bug 6310 will reappear, only for kernel-rt inside > Mageia3... > Looking again about this missing patch inside the last updated kernel-rt-3.4.34-0.rt47.1 I tried to remove the rdloaddriver=pata_amd option in the line of this kernel in /boot/grub/menu.lst (it was automatically written when I installed this new kernel with the same skeleton as for the kernel of the initial installation) Without this option, for this kernel I don't have any problem with the IDE DVD drive and DVDrw drive (they appear correctly in /dev/ as sr0 correctly linked to /dev/cdrom and /dev/cdrw and to /dev/dvd and /dev/dvdrw and as sr1 correctly linked to /dev/cdrom1 and to /dev/dvd1) Surprising indeed ! Would that mean that the patch is no more needed for the 3.4 series (may it be removed for the normal kernels ???) or is this the consequence of the fact that the initrd.img was built with this option...
Hi Philippe. Is this bug still valid? If so please put a more detailed summary. If valid in cauldron, set version to cauldron and add MGA2TOO and MGA3TOO in whiteboard.
CC: (none) => stormiSource RPM: (none) => kernel-rtWhiteboard: MGA2 CAULDRON KERNEL-RT => (none)
Keywords: (none) => NEEDINFO
Hi Samuel This bug is only valid for Mageia 2 On an up to date Mageia 3, the kernel-rt (both of kernel-rt-3.8.13-0.rt8.1.mga3-1-1.mga3.i586 and kernel-rt-3.8.13.4-0.rt14.2.mga3-1-1.mga3.i586) builds the dkms nvidia module during installation and can use this module without the problem I encountered on Mageia2 !
Summary: Some things to improve for kernel-rt => Kernel-rt freezes with nvidia module built by dkms on Mageia2 : it needs nouveau !
Keywords: NEEDINFO => TriagedAssignee: bugsquad => tmb
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD