[Ubuntu-x-swat] [Bug 1968235] Re: Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz
I managed to bring both screens up at 30Hz by passing video resolutions as kernel parameters video=DP-3:3840x2160@30 video=DP-4:3840x2160@30 This means I do not have to do any display port replugging on startup. I still have to manually change the refresh from 30Hz to 60Hz in the settings. If there was a way to do this via cli, I would have a full workaround for this issue. I also noted that I was actually loosing the displays earlier in the boot process, maybe at some DRM/framebuffer loading point, as I was not seeing the extra few seconds of green service [OK]s, prior to wayland. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1968235 Title: Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1968235/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1968235] [NEW] Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz
Public bug reported: I recently started using a Cable-Matters-201355 with my XPS 9380 (8th Gen TB3). The dock supports dual 4K DP @ 60Hz via thunderbolt with PD input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4 high speed lanes to get dual 60Hz) Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel output) however go blank just as wayland starts up. Unplugging one of them allows the other to appear at 3840x2160@60Hz, after which I have to execute the following process to get both up and running. 1) Change the refresh rate of the active display to 30Hz, apply in Screen Display settings dialog 2) Plug the 2nd monitor in; At this point both appear in Screen Display dialog @60Hz, but the 2nd remains blank 3) Change both to 30Hz, apply; At this point the 2nd screen turns on 4) Change both to 60Hz, apply; At this point both are working at 60Hz, my desired end state Inspection of edid seems fine (below), other than the DisplaySize showing 27" instead of 32". Monitors are identical. Previously, I might be able to script my steps above using xrandr, but that seems to no longer be the case with 21.10 and wayland. I seem to be limited to the Screen Display dialog. Since I can fix by simply re-applying the settings, it seems like a bug on startup. If I could find a CLI option to allow me to script this somehow, that workaround would be just fine for myself. Lid open/closed, power via the 201344 or direct via other TB-PD port has no impact. Here's hoping for a bugfix in 22.04 or at least a way to script the display configuration. $ cat /sys/class/drm/card0-DP-4/edid | parse-edid Checksum Correct Section "Monitor" Identifier "LG HDR 4K" ModelName "LG HDR 4K" VendorName "GSM" # Monitor Manufactured week 5 of 2021 # EDID version 1.4 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "true" Horizsync 30-135 VertRefresh 56-61 # Maximum pixel clock is 560MHz #Not giving standard mode: 1152x864, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x720, 60Hz #Not giving standard mode: 1600x900, 60Hz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x800, 60Hz #Extension block found. Parsing... Modeline "Mode 6" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 0" 519.38 3840 3864 3880 3896 2160 2214 2219 +hsync -vsync Modeline "Mode 1" 266.64 3840 3848 3992 4000 2160 2214 2219 +hsync -vsync Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 5" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline "Mode 7" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Option "PreferredMode" "Mode 6" EndSection ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Description changed: I recently started using a Cable-Matters-201355 with my XPS 9380 (8th Gen TB3). The dock supports dual 4K DP @ 60Hz via thunderbolt with PD input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4 high speed lanes to get dual 60Hz) Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel output) however go blank just as wayland starts up. Unplugging one of them allows the other to appear at 3840x2160@60Hz, after which I have to execute the following process to get both up and running. 1) Change the refresh rate of the active display to 30Hz, apply in Screen Display settings dialog 2) Plug the 2nd monitor in; At this point both appear in Screen Display dialog @60Hz, but the 2nd remains blank 3) Change both to 30Hz, apply; At this point the 2nd screen turns on 4) Change both to 60Hz, apply; At this point both are working at 60Hz, my desired end state Inspection of edid seems fine (below), other than the DisplaySize - showing 27" instead of 32" + showing 27" instead of 32". Monitors are identical. Previously, I might be able to script my steps above using xrandr, but that seems to no longer be the case with 21.10 and wayland. I seem to be limited to the Screen Display dialog. Since I can fix by simply re-applying the settings, it seems like a bug on startup. If I could find a CLI option to allow me to script this somehow, that workaround would be just fine for myself. Lid open/closed, power via the 201344 or direct via other TB-PD port has no impact. Here's hoping for a bugfix in 22.04 or at least a way to script the display configuration. - $ cat /sys/class/drm/card0-DP-4/edid | parse-edid Checksum Correct Section "Monitor" - Identifier "LG HDR 4K" - ModelName "LG HDR 4K" - VendorName "GSM" - # Monitor Manufactured week 5 of 2021 - # EDID version 1.4 -
[Ubuntu-x-swat] [Bug 964266] Re: Shutdown Screen Freezes
Its not 100% repeatable, and this time I did it again to capture the Oops via my camera (no external console) and it didn't happen AND I had to still hit ESC to see the console (which I am pretty sure I didn't do, as I didn't think I had to on the console which is the reason I suggested starting with console). So perhaps this firegl oops is happening right around when the screen mode is changing to show the pretty little shutdown dots. If it happens again and my phone is handy I'll attach the [last] Oops, noting there was a series of them and only the last one will likely be visible. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/964266 Title: Shutdown Screen Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/964266/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 964266] Re: Shutdown Screen Freezes
I can confirm this. You can flip over to a console using ALT-CTL-F1 and then login, become root and use the shutdown -h now command and see the kernel oops a la fglrx. My setup is an HP DV7 with HD3400 seen via lspci as ATI RV620 [Mobility Radeon HD 3400 Series] I am uptodate with current fglrx 2:8.960-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/964266 Title: Shutdown Screen Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/964266/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 288620] Re: fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff000066 is not supported on this hardware (return code = 1) [EPR#257840]
This bug used to be transient for myself, however it now crashes my VirtualBox (4.0.12-72916~Ubuntu~natty) when switching to full screen periodically, which is a showstopper, literally for Powerpoint presentations. From the logs, it appears the VBox instance dies just prior to seeing this message. This is in addition to when I suspend my HP dv7z laptop. My last Virtbox crash switching fullscreen: Jul 29 16:28:18 repo kernel: [32629.335431] [fglrx:fireglAsyncioIntDisableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to disable interrupt source ff66 Two suspends yesterday: Aug 2 11:29:29 repo kernel: [ 2053.381119] [fglrx:fireglAsyncioIntDisableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to disable interrupt source ff66 Aug 2 15:23:22 repo kernel: [11255.334401] [fglrx:fireglAsyncioIntDisableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to disable interrupt source ff66 imac@repo:~$ lspci -vvnn -s 01:00.0 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30fc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 47 Region 0: Memory at c000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at 7000 [size=256] Region 2: Memory at d230 (32-bit, non-prefetchable) [size=64K] Expansion ROM at d232 [disabled] [size=128K] Capabilities: access denied Kernel driver in use: fglrx_pci Kernel modules: fglrx, radeon root@repo:~# dmidecode -t bios # dmidecode 2.9 SMBIOS 2.4 present. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Hewlett-Packard Version: F.49 Release Date: 08/17/2009 ROM Size: 1024 kB -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/288620 Title: fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) [EPR#257840] To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/288620/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 755471] Re: AMD Radeon HD 6550M: Driver was not installed or is not functioning properly.
I tripped on the issue of unity-support-test failing on my Natty 11.04 running X(vnc4server) on a Xen domu. Nothing fatal for myself, as I do not want 3D support, but might a useful way to reproduce. [ 623.693687] show_signal_msg: 15 callbacks suppressed [ 623.693693] unity_support_t[1703]: segfault at 7f5ebd0f0c90 ip 7f5ebd6b4eed sp 7fff22cdf880 error 7 in libGL.so.1.2[7f5ebd68d000+6e000] [ 623.736957] unity_support_t[1705]: segfault at 7ff3d9955c90 ip 7ff3d9f19eed sp 7fff589cd840 error 7 in libGL.so.1.2[7ff3d9ef2000+6e000] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/755471 Title: AMD Radeon HD 6550M: Driver was not installed or is not functioning properly. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 288620] Re: fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff000066 is not supported on this hardware (return code = 1) [EPR#257840]
Running Maverick 10.10 / fglrx 2:8.780-0ubuntu2 / 2.6.35-22.34 I don't have suspend issues .. I have tested multiple times on my dv5z and dv7z which have ATI 3200/3400 that both still show this message. On first boot/resume: [fglrx] IRQ 47 Enabled [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) On suspend: [fglrx:fireglAsyncioIntDisableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to disable interrupt source ff66 [fglrx] IRQ 47 Disabled using MSI as expected In /proc/interrupts 46: 0 0 PCI-MSI-edge hda_intel 47:691 321594 PCI-MSI-edge fglrx...@pci:1:0:0 I wonder if it is related to the only other IRQ message I see which is for the ATI audio HDMI component, as I see a similar message for that piece, noting below that Card #1 is the ATI component. [ 58.462714] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj. # aplay -l List of PLAYBACK Hardware Devices No protocol specified xcb_connection_has_error() returned true card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: STAC92xx Digital [STAC92xx Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 I have no ALSA playback issues either via the HDMI or other ports -- fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) [EPR#257840] https://bugs.launchpad.net/bugs/288620 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 609938] Re: fglrx fails build on 2.6.35-10-generic
Initially my system was unusable, but I have removed fglrx for now and enabled radeon by modifying my xorg.conf (previously created by the amdccle tool) Driver radeon in my xorg.conf where it used to say fglrx.. performance seems surprisingly good with compiz, etc. Its a good workaround for now that enables gnome whilst we wait for fglrx to catch up again -- fglrx fails build on 2.6.35-10-generic https://bugs.launchpad.net/bugs/609938 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625787] Re: utsrelease.h not found during DKMS build
My fglrx worked fine on 10.04 to the best of my knowledge. After performing an upgrade to 10.10 on 9/10 I experienced the same output trying to run dkms build manually. Removing fglrx and my xorg.conf allowed me to reboot into a GUI using Radeon.. which I am using now. In the process of debugging, I purged all dkms cruft (old modules) and tried purging and re-adding the fglrx packages. -- utsrelease.h not found during DKMS build https://bugs.launchpad.net/bugs/625787 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 560571] Re: BUG: using smp_processor_id() in preemptible [00000000] code: Xorg/1157
Guess I'll be switching to -generic until this is resolved.. battery aside, I prefer preempt for desktop responsiveness. -- BUG: using smp_processor_id() in preemptible [] code: Xorg/1157 https://bugs.launchpad.net/bugs/560571 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 288620] Re: fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff000066 is not supported on this hardware (return code = 1) [EPR#257840]
Further to my previous post, I am now running Lucid on my dv5 with the current -preempt kernel and no longer seeing this message, however I am probably going back to -generic due to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/560571 -- fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) [EPR#257840] https://bugs.launchpad.net/bugs/288620 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 288620] Re: fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff000066 is not supported on this hardware (return code = 1) [EPR#257840]
Well, I have this message on my dv7z also; Didn't notice it since things appear to run fine. [ 28.318371] [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) Running F.47 BIOS on dv7-1000 CTO Kernel: 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:02:26 UTC 2010 x86_64 GNU/Linux 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series Subsystem: Hewlett-Packard Company Device 30fc Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at c000 (32-bit, prefetchable) [size=256M] I/O ports at 7000 [size=256] Memory at d230 (32-bit, non-prefetchable) [size=64K] Expansion ROM at d232 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Capabilities: [100] Vendor Specific Information ? Kernel driver in use: fglrx_pci Kernel modules: fglrx, radeon -- fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) [EPR#257840] https://bugs.launchpad.net/bugs/288620 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 288620] Re: fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff000066 is not supported on this hardware (return code = 1) [EPR#257840]
Following up on my previous comment, I now believe my freeze issue may be overheating. I still receive these firegl messages intermittently with no obvious impact on my system. Today I have received none. I can see one from a few days ago in my syslog -- fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) [EPR#257840] https://bugs.launchpad.net/bugs/288620 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 288620] Re: fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff000066 is not supported on this hardware (return code = 1) [EPR#257840]
This affects my HP dv5z F.37 BIOS, running Karmic 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux [ 279.598245] [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to enable interrupt source ff34 01:05.0 VGA compatible controller: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics] Subsystem: Hewlett-Packard Company Device 30f2 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 29 Region 0: Memory at c000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at 5000 [size=256] Region 2: Memory at d230 (32-bit, non-prefetchable) [size=64K] Region 5: Memory at d220 (32-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: fee0300c Data: 41a1 Kernel driver in use: fglrx_pci Kernel modules: fglrx, radeon I also experience a hard system freeze; blank black screen (still backlit), network/ssh dead, console/alt-ctrl-fn unresponsive, hd activity light frozen. Using screen remotely to tail a console via ssh from another system I have seen no output in dmesg/messages/syslog to indicate an issue or that the freeze is related to this specific error, however I have my suspicions. The freeze happens about twice per week, though twice already today prompting me to have a closer look. -- fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is not supported on this hardware (return code = 1) [EPR#257840] https://bugs.launchpad.net/bugs/288620 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 394985] [NEW] fglrx: Unknown symbol find_task_by_vpid
Public bug reported: After updating to 2.6.31 and adding blacklists for drm, radeon and ttm (module will not attempt to load with these other conflicting modules present), I receive this unkown symbol message in dmesg. fglrx does not load. Notably, in previous 2.6.30 kernel we have no problem after unloading a i915 conflicting module (no idea why this is happening, tracked separately at https://bugs.launchpad.net/ubuntu/+source/fglrx- installer/+bug/392039). So its back to 2.6.30 for compiz for now. A quick google did not help me figure out how to resolve this missing dependency kernel dependency. Linux imac-karmic 2.6.31-1-generic #14-Ubuntu SMP Thu Jul 2 16:02:38 UTC 2009 x86_64 GNU/Linux ii fglrx-kernel-source 2:8.620-0ubuntu3 fglrx, 8.620, 2.6.30-8-generic, x86_64: installed fglrx, 8.620, 2.6.31-1-generic, x86_64: installed ProblemType: Bug Architecture: amd64 Date: Thu Jul 2 22:33:09 2009 DistroRelease: Ubuntu 9.10 MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Package: fglrx-kernel-source 2:8.620-0ubuntu3 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-1-generic root=UUID=27009b37-d288-4f07-9892-1fe2c70be35f ro quiet splash ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-1.14-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu4 libgl1-mesa-glx 7.5~rc4-1ubuntu2 libdrm2 2.4.11-0ubuntu1 xserver-xorg-video-intel 2:2.7.99.1+git20090602.ec2fde7c-0ubuntu4 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu1 SourcePackage: fglrx-installer Uname: Linux 2.6.31-1-generic x86_64 dmi.bios.date: 10/02/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30FD dmi.board.vendor: Hewlett-Packard dmi.board.version: 01.69 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd10/02/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr1:rvnHewlett-Packard:rn30FD:rvr01.69:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 1 dmi.sys.vendor: Hewlett-Packard fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-1-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- fglrx: Unknown symbol find_task_by_vpid https://bugs.launchpad.net/bugs/394985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 394985] Re: fglrx: Unknown symbol find_task_by_vpid
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/28645762/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/28645763/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/28645764/Dependencies.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/28645765/GdmLog.txt ** Attachment added: GdmLogOld.txt http://launchpadlibrarian.net/28645766/GdmLogOld.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/28645767/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/28645768/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/28645769/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/28645770/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/28645771/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/28645772/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/28645773/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/28645774/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/28645775/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/28645776/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/28645777/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/28645778/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/28645779/glxinfo.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/28645780/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/28645781/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/28645782/xkbcomp.txt -- fglrx: Unknown symbol find_task_by_vpid https://bugs.launchpad.net/bugs/394985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 392039] Re: [HD 3600] fglrx DRI initialization failed
I am also seeing this on my dv7 laptop, 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series Linux imac-karmic 2.6.30-8-generic #9-Ubuntu SMP Wed Jun 3 15:38:38 UTC 2009 x86_64 GNU/Linux ii fglrx-kernel-source 2:8.620-0ubuntu2 Kernel module source for the ATI graphics ac Removing i915, then drm resolved the issue for me also. Adding to my local blacklist for now. ** Changed in: fglrx-installer (Ubuntu) Status: Incomplete = Confirmed ** Summary changed: - [HD 3600] fglrx DRI initialization failed + [Mobility Radeon HD] fglrx DRI initialization failed -- [Mobility Radeon HD] fglrx DRI initialization failed https://bugs.launchpad.net/bugs/392039 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
