Porteus Kernel Builder

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
User avatar
Rava
Contributor
Contributor
Posts: 2252
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Porteus Kernel Builder

Post#631 by Rava » 12 Jul 2019, 10:25

Blaze wrote:
11 Jul 2019, 16:56
I think that not bad if brokenman replace kernel and all stuff (vmlinuz, 000-kernel.xzm, 06-crippled_sources.xzm) for him to current 5.1.xx kernel by neko in all ISO files and sync updated ISO files in the all Porteus mirrors.
I think that would be even better. +2

But will also put workload on brokenman.

And we might call it 5.0rc2 then cause - you know - users might otherwise get confused when Porteus 5.0rc1 differs to Porteus 5.0rc1. Just my 2 cents.
Cheers!
Yours Rava

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2255
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

Porteus Kernel Builder

Post#632 by ncmprhnsbl » 12 Jul 2019, 12:41

Blaze wrote:
12 Jul 2019, 07:46
Probably this problem in the old nvidia driver and it is not compatible with the new Porteus 5.0 RC1 base (xorg-server etc) and a new kernel.
check this patch: https://aur.archlinux.org/cgit/aur.git/ ... idia-340xx
and for 5.1: https://aur.archlinux.org/cgit/aur.git/ ... idia-340xx
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
M. Eerie
Samurai
Samurai
Posts: 179
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

Porteus Kernel Builder

Post#633 by M. Eerie » 13 Jul 2019, 10:30

Kernel 5.1.17 this is my /var/log/rc.log

Code: Select all

 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
Error parsing source statement, source plugin unix-dgram not found in source generator system:6:14-6:24:
1       
2       #Start Block source generator system
3       channel {
4           source {
5       channel {
6----->     source { unix-dgram("/dev/log" so_rcvbuf(8192) flags(syslog-protocol));
6----->              ^^^^^^^^^^
7        };
8           rewrite { set("${.unix.pid}" value("PID") condition("${.unix.pid}" ne "")); };
9       };
10      file("/dev/kmsg" program-override("kernel") flags(kernel) format(linux-kmsg) keep-timestamp(no));
11      

Included from /etc/syslog-ng/syslog-ng.conf:22:3-22:11:
17        perm(0640);
18        group("log");
19      };
20      
21      source src {
22---->   system();
22---->   ^^^^^^^^
23        internal();
24      };
25      
26      destination d_authlog { file("/var/log/auth.log"); };
27      destination d_syslog { file("/var/log/syslog.log"); };


syslog-ng documentation: https://www.balabit.com/support/documentation?product=syslog-ng-ose
contact: https://lists.balabit.hu/mailman/listinfo/syslog-ng
 * Configuration error. Please fix your configfile (/etc/syslog-ng/syslog-ng.conf)
 [ !! ]
 * ERROR: syslog-ng failed to start
 * Starting acpid ...
At least /etc/porteus.d is back again :)

Thanks

User avatar
Rava
Contributor
Contributor
Posts: 2252
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Porteus Kernel Builder

Post#634 by Rava » 13 Jul 2019, 12:22

Thanks I Check these out but first I need the official 5.0rc1 running - see my failure wird startx when using older kernel. Porteus-5.0rc1 (Post by Rava #72791) Hopefully nekos newer kernel and 000-kernel and *devel helps and I can start the system.
Cheers!
Yours Rava

neko
DEV Team
DEV Team
Posts: 1562
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#635 by neko » 14 Jul 2019, 12:51

Most recent versions of build examples were updated.

Please refer to the top article of this thread.
Porteus Kernel Builder


Note 1: gcc is updated.
gcc-9.1.0-x86_64-1 ---> gcc-9.1.0-x86_64-2

Note 2: Configs were changed by "make oldconfig" command with the following spec.
<5.1.18 32/64Bit>
Asix PHYs (AX88796B_PHY) [N/m/?] (NEW) N
<4.19.59 32/64Bit>
Asix PHYs (AX88796B_PHY) [N/m/?] (NEW) N



Thanks.

User avatar
Rava
Contributor
Contributor
Posts: 2252
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Porteus Kernel Builder

Post#636 by Rava » 14 Jul 2019, 21:02

neko wrote:
14 Jul 2019, 12:51
Note 1: gcc is updated.
gcc-9.1.0-x86_64-1 ---> gcc-9.1.0-x86_64-2
Would that be too much of a change to push e.g. Nvidia driver compile off its tracks?
Cheers!
Yours Rava

neko
DEV Team
DEV Team
Posts: 1562
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#637 by neko » 14 Jul 2019, 22:37

@Rava
My build environment is constructed with ArchLinux packages.
These packages are updated frequently (rolling-release).
Now, the current gcc was updated.

I don't know that the new gcc has some effect on Nvidia driver.
I don't have NVIDIA.
If you have the time that you check it and report the result, it will be happy for us.


Thanks.

fulalas
DEV Team
DEV Team
Posts: 1456
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus Kernel Builder

Post#638 by fulalas » 15 Jul 2019, 00:14

@Rava, I've just tested Blaze's nvidia script and it's working with neko's last kernel (5.2.1) and current Porteus 5 RC1 devel module :good:

User avatar
Rava
Contributor
Contributor
Posts: 2252
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Porteus Kernel Builder

Post#639 by Rava » 15 Jul 2019, 00:38

Update - I edited / expanded the post, but quite some hours later. When I tried saving the edit promptly I got into Ajax error: Internal Server Error every single time I tried saving the edit, even https://downforeveryoneorjustme.com/forum.porteus.org reported:
Forum.porteus.org Status
Is forum.porteus.org down right now?
It's not just you! forum.porteus.org is down.
(highlighting by me)
__________________________________________
fulalas wrote:
15 Jul 2019, 00:14
@Rava, I've just tested Blaze's nvidia script and it's working with neko's last kernel (5.2.1)
Does it need patches for the Nvidia source or does it work out of the box?

Also, which versions did you compile?
304.37? 340.107? Or 390.87?
fulalas wrote:
15 Jul 2019, 00:14
current Porteus 5 RC1 devel module :good:
The kernel and system gcc in current 5.0rc1 mismatch. How can you compile a working Nvidia module with that?

Also, if it is a V304 and a V340 working module, can you please upload these?
Last edited by Rava on 15 Jul 2019, 16:44, edited 3 times in total.
Reason: typo; expanded the post 16 hours later - promply edit saving failed due to AJAX error - Internal Server Error
Cheers!
Yours Rava

fulalas
DEV Team
DEV Team
Posts: 1456
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus Kernel Builder

Post#640 by fulalas » 16 Jul 2019, 18:45

@Blaze, it's working out of the box -- no patch needed; it simply works :)

Current version is 430.34 :good:

User avatar
Rava
Contributor
Contributor
Posts: 2252
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Porteus Kernel Builder

Post#641 by Rava » 17 Jul 2019, 11:27

fulalas wrote:
16 Jul 2019, 18:45
Current version is 430.34 :good:
AFAIK this is a working version for recent hardware, but for older hardware, older versions are needed, e.g. 340.107 (unless there is now a newer 340 version) or even 304.37 (unless there is now a newer 304, blabla).

My most recent hardware is in a Laptop - GeForce GT330M - and it never worked with any version with a larger main version number than 340. Not even 390.87. Image
Cheers!
Yours Rava

fulalas
DEV Team
DEV Team
Posts: 1456
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus Kernel Builder

Post#642 by fulalas » 17 Jul 2019, 15:24

@Rava, see this topic to better understand Nvidia driver number conventions: Understanding Nvidia drivers numbers (plus: xzm modules)

User avatar
Rava
Contributor
Contributor
Posts: 2252
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 4.0 x86-64 XFCe
Location: Forests of Germany

Porteus Kernel Builder

Post#643 by Rava » 17 Jul 2019, 16:06

fulalas wrote:
17 Jul 2019, 15:24
@Rava, see this topic to better understand Nvidia driver number conventions: Understanding Nvidia drivers numbers (plus: xzm modules)
There you wrote:
fulalas wrote:
20 Nov 2016, 18:35
GeForce up to 300 -> driver version up to 340.xx (current 340.101)
Current was last I checked 340.107 - and is GeForce GT330M now included in "GeForce up to 300", cause 300 < 330. But for me, the 340.107 always worked. (I presume you meant up to 3xx, aka up to 399)

Now the newest seems to be "340.1070" :)

Update
At least the Nvidia.com site said so, seems they are either incompetent or practical jokers, since I got only redirected to the download of the "340.107" version, and sure the md5sum of the new download is the same as the one from "340.107". :x


Update2
Now I had a support chat - and he or she told me that "340.107" is indeed the newest version.
Cheers!
Yours Rava

fulalas
DEV Team
DEV Team
Posts: 1456
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus Kernel Builder

Post#644 by fulalas » 17 Jul 2019, 18:45

Rava wrote:
17 Jul 2019, 16:06
cause 300 < 330
Oh, gosh... By 300 I mean 300 series (which include all 3xx), of course. ;)

User avatar
Blaze
DEV Team
DEV Team
Posts: 2720
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#645 by Blaze » 17 Jul 2019, 19:24

fulalas wrote:
16 Jul 2019, 18:45
it's working out of the box -- no patch needed; it simply works :)

Current version is 430.34
I belive in it.

Just I use at my job old NVIDIA GeForce GTS 250 video card and if look at official website of NVIDIA - the latest driver version for this card is 340.107 from 2018.6.6 and seems for Rava too.
Seems too that NVIDIA does not support by a new drivers for these old video cards :Oops:
Probaly need to apply some Arch Linux pathes that share ncmprhnsbl, but this PC is use Porteus v4.0 x86_64 + kernel 4.15.0-rc7 and I have no reason to check it. It was just a sporting interest.
Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

Post Reply