Re: SLiM dependency on xterm?

[Ralf Corsepius]

On 12/21/2014 06:51 PM, Rahul Sundaram wrote:

Hi

On Sun, Dec 21, 2014 at 9:46 AM, Ranjan Maitra  wrote:


Sorry, I do not understand the question: SLiM is a simple login
manager. I like it, but I don't quite see why it needs to bring in
the dependency on xterm.


You should probably file a bug report.   It has a dependency on
xorg-x11-apps which appears unnecessary as well
There direct references to xterm in the source code, so the deps 
probably are correct.


Ralf


--
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

Congrats on F21. fedup worked great!

[Tony Camuso]

Updated from F20 to F21 on two systems, one a VM, the other
bare metal. Used nonproduct to accommodate customizations.

Had zero problems.




--
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: Congrats on F21. fedup worked great!

[Timothy Murphy]

Tony Camuso wrote:

> Updated from F20 to F21 on two systems, one a VM, the other
> bare metal. Used nonproduct to accommodate customizations.

I had a moderate experience with Fedup on two Thinkpad laptops.

One (T510) worked perfectly, except that I could not turn off the touchpad,
until told that Fn+F8 did this (permanently, to my surprise).

The second (T61) lost WiFi after Fedup, 
which I have not been able to recover.

I'd be happier if there were some evidence that the Fedup developers
were keeping a note of problems.
Reference to user experience is not one of Fedora's strong points.


-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin


-- 
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: NTP vulnerability

[Patrick O'Callaghan]

On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
> On 12/22/14 02:46, Aaron Gray wrote:
> > There are no ntp or ntpd or systemd-timesyncd packages on F20 !
> 
> The default time sync package is now chrony.
> 
> ntp is available in the F20 repos.
> 

AFAIK chrony still connects to NTP servers, however the vulnerability in
question is not with NTP as such but with ntpd, which as you say is no
longer part of Fedora.

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: name of file system : "unknown filesystem type 'FAT32"

[Angelo Moreschini]

OK..  thank you

On Mon, Dec 22, 2014 at 1:57 AM, Chris Murphy 
wrote:

>
>
> On Sun, Dec 21, 2014 at 9:50 AM, Angelo Moreschini <
> mrangelo.fed...@gmail.com> wrote:
>
>> Hi Joachim,
>>
>> "-t vfat"  worked... [?]
>>
>>
>> [angelo_user@zorro ~]$ sudo mount --type vfat /dev/sde1 /media/tmp_USB1
>> [angelo_user@zorro ~]$ ls -l /media/tmp_USB1
>>
>> *So, vfat include FAT32..*.
>>
>> Thank you very much .
>>
>> But,  how I can know -in general- things like this ..?
>>
>> Can you give me a link to a such documentation?
>>
>
> You really can't, it's just rote memorization, or fill your head with the
> right search engine keywords. If you'd used -t msdos that would have worked
> too, but only if you're familiar with the difference in would you know to
> prefer vfat. And for that matter -t umsdos also would have worked. But
> normally just omit -t and it gets autodetected, and I just tested this,
> both command line and GNOME default to vfat.
>
> --
> 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
>
>
-- 
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: NTP vulnerability

[Ed Greshko]

On 12/22/14 20:50, Patrick O'Callaghan wrote:
> On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
>> On 12/22/14 02:46, Aaron Gray wrote:
>>> There are no ntp or ntpd or systemd-timesyncd packages on F20 !
>> The default time sync package is now chrony.
>>
>> ntp is available in the F20 repos.
>>
> AFAIK chrony still connects to NTP servers, however the vulnerability in
> question is not with NTP as such but with ntpd, which as you say is no
> longer part of Fedora.
>

Of course I didn't quite say that "ntpd is no longer part of Fedora". 

I did say (or meant to say) that for new installs chrony is used by default 
over ntpd.  But, ntpd is still available in the repos.  And, if you happen to 
have been using ntpd in earlier versions of Fedora and doing updates instead of 
a new install you'd still be using ntpd.


-- 
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: Congrats on F21. fedup worked great!

[Ed Greshko]

On 12/22/14 19:53, Timothy Murphy wrote:
> I'd be happier if there were some evidence that the Fedup developers
> were keeping a note of problems.

Of course that would only come about if the folks having problems would be so 
kind as to file bugzillas.


-- 
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: NTP vulnerability

[sean darcy]

On 12/22/2014 08:32 AM, Ed Greshko wrote:

On 12/22/14 20:50, Patrick O'Callaghan wrote:

On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:

On 12/22/14 02:46, Aaron Gray wrote:

There are no ntp or ntpd or systemd-timesyncd packages on F20 !

The default time sync package is now chrony.

ntp is available in the F20 repos.


AFAIK chrony still connects to NTP servers, however the vulnerability in
question is not with NTP as such but with ntpd, which as you say is no
longer part of Fedora.



Of course I didn't quite say that "ntpd is no longer part of Fedora".

I did say (or meant to say) that for new installs chrony is used by default 
over ntpd.  But, ntpd is still available in the repos.  And, if you happen to 
have been using ntpd in earlier versions of Fedora and doing updates instead of 
a new install you'd still be using ntpd.


I'm on F20 (by fedup)  with ntp. I just ran yum to install chrony. yum 
didn't remove ntp* as part of the install.


How do you move to chrony?

sean

--
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: NTP vulnerability

[Tom Horsley]

On Mon, 22 Dec 2014 11:19:11 -0500
sean darcy wrote:

> How do you move to chrony?

Disable ntp and enable chrony.
-- 
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: [OT] Compiling a module for the Fedora kernel

[Klaus-Peter Schrage]

Am 22.12.2014 um 00:11 schrieb poma:

On 21.12.2014 19:45, Klaus-Peter Schrage wrote:

Am 21.12.2014 um 18:34 schrieb Heinz Diehl:

On 21.12.2014, Klaus-Peter Schrage wrote:


I first tried the latest and greatest nouveau driver from
freedesktop.org "as is", but the fan problem remains, so I
still have to apply "my" patch to the nouveau source..


I think you should file a bug against the nouveau driver on
bugs.freedesktop.org (xorg -> driver -> nouveau).


Yes, I'll do so when I have figured out how to apply the patch to
the nouveau driver from freedesktop.org. The patch is *againsts the
kernel source*, like: --- a/drivers/gpu/drm/nouveau/core/... +++
b/drivers/gpu/drm/nouveau/core/... but the structure of the driver
from git is: nouveau/drm/core/... (sorry for being so clueless, but
I never dealt with kernel modules ...)



Check rhbz #1121331, recent comments.


Thank you for your detailed instructions on bugzilla, they were easy to
follow - but on reboot, the gpu fan began to roar like before, although 
no errors occurred during the process of building and installing the 
nouveau module:


1. The nouveau source from git got patched by your patchfile in exactly 
the same way as the kernel source tree got patched by "my" patchfile. 
The four respective files were identical.


2. The make process of the nouveau module finished without error, I 
copied nouveau.ko to

/lib/modules/3.17.6-300.fc21.x86_64/updates/

3. After depmod, modinfo -n showed the appropriate location of the module:
/lib/modules/3.17.6-300.fc21.x86_64/updates/nouveau.ko

So I really can't figure out what happened, I repeated the process of 
rebuilding the complete kernel tree and got a quiet fan again ...





--
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: NTP vulnerability

[Lars E. Pettersson]

On 12/21/14 19:43, Aaron Gray wrote:

It should be 4.2.8 now as there are new vulnerabilities !


The following updates was submitted for testing at 2014-12-19.

For F19 in updates-testing
ntp-4.2.6p5-13.fc19

For F20 in updates-testing
ntp-4.2.6p5-19.fc20

For F21 in updates testing
ntp-4.2.6p5-25.fc21

All fixes the following bugs
1176191 - CVE-2014-9296: CVE-2014-9294 CVE-2014-9295 CVE-2014-9293 
ntp: various flaws [fedora-all]
1176032 - CVE-2014-9293: ntp: automatic generation of weak default 
key in config_auth()
1176035 - CVE-2014-9294: ntp: ntp-keygen uses weak random number 
generator and seed when generating MD5 keys
1176037 - CVE-2014-9295: ntp: Multiple buffer overflows via 
specially-crafted packets

1176040 - CVE-2014-9296: ntp: receive() missing return on error

If you are interested in NTP, install the test updates, and test them, 
and then give good (or bad) karma for faster release at 



Lars
--
Lars E. Pettersson 
http://www.sm6rpz.se/
--
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: [OT] Compiling a module for the Fedora kernel

[Rick Stevens]

On 12/22/2014 08:52 AM, Klaus-Peter Schrage wrote:

Am 22.12.2014 um 00:11 schrieb poma:

On 21.12.2014 19:45, Klaus-Peter Schrage wrote:

Am 21.12.2014 um 18:34 schrieb Heinz Diehl:

On 21.12.2014, Klaus-Peter Schrage wrote:


I first tried the latest and greatest nouveau driver from
freedesktop.org "as is", but the fan problem remains, so I
still have to apply "my" patch to the nouveau source..


I think you should file a bug against the nouveau driver on
bugs.freedesktop.org (xorg -> driver -> nouveau).


Yes, I'll do so when I have figured out how to apply the patch to
the nouveau driver from freedesktop.org. The patch is *againsts the
kernel source*, like: --- a/drivers/gpu/drm/nouveau/core/... +++
b/drivers/gpu/drm/nouveau/core/... but the structure of the driver
from git is: nouveau/drm/core/... (sorry for being so clueless, but
I never dealt with kernel modules ...)



Check rhbz #1121331, recent comments.


Thank you for your detailed instructions on bugzilla, they were easy to
follow - but on reboot, the gpu fan began to roar like before, although
no errors occurred during the process of building and installing the
nouveau module:

1. The nouveau source from git got patched by your patchfile in exactly
the same way as the kernel source tree got patched by "my" patchfile.
The four respective files were identical.


Are all four files inside nouveau or is there one or a couple that patch
something else?


2. The make process of the nouveau module finished without error, I
copied nouveau.ko to
/lib/modules/3.17.6-300.fc21.x86_64/updates/

3. After depmod, modinfo -n showed the appropriate location of the module:
/lib/modules/3.17.6-300.fc21.x86_64/updates/nouveau.ko

So I really can't figure out what happened, I repeated the process of
rebuilding the complete kernel tree and got a quiet fan again ...


a) Does your patch modify the version number of the driver, and if so,
b) After installing the new driver, does "modinfo nouveau" show your
new version?
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-First Law of Work:  -
-If you can't get it done in the first 24 hours, work nights.-
--
--
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: [OT] Compiling a module for the Fedora kernel

[Klaus-Peter Schrage]

Am 22.12.2014 um 17:52 schrieb Klaus-Peter Schrage:

Am 22.12.2014 um 00:11 schrieb poma:

On 21.12.2014 19:45, Klaus-Peter Schrage wrote:

Am 21.12.2014 um 18:34 schrieb Heinz Diehl:

On 21.12.2014, Klaus-Peter Schrage wrote:


I first tried the latest and greatest nouveau driver from
freedesktop.org "as is", but the fan problem remains, so I
still have to apply "my" patch to the nouveau source..


I think you should file a bug against the nouveau driver on
bugs.freedesktop.org (xorg -> driver -> nouveau).


Yes, I'll do so when I have figured out how to apply the patch to
the nouveau driver from freedesktop.org. The patch is *againsts the
kernel source*, like: --- a/drivers/gpu/drm/nouveau/core/... +++
b/drivers/gpu/drm/nouveau/core/... but the structure of the driver
from git is: nouveau/drm/core/... (sorry for being so clueless, but
I never dealt with kernel modules ...)



Check rhbz #1121331, recent comments.


Thank you for your detailed instructions on bugzilla, they were easy to
follow - but on reboot, the gpu fan began to roar like before, although
no errors occurred during the process of building and installing the
nouveau module:

1. The nouveau source from git got patched by your patchfile in exactly
the same way as the kernel source tree got patched by "my" patchfile.
The four respective files were identical.

2. The make process of the nouveau module finished without error, I
copied nouveau.ko to
/lib/modules/3.17.6-300.fc21.x86_64/updates/

3. After depmod, modinfo -n showed the appropriate location of the module:
/lib/modules/3.17.6-300.fc21.x86_64/updates/nouveau.ko

So I really can't figure out what happened, I repeated the process of
rebuilding the complete kernel tree and got a quiet fan again ...

There is even more magic: I repeated the proposed build process of the 
patched nouveau driver after an update to the most recent kernel 
(3.17.7-300) - result again: a noisy fan.


Than (after booting into a different kernel) I removed 
kernel-3.17.7-300.fc21.x86_64 (and the corresponding kernel-core and 
kernel-modules), this, btw., left /lib/modules/3.17.7-300.fc21.x86_64/ 
untouched, including the module binary nouveau.ko.


Next step was an update to kernel-3.17.7-300.fc21.x86_64 again, and 
after booting into it, the fan was silent! modinfo -n nouveau says:

/lib/modules/3.17.7-300.fc21.x86_64/updates/nouveau.ko,
which is the binary that had survived the erasure of 3.17.7-300.

I really have no idea about the way modules get installed during a 
kernel update, but there seems to be something more than a "simple" 
depmod command that I gave after the initial modules build.



--
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: [OT] Compiling a module for the Fedora kernel

[Lars E. Pettersson]

On 12/22/14 17:52, Klaus-Peter Schrage wrote:

2. The make process of the nouveau module finished without error, I
copied nouveau.ko to
/lib/modules/3.17.6-300.fc21.x86_64/updates/


I did exactly this, but did not realize that the kernel had been updated 
since I started my computer, so after the reboot the kernel was now at 
3.17.7-300, and it, of course, did not find my newly compiled module :) 
Perhaps this happened to you also?


I then compiled it for the new kernel, but for me the problem is still 
there, a noisy fan. I will investigate further...


Regarding Nicks question, here I get:
$ modinfo nouveau
filename:   /lib/modules/3.17.7-300.fc21.x86_64/updates/nouveau.ko

Which is the file I compiled.

Lars
--
Lars E. Pettersson 
http://www.sm6rpz.se/
--
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: [OT] Compiling a module for the Fedora kernel

[Rick Stevens]

On 12/22/2014 09:58 AM, Klaus-Peter Schrage wrote:

Am 22.12.2014 um 17:52 schrieb Klaus-Peter Schrage:

Am 22.12.2014 um 00:11 schrieb poma:

On 21.12.2014 19:45, Klaus-Peter Schrage wrote:

Am 21.12.2014 um 18:34 schrieb Heinz Diehl:

On 21.12.2014, Klaus-Peter Schrage wrote:


I first tried the latest and greatest nouveau driver from
freedesktop.org "as is", but the fan problem remains, so I
still have to apply "my" patch to the nouveau source..


I think you should file a bug against the nouveau driver on
bugs.freedesktop.org (xorg -> driver -> nouveau).


Yes, I'll do so when I have figured out how to apply the patch to
the nouveau driver from freedesktop.org. The patch is *againsts the
kernel source*, like: --- a/drivers/gpu/drm/nouveau/core/... +++
b/drivers/gpu/drm/nouveau/core/... but the structure of the driver
from git is: nouveau/drm/core/... (sorry for being so clueless, but
I never dealt with kernel modules ...)



Check rhbz #1121331, recent comments.


Thank you for your detailed instructions on bugzilla, they were easy to
follow - but on reboot, the gpu fan began to roar like before, although
no errors occurred during the process of building and installing the
nouveau module:

1. The nouveau source from git got patched by your patchfile in exactly
the same way as the kernel source tree got patched by "my" patchfile.
The four respective files were identical.

2. The make process of the nouveau module finished without error, I
copied nouveau.ko to
/lib/modules/3.17.6-300.fc21.x86_64/updates/

3. After depmod, modinfo -n showed the appropriate location of the
module:
/lib/modules/3.17.6-300.fc21.x86_64/updates/nouveau.ko

So I really can't figure out what happened, I repeated the process of
rebuilding the complete kernel tree and got a quiet fan again ...


There is even more magic: I repeated the proposed build process of the
patched nouveau driver after an update to the most recent kernel
(3.17.7-300) - result again: a noisy fan.

Than (after booting into a different kernel) I removed
kernel-3.17.7-300.fc21.x86_64 (and the corresponding kernel-core and
kernel-modules), this, btw., left /lib/modules/3.17.7-300.fc21.x86_64/
untouched, including the module binary nouveau.ko.

Next step was an update to kernel-3.17.7-300.fc21.x86_64 again, and
after booting into it, the fan was silent! modinfo -n nouveau says:
/lib/modules/3.17.7-300.fc21.x86_64/updates/nouveau.ko,
which is the binary that had survived the erasure of 3.17.7-300.

I really have no idea about the way modules get installed during a
kernel update, but there seems to be something more than a "simple"
depmod command that I gave after the initial modules build.


Oh, yeah. Forgot. I suspect you'll need to rebuild the initramfs after
patching your driver. The "depmod" verifies that all the module
dependencies were met so if you were to "modprobe" nouveau it'd work,
but I believe nouveau goes into the initramfs so the boot was still
using the original one from the kernel update. So:

1. Patch
2. Build
3. Move to appropriate spot
4. Depmod
5. Rebuild initramfs...make sure the new module is included
6. Reboot
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-   To err is human, to moo bovine.  -
--
--
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: [OT] Compiling a module for the Fedora kernel

[Rick Stevens]

On 12/22/2014 10:03 AM, Lars E. Pettersson wrote:

On 12/22/14 17:52, Klaus-Peter Schrage wrote:

2. The make process of the nouveau module finished without error, I
copied nouveau.ko to
/lib/modules/3.17.6-300.fc21.x86_64/updates/


I did exactly this, but did not realize that the kernel had been updated
since I started my computer, so after the reboot the kernel was now at
3.17.7-300, and it, of course, did not find my newly compiled module :)
Perhaps this happened to you also?

I then compiled it for the new kernel, but for me the problem is still
there, a noisy fan. I will investigate further...

Regarding Nicks question, here I get:
$ modinfo nouveau
filename:   /lib/modules/3.17.7-300.fc21.x86_64/updates/nouveau.ko

Which is the file I compiled.


I was more interested in the "version:" line, not the filename, but
looking at nouveau, it doesn't support that, just the "vermagic:" line.
Gr!
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-   Sarchasm: The gulf between the author of sarcastic wit and the   -
- reader...who doesn't get it.   -
--
--
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: [OT] Compiling a module for the Fedora kernel

[Lars E. Pettersson]

On 12/22/14 19:10, Rick Stevens wrote:

On 12/22/2014 10:03 AM, Lars E. Pettersson wrote:

Regarding Nicks question, here I get:
$ modinfo nouveau
filename:   /lib/modules/3.17.7-300.fc21.x86_64/updates/nouveau.ko

Which is the file I compiled.


I was more interested in the "version:" line, not the filename, but
looking at nouveau, it doesn't support that, just the "vermagic:" line.
Gr!


Sorry for misspelling your name.

Yes, no version, just vermagic.

You were completely right. Step "5. Rebuild initramfs...make sure the 
new module is included" is needed. Just did it, and my computer is now 
as silent as it was when I bought it :) Thanks!


Lars
--
Lars E. Pettersson 
http://www.sm6rpz.se/
--
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: [OT] Compiling a module for the Fedora kernel

[Heinz Diehl]

On 22.12.2014, Lars E. Pettersson wrote: 

> I then compiled it for the new kernel, but for me the problem is still
> there, a noisy fan. I will investigate further...

How about finding the first official kernel with the faulty behaviour,
bisecting the offending commit and reporting it to the lkml people?

Continuously patching away an obvious bug can't be the solution (and
someday it won't work any longer or need a manual merge)..

Btw: is the problem still persistent in plain vanilla 3.19-rc1?
https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.19-rc1.tar.xz

-- 
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: [OT] Compiling a module for the Fedora kernel

[Klaus-Peter Schrage]

Am 22.12.2014 um 19:05 schrieb Rick Stevens:

On 12/22/2014 09:58 AM, Klaus-Peter Schrage wrote:

Am 22.12.2014 um 17:52 schrieb Klaus-Peter Schrage:

Am 22.12.2014 um 00:11 schrieb poma:

On 21.12.2014 19:45, Klaus-Peter Schrage wrote:

Am 21.12.2014 um 18:34 schrieb Heinz Diehl:

On 21.12.2014, Klaus-Peter Schrage wrote:



Oh, yeah. Forgot. I suspect you'll need to rebuild the initramfs after
patching your driver. The "depmod" verifies that all the module
dependencies were met so if you were to "modprobe" nouveau it'd work,
but I believe nouveau goes into the initramfs so the boot was still
using the original one from the kernel update. So:

1. Patch
2. Build
3. Move to appropriate spot
4. Depmod
5. Rebuild initramfs...make sure the new module is included
6. Reboot


Rick, I think that's it: lsinitrd lists the nouveau driver and points to 
the newly built binary in /lib/modules/.../updates/.


In older versions of the initramfs image in my /boot directory, the 
original driver is listed.


So, in your step 5, a simple "dracut" should do the trick (with the 
"--force"-option when the initramfs version corresponds to the running 
kernel). I found that dracut finds and includes the binary in 
/lib/modules/ .../updates/.


Thank you for pointing me into this direction!


--
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: [OT] Compiling a module for the Fedora kernel

[Lars E. Pettersson]

On 12/22/14 19:48, Heinz Diehl wrote:

How about finding the first official kernel with the faulty behaviour,
bisecting the offending commit and reporting it to the lkml people?


This bugzilla-comment contains a link to the kernel patch that seem to 
create problems for some of us. The question is whether this patch cures 
problems for others?




(my card is Fermi card, NVC0, a Quadro 2000, code name NVC3(GF106), 
whether that one has "0x46 entries in the thermal table", or not, is 
beyond me)



Continuously patching away an obvious bug can't be the solution (and
someday it won't work any longer or need a manual merge)..


Yes...


Btw: is the problem still persistent in plain vanilla 3.19-rc1?
https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.19-rc1.tar.xz


I haven't compiled a kernel in years (decades), but my hunch is that if 
the patch mentioned in the bugzilla above is still there, it will still 
have problems (for some of us).


Lars
--
Lars E. Pettersson 
http://www.sm6rpz.se/
--
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: [OT] Compiling a module for the Fedora kernel

[Klaus-Peter Schrage]

Am 22.12.2014 um 19:48 schrieb Heinz Diehl:

On 22.12.2014, Lars E. Pettersson wrote:


I then compiled it for the new kernel, but for me the problem is still
there, a noisy fan. I will investigate further...


How about finding the first official kernel with the faulty behaviour,
bisecting the offending commit and reporting it to the lkml people?


Heinz, it was you who pointed me to the offending patch:
http://tinyurl.com/mz4vsr8
As far as I can see, the nouveau driver hasn't changed much since then.



Continuously patching away an obvious bug can't be the solution (and
someday it won't work any longer or need a manual merge)..


As you have suggested, I will file a bug on freedesktop.org against the 
nouveau driver.



--
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: [OT] Compiling a module for the Fedora kernel

[Heinz Diehl]

On 22.12.2014, Klaus-Peter Schrage wrote: 

> Heinz, it was you who pointed me to the offending patch:
> http://tinyurl.com/mz4vsr8
> As far as I can see, the nouveau driver hasn't changed much since then.

Hmm, I wrote this because it seems to me that reverting this
particular commit does work for some, but not for others. Maybe the
faulty behavior is triggered by something which is exposed to this
particuar commit, without the commit itself being the root cause.

-- 
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: [OT] Compiling a module for the Fedora kernel

[kpschrage]

Gesendet von: YOGA TABLET 10 HD+
Am 22.12.2014 20:37 schrieb Heinz Diehl :
>
> On 22.12.2014, Klaus-Peter Schrage wrote:
>
> > Heinz, it was you who pointed me to the offending patch:
> > http://tinyurl.com/mz4vsr8
> > As far as I can see, the nouveau driver hasn't changed much since then.
>
> Hmm, I wrote this because it seems to me that reverting this
> particular commit does work for some, but not for others. Maybe the
> faulty behavior is triggered by something which is exposed to this
> particuar commit, without the commit itself being the root cause.
>
Findung out that would be beyond my scope, so, again, filing a bug upstream 
will be my next step.





-- 
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: Congrats on F21. fedup worked great!

[Rolf Turner]

On 23/12/14 02:35, Ed Greshko wrote:

On 12/22/14 19:53, Timothy Murphy wrote:

I'd be happier if there were some evidence that the Fedup
developers were keeping a note of problems.


Of course that would only come about if the folks having problems
would be so kind as to file bugzillas.


I tried to file a bugzilla once, in respect of a problem that I'd found 
--- or at least thought I'd found.  Can't remember what the problem was; 
it was quite a while ago.


Anyhow I found it impossible.  The interface was opaque, myriad 
questions were asked that I had no idea how to answer, and the whole 
thing was riddled with incomprehensible geek-speak.  I gave up and have 
not been back since.


cheers,

Rolf Turner

--
Rolf Turner
Technical Editor ANZJS
--
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: Congrats on F21. fedup worked great!

[Timothy Murphy]

Ed Greshko wrote:

> On 12/22/14 19:53, Timothy Murphy wrote:
>> I'd be happier if there were some evidence that the Fedup developers
>> were keeping a note of problems.
> 
> Of course that would only come about if the folks having problems would be
> so kind as to file bugzillas.

I agree that would be good.
(I did actually file a bugzilla for one of my two Fedup problems.)

But I think a simple survey - "How did your Fedup go?" - would be good too.
I guess 80% would just say "Fine", but it might be worth knowing
what problems the other 20% encountered.

-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin


-- 
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: [OT] Compiling a module for the Fedora kernel

[poma]

On 22.12.2014 17:52, Klaus-Peter Schrage wrote:
> Am 22.12.2014 um 00:11 schrieb poma:
>> On 21.12.2014 19:45, Klaus-Peter Schrage wrote:
>>> Am 21.12.2014 um 18:34 schrieb Heinz Diehl:
 On 21.12.2014, Klaus-Peter Schrage wrote:

> I first tried the latest and greatest nouveau driver from
> freedesktop.org "as is", but the fan problem remains, so I
> still have to apply "my" patch to the nouveau source..

 I think you should file a bug against the nouveau driver on
 bugs.freedesktop.org (xorg -> driver -> nouveau).
>>>
>>> Yes, I'll do so when I have figured out how to apply the patch to
>>> the nouveau driver from freedesktop.org. The patch is *againsts the
>>> kernel source*, like: --- a/drivers/gpu/drm/nouveau/core/... +++
>>> b/drivers/gpu/drm/nouveau/core/... but the structure of the driver
>>> from git is: nouveau/drm/core/... (sorry for being so clueless, but
>>> I never dealt with kernel modules ...)
>>>
>>
>> Check rhbz #1121331, recent comments.
> 
> Thank you for your detailed instructions on bugzilla, they were easy to
> follow - but on reboot, the gpu fan began to roar like before, although 
> no errors occurred during the process of building and installing the 
> nouveau module:
> 
> 1. The nouveau source from git got patched by your patchfile in exactly 
> the same way as the kernel source tree got patched by "my" patchfile. 
> The four respective files were identical.
> 
> 2. The make process of the nouveau module finished without error, I 
> copied nouveau.ko to
> /lib/modules/3.17.6-300.fc21.x86_64/updates/
> 
> 3. After depmod, modinfo -n showed the appropriate location of the module:
> /lib/modules/3.17.6-300.fc21.x86_64/updates/nouveau.ko
> 
> So I really can't figure out what happened, I repeated the process of 
> rebuilding the complete kernel tree and got a quiet fan again ...
> 


- Create a custom dracut config
/etc/dracut.conf.d/exclude-nouveau-in-the-initramfs.conf
# PUT YOUR CONFIG IN files named *.conf in /etc/dracut.conf.d/
# /etc/dracut.conf.d/*.conf will override the settings in /etc/dracut.conf
# SEE man dracut.conf(5)
#
# kernel modules to omit
# Specify a space-separated list of kernel modules not to add to the initramfs.
# The kernel modules have to be specified without the ".ko" suffix.
#
omit_drivers+=" nouveau "


- Only this time, for the current kernel
# dracut -f --kver $(uname -r)


- nouveau.ko doesn't fall anymore into the init image
# lsinitrd /boot/initramfs-$(uname -r).img | grep nouveau ; echo $?
1


Therefore, you no longer need to re/generate an initramfs after building and 
installing patched nouveau.

-- 
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: [OT] Compiling a module for the Fedora kernel

[Lars E. Pettersson]

On 12/22/14 22:07, poma wrote:

Therefore, you no longer need to re/generate an initramfs after building and 
installing patched nouveau.


Isn't the nouveau module needed in initramfs? If not, why is it put 
there in the first place?


Lars
--
Lars E. Pettersson 
http://www.sm6rpz.se/
--
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: [OT] Compiling a module for the Fedora kernel

[poma]

On 22.12.2014 22:18, Lars E. Pettersson wrote:
> On 12/22/14 22:07, poma wrote:
>> Therefore, you no longer need to re/generate an initramfs after building and 
>> installing patched nouveau.
> 
> Isn't the nouveau module needed in initramfs? If not, why is it put 
> there in the first place?
> 
> Lars
> 

http://www.linuxfromscratch.org/~krejzi/kde5/postlfs/initramfs.html
"The only purpose of an initramfs is to mount the root filesystem."
...
But in modern Linux distributions in the init-ram-fs-image are the giraffe, 
elephant and parrot, of course.


-- 
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: NTP vulnerability

[Patrick O'Callaghan]

On Mon, 2014-12-22 at 21:32 +0800, Ed Greshko wrote:
> On 12/22/14 20:50, Patrick O'Callaghan wrote:
> > On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
> >> On 12/22/14 02:46, Aaron Gray wrote:
> >>> There are no ntp or ntpd or systemd-timesyncd packages on F20 !
> >> The default time sync package is now chrony.
> >>
> >> ntp is available in the F20 repos.
> >>
> > AFAIK chrony still connects to NTP servers, however the vulnerability in
> > question is not with NTP as such but with ntpd, which as you say is no
> > longer part of Fedora.
> >
> 
> Of course I didn't quite say that "ntpd is no longer part of Fedora". 
> 
> I did say (or meant to say) that for new installs chrony is used by default 
> over ntpd.  But, ntpd is still available in the repos.  And, if you happen to 
> have been using ntpd in earlier versions of Fedora and doing updates instead 
> of a new install you'd still be using ntpd.

My bad. I should have said "ntpd is no longer the default in Fedora".

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: NTP vulnerability

[Ralf Corsepius]

On 12/22/2014 01:50 PM, Patrick O'Callaghan wrote:

On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:

On 12/22/14 02:46, Aaron Gray wrote:

There are no ntp or ntpd or systemd-timesyncd packages on F20 !


The default time sync package is now chrony.

ntp is available in the F20 repos.



AFAIK chrony still connects to NTP servers, however the vulnerability in
question is not with NTP as such but with ntpd, which as you say is no
longer part of Fedora.


Of course, ntp is part of Fedora:

# repoquery -q ntp
ntp-0:4.2.6p5-23.fc21.x86_64

It's just that it's not installed by default.

Ralf

--
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

running a join.me meeting

[Robert Moskowitz]

Has anyone here used join.me on Fedora?

As a participant it is no problem.  But to manage the meeting, there is 
a windows exe that gets downloaded.


I had to quickly switch to a windows system for a meeting I had to run 
today.  Has anyone tried this?  Does this exe work in WINE?



--
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

man sections

[Tim]

Going off on a tangent here, so I'm deliberately splitting a thread...


On Mon, 2014-12-22 at 10:38 +1100, Cameron Simpson wrote:
> Run the command:
>  
>   man 8 mount
>  
> and see the types available for "-t" option.
>  
> The "general" part of this advice is that: you're using the "mount"
> command, so read the "mount" manual entry!
>  
> ("mount" is an administrative command, so it is in section 8, not
> section 1.)

I've never come to grips with multiple docs for man, depending on such
things as section numbers.  And I see no difference in output between
"man 8 mount" or "man mount"  Granted I haven't gone the whole way
through, but I've already gone deep into them, and not seen anything.

-- 
tim@localhost ~]$ uname -rsvp

Linux 3.17.6-200.fc20.i686 #1 SMP Mon Dec 8 15:42:32 UTC 2014 i686

All mail to my mailbox is automatically deleted, there is no point trying
to privately email me, I will only read messages posted to the public lists.

George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.

-- 
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