XPost: alt.os.linux.mint, alt.comp.os.windows-10, alt.computer.workshop   
   From: David@example.net   
      
   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 0x   
                                           # 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   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)