nvidia
by Karl Larsen
You might have a nvidia video card on your motherboard. There are
two choices here. Try to use the nvidia or turn it off and plug in your
old known video card. Today I wish I had done the latter because using
nvidia with f7 is a pain.
I really do not see a new Linux user ever getting his/her computer
working with nvidia. You need to go to the nvidia web page and get a
tarball and install it, not a new person's thing, or you can get 4 rpm
files and learn to use --nodeps at the proper time.
Hoping that the updates would by now have some nvidia help, after
getting 236 updates last night on my f7-64 bit system it did not fix the
problem. I used the 4 rpm files from www.atrpms.net which worked but
maybe not well. I heard from Ric Moore that the tarball is the way to
go. I will try that on f8.
A bug I keep forgetting to file is the following. A really bad
problem with nvidia is the missing pointer when X windows boots up. You
can do nothing! This is fixed by edit of the /etc/X11/xrog.conf file
adding you want to use a software pointer.
But this will not work if grub.conf has a kernel directive to use
rhxxx which hides the boot up output. While that standard kernel
directive exists you can not get a pointer period.
This bug makes f7 and I expect f8 useless to a new user with nvidia.
--
Karl F. Larsen, AKA K5DI
Linux User
#450462 http://counter.li.org.
16 years, 7 months
dd command to clear start of harddrive
by Nigel Henry
This is not directly Fedora related.
I connect to the Internet through my Smoothwall, and a serial modem. Recently
the machine that the Smoothwall is running on has been playing up. Harddrive
spinning up and down. I have another older machine (1.33GHz, 64MB RAM, and
6GB harddrive) which had Win 2000 pro on it, and was trying to install a
backup Smoothwall on it. The Smoothwall installs ok, and lilo is installed,
but when I reboot the BIOS does the memory check, and all I get next is half
a screenfull of "40's" printed out. they remain for a few seconds, then I
just get a prompt that I can't do anything with.
I am wondering if something has been left behind on the harddrive from the Win
2000 install, that linux has not been able to remove.
I've seen a few times a dd command that can get rid of stuff at the start of a
drive, but stupidly have not written down the info.
Could someone kindly give the required dd command to make sure that the
harddrive is clear of all data.
The machine won't boot off cd, but using smart boot manager on a floppy, I can
get Finnix booted up on it, and work off the CLI.
Thanks for any help from the list.
Nigel.
16 years, 7 months
hostname
by tony.chamberlain@lemko.com
Someone wants to use java and get a host name from an IP address.
I know how to do it lcoally through /etc/hosts BUT the host file does not
have names for every IP address reachable.
Someone found http://www.faqs.org/rfcs/rfc953.html which looks like you are supposed to be
able to use port 101 of a machine and connect to it and echo a command and it should respond.
It also says HNAME should give the host name so I tried (from 192.168.5.191)
echo HNAME | nc -e cat 192.168.5.15 101
which I would guess should return the host name for machine 192.168.5.15, but I got
no response and a return code of 1. There is probably something I am overlooking.
Anyone know how to query this port? (both machines are CentOS 4.5)
16 years, 7 months
Re: can't get Xnest to work against Fedora 7
by Hugh Caley
> *
>
> ______________________________________________________________________
> Frank Cox wrote:
>
> I was making a custom gdm theme a month or two back and couldn't get xnest to
> work for me then either. I eventually gave up and just installed my theme and
> logged out to see how it worked. Which was a lot more inconvenient than it
> needed to be but at least I got the job done.
>
> xnest used to work for that purpose -- the last time I made a gdm theme was in
> the FC6 or FC6 days, I think, and it worked fine then.
>
>
> For _that_, just enable more than one X. On typical systems, it will
> appear at VT8, and on.
I can get the Xnest login to succeed if I turn "Accessibility" off in
gdmsetup.
I've filed a bugzilla bug about this.
Hugh
--
Hugh Caley, Linux Administrator
Aldon Computer Group
6001 Shellmound St. Suite 600
Emeryville, CA 94608
(510) 285-8542 | hughc(a)aldon.com
16 years, 7 months
PCI: BIOS BUG #81[00000011] found
by Dan Barnes
Has anyone come across this problem when
booting Fedora 7? If so how did you fix it?
PCI: BIOS BUG #81[00000011] found
This is with kernel version "2.6.21-1.3194.fc7".
Thanks
Dan Barnes
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
16 years, 7 months
Problem with yum
by Timothy Murphy
I find yum a marvelous resource, so the following should not be taken
as even a mild criticism.
I recently tried to download gnokii-devel,
but I was told this required an older version of gnokii than I had,
as shown below.
I'm not sure where I got the "fc8" version I have -
I don't normally open any non-standard repositories,
but I might have done so in error.
I tested "yum remove gnokii" but this would have removed
dozens of packages.
I'm just wondering: what is the standard way of dealing with this
yum quandary, if indeed there is a way?
--------------------------------
[tim@elizabeth ~]$ sudo yum install gnokii-devel
...
Resolving Dependencies
...
--> Processing Dependency: gnokii = 0.6.14-3.fc7 for package: gnokii-devel
...
Error: Missing Dependency: gnokii = 0.6.14-3.fc7 is needed by package
gnokii-devel
[tim@elizabeth ~]$ grep gnokii /var/log/rpmpkgs
gnokii-0.6.17-1.fc8.i386.rpm
--------------------------------
16 years, 7 months
Opening .rar files
by Tony Crouch
Hi All,
A friend has sent me a file which I need to open which has a .rar file
format.
I was wondering if someone might be able to point me in the right
program direction to getting the file opened.
Thanks for your help.
All the best.
Cheers,
Tony Crouch
16 years, 7 months
speedy recompiles
by Michael D. Berger
On FC7, in compiling my libraries, I see that
re-compiles of C++ code goes much faster than
than the original compiles. I delete all *.o
between the compiles. How does that happen?
Thanks,
Mike.
16 years, 7 months
how does "du" deal with hard links?
by Robert P. J. Day
i'm wondering if i should be surprised about something i just
noticed WRT how "du" tries to avoid [re]counting files that it's
already seen via hard links.
given the following directories that are git repositories that i'm
playing with just to see the space savings i might get:
$ ls -ld git*
drwxrwxr-x 15 rpjday rpjday 12288 2007-11-01 07:53 git
drwxrwxr-x 15 rpjday rpjday 12288 2007-11-01 08:23 git.local
drwxrwxr-x 15 rpjday rpjday 12288 2007-11-01 08:23 git.nolinks
$
the first is the master repo, the second (git.local) was cloned
allowing hard links to save space, while the third (git.nolinks) was
explicitly cloned without allowing hard links (using --no-hardlinks).
if i check their disk usage individually, i get:
$ for r in git* ; do
> du -s $r
> done
26340 git
26292 git.local
26292 git.nolinks
$
but if i use wildcards, notice the difference:
$ du -s git*
26340 git
9672 git.local
26292 git.nolinks
$
as if du already knows which files it's seen under "git" and won't
recount them under "git.local" based on hard links. if that's the
case, then it won't be surprising to see the numbers on the first two
reversed if i explicitly change the order of the arguments:
$ du -s git.local git git.nolinks
26292 git.local
9720 git
26292 git.nolinks
$
i can see what's happening, i just didn't realize that that's how
"du" operated. is that deliberate?
rday
p.s. i can see the rationale here -- if du *didn't* do something like
that, then you might get results that were wildly out of sync with
reality. like i said, i just never noticed that before.
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
16 years, 7 months