Porteus

brokenman, here's the full log after the ethernet problem I told you: http://www.mediafire.com/file/k0cvaurvb ... report.txt

Blaze wrote:Hi, fulalas. You are forgot to clean nvidia module via my script.
Look at this topic http://forum.porteus.org/viewtopic.php?f=54&t=5858 (Russian) and this post (English)

I'll take a look! Thank you very much!

@ brokenman

What translation would you use in german?

What I've changed so far:

Imho every linux user knows "Root", no need to Translate..
Bulk Rename Utility is also known in Germany - "Massenumbenennen" sounds like a word originated in the WW2..lol.

Ok so I've added (root) to the Thunar-gksu.desktop file. I also changed the icon in the menu to a red folder color.

Ed_P, thanks for the reminder about updating the version on the forum.

Fulalas, thanks for the system log. It looks like your using realtek. The 4.8.7 kernel saw many updates to intel/i915 video and to network. The next kernel also has many network related fixes. I think it is best to wait for the next kernel. I can upload it to the server tonight.

from /var/log/secure

porteus polkitd[903]: Loading rules from directory /etc/polkit-1/rules.d
porteus polkitd[903]: Loading rules from directory /usr/share/polkit-1/rules.d
porteus polkitd[903]: /etc/polkit-1/rules.d/25-guest-mount.rules:10: SyntaxError: syntax error
porteus polkitd[903]: Error compiling script /etc/polkit-1/rules.d/25-guest-mount.rules

brokenman wrote:The 4.8.7 kernel saw many updates to intel/i915 video and to network. The next kernel also has many network related fixes. I think it is best to wait for the next kernel. I can upload it to the server tonight.

Great news! I'm waiting to test it

Blaze, looks like your script removes the garbage that Nvidia driver setup creates, but it doesn't solve the problem I was talking about.

Just to clarify: ldconfig -- called when you activate a xzm module -- checks all libraries and its symlinks, trying to correct something wrong or not in the best situation. So if, for instance, you have two versions of a given library, ldconfig will change all symlinks of this library to the newest version. In the case of Nvidia driver the problem happens with libGL.so.1 symlink that should point to libGL.so.1.0.0 (from Nvidia driver), but Porteus already comes with libGL.so.1.2.0, so ldconfig repoints libGL.so.1 symlink to libGL.so.1.2.0 library, blowing away OpenGL support (and god knows what else).

I ended doing a copy of libGL.so.1.0.0 (Nvidia driver) with the name libGL.so.1.2.0 inside Nvidia driver xzm module, so ldconfig can't mess with it anymore (another solution can be removing libGL.so.1.2.0 during boot, but I didn't test it). If you're interested, here's the link of the patched Nvidia driver 367-57 xzm module: http://www.mediafire.com/file/3ylt1meyu ... x86_64.xzm

I've uploaded the 64bit kernel for you to check. kernel-4.8.8
It's in the x86_64/kernel folder. Please replace vmlinuz and 000-kernel.xzm in your current ISO.

brokenman wrote:I've uploaded the 64bit kernel for you to check. kernel-4.8.8
It's in the x86_64/kernel folder. Please replace vmlinuz and 000-kernel.xzm in your current ISO.

Cool! I'm using it right now, so the first good news is that it fixes the first problem with my Realtek ethernet wired, which was simply not working at all. Let's hope the second problem (random driver freezing) gets fixed too. Thanks!

That's good news. I had a feeling it would be the case.

Regarding the nVidia links, here is what the nVidia site recommends:
http://us.download.nvidia.com/XFree86/L ... nents.html

If there are other libraries whose "soname" conflicts with that of the NVIDIA libraries, ldconfig may create the wrong symlinks. It is recommended that you manually remove or rename conflicting libraries

EDIT:
Removed code as I realized this is not a module you activate.

brokenman wrote:That's good news. I had a feeling it would be the case.

Regarding the nVidia links, here is what the nVidia site recommends:
http://us.download.nvidia.com/XFree86/L ... nents.html

If there are other libraries whose "soname" conflicts with that of the NVIDIA libraries, ldconfig may create the wrong symlinks. It is recommended that you manually remove or rename conflicting libraries

Great! So we're doing just fine! I'll upload the driver module I've created right now and give people the change to test.

Is there anyone here with a Nvidia card available to test?

brokenman wrote:I've uploaded the 64bit kernel for you to check. kernel-4.8.8
It's in the x86_64/kernel folder. Please replace vmlinuz and 000-kernel.xzm in your current ISO.

Should we include the crippled_sources and virtualbox modules too?

fulalas wrote:Is there anyone here with a Nvidia card available to test?

I'll check my wife's notebook later. Any special command or log to check?

Should we include the crippled_sources and virtualbox modules too?

No. Just the kernel files. I'm off to bed now. 2am here.

^ Interesting. You're 3 hrs ahead of me. I would have thought only 2.

Ed_P wrote:I'll check my wife's notebook later. Any special command or log to check?

Just put this xzm module inside porteus/modules/ then reboot and pray Now, serious: check if Nvidia Settings opens without any error and that you can run glxgears.

http://www.mediafire.com/file/iigth9v5j ... x86_64.xzm

Ed_P wrote:^ Interesting. You're 3 hrs ahead of me. I would have thought only 2.

We're now on DST (Daylight Savings Time)

update-flash wasnt getting past the firewall (if fw off, would work)
tracked it down to this line:
67 -- changed it to: (like update-firefox)
or (like the others)

now works with firewall on..
apologies for not finding this sooner...