oS Leap 15.4 Kernel difference between install and OBS
Hi, The last few days I've been trying to install a broadcom-wl package from 2 different home repos for my newly installed Macbook Air 2015 with Leap 15.4. However I keep getting the same error while installing, as the kernel version from the broadcom-wl package does not match the installed kernel. Leap 15.4 Alpha: 5.14.21-150400.3.3.x86_64 OBS and PBS: 5.14.21-150400.6.2.x86_64 Why is there a difference between these kernels? Also can we expect an update for the kernel to version xx6.2? Also I posted this to the project ML first, but I guess that was the wrong ML. Is this one better for 15.4 related questions? BR, Syds
Syds Bearda wrote:
Hi, The last few days I've been trying to install a broadcom-wl package from 2 different home repos for my newly installed Macbook Air 2015 with Leap 15.4.
Hi Syds! I'm assuming you already know the current state of development of Leap 15.4 (i.e., alpha phase) and you're just testing, right?!
However I keep getting the same error while installing, as the kernel version from the broadcom-wl package does not match the installed kernel.
If this/these broadcom-wl package(s) you are trying to install has/have a '15.4' repository and you are using it, you probably are hitting another issue rather than version mismatch.
Leap 15.4 Alpha: 5.14.21-150400.3.3.x86_64 OBS and PBS: 5.14.21-150400.6.2.x86_64 Why is there a difference between these kernels?
There is no version difference between both of them, other than the release bit. Distribution packages generally hold two sets of versions separated by a '-': * The upstream one: 5.14.21, in this example; * The distro release one: 150400.3.3.x86_64 and 150400.6.2.x86_64. Where we have: 1) 150400: the release target bit (in previous versions of Leap it was a string, 'lp', if memory serves); 2) 3.3 and 6.2: the release version, automatically increase by the open build service; 3) x86_64: plus the architecture. So, both repositories here have the same upstream version: '5.14.21', but different RELEASE version: '.3.3' and '.6.2', and both prefixed by the same target release: '150400'. And this difference is due to where both Kernels live. I'm using my packaging instincts here, but every time there's a change in the kernel package, a direct change, (or any other package, for that matter) that is not a version update from upstream (e.g., adding a patch), the first bit of the release version (.3 and .6 from the packages in question) is increased by 1. And every time there's a change in development project where it lives, an indirect change, that affects the kernel package (i.e., any of its build dependencies), the second part of the release bit (.3 and .2 from the packages in question) is increased by 1 as well. Since the second project you pointed out (OBS and PBS) is a busier development project than the first one (Leap 15.4 Alpha) we can see how much one gets more rebuilt than the other. Also can we expect an update for the kernel to version xx6.2? Now that you (hopefully) understand how package versioning works, we can say YES! But if you're curious if the 5.14 will change, I don't think so since the beta freeze is about to happen this mid February.
Also I posted this to the project ML first, but I guess that was the wrong ML. Is this one better for 15.4 related questions?
Dang right! Since we don't have a specific ML for openSUSE regular distro releases we use Factory instead.
BR, Syds
Take care, Luciano.
Hi Luciano, First of all thanks for your comment. On Tue, 8 Feb 2022, at 00:37, Luciano Santos wrote:
Syds Bearda wrote:
Hi, The last few days I've been trying to install a broadcom-wl package from 2 different home repos for my newly installed Macbook Air 2015 with Leap 15.4.
Hi Syds! I'm assuming you already know the current state of development of Leap 15.4 (i.e., alpha phase) and you're just testing, right?!
That's exactly what I was doing :)
However I keep getting the same error while installing, as the kernel version from the broadcom-wl package does not match the installed kernel.
If this/these broadcom-wl package(s) you are trying to install has/have a '15.4' repository and you are using it, you probably are hitting another issue rather than version mismatch.
No issue seems completely related to
Leap 15.4 Alpha: 5.14.21-150400.3.3.x86_64 OBS and PBS: 5.14.21-150400.6.2.x86_64 Why is there a difference between these kernels?
There is no version difference between both of them, other than the release bit. Distribution packages generally hold two sets of versions separated by a '-':
* The upstream one: 5.14.21, in this example;
* The distro release one: 150400.3.3.x86_64 and 150400.6.2.x86_64.
Where we have:
1) 150400: the release target bit (in previous versions of Leap it was a string, 'lp', if memory serves); 2) 3.3 and 6.2: the release version, automatically increase by the open build service; 3) x86_64: plus the architecture.
So, both repositories here have the same upstream version: '5.14.21', but different RELEASE version: '.3.3' and '.6.2', and both prefixed by the same target release: '150400'. And this difference is due to where both Kernels live.
I think that's the problem though. Shouldn't those versions be the same as well? When installing broadcom-wl today I still get: syds@localhost:~> sudo zypper in broadcom-wl Loading repository data... Warning: Repository 'Update repository of openSUSE Backports' appears to be outdated. Consider using a different mirror or server. Warning: Repository 'Main Update Repository' appears to be outdated. Consider using a different mirror or server. Reading installed packages... Resolving package dependencies... Problem: nothing provides 'ksym(default:PDE_DATA) = a03fad84' needed by the to be installed broadcom-wl-kmp-default-6.30.223.271_k5.14.21_150400.7-lp154.15.8.x86_64 Solution 1: do not install broadcom-wl-6.30.223.271-lp154.15.8.x86_64 Solution 2: break broadcom-wl-kmp-default-6.30.223.271_k5.14.21_150400.7-lp154.15.8.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): Also I do have ksym PDE_DATA available for 15.14: syds@localhost:~> sudo grep PDE_DATA /boot/System.map-$(uname -r) ffffffff813d2bd0 T PDE_DATA ffffffff8244e440 r __ksymtab_PDE_DATA ffffffff8247f473 r __kstrtabns_PDE_DATA ffffffff82485885 r __kstrtab_PDE_DATA
I'm using my packaging instincts here, but every time there's a change in the kernel package, a direct change, (or any other package, for that matter) that is not a version update from upstream (e.g., adding a patch), the first bit of the release version (.3 and .6 from the packages in question) is increased by 1. And every time there's a change in development project where it lives, an indirect change, that affects the kernel package (i.e., any of its build dependencies), the second part of the release bit (.3 and .2 from the packages in question) is increased by 1 as well. Since the second project you pointed out (OBS and PBS) is a busier development project than the first one (Leap 15.4 Alpha) we can see how much one gets more rebuilt than the other.
Also can we expect an update for the kernel to version xx6.2?
Now that you (hopefully) understand how package versioning works, we can say YES! But if you're curious if the 5.14 will change, I don't think so since the beta freeze is about to happen this mid February.
So I should just wait till the beta to be able to install broadcom-wl?
Also I posted this to the project ML first, but I guess that was the wrong ML. Is this one better for 15.4 related questions?
Dang right! Since we don't have a specific ML for openSUSE regular distro releases we use Factory instead.
BR, Syds
Take care, Luciano.
Syds Bearda wrote:
...
150400: the release target bit (in previous versions of Leap it was
a string, 'lp', if memory serves);
Disregard what I said about the 150400. I'm not sure where and when it's used, anymore. The distribution release target identifier still is 'lp...' for Leap. 'lp154' for Leap 15.4, 'lp153', 15.3, 'lp152, 15.2, etc.
... And this difference is due to where both Kernels live. I think that's the problem though. Shouldn't those versions be the same as well?
You may want to read again the part where I speculate how the distribution release bit (anything after the dash: 150400.3.3.x86_64 and 150400.6.2.x86_64, where, for the sake of our discussion here, we can ignore the distribution release target identifier, 150400 in this case), is increased. To not overwhelm you with more details that may be hard to grasp if you are not familiar with openSUSE's development model, how many packages in Leap are inherited from SLE devel projects. The bottom line is: If we have the same package in two different projects (to get easier to imagine it, think of one of them being in openSUSE:Factory and the other one in openSUSE:Leap:15.4), where neither one of them is a link to the other (what happens to a lot of devel projects, many of them are links to their respective packages in openSUSE:Factory), they VERY hardly will EVER get the same distro release version (we are simplifying it for the sake of this discussion, so remember, after the '-' and between the distro release target identifier and the architecture).
When installing broadcom-wl today I still get: syds@localhost:~> sudo zypper in broadcom-wl Loading repository data... Warning: Repository 'Update repository of openSUSE Backports' appears to be outdated. Consider using a different mirror or server. Warning: Repository 'Main Update Repository' appears to be outdated. Consider using a different mirror or server.
Those warnings make me worried, are you sure your system is up to date? Please make sure it is.
Reading installed packages... Resolving package dependencies... Problem: nothing provides 'ksym(default:PDE_DATA) = a03fad84' needed by the to be installed broadcom-wl-kmp-default-6.30.223.271_k5.14.21_150400.7-lp154.15.8.x86_64 Solution 1: do not install broadcom-wl-6.30.223.271-lp154.15.8.x86_64 Solution 2: break broadcom-wl-kmp-default-6.30.223.271_k5.14.21_150400.7-lp154.15.8.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): Also I do have ksym PDE_DATA available for 15.14: syds@localhost:~> sudo grep PDE_DATA /boot/System.map-$(uname -r) ffffffff813d2bd0 T PDE_DATA ffffffff8244e440 r __ksymtab_PDE_DATA ffffffff8247f473 r __kstrtabns_PDE_DATA ffffffff82485885 r __kstrtab_PDE_DATA
Everything gets clearer when you post the commands you tried and its output. This is what you should've posted in the first place. The key here is: ksym(default:PDE_DATA) = a03fad84 Which doesn't match with the one you have:
ffffffff813d2bd0 T PDE_DATA
a03fad84 != 813d2bd0 So let's go through what's going on here. You didn't show from where exactly you are trying to install this broadcom-wl package, using Sauerland's, as an example, we have this symbol requirements: https://build.opensuse.org/package/binary/home:Sauerland/broadcom-wl/15.4/x8... And you can see it has this symbol requirement: ksym(default:PDE_DATA) = a03fad84 Exactly like the one you are trying to install, maybe they are the same, I haven't checked other packages so far. And at the right you can see what packages provide this symbol: kernel-default and kernel-default-base; Now if we go to the Kernel:SLE15-SP4/kernel-default project/package detailed information page about the package here: https://build.opensuse.org/package/binary/Kernel:SLE15-SP4/kernel-default/po... A Ctrl+F and typing 'pde_data' will give you this: ksym(default:PDE_DATA) = a03fad84 That makes me wonder whether your kernel is really up to date and/or where it comes from. Luciano, Kind regards.
P.S.: It kind of doesn't matter where you are getting the broadcom-wl package from. The version 6.30.223.271 is requiring the symbol "ksym(default:PDE_DATA) = a03fad84" which is provided by the kernel-default version 5.14.21 and maybe by other 5.14.x version. And I'm not sure which one, 'ffffffff813d2bd0 T PDE_DATA' or 'ffffffff8244e440 r __ksymtab_PDE_DATA' is the one that holds the right value provided by ksym(default:PDE_DATA). Luciano, Kind regards.
participants (2)
-
Luciano Santos -
Syds Bearda