[ubuntu-za] Slow Ubuntu Installation

[Tom Bamford]

Hi Charl

This is sounding like a network issue - among other distros, recent Ubuntus
exhibit laggy behaviour when the network is not fully reachable and it
happens during boot time, login time and when running certain commands such
as sudo.

Your attached dmesg.0 indicates your machine is waiting for eth0 to come up
before continuing to boot. Your machine is loading the r8169 driver, the
hardware for which some people seem to have trouble with autonegotiation -
potential solution here:
http://forums.fedoraforum.org/showthread.php?t=250807

If you switch off autoneg, then make sure that your switch and your card
are both running with the same speed and duplex else your network
performance will drop through the floor.

Regards
Tom



On 30 January 2013 08:53, Charl Wentzel <charl.wentzel at vodamail.co.za>wrote:

> On 29/01/2013 22:46, Lee Sharp wrote:
>
>> On 01/29/2013 02:38 PM, Charl Wentzel wrote:
>>
>>> On 29/01/2013 19:32, Lee Sharp wrote:
>>>
>>>> How are you mounting the Compact Flash? How is it referred to in the
>>>> BIOS? This can often be a problem, as it can detect wrong on install...
>>>>
>>> The Wafer has a built-in CF card slot. It is specifically designed for
>>> the purpose of acting as a hard drive.
>>>
>>> In the BIOS it is shown as "PATA - Innodisk", with Innodisk being the
>>> manfucturer.
>>>
>>> PS: this is Industrial CompactFlash, not the normal consumer type
>>>
>>
>> Some CF media has odd architecture, or reports it oddly. You mght try a
>> different CF card... Or, turn off the nic in the BIOS and see if that
>> changes things.
>>
> Thanks, Lee.
>
> I tried two different CF cards yesterday, an Industrial 32GB CF card and
> an older Sandisk 8GB CF card, both gave the exact same result. So the
> problem is not the physical CF cards.
>
> The BIOS does not allow me to disable the NICs (there are two). Not sure
> how to bypass this.
>
> I noticed something else that is odd though. Once I booted the device (and
> waited to get logged in), I started "top" in that terminal. Nothing was
> "hogging" the processor.
> I then logged in on another virtual terminal and watched what happened in
> top. The login in process took just as long and serveral processes were
> fired up during the login; "login", "bash" and a few others in between. In
> each case the CPU usage by that process went to 100% while it was running.
> Nothing seemed particularly odd except for the duration. Why would "bash"
> run for 20 seconds at 100% CPU usage before giving me a login prompt?
> I tried a few other commands such as "ls" and "nano". Although slow, they
> started/finished quite quickly. "sudo" was another command that took a long
> time to execute.
>
> So I don't get it. It seems that the applications themselves execute
> slowly despite the fact that they are running at 100% CPU. If they were
> waiting for something else then they wouldn't consume 100% CPU. There also
> doesn't seem to be a hidden processor hog.
>
> Any fresh ideas?
>
>
> --
> ubuntu-za mailing list
> ubuntu-za at lists.ubuntu.com
> https://lists.ubuntu.com/**mailman/listinfo/ubuntu-za<https://lists.ubuntu.com/mailman/listinfo/ubuntu-za>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-za/attachments/20130130/9f1bb446/attachment.html>