[Ubuntu-x-swat] [Bug 871424] Re: [Thinkpad X100e] Ctrl+Alt+UpArrow generates no keycode
Still holds, no magic fix happened. ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/871424 Title: [Thinkpad X100e] Ctrl+Alt+UpArrow generates no keycode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/871424/+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 855943] Re: Installing then uninstalling FGLRX makes Oneiric's Unity unbootable
Confirming the fix in oneiric with fglrx 8.881-0ubuntu4.1. Thanks a lot ! -- 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/855943 Title: Installing then uninstalling FGLRX makes Oneiric's Unity unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/855943/+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 855943] Re: Installing then uninstalling FGLRX makes Oneiric's Unity unbootable
Agreed, for non-techie users it’s going to break their systems in a way they can’t fix (neither Unity nor Unity 2D work with the broken libGL). -- 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/855943 Title: Installing then uninstalling FGLRX makes Oneiric's Unity unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/855943/+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 855943] Re: Installing then uninstalling FGLRX makes Oneiric's Unity unbootable
Here you go ! ** Attachment added: jockey.log https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/855943/+attachment/2532992/+files/jockey.log -- 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/855943 Title: Installing then uninstalling FGLRX makes Oneiric's Unity unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/855943/+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 871424] [NEW] [Thinkpad X100e] Ctrl+Alt+UpArrow generates no keycode
Public bug reported:
On oneiric, I can’t go to workspaces above the current one because the
Ctrl+Alt+Up arrow key combination generates no code.
Other equivalents like Ctrl+Alt+{Left,Right,Down} work just fine.
Combinations like Ctrl+Up and Alt+Up also work.
Here’s the output of xev.
###
For Ctrl+Alt+Down :
KeyPress event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1745539, (897,445), root:(964,498),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1745914, (897,445), root:(964,498),
state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 36, synthetic NO, window 0x3e1,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 36, synthetic NO, window 0x3e1,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 36, synthetic NO, window 0x0,
keys: 0 0 0 0 32 0 0 0 1 0 0 0 0 0 16 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1750632, (897,445), root:(964,498),
state 0xc, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1751380, (897,445), root:(964,498),
state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1751810, (897,445), root:(964,498),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1752931, (897,445), root:(964,498),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1753046, (897,445), root:(964,498),
state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1754523, (897,445), root:(964,498),
state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 1754928, (897,445), root:(964,498),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
###
For Ctrl+Alt+Up :
KeyPress event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 2644386, (607,278), root:(674,331),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 2645012, (607,278), root:(674,331),
state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 2647112, (607,278), root:(674,331),
state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 2647393, (607,278), root:(674,331),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
###
For Up :
KeyPress event, serial 33, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 2727742, (993,538), root:(1060,591),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
root 0x14e, subw 0x0, time 2728135, (993,538), root:(1060,591),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
ProblemType: Bug
[Ubuntu-x-swat] [Bug 871424] Re: [Thinkpad X100e] Ctrl+Alt+UpArrow generates no keycode
** Description changed:
On oneiric, I can’t go to workspaces above the current one because
Ctrl+Alt+Up arrow key combination generates no code.
Other equivalents like Ctrl+Alt+{Left,Right,Down} work just fine.
Combination like Ctrl+Up and Alt+Up also work.
Here’s the input of xev.
+ ###
For Ctrl+Alt+Down :
KeyPress event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1745539, (897,445), root:(964,498),
- state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
- XLookupString gives 0 bytes:
- XmbLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw 0x0, time 1745539, (897,445), root:(964,498),
+ state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
+ XLookupString gives 0 bytes:
+ XmbLookupString gives 0 bytes:
+ XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1745914, (897,445), root:(964,498),
- state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
- XLookupString gives 0 bytes:
- XmbLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw 0x0, time 1745914, (897,445), root:(964,498),
+ state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
+ XLookupString gives 0 bytes:
+ XmbLookupString gives 0 bytes:
+ XFilterEvent returns: False
FocusOut event, serial 36, synthetic NO, window 0x3e1,
- mode NotifyGrab, detail NotifyAncestor
+ mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 36, synthetic NO, window 0x3e1,
- mode NotifyUngrab, detail NotifyAncestor
+ mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 36, synthetic NO, window 0x0,
- keys: 0 0 0 0 32 0 0 0 1 0 0 0 0 0 16 0
-0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
+ keys: 0 0 0 0 32 0 0 0 1 0 0 0 0 0 16 0
+ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1750632, (897,445), root:(964,498),
- state 0xc, keycode 116 (keysym 0xff54, Down), same_screen YES,
- XLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw 0x0, time 1750632, (897,445), root:(964,498),
+ state 0xc, keycode 116 (keysym 0xff54, Down), same_screen YES,
+ XLookupString gives 0 bytes:
+ XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1751380, (897,445), root:(964,498),
- state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
- XLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw 0x0, time 1751380, (897,445), root:(964,498),
+ state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
+ XLookupString gives 0 bytes:
+ XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1751810, (897,445), root:(964,498),
- state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
- XLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw 0x0, time 1751810, (897,445), root:(964,498),
+ state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
+ XLookupString gives 0 bytes:
+ XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1752931, (897,445), root:(964,498),
- state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
- XLookupString gives 0 bytes:
- XmbLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw 0x0, time 1752931, (897,445), root:(964,498),
+ state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
+ XLookupString gives 0 bytes:
+ XmbLookupString gives 0 bytes:
+ XFilterEvent returns: False
KeyPress event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1753046, (897,445), root:(964,498),
- state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
- XLookupString gives 0 bytes:
- XmbLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw 0x0, time 1753046, (897,445), root:(964,498),
+ state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
+ XLookupString gives 0 bytes:
+ XmbLookupString gives 0 bytes:
+ XFilterEvent returns: False
KeyRelease event, serial 36, synthetic NO, window 0x3e1,
- root 0x14e, subw 0x0, time 1754523, (897,445), root:(964,498),
- state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
- XLookupString gives 0 bytes:
- XFilterEvent returns: False
+ root 0x14e, subw
[Ubuntu-x-swat] [Bug 749553] Re: Changing resolution leaves red display identification box
Fixed a long time ago. ** Changed in: fglrx-installer (Ubuntu) Status: Confirmed = Fix Released -- 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/749553 Title: Changing resolution leaves red display identification box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/749553/+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 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
The bug was still marked opened for zUbuntu (zSeries port of Ubuntu) which makes no sense, closed. ** Changed in: fglrx-installer (zUbuntu) Status: New = Fix Released -- 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/494699 Title: Does not support current Lucid kernel (2.6.32) or xserver (1.7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/494699/+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 749553] [NEW] Changing resolution leaves red display identification box
Public bug reported: When changing the display resolution outside of Catalyst Control Center, the red box with the display identification number is displayed, and stays on screen. It can be reproduced with xrandr, with the Screens Gnome tool, and with any other application changing the resolution. To get rid of the red box, you need to launch and close Catalyst Control Center. This practically makes it unacceptable to use an application in non- desktop resolution… ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Description changed: - When changing the display resolution outside of Catalyst Control Center, the red box with the display identification number gets displayed. + When changing the display resolution outside of Catalyst Control Center, the red box with the display identification number is displayed, and stays on screen. It can be reproduced with xrandr, with the Screens Gnome tool, and with any other application changing the resolution. To get rid of the red box, you need to launch and close Catalyst Control Center. This practically makes impossible to use an application in non-desktop resolution… ** Description changed: When changing the display resolution outside of Catalyst Control Center, the red box with the display identification number is displayed, and stays on screen. It can be reproduced with xrandr, with the Screens Gnome tool, and with any other application changing the resolution. To get rid of the red box, you need to launch and close Catalyst Control Center. - This practically makes impossible to use an application in non-desktop - resolution… + This practically makes it unacceptabl to use an application in non- + desktop resolution… ** Description changed: When changing the display resolution outside of Catalyst Control Center, the red box with the display identification number is displayed, and stays on screen. It can be reproduced with xrandr, with the Screens Gnome tool, and with any other application changing the resolution. To get rid of the red box, you need to launch and close Catalyst Control Center. - This practically makes it unacceptabl to use an application in non- + This practically makes it unacceptable to use an application in non- desktop resolution… -- 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/749553 Title: Changing resolution leaves red display identification box ___ 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 570835] Re: [rs780] System freeze on backlight change with KMS
Fixed in Maverick. -- You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. https://bugs.launchpad.net/bugs/570835 Title: [rs780] System freeze on backlight change with KMS ___ 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 557065] Re: frozen mouse/ keyboard
Affecting bug to xserver-xorg-input-evdev like duplicate #576351. ** Package changed: ubuntu = xserver-xorg-input-evdev (Ubuntu) -- frozen mouse/ keyboard https://bugs.launchpad.net/bugs/557065 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev 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 570835] [NEW] [rs780] System freeze on backlight change with KMS
Public bug reported: Binary package hint: xserver-xorg-video-ati This bug is referenced upstream. An annoying problem is that the gnome power manager must try and change the backlight brightness while loading the live session user, thus the live CD/USB just freezes a short time after X is up. Maybe an exception could be added to disable KMS for this chip for Lucid and avoid the freeze ? UMS works fine with acceleration. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- [rs780] System freeze on backlight change with KMS https://bugs.launchpad.net/bugs/570835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 570835] Re: [rs780] System freeze on backlight change with KMS
** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New = Confirmed ** Bug watch added: Linux Kernel Bug Tracker #15166 http://bugzilla.kernel.org/show_bug.cgi?id=15166 ** Also affects: xserver-xorg-driver-ati via http://bugzilla.kernel.org/show_bug.cgi?id=15166 Importance: Unknown Status: Unknown -- [rs780] System freeze on backlight change with KMS https://bugs.launchpad.net/bugs/570835 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. ___ 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 570835] Re: [rs780] System freeze on backlight change with KMS
r ** Attachment added: Output of lspci -vvnn http://launchpadlibrarian.net/45763179/lspci-vvnn -- [rs780] System freeze on backlight change with KMS https://bugs.launchpad.net/bugs/570835 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. ___ 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 570835] Re: [rs780] System freeze on backlight change with KMS
As a workaround, you can disable KMS by giving radeon.modeset=0 to the kernel line. You'll need to do it: 1. For the live CD (hit F6) 2. For the first boot after installation (hold shift to get the GRUB menu, press E to edit the boot entry) The updated kernel line should end with: (…) quiet splash radeon.modeset=0 3. To make it permanent, set the GRUB_CMDLINE_LINUX variable in /etc/default/grub like this: GRUB_CMDLINE_LINUX=radeon.modeset=0 Don't forget to run update-grub afterwards. Affected laptops include at least: - the Lenovo X100e I use; - the HP Compaq 6735b mentioned in the upstream bug report. ** Tags added: freeze -- [rs780] System freeze on backlight change with KMS https://bugs.launchpad.net/bugs/570835 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. ___ 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 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
@danube Your graphic chip is not supported by the binary fglrx driver, you should probably file a new bug against the xserver-xorg-video-radeon free software package. @mattrenfer Your graphic chip isn't supported by fglrx either, you should stick to the radeon driver. Please note that fglrx only supports most recent AMD products : Desktop : Radeon HD 24xx to 59xx. Laptop : Mobility Radeon HD 24xx to 48xx. Integrated : Radeon HD 30xx, 31xx, 32xx, 33xx and 42xx. The fglrx driver won't work with older graphic chip, whether HD pre 24xx Radeons, or all former non HD Radeons. Users of these types of hardware should stay with the (default) radeon driver. -- Does not support current Lucid kernel (2.6.32) or xserver (1.7) https://bugs.launchpad.net/bugs/494699 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 494699] Re: Does not support current Lucid kernel (2.6.32)
There has been a trivial patch in Debian unstable for a while to make recent fglrx build with linux 2.6.32. The real show stopper though, is that Catalyst at least up to 10.1 won't work with Xorg 7.5 found in lucid. ** Patch added: 05-fix_missing_signal_include.diff http://launchpadlibrarian.net/39303471/05-fix_missing_signal_include.diff -- Does not support current Lucid kernel (2.6.32) https://bugs.launchpad.net/bugs/494699 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
