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.
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:
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
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 ();
| 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?
I'm trying to install FC2 Test 1 on a Digital PC 5400 (an old Pentium
Pro box). Curiously, Knoppix boots on it fine, but it has failed to boot
up FC1, Mandrake 9.2, and now FC2 from CD, saying
isolinux: Found something at drive=9F
isolinux: Looks like it might be right, continuing...
isolinux: image checksum error, sorry...
Boot failed: press a key to retry...
No problem, I say; I'll make a bootable floppy. I double check the
README files, and then head to the images directory...but there are no
.img files to be found there.
What should I do?
I've been using rawhide since a little before FC2-test1. And I must say
that I am more than a bit taken aback by the new nautilus default mode.
I'm a KDE fan from before their 1.0 release, and it took a long while
for Gnome to win me over. But it did eventually, and what won me over
was its adherence to the HIG, and the beautiful simplicity of Bluecurve
Gnome. i.e. I'm not one of those people who bemoaned the replacement of
sawfish with metacity, and I like the "less is more" philosophy of the
current Gnome series. Gnome has done a lot of things right.
So I can't help but feel that I am missing the boat when it comes to
spatial mode nautilus. On the plus side, I can see that it certainly
has a cleaner look. And that's it.
On the minus side, it wants to open a window for every mouse click,
navigation is cumbersome, finding what options you do have is a hunt and
peck afair. I realize that if you know to "right click-> browse folder"
or "nautilus -browser", you can get the old behavior back, but what I
don't understand is why spatial is the default. How does spatial mode
as the default benefit the new user? To me, this seems to be a case of
cutting out too much of the interface.
I realize that this may really be a question for another list, but as
the Fedora project could decide to change the default, it seems an
appropriate thing to ask in this forum. I almost feel that I should be
posting this to bugzilla instead of here.
What are the advantages of spatial that I am not seeing?
> Curious why more people haven't reported this. Is it card
> related? Network related? Is IPV6 on for everyone, but for
> some reason it's not causing everyone a problem?
Personally, I would like to see an option in the setup for whether you want
to enable IPV6 or not, with the default being Not. At least, until IPV6
becomes a reality for mainstream users.
I noticed that we are both on comcast. I didn't play around with nslookup
or dig, but perhaps comcast' dns servers are actually returning IPV6
addresses for some hosts. If we're getting v6 addresses, but can't connect
to them because we haven't got a tunnel set up, it would explain the delays,
as it attempts a v6 connection, fails, then falls back to v4.
after an update from the development tree (something around 80 packages)
several minutes ago, the german "umlaute" are broken inside KDE.
That applys to all saved data, like E-Mails, program-interfaces, menu-buttons,
but not to the manpages!
The Code in my /etc/sysconfig/i18n is set to LANG="de_DE.UTF-8", everything
worked fine before the update of the system from FC2T2 to Development.
At this moment I see that I am not possible to insert the "umlaute" into the
mail written inside contact - but in shell it works, in Konqueror and kwrite
c&p from konqueror to kontact does not work...
The knewsticker shows the lines in the right way, if I open the right-klick
menu to see all the links, the links have the wrong codes (see below).
The short help for the kicker icons (if you move your mouse over them, you get
a smal yellow box with a little more information) shows the correct codes,
there I can read the "umlaute".
Maybe a KDE-special Problem?
Here is the replacement table:
ae is ä
AE is Ä
oe is ö
OE is Ö
ue is ü
UE is ü
ss is ß
euro-symbol is €
Maybe that helpes? Do other people have these problems?
Seems like KDE was copiled with ISO-8859-1, an not with UTF-8....
So now I am up and running with xorg, but I have a few questions. I am using
the Radeon Mobility 9600 (M10) and want to actually use the card, and not
just the VESA driver.
So, what do I use to configure xorg? Do I use systen-display-config as
usual? I say that since it seems odd that the configuration file used to
drive xorg would still be XF86Config.
Where do I find out what drivers are supported in the release> I am looking
and looking, but cannot find docs on the sparse xorg site.