Fedora Core 3

[Void Main]

insomnia, yes I did do that. & void, no the module was not loaded until I did /.sbin/modprobe nvidia. I 'm at work right now, but I have some documentation at home that specificall warned against the module not loading. I will respond in greater detail later today.

The module not loading automatically is a common problem which we have already addressed. By your quote above it sounds like the module loaded with no errors after you did an "/sbin/modprobe nvidia". If this is true (verify with an "lsmod") then did everything work at that time when you did a startx?

Yes void, it did load, but I still get the 'grey screen of death".

Hmm, then at this point I think I would be looking to that Appendix H in the README that I quoted a few posts back, and if that doesn't bear fruit I would wander over to the nVidia forums and start probing. I would be interested in hearing about that other documentation is that you mentioned too.

[lovswr]

Ok, I did what sombody else on the nvnews forums did. I got a 5200 Well it seems to work except that the max resolution is 800X600. I know that this KDS monitor can do 1600X1200 (& the TNT2 that I took out was set to 1280X1024). I can't seem to find where in KDE 3 that I should go to set the video card settings. The driver that Kudzu picked is Generic GeoForce.

Found it I guess I'll get the hang of this *nix stuff yet!

p.s Is it ok to mix repos from freshrpms & fedora.repo. As in fedora.repo is not the same as fedora.us (or is it)?

[Void Main]

I don't know about KDE but on the GNOME side there is a "System Settings" menu with a "Display" icon. If you do not have this you can run the program directly by pressing ALT+F2 and typing "system-config-display". The only problem with this is it will probably reset your Driver variable to "nv" so after setting your resolution go back in and check your config (/etc/X11/xorg.conf). You should probably make a backup copy of it before making the change.

You might have to make some manual changes. The resolution lines are toward the bottom in the "Screen" section under "Modes". Your old config definitely starts with 1280x1024 so if that hasn't changed then we might have to look over your /var/log/Xorg.0.log again (you could rerun that script I gave you).

[lovswr]

I don't know about KDE but on the GNOME side there is a "System Settings" menu with a "Display" icon. If you do not have this you can run the program directly by pressing ALT+F2 and typing "system-config-display". The only problem with this is it will probably reset your Driver variable to "nv" so after setting your resolution go back in and check your config (/etc/X11/xorg.conf). You should probably make a backup copy of it before making the change.

You might have to make some manual changes. The resolution lines are toward the bottom in the "Screen" section under "Modes". Your old config definitely starts with 1280x1024 so if that hasn't changed then we might have to look over your /var/log/Xorg.0.log again (you could rerun that script I gave you).

You were correct. It put Load "dri" back in.

[Void Main]

Yes but what about the answer to the important question, do you have your desired resolution?

[lovswr]

Yes but what about the answer to the important question, do you have your desired resolution?

Yes, back at 1280X1024 now. Also for some reason now, xmms will only run as root. What should I chown /usr/bin/xmms so that user /home/lovswr can run that? And finally (I hope) can I mix fedoro repos with freshrpms & dag's repositories?

[Void Main]

Also for some reason now, xmms will only run as root. What should I chown /usr/bin/xmms so that user /home/lovswr can run that?

No, the permissions shoud be fine on the executable, we should try and figure out what is wrong. My guess is it's the permissions on your sound device files. Normally when you log on they should get chown'ed to the user who is logging on. Historically this is defined in your /etc/security/console.perm file (see the sections labeled "sound").

There is also now a /etc/udev/permissions.d/50-udev.permissions which has these:

Code: Select all

# audio devices
dsp*:root:root:0660
audio*:root:root:0660
midi*:root:root:0660
mixer*:root:root:0660
sequencer*:root:root:0660
sound/*:root:root:0660
snd/*:root:root:0660
beep:root:root:0660
admm*:root:root:0660
adsp*:root:root:0660
aload*:root:root:0660
amidi*:root:root:0660
dmfm*:root:root:0660
dmmidi*:root:root:0660
sndstat:root:root:0660


You could try changing all those lines from 0660 to 0666. You can also manually change permissions on the above names directly for the current session. e.g.:

# chmod 666 /dev/dsp*
# chmod 666 /dev/audio*
# chmod 666 /dev/mixer*
etc...

And finally (I hope) can I mix fedoro repos with freshrpms & dag's repositories?

If you are talking about fedora.us and the Dag repositories then no, you can't. I'm not quite sure why you would want to, maybe you can enlighten me? The Dag repos seem to have everything fedora.us has plus a lot more. For more info on the repo mixing:

http://dag.wieers.com/home-made/apt/

Truths and lies about mixing repositories
For almost 2 years now the fedora.us project has been spreading FUD about mixing repositories. I finally decided to bounce the ball back. Shame on them.

http://dag.wieers.com/home-made/apt/FAQ.php#D

This has been discussed in many threads here.

[lovswr]

My xmms problem is fixed. Yes I know that fedora.us can not be mixed. in my /etc/fedora.repos.d the files are just fedora. For example:


name=Fedora Core $releasever - $basearch - Base
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever
enabled=1
gpgcheck=1


Is that really fedora.us or something else that can be mixed with freshrpms & dag?

[Void Main]

My xmms problem is fixed. Yes I know that fedora.us can not be mixed. in my /etc/fedora.repos.d the files are just fedora. For example:


name=Fedora Core $releasever - $basearch - Base
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever
enabled=1
gpgcheck=1


Is that really fedora.us or something else that can be mixed with freshrpms & dag?

I don't have a "/etc/fedora.repos.d" directory and I don't know what pacakge that is associated with. To see what package it belongs to do this:

$ rpm -qif /etc/fedora.repos.d

Copy/paste the output of the above command. If it is "apt" from somewhere else you would want to remove it and install the apt package from Dag's web site. It appears that the only URLs you have there are for the base OS which you will also get via Dag's apt so you aren't losing anything, just gaining a lot.

[lovswr]

Whoops..it is really /etc/yum.fedora.repos.d As I already have freshrpms & dag set up, I will just stick with those.



sudo rpm -qif /etc/yum.repos.d
Name : fedora-release Relocations: (not relocatable)
Version : 3 Vendor: Red Hat, Inc.
Release : 8 Build Date: Mon 01 Nov 2004 01:56:15 PM EST
Install Date: Thu 11 Nov 2004 10:23:04 PM EST Build Host: tweety.build.redhat.com
Group : System Environment/Base Source RPM: fedora-release-3-8.src.rpm
Size : 274954 License: GFDL
Signature : DSA/SHA1, Mon 01 Nov 2004 02:08:17 PM EST, Key ID b44269d04f2a6fd2
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Summary : Fedora Core release file
Description :
Fedora Core release file
Name : yum Relocations: (not relocatable)
Version : 2.1.11 Vendor: Red Hat, Inc.
Release : 3 Build Date: Sun 31 Oct 2004 12:46:59 AM EDT
Install Date: Sun 14 Nov 2004 11:34:26 PM EST Build Host: tweety.build.redhat.com
Group : System Environment/Base Source RPM: yum-2.1.11-3.src.rpm
Size : 653762 License: GPL
Signature : DSA/SHA1, Mon 01 Nov 2004 02:08:11 PM EST, Key ID b44269d04f2a6fd2
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL : http://linux.duke.edu/yum/
Summary : RPM installer/updater
Description :
Yum is a utility that can check for and automatically download and
install updated RPM packages. Dependencies are obtained and downloaded
automatically prompting the user as necessary.
[lovswr@matrix1 yum.repos.d]$

[Void Main]

Yeah, if you are using Dag's apt then your lists should be in the /etc/apt/sources.list.d directory.

[lovswr]

I now have the following installed for yum. Downloading tuxkart now!

Setting up Repo: dag
repomd.xml 100% |=========================| 951 B 00:00
Setting up Repo: newrpms.sunsite.dk
repomd.xml 100% |=========================| 1.1 kB 00:00
Setting up Repo: jpackage16-fc3
repomd.xml 100% |=========================| 903 B 00:00
Setting up Repo: freshrpms
repomd.xml 100% |=========================| 843 B 00:00

[Void Main]

I refuse to use any tool named "yum", "yuk", "eww", etc.. :) I can't imagine why you would want to use it anyway when you have apt.

[Calum]

i would use it if it was called "guk" but i agree, it's pretty pointless having two totally different and incompatible systems for this purpose, they have this problem with slack apps too, unless swaret has finally gone the way of the dodo. (and rightfully so, since slapt-get is a lot better)

[Void Main]

Well, actually they (apt & yum) aren't totally incompatible. Most repos are now designed to work with either tool. You can use either tool to install/remove software and the other will know what software has been changed (because it's still the RPM database at the heart). I just don't understand what the point of using yum is when apt is so much better, not to mention an awesome graphical tool called synaptic that can be used with apt, if you are in to that sort of thing.

There are several advantages to using apt, the biggest is that many distros use apt, especially all the Debian based distros but Red Hat and SuSE also have large apt repos. It's a very flexible tool with a lot of development behind it. If you can use apt on one distro you can use it on any distro. I don't really see the point in yum at all and question why they didn't just go with apt as the default Fedora tool. Maybe someone can enlighten me? But that's one nice thing about Linux I guess, choices.