Re: How to comment or reply to others?
On Thu, 08 Jul 2021 11:49:46 -0600, jim.cro...@gmail.com said: > On Sun, Jul 4, 2021 at 9:36 AM Valdis KlÄtnieks > wrote: > > > smtpEncryption = ssl > > > smtpServer = smtp.gmail.com > > > smtpUser = my-email-addr...@gmail.com > > > smtpServerPort = 465 > I have tls, and port = 587, and an smtppass Thanks for catching that. I saw the encryption, and totally missed the other two. pgpeAHbvvm7vP.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: How to comment or reply to others?
On Sun, Jul 4, 2021 at 9:36 AM Valdis Klētnieks wrote: > > On Sun, 04 Jul 2021 11:13:08 +0200, Abd-Alrhman Masalkhi said: > > > I have allready set up the .gitconfig file with following configuration: > > > > smtpEncryption = ssl > > smtpServer = smtp.gmail.com > > smtpUser = my-email-addr...@gmail.com > > smtpServerPort = 465 > > Try 'smtpEncryption = tls' instead. Gmail's email submission servers require > at least TLS 1.1 (current protocol version is 1.3), and they stopped allowing > SSL (the known-insecure predecessor of TLS) some 5 years ago. > > https://threatpost.com/google-to-deprecate-sslv3-rc4-in-gmail-imappop-clients/118533/ I have tls, and port = 587, and an smtppass ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: laptop iwlwifi suddenly not working
Solved ! On Fri, Jul 2, 2021 at 7:39 AM wrote: > > On Thu, Jul 1, 2021 at 9:53 PM Connor Kuehl wrote: > > > > Maybe there’s a hardware switch that toggles airplane mode? Might not be, > > since I’d think that would be kind of redundant if there’s a fn key > > dedicated to it, but I remember my previous laptops had a physical slider > > switch for airplane mode. Might be worth checking to see if your laptop has > > one and if it was accidentally toggled. > > > > nope. 2 older laptops have that switch, but not this one. > One of the leds on the edge is a wifi indicator, > it turns on/off when I hit F12, they are in sync with WM-screen notifications > > There is a bios update, but it requires windows to install, long gone > with dead hd. > Im trying to download a windows iso, I'll try sticking it on a Usb and > try booting it, > but Im not optimistic > > > Connor > > > thanks So, to close this out, I'll report I found fix on toms-hardware, from 2013, for another toshiba laptop. pull the battery and plug-power, hit the power button, to attempt turn-on reinstall battery, boot thats it. heres when it was broken [jimc@frodo ~]$ journalctl -b-1 | grep -P 'iwl|rfkill' Jul 08 10:15:58 frodo systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: Found debug destination: EXTERNAL_DRAM Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: Found debug configuration: 0 Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: loaded firmware version 29.4063824552.0 7265D-29.ucode op_mode iwlmvm Jul 08 10:15:58 frodo kernel: audit: type=1130 audit(1625760958.369:115): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 08 10:15:58 frodo audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210 Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: reporting RF_KILL (radio disabled) Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: Applying debug destination EXTERNAL_DRAM Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: Allocated 0x0040 bytes for firmware monitor. Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0: base HW address: 00:db:df:4e:ca:f0 Jul 08 10:15:58 frodo kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' Jul 08 10:15:58 frodo kernel: iwlwifi :07:00.0 wlp7s0: renamed from wlan0 Jul 08 10:16:02 frodo NetworkManager[883]: [1625760962.0689] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:1c.1/:07:00.0/ieee80211/phy0/rfkill2) (driver iwlwifi) Jul 08 10:16:02 frodo NetworkManager[883]: [1625760962.0714] manager[0x5604d91ba030]: rfkill: Wi-Fi hardware radio set enabled Jul 08 10:16:02 frodo NetworkManager[883]: [1625760962.0721] manager[0x5604d91ba030]: rfkill: WWAN hardware radio set enabled Jul 08 10:16:02 frodo NetworkManager[883]: [1625760962.1109] manager: rfkill: Wi-Fi disabled by radio killswitch; enabled by state file Jul 08 10:16:02 frodo NetworkManager[883]: [1625760962.] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Jul 08 10:16:03 frodo systemd[1]: systemd-rfkill.service: Deactivated successfully. Jul 08 10:16:03 frodo audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 08 10:16:13 frodo kernel: rfkill: input handler disabled Jul 08 10:16:14 frodo gsd-media-keys[1298]: Failed to grab accelerator for keybinding settings:rfkill Jul 08 10:16:25 frodo kernel: rfkill: input handler enabled Jul 08 10:16:28 frodo kernel: rfkill: input handler disabled Jul 08 10:16:29 frodo gsd-media-keys[1965]: Failed to grab accelerator for keybinding settings:rfkill Jul 08 11:16:33 frodo kernel: rfkill: input handler enabled Jul 08 11:16:33 frodo systemd[1]: systemd-rfkill.socket: Deactivated successfully. Jul 08 11:16:33 frodo systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. [jimc@frodo ~]$ theres a lot of rfkill toggling going on there, but oddly in working version too, just less (not the early reported one) other diffs might be cuz i fiddled with systemd disable rfkill, which didnt fix it [jimc@frodo ~]$ journalctl -b-0 | grep -P 'iwl|rfkill' Jul 08 11:23:19 frodo systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Jul 08 11:23:19 frodo audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
Re: trigger timestamp
On Thu, 08 Jul 2021 18:11:13 +0200, Muni Sekhar wrote: > > On Thu, Jul 8, 2021 at 6:02 PM Takashi Iwai wrote: > > > > On Thu, 08 Jul 2021 14:19:12 +0200, > > Muni Sekhar wrote: > > > > > > On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai wrote: > > > > > > > > On Thu, 01 Jul 2021 01:41:29 +0200, > > > > Muni Sekhar wrote: > > > > > > > > > > Hi all, > > > > > > > > > > >From the user space test application , Is it possible to get the > > > > > trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & > > > > > SNDRV_PCM_TRIGGER_STOP events for audio playback capture? > > > > > > > > That's exactly what trigger_tstamp of snd_pcm_status corresponds for. > > > Does aplay and arecord have any command line options to get the > > > trigger_tstamp? If not how to get it? > > > > Implement some code :) > > > > Alternatively you can check the proc output contents in > > /proc/asound/card*/pcm*/sub*/status. It'd be difficult to see the > > stop timestamp, though (as the application closes the stream > > immediately after that). > How to specify if i want the REALTIME/MONOTONIC_RAW trigger_time > timestamp type output in /proc/asound/card*/pcm*/sub*/status? It's not provided in a standard tool and you have to write some program by yourself, I suppose. Takashi ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: trigger timestamp
On Thu, Jul 8, 2021 at 6:02 PM Takashi Iwai wrote: > > On Thu, 08 Jul 2021 14:19:12 +0200, > Muni Sekhar wrote: > > > > On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai wrote: > > > > > > On Thu, 01 Jul 2021 01:41:29 +0200, > > > Muni Sekhar wrote: > > > > > > > > Hi all, > > > > > > > > >From the user space test application , Is it possible to get the > > > > trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & > > > > SNDRV_PCM_TRIGGER_STOP events for audio playback capture? > > > > > > That's exactly what trigger_tstamp of snd_pcm_status corresponds for. > > Does aplay and arecord have any command line options to get the > > trigger_tstamp? If not how to get it? > > Implement some code :) > > Alternatively you can check the proc output contents in > /proc/asound/card*/pcm*/sub*/status. It'd be difficult to see the > stop timestamp, though (as the application closes the stream > immediately after that). How to specify if i want the REALTIME/MONOTONIC_RAW trigger_time timestamp type output in /proc/asound/card*/pcm*/sub*/status? > > > Takashi -- Thanks, Sekhar ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: trigger timestamp
On Thu, 08 Jul 2021 14:19:12 +0200, Muni Sekhar wrote: > > On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai wrote: > > > > On Thu, 01 Jul 2021 01:41:29 +0200, > > Muni Sekhar wrote: > > > > > > Hi all, > > > > > > >From the user space test application , Is it possible to get the > > > trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & > > > SNDRV_PCM_TRIGGER_STOP events for audio playback capture? > > > > That's exactly what trigger_tstamp of snd_pcm_status corresponds for. > Does aplay and arecord have any command line options to get the > trigger_tstamp? If not how to get it? Implement some code :) Alternatively you can check the proc output contents in /proc/asound/card*/pcm*/sub*/status. It'd be difficult to see the stop timestamp, though (as the application closes the stream immediately after that). Takashi ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: trigger timestamp
On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai wrote: > > On Thu, 01 Jul 2021 01:41:29 +0200, > Muni Sekhar wrote: > > > > Hi all, > > > > >From the user space test application , Is it possible to get the > > trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & > > SNDRV_PCM_TRIGGER_STOP events for audio playback capture? > > That's exactly what trigger_tstamp of snd_pcm_status corresponds for. Does aplay and arecord have any command line options to get the trigger_tstamp? If not how to get it? > > > HTH, > > Takashi -- Thanks, Sekhar ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: trigger timestamp
On Thu, 01 Jul 2021 01:41:29 +0200, Muni Sekhar wrote: > > Hi all, > > >From the user space test application , Is it possible to get the > trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & > SNDRV_PCM_TRIGGER_STOP events for audio playback capture? That's exactly what trigger_tstamp of snd_pcm_status corresponds for. HTH, Takashi ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
