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, 4 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, 4 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, 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.
7 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, 4 months
XO: SDHCI: Card didn't power up after 1 second
by Jan Pazdziora
Hello,
I have my 4GB SanDisk with the Fedora live, I've copied the developer
key to /security/develop.sig.
Upon booting the XO, I get
Type the Esc key to interrupt automatic startup
SDHCI: Card didn't power up after 1 second
Boot device: /sd/disk:\boot\olpc.fth Arguments:
Boot device: /sd/disk:\syslinux\vmlinuz0 Arguments: root=UUID=6462-3436 riitfstype=vfat rw liveimg overlay=UUID=6462-3436 quiet rhgb persistenthome=mtd0 reset_overlay
SDHCI: Card didn't power up after 1 second
<buffer@ffb676d0>:33:
Can't open boot device
Then I do
dir sd:\boot
on the ok prompt, the first attempts returns
SDHCI: Card didn't power up after 1 second
Can't open directory
but when I rerun the dir command, I get the /boot listing (showing
OLPC.FTH there). So the XO seems to be able to talk to the SD card,
at least somehow.
When I try
boot sd:\boot\olpc.fth
I get
Boot device: /sd/disk:\boot\olpc.fth Arguments: root=UUID=6462-3436 riitfstype=vfat rw liveimg overlay=UUID=6462-3436 quiet rhgb persistenthome=mtd0 reset_overlay
SDHCI: Card didn't power up after 1 second
Can't open boot device
and when I do it again I get
Boot device: /sd/disk:\boot\olpc.fth Arguments: root=UUID=6462-3436 riitfstype=vfat rw liveimg overlay=UUID=6462-3436 quiet rhgb persistenthome=mtd0 reset_overlay
<buffer@ffb651d8>:2: Can't find word to replace
but when I do just
boot
Fedora starts to boot.
Is the
SDHCI: Card didn't power up after 1 second
message an expected thing?
--
Jan Pazdziora
Satellite Engineering, Red Hat
14 years, 5 months
Is Gnome windown manager switching broken again?
by Michal Jaegermann
Trying on a rawhide installation 'man gnome-wm', which is supplied by
gnome-session-2.24.1-3.fc10, you can read the following:
NAME
gnome-wm - Launches the user selected window manager for the
GNOME session
The catch is none what is described down this page seems to be true.
If you will look at /usr/bin/gnome-wm script then you can find in it
the following:
# NOTE: DON'T USE THIS. Please have your window manager install
# a desktop file and change the gconf key
# /desktop/gnome/session/required_components/windowmanager
That gconf key used to be /apps/gnome-session/rh/window_manager and
that worked, even if 'man gnome-wm' was telling fairy tales. With
/desktop/gnome/session/required_components/windowmanager the best
I could achieve was a session with no window manager at all. I tried
some interpretations of an "install a desktop file" remark but this
got me nowhere.
There are hacks to get another window manager running. For example,
you can put early enough in $PATH a link, named 'metacity', to a
desired window manager binaries. In case some option mapping would be
required then this link should be replaced by an appropriate shell
script but you get the drift. So you can have any windown manager
you want as long as it is _called_ "metacity".
Is this un-documented somewhere and I missed it or this is a straight
bugzilla material? A Google search brought me only numerous tales of
woe from people attempting switch window managers for Gnome and
miserably failing.
Michal
p.s. For "again" part check https://bugzilla.redhat.com/show_bug.cgi?id=449048
14 years, 6 months
XO: Who ate my rpms
by Bryan Kearney
Ok... this is probably a dumb question. I booted up snap3. I opened a
terminal, su -, and then installed ekiga. I selected shutdown from the
menu, and it seemed to hang (not fully shutting down).
I reboot, log in, and there is no ekiga.
so.. who ate my rpms?
-- bk
14 years, 6 months
f10 beta sendmail boot delay
by cornel panceac
after installing f10beta (x86_64) from current boot.iso, the boot has a
significant delay waiting for sendmail and sm-client to fail. the problem is
not present after installing from live cd. of course, disabling the sendmail
service skips the problem for now.
--
Linux counter #213090
14 years, 6 months
