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
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
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, 2 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, 2 months
autoconf breakage on x86_64.
by Sam Varshavchik
I don't know the right way to fix this, but something is definitely broken;
and something needs to be fixed, one way or the other. The question is what
exactly needs to be fixed.
Consider something like this:
LIBS="-lresolv $LIBS"
AC_TRY_LINK_FUNC(res_query, AC_MSG_RESULT(yes), AC_MSG_RESULT(no))
Here's what happens on x86_64:
gcc -o conftest -g -O2 -Wall -I.. -I./.. conftest.c -lresolv >&5
/tmp/ccW7EeDX.o(.text+0x7): In function `main':
/home/mrsam/src/courier/authlib/configure:5160: undefined reference to
`res_query'
collect2: ld returned 1 exit status
configure:5147: $? = 1
configure: failed program was:
[ blah blah blah ]
| /* We use char because int might match the return type of a gcc2
| builtin and then its argument prototype would still apply. */
| char res_query ();
| int
| main ()
| {
| res_query ();
| ;
| return 0;
| }
The same exact test on FC1 x86 will work.
The reason appears to be that you have to #include <resolv.conf> on x86_64
in order to succesfully pull res_query() out of libresolv.so. You don't
need to do this on x86, and the test program generated by AC_TRY_LINK_FUNC
does not include any headers, but uses a manual prototype.
So, what now?
16 years, 4 months
FC3T2 EggCups Crashing
by Will H. Backman
After updating today, I keep getting a popup that egg-cups has crashed
(Restart?)
It seems to be when I stick a CD in with a windows autorun. I'll have to
dig more. Anyone else seeing this?
--
Will Backman
Coastal Enterprises, Inc.
- A computer is a device used to convert data into error messages.
18 years, 3 months
no /dev/nst0
by Neal Becker
My scsi tape used to be /dev/nst0, now it doesn't seem to have been created.
18 years, 4 months
SELinux error with -584 kernel
by Michel Salim
Hi,
I get audit errors when booting up (and similar messages when shutting
down) with the -1.584 kernel:
audit(1095879279.586:0): avc: denied { read write } for pid=1701
exe=/sbin/minilogd name=console dev=tmpfs ino=993
scontext=user_u:system_r:syslogd_t tcontext=user_u:object_r:tmpfs_t
tclass=chr_file
(and lots of other messages like this one)
This does not happen under the -1.541 kernel that shipped with the
install media; is this normal, should I file a bug, and against the
kernel, selinux-policy-targetd, or mkinitrd?
Thanks,
--
Michel Salim 林智勇
http://salimma.livejournal.com
18 years, 4 months
some questions regarding FC3t2 release notes
by Robert P. J. Day
(repost of what was sent to anaconda list since it mostly involved
installation.)
reading the FC3t2 release notes, some curiosities:
1) "The disk space requirements listed below represent the disk space taken up
by Fedora Core 2.91 Test 2 after the installation is complete. However,
additional disk space is required during the installation to support the
installation environment. This additional disk space corresponds to the size of
/Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in
/var/lib/rpm on the installed system."
this suggests that the stage2.img file is copied to the hard drive during the
installation, so that makes sense. but i don't understand why the stuff under
/var/lib/rpm would be considered an "additional" space requirement above and
beyond the regular install. it's all still there after the installation is
complete.
can someone clarify why the contents of /var/lib/rpm would be considered an
"additional" space requirement?
2) i could have sworn that someone posted that SELinux was disabled by default
during the install, but during my install, it was definitely activated, and i
had to manually turn it off.
3) "Memory testing may be performed prior to installing Fedora Core by entering
memtest86 at the boot: prompt. This causes the Memtest86 standalone memory
testing software to run. Memtest86 memory testing continues until the Esc key
is pressed."
"NOTE: You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use this
feature."
um ... i'm pretty sure memtest is also part of boot.iso and diskboot.img, no?
the way the above is worded is a bit misleading.
4) regarding space required for installation:
"... Minimum for graphical: 192MB ..."
"... However, due to the necessity of containing the installer image in RAM,
only systems with more than 128MB of RAM (or systems booted from CD-ROM 1,
which contains the installer image) can use the graphical installer."
and the correct minimum value would be ... ?
more later as i keep reading.
rday
18 years, 4 months
