NVIDIA Question
by David St.Clair
This may be a dumb question, but why can't Redhat distribute NVIDIA binary
drivers?
In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it
says:
"2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section
2.1.1, SOFTWARE designed exclusively for use on the Linux operating system
may be
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?
Thanks,
--
David St.Clair
dstclair(a)cs.wcu.edu
1 year, 8 months
Mouse goes crazy
by Jonathan Villa
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.
Any ideas?
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.
???
1 year, 8 months
Mouse Wheel gone
by Christian Menzel
Since the latest xorg-X11 upgrade I receive the already mentioned XKB
error and the mouse wheel is not working anymore.
Has anybody seen this behavior?
Regards
Chris
7 years, 10 months
Re: NFS failure
by Fulko.Hew＠sita.aero
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
wrote:
> On Wed, 7 Apr 2004, Jeff Elkins wrote:
>
> > I'm getting failure messages on my nfs mounts i.e. :
> >
> > mount to NFS server 'music.elkins' failed: server is down.
> >
> > nsfd appears to be running and I didn't see anything suspicious in the
logs.
> > The servers are up and running and have other clients connected.
>
> You didn't mention what steps you took to debug it:
>
> Can you ping the server?
> What is the output of rpcinfo -p servername?
> Does the server have access restrictions (firewall, TCP Wrappers, etc)?
I have the same symptoms...
rpcinfo says that nfs et.al. are running.
Something has changed in test 2, since the same PC running RH9
accesses that host just fine.
7 years, 10 months
Dependencies for MonoDevelop
by Benjamín Valero Espinosa
Today I have installed MonoDevelop in FC10 (recently installed and
updated) and cannot see or navigate any source file when I try to open
it. For the second problem I have installed "ctags". For the first, I
have tried to install "gtksourceview2-sharp". I think both should be
dependencies of the "monodevelop" package.
When I try:
# pkcon install gtksourceview2-sharp
I get that:
Error: package-already-installed : The packages failed to be installed
But if I search that package, I get that:
available gtksourceview2-sharp-1.0-2.svn89788.2.fc10 A C sharp
binder for gtksourceview2
available gtksourceview2-sharp-devel-1.0-2.svn89788.2.fc10 Development
files for gtksourceview-sharp
so is not really installed. What can it be? Thanks for your work.
14 years, 6 months
F10 and nVidia ==> Big Problems
by Christopher A Williams
This was also a problem on F9, but it is now worse on F10 beta. Video
simply fails to load on my system using the F10 live CD. This happens on
both 32-bit and 64-bit versions. I've reproduced this on other similar
computers as well.
Video attempts to load at bootup but eventually fails and drops to a
text mode login prompt. My system is a self-built machine. Here's the
specific video oriented info:
EVGA e-7100/630i Motherboard
- Onboard nVidia GeForce 7100 GPU
- nVidia nForce 630i chip set
I have 4GB RAM and a Intel Quad-Core processor.
When I loaded F9, I worked around the problem by:
1) Waiting for the live system to fail back to text mode
2) Logging in as root at the text prompt
3) Run system-config-display and accepting the detected defaults
4) Run startx to start the gui
5) Run the installer as normal
Post-install, the OpenSource nv driver would load and provide a
reasonable display resolution until I could install the Livna nVidia
drivers.
On F10, system-config-display is no longer there! So instead I have to:
1) Wait for the live system to fail back to text mode
2) Log in as root at the text prompt
3) Install system-config-display (yum -y install system-config-display)
4) Run system-config-display and accept the detected defaults (nothing
else works)
5) Run startx to start the gui
6) Run the installer as normal
However, on F10, startx only provides 800x600 resolution, despite that
my display is capable of 1920x1200.
Can we get this fixed in F10 please? I'm happy to Bugzilla this if it
isn't there already.
Cheers,
Chris
--
=========================================
"In theory there is no difference between theory and practice.
In practice there is."
--Yogi Berra
14 years, 8 months
java redisplay problem on intel driver
by Per Bothner
Could people try the attached Java test program?
There is a bad redisplay problem for large (greater than around 1000
lines) text windows using a TextArea (or a Swing JTextPane).
I have the feeling it is specific to the Intel driver.
To test it, you need to have openjdk "java" installed and
in your path:
$ java -version
java version "1.6.0_0"
IcedTea6 1.4 (fedora-7.b12.fc10-i386) Runtime Environment (build
1.6.0_0-b12)
OpenJDK Server VM (build 10.0-b19, mixed mode)
Java is provided by java-1.6.0-openjdk-1.6.0.0-7.b12.fc10.i386.
However, the same problem occurs with jdk1.6.0 update 11
downloaded directly from Sun, as well as jdk 1.5.0_05.
To test it, put TextTest.java in a temporary directory,
cd to that directory, compile it, and run it:
$ javac TextTest.java
$ java TextTest
Now try scrolling back and forth a bit. What happens for me is that
the text lines will be over-written multiple times on top of each other.
The interesting thing is that only the first 700 lines
or so are garbled - the remaining lines are fine.
My guess is that there is some weird interaction between Java,
the Gtk peers, and the intel driver, since otherwise more people
would have reported this problem. Also, I have tried it on an
NVidia-based laptop, and well as with the vesa driver (iirc).
It would be helpful to get some data-points before I decide
whether to complain to Sun or to Intel or to Gnome!
--
--Per Bothner
per(a)bothner.com http://per.bothner.com/
14 years, 8 months
selinux adventures/troubles
by Michal Jaegermann
I wonder if this is my unique experience or this is widely observed.
So far, AFAICT, when installing a machine "from scratch", and while
keeping a layout as plain as possible, then selinux is rather
expected to work; at least decently enough. The picture becomes
entirely diferent when you are trying to upgrade a distro. What
results of such exercise will be I am unable to predict.
I have now such example recently moved from F8 to F10. It was
configured "targeted" and in the past it was behaving ok. Burned on
other occasions I set selinux to "permissive" before upgrading
distros with an intentions to restore "enforcing" later on. In
anaconda it is hard not to notice that an installation of
selinux-policy-targeted package takes a really long time. One would
think that this is because some checks are run or some relabeling
takes place or whatever. Only the end result was that after a
reboot a machine was mostly busy spitting all kind of complaints and
warnings. If not that "permissive" setting it most likely would
not boot at all. 'touch /.autorelabel' followed by a reboot and
relabelling took care of most of that stuff. But without the
machine really going into a service at least two "mysteries" remain
(and I fully expect more to show up later).
There is a requirement that a root needs to be able to login via
ssh on this machine using an authorized key (a remote root login
with a password is blocked). This works but I am getting every
time "Unable to get valid context for root" and in /var/log/secure:
"pam_selinux(sshd:session): Security context
system_u:system_r:logrotate_t:s0-s0:c0.c1023 is not allowed for
system_u:system_r:logrotate_t:s0-s0:c0.c1023".
Eh? What this is supposed to mean? There are no corresponding
'sealert' message I can find nor 'allow2why' comes with any reasons.
Another problem which hits immediately is that 'root' has
.procmailrc file and it is necessary there. Every mail to root
results in selinux complaints. Initially these were in a form:
SELinux is preventing the procmail from using potentially mislabeled
files (./_ZoC.lwQVJB.xxxxxx.yyyy.zzz).
and propositions to relabel these. A very good advice. :-)
This time 'allow2rules' had the following things to propose:
allow procmail_t admin_home_t:dir { write remove_name add_name };
allow procmail_t admin_home_t:file { write create unlink link };
I generated a corresponding module, and added it to a fray, and
that only changed a nature of complaints to:
SELinux is preventing the procmail from using potentially mislabeled
files (./.procmailrc).
The catch is that /root/.procmailrc has for a label
system_u:object_r:admin_home_t:s0 and 'restorecon -v' on it does not
change anything at all.
Of course I have no idea if there are policy problems, or troubles
are somewhere else, or everything really works as expected. A big
mystery.
To makes things even more interesting I have another machine, also
upgraded from F8 to F10 and configured, it would appear, in a
similar way, and none of symptoms described above shows there.
Only on that other box /root/.procmailrc is labeled with
system_u:object_r:user_home_t (do not ask me why!) and
system_u:object_r:user_home_dir_t shows on /root and running
there 'restorecon -vR /root' also does not change anything at all.
So apparently both are correct only one does not work and how and
why they aquired different labels is another of those puzzles.
Does selinux policies are applied at random?
Michal
14 years, 8 months
