On 10/23/07, Philip Prindeville <[EMAIL PROTECTED]> wrote: > > That depends on how quickly Verizon's DHCP server responds... >
udhcpc will keep trying in the background. You should get an IP address eventually. > > Ok. Is there a fix for that? Nothing is broken... The RTC driver tries to set the system clock from the RTC but fails because the device node isn't there yet, which is fine because we do it later in the startup script with "hwclock". > Or is that a result of using modules? Has nothing to do with it. > > Really? I thought I did an "lsmod" when I booted up, and the module > hadn't yet loaded... Um, yeah... From the lmsensors init script: if `grep -q "astlinux=net5501" /proc/cmdline` then modprobe -q pc87360 init=2 fi As long as you have "astlinux=net5501" on the kernel command line from GRUB/runnix, it will automatically modprobe the correct module. > I'll double-check. Please do. > My GND looks good? ;-) No, it doesn't but you said "most". Don't be so dramatic! ;-) > Ok. It didn't seem that you could set options per-entry (like bootfile, > etc) but I'll double-check. The docs I sent explain how to do this but I see Darrick has already replied with some specific examples for you. -- Kristian Kielhofner ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
