Update the kernel of Porteus v3.1

[beny]

hi Ed_P maybe the network device section on neko kernel is build like modules so you can recall via modprobe,i have see if i use a huge config in porteus-nemesis the system don't boot,so i have used the brokenman slim config and it work.try if this is possible via modprobe,you can see the modules in the lib/modules/modules.dep

[Ed_P]

My normal 3.1 LXQT system with a 3.x kernel supports my network config ok on my netbook. I'll try the modprobe on that and see what it shows.

[neko]

@beny and @Ed_P

If you get a good result,
would you tell me the method by which the good result was gotten ?

I will follow it at next update.
I want to make this tool better.

Excuse me for there might be many issues caused depending on my poor skill.

Thanks.

[Ed_P]

try if this is possible via modprobe,you can see the modules in the lib/modules/modules.dep

beny with Porteus 3.1 LXQT on my netbook modprobe -c is hundreds of lines long. Which ones are you looking for? And with the 3.x kernel nor the 4.3 kernel I have no /lib/modules/modules.dep file.

-edit-

I do have a /lib/modules/3.14.15-porteus/ folder with 3.x and I suspect the 4.3 kernel system has something similar. I also see in the /lib/modules/3.14.15-porteus/kernel/drivers/net/wireless folders drivers that support the network on my netbook. I suspect one or more of them is missing in the 4.3 kernel's matching folder.

I see a very long modules.dep file in the /lib/modules/3.14.15-porteus folder. Is this what you were referring to?

[beny]

hi, in modules.dep you have kernel/driver/net have the ethernet,wan and wireless driver for a lot of device so you have to know yours and modprobe this module, you can search in:/lib/modules/4.1.10-zen/ok this is mine.

[Ed_P]

hi, in modules.dep you have kernel/driver/net have the ethernet,wan and wireless driver for a lot of device so you have to know yours and modprobe this module

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# modprobe -c | grep .wan
alias usb:v03F0p1F1Dd*dc*dsc*dp*ic*isc*ip*in03* qmi_wwan
alias usb:v03F0p251Dd*dc*dsc*dp*ic*isc*ip*in00* qmi_wwan
alias usb:v03F0p371Dd*dc*dsc*dp*ic*isc*ip*in00* qmi_wwan
alias usb:v0408pEA42d*dc*dsc*dp*ic*isc*ip*in04* qmi_wwan
alias usb:v04DAp250Dd*dc*dsc*dp*ic*isc*ip*in03* qmi_wwan
alias usb:v05C6p7000d*dc*dsc*dp*ic*isc*ip*in00* qmi_wwan
alias usb:v05C6p7001d*dc*dsc*dp*ic*isc*ip*in01* qmi_wwan
 :
plus a hundred more
 :
alias usb:v413Cp81A3d*dc*dsc*dp*ic*isc*ip*in08* qmi_wwan
alias usb:v413Cp81A4d*dc*dsc*dp*ic*isc*ip*in08* qmi_wwan
alias usb:v413Cp81A8d*dc*dsc*dp*ic*isc*ip*in08* qmi_wwan
alias usb:v413Cp81A9d*dc*dsc*dp*ic*isc*ip*in08* qmi_wwan
alias symbol:flexcop_wan_set_speed b2c2_flexcop
alias symbol:usb_wwan_chars_in_buffer usb_wwan
alias symbol:usb_wwan_close usb_wwan
alias symbol:usb_wwan_dtr_rts usb_wwan
alias symbol:usb_wwan_ioctl usb_wwan
alias symbol:usb_wwan_open usb_wwan
alias symbol:usb_wwan_port_probe usb_wwan
alias symbol:usb_wwan_port_remove usb_wwan
alias symbol:usb_wwan_resume usb_wwan
alias symbol:usb_wwan_set_termios usb_wwan
alias symbol:usb_wwan_suspend usb_wwan
alias symbol:usb_wwan_tiocmget usb_wwan
alias symbol:usb_wwan_tiocmset usb_wwan
alias symbol:usb_wwan_write usb_wwan
alias symbol:usb_wwan_write_room usb_wwan
root@porteus:/home/guest# modprobe -c | grep ethernet.wan
root@porteus:/home/guest# modprobe -c | grep ethernet
alias symbol:usbnet_get_ethernet_addr usbnet
root@porteus:/home/guest# 

Is there a way to compare the list of driver files in 3.x with the list of driver files in 4.3 to see what doesn't match?

When updating a kernel can the driver folders from the base kernel be copied to the new kernel and then the new kernel's drivers superimposed upon it? The thought being any old drivers not updated would still be available in the new kernel.

[beny]

no only the firmware, the driver follow the kernel release so you can't use a mix of two kernel modules,porteus have the hardware detection tool if i remember well so you can detect your net device and compare it with the modules list,ok is a boring task,but before the downgrade of kernel,you can do a try.

[Ed_P]

Any of this help?

Code: Select all

guest@porteus:~$ cat /home/guest/Desktop/psinfo3x.txt | grep network
network-manager-applet-0.9.8.8-x86_64-1ftm
network-scripts-14.1-noarch-2
Dec 29 01:40:39 porteus NetworkManager[3528]: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'QuickMoose'.
Dec 29 07:11:59 porteus NetworkManager[3528]: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'QuickMoose'.
Dec 29 09:12:22 porteus NetworkManager[3528]: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'QuickMoose'.
guest@porteus:~$ cat /home/guest/Desktop/psinfo.txt | grep wifi
guest@porteus:~$ cat /home/guest/Desktop/psinfo.txt | grep wi-fi
guest@porteus:~$ cat /home/guest/Desktop/psinfo.txt | grep WiFi
Dec 29 01:40:36 porteus NetworkManager[3528]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:15.3/0000:07:00.0/ieee80211/phy0/rfkill1) (driver wl)
Dec 29 01:40:36 porteus NetworkManager[3528]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (platform driver acer-wmi)
Dec 29 01:40:36 porteus NetworkManager[3528]: <info> WiFi hardware radio set enabled
Dec 29 01:40:36 porteus NetworkManager[3528]: <info> WiFi enabled by radio killswitch; enabled by state file
Dec 29 01:40:36 porteus NetworkManager[3528]: <info> (eth1): using nl80211 for WiFi device control
Dec 29 01:40:36 porteus NetworkManager[3528]: <info> (eth1): new 802.11 WiFi device (driver: 'wl' ifindex: 3)
guest@porteus:~$ 

Code: Select all

psinfo from 3.x kernel
guest@porteus:~$ cat /home/guest/psinfo3x.txt | grep WiFi
Dec 29 14:18:02 porteus NetworkManager[3583]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:15.3/0000:07:00.0/ieee80211/phy0/rfkill1) (driver wl)
Dec 29 14:18:02 porteus NetworkManager[3583]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (platform driver acer-wmi)
Dec 29 14:18:02 porteus NetworkManager[3583]: <info> WiFi hardware radio set enabled
Dec 29 14:18:02 porteus NetworkManager[3583]: <info> WiFi enabled by radio killswitch; enabled by state file
Dec 29 14:18:02 porteus NetworkManager[3583]: <info> (eth1): using nl80211 for WiFi device control
Dec 29 14:18:02 porteus NetworkManager[3583]: <info> (eth1): new 802.11 WiFi device (driver: 'wl' ifindex: 3)

psinfo from 4.3 kernel
guest@porteus:~$ cat /home/guest/psinfo43.txt | grep WiFi
Dec 29 14:14:05 porteus NetworkManager[1910]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (platform driver acer-wmi)
Dec 29 14:14:05 porteus NetworkManager[1910]: <info> WiFi hardware radio set enabled
Dec 29 14:14:05 porteus NetworkManager[1910]: <info> WiFi enabled by radio killswitch; enabled by state file
guest@porteus:~$ 

[Jack]

Well I try it with this "upkernel-3.18.25-noarch-1.xzm" and "Porteus-MATE-v3.1-x86_64.iso" and I will build on a thumb drive and get back.

Here is the output what I did. And this was my first try.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# cd Downloads/working
root@porteus:/home/guest/Downloads/working# ls -l
total 253448
-rwxrwxrwx 1 guest guest 217591808 Dec 14  2014 Porteus-MATE-v3.1-x86_64.iso*
-rw-r--r-- 1 guest guest  41938944 Jan  1 14:02 upkernel-3.18.25-noarch-1.xzm
root@porteus:/home/guest/Downloads/working# md5sum *
d133e1dfff7a255045abfff90d2061dc  Porteus-MATE-v3.1-x86_64.iso
d905a2d98c97160d38efe4c14bce4d9b  upkernel-3.18.25-noarch-1.xzm
root@porteus:/home/guest/Downloads/working# su
root@porteus:/home/guest/Downloads/working# activate upkernel-3.18.25-noarch-1.xzm
Updating shared library links:  /sbin/ldconfig
root@porteus:/home/guest/Downloads/working# upkernel Porteus-MATE-v3.1-x86_64.iso
mount: block device /home/guest/Downloads/working/Porteus-MATE-v3.1-x86_64.iso is write-protected, mounting read-only
Setting input-charset to 'UTF-8' from locale.
3.01a16 (x86_64-unknown-linux-gnu)
Scanning UP.Porteus-MATE-v3.1-x86_64
Scanning UP.Porteus-MATE-v3.1-x86_64/EFI
Scanning UP.Porteus-MATE-v3.1-x86_64/EFI/BOOT
Scanning UP.Porteus-MATE-v3.1-x86_64/EFI/BOOT/drivers_x64
Scanning UP.Porteus-MATE-v3.1-x86_64/EFI/BOOT/icons
Scanning UP.Porteus-MATE-v3.1-x86_64/boot
Scanning UP.Porteus-MATE-v3.1-x86_64/boot/docs
Scanning UP.Porteus-MATE-v3.1-x86_64/boot/syslinux
Excluded by match: UP.Porteus-MATE-v3.1-x86_64/boot/syslinux/isolinux.boot
Scanning UP.Porteus-MATE-v3.1-x86_64/porteus
Scanning UP.Porteus-MATE-v3.1-x86_64/porteus/optional
Scanning UP.Porteus-MATE-v3.1-x86_64/porteus/rootcopy
Scanning UP.Porteus-MATE-v3.1-x86_64/porteus/modules
Scanning UP.Porteus-MATE-v3.1-x86_64/porteus/base
Writing:   Initial Padblock                        Start Block 0
Done with: Initial Padblock                        Block(s)    16
Writing:   Primary Volume Descriptor               Start Block 16
Done with: Primary Volume Descriptor               Block(s)    1
Writing:   Eltorito Volume Descriptor              Start Block 17
Size of boot image is 4 sectors -> No emulation
Done with: Eltorito Volume Descriptor              Block(s)    1
Writing:   Joliet Volume Descriptor                Start Block 18
Done with: Joliet Volume Descriptor                Block(s)    1
Writing:   End Volume Descriptor                   Start Block 19
Done with: End Volume Descriptor                   Block(s)    1
Writing:   Version block                           Start Block 20
Done with: Version block                           Block(s)    1
Writing:   Path table                              Start Block 21
Done with: Path table                              Block(s)    4
Writing:   Joliet path table                       Start Block 25
Done with: Joliet path table                       Block(s)    4
Writing:   Directory tree                          Start Block 29
Done with: Directory tree                          Block(s)    15
Writing:   Joliet directory tree                   Start Block 44
Done with: Joliet directory tree                   Block(s)    14
Writing:   Directory tree cleanup                  Start Block 58
Done with: Directory tree cleanup                  Block(s)    0
Writing:   Extension record                        Start Block 58
Done with: Extension record                        Block(s)    1
Writing:   The File(s)                             Start Block 59
  4.71% done, estimate finish Fri Jan  1 14:25:34 2016
  9.40% done, estimate finish Fri Jan  1 14:25:13 2016
 14.10% done, estimate finish Fri Jan  1 14:25:06 2016
 18.80% done, estimate finish Fri Jan  1 14:25:02 2016
 23.49% done, estimate finish Fri Jan  1 14:25:00 2016
 28.20% done, estimate finish Fri Jan  1 14:24:59 2016
 32.89% done, estimate finish Fri Jan  1 14:24:58 2016
 37.58% done, estimate finish Fri Jan  1 14:24:57 2016
 42.29% done, estimate finish Fri Jan  1 14:24:56 2016
 46.98% done, estimate finish Fri Jan  1 14:24:56 2016
 51.68% done, estimate finish Fri Jan  1 14:24:55 2016
 56.38% done, estimate finish Fri Jan  1 14:24:55 2016
 61.07% done, estimate finish Fri Jan  1 14:24:55 2016
 65.78% done, estimate finish Fri Jan  1 14:24:55 2016
 70.47% done, estimate finish Fri Jan  1 14:24:54 2016
 75.17% done, estimate finish Fri Jan  1 14:24:54 2016
 79.86% done, estimate finish Fri Jan  1 14:24:54 2016
 84.56% done, estimate finish Fri Jan  1 14:24:54 2016
 89.26% done, estimate finish Fri Jan  1 14:24:54 2016
 93.95% done, estimate finish Fri Jan  1 14:24:54 2016
 98.66% done, estimate finish Fri Jan  1 14:24:54 2016
Total translation table size: 2048
Total rockridge attributes bytes: 9888
Total directory bytes: 28672
Path table size(bytes): 184
Done with: The File(s)                             Block(s)    106232
Writing:   Ending Padblock                         Start Block 106291
Done with: Ending Padblock                         Block(s)    150
Max brk space used 23000
106441 extents written (207 MB)
root@porteus:/home/guest/Downloads/working# ls
Porteus-MATE-v3.1-x86_64.iso*  UP.Porteus-MATE-v3.1-x86_64.iso  UP.Porteus-MATE-v3.1-x86_64.iso.md5  upkernel-3.18.25-noarch-1.xzm
root@porteus:/home/guest/Downloads/working#

Thanks neko for upkernel.

[Jack]

@ neko I went to Porteus System Info the current kernel still shows 3.17.4-porteus and upkernel to 3.18.25. Which one is right? Did it do the upgrade or did I do something wrong?

[neko]

@Jack
I followed your operation.

Code: Select all

$ md5sum Porteus-MATE-v3.1-x86_64.iso upkernel-3.18.25-noarch-1.xzm
d133e1dfff7a255045abfff90d2061dc  Porteus-MATE-v3.1-x86_64.iso
d905a2d98c97160d38efe4c14bce4d9b  upkernel-3.18.25-noarch-1.xzm
$ su 
# activate upkernel-3.18.25-noarch-1.xzm
# upkernel Porteus-MATE-v3.1-x86_64.iso
# ls -1
Porteus-MATE-v3.1-x86_64.iso
UP.Porteus-MATE-v3.1-x86_64.iso
UP.Porteus-MATE-v3.1-x86_64.iso.md5
upkernel-3.18.25-noarch-1.xzm
# mloop UP.Porteus-MATE-v3.1-x86_64.iso 
# ls /mnt/loop/porteus/*.sgn
/mnt/loop/porteus/kernel-v3.18.25-x86_64.sgn

I booted UP.Porteus-MATE-v3.1-x86_64.iso with the following grub2 menu.

menuentry "UP.Porteus-MATE-v3.1-x86_64.iso" {
search --no-floppy --fs-uuid --set=root 57597f01-0129-4e2f-8c86-fad1aff4a08e
set ISO="/porteus/3.1/64/org/UP.Porteus-MATE-v3.1-x86_64.iso"
loopback loop $ISO
linux (loop)/boot/syslinux/vmlinuz from=/$ISO copy2ram
initrd (loop)/boot/syslinux/initrd.xz
}

I got the screen shot of the "Porteus System Info" on the running UP.Porteus-MATE-v3.1-x86_64.iso.


It showed "3.18.25" as above.

I guess that the boot menu might be same as the origin ISO.
Please confirm your UP.ISO boot menu.

Thanks.

[Jack]

I must have created the wrong ISO file and when I redid it I made sure I had the right one. Now it shows 3.18.25-porteus.

When I upgrade to version 4.3.3 what I want to do is rebuild 001.core, 002-xorg and 003-mate to the current packages if I can. I'm not sure how to keep all the Porteus setting like root and guest password and the rest that it Porteus has. For me I want to keep Slackware alive for now so if I can learn how to do rebuild I'll be happy. I know I can use this to remove a package but not sure how upgrade a package.

Code: Select all

    mkdir /tmp/unpacked
    xzm2dir /my/modules.xzm /tmp/unpacked
    ROOT=/tmp/unpacked removepkg your_package
    dir2xzm /tmp/unpacked mynewmodulename.xzm

I have all ready unpack all 3 of them in there own directory all I need to do is upgrade the packages.

This is for me to learn how and just my $0.02 cents

[Ed_P]

The 4.3.3 kernel update didn't work for me unfortunately.

The differences between the 3.1 kernel that works for me and the 4.3.3 one is as follows.

My 3.1 LXQT system uses the kernel from the 3.0.1 system because that was the fix fanthom guided me through to resolve the problem of the system not suspending when the lid of my netbook was closed.

I used the Porteus System Info applet to display the Kernel on each system and saved each report to the system's /home/guest/ folder then copied the two .tmp file to the 3.0.1 /home/guest/ folder and ran the diff command on them with the results shown below.

Code: Select all

guest@porteus:~$ diff 31info.tmp 43info.tmp
1c1
< CURRENT KERNEL: 3.14.15-porteus
---
> CURRENT KERNEL: 4.3.3-porteus
5,6c5,6
< ipv6
< wl
---
> 
> 
17c17
< sparse_keymap
---
> 
19,20c19,20
< cfg80211
< k10temp
---
> 
> 
25c25
< drm_kms_helper
---
> 
31c31
< video
---
> 
32a33,38
> 
> input_leds
> snd_hda_core
> fjes
> mac_hid
> firmware_class
guest@porteus:~$ 

As can be seen there are modules in 3.1's 3.14 kernel that aren't in the 4.3 kernel and visa versa. If the missing 3.14 modules could be somehow added to the 4.3 kernel I think things would work. Unfortunately how to do that is beyond my skills.

Code: Select all

CURRENT KERNEL: 3.14.15-porteus

KERNEL MODULES LOADED:
Module
ipv6
wl
radeon
snd_hda_codec_conexant
snd_hda_codec_generic
snd_hda_codec_hdmi
uvcvideo
videobuf2_vmalloc
acer_wmi
videobuf2_memops
videobuf2_core
snd_hda_intel
sparse_keymap
snd_hda_codec
cfg80211
k10temp
i2c_piix4
atl1c
led_class
snd_hwdep
drm_kms_helper
snd_pcm
ttm
rfkill
snd_timer
wmi
video
acpi_cpufreq

Code: Select all

CURRENT KERNEL: 4.3.3-porteus

KERNEL MODULES LOADED:
Module


radeon
snd_hda_codec_conexant
snd_hda_codec_generic
snd_hda_codec_hdmi
uvcvideo
videobuf2_vmalloc
acer_wmi
videobuf2_memops
videobuf2_core
snd_hda_intel

snd_hda_codec


i2c_piix4
atl1c
led_class
snd_hwdep

snd_pcm
ttm
rfkill
snd_timer
wmi

acpi_cpufreq

input_leds
snd_hda_core
fjes
mac_hid
firmware_class

[neko]

@Ed_P
If you have a chance, please try to convert OK kernel(3.0.1 system) conf to 4.3.3 conf.

Please refer to the 'COMPILATION AND USAGE OF CUSTOM PORTEUS KERNEL'
http://www.porteus.org/component/conten ... ernel.html

====================================================
1. preparation
linux-4.3.3.tar.xz
https://www.kernel.org/pub/linux/kernel ... 3.3.tar.xz
upkernel-4.3.3-noarch-1.xzm
http://www.mediafire.com/download/0ap6c ... arch-1.xzm
000-kernel.xzm
http://dl.porteus.org/x86_64/archive/Po ... kernel.xzm
Porteus-LXQT-v3.1-x86_64.iso
http://dl.porteus.org/x86_64/current/Po ... x86_64.iso
manjaro-xfce-15.12-x86_64.iso (1,537 M)
http://sourceforge.net/projects/manjarolinux/

2. get 'OK kernel(3.0.1 system)' conf
on 'OK kernel' running environment.

Code: Select all

% su
# modprobe configs
# zcat /proc/config.gz > v3.0.1.config

3. set data
2 partitions are used.

3.1. set manjaro-xfce-15.12-x86_64.iso
example:
partition UUID:7825790e-6578-4c89-b3c6-d275facc89f2
directory:/your-set-directory
grub2 entry

menuentry "manjaro-xfce-15.12-x86_64.iso" {
search --no-floppy --fs-uuid --set=root 7825790e-6578-4c89-b3c6-d275facc89f2
set ISO="/your-set-directory/manjaro-xfce-15.12-x86_64.iso"
set partiuuid="7825790e-6578-4c89-b3c6-d275facc89f2"
set mlabel="MJRO1512"
set archi="x86_64"
set dri="free"
loopback loop $ISO
linux (loop)/manjaro/boot/$archi/manjaro img_dev=UUID=$partiuuid img_loop=$ISO misobasedir=manjaro misolabel=$mlabel nouveau.modeset=1 i915.modeset=1 radeon.modeset=1 logo.nologo overlay=$dri showopts
initrd (loop)/manjaro/boot/$archi/manjaro.img
}

3.2. set 'preparation data'
example:
partition: /dev/sda3
directory:/your-work

Code: Select all

% cd /mnt/sda3/your-work
% ls -1
000-kernel.xzm
Porteus-LXQT-v3.1-x86_64.iso
linux-4.3.3.tar.xz
upkernel-4.3.3-noarch-1.xzm
v3.0.1.config
% mloop upkernel-4.3.3-noarch-1.xzm
% cp /mnt/loop/usr/local/share/upkernel/Kernel.v4.3.3-1/boot/syslinux/initrd.xz .
% cp /mnt/loop/usr/local/share/upkernel/Kernel.v4.3.3-x86_64-1/porteus/kernel-v4.3.3-x86_64.sgn .
% cp /mnt/loop/usr/local/share/upkernel/config/get.aufs4.3.patch .
% uloop
% ls -1
000-kernel.xzm
Porteus-LXQT-v3.1-x86_64.iso
get.aufs4.3.patch
initrd.xz
kernel-v4.3.3-x86_64.sgn
linux-4.3.3.tar.xz
upkernel-4.3.3-noarch-1.xzm
v3.0.1.config

4. compile on manjaro-xfce-15.12-x86_64.iso running environment.
4.1. boot manjaro-xfce-15.12-x86_64.iso live
after boot,
set network and change to (/dev/sda3) /your-work directory.

4.2. get 'auf patch', patch auf, update config, compile

Code: Select all

% su
# ./get.aufs4.3.patch
# xz -dc linux-4.3.3.tar.xz | tar -x
# ls -1
000-kernel.xzm
Porteus-LXQT-v3.1-x86_64.iso
aufs4.3.patch
get.aufs4.3.patch
initrd.xz
kernel-v4.3.3-x86_64.sgn
linux-4.3.3
linux-4.3.3.tar.xz
upkernel-4.3.3-noarch-1.xzm
v3.0.1.config
# cd linux-4.3.3
# patch -p1 < ../aufs4.3.patch
# cp ../v3.0.1.config .config
# make oldconfig
# make

answers for 'make oldconfig' are your choices.

4.3. get vmlinuz, lib

Code: Select all

# cp arch/x86/boot/bzImage ../vmlinuz
# make modules_install INSTALL_MOD_PATH=../
# make firmware_install INSTALL_MOD_PATH=../
# cd ../
# ls -1
000-kernel.xzm
Porteus-LXQT-v3.1-x86_64.iso
aufs4.3.patch
get.aufs4.3.patch
initrd.xz
kernel-v4.3.3-x86_64.sgn
lib
linux-4.3.3
linux-4.3.3.tar.xz
upkernel-4.3.3-noarch-1.xzm
v3.0.1.config
vmlinuz

5. create kernel 4.3.3 Porteus-LXQT-v3.1-x86_64.iso on Porteus environment

Code: Select all

% cd /mnt/sda3/your-work
# su
# mloop 000-kernel.xzm
# mkdir new000
# cp -a /mnt/loop/* new000/.
# uloop
# rm -fr new000/lib/modules/
# cp -a lib/* new000/lib/.
# mksquashfs new000 new000.xzm -b 256K -comp xz -Xbcj x86
# rm -fr new000
# mloop Porteus-LXQT-v3.1-x86_64.iso
# mkdir NEW
# cp -a /mnt/loop/* NEW/.
# uloop
# mv vmlinuz NEW/boot/syslinux/.
# mv initrd.xz NEW/boot/syslinux/.
# rm NEW/porteus/*.sgn
# mv kernel-v4.3.3-x86_64.sgn NEW/porteus
# mv new000.xzm NEW/porteus/base/000-kernel.xzm
# mkisofs -o UP.Porteus-LXQT-v3.1-x86_64.iso -v -l -J -joliet-long  -R -D -A Porteus -V Porteus \
-no-emul-boot -boot-info-table -boot-load-size 4 \
-b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot NEW
# rm -fr NEW
# ls -1
000-kernel.xzm
Porteus-LXQT-v3.1-x86_64.iso
UP.Porteus-LXQT-v3.1-x86_64.iso
aufs4.3.patch
get.aufs4.3.patch
lib
linux-4.3.3
linux-4.3.3.tar.xz
upkernel-4.3.3-noarch-1.xzm
v3.0.1.config

====================================================

Thanks.

[Bogomips]

@neko
Thanks for step by step on how to do kernel. It's been a while since I last compiled kernel.