users January 2024

users@lists.fedoraproject.org

57 participants
40 discussions

by Sumantro Mukherjee

Hey All, I would like to invite all of you to participate in the Kernel 6.7 Test week is happening from 2024-01-21 to 2024-01-28. It's fairly simple, head over to the wiki [0] and read in detail about the test week and simply run the test case mentioned in[1] and enter your results. As usual, the Fedora QA team will hangout at #fedora-test-day(a)libera.chat for questions and discussion. Happy New Year :) [0] http://fedoraproject.org/wiki/Test_Day:2024-01-21_Kernel_6.7_Test_Week [1] https://testdays.fedoraproject.org/events/173 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

4 months, 1 week

2
1
0 / 0

libdvdcss

by Bill Cunningham

Does fedora maintain a version of libdvdcss. I thought for sure I backed up my version online but can't seem to find it. I went to the main repo and downloaded the 4.x.x. version which is the latest but cannot get it to compile. I have libdvdread-devel installed. Maybe I am missing something else. I believe this is a decryption library. Maybe someone can point me in the right direction. B

4 months, 1 week

4
6
0 / 0

VMware woes

by Sherman Grunewagen

Hello all. Does anyone have VMware Workstation Pro 17.5.0 running with any of the later 6.6.X kernels? I'm having a hard time getting it to run with a Fedora 38 installation. I'm fully updated as of 2 days ago, including the 6.6.9 kernel. When I try to start Workstation directly after VMware installation I get a popup saying that the kernel-headers package for kernel-6.6.9 is missing and so it can't build some modules. the problem is that the kernel-headers package for 6.6.9 is missing from Updates. The latest package is for 6.6.3. I'm guessing those modules are vmmon and vmnet, which usually have to be rebuilt for new kernels and so I also tried build the modules following the instructions here: https://github.com/mkubecek/vmware-host-modules/blob/workstation-17.5.0/I... but it failed also and I don't know how to debug the problems. Would appreciate any help! -- Sherman

4 months, 1 week

12
23
0 / 0

KAMPANAT THUMWONG

by KAMPANAT

4 months, 1 week

1
0
0 / 0

Lenovo ThinkBook 16 G6 touchpad - no right click ?

by lejeczek

Hi guys. Anybody here on a Thinkbook 16 G6? I just got one myself and it seems that the right-click is not there - that should not be new laptop with mechanical-electrical damage, right? many thanks, L.

4 months, 1 week

1
0
0 / 0

Q about Fedora Users list behaviour

by Sherman Grunewagen

When I send a message to the list, the "From" field has my name and e-mail addr. But when it appears on the list, it's been magically changed to "fedora users". Some posters have their name preserved in the From: field. Is there a list setting that controls this?

4 months, 1 week

3
3
0 / 0

a bit off topic -- software development checklist!

by bruce

Hey. A bit off topic, but I'll ask anyway. For those of you who dabble in developing/managing software teams, do you have any "fav" open source proj management webapps you use? I'm looking for a reasonable/good app I could use for a personal project that might have a small team . I'm looking for the ability to "manage"/track the dev/test/deploy processes as the app is created. I'm looking at some different apps, thought I'd ask here as well. Any thoughts/pointers would be appreciated. thanks

4 months, 1 week

1
0
0 / 0

NVMe sector size ?

by lejeczek

Hi guys. I wonder if anybody played with both sector sizes 512 & 4086 and if yes so - also had some test results / thoughts to share? There are bits about it - bit confusing & a mixed-bag - over the net but I failed to find anything Fedora-specific. thanks, L.

4 months, 1 week

9
9
0 / 0

Re: NVMe sector size ?

by Thomas Cameron

On 1/10/24 12:39, Bob Marčan wrote: > On Wed, 10 Jan 2024 12:19:30 -0600 > "Thomas Cameron" <thomas.cameron(a)camerontech.com> wrote: > >> I just checked my system, and it looks like it's set for 512k blocks: >> >> [root@case ~]# blockdev --report /dev/nvme1n1p4 >> RO RA SSZ BSZ StartSec Size Device >> rw 256 512 512 69216256 964765417472 /dev/nvme1n1p4 >> >> I assume the installer chose the block size, since I basically did a >> "next, next, next" installation. Should I have chosen something different? >> >> Thomas >> > > [root@smicro bob]# di |grep nvme > /dev/nvme0n1p2 /boot 1.9G 0.5G 1.3G 32% ext4 > /dev/nvme0n1p1 /boot/efi 1022.0M 17.4M 1004.6M 2% vfat <== > /dev/nvme1n1p4 /root-ssd1 849.9G 88.0G 718.6G 15% ext4 > [root@smicro bob]# > [root@smicro bob]# blockdev --report /dev/nvme* > RO RA SSZ BSZ StartSec Size Device > blockdev: ioctl error on /dev/nvme0 > rw 256 512 4096 0 1000204886016 /dev/nvme0n1 > rw 256 512 512 2048 1073741824 /dev/nvme0n1p1 <== > rw 256 512 4096 2099200 2147483648 /dev/nvme0n1p2 > rw 256 512 4096 6293504 68719476736 /dev/nvme0n1p3 > rw 256 512 4096 140511232 928262389760 /dev/nvme0n1p4 > blockdev: ioctl error on /dev/nvme1 > rw 256 512 4096 0 1000204886016 /dev/nvme1n1 > rw 256 512 4096 2048 1073741824 /dev/nvme1n1p1 > rw 256 512 4096 2099200 2147483648 /dev/nvme1n1p2 > rw 256 512 4096 6293504 68719476736 /dev/nvme1n1p3 > rw 256 512 4096 140511232 928262389760 /dev/nvme1n1p4 > [root@smicro bob]# > > > Ah, ok... I see. My first drive is a Windows drive, the second is Linux: [root@case ~]# blockdev --report /dev/nvme* RO RA SSZ BSZ StartSec Size Device blockdev: ioctl error on /dev/nvme0 rw 256 512 4096 0 1000204886016 /dev/nvme0n1 rw 256 512 4096 2048 104857600 /dev/nvme0n1p1 rw 256 512 4096 206848 16777216 /dev/nvme0n1p2 rw 256 512 4096 239616 999373668352 /dev/nvme0n1p3 rw 256 512 4096 1952141312 706740224 /dev/nvme0n1p4 blockdev: ioctl error on /dev/nvme1 rw 256 512 4096 0 1000204886016 /dev/nvme1n1 rw 256 512 512 2048 629145600 /dev/nvme1n1p1 rw 256 512 512 1230848 1073741824 /dev/nvme1n1p2 rw 256 512 4096 3328000 33734787072 /dev/nvme1n1p3 rw 256 512 512 69216256 964765417472 /dev/nvme1n1p4 [root@case ~]# I wonder why the installer chose a 512k block size on my largest partition, but 4096 for my swap? I don't recall seeing a block size option during installation, but I may very well have missed it. I'll throw it out there again, though: should I have done something different during installation? -- Thomas

4 months, 1 week

1
0
0 / 0

Re: 6.6.x kernels do not boot successfully

by olivares33561

Sent from ProtonMail, encrypted email based in Switzerland. Sent with Proton Mail secure email. On Friday, December 15th, 2023 at 12:53 PM, Felix Miata <mrmazda(a)earthlink.net> wrote: > olivares33561 composed on 2023-12-15 13:35 (UTC-0500): > > > Do I try to use these parameters here: > > > noresume audit=0 ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full mitigations=off > > > after removing rhgb ? > > > Will give it a try and report back. > > > I wasn't suggesting you should, but they are all valid, so you may try them if you > think them relevant to your installation. I included them because their presence > here makes my configuration different from yours, and /might/ affect outcome. > > noresume does as it says, prevents attempting to resume from hibernation > > audit=0 simply disables auditing, so makes journal and dmesg less noisy > > ipv6.disable does as it says, and may or may not present trouble from an otherwise > successful boot > > net.ifnames=0 could very well break your network configuration, so I don't suggest > you try it. It wouldn't likely help you boot anyway. > > consoleblank=0 acts as a screensaving disabler on the vttys, so would not affect > whether you can boot. > > preempt=full shouldn't affect whether or not you can boot, but could be worth > trying, but I wouldn't expect it to affect your problem. > > mitigations=off makes a computer faster, but breaks some security function. It > could be worth trying, but I wouldn't expect it to affect your problem. > -- > Evolution as taught in public schools is, like religion, > based on faith, not based on science. > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata Tried it but no success. I am looking for differences, and System.map is biggger in 6.6.6-* kernel olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ ls -l /lib/modules/6.6.6-200.fc39.x86_64/ total 28744 lrwxrwxrwx. 1 root root 38 Dec 10 18:00 build -> /usr/src/kernels/6.6.6-200.fc39.x86_64 -rw-r--r--. 1 root root 266380 Dec 10 18:00 config drwxr-xr-x. 1 root root 0 Dec 10 18:00 extra drwxr-xr-x. 1 root root 84 Dec 15 12:41 kernel -rw-r--r--. 1 root root 1286827 Dec 15 12:41 modules.alias -rw-r--r--. 1 root root 1262387 Dec 15 12:41 modules.alias.bin -rw-r--r--. 1 root root 1707 Dec 10 18:00 modules.block -rw-r--r--. 1 root root 10890 Dec 10 18:00 modules.builtin -rw-r--r--. 1 root root 13436 Dec 15 12:41 modules.builtin.alias.bin -rw-r--r--. 1 root root 13506 Dec 15 12:41 modules.builtin.bin -rw-r--r--. 1 root root 93962 Dec 10 18:00 modules.builtin.modinfo -rw-r--r--. 1 root root 574036 Dec 15 12:41 modules.dep -rw-r--r--. 1 root root 765276 Dec 15 12:41 modules.dep.bin -rw-r--r--. 1 root root 375 Dec 15 12:41 modules.devname -rw-r--r--. 1 root root 241 Dec 10 18:00 modules.drm -rw-r--r--. 1 root root 34 Dec 10 18:00 modules.modesetting -rw-r--r--. 1 root root 2826 Dec 10 18:00 modules.networking -rw-r--r--. 1 root root 180153 Dec 10 18:00 modules.order -rw-r--r--. 1 root root 1208 Dec 15 12:41 modules.softdep -rw-r--r--. 1 root root 583203 Dec 15 12:41 modules.symbols -rw-r--r--. 1 root root 707403 Dec 15 12:41 modules.symbols.bin lrwxrwxrwx. 1 root root 5 Dec 10 18:00 source -> build -rw-r--r--. 1 root root 157932 Dec 10 18:00 symvers.xz -rw-------. 1 root root 8782310 Dec 10 18:00 System.map drwxr-xr-x. 1 root root 0 Dec 10 18:00 systemtap drwxr-xr-x. 1 root root 0 Dec 10 18:00 updates drwxr-xr-x. 1 root root 36 Dec 15 12:41 vdso -rwxr-xr-x. 1 root root 14669576 Dec 10 18:00 vmlinuz drwxr-xr-x. 1 root root 0 Dec 10 18:00 weak-updates olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ ls -l /lib/modules/6.5.12-300.fc39.x86_64/ total 28496 lrwxrwxrwx. 1 root root 39 Nov 19 18:00 build -> /usr/src/kernels/6.5.12-300.fc39.x86_64 -rw-r--r--. 1 root root 264245 Nov 19 18:00 config drwxr-xr-x. 1 root root 0 Nov 19 18:00 extra drwxr-xr-x. 1 root root 84 Nov 27 07:21 kernel -rw-r--r--. 1 root root 1275188 Nov 27 07:23 modules.alias -rw-r--r--. 1 root root 1252698 Nov 27 07:23 modules.alias.bin -rw-r--r--. 1 root root 1707 Nov 19 18:00 modules.block -rw-r--r--. 1 root root 10883 Nov 19 18:00 modules.builtin -rw-r--r--. 1 root root 13436 Nov 27 07:23 modules.builtin.alias.bin -rw-r--r--. 1 root root 13506 Nov 27 07:23 modules.builtin.bin -rw-r--r--. 1 root root 93722 Nov 19 18:00 modules.builtin.modinfo -rw-r--r--. 1 root root 565244 Nov 27 07:23 modules.dep -rw-r--r--. 1 root root 755050 Nov 27 07:23 modules.dep.bin -rw-r--r--. 1 root root 375 Nov 27 07:23 modules.devname -rw-r--r--. 1 root root 241 Nov 19 18:00 modules.drm -rw-r--r--. 1 root root 34 Nov 19 18:00 modules.modesetting -rw-r--r--. 1 root root 2826 Nov 19 18:00 modules.networking -rw-r--r--. 1 root root 178440 Nov 19 18:00 modules.order -rw-r--r--. 1 root root 1152 Nov 27 07:23 modules.softdep -rw-r--r--. 1 root root 575357 Nov 27 07:23 modules.symbols -rw-r--r--. 1 root root 698154 Nov 27 07:23 modules.symbols.bin lrwxrwxrwx. 1 root root 5 Nov 19 18:00 source -> build -rw-r--r--. 1 root root 156460 Nov 19 18:00 symvers.xz -rw-------. 1 root root 8727513 Nov 19 18:00 System.map drwxr-xr-x. 1 root root 0 Nov 19 18:00 systemtap drwxr-xr-x. 1 root root 0 Nov 19 18:00 updates drwxr-xr-x. 1 root root 36 Nov 27 07:21 vdso -rwxr-xr-x. 1 root root 14540552 Nov 19 18:00 vmlinuz drwxr-xr-x. 1 root root 0 Nov 19 18:00 weak-updates olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ Best Regards, Antonio

4 months, 1 week

2
2
0 / 0