I have a Dell Latitude D610 running Linux Lite 3.8. My primary network connection is through a USB NIC dongle. See output following:

Bus 001 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The performance on the RTL dongle is good but when the system starts BIOS also starts up a PCI card with the old Dell b/g wireless connection. At restart, both of the wireless connections start and internet access slows substantially.  I have to manually disconnect the Dell card so that the dongle works properly.

I tried to switch off the WIFI in BIOS but then it also disables the RTL adapter and there is no network connection. Short of removing the original Dell WIF card, is there a way to disable it at login so that I just use the USB RTL adapter?

Thanks for your help.

Hey Jerry,
I took your advice and bought a new SSD.  I even bumped up RAM to a whopping 3GB.  :
However boot time is still sloooooooooooooow!

Here's the current analysis:

systemd-analyze blame
    1min 11.601s plymouth-quit-wait.service
        40.464s vboxadd.service
        31.669s lightdm.service
          5.029s NetworkManager-wait-online.service
          3.071s dev-sda1.device
          1.036s networkd-dispatcher.service
          875ms ufw.service
          756ms motd-news.service
          739ms lm-sensors.service
          714ms networking.service
          567ms upower.service
          546ms udisks2.service
          540ms apparmor.service
          525ms NetworkManager.service
          507ms systemd-rfkill.service
          487ms apport.service
          469ms grub-common.service
          442ms systemd-udev-trigger.service
          415ms keyboard-setup.service
          373ms pppd-dns.service
          371ms ModemManager.service
          367ms thermald.service
          355ms accounts-daemon.service
          354ms ubiquity.service
          332ms systemd-udevd.service
          330ms gpu-manager.service
          308ms systemd-journald.service
          290ms swapfile.swap
          279ms rsyslog.service
          269ms systemd-journal-flush.service
          222ms wpa_supplicant.service
          210ms avahi-daemon.service
          178ms systemd-resolved.service
          178ms systemd-modules-load.service
          164ms systemd-timesyncd.service
          145ms systemd-logind.service
          129ms lvm2-monitor.service
          120ms smbd.service
          109ms packagekit.service
          100ms [email protected]
          100ms systemd-sysctl.service
            93ms nmbd.service
            90ms polkit.service
            70ms blk-availability.service
            67ms dev-mqueue.mount
            65ms systemd-tmpfiles-setup.service
            64ms dev-hugepages.mount
            59ms systemd-remount-fs.service
            55ms kmod-static-nodes.service
            53ms sys-kernel-debug.mount
            40ms hddtemp.service
            39ms systemd-tmpfiles-setup-dev.service
            38ms plymouth-start.service
            37ms dns-clean.service
            35ms systemd-random-seed.service
            34ms iio-sensor-proxy.service
            32ms resolvconf.service
            31ms console-kit-daemon.service
            30ms systemd-user-sessions.service
            27ms console-setup.service
            27ms sys-kernel-config.mount
            27ms systemd-update-utmp.service
            27ms systemd-tmpfiles-clean.service
            26ms resolvconf-pull-resolved.service
            25ms sys-fs-fuse-connections.mount
            21ms bluetooth.service
            19ms openvpn.service
            16ms plymouth-read-write.service
            14ms console-kit-log-system-start.service
            13ms ureadahead-stop.service
            13ms systemd-backlight@backlight:acpi_video0.serv
            8ms systemd-backlight@backlight:intel_backlight.
            8ms systemd-update-utmp-runlevel.service
            7ms rtkit-daemon.service
            7ms setvtrgb.service
lines 60-75/75 (END)
            27ms console-setup.service
            27ms sys-kernel-config.mount
            27ms systemd-update-utmp.service
            27ms systemd-tmpfiles-clean.service
            26ms resolvconf-pull-resolved.service
            25ms sys-fs-fuse-connections.mount
            21ms bluetooth.service
            19ms openvpn.service
            16ms plymouth-read-write.service
            14ms console-kit-log-system-start.service
            13ms ureadahead-stop.service
            13ms systemd-backlight@backlight:acpi_video0.serv
            8ms systemd-backlight@backlight:intel_backlight.
            8ms systemd-update-utmp-runlevel.service
            7ms rtkit-daemon.service

systemd-analyze critical-chain
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha

graphical.target @1min 13.708s
└─lightdm.service @42.038s +31.669s
  └─systemd-user-sessions.service @2.034s +30ms
    └─network.target @2.028s
      └─NetworkManager.service @1.502s +525ms
        └─dbus.service @1.392s
          └─basic.target @1.258s
            └─paths.target @1.258s
              └─resolvconf-pull-resolved.path @1.250s
                └─sysinit.target @1.234s
                  └─systemd-backlight@backlight:intel_backlig
                    └─system-systemd\x2dbacklight.slice @2.32

Any suggestions?

Hi all,
I'm new to LL. I needed to get an old laptop running to use as an audio player -- tried Mint and a couple of other flavours, but LL is the only distro that the wifi would work with. Now I'm up and running. Very straight forward.

Disclaimer - I'm playing around with VMs (using KVM on unRAID, if anybody cares) so there's nothing at stake here - I can wipe & reinstall without any issue.
I did a standard install of LL4 (to ext4) with no issues.  I then did a non-standard install to a BTRFS partition because I wanted to play around with Timeshift.
While the ext4 based install boots just fine, I find that the BTRFS install starts with the following message:

Quote:error: sparse file not allowed.
Press any key to continue...

Hi All,
My user name is charvie from the Philippines. New to the forum but a LL user since 3.2. Right now I have 3 machines running LL 4.0.

Yesterday I did an Install Updates on two of my computers. Both are running Lite 4.0. One computer has a Foxconn mb with an intel d2500 cpu and the other a china made oem mb with a AMD A4. On both machines after the update and reboot the boot process stopped short of completing until I moved the mouse or tapped some keys on the keyboard. The machines work normally once the bootup finishes.  If I change back to the previous kernel through the grub startup menu, (one was running -22, the other -23), they both come up normally.  For now I have changed the grub default so they bootup on the old kernel but not deleted the -24 kernel from the machines so that I can continue to install updates without -24 kernel becoming the default again.

Hi to everyone i made live linux lite usb and when i watched youtube video on preinstalled firefox i noticed horizontal screen tearing on video. Is that possible to solve??
Im asking because i want to replace windows 7 with linux lite in near future.

After installing 3.4 and deleting all my files I cannot open any programs(when I click on them the cursor changes like its trying to open then it goes back to an arrow and nothing happens.I can open my system files and terminal but thats it.I did the updates with install and that may be the problem, when I first installed 3.4 (when it first came out) everything worked properly except boot up(I always had to go to advanced options, update grub and restart) but it would work afterwards.I tried accessing some previous kernels but they didn't work either and since I was using another machine primarily I was just using this one as a back up but now it is useless.

Hi, I dont know how it describe.

I installed new version 4.0 couple days ago and I am facing with weird graphic issues (icons,cursors,etc).

I am adding some printscreen and I hope you will help me.

Thanks

Hi, all,

I've searched the manual and forum but with no joy.

I'm wondering whether it is worth downloading and burning a couple of CDs/DVDs as part of covering contingencies around security and disaster recovery.  From the little I've been able to glean online (still being relatively new to Linux), there are a couple of options which may be relevant to my needs.  But I'm hoping someone else has already thought about this.  My set up is perhaps a little unusual, in that I have opted for full-HD encryption at installation because I am using laptops.  I should stress, that at this time I am having no problems with my installations - I'm just thinking ahead.

1)  In the event that LL won't boot from HD, is it worth having a bootable disaster recovery USB, CD or DVD?  Would the Live USB / DVD perform this function anyway?  One option looks like it could be, for example, SystemRescueCD.

2)  In the event that I suspect malicious activity - or to routinely audit outside of booting from the HD installation - is it worth having a bootable security/auditing USB, CD or DVD?  In this instance I am thinking about Auditor, for example.

3)  Alternatively, might I be able to burn LL 3.6 or LL 3.8 live USB or DVD using systemback having built a bespoke system on my test unit?  If so, which programs would others think good to install?  Note that my personal preference is to restrict downloads to the official repos.

Many thanks,
Ian