Bionic64 with more recent kernel? (Solved)

Message

fabrice_035 · #1 Post by **fabrice_035** » Sun 12 Apr 2020, 11:36

Hello, I would like to have a version of bionic64 with a kernel 5.x, can someone tell me how to do that ? Thanks

ozsouth · #2 Post by **ozsouth** » Sun 12 Apr 2020, 11:47

See a manual kernel change howto, with my 5.4.8 kernel (choose the ubuntu one & you will need the fdrv too) here:
http://murga-linux.com/puppy/viewtopic. ... 40#1049140

fabrice_035 · #3 Post by **fabrice_035** » Sun 12 Apr 2020, 12:23

@ozsouth Thanks, nice, it's working.

This will allow me to move forward on a problem I can't solve. My notebook is an asus rog GL752 and the shortcut to illuminate the keyboard doesn't work. I tried BarryK's EasyOS and the shortcut works. Curious
I'm continuing my research and thank you very much for your help.

enrique · #4 Post by **enrique** » Sun 12 Apr 2020, 20:03

fabrice_035
Try new kernel 1rst. I hope it helps.

If for any reason you need a little more help. here is what you can do. I am attaching a script. It will collect many information of your Puppy to a file systeminfo-report.txt. Then it will tar so that you can post results here. The we can inspect the file and make suggestions.

This is a standard file I made to help people like you. The important added lines for LED are at the end from line 146. If for any reason you do not want to post here you can do it by PM. If not you can look at those commands yourself to get useful information.

Hope it helps.
Enrique.

NOTE:
1) You got two scenarios:
BarryK's EasyOS - where you claim backlight works. And your Bionic64.
So you need to run it in both scenarios, so that you can compare the differences.

2) when you run the script, it will ask you to Turn ALL keyboard LEDs, Then Hit enter. Then turn on "CAPS" Capitals and Turn on the Back Light. Again to try to identify the correct settings.

3) Once we identify the correct settings we will find a way to activate you Short Cut.

See attachment.

fabrice_035 · #5 Post by **fabrice_035** » Sun 12 Apr 2020, 20:41

@Enrique

Thanks to help me.

https://pastebin.com/RqU7Efaw[quote][/quote]

enrique · #6 Post by **enrique** » Sun 12 Apr 2020, 22:28

fabrice_035

OK this is from the none working back-light on Bionicpup64
bionicpup64 Linux 5.4.8-64oz [x86_64 arch]

You got only 4 leds showing up on kernel

Code: Select all

/sys/class/leds/../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane/brightness
/sys/class/leds/../../devices/platform/i8042/serio0/input/input3/input3::numlock/brightness
/sys/class/leds/../../devices/platform/i8042/serio0/input/input3/input3::capslock/brightness
/sys/class/leds/../../devices/platform/i8042/serio0/input/input3/input3::scrolllock/brightness

Wireless, numlock, capslock, scrolllock.

You did not Turn on CAPS lock after ENTER. Do not worry.

It will be nice to see results on BarryK's EasyOS, so that we can compare with a working environment.

For the moment try this generic commands, see if it do something.

To turn ON

Code: Select all

xset led 3

To turn OFF

Code: Select all

xset -led 3

enrique · #7 Post by **enrique** » Sun 12 Apr 2020, 23:16

I believe I found what we should be looking.

Code: Select all

/sys/class/leds/asus::kbd_backlight/brightness

as if you do

Code: Select all

ls -la /sys/class/leds/asus::kbd_backlight/brightness

I got this from a good finding see:

Code: Select all

https://github.com/ktoso/g73-keyboard-backlight-sh/

Problem is it did not show up. My best guess is that we will be require to enable this on kernel.

Since we know it works in BarryK's EasyOS send me that results. Then we can compare kernel config to figure out what we need to enable.

At the moment this ones are the ones I see suspicious

Code: Select all

cat config-5.4.8-64oz | grep -i -e 'keyboard\|CONFIG_LEDS\|asus' | grep -e 'is not set'
# CONFIG_KEYBOARD_ADP5520 is not set
# CONFIG_KEYBOARD_APPLESPI is not set
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_LEDS_CLASS_FLASH is not set
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set
# CONFIG_LEDS_88PM860X is not set
# CONFIG_LEDS_APU is not set
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_PCA9532_GPIO is not set
# CONFIG_LEDS_GPIO is not set
# CONFIG_LEDS_CLEVO_MAIL is not set
# CONFIG_LEDS_PCA955X_GPIO is not set
# CONFIG_LEDS_WM831X_STATUS is not set
# CONFIG_LEDS_WM8350 is not set
# CONFIG_LEDS_DA903X is not set
# CONFIG_LEDS_DA9052 is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_ADP5520 is not set
# CONFIG_LEDS_MC13783 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_MAX8997 is not set
# CONFIG_LEDS_LM355x is not set
# CONFIG_LEDS_MENF21BMC is not set
# CONFIG_LEDS_BLINKM is not set
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_TI_LMU_COMMON is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
# CONFIG_LEDS_TRIGGER_DISK is not set
# CONFIG_LEDS_TRIGGER_MTD is not set
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not set
# CONFIG_LEDS_TRIGGER_GPIO is not set
# CONFIG_LEDS_TRIGGER_TRANSIENT is not set
# CONFIG_LEDS_TRIGGER_CAMERA is not set
# CONFIG_LEDS_TRIGGER_PANIC is not set
# CONFIG_LEDS_TRIGGER_NETDEV is not set
# CONFIG_LEDS_TRIGGER_PATTERN is not set

enrique · #8 Post by **enrique** » Sun 12 Apr 2020, 23:38

deleted

enrique · #9 Post by **enrique** » Mon 13 Apr 2020, 00:29

Another Idea to test. Drivers are been build as modules

Code: Select all

cat config-5.4.8-64oz | grep -i -e 'asus'
CONFIG_USB_PEGASUS=m
CONFIG_TABLET_USB_PEGASUS=m
CONFIG_HID_ASUS=m
CONFIG_ASUS_LAPTOP=m
CONFIG_ASUS_WIRELESS=m

I think module is asus-nb-wmi and looking at lsmod driver has not been loaded.

To show if module is loaded

Code: Select all

lsmod | grep asus-nb-wmi

Load module

Code: Select all

modprobe asus-nb-wmi

Now Test if we succeeded

Code: Select all

echo 2 /sys/devices/platform/asus-nb-wmi/leds/asus::kbd_backlight/brightness
echo 1 /sys/devices/platform/asus-nb-wmi/leds/asus::kbd_backlight/brightness
echo 0 /sys/devices/platform/asus-nb-wmi/leds/asus::kbd_backlight/brightness

Just in case is been populated some where else do

Code: Select all

find  /sys/devices/platform | grep -i -e 'brightness\|kbd_backlight'

enrique · #10 Post by **enrique** » Mon 13 Apr 2020, 01:37

I took another look. And in my Debian Buster config-4.19.0-6-amd64 I have two extra configs.

Code: Select all

CONFIG_ASUS_WMI=m
CONFIG_ASUS_NB_WMI=m

I have a feeling this are the missing ones. I will see if I have time to look into kernel sources of Bionic64.

EDIT:
I can build the modules easily, but they will not load as Kernel have set # CONFIG_HOTPLUG_PCI is not set
And CONFIG_HOTPLUG_PCI can not be build as a module in this kernel!!! So a New Kernel has to be build.

enrique · #11 Post by **enrique** » Mon 13 Apr 2020, 06:22

fabrice_035
I took some time last night to help you. As I said without more info I concluded you needed to build a new kernel, to enable asus requirements.

1rst test if this helps you. If it does, then try to learn to build it yourself. It is not that complex, only takes like 1.5 hours to do.

I will attached the 2 kernel files. Save the originals in a folder and then replace with the one I am giving you. If it does work let us know and I will let you know how you can learn to build it yourself.

Code: Select all

https://mega.nz/file/TLBFkIyT#CnGadolm0mxY8dwxAkRFKrIf3UlhGMgK-FGuf_o4Q1s

Hope it helps
enrique

fabrice_035 · #12 Post by **fabrice_035** » Mon 13 Apr 2020, 08:34

Hi,
thanks again for your help. You've done a lot of work for me, thank you.

--> 5.4.8 kernel (ozsouth kernel)

Code: Select all

lsmod | grep asus-nb-wmi

return nothing

I think you found the problem.

Then i installed your news files but unfortunately the boot remains blocked because x doesn't start. xorgwizard can't help me.

is it possible to add just the drivers "asus-nb-wmi" into 5.4.8 kernel (ozsouth kernel) ?

Regard

ozsouth · #13 Post by **ozsouth** » Mon 13 Apr 2020, 10:11

Unfortunately kernels need to be compiled (a 2-3 hour job) with those asus options enabled. Run lsmod & see if asus_laptop is loaded - if not try to modprobe that.

fabrice_035 · #14 Post by **fabrice_035** » Mon 13 Apr 2020, 10:33

there is no such module

Code: Select all

root# lsmod
Module                  Size  Used by
xt_pkttype             16384  1
xt_conntrack           16384  4
iptable_mangle         16384  0
iptable_nat            16384  0
nf_nat_ipv4            16384  1 iptable_nat
iptable_filter         16384  1
bnep                   20480  2
nf_conntrack_irc       16384  0
nf_nat_ftp             16384  0
nf_conntrack_ftp       16384  1 nf_nat_ftp
nf_nat                 32768  2 nf_nat_ftp,nf_nat_ipv4
nf_conntrack           86016  6 xt_conntrack,nf_nat,nf_nat_ftp,nf_nat_ipv4,nf_conntrack_irc,nf_conntrack_ftp
nf_defrag_ipv6         20480  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
ip_tables              28672  5 iptable_filter,iptable_nat,iptable_mangle
fan                    16384  0
snd_hda_codec_hdmi     45056  1
joydev                 20480  0
input_leds             16384  0
btusb                  40960  0
btrtl                  16384  1 btusb
btbcm                  16384  1 btusb
btintel                16384  1 btusb
bluetooth             311296  26 btrtl,btintel,btbcm,bnep,btusb
ecdh_generic           24576  1 bluetooth
uvcvideo               86016  0
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_memops       16384  1 videobuf2_vmalloc
videobuf2_v4l2         20480  1 uvcvideo
videodev              139264  2 videobuf2_v4l2,uvcvideo
videobuf2_common       36864  2 videobuf2_v4l2,uvcvideo
rtsx_pci_sdmmc         20480  0
rtsx_pci_ms            16384  0
pcspkr                 16384  0
iwlmvm                241664  0
mac80211              368640  1 iwlmvm
iwlwifi               196608  1 iwlmvm
r8169                  69632  0
realtek                20480  0
libphy                 49152  3 r8169,realtek
cfg80211              278528  3 iwlmvm,iwlwifi,mac80211
rfkill                 20480  3 bluetooth,cfg80211
snd_hda_intel          28672  0
snd_hda_codec          90112  2 snd_hda_codec_hdmi,snd_hda_intel
snd_hda_core           49152  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_pcm_oss            45056  0
snd_mixer_oss          24576  1 snd_pcm_oss
snd_pcm                77824  5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_hda_core
snd_seq_dummy          16384  0
snd_seq_oss            36864  0
i2c_i801               28672  0
snd_seq_midi           16384  0
snd_seq_midi_event     16384  2 snd_seq_midi,snd_seq_oss
snd_rawmidi            24576  1 snd_seq_midi
snd_seq                45056  6 snd_seq_midi,snd_seq_oss,snd_seq_midi_event,snd_seq_dummy
snd_seq_device         16384  4 snd_seq,snd_seq_midi,snd_seq_oss,snd_rawmidi
snd_timer              28672  2 snd_seq,snd_pcm
snd                    65536  11 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_seq_oss,snd_hda_intel,snd_hda_codec,snd_timer,snd_pcm_oss,snd_pcm,snd_rawmidi,snd_mixer_oss
soundcore              16384  1 snd
mei_me                 20480  0
mei                    57344  1 mei_me
idma64                 20480  0
virt_dma               16384  1 idma64
intel_lpss_pci         20480  0
intel_lpss             16384  1 intel_lpss_pci
i915                 1302528  4
i2c_algo_bit           16384  1 i915
drm_kms_helper        131072  1 i915
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
drm                   335872  5 drm_kms_helper,i915
mxm_wmi                16384  0
wmi                    20480  1 mxm_wmi
battery                20480  0
tpm_crb                16384  0
tpm_tis                16384  0
tpm_tis_core           20480  1 tpm_tis
tpm                    49152  3 tpm_tis,tpm_crb,tpm_tis_core
pcc_cpufreq            16384  0
asus_wireless          16384  0
acpi_pad               16384  0
ac                     16384  0

Code: Select all

root# modprobe asus_laptop
modprobe: ERROR: could not insert 'asus_laptop': No such device

Just need that https://cateee.net/lkddb/web-lkddb/ASUS_WMI.html

ozsouth · #15 Post by **ozsouth** » Mon 13 Apr 2020, 11:39

You need a kernel compiled with the asus options. I checked several in the puppy kernel archive, but none had it. However, BarryK's 5.4.27 kernel does. I have attached the DOTconfig, but perhaps Barry can supply you with a kernel package.

fabrice_035 · #16 Post by **fabrice_035** » Mon 13 Apr 2020, 11:50

thanks again, I'm going to ask a silly question but I don't know much about it, your file allows you to compile a new kernel with the right options? Me it would not make me happy to be able to do it without disturbing anybody then I will try to find a tutorial or to follow your method.

so I download the source kernel for example here
https://cdn.kernel.org/pub/linux/kernel/v5.x/
and I compile it with your configuration file?

fabrice_035 · #17 Post by **fabrice_035** » Mon 13 Apr 2020, 11:55

or can I find a working tutorial that you use to compile a kernel for puppy?

ozsouth · #18 Post by **ozsouth** » Mon 13 Apr 2020, 12:58

Even using Puppy Kernel-Kit which is the best & simplest way, there is a fair bit to learn. You need to set up a compiling environment, with devx & kernel headers loaded. You also need to work on a physical drive or you will run out of space. You need to have a working kernel-kit (from github - I use the master branch) & configured DOTconfig (stating gcc version) in appropriate folder. Also build.conf needs very careful editing. I won't publish my exact method publicly as there are dangers. I'm thinking of compiling a kernel tomorrow & will include asus if I do.

fabrice_035 · #19 Post by **fabrice_035** » Mon 13 Apr 2020, 13:45

I remain hopeful and thank you for your investments.
I tried with what's written here, but it didn't give a good result.

http://murga-linux.com/puppy/viewtopic.php?t=96723

enrique · #20 Post by **enrique** » Mon 13 Apr 2020, 14:31

fabrice_035

Then i installed your news files but unfortunately the boot remains blocked because x doesn't start. xorgwizard can't help me.

UPSSS! My apology. My test Puppy of Bionic64 is in fact a LXDE Remaster. And I have included the firmware.

In your case Xorg failed because the it most not have the firmware. My fault. You could create it from your actual files. But easy method. Try downloading

20.3 MB
https://sourceforge.net/projects/lxpup/ ... s/fdrv.sfs

And rename it fdrv_bionicpup64_8.0.sfs. Place it in your Puppy folder.

If it failed you could create it with yours or use this one where is more complete.
140 MB
http://smokey01.com/radky/Woof/fdrv_buster_8.0.sfs

again rename it fdrv_bionicpup64_8.0.sfs

Once you prove it works I show you the build process.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Bionic64 with more recent kernel? (Solved)

Bionic64 with more recent kernel? (Solved)