| Summary: | xserver doesn't start with udev 172 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | gil gil <puntogil> |
| Component: | RPM Packages | Assignee: | Anssi Hannula <anssi.hannula> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | zen25000 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
Xorg.0.log
dmesg Xorg.0.log with kernel 3.x dsmeg with 3.0.0-desktop586-0.rc7.2.1.mga2 |
||
|
Description
gil gil
2011-07-16 16:04:36 CEST
Created attachment 654 [details]
Xorg.0.log
Same issue here with the 173 nvidia that Anssi committed today.
Xorg.0.log attached.
Created attachment 655 [details]
dmesg
/var/log/dmesg
This looks like the issue I had when I was booting without "nokmsboot" a month or two back, but this time the menu.lst kernel line does have "nokmsboot".
Created attachment 656 [details]
Xorg.0.log with kernel 3.x
Created attachment 657 [details]
dsmeg with 3.0.0-desktop586-0.rc7.2.1.mga2
I managed a workaround by blacklisting nouveau - now I can use cauldron with nvidia. :) CC:
(none) =>
zen25000
Anssi Hannula
2011-07-17 00:40:24 CEST
Status:
NEW =>
ASSIGNED Fixed in udev 173-3mga2. A patch had been inadvertently disabled, causing a random display kernel module supporting the device to be loaded instead of the one which is needed by the presently configured X driver. Thanks for the report. Status:
ASSIGNED =>
RESOLVED |