This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on
the current status under
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I am assigning this bug to the 'ubuntu-kernel-team' per their bug
policy. For future reference you can learn more about their bug policy
at https://wiki.ubuntu.com/KernelTeamBugPolicies .
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team
I think you should try different values of MTU around and below 1500,
also open an Ethereal (wireshark? can't remember its new name) and try
to check what is going on with your packets. As this is a computer lab
and you probably must fix it, (I don't know if this NIC is so badly
designed or is so
Hi!
In our computer lab, I have installed edubuntu 7.10 on 13 machines
with Foxconn motherboard 622MX.
This motherboard uses the same network controller and I had the same
problem which I fixed by changing the mtu to 1492.
However, I would like to report that three out of 13 machines were still
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None = linux-source-2.6.22
--
[GUTSY] SiS 190 onboard NIC problems
https://bugs.launchpad.net/bugs/137630
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Hi!
Thanks for the bugreport!
I think we can confirm this bug and the workaround working ([1] [2]).
Now as a quick fix, i don't know if there is per-driver scripts in network
scripts so that we can change the MTU...
The bug itself would be interesting to investigate... The only probable
