Porteus-4.0 is in the pipeline.

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
evergreen
White ninja
White ninja
Posts: 15
Joined: 27 Mar 2016, 16:58
Distribution: porteus x64
Location: sweden

Porteus-4.0 is in the pipeline.

Post#16 by evergreen » 04 Dec 2017, 16:38

if Porteus 3.2.2 was great with the upcoming Porteus will be awesome!
I want to do a few observation when I tested "porteus-4.0-x86_64-20171203.iso" I noticed that I can't see my networks wifi .. I only added this module 003-xfce4.xzm to have access to nm-applet from this testing ISO that is working good http://ftp.vim.org/ftp/os/Linux/distr/p ... teus-v4.0/ maybe it is my mistake use a module in this way but i dont know how to connect from console to be sure about this.
I got this from system information: WIRELESS INFO: 03:00.0 Network controller: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter (rev 20).. This mean that my wifi is load?

I'm editing this post, I have forgotten there is a tool to setup my network 'pns-tool' and this tool only show me eth0.

PD. Thanks to the Dev team to keep this project Lactose free and free systemD allergies :worship:
Porteus-XFCE-v3.2.2-x86_64 Kernel 4.9 AMD A8-7410, APU AMD Radeon R5 Graphics M330

cttan
Shogun
Shogun
Posts: 333
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 and 4.0 64bit KDE
Location: Malaysia

Porteus-4.0 is in the pipeline.

Post#17 by cttan » 21 Dec 2017, 04:06

Hi brokenman,

Thanks for releasing 4.0 RC1. :good:

I am not able to start MariaDB. Found hostname is not included as per upstream Slackware 14.2 update.
http://www.slackware.com/changelog/curr ... cpu=x86_64
a/hostname-3.18-x86_64-1.txz: Added.
This is the latest version of the hostname utility, broken out into a new
package to get rid of duplication between util-linux and net-tools.

n/net-tools-20170208_479bb4a-x86_64-1.txz: Upgraded.
Don't include hostname, domainname, dnsdomainname, nisdomainname,
or ypdomainname. These are provided by the new hostname package.


The other is Kwrite unable to start as root. Found workaround using guest.

Is Xmas Santa bringing in another release this year?
B)

Cause it seems like every year end there is a Porteus release.

Merry Xmas! Ho! Ho! Ho! :santa: :newyear:

evergreen
White ninja
White ninja
Posts: 15
Joined: 27 Mar 2016, 16:58
Distribution: porteus x64
Location: sweden

Porteus-4.0 is in the pipeline.

Post#18 by evergreen » 23 Dec 2017, 11:02

Hi brokenman,

Again here, thanks for the new release Porteus always became better and better, but since 4.0 RC1 isn't working my WiFi , I found a log that show some errors loading a module that is for sure the reason of my inconvenience.

Code: Select all

SYSLOG:

Dec 23 07:44:24 porteus kernel: [    0.058000] TSC synchronization [CPU#0 -> CPU#1]:
Dec 23 07:44:24 porteus kernel: [    0.058000] Measured 105649379 cycles TSC warp between CPUs, turning off TSC clock.
Dec 23 07:44:24 porteus kernel: [    0.065034]  #2 #3
Dec 23 07:44:24 porteus kernel: [    0.097685] ACPI Exception: AE_AML_OPERAND_TYPE, During return object analysis (20170728/nsrepair-187)
Dec 23 07:44:24 porteus kernel: [    0.097703] ACPI Warning: \_SB.PCI0.LPC0.HPET._CRS: Return type mismatch - found Integer, expected Buffer (20170728/nspredef-290)
Dec 23 07:44:24 porteus kernel: [    0.097707] ACPI Error: Return object type is incorrect \_SB.PCI0.LPC0.HPET._CRS, AE_TYPE (20170728/uteval-165)
Dec 23 07:44:24 porteus kernel: [    0.097719] ACPI Error: Type returned from _CRS was incorrect: Integer, expected Btypes: 0x4 (20170728/uteval-171)
Dec 23 07:44:24 porteus kernel: [    0.119613] ACPI Exception: AE_AML_OPERAND_TYPE, During return object analysis (20170728/nsrepair-187)
Dec 23 07:44:24 porteus kernel: [    0.119631] ACPI Error: Return object type is incorrect \_SB.PCI0.LPC0.HPET._CRS, AE_TYPE (20170728/uteval-165)
Dec 23 07:44:24 porteus kernel: [    0.119643] ACPI Error: Type returned from _CRS was incorrect: Integer, expected Btypes: 0x4 (20170728/uteval-171)
Dec 23 07:44:24 porteus kernel: [    0.306423] ACPI Warning: \_SB.PCI0.GFX.VGA.LCD._BCL: Return Package type mismatch at index 0 - found Buffer, expected Integer (20170728/nspredef-297)
Dec 23 07:44:24 porteus kernel: [    0.308231] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
Dec 23 07:44:24 porteus kernel: [    0.309477] ACPI Exception: AE_AML_OPERAND_TYPE, During return object analysis (20170728/nsrepair-187)
Dec 23 07:44:24 porteus kernel: [    0.309558] ACPI Error: Return object type is incorrect \_SB.PCI0.LPC0.HPET._CRS, AE_TYPE (20170728/uteval-165)
Dec 23 07:44:24 porteus kernel: [    0.309682] ACPI Error: Type returned from _CRS was incorrect: Integer, expected Btypes: 0x4 (20170728/uteval-171)
Dec 23 07:44:24 porteus kernel: [   14.106597] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Dec 23 07:44:24 porteus kernel: [   14.109773] ATPX version 1, functions 0x00000003
Dec 23 07:44:24 porteus kernel: [   14.173039] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Dec 23 07:44:24 porteus kernel: [   14.571953] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
Dec 23 07:44:24 porteus kernel: [   14.572063] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
Dec 23 07:44:24 porteus kernel: [   14.572145] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-6.bin failed with error -2
Dec 23 07:44:24 porteus kernel: [   14.572190] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
Dec 23 07:44:24 porteus kernel: [   14.572231] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-4.bin failed with error -2
Dec 23 07:44:24 porteus kernel: [   14.572271] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-3.bin failed with error -2
Dec 23 07:44:24 porteus kernel: [   14.572312] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-2.bin failed with error -2
Dec 23 07:44:24 porteus kernel: [   14.572318] ath10k_pci 0000:03:00.0: Failed to find firmware-N.bin (N between 2 and 6) from ath10k/QCA6174/hw2.1: -2
Dec 23 07:44:24 porteus kernel: [   14.572320] ath10k_pci 0000:03:00.0: could not fetch firmware files (-2)
Dec 23 07:44:24 porteus kernel: [   14.572323] ath10k_pci 0000:03:00.0: could not probe fw (-2)
Dec 23 07:44:27 porteus kernel: [   17.815316] kfd kfd: DID 9851 is missing in supported_devices
Dec 23 07:44:27 porteus kernel: [   17.815320] kfd kfd: kgd2kfd_probe failed
Dec 23 07:44:27 porteus kernel: [   17.826387] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\_SB.PCI0.SMB.SMB0) (20170728/utaddress-247)
Dec 23 07:44:28 porteus kernel: [   18.882496] kfd kfd: DID 6660 is missing in supported_devices
Dec 23 07:44:28 porteus kernel: [   18.882499] kfd kfd: kgd2kfd_probe failed
Dec 23 07:44:28 porteus kernel: [   18.965018] ATPX version 1, functions 0x00000003
Dec 23 07:44:29 porteus NetworkManager[1099]: <warn>  [1514015069.3261] keyfile: 'hostname' option is deprecated and has no effect
Dec 23 07:44:35 porteus console-kit-daemon[1188]: WARNING: Failed to open connection to cgmanager. Is the cgmanager daemon running? 
Dec 23 07:44:39 porteus pulseaudio[1360]: [pulseaudio] authkey.c: Failed to open cookie file '/home/guest/.config/pulse/cookie': No such file or directory
Dec 23 07:44:39 porteus pulseaudio[1360]: [pulseaudio] authkey.c: Failed to load authentication key '/home/guest/.config/pulse/cookie': No such file or directory
Dec 23 07:44:39 porteus pulseaudio[1360]: [pulseaudio] authkey.c: Failed to open cookie file '/home/guest/.pulse-cookie': No such file or directory
Dec 23 07:44:39 porteus pulseaudio[1360]: [pulseaudio] authkey.c: Failed to load authentication key '/home/guest/.pulse-cookie': No such file or directory
Dec 23 07:44:39 porteus pulseaudio[1360]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
I hope this time I submitted something useful to find a way to fix it :oops:

Thanks
Porteus-XFCE-v3.2.2-x86_64 Kernel 4.9 AMD A8-7410, APU AMD Radeon R5 Graphics M330

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1099
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Porteus-4.0 is in the pipeline.

Post#19 by ncmprhnsbl » 24 Dec 2017, 01:57

@evergreen
looks like missing firmware
try installing this package kernel-firmware-20171130git-noarch-1.txz
and see if it makes a difference
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

evergreen
White ninja
White ninja
Posts: 15
Joined: 27 Mar 2016, 16:58
Distribution: porteus x64
Location: sweden

Porteus-4.0 is in the pipeline.

Post#20 by evergreen » 24 Dec 2017, 09:38

@ncmprhnsbl Finally is working just I have now an extra module with 92.6 MG to me is nothing nowadays extra data isn't a big deal
I didn't see any other issue with RC1 XFCE just USM didn't update properly , maybe my internet is poor
BTW kernel-firmware was unnecessary In the previous Porteus 3.2
Thanks and Merry Christmas !!
Porteus-XFCE-v3.2.2-x86_64 Kernel 4.9 AMD A8-7410, APU AMD Radeon R5 Graphics M330

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1099
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Porteus-4.0 is in the pipeline.

Post#21 by ncmprhnsbl » 24 Dec 2017, 12:35

very good :good:
brokenman should be able to use your info to include the relevant firmware so the firmware package isn't needed..
apparently there was some change upstream where firmware is no longer included in the kernel, instead now is a distro package
which has made brokenmans build process a little difficult, hence the possiblitiy of missing some firmware..
hopefully through the rc process most of these can be accounted for..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply