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
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?
17 years
Re: no USB jump/flash drive support yet
by t l
The only additional info I've been able to get
is by running 'lsusb'. It lists the USB Flash
drive that usbcore fails to probe correctly.
Here is the output from 'lsusb':
Bus 004 Device 004: ID 08ec:0010 M-Systems Flash Disk Pioneers DiskOnKey
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 03f0:1e11 Hewlett-Packard
Bus 001 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 0000:0000
tom
------------------------------------
* From: TGS <spam tachegroup com>
Same exact problem here.
I am able to use some USB Flash drives without issue, but some fail. The
failures lock up the whole mount subsystem capability, and the only way to
fix it is to restart. My errors are just like the below. Is there a way to
gather detailed information for the failed devices?
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
19 years
kernel for testing
by Arjan van de Ven
Hi,
we're looking at doing a kernel update in about a week or so, a
candidate kernel for testing just has been uploaded to the test area for
fc2; kernel 2.6.8-1.520
Greetings,
Arjan van de Ven
19 years
Bug in konsole
by Harry Putnam
My setup:
*--
Software:
Linux kernel 2.6.7-1.517 Architecture i686
Fedora Core release 2.90 (FC3 Test 1)
kde desktop
Hardware:
model name : Intel(R) Pentium(R) 4 CPU 2.00GHz
cpu MHz : 1994.032
*--
I'm seeing a freeze in a konsole terminal under these circumstances:
From an xterm: konsole &
The resulting terminal reports `echo $TERM'
konsole
Now from that konsole ssh LANHOST (login)
In that terminal press ^-s (C-s). It then is unusable.
(LANHOST is also running FC 2.90 updated
19 years
usb disk installations
by Jim Cornette
I attempted to install FC3T1 on a USB drive using expert mode. It seems
that all the proper files installed on the disk. The disk is a laptop
disk contained inside a usb - ATA adapter and seems to work with the
proper modeles loaded.
Are there any plans to get the module needed to mount USB disks loaded
soon enough to be able to boot from these disks.
My grub.conf file is in the attached file.
There is a lot of interest in getting this concept to work.
Thanks,
Jim
--
The duck hunter trained his retriever to walk on water.....
"Notice anything?" the owner asked eagerly.
"Yes," said his friend, "I see that fool dog of yours can't swim."
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd2,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda1
default=0
timeout=5
splashimage=(hd2,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.7-1.478)
root (hd2,0)
kernel /vmlinuz-2.6.7-1.478 ro root=LABEL=/12 rhgb quiet
initrd /initrd-2.6.7-1.478.img
title hda
rootnoverify (hd0,0)
chainloader +1
title hdb
rootnoverify (hd1,0)
chainloader +1
19 years
