Problem with Nvidia Driver (API mismatch)

Too late. I updated and now I’m again stuck with the sad smiley face. Please keep me informed about any fixes concerning this in the new update. When is this update scheduled?

Best and thanks
Henry

At the end of the month.

But I will be discontinuing AppleTV support soon.

I will however put the platform in a state that allows it to stay alive for a while.

Cheers

Sam

Sorry to hear that. But thanks anyways for all the work you put into the project. I reckon this is also the reason why you discontinue the project. What do you recommend to use in a long-term perspective instead?

An Rpi3 or a Vero4k :wink:

Will the ATV support be dropped before or after the crystal card it going to work?

$DEITY, I hope the answer is after.

Hi,

Unfortunately I’m not really choosing to discontinue the AppleTV project. It’s more that I have no other option.

  • The device is ten years old and no longer meets the requirements for smooth GUI performance or playback. Content has become more demanding, and Kodi now requires beefier hardware for a smooth GUI alone.
  • It’s become extremely difficult to maintain:
    • Official Kodi support was dropped three years ago
    • Apple dropped support eight years ago
  • There are very few users on this platform; but it takes the most of my time to maintain

It upsets me to do this because AppleTV is where it all began for me. I kept it going for as long as possible (eight years after Apple discontinued support) and many years after Team XBMC / Kodi dropped support.

For the long term, I recommend Vero 4K. It will be supported for a minimum of five years; which is a long time for any device. If you like my work on AppleTV and want to keep supporting OSMC, then it’s a good choice. It will be an asounding upgrade coming from an Apple TV.

Realistically – I don’t want to ship you something that’s slow and can’t keep up with modern playback and GUI requirements. The source will still be there, and old Downloads will remain up for some time, but Kodi v18 will be a no go for Apple TV.

Best

Sam

1 Like

Awe. I haven’t had any major issues with my AT1. The issue with the sad face did occur but after I unplugged it then powered it back on and it basically fixed itself.

It won’t stop working when we discontinue support; it will just stop receiving updates.

1 Like

After reinstalling OSMC on my ATV some days ago, my ATV just auto-updated itself into a “sad face”.

I though that my leaving things alone, the system would “wait” with the updates till the fixed drivers were available.

Luckily, I have a spare RPI2 that I loaded OSMC on to press into service till the ATV is fixed. Hopefully - please, please, please - the fixes will also include a fix for the Crystal card not working.

OSMC never automatically updates without your consent.
It’s not possible for this to happen.

It had been a few days since the “sad face” updates, and those seemed to happen to people, like me, who were using the CLI to update. So, I reinstalled, didn’t install any of the extra stuff I normally do, and other than add directories with content, I left everything default.

When it prompted me with a “updates available …” I thought it’d be safe to say yes. Looks like I was wrong. In the end, no biggie as I hadn’t done and customization, so hardly any time lost.

RPI2 with a USB sound card - for SP/DIF sound out - and and old HP MEC remote & USB dongle is working OK, but with all the cables it looks “ugly”.

Regardless, I really do appreciate all the work you, and everyone else, is putting into this.

Hi,

How you update OSMC (CLI vs My OSMC) shouldn’t affect things significantly, provided you update as recommended in our Wiki.

The problem is that Debian userland (which we used for NVIDIA X11) is tightly coupled to the kernel driver which we forward ported for 4.x. Unfortunately, userland slips out of sync with Debian updates. This won’t be an issue with x64 as we will closely manage both and distrbute them downstream; but it has been something to learn from here.

That does seem a bit hacky. If you like OSMC, consider a Vero 4K. It will support OSMC and your device will be supported for many years to come. Something you’ve probably come to expect with OSMC and Crystalbuntu.

I’d love to give AppleTV a good send off with a final update with some CrystalHD support. I will do my best!

Sam

With all due respect, its sad that soon we will not have more updates for the old ATV1 but i’m so glad that thanks to you we have all this beneffits from this Device, i believe that still remain some of time to have good moments with it. “Gracias por el excelente trabajo”. Regards from Venezuela

I will prepare a final, working image and leave it on the OSMC site for the forseeable future.

Sam

Make an image for the atv with just the operating system without kodi when support and updates cease :slight_smile: I will make a stack of them and put them in the server room.

I’ve now updated the kernel to match the new NVIDIA driver API that’s shipped in Debian Jessie. I’ve pushed this to the main repository so all you need to do is update again for things to work as expected.

Remember to make sure you power off your device properly or /boot will be mounted as RO and updates will fail unless you manually fsck and remount the volume.

Thanks for your patience while I resolved the issue.

Cheers

Sam

1 Like

Thanks a lot @sam_nazarko, proceeding and reverting once done. One thing, the ATV1 has no power switch… there’s any problem about that?

You should shut it down properly via the Kodi menu or command line.
When the system halts, it’s safe to pull the plug.

Ok, understood. Thanks again, today i’ll update and will revert

I just did the new update but I still have the ndivia problem
─Configuring libgl1-nvidia-legacy-304xx-glx:i386───────────────┐
│ Mismatching nvidia kernel module loaded │
│ │
│ The NVIDIA driver that is being installed (version 304.135) does not │
│ match the nvidia kernel module currently loaded (version 304.134). │
│ │
│ The X server, OpenGL, and GPGPU applications may not work properly. │
│ │
│ The easiest way to fix this is to reboot the machine once the │
│ installation has finished. You can also stop the X server (usually by │
│ stopping the login manager, e.g. gdm3, kdm, or xdm), manually unload │
│ the module (“rmmod nvidia”), and restart the X server.