Lines Matching full:latest
15 you don't find any, install `the latest release from that series
26 don't find any to join, install `the latest mainline kernel
30 supported stable or longterm series as well? Then install its latest release.
71 willing to install the latest Linux version yourself. Be aware the latter
116 * Unless you are already running the latest 'mainline' Linux kernel, better
118 the latest 'stable' Linux can be an acceptable alternative in some
145 issue. Always mention a few things: the latest kernel version you installed
181 the latest release of the particular version line without an '[EOL]' tag.
186 * Install the latest release from the particular version line as a vanilla
206 This subsection is for you, if you tried the latest mainline kernel as outlined
281 willing to install the latest Linux version yourself. Be aware the latter
303 vendor by installing the very latest Linux kernel core yourself. If that's an
314 with kernels from distributions shipping the latest stable kernel, as long as
490 install the latest mainline kernel; you will need to check the taint flag again
773 *Unless you are already running the latest 'mainline' Linux kernel, better
775 the latest 'stable' Linux can be an acceptable alternative in some
786 interest that you confirm the issue still exists with the latest upstream code
791 In the scope of the kernel "latest upstream" normally means:
793 * Install a mainline kernel; the latest stable kernel can be an option, but
807 want to use for testing. Ignore the big yellow button that says 'Latest release'
830 consider obtaining the latest mainline kernel via git (see below) or use the
831 latest stable version offered on kernel.org. Using that is also acceptable in
836 Better avoid using the latest stable kernel outside merge windows, as all fixes
837 must be applied to mainline first. That's why checking the latest mainline
862 latest mainline or stable Linux built as vanilla kernel. It's totally okay to
864 at least close to it. Additionally ensure the packages contain the latest
878 often best served by obtaining the latest Linux kernel sources straight from the
881 Those are likely a bit ahead of the latest mainline pre-release. Don't worry
1072 issue. Always mention a few things: the latest kernel version you installed
1238 make your report mention the latest tested version that's working fine (say 5.7)
1475 mentions the latest release of the particular version line without an
1505 *Install the latest release from the particular version line as a vanilla
1512 was already fixed in the latest release of version line you're interested in.
1520 5.10.5-vendor.43. Then after testing the latest 5.10 release as outlined in
1548 instructed above go and check the latest kernel from that version line, say
1607 * Check with the latest release.