Page 43 of 50

Porteus Kernel Builder

Posted: 12 Jul 2019, 10:25
by Rava
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.

Porteus Kernel Builder

Posted: 12 Jul 2019, 12:41
by ncmprhnsbl
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

Porteus Kernel Builder

Posted: 13 Jul 2019, 10:30
by M. Eerie
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

Porteus Kernel Builder

Posted: 13 Jul 2019, 12:22
by Rava
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.

Porteus Kernel Builder

Posted: 14 Jul 2019, 12:51
by neko
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.

Porteus Kernel Builder

Posted: 14 Jul 2019, 21:02
by Rava
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?

Porteus Kernel Builder

Posted: 14 Jul 2019, 22:37
by neko
@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.

Porteus Kernel Builder

Posted: 15 Jul 2019, 00:14
by fulalas
@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:

Porteus Kernel Builder

Posted: 15 Jul 2019, 00:38
by Rava
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?

Porteus Kernel Builder

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

Current version is 430.34 :good:

Porteus Kernel Builder

Posted: 17 Jul 2019, 11:27
by Rava
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

Porteus Kernel Builder

Posted: 17 Jul 2019, 15:24
by fulalas
@Rava, see this topic to better understand Nvidia driver number conventions: Understanding Nvidia drivers numbers (plus: xzm modules)

Porteus Kernel Builder

Posted: 17 Jul 2019, 16:06
by Rava
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.

Porteus Kernel Builder

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

Porteus Kernel Builder

Posted: 17 Jul 2019, 19:24
by Blaze
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.