Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #181681 > unrolled thread
| Started by | David <David@example.net> |
|---|---|
| First post | 2025-01-23 22:48 +0000 |
| Last post | 2025-02-08 17:17 +0000 |
| Articles | 20 on this page of 43 — 8 participants |
Back to article view | Back to alt.comp.os.windows-10
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-01-23 22:48 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Mike Easter <MikeE@ster.invalid> - 2025-01-23 16:41 -0800
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Paul <nospam@needed.invalid> - 2025-01-24 02:40 -0500
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-01-24 08:55 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Mike Easter <MikeE@ster.invalid> - 2025-01-24 09:09 -0800
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-01-24 20:17 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) % <pursent100@gmail.com> - 2025-01-24 13:24 -0700
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Mike Easter <MikeE@ster.invalid> - 2025-01-24 14:31 -0800
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-01-24 23:55 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-01-26 08:46 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Paul <nospam@needed.invalid> - 2025-01-24 14:45 -0500
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-01-26 19:43 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Mike Easter <MikeE@ster.invalid> - 2025-01-26 12:14 -0800
Re: Window 10 - No Sound (was - Mint 22 - No Sound) wasbit <wasbit@nowhere.com> - 2025-01-27 09:50 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-01-27 10:43 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-06 08:59 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Paul <nospam@needed.invalid> - 2025-02-06 06:32 -0500
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-06 14:55 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-06 20:33 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) % <pursent100@gmail.com> - 2025-02-06 13:55 -0700
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Paul <nospam@needed.invalid> - 2025-02-06 16:16 -0500
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-06 22:36 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Java Jive <java@evij.com.invalid> - 2025-02-06 23:31 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-07 16:03 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Java Jive <java@evij.com.invalid> - 2025-02-07 17:04 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Java Jive <java@evij.com.invalid> - 2025-02-07 17:39 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Java Jive <java@evij.com.invalid> - 2025-02-07 17:53 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-07 20:18 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-07 20:03 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Java Jive <java@evij.com.invalid> - 2025-02-07 22:03 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-07 23:04 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Java Jive <java@evij.com.invalid> - 2025-02-08 01:16 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Paul <nospam@needed.invalid> - 2025-02-07 21:49 -0500
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-08 09:26 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Frank Slootweg <this@ddress.is.invalid> - 2025-02-08 15:22 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Char Jackson <none@none.invalid> - 2025-02-08 12:08 -0600
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Frank Slootweg <this@ddress.is.invalid> - 2025-02-07 18:42 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Paul <nospam@needed.invalid> - 2025-02-07 14:18 -0500
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-07 19:52 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) Paul <nospam@needed.invalid> - 2025-02-07 16:31 -0500
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-08 17:47 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) wasbit <wasbit@nowhere.com> - 2025-02-08 09:48 +0000
Re: Window 10 - No Sound (was - Mint 22 - No Sound) David <David@example.net> - 2025-02-08 17:17 +0000
Page 1 of 3 [1] 2 3 Next page →
| From | David <David@example.net> |
|---|---|
| Date | 2025-01-23 22:48 +0000 |
| Subject | Re: Window 10 - No Sound (was - Mint 22 - No Sound) |
| Message-ID | <lvfv97F421U4@mid.individual.net> |
On 23/01/2025 22:43, David wrote: > On 23/01/2025 22:14, Mike Easter wrote: >> BDB wrote: >>> You may be pleased to learn that I am now on the latest version of >>> Windows 10! > > On my Dell laptop Service Tag - 4WX4YB2 > >>> 22H2 General Availability Channel 2022-10-18 2025-01-14 >>> 19045.5371 2025-10-14 >>> >>> My BIOS setting is now 1.23.1 >>> >>> *I still have no sound*. >>> >>> What would you like me to try now? >> >> My recollection is that you had sound w/ both the MS W10 and the >> Hiren's W11 PE. >> >> I would recommend that you boot the live W11 PE that you have. At one >> time you had a current Ventoy stick. All you would have to do would >> be to copy the Hiren's .iso to that Ventoy and boot it. Then we would >> have sound via Win implementation. > > I've gone past that stage! > >> If you have 'destroyed' your Ventoy stick and you have also forgotten >> how to make it w/ linux browser GUI, say so and maybe we can figure >> out a simple route to see the device manager of a Win w/ working >> speakers. > > Your memory is slipping! This Dell laptop has /never/ had any sound as > far as I can recall. > > I thought you'd wanted to use the CLI to find information for you to > consider. > > (Windows 10 Usenet group added.) Reposted
[toc] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2025-01-23 16:41 -0800 |
| Message-ID | <lvg5taF1j39U1@mid.individual.net> |
| In reply to | #181681 |
David wrote: > David wrote: >> Mike Easter wrote: >>> BDB wrote: >>>> You may be pleased to learn that I am now on the latest version of >>>> Windows 10! >> >> On my Dell laptop Service Tag - 4WX4YB2 >> >>>> 22H2 General Availability Channel 2022-10-18 2025-01-14 >>>> 19045.5371 2025-10-14 >>>> >>>> My BIOS setting is now 1.23.1 >>>> >>>> *I still have no sound*. >>>> >>>> What would you like me to try now? >>> >>> My recollection is that you had sound w/ both the MS W10 and the >>> Hiren's W11 PE. >>> >>> I would recommend that you boot the live W11 PE that you have. At >>> one time you had a current Ventoy stick. All you would have to do >>> would be to copy the Hiren's .iso to that Ventoy and boot it. Then >>> we would have sound via Win implementation. >> >> I've gone past that stage! >> >>> If you have 'destroyed' your Ventoy stick and you have also forgotten >>> how to make it w/ linux browser GUI, say so and maybe we can figure >>> out a simple route to see the device manager of a Win w/ working >>> speakers. >> >> Your memory is slipping! This Dell laptop has /never/ had any sound as >> far as I can recall. >> My recollection and confirmation by this HK message: http://al.howardknight.net/?ID=173767883500 From: David Newsgroups: alt.os.linux.mint Subject: Re: Ping: Paul Date: Tue, 7 Jan 2025 20:43:20 +0000 Message-ID: <lu5hv8F3nfcU4@mid.individual.net> You said that while running Hiren's W11 PE that you used its sound test function which says such as Right speaker and Left speaker (as I recall) that you heard sound from both (each individually) speakers: > Thanks. I've done that - I hear a sound from both left and right speakers. I haven't put my fingers on the msg in which you stated that you also had appropriate sound from the W10 install which was done from a MS W10 .iso Not just a click as heard on various linux installs and live boots. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-01-24 02:40 -0500 |
| Message-ID | <vmvg5r$24kse$1@dont-email.me> |
| In reply to | #181681 |
On Thu, 1/23/2025 5:48 PM, David wrote: > On 23/01/2025 22:43, David wrote: >> On 23/01/2025 22:14, Mike Easter wrote: >>> BDB wrote: >>>> You may be pleased to learn that I am now on the latest version of Windows 10! >> >> On my Dell laptop Service Tag - 4WX4YB2 >> >>>> 22H2 General Availability Channel 2022-10-18 2025-01-14 19045.5371 2025-10-14 >>>> >>>> My BIOS setting is now 1.23.1 >>>> >>>> *I still have no sound*. >>>> >>>> What would you like me to try now? >>> >>> My recollection is that you had sound w/ both the MS W10 and the Hiren's W11 PE. >>> >>> I would recommend that you boot the live W11 PE that you have. At one time you had a current Ventoy stick. All you would have to do would be to copy the Hiren's .iso to that Ventoy and boot it. Then we would have sound via Win implementation. >> >> I've gone past that stage! >> >>> If you have 'destroyed' your Ventoy stick and you have also forgotten how to make it w/ linux browser GUI, say so and maybe we can figure out a simple route to see the device manager of a Win w/ working speakers. >> >> Your memory is slipping! This Dell laptop has /never/ had any sound as far as I can recall. >> >> I thought you'd wanted to use the CLI to find information for you to consider. >> >> (Windows 10 Usenet group added.) > > Reposted > You have the Windows driver. But Windows has ways of rejecting those, so I don't know if a current Windows 10 will accept that driver in the normal way. Name: Realtek-High-Definition-Audio-Driver_D7VCY_WIN_6.0.1.8224_A08_02.EXE Size: 318,464,720 bytes (303 MiB) SHA256: 04A92B91607ECE504A72A5E9C22DC65A1BC2170B7D887EA980FBAF22D237D585 On the Linux side, it is suggested to do the following if the driver is blacklisted and some other driver was tried in its place. You can quickfix this with a "sudo modprobe snd_hda_intel" and a "sudo alsactl force-reload' but you still need to remove the blacklisted module in /etc/modprobe.d (which file varies) – osirisgothra Commented Aug 13, 2023 at 21:15 In addition, apparently some of the behaviors are related to Linux power saving. These would only be of interest, if the previous paragraph was resolved successfully. sudo tee /etc/modprobe.d/snd-hda-intel.conf <<<'options snd-hda-intel power_save=0' # headphones sudo hda-verb /dev/snd/hwC0D0 0x02 SET_POWER 0x0 # speakers Equipment ID: Realtek ALC3253 on Dell Inspiron 13" 5368 (Speaker Amp Type unknown -- could be 2W analog, not 5W digital) Dell Inspiron 13-5368 2-In-1 (P69G001) Paul
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-01-24 08:55 +0000 |
| Message-ID | <lvh2saF5nvuU1@mid.individual.net> |
| In reply to | #181693 |
On 24/01/2025 07:40, Paul wrote: > On Thu, 1/23/2025 5:48 PM, David wrote: >> On 23/01/2025 22:43, David wrote: >>> On 23/01/2025 22:14, Mike Easter wrote: >>>> BDB wrote: >>>>> You may be pleased to learn that I am now on the latest version of Windows 10! >>> >>> On my Dell laptop Service Tag - 4WX4YB2 >>> >>>>> 22H2 General Availability Channel 2022-10-18 2025-01-14 19045.5371 2025-10-14 >>>>> >>>>> My BIOS setting is now 1.23.1 >>>>> >>>>> *I still have no sound*. >>>>> >>>>> What would you like me to try now? >>>> >>>> My recollection is that you had sound w/ both the MS W10 and the Hiren's W11 PE. >>>> >>>> I would recommend that you boot the live W11 PE that you have. At one time you had a current Ventoy stick. All you would have to do would be to copy the Hiren's .iso to that Ventoy and boot it. Then we would have sound via Win implementation. >>> >>> I've gone past that stage! >>> >>>> If you have 'destroyed' your Ventoy stick and you have also forgotten how to make it w/ linux browser GUI, say so and maybe we can figure out a simple route to see the device manager of a Win w/ working speakers. >>> >>> Your memory is slipping! This Dell laptop has /never/ had any sound as far as I can recall. >>> >>> I thought you'd wanted to use the CLI to find information for you to consider. >>> >>> (Windows 10 Usenet group added.) >> >> Reposted >> > > You have the Windows driver. But Windows has ways of rejecting those, > so I don't know if a current Windows 10 will accept that driver > in the normal way. > > Name: Realtek-High-Definition-Audio-Driver_D7VCY_WIN_6.0.1.8224_A08_02.EXE > Size: 318,464,720 bytes (303 MiB) > SHA256: 04A92B91607ECE504A72A5E9C22DC65A1BC2170B7D887EA980FBAF22D237D585 > > On the Linux side, it is suggested to do the following if the > driver is blacklisted and some other driver was tried in its place. > > You can quickfix this with a "sudo modprobe snd_hda_intel" > and a "sudo alsactl force-reload' but you still need to > remove the blacklisted module in /etc/modprobe.d (which file varies) – > osirisgothra > Commented Aug 13, 2023 at 21:15 > > In addition, apparently some of the behaviors are related to Linux power saving. > These would only be of interest, if the previous paragraph was resolved successfully. > > sudo tee /etc/modprobe.d/snd-hda-intel.conf <<<'options snd-hda-intel power_save=0' # headphones > > sudo hda-verb /dev/snd/hwC0D0 0x02 SET_POWER 0x0 # speakers > > Equipment ID: > > Realtek ALC3253 on Dell Inspiron 13" 5368 (Speaker Amp Type unknown -- could be 2W analog, not 5W digital) > Dell Inspiron 13-5368 2-In-1 (P69G001) All very interesting, Paul, BUT ..... What, exactly, do you recommend that I physically *DO*, now, to determine if it is possible to play music or hear speech on this device? Thanks. -- David
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2025-01-24 09:09 -0800 |
| Message-ID | <lvhvqiFae1cU1@mid.individual.net> |
| In reply to | #181694 |
BDB wrote: > What, exactly, do you recommend that I physically *DO*, now, to > determine if it is possible to play music or hear speech on this device? Will you confirm or deny that both Hiren's W11 PE and the install of the MS W10 .iso were successful in playing sound? That has been my impression since Jan 7. Since then, my next intention was to use the information from the Win device manager to provide information in an Win environment w/ working audio from the case speakers to interpret in the manner I'm accustomed to doing in linux from the chip ID number in the format xxxx:yyyy. I was able to use that type information in the W10 Lenovo laptop I have which has two audio devices, which worked properly in Win, the HDMI one of which did NOT play in linux until I remedied the problem with a boot parameter when booting linux. This story has been very broken by your struggles w/ providing a consistent picture with a consistent setup in a consistent thread in a consistent newsgroup. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-01-24 20:17 +0000 |
| Message-ID | <lviar7FbveaU1@mid.individual.net> |
| In reply to | #181700 |
On 24/01/2025 17:09, Mike Easter wrote: > BDB wrote: >> What, exactly, do you recommend that I physically *DO*, now, to >> determine if it is possible to play music or hear speech on this device? > > Will you confirm or deny that both Hiren's W11 PE and the install of the > MS W10 .iso were successful in playing sound? That has been my > impression since Jan 7. At no time have I ever heard music or speech from the laptop speakers. I HAVE heard a 'click' sound - indicating (to me) that each speaker (L & R) can receive a signal. > Since then, my next intention was to use the information from the Win > device manager to provide information in an Win environment w/ working > audio from the case speakers to interpret in the manner I'm accustomed > to doing in linux from the chip ID number in the format xxxx:yyyy. My Device Manager shows 1. Intel(R) Display Audio and 2. Realtek Audio > I was able to use that type information in the W10 Lenovo laptop I have > which has two audio devices, which worked properly in Win, the HDMI one > of which did NOT play in linux until I remedied the problem with a boot > parameter when booting linux. I'm aware that you are a Linux buff. > This story has been very broken by your struggles w/ providing a > consistent picture with a consistent setup in a consistent thread in a > consistent newsgroup. You are correct, as usual.
[toc] | [prev] | [next] | [standalone]
| From | % <pursent100@gmail.com> |
|---|---|
| Date | 2025-01-24 13:24 -0700 |
| Message-ID | <p0idnWdENYaIag76nZ2dnZfqn_ednZ2d@giganews.com> |
| In reply to | #181705 |
David wrote: > On 24/01/2025 17:09, Mike Easter wrote: >> BDB wrote: >>> What, exactly, do you recommend that I physically *DO*, now, to >>> determine if it is possible to play music or hear speech on this device? >> >> Will you confirm or deny that both Hiren's W11 PE and the install of >> the MS W10 .iso were successful in playing sound? That has been my >> impression since Jan 7. > > At no time have I ever heard music or speech from the laptop speakers. > > I HAVE heard a 'click' sound - indicating (to me) that each speaker (L & > R) can receive a signal. > >> Since then, my next intention was to use the information from the Win >> device manager to provide information in an Win environment w/ working >> audio from the case speakers to interpret in the manner I'm accustomed >> to doing in linux from the chip ID number in the format xxxx:yyyy. > > My Device Manager shows 1. Intel(R) Display Audio and 2. Realtek Audio > >> I was able to use that type information in the W10 Lenovo laptop I >> have which has two audio devices, which worked properly in Win, the >> HDMI one of which did NOT play in linux until I remedied the problem >> with a boot parameter when booting linux. > > I'm aware that you are a Linux buff. > >> This story has been very broken by your struggles w/ providing a >> consistent picture with a consistent setup in a consistent thread in a >> consistent newsgroup. > > You are correct, as usual. > mine plays frank zappa guitar leads when it's not even on
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2025-01-24 14:31 -0800 |
| Message-ID | <lviiluFdbq2U1@mid.individual.net> |
| In reply to | #181705 |
David wrote: > At no time have I ever heard music or speech from the laptop speakers. On the basis of my experience w/ my Lenovo laptop which also had HDMI case speakers which did not play w/ linux until I boot parameter 'radeon-ized' it, at which time linux did play thru' the case speakers... ... but at /all/ times, both default Win (which played thru' the case) and default linux (which did NOT play thru' the case) but DID play thru' the headset... ... the 'gain' of functional case speakers, in terms of sound quality, wasn't worth the trouble. For a very long time, I did not even /know/ the case speakers didn't work on that device because of how I use it and do NOT normally listen to sound on it. Once I started listening to sound in the process of troubleshooting what worked and what did not work, I discovered that... ... the case speakers aren't *WORTH* listening to. Even the world's cheapest ear phones sound was superior to that of the case speakers. My advice to you regarding this particular device, considering your other device options: - forget about getting the sound to come from those case speakers - if you are going to listen to sound, listen via the headset plug only or not at all -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-01-24 23:55 +0000 |
| Message-ID | <lvinjtFe01iU1@mid.individual.net> |
| In reply to | #181707 |
On 24/01/2025 22:31, Mike Easter wrote: > David wrote: >> At no time have I ever heard music or speech from the laptop speakers. > > On the basis of my experience w/ my Lenovo laptop which also had HDMI > case speakers which did not play w/ linux until I boot parameter > 'radeon-ized' it, at which time linux did play thru' the case speakers... > > ... but at /all/ times, both default Win (which played thru' the case) > and default linux (which did NOT play thru' the case) but DID play thru' > the headset... > > ... the 'gain' of functional case speakers, in terms of sound quality, > wasn't worth the trouble. > > For a very long time, I did not even /know/ the case speakers didn't > work on that device because of how I use it and do NOT normally listen > to sound on it. Once I started listening to sound in the process of > troubleshooting what worked and what did not work, I discovered that... > > ... the case speakers aren't *WORTH* listening to. Even the world's > cheapest ear phones sound was superior to that of the case speakers. > > My advice to you regarding this particular device, considering your > other device options: > > - forget about getting the sound to come from those case speakers > - if you are going to listen to sound, listen via the headset plug > only or not at all Thank you for your words of wisdom, Mike. 🙂 I've more or less come to the same conclusion, although I did reach out for alternative help here:- https://answers.microsoft.com/en-us/windows/forum/all/how-can-i-regain-sound-from-the-speakers-on-my/6a7dfbdf-98e7-4be7-b9e0-ca878c633132?page=1 There must BE a solution ....... but it's still just a game to me! -- Kind regards, David
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-01-26 08:46 +0000 |
| Message-ID | <lvmb2bFl22U2@mid.individual.net> |
| In reply to | #181708 |
On 24/01/2025 23:55, David wrote: > On 24/01/2025 22:31, Mike Easter wrote: >> David wrote: >>> At no time have I ever heard music or speech from the laptop speakers. >> >> On the basis of my experience w/ my Lenovo laptop which also had HDMI >> case speakers which did not play w/ linux until I boot parameter >> 'radeon-ized' it, at which time linux did play thru' the case speakers... >> >> ... but at /all/ times, both default Win (which played thru' the case) >> and default linux (which did NOT play thru' the case) but DID play >> thru' the headset... >> >> ... the 'gain' of functional case speakers, in terms of sound quality, >> wasn't worth the trouble. >> >> For a very long time, I did not even /know/ the case speakers didn't >> work on that device because of how I use it and do NOT normally listen >> to sound on it. Once I started listening to sound in the process of >> troubleshooting what worked and what did not work, I discovered that... >> >> ... the case speakers aren't *WORTH* listening to. Even the world's >> cheapest ear phones sound was superior to that of the case speakers. >> >> My advice to you regarding this particular device, considering your >> other device options: >> >> - forget about getting the sound to come from those case speakers >> - if you are going to listen to sound, listen via the headset plug >> only or not at all > > Thank you for your words of wisdom, Mike. 🙂 > > I've more or less come to the same conclusion, although I did reach out > for alternative help here:- > > https://answers.microsoft.com/en-us/windows/forum/all/how-can-i-regain- > sound-from-the-speakers-on-my/6a7dfbdf-98e7-4be7-b9e0-ca878c633132?page=1 > > There must BE a solution ....... but it's still just a game to me! Maybe I'll review here again - later! https://www.dell.com/support/product-details/en-uk/servicetag/0-NHlCWElhR1RjMFFkOVRpS1duc1NkUT090/overview -- David
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-01-24 14:45 -0500 |
| Message-ID | <vn0qlb$2cjo8$1@dont-email.me> |
| In reply to | #181694 |
On Fri, 1/24/2025 3:55 AM, David wrote:
> On 24/01/2025 07:40, Paul wrote:
>> On Thu, 1/23/2025 5:48 PM, David wrote:
>>> On 23/01/2025 22:43, David wrote:
>>>> On 23/01/2025 22:14, Mike Easter wrote:
>>>>> BDB wrote:
>>>>>> You may be pleased to learn that I am now on the latest version of Windows 10!
>>>>
>>>> On my Dell laptop Service Tag - 4WX4YB2
>>>>
>>>>>> 22H2 General Availability Channel 2022-10-18 2025-01-14 19045.5371 2025-10-14
>>>>>>
>>>>>> My BIOS setting is now 1.23.1
>>>>>>
>>>>>> *I still have no sound*.
>>>>>>
>>>>>> What would you like me to try now?
>>>>>
>>>>> My recollection is that you had sound w/ both the MS W10 and the Hiren's W11 PE.
>>>>>
>>>>> I would recommend that you boot the live W11 PE that you have. At one time you had a current Ventoy stick. All you would have to do would be to copy the Hiren's .iso to that Ventoy and boot it. Then we would have sound via Win implementation.
>>>>
>>>> I've gone past that stage!
>>>>
>>>>> If you have 'destroyed' your Ventoy stick and you have also forgotten how to make it w/ linux browser GUI, say so and maybe we can figure out a simple route to see the device manager of a Win w/ working speakers.
>>>>
>>>> Your memory is slipping! This Dell laptop has /never/ had any sound as far as I can recall.
>>>>
>>>> I thought you'd wanted to use the CLI to find information for you to consider.
>>>>
>>>> (Windows 10 Usenet group added.)
>>>
>>> Reposted
>>>
>>
>> You have the Windows driver. But Windows has ways of rejecting those,
>> so I don't know if a current Windows 10 will accept that driver
>> in the normal way.
>>
>> Name: Realtek-High-Definition-Audio-Driver_D7VCY_WIN_6.0.1.8224_A08_02.EXE
>> Size: 318,464,720 bytes (303 MiB)
>> SHA256: 04A92B91607ECE504A72A5E9C22DC65A1BC2170B7D887EA980FBAF22D237D585
>>
>> On the Linux side, it is suggested to do the following if the
>> driver is blacklisted and some other driver was tried in its place.
>>
>> You can quickfix this with a "sudo modprobe snd_hda_intel"
>> and a "sudo alsactl force-reload' but you still need to
>> remove the blacklisted module in /etc/modprobe.d (which file varies) –
>> osirisgothra
>> Commented Aug 13, 2023 at 21:15
>>
>> In addition, apparently some of the behaviors are related to Linux power saving.
>> These would only be of interest, if the previous paragraph was resolved successfully.
>>
>> sudo tee /etc/modprobe.d/snd-hda-intel.conf <<<'options snd-hda-intel power_save=0' # headphones
>>
>> sudo hda-verb /dev/snd/hwC0D0 0x02 SET_POWER 0x0 # speakers
>>
>> Equipment ID:
>>
>> Realtek ALC3253 on Dell Inspiron 13" 5368 (Speaker Amp Type unknown -- could be 2W analog, not 5W digital)
>> Dell Inspiron 13-5368 2-In-1 (P69G001)
>
>
>
> All very interesting, Paul, BUT .....
>
> What, exactly, do you recommend that I physically *DO*, now, to
> determine if it is possible to play music or hear speech on this device?
>
> Thanks.
>
On Windows 10, you can check Device Manager (right-click start, it should be in there).
But that's a bit of a bore.
Look for the speaker icon in the task bar.
Apparently, all outputs can be listed, but only
the devices which are currently hooked up and
ready to use, can be set as "Default Device".
If two devices are both ready (like my HDMI monitor
and my analog speakers), then I have two devices I
can alternate between.
*******
The difference on Linux Mint, is on the video card,
only the output which is running can be used for
an output. In the picture, only one of four video
card outputs is connected at present, so only
one LCD-monitor-related outputs can have sound on it.
On a laptop, when just the (lvds) LCDpanel is being used,
there is no reason for any iGPU entry to be present
in the sound output selection.
The Realtek outputs are all listed, but the speakers
are plugged into LineOut at the moment. While Analog
Devices Soundmax has actual impedance measurement, and
some motherboards have side-contect HDAudio jacks to detect
that a plug is present, some motherboards do not know
that a plug is inserted. The RealTek does not typically
have impedance measurement capability (protected by a patent).
[Picture]
https://i.postimg.cc/dt02vvv6/speaker-selection.gif
Paul
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-01-26 19:43 +0000 |
| Message-ID | <lvnhiaF720jU2@mid.individual.net> |
| In reply to | #181703 |
On 24/01/2025 19:45, Paul wrote: > On Fri, 1/24/2025 3:55 AM, David wrote: >> On 24/01/2025 07:40, Paul wrote: >>> On Thu, 1/23/2025 5:48 PM, David wrote: >>>> On 23/01/2025 22:43, David wrote: >>>>> On 23/01/2025 22:14, Mike Easter wrote: >>>>>> BDB wrote: >>>>>>> You may be pleased to learn that I am now on the latest version of Windows 10! >>>>> >>>>> On my Dell laptop Service Tag - 4WX4YB2 >>>>> >>>>>>> 22H2 General Availability Channel 2022-10-18 2025-01-14 19045.5371 2025-10-14 >>>>>>> >>>>>>> My BIOS setting is now 1.23.1 >>>>>>> >>>>>>> *I still have no sound*. >>>>>>> >>>>>>> What would you like me to try now? >>>>>> >>>>>> My recollection is that you had sound w/ both the MS W10 and the Hiren's W11 PE. >>>>>> >>>>>> I would recommend that you boot the live W11 PE that you have. At one time you had a current Ventoy stick. All you would have to do would be to copy the Hiren's .iso to that Ventoy and boot it. Then we would have sound via Win implementation. >>>>> >>>>> I've gone past that stage! >>>>> >>>>>> If you have 'destroyed' your Ventoy stick and you have also forgotten how to make it w/ linux browser GUI, say so and maybe we can figure out a simple route to see the device manager of a Win w/ working speakers. >>>>> >>>>> Your memory is slipping! This Dell laptop has /never/ had any sound as far as I can recall. >>>>> >>>>> I thought you'd wanted to use the CLI to find information for you to consider. >>>>> >>>>> (Windows 10 Usenet group added.) >>>> >>>> Reposted >>>> >>> >>> You have the Windows driver. But Windows has ways of rejecting those, >>> so I don't know if a current Windows 10 will accept that driver >>> in the normal way. >>> >>> Name: Realtek-High-Definition-Audio-Driver_D7VCY_WIN_6.0.1.8224_A08_02.EXE >>> Size: 318,464,720 bytes (303 MiB) >>> SHA256: 04A92B91607ECE504A72A5E9C22DC65A1BC2170B7D887EA980FBAF22D237D585 >>> >>> On the Linux side, it is suggested to do the following if the >>> driver is blacklisted and some other driver was tried in its place. >>> >>> You can quickfix this with a "sudo modprobe snd_hda_intel" >>> and a "sudo alsactl force-reload' but you still need to >>> remove the blacklisted module in /etc/modprobe.d (which file varies) – >>> osirisgothra >>> Commented Aug 13, 2023 at 21:15 >>> >>> In addition, apparently some of the behaviors are related to Linux power saving. >>> These would only be of interest, if the previous paragraph was resolved successfully. >>> >>> sudo tee /etc/modprobe.d/snd-hda-intel.conf <<<'options snd-hda-intel power_save=0' # headphones >>> >>> sudo hda-verb /dev/snd/hwC0D0 0x02 SET_POWER 0x0 # speakers >>> >>> Equipment ID: >>> >>> Realtek ALC3253 on Dell Inspiron 13" 5368 (Speaker Amp Type unknown -- could be 2W analog, not 5W digital) >>> Dell Inspiron 13-5368 2-In-1 (P69G001) >> >> >> >> All very interesting, Paul, BUT ..... >> >> What, exactly, do you recommend that I physically *DO*, now, to >> determine if it is possible to play music or hear speech on this device? >> >> Thanks. >> > > On Windows 10, you can check Device Manager (right-click start, it should be in there). > But that's a bit of a bore. > > Look for the speaker icon in the task bar. > > Apparently, all outputs can be listed, but only > the devices which are currently hooked up and > ready to use, can be set as "Default Device". > > If two devices are both ready (like my HDMI monitor > and my analog speakers), then I have two devices I > can alternate between. > > ******* > > The difference on Linux Mint, is on the video card, > only the output which is running can be used for > an output. In the picture, only one of four video > card outputs is connected at present, so only > one LCD-monitor-related outputs can have sound on it. > > On a laptop, when just the (lvds) LCDpanel is being used, > there is no reason for any iGPU entry to be present > in the sound output selection. > > The Realtek outputs are all listed, but the speakers > are plugged into LineOut at the moment. While Analog > Devices Soundmax has actual impedance measurement, and > some motherboards have side-contect HDAudio jacks to detect > that a plug is present, some motherboards do not know > that a plug is inserted. The RealTek does not typically > have impedance measurement capability (protected by a patent). > > [Picture] > > https://i.postimg.cc/dt02vvv6/speaker-selection.gif > > Paul Hi Paul I followed the guidance from "David" on Microsoft Answers and made a new bootable flash drive then once again installed Windows 10 on my old Dell laptop. Sadly, still no sound! On the Dell website, though, this time, I was able to carry out a hardware scan. Here's a screenshot of the failures indicated:- https://i.ibb.co/XjYDWtv/IMG-3158.jpg Any comment beyond time to recycle it?!! -- David
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2025-01-26 12:14 -0800 |
| Message-ID | <lvnjd9F7f4qU1@mid.individual.net> |
| In reply to | #181752 |
David wrote: > On the Dell website, though, this time, I was able to carry out a > hardware scan. Here's a screenshot of the failures indicated:- > https://i.ibb.co/XjYDWtv/IMG-3158.jpg > > Any comment beyond time to recycle it?!! The screenshot doesn't like the PCI bus situation. In my world, if something is working, it is working, aside from the possibility of something NOT working or not working right, whether or not it is practical to 'fix'. To me, except for the case speaker sound, the laptop is working. To me, personally, I would rather be running a linux on it than W10; or perhaps I would rather be running a dual boot W10 and a modern/current linux whose end of update life isn't near. I would keep the W10 install, add a linux distro of your choice install as an alternate boot trying not to mess up your W10 install again. Personally, I don't need the sound except occasionally; on the occasion which I needed sound, I would use the headset plug for Win or linux. This is cross-posted excessively. Just because some topic of your interest may deserve posting in some choice of groups doesn't mean that it should be posted to all of the groups that it possibly pertains. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | wasbit <wasbit@nowhere.com> |
|---|---|
| Date | 2025-01-27 09:50 +0000 |
| Message-ID | <vn7ktq$ofj8$1@dont-email.me> |
| In reply to | #181752 |
On 26/01/2025 19:43, David wrote: > snip < > > I followed the guidance from "David" on Microsoft Answers and made a new > bootable flash drive then once again installed Windows 10 on my old Dell > laptop. Sadly, still no sound! > > On the Dell website, though, this time, I was able to carry out a > hardware scan. Here's a screenshot of the failures indicated:- > https://i.ibb.co/XjYDWtv/IMG-3158.jpg > > Any comment beyond time to recycle it?!! > You are missing motherboard chip set drivers. -- Regards wasbit
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-01-27 10:43 +0000 |
| Message-ID | <lvp6aqFeto7U1@mid.individual.net> |
| In reply to | #181760 |
On 27/01/2025 09:50, wasbit wrote: > On 26/01/2025 19:43, David wrote: >> snip < >> >> I followed the guidance from "David" on Microsoft Answers and made a >> new bootable flash drive then once again installed Windows 10 on my >> old Dell laptop. Sadly, still no sound! >> >> On the Dell website, though, this time, I was able to carry out a >> hardware scan. Here's a screenshot of the failures indicated:- >> https://i.ibb.co/XjYDWtv/IMG-3158.jpg >> >> Any comment beyond time to recycle it?!! >> > > You are missing motherboard chip set drivers. Wow! Thanks. I've now gone back to Dell's support website and am installing drivers. Fingers crossed! :-)
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-02-06 08:59 +0000 |
| Message-ID | <m0jbvlFmj94U2@mid.individual.net> |
| In reply to | #181760 |
On 27/01/2025 09:50, wasbit wrote: > On 26/01/2025 19:43, David wrote: >> snip < >> >> I followed the guidance from "David" on Microsoft Answers and made a >> new bootable flash drive then once again installed Windows 10 on my >> old Dell laptop. Sadly, still no sound! >> >> On the Dell website, though, this time, I was able to carry out a >> hardware scan. Here's a screenshot of the failures indicated:- >> https://i.ibb.co/XjYDWtv/IMG-3158.jpg >> >> Any comment beyond time to recycle it?!! >> > > You are missing motherboard chip set drivers. How would YOU correct that situation? -- David Dell visit didn't help!
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-02-06 06:32 -0500 |
| Message-ID | <vo26ks$2u9h4$1@dont-email.me> |
| In reply to | #182026 |
On Thu, 2/6/2025 3:59 AM, David wrote:
> On 27/01/2025 09:50, wasbit wrote:
>> On 26/01/2025 19:43, David wrote:
>>> snip <
>>>
>>> I followed the guidance from "David" on Microsoft Answers and made a new bootable flash drive then once again installed Windows 10 on my old Dell laptop. Sadly, still no sound!
>>>
>>> On the Dell website, though, this time, I was able to carry out a hardware scan. Here's a screenshot of the failures indicated:-
>>> https://i.ibb.co/XjYDWtv/IMG-3158.jpg
>>>
>>> Any comment beyond time to recycle it?!!
>>>
>>
>> You are missing motherboard chip set drivers.
>
> How would YOU correct that situation?
>
This is a chipset driver, but the SunRise Point does not have an HDAudio entry,
and in any case, these are cosmetic drivers for putting a text string in
Device Manager to label system devices. I used this one to fix my Patsburg
entries (X79) so they displayed properly. If your Device Manager "System" area
is all labeled, and no yellow codes showing, then chances are nothing in there
needs assistance.
https://web.archive.org/web/20220120160547/https://www.intel.com/content/www/us/en/download/16356/intel-server-chipset-driver-for-windows-for-legacy-intel-server-board.html?v=t
https://downloadmirror.intel.com/28531/eng/intel_chipset_win_10.1.17903.8106_pv.zip
Name: intel_chipset_win_10.1.17903.8106_pv--X79.zip
Size: 5688157 bytes (5554 KiB)
SHA256: 93E77ED3AC0659E7D9017FD285698760F7B333694C3614917E8B73577870F1F6
SHA1: 7A34C56D16357BAFAE1A749BAC465E8976CBF8FA
The Dell website has an audio driver for the machine. It's the MaxxAudio one,
which includes some sound effects, such as the tres annoying Realtek Concert
Hall "Reverb effect" when the sound effects menu is set to "None".
*******
The reason this is so big, is it is similar to the RealTek Jumbo driver
which is also in the hundreds of megabytes (the 600MB RealTek is squeezed down
to 300MB by compression -- it should really just be a RealTek driver in a Dell
wrapper).
Name: Realtek-High-Definition-Audio-Driver_D7VCY_WIN_6.0.1.8224_A08_02.EXE
Size: 318,464,720 bytes (303 MiB)
SHA256: 04A92B91607ECE504A72A5E9C22DC65A1BC2170B7D887EA980FBAF22D237D585
It's on this page.
https://www.dell.com/support/product-details/en-ca/product/inspiron-13-5368-2-in-1-laptop/drivers
Once it is installed, look for "RtkNGUI64.exe" or "RtkNGUI.exe"
as that's the custom control panel that RealTek likes but
Microsoft does not like. To get that, I had to hunt that down
and run it manually, as the automation didn't put it in the tray.
Paul
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-02-06 14:55 +0000 |
| Message-ID | <m0k0qhFqafqU1@mid.individual.net> |
| In reply to | #182027 |
On 06/02/2025 11:32, Paul wrote: > On Thu, 2/6/2025 3:59 AM, David wrote: >> On 27/01/2025 09:50, wasbit wrote: >>> On 26/01/2025 19:43, David wrote: >>>> snip < >>>> >>>> I followed the guidance from "David" on Microsoft Answers and made a new bootable flash drive then once again installed Windows 10 on my old Dell laptop. Sadly, still no sound! >>>> >>>> On the Dell website, though, this time, I was able to carry out a hardware scan. Here's a screenshot of the failures indicated:- >>>> https://i.ibb.co/XjYDWtv/IMG-3158.jpg >>>> >>>> Any comment beyond time to recycle it?!! >>>> >>> >>> You are missing motherboard chip set drivers. >> >> How would YOU correct that situation? >> > > This is a chipset driver, but the SunRise Point does not have an HDAudio entry, > and in any case, these are cosmetic drivers for putting a text string in > Device Manager to label system devices. I used this one to fix my Patsburg > entries (X79) so they displayed properly. If your Device Manager "System" area > is all labeled, and no yellow codes showing, then chances are nothing in there > needs assistance. > > https://web.archive.org/web/20220120160547/https://www.intel.com/content/www/us/en/download/16356/intel-server-chipset-driver-for-windows-for-legacy-intel-server-board.html?v=t > > https://downloadmirror.intel.com/28531/eng/intel_chipset_win_10.1.17903.8106_pv.zip > > Name: intel_chipset_win_10.1.17903.8106_pv--X79.zip > Size: 5688157 bytes (5554 KiB) > SHA256: 93E77ED3AC0659E7D9017FD285698760F7B333694C3614917E8B73577870F1F6 > SHA1: 7A34C56D16357BAFAE1A749BAC465E8976CBF8FA > > The Dell website has an audio driver for the machine. It's the MaxxAudio one, > which includes some sound effects, such as the tres annoying Realtek Concert > Hall "Reverb effect" when the sound effects menu is set to "None". > > ******* > > The reason this is so big, is it is similar to the RealTek Jumbo driver > which is also in the hundreds of megabytes (the 600MB RealTek is squeezed down > to 300MB by compression -- it should really just be a RealTek driver in a Dell > wrapper). > > Name: Realtek-High-Definition-Audio-Driver_D7VCY_WIN_6.0.1.8224_A08_02.EXE > Size: 318,464,720 bytes (303 MiB) > SHA256: 04A92B91607ECE504A72A5E9C22DC65A1BC2170B7D887EA980FBAF22D237D585 > > It's on this page. > > https://www.dell.com/support/product-details/en-ca/product/inspiron-13-5368-2-in-1-laptop/drivers > > Once it is installed, look for "RtkNGUI64.exe" or "RtkNGUI.exe" > as that's the custom control panel that RealTek likes but > Microsoft does not like. To get that, I had to hunt that down > and run it manually, as the automation didn't put it in the tray. Thank you, Paul :-) I'll find a few minutes to flash-up the Dell and try what you suggest. -- David
[toc] | [prev] | [next] | [standalone]
| From | David <David@example.net> |
|---|---|
| Date | 2025-02-06 20:33 +0000 |
| Message-ID | <m0kklnFt3vgU2@mid.individual.net> |
| In reply to | #182027 |
On 06/02/2025 11:32, Paul wrote: > Once it is installed, look for "RtkNGUI64.exe" or "RtkNGUI.exe" > as that's the custom control panel that RealTek likes but > Microsoft does not like. To get that, I had to hunt that down > and run it manually, as the automation didn't put it in the tray. *HOW* should I "hunt that down", Paul? I am at that stage now! (It's like going back to Windows 95 days!) -- David
[toc] | [prev] | [next] | [standalone]
| From | % <pursent100@gmail.com> |
|---|---|
| Date | 2025-02-06 13:55 -0700 |
| Message-ID | <xgSdnd5A4KBPvDj6nZ2dnZfqn_udnZ2d@giganews.com> |
| In reply to | #182041 |
David wrote: > On 06/02/2025 11:32, Paul wrote: >> Once it is installed, look for "RtkNGUI64.exe" or "RtkNGUI.exe" >> as that's the custom control panel that RealTek likes but >> Microsoft does not like. To get that, I had to hunt that down >> and run it manually, as the automation didn't put it in the tray. > > *HOW* should I "hunt that down", Paul? > > I am at that stage now! > > (It's like going back to Windows 95 days!) > you'll blow up soon , yougot 50 different guys saying , change this , delete that , move those , none of them can actually see what they are doing , and you're letting them all in ))))))))))*** BOOM *** (((((((((((
[toc] | [prev] | [next] | [standalone]
Page 1 of 3 [1] 2 3 Next page →
Back to top | Article view | alt.comp.os.windows-10
csiph-web