[gentoo-user]
mt aoos, vdt; hs,lqk ,sov dgkjdoe... :dogsf;ptw, G ialqk ktrd ak app f;glu x,dokt a; G ja.dlqk f;dh gk ;glid kjd 20kj idlkfote -- Beware of Zombies. =O #EggCrisis #BlackWinter White is the new Kulak. Powers are not rights.
[gentoo-user] EMERGENCY: X11 KEYBOARD MAPPING STOPPED WORKING!!!!
having extreme trouble typing this, haven't had to type qwerty in fifteen years, keyboard mapping I need went poof during recent update, rebooted for kernel 6.3, X11 is NOT recording logs to /var/log since last year. Console seemed to be barfing about not knowing what a dvorak is even though it is the only other ISO standard keyboard mapping. No way to access console barf from within X11, no idea where logs are if they exist. here are my configs, 2010 version has: drwxr-xr-x 2 root root 4096 Mar 7 2020 xorg.conf.d -rw-r--r-- 1 root root 2490 Oct 21 2010 xorg.conf.good Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "dvorak" EndSection Since that was too simple and made too much sense, they had to make it uglier... current active config: Section "InputClass" Identifier "keyboard-layout" MatchIsKeyboard "on" Option "XkbLayout" "dvorak" Option "XkbModel" "pc104" # Option "XkbOptions" "grp:caps_toggle" EndSection atg@tortoise ~ $ setxkbmap Error loading new keyboard description atg@tortoise ~ $ still have package x11-apps/xinput-1.6.3 installed even tho eclean-dist wants it gone, must be error because no clue how x11 is supposed to work without it. =( Yet agan Linux manufactures a new insoluble problem without warning and for no reason. -- Beware of Zombies. =O #EggCrisis #BlackWinter White is the new Kulak. Powers are not rights.
Re: [gentoo-user] Loading modules prevents shutdown
On 17/06/2023 12:57, dhk wrote: Thanks for the tips. After spending a lot of time on and off for a few weeks trying to keep /lib/modules on its own partition, it just did not work right; the system was scrapped and rebuilt per the trivial solution with /lib/modules on the root partition. Now it works as expected. A good explanation as to why /lib/modules cannot be a separate partition would be nice, but after learning learning the hard way again it stays on the root partition going forward. The kernel needs to load modules to boot fully. If mount hasn't run by the time the kernel needs a module, you have a problem ... Even worse, if mount needs the kernel to load a module, you're stuffed ... Cheers, Wol
Re: [gentoo-user] Loading modules prevents shutdown
Thanks for the tips. After spending a lot of time on and off for a few weeks trying to keep /lib/modules on its own partition, it just did not work right; the system was scrapped and rebuilt per the trivial solution with /lib/modules on the root partition. Now it works as expected. A good explanation as to why /lib/modules cannot be a separate partition would be nice, but after learning learning the hard way again it stays on the root partition going forward. On 5/23/23 15:58, dhk wrote: After a new install on an HP EliteBook with an Intel I7 core, when the iwlwifi module is loaded the system fails to complete shutdown and power off. The install is mostly a standard openrc install for a personal use laptop. The usual partitions were created and only /var, /opt and /home are on lvm2; one non-standard partition configuration is /usr/src and /lib/modules are on their own partition. The /usr/src partition should be benign since it is only used when building the kernel; however, the /lib/modules partition was the cause of one issue that has already been resolved and may be the cause of the other. First, the resolved issue. On boot, the iwlwifi module was not found and the following message was displayed. * Loading kernel modules ... modprobe: FATAL: Module iwlwifi not found in directory /lib/modules/6.1.19-gentoo-x86_64 This was puzzling, since once logged in a find command found it where it should be and the module could be added on the command line without any problem. This issue caused me to reboot and shutdown many times until noticing that modprobe was trying to load the iwlwifi module before /lib/modules was mounted. This was easily fixed by adding a "/lib/modules" line to the /etc/initramfs.mounts file. The one thing noticed from all the shutdowns and reboots was, when the iwlwifi module was not loaded the system shutdown fine and when it was loaded the system failed to shutdown and power off completely. Second, Loading modules prevents shutdown, The issue was discovered with iwlwifi, but occurs when any module from the /lib/modules/6.1.19-gentoo-x86_64 directory is tried instead and deleting the module before the "shutdown -h -P now" does not make a difference. To get a better look at what is going on, the rc_logger variable was set to "YES" in /etc/rc.conf (rc_logger="YES"). Now the difference between the console display and /var/log/rc.log file on a clean shutdown and one with a module loaded preventing a clean shutdown. Whether a module is loaded or not, the console and /var/log/rc.log match up to and including "Stopping the Logical Volume Manager" and then things start to deviate. * Stopping syslog-ng ... [ ok ] <= console and /var/log/rc.log match. * Unmounting loop devices * Unmounting filesystems * Unmounting /var ... [ ok ] * Unmounting /opt ... [ ok ] * Unmounting /home ... [ ok ] * Unmounting /usr/src ... [ ok ] * Unmounting /tmp ... [ ok ] * Unmounting /lib/modules ... [ ok ] * Unmounting /boot ... [ ok ] * Deactivating swap devices ... [ ok ] <= console and /var/log/rc.log match. * Stopping the Logical Volume Manager ... <= When a module is loaded, this is the last line on the console. 0 logical volume(s) in volume group "vg1" now active 0 logical volume(s) in volume group "vg0" now active [ ok ] <= When a module is loaded, this is the last line in /var/log/rc.log. * Setting hardware clock using the system clock [UTC] ... [ ok ] <= When no module is loaded, this is on the console and in /var/log/rc.log. * Stopping udev ... [ ok ] <= When no module is loaded, this is on the console and in /var/log/rc.log. rc shutdown logging stopped at Thu May 18 05:44:09 2023 <= When no module is loaded, this is the last line in /var/log/rc.log. * Terminating remaining processes ... [ ok ] <= When no module is loaded, this is on the console (See: /etc/init.d/killprocs). * Killing remaining processes ... [ ok ] <= When no module is loaded, this is on the console (See: /etc/init.d/killprocs). * Saving dependency cache ... [ ok ] <= When no module is loaded, this is on the console (See: /etc/init.d/savecache). * Remounting remaining filesystems read-only ... [ ok ] <= When no module is loaded, this is on the console (See: /etc/init.d/mount-ro). * Remounting / read only ... [ ok ] <= When no module is loaded, this is on the console. reboot: Power down <= When no module is loaded, this is on the console. In short, it looks like the LVM was stopped correctly and everything was good up to that point; however, when a module is loaded it looks like nothing in /etc/runlevels/shutdown/ gets kicked off and the system is waiting. My preference is to have this
Re: [gentoo-user] QMPlay2 single instance, want multiple.
Dale wrote: > > What I wanted to get rid of mostly was the progress bar when I hit left > or right arrow. It was only there for a second but I just look at the > bottom if I need to know where I am. In case someone else runs up on > this thread, this is how to get rid of it, or set it to something else. > In mpv.conf, located in /etc/mpv/ here, add this line. > > --osd-on-seek=no > > >From the man page: > > > --osd-on-seek= > Set what is displayed on the OSD during seeks. The default is bar. > > > It defaults to bar which annoys me. Set to no, when you seek, it > displays nothing, just moves the video. I'm not sure what msg does. > Maybe it adds flavor or something. LOL > > I did test multiple instances, it opens at least three with no > problems. Now to get rid of the caption thing. The man page comes to > the rescue again. Added this to mpv.conf as well. > > --sub-create-cc-track=no > > >From man page: > > > --sub-create-cc-track= > For every video stream, create a closed captions track (default: no). > The only purpose is to make the track available for selection at the > start of playback, instead of creating it lazily. This applies only to > ATSC A53 Part 4 Closed Captions (displayed by mpv as subtitle tracks > using the codec eia_608). The CC track is marked "default" and selected > according to the normal subtitle track selection rules. You can then use > --sid to explicitly select the correct track too. > > If the video stream contains no closed captions, or if no video is being > decoded, the CC track will remain empty and will not show any text. > > > It says it defaults to no but it appears something changed somewhere. > It showed captions by default but setting to no cut them off. I assume > this doesn't work if they are coded into the video itself tho. > Sometimes people do it that way instead of having it a separate track > thingy. > > Also, I put both options on ONE line in the config file. Having it on > two separate lines may work but it certainly works with both on the same > line. Also, there is a line in there for youtube-dl that is on its own > line. I assume those are two different things. > > Thanks Matt for pointing me in this direction. As it is, this might be > a better player for me than QMPlay2 is. This works as good as QMPlay2 > and it closes at the end. I miss gnome-player tho. Silly old thing > gave me a lot of years of good use. :/ > > Dale > > :-) :-) > I added another option, to set default language, and the options were ignored. I edited the mpv.conf file and put each option on a separate line. Everything worked again. So, it may be best to put each option on a single line after all. It may have a limit for each line or something. I dunno. To be honest tho, I wish mpv just had a preferences screen to set this stuff. The good thing, once you set everything up like you want it, it should be done. Dale :-) :-)
Re: [gentoo-user] SMTP relay settings with Telus
On 6/11/23 14:58, Jigme Datse wrote: On Sun, 11 Jun 2023 00:10:15 -0600 the...@sys-concept.com wrote: Just switched to Telus from Shaw and for some reason, there either isn't a working SMTP relay Not quite sure what the issue is. Were you using the Shaw mail servers as you MX host? Or are you having issues with connecting to your mail server through Telus? Yes, I was using Shaw for my remote and local system to send emails to me after compilation and system notification. So after switching to Telus, it all ended. So all those linux email notification stop working, what is the solution? We don't have enough information to answer that, unless someone has gone through the same situation as you're going through. We'll need more information about exactly what is going on. I've tried configure remote host to send email via Google SMTP but it doesn't work either: main.cf relayhost = [smtp.gmail.com]:587 smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_maps = hash:/etc/postfix/saslpass smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt smtp_use_tls = yes /etc/postfix/saslpass [smtp.gmail.com]:587 em...@gmail.com:password But the above is not working either.
