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
4 months, 1 week
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.
???
4 months, 1 week
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
6 years, 6 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.
6 years, 6 months
Error: No Package Matching glibc.i686
by Michael Schwendt
Is this a new feature or a bug? Shouldn't this update also glibc?
$ sudo yum update glibc-common
Loading "installonlyn" plugin
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package glibc-common.i386 0:2.5.90-21 set to be updated
Checking deps for glibc-common.i386 0-2.5.90-21 - u
Checking deps for glibc-common.i386 0-2.5.90-20 - None
--> Processing Dependency: glibc-common = 2.5.90-20 for package: glibc
Error: No Package Matching glibc.i686
On the contrary, yum update glibc and glibc.i686 work just fine:
$ sudo yum update glibc.i686
Loading "installonlyn" plugin
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package glibc.i686 0:2.5.90-21 set to be updated
Checking deps for glibc.i686 0-2.5.90-21 - u
Checking deps for glibc.i686 0-2.5.90-20 - None
--> Processing Dependency: glibc-common = 2.5.90-21 for package: glibc
--> Processing Dependency: glibc = 2.5.90-20 for package: glibc-headers
--> Processing Dependency: glibc = 2.5.90-20 for package: glibc-devel
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package glibc-common.i386 0:2.5.90-21 set to be updated
Checking deps for glibc-common.i386 0-2.5.90-21 - u
---> Package glibc-devel.i386 0:2.5.90-21 set to be updated
Checking deps for glibc-devel.i386 0-2.5.90-21 - u
Checking deps for glibc-common.i386 0-2.5.90-20 - None
---> Package glibc-headers.i386 0:2.5.90-21 set to be updated
Checking deps for glibc-headers.i386 0-2.5.90-21 - u
Checking deps for glibc-headers.i386 0-2.5.90-20 - None
Checking deps for glibc-devel.i386 0-2.5.90-20 - None
Dependencies Resolved
=============================================================================
Package Arch Version Repository Size
=============================================================================
Updating:
glibc i686 2.5.90-21 development 5.3 M
Updating for dependencies:
glibc-common i386 2.5.90-21 development 17 M
glibc-devel i386 2.5.90-21 development 2.0 M
glibc-headers i386 2.5.90-21 development 609 k
Transaction Summary
=============================================================================
Install 0 Package(s)
Update 4 Package(s)
Remove 0 Package(s)
Total download size: 25 M
Is this ok [y/N]: n
Exiting on user Command
Complete!
14 years, 8 months
Fedora 7 Test Update: xorg-x11-drv-i810-2.1.0-1.fc7
by updates＠fedoraproject.org
--------------------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2007-0925
2007-07-06 11:11:08.527615
--------------------------------------------------------------------------------
Name : xorg-x11-drv-i810
Product : Fedora 7
Version : 2.1.0
Release : 1.fc7
Summary : Xorg X11 i810 video driver(s)
Description :
X.Org X11 i810 video driver.
--------------------------------------------------------------------------------
ChangeLog:
* Tue Jul 3 2007 Adam Jackson <ajax(a)redhat.com> 2.1.0-1
- xf86-video-intel 2.1.0.
* Mon Jun 18 2007 Adam Jackson <ajax(a)redhat.com> 2.0.0-5
- Update Requires and BuildRequires.
* Wed Jun 6 2007 Adam Jackson <ajax(a)redhat.com> 2.0.0-4
- Update to git master. Many Xv and DVO fixes. Adds support for 945GME,
965GME, G33, Q33, and Q35 chips.
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #245965
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245965
--------------------------------------------------------------------------------
Updated packages:
a8e40a2cf69d53c4290a5e465468d60342b1ffa8 xorg-x11-drv-i810-debuginfo-2.1.0-1.fc7.i386.rpm
5f4778f4cfe378172770e5a76bd6d2c4b0a9e258 xorg-x11-drv-i810-2.1.0-1.fc7.i386.rpm
85b0079662d0de5dd834061e7392a734380772ed xorg-x11-drv-i810-devel-2.1.0-1.fc7.i386.rpm
1912a65e024efb76d62fba1c3309d27f38e03ee6 xorg-x11-drv-i810-2.1.0-1.fc7.x86_64.rpm
a5fd39173caa57700067662cd11ba2851e6ae194 xorg-x11-drv-i810-devel-2.1.0-1.fc7.x86_64.rpm
18300084e8acbd79fbbb92d13c4aaf5f7c94741b xorg-x11-drv-i810-debuginfo-2.1.0-1.fc7.x86_64.rpm
3372cc73e5cbe852c4bb591f3c92d532d0089084 xorg-x11-drv-i810-2.1.0-1.fc7.src.rpm
This update can be installed with the 'yum' update program. Use 'yum update
package-name' at the command line. For more information, refer to 'Managing
Software with yum,' available at http://docs.fedoraproject.org/yum/.
--------------------------------------------------------------------------------
14 years, 8 months
gnomebaker problems
by Rick Marshall
After upgrading from FC6 to F7 gnomebaker stopped working.
After poking around again I found that the reason is that gnomebaker is
trying to open /dev/sr0 as the scsi recording device, but in my F7 that
doesn't exist.
However these do exist:
[root@rjm src]# ls -l /dev/*sr0
lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdrom-sr0 -> scd0
lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdrw-sr0 -> scd0
lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdwriter-sr0 -> scd0
lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvdrw-sr0 -> scd0
lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvd-sr0 -> scd0
lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvdwriter-sr0 -> scd0
So I added the line:
ln -s /dev/scd0 /dev/sr0
to /etc/rc.d/rc5.d/S99local and gnomebaker works.
Why does it get it wrong? Well...
[root@rjm src]# cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: sr0
drive speed: 24
drive # of slots: 1
Can close tray: 1
Can open tray: 1
Can lock tray: 1
Can change speed: 1
Can select disk: 0
Can read multisession: 1
Can read MCN: 1
Reports media changed: 1
Can play audio: 1
Can write CD-R: 1
Can write CD-RW: 1
Can read DVD: 1
Can write DVD-R: 1
Can write DVD-RAM: 1
Can read MRW: 1
Can write MRW: 1
Can write RAM: 1
so I guess gnomebaker assumes there is a node called /dev/sr0, but
obviously F7 is trying to be friendly by creating specific nodes based
on the capabilities of the device and then I assume an application can
open the appropriate device.
Should gnomebaker be changed? or would it be friendly for F7 to also
create the generic node /dev/sr0 at startup as well as the capability
specific nodes?
Thanks
Rick
14 years, 9 months
Kernel errors in logs with latest F7 kernel
by Gilbert Sebenste
Hey gang,
These aren't fatal, so far as I can tell. But they are new to my machine
after I installed F7 on all of them. Machine is a Pentium 4, 3GHZ
processor with 1.5 GB of RAM, SCSI hard drive with two 75 GB hard drives
(RAID), with 46% space used. Anyone else seeing this? Using:
Linux weather 2.6.22.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686
i686 i386 GNU/Linux
WARNING: Kernel Errors Present
Intel ICH: probe of 0000:00:1f.5 failed with error -12 ...: 2 Time(s)
cannot find the slot for index 1 (range 0-1), error: -16 ...: 2
Time(s)
end_request: I/O error, dev fd0, sector ...: 2 Time(s)
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
*******************************************************************************
14 years, 9 months
