>
>ага! Он самый! Realtek! Он же и на виндовой машине стоит однако
>та пашет как ни странно ) Слух а даже если 10
>- ведь это 10Мбит а у нас хабы и так 10мегабитные
>:)
одно могу сказать - из man rl взято
BUGS
Since outbound packets must be longword aligned, the transmit routine has
to copy an unaligned packet into an mbuf cluster buffer before transmis-
sion. The driver abuses the fact that the cluster buffer pool is allo-
cated at system startup time in a contiguous region starting at a page
boundary. Since cluster buffers are 2048 bytes, they are longword
aligned by definition. The driver probably should not be depending on
this characteristic.
The RealTek data sheets are of especially poor quality, and there is a
lot of information missing particularly concerning the receiver opera-
tion. One particularly important fact that the data sheets fail to men-
tion relates to the way in which the chip fills in the receive buffer.
When an interrupt is posted to signal that a frame has been received, it
is possible that another frame might be in the process of being copied
into the receive buffer while the driver is busy handling the first one.
If the driver manages to finish processing the first frame before the
chip is done DMAing the rest of the next frame, the driver may attempt to
process the next frame in the buffer before the chip has had a chance to
finish DMAing all of it.
The driver can check for an incomplete frame by inspecting the frame
length in the header preceding the actual packet data: an incomplete
frame will have the magic length of 0xFFF0. When the driver encounters
this value, it knows that it has finished processing all currently avail-
able packets. Neither this magic value nor its significance are docu-
mented anywhere in the RealTek data sheets.
----------
на винде производитель готовые дрова дает, а под unix дрова делают энтузиасты, поэтому если производитель не раскрывает документацию, то возникают проблемы.
Смени сетевуху.