Tvheadend

I'm not surprised you're running into problems with media_build, it's to be expected seeing as it's the dev version, did you do a backup of the kernel modules (or even a complete system backup) BEFORE you built the linuxtv drivers?

OMV is still using wheezy which is OLD now and the latest kernel you can get pre-packaged is what you already have installed.

I have the August T210v2 myself running Debian Jessie on Kernel 4.x+ and it's fine here, I know this doesn't help your situation.

You have a number of options (that I can think of).

• Reinstall OMV.
• Attempt to fix the broken modules, by doing something like this:

rm -rf /lib/modules/$(uname -r)/kernel/drivers/media/ 
reboot
> Then rebuild and install linuxtv media_build

• Update to a newer distro, Ubuntu 16.04 / Debian Jessie and install something like webmin, it's not as fancy as OMV but it should do most of the same thing.
• (This one is a joke) - Take a hammer to your machine and then throw it out the window!

Note, you do all of the above at your own risk, I take no responsibility for: data loss, baldness, explosions, your dishwasher/wife/goat leaving you and/or total machine failure.

Mark Clarkstone wrote:

I'm not surprised you're running into problems with media_build, it's to be expected seeing as it's the dev version, did you do a backup of the kernel modules (or even a complete system backup) BEFORE you built the linuxtv drivers?

OMV is still using wheezy which is OLD now and the latest kernel you can get pre-packaged is what you already have installed.

I have the August T210v2 myself running Debian Jessie on Kernel 4.x+ and it's fine here, I know this doesn't help your situation.

You have a number of options (that I can think of).

• Reinstall OMV.
• Attempt to fix the broken modules, by doing something like this:

[...]

• Update to a newer distro, Ubuntu 16.04 / Debian Jessie and install something like webmin, it's not as fancy as OMV but it should do most of the same thing.
• (This one is a joke) - Take a hammer to your machine and then throw it out the window!

Note, you do all of the above at your own risk, I take no responsibility for: data loss, baldness, explosions, your dishwasher/wife/goat leaving you and/or total machine failure.

Oh that's not great to hear.
No I mede no backups what so ever as I thought the process was "safe" as I was purely following a guide.
I am very much a linux novice and many of the things In guide are foreign to me.
But I'l look into the topic of backing up kernels as a future precaution and will probably just reinstall OMV even if that will take its time...

To solve my problem I would need a stick that is supported by my Kernel. Are there any suggestions?

Daniel Kurth wrote:

Mark Clarkstone wrote:

I'm not surprised you're running into problems with media_build, it's to be expected seeing as it's the dev version, did you do a backup of the kernel modules (or even a complete system backup) BEFORE you built the linuxtv drivers?

OMV is still using wheezy which is OLD now and the latest kernel you can get pre-packaged is what you already have installed.

I have the August T210v2 myself running Debian Jessie on Kernel 4.x+ and it's fine here, I know this doesn't help your situation.

You have a number of options (that I can think of).

• Reinstall OMV.
• Attempt to fix the broken modules, by doing something like this:

[...]

• Update to a newer distro, Ubuntu 16.04 / Debian Jessie and install something like webmin, it's not as fancy as OMV but it should do most of the same thing.
• (This one is a joke) - Take a hammer to your machine and then throw it out the window!

Note, you do all of the above at your own risk, I take no responsibility for: data loss, baldness, explosions, your dishwasher/wife/goat leaving you and/or total machine failure.

Oh that's not great to hear.
No I mede no backups what so ever as I thought the process was "safe" as I was purely following a guide.
I am very much a linux novice and many of the things In guide are foreign to me.
But I'l look into the topic of backing up kernels as a future precaution and will probably just reinstall OMV even if that will take its time...

To solve my problem I would need a stick that is supported by my Kernel. Are there any suggestions?

It's more the other way around, you need a kernel that supports the stick, most of the sticks on the market use the Si2*** chipsets because they're pretty decent, the drivers are fine and they're cheap.

You can always build yourself a new kernel (it's not that hard, I do it all the time).

If you mainly run tvheadend / samba like I do, barebones ubuntu (or debian) will work just as well as OMV.

Mark Clarkstone wrote:

It's more the other way around, you need a kernel that supports the stick, most of the sticks on the market use the Si2*** chipsets because they're pretty decent, the drivers are fine and they're cheap.

You can always build yourself a new kernel (it's not that hard, I do it all the time).

If you mainly run tvheadend / samba like I do, barebones ubuntu (or debian) will work just as well as OMV.

You're most probably right and if I had more time on my hands I would do that.
But as don't have a lot of spare time and I'm no so familiar with linux I like the idea of Nas oriented operating systems.
They give me the ability to add features, edit setting and maintain an up to date system in a much more user friendly way. This has the benefit, that I don't have to read into all the topics I want to accomplish and my room mate can also make changes to the system.

Maybe I should look towards changing to a more up to date system as I've probably done irreparable damage.
But thanks for the help.