Experience + a problem on 10.04 Installation with Diskless MD and Kernel upgrade

[Roman]

Hi!
I thought I will post some experience I got in the last weeks with 8.10 and 10.04.
Also there is one issue that I can not install any MD running Diskless - booting from Core.
But first I want to share some personal experience and comethen to my question at the end.

I started with 8.10 which was running very nice. I had big troubles in getting my AFA9015 DVB-T Stick be recognized.
For this I played around with v4l drivers and lernel upgrades... it simply did not work. What I can say from my side that a kernel upgrade from the default LMCE 8.10 Kernel (I guoess it is 2.6.27) to 2.6.32 or 2.6.38 does not work - I mean the upgrade works but LMCE is not working anymore.

So I decided to go to LMCE10.04 - but the DVB-T Stick still was not working. So I decided right on the beginning to upgrade to Kernel 2.6.38. The result was an X-Error but installing again the last NVIDIA driver brought me back to the LMCE Dashboard. So a kernel upgrade in 10.04 works also with a working LMCE Dashboard - also just a experience from my side.

My new DVB-C external Device Techno Trend Connect CT-3650-CI http://www.tt-pc.com/2916/TT-connect__CT-3650_CI.html is now also recognized BUT just the DVB-C Receiver!!! The DVB-T Receiver of this Device seems not to be supported by LMCE 10.04 or Linux in general (just an assumption I can not say for sure). I now have 2 adapters in the DVB Directory - One for the AFA9015 DVB-T Stick and one for the TT connect CT-3650CI. The DVB-T Stick is running perfect now, the DVB-C I can not test because it still will take some weeks to get DVB-C in my house.

Now comes the caveat for the MD Diskless boot part.
With LMCE 8.10 I just switched on a Client, told him to boot from the network and the rest was just watching until it was a ready MD onc my core.
Now with 10.04 it even does not boot on the first time. The HW gets an IP Adress, tries to boot, but then I get an error that the kernel was not found. But in the "default" directory - where normaly a new HW boots in, there is a vmlinuz file ...
So my question to this part:

-) Has anybody the same experience that in LMCE 10.04 a new MD does not boot from network initially?
-) Is it possible that the Kernel upgrade is responsible for this behaviour?
-) Can anybody help me with troubleshooting? What can I do in this situation?

Perhaps someone can reply on my questions!?

Especially to the new people here do not hesitate to ask details on my experience due to the fact that I am also a beginner and already spent hours on troubleshooting and asking questions here in this forum ;-)

Very best regards
Roman

[coley]

hi,
Did you run /usr/pluto/bin/Diskless_CreateTBZ.sh on your core before trying to boot the MD?
This will create the default boot image for the Media Directors.

-Coley.

[merkur2k]

check the permissions on /tftpboot/default/vmlinuz
i noticed on my install the other day that it was not readable by the tftp daemon. it should be set to 644 like the initrd.
if this is the case with yours as well, then i guess we have a bug.

[Roman]

@Coley:Yes, I did this command of course. I already had the diskless MDs running in 8.10.

@Merkur2k: Thank you for this hint. I will be able to look at this on Wednesday. I will have a look on this and will try the solution if I hit this point. I will post an update here in anyway!

Cheers mate!

[Roman]

Hi Merkur2k!
Your hint was 100% the solution of my profile!

The Permission of /tftpboot/default/vmlinuz was 600
I changed it to 644 and ... the new HW was able to boot the default image and so i created successful a diskless MD.
Please take this response as positive direction for the possible bug you mentioned.

Thank you very much for your hint! Never found that on my own!
best regards
Roman