* Re: linux5.6 unavailable on i686
2020-04-27 6:00 [ISSUE] linux5.6 unavailable on i686 mithodin
@ 2020-04-27 6:45 ` Hoshpak
2020-04-27 6:51 ` mithodin
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Hoshpak @ 2020-04-27 6:45 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/21369#issuecomment-619765311
Comment:
I rather looks like the person creating the template didn't bother to create a config for the architecture. Someone has to do that and PR it for the kernel to become available.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: linux5.6 unavailable on i686
2020-04-27 6:00 [ISSUE] linux5.6 unavailable on i686 mithodin
2020-04-27 6:45 ` Hoshpak
@ 2020-04-27 6:51 ` mithodin
2020-04-27 6:59 ` Hoshpak
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: mithodin @ 2020-04-27 6:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
New comment by mithodin on void-packages repository
https://github.com/void-linux/void-packages/issues/21369#issuecomment-619768148
Comment:
Well, is there documentation available for how the config is supposed to look like? Just enable all the modules? I have a grand whopping one i686 machine, so I'm not sure a config that works for me(TM) would be sufficient as a general template.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: linux5.6 unavailable on i686
2020-04-27 6:00 [ISSUE] linux5.6 unavailable on i686 mithodin
2020-04-27 6:45 ` Hoshpak
2020-04-27 6:51 ` mithodin
@ 2020-04-27 6:59 ` Hoshpak
2020-04-27 7:00 ` Hoshpak
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Hoshpak @ 2020-04-27 6:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/21369#issuecomment-619772521
Comment:
New configs are generally created using `make oldconfig` over an earlier config (5.5 would be best to use in that case). The new options should mostly be set according to the existing x86_64 config. If there are options specific to the i686 architecture, I would look into the documentation on how to set them oder go with the defaults. The resulting configuration should be tested on physical hardware by locally compiling the package and giving it a test run on the target machine before creating a PR.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: linux5.6 unavailable on i686
2020-04-27 6:00 [ISSUE] linux5.6 unavailable on i686 mithodin
` (2 preceding siblings ...)
2020-04-27 6:59 ` Hoshpak
@ 2020-04-27 7:00 ` Hoshpak
2020-04-27 7:00 ` mithodin
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Hoshpak @ 2020-04-27 7:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/21369#issuecomment-619772521
Comment:
New configs are generally created using `make oldconfig` over an earlier config (5.5 would be best to use in that case). The new options should mostly be set according to the existing x86_64 config. If there are options specific to the i686 architecture, I would look into the documentation on how to set them or go with the defaults. The resulting configuration should be tested on physical hardware by locally compiling the package and giving it a test run on the target machine before creating a PR.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: linux5.6 unavailable on i686
2020-04-27 6:00 [ISSUE] linux5.6 unavailable on i686 mithodin
` (3 preceding siblings ...)
2020-04-27 7:00 ` Hoshpak
@ 2020-04-27 7:00 ` mithodin
2020-05-01 8:18 ` [ISSUE] [CLOSED] " Hoshpak
2020-05-01 8:44 ` mithodin
6 siblings, 0 replies; 8+ messages in thread
From: mithodin @ 2020-04-27 7:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 174 bytes --]
New comment by mithodin on void-packages repository
https://github.com/void-linux/void-packages/issues/21369#issuecomment-619773037
Comment:
Right. I'll give it a go then.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [ISSUE] [CLOSED] linux5.6 unavailable on i686
2020-04-27 6:00 [ISSUE] linux5.6 unavailable on i686 mithodin
` (4 preceding siblings ...)
2020-04-27 7:00 ` mithodin
@ 2020-05-01 8:18 ` Hoshpak
2020-05-01 8:44 ` mithodin
6 siblings, 0 replies; 8+ messages in thread
From: Hoshpak @ 2020-05-01 8:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Closed issue by mithodin on void-packages repository
https://github.com/void-linux/void-packages/issues/21369
Description:
5.6 has been available on x86_64 (and some other archs) for a few weeks now, but not on i686. Is there a specific reason for this, or has it simply been forgotten?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: linux5.6 unavailable on i686
2020-04-27 6:00 [ISSUE] linux5.6 unavailable on i686 mithodin
` (5 preceding siblings ...)
2020-05-01 8:18 ` [ISSUE] [CLOSED] " Hoshpak
@ 2020-05-01 8:44 ` mithodin
6 siblings, 0 replies; 8+ messages in thread
From: mithodin @ 2020-05-01 8:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
New comment by mithodin on void-packages repository
https://github.com/void-linux/void-packages/issues/21369#issuecomment-622304105
Comment:
Hey, thanks a lot! I had not found the time yet to do it myself.
^ permalink raw reply [flat|nested] 8+ messages in thread