![]() |
|
[LINUX] HOW-TO create a XBMC server for diskless PXE network booting clients - Printable Version +- XBMC Community Forum (http://forum.xbmc.org) +-- Forum: Announcements, Info, and General Discussion (/forumdisplay.php?fid=85) +--- Forum: Tips, tricks, and step by step guides (/forumdisplay.php?fid=110) +--- Thread: [LINUX] HOW-TO create a XBMC server for diskless PXE network booting clients (/showthread.php?tid=83840) |
- JohnPollaert - 2011-01-04 22:06 Just before the Unable to locate configuration file message, I got a message with TFTP prefix: /xbmc-netboot/ So I think that wouln't the problem. But to be sure i've added the path to the file. But still the same message. ![]() I also found the folloing in daemon.log: Code: Jan 4 20:23:49 john-MS-7596 in.tftpd[2247]: tftp: client does not accept options- opdenkamp - 2011-01-04 22:47 can you access the file from another machine using a tftp client supplying the same path as your diskless installation does (or should do)? - RavenDK - 2011-01-04 23:04 Hey, Thanks for this really nice thing, but I'm having trouble getting it to run on a HTPC with a ATI graphicscard (onboard HD3200). I could see in the Xorg.0.log, that it didn't find ATI, VESA and a third module, can't remember the name of it. I discovered by googleling around that I can fix this by installing the fglrx package. Finally XBMC started fine, but only the first time. The second time I got an OpenGL error (XBMC needs hardware accelerated OpenGL rendering. Install a appropriate graphics driver). By trial and error I discovered that, if I remove the folder in the overlay directory for the specific HTPC I could start it again, but again only the first time. So apparently some settings are stored there, which is causing the error, but I can't find out what. I get this error when I start the XBMC for the second time in the Xorg.0.log: Code: xbmc@xbmc-diskless:~$ cat /var/log/Xorg.0.log |grep EEDo you have any ideas how to solve this. I'm quite new at this linux thing, so please don't use to many linuxgeek words Thanks - JohnPollaert - 2011-01-04 23:24 dushmaniac Wrote:can you access the file from another machine using a tftp client supplying the same path as your diskless installation does (or should do)? I have never used TFTP before. I have installed the TFTP client on windows vista. What command do I have to execute to do that? When I try: TFTP 192.168.0.10 GET initrd.img I get a time-out error. - opdenkamp - 2011-01-05 02:29 @JohnPollaert: it looks like your diskless client can reach the server, or you wouldn't see any log entries. it should be something like Code: TFTP 192.168.0.10 GET /xbmc-netboot/initrd.img@RavenDK: stuff like that isn't really easy to do yourself if you don't know anything about linux as you stated in your post. you'd have to install a package in the image. if someone can tell me what the package is that is needed for those cards, I'll include it. - JohnPollaert - 2011-01-05 09:22 The windows firewall was in the way. Now Code: TFTP 192.168.0.10 GET initrd.imgAnd: Code: TFTP 192.168.0.10 GET /xbmc-netboot/initrd.img- opdenkamp - 2011-01-05 13:04 I assume you verified that the file is present on that server in /var/lib/tftpboot/xbmc-netboot/initrd.img ? are you running tftpd-hpa? if not, install it. then open /etc/default/tftpd-hpa and add "-v" to the options. restart the daemon with /etc/init.d/tftpd-hpa restart now try to access the file again from your diskless client or windows machine and have a look at the log. - JohnPollaert - 2011-01-05 21:22 Thank you! That did it. After adding the -v option I was able to see in the log that all the needed files where in the /var/lib/tftpboot/ folder, and not in /var/lib/tftpboot/xbmc-netboot. After copying the files over to the correct location, it started working! Thanks for your help! - JohnPollaert - 2011-01-06 09:29 One of my clients is an Acer Revo 3600. It is having the exact same issue as drefas has. Does anyone has a solution for this problem? drefas Wrote:Thank you for a great product! - opdenkamp - 2011-01-06 13:55 looks like an issue with the network driver or the udhcp script. adding a sleep before calling udhcp might help. I'll add a boot option so you can configure a sleep time before calling udhcp. |