Re: "It's time for you to leave."

2011-12-31 Thread Gerhard Magnus 

On 12/31/2011 11:13 AM, Joe Zeff wrote:

On 12/31/2011 09:06 AM, Jim wrote:

For those of you that are garus , if you do not have the patience with
dealing with NEWBIEs to Linux. just ignore the post and let someone who
does.


I'm not claiming to be a guru, but I don't consider myself a newbie any
more. I've been using Linux, off and on, since about '98, and as my sole
OS since FC6. I won't go into how long I've been using computers, but
when I started, I had to use an IBM 029 keypunch.


...talk about "The Long Goodbye"! (also a cool book by Raymond Chandler 
and a great 1973 movie by Robert Altman, both far more interesting than 
this thread...)

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

NFS issues -- fixed but not solved

2011-11-08 Thread Gerhard Magnus 
Restating the problem:

On the server, running FC15 (192.168.1.14):
(1) My /etc/exports file looks like this:
/home/magnusg/Music  192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
(2) Using the system-config-nfs "General Options tab" I have "Allow
connections from port 1024 and higher" checked.
(3) I have services nfs and nfslock running on levels 3,4,5.
(4) In /etc/sysconfig/nfs I've set these ports:
RQUOTAD_PORT=4000
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
STATD_PORT=4003
(5) In the firewall I have these ports open:
NFSV4 2049 (tcp)
4000-4003 (tcp and udp)
111 (tcp and udp)

on the client, running FC13 (192.168.1.13):
(1) I added this to /etc/fstab:
192.168.1.14:/home/magnusg/Music /home/magnusg/Music nfs
rw,auto,hard,intr,bg 0 0
(no change by adding option "nfsvers=3" which has made this work in the
past.)
(2) Services netfs, nfslock and rpcbind are running on levels 3,4,5.

...but /home/magnusg/Music won't mount on the client, either during the
boot or when I use the mount command later: mount.nfs: access denied by
server while mounting PuteF:/home/magnusg/Music



I fixed the problem by installing FC14 on the server. It's amazing the
linux problems that simply disappear by avoiding all use of the disaster
that is FC15!

I can understand the rationale for making users go through a big song
and dance in order to play mp3 files, but stuff like scp and nfs should
be as simple to set up on a LAN as they are easy to use.



-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

corrupted MAC error -- fixed but not solved

2011-11-07 Thread Gerhard Magnus 
Here's the problem -- fixed, but not solved:

A small LAN with three boxes and hardwired ethernet connections through
a router.
PuteF: server, running FC15 (x86) and LXDE  
PuteB: running FC13 (386) and gnome
PuteD: running FC15 (386) and KDE

I can transfer files between PuteB and PuteD using scp without any
problems. Regardless of which machine the scp is initiated on, all file
transfers between PuteF and PuteB, and between PuteF and PuteD fail with
the error message "Corrupted MAC on input. Disconnecting: Packet
corrupt. lost connection." The time this takes to happen varies within a
few minutes.

Things tried without success:
(1) installing a new ethernet card on PuteF and connecting it to the
router with a new cable
(2) connecting PuteF and PuteB using every possible combination of ports
on the router
(3) running a new long ethernet cable directly from PuteB to PuteF
(4) reinstalling FC15 (x86) on PuteF
(5) installing the 386 version of FC15 on PuteF

What worked:
Installing FC14 (x86) on PuteF -- which, obviously, is only a short-term
fix.

Is this a bug in FC15? Or a feature of FC15 that can't deal with my
older hardware? Assuming the latter, how old is "too old" hardware for
FC15? I bought the box (Intel dual core with 4GB memory) in 2007 from
one of those priceless dealers who builds them and is then a victim of
his success. There haven't been any problems with this box (despite a
lot of use) until a hard drive crash about a month ago, when I took it
into the shop for a full checkup. (Presumably this would have included
memory diagnostics.) The hard drives are also new. I started having
these problems as soon as I installed FC15 (x86). 

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

corrupted MAC error using scp

2011-11-02 Thread Gerhard Magnus 
I'm at my wits end with this problem:

A small LAN with three boxes and hardwired ethernet connections through
a router.
PuteF: server, running FC15 (x86) and LXDE  
PuteB: running FC13 (386) and gnome
PuteD: running FC15 (386) and KDE

I can transfer files between PuteB and PuteD using scp without any
problems. Regardless of which machine the scp is initiated on, all file
transfers between PuteF and PuteB, and between PuteF and PuteD fail with
the error message "Corrupted MAC on input. Disconnecting: Packet
corrupt. lost connection." The time this takes to happen varies within a
few minutes.

Based my not getting this error for file transfers between PuteB and
PuteD (running FC13 and FC15, respectively) I assumed (1) the problem is
with PuteF or its connectivity, and (2) the problem does not involve
different versions of Fedora. Based on what I read on the Web about this
error I assumed the hardware was at fault. So I put in a new ethernet
card on PuteF and connected it to the router with a new cable. But I
still get the "Corrupted MAC" error.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

more attempts to resolve NSF issues

2011-10-23 Thread Gerhard Magnus 
I can ping (and ssh) the server from the client.
When I restart nfs and nfslock on the server I get this in the
server /var/log/messages:
PuteF kernel: [25572.902466] NFSD: Using /var/lib/nfs/v4recovery as the
NFSv4 state recovery directory
PuteF kernel: [25572.902504] NFSD: starting 90-second grace period
PuteF rpc.mountd[8699]: Version 1.2.4 starting
But on the client, mount /home/magnusg/Music returns:
mount.nfs: access denied by server while mounting
192.168.1.14:/home/magnusg/Music

a couple more things
(1) on the client, showmount -e 192.168.1.14 (the server)
Export list for 192.168.1.14: (shows nothing)
But on the server, my /etc/exports file contains:
/home/magnusg/Music 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
(2) also on the client, trying to mount with mount.nfs:
mount.nfs PuteF:/home/magnusg/Music /home/magnusg/Music -v
mount.nfs: timeout set for Sun Oct 23 17:25:32 2011
mount.nfs: trying text-based options
'vers=4,addr=192.168.1.14,clientaddr=192.168.1.13'
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting
PuteF:/home/magnusg/Music

OK, my only contact with people who use Linux these days is on this
list, so I have no idea what the current "lore" is. Does anybody
actually use NFS anymore? If not, is there any alternative to NFS
besides using ssh?

---

Restating the problem from yesterday:

On the server, running FC15 (192.168.1.14):
(1) My /etc/exports file looks like this:
/home/magnusg/Music  192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
(2) Using the system-config-nfs "General Options tab" I have "Allow
connections from port 1024 and higher" checked.
(3) I have services nfs and nfslock running on levels 3,4,5.
(4) In /etc/sysconfig/nfs I've set these ports:
RQUOTAD_PORT=4000
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
STATD_PORT=4003
(5) In the firewall I have these ports open:
NFSV4 2049 (tcp)
4000-4003 (tcp and udp)
111 (tcp and udp)

on the client, running FC13 (192.168.1.13):
(1) I added this to /etc/fstab:
192.168.1.14:/home/magnusg/Music /home/magnusg/Music nfs
rw,auto,hard,intr,bg 0 0
(2) Services netfs, nfslock and rpcbind are running on levels 3,4,5.

When I boot the client and get to the "Mounting NFS filesystems" section
I don't get error messages -- but I do see this:
mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music
: mount options
"hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13
/home/magnusg/Music remains unmounted


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

NFS issues

2011-10-23 Thread Gerhard Magnus 
I can ping (and ssh) the server from the client.
When I restart nfs and nfslock on the server I get this in the
server /var/log/messages:
PuteF kernel: [25572.902466] NFSD: Using /var/lib/nfs/v4recovery as the
NFSv4 state recovery directory
PuteF kernel: [25572.902504] NFSD: starting 90-second grace period
PuteF rpc.mountd[8699]: Version 1.2.4 starting
But on the client, mount /home/magnusg/Music returns:
mount.nfs: access denied by server while mounting
192.168.1.14:/home/magnusg/Music

---

Restating the problem from yesterday:

On the server, running FC15 (192.168.1.14):
(1) My /etc/exports file looks like this:
/home/magnusg/Music  192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
(2) Using the system-config-nfs "General Options tab" I have "Allow
connections from port 1024 and higher" checked.
(3) I have services nfs and nfslock running on levels 3,4,5.
(4) In /etc/sysconfig/nfs I've set these ports:
RQUOTAD_PORT=4000
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
STATD_PORT=4003
(5) In the firewall I have these ports open:
NFSV4 2049 (tcp)
4000-4003 (tcp and udp)
111 (tcp and udp)

on the client, running FC13 (192.168.1.13):
(1) I added this to /etc/fstab:
192.168.1.14:/home/magnusg/Music /home/magnusg/Music nfs
rw,auto,hard,intr,bg 0 0
(2) Services netfs, nfslock and rpcbind are running on levels 3,4,5.

When I boot the client and get to the "Mounting NFS filesystems" section
I don't get error messages -- but I do see this:
mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music
: mount options
"hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13
/home/magnusg/Music remains unmounted


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: NFS issues

2011-10-22 Thread Gerhard Magnus 
On Sun, 2011-10-23 at 05:19 +0530, Soham Chakraborty wrote:
> Yes, mount command seems fine to me. What does this command say
> 
> mount -t nfs,_netdev
> 192.168.1.14:/home/magnusg/Music /home/magnusg/Music

magnusg@PuteB Sat Oct 22 17:03:07
[1004] ~ $ su -c "mount -t nfs,_netdev
192.168.1.14:/home/magnusg/Music /home/magnusg/Music"
mount.nfs: Connection timed out


> 
> On Sun, Oct 23, 2011 at 5:12 AM, Gerhard Magnus
>  wrote:
> 
>     > On 10/23/2011 07:24 AM, Gerhard Magnus wrote:
> > > I have a small home LAN. I am running FC15 on the server.
> As I still
> > > have not made a full peace with FC15 I'm still running
> FC13 on the
> > > client. Several years and FC versions ago, someone on the
> list told me
> > > about this procedure for setting up NFS, which has been
> working fine...
> > > until now.
> 
> 
> 
> > > 
> > >
> > > On the server (192.168.1.14):
> > > My /etc/exports file looks like this:
> > > /home/magnusg/Music
> > > 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
> > > Using the system-config-nfs "General Options tab" I have
> "Allow
> > > connections from port 1024 and higher" checked.
> > > I have services nfs and nfslock running on levels 3,4,5.
> > > In /etc/sysconfig/nfs I've set these ports:
> > > RQUOTAD_PORT=4000
> > > LOCKD_TCPPORT=4001
> > > LOCKD_UDPPORT=4001
> > > MOUNTD_PORT=4002
> > > STATD_PORT=4003
> > > In the firewall I have these ports open:
> > > NFSV4 2049 (tcp)
> > > 4000-4003 (tcp and udp)
> > > 111 (tcp and udp)
> > > 
> > > on the client (192.168.1.13):
> > > I added this to /etc/fstab:
> > > 192.168.1.14:/home/magnusg/Music/home/magnusg/Music
>  nfs
> > > rw,auto,hard,intr,bg  0 0
> > > Services netfs, nfslock and rpcbind are running on levels
> 3,4,5.
> > > 
> > > When I boot the client and get to the "Mounting NFS
> filesystems" section
> > > I don't get error messages -- but I do see this:
> > > mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music
> > > : mount options
> > >
> "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13"
> > > Then I don't get a "Music" icon on my desktop, and when I
> open the
> > > folder there's nothing in it.
> 
> 
> On Sun, 2011-10-23 at 07:32 +0800, Ed Greshko wrote
> > You may be running into the same bug others have  That
> is NFS
> mounts
> > not mounting at boot time.  There is a bugzilla open for
> it
> > https://bugzilla.redhat.com/show_bug.cgi?id=692008
> >
> > Try mounting manually.  If that works, then you're
> experiencing the
> bug.
> 
> 
> Is this the right mount command?
> mount -t nfs
> 192.168.1.14:/home/magnusg/Music /home/magnusg/Music
> 
> I get this error message:
> mount.nfs: Connection timed out
> 
> 
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines:
> http://fedoraproject.org/wiki/Mailing_list_guidelines
> 
> 
> 

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: NFS issues

2011-10-22 Thread Gerhard Magnus 

> On 10/23/2011 07:24 AM, Gerhard Magnus wrote:
> > I have a small home LAN. I am running FC15 on the server. As I still
> > have not made a full peace with FC15 I'm still running FC13 on the
> > client. Several years and FC versions ago, someone on the list told me
> > about this procedure for setting up NFS, which has been working fine...
> > until now.

> > 
> >
> > On the server (192.168.1.14):
> > My /etc/exports file looks like this:
> > /home/magnusg/Music
> > 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
> > Using the system-config-nfs "General Options tab" I have "Allow
> > connections from port 1024 and higher" checked.
> > I have services nfs and nfslock running on levels 3,4,5.
> > In /etc/sysconfig/nfs I've set these ports:
> > RQUOTAD_PORT=4000
> > LOCKD_TCPPORT=4001
> > LOCKD_UDPPORT=4001
> > MOUNTD_PORT=4002
> > STATD_PORT=4003
> > In the firewall I have these ports open:
> > NFSV4 2049 (tcp)
> > 4000-4003 (tcp and udp)
> > 111 (tcp and udp)
> > 
> > on the client (192.168.1.13):
> > I added this to /etc/fstab:
> > 192.168.1.14:/home/magnusg/Music/home/magnusg/Musicnfs
> > rw,auto,hard,intr,bg  0 0
> > Services netfs, nfslock and rpcbind are running on levels 3,4,5.
> > 
> > When I boot the client and get to the "Mounting NFS filesystems" section
> > I don't get error messages -- but I do see this:
> > mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music
> > : mount options
> > "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13"
> > Then I don't get a "Music" icon on my desktop, and when I open the
> > folder there's nothing in it. 

On Sun, 2011-10-23 at 07:32 +0800, Ed Greshko wrote
> You may be running into the same bug others have  That is NFS
mounts
> not mounting at boot time.  There is a bugzilla open for it 
> https://bugzilla.redhat.com/show_bug.cgi?id=692008
> 
> Try mounting manually.  If that works, then you're experiencing the
bug.

Is this the right mount command?
mount -t nfs 192.168.1.14:/home/magnusg/Music /home/magnusg/Music

I get this error message:
mount.nfs: Connection timed out

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

NFS issues

2011-10-22 Thread Gerhard Magnus 
I have a small home LAN. I am running FC15 on the server. As I still
have not made a full peace with FC15 I'm still running FC13 on the
client. Several years and FC versions ago, someone on the list told me
about this procedure for setting up NFS, which has been working fine...
until now.



On the server (192.168.1.14):

My /etc/exports file looks like this:
/home/magnusg/Music
192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)

Using the system-config-nfs "General Options tab" I have "Allow
connections from port 1024 and higher" checked.

I have services nfs and nfslock running on levels 3,4,5.

In /etc/sysconfig/nfs I've set these ports:
RQUOTAD_PORT=4000
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
STATD_PORT=4003

In the firewall I have these ports open:
NFSV4 2049 (tcp)
4000-4003 (tcp and udp)
111 (tcp and udp)



on the client (192.168.1.13):

I added this to /etc/fstab:
192.168.1.14:/home/magnusg/Music/home/magnusg/Musicnfs
rw,auto,hard,intr,bg  0 0

Services netfs, nfslock and rpcbind are running on levels 3,4,5.



When I boot the client and get to the "Mounting NFS filesystems" section
I don't get error messages -- but I do see this:
mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music
: mount options
"hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13"

Then I don't get a "Music" icon on my desktop, and when I open the
folder there's nothing in it. 

Any advice on how to proceed would be appreciated.
Jerry





-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: running programs as root in KDE: Solved

2011-09-13 Thread Gerhard Magnus 
On Tue, 2011-09-13 at 11:39 +0530, Digvijay Patankar wrote:
> 
> 
> On Tue, Sep 13, 2011 at 5:55 AM, Gerhard Magnus
>  wrote:
> Something that used to be
> simple -- i.e. open Konsole, then as superuser,
> kwrite /etc/hosts & --
> doesn't work and instead delivers error messages that make no
> sense to
> me, let alone give me anything to work with.
> 
> Have you tried 
>  + F2 > kdesu kwrite  ?
> I think this will work for you. 

Thanks for all the help -- this was most like what this former gnome
user has been doing before. (kdesu kwrite  also works from
the terminal command line.)

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

running programs as root in KDE

2011-09-12 Thread Gerhard Magnus 
As a longtime gnome user, I've been disappointed in finding my hardware
simply can't handle gnome3 of FC15 and have switched to KDE. I've
connected to the Internet and now want to enter the names of IP
addresses of my other boxes in /etc/hosts. Something that used to be
simple -- i.e. open Konsole, then as superuser, kwrite /etc/hosts & --
doesn't work and instead delivers error messages that make no sense to
me, let alone give me anything to work with.

Clearly there must be an easier way to do this but, so far at least,
Google has not been my friend. One "howto" suggested using the "Run
command..." from the K menu and then completing the "run as different
user" section of the "Options" menu, but the "Options" menu doesn't
exist in this version of KDE.

Any suggestions would be most appreciated so I can continue with this
upgrade. I don't mind using Linux being an ongoing adventure, but this
is a bit much.

Jerry

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

first FC15 boot -- oh no!

2011-07-28 Thread Gerhard Magnus 
When I try logging on after booting up FC15 for the first time... oh no!
It's extremely irritating to get a cute message that offers no useful
information whatsoever.

My impression from cursory scanning of this list is that gnome 3 doesn't
work with a lot of hardware configurations. Is this likely the problem,
and if so is there a way I can log on to KDE, which presumably still
works? Any suggestions as to how to proceed would be appreciated.

Jerry

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

where is the gedit dictionary?

2011-01-31 Thread Gerhard Magnus 
I'm running FC13 with a gnome desktop. Does anyone know the name of the
file for the dictionary used by the gedit spell checker and where it's
stored?


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

wireless networking problem (fixed)

2010-09-05 Thread Gerhard Magnus 
Gerhard Magnus wrote:

My old DSL modem doesn't have a wireless interface. It's connected to a
router (the LAN gateway) which then has ethernet connections to my
boxes. All of these computers use static IP addresses. The DSL modem is
assigned a dynamic IP address by my ISP. 

I recently added a DIR-615 D-Link wireless router which connects to the
gateway router. I also have a netbook which I first configured with a
static IP address and the IP address of the gateway router. This worked
fine -- but, of course, I mostly use the netbook away from home, so I
reconfigured it to accept a dynamic IP address from whatever Starbucks
wireless network I'm connected to. 

So now the netbook works fine, as long as I'm NOT connected to my own
LAN. When I'm at home connected to my LAN on the netbook I can get to
all the local computers fine -- but I can't reach the Internet.



Ed.Greshko wrote:

Plug the WAN interface of the D-Link DIR-615 into one of the ports of
your router, just like all of your other hardwired systems, and manually
configure the WAN interface the same as those systems.  i.e. Static IP.
Configure the wireless side making sure that the subnet assigned is
different than the one being used on the WAN side. Also, make sure the
wireless side is configured to supply DHCP services to wireless clients.



I finally got around to dealing with this

Here are the details of what worked (possibly of use to someone beside
me with basic networking issues):
(1) connected DIR-615 "Internet" port to Gateway router (192.168.1.1)
(2) on DIR-615 "INTERNET SETUP" page:
   Internet Connection: Static IP
   IP Address: 192.168.1.2
   Subnet Mask: 255.255.255.0
   Default Gateway: 192.168.1.1
(3) on DIR-615 "NETWORK SETTINGS SETUP" page:
   Router IP Address: 192.168.2.1
   Subnet Mask: 255.255.255.0
   Enable DHCP Server (checked)
   DHCP IP address Range: 192.168.2.11 to 192.168.2.12


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

wireless networking problem

2010-08-09 Thread Gerhard Magnus 
I'm at my wits end trying to solve what I keep thinking is a simple
problem.

My old DSL modem doesn't have a wireless interface. It's connected to a
router (the LAN gateway) which then has ethernet connections to my
boxes. All of these computers use static IP addresses. The DSL modem is
assigned a dynamic IP address by my ISP. 

I recently added a DIR-615 D-Link wireless router which connects to the
gateway router. I also have a netbook which I first configured with a
static IP address and the IP address of the gateway router. This worked
fine -- but, of course, I mostly use the netbook away from home, so I
reconfigured it to accept a dynamic IP address from whatever Starbucks
wireless network I'm connected to. 

So now the netbook works fine, as long as I'm NOT connected to my own
LAN. When I'm at home connected to my LAN on the netbook I can get to
all the local computers fine -- but I can't reach the Internet.

The wireless router has an Internet --> WAN page in its setup that
includes a choice of Internet Connection Types: (1) Dynamic IP (DHCP),
which I can't use since the DSL modem has already taken the one IP
address assigned by my ISP;
(2) Static IP; (3) PPPoE; (4) PPTP; and (5) L2TP 

Will any of these work? I'd appreciate some advice before I rush in and
start changing things without knowing what I'm doing...

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: Who's moderating this forum?

2010-07-18 Thread Gerhard Magnus 
On Sun, 2010-07-18 at 17:09 -0400, Marcel Rieux wrote:
> On Sat, Jul 17, 2010 at 10:14 PM, David  wrote:
> On 7/17/2010 9:58 PM, Marcel Rieux wrote:
> > On Sat, Jul 17, 2010 at 5:12 PM, Darr  
> 
> > > wrote:
> >
> > On Friday, 16 July, 2010 @02:48 zulu, Marcel Rieux
> scribed:
> >
> > > and it will most probably prove my point that while
> Nouveau developers
> > > pretend they work really hard to get new users,
> installing Kmod is a
> > > one way ticket. Unless, of course, you're willing to
> spend a day or
> > > two trying suggestions that have never been tested
> such as the one I
> > > already received: yum remove, and that's it.
> >
> >
> > Since somebody from Nouveau told me here that installing
> Nvidia drivers
> > is not a one way ticket that will prevent users to get back
> to Nouveau
> > and that RPMfusion should provide instructions to remove
> kmod-nvidia,
> > I'm following the instructions provided by RPMfusion. But,
> since this
> > hasn't much to do with "Who's moderating this forum?", I'll
> repost your
> > answer in "Wo, I'm asking RPMfusion how to uninstall Kmod
> nvidia"
> > (Don't ask me what Wo is doing there, I supposed I forgot
> from a title I
> > previously wrote :) 
> 
> 
> Knock. Knock. Anyone home?
> 
> You should get a blog for this crap becasue no one here cares.
> 
> I wouldn't say nobody, but next to nobody. To me this is a problem.
> When people, including Fedora administrators, don't give a shit about
> trademark matters or who the bank that underwrote Red Hat really is --
> maybe you noticed I never got a single comment for my link to
> rollingstone.org -- and what kind of enterprise culture this sets,
> there really is a HUGE problem.
> 
> But that's what happens when geeks run a project.
> 
> If you want to filter any of my messages or all post from me, feel
> free. Otherwise, why don't you just buzz off? People complain about my
> posts but the number of posts like yours almost outnumber them. So
> what's the point, except for preventing some people expressing matters
> they believe are important, flooding their posts in heaps of nonsense?
> 
As Hannah Jelkes says at the end of Tennessee Williams' play "The Night
of the Iguana" -- "Oh God, can’t we stop now? Finally? Please let
us. It’s so quiet here now."

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: nvidia driver issues -- SOLVED

2010-07-07 Thread Gerhard Magnus 
On Tue, 2010-07-06 at 17:35 -0400, Mauriat Miranda wrote:
> On Tue, Jul 6, 2010 at 1:36 PM, Gerhard Magnus  wrote:

> Sadly the proprietary nvidia driver is a mess.
> 
> The best answer to all your questions is: Try and see.  If you don't
> have problems then you're fine.
> 
> > QUESTION: Google tells me that specifying "nomodeset" basically tells
> > the system to use an older set of software/drivers which does work but
> > may be slower or have some other issues that people would like to
> > eliminate. Is the "nomodeset" parameter necessary in this case?
> 
> Some people claim the driver didn't work without it, while others
> (myself included) have found it made no noticeable difference(?).  It
> only takes 1 extra reboot to test this.
> 
> > The rpmfusion.org/Howto/nVidia instructions also say that SElinux
> > protection should be lowered:
> > setsebool -P allow_execstack on
> >
> > QUESTION: Is this really necessary? Does it risk compromising the
> > security of my system?
> 
> I would guess no (not any more).  I didn't need it when I tested it on
> a few different systems.  I think it was needed once upon a time.
> Again, test your installation without running that command (more
> secure).  If you find SELinux errors in your log files or that the
> driver won't load due to SElinux then execute that command.
> 
> > MOST IMPORTANT QUESTION: Suppose this doesn't work and the reboot hangs
> > (presumably with the X startup). Will I be able to use a previous kernel
> > (on the grub menu) or will yum have automatically associated
> > kmod-nvidia-PAE with all the retained kernels? Or is the back-out
> > procedure (from run level 3) to (1) yum remove kmod-nvidia-PAE (2) take
> > out the extra parameters on the kernel line in grub.conf, and (3)
> > reboot?
> 
> Typically when you 'yum' install the Nvidia driver like this, it is
> built for a specific kernel.  The yum command may also install a new
> kernel in order to match the nvidia driver.  Going back the previous
> kernel should work (I think).  Try and see, no harm done.
> 
> In the case of a locked X-server, you can as you state go back to runlevel 3.
> To force this at grub, hit a key to see the kernels menu and select
> one but don't hit enter.
> Hit 'E' (to edit) and scroll to the end of the 'kernel' line and add '3'.
> Then hit enter and 'B' to boot.
> Then you can do the steps you stated to remove.

I've been able to replace the nouveau driver with an nvidia one by (1)
adding rdblacklist=nouveau to the active kernel entry in grub.conf and
(2) yum install kmod-nvidia-PAE. The last little "Gotcha!" for his
problem was the need to run nvidia-settings as root (rather than from
the Applications --> System Tools --> nvidia Display Settings menu):

sudo nvidia-settings

Otherwise I was unable to permanently activate the second monitor by
saving the X configuration file.\

Thanks for the help with this!


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

nvidia driver issues

2010-07-06 Thread Gerhard Magnus 
As the nouveau driver for nvidia cards (installed by default with FC13)
does not adequately support dual monitors I would like to replace it
with a nvidia driver. I'm using this documentation:

http://rpmfusion.org/Howto/nVidia
http://www.mjmwired.net/resources/mjm-fedora-nvidia.html

Here's the procedure I've decided to follow, although I still have some
questions, mostly based on discrepancies between the two sets of
instructions:

1. determine card model and level of support
[98] ~ $ /sbin/lspci -nn | grep 'VGA\|NV'
06:01.0 VGA compatible controller [0300]: nVidia Corporation NV44A
[GeForce 6200] [10de:0221] (rev a1)
I found the card name and PCI ID (221) listed at
http://www.nvidia.com/object/IO_18897.html:
GeForce 62000x0221
So apparently this card (GPU) is supported.

2. modify grub.conf to disable nouveau driver
Both instructions say to add this to the end of the entry for the active
kernel:
rdblacklist=nouveau
...but the rpmfusion.org/Howto/nVidia instructions differ in saying to
add instead:
rdblacklist=nouveau nomodeset

QUESTION: Google tells me that specifying "nomodeset" basically tells
the system to use an older set of software/drivers which does work but
may be slower or have some other issues that people would like to
eliminate. Is the "nomodeset" parameter necessary in this case?

The rpmfusion.org/Howto/nVidia instructions also say that SElinux
protection should be lowered:
setsebool -P allow_execstack on

QUESTION: Is this really necessary? Does it risk compromising the
security of my system?

3. Select and install proper kmod (Fedora Kernel Module) which matches
the driver. This kmod must match the specific driver for the PCI ID
determined earlier.

As far as I can tell from
www.mjmwired.net/resources/mjm-fedora-nvidia.html (and since my system
has been using PAE kernels) the proper kernel module to use is:
kmod-nvidia-PAE

...which I can install using yum (as I already have the rpmfusion
repository configuration files):
su -c 'yum install kmod-nvidia-PAE'

...and then reboot.

MOST IMPORTANT QUESTION: Suppose this doesn't work and the reboot hangs
(presumably with the X startup). Will I be able to use a previous kernel
(on the grub menu) or will yum have automatically associated
kmod-nvidia-PAE with all the retained kernels? Or is the back-out
procedure (from run level 3) to (1) yum remove kmod-nvidia-PAE (2) take
out the extra parameters on the kernel line in grub.conf, and (3)
reboot?

Thanks for the help!
Jerry




-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

problem with dual monitors

2010-07-05 Thread Gerhard Magnus 
I've just installed FC13 on a box with a nVidia GeForce7300GS graphics
card into which I've plugged two monitors. The driver is the one
selected by the installation program. I'm using the gnome desktop

Here's the problem (which I didn't have with FC11): When I turn on the
system only one monitor shows the panel and desktop icons. If I turn on
the second monitor after booting up I lose the panel and desktop icons
on the first monitor.

Is there some way of "nailing down" the monitor on which the panel and
desktop icons are displayed? I only need them on one monitor -- it's
just some consistency that I'd like.

Thanks for the help!
Jerry


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

how to start Xscreensaver automatically

2010-06-20 Thread Gerhard Magnus 
I'm running FC13 with a gnome desktop and would like to have the new
screensaver start automatically when I log on.

What happens now is that I have to start the configuration gui manually
using System --> Preferences --> Screensaver. I then get the message:
"The XScreenSaver daemon doesn't seem to be running on display ":0.0".
Launch it now?" Then replying OK starts it and the show is fine.

Using gnome-session-properties I have shut off the old gnome screensaver
program so that it won't start up at login and turned on Xscreensaver.
But I still have to start it manually.

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: NFS problem in FC13 FIXED, at least for now

2010-06-16 Thread Gerhard Magnus 
On Tue, 2010-06-15 at 23:41 +0100, M A Young wrote:
> On Tue, 15 Jun 2010, Gerhard Magnus wrote:
> 
> > I am trying to upgrade the boxes on a small LAN from FC11 to FC13. The
> > server is now running FC13 and NFS. One of the boxes that is still
> > running FC11 can read & write to the shared directories on the server
> > without problems. But I'm having problems accessing these directories on
> > another client that I have upgraded to FC13.
> >
> > During booting of this second client running FC13 I get this message:
> >
> > Mounting NFS filesystems:  mount.nfs: access denied by server while
> > mounting 192.168.1.14:/home/magnusg/Music
> >
> > Any suggestions for troubleshooting this would be most appreciated.
> 
> FC13 now defaults to NFSv4 which might (or might not) be related to the 
> problem you are seeing. You could try to mount the directory with the 
> option -o nfsvers=3 and look to see if that makes any difference. Of 
> course it is also worth checking that the client really does have 
> permission to mount that directory.

I changed the entry for the share in the client's fstab file to:

192.168.1.14:/home/magnusg/Music/home/magnusg/Musicnfs
rw,auto,hard,intr,bg,nfsvers=3   0 0

and everything works fine -- i.e. I can run NFS on an FC13 server and
access the share on an FC13 client.

My understanding is that I've forced the client to use NFSv3, right? So,
assuming Fedora continue to use NSFv4 for awhile, the long-term problem
of how settings on the client differ for NSFv4 with respect to earlier
versions.

However -- thank you! It's yet another example of help I've received
from this list in cutting through what to me seemed an intractable
problem.  

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

NFS problem in FC13

2010-06-15 Thread Gerhard Magnus 
I am trying to upgrade the boxes on a small LAN from FC11 to FC13. The
server is now running FC13 and NFS. One of the boxes that is still
running FC11 can read & write to the shared directories on the server
without problems. But I'm having problems accessing these directories on
another client that I have upgraded to FC13.

During booting of this second client running FC13 I get this message:

Mounting NFS filesystems:  mount.nfs: access denied by server while
mounting 192.168.1.14:/home/magnusg/Music

Any suggestions for troubleshooting this would be most appreciated.


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

RPMFusion Depository issue

2010-06-13 Thread Gerhard Magnus 
I'm trying to set up the RPMFusion Depository on a x86_64 system running
FC13. According to the "Personal Guide" at
http://www.mjmwired.net/resources/mjm-fedora-f13.html#yum
I need to run these two commands

rpm -ivh
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
rpm -ivh
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

But running the first, I get:

Retrieving
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
curl: (7) couldn't connect to host
error: skipping
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
 - transfer failed

Is this some temporary error with the repository?


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

editing menus on FC13 gnome desktop

2010-06-11 Thread Gerhard Magnus 
How does one edit menu items on the gnome desktop in FC13? In FC11,
right-clicking on the little footprint logo on the left end of the panel
would bring up an "edit menus" option. But in FC13, right-clicking on
the similarly placed "f" logo gives a list from which this option is
missing.


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

question about NSFv4 and FC13

2010-06-05 Thread Gerhard Magnus 
I'm currently running FC11 and plan to do a clean install of FC13
throughout my small home LAN. But before I do this I'd like to get a few
things straight about NSFv4 and FC13.

I've been using a setup for NSF suggested by someone on this list for
several versions of Fedora. Here's the procedure:

I use system-config-nfs on the server to create entries in
the /etc/exports file for each directory I want to share, e.g.:
/home/magnusg/Music   192.168.1.12(rw,sync)   192.168.1.13(rw,sync)

Also on the server, I use system-config-services to enable and start nfs
and nfslock on levels 3, 4 and 5.

In /etc/sysconfig/nfs on the server I force several ports to be
non-random by specifying them as follows:
RQUOTAD_PORT=4000
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
STATD_PORT=4003

Then, using system-config-firewall on the server, I make NSF4 a trusted
service. On the "Other Ports" panel I open ports 4000-4003 as well as
port 111 (for the portmapper) as tcp and udp

Finally, on each client, I add a line like this to the fstab file:
192.168.1.14:/home/magnusg/Music  /home/magnusg/Music  nfs
rw,auto,hard,intr,bg  0 0

My question is: does any of this procedure change for the NSFv4 on FC13?
Or is there now a less complicated way to accomplish the same thing?

Thanks for the help!


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: Is this the Linux list for beginners

2010-05-29 Thread Gerhard Magnus 
On Sat, 2010-05-29 at 10:19 -0700, Patrick Bartek wrote:
> --- On Fri, 5/28/10, Mercury Rising  wrote:
> 
> > Linux seems a bit overwhelming to me, but I am determined to get it and
> > learn it. Is this the right LISTSERV to be on?
> 
> This list is specifically for Fedora Linux users.  Many other distros have 
> their own.  Although, many of the solutions and fixes proffered here will 
> work with other distros.
> 
> Since you are new to Linux, you need to get a good knowledge foundation first 
> instead of stumbling around
in cyberspace looking for answers.  Buy and study this book: RUNNING LINUX by 
O'Reilly Press

I would also highly recommend the aptly titled: "UNIX for the Impatient"
by Paul Abraahams & Bruce Larson. 

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

esata drive question

2010-05-12 Thread Gerhard Magnus 
I recently acquired a Toshiba external hard drive that has both usb and
eSATA ports and would like to use the eSATA connection to take advantage
of the speed. I'm running FC11 with the gnome desktop. Is it as simple
as getting an eSATA PCI card and cable or does Fedora have other
requirements? Thanks for any advice! --Jerry


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

illuminated keyboard issue

2010-04-06 Thread Gerhard Magnus 
I'm running FC11 with a gnome desktop on a box dual booting Windows XP.
I recently acquired a sunbeam illuminated keyboard that works fine with
the machine in Windows mode -- the keyboard lighting toggles on and off
with the scroll lock key. But this doesn't work when I'm running FC11.
Is there some way to hack this? Any suggestions would be most
appreciated. --Jerry


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

saving links and images

2010-03-13 Thread Gerhard Magnus 
I'm running a fully updated FC11 with the gnome desktop and Firefox
3.5.8. Recently, the right mouse buttons for "Save link as..." and "Save
link as..." have stopped working; i.e. nothing happens instead of my
getting the usual second box with options for saving. Is anyone else
having this problem or know of a solution? Thanks for the help!


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines