This is a new Lenovo X1 Carbon (v3).
I booted up Fedora-Live-KDE-x86_64-22-TC2.iso
It boots OK, but on switching to VT (alt-ctrl-f2), the screen starts flashing and is unusable.
The video is 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
On 05/07/2015 12:37 PM, Neal Becker wrote:
This is a new Lenovo X1 Carbon (v3).
I booted up Fedora-Live-KDE-x86_64-22-TC2.iso
It boots OK, but on switching to VT (alt-ctrl-f2), the screen starts flashing and is unusable.
The video is 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
Don't the X1 systems have the function keys remapped in BIOS to actual functions, as opposed to F1-12? IIRC, there's either a setting in the firmware or a (soft) switch on the keyboard somewhere to turn this off.
Dan
Dan Mossor wrote:
On 05/07/2015 12:37 PM, Neal Becker wrote:
This is a new Lenovo X1 Carbon (v3).
I booted up Fedora-Live-KDE-x86_64-22-TC2.iso
It boots OK, but on switching to VT (alt-ctrl-f2), the screen starts flashing and is unusable.
The video is 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
Don't the X1 systems have the function keys remapped in BIOS to actual functions, as opposed to F1-12? IIRC, there's either a setting in the firmware or a (soft) switch on the keyboard somewhere to turn this off.
Dan
I don't think I explained this well. I can get a VT by hitting alt-ctrl-f2, for example, but it is not usable. I can see there is a login prompt, but the screen is going nuts flashing - the video is all screwed up.
On Thu, 2015-05-07 at 14:16 -0400, Neal Becker wrote:
Dan Mossor wrote:
On 05/07/2015 12:37 PM, Neal Becker wrote:
This is a new Lenovo X1 Carbon (v3).
I booted up Fedora-Live-KDE-x86_64-22-TC2.iso
It boots OK, but on switching to VT (alt-ctrl-f2), the screen starts flashing and is unusable.
The video is 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
Don't the X1 systems have the function keys remapped in BIOS to actual functions, as opposed to F1-12? IIRC, there's either a setting in the firmware or a (soft) switch on the keyboard somewhere to turn this off.
Dan
I don't think I explained this well. I can get a VT by hitting alt -ctrl-f2, for example, but it is not usable. I can see there is a login prompt, but the screen is going nuts flashing - the video is all screwed up.
IIRC someone's reported this already, also on the X1 Carbon, so I think it's a driver issue there.
Adam Williamson wrote:
On Thu, 2015-05-07 at 14:16 -0400, Neal Becker wrote:
Dan Mossor wrote:
On 05/07/2015 12:37 PM, Neal Becker wrote:
This is a new Lenovo X1 Carbon (v3).
I booted up Fedora-Live-KDE-x86_64-22-TC2.iso
It boots OK, but on switching to VT (alt-ctrl-f2), the screen starts flashing and is unusable.
The video is 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
Don't the X1 systems have the function keys remapped in BIOS to actual functions, as opposed to F1-12? IIRC, there's either a setting in the firmware or a (soft) switch on the keyboard somewhere to turn this off.
Dan
I don't think I explained this well. I can get a VT by hitting alt -ctrl-f2, for example, but it is not usable. I can see there is a login prompt, but the screen is going nuts flashing - the video is all screwed up.
IIRC someone's reported this already, also on the X1 Carbon, so I think it's a driver issue there.
Could have been me :)
1. It does not happen with f21 2. Where should I report this (other than here?)
On Thu, 2015-05-07 at 14:54 -0400, Neal Becker wrote:
Could have been me :)
- It does not happen with f21
- Where should I report this (other than here?)
Kernel or freedesktop bugzilla against the appropriate graphics driver, probably, but it'd be good to run through the graphics debugging process and see if you see any indicative messages (boot with drm.debug=14, reproduce the issue, and look in the journal for messages from the kernel graphics driver, basically).
Adam Williamson wrote:
On Thu, 2015-05-07 at 14:54 -0400, Neal Becker wrote:
Could have been me :)
- It does not happen with f21
- Where should I report this (other than here?)
Kernel or freedesktop bugzilla against the appropriate graphics driver, probably, but it'd be good to run through the graphics debugging process and see if you see any indicative messages (boot with drm.debug=14, reproduce the issue, and look in the journal for messages from the kernel graphics driver, basically).
How do I get to edit kernel command line in f22 live usb?
On Thu, 2015-05-07 at 15:30 -0400, Neal Becker wrote:
Adam Williamson wrote:
On Thu, 2015-05-07 at 14:54 -0400, Neal Becker wrote:
Could have been me :)
- It does not happen with f21
- Where should I report this (other than here?)
Kernel or freedesktop bugzilla against the appropriate graphics driver, probably, but it'd be good to run through the graphics debugging process and see if you see any indicative messages (boot with drm.debug=14, reproduce the issue, and look in the journal for messages from the kernel graphics driver, basically).
How do I get to edit kernel command line in f22 live usb?
Hit 'e' or 'tab' at the boot menu.
Adam Williamson wrote:
On Thu, 2015-05-07 at 14:54 -0400, Neal Becker wrote:
Could have been me :)
- It does not happen with f21
- Where should I report this (other than here?)
Kernel or freedesktop bugzilla against the appropriate graphics driver, probably, but it'd be good to run through the graphics debugging process and see if you see any indicative messages (boot with drm.debug=14, reproduce the issue, and look in the journal for messages from the kernel graphics driver, basically).
OK, submitted: https://bugzilla.redhat.com/show_bug.cgi?id=1219826
-
Adam Williamson -
Dan Mossor -
Neal Becker