Unfortunately I've had another GPU lockup this time with kernel 4.9.0
See attached extract from journal
Dec 30 23:36:04 laptop kernel: radeon :02:00.0: GPU lockup (current fence
id 0x002057e9 last fence id 0x002057ea on ring 0)
Dec 30 23:36:05 laptop kernel: BUG: unable to h
On 30/12/2016 19:54, Gordon Messmer wrote:
> On 12/30/2016 02:39 AM, Mayavimmer wrote:
>> The plan is to nondestructively
>> upgrade the old OS to F25 by keeping both for a while, giving the user
>> the option to boot the old OS if they want
>
> I don't understand how "upgrading" the old OS will b
On 30/12/2016 19:46, Gordon Messmer wrote:
> On 12/30/2016 02:19 AM, Mayavimmer wrote:
>> Is it safe?
>
> If your system boots, then probably, yes.
>
Actually, I just found out that might not be the case. Out of five F25
installs I tried on one machine today, the ones without separate /boot
destr
It appears to be something with the docking station the kernel doesn't
like, I remove the laptop from the docking station and the gui starts
right up.
When not in the docking station and I run lspci -vnn it provides the
following
00:02.0 VGA compatible controller [0300]: Intel Corporation 4
I'm running Fedora 24 kernel 4.7.9-200 (x86_64). the system is on a
Lenovo T440P. the machine boots and is accessable from the network but
the system itself never presents a login prompt after starting a blank
gray screen.
Below are some the information that I think is useful, I'm not sure where
On 12/30/2016 02:39 AM, Mayavimmer wrote:
The plan is to nondestructively
upgrade the old OS to F25 by keeping both for a while, giving the user
the option to boot the old OS if they want
I don't understand how "upgrading" the old OS will be "non destructive"
or give the user the option to boo
On 12/30/2016 02:19 AM, Mayavimmer wrote:
Is it safe?
If your system boots, then probably, yes.
If so, why does the Fedora installer propose a separate
/boot in this EFI hardware case with GPT partitioning?
The kernel and initrd need to be in a place that GRUB2 can read them.
Anaconda can
Thanks Chris
I was waiting for kernel 4.9.0 to hit the fedora 25 repo but I took your advice
and downloaded it now from koji and installed it
I am testing it now & so far so good. I will let you know how I get on
___
users mailing list -- users@lists.
On Dec 30, 2016 4:20 AM, "Mayavimmer" wrote:
>
> It seems that on EFI hardware Fedora 25 can be installed without the
> suggested separate /boot partition. I just selected auto partitioning on
> a LVM device, then deleted the given new /boot partition. It seems to
> work ok.
>
The simple answer is
On 12/30/2016 06:55 AM, Patrick O'Callaghan wrote:
> On Thu, 2016-12-29 at 16:04 -0800, Rick Stevens wrote:
>>> I think you're right, though it requires a close reading of the man
>>> page to understand this. Anyway I've enabled it in the audit rules and
>>> so far it seems to work.
>>
>> Huzzah! H
On 29/12/2016 15:46, Chris Murphy wrote:
On Wed, Dec 28, 2016 at 1:55 PM, Ron Leach wrote:
Grub starts fine, the F24 selection boots perfectly
into F24, but selecting Windows just causes the machine to 'hang', showing
a constant cursor in the top left corner of the screen.
Could be this bug
On Thu, 2016-12-29 at 16:04 -0800, Rick Stevens wrote:
> > I think you're right, though it requires a close reading of the man
> > page to understand this. Anyway I've enabled it in the audit rules and
> > so far it seems to work.
>
> Huzzah! Hope that's "the magic bullet" for you.
Unfortunately
I am trying to install F25 on a legacy box that already has a working
Ext4 over LVM over Md raid 1 of 2x2TB disks, and only a single empty non
raid partition on the second disk. The plan is to nondestructively
upgrade the old OS to F25 by keeping both for a while, giving the user
the option to boot
It seems that on EFI hardware Fedora 25 can be installed without the
suggested separate /boot partition. I just selected auto partitioning on
a LVM device, then deleted the given new /boot partition. It seems to
work ok.
Is it safe? If so, why does the Fedora installer propose a separate
/boot in
On 29 December 2016 at 18:34, Javier Perez wrote:
> I remember reading years back about solutions that allowed Kernel upgrade
> without reboot. Ksplice and Kpatch comes to mind. Whatever happened to them?
>
>
The facilities arrived in kernel 4.0 with Red Hat and Suse working
together with kpatch
15 matches
Mail list logo
