Sorry. It did it again. On Mon, Jan 3, 2011 at 4:54 PM, Russel Caldwell <[email protected]> wrote:
> Sorry in the delay of the reply. I've been preoccupied with getting ready > for school. > > On Fri, Dec 31, 2010 at 5:24 PM, Charles Curley < > [email protected]> wrote: > >> Russ, please reply to the list so we keep a record in case anyone else >> see this problem, and also so other folks can pitch in if they know >> something I don't (a vast domain). Thanks >> >> > Sorry about that. I thought I just hit reply so I'm not sure what happened. > > >> > > >> > > Wired? Wireless? Chipset? Driver? Ubuntu 10.4 "good buddy" or Ubuntu >> > > 10.10 "mendacious meerkat"? >> > > >> > > I know wireless doesn't work. When I plugged it in to a wired >> > > connection it >> > didn't seem to work either. >> >> What do you mean by "didn't seem to work"? Did you get a link light on >> both the computer (assuming it has one; most do) and the switch? Did >> the link lights agree on the data rates (i.e. both agree that the >> connection is, say, gigabit)? >> >> If you got a link light, did you get an IP address? "ifconfig" for that. >> >> > The link light and the switch light don't go on. > > >> Hmmm, that's interesting. The wired and wireless stuff should not have >> hardware or drivers in common, which makes me wonder if Network Manager >> is crashing. Run this command now, and note the results: >> >> ps aux | grep Network >> >> My results look like: >> >> r...@dragon:~# ps aux | grep Network >> root 928 0.0 0.1 19252 1784 ? Ssl Dec26 1:10 >> NetworkManager >> root 2746 0.0 0.0 4012 744 pts/2 S+ 17:10 0:00 grep >> --color=auto Network >> root 22085 0.0 0.0 2296 468 ? S Dec28 0:00 >> /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf >> /var/run/dhclient-eth1.pid -lf >> /var/lib/dhcp3/dhclient-fd700ea5-35ec-44b1-ba7a-d200380ccce7-eth1.lease -cf >> /var/run/nm-dhclient-eth1.conf eth1 >> r...@dragon:~# >> >> This is the results when I run the command: > r...@rlc:~$ ps aux | grep Network > root 843 0.0 0.1 8640 3792 ? Ss 16:02 0:00 > NetworkManager > rlc 1513 0.0 0.0 3328 876 pts/0 S+ 16:10 0:00 grep > --color=auto Network > > > >> First you need to know the name of the device. "lspci" E.g. I have: >> >> The results are: > 10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] > Network Connection (rev 02) > 18:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit > Ethernet PCI Express (rev 02) > > >> "lsmod | less" will give you a complete list of all the modules you are >> running at the time. >> >> It looks like the wireless module is iwl3945. If I were to guess for the > ethernet, it would be i915. I did cut some of the results that looked to be > obviously something else such as sound and video. > Module Size Used by > nls_iso8859_1 3249 0 > nls_cp437 4919 0 > binfmt_misc 6587 1 > tpm_infineon 7745 0 > fbcon 35102 71 > arc4 1153 2 > pcmcia 30784 0 > iwl3945 68727 0 > i915 287458 3 > iwlcore 106050 1 iwl3945 > drm_kms_helper 29329 1 i915 > ppdev 5259 0 > tpm_tis 7422 0 > yenta_socket 20408 1 > rsrc_nonstatic 10015 1 yenta_socket > mac80211 205402 2 iwl3945,iwlcore > drm 162409 4 i915,drm_kms_helper > i2c_algo_bit 5028 1 i915 > parport_pc 25962 1 > tpm 13484 2 tpm_infineon,tpm_tis > tpm_bios 5266 1 tpm > pcmcia_core 32964 3 pcmcia,yenta_socket,rsrc_nonstatic > serio_raw 3978 0 > input_polldev 2482 1 lis3lv02d > led_class 2864 3 iwl3945,iwlcore,hp_accel > cfg80211 126528 3 iwl3945,iwlcore,mac80211 > intel_agp 24375 2 i915 > agpgart 31724 2 drm,intel_agp > lp 7028 0 > parport 32635 3 ppdev,parport_pc,lp > ohci1394 26950 0 > ieee1394 81181 1 ohci1394 > tg3 109324 0 > > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
