
Porteus Kernel Builder
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
So Porteus gets it's driver support in 000-nucleus.xzm. I assume vmlinuz gets it's driver support the same way. So where/how does initrd.xz get it's driver support? Obviously not 000-nucleus.xzm. 

Porteus Kernel Builder
hi babam here the mediafire link:https://www.mediafire.com/folder/oayeop ... .1-porteus
- babam
- Warlord
- Posts: 528
- Joined: 16 Nov 2016, 10:30
- Distribution: Porteus 5.0rc3 Xfce K6.1.1
- Location: Rainy city
Porteus Kernel Builder
Thank you, everything is working fine.beny wrote: ↑01 Apr 2022, 21:50hi babam here the mediafire link:https://www.mediafire.com/folder/oayeop ... .1-porteus
Update: Wifi not working
Last edited by babam on 03 Apr 2022, 17:44, edited 1 time in total.
Sorry, my English is bad.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
Hi raja, an update. I have a config that boots:
initrd.xz from the current Porteus 5.0 ISO
boot parm cfgfile=porteus-v4.0-x86_64.cfg
and a Porteus-CINNAMON-v4.0-x86_64-5.17.1.iso ISO file.
The only problem, it boots to a black screen.

ctrl+alt+f1 brings me to the boot terminal screen. I signon as root, run startx and I'm back to a black screen.
-
- DEV Team
- Posts: 2113
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Porteus Kernel Builder
@beny
"AUFS" is the only patch normally handled by "Porteus Kernel Builder".
It is assumed that kernel patches and configuration changes required by individual users
will be made individually.
Unfortunately, 88x2bu.ko introduced this time is beyond my understanding.
Thanks.
"AUFS" is the only patch normally handled by "Porteus Kernel Builder".
It is assumed that kernel patches and configuration changes required by individual users
will be made individually.
Unfortunately, 88x2bu.ko introduced this time is beyond my understanding.
Code: Select all
% su
# modinfo 88x2bu.ko
filename: /home/guest/kernel/beny/88x2bu.ko
version: v5.13.1-20-gbd7c7eb9d.20210702_COEX20210316-18317b7b
author: Realtek Semiconductor Corp.
description: Realtek Wireless Lan Driver
license: GPL
srcversion: FFDA7E7464948295EE73EC2
alias: usb:v20F4p808Ad*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v2357p0115d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v2357p0138d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v2357p012Dd*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0846p9055d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v2001p331Cd*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v2001p331Ed*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v7392pF822d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v7392pC822d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v7392pB822d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0B05p19AAd*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0B05p184Cd*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0B05p1841d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v13B1p0043d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0BDApB812d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0BDApB82Cd*dc*dsc*dp*icFFiscFFipFFin*
depends: cfg80211
retpoline: Y
name: 88x2bu
vermagic: 5.17.1-porteus SMP preempt mod_unload
parm: rtw_wireless_mode:int
parm: rtw_ips_mode:The default IPS mode (int)
parm: rtw_lps_level:The default LPS level (int)
parm: rtw_lps_chk_by_tp:int
parm: rtw_max_bss_cnt:int
parm: rtw_usb_rxagg_mode:int
parm: rtw_dynamic_agg_enable:int
parm: rtw_drv_log_level:set log level when insert driver module, default log level is _DRV_INFO_ = 4 (uint)
parm: rtw_tx_aclt_flags:device TX AC queue packet lifetime control flags (uint)
parm: rtw_tx_aclt_conf_default:device TX AC queue lifetime config for default status (array of uint)
parm: rtw_tx_aclt_conf_ap_m2u:device TX AC queue lifetime config for AP mode M2U status (array of uint)
parm: rtw_tx_bw_mode:The max tx bw for 2.4G and 5G. format is the same as rtw_bw_mode (uint)
parm: rtw_rx_ampdu_sz_limit_1ss:RX AMPDU size limit for 1SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_rx_ampdu_sz_limit_2ss:RX AMPDU size limit for 2SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_rx_ampdu_sz_limit_3ss:RX AMPDU size limit for 3SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_rx_ampdu_sz_limit_4ss:RX AMPDU size limit for 4SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_stbc_cap:int
parm: rtw_vht_enable:int
parm: rtw_vht_24g_enable:int
parm: rtw_vht_rx_mcs_map:VHT RX MCS map (uint)
parm: rtw_trx_path_bmp:int
parm: rtw_tx_path_lmt:int
parm: rtw_rx_path_lmt:int
parm: rtw_tx_nss:int
parm: rtw_rx_nss:int
parm: rtw_country_code:The default country code (in alpha2) (charp)
parm: rtw_channel_plan:The default chplan ID when rtw_alpha2 is not specified or valid (int)
parm: rtw_excl_chs:exclusive channel array (array of uint)
parm: rtw_btcoex_enable:BT co-existence on/off, 0:off, 1:on, 2:by efuse (int)
parm: rtw_ant_num:Antenna number setting, 0:by efuse (int)
parm: rtw_pci_dynamic_aspm_linkctrl:int
parm: rtw_qos_opt_enable:int
parm: ifname:The default name to allocate for first interface (charp)
parm: if2name:The default name to allocate for second interface (charp)
parm: rtw_ap_src_b2u_flags:int
parm: rtw_ap_fwd_b2u_flags:int
parm: rtw_wowlan_sta_mix_mode:int
parm: rtw_pwrtrim_enable:int
parm: rtw_initmac:charp
parm: rtw_chip_version:int
parm: rtw_rfintfs:int
parm: rtw_lbkmode:int
parm: rtw_network_mode:int
parm: rtw_channel:int
parm: rtw_mp_mode:int
parm: rtw_wmm_enable:int
parm: rtw_uapsd_max_sp:int
parm: rtw_uapsd_ac_enable:int
parm: rtw_wmm_smart_ps:int
parm: rtw_vrtl_carrier_sense:int
parm: rtw_vcs_type:int
parm: rtw_busy_thresh:int
parm: rtw_ht_enable:int
parm: rtw_bw_mode:int
parm: rtw_ampdu_enable:int
parm: rtw_rx_stbc:int
parm: rtw_rx_ampdu_amsdu:int
parm: rtw_tx_ampdu_amsdu:int
parm: rtw_quick_addba_req:int
parm: rtw_beamform_cap:int
parm: rtw_power_mgnt:int
parm: rtw_smart_ps:int
parm: rtw_low_power:int
parm: rtw_wifi_spec:int
parm: rtw_full_ch_in_p2p_handshake:int
parm: rtw_antdiv_cfg:int
parm: rtw_antdiv_type:int
parm: rtw_drv_ant_band_switch:int
parm: rtw_single_ant_path:int
parm: rtw_switch_usb_mode:int
parm: rtw_enusbss:int
parm: rtw_hwpdn_mode:int
parm: rtw_hwpwrp_detect:int
parm: rtw_hw_wps_pbc:int
parm: rtw_check_hw_status:int
parm: rtw_max_roaming_times:The max roaming times to try (uint)
parm: rtw_advnace_ota:int
parm: rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint)
parm: rtw_hiq_filter:0:allow all, 1:allow special, 2:deny all (uint)
parm: rtw_adaptivity_en:0:disable, 1:enable (uint)
parm: rtw_adaptivity_mode:0:normal, 1:carrier sense (uint)
parm: rtw_adaptivity_th_l2h_ini:th_l2h_ini for Adaptivity (int)
parm: rtw_adaptivity_th_edcca_hl_diff:th_edcca_hl_diff for Adaptivity (int)
parm: rtw_dfs_region_domain:0:NONE, 1:FCC, 2:MKK, 3:ETSI (uint)
parm: rtw_amsdu_mode:0:non-spp, 1:spp, 2:all drop (uint)
parm: rtw_amplifier_type_2g:BIT3:2G ext-PA, BIT4:2G ext-LNA (uint)
parm: rtw_amplifier_type_5g:BIT6:5G ext-PA, BIT7:5G ext-LNA (uint)
parm: rtw_RFE_type:default init value:64 (uint)
parm: rtw_powertracking_type:default init value:64 (uint)
parm: rtw_GLNA_type:default init value:0 (uint)
parm: rtw_TxBBSwing_2G:default init value:0xFF (uint)
parm: rtw_TxBBSwing_5G:default init value:0xFF (uint)
parm: rtw_OffEfuseMask:default open Efuse Mask value:0 (uint)
parm: rtw_FileMaskEfuse:default drv Mask Efuse value:0 (uint)
parm: rtw_rxgain_offset_2g:default RF Gain 2G Offset value:0 (uint)
parm: rtw_rxgain_offset_5gl:default RF Gain 5GL Offset value:0 (uint)
parm: rtw_rxgain_offset_5gh:uint
parm: rtw_rxgain_offset_5gm:default RF Gain 5GM Offset value:0 (uint)
parm: rtw_pll_ref_clk_sel:force pll_ref_clk_sel, 0xF:use autoload value (uint)
parm: rtw_tx_pwr_by_rate:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm: rtw_tx_pwr_lmt_enable:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm: rtw_target_tx_pwr_2g_a:2.4G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_2g_b:2.4G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_2g_c:2.4G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_2g_d:2.4G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_a:5G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_b:5G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_c:5G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_d:5G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_antenna_gain:Antenna gain in mBi. 0x7FFF: unspecifed (int)
parm: rtw_tsf_update_pause_factor:num of bcn intervals to stay TSF update pause status (int)
parm: rtw_tsf_update_restore_factor:num of bcn intervals to stay TSF update restore status (int)
parm: rtw_phy_file_path:The path of phy parameter (charp)
parm: rtw_load_phy_file:PHY File Bit Map (int)
parm: rtw_decrypt_phy_file:Enable Decrypt PHY File (int)
parm: rtw_recvbuf_nr:Preallocated number of struct recv_buf (int)
parm: rtw_phydm_ability:uint
parm: rtw_halrf_ability:uint
parm: rtw_en_napi:int
parm: rtw_en_gro:int
parm: rtw_iqk_fw_offload:int
parm: rtw_ch_switch_offload:int
parm: rtw_en_dyn_rrsr:int
parm: rtw_rrsr_value:int
parm: rtw_scan_interval_thr:Threshold used to judge if scan request comes from scan UI, unit is ms. (uint)
#
Thanks.
Porteus Kernel Builder
hi neko the wifi driver for the realtek chipset are not related with the kernel is a driver that you can put in or not,why you think:will be made individually i have change nothing your the tool your the config and the aufs patch and if you remeber you have asked for this driver,btw kernel version change every two or three week,so don't worry for....
Code: Select all
## Supported Devices
<details>
<summary>
ASUS
</summary>
* ASUS AC1300 USB-AC55 B1
* ASUS U2
* ASUS USB-AC53 Nano
* ASUS USB-AC58
</details>
<details>
<summary>
Dlink
</summary>
* Dlink - DWA-181
* Dlink - DWA-182
</details>
<details>
<summary>
Edimax
</summary>
* Edimax EW-7822ULC
* Edimax EW-7822UTC
* Edimax EW-7822UAD
</details>
<details>
<summary>
NetGear
</summary>
* NetGear A6150
</details>
<details>
<summary>
TP-Link
</summary>
* TP-Link Archer T3U
* TP-Link Archer T3U Plus
* TP-Link Archer T4U V3
* TP-Link Archer T4U Plus
</details>
<details>
<summary>
TRENDnet
</summary>
* TRENDnet TEW-808UBM
</details>
<details>
<summary>
ZYXEL
</summary>
* ZYXEL NWD6602
</details>
-
- DEV Team
- Posts: 2113
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Porteus Kernel Builder
@beny
Understood.
"btw kernel version change every two or three week"
--->
I am building the latest series of kernels, which are updated almost every week, without AUFS patches.
The results are uploaded for Porteus v5.0rc3 with OverlayFS kernel.
OverlayFS Porteus (Post by neko #87516)
APorteus's "ISO Builder" is updated with this new kernel too.
ArchLinux packages manager for Porteus (Post by neko #36689)
This weekly routine is a bit of a burden.
Thanks
Understood.
"btw kernel version change every two or three week"
--->
I am building the latest series of kernels, which are updated almost every week, without AUFS patches.
The results are uploaded for Porteus v5.0rc3 with OverlayFS kernel.
OverlayFS Porteus (Post by neko #87516)
APorteus's "ISO Builder" is updated with this new kernel too.
ArchLinux packages manager for Porteus (Post by neko #36689)
This weekly routine is a bit of a burden.
Thanks
- babam
- Warlord
- Posts: 528
- Joined: 16 Nov 2016, 10:30
- Distribution: Porteus 5.0rc3 Xfce K6.1.1
- Location: Rainy city
Porteus Kernel Builder
I had to manually add iwlwifi-QuZ-a0-hr-b0-68.ucode so that Wifi could work.beny wrote: ↑01 Apr 2022, 21:50hi babam here the mediafire link:https://www.mediafire.com/folder/oayeop ... .1-porteus
Sorry, my English is bad.
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
Porteus Kernel Builder
Ed_P,
Kernel comes into the picture only with your graphics driver. Check your display driver for any anomaly. What is your graphics card?
Delete any changes modules you have added to ISO. Try again.
Kernel-5.17 boots without any problem porteus-4.0 edition for me.
Here are the proof:
I use LXQt. Shall try cinnamon for your sake in porteus-4.0
cinnamon too boots to desktop. But child process missing error. gave ctrl+alt+f2 and logged in as guest
startx brings out desktop. adding this from cinnamon desktop only.
from Porteus system info...
Kernel comes into the picture only with your graphics driver. Check your display driver for any anomaly. What is your graphics card?
Delete any changes modules you have added to ISO. Try again.
Kernel-5.17 boots without any problem porteus-4.0 edition for me.
Here are the proof:
Since you have said last time that you had the desktop without panel, again get the desktop that way and restart the panel.guest@porteus:~$ uname -a
Linux porteus 5.17.0-porteus
X.Org X Server 1.19.6
Release Date: 2017-12-20
initrd.xz:20180311
001-core.xzm:20180422
002-xorg.xzm:20180422
003-lxqt.xzm:20180415
I use LXQt. Shall try cinnamon for your sake in porteus-4.0
cinnamon too boots to desktop. But child process missing error. gave ctrl+alt+f2 and logged in as guest
startx brings out desktop. adding this from cinnamon desktop only.
from Porteus system info...
Modules
000-kernel-5.17.xzm
001-core.xzm
002-xorg.xzm
003-cinnamon.xzm
apps.xzm
audacity-2.3.2-x86_64-3_slonly.xzm
avidemux-2.7.1-x86_64-bundle.xzm
conky-1.10.6-x86_64-alldesktops-1bundle.xzm
firefox-91.0-x86_64-en-US.xzm
florence-0.6.3.xzm
geany-1.34.1-1gv.xzm
gimp.xzm
guvcview-2.0.6-x86_64-1ponce.xzm
hardinfo-0.5.1-x86_64-3_slonly.xzm
lxqt-themes.xzm
rezound-0.13.1beta-x86_64-2_slonly.xzm
smplayer-19.10.2-x86_64-1_slonly.xzm
usm-current.xzm
winff-20170714_220b212-x86_64-1_slonly.xzm
VERSION:
Porteus-v4.0
Kernel: 5.17.0-porteus
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
From my 5.0 system:
Code: Select all
guest@porteus:~$ su
Password:
root@porteus:/home/guest# lspci
00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01)
00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
00:07.0 PCI bridge: Intel Corporation Device 9a23 (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
00:0d.0 USB controller: Intel Corporation Device 9a13 (rev 01)
00:0d.2 USB controller: Intel Corporation Device 9a1b (rev 01)
00:12.0 Serial controller: Intel Corporation Device a0fc (rev 20)
00:14.0 USB controller: Intel Corporation Device a0ed (rev 20)
00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20)
00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20)
00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20)
00:1c.0 PCI bridge: Intel Corporation Device a0bc (rev 20)
00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20)
00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20)
00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20)
2b:00.0 Non-Volatile memory controller: Sandisk Corp Device 501a
root@porteus:/home/guest#
As for the 4.0 iso:
Code: Select all
root@porteus:/home/guest# mloop /mnt/nvme0n1p7/ISOs/Porteus-CINNAMON-v4.0-x86_64-5.17.1.iso
using /dev/loop11
Please wait while I gather some info ....
mount: /mnt/loop: WARNING: source write-protected, mounted read-only.
#################################
Your image has been mounted at:
/mnt/loop
You can unmount it by typing uloop
Here is a list of the files:
EFI USB_INSTALLATION.txt boot porteus
root@porteus:/home/guest# ls /mnt/loop/porteus/base
000-kernel.xzm 002-xorg.xzm 06-crippled_sources-5.17.1-64bit.xzm*
001-core.xzm 003-cinnamon.xzm
root@porteus:/home/guest# ls /mnt/loop/porteus/base/modules
/bin/ls: cannot access '/mnt/loop/porteus/base/modules': No such file or directory
root@porteus:/home/guest# ls /mnt/loop/porteus/base/optional
/bin/ls: cannot access '/mnt/loop/porteus/base/optional': No such file or directory
root@porteus:/home/guest# ls /mnt/loop/porteus/base/rootcopy
/bin/ls: cannot access '/mnt/loop/porteus/base/rootcopy': No such file or directory
root@porteus:/home/guest#
Added in 46 minutes 19 seconds:
From my Porteus 4.0 boot:
Code: Select all
~# uname -a
Linux porteus 4.16.3-porteus #1 SMP PREEMPT Sat Apr 21 12:42:52 Local time zone must be set-- x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
~# cat /etc/porteus/*
001-core.xzm:20180422
002-xorg.xzm:20180422
003-cinnamon.xzm:20180416
initrd.xz:20201102
~# ls -l /mnt/live/memory/images
000-kernel.xzm : Apr 21 2018
001-core.xzm : Apr 22 2018
002-xorg.xzm : Apr 22 2018
003-cinnamon.xzm : Jul 15 2016
ISO: /ISOs/Porteus-CINNAMON-v4.0-x86_64.iso
Code: Select all
guest@porteus:~$ su
Password:
root@porteus:/home/guest# lspci
00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01)
00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
00:07.0 PCI bridge: Intel Corporation Device 9a23 (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
00:0d.0 USB controller: Intel Corporation Device 9a13 (rev 01)
00:0d.2 USB controller: Intel Corporation Device 9a1b (rev 01)
00:12.0 Serial controller: Intel Corporation Device a0fc (rev 20)
00:14.0 USB controller: Intel Corporation Device a0ed (rev 20)
00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20)
00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20)
00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20)
00:1c.0 PCI bridge: Intel Corporation Device a0bc (rev 20)
00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20)
00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20)
00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20)
2b:00.0 Non-Volatile memory controller: Sandisk Corp Device 501a
root@porteus:/home/guest#
Porteus Kernel Builder
hi Ed_P try this on terminal: that show more of your video hardware and software well try after you log in
bash-5.1# inxi -G
Graphics:
Device-1: NVIDIA GK107 [GeForce GT 740] driver: nouveau v: kernel
Display: server: X.Org v: 1.20.14 driver: X: loaded: modesetting
unloaded: vesa gpu: nouveau resolution: 1920x1080~60Hz
OpenGL: renderer: NVE7 v: 4.3 Mesa 21.3.8
bash-5.1#
or another is lshw -c video well seem that porteus do not have this.....
bash-5.1# inxi -G
Graphics:
Device-1: NVIDIA GK107 [GeForce GT 740] driver: nouveau v: kernel
Display: server: X.Org v: 1.20.14 driver: X: loaded: modesetting
unloaded: vesa gpu: nouveau resolution: 1920x1080~60Hz
OpenGL: renderer: NVE7 v: 4.3 Mesa 21.3.8
bash-5.1#
or another is lshw -c video well seem that porteus do not have this.....
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
Hi beny. In Porteus 5.0 I get:
Code: Select all
guest@porteus:~$ inxi -G
bash: inxi: command not found
guest@porteus:~$ su
Password:
root@porteus:/home/guest# inxi -G
bash: inxi: command not found
root@porteus:/home/guest# lshw -c
bash: lshw: command not found
Porteus Kernel Builder
hi Ed_P in terminal or konsole....or
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
Porteus Kernel Builder
I notice two problems with cinnamon.
1)It is based on python2.7 and porteus-4.0 shows "undefined symbol pam_start error. It will be only linkages error created by installation. Many python based apps have this type of errors.
so none of system-settings open.
2)In porteus-5.0 they have forced xorg to use modsetting.drv.so. Check when you boot 5.0 , whether xorg uses intel or modsetting. If xorg.0.log shows, it has used modsetting as auto configured driver.
In that case you will have to copy /etc/X11/modsetting.conf and vesa.conf from porteus-5.0 to porteus-4.0 and try.
My m/c too has intel as graphics driver, but old one.Your new dell may have intel iris XE graphics which porteus-4.0 xorg is not able to use.
my xorg.0.log:
intel.drv.so driver in kernel-5.17 covers intel iris graphics card also.
You wanted only porteus-4.0 for usm. Try lxde.lxqt or xfce DMs. You may succeed with your new m/c.
1)It is based on python2.7 and porteus-4.0 shows "undefined symbol pam_start error. It will be only linkages error created by installation. Many python based apps have this type of errors.
so none of system-settings open.
2)In porteus-5.0 they have forced xorg to use modsetting.drv.so. Check when you boot 5.0 , whether xorg uses intel or modsetting. If xorg.0.log shows, it has used modsetting as auto configured driver.
In that case you will have to copy /etc/X11/modsetting.conf and vesa.conf from porteus-5.0 to porteus-4.0 and try.
My m/c too has intel as graphics driver, but old one.Your new dell may have intel iris XE graphics which porteus-4.0 xorg is not able to use.
my xorg.0.log:
Code: Select all
[ 16.737] (==) Matched intel as autoconfigured driver 0
[ 16.737] (==) Matched intel as autoconfigured driver 1
[ 16.737] (==) Matched modesetting as autoconfigured driver 2
[ 16.737] (==) Matched fbdev as autoconfigured driver 3
[ 16.737] (==) Matched vesa as autoconfigured driver 4
[ 16.737] (==) Assigned the driver to the xf86ConfigLayout
[ 16.737] (II) LoadModule: "intel"
[ 16.737] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 16.778] (II) Module intel: vendor="X.Org Foundation"
[ 16.778] compiled for 1.19.6, module version = 2.99.917
[ 16.778] Module class: X.Org Video Driver
[ 16.778] ABI class: X.Org Video Driver, version 23.0
[ 16.778] (II) LoadModule: "modesetting"
[ 16.778] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 16.795] (II) Module modesetting: vendor="X.Org Foundation"
[ 16.795] compiled for 1.19.6, module version = 1.19.6
[ 16.795] Module class: X.Org Video Driver
[ 16.795] ABI class: X.Org Video Driver, version 23.0
[ 16.795] (II) LoadModule: "fbdev"
[ 16.795] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[ 16.809] (II) Module fbdev: vendor="X.Org Foundation"
[ 16.809] compiled for 1.19.4, module version = 0.4.4
[ 16.809] Module class: X.Org Video Driver
[ 16.809] ABI class: X.Org Video Driver, version 23.0
[ 16.809] (II) LoadModule: "vesa"
[ 16.810] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 16.822] (II) Module vesa: vendor="X.Org Foundation"
[ 16.822] compiled for 1.19.6, module version = 2.4.0
[ 16.822] Module class: X.Org Video Driver
[ 16.822] ABI class: X.Org Video Driver, version 23.0
[ 16.822] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 16.822] (II) intel: Driver for Intel(R) HD Graphics
[ 16.822] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 16.822] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 16.822] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 16.822] (II) FBDEV: driver for framebuffer: fbdev
[ 16.822] (II) VESA: driver for VESA chipsets: vesa
[ 16.822] (--) using VT number 7
[ 16.857] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20201103
[ 16.881] (WW) Falling back to old probe method for modesetting
[ 16.881] (WW) Falling back to old probe method for fbdev
[ 16.881] (II) Loading sub module "fbdevhw"
[ 16.881] (II) LoadModule: "fbdevhw"
[ 16.882] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 16.891] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 16.891] compiled for 1.19.6, module version = 0.0.2
[ 16.891] ABI class: X.Org Video Driver, version 23.0
[ 16.891] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 620
You wanted only porteus-4.0 for usm. Try lxde.lxqt or xfce DMs. You may succeed with your new m/c.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
Porteus Kernel Builder
sorry for that: inxi is part of slackware64 /ap directory..