Log in
Register
Menu
Log in
Register
Home
What's new
Latest activity
Authors
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Satellite TV receivers & systems support forums
Satellite PC Card Receivers, Internet by Satellite
neumoDVB
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="deeptho" data-source="post: 1128178" data-attributes="member: 215446"><p>Satesco, and everyone,</p><p>there are many messages today and I will not try to attempt to address all the issues raised, but here is a summary</p><p>The drivers on your computer come from two places</p><p>1. the linux kernel as installed in your os.</p><p>2. the tbs drivers which are integrated into media_build to allow them to build separately from the kernel.</p><p>They are maintained by tbs and crazycat and I can tell you that is not an easy job.</p><p></p><p>media_build makes changes to the kernel source to fix all kinds of problems.</p><p>... and introduces new ones.</p><p></p><p>The summary is that it builds many kernel modules, including the ones that you don't need/want changed and </p><p>then depending on how you install it, also installs a new version of other unrelated drivers. It seems one of those is </p><p>based on slightly different code than the one in the ubuntu kernel. For example, perhaps ubuntu has fixed some bug in </p><p>a display driver, but that fix is not yet in the code that is compiled by media_build. After installation, you know have accidentally installed a "bad" driver.</p><p></p><p>So the trick is to not overrwite the bad driver. This means</p><p>1. compiling drivers for exactly the same kernel version as installed by ununtu. Otherwise, the "good" driver is </p><p>not even present (for the correct version) from the start</p><p>2. finding out which driver is the one that should not be overritten </p><p>3. Either making sure that the installation scripts do not overwrite that driver (this might be the tbs proposed solution, Not sure) or keeping a copy of the correct driver and afterwards restoring it.</p><p></p><p>So: if someone knows what driver is being overwritten, then simply copy that driver file somwhere before installing and then </p><p>later copy it over the "bad" version that is accidentally installed.</p><p></p><p>This solution may not always be possible. Some drivers depend on each other and need to be replaced together (all of them</p><p>or none of them). This is probably why media_build overwrites everything, Usually this works.</p><p> </p><p>Satesco is unlucky because probably his display driver has a bug which is fixed only by unbuntu but not in some </p><p>official kernel, or because the fix is in the official kernel but not yet in media_build or because the fix is in the </p><p>generic media_build but not yet in the tbs version of media_build or perhaps because he is (needs to) compile an</p><p>older version of the kernel.</p><p></p><p>Needless to say: this is not a good way of working, with at least three different possible versions for each driver: </p><p>1) ubuntu 2) generic media/media_build and 3) tbs /media/media_build and all of them potentially having small differences.</p><p>On top of that there are also differences between kernels. </p><p></p><p>Normally none of that matters, except now that there is some unrelated bug fixed in some unrelated drivers.</p><p>So this problem has nothing todo with tbs, with blindscan drivers or with and it will eventually disappear when all</p><p>versions are synchronised.</p><p></p><p></p><p>A simple solution is to ask Llew to make a copy of his ubuntu kernel and drivers, install them on Satesco's computer</p><p>and boot from that.</p><p>The copy needs to include:</p><p>-any file in /boot related to the correctlly running kernel version. </p><p>ls /boot/*`uname -r`* /lib/modules/*`uname -r`*</p><p></p><p>such files can be copied with tar. After installation, you also need to update grub.cfg. There must be a ubuntu-specific </p><p>procedure for that.</p><p></p><p>Note that the linux drivers (blindscan) are better than the windows drivers for tbs6909x and tbs6903x.</p><p></p><p>And if it is any consolation: with my cards, many of the windows programs do not work at all or with some serious limitations.</p><p>E.g.., ebspro: rf-scan not supported, iqmonitor (never any useful result), crayzscan (some versions work on some cards).</p><p>I have even seen blue screens of death. So you need some luck.</p><p></p><p></p><p>And of someone has info on what the problem exactly is, I can have a look at that driver (but explanations like </p><p>"tbs suggests to use ./install.sh to install are not informative enough in that respect.) and could add it to </p><p>the kernel source. </p><p></p><p>In the longer term I plan to go for a new install system. That might be easier (or not).</p><p></p><p>PS. I don't have ubuntu and cannot test. It also depends on your computer hardware.</p></blockquote><p></p>
[QUOTE="deeptho, post: 1128178, member: 215446"] Satesco, and everyone, there are many messages today and I will not try to attempt to address all the issues raised, but here is a summary The drivers on your computer come from two places 1. the linux kernel as installed in your os. 2. the tbs drivers which are integrated into media_build to allow them to build separately from the kernel. They are maintained by tbs and crazycat and I can tell you that is not an easy job. media_build makes changes to the kernel source to fix all kinds of problems. ... and introduces new ones. The summary is that it builds many kernel modules, including the ones that you don't need/want changed and then depending on how you install it, also installs a new version of other unrelated drivers. It seems one of those is based on slightly different code than the one in the ubuntu kernel. For example, perhaps ubuntu has fixed some bug in a display driver, but that fix is not yet in the code that is compiled by media_build. After installation, you know have accidentally installed a "bad" driver. So the trick is to not overrwite the bad driver. This means 1. compiling drivers for exactly the same kernel version as installed by ununtu. Otherwise, the "good" driver is not even present (for the correct version) from the start 2. finding out which driver is the one that should not be overritten 3. Either making sure that the installation scripts do not overwrite that driver (this might be the tbs proposed solution, Not sure) or keeping a copy of the correct driver and afterwards restoring it. So: if someone knows what driver is being overwritten, then simply copy that driver file somwhere before installing and then later copy it over the "bad" version that is accidentally installed. This solution may not always be possible. Some drivers depend on each other and need to be replaced together (all of them or none of them). This is probably why media_build overwrites everything, Usually this works. Satesco is unlucky because probably his display driver has a bug which is fixed only by unbuntu but not in some official kernel, or because the fix is in the official kernel but not yet in media_build or because the fix is in the generic media_build but not yet in the tbs version of media_build or perhaps because he is (needs to) compile an older version of the kernel. Needless to say: this is not a good way of working, with at least three different possible versions for each driver: 1) ubuntu 2) generic media/media_build and 3) tbs /media/media_build and all of them potentially having small differences. On top of that there are also differences between kernels. Normally none of that matters, except now that there is some unrelated bug fixed in some unrelated drivers. So this problem has nothing todo with tbs, with blindscan drivers or with and it will eventually disappear when all versions are synchronised. A simple solution is to ask Llew to make a copy of his ubuntu kernel and drivers, install them on Satesco's computer and boot from that. The copy needs to include: -any file in /boot related to the correctlly running kernel version. ls /boot/*`uname -r`* /lib/modules/*`uname -r`* such files can be copied with tar. After installation, you also need to update grub.cfg. There must be a ubuntu-specific procedure for that. Note that the linux drivers (blindscan) are better than the windows drivers for tbs6909x and tbs6903x. And if it is any consolation: with my cards, many of the windows programs do not work at all or with some serious limitations. E.g.., ebspro: rf-scan not supported, iqmonitor (never any useful result), crayzscan (some versions work on some cards). I have even seen blue screens of death. So you need some luck. And of someone has info on what the problem exactly is, I can have a look at that driver (but explanations like "tbs suggests to use ./install.sh to install are not informative enough in that respect.) and could add it to the kernel source. In the longer term I plan to go for a new install system. That might be easier (or not). PS. I don't have ubuntu and cannot test. It also depends on your computer hardware. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Satellite TV receivers & systems support forums
Satellite PC Card Receivers, Internet by Satellite
neumoDVB
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top