Porteus Kernel Builder

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#721 by neko » 06 Nov 2019, 03:30

@Buurman

These are new sample build kernels of your request.

32bit-BPLUS-kernel5.4-rc6-2.tar (88 M)
http://www.mediafire.com/file/934dijxtk ... -rc6-2.tar
md5sum: 8ed6f9318ce819ff442ac605b1a9770d 32bit-BPLUS-kernel5.4-rc6-2.tar

64bit-BPLUS-kernel5.4-rc6-2.tar (93 M)
http://www.mediafire.com/file/bgiwd7th0 ... -rc6-2.tar
md5sum: ca6caa5060c36ac14b94bc676a65edef 64bit-BPLUS-kernel5.4-rc6-2.tar

Code: Select all

# diff old.64bit.config 64bit.config
4893,4894c4893,4894
< # CONFIG_LOGITECH_FF is not set
< # CONFIG_LOGIRUMBLEPAD2_FF is not set
---
> CONFIG_LOGITECH_FF=y
> CONFIG_LOGIRUMBLEPAD2_FF=y
Other kernel version line's (5.3, 4.19) configs will be updated at next kernel update.


Thanks.

User avatar
ralcocer
Samurai
Samurai
Posts: 178
Joined: 02 Jan 2011, 12:53
Distribution: 3.2rc5 Xfce
Location: Puerto Rico
Contact:

Porteus Kernel Builder

Post#722 by ralcocer » 06 Nov 2019, 11:40

I am using the latest Porteus 4 iso and looking at the log I see this message.

notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!

I though PAE was in kernel 4.16.3.

neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#723 by neko » 06 Nov 2019, 13:30

@ralcocer

I don't understand your problem situation.
Please upload your "fault Porteus 4 iso".

Thanks.

Buurman
White ninja
White ninja
Posts: 11
Joined: 28 Oct 2019, 18:00
Distribution: ver5

Porteus Kernel Builder

Post#724 by Buurman » 06 Nov 2019, 20:13

neko wrote:
06 Nov 2019, 03:30
@Buurman

These are new sample build kernels of your request.

32bit-BPLUS-kernel5.4-rc6-2.tar (88 M)
http://www.mediafire.com/file/934dijxtk ... -rc6-2.tar
md5sum: 8ed6f9318ce819ff442ac605b1a9770d 32bit-BPLUS-kernel5.4-rc6-2.tar

64bit-BPLUS-kernel5.4-rc6-2.tar (93 M)
http://www.mediafire.com/file/bgiwd7th0 ... -rc6-2.tar
md5sum: ca6caa5060c36ac14b94bc676a65edef 64bit-BPLUS-kernel5.4-rc6-2.tar

Code: Select all

# diff old.64bit.config 64bit.config
4893,4894c4893,4894
< # CONFIG_LOGITECH_FF is not set
< # CONFIG_LOGIRUMBLEPAD2_FF is not set
---
> CONFIG_LOGITECH_FF=y
> CONFIG_LOGIRUMBLEPAD2_FF=y
Other kernel version line's (5.3, 4.19) configs will be updated at next kernel update.


Thanks.
Tested and Rumblepad2's work fine now :good: , 'rumbling' and everything, haven't noticed any other problems with the new kernel for now (only using 3 programs on porteus anyhow)

neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#725 by neko » 06 Nov 2019, 23:08

Most recent versions of build examples were updated.
5.3.9, 4.19.82

Note: Updating configs

Code: Select all

$ diff .config.old .config
3c3
< # Linux/x86 5.3.7 Kernel Configuration
---
> # Linux/x86 5.3.9 Kernel Configuration
4872,4873c4872,4873
< # CONFIG_LOGITECH_FF is not set
< # CONFIG_LOGIRUMBLEPAD2_FF is not set
---
> CONFIG_LOGITECH_FF=y
> CONFIG_LOGIRUMBLEPAD2_FF=y
$
$
$ diff .config.old .config
3c3
< # Linux/x86 4.19.80 Kernel Configuration
---
> # Linux/x86 4.19.82 Kernel Configuration
4640,4641c4640,4641
< # CONFIG_LOGITECH_FF is not set
< # CONFIG_LOGIRUMBLEPAD2_FF is not set
---
> CONFIG_LOGITECH_FF=y
> CONFIG_LOGIRUMBLEPAD2_FF=y

Please refer to the top article of this thread.
Porteus Kernel Builder


--------------------------------
@Buurman

Thank you for your report.


Thanks.

neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#726 by neko » 11 Nov 2019, 07:17

Most recent versions of build examples were updated.
5.4-rc7, 5.3.10, 4.19.83

Note 1: AUFS patch "5.x-rcN-20191021" is not yet ready for kernel version 5.4-rc.
It was patched by manual as same as patching to kernel version 5.4.0-rc2.
Porteus Kernel Builder (Post by neko #74116)


Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2721
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#727 by Blaze » 12 Nov 2019, 09:08

Hi neko.
If look at torday updates of Slackware-current from 2019-11-12
ftp://ftp.osuosl.org/pub/slackware/slac ... ngeLog.txt
they are applyed this option as module for kernel 5.4 RC7

Code: Select all

VBOXSF_FS=m
more information about this option you can find here

I think we must to have the same thing in your next kernel update too.

Thanks.
Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#728 by neko » 12 Nov 2019, 11:30

@Blaze

These are your requested "kernel 5.4-rc7"s.

[5.4-rc7]
"Basic & Option patches" patching was done.
32bit-BPLUS-kernel5.4-rc7-2.tar (88 M)
http://www.mediafire.com/file/7mtze00k0 ... -rc7-2.tar
md5sum: 3cb57306ee76053f8fd329ec37d4fc9e 32bit-BPLUS-kernel5.4-rc7-2.tar

64bit-BPLUS-kernel5.4-rc7-2.tar (93 M)
http://www.mediafire.com/file/qyoay6yhy ... -rc7-2.tar
md5sum: bf7f0cd68851382b3772379a03d68f17 64bit-BPLUS-kernel5.4-rc7-2.tar


Note: The config was updated by the "make menuconfig" command.

Code: Select all

  
Symbol: VBOXGUEST [=n]                                                                                                                │  
  │ Type  : tristate                                                                                                                      │  
  │ Prompt: Virtual Box Guest integration support                                                                                         │  
  │   Location:                                                                                                                           │  
  │     -> Device Drivers                                                                                                                 │  
  │ (1)   -> Virtualization drivers (VIRT_DRIVERS [=n])                                                                                   │  
  │   Defined at drivers/virt/vboxguest/Kconfig:2                                                                                         │  
  │   Depends on: VIRT_DRIVERS [=n] && X86 [=y] && PCI [=y] && INPUT [=y]                                                                 │  
  │                                                                                                                                       │  
  │
  
Symbol: VBOXSF_FS [=n]                                                                                                                │  
  │ Type  : tristate                                                                                                                      │  
  │ Prompt: VirtualBox guest shared folder (vboxsf) support                                                                               │  
  │   Location:                                                                                                                           │  
  │     -> Device Drivers                                                                                                                 │  
  │ (1)   -> Staging drivers (STAGING [=y])                                                                                               │  
  │   Defined at drivers/staging/vboxsf/Kconfig:1                                                                                         │  
  │   Depends on: STAGING [=y] && X86 [=y] && VBOXGUEST [=n]                                                                              │  
  │   Selects: NLS [=y]                                                                                                                   │  

Code: Select all

# diff .config.old .config
5569c5569,5570
< # CONFIG_VIRT_DRIVERS is not set
---
> CONFIG_VIRT_DRIVERS=y
> CONFIG_VBOXGUEST=m
5668a5670
> CONFIG_VBOXSF_FS=m
#

Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2721
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#729 by Blaze » 13 Nov 2019, 08:15

neko, thanks, but seems need to defer these options until the next release of kernel 5.5
More info is here VirtualBox SF Driver Ejected From The Linux 5.4 Kernel

I am sorry about this.

UPDATED
NEWS >>> True to its name, Intel CPU flaw ZombieLoad comes shuffling back with new variant

Intel:
https://www.intel.com/content/www/us/en ... 00270.html
CVE-2019-11135

Phoronix:
https://www.phoronix.com/scan.php?page= ... ernel-Code

RedHat has a tech article describing two mitigation techniques:
- disable TSX feature of the CPU with the kernel boot parameter "tsx="
- clear CPU buffers upon context switch with the kernel boot parameter "tsx_async_abort="
It needs both new (patched) kernel and latest Intel microcode:
https://access.redhat.com/solutions/tsx ... onousabort

Latest Intel microcode:
https://github.com/intel/Intel-Linux-Pr ... e-20191112

If look again at Slackware-current changelog from 2019-11-12 -> ftp://ftp.osuosl.org/pub/slackware/slac ... ngeLog.txt

Code: Select all

X86_INTEL_TSX_MODE_AUTO=n
X86_INTEL_TSX_MODE_OFF=y
X86_INTEL_TSX_MODE_ON=n
We must to have these options too.
Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#730 by neko » 14 Nov 2019, 02:34

@Blaze
The config of 32/64bit-BPLUS-kernel5.4-rc7-2 build was deleted.
When that config will be needed, it will be introduced.

Thank you for your report.

Thanks.

User avatar
ralcocer
Samurai
Samurai
Posts: 178
Joined: 02 Jan 2011, 12:53
Distribution: 3.2rc5 Xfce
Location: Puerto Rico
Contact:

Porteus Kernel Builder

Post#731 by ralcocer » 14 Nov 2019, 13:26


neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#732 by neko » 15 Nov 2019, 07:46

Most recent versions of build examples were updated.
5.3.11, 4.19.84

Note : update the config of kernel 5.3.11/4.19.84 with "make oldconfig" command.
==5.3.11 64bit config==

Code: Select all

TSX enable mode
> 1. off (X86_INTEL_TSX_MODE_OFF) (NEW)
  2. on (X86_INTEL_TSX_MODE_ON) (NEW)
  3. auto (X86_INTEL_TSX_MODE_AUTO) (NEW)
choice[1-3?]: 1
==5.3.11 32bit config==

Code: Select all

TSX enable mode
> 1. off (X86_INTEL_TSX_MODE_OFF) (NEW)
  2. on (X86_INTEL_TSX_MODE_ON) (NEW)
  3. auto (X86_INTEL_TSX_MODE_AUTO) (NEW)
choice[1-3?]: 1
==4.19.84 64bit config==

Code: Select all

TSX enable mode
> 1. off (X86_INTEL_TSX_MODE_OFF) (NEW)
  2. on (X86_INTEL_TSX_MODE_ON) (NEW)
  3. auto (X86_INTEL_TSX_MODE_AUTO) (NEW)
choice[1-3?]: 1
==4.19.84 32bit config==

Code: Select all

TSX enable mode
> 1. off (X86_INTEL_TSX_MODE_OFF) (NEW)
  2. on (X86_INTEL_TSX_MODE_ON) (NEW)
  3. auto (X86_INTEL_TSX_MODE_AUTO) (NEW)
choice[1-3?]: 1

Please refer to the top article of this thread.
Porteus Kernel Builder


--------------------------------
@ralcocer
One of the applying the Porteus kernel to other distri which uses OverlayFS/AUFS is to AUSTRUMI.
I didn't know the Applying to Puppy.
Thank you for your information.


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2721
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#733 by Blaze » 15 Nov 2019, 09:11

neko, thank you so much, because you are :magic:

I have a few new requests :oops:
  • CONFIG_LIBCRC32C must to be set as M
    (Library routines ---> <M> CRC32c (Castagnoli, et al) Cyclic Redundancy-Check)

    Code: Select all

    CONFIG_LIBCRC32C=m
    Why M and not Y - look at this :url: description
  • CONFIG_CRYPTO_CRC32C_INTEL must to be set as Y
    (Cryptographic API ---> <*> CRC32c INTEL hardware acceleration )

    Code: Select all

    CONFIG_CRYPTO_CRC32C_INTEL=y
    Why Y and not M - look at this :url: Slackware64-current - ChangeLog

    Code: Select all

    # Sat Nov 16 03:31:45 UTC 2019
    testing/packages/kernel-source-5.4.0_rc7-noarch-2.txz:  Rebuilt.
      CRYPTO_CRC32C_INTEL m -> y
      Make modules before cleaning up the source tree. This does some magic in
      Module.symvers that fixes building the NVIDIA kernel modules.
    
    # Fri Nov 15 01:28:36 UTC 2019
    k/kernel-source-4.19.84-noarch-2.txz:  Rebuilt.
      CRYPTO_CRC32C_INTEL m -> y
      This fixes btrfs+crc32c-intel hardware acceleration. Thanks to nullptr.
  • request about rtwpci from roadie (look at this post)
    Realtek 802.11ac wireless chips support must to be set as M
    -> Realtek 8822BE PCI wireless network adapter must to be set as Y
    -> Realtek 8822CE PCI wireless network adapter must to be set as Y
    Device Drivers ---> Network device support ---> Wireless LAN ---> <M> Realtek 802.11ac wireless chips support --->
    --- Realtek 802.11ac wireless chips support
    [*] Realtek 8822BE PCI wireless network adapter
    [*] Realtek 8822CE PCI wireless network adapter

    Code: Select all

    CONFIG_RTW88=m
    CONFIG_RTW88_CORE=m
    CONFIG_RTW88_PCI=m
    CONFIG_RTW88_8822BE=y
    CONFIG_RTW88_8822CE=y
    # CONFIG_RTW88_DEBUG is not set
    # CONFIG_RTW88_DEBUGFS is not set
@all
I do not know what solution can be on this request from sam
At our forum we have many calls from users with wireless issues on Broadcom 43xx wireless devices.
If neko will apply this scheme - seems it will give a large size
Device Drivers > Network device support > Wireless LAN
Image

Code: Select all

[*]   Broadcom devices
<M>     Broadcom 43xx wireless support (mac80211 stack)
        Supported bus types (BCMA and SSB)  --->
[*]     Support for G-PHY (802.11g) devices (NEW)
[*]     Support for N-PHY (the main 802.11n series) devices (NEW)
[*]     Support for LP-PHY (low-power 802.11g) devices (NEW)
[*]     Support for HT-PHY (high throughput 802.11n) devices (NEW)
[ ]     Broadcom 43xx debugging (NEW)
<M>     Broadcom 43xx-legacy wireless support (mac80211 stack)
[ ]     Broadcom 43xx-legacy debugging 
        Broadcom 43xx-legacy data transfer mode (DMA + PIO)  --->
<M>     Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
<M>     Broadcom FullMAC WLAN driver
[*]     USB bus interface support for FullMAC driver
[*]     PCIE bus interface support for FullMAC driver
[ ]     Broadcom device tracing
[ ]     Broadcom driver debug functions (NEW)
In my variant it gives me additional activated options:

Code: Select all

--- .config.old	2019-11-16 13:11:53.779003611 +0000
+++ .config	2019-11-16 18:43:08.857000386 +0000
@@ -2005,10 +2005,43 @@
 # CONFIG_ATMEL is not set
 # CONFIG_AT76C50X_USB is not set
 CONFIG_WLAN_VENDOR_BROADCOM=y
-# CONFIG_B43 is not set
-# CONFIG_B43LEGACY is not set
-# CONFIG_BRCMSMAC is not set
-# CONFIG_BRCMFMAC is not set
+CONFIG_B43=m
+CONFIG_B43_BCMA=y
+CONFIG_B43_SSB=y
+CONFIG_B43_BUSES_BCMA_AND_SSB=y
+# CONFIG_B43_BUSES_BCMA is not set
+# CONFIG_B43_BUSES_SSB is not set
+CONFIG_B43_PCI_AUTOSELECT=y
+CONFIG_B43_PCICORE_AUTOSELECT=y
+CONFIG_B43_BCMA_PIO=y
+CONFIG_B43_PIO=y
+CONFIG_B43_PHY_G=y
+CONFIG_B43_PHY_N=y
+CONFIG_B43_PHY_LP=y
+CONFIG_B43_PHY_HT=y
+CONFIG_B43_LEDS=y
+CONFIG_B43_HWRNG=y
+# CONFIG_B43_DEBUG is not set
+CONFIG_B43LEGACY=m
+CONFIG_B43LEGACY_PCI_AUTOSELECT=y
+CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
+CONFIG_B43LEGACY_LEDS=y
+CONFIG_B43LEGACY_HWRNG=y
+# CONFIG_B43LEGACY_DEBUG is not set
+CONFIG_B43LEGACY_DMA=y
+CONFIG_B43LEGACY_PIO=y
+CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
+# CONFIG_B43LEGACY_DMA_MODE is not set
+# CONFIG_B43LEGACY_PIO_MODE is not set
+CONFIG_BRCMUTIL=m
+CONFIG_BRCMSMAC=m
+CONFIG_BRCMFMAC=m
+CONFIG_BRCMFMAC_PROTO_BCDC=y
+CONFIG_BRCMFMAC_PROTO_MSGBUF=y
+CONFIG_BRCMFMAC_USB=y
+CONFIG_BRCMFMAC_PCIE=y
+# CONFIG_BRCM_TRACING is not set
+# CONFIG_BRCMDBG is not set
 CONFIG_WLAN_VENDOR_CISCO=y
 # CONFIG_AIRO is not set
 # CONFIG_AIRO_CS is not set
@@ -2774,9 +2807,25 @@
 #
 # CONFIG_USBPCWATCHDOG is not set
 CONFIG_SSB_POSSIBLE=y
-# CONFIG_SSB is not set
+CONFIG_SSB=m
+CONFIG_SSB_SPROM=y
+CONFIG_SSB_BLOCKIO=y
+CONFIG_SSB_PCIHOST_POSSIBLE=y
+CONFIG_SSB_PCIHOST=y
+CONFIG_SSB_B43_PCI_BRIDGE=y
+CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
+# CONFIG_SSB_PCMCIAHOST is not set
+CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
+CONFIG_SSB_DRIVER_PCICORE=y
 CONFIG_BCMA_POSSIBLE=y
-# CONFIG_BCMA is not set
+CONFIG_BCMA=m
+CONFIG_BCMA_BLOCKIO=y
+CONFIG_BCMA_HOST_PCI_POSSIBLE=y
+CONFIG_BCMA_HOST_PCI=y
+# CONFIG_BCMA_HOST_SOC is not set
+CONFIG_BCMA_DRIVER_PCI=y
+# CONFIG_BCMA_DRIVER_GMAC_CMN is not set
+# CONFIG_BCMA_DEBUG is not set
 
 #
 # Multifunction device drivers
@@ -3373,6 +3422,8 @@
 CONFIG_USB_UHCI_HCD=y
 # CONFIG_USB_SL811_HCD is not set
 # CONFIG_USB_R8A66597_HCD is not set
+# CONFIG_USB_HCD_BCMA is not set
+# CONFIG_USB_HCD_SSB is not set
 # CONFIG_USB_HCD_TEST_MODE is not set
 
 #
@@ -4397,7 +4448,7 @@
 CONFIG_GENERIC_STRNLEN_USER=y
 CONFIG_GENERIC_NET_UTILS=y
 CONFIG_GENERIC_FIND_FIRST_BIT=y
-# CONFIG_CORDIC is not set
+CONFIG_CORDIC=m
 CONFIG_RATIONAL=y
 CONFIG_GENERIC_PCI_IOMAP=y
 CONFIG_GENERIC_IOMAP=y
If look at :url: CONFIG_B43: Broadcom 43xx wireless support (mac80211 stack)
This driver uses V4 firmware, which must be installed separately using b43-fwcutter.
I builded xzm module with these firmwares - Download b43-firmware-6.30.163.46-fw-1bl.xzm
WARNING! Need to extract content of this xzm module (of course except b43-firmware-6.30.163.46-fw-1bl/var directory) to 000-kernel

Any thoughts on this.

UPDATE.
At this moment jssouza and Blaze are vote for adding support of Broadcom 43xx wireless devices to kernel.

Thanks.
Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

neko
DEV Team
DEV Team
Posts: 1566
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#734 by neko » 18 Nov 2019, 06:36

1. Most recent version of build examples was updated.
5.4-rc8

Note 1: AUFS patch "5.x-rcN-20191021" is not yet ready for kernel version 5.4-rc.
It was patched by manual as same as patching to kernel version 5.4.0-rc2.
Porteus Kernel Builder (Post by neko #74116)

Code: Select all

# patch -p1 < ../../aufs.patch
patching file Documentation/ABI/testing/debugfs-aufs
patching file Documentation/ABI/testing/sysfs-aufs
patching file Documentation/filesystems/aufs/README
patching file Documentation/filesystems/aufs/design/01intro.txt
patching file Documentation/filesystems/aufs/design/02struct.txt
patching file Documentation/filesystems/aufs/design/03atomic_open.txt
patching file Documentation/filesystems/aufs/design/03lookup.txt
patching file Documentation/filesystems/aufs/design/04branch.txt
patching file Documentation/filesystems/aufs/design/05wbr_policy.txt
patching file Documentation/filesystems/aufs/design/06dirren.dot
patching file Documentation/filesystems/aufs/design/06dirren.txt
patching file Documentation/filesystems/aufs/design/06fhsm.txt
patching file Documentation/filesystems/aufs/design/06mmap.txt
patching file Documentation/filesystems/aufs/design/06xattr.txt
patching file Documentation/filesystems/aufs/design/07export.txt
patching file Documentation/filesystems/aufs/design/08shwh.txt
patching file Documentation/filesystems/aufs/design/10dynop.txt
patching file fs/aufs/Kconfig
patching file fs/aufs/Makefile
patching file fs/aufs/aufs.h
patching file fs/aufs/branch.c
patching file fs/aufs/branch.h
patching file fs/aufs/conf.mk
patching file fs/aufs/cpup.c
patching file fs/aufs/cpup.h
patching file fs/aufs/dbgaufs.c
patching file fs/aufs/dbgaufs.h
patching file fs/aufs/dcsub.c
patching file fs/aufs/dcsub.h
patching file fs/aufs/debug.c
patching file fs/aufs/debug.h
patching file fs/aufs/dentry.c
patching file fs/aufs/dentry.h
patching file fs/aufs/dinfo.c
patching file fs/aufs/dir.c
patching file fs/aufs/dir.h
patching file fs/aufs/dirren.c
patching file fs/aufs/dirren.h
patching file fs/aufs/dynop.c
patching file fs/aufs/dynop.h
patching file fs/aufs/export.c
patching file fs/aufs/f_op.c
patching file fs/aufs/fhsm.c
patching file fs/aufs/file.c
patching file fs/aufs/file.h
patching file fs/aufs/finfo.c
patching file fs/aufs/fstype.h
patching file fs/aufs/hbl.h
patching file fs/aufs/hfsnotify.c
patching file fs/aufs/hfsplus.c
patching file fs/aufs/hnotify.c
patching file fs/aufs/i_op.c
patching file fs/aufs/i_op_add.c
patching file fs/aufs/i_op_del.c
patching file fs/aufs/i_op_ren.c
patching file fs/aufs/iinfo.c
patching file fs/aufs/inode.c
patching file fs/aufs/inode.h
patching file fs/aufs/ioctl.c
patching file fs/aufs/lcnt.h
patching file fs/aufs/loop.c
patching file fs/aufs/loop.h
patching file fs/aufs/magic.mk
patching file fs/aufs/module.c
patching file fs/aufs/module.h
patching file fs/aufs/mvdown.c
patching file fs/aufs/opts.c
patching file fs/aufs/opts.h
patching file fs/aufs/plink.c
patching file fs/aufs/poll.c
patching file fs/aufs/posix_acl.c
patching file fs/aufs/procfs.c
patching file fs/aufs/rdu.c
patching file fs/aufs/rwsem.h
patching file fs/aufs/sbinfo.c
patching file fs/aufs/super.c
patching file fs/aufs/super.h
patching file fs/aufs/sysaufs.c
patching file fs/aufs/sysaufs.h
patching file fs/aufs/sysfs.c
patching file fs/aufs/sysrq.c
patching file fs/aufs/vdir.c
patching file fs/aufs/vfsub.c
patching file fs/aufs/vfsub.h
patching file fs/aufs/wbr_policy.c
patching file fs/aufs/whout.c
patching file fs/aufs/whout.h
patching file fs/aufs/wkq.c
patching file fs/aufs/wkq.h
patching file fs/aufs/xattr.c
patching file fs/aufs/xino.c
patching file include/uapi/linux/aufs_type.h
patching file MAINTAINERS
Hunk #1 succeeded at 2832 (offset 10 lines).
patching file drivers/block/loop.c
patching file fs/dcache.c
patching file fs/fcntl.c
patching file fs/inode.c
Hunk #1 succeeded at 1673 (offset 3 lines).
patching file fs/namespace.c
patching file fs/read_write.c
patching file fs/splice.c
patching file fs/sync.c
patching file include/linux/fs.h
Hunk #1 succeeded at 1349 (offset 18 lines).
Hunk #2 succeeded at 1836 (offset 25 lines).
Hunk #3 succeeded at 1907 (offset 25 lines).
Hunk #4 succeeded at 2333 (offset 27 lines).
Hunk #5 succeeded at 2622 (offset 27 lines).
patching file include/linux/lockdep.h
Hunk #1 succeeded at 331 (offset -3 lines).
Hunk #2 succeeded at 475 (offset -3 lines).
patching file include/linux/mnt_namespace.h
patching file include/linux/splice.h
patching file kernel/locking/lockdep.c
patching file fs/Kconfig
Hunk #1 FAILED at 261.
1 out of 1 hunk FAILED -- saving rejects to file fs/Kconfig.rej
patching file fs/Makefile
Hunk #1 FAILED at 130.
1 out of 1 hunk FAILED -- saving rejects to file fs/Makefile.rej
patching file drivers/block/loop.c
Hunk #10 succeeded at 1085 (offset 10 lines).
Hunk #11 succeeded at 1133 (offset 10 lines).
Hunk #12 succeeded at 1157 (offset 10 lines).
Hunk #13 succeeded at 1240 (offset 10 lines).
patching file drivers/block/loop.h
patching file fs/aufs/f_op.c
Hunk #1 succeeded at 369 (offset 10 lines).
patching file fs/aufs/loop.c
Hunk #1 succeeded at 146 (offset 13 lines).
patching file fs/aufs/loop.h
Hunk #1 succeeded at 39 (offset 13 lines).
Hunk #2 succeeded at 51 (offset 13 lines).
patching file fs/aufs/super.c
Hunk #1 succeeded at 857 (offset 13 lines).
patching file include/linux/fs.h
Hunk #1 succeeded at 1973 (offset 25 lines).
patching file fs/proc/base.c
patching file fs/proc/nommu.c
patching file fs/proc/task_mmu.c
Hunk #2 succeeded at 1822 with fuzz 2 (offset 12 lines).
patching file fs/proc/task_nommu.c
patching file include/linux/mm.h
Hunk #1 succeeded at 1510 (offset -28 lines).
patching file include/linux/mm_types.h
Hunk #1 succeeded at 267 (offset 5 lines).
Hunk #2 succeeded at 342 (offset 5 lines).
patching file kernel/fork.c
Hunk #1 succeeded at 562 (offset 9 lines).
patching file mm/Makefile
Hunk #1 succeeded at 42 (offset 3 lines).
patching file mm/filemap.c
Hunk #1 succeeded at 2696 (offset -25 lines).
patching file mm/mmap.c
Hunk #2 succeeded at 940 (offset 9 lines).
Hunk #3 succeeded at 1865 (offset 18 lines).
Hunk #4 succeeded at 2695 (offset 15 lines).
Hunk #5 succeeded at 2714 (offset 15 lines).
Hunk #6 succeeded at 2906 (offset 16 lines).
Hunk #7 succeeded at 2981 (offset 16 lines).
Hunk #8 succeeded at 3291 (offset 16 lines).
patching file mm/nommu.c
patching file mm/prfile.c
patching file fs/dcache.c
patching file fs/exec.c
patching file fs/fcntl.c
patching file fs/file_table.c
Hunk #2 succeeded at 313 with fuzz 2 (offset -15 lines).
Hunk #3 succeeded at 377 (offset 1 line).
patching file fs/inode.c
Hunk #1 succeeded at 1682 (offset 3 lines).
patching file fs/namespace.c
Hunk #3 succeeded at 1905 (offset 3 lines).
patching file fs/notify/group.c
Hunk #2 FAILED at 109.
Hunk #3 FAILED at 138.
2 out of 3 hunks FAILED -- saving rejects to file fs/notify/group.c.rej
patching file fs/notify/mark.c
Reversed (or previously applied) patch detected!  Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file fs/notify/mark.c.rej
patching file fs/open.c
patching file fs/read_write.c
patching file fs/splice.c
patching file fs/sync.c
patching file fs/xattr.c
patching file kernel/locking/lockdep.c
patching file kernel/task_work.c
patching file security/device_cgroup.c
patching file security/security.c
Hunk #1 succeeded at 1036 (offset 40 lines).
Hunk #2 succeeded at 1053 (offset 40 lines).
Hunk #3 succeeded at 1062 (offset 40 lines).
Hunk #4 succeeded at 1090 (offset 40 lines).
Hunk #5 succeeded at 1098 (offset 40 lines).
Hunk #6 succeeded at 1106 (offset 40 lines).
Hunk #7 succeeded at 1207 (offset 40 lines).
Hunk #8 succeeded at 1385 (offset 40 lines).
patching file include/linux/lockdep.h
patching file kernel/locking/lockdep.c
Hunk #1 succeeded at 4767 (offset 75 lines).
patching file kernel/locking/lockdep_internals.h
Hunk #1 FAILED at 93.
1 out of 1 hunk FAILED -- saving rejects to file kernel/locking/lockdep_internals.h.rej
patching file fs/mount.h
patching file fs/namespace.c
Hunk #1 succeeded at 1254 (offset 8 lines).
patching file fs/proc_namespace.c
patching file include/linux/shmem_fs.h
patching file mm/shmem.c
Hunk #1 succeeded at 128 (offset 15 lines).
Hunk #2 succeeded at 1115 (offset 15 lines).
Hunk #3 succeeded at 2244 (offset 15 lines).
Hunk #4 succeeded at 2294 (offset 15 lines).
Hunk #5 succeeded at 3318 (offset 15 lines).
Hunk #6 succeeded at 3338 (offset 15 lines).
Hunk #7 succeeded at 3354 (offset 15 lines).
Hunk #8 FAILED at 3411.
Hunk #9 FAILED at 3476.
Hunk #10 succeeded at 3600 (offset 75 lines).
Hunk #11 succeeded at 3624 (offset 75 lines).
Hunk #12 FAILED at 3569.
Hunk #13 succeeded at 3777 (offset 103 lines).
Hunk #14 succeeded at 3926 (offset 116 lines).
3 out of 14 hunks FAILED -- saving rejects to file mm/shmem.c.rej
patching file fs/inode.c
Hunk #1 succeeded at 885 (offset 3 lines).
Hunk #2 succeeded at 899 (offset 3 lines).
#
Note 2: update the config of kernel 5.4-rc8 with "make oldconfig" command.
==5.4-rc8 64bit config==

Code: Select all

TSX enable mode
> 1. off (X86_INTEL_TSX_MODE_OFF) (NEW)
  2. on (X86_INTEL_TSX_MODE_ON) (NEW)
  3. auto (X86_INTEL_TSX_MODE_AUTO) (NEW)
choice[1-3?]: 1
==5.4-rc8 32bit config==

Code: Select all

TSX enable mode
> 1. off (X86_INTEL_TSX_MODE_OFF) (NEW)
  2. on (X86_INTEL_TSX_MODE_ON) (NEW)
  3. auto (X86_INTEL_TSX_MODE_AUTO) (NEW)
choice[1-3?]: 1
Note 3:
Kernel by the Blaze requested config is being built now.

Please refer to the top article of this thread.
Porteus Kernel Builder


2. Kernel by the Blaze requested config
[5.4-rc8-2] : "Basic & Option patches" patching was done.
32bit-BPLUS-kernel5.4-rc8-2.tar (88 M)
http://www.mediafire.com/file/z8wksbmcq ... -rc8-2.tar
md5sum: f51d5c2c3723440afdc10ad85bd10f40 32bit-BPLUS-kernel5.4-rc8-2.tar

64bit-BPLUS-kernel5.4-rc8-2.tar (94 M)
http://www.mediafire.com/file/9xq5bysq2 ... -rc8-2.tar
md5sum: 5461e4d3e5596ba96d32b5f1dd1edfde 64bit-BPLUS-kernel5.4-rc8-2.tar


Note 1: diff 5.4-rc8 config 5.4-rc8-2 config
==64 Bit==

Code: Select all

2540,2541c2540,2545
< # CONFIG_RTW88_8822BE is not set
< # CONFIG_RTW88_8822CE is not set
---
> CONFIG_RTW88_CORE=m
> CONFIG_RTW88_PCI=m
> CONFIG_RTW88_8822BE=y
> CONFIG_RTW88_8822CE=y
> # CONFIG_RTW88_DEBUG is not set
> # CONFIG_RTW88_DEBUGFS is not set
6406c6410
< CONFIG_CRYPTO_CRC32C_INTEL=m
---
> CONFIG_CRYPTO_CRC32C_INTEL=y
==32 Bit==

Code: Select all

2520,2521c2520,2525
< # CONFIG_RTW88_8822BE is not set
< # CONFIG_RTW88_8822CE is not set
---
> CONFIG_RTW88_CORE=m
> CONFIG_RTW88_PCI=m
> CONFIG_RTW88_8822BE=y
> CONFIG_RTW88_8822CE=y
> # CONFIG_RTW88_DEBUG is not set
> # CONFIG_RTW88_DEBUGFS is not set
6374c6378
< CONFIG_CRYPTO_CRC32C_INTEL=m
---
> CONFIG_CRYPTO_CRC32C_INTEL=y
Note 2: Addtional firemware
> ====kernel/drivers/net/wireless/realtek/rtw88/rtw88.ko
> rtw88/rtw8822b_fw.bin
> rtw88/rtw8822c_fw.bin


Note 3:
Blaze's request is "CONFIG_LIBCRC32C must to be set as M".
But "CONFIG_LIBCRC32C" of 5.4-rc8-2 is "y".

Code: Select all

# grep CONFIG_LIBCRC32C v5.4-rc8/*/linux-5.4-rc8/.config
v5.4-rc8/32/linux-5.4-rc8/.config:CONFIG_LIBCRC32C=y
v5.4-rc8/64/linux-5.4-rc8/.config:CONFIG_LIBCRC32C=y
#
If no problem, it is not changed.
Because it will be needed with many processes.

Blaze explained:
(Library routines ---> <M> CRC32c (Castagnoli, et al) Cyclic Redundancy-Check)

"make menuconfig":
(Library routines ---> -*- CRC32c (Castagnoli, et al) Cyclic Redundancy-Check)

Code: Select all

┌─────────────────────────────────────────────────────────── Search Results ────────────────────────────────────────────────────────────┐
  │ Symbol: LIBCRC32C [=y]                                                                                                                │  
  │ Type  : tristate                                                                                                                      │  
  │ Prompt: CRC32c (Castagnoli, et al) Cyclic Redundancy-Check                                                                            │  
  │   Location:                                                                                                                           │  
  │ (1) -> Library routines                                                                                                               │  
  │   Defined at lib/Kconfig:222                                                                                                          │  
  │   Selects: CRYPTO [=y] && CRYPTO_CRC32C [=y]                                                                                          │  
  │   Selected by [y]:                                                                                                                    │  
  │   - XFS_FS [=y] && BLOCK [=y]                                                                                                         │  
  │   Selected by [m]:                                                                                                                    │  
  │   - NF_CT_PROTO_SCTP [=y] && NET [=y] && INET [=y] && NETFILTER [=y] && NF_CONNTRACK [=m] && NETFILTER_ADVANCED [=y]                  │  
  │   - MD_RAID456 [=m] && MD [=y] && BLK_DEV_MD [=m]                                                                                     │  
  │   - DM_PERSISTENT_DATA [=m] && MD [=y] && BLK_DEV_DM [=m]                                                                             │  
  │   - BNX2X [=m] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_BROADCOM [=y] && PCI [=y]                                            │  
  │   - BNXT [=m] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_BROADCOM [=y] && PCI [=y]                                             │  
  │   - LIQUIDIO [=m] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CAVIUM [=y] && 64BIT [=y] && PCI [=y]                             │  
  │   - BTRFS_FS [=m] && BLOCK [=y]                                                                                                       │  
  │   Selected by [n]:                                                                                                                    │  
  │   - CEPH_LIB [=n] && NET [=y] && INET [=y]                                                                                            │  
  │   - IP_SCTP [=n] && NET [=y] && INET [=y] && (IPV6 [=m] || IPV6 [=m]=n)                                                               │  
  │   - BATMAN_ADV [=n] && NET [=y]                                                                                                       │  
  │   - OPENVSWITCH [=n] && NET [=y] && INET [=y] && (!NF_CONNTRACK [=m] || NF_CONNTRACK [=m] && (!NF_DEFRAG_IPV6 [=m] || NF_DEFRAG_IPV6  │  
  │   - IP_VS_PROTO_SCTP [=n] && NET [=y] && NETFILTER [=y] && IP_VS [=n]                                                                 │  
  │   - NET_ACT_CSUM [=n] && NET [=y] && NET_SCHED [=n] && NET_CLS_ACT [=n] && INET [=y]                                                  │  
  │   - BLK_DEV_DRBD [=n] && BLK_DEV [=y] && PROC_FS [=y] && INET [=y]                                                                    │  
  │   - BLK_DEV_RBD [=n] && BLK_DEV [=y] && INET [=y] && BLOCK [=y]                                                                       │  
  │   - GFS2_FS [=n] && BLOCK [=y]                                                                                                        │  
  │   - CEPH_FS [=n] && NETWORK_FILESYSTEMS [=y] && INET [=y]  

Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2721
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#735 by Blaze » 19 Nov 2019, 12:56

neko, I see that you activated:

Code: Select all

CONFIG_B43=m
CONFIG_B43_BCMA=y
CONFIG_B43_SSB=y
CONFIG_B43_BUSES_BCMA_AND_SSB=y
# CONFIG_B43_BUSES_BCMA is not set
# CONFIG_B43_BUSES_SSB is not set
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_SDIO=y
CONFIG_B43_BCMA_PIO=y
CONFIG_B43_PIO=y
CONFIG_B43_PHY_G=y
CONFIG_B43_PHY_N=y
CONFIG_B43_PHY_LP=y
CONFIG_B43_PHY_HT=y
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_HWRNG=y
# CONFIG_B43LEGACY_DEBUG is not set
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
CONFIG_SSB_B43_PCI_BRIDGE=y
not bad if you add b43-firmware-6.30.163.46-fw-1bl.xzm
or :url: https://aur.archlinux.org/packages/b43-firmware/

Thanks.
Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

Post Reply