Porteus Kernel Builder

[maia]

Hi Blaze.

I have now tested the 5.7.8 version that you just compiled.
I did not receive any error messages from ACPI.
"Buggy seq_file .next function" messages persist.

[]s

[Blaze]

Hi maia,

what about wifi?

[maia]

Hi Blaze, still dead.

[Blaze]

Hi maia,
Copy to modules firmware-ath9k-htc_1.4.0-97-g75b3e59+dfsg-3_all.xzm, reboot and check wifi.

[maia]

Blaze, thanks for all the help.
But it's still dead.

With 2.7.8

[ 26.682256] usb 1-1.2.1.1: USB disconnect, device number 8
[ 26.724674] ath9k_htc: Failed to initialize the device
[ 26.724717] usb 1-1.2.1.1: ath9k_htc: USB layer deinitialized
[ 28.492467] usb 1-1.2.1.1: new high-speed USB device number 10 using ehci-pci
[ 28.694132] usb 1-1.2.1.1: New USB device found, idVendor=0cf3, idProduct=9271, bcdDevice= 1.08
[ 28.694137] usb 1-1.2.1.1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 28.694141] usb 1-1.2.1.1: Product: USB2.0 WLAN
[ 28.694143] usb 1-1.2.1.1: Manufacturer: ATHEROS
[ 28.694145] usb 1-1.2.1.1: SerialNumber: 12345
[ 28.694902] usb 1-1.2.1.1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw requested
[ 28.987991] usb 1-1.2.1.1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.dev.0.fw, size: 51008
[ 29.239455] ath9k_htc 1-1.2.1.1:1.0: ath9k_htc: HTC initialized with 33 credits
[ 29.500469] ath: phy2: Invalid EEPROM magic (0xfffb).
[ 29.500474] ath: phy2: Unable to initialize hardware; initialization status: -22
[ 29.500476] ath: phy2: Unable to initialize hardware; initialization status: -22
[ 29.667706] ath9k_htc: Failed to initialize the device
[ 29.667876] usb 1-1.2.1.1: ath9k_htc: USB layer deinitialized

With 5.6.18

[ 21.894270] usb 3-2: new high-speed USB device number 3 using xhci_hcd
[ 24.924243] usb 1-1.2.1.1: new high-speed USB device number 9 using ehci-pci
[ 25.125915] usb 1-1.2.1.1: New USB device found, idVendor=0cf3, idProduct=9271, bcdDevice= 1.08
[ 25.125921] usb 1-1.2.1.1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 25.125924] usb 1-1.2.1.1: Product: USB2.0 WLAN
[ 25.125927] usb 1-1.2.1.1: Manufacturer: ATHEROS
[ 25.125929] usb 1-1.2.1.1: SerialNumber: 12345
[ 25.691344] usb 1-1.2.1.1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[ 25.691587] usbcore: registered new interface driver ath9k_htc
[ 25.985086] usb 1-1.2.1.1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[ 26.237940] ath9k_htc 1-1.2.1.1:1.0: ath9k_htc: HTC initialized with 33 credits
[ 26.500144] ath9k_htc 1-1.2.1.1:1.0: ath9k_htc: FW Version: 1.4
[ 26.500149] ath9k_htc 1-1.2.1.1:1.0: FW RMW support: On
[ 26.500151] ath: EEPROM regdomain: 0x809c
[ 26.500153] ath: EEPROM indicates we should expect a country code
[ 26.500154] ath: doing EEPROM country->regdmn map search
[ 26.500155] ath: country maps to regdmn code: 0x52
[ 26.500157] ath: Country alpha2 being used: CN
[ 26.500177] ath: Regpair used: 0x52
[ 26.505209] ieee80211 phy1: Atheros AR9271 Rev:1
[ 35.684707] wlan1: authenticate with e0:88:5d:0b:bf:17
[ 35.907376] wlan1: send auth to e0:88:5d:0b:bf:17 (try 1/3)
[ 35.912600] wlan1: authenticated
[ 35.920177] wlan1: associate with e0:88:5d:0b:bf:17 (try 1/3)
[ 35.924821] wlan1: RX AssocResp from e0:88:5d:0b:bf:17 (capab=0x1411 status=0 aid=1)
[ 35.932174] wlan1: associated

[Blaze]

maia, if try with

Code: Select all

su
toor

echo '[device-mac-randomization]
wifi.scan-rand-mac-address=no' >> /etc/NetworkManager/NetworkManager.conf

# and reboot
reboot

?

But better to wait a new kernel and test it

http://lkml.iu.edu/hypermail/linux/kern ... 07776.html

Code: Select all

Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"

http://lkml.iu.edu/hypermail/linux/kern ... 07856.html

Code: Select all

Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"

[maia]

Hi Blaze, tks

I made two attempts using the /etc/NetworkManager/NetworkManager.conf profided configuration and each of the last firmware and TP-LINK does not start.

I will wait for these security fixes to be implemented in the kernel for future testing.

Thank you for the informations.

[Blaze]

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel.xzm, 06-crippled_sources-NNN-XXbit.xzm)

[4.19.133] <-- NEW : "All patches" patching was done.
32bit-ALL-kernel4.19.133.tar (82 M)
http://www.mediafire.com/file/lv1mz1a9c ... 19.133.tar
2c54588421587a98cc6db170e076e4c8 32bit-ALL-kernel4.19.133.tar

[5.4.52] <-- NEW : "All patches" patching was done.
32bit-ALL-kernel5.4.52.tar (90 M)
http://www.mediafire.com/file/jakpy3gpg ... 5.4.52.tar
4bd589366625ae48a04974b813712aa4 32bit-ALL-kernel5.4.52.tar

[5.4.52] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.4.52.tar (92 M)
http://www.mediafire.com/file/5jg5vb1m7 ... 5.4.52.tar
811f6ef8f52155445576eceaeb309a58 64bit-ALL-kernel5.4.52.tar

[5.7.9] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.7.9.tar (96 M)
http://www.mediafire.com/file/lo3ercdhw ... l5.7.9.tar
18f378434745e400898ddd57a38835b1 64bit-ALL-kernel5.7.9.tar

Note : Compiler that was used.
for kernels 4.19.133, 5.4.52, 5.7.9: gcc-10.1.0-x86_64

The change logs:

• ChangeLog-4.19.133
• ChangeLog-5.4.52
• ChangeLog-5.7.9

[maia]

Blaze thank you.

They fixed the patch, the TP-LINK card worked with 5.7.9 and 5.4.52.

On version 5.7.9 it still presents many messages:: [2.744227] buggy seq_file .next function 0xffffffff81152ebb. And I don't know how to qualify whether it is important or not.

I still get an old error message that already appeared in the old kernel versions but that does not prevent my Intel wifi card from working:

dmesg | grep error
[ 4.994024] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 6.488356] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq failed with error -2
[ 6.488390] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.bseq failed with error -2

[Ed_P]

Code: Select all

root@porteus:/home/guest# cat /var/log/messages | grep "Linux version"
Jul 16 11:59:43 porteus kernel: [    0.000000] Linux version 5.4.52-porteus (root@porteus) (gcc version 10.1.0 (GCC)) #1 SMP Thu Jul 16 09:48:39 UTC 2020
root@porteus:/home/guest# cat /var/log/messages | grep "action lid"
Jul 16 17:22:55 porteus root: ACPI action lid is not defined
Jul 16 17:35:59 porteus root: ACPI action lid is not defined
Jul 16 17:40:32 porteus root: ACPI action lid is not defined
Jul 16 17:41:31 porteus root: ACPI action lid is not defined
root@porteus:/home/guest# 

And the notebook was warm when I opened it after an hour.

[maia]

Hi Ed_p

Here on my notebook I no longer use "action lid" to suspend. I use the command I put in fbpanel config:

Code: Select all

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

Works well.

[Ed_P]

Hi maia

I tried your command and it does work.

Code: Select all

guest@porteus:~$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
method return time=1595003965.382024 sender=:1.15 -> destination=:1.67 serial=73 reply_serial=2
guest@porteus:~$ 

But I don't understand it. Where/what is the fbpanel? And what/where is org.freedesktop.UPower?

Added in 19 minutes 16 seconds:
OK this link helped: https://bfy.tw/OWtd and I suspect an fbpanel is created as a desktop file.

Added in 3 minutes 39 seconds:
Any way to add a password signon to the command when powering back on?

Added in 14 minutes 21 seconds:
And this link looks interesting also. http://www.thinkwiki.org/wiki/How_to_configure_acpid

[maia]

Hi

fbpanel is old desktop panel that i like.


I'm using the: Porteus 5 rc and ( dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend ) works on my notebook by command line or in a bash script no required sudo

I learned the command on the page:
https://qastack.com.br/ubuntu/1792/how- ... mmand-line
But it's a page in Portuguese

Previously I used the following command before, works but it required sudo.
#!/bin/sh
#sudo echo mem > /sys/power/state

Any way to add a password signon to the command when powering back on?
I don't know about this feature.
[]s

[tome]

Any way to add a password signon to the command when powering back on?

If you have lxdm login manager something like this should work:
sudo echo mem > /sys/power/state && lxdm -c USER_SWITCH

[maia]

Tome, thank you.