Messages

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

You can try with LMCE 8.10 which is quite stable but due to the old kernel there is not much HW support (axternal devices like DVB Receivers).
I played with 8.10 a while and now I am setting up a 10.04 system. in 10.04 you can upgrade the Kernel to at least 2.6.38 which already helps a lot.

Important is an NVIDIA GPU. Downloading the NVIDIA Firmware from the NVIDIA Website to install it on LMCE works straight forward. If you get to a blue consiole screen with "X error" ever mind, just (re)install the NVIDIA driver and it will work again.

Buy 2 intel NICs. I struggeled a while with my internal ones.... the intel NICs work from scratch.

Install LMCE with a screen plugged to DVI port. It saves you from strange behaviours and it works. Afterwards you can change to HDMI or leave it on DVI

Last but not least write down every step in troubleshooting to get a solution. It helps a lot in doing and saving time. I am nearly sure that you will install the system more than once from sratch ;-) Like I did ;-)

cheers
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!

Hi Coley!
I decided to install LMCE 10.04 from scratch.
When I did this I decided to upgrade the Kernel right at the beginning and did an upgrade to 2.6.38.
It worked pretty good, just had to re-install the NVIDIA driver and the LMCE Dashboard was up and running again.
with LMCE 10.04 I was able to install "linux-firmware-nonfree" and with 2.6.38 Kernel I have now a working DVB-T AFA9015 Stick.
My guess is that the Kernel 2.6.27 from 8.10 is simply "too old" !?
Just a guess.
best regards
Roman

To bring this thread to an end...
I purged LMCE 8.10 and installed LMCE 10.04 from scratch.
My experience is that 8.10 does not work with a 2.6.3x Kernel. The Dashboard of LMCE does not come up anymore.

Doing an Kernel upgrade on LMCE 10.04 works! I uprgraded to 2.6.38 because of my AFA9015 DVB-T Stick and after getting an X-Error - just installed again the latest NVIDIA driver - it again came up with the LMCE Dashboard and my DVB Hardware is now recognized and working properly.
I just have the problem that the MD does not Netboot anymore ... but I guess this is another story.
@Joakim: You stated in your last thread that I should take care about a "kernel configuration that is LMCE specific". How can I find this information?
thank you and best regards
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

Hi,
at least I changed the core to 10.04 because of HW support. Until now I can not say if the VESA stuff got better because I did not get any MD to self register at the new core. As soon as I have the DELL laptop with the VESA issue online again I will post the rensult here.
best regards
Roman

Hi Coley!
Unfortunately it did not work.
I followed exactly the guideline and during this no error happened. It simply does not do anything when I plug in the DVB-T Stick. I rebootet also the PC to be quite sure .... nothing.
I tool some logs and will paste them here - perhaps it is worth to look at.
best regards
Roman

Code Select Expand

sudo lsusb -v -s 4:3

Bus 004 Device 003: ID 15a4:9015
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
idVendor           0x15a4
idProduct          0x9015
bcdDevice            2.00
iManufacturer           1 Afatech
iProduct                2 DVB-T 2
iSerial                 3 010101010600001
bNumConfigurations      1
Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength           46
   bNumInterfaces          1
   bConfigurationValue     1
   iConfiguration          0
   bmAttributes         0x80
     (Bus Powered)
   MaxPower              500mA
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           4
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass      0
     bInterfaceProtocol      0
     iInterface              0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x81  EP 1 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x02  EP 2 OUT
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x84  EP 4 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x85  EP 5 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
Device Qualifier (for other device speed):
bLength                10
bDescriptorType         6
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
bNumConfigurations      1
Device Status:     0x0000
(Bus Powered)

Code Select Expand

dmesg:
793.720553] usb 4-3: new high speed USB device using ehci_hcd and address 3
[  793.862794] usb 4-3: configuration #1 chosen from 1 choice
[  793.958250] dvb_core: Unknown symbol __kmalloc_track_caller
[  793.960778] dvb_usb: Unknown symbol dvb_dmxdev_init
[  793.961695] dvb_usb: Unknown symbol dvb_register_adapter
[  793.962846] dvb_usb: Unknown symbol dvb_dmx_swfilter_204
[  793.963064] dvb_usb: Unknown symbol dvb_dmx_release
[  793.963514] dvb_usb: Unknown symbol dvb_net_init
[  793.963727] dvb_usb: Unknown symbol dvb_dmx_swfilter
[  793.963990] dvb_usb: Unknown symbol dvb_dmxdev_release
[  793.964338] dvb_usb: Unknown symbol dvb_frontend_detach
[  793.964727] dvb_usb: Unknown symbol dvb_net_release
[  793.964982] dvb_usb: Unknown symbol dvb_unregister_frontend
[  793.965565] dvb_usb: Unknown symbol dvb_register_frontend
[  793.965784] dvb_usb: Unknown symbol dvb_unregister_adapter
[  793.966002] dvb_usb: Unknown symbol dvb_dmx_init
[  793.969318] dvb_usb_af9015: Unknown symbol dvb_usb_device_init
[  793.969538] dvb_usb_af9015: Unknown symbol dvb_usb_device_exit

No, I had not the chance so far to test the description in the link.
I will do it later this evening and will post the result here.
Thanks again Coley,
best regards
Roman

It is again me for this topic.
I read the pages of the link you provided a little deeper.
There is often the link to a driver.
So I need a Driver and a firmware?
I followed another link (http://linuxtv.org/hg/~anttip/af9015/) which is mentioned very often in forums - to locate the driver but when I follow this link I get to a page where it not seems to get anything for DVB stuff.

Perhaps you can light my darkness a little again ;-)

thank you and best regards
Roman

Hi Coley!
Thank you for your reply!
I never did this and so your link looks like a good step-by-step description.
Hopefully this will lead to success - I will try this and will provide feedback.

very best regards
Roman

Hi Joakim!
What alternatives are available?
Sorry, but I am not that Linux Crack to know what to do now.
It seems that you have know how in this area so please get back to me with a proposal which I can try.
thank you and best regards
Roman

Hi Community!
I am still trying to get my DVB-T USB Stick (afa9015) up and running.
What I always read in different forums that I need to install "linux-firmware-nonfree".
I would like to install this package but doing "apt-get install linux-firmware-nonfree" brings an error due to the fact that this package is not available.
I have the original and unchanged sources.list on my Core.

Is there any way to install this package?
it would be wonderful if I get help here - if possible with a detailed step by step description.

Thank you very much and best regards
Roman

Hi Joakim!
That was exactly the point I need support for.
Upgrading thr kernel is definitely not the point but what happens with the LinuxMCE installation when upgrading KDE8.10 to Kernel 2.6.39 or 3.x for example.
Will LinuxMCE still work? What will happen to KDE8.10 itself?
Where can I find out what Kernel is LinuxMCE 8.10 compliant.
Thank you and best regards
Roman

I deleted the MD copletely and let it build from scratch. Of course with the guideline from the link to prevent the problem with fglrx.
I will try your last posting later this week and keep you informed what happened.
best regards
Roman