Activity for Jim Ward
-
Jim Ward posted a comment on ticket #12
Okay, I got past the original issue with WiFi with David's help. The issue with the acpi-call-dkms installation with the 6.1.0-34-amd64 kernel got resolved when I went ahead and started using the 6.1.0-41-amd64 kernel. Still not quite out of the woods since what I need to use is the acpi_cpufreq scaling driver instead of intel_pstate driver, and I need to find out where to set that in the kernel parameters. I'll open a new ticket for that so this one can be closed.
-
TDM --> SDDM to fix a display bug with multiple monitors
-
Just downloaded and installed from the newer ISO, tethered TDE to my old Android tablet, downloaded the brcm80211 firmware (most other distros use wl, but apparently it's not available here?). Did the modprobe activation and have wifi. So the wifi issue is done. HOWEVER -- I'm not yet done. My ancient laptop needs to have the power turned off to the Nvidia GPU, so I usually download and install acpi-call-dkms and set it up. Did that, but the acpi-call.ko module can't be built bcz the linux headers...
-
Just downloaded and installed from the newer ISO, tethered TDE to my old Android tablet, downloaded the brcm80211 firmware (most other distros use wl, but apparently it's not available here?). Did the modprobe activation and have wifi. So the wifi issue is done. HOWEVER -- I'm not yet done. My ancient laptop needs to have the power turned off to the Nvidia GPU, so I usually download and install acpi-call-dkms and set it up. Did that, but the acpi-call.ko module can't be built bcz the linux headers...
-
Just downloaded and installed from the newer ISO, tethered TDE to my old Android tablet, downloaded the brcm80211 firmware (most other distros use wl, but apparently it's not available here?). Did the modprobe activation and have wifi. So the wifi issue is done. HOWEVER -- I'm not yet done. My ancient laptop needs to have the power turned off to the Nvidia GPU, so I usually download and install acpi-call-dkms and set it up. Did that, but the acpi-call.ko module can't be built bcz the linux headers...
-
Just downloaded and installed from the newer ISO, tethered TDE to my old Android tablet, downloaded the brcm80211 firmware (most other distros use wl, but apparently it's not available here?). Did the modprobe activation and have wifi. So the wifi issue is done. HOWEVER -- I'm not yet done. My ancient laptop needs to have the power turned off to the Nvidia GPU, so I usually download and install acpi-call-dkms and set it up. Did that, but the acpi-call.ko module can't be built bcz the linux headers...
-
Yes, it's a Broadcom 4313, I had seen the wiki or other article before. I think my mistake was in adding a DIFFERENT source line with a DIFFERENT repository with the contrib non-free stuff. Duh. I don't usually muck with that part of my setups unless I have more specific info like what you just gave! inxi -nn (rf711) 10:30:27 Network: Device-1: Broadcom BCM4313 802.11bgn Wireless Network Adapter driver: wl IF: wlan0 state: up mac: b4:74:9f:7c:bd:95 SOOO...should I simply tether my Exe install to...
-
Yes, it's a Broadcom 4318, I had seen the wiki or other article before. I think my mistake was in adding a DIFFERENT source line with a DIFFERENT repository with the contrib non-free stuff. Duh. I don't usually muck with that part of my setups unless I have more specific info like what you just gave! inxi -nn (rf711) 10:30:27 Network: Device-1: Broadcom BCM4313 802.11bgn Wireless Network Adapter driver: wl IF: wlan0 state: up mac: b4:74:9f:7c:bd:95 SOOO...should I simply tether my Exe install to...
-
Yes, it's a Broadcom 4318, I had seen the wiki or other article before. I think my mistake was in adding a DIFFERENT source line with a DIFFERENT repository with the contrib non-free stuff. Duh. I don't usually muck with that part of my setups unless I have more specific info like what you just gave! SOOO...should I simply tether my Exe install to my Android tablet's wifi* or first download and use the new ISO? *The first try with tethering went horribly -- TDEnetworkmanager kept connecting and disconnecting...
-
Aha -- I wasn't aware of the bit about MOVING the flag-aligned keyboard to the top. That ALMOST fixed the problem, but no, I had to go back in and then noticed that the layout that was set was for a 104 key keyboard. When I changed it to the PC 105 key keyboard layout, I got my vertical bar back YAY!!! This can be marked as SOLVED, I think.
-
Thanks to the fix to the keyboard settings, I was able to get some more diagnostic information from dmesg for things related to firmware (which searches for the "RNETLINK" error message suggested -- missing firmware/modules). Here's the output of the "dmesg | grep -i firmware" command: [ 0.074518] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 7.757643] ACPI: video: [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 7.992466] psmouse serio1: elantech: assuming hardware version 3 (with...
-
Aha -- I wasn't aware of the bit about MOVING the flag-aligned keyboard to the top. That ALMOST fixed the problem, but no, I had to go back in and then noticed that the layout that was set was for a 104 key keyboard. When I changed it to the PC 105 key keyboard layout, I got my vertical bar back YAY!!!
-
Thanks! I just deleted that tdesurc file remotely from this distro. While I was trying to check things that might be different with the Exe environment and the several distros that I'm also running, I DID already edit the /etc/hosts file to look more like the others (IPV6 stuff added): 127.0.0.1 localhost 127.0.0.1 exe_RF711 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2...
-
Thanks, David. Pretty sure I tried that, to no avail. I'll give it another try when I boot back into EXE. Meanwhile, I took a hard-core approach and edited the /etc/default/keyboard file to mimic what's in my other distros. While it did NOT work for the TDE environment, It DID work in the Openbox session, so I'm posting the output of "sudo dmesg | grep -i firmware" into the network issue. I had read that one of the causes of the error message I was getting could be due to missing modules or firw...
-
Hey, thanks! Here ya go: $ md5sum exegnu64_daedalus-20240604.iso e25ea589354a3c9d17b12fccea51c3c9 exegnu64_daedalus-20240604.iso $ cat md5sum_exegnu64_daedalus-20240604.txt e25ea589354a3c9d17b12fccea51c3c9 They look the same to me.
-
Keyboard setting stuck on UK style, cannot override
-
The above is my ticket. Sorry, shoulda logged in first. I'm also getting a weird error message for anything I do with sudo -- it's shown below. Tried this: $ ip link 1: lo: <loopback,up,lower_up> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <no-carrier,broadcast,multicast,up> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether e8:11:32:44:7e:5f brd ff:ff:ff:ff:ff:ff 3: wlan0:...
-
-
I'm pretty sure that Brave Browser is (or at least was) a Chromium based browser. It has a specific feature that is only available there (Brave News) and I'd like to make a web app for it. Is there some way to fool Ice into thinking it's just Chromium or something like that?
-
Thanks. @pepdebian! Turns out I'd shot meself in the foot with a script that I'd configured the greeter to run when my session started up to kill the Nvidia GPU. Worked FINE the very first time it runs (as in reboot), but not when trying to logout/login because the script did not exit with rc=0. OOOOPS! Fixed the script and all is well now! Meanwhile, would love to be able to use the much lighter greeter, ly, but I can't get it to build. (The ly greeter works great on EndeavourOS, where it was suggested...
-
I fiddle around with various DEs (but mostly WMs), so I was trying to log out of one, switch to another, and log back in. It just churned a bit and returned to the login dialog. I've only had this problem on a couple of other distros -- EndeavourOS and Salix -- and they both were solve by installing and using a display manager other than lightdm. I tried to get the very lightweight "ly" display manager (a TTY greeter, really) that I'm using with EndeavourOS, but it wouldn't install/build on PMOS....
-
This is my trusty but rusty 17.3" Samsung RF711 laptop, which originally came with Windows 7. It has SOOO many problems, mostly relating to thermal issues (fan can't be controlled and is weak as Hades, CPUs can't be undervolted, Nvidia GEForce 540 or whatever adds heat even when it's not in use, etc., etc.). I have 4 distros installed on the 512 GB internal SSD (peppermintOS being one of them) and two on an external bootable 512 GB SSD drive). I look for distros that seem to be light and sometimes...
-
Okay, nevermind! I downloaded the script to a file and edited it so that the $repo_code variable would have "bookworm" rather than "daedalus" (so not calling lsb_release) and then piped the hacked script to the "sudo bash" command and the rest is history. Interestingly, starting in liquorix reduced the initial memory footprint by ~13MB ! I now have "ondemand" CPU governor as well as userspace and performance. It seems to be the default, and even without tweaking, it's already showing better temperature...
-
Okay, nevermind! I downloaded the script to a file and edited it so that the $repo_code variable would have "bookworm" rather than "daedalus" (so not calling lsb_release) and then piped the hacked script to the "sudo bash" command and the rest is history. Interestingly, starting in liquorix reduced the initial memory footprint by ~13MB ! I now have "ondemand" CPU governor as well as schedutil and performance. It seems to be the default, and even without tweaking, it's already showing better temperature...
-
Has anyone successfully installed the Liquorix kernel in Peppermint OS? Would this work if you could override the "daedalus" (Devuan) release with an equivalent Debian release? (Is there one?) $ curl 'https://liquorix.net/install-liquorix.sh' | sudo bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4082 100 4082 0 0 19085 0 --:--:-- --:--:-- --:--:-- 19074 [INFO ] Possible distributions: debian Ign:1 https://liquorix.net/debian daedalus InRelease...
-
Thanks!
-
Most of my Linuxes run with thermald to manage CPU (etc.) temps. I didn't see it running in my ps_mem output, and was about to install it, when I ran "ps -ef | grep therm" and saw "[acpi_thermal_pm]" in the output. Does it do the same stuff as thermald, or woulc there still be a benefit to installing and running thermald?
-
Ummmm.... Is there a mechanism to mark a topic as SOLVED?
-
Hi all, New to PeppermintOS but not Linux. (Besides, I got my start on an OS360 system back in the day -- huge system with [gasp] 200K magnetic core RAM!!) I started my personal (not work) Linux journey with Mint, moved on to MX and stayed there for years (still use it). But being of a curious mind, I wanted to try other distros to find the right stuff for my aging laptop with its overheating issues. Was looking for lightness and coolness. I've tried AntiX, Sparky Linux, Q4OS (really nice, BTW!),...
-
@Peppermint OS guy or gal -- I have great praise for this distribution! I finally got the thermal business licked. Leaving the machine idle for a while with psensor running recorded low temps of ~40C, which for ME, is terrific. My custom JWM setup with custom conky and tint2 panel, nitrogen wallpaper, dunst notifier, chrony timekeeper, udevil USB automounter, Xfe (and its xfw and other goodies) file manager system, and other cool things, all boot up to around 250-260 MB. That's in line with what...
-
Okay, I think I got it under control. For starters, apparently merely probing the contents of /proc/acpi/call RESETS IT. Soooo -- DON'T DO THAT. Second, I hadn't done everything in the article I cited on the first page. I added code to remove the NVIDIA PCI busses. However, PMOS with OpenRC doesn't run stuff in /etc/tmpfiles.d or so it would seem. I had to put the code in with the acpi_call code in a shell script that I have LightDM call as root (session-setup-script=). Also re-ran update-initramfs....
-
Does this provide any clarity? Stinkin' nouveau is lots of places: $ lsmod | grep nouveau nouveau 2433024 2 i2c_algo_bit 16384 2 i915,nouveau drm_display_helper 184320 2 i915,nouveau drm_ttm_helper 16384 1 nouveau mxm_wmi 16384 1 nouveau ttm 94208 3 drm_ttm_helper,i915,nouveau drm_kms_helper 212992 3 drm_display_helper,i915,nouveau drm 614400 13 drm_kms_helper,drm_display_helper,drm_buddy,drm_ttm_helper,i915,ttm,nouveau video 65536 3 i915,samsung_laptop,nouveau wmi 36864 3 video,mxm_wmi,nouveau button...
-
AHA!!! It seems I can get whatever it is to reset the Nvidia OFF switch simply by doing some rc-xxx command (simply running "sudo rc-status" will do it). EDIT: No, no aha moment. I just ran the code to turn off GPU, checked /proc/acpi/call and saw the good "0x0" then the next time I checked it, it was "not called". What the heck is going on here????
-
AHA!!! It seems I can get whatever it is to reset the Nvidia OFF switch simply by doing some rc-xxx command (simply running "sudo rc-status" will do it). What's going on?
-
Bummer. Tried @PeppermingOS's solution but still not working. WEIRD PROBLEM! Maybe I need to set up a root cron job to fire up the acpi_call code every 5 minutes or so? Does having a 5 minute timer add to system CPU utilization?
-
Well, I suppose I can give it a try. At least I have another few distros that I can use to get back into the PMOS filesystem to try to undo it if anything goes wrong. If not, PMOS is still on my Ventoy stick, and maybe I've learned enough to get back to where I am quickly enough..... ;) EDIT: OTOH, for whatever reason, the acpi_call stuff seems to have steadied out for now -- at least, repeated runs of "sudo cat /proc/acpi/call" have consistently shown "0x0" and the sensor temps are relatively stable....
-
Well, I suppose I can give it a try. At least I have another few distros that I can use to get back into the PMOS filesystem to try to undo it if anything goes wrong. If not, PMOS is still on my Ventoy stick, and maybe I've learned enough to get back to where I am quickly enough..... ;)
-
Hi all, new to PeppermintOS but not to Linux. I have a Samsung RF711 laptop (circa 2011, according to last BIOS update) that overheats all too readily, much of it being due to the Nvidia GPU. I have been using the setup described here for the most part. I've tried various ways of setting the flags into the /proc/acpi/call registers but it's not working. Actually, it DOES work, but only briefly. I can run the command to turn off the card, and /proc/acpi/call shows the proper "0x0" -- for a few seconds...
-
Make "Size" column show folder files count
-
Sorry, please ignore this. It turned out to be an artifact of the menu system of the current OS I'm using.
-
Shell window runs when starting Xfe
-
I have fixed my problem regarding the automounts. Found out about udevil/devmon and started using it (added devmon & to my startup script). It's very small, way smaller than udiskie. Had to change the xfe unmount command to "udevil umount" so non-root user could unmount. Works, and I don't need to use the script I had. Thanks for your great software! (Still waiting for the fix to the memory leaks, however!)
-
Yes, I CAN use "udiskie" to auto-mount my USB sticks. It just takes up ~25 MB (?) just sitting there all the time on my little 2 GB RAM machine, which is what I'm trying to avoid. I spent much of the day trying various scripts, commands and such with the udev rules to auto-mount the USB sticks, and could not get it to work except to be mounted by and for root. I have a working script solution that I'll just have to live with and use.
-
Yes, I CAN use "udiskie" to auto-mount my USB sticks. It just takes up ~25 MB (?) just sitting there all the time on my little 2 GB RAM machine, which is what I'm trying to avoid. I spent much of the day trying various scripts, commands and such with the udev rules to auto-mount the USB sticks, and could not get it to work except to be mounted by and for root. I have a working script solution that I'll just have to live with and use.
-
Thanks, Roland, BUT -- not only did that not work for me, it caused me not to be able to boot my HP Stream 13 notebook running MX Linux 23.5 Fluxbox edition. I finally waited long enough during the boot to see a message about a "timeout waiting for dev-sda.device...." I had to plug in a bootable USB linux and edit the /etc/fstab -- first thinking I must have flubbed the syntax or didn't have a CRLF at the end of the line or something. THEN I saw the comment at the top of the file: # Pluggable devices...
-
-
Thanks, Roland! I guess I didn't (still don't) know how to use the mount tool. I DID try it and could not get it to work for me. FWIW, the main environment this is a bigger issue for me is in an MX Linux install on an HP Stream 13 notebook, which has a non-upgradable 2 GB RAM. On that machine, I don't keep anything always running like daemonized Thunar or udiskie. The way I've been doing this is by making a bookmark to /dev/disks/by-uuid and when a USB stick is plugged in, it shows up there. I click...
-
Thanks, Roland! I guess I didn't (still don't) know how to use the mount tool. I DID try it and could not get it to work for me. FWIW, the main environment this is a bigger issue for me is in an MX Linux install on an HP Stream 13 notebook, which has a non-upgradable 2 GB RAM. On that machine, I don't keep anything always running like daemonized Thunar or udiskie. The way I've been doing this is by making a bookmark to /dev/disks/by-uuid and when a USB stick is plugged in, it shows up there. I click...
-
Just ran an example. Prior to mounting one of my partitions via script, xfe's memory footprint was 30.5 MB. After mount, it's 32.7 MB. Then, after using xfe unmount menu action, it's 33.3 MB. Did another one, went to 35 MB then 38.3 MB.
-
Memory leaks using scripts
-
Getting a ton of Java exceptions and finally an X system error trying to start up PM. See attached pm.out file for details.
1
