Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, 2009-02-26 at 15:22 -0500, Rick Bilonick wrote: This all started with installing F10 and then not being able to connect to a wired ethernet port using a static IP. Everything worked fine in F10. Now the networking works but I get no display. Sure, but the appropriate thing to do would have been to start a new thread. It *is* a new topic after all. Never mind. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
I had to reboot the system (after updating) - the USB wireless keyboard stopped working (replaced batteries - still does not work). The wireless mouse worked and I could use the cursor to start programs but could not type any input. I plugged in a wired usb keyboard and mouse. Now the system refuses to reboot into a graphical display even though inittab is at 5. I can ctrl-alt F2 into a shell and even install new packages (so the networking is still working). But X refuses to run (although I don't see any error messages even with dmesg). I checked xorg.conf and it consists of just Section Device using the vesa driver. I looked through the entire X11 log but no errors are reported - it finds the vesa driver and usable modes - yet no display. After the F10 white line thingy at the bottom goes away, the cursor just blinks in the upper left hand corner. I have to ctrl alt F2 to a shell to log in. I'm completely stumped. What else should I check? The kernel is 2.6.27.15-170.2.24.fc10.x86_64. If I type startx I get No address associated with name. It says to check /usr/bin/X but this does not exist. Rick B. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, Feb 26, 2009 at 9:56 AM, Rick Bilonick r...@nauticom.net wrote: I'm completely stumped. What else should I check? The kernel is 2.6.27.15-170.2.24.fc10.x86_64. If I type startx I get No address associated with name. It says to check /usr/bin/X but this does not exist. /usr/bin/X doesn't exist? What does the output of rpm -qf /usr/bin/X say? What does the output of rpm -q rpm -q xorg-x11-server-Xorg say? -jef -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, 2009-02-26 at 13:56 -0500, Rick Bilonick wrote: I had to reboot the system (after updating) - the USB wireless keyboard stopped working (replaced batteries - still does not work). The wireless mouse worked and I could use the cursor to start programs but could not type any input. I plugged in a wired usb keyboard and mouse. Now the system refuses to reboot into a graphical display even though inittab is at 5. I can ctrl-alt F2 into a shell and even install new packages (so the networking is still working). But X refuses to run (although I don't see any error messages even with dmesg). I checked xorg.conf and it consists of just Section Device using the vesa driver. I looked through the entire X11 log but no errors are reported - it finds the vesa driver and usable modes - yet no display. After the F10 white line thingy at the bottom goes away, the cursor just blinks in the upper left hand corner. I have to ctrl alt F2 to a shell to log in. I'm completely stumped. What else should I check? The kernel is 2.6.27.15-170.2.24.fc10.x86_64. If I type startx I get No address associated with name. It says to check /usr/bin/X but this does not exist. It could be useful to mention your graphics card as it might be a driver problem. Does ~/.xsession-errors say anything useful? Not all logging goes to /var/log/X* BTW, try as I mught I can see nothing in your message related to Fedora 10 64-bit Wired Network Problems. Looks like a hijack. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
Rick Bilonick wrote:
I installed F10 64-bit from the DVD iso on a 64-bit Intel 4-cpu
computer. I had problems getting the wired network connection to work on
network A UNTIL I realized that the network daemon was for some
reason turned off by default. Once I turned it on via services,
networking worked fine (using a static IP). (There is an annoying bug in
the F10 gui for networking - the net mask gets changed to the gateway ip
which of course screws up networking - this appears to be fixed once you
upgrade the system but I had to manually fix the eth0 script to get the
netmask to the correct value.)
Now I've installed the same DVD iso on a dual 64-bit AMD Opteron system
that previously had run F8 (networking worked fine on network A). I've
made sure network is on. I've manually configured the eth0 script to
avoid the buggy network gui netmask problem. I can ping the gateway on
network A. For some reason I cannot ping the DNS on this network. I
can connect to my home computer using its IP address using ssh. But I
cannot view web pages using the URL's. I switched to a different
ethernet port on a different network B with different fixed IP and
DNS that I know works (I use it for my F8 laptop every day) and although
I can ping the gateway and DNS, I still cannot view web pages. I just
now hooked my Ubuntu 8.10 laptop to network A and it connects
flawlessly and I can view web pages so I know the port works - both
ports on networks A and B work fine. But I cannot get the F10 AMD
computer to connect to either network and view web pages (I do as I said
get some connection using IP addresses and ssh).
Any ideas on what is wrong? This is very frustrating. If I could get a
network connection I could upgrade the computer but I can't get to
square one.
P.S. I've looked at the eth0 script, the resolv.conf and hosts files and
everything looks fine. I've tried turning different things on and off
(like IPv6 and peer) but nothing makes a difference. I'm using DNS1,
DNS2, and DNS3 in the eth0 script and these appear appropriately in the
resolv.conf file.
I have never had this much trouble getting a wired network connection -
it almost always works by default.
Rick B.
My rule for this issue is to remove network manager.
On two desktop computers with static IP addresses was.
-install F10 from DVD.
-apply all the updates.
-install yumex. {I like it better than packagekit}
-install system-config-network
-turn off networkmanager
-remove networkmanager
-run system-config-network
-enter in settings
-restart networking
-ensure networking is running properly
-test by rebooting.
As others have suggested, check /etc/sysconfig/network*
as well as /etc/resolve.conf
--
Robin Laing
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, 2009-02-26 at 14:58 -0430, Patrick O'Callaghan wrote: It could be useful to mention your graphics card as it might be a driver problem. Does ~/.xsession-errors say anything useful? Not all logging goes to /var/log/X* BTW, try as I mught I can see nothing in your message related to Fedora 10 64-bit Wired Network Problems. Looks like a hijack. poc I will have to check the graphics card. I think it is an ati card. It has always worked with the vesa driver. But I will check the .xsession-errors. What is weird is that sometimes F10 works although most of the time it doesn't. Yesterday I had been able to boot the live CD version but today it cannot find the root file system. This all started with installing F10 and then not being able to connect to a wired ethernet port using a static IP. Everything worked fine in F10. Now the networking works but I get no display. Rick B. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
On Thu, 2009-02-26 at 12:58 -0700, Robin Laing wrote:
Rick Bilonick wrote:
I installed F10 64-bit from the DVD iso on a 64-bit Intel 4-cpu
computer. I had problems getting the wired network connection to work on
network A UNTIL I realized that the network daemon was for some
reason turned off by default. Once I turned it on via services,
networking worked fine (using a static IP). (There is an annoying bug in
the F10 gui for networking - the net mask gets changed to the gateway ip
which of course screws up networking - this appears to be fixed once you
upgrade the system but I had to manually fix the eth0 script to get the
netmask to the correct value.)
Now I've installed the same DVD iso on a dual 64-bit AMD Opteron system
that previously had run F8 (networking worked fine on network A). I've
made sure network is on. I've manually configured the eth0 script to
avoid the buggy network gui netmask problem. I can ping the gateway on
network A. For some reason I cannot ping the DNS on this network. I
can connect to my home computer using its IP address using ssh. But I
cannot view web pages using the URL's. I switched to a different
ethernet port on a different network B with different fixed IP and
DNS that I know works (I use it for my F8 laptop every day) and although
I can ping the gateway and DNS, I still cannot view web pages. I just
now hooked my Ubuntu 8.10 laptop to network A and it connects
flawlessly and I can view web pages so I know the port works - both
ports on networks A and B work fine. But I cannot get the F10 AMD
computer to connect to either network and view web pages (I do as I said
get some connection using IP addresses and ssh).
Any ideas on what is wrong? This is very frustrating. If I could get a
network connection I could upgrade the computer but I can't get to
square one.
P.S. I've looked at the eth0 script, the resolv.conf and hosts files and
everything looks fine. I've tried turning different things on and off
(like IPv6 and peer) but nothing makes a difference. I'm using DNS1,
DNS2, and DNS3 in the eth0 script and these appear appropriately in the
resolv.conf file.
I have never had this much trouble getting a wired network connection -
it almost always works by default.
Rick B.
My rule for this issue is to remove network manager.
On two desktop computers with static IP addresses was.
-install F10 from DVD.
-apply all the updates.
-install yumex. {I like it better than packagekit}
-install system-config-network
-turn off networkmanager
-remove networkmanager
-run system-config-network
-enter in settings
-restart networking
-ensure networking is running properly
-test by rebooting.
As others have suggested, check /etc/sysconfig/network*
as well as /etc/resolve.conf
--
Robin Laing
The network problem has been resolved. Now networking works but after
having to reboot because the keyboard locked up, now F10 refuses to boot
to a graphic display. I can get to a shell and install updates via yum.
Rick B.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, 2009-02-26 at 10:01 -0900, Jeff Spaleta wrote: On Thu, Feb 26, 2009 at 9:56 AM, Rick Bilonick r...@nauticom.net wrote: I'm completely stumped. What else should I check? The kernel is 2.6.27.15-170.2.24.fc10.x86_64. If I type startx I get No address associated with name. It says to check /usr/bin/X but this does not exist. /usr/bin/X doesn't exist? What does the output of rpm -qf /usr/bin/X say? What does the output of rpm -q rpm -q xorg-x11-server-Xorg say? -jef I had to install this. I had problems trying to update after the install. yum kept complaining about about a conflict so I had to remove all the kde packages - it must have removed too much. Now it boots up with an X type login screen - but it won't let me login. Rick B. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, Feb 26, 2009 at 11:57 AM, Rick Bilonick r...@nauticom.net wrote: I had to install this. I had problems trying to update after the install. yum kept complaining about about a conflict so I had to remove all the kde packages - it must have removed too much. Now it boots up with an X type login screen - but it won't let me login. You did what? you did a yum remove that removed the xserver itself! I'm going to give you a second to think about the implications of that action, and how far reaching that action could have been. What else did that remove. We can't tell you. And it certainly explains your problem. Now you need to go check your yum transaction log and see exactly all the packages you removed. Assuming you did this recently enough there should be a record of all the packages removed in /var/log/yum.log -jef -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, Feb 26, 2009 at 11:57 AM, Rick Bilonick r...@nauticom.net wrote: I had to install this. And please, don't short-circuit the diagnose like that. When I ask for specific command output, its not a rhetorical question. I want that command output, I don't want you to interpret or act on it. I don't want you to go and try to fix anything on your own. I need system tool output because the system tool output to diagnose what your system state is. Human language isn't going to cut it, human interpretation of the output isnt going to cut it. To get an accurate picture, I need system tool output exactly as I have requested. You need to understand, in a lot of cases like this, its a local user action initiated issue. People will get into these sort of messes because they don't understand the implications of their actions. That's OKAYmistakes happen...people aren't perfect..the computer tools they produce aren't perfect...the only things which intuitively understand computers are other computers...and skynet isn't here yet to take all the frustration away. As soon as you get to the point where your system is messed up enough where you can't figure out how to fix it on your own and need to ask for help.. you need to follow the instructions you are given. Every subsequent action you take could further distort the state of your system causing more problems simply because you don't know what you are doing. You have to be able to admit that to yourself and be willing to answer questions asked of you and provide the information explicitly asked for. What I and other helpers need you to do is to be patient and to not screw around with it while dagnose your system while its in a known but broken state. It's hard enough remotely diagnosing a system even when the system state is static. The more actions you do on your own, and the fewer questions you answer, the harder it is for us..the people taking time out of our day..to help you unbreak your system. -jef -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems - New Problem
On Thu, 2009-02-26 at 12:23 -0900, Jeff Spaleta wrote: On Thu, Feb 26, 2009 at 11:57 AM, Rick Bilonick r...@nauticom.net wrote: I had to install this. And please, don't short-circuit the diagnose like that. When I ask for specific command output, its not a rhetorical question. I want that command output, I don't want you to interpret or act on it. I don't want you to go and try to fix anything on your own. I need system tool output because the system tool output to diagnose what your system state is. Human language isn't going to cut it, human interpretation of the output isnt going to cut it. To get an accurate picture, I need system tool output exactly as I have requested. You need to understand, in a lot of cases like this, its a local user action initiated issue. People will get into these sort of messes because they don't understand the implications of their actions. That's OKAYmistakes happen...people aren't perfect..the computer tools they produce aren't perfect...the only things which intuitively understand computers are other computers...and skynet isn't here yet to take all the frustration away. As soon as you get to the point where your system is messed up enough where you can't figure out how to fix it on your own and need to ask for help.. you need to follow the instructions you are given. Every subsequent action you take could further distort the state of your system causing more problems simply because you don't know what you are doing. You have to be able to admit that to yourself and be willing to answer questions asked of you and provide the information explicitly asked for. What I and other helpers need you to do is to be patient and to not screw around with it while dagnose your system while its in a known but broken state. It's hard enough remotely diagnosing a system even when the system state is static. The more actions you do on your own, and the fewer questions you answer, the harder it is for us..the people taking time out of our day..to help you unbreak your system. -jef My bad. My very bad. I was in a hurry and annoyed that a simple update after installing F10 always crapped out due to a conflict. I'm not sure why there would be any conflicts on a newly installed F10. Regardless, I'll never blindly remove software again. I re-installed xorg and gnome and that has fixed the problem. Thanks for your help. Rick B. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
On Wed, Feb 25, 2009 at 9:41 AM, Rick Bilonick r...@nauticom.net wrote: I installed F10 64-bit from the DVD iso on a 64-bit Intel 4-cpu computer. I had problems getting the wired network connection to work on network A UNTIL I realized that the network daemon was for some reason turned off by default. Once I turned it on via services, networking worked fine (using a static IP). (There is an annoying bug in the F10 gui for networking - the net mask gets changed to the gateway ip which of course screws up networking - this appears to be fixed once you upgrade the system but I had to manually fix the eth0 script to get the netmask to the correct value.) Now I've installed the same DVD iso on a dual 64-bit AMD Opteron system that previously had run F8 (networking worked fine on network A). I've made sure network is on. I've manually configured the eth0 script to avoid the buggy network gui netmask problem. I can ping the gateway on network A. For some reason I cannot ping the DNS on this network. I can connect to my home computer using its IP address using ssh. But I cannot view web pages using the URL's. I switched to a different ethernet port on a different network B with different fixed IP and DNS that I know works (I use it for my F8 laptop every day) and although I can ping the gateway and DNS, I still cannot view web pages. I just now hooked my Ubuntu 8.10 laptop to network A and it connects flawlessly and I can view web pages so I know the port works - both ports on networks A and B work fine. But I cannot get the F10 AMD computer to connect to either network and view web pages (I do as I said get some connection using IP addresses and ssh). Any ideas on what is wrong? This is very frustrating. If I could get a network connection I could upgrade the computer but I can't get to square one. P.S. I've looked at the eth0 script, the resolv.conf and hosts files and everything looks fine. I've tried turning different things on and off (like IPv6 and peer) but nothing makes a difference. I'm using DNS1, DNS2, and DNS3 in the eth0 script and these appear appropriately in the resolv.conf file. I have never had this much trouble getting a wired network connection - it almost always works by default. Rick B. Have you turned off NetworkManager? chkconfig --list | grep Manager NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off You either run the network service or NetworkManager...there can be only one ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
On Wed, 2009-02-25 at 10:24 -0800, Aldo Foot wrote: Have you turned off NetworkManager? chkconfig --list | grep Manager NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off You either run the network service or NetworkManager...there can be only one ~af The one detail I forgot to mention. Yes, I turned off NetworkManager. NetworkManager doesn't work well with wired networks (at least, it hasn't in the recent past). Any other idea on what could be wrong with F10 networking? Rick B. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
On Wednesday 25 February 2009 19:00:46 Rick Bilonick wrote: On Wed, 2009-02-25 at 10:24 -0800, Aldo Foot wrote: Have you turned off NetworkManager? chkconfig --list | grep Manager NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off You either run the network service or NetworkManager...there can be only one ~af The one detail I forgot to mention. Yes, I turned off NetworkManager. NetworkManager doesn't work well with wired networks (at least, it hasn't in the recent past). Any other idea on what could be wrong with F10 networking? Rick B. I had a couple of issues while testing F10 (abandoned for other reasons). Unless you rebooted, you need to make sure you actually *stop* NM as well as disable it with chkconfig. You also need to explicitly start the network service, if you didn't already, as without a reboot it won't get run just because you enable it. Check that you have ONBOOT=yes in the ifcfg-eth0 file. Just for laughs, make sure you actually have an /etc/resolv.conf that mentions the correct nameserver, ... -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
On Wed, 25 Feb 2009 14:00:46 -0500 Rick Bilonick wrote: Any other idea on what could be wrong with F10 networking? Before you get a chance to turn it off, NetworkManager often screws up the /etc/resolv.conf file so that you can't lookup any names, you might want to check it. It also often screws up the ifcfg-eth0 script to add incorrect DNS info so that even the network service will continue to screw up your resolv.conf file, you might want to add PEERDNS=OFF to the eth0 script (or is it PEERDNS=NO) something like that. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
On Wed, 2009-02-25 at 14:17 -0500, Tom Horsley wrote: On Wed, 25 Feb 2009 14:00:46 -0500 Rick Bilonick wrote: Any other idea on what could be wrong with F10 networking? Before you get a chance to turn it off, NetworkManager often screws up the /etc/resolv.conf file so that you can't lookup any names, you might want to check it. It also often screws up the ifcfg-eth0 script to add incorrect DNS info so that even the network service will continue to screw up your resolv.conf file, you might want to add PEERDNS=OFF to the eth0 script (or is it PEERDNS=NO) something like that. Thanks very much for everyone's suggestions. I will have to admit the behavior of this system is very bizarre. I tried booting the 32 bit live CD just to see if I could configure the network. (I had previously rebooted but it had not fixed the problems.) I had originally tried the live CD which had booted and had a working X display by default. (When I installed the 64-bit I had to use linux vesa to get a usable display for installing.) Now when I try the live CD I get a corrupted display that is unusable. I tried a bunch of kernel parameters to no avail to the point that it would just hang. At one point it could not find the root file system on the CD. So then I went back to just rebooting F10 from the hard drive. This also failed! I tried turning the system completely off (several times). So I finally got F10 64-bit to boot from the hard drive to which it had been installed yesterday by using rescue on the install DVD. It asked me at some point if I wanted to put in network info so I did. Once I got out of rescue and it rebooted, miracle of miracles it rebooted, had a useable display, and NOW the networking is working - I can view web pages and update and install packages. There may be some hardware problem with this 4+ years-old system or some hardware quirks that I need to totally turn the system off before re-booting. I guess the comments about enabling/disabling NetworkManager and network not being enough are appropriate also. Rick B. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Fedora 10 64-bit Wired Network Problems
On Wed, 2009-02-25 at 18:33 -0430, Patrick O'Callaghan wrote: On Wed, 2009-02-25 at 14:00 -0500, Rick Bilonick wrote: On Wed, 2009-02-25 at 10:24 -0800, Aldo Foot wrote: Have you turned off NetworkManager? chkconfig --list | grep Manager NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off You either run the network service or NetworkManager...there can be only one ~af The one detail I forgot to mention. Yes, I turned off NetworkManager. NetworkManager doesn't work well with wired networks (at least, it hasn't in the recent past). I've used NM with a wired network with zero problems since before F10 was released. Perhaps you meant to say doesn't work well with static IP addresses, which I've seen several comments about here. poc Yes that is what I meant. NM works OK with wired DHCP. Rick B. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
