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.
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
> 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
> > 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.
Installing the OO.org 2.4 packages on F9 beta, I get this message when
Gtk-Message: Failed to load module "gnomebreakpad":
/opt/OOH680_m12/program/libstdc++.so.6: version `GLIBCXX_3.4.9' not
found (required by /usr/lib/bug-buddy/libbreakpad.so.0)
OOo then starts and seems to run ok, but it will not run from a desktop
launcher using that same command, I presume because bug-buddy can't be
I don't know what the Fedora policy is here: does it matter at this
point whether a third-party package isn't starting cleanly? Nor do I
understand the message well enough to decide who to report it to.
It seems that OOo uses it's own libstdc++ which is not compatible with
gnomebreakpad, but I've not found a way to have gnomebreakpad look
elsewhere for that library.
Any suggestions if/where to file a report, and/or how to workaround the
Fedora 9 will have a lot of new and exciting things. Naturally, we want
those things to be stable and well-polished for the final release.
With that in mind, here's a list of things that deserve especially close
This *replaces* pup and pirut, by default, on all new installs. If
you're following rawhide, *please* disable or remove pup and pirut and
test this. It's very important that you file bugs about *any* problems
Use the "gnome-packagekit" component in bugzilla for bugs about
confusing (or missing) UI pieces, and "PackageKit" for bugs about
backend errors, missing capabilities, or other (non-UI) problems.
At long last, NetworkManager is installed and enabled by default for all
new installs. It is *supposed* to play nice with the system
configuration set up by Anaconda and the old system-config-network tool.
I'd recommend that all testers install and enable NetworkManager if
possible. File bugs about network configuration problems (not honoring
static IP configurations, for instance) against "NetworkManager".
Upstart has replaced sysvinit. Everything should be working as it did in
F8, but if you have problems with serial consoles, boot-time arguments,
changing runlevels (using telinit or similar), or the like, make sure
bugs get filed.
The runlevels are now controlled by the Upstart event scripts
in /etc/event.d. If you have problems changing runlevels file bugs
against "event-compat-sysv". Other upstart bugs should probably be filed
Xorg is now using the new "evdev" generic input driver. This driver is
intended to automatically handle all input devices recognized by the
kernel - keyboards, mice, joysticks, whatever.
Unfortunately its handling of keyboards is still a bit messy and
probably won't be ready for F9. Therefore, ajax modified it to let the
old, working driver claim your keyboard.
So as of F9Beta, keyboards *should* work just like they did in F8. If
you have *new* problems with your keyboard layout (and you're not having
lingering evdev problems from older rawhide), check Xorg.0.log to see
if evdev has claimed your keyboard. If so, file a bug against
"xorg-x11-drv-evdev". Otherwise, use "xorg-x11-drv-keyboard".
If there's any other things that people think need closer attention..
now would be a good time to mention them.
It seems that starting at 23/04 with
xorg-x11-server-188.8.131.521-23.20080415.fc9 I'm not able to use EXA accel
anymore and so no xvideo with my Sapphire X1900 card.
01:00.0 VGA compatible controller: ATI Technologies Inc R580 [Radeon X1900
Leaving AccelMethod EXA in xorg.conf I get:
1) rhgb freeze at mid startup point (with both 2.6.25-1 and 2.6.25-8
kernels). I need to switch off keeping power button pressed
2) if I boot without rhgb and without quiet I get black screen with cursor
circle when starting gdm part and only able to move mouse but no console
I can press power button and get clean shutdown (without screen changes)
3) if I boot as in 2) and specifying init level 3 I can get a console
If I log as normal user and do a startx I get gnome but after few seconds
screen freezes. I need to switch off keeping power button pressed
4) if I comment out the option about EXA in xorg.conf it seems ok (just in
Is there a particular option for EXA in this latest updates?
BTW: also fglrx doesn't work (tried with -1 kernel, not available for -8
yet). I get a
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
dlopen: /usr/lib/xorg/modules/drivers//fglrx_drv.so: undefined symbol:
(EE) Failed to load /usr/lib/xorg/modules/drivers//fglrx_drv.so
Not tried radeonhd in these days (I have installed
xorg-x11-drv-radeonhd-1.1.0-0.7.20080404git.fc9.i386) because it doesn't
provide xvideo yet...
My system is an updated rawhide x86. Relevant packages now are:
Any help? See below my current xorg.conf
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
Option "AIGLX" "on"
Option "XkbModel" "pc105"
Option "XkbLayout" "us+inet"
# Option "AccelMethod" "EXA"
Viewport 0 0
Option "Composite" "Enable"
Option "DAMAGE" "Enable"
Option "RENDER" "Enable"
Option "RandR" "on"
(extmod, dri, freetype, glx, dbe are not specified as they are loaded
automatically, as in log file:
(II) "extmod" will be loaded by default.
(II) "dbe" will be loaded by default.
(II) "glx" will be loaded by default.
(II) "freetype" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
My F9 system intermittently refuses to shut down with:
nm-system-settings: Could not get the system bus. Make sure the message
bus daemon is running! Message: Failed to connect to socket
/var/run/dbus/system_bus_socket: Connection refused
Can anyone suggest how to fix this or is it a bug?