LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

Loomx 12-22-2020 08:10 PM

Quote:

Originally Posted by SCerovec (Post 6198768)
We aren't old ones really, it's only that there are no more spare parts left in production for us.

So, not even LTS?

Regarding the bash completions, mine are the correct permissions so could be a local issue?

gmgf 12-22-2020 08:11 PM

ndctl-71.1:

https://github.com/pmem/ndctl/releases

gmgf 12-22-2020 08:32 PM

Quote:

Originally Posted by gmgf (Post 6198788)

the 'ndctl-71' package probabbly have bad permission, the file /usr/share/bash-completion/completions/ndctl need to change to chmod 644.

biker_rat 12-22-2020 09:08 PM

Xfce 4.16 is released today.

gmgf 12-22-2020 09:25 PM

In the util-linux package the doinst.sh create a symbolic link /usr/share/bash-completion/completions/runuser, which does not point to anything, probably because su is in shadow package not in util-linux.

( cd usr/share/bash-completion/completions ; rm -rf runuser )
( cd usr/share/bash-completion/completions ; ln -sf su runuser )

gmgf 12-22-2020 10:48 PM

Quote:

Originally Posted by biker_rat (Post 6198803)
Xfce 4.16 is released today.

https://www.xfce.org/download/changelogs/4.16

I have added 'libgtop' it's a new dep, xfce4-4.16, build and work here on current ;)

gmgf 12-23-2020 12:10 AM

Quote:

Originally Posted by gmgf (Post 6198804)
In the util-linux package the doinst.sh create a symbolic link /usr/share/bash-completion/completions/runuser, which does not point to anything, probably because su is in shadow package not in util-linux.

( cd usr/share/bash-completion/completions ; rm -rf runuser )
( cd usr/share/bash-completion/completions ; ln -sf su runuser )

Probably, one possible solution is build util-linux with, '--disable-su'. (tested here)

chrisretusn 12-23-2020 03:38 AM

Quote:

Originally Posted by ardya (Post 6198752)
If this isn't the correct thread to ask, my apologies in advance.

I went looking for avahi in -current while testing a new service I've deployed, but couldn't find it.

Is avahi being ignored by Slackware for specific reasons?

Thanks

It's not being ignored, it just not in -current, it is available on SBo. You have to build it. I have it installed on my system, using my own build, you will also need to rebuild cups from the slackware source tree.

TheTKS 12-23-2020 08:11 AM

Quote:

Originally Posted by mario (Post 6198670)
It looks like xhci-pci.ko from 5.10.x needs "renesas_usb_fw.mem" file, which is not in kernel-firmware.

Quote:

Originally Posted by LuckyCyborg (Post 6198749)
Hint: no, it is not named "renesas_usb_fw.mem" and the special hint is on question.

Joking aside, without that particular firmware file, probably half of the USB 3.0 pci-express adapters will stop working.

In my case, being unlucky as usal, the ratio was around 90% of not working.
...

OK, there it is: https://raw.githubusercontent.com/de...ter/UPDATE.mem

Should be saved to /lib/firmware with the name requested by kernel.

Still in 5.10.2

Running the output of mkinitrd_command_generator.sh with 5.10.2 as

Code:

# mkinitrd -c -k 5.10.2...
gives

Code:

OK: /lib/modules/5.10.2/kernel/drivers/usb/host/xhci-pci.ko added.
WARNING:  Could not find firmware "/lib/firmware/renesas_usb_fw.mem"

I'm not one of the unlucky ones like (un)LuckyCyborg with a problem connecting USB devices, though. Sorry to hear that, LC, hopefully this is resolved for you soon.

TKS

ardya 12-23-2020 08:24 AM

Quote:

Originally Posted by chrisretusn (Post 6198874)
It's not being ignored, it just not in -current, it is available on SBo. You have to build it. I have it installed on my system, using my own build, you will also need to rebuild cups from the slackware source tree.

Yes, I'm aware its on SBo.
My question is why is it excluded from the main distribution?

ponce 12-23-2020 08:37 AM

Quote:

Originally Posted by TheTKS (Post 6198962)
Code:

OK: /lib/modules/5.10.2/kernel/drivers/usb/host/xhci-pci.ko added.
WARNING:  Could not find firmware "/lib/firmware/renesas_usb_fw.mem"


that's an issue only if you have one of the two affected USB 3.0 controllers, Renesas uPD720201 and uPD720202, otherwise is just an harmless warning: you can check with
Code:

lspci | grep Renesas
BTW should be fixed soon upstream
https://bugzilla.kernel.org/show_bug.cgi?id=208911

https://lore.kernel.org/lkml/2020081...ul@kernel.org/

LuckyCyborg 12-23-2020 08:45 AM

Quote:

Originally Posted by ponce (Post 6198971)
that's an issue only if you have one of the two affected USB 3.0 controllers, Renesas uPD720201 and uPD720202, otherwise is just an harmless warning: you can check with
Code:

lspci | grep Renesas
BTW should be fixed soon upstream
https://bugzilla.kernel.org/show_bug.cgi?id=208911

https://lore.kernel.org/lkml/2020081...ul@kernel.org/

Yeah, are affected "only" half of the cheap USB 3.0 controllers available on the market. Because the other half luckily have a VLI chipset.

Probably a not so important issue to worth adding that 12KB file to our firmware...

BTW, they talk about fixing the accepting various versions of that firmware file. We, we have no one yet.

ponce 12-23-2020 08:58 AM

it seems that to provide/use that firmware file you are bound to accept an EULA, so I'm not sure if its inclusion is acceptable...

https://github.com/denisandroid/uPD72020x-Firmware/
https://github.com/denisandroid/uPD7...er/License.rtf

LuckyCyborg 12-23-2020 10:29 AM

Quote:

Originally Posted by ponce (Post 6198986)
it seems that to provide/use that firmware file you are bound to accept an EULA, so I'm not sure if its inclusion is acceptable...

https://github.com/denisandroid/uPD72020x-Firmware/
https://github.com/denisandroid/uPD7...er/License.rtf

Permit me to doubt that the well versed kernel devs will be crazy enough to put half of the potential users of XHCI driver and the Linux distros in an embarrassing legal situation, just for asking for a firmware blob with highly restrictive license.

Maybe this is just the file found by me and they thought about another one. Or maybe this OMG! EULA! is not that restrictive.

I for one I have no clue about the American legalese, BUT I wonder what the other Linux distributions do...

TheTKS 12-23-2020 10:44 AM

Quote:

Originally Posted by ponce (Post 6198971)
that's an issue only if you have one of the two affected USB 3.0 controllers, Renesas uPD720201 and uPD720202, otherwise is just an harmless warning: you can check with
Code:

lspci | grep Renesas

Quote:

Originally Posted by ponce (Post 6198986)
it seems that to provide/use that firmware file you are bound to accept an EULA, so I'm not sure if its inclusion is acceptable...

Thanks, turns out not a problem for me. Unfortunate for others.

As an aside, not a request for -current, I just keep experiencing and hearing of more and more USB weirdness. I thought the whole idea was that it was going to be a standard. Maybe it turned out to be less "standard" than intended, maybe it's bad implementation, but as a user, it's a bit of a mess.

TKS


All times are GMT -5. The time now is 04:12 PM.