LTSP Lucid doesn't work with etherboot clients

[domenec]

Until now I had a Debian Lenny box working fine as an LTSP server.
Thin clients connected via etherboot (booting with a diskette) and loaded nbi.img from the server, or via PXE if they could be able.
The server is Pertium Core Duo 7300. DHCP is provided by another server in the same network.

I installed in the same computer a Lucid Lynx in the standard way (as a standalone machine). Afther that, I did
- sudo aptitude install ltsp-server openssh-server
- sudo dpkg-reconfigure -plow nbd -server (to create the config file, with the exports and ports)
- sudo ltsp-build-client
- sudo ltsp-update-sshkeys
- sudo ltsp-update-image

All these steps were done fine, without any error message.

The installation works fine with PXE clients, such as laptops, but it doesn't work with etherboot clients, booting from floppies (I tried some of them, that were previously working). Thin clients boot, find DHCP server, get an IP address, get nbi.img (a lot of dots appear, as usual), the word "done" appear after the dots, and that's all. It hangs up. No more messages. No logs anywhere. I have not any clue to know what is going on.

The worst of all is that it doesn't give any clues: no messages, no logs, and I couldn't find anything similar by googling. Except Launchpad Question 118802, which I think that describes the same problem in another environment.

Thanks in advance

[ty debelser (tydb)]

I have exactly the same issue with my system at home. Worked fine with Hardy ltsp but when I installed 10.10 my diskless workstation terminal no longer boots. Does do the "..............done" and then sits forever. I can boot either of my laptops as terminals using pxe so I believe ltsp is Ok, just a problem with etherboot.
this is preventing us from updating Ubuntu at work as there we run a dozen Diskless workstations terminals, all with etherboot.

Any solutions????

[domenec (darcalis)]

The workaround that I found is to boot clients with a CDROM burnt with the
gpxe-1.0.1-gpxe.iso image.

I haven't tried the .dsk image (foo floppy) of this gpxe version

Domènec Arcalís

2010/12/29 ty debelser <email address hidden>

> I have exactly the same issue with my system at home. Worked fine with
> Hardy ltsp but when I installed 10.10 my diskless workstation terminal no
> longer boots. Does do the "..............done" and then sits forever. I
> can boot either of my laptops as terminals using pxe so I believe ltsp is
> Ok, just a problem with etherboot.
> this is preventing us from updating Ubuntu at work as there we run a dozen
> Diskless workstations terminals, all with etherboot.
>
> Any solutions????
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/619204
>
> Title:
> LTSP Lucid doesn't work with etherboot clients
>
> Status in Ubuntu:
> New
>
> Bug description:
> Until now I had a Debian Lenny box working fine as an LTSP server.
> Thin clients connected via etherboot (booting with a diskette) and loaded
> nbi.img from the server, or via PXE if they could be able.
> The server is Pertium Core Duo 7300. DHCP is provided by another server in
> the same network.
>
> I installed in the same computer a Lucid Lynx in the standard way (as a
> standalone machine). Afther that, I did
> - sudo aptitude install ltsp-server openssh-server
> - sudo dpkg-reconfigure -plow nbd -server (to create the config file, with
> the exports and ports)
> - sudo ltsp-build-client
> - sudo ltsp-update-sshkeys
> - sudo ltsp-update-image
>
> All these steps were done fine, without any error message.
>
> The installation works fine with PXE clients, such as laptops, but it
> doesn't work with etherboot clients, booting from floppies (I tried some of
> them, that were previously working). Thin clients boot, find DHCP server,
> get an IP address, get nbi.img (a lot of dots appear, as usual), the word
> "done" appear after the dots, and that's all. It hangs up. No more messages.
> No logs anywhere. I have not any clue to know what is going on.
>
> The worst of all is that it doesn't give any clues: no messages, no logs,
> and I couldn't find anything similar by googling. Except Launchpad Question
> 118802, which I think that describes the same problem in another
> environment.
>
> Thanks in advance
>
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+bug/619204/+subscribe
>