Ethernet not working

[wilks]

Hi all,

I've installed YDL 6.2 on a partition for a iBook 1.42GHz model. The install went fine. I want to plug in my ethernet cable for temporary access to the internet so I can install the firmware and drivers to get wifi going, but I can't connect when I plug in the ethernet cable. A "/etc/rc.d/init.d/network restart" reveals this in /var/log/messages:"DHCPDISCOVER on eth0 to 255.255.255.255 port 67" but fails with "localhost dhclient: No DHCPOFFERS received."

Any advice on how to diagnose this problem?

Thank you,
w

[gibroni]

[MODERATOR EDIT: The best way to show your output is with the [ code] directive. I've edited your post to include the [ code] tags. -Paul]

I get a similar message. I installed 6.2 on my PS3 80GB version. I have never been able to get a stable wireless connection. Then after installing VLC my wireless dropped out for good. NetworkManager failed to give me a wireless connection so I tried WICD. WICD worked but the connection would drop out for no apparent reason. Then all of a sudden WICD would not start. I found a solution to WICD not starting on this forum via a patch to WICD, and it worked but the wireless still doesn't connect. I like wireless because my stereo system is in a different room and I don't want to hardwire a connection. Anyway, my message file is attached and shows the errors but I don't know how to resolve them. A side issue: when i tried to upload a copy of the message file I got a error from this forum saying:

The extension is not allowed.

I tried .txt, .jpg, and blank??? Here is an excerpt:

Code: Select all

Sep 12 12:24:10 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:10 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat
Sep 12 12:24:10 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
Sep 12 12:24:10 localhost dhclient: All rights reserved.
Sep 12 12:24:10 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Sep 12 12:24:10 localhost dhclient:
Sep 12 12:24:11 localhost dhclient: Listening on LPF/wlan0/00:19:c5:b2:db:55
Sep 12 12:24:11 localhost dhclient: Sending on   LPF/wlan0/00:19:c5:b2:db:55
Sep 12 12:24:11 localhost dhclient: Sending on   Socket/fallback
Sep 12 12:24:11 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Sep 12 12:24:12 localhost avahi-daemon[4094]: New relevant interface wlan0.IPv6 for mDNS.
Sep 12 12:24:12 localhost avahi-daemon[4094]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:24:12 localhost avahi-daemon[4094]: Registering new address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:24:12 localhost kernel: gelic_wl_assoc_worker: no bss matched. association failed
Sep 12 12:24:15 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Sep 12 12:24:15 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:19 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Sep 12 12:24:19 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:23 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Sep 12 12:24:23 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:27 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:28 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Sep 12 12:24:31 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:39 localhost last message repeated 2 times
Sep 12 12:24:40 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Sep 12 12:24:43 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:51 localhost last message repeated 2 times
Sep 12 12:24:52 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Sep 12 12:24:55 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:59 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:02 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Sep 12 12:25:03 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:14 localhost last message repeated 14 times
Sep 12 12:25:15 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Sep 12 12:25:15 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:23 localhost last message repeated 11 times
Sep 12 12:25:24 localhost dhclient: No DHCPOFFERS received.
Sep 12 12:25:24 localhost dhclient: Trying recorded lease 192.168.0.223
Sep 12 12:25:24 localhost avahi-daemon[4094]: New relevant interface wlan0.IPv4 for mDNS.
Sep 12 12:25:24 localhost avahi-daemon[4094]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.223.
Sep 12 12:25:24 localhost avahi-daemon[4094]: Registering new address record for 192.168.0.223 on wlan0.
Sep 12 12:25:24 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:26 localhost last message repeated 2 times
Sep 12 12:25:27 localhost avahi-daemon[4094]: Withdrawing address record for 192.168.0.223 on wlan0.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.223.
Sep 12 12:25:27 localhost avahi-daemon[4094]: iface.c: interface_mdns_mcast_join() called but no local address available.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Interface wlan0.IPv4 no longer relevant for mDNS.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Interface wlan0.IPv6 no longer relevant for mDNS.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Withdrawing address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:25:27 localhost dhclient: No working leases in persistent database - sleeping.
Sep 12 12:25:27 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:27 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:27 localhost NET[4707]: /sbin/dhclient-script : updated /etc/resolv.conf
Sep 12 12:25:27 localhost dhclient: receive_packet failed on wlan0: Network is down
Sep 12 12:25:28 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:31 localhost last message repeated 3 times
Sep 12 12:25:33 localhost avahi-daemon[4094]: New relevant interface wlan0.IPv6 for mDNS.
Sep 12 12:25:33 localhost avahi-daemon[4094]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:25:33 localhost avahi-daemon[4094]: Registering new address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:25:34 localhost avahi-daemon[4094]: Interface wlan0.IPv6 no longer relevant for mDNS.
Sep 12 12:25:34 localhost avahi-daemon[4094]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:25:34 localhost avahi-daemon[4094]: Withdrawing address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:25:34 localhost dhclient: receive_packet failed on wlan0: Network is down
Sep 12 12:25:34 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat
Sep 12 12:25:34 localhost Internet Systems Consortium DHCP Client V3.0.5-RedHat
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
Sep 12 12:25:34 localhost Copyright 2004-2006 Internet Systems Consortium.
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: All rights reserved.
Sep 12 12:25:34 localhost All rights reserved.
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Sep 12 12:25:34 localhost For info, please visit http://www.isc.org/sw/dhcp/
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient:
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: Failed to get interface index: No such device
Sep 12 12:25:34 localhost Failed to get interface index: No such device
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient:
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: If you did not get this software from ftp.isc.org, please
Sep 12 12:25:34 localhost If you did not get this software from ftp.isc.org, please
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: get the latest from ftp.isc.org and install that before
Sep 12 12:25:34 localhost get the latest from ftp.isc.org and install that before
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: requesting help.
Sep 12 12:25:34 localhost requesting help.

[ppietro]

[MODERATOR EDIT: The best way to show your output is with the [ code] directive. I've edited your post to include the [ code] tags. -Paul]

I get a similar message. I installed 6.2 on my PS3 80GB version. I have never been able to get a stable wireless connection. Then after installing VLC my wireless dropped out for good. NetworkManager failed to give me a wireless connection so I tried WICD. WICD worked but the connection would drop out for no apparent reason. Then all of a sudden WICD would not start. I found a solution to WICD not starting on this forum via a patch to WICD, and it worked but the wireless still doesn't connect. I like wireless because my stereo system is in a different room and I don't want to hardwire a connection. Anyway, my message file is attached and shows the errors but I don't know how to resolve them. A side issue: when i tried to upload a copy of the message file I got a error from this forum saying:

The extension is not allowed.

I tried .txt, .jpg, and blank??? Here is an excerpt:

Code: Select all

Sep 12 12:24:10 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:10 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat
Sep 12 12:24:10 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
Sep 12 12:24:10 localhost dhclient: All rights reserved.
Sep 12 12:24:10 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Sep 12 12:24:10 localhost dhclient:
Sep 12 12:24:11 localhost dhclient: Listening on LPF/wlan0/00:19:c5:b2:db:55
Sep 12 12:24:11 localhost dhclient: Sending on   LPF/wlan0/00:19:c5:b2:db:55
Sep 12 12:24:11 localhost dhclient: Sending on   Socket/fallback
Sep 12 12:24:11 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Sep 12 12:24:12 localhost avahi-daemon[4094]: New relevant interface wlan0.IPv6 for mDNS.
Sep 12 12:24:12 localhost avahi-daemon[4094]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:24:12 localhost avahi-daemon[4094]: Registering new address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:24:12 localhost kernel: gelic_wl_assoc_worker: no bss matched. association failed
Sep 12 12:24:15 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Sep 12 12:24:15 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:19 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Sep 12 12:24:19 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:23 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Sep 12 12:24:23 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:27 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:28 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Sep 12 12:24:31 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:39 localhost last message repeated 2 times
Sep 12 12:24:40 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Sep 12 12:24:43 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:51 localhost last message repeated 2 times
Sep 12 12:24:52 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Sep 12 12:24:55 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:24:59 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:02 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Sep 12 12:25:03 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:14 localhost last message repeated 14 times
Sep 12 12:25:15 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Sep 12 12:25:15 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:23 localhost last message repeated 11 times
Sep 12 12:25:24 localhost dhclient: No DHCPOFFERS received.
Sep 12 12:25:24 localhost dhclient: Trying recorded lease 192.168.0.223
Sep 12 12:25:24 localhost avahi-daemon[4094]: New relevant interface wlan0.IPv4 for mDNS.
Sep 12 12:25:24 localhost avahi-daemon[4094]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.223.
Sep 12 12:25:24 localhost avahi-daemon[4094]: Registering new address record for 192.168.0.223 on wlan0.
Sep 12 12:25:24 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:26 localhost last message repeated 2 times
Sep 12 12:25:27 localhost avahi-daemon[4094]: Withdrawing address record for 192.168.0.223 on wlan0.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.223.
Sep 12 12:25:27 localhost avahi-daemon[4094]: iface.c: interface_mdns_mcast_join() called but no local address available.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Interface wlan0.IPv4 no longer relevant for mDNS.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Interface wlan0.IPv6 no longer relevant for mDNS.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:25:27 localhost avahi-daemon[4094]: Withdrawing address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:25:27 localhost dhclient: No working leases in persistent database - sleeping.
Sep 12 12:25:27 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:27 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:27 localhost NET[4707]: /sbin/dhclient-script : updated /etc/resolv.conf
Sep 12 12:25:27 localhost dhclient: receive_packet failed on wlan0: Network is down
Sep 12 12:25:28 localhost kernel: gelic_eurus_sync_cmd_worker: cmd issue failed
Sep 12 12:25:31 localhost last message repeated 3 times
Sep 12 12:25:33 localhost avahi-daemon[4094]: New relevant interface wlan0.IPv6 for mDNS.
Sep 12 12:25:33 localhost avahi-daemon[4094]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:25:33 localhost avahi-daemon[4094]: Registering new address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:25:34 localhost avahi-daemon[4094]: Interface wlan0.IPv6 no longer relevant for mDNS.
Sep 12 12:25:34 localhost avahi-daemon[4094]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::219:c5ff:feb2:db55.
Sep 12 12:25:34 localhost avahi-daemon[4094]: Withdrawing address record for fe80::219:c5ff:feb2:db55 on wlan0.
Sep 12 12:25:34 localhost dhclient: receive_packet failed on wlan0: Network is down
Sep 12 12:25:34 localhost dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat
Sep 12 12:25:34 localhost Internet Systems Consortium DHCP Client V3.0.5-RedHat
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: Copyright 2004-2006 Internet Systems Consortium.
Sep 12 12:25:34 localhost Copyright 2004-2006 Internet Systems Consortium.
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: All rights reserved.
Sep 12 12:25:34 localhost All rights reserved.
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Sep 12 12:25:34 localhost For info, please visit http://www.isc.org/sw/dhcp/
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient:
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: Failed to get interface index: No such device
Sep 12 12:25:34 localhost Failed to get interface index: No such device
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient:
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: If you did not get this software from ftp.isc.org, please
Sep 12 12:25:34 localhost If you did not get this software from ftp.isc.org, please
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: get the latest from ftp.isc.org and install that before
Sep 12 12:25:34 localhost get the latest from ftp.isc.org and install that before
Sep 12 12:25:34 localhost 
Sep 12 12:25:34 localhost dhclient: requesting help.
Sep 12 12:25:34 localhost requesting help.

Your issues are most likely not related. Macs use a different network driver than PS3s.

With 6.2, you probably shouldn't use the forum patch for wicd, unless you replace the stock YDL version of wicd with another. The patch is for 6.1, and for versions of WICD directly from the source code website. YDL did their own patch for 6.2.

I don't know if it's been established that you can use the forum patch over the YDL patch - I'll defer to the patch author on this one. I'm thinking you may have to unpatch if you're using the stock wicd that comes with 6.2.

If wicd won't start in 6.2, there's a fix you might need to do in the YDL advisory section, instead of applying our forum patch. The advisory is here:
http://us.fixstars.com/support/advisories.shtml

Look for the secton marked "If Wicd Network Manager dies after reboot ...".

NOTE: That guide assumes the use of sudo, which isn't set up on YDL systems by default. Instead of using sudo bash -, just use the su command as follows: su -l - that's "s" "u" "space" "dash" "lowercase L".

Cheers,
Paul

[gibroni]

Thank you for the timely reply. A little bit of history is in order. Prior to patching wicd to 1.5.9 I followed the advisory you suggested and was running with wicd to start up after booting. As I said, this worked for awhile but I had the following symptoms: a. wicd would not start on boot b. my network connection would drop out. The easy fix was to restart the network connection (using wicd) every time I got a dropout (painful too). After installing VLC, wicd would not start - it would temporarily flash on the screen and then drop out. So in desperation, I tried the patch I found on this forum and 'voila' wicd would stay up but not connect. The patch instructions were as follows:


wicd-1.5.9_patched.tar.gz
wicd v1.5.9 patched tarball installer
**includes**
"Stuck Obtaining IP Address" fix
"0% Signal Strength" fix
"Auto-Reconnect" fix
(250.68 KiB) Downloaded 211 times


Since multiple files needed to be edited for this one, I've decided to post it as a modified installer tarball. The good news is, by installing this, you don't have to worry about any of my other patches because they're already in here. Should you wish to try this out, I have provided basic install instructions below. It's a pretty simple tarball install.

Intructions:
( * ) = must be done as logged in as root, or through a su - or sudo console

Step 1*: Backup and delete all files located in /usr/lib/wicd/
Step 2*: Backup and delete all files located in /usr/lib/python2.x/site-packages/wicd/ <-- x could be 4 or 5 depending on python version installed
Step 3: In console, extract tarball with the command tar-zxvf wicd-1.5.9_patched.tar.gz <-- this will extract the files to a folder called wicd-1.5.9_patched
Step 4: In console, type cd wicd-1.5.9_patched to enter that folder
Step 5: In console, type python ./setup.py configure <-- this will gather information about your system and prep for install
Step 6: If not done already, type su - and when prompted, type your root password to root yourself
Step 7*: In console, type python ./setup.py install <-- this will copy all the files to where they need to be
Step 8: Finally. reboot

My questions are as follows:

1. In order to back out the patch, can I restore the original directories (which I diligently saved)?
2. Given that I don't have and internet connection via wireless, can I take the PS3 machine and hook it up to my Dell monitor and wire it to my router until I get it working (i.e. move it into my computer room vice my living room).
3. I use a wireless keyboard for my PS3. Could my wireless keyboard be interfering with the PS3/YDL wireless? I have been using the wireless key board on the PS3 side for a year.

My gut feeling is that there is a dhclient problem. I am new to YDL and hope I don't have to become a network guru or linux jock. I love the YDL kde interface and the easy Yum updating. By the way, I checked my D-link dgl 4300 router and can't find any bad messages. I am using Verizon 3mbs high speed DSL internet (I know it's yucky!). Any further suggestions would be much appreciated.

[ppietro]

Thank you for the timely reply. A little bit of history is in order. Prior to patching wicd to 1.5.9 I followed the advisory you suggested and was running with wicd to start up after booting. As I said, this worked for awhile but I had the following symptoms: a. wicd would not start on boot b. my network connection would drop out. The easy fix was to restart the network connection (using wicd) every time I got a dropout (painful too). After installing VLC, wicd would not start - it would temporarily flash on the screen and then drop out. So in desperation, I tried the patch I found on this forum and 'voila' wicd would stay up but not connect.

That means that wicd isn't working correctly, post patch, I think.

My questions are as follows:

1. In order to back out the patch, can I restore the original directories (which I diligently saved)?

Hmm - maybe. See - here's the deal. We usually use an RPM installer file to add/remove software. An RPM is kinda like a Windows MSI file - it puts the files where they need to go, then registers them in a database. Once done, they can be upgraded with newer RPMs or uninstalled.

By running a tarball installer like this, these files aren't registered. They just copy the files in place. This isn't a bad thing - it's the way Unix started - but mixing tarball installs and RPM installs can lead to file confusion.

This is a long way of saying: "I think so."

2. Given that I don't have and internet connection via wireless, can I take the PS3 machine and hook it up to my Dell monitor and wire it to my router until I get it working (i.e. move it into my computer room vice my living room).

That should work - assuming your Dell monitor accepts the PS3's signal via HDMI. If your Dell monitor has DVI-D, and you were planning on using an HDMI-to-DVI adapter, then it must also have HDCP, or you'll get nothing but a black screen.

3. I use a wireless keyboard for my PS3. Could my wireless keyboard be interfering with the PS3/YDL wireless? I have been using the wireless key board on the PS3 side for a year.

It depends on the Wireless keyboard. If it's a 2.4 GHz RF keyboard, then, yes, it can. (Generally, that would manifest as a network slowdown.) If it's Bluetooth, not so much. If it's Infrared, then not at all.

My gut feeling is that there is a dhclient problem.

My gut feeling tells me it's not dhclient, but wicd problems. YMMV.

Cheers,
Paul