Kernel Versions 4. Check the branches for support of kernel versions 4. Special thanks to waveletlet their profile on github for having provided the merge request to add support for changes made to the kernel sources in version s 5. The original source for kernel versions up to 4. The latest is based on the respective kernel's sources. This update is still functional with kernel version 5. Check out the branch for your kernel version.
If you are using the latest kernel version available in Debian Buster or from the buster-backports channel at the time of this writing , you can just use master. The remaining process depends upon whether this is your first time building the source, or whether you're rebuilding due to a kernel patch version update i. If you are updating due to a kernel patch or packaging version update, you'll need to clean your working directory first [1] :. At the time of writing, I'm using debian-live You may see a more recent version, but make sure you download the "- standard.
Use putty to connect to the serial port. Putty instructions for Windows are available here and for macOS here. Connect power to APU to boot the system. Select the first option and press Tab. It should look similar to this:. Now you should be logged in either via ssh or through the serial cable as shown above. Make sure you have the WAN cable connected, so you have a connection to the internet.
We need an image called "combined-ext4. Make sure you get the ext4 image; otherwise, you won't be able to resize the partition and use the entire disk space. This should produce a file named " openwrt Then when you get to the point of generating an initramfs image, you also need to substitute the kernel version with yours in the mkinitramfs command.
That should automatically update your grub2 and you should not see it in the boot options any more. I tried your excellent guide too, but it only seemed to do the trick once. Any idea what I could do next? If you connected once, but after the next reboot you are having the same issue that most likely means one of two things:. You are not loading your new custom kernel image. Make sure that you are booting that new image.
If not, reboot and select the custom one. If after this you can connect, then you are running the right kernel, but you are not loading the ath9k module on boot. I think I may be way over my head here. It was in one of the steps above.
The former is a Gtk based and the latter is text based. Any help would be greatly appreciated!! Thanks, Mark. Thanks for the quick reply. Or at least a whole bunch of stuff happened in the terminal. Too much to past here. Tried all 3 of the commands and same thing happened. The path looks right, but it seems that your source might not be there. I was surprised how long the terminal ran, well over an hour doing all kinds of weird stuff.
It made another linux-source That may be causing me some trouble. If you have already compiled the kernel with the make-kpkg can now install it with the dpkg -i command. Just follow the instructions in the blog. Also, make sure that you are typing the name of the.
0コメント