1 |
On Thursday, 14 July 2022 07:19:14 BST gevisz wrote: |
2 |
> пт, 11 мар. 2022 г. в 20:15, gevisz <gevisz@×××××.com>: |
3 |
> > пн, 19 окт. 2020 г. в 00:15, gevisz <gevisz@×××××.com>: |
4 |
> > > вс, 18 окт. 2020 г. в 21:15, Dale <rdalek1967@×××××.com>: |
5 |
> > > > gevisz wrote: |
6 |
> > > > > вс, 18 окт. 2020 г. в 17:20, Dale <rdalek1967@×××××.com>: |
7 |
> > > > >> gevisz wrote: |
8 |
> > > > >>> No sound at least in Firefox. Tried it on youtube. Skype is |
9 |
> > > > >>> currently |
10 |
> > > > >>> uninstalled. So, I cannot check using it. |
11 |
> > > > >> |
12 |
> > > > >> Just a thought. Are you sure that everything is unmuted? Years |
13 |
> > > > >> ago, |
14 |
> > > > >> all the sound control software, Kmix, alsa and others, default to |
15 |
> > > > >> mute. |
16 |
> > > > >> If just one of them is muted, no sound. I seem to recall when I |
17 |
> > > > >> did my |
18 |
> > > > >> install on this rig that I had to unmute the sound in three places, |
19 |
> > > > >> Kmix, alsa and one other that I can't recall the name of. I think |
20 |
> > > > >> I had |
21 |
> > > > >> to turn up the volume on alsa as it was set to a really low level |
22 |
> > > > >> once |
23 |
> > > > >> it was unmuted. Usually, I turn all of them to the max except the |
24 |
> > > > >> one I |
25 |
> > > > >> mainly use. In my case, Kmix is the one I use to really control |
26 |
> > > > >> things |
27 |
> > > > >> since it sits on the panel thingy. The others are set at the max. |
28 |
> > > > >> |
29 |
> > > > >> It's a silly thing but thought it worth a mention just in case |
30 |
> > > > >> there is |
31 |
> > > > >> a muted setting somewhere. |
32 |
> > > > > |
33 |
> > > > > Thank you for your input. Yes, it seems that something is muted but |
34 |
> > > > > what? |
35 |
> > > > > I have no KDE and no kmix installed. No pulseaudio. |
36 |
> > > > |
37 |
> > > > Type in alsamixer in a console or whatever you use and hit tab twice. |
38 |
> > > > I |
39 |
> > > > suspect you have that installed. You should have a text version, like |
40 |
> > > > a |
41 |
> > > > console uses, and a gui version, that should work in any DM. Pick |
42 |
> > > > your |
43 |
> > > > poison and see if anything there is muted or the volume is set really |
44 |
> > > > low, like 1 out of 100 or something. I think hitting the "m" key |
45 |
> > > > toggles the mute. |
46 |
> > > |
47 |
> > > I am sorry to confess that I forgot that I should use M to unmute |
48 |
> > > a channel in alsamixer (as I did about 14 years ago) and thought |
49 |
> > > that arrows up and down do all the work. :( |
50 |
> > > |
51 |
> > > So, now the problem has been solved. |
52 |
> > |
53 |
> > Last time I have ended the discussion on my |
54 |
> > "no sound" problem acknowledging that I was |
55 |
> > so stupid that "forgot that I should use M to |
56 |
> > unmute a channel in alsamixer." |
57 |
> > |
58 |
> > However, it turned out that it was not the case: |
59 |
> > currently I have all channels in alsamixer unmuted |
60 |
> > and have sound only in about 1 from 10 bootings of |
61 |
> > my Gentoo system, while I do always have sound |
62 |
> > on the same computer while I boot it with Ubuntu 20.04. |
63 |
> > |
64 |
> > I have also compared the output of lsmod command |
65 |
> > on both systems and found out that my Gentoo system |
66 |
> > had all sound kernel modules that my Ubuntu system has |
67 |
> > and even more. (In Gentoo, I still have quite an old 5.4.97 |
68 |
> > kernel, but I do not think that it is the cause of my |
69 |
> > "no sound" problem.) |
70 |
> > |
71 |
> > Of course, it is completely my responsibility that |
72 |
> > I have built my Gentoo system in such a way that |
73 |
> > I never know if I will have sound after its next boot. |
74 |
> > However I am lost guessing what I did wrong. |
75 |
> > (Comparing with Ubuntu 20.04, my Gentoo system |
76 |
> > has no systemd and no pulseaudio, no consolekit, |
77 |
> > and no policykit.) |
78 |
> > |
79 |
> > I leave this just for history, as I am currently |
80 |
> > in a war zone and so investigating this problem |
81 |
> > further is not in my priority list. :( |
82 |
> |
83 |
> I have accidentally found that the problem with |
84 |
> absence of sound on my Gentoo box appears |
85 |
> only when my USB Logitech webcam is connected |
86 |
> to the computer during the boot time. |
87 |
> |
88 |
> Moreover, if it happens and the sound is absent, |
89 |
> the alsamixer shows that my USB Logitech webcam |
90 |
> is considered by the system as a default sound device. |
91 |
> |
92 |
> So, it tries to send sound there even though it does |
93 |
> not have any speaker. |
94 |
|
95 |
I'll blame some relatively recent change in the kernel or some interaction |
96 |
with udev. I have previously posted a problem regarding a USB NIC, rather |
97 |
than a USB sound card as in your case. Now I also noticed a problem with the |
98 |
initialisation of an onboard WiFi card on another laptop, which is driven by |
99 |
the internal MoBo USB controller along with bluetooth. |
100 |
|
101 |
I don't know what causes the problem but I wager the order in which a device |
102 |
is plugged in/switched on by the user affects whether the kernel will detect it |
103 |
and initialise it, or not. |
104 |
|
105 |
On this laptop the onboard WiFi has to be switched on already at boot time, or |
106 |
I need to reboot after switching it on. Restarting the wlan0 service without |
107 |
a reboot fails to connect to the AP. |
108 |
|
109 |
On the previous post of mine about another laptop with an external USB NIC |
110 |
adaptor (wired), the ethernet cable has to remain disconnected until SDDM |
111 |
starts, or SDDM will not launch. Restarting the wired interface service |
112 |
allows SDDM to start. |
113 |
|
114 |
My superficial conclusion is ... something changed and the result is a |
115 |
regressive behavior. I don't know if this is related to kernel code or udev, |
116 |
or some interaction between the two, but I suggest this is where the cause of |
117 |
this problem lies rather than USB sound or NIC devices. |