On 04.04.2015 14:01, Patrick O'Callaghan wrote:
...
>
> Mine all use UUID. These are the two entries (not working, working):
>
> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
> fedora --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnul
> inux-3.13.5-202.fc2
On 04/04/2015 04:02 PM, Patrick O'Callaghan wrote:
On Sat, 2015-04-04 at 12:45 -0700, Joe Zeff wrote:
On 04/04/2015 06:19 AM, Paul Cartwright wrote:
then grub2-install /dev/sda ( assuming sda is where you have grub installed)
Unless you think there's something wrong with grub, that shouldn't
On Sat, 2015-04-04 at 12:45 -0700, Joe Zeff wrote:
> On 04/04/2015 06:19 AM, Paul Cartwright wrote:
> > then grub2-install /dev/sda ( assuming sda is where you have grub installed)
>
> Unless you think there's something wrong with grub, that shouldn't be
> needed.
I also thought that grub2 wasn'
On 04/04/2015 06:19 AM, Paul Cartwright wrote:
then grub2-install /dev/sda ( assuming sda is where you have grub installed)
Unless you think there's something wrong with grub, that shouldn't be
needed.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription o
On Sat, 4 Apr 2015 13:57:39 -0400 Tom Horsley wrote:
> On Sat, 04 Apr 2015 18:50:39 +0100
> Patrick O'Callaghan wrote:
>
> > No idea. Obviously not something I expected. I would assume a problem
> > with the yum install script but no-one else seems to have mentioned it.
>
> I just updated my f2
On Sat, 2015-04-04 at 13:57 -0400, Tom Horsley wrote:
> On Sat, 04 Apr 2015 18:50:39 +0100
> Patrick O'Callaghan wrote:
>
> > No idea. Obviously not something I expected. I would assume a problem
> > with the yum install script but no-one else seems to have mentioned it.
>
> I just updated my f21
On Sat, 2015-04-04 at 09:19 -0400, Paul Cartwright wrote:
> On 04/04/2015 08:28 AM, Patrick O'Callaghan wrote:
> > On Sat, 2015-04-04 at 13:01 +0100, Patrick O'Callaghan wrote:
> >> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
> >> fedora --class gnu-linux --class gnu --class
On Sat, 04 Apr 2015 18:50:39 +0100
Patrick O'Callaghan wrote:
> No idea. Obviously not something I expected. I would assume a problem
> with the yum install script but no-one else seems to have mentioned it.
I just updated my f21 partition and got this new kernel. It built
the initrd and boots ju
On Sat, 2015-04-04 at 10:33 -0600, jd1008 wrote:
>
> On 04/04/2015 06:01 AM, Patrick O'Callaghan wrote:
> > menuentry 'Fedora (3.19.3-200.fc21.x86_64)
> Why is initrd missing for 3.19.3-200 ??
No idea. Obviously not something I expected. I would assume a problem
with the yum install script but no
On 04/04/2015 06:01 AM, Patrick O'Callaghan wrote:
menuentry 'Fedora (3.19.3-200.fc21.x86_64)
Why is initrd missing for 3.19.3-200 ??
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora
On 04/04/2015 08:28 AM, Patrick O'Callaghan wrote:
> On Sat, 2015-04-04 at 13:01 +0100, Patrick O'Callaghan wrote:
>> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
>> fedora --class gnu-linux --class gnu --class os $menuentry_id_option
>> 'gnul
>> inux-3.13.5-202.fc20.x86_64-a
On Sat, 2015-04-04 at 13:01 +0100, Patrick O'Callaghan wrote:
> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
> fedora --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnul
> inux-3.13.5-202.fc20.x86_64-advanced-6a9a800c-309b-4b69-b269-884ad495e7b9' {
>
On Sat, 2015-04-04 at 07:52 -0400, Paul Cartwright wrote:
> On 04/04/2015 07:45 AM, Patrick O'Callaghan wrote:
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
> > (0,0)
> >
> > Maybe something wrong in grub.conf? The previous kernel boots fine.
> >
> > poc
> my entrie
On 04/04/2015 07:45 AM, Patrick O'Callaghan wrote:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
> (0,0)
>
> Maybe something wrong in grub.conf? The previous kernel boots fine.
>
> poc
my entries show UUID, not block..
linux16 /boot/vmlinuz-3.17.4-301.fc21.x86
On 04/04/2015 07:45 AM, Patrick O'Callaghan wrote:
> As I suspected, the nVidia thing does seem to be a red herring. I
> rebooted and copied the last line of the stack trace:
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
> (0,0)
>
> Maybe something wrong in grub.con
On Sat, 2015-04-04 at 12:27 +0100, Patrick O'Callaghan wrote:
> On Fri, 2015-04-03 at 15:00 -0700, Joe Zeff wrote:
> > On 04/03/2015 02:55 PM, jd1008 wrote:
> > > What if you downloaded the source code of the kmod,
> > > built it on your machine (be sure you have the kernel
> > > source code instal
On Fri, 2015-04-03 at 15:00 -0700, Joe Zeff wrote:
> On 04/03/2015 02:55 PM, jd1008 wrote:
> > What if you downloaded the source code of the kmod,
> > built it on your machine (be sure you have the kernel
> > source code installed in /usr/src/kernel
> >
> > Perhaps that might fix your prblem???
>
On 04/03/2015 06:18 PM, Joe Zeff wrote:
> On 04/03/2015 03:07 PM, jd1008 wrote:
>> Of course. If you proceed on the assumption that akmod-nvidia
>> was indeed compiled for the kernel at hand.
>
> It's been my experience that akmod-nvidia doesn't need to be updated for
> every new kernel; I've only
On Fri, 03 Apr 2015 15:13:51 -0700
Joe Zeff wrote:
> (If you ever
> want to try, I think I can find out how to do it.)
I tried finding out how to do it, but it was far less
work to reinstall everything from scratch than to
dig up the secret handshake to make it rebuild :-).
--
users mailing lis
On 04/03/2015 03:07 PM, jd1008 wrote:
Of course. If you proceed on the assumption that akmod-nvidia
was indeed compiled for the kernel at hand.
It's been my experience that akmod-nvidia doesn't need to be updated for
every new kernel; I've only received a new version when nVidia releases
a ne
On 04/03/2015 03:06 PM, Tom Horsley wrote:
I once had an akmod screw up somehow, and was never able
to figure out how to convince it to rebuild something it
was convinced it already built.
Did you try removing kmod-nvidia and rebooting? I think there's a way
to run the service from the comman
On 04/03/2015 04:00 PM, Joe Zeff wrote:
On 04/03/2015 02:55 PM, jd1008 wrote:
What if you downloaded the source code of the kmod,
built it on your machine (be sure you have the kernel
source code installed in /usr/src/kernel
Perhaps that might fix your prblem???
Isn't that what akmod-nvidia
I once had an akmod screw up somehow, and was never able
to figure out how to convince it to rebuild something it
was convinced it already built.
I eventually solved the problem by booting in multi-user
mode, logging in to the console as root, uninstalling
everything named *nvidia*, then reinstall
On 04/03/2015 02:55 PM, jd1008 wrote:
What if you downloaded the source code of the kmod,
built it on your machine (be sure you have the kernel
source code installed in /usr/src/kernel
Perhaps that might fix your prblem???
Isn't that what akmod-nvidia does? Remember, KISS.
--
users mailing li
On 04/03/2015 04:49 AM, Patrick O'Callaghan wrote:
kernel-3.19.3-200.fc21.x86_64
kmod-nvidia-3.19.3-200.fc21.x86_64-346.47-2.fc21.4.x86_64
The failure happens immediately after selecting the kernel from the boot
menu. A stack trace appears which I'll post if someone tells me how to
capture it.
On Fri, 2015-04-03 at 06:57 -0500, Richard Shaw wrote:
> On Fri, Apr 3, 2015 at 5:49 AM, Patrick O'Callaghan
> wrote:
>
> >
> > kernel-3.19.3-200.fc21.x86_64
> > kmod-nvidia-3.19.3-200.fc21.x86_64-346.47-2.fc21.4.x86_64
> >
> > The failure happens immediately after selecting the kernel from the b
On Fri, Apr 3, 2015 at 5:49 AM, Patrick O'Callaghan
wrote:
>
> kernel-3.19.3-200.fc21.x86_64
> kmod-nvidia-3.19.3-200.fc21.x86_64-346.47-2.fc21.4.x86_64
>
> The failure happens immediately after selecting the kernel from the boot
> menu. A stack trace appears which I'll post if someone tells me h
kernel-3.19.3-200.fc21.x86_64
kmod-nvidia-3.19.3-200.fc21.x86_64-346.47-2.fc21.4.x86_64
The failure happens immediately after selecting the kernel from the boot
menu. A stack trace appears which I'll post if someone tells me how to
capture it.
poc
--
users mailing list
users@lists.fedoraproje
28 matches
Mail list logo