Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tle

Pages: 1 2 [3] 4 5 ... 29
31
The PR 3 years in the making has finally got merged into the main trunk!

Ref: https://github.com/briansmith/ring/pull/1057

The ring library is widely used by many rust-based projects. Having the upstream support ppc64le is a major milestone! I cannot wait to get DenoJS to support ppc64le


32
General Discussion / Re: Samsung PRO 980 1TB NVMe is working flawlessly
« on: September 23, 2023, 09:47:10 am »
Looking at the history of kernel performance changes in Fedora 37, I get the impression that no one does performance testing before releasing a kernel. The variability is high. It's a shame that Fedora developers don't see this.

SSD-Samsung-980-Pro-History-2023-09-20.png

ppc64le has always been treated as 2nd class citizen mainly due to hardware availability. I am wondering the performance regression also impact the x86_64?

33
Operating Systems and Porting / Re: [NEWS] Fedora 39 Beta
« on: September 21, 2023, 06:34:34 am »
All the recent announcements about X11 make me more worried about Fedora 40.

I do not think it would be the deal breaker because XWayland is still supported

34
Operating Systems and Porting / Re: [NEWS] Fedora 39 Beta
« on: September 21, 2023, 06:33:46 am »
It has actually happened (but in bug form)

GDM would crash if I use disable WaylandMode and GNOME (XOrg) also crashes for me

Bug reported at https://bugzilla.redhat.com/show_bug.cgi?id=2239055

35
Applications and Porting / Re: GZDoom
« on: September 21, 2023, 06:31:36 am »
For Fedora users, you can find the RPM at https://copr.fedorainfracloud.org/coprs/nalika/gzdoom/

36
This is yet another source port for Quake 3 and considered one of the best Vulkan renderer port out there.



I am happy that the author has finally accepted my Pull Request to make it compile for ppc64le

https://github.com/suijingfeng/vkQuake3/pull/18

37
Operating Systems and Porting / [NEWS] Fedora 39 Beta
« on: September 19, 2023, 05:20:33 pm »
It’s that time of the year again.

https://fedoramagazine.org/announcing-fedora-39-beta/

Fedora 39 is now Beta. Please have a go at it and report and any issue in Bugzilla



38
General Discussion / Re: Samsung PRO 980 1TB NVMe is working flawlessly
« on: September 19, 2023, 08:51:41 am »
Just do a quick reading benchmark with Linux 6.5.3, it's around  3361.47 MB/sec which is a bit disappointing

```
$ uname -ar
Linux shrimp-paste 6.5.3-300.fc39.ppc64le #1 SMP Wed Sep 13 12:19:24 UTC 2023 ppc64le GNU/Linux

$ sudo hdparm -t /dev/nvme0n1
[sudo] password for tle:

/dev/nvme0n1:
 Timing buffered disk reads: 10086 MB in  3.00 seconds = 3361.47 MB/sec
```

39
Talos II / Re: Unsatisfactory performance of SSD drives
« on: September 19, 2023, 06:18:01 am »
That’s intriguing. Can you tried the 6.5.0?

40
Operating Systems and Porting / Re: [NEWS] Linux 6.5
« on: September 11, 2023, 06:15:09 pm »
I'm testing it, it seems to be fine on Debian 11.7... I temporarily went back to 11 because 12 no longer works for me, after the Kernel problems the file directory disappeared and it wasn't even updating anymore.

which file directory has gone missing?

42
These days I am using GNOME Web simply because I loves its simplicity. However the WebkitGTK is pretty poor in performance.

I am too grateful for all the works the OpenPOWER community has done.

@ClassicHasClass is there anything I could assist with the firefox JIT?


43

EDIT: Than Ngo of Red Hat has cherry-picked all ppc64le patches into the main trunk. Now we officially have chromium for Fedora 40 or newer!

URL https://src.fedoraproject.org/rpms/chromium/pull-request/37 *STILL WORK IN PROGRESS*

The last time I was successful at getting Chromium up and running in Fedora is 3 years ago. That was version 88. Now Chromium has reached version 117.

This weekend I've spent a bit of time to adapt Timothy Pearson's patchset from Debian deb package for the official chromium Fedora RPM. So far I could get the whole application compiled and running HOWEVER the browser get into SIGSEGV or SIGTRAP with web pages that has JavaScript. So I speculate this might be related to the V8 engine.

The error outputs in the console is not so much helpful:

Code: [Select]
[1961086:1961086:0910/235841.808221:ERROR:CONSOLE(1)] "Uncaught SyntaxError: Invalid regular expression: /([^\s]+?)\(([\s\S]*)\)/: Maximum call stack size exceeded", source: chrome://resources/polymer/v3_0/polymer/polymer_bundled.min.js (1)
[0910/235911.891648:ERROR:check.cc(298)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[0911/000357.201831:ERROR:check.cc(298)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

I also attempt to gdb and could not find any useful backtrace (NOTE: I manually commented out all `strip` symbols in the build spec file).

The full log out when trying to open a webpage https://gist.github.com/runlevel5/3c85515c521ebcfb6ca65e4697b6b1d1

Any idea how to get more logs out of V8 in Chromium?



44
Everything, I mean every single component has redundancy. Plus it runs the super fast IBM Power10 CPU!

It's surely unaffordable for us pro-consumers but hey we all can dream one day Raptor come out with a Power10 workstation/

Source: https://www.youtube.com/watch?v=7ZdsWebj9Jw

45
Great thanks to ClassicHasClass for the Pull Request https://github.com/dosbox-staging/dosbox-staging/pull/2828

Now dosbox-staging can achieve 41 fps!


Pages: 1 2 [3] 4 5 ... 29