Date: Wed, 4 Jul 2007 12:37:29 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: emre n/a <emre@uoregon.edu> Cc: freebsd-ppc@freebsd.org Subject: Re: gem0 problems with 6.2 Message-ID: <20070704033729.GD72486@cdnetworks.co.kr> In-Reply-To: <08B90B8B-8CA7-4624-BCDA-3886AE29FD2F@uoregon.edu> References: <6938E4E6-5A05-4793-BB99-4F2D33952561@uoregon.edu> <20070704012730.GC72486@cdnetworks.co.kr> <08B90B8B-8CA7-4624-BCDA-3886AE29FD2F@uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 03, 2007 at 07:40:05PM -0700, emre n/a wrote: > Hello, > > Thanks for the quick reply. I'm not sure what I did, but networking > is somewhat working, not smoothly however. > > I unplugged the cable, plugged it back in, and then manually ran > dhclient gem0 after reboot (after an unsuccessful configuration). I > got an IP address back and IPv6 configured itself fine as well. > > I put ifconfig_gem0="DHCP" instead of the static IP address into > rc.conf. Then I rebooted. dhclient tries to get an IP address at > boot-up but fails to get any offers, and ultimately gives up. It > then uses the 'recorded lease' IP address, and then everything > works....sometimes. It's very random and rarely works. > > I changed my rc.conf back to what it was (static IP config), and > added 'media 100baseTX' at the end. It seems that it might've fixed > the problem. I have no problem getting networking to work now, > however DHCP still remains problematic. Maybe it wasn't unable to > correctly determine the media type? See dmesg below. > > Take care > Thanks for feedback but what I really want is "verbosed boot message" instead of plain dmesg output. You can get the verbosed boot message by adding the following line to /boot/loader.conf. boot_verbose="1" -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070704033729.GD72486>