Just an update on this one.

using ltsp-4.1 and kernel vmlinuz-2.4.26-ltsp-3 I am able to get to the 
end of

"rc.sysinit completed, switching to multi-session mode"
 followed by the now predictable

Wake up event 0x80000b
eth0: Setting full-duplex based on negotiated link capability
Wake up event 0x80000b
eth0: Setting full-duplex based on negotiated link capability
Wake up event 0x80000b
eth0: Setting full-duplex based on negotiated link capability

ad infinitum

I see that there is a WOL bug in the natsemi driver so i booted damn 
small linux and used ethtool to set

ethtool -s eth0 wol d

but upon reflashing with etherboot image i still get the errors above.

Has anyone got these working/overcome the Wake on Lan issue?

Bails

bails wrote:

>Hi all
>
>I recently bought a couple of T20's from ebay and I'm attmpting to use 
>them with ltsp.
>
>I followed this to get grub + etherboot onto the boxes
>
>http://www.pug.org/index.php/Thin_Client_evo_T20
>
>the problem i am having now is that the kernel is downloaded and 
>modprobes the nsc driver does the pivot root and then hangs with
>
>2.6.9-ltsp-1
>
>Running /sbin/init
>Wake up event 0x80000b
>eth0: Setting full-duplex based on negotiated link capability
>eth0: Setting full-duplex based on negotiated link capability
>eth0: Setting full-duplex based on negotiated link capability
>eth0: Setting full-duplex based on negotiated link capability
>eth0: Setting full-duplex based on negotiated link capability
>eth0: Setting full-duplex based on negotiated link capability
>for ever :(
>
>2.4.24-ltsp-1
>
>Running /sbin/init enter runlevel
>Wake up event 0x80000b
>eth0: Setting full-duplex based on negotiated link capability
>Wake up event 0x80000b
>eth0: Setting full-duplex based on negotiated link capability
>Wake up event 0x80000b
>eth0: Setting full-duplex based on negotiated link capability
>Wake up event 0x80000b
>eth0: Setting full-duplex based on negotiated link capability
>Wake up event 0x80000b
>eth0: Setting full-duplex based on negotiated link capability
>Wake up event 0x80000b
>eth0: Setting full-duplex based on negotiated link capability
>for ever :(
>
>I should make you aware that there is no keyboard present at this point 
>in the boot process as the T20 only has usb keyboard/mouse
>
>Any ideas?
>
>Thanks
>
>Bails
>
>
>
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_____________________________________________________________________
>Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
>For additional LTSP help,   try #ltsp channel on irc.freenode.net
>
>  
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to