This may be a dumb question, but why can't Redhat distribute NVIDIA binary
In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it
"2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section
2.1.1, SOFTWARE designed exclusively for use on the Linux operating system
copied and redistributed, provided that the binary files thereof are not
modified in any
way (except for unzipping of compressed files)."
So, what's keeping RedHat from putting the drivers in the distribution? If
it's a GPL
thing, would it be easy to just download it during installation or at
least give the option to the user?
Ok, I have had Yarrow working well for a while now, but yesterday I
started experiencing some odd issues with my mouse. All of a sudden it
stops working correctly. The only thing that seems to fix is to kill X
and run mouse-test, then restart.
Also, I have FC 1 running on a desktop which is hooked up to a KVM
switch. Whenever I go to another PC, and return, the same thing
happens, the mouse goes crazy.
On Thu, 2017-07-06 at 15:13 -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote:
> > Hi, folks! A while ago, Xen virtualization functionality was added to
> > the criteria and the validation test case set, on the understanding
> > that Oracle would provide testing for it (and help fix bugs as they
> > arose).
> > For the last couple of releases we really have not had any such testing
> We had been doing the testing, it just that we (or rather me and
> Dariof) seem to get a wind of this at the last minute. Not sure exactly
> how to fix that thought.
Well, I mean, every few *days* a compose gets nominated for validation
testing, and a mail is sent to test-announce. Just check your test-
announce archives for mails with "nominated for testing" in their
subject lines, and you'll see dozens. Is this not sufficient
> > from Oracle. On that basis, I'm proposing we remove this Final
> > criterion:
> s/Oracle/Xen Project/ I believe?
Perhaps, it's just that it always seemed to be you doing the testing,
so they got a bit conflated :)
> > "The release must boot successfully as Xen DomU with releases providing
> > a functional, supported Xen Dom0 and widely used cloud providers
> > utilizing Xen."
> > and change the 'milestone' for the test case -
> > https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt -
> > from Final to Optional.
> > Thoughts? Comments? Thanks!
> I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release
cycle, on the composes that are "nominated for testing".
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
Did anyone succeed in virt-install'ing F24 beta using kickstart
(on CentOS 6 host, if that matters)?
I see lots of warnings (dracut-initqueue), then the console goes
into a slowly filling bar at the bottom (plymouthd!?), then I see
lots of "No space left on device" errors, then a dracut emergency
shell is started.
The generated rdsosreport.txt contains 34284 lines...
FWIW, when *not* using kickstart I can install F24 beta on the
same system with virt-install fine.
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
I'm interested in helping out with QA. I have been a GNU/Linux user on
and off since the late 90s but went all GNU/Linux about 10 years
ago. I've been running Fedora as my desktop system for a couple of
years and now I'd like to give something back.
There are a lot of different tasks listed on the Wiki. What would be
something useful/a priority that a beginner could do? My IRC and FAS
nickname is andrzejp.
I've filed a bug about this here:
Fedora 27 offline updates (gnome-software intitiated) are failing
This is on a system upgraded a couple weeks ago with 'dnf
system-upgrade' from Fedora 26 to Fedora 27.
I've receive a notification there are updatess, so I go into Gnome
Software, choose Restart & Upgrade from within Gnome-Software, it
reboots and plymouth gives me the updating indication and status, and
pretty much immediately I get a reboot.
Once rebooted, it's clear the updates have not been applied.
[ 6.218141] f27h.localdomain pk-offline-update: percentage 4%
[ 6.254059] f27h.localdomain pk-offline-update: percentage 6%
[ 6.325118] f27h.localdomain dnf: Error: use 'dnf
system-upgrade reboot' to begin the upgrade
[ 6.352470] f27h.localdomain systemd:
dnf-system-upgrade.service: Main process exited, code=exited,
[ 6.356239] f27h.localdomain systemd: Failed to start System
Upgrade using DNF.
[ 6.356570] f27h.localdomain systemd:
dnf-system-upgrade.service: Unit entered failed state.
[ 6.356777] f27h.localdomain systemd:
dnf-system-upgrade.service: Failed with result 'exit-code'.
[ 6.356983] f27h.localdomain systemd: Rebooting: service failed
Why is dnf saying to use 'dnf system-upgrade reboot' for a minor
update? I'm not asking for an upgrade, that's already been done and it