crazycat Wrote:You have already cloned media_build and media. You can update this cloned repos, compile and install:
- Code: Select All Code
~ $ cd media
~/media $ git remote update
~/media $ git pull
~/media $ cd ../media_build
~/media_build $ git remote update
~/media_build $ git pull
~/media_build $ ./install.sh
Huh? Now I am REALLY confused. Those are completely different instructions from what SPiKeGoD gave above. Is there no longer a need to "comment the line #add v6.8-ccs.patch" in backports/backports.txt, or run those two sed commands? Those were the instructions that worked for me.
Of course I am assuming that when you do
- Code: Select All Code
~/media $ git remote update
~/media $ git pull
(shown twice in what you posted) that is going out to the internet to update the cloned repos, and that is exactly what I am trying to avoid. Whenever there is a kernel update, I just want to be able to run a script that will rebuild the drivers without depending on the availability of git, so that if the Internet goes down between the time the kernel finishes updating and the time I attempt to rebuild the drivers I'm not left with non-functional tuner cards. I am NOT a Linux expert at all, so it is really confusing to me when I see different instructions for doing something and one shows you have to do modifications or patches and another seems to take a different approach.
Just so you know, my /usr/src/media_build/install.sh file contains this:
- Code: Select All Code
#!/bin/bash
# Enable some staging drivers
make stagingconfig
# Disable RC/IR support
sed -i -r 's/(^CONFIG.*_RC.*=)./\1n/g' v4l/.config
sed -i -r 's/(^CONFIG.*_IR.*=)./\1n/g' v4l/.config
echo "V4L drivers building..."
make -j$(nproc)
echo "V4L drivers installing..."
sudo rm -r -f /lib/modules/$(uname -r)/updates/extra
sudo make install
echo "V4L drivers installation done"
echo "You need to reboot..."
