On Thu, Aug 09, 2012 at 09:05:26PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Jul 31, 2012 at 08:33:04PM +0100, Matthew Garrett wrote:
> > On Tue, Jul 31, 2012 at 10:27:54PM +0300, Pasi Kärkkäinen wrote:
> >
> > > .. and it's stuck there. I need to press Reset button to continue.
> > > It did read th
On Tue, Jul 31, 2012 at 08:33:04PM +0100, Matthew Garrett wrote:
> On Tue, Jul 31, 2012 at 10:27:54PM +0300, Pasi Kärkkäinen wrote:
>
> > .. and it's stuck there. I need to press Reset button to continue.
> > It did read the CD for a while until it got frozen.
>
> Yeah, that's definitely a bug th
On Thu, Aug 02, 2012 at 08:09:05PM +0100, Matthew Garrett wrote:
> On Mon, Jul 30, 2012 at 05:54:46PM +0300, Pasi Kärkkäinen wrote:
>
> > "nomodeset" doesn't help or change anything unfortunately..
>
> Try with noapic?
>
That didn't help either :(
-- Pasi
--
devel mailing list
devel@lists.fe
On Mon, Jul 30, 2012 at 05:54:46PM +0300, Pasi Kärkkäinen wrote:
> "nomodeset" doesn't help or change anything unfortunately..
Try with noapic?
--
Matthew Garrett | mj...@srcf.ucam.org
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, Jul 31, 2012 at 10:27:54PM +0300, Pasi Kärkkäinen wrote:
> .. and it's stuck there. I need to press Reset button to continue.
> It did read the CD for a while until it got frozen.
Yeah, that's definitely a bug then. We'll see if we can reproduce it.
--
Matthew Garrett | mj...@srcf.ucam.
On Tue, Jul 31, 2012 at 08:16:29PM +0100, Matthew Garrett wrote:
> On Tue, Jul 31, 2012 at 09:41:48PM +0300, Pasi Kärkkäinen wrote:
> > Secure boot not enabled
> > error: failure reading sector 0x40 from `cd0Ž.
>
> Try changing the firmware from AHCI to IDE mode. We're pretty sure this
> is a bug
On Tue, Jul 31, 2012 at 09:41:48PM +0300, Pasi Kärkkäinen wrote:
> Secure boot not enabled
> error: failure reading sector 0x40 from `cd0Ž.
Try changing the firmware from AHCI to IDE mode. We're pretty sure this
is a bug in Intel's AHCI driver, but we'll try to figure out a
workaround in grub.
On Tue, Jul 31, 2012 at 11:11:07AM -0400, Peter Jones wrote:
> On Mon, 2012-07-30 at 21:23 +0300, Pasi Kärkkäinen wrote:
> > On Thu, Jul 26, 2012 at 11:02:07PM +0300, Pasi Kärkkäinen wrote:
> > >
> > > > >I'm pretty sure this is a Intel firmware bug, but it'd be nice to be
> > > > >able to
> > >
On Mon, 2012-07-30 at 21:23 +0300, Pasi Kärkkäinen wrote:
> On Thu, Jul 26, 2012 at 11:02:07PM +0300, Pasi Kärkkäinen wrote:
> >
> > > >I'm pretty sure this is a Intel firmware bug, but it'd be nice to be
> > > >able to
> > > >confirm that somehow..
> > >
> > > Well, either the bootloader or the
On Thu, Jul 26, 2012 at 11:02:07PM +0300, Pasi Kärkkäinen wrote:
>
> > >I'm pretty sure this is a Intel firmware bug, but it'd be nice to be able
> > >to
> > >confirm that somehow..
> >
> > Well, either the bootloader or the kernel (or something after that) is not
> > succeeding If Windows works
On Mon, Jul 30, 2012 at 09:59:11AM -0600, Chris Murphy wrote:
>
> On Jul 30, 2012, at 9:36 AM, Pasi Kärkkäinen wrote:
>
> > Multiple people have confirmed UEFI boot is broken on Intel 7-series
> > motherboards,
> > so I believe this is Intel BIOS/firmware bug.
>
> Does it UEFI boot a Windows 7
On Jul 30, 2012, at 9:36 AM, Pasi Kärkkäinen wrote:
> Multiple people have confirmed UEFI boot is broken on Intel 7-series
> motherboards,
> so I believe this is Intel BIOS/firmware bug.
Does it UEFI boot a Windows 7 X86_64 install disk?
Does Intel think it's broken?
Chris Murphy
--
devel
On Mon, Jul 30, 2012 at 11:34:12AM -0400, Gerry Reno wrote:
> On 07/30/2012 11:28 AM, Pasi Kärkkäinen wrote:
> > On Mon, Jul 30, 2012 at 11:21:54AM -0400, Gerry Reno wrote:
> >> On 07/30/2012 10:58 AM, Pasi Kärkkäinen wrote:
> >>> On Thu, Jul 26, 2012 at 05:35:20PM -0400, Gerry Reno wrote:
> O
On 07/30/2012 11:28 AM, Pasi Kärkkäinen wrote:
> On Mon, Jul 30, 2012 at 11:21:54AM -0400, Gerry Reno wrote:
>> On 07/30/2012 10:58 AM, Pasi Kärkkäinen wrote:
>>> On Thu, Jul 26, 2012 at 05:35:20PM -0400, Gerry Reno wrote:
On 07/26/2012 05:12 PM, Matthew Garrett wrote:
> On Thu, Jul 26, 20
On Mon, Jul 30, 2012 at 11:21:54AM -0400, Gerry Reno wrote:
> On 07/30/2012 10:58 AM, Pasi Kärkkäinen wrote:
> > On Thu, Jul 26, 2012 at 05:35:20PM -0400, Gerry Reno wrote:
> >> On 07/26/2012 05:12 PM, Matthew Garrett wrote:
> >>> On Thu, Jul 26, 2012 at 08:59:20PM +0300, Pasi Kärkkäinen wrote:
> >
On 07/30/2012 10:58 AM, Pasi Kärkkäinen wrote:
> On Thu, Jul 26, 2012 at 05:35:20PM -0400, Gerry Reno wrote:
>> On 07/26/2012 05:12 PM, Matthew Garrett wrote:
>>> On Thu, Jul 26, 2012 at 08:59:20PM +0300, Pasi Kärkkäinen wrote:
>>>
When booting Fedora 17 x64 there's the GRUB bootloader with gr
On Thu, Jul 26, 2012 at 05:35:20PM -0400, Gerry Reno wrote:
> On 07/26/2012 05:12 PM, Matthew Garrett wrote:
> > On Thu, Jul 26, 2012 at 08:59:20PM +0300, Pasi Kärkkäinen wrote:
> >
> >> When booting Fedora 17 x64 there's the GRUB bootloader with graphical
> >> background image,
> >> I let it boo
On Thu, Jul 26, 2012 at 10:12:19PM +0100, Matthew Garrett wrote:
> On Thu, Jul 26, 2012 at 08:59:20PM +0300, Pasi Kärkkäinen wrote:
>
> > When booting Fedora 17 x64 there's the GRUB bootloader with graphical
> > background image,
> > I let it boot the default entry "Fedora 17", I see it the allo
On 07/26/2012 05:12 PM, Matthew Garrett wrote:
> On Thu, Jul 26, 2012 at 08:59:20PM +0300, Pasi Kärkkäinen wrote:
>
>> When booting Fedora 17 x64 there's the GRUB bootloader with graphical
>> background image,
>> I let it boot the default entry "Fedora 17", I see it the allocating memory
>> page
On Thu, Jul 26, 2012 at 08:59:20PM +0300, Pasi Kärkkäinen wrote:
> When booting Fedora 17 x64 there's the GRUB bootloader with graphical
> background image,
> I let it boot the default entry "Fedora 17", I see it the allocating memory
> pages, loading VMLINUZ etc,
> and then the display mode /
On Thu, Jul 26, 2012 at 04:44:03PM -0400, Gerry Reno wrote:
> On 07/26/2012 04:31 PM, Pasi Kärkkäinen wrote:
> > On Thu, Jul 26, 2012 at 02:44:24PM -0400, Gerry Reno wrote:
> >> There are missing Ivy Bridge definitions in the intel_chipset.h file in
> >> libdrm which causes machines with Ivy Bridg
On 07/26/2012 04:31 PM, Pasi Kärkkäinen wrote:
> On Thu, Jul 26, 2012 at 02:44:24PM -0400, Gerry Reno wrote:
>> There are missing Ivy Bridge definitions in the intel_chipset.h file in
>> libdrm which causes machines with Ivy Bridge
>> CPU's w/embedded iGPU to fail when starting X.
>>
>> As I said
On Thu, Jul 26, 2012 at 02:44:24PM -0400, Gerry Reno wrote:
> There are missing Ivy Bridge definitions in the intel_chipset.h file in
> libdrm which causes machines with Ivy Bridge
> CPU's w/embedded iGPU to fail when starting X.
>
> As I said in the bug, installing libdrm 2.4.37 from bodhi fixed
On Thu, Jul 26, 2012 at 02:36:39PM -0400, Przemek Klosowski wrote:
> On 07/26/2012 06:32 AM, Pasi Kärkkäinen wrote:
>
> >I have a new Intel DQ77MK motherboard, based on the Intel Q77 chipset.
> >CPU is Intel Ivy Bridge i7-3770.
> >I'm running the latest BIOS version (0048), and UEFI boot is enable
On Thu, Jul 26, 2012 at 03:52:25PM -0400, Peter Jones wrote:
> On 07/26/2012 01:59 PM, Pasi Kärkkäinen wrote:
> >"noefi" kernel cmdline option didn't help unfortunately.
> >
> >When booting Fedora 17 x64 there's the GRUB bootloader with graphical
> >background image, I let it boot the default entry
On 07/26/2012 01:59 PM, Pasi Kärkkäinen wrote:
"noefi" kernel cmdline option didn't help unfortunately.
When booting Fedora 17 x64 there's the GRUB bootloader with graphical
background image, I let it boot the default entry "Fedora 17", I see it the
allocating memory pages, loading VMLINUZ etc,
On 07/26/2012 02:36 PM, Przemek Klosowski wrote:
On 07/26/2012 06:32 AM, Pasi Kärkkäinen wrote:
I have a new Intel DQ77MK motherboard, based on the Intel Q77 chipset.
CPU is Intel Ivy Bridge i7-3770.
I'm running the latest BIOS version (0048), and UEFI boot is enabled in the
BIOS.
I take it
There are missing Ivy Bridge definitions in the intel_chipset.h file in libdrm
which causes machines with Ivy Bridge
CPU's w/embedded iGPU to fail when starting X.
As I said in the bug, installing libdrm 2.4.37 from bodhi fixed the issue on my
F17 machine.
On 07/26/2012 02:05 PM, Gerry Reno w
On 07/26/2012 06:32 AM, Pasi Kärkkäinen wrote:
I have a new Intel DQ77MK motherboard, based on the Intel Q77 chipset.
CPU is Intel Ivy Bridge i7-3770.
I'm running the latest BIOS version (0048), and UEFI boot is enabled in the
BIOS.
I take it that this one doesn't have the secure boot yet? Th
I encountered a similar problem when using a new Intel Xeon (Ivy Bridge) CPU.
The issue occurred with Ivy Bridge w/iGPU onboard.
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=840180
.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Thu, Jul 26, 2012 at 01:17:58PM -0400, Peter Jones wrote:
> On 07/26/2012 06:32 AM, Pasi Kärkkäinen wrote:
> >UEFI boot fails with all of the listed operating systems. Symptoms:
> >
> >- I get the Fedora/RHEL EFI boot menu, and I let it boot with the default
> >options.
> >- I get text on the sc
On 07/26/2012 06:32 AM, Pasi Kärkkäinen wrote:
UEFI boot fails with all of the listed operating systems. Symptoms:
- I get the Fedora/RHEL EFI boot menu, and I let it boot with the default
options.
- I get text on the screen about allocating memory pages for Linux-EFI,
loading VMLINUZ, etc.
- Th
32 matches
Mail list logo
