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: 995
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#181 by neko » 15 Aug 2017, 07:25

"Porteus Kernel Builder" was updated to mkKernel-17.08.15-noarch-1.xzm
Please refer to Porteus Kernel Builder (Post by neko #52232)

New own patch that was reported by raja was added. (@raja, thank you.)
This patch will be applied to drivers/acpi/sleep.c .
Please refer to https://patchwork.kernel.org/patch/9041141/

If "own patch" item in "Build kernel" circle of "Kernel Builder" setting window is set,
this patch will be applied to drivers/acpi/sleep.c.

This "own patch" is available for version line 4.1, 4.4, 4.9, 4.12 and 4.13-rc.

To avoid syntax error,
version line 4.12 and 4.13-rc need another "own patch" that will be applied to drivers/block/loop.c.
Setting "own patch" item make 2 patch be applied.
If you do not need new patch, tune as followed before executing "Kernel Builder".
And then execute with setting "own patch" item.
[4.12 line]

Code: Select all

% su
# rm /usr/local/share/mkKernel/lib/v4.12/ownPatch.sh
# ln -sf ownPatch1.sh /usr/local/share/mkKernel/lib/v4.12/ownPatch.sh
[4.13-rc line]

Code: Select all

% su
# rm /usr/local/share/mkKernel/lib/v4.13-rc/ownPatch.sh
# ln -sf ownPatch1.sh /usr/local/share/mkKernel/lib/v4.13-rc/ownPatch.sh
Thanks.

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

Porteus Kernel Builder

Post#182 by neko » 16 Aug 2017, 07:48

NEW Example of updated kernels that were built by "Porteus Kernel builder" were updated.

Refer to Porteus Kernel Builder (Post by neko #57468)
or
refer to Porteus Kernel Builder (Post by neko #52232)

At the time of building version 4.13-rc5/4.12.8 kernel,
the patch to drivers/block/loop.c and the patch to drivers/acpi/sleep.c were applied.


At the time of building version 4.9.44/4.4.83 kernel,
the patch to drivers/acpi/sleep.c was applied.



Thanks.

privateip
White ninja
White ninja
Posts: 14
Joined: 17 Aug 2017, 18:34
Distribution: LFS

Porteus Kernel Builder

Post#183 by privateip » 17 Aug 2017, 19:10

notice this while booting, after doing 4.9.43 x64

^ copying Porteus data to RAM, this may take some time...
-> 000-kernel.xzm
-> 001-core.xzm
-> 002-xorg.xzm
-> 003-xfce.xzm
^ copying content of /mnt/sda1/porteus/rootcopy directory
BusyBox v1.25.1 (2016-10-10 13:32:29 MSK) multi-call binary

Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
losetup -d LOOPDEV - disassociate
losetup -a - show status
losetup -f - show next free loop device

-o OFS Start OFS bytes into FILE
- r Read-only
-f Show/use next free loop device
sh: 7: unknown operand
^ changing root directory
live system is ready now - starting Porteus

how to clean up sh: 7: unknown operand?

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

Porteus Kernel Builder

Post#184 by neko » 18 Aug 2017, 09:27

@privateip
Sorry, it is impossible for me to understand your post.

This thread is for "Porteus Kernel Builder", not for "BusyBox".

If something problem are concerned to "Porteus Kernel Builder", please point out the problem function of "Porteus Kernel Builder".

Thanks.

privateip
White ninja
White ninja
Posts: 14
Joined: 17 Aug 2017, 18:34
Distribution: LFS

Porteus Kernel Builder

Post#185 by privateip » 18 Aug 2017, 16:01

@neko,
I attached both screenshots in below post to explain my issue better,

1st ~ boot up using official Porteus-XFCE-v3.2.2-x86_64.iso
Image

2nd - boot up using Porteus Kernel Builder with kernel 4.9.43 - UP.Porteus-XFCE-v3.2.2-x86_64.iso
Image

sh: 7: unknown operand appeared in Porteus Kernel Builder built kernel.

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

Porteus Kernel Builder

Post#186 by neko » 19 Aug 2017, 04:19

@privateip
Thank you for your exact explanation with using pictures.
It makes my stupid head understand your situation.

====< guess >====
I guess your operation.
"ISO whose kernel will be update" item was set with "Porteus-XFCE-v3.2.2-x86_64.iso".
"keep org" item might be checked off.

====< correct >====
Please make UP.Porteus-XFCE-v3.2.2-x86_64.iso by checking on "keep org" item.

====< "keep org" item >====
"on": for Porteus & Nemesis
The original ISO's initrd.xz will be copied to updated ISO.
BusyBox of the original ISO's initrd.xz is ported from Slackware.

"off": for APorteus
The new created initrd.xz will be set in updated ISO.
BusyBox of the new created initrd.xz is ported from ArchLinux.
The new created initrd.xz has the processer routines for Porteus & Nemesis.
These routines are not yet rewritten. (old code)
--->
ArchLinux BusyBox and this old code might be mismatched on usage.

====< test >====
I have done 2 tests.
1.make UP.Porteus-XFCE-v3.2.2-x86_64.iso by checking on "keep org" item.
result: OK
2.make UP.Porteus-XFCE-v3.2.2-x86_64.iso by checking off "keep org" item.
result: same as you.


Thanks.

privateip
White ninja
White ninja
Posts: 14
Joined: 17 Aug 2017, 18:34
Distribution: LFS

Porteus Kernel Builder

Post#187 by privateip » 19 Aug 2017, 10:17

Thanks neko for prompt reply, I redo using 4.9.44 now. :)

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

Porteus Kernel Builder

Post#188 by neko » 21 Aug 2017, 09:40

NEW Example of updated kernels that were built by "Porteus Kernel builder" were updated.

Refer to Porteus Kernel Builder (Post by neko #57468)
or
refer to Porteus Kernel Builder (Post by neko #52232)


Thanks.

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

Porteus Kernel Builder

Post#189 by neko » 25 Aug 2017, 13:23

NEW Example of updated kernels that were built by "Porteus Kernel builder" were updated.

Refer to Porteus Kernel Builder (Post by neko #57468)
or
refer to Porteus Kernel Builder (Post by neko #52232)

At the time of building version 4.13-rc6 kernel,
the patch to drivers/block/loop.c
and
the patch to drivers/acpi/sleep.c
were applied.

At the time of building version 4.12.9 kernel,
the patch to drivers/block/loop.c,
the patch to drivers/acpi/sleep.c
and
the patch to drivers/mfd/intel-lpss-pci.c
were applied.

At the time of building version 4.9.45/4.4.84 kernel,
the patch to drivers/acpi/sleep.c
and
the patch to drivers/mfd/intel-lpss-pci.c
were applied.

-----------------------
[the patch to drivers/mfd/intel-lpss-pci.c]
It was reported by raja. (@raja, thank you.)
Please refer to ArchLinux packages manager for Porteus (Post by raja #57944)

"Kernel Builder" does not yet include this patch interface.
At next update of "Kernel Builder", its interface will be included.


Thanks.

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

Porteus Kernel Builder

Post#190 by neko » 26 Aug 2017, 13:21

"Porteus Kernel Builder" was updated to mkKernel-17.08.26-noarch-1.xzm
Please refer to Porteus Kernel Builder (Post by neko #52232)

New own patch that was reported by raja was added. (@raja, thank you.)
This patch will be applied to drivers/mfd/intel-lpss-pci.c .
Please refer to ArchLinux packages manager for Porteus (Post by raja #57944)

[ own patch ]
There are 3 own patches.
(1) patch to drivers/block/loop.c
to fix AUFS syntax error.
(2) patch to drivers/acpi/sleep.c
to fix reboot/shutdown problem.
(3) patch to drivers/mfd/intel-lpss-pci.c <---- NEW
to fix "Touch Pad" problem.

"own patch" button is available for following version line.
=== version line 4.13-rc ===
patch to drivers/block/loop.c
patch to drivers/acpi/sleep.c
patch to drivers/mfd/intel-lpss-pci.c

=== version line 4.12 ===
patch to drivers/block/loop.c
patch to drivers/acpi/sleep.c
patch to drivers/mfd/intel-lpss-pci.c

=== version line 4.9 ===
patch to drivers/acpi/sleep.c
patch to drivers/mfd/intel-lpss-pci.c

=== version line 4.4 ===
patch to drivers/acpi/sleep.c
patch to drivers/mfd/intel-lpss-pci.c

=== version line 4.1 ===
patch to drivers/acpi/sleep.c


Thanks.

Falcony
Full of knowledge
Full of knowledge
Posts: 235
Joined: 01 Jan 2011, 12:44
Location: Russia

Porteus Kernel Builder

Post#191 by Falcony » 28 Aug 2017, 06:05

neko,

is it possible to add patch for .config files to support Toshiba notebook? There are many such PC now and users complains that porteus boot for them only in debug mode.

Currently default config have options with "n". If possibel please change it to

CONFIG_TOSHIBA=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_TOSHIBA_FIR=m
CONFIG_PATA_TOSHIBA=m
CONFIG_MMC_TOSHIBA_PCI=m
CONFIG_TOSHIBA_BT_RFKILL=m
CONFIG_TOSHIBA_HAPS=m
CONFIG_TOSHIBA_WMI=m

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

Porteus Kernel Builder

Post#192 by neko » 28 Aug 2017, 06:31

1. "Porteus Kernel Builder" was updated to mkKernel-17.08.28-noarch-1.xzm
Please refer to Porteus Kernel Builder (Post by neko #52232)

version line 4.13-rc patch to drivers/block/loop.c was updated.

NOTE:
If you will build kernel earlier version than 4.13-rc7,
you could use
the patch:
/usr/local/share/mkKernel/lib/v4.13-rc/own.patch.v4.13-rc6.drivers+block+loop.c
the 32bit config:
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.v4.13-rc6.config
the 64bit config:
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.v4.13-rc6.config

2. NEW Example of updated kernels that were built by "Porteus Kernel builder" were updated.

Refer to Porteus Kernel Builder (Post by neko #57468)
or
refer to Porteus Kernel Builder (Post by neko #52232)

At the time of building version 4.13-rc7 kernel,
the patch to drivers/block/loop.c,
the patch to drivers/acpi/sleep.c
and
the patch to drivers/mfd/intel-lpss-pci.c
were applied.


Thanks.

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

Porteus Kernel Builder

Post#193 by neko » 28 Aug 2017, 07:59

@Falcony
"is it possible.... ?"
Yes, it is.

Please refer to Porteus Kernel Builder

[How to use]
step 1. prepare compile environment.
step 2. set working direcory.
step 3. select kernel version.
step 4. (option) "Build kernel" circle
"32Bit" item:
"download" item:
"expand & patch" item:
"own patch" item:

modify .config with "make menuconfig" command.

step 2. set working direcory.
step 3. select kernel version.
step 4. (option) "Build kernel" circle
"32Bit" item:
"compile" item:


[How to set with "make menuconfig" command]
1. CONFIG_TOSHIBA=y
"Processor type and feature" ---> <*> "Toshiba Laptop support"
2. CONFIG_TOSHIBA_FIR=m
"Networking support" ---> "IrDA (infrared) subsystem support" ---> "Infrared-port device drivers" ---> <M> "Toshiba Type-O IR Port"


[Note]:
At next uploading of example kernel, its 32Bit config will be updated.



[current config]

Code: Select all

% grep TOSHIBA /usr/local/share/mkKernel/lib/*/*.config
/usr/local/share/mkKernel/lib/v3.18/32bit.config:CONFIG_TOSHIBA=m
/usr/local/share/mkKernel/lib/v3.18/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v3.18/32bit.config:CONFIG_TOSHIBA_FIR=m
/usr/local/share/mkKernel/lib/v3.18/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v3.18/32bit.config:CONFIG_ACPI_TOSHIBA=m
/usr/local/share/mkKernel/lib/v3.18/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v3.18/32bit.config:CONFIG_TOSHIBA_HAPS=m

/usr/local/share/mkKernel/lib/v3.18/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v3.18/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v3.18/64bit.config:CONFIG_ACPI_TOSHIBA=m
/usr/local/share/mkKernel/lib/v3.18/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v3.18/64bit.config:CONFIG_TOSHIBA_HAPS=m

/usr/local/share/mkKernel/lib/v4.1/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.1/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.1/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.1/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.1/32bit.config:# CONFIG_MMC_TOSHIBA_PCI is not set
/usr/local/share/mkKernel/lib/v4.1/32bit.config:CONFIG_ACPI_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.1/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.1/32bit.config:CONFIG_TOSHIBA_HAPS=m

/usr/local/share/mkKernel/lib/v4.1/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.1/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.1/64bit.config:# CONFIG_MMC_TOSHIBA_PCI is not set
/usr/local/share/mkKernel/lib/v4.1/64bit.config:CONFIG_ACPI_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.1/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.1/64bit.config:CONFIG_TOSHIBA_HAPS=m

/usr/local/share/mkKernel/lib/v4.10/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.10/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.10/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.10/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.10/32bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.10/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.10/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.10/32bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.10/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.10/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.10/64bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.10/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.10/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.10/64bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.11/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.11/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.11/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.11/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.11/32bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.11/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.11/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.11/32bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.11/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.11/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.11/64bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.11/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.11/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.11/64bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.12/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.12/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.12/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.12/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.12/32bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.12/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.12/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.12/32bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.12/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.12/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.12/64bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.12/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.12/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.12/64bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.13-rc/32bit.ov.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.13-rc/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.13-rc/64bit.ov.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.ov.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.ov.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.ov.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.ov.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.13-rc/64bit.ov.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.4/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.4/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.4/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.4/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.4/32bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.4/32bit.config:# CONFIG_ACPI_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.4/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.4/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.4/32bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.4/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.4/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.4/64bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.4/64bit.config:# CONFIG_ACPI_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.4/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.4/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.4/64bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.7/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.7/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.7/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.7/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.7/32bit.config:# CONFIG_MMC_TOSHIBA_PCI is not set
/usr/local/share/mkKernel/lib/v4.7/32bit.config:CONFIG_ACPI_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.7/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.7/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.7/32bit.config:# CONFIG_TOSHIBA_WMI is not set

/usr/local/share/mkKernel/lib/v4.7/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.7/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.7/64bit.config:# CONFIG_MMC_TOSHIBA_PCI is not set
/usr/local/share/mkKernel/lib/v4.7/64bit.config:CONFIG_ACPI_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.7/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.7/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.7/64bit.config:# CONFIG_TOSHIBA_WMI is not set

/usr/local/share/mkKernel/lib/v4.8/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.8/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.8/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.8/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.8/32bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.8/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.8/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.8/32bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.8/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.8/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.8/64bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.8/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.8/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.8/64bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.9/32bit.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.9/32bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.9/32bit.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.9/32bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.9/32bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.9/32bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.9/32bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.9/32bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:# CONFIG_TOSHIBA is not set
/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:# CONFIG_TOSHIBA_FIR is not set
/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.9/32bit.ov.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.9/64bit.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.9/64bit.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.9/64bit.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.9/64bit.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.9/64bit.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.9/64bit.config:CONFIG_TOSHIBA_WMI=m

/usr/local/share/mkKernel/lib/v4.9/64bit.ov.config:CONFIG_YENTA_TOSHIBA=y
/usr/local/share/mkKernel/lib/v4.9/64bit.ov.config:CONFIG_PATA_TOSHIBA=m
/usr/local/share/mkKernel/lib/v4.9/64bit.ov.config:CONFIG_MMC_TOSHIBA_PCI=m
/usr/local/share/mkKernel/lib/v4.9/64bit.ov.config:CONFIG_TOSHIBA_BT_RFKILL=m
/usr/local/share/mkKernel/lib/v4.9/64bit.ov.config:CONFIG_TOSHIBA_HAPS=m
/usr/local/share/mkKernel/lib/v4.9/64bit.ov.config:CONFIG_TOSHIBA_WMI=m
Thanks.

raja
Black ninja
Black ninja
Posts: 65
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

Porteus Kernel Builder

Post#194 by raja » 28 Aug 2017, 09:06

Thanks neko.
Tried Acer 15E with intel pci-i2c patch.

Previously there was nothing about mouse in dmesg log. now, after the patch,

Code: Select all

0.000000] Linux version 4.12.9-porteus (root@porteus) (gcc version 7.1.1 20170630 (GCC) ) #1 SMP PREEMPT Fri Aug 25 14:48:31 UTC 2017
[    0.000000] Command line: \boot\syslinux\vmlinuz initrd=boot\syslinux\initrd.xz

i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[    0.871404] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    0.873268] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.873367] mousedev: PS/2 mouse device common for all mice
Acer has implemented Microsoft's precision mouse guidelines using USB hub connected to I2c bus. Windows 10 reports this Touchpad as I2C HID Device. Since it is a Microsoft design, it has got proper I2C driver which works well.

https://docs.microsoft.com/en-us/window ... nnectivity

But Linux lags behind, though this Laptop has loaded I2C_hid Kernel module, it is not loading synaptics_i2c.ko driver. I tried modprobe to load this. But it reports fetal error... no such file or directory, though it is there in /drivers/mouse. Why? any answers! I tried with terminal opened in the very 'mouse' directory.

from the dmesg, it is clear the PS2 mouse port is disabled.

There was a suggestion to black list i2c_hid module and go back to PS2 port. I did not try. Is it worth?

Thanks again,this is for information. Solutions are welcome. This touchpad is not listed in /proc/bus/input/devices.

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

Porteus Kernel Builder

Post#195 by neko » 30 Aug 2017, 02:59

@Falcony
1. Example that 32 Bit 4.13-rc7 kernel was built with config "CONFIG_TOSHIBA=y".

v4.13-rc7-2.tar.xz (20 M)
http://www.mediafire.com/file/uaupr08bx ... 7-2.tar.xz
md5sum: de1cd250a69b2da91f2e064d9ceb1ec6 v4.13-rc7-2.tar.xz

crippled_sources-4.13-rc7-2-32bit.xzm (19 M)
http://www.mediafire.com/file/utclxpkbc ... -32bit.xzm
md5sum: c8df04d349d42bd6bb7dc9f9eb9d47a6 crippled_sources-4.13-rc7-2-32bit.xzm

Code: Select all

% grep TOSHIBA .config
CONFIG_TOSHIBA=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_TOSHIBA_FIR=m
CONFIG_PATA_TOSHIBA=m
CONFIG_MMC_TOSHIBA_PCI=m
CONFIG_TOSHIBA_BT_RFKILL=m
CONFIG_TOSHIBA_HAPS=m
CONFIG_TOSHIBA_WMI=m
2. APorteus ISO that was constructed with this kernel was created.
Please refer to ArchLinux packages manager for Porteus (Post by neko #58031)


Thanks.

Post Reply