Re: Issue with GOG native games and opengl?

[Ed Greshko]

On 03/17/15 08:38, Bruno Wolff III wrote:
> The game works in current f21, but not rawhide. I suspect this is due to mesa 
> or nouveau versions rather than a bug. 

Are you saying you're trying to use the game under rawhide and it doesn't 
workbut that it does work in the released and "supported" F21 version?

If that is the case, wouldn't the answer be to run it on F21?  And, maybe, 
bring up the issue on the "test" list?

-- 
If you can't laugh at yourself, others will gladly oblige.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Issue with GOG native games and opengl?

[Bruno Wolff III]

When running Icewind Dale's start up script I get the following:
Running Icewind Dale Enhanced Edition
libGL error: unable to load driver: nouveau_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: nouveau
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
 Major opcode of failed request:  154 (GLX)
 Minor opcode of failed request:  3 (X_GLXCreateContext)
 Value in failed request:  0x0
 Serial number of failed request:  84
 Current serial number in output stream:  85

They only officially support Ubuntu LTS, so I can't get official support
from GOG.

Is there a way to work around the above? (Other than running the Windows
version under Wine.) The game works in current f21, but not rawhide. I 
suspect this is due to mesa or nouveau versions rather than a bug.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Joe Zeff]

On 03/16/2015 04:45 PM, Ed Greshko wrote:

On 03/17/15 06:25, Joe Zeff wrote:

My laptop reports several kerneloops every time it boots.  AFAIK, there's 
nothing installed that taints the kernel, but 99% of the time abrt tells me 
that the kernel is tainted and that I can't report it. Suggestions?  (If you 
need, I can get you a copy of the specifics.)


Does "cat /proc/sys/kernel/tainted" return a value?
Does "journalctl -r -b | grep -i taint"  list a mod?



I don't know, because I'm at my desktop, not my laptop and don't have 
time ATM to fire it up and find out.  When I do, I'll let you know.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Ed Greshko]

On 03/17/15 06:25, Joe Zeff wrote:
> My laptop reports several kerneloops every time it boots.  AFAIK, there's 
> nothing installed that taints the kernel, but 99% of the time abrt tells me 
> that the kernel is tainted and that I can't report it. Suggestions?  (If you 
> need, I can get you a copy of the specifics.) 

Does "cat /proc/sys/kernel/tainted" return a value?
Does "journalctl -r -b | grep -i taint"  list a mod?

-- 
If you can't laugh at yourself, others will gladly oblige.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Ed Greshko]

On 03/17/15 07:43, Chris Murphy wrote:
> Crude but this should work
> # journalctl -b -l -o short-monotonic | grep -i "tainted"

That won't work since the string in the journal is "taints kernel"

-- 
If you can't laugh at yourself, others will gladly oblige.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Chris Murphy]

On Mon, Mar 16, 2015 at 4:25 PM, Joe Zeff  wrote:
> On 03/16/2015 02:29 PM, Matthew Miller wrote:
>>
>> Reboot into a stock kernel without the modules? Ask other people for
>> help in replicating? Contact the vendor of the binary module and ask
>> for their help?
>
>
> My laptop reports several kerneloops every time it boots.  AFAIK, there's
> nothing installed that taints the kernel, but 99% of the time abrt tells me
> that the kernel is tainted and that I can't report it. Suggestions?  (If you
> need, I can get you a copy of the specifics.)

Crude but this should work
# journalctl -b -l -o short-monotonic | grep -i "tainted"

That should get you more than one line. What's probably happening is
there's an early "Not Tainted" line which is the one to file as a bug.
And then any oops that happens after that is always considered tainted
because of the first one. If the first oops (for a boot) is tainted,
then there's a letter code that indicates why, but Fedora kernels
don't ever do this on their own, but if they did that itself would be
a bug.

-- 
Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Joe Zeff]

On 03/16/2015 02:29 PM, Matthew Miller wrote:

Reboot into a stock kernel without the modules? Ask other people for
help in replicating? Contact the vendor of the binary module and ask
for their help?


My laptop reports several kerneloops every time it boots.  AFAIK, 
there's nothing installed that taints the kernel, but 99% of the time 
abrt tells me that the kernel is tainted and that I can't report it. 
Suggestions?  (If you need, I can get you a copy of the specifics.)

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Matthew Miller]

On Mon, Mar 16, 2015 at 01:59:17PM -0700, Joe Zeff wrote:
> >That's a lot of obligation to put onto someone you are not paying. The
> >kernel maintainers have a huge and constantly growing pile of work. I
> >don't think it's unreasonable to ask for bug submitters to recreate the
> >crash on a stock system.
> What do you do, then, if you're a home user with one computer?

Reboot into a stock kernel without the modules? Ask other people for
help in replicating? Contact the vendor of the binary module and ask
for their help?

-- 
Matthew Miller

Fedora Project Leader
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Chris Murphy]

On Mon, Mar 16, 2015 at 2:58 PM, Joe Zeff  wrote:
> On 03/16/2015 12:37 PM, Chris Murphy wrote:
>>
>>
>> Just because the crash doesn't occur in an out of tree module, doesn't
>> mean that the out of tree module isn't instigating the problem though.
>
>
> Agreed.  That's why I suggested trying to duplicate the crash with an
> untainted kernel.

Burden is on the user to do this. The distribution provides an
untainted kernel. The user chose to use an out of tree module that
taints it. It can't be claimed to be a kernel bug when an out of tree
module it used, short of the often tedious analysis of exactly how the
out of tree kernel affects kernel behavior.

-- 
Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Chris Murphy]

On Mon, Mar 16, 2015 at 3:19 PM, Chris Murphy  wrote:

> out of tree kernel affects kernel behavior.

tree kernel ^module



-- 
Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Joe Zeff]

On 03/16/2015 01:46 PM, Matthew Miller wrote:

That's a lot of obligation to put onto someone you are not paying. The
kernel maintainers have a huge and constantly growing pile of work. I
don't think it's unreasonable to ask for bug submitters to recreate the
crash on a stock system.


What do you do, then, if you're a home user with one computer?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Joe Zeff]

On 03/16/2015 12:37 PM, Chris Murphy wrote:


Just because the crash doesn't occur in an out of tree module, doesn't
mean that the out of tree module isn't instigating the problem though.


Agreed.  That's why I suggested trying to duplicate the crash with an 
untainted kernel.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Matthew Miller]

On Mon, Mar 16, 2015 at 09:58:54AM -0700, Joe Zeff wrote:
> >Since none of the crashes occur in the modules
> >inserted via akmods, why is the fedora abrt not
> >allowing thes ending of such reports?
> I've been thinking the same thing.  If nothing else, whoever is
> assigned to the bug should try to recreate the crash on a stock
> machine with no kmods and work on it if they succeed.

That's a lot of obligation to put onto someone you are not paying. The
kernel maintainers have a huge and constantly growing pile of work. I
don't think it's unreasonable to ask for bug submitters to recreate the
crash on a stock system.


-- 
Matthew Miller

Fedora Project Leader
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Matthew Miller]

On Mon, Mar 16, 2015 at 10:44:16AM -0600, jd1008 wrote:
> Since none of the crashes occur in the modules
> inserted via akmods, why is the fedora abrt not
> allowing thes ending of such reports?

Kernel modules can pretty much do whatever they like once they're
loaded; how do you demonstrate that the crash in some other area is not
actually caused by the binary module you loaded?

-- 
Matthew Miller

Fedora Project Leader
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Chris Murphy]

On Mon, Mar 16, 2015 at 10:44 AM, jd1008  wrote:

> Since none of the crashes occur in the modules
> inserted via akmods, why is the fedora abrt not
> allowing thes ending of such reports?

I think this question needs to go to the Fedora devel@ list, or maybe
also kernel@ as a cross-post (explicitly mentioned from the outset
it's a crosspost).

Just because the crash doesn't occur in an out of tree module, doesn't
mean that the out of tree module isn't instigating the problem though.


Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Roger Heflin]

If it is a obvious bug, yes those are easy to find, the obvious bugs
also have lots of crashes tainted or untainted.   The ones that always
get everyone in trouble are the ones were something modifies something
unrelated to it and causes someone else's code to crash in a bizarre
way.

On Mon, Mar 16, 2015 at 12:56 PM, jd1008  wrote:
>
>
> On 03/16/2015 11:29 AM, Roger Heflin wrote:
>>
>> Recreating a rare crash even when you know the exact conditions that
>> caused the crash is very very difficult.I have been involved in
>> not so rare crashes (we had some machines of the exact same hw type
>> that all crashed randomly about 1x per week). And duplicating that
>> crash tied up a test machine for >30 days before finally duplicated
>> the crash, as we were not able to exactly duplicate the load condition
>> that caused the crash.Typically the crashes are dealt with is by
>> noticing a pattern and using that pattern to try to determine the
>> nature of the failure and how common it is.   With a single crash you
>> have no idea if it as a hardware fault or not.
>>
>> Given the number of crashes we are probably talking about and the
>> number of different kernel versions you are talking about one would
>> need to have an almost infinite hardware budget to even possibly run
>> the test.
>>
>> On Mon, Mar 16, 2015 at 11:58 AM, Joe Zeff  wrote:
>>>
>>> On 03/16/2015 09:44 AM, jd1008 wrote:

 Since none of the crashes occur in the modules
 inserted via akmods, why is the fedora abrt not
 allowing thes ending of such reports?
>>>
>>>
>>> I've been thinking the same thing.  If nothing else, whoever is assigned
>>> to
>>> the bug should try to recreate the crash on a stock machine with no kmods
>>> and work on it if they succeed.
>>>
>>> --
>>> users mailing list
>>> users@lists.fedoraproject.org
>>> To unsubscribe or change subscription options:
>>> https://admin.fedoraproject.org/mailman/listinfo/users
>>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>>> Have a question? Ask away: http://ask.fedoraproject.org
>
> I do not mean to discredit you Roger,
> but I did kernel development and debugging for almost
> 40 years, starting with the AT&T version 3 Unix.
> It is not as you say.
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[jd1008]

On 03/16/2015 11:29 AM, Roger Heflin wrote:

Recreating a rare crash even when you know the exact conditions that
caused the crash is very very difficult.I have been involved in
not so rare crashes (we had some machines of the exact same hw type
that all crashed randomly about 1x per week). And duplicating that
crash tied up a test machine for >30 days before finally duplicated
the crash, as we were not able to exactly duplicate the load condition
that caused the crash.Typically the crashes are dealt with is by
noticing a pattern and using that pattern to try to determine the
nature of the failure and how common it is.   With a single crash you
have no idea if it as a hardware fault or not.

Given the number of crashes we are probably talking about and the
number of different kernel versions you are talking about one would
need to have an almost infinite hardware budget to even possibly run
the test.

On Mon, Mar 16, 2015 at 11:58 AM, Joe Zeff  wrote:

On 03/16/2015 09:44 AM, jd1008 wrote:

Since none of the crashes occur in the modules
inserted via akmods, why is the fedora abrt not
allowing thes ending of such reports?


I've been thinking the same thing.  If nothing else, whoever is assigned to
the bug should try to recreate the crash on a stock machine with no kmods
and work on it if they succeed.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

I do not mean to discredit you Roger,
but I did kernel development and debugging for almost
40 years, starting with the AT&T version 3 Unix.
It is not as you say.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[jd1008]

On 03/16/2015 10:58 AM, Joe Zeff wrote:

On 03/16/2015 09:44 AM, jd1008 wrote:

Since none of the crashes occur in the modules
inserted via akmods, why is the fedora abrt not
allowing thes ending of such reports?


I've been thinking the same thing.  If nothing else, whoever is 
assigned to the bug should try to recreate the crash on a stock 
machine with no kmods and work on it if they succeed.

Thank you Joe!
We need to collect some user steam behind this need.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Roger Heflin]

Recreating a rare crash even when you know the exact conditions that
caused the crash is very very difficult.I have been involved in
not so rare crashes (we had some machines of the exact same hw type
that all crashed randomly about 1x per week). And duplicating that
crash tied up a test machine for >30 days before finally duplicated
the crash, as we were not able to exactly duplicate the load condition
that caused the crash.Typically the crashes are dealt with is by
noticing a pattern and using that pattern to try to determine the
nature of the failure and how common it is.   With a single crash you
have no idea if it as a hardware fault or not.

Given the number of crashes we are probably talking about and the
number of different kernel versions you are talking about one would
need to have an almost infinite hardware budget to even possibly run
the test.

On Mon, Mar 16, 2015 at 11:58 AM, Joe Zeff  wrote:
> On 03/16/2015 09:44 AM, jd1008 wrote:
>>
>> Since none of the crashes occur in the modules
>> inserted via akmods, why is the fedora abrt not
>> allowing thes ending of such reports?
>
>
> I've been thinking the same thing.  If nothing else, whoever is assigned to
> the bug should try to recreate the crash on a stock machine with no kmods
> and work on it if they succeed.
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Crashes of tainted kernels

[Joe Zeff]

On 03/16/2015 09:44 AM, jd1008 wrote:

Since none of the crashes occur in the modules
inserted via akmods, why is the fedora abrt not
allowing thes ending of such reports?


I've been thinking the same thing.  If nothing else, whoever is assigned 
to the bug should try to recreate the crash on a stock machine with no 
kmods and work on it if they succeed.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kernel-core-3.18.9-200.fc21.x86_64 fails to boot

[Joe Zeff]

On 03/16/2015 09:34 AM, Patrick O'Callaghan wrote:

I already have akmod installed, but it didn't seem to do anything in
this case.


Interesting.  Have you checked to see if the appropriate kmod exists and 
has the proper date stamp?

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Crashes of tainted kernels

[jd1008]

Many of us need akmods for our hardware.

But when the kernel crashes or ooops'es,
we are unable to send the crash report.

Since none of the crashes occur in the modules
inserted via akmods, why is the fedora abrt not
allowing thes ending of such reports?

At least provide a way for us to send them to
the place we got them from, namely rpmfusion
in this case, or other repos in other cases.

All abrt has to do is ask for the user's login
id and password and have it submit the report there.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kernel-core-3.18.9-200.fc21.x86_64 fails to boot

[Patrick O'Callaghan]

On Mon, 2015-03-16 at 09:19 -0700, Joe Zeff wrote:
> On 03/16/2015 01:26 AM, Frédéric Bron wrote:
> > for me, I always have to run 'yum update' twice. The first time, I get
> > the new kernel from fedora, then I need to reboot and do 'yum update'
> > again for the nvidia driver.
> 
> That's odd.  I use yumex, which is just a GUI front-end for yum, and I 
> normally get both the kernel and the kmod together.  And, if there's a 
> delay on the kmod, I also have akmod as a backup.  That way, if I don't 
> notice the lack of kmod I can still boot safely into the new kernel.

I already have akmod installed, but it didn't seem to do anything in
this case.

poc

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kernel-core-3.18.9-200.fc21.x86_64 fails to boot

[Joe Zeff]

On 03/16/2015 01:26 AM, Frédéric Bron wrote:

for me, I always have to run 'yum update' twice. The first time, I get
the new kernel from fedora, then I need to reboot and do 'yum update'
again for the nvidia driver.


That's odd.  I use yumex, which is just a GUI front-end for yum, and I 
normally get both the kernel and the kmod together.  And, if there's a 
delay on the kmod, I also have akmod as a backup.  That way, if I don't 
notice the lack of kmod I can still boot safely into the new kernel.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Yum suggestion

[Matthew Miller]

On Fri, Mar 13, 2015 at 11:54:47AM +, Timothy Murphy wrote:
> Yum tells me the repos where it fails to find a package,
> but not those where it succeeds.
> It would be nice to know who around the world
> I should be grateful to.

Hi Timothy! You can see the full mirror list at
. And, also, see the
Fedora Sponsors page at  (the list is
more than just Red Hat!)

Giving credit to the mirrors involved in actual use isn't a terrible
idea — perhaps submit it as an RFE for DNF, the successor to yum?

-- 
Matthew Miller

Fedora Project Leader
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: How to increase maximum user cpu usage allowed on a multi core system?

[Heinz Diehl]

On 09.03.2015, Martin Cigorraga wrote: 

> Just a minor clarification: when compiling, the -j flag should point to a
> unit above your available cores in order to fully utilize all of them.

Curious what would happen, I remembered this mail when compiling a new kernel
today. A "nice -n 19 make -j" opened *hundreds* of cc incarnations, pushed the
load to over 800 and seriously blocked the machine (an 8-core Xeon with 16 GB
of RAM) within *seconds*!



-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kernel-core-3.18.9-200.fc21.x86_64 fails to boot

[Tom Horsley]

On Mon, 16 Mar 2015 12:25:39 +
Patrick O'Callaghan wrote:

> This is a meta-package without payload which sole purpose is to 
> require the
> nvidia kernel module(s) for the newest kernel.
> to make sure you get it together with a new kernel.

You need to read the detailed instructions in the rpmfusion
installing nvidia driver page. The change that made "kernel"
split into "kernel-core" and other packages has blown the minds
of many many things.

according to http://rpmfusion.org/Howto/nVidia you now need
something absurd like:"kernel-devel-uname-r == $(uname -r)"
added to the yum command.

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kernel-core-3.18.9-200.fc21.x86_64 fails to boot

[Patrick O'Callaghan]

On Mon, 2015-03-16 at 09:26 +0100, Frédéric Bron wrote:
> > Installed the latest stable kernel using yum. On booting, a few seconds
> > after the splash screen, I get a solitary blinking cursor.
> > Rebooting with the previous version (3.18.8-201) works fine.
> > Video is an Nvidia GT630 using the kmod-nvidia driver.
> 
> for me, I always have to run 'yum update' twice. The first time, I get
> the new kernel from fedora, then I need to reboot and do 'yum update'
> again for the nvidia driver. Sometimes, the graphical interface does
> not start after the reboot. Can you switch to a terminal window with
> Ctrl+Alt+F#? If so, try to log as root, do yum update and reboot.

Thanks, the normal yum update I do every day sorted it out.

The info for kmod-nvidia says:

This is a meta-package without payload which sole purpose is to require 
the
nvidia kernel module(s) for the newest kernel.
to make sure you get it together with a new kernel.

Either I'm misunderstanding what that comment says, or it isn't doing
what it's supposed to.

poc

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: installing fedora on HEWLETT PACKARD pavilion 500

[Angelo Moreschini]

studying this my problem (which is connected to  the use of the UEFI on HP
computers  in place of the traditional BIOS) I found this link:

http://www.rodsbooks.com/efi-bootloaders/index.html

There is wrote :
"The way EFI computers boot is very different from the way older computers
based on the Basic Input/Output System (BIOS) boot."

*But I didn't yet realized very well what really is this difference *.

Of course I had to disable the "secure boot" (in order to use the CD with
The Fedora installation)..

But, still, I am confused about the boot loader to use (how the Web page
says )...

Perhaps my problem come because I am using the default boot loader (Grub2)
that come with the installation of Fedora and, instead, I should change it
with another more appropriate boot-loader  ???



On Mon, Mar 16, 2015 at 4:07 AM, Angelo Moreschini <
mrangelo.fed...@gmail.com> wrote:

> the output for lsblk is :
>
>
> [liveuser@localhost ~]$ lsblk
> NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
> sda 8:00 931.5G  0 disk
> ├─sda1  8:10  1023M  0 part
> ├─sda2  8:20   360M  0 part
> ├─sda3  8:30   128M  0 part
> ├─sda4  8:40 439.6G  0 part
> ├─sda5  8:50  10.4G  0 part
> ├─sda6  8:60 1M  0 part
> ├─sda7  8:70   500M  0 part /mnt/sysimage/boot
> └─sda8  8:80 479.6G  0 part
>   ├─fedora_localhost-swap 253:30   7.8G  0 lvm  [SWAP]
>   ├─fedora_localhost-home 253:40 421.7G  0 lvm  /mnt/sysimage/home
>   └─fedora_localhost-root 253:5050G  0 lvm  /mnt/sysimage
> sr011:01   1.4G  0 rom  /run/initramfs/live
> loop0   7:0012K  1 loop
> loop1   7:10   1.8M  1 loop
> └─live-osimg-min  253:20 6G  1 dm
> loop2   7:20   1.3G  1 loop
> loop3   7:30 6G  1 loop
> ├─live-rw 253:00 6G  0 dm   /
> ├─live-base   253:10 6G  1 dm
> └─live-osimg-min  253:20 6G  1 dm
> loop4   7:40   512M  0 loop
> └─live-rw 253:00 6G  0 dm   /
> 
> I see the partition I made for Fesora in sda8
>
> smartctl -x /dev/sda8 produce this output :
> 
> [root@localhost ~]# smartctl -x /dev/sda8
> smartctl 6.2 2014-07-16 r3952 [x86_64-linux-3.17.4-301.fc21.x86_64] (local
> build)
> Copyright (C) 2002-13, Bruce Allen, Christian Franke,
> www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family: Seagate Barracuda 7200.14 (AF)
> Device Model: ST1000DM003-1ER162
> Serial Number:Z4Y5HTPQ
> LU WWN Device Id: 5 000c50 07aaff0a2
> Firmware Version: HP51
> User Capacity:1,000,204,886,016 bytes [1.00 TB]
> Sector Sizes: 512 bytes logical, 4096 bytes physical
> Rotation Rate:7200 rpm
> Device is:In smartctl database [for details use: -P show]
> ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
> SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
> Local Time is:Mon Mar 16 04:06:01 2015 EDT
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
> AAM feature is:   Unavailable
> APM level is: 128 (minimum power consumption without standby)
> Rd look-ahead is: Enabled
> Write cache is:   Enabled
> ATA Security is:  Disabled, frozen [SEC2]
> Wt Cache Reorder: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status:  (0x00)Offline data collection activity
> was never started.
> Auto Offline Data Collection: Disabled.
> Self-test execution status:  (   0)The previous self-test routine
> completed
> without error or no self-test has ever
> been run.
> Total time to complete Offline
> data collection: (   80) seconds.
> Offline data collection
> capabilities:  (0x53) SMART execute Offline immediate.
> Auto Offline data collection on/off support.
> Suspend Offline collection upon new
> command.
> No Offline surface scan supported.
> Self-test supported.
> No Conveyance Self-test supported.
> Selective Self-test supported.
> SMART capabilities:(0x0003)Saves SMART data before entering
> power-saving mode.
> Supports SMART auto save timer.
> Error logging capability:(0x01)Error logging supported.
> General Purpose Logging supported.
> Short self-test routine
> recommended p

Re: kernel-core-3.18.9-200.fc21.x86_64 fails to boot

[Frédéric Bron]

> Installed the latest stable kernel using yum. On booting, a few seconds
> after the splash screen, I get a solitary blinking cursor.
> Rebooting with the previous version (3.18.8-201) works fine.
> Video is an Nvidia GT630 using the kmod-nvidia driver.

for me, I always have to run 'yum update' twice. The first time, I get
the new kernel from fedora, then I need to reboot and do 'yum update'
again for the nvidia driver. Sometimes, the graphical interface does
not start after the reboot. Can you switch to a terminal window with
Ctrl+Alt+F#? If so, try to log as root, do yum update and reboot.
Frédéric
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: installing fedora on HEWLETT PACKARD pavilion 500

[Angelo Moreschini]

the output for lsblk is :


[liveuser@localhost ~]$ lsblk
NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda 8:00 931.5G  0 disk
├─sda1  8:10  1023M  0 part
├─sda2  8:20   360M  0 part
├─sda3  8:30   128M  0 part
├─sda4  8:40 439.6G  0 part
├─sda5  8:50  10.4G  0 part
├─sda6  8:60 1M  0 part
├─sda7  8:70   500M  0 part /mnt/sysimage/boot
└─sda8  8:80 479.6G  0 part
  ├─fedora_localhost-swap 253:30   7.8G  0 lvm  [SWAP]
  ├─fedora_localhost-home 253:40 421.7G  0 lvm  /mnt/sysimage/home
  └─fedora_localhost-root 253:5050G  0 lvm  /mnt/sysimage
sr011:01   1.4G  0 rom  /run/initramfs/live
loop0   7:0012K  1 loop
loop1   7:10   1.8M  1 loop
└─live-osimg-min  253:20 6G  1 dm
loop2   7:20   1.3G  1 loop
loop3   7:30 6G  1 loop
├─live-rw 253:00 6G  0 dm   /
├─live-base   253:10 6G  1 dm
└─live-osimg-min  253:20 6G  1 dm
loop4   7:40   512M  0 loop
└─live-rw 253:00 6G  0 dm   /

I see the partition I made for Fesora in sda8

smartctl -x /dev/sda8 produce this output :

[root@localhost ~]# smartctl -x /dev/sda8
smartctl 6.2 2014-07-16 r3952 [x86_64-linux-3.17.4-301.fc21.x86_64] (local
build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST1000DM003-1ER162
Serial Number:Z4Y5HTPQ
LU WWN Device Id: 5 000c50 07aaff0a2
Firmware Version: HP51
User Capacity:1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate:7200 rpm
Device is:In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Mon Mar 16 04:06:01 2015 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is: 128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status:  (   0)The previous self-test routine
completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (   80) seconds.
Offline data collection
capabilities:  (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:(0x0003)Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:(0x01)Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time:  (   2) minutes.
Extended self-test routine
recommended polling time:  ( 104) minutes.
SCT capabilities:(0x103f)SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAGSVALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate POSR-K   115   100   006-84045512
  3 Spin_Up_TimePO---K   098   098   000-0
  4 Start_Stop_Count-O--CK   100   100   020-102
  5 Reallocated_Sector_Ct   PO--CK   100   100   010-0
  7 Seek_Error_Rate POSR-K   063   060   030-1885699
  9 Power_On_Hours  -O--CK   100   100   000-76
 10 Spin_Retry_CountPO--CK   100   100   097-0
 12 Power_Cycle_Count   -O--CK   100   100   020-98
180 Unknown_HDD_Attribute   -O-R-K   1