Bug 7212 - kernel-3.5* and any fglrx disable X on this machine, due to ??
Summary: kernel-3.5* and any fglrx disable X on this machine, due to ??
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-26 18:55 CEST by Dick Gevers
Modified: 2012-09-14 06:05 CEST (History)
0 users

See Also:
Source RPM: kernel-server-3.5.3-3.mga3-1-1.mga3
CVE:
Status comment:


Attachments
dmesg from last working kernel (59.77 KB, text/plain)
2012-08-26 18:55 CEST, Dick Gevers
Details
newest-kernel-dmesg (60.90 KB, application/octet-stream)
2012-08-26 19:03 CEST, Dick Gevers
Details
/proc/cpuinfo (6.55 KB, application/octet-stream)
2012-08-26 19:04 CEST, Dick Gevers
Details
/proc/iomem (2.32 KB, application/octet-stream)
2012-08-26 19:05 CEST, Dick Gevers
Details
/proc/ioports (1.90 KB, application/octet-stream)
2012-08-26 19:06 CEST, Dick Gevers
Details
lsmod (5.50 KB, application/octet-stream)
2012-08-26 19:06 CEST, Dick Gevers
Details
lspci -vvv (60.53 KB, application/octet-stream)
2012-08-26 19:07 CEST, Dick Gevers
Details
latest working Xorg.log (69.34 KB, text/x-log)
2012-08-26 21:32 CEST, Dick Gevers
Details
not working Xorg log (12.00 KB, application/octet-stream)
2012-08-26 21:33 CEST, Dick Gevers
Details

Description Dick Gevers 2012-08-26 18:55:00 CEST
Description of problem:
Since kernel 3.5.0, upto 3.5.2-1 and inl. kernel-tmb-3.5.2-1, I cannot get X to start with either fglrx-8.980-3.mga3 or fglrx-8.982-1.mga3

Nor can I cange to any tty to see what's happening, nor restart X via [ alt + ctrl + backspace]

Same kernel on an nvidia laptop work flawlessly. Also booting seems quite okay until the moment X is supposed to start.

The only thing I can find in the logs which is different from before is
this:

Jul 28 09:45:31 dvg kernel: [   13.289114] ACPI Warning:
0x0000000000000830-0x0000000000000833 SystemIO conflicts with Region \PMRG
1 (20120320/utaddress-251)
Jul 28 09:45:31 dvg kernel: [   13.289118] ACPI Warning:
0x0000000000000830-0x0000000000000833 SystemIO conflicts with Region
\_SB_.PCI0.SBRG.SMIE 2 (20120320/utaddress-251) 
Jul 28 09:45:31 dvg kernel: [   13.289122] lpc_ich: Resource conflict(s)
found affecting iTCO_wdt
Jul 28 09:45:31 dvg kernel: [   13.289124] ACPI Warning:
0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \PMRG
1 (20120320/utaddress-251) 
Jul 28 09:45:31 dvg kernel: [   13.289128] ACPI Warning:
0x0000000000000500-0x000000000000053f SystemIO conflicts with Region \GPS0
1 (20120320/utaddress-251) 
Jul 28 09:45:31 dvg kernel:[   13.289131] lpc_ich: Resource conflict(s)
found affecting gpio_ich 
Jul 28 09:45:31 dvg kernel: [   13.558339] ACPI Warning:
0x0000000000000400-0x000000000000041f SystemIO conflicts with Region \SMRG
1 (20120320/utaddress-251)

while if using the older kernels I only get this:

Jul 28 09:50:18 dvg kernel: [   14.724078] ACPI Warning:
0x0000000000000400-0x000000000000041f SystemIO conflicts with Region \SMRG
1 (20120320/utaddress-251) 
Jul 28 09:50:18 dvg kernel: [   38.563510] ACPI
Warning: 0x0000000000000295-0x0000000000000296 SystemIO conflicts with
Region \_SB_.PCI0.SBRG.SIOR.HWRE 1 (20120320/utaddress-251) 

but I see no real problems anywhere with the older kernels.

I will attach all the usual info needed for any kernel bug report.
Comment 1 Dick Gevers 2012-08-26 18:55:42 CEST
Created attachment 2675 [details]
dmesg from last working kernel
Comment 2 Dick Gevers 2012-08-26 19:03:15 CEST
Created attachment 2676 [details]
newest-kernel-dmesg
Comment 3 Dick Gevers 2012-08-26 19:04:32 CEST
Created attachment 2677 [details]
/proc/cpuinfo
Comment 4 Dick Gevers 2012-08-26 19:05:37 CEST
Created attachment 2678 [details]
/proc/iomem
Comment 5 Dick Gevers 2012-08-26 19:06:27 CEST
Created attachment 2679 [details]
/proc/ioports
Comment 6 Dick Gevers 2012-08-26 19:06:58 CEST
Created attachment 2680 [details]
lsmod
Comment 7 Dick Gevers 2012-08-26 19:07:41 CEST
Created attachment 2681 [details]
lspci -vvv
Comment 8 Dick Gevers 2012-08-26 21:32:12 CEST
Created attachment 2683 [details]
latest working Xorg.log
Comment 9 Dick Gevers 2012-08-26 21:33:20 CEST
Created attachment 2684 [details]
not working Xorg log

It won't be much help, but I should include it in my report.
Comment 10 Dick Gevers 2012-08-27 19:21:40 CEST
Same with kernel-server-3.5.3-1.mga3 and fglrx-kernel-3.5.3-server-1.mga3-8.982-2.mga3.nonfree

Source RPM: kernel-server-3.5.2-1.mga3-1-1.mga3 => kernel-server-3.5.3-1.mga3-1-1.mga3

Comment 11 Dick Gevers 2012-08-31 07:56:00 CEST
Alas. Same again with kernel-server-3.5.3-2.mga3 and fglrx-kernel-3.5.3-server-2.mga3-8.982-3.mga3.nonfree

Source RPM: kernel-server-3.5.3-1.mga3-1-1.mga3 => kernel-server-3.5.3-2.mga3-1-1.mga3

Comment 12 Dick Gevers 2012-09-12 20:27:49 CEST
And again with 3.5.3-3

Source RPM: kernel-server-3.5.3-2.mga3-1-1.mga3 => kernel-server-3.5.3-3.mga3-1-1.mga3

Comment 13 Dick Gevers 2012-09-14 06:05:39 CEST
Working with ati instead of radeonhd driver

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.