removing drivers to trim memory usage

Forum Forums General Tips and Tricks removing drivers to trim memory usage

This topic contains 7 replies, has 3 voices, and was last updated by BobC Jun 20-9:27 pm.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #23469
    Member
    linuxdaddy
    linuxdaddy

    This has to be done on a per-machine install basis not a live usb
    that gets taken from pc 2 pc. Overall ram usage is lower to due to
    them not getting loaded. This helps making an isosnapshot smaller and
    a live-persistant usb for a particular pc.

    1: In a terminal using the lspci command
    or using inxi -Fxz make a note of which drivers are
    being used.

    2: Open synaptic and do a search for the firmware and remove the ones
    the pc doesn’t need. Then do another search for xservers and remove all
    the extra video drivers that aren’t being used. I left the vesa, intel,
    and fbdev ones on mine. Be sure to leave fbdev as the kernel loading uses it.
    I also removed the amd-microcode package since This cpu is intel.
    If the cpu is AMD then you could remove the intel-micrcode package.
    Doing a search for printer-driver and removing the ones not needed can
    trim space on a iso or usb-persist as well.

    3: Apply and reboot.

    4: Enjoy seeing the memory usage for overall alot lower in sudo ps_mem.py

    • This topic was modified 4 months, 3 weeks ago by linuxdaddy. Reason: added printer removal

    Normal == 🙂
    depends on the surrounding crowd ?!

    #23501
    Member
    Avatar
    BobC

    I will try this when I can get the apt-get update to work again. Its been failing for a week now.

    • This reply was modified 4 months, 3 weeks ago by BobC.
    #23506
    Member
    linuxdaddy
    linuxdaddy

    Hi BobC,

    see if changing the repo will let you update. It
    might be that server having issues.

    Normal == 🙂
    depends on the surrounding crowd ?!

    #23524
    Member
    Avatar
    BobC

    anti suggested that, but I wouldn’t know what to change it to. Its the debian servers that are failing all the time. This is running 19b1, BTW.

    $ sudo apt-get update
    [sudo] password for bobc:
    Hit:1 http://mirrors.rit.edu/mxlinux/mx-packages/antix/buster buster InRelease
    Get:2 http://ftp.us.debian.org/debian buster-updates InRelease [46.8 kB]
    Get:3 http://ftp.us.debian.org/debian buster InRelease [163 kB]
    Get:4 http://security.debian.org buster/updates InRelease [39.1 kB]
    Reading package lists… Done
    E: Release file for http://ftp.us.debian.org/debian/dists/buster-updates/InRelease is not valid yet (invalid for another 2h 50min 16s). Updates for this repository will not be applied.
    E: Release file for http://ftp.us.debian.org/debian/dists/buster/InRelease is not valid yet (invalid for another 2h 50min 15s). Updates for this repository will not be applied.
    E: Release file for http://security.debian.org/dists/buster/updates/InRelease is not valid yet (invalid for another 4h 46min 25s). Updates for this repository will not be applied.
    bobc@Dell-i7-7559:~

    • This reply was modified 4 months, 3 weeks ago by BobC.
    #23526
    Member
    Avatar
    skidoo

    FWIW, during last weekend I had intermittent problems connecting to those same repo servers (not same as your “not valid until” errormsg), but no problems during past 2 days.

    but I wouldn’t know what to change…

    Based on past experiences, I’d suspect the l’il coin battery for CMOS hardware clock is kaput…

    startpage.com
    query: debian release file is not valid yet. Updates for this repository will not be applied
    filter: results from past month, results from past week…

    [ a cursory search finds no wave of recent bugreports mentioning “not valid until” ]

    This, from among the search results, advises using “date -s blahbla” (see date manpage for details)
    to manually adjust the time, then retry the apt update operation
    https://ahelpme.com/linux/ubuntu/ubuntu-apt-inrelease-is-not-valid-yet-invalid-for-another-151d-18h-5min-59s/

    #23527
    Member
    Avatar
    BobC

    I bet it has to do with the time on my PC. It says 7:47, but if I right click the clock and click UTC it changes to the correct time, 12:47.

    This is a newfangled, no removable battery, I7 laptop.

    In the boot setup screen the time is right, but linux thinks that time is the UTC time. The fix attempts below were run at 1:28 pm but linux thinks its 8:28 am

    any ideas????

    bobc@Dell-i7-7559:~
    $ sudo hwclock –debug
    [sudo] password for bobc:
    hwclock: use –verbose, –debug has been deprecated.
    2019-06-20 08:28:45.045097-05:00
    bobc@Dell-i7-7559:~
    $ sudo dpkg-reconfigure tzdata

    Current default time zone: ‘America/Chicago’
    Local time is now: Thu Jun 20 08:28:58 CDT 2019.
    Universal Time is now: Thu Jun 20 13:28:58 UTC 2019.

    bobc@Dell-i7-7559:~
    $ date -u
    Thu 20 Jun 2019 01:29:24 PM UTC
    bobc@Dell-i7-7559:~

    • This reply was modified 4 months, 3 weeks ago by BobC.
    #23541
    Member
    linuxdaddy
    linuxdaddy

    @BobC

    Your time says the same as mine for “date -u”.
    You could try to wrap the date command in with a wget to temporarily set the time
    in sync with the internet servers like in the screenshot … it allows this one
    with wrong utc times to still update. This one is also 19b1.

    Attachments:

    Normal == 🙂
    depends on the surrounding crowd ?!

    #23565
    Member
    Avatar
    BobC

    I hate to say this, but something I tried fixed it, but I don’t know which, because nothing was apparent at the time, and when I rebooted, the time in setup was off by 5 hours, so I fixed that, and now its correct in antiX, and apt-get update works, so I’m now able to add or remove packages again.

    LOL, I haven’t rebooted into Windoze, yet….

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.