eBox 2300 boots VERY slow with Ubuntu/LTSP-5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ltsp (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
The eBox e2300 thin client is a very cheap small thin client. Around $100 in large quantities. This unit is becoming very popular. The problem is, it boots VERY slowly in Ubuntu's LTSP on feisty.
I'm talking SLOW. With LTSP-4.2 installed on feisty, it boots in 41 seconds, all the way from hitting the power button, to getting a login prompt. That's pretty respectable. But, in feisty, it takes 4 minutes and 43 seconds to boot !!! That's 41 seconds vs 281 seconds.
A faster client, the T-1220 from DisklessWorksta
281 seconds isn't understandable, and people will be angry if they buy a classroom full of e2300's and it takes that long to boot. This will cause people to recommend k12ltsp over Edubuntu, because k12ltsp is still using LTSP-4.2.
LDM is a big part of the speed problem, but it's not the ONLY problem. If I set SCREEN_07 = startx, to use xdmcp, instead of LDM, it reduces the boot time considerably. From 281 seconds down to 171 seconds. That's still too slow.
Another speed issue is the amount of time it takes to log out, and get a login box to appear on the screen. when using XDMCP, with either LTSP-4.2 or LTSP-5, it takes only about 8-10 seconds. when using LDM, it takes 106 seconds. That's approaching 2 minutes to get a login screen after logging out. Even the faster workstation takes 28 seconds to get the login screen after logging out. Back on LTSP-4.2, we could boot a whole workstation in the same amount of time it takes just to re-launch LDM on ltsp-5.
I've tried not to complain too much about boot times between LTSP-4.2 and Ubuntu's LTSP, but I really believe that now it's a serious issue that will turn people away if we don't come up with a solution.
Changed in ltsp (Ubuntu): | |
assignee: | Oliver Grawert (ogra) → nobody |
Changed in ltsp (Ubuntu): | |
status: | Incomplete → Won't Fix |
could you also attach an xorg.conf from a running client and the snippets of teh servers syslog that are written by the client ?