Russell Smith <[EMAIL PROTECTED]> writes:
> Your waiting for the driver to initialize an get it's head together.
> It takes this amount of time for the Broadcom card to get the Link
> up and running properly. the Driver RX/TX lines come up after the
> DHCP requests. At least that's what I'm waiting for. (I'll be
> testing again in about 60 minutes.)
Fair enough. It's the arbitrary timeout that bothers me. It would be
nice if insmod/modprobe would not exit until the driver was fully
initialized. I may send a message to the linux-kernel list this week
asking about this.
> I'll time, but something like 30 minutes to do the linux based dos
> copy. 10Mbit Switched Network. Could be the NetCard, I hate
> Broadcom already. Win2k is the OS, slip streamed SP4.
I have only ever used 100Mbit, and never Broadcom.
I think it is more likely to be the driver than the hardware.
(Although I suppose it is still Broadcom's fault, since they refuse to
release specs for their hardware, which the Linux folks need to write
a good driver.)
> install.pl is the one from the 4.1 Release. using fdisk_cmds from
> site\unattend.txt
>
> [_meta]
> fdisk_cmds="fdisk /clear 1;fdisk /prio:2000;fdisk /activate:1"
Something must be wrong with FAT16 creation. I will look into it this
week. Meanwhile, could you try this instead:
fdisk /clear 1;fdisk /pri:4000;fdisk /activate:1
...and see if it works better?
> PS More throughout the day as I test these things.
"Day"? Oh, right, you're on the other side of the planet...
- Pat
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
unattended-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-devel
