LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-27-2021, 05:15 AM   #16
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by marav View Post
otherwise, just to know
why not use an LTS kernel in this case? (5.10.x for ex.)
I am just following Patrick's policy, as he knows a lot better than me:
Code:
Mon Jun  7 18:53:49 UTC 2021
Hey folks! Sorry about the delay in getting this batch out but I had other
distractions going on here last week that prevented getting this one wrapped
up. Anyway, probably the highlight of this update set is that we've decided
to abandon the 5.10 LTS kernel in favor of following the latest one. We've
never really had a policy that required LTS in a stable release although that
is how it has been done for years, but based on comments from the Slackware
community it seems like 5.10 LTS isn't getting a lot of love and lacks
hardware support that people need now. Conversely, the reports on 5.12 have
been almost entirely positive, so we're going to provide what we think is the
best available kernel. It's unlikely that we'll see another LTS prior to
release, so the plan for maintenance is to keep following the latest kernels
as needed for security purposes. If that means we have to jump to a new branch
while supporting the stable release, we'll start the kernel out in testing
first until we've had some feedback that it's safe to move it to the patches
directory. Sooner or later we will end up on an LTS kernel again, and at that
point we'll just roll with that one. Feel free to comment (or complain) about
this plan on LQ... I'll be curious to see what people think. Anyway, enjoy!

Last edited by Didier Spaier; 07-27-2021 at 05:21 AM.
 
Old 07-27-2021, 05:33 AM   #17
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,442

Rep: Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191
Code:
Sooner or later we will end up on an LTS kernel again
It can be earlier for you ;-)
 
Old 07-27-2021, 06:57 AM   #18
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,605

Rep: Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472Reputation: 3472
Deleted. Sorry for the noise!

Last edited by LuckyCyborg; 07-27-2021 at 07:43 AM.
 
Old 07-27-2021, 07:47 AM   #19
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 2,717
Blog Entries: 1

Rep: Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625
Are you custom build kernel on 14.2? I guess yes. If not build your own. Now it is mess. Try to connect to system via network. But imo this is completely unworthy any investigation. Use 5.12.x. Why does it matter for you? You are still using 14.2. We can spend month here without any result. Just things happen. Like for me today. All wifi network stack just refused to work. I rebooted and it works now. Should I spend two weeks to figure out what happened? For time being stick to 5.12.x - 5.13.x seems also be some kind flawed. Let forget about it and move on.
 
Old 07-27-2021, 08:05 AM   #20
Franklin
Senior Member
 
Registered: Oct 2002
Distribution: Slackware
Posts: 1,348

Rep: Reputation: 217Reputation: 217Reputation: 217
5.13.5 seems to have cleared up things for me. I use the Huge kernel on -current. Can confirm 3.0 and 3.1 ports had been impacted (all I have on my rear IO). This happened only after a cold boot. I likely did not notice this on earlier kernel updates as I usually "restart" after I apply an upgrade to -current. I tested a couple times using 5.13.4 and cold boot was still leaving me with a powered mouse and keyboard, but no input was recognized until I did a hard reset. After upgrading to 5.13.5 things work fine after starting cold. I had mentioned earlier that unplugging and re-plugging the mouse and keyboard seemed to fix things, but this was either incorrect or inconsistent.
 
1 members found this post helpful.
Old 07-27-2021, 08:31 AM   #21
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
[duplicate, deleted]

Last edited by Didier Spaier; 07-27-2021 at 08:32 AM.
 
Old 07-27-2021, 08:32 AM   #22
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by igadoter View Post
Are you custom build kernel on 14.2? I guess yes. If not build your own. Now it is mess. Try to connect to system via network. But imo this is completely unworthy any investigation. Use 5.12.x. Why does it matter for you? You are still using 14.2. We can spend month here without any result. Just things happen. Like for me today. All wifi network stack just refused to work. I rebooted and it works now. Should I spend two weeks to figure out what happened? For time being stick to 5.12.x - 5.13.x seems also be some kind flawed. Let forget about it and move on.
I disagree. Getting stuck with an old kernel can be an option for you, just not my choice for Slint. Also solving this issue probably matters too for folks wanting to upgrade to Slackware 15 when released and eager to help making it as good as previous versions.

Quote:
Originally Posted by Franklin View Post
5.13.5 seems to have cleared up things for me. I use the Huge kernel on -current. Can confirm 3.0 and 3.1 ports had been impacted (all I have on my rear IO). This happened only after a cold boot. I likely did not notice this on earlier kernel updates as I usually "restart" after I apply an upgrade to -current. I tested a couple times using 5.13.4 and cold boot was still leaving me with a powered mouse and keyboard, but no input was recognized until I did a hard reset. After upgrading to 5.13.5 things work fine after starting cold. I had mentioned earlier that unplugging and re-plugging the mouse and keyboard seemed to fix things, but this was either incorrect or inconsistent.
Thanks, will upgrade Slackware64-current to 5.13.5 (both huge and generic) and if that confirms your findings will build a generic package to with 5.13.5 for Slint.

Quote:
Originally Posted by chris.willing View Post
Another data point here. In a mature machine (about 6yrs old), all the USB-2 ports work fine but none of the 3x USB-3.0 ports work with kernels 5.13.3,4. On a newer machine all the USB ports are USB-3.2 Gen 2 and all seem to be working OK (as do the USB-2 ports).

The resulting conjecture would be that older USB-3.0 ports are problematic with 5.13.x kernels.

chris
Thanks for this information, Chris. Can you confirm that 5.13.5 is better on this respect?
 
Old 07-27-2021, 09:21 AM   #23
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
Thanks, will upgrade Slackware64-current to 5.13.5 (both huge and generic) and if that confirms your findings will build a generic package to with 5.13.5 for Slint.
Here, having upgraded kernel-huge and kernel-generic to version 5.13.5 didn't help. Keyboard and mouse still don't work plugged in the same USB ports, but do in the other ones.
 
Old 07-27-2021, 09:28 AM   #24
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 2,717
Blog Entries: 1

Rep: Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625
Quote:
Originally Posted by Didier Spaier View Post
I disagree. Getting stuck with an old kernel can be an option for you, just not my choice for Slint. Also solving this issue probably matters too for folks wanting to upgrade to Slackware 15 when released and eager to help making it as good as previous versions.
Kernel 5.12.x is by no means old kernel. Today used kernel for stable releases of many distributions are 4.19.x , 5.4.x. It is planned next Debian will be shipped with 5.10.x.

It is just Slackware -current is racing horse. There is no need to follow kernel policy as it is in Slackware -current. I would say - you should expect problems running -current. Get to used it.

Almost no one here has enough knowledge about kernel usb stack to have even glimpse what's happening. Sure we can behave like say monkeys (no abuse for monkeys) by unplugging and plugging again usb keyboard, mouse. But it does not make us an inch closer to solution of problem.

I think it is better for now to stick to "old" 5.12.x which works. I am almost sure things will improve in time.
 
Old 07-27-2021, 09:32 AM   #25
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,442

Rep: Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191
Quote:
Originally Posted by igadoter View Post
Kernel 5.12.x is by no means old kernel. Today used kernel for stable releases of many distributions are 4.19.x , 5.4.x. It is planned next Debian will be shipped with 5.10.x.
because these many distributions maintain their own kernel
slackware is not in this case
 
Old 07-27-2021, 09:37 AM   #26
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by igadoter View Post
I think it is better for now to stick to "old" 5.12.x which works. I am almost sure things will improve in time.
I have indicated in post #11 that the same issue occurs with 5.12.19 (mostly recent release of this branch) furthermore this branch has been declared EOL (End of Life) as you can check here.

Last edited by Didier Spaier; 07-27-2021 at 09:38 AM.
 
Old 07-27-2021, 09:39 AM   #27
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,811

Rep: Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447
Quote:
Originally Posted by marav View Post
because these many distributions maintain their own <massively altered> kernel
slackware is not in this case
There! Refined that for ya.
 
Old 07-27-2021, 09:41 AM   #28
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,442

Rep: Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191Reputation: 4191
Quote:
Originally Posted by enorbet View Post
There! Refined that for ya.
you're welcome
 
Old 07-27-2021, 09:52 AM   #29
Franklin
Senior Member
 
Registered: Oct 2002
Distribution: Slackware
Posts: 1,348

Rep: Reputation: 217Reputation: 217Reputation: 217
Quote:
Originally Posted by Didier Spaier View Post
Here, having upgraded kernel-huge and kernel-generic to version 5.13.5 didn't help. Keyboard and mouse still don't work plugged in the same USB ports, but do in the other ones.

That's unfortunate. I went back and rested all my USB ports again using the same methods that failed for me with 5.13.4 and everything is working as expected now. These are USB 3.0 and 3.1 ports.

Last edited by Franklin; 07-27-2021 at 10:19 AM.
 
Old 07-27-2021, 10:47 AM   #30
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,383

Rep: Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762Reputation: 2762
I have been looking at commit 34ada7b357dda19b32a1c440512da5367621be20 in ChangeLog-5.13.4 , which has also been backported into the 5.12.19 kernel. (Thanks Marav!)

I am no expert, but the way I read the code,
Code:
        if (gadget_is_otg(gadget) && !otg_desc[0]) {
                struct usb_descriptor_header *usb_desc;

                usb_desc = usb_otg_descriptor_alloc(gadget);
                if (!usb_desc) {
                        status = -ENOMEM;
                        goto put;
                }
                usb_otg_descriptor_init(gadget, usb_desc);
                otg_desc[0] = usb_desc;
                otg_desc[1] = NULL;
        }

        /* register our configuration */
        status = usb_add_config(cdev, &config_driver, do_config);
        if (status < 0)
                goto free_otg_desc;

        usb_composite_overwrite_options(cdev, &coverwrite);
        dev_info(&gadget->dev, DRIVER_DESC ", version: " DRIVER_VERSION "\n");

        return 0;

free_otg_desc:
        kfree(otg_desc[0]);
        otg_desc[0] = NULL;
put:
        list_for_each_entry(m, &hidg_func_list, node) {
                if (m == n)
                        break;
                usb_put_function_instance(m->fi);
        }
        return status;
}
if the test is passed, then it is possible to skip over the usb configuration if USB On-The-Go capability is detected.
The gadget_is_otg() is defined in /include/linux/usb/gadget.h
Code:
/**
 * gadget_is_otg - return true iff the hardware is OTG-ready
 * @g: controller that might have a Mini-AB connector
 *
 * This is a runtime test, since kernels with a USB-OTG stack sometimes
 * run on boards which only have a Mini-B (or Mini-A) connector.
 */
static inline int gadget_is_otg(struct usb_gadget *g)
{
#ifdef CONFIG_USB_OTG
        return g->is_otg;
#else
        return 0;
#endif
}
In the Slackware64 kernel 5.13.4 and 5.13.5 there is
Quote:
bash-5.1$ grep CONFIG_USB_OTG /usr/src/linux/.config
CONFIG_USB_OTG=y
# CONFIG_USB_OTG_PRODUCTLIST is not set
# CONFIG_USB_OTG_DISABLE_EXTERNAL_HUB is not set
# CONFIG_USB_OTG_FSM is not set
I do not have hardware to test this, but my suggestion is to either try reversing that commit or perhaps disabling the .config setting.

Last edited by allend; 07-27-2021 at 10:49 AM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] RedHat USB keyboard/mouse not detected w/ usbserial error message penyuan Linux - Software 7 06-26-2017 08:20 PM
Mouse not working on Damn Small Linux | Mouse: Omega Optical Mouse (16c Gaming Mouse) AndyDeveloper Linux - Hardware 3 04-09-2017 01:32 PM
hp wireless keyboard & mouse, keyboard works, mouse do not work not working john hughes Linux - Desktop 2 04-04-2016 11:00 AM
Keyboard and mouse not detected after starting X Infinity8 Slackware 26 09-09-2012 01:04 AM
usb mouse NOT detected, but usb keyboard IS detected mr.anderson Slackware 16 04-26-2006 09:09 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:49 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration