#964: Control Panel/Network Configuration - serious issues!
------------------------------+----------------------------
Reporter: geostar | Owner: kenmoore
Type: System Defect | Status: closed
Priority: critical | Milestone:
Component: Network Manager | Version: 10.0-RELEASE
Resolution: worksforme | Keywords: networking lan
------------------------------+----------------------------
Changes (by kenmoore):
* status: assigned => closed
* resolution: => worksforme
Comment:
This was actually a lot more helpful than you were probably expecting...
:-)
I think this narrows down the issue(s) specifically to a hardware/driver
issue. This seems to make the most sense because of the following things
you mentioned:
1) The GUI only hangs when trying to load the msk device information or
change the msk device configuration (not the config file, but
restarting/accessing the device with the new configuration).
2) Even with correct configuration settings, you msk device still does not
function properly (dropping connection).
3) This seems to correspond to the "watchdog timeout" errors that you
noticed in your initial report.
4) This seems to explain why it works perfectly fine on my systems but not
on yours (since I do not have an msk network device).
I did find a bit of information about the "msk" family of devices just
from doing some google searches on it, and apparently there are many
variants of the same supported msk device chipsets that can cause
different levels of support with the FreeBSD msk driver. So while your
particular device is listed as supported, it might actually be one of
those variants and is having issues because of it.
The main "solutions" that I found were this:
1) Get a different network card. This was the most common answer that I
found, with a lot of people saying they just bought a cheap Intel (em) or
Realtek (re) card and it worked fine with that new card.
2) Check your network cable. A few people said that replacing the network
cable connected to their card fixed the issue (but I don't think this is
that likely for you since you could ping the router just fine).
3) Contact the FreeBSD driver developers mailing list[1] and work with one
of them to find the issue and get it fixed. This would be the most helpful
to the community, but I understand if you don't have the time.
In the meantime, I am going to close this ticket as "works for me" since
it specifically deals with the GUI utility.
Thank you for all your time and energy in trying to work out what was
going on with your system.
[1] http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
--
Ticket URL: <http://trac.pcbsd.org/ticket/964#comment:12>
PC-BSD <http://trac.pcbsd.org>
PC-BSD Project Management