Confirm SCSI Controller Card Detection https://askubuntu.com/questions/1564045/confirm-scsi-controller-card-detection

Im running Ubuntu 18.04, not sure if SCSI Support is in the kernel of this version or not, if not please let me know.

I have a PCI AHA-2940w SE Legacy SCSI Controller Card Installed on the ISA PCI Slot of a legacy MB Gigatebyte X58A-UD3R.

LSPCI is identifying it as (If I am correctly identifying the entry): Non-VGA unclassified device: Adaptec AIC-7880U (rev 01).

I have two Legacy Ultra320 drives that I need to get data off of and so I want to confirm the card is being detected correctly so I can see if I can get this drives to detect. But Im not really sure if its correctly addressed since the entry says unclassified device.

Im pretty sure I don't need to worry about BIOS because I am not booting from the drives, but I thought I would check. scroll-lock is not working at boot so I cant see if the device is being detected during POST because its scrolls to fast.

I checked DMESG but I dont see any detection for this card.

Any ideas on how to see/get this working?

The longer I leave my computer on, the more dropped frames I get when playing media. Can I fix this issue without rebooting? https://askubuntu.com/questions/1564043/the-longer-i-leave-my-computer-on-the-more-dropped-frames-i-get-when-playing-me

I'm on ubuntu 22.04.5 LTS, and I've noticed that the longer I leave my computer on, the more dropped frames I get when playing media. I've tested in both MPV and VLC, and the problem persists. However, it's instantly solved with a reboot. I was hoping someone could explain what might be causing this, and if there's a way to prevent dropped frames without needing to reboot. My best guess is that it's something to do with memory/cache building up and needing to be cleared? I'm somewhat of a beginner to Ubuntu, so I'd greatly appreciate a beginner friendly explanation from anyone who can offer one.

I'm attempting to install Ubuntu on my Lenovo G51 Laptop (51 35 not a think pad) https://askubuntu.com/questions/1564041/im-attempting-to-install-ubuntu-on-my-lenovo-g51-laptop-51-35-not-a-think-pad

I haven't been able to to even start booting. The BIOS is different than the Think Pads I've had before. I am hoping that installing with Etcher will help.

How do I install Etcher on my usb drive?

Should I download Ubuntu onto the same usb drive?

. 
Thunderbird will not Connect email Error 12 Ubunto Noble Numbat https://askubuntu.com/questions/1564040/thunderbird-will-not-connect-email-error-12-ubunto-noble-numbat

Trying to use Thunderbird email system for several emails addresses. The Godaddy/Microsoft combination gives an error 12 when set up. The setup was done multiple times (adding and deleting the account, deleting passwords, etc.) trying many things. The data is

Incoming Imap outlook.office365.con 993 SSL/TLS OAuth2

Outgoing SMTP.office365.com 587 Starttls Oauth2

The account sets up and is confirmed but will not pass any data. Getting an error 12.
Godaddy is no help.

Gmail and yahoo accounts work great but not Godaddy. Any ideas??

Unable to boot from GRUB using chainloader and the efi path and also via chainloader +1 https://askubuntu.com/questions/1564038/unable-to-boot-from-grub-using-chainloader-and-the-efi-path-and-also-via-chainlo

I am trying to run an iso file off a USB. My system has dual-boot Ubuntu / Windows.

I press 'c' at GRUB and type: root=(cd0) # identity of USB based on ls -l chainloader /boot/efi/EFI/Boot/bootx64.efi

However, the efi file is not found although I know this is the correct path.

I have also tried "chainloader +1" and am informed "Invalid EFI file path" so perhaps the assumption above is incorrect somehow?

I also tried the standard hard drive (hd0,gpt5) but had the same error. My impression is that the path is often /EFI/boot/bootx64.efi but I do not appear to possess an /EFI directory.

Can anyone please suggest the solution - as I said I want to boot from the USB but it looks as if I cannot boot from any device manually in GRUB.

Long boot times https://askubuntu.com/questions/1564037/long-boot-times

Hi I need some help to improve boot times. I sit on the ubuntu splash screen for a long time and once I've logged in it takes another minute or two before I can even launch anything.

I am dual booting Ubuntu and Windows 11 for university.

1min 2.822s plymouth-quit-wait.service
    31.224s sys-devices-virtual-misc-rfkill.device
    31.224s dev-rfkill.device
    31.033s dev-ttyS1.device
    31.033s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
    31.026s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
    31.026s dev-ttyS0.device
    31.025s dev-ttyS3.device
    31.025s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
    31.025s dev-ttyS2.device
    31.025s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
    31.020s dev-ttyprintk.device
    31.020s sys-devices-virtual-tty-ttyprintk.device
    31.016s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
    31.016s dev-tpmrm0.device
    31.007s sys-module-fuse.device
    31.007s sys-module-configfs.device
    30.738s dev-disk-by\x2ddiskseq-9\x2dpart1.device
    30.738s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
    30.738s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-25fd10fb\x2d67de\x2d4f67\x2d9cae\x2d2a421ff77db8.device
    30.738s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-SYSTEM.device
    30.738s dev-disk-by\x2dpartuuid-25fd10fb\x2d67de\x2d4f67\x2d9cae\x2d2a421ff77db8.device
    30.738s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436\x2dpart1.device
    30.738s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4d5b89d9\x2dpart1.device
    30.738s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.1-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
    30.738s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
    30.738s dev-disk-by\x2dlabel-SYSTEM.device
    30.738s dev-nvme0n1p1.device
    30.738s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-66B4\x2dE825.device
    30.738s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436_1\x2dpart1.device
    30.738s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart1.device
    30.738s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
    30.738s dev-disk-by\x2duuid-66B4\x2dE825.device
    30.729s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4d5b89d9\x2dpart2.device
    30.729s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart2.device
    30.729s dev-nvme0n1p2.device
    30.729s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.1-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
    30.729s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
    30.729s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436\x2dpart2.device
    30.729s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436_1\x2dpart2.device
    30.729s dev-disk-by\x2ddiskseq-9\x2dpart2.device
    30.729s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
    30.729s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
    30.729s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-f7c9ef6a\x2dfdce\x2d428d\x2d9da6\x2d3427922d3773.device
    30.729s dev-disk-by\x2dpartuuid-f7c9ef6a\x2dfdce\x2d428d\x2d9da6\x2d3427922d3773.device
    30.724s dev-disk-by\x2duuid-b9c709f4\x2d48b9\x2d4860\x2d859f\x2d7c78b45831fd.device
    30.724s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4d5b89d9\x2dpart6.device
    30.724s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart6.device
    30.724s dev-nvme0n1p6.device
    30.724s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-b9c709f4\x2d48b9\x2d4860\x2d859f\x2d7c78b45831fd.device
    30.724s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-6.device
    30.724s dev-disk-by\x2ddiskseq-9\x2dpart6.device
    30.724s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436_1\x2dpart6.device
    30.724s dev-disk-by\x2dpartuuid-e6f8a62e\x2d4f95\x2d48b9\x2dbe41\x2d7e51b5857f34.device
    30.724s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.1-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p6.device
    30.724s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-e6f8a62e\x2d4f95\x2d48b9\x2dbe41\x2d7e51b5857f34.device
    30.724s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436\x2dpart6.device
    30.720s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4d5b89d9.device
    30.720s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.1-10000:e1:00.0-nvme-nvme0-nvme0n1.device
    30.720s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436.device
    30.720s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436_1.device
    30.720s dev-disk-by\x2ddiskseq-9.device
    30.720s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1.device
    30.720s dev-nvme0n1.device
    30.719s dev-disk-by\x2dpartuuid-0747e19f\x2de332\x2d4ac1\x2daaab\x2d9af26d645335.device
    30.719s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-OS.device
    30.719s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart3.device
    30.719s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
    30.719s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.1-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
    30.719s dev-disk-by\x2dlabel-OS.device
    30.719s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4d5b89d9\x2dpart3.device
    30.719s dev-disk-by\x2duuid-7C26B69E26B658BA.device
    30.719s dev-nvme0n1p3.device
    30.719s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436_1\x2dpart3.device
    30.719s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-0747e19f\x2de332\x2d4ac1\x2daaab\x2d9af26d645335.device
    30.719s dev-disk-by\x2ddiskseq-9\x2dpart3.device
    30.719s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436\x2dpart3.device
    30.719s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-7C26B69E26B658BA.device
    30.715s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-2EAC\x2d5D11.device
    30.715s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436_1\x2dpart5.device
    30.715s dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436\x2dpart5.device
    30.715s dev-nvme0n1p5.device
    30.715s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart5.device
    30.714s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-5.device
    30.714s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-27b0d2f3\x2d9479\x2d4066\x2dae6b\x2d7dfe83987ec3.device
    30.714s dev-disk-by\x2ddiskseq-9\x2dpart5.device
    30.714s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-MYASUS.device
    30.714s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.1-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p5.device
    30.714s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
    30.714s dev-disk-by\x2duuid-2EAC\x2d5D11.device
    30.714s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
    30.714s dev-disk-by\x2dlabel-MYASUS.device
    30.714s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4d5b89d9\x2dpart5.device
    30.714s dev-disk-by\x2dpartuuid-27b0d2f3\x2d9479\x2d4066\x2dae6b\x2d7dfe83987ec3.device
    30.436s dracut-initqueue.service
      641ms NetworkManager.service
      628ms dev-disk-by\x2duuid-EE1621A51621702F.device
      628ms dev-disk-by\x2ddiskseq-9\x2dpart4.device
      628ms dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-4.device
      628ms sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.1-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
      628ms dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-e0b1b6a7\x2d3f1a\x2d4dda\x2db1bf\x2d54938ca8c235.device
      628ms dev-disk-by\x2dpartuuid-e0b1b6a7\x2d3f1a\x2d4dda\x2db1bf\x2d54938ca8c235.device
      628ms dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436\x2dpart4.device
      628ms dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-RECOVERY.device
      628ms dev-disk-by\x2dlabel-RECOVERY.device
      628ms dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4d5b89d9\x2dpart4.device
      628ms dev-disk-by\x2did-nvme\x2dWD_PC_SN5000S_SDEQNSJ\x2d512G\x2d1002_250301809436_1\x2dpart4.device
      628ms dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart4.device
      628ms dev-nvme0n1p4.device
      628ms dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-EE1621A51621702F.device
      383ms snapd.seeded.service
      283ms initrd-switch-root.service
      281ms thermald.service
      280ms snapd.service
      194ms kdump-tools.service
      179ms apport.service
      166ms avahi-daemon.service
      165ms bluetooth.service
      151ms udisks2.service
      146ms dbus.service
      139ms networkd-dispatcher.service
      137ms polkit.service
      134ms accounts-daemon.service
      127ms user@1000.service
      125ms chrony.service
      109ms switcheroo-control.service
      106ms systemd-journal-flush.service
       88ms apparmor.service
       85ms rsyslog.service
       83ms gdm.service
       80ms systemd-udevd.service
       80ms upower.service
       78ms lm-sensors.service
       78ms update-notifier-download.service
       75ms systemd-udev-trigger.service
       74ms preload.service
       74ms gpu-manager.service
       62ms grub2-common.service
       59ms secureboot-db.service
       58ms snapd.apparmor.service
       58ms systemd-resolved.service
       55ms grub-initrd-fallback.service
       53ms boot-efi.mount
       53ms dracut-shutdown.service
       53ms snap-bare-5.mount
       52ms snap-core22-2216.mount
       51ms snap-core22-2292.mount
       50ms e2scrub_reap.service
       50ms ModemManager.service
       45ms power-profiles-daemon.service
       44ms systemd-logind.service
       43ms plymouth-read-write.service
       43ms systemd-fsck@dev-disk-by\x2duuid-66B4\x2dE825.service
       42ms systemd-timedated.service
       41ms snap-core24-1267.mount
       40ms snap-core24-1349.mount
       38ms packagekit.service
       38ms snap-desktop\x2dsecurity\x2dcenter-59.mount
       37ms snap-desktop\x2dsecurity\x2dcenter-99.mount
       36ms systemd-hostnamed.service
       36ms colord.service
       36ms dracut-cmdline.service
       35ms snap-firefox-7720.mount
       35ms snap-firefox-7766.mount
       33ms snap-firmware\x2dupdater-167.mount
       32ms sysstat.service
       32ms snap-firmware\x2dupdater-210.mount
       31ms systemd-oomd.service
       30ms snap-gnome\x2d42\x2d2204-226.mount
       30ms snap-gnome\x2d42\x2d2204-247.mount
       29ms dev-loop24.device
       29ms dev-loop20.device
       29ms dev-loop25.device
       29ms dev-loop26.device
       29ms snap-gnome\x2d46\x2d2404-145.mount
       28ms dev-loop22.device
       28ms dev-loop23.device
       28ms dev-loop19.device
       28ms snap-gnome\x2d46\x2d2404-153.mount
       28ms dev-loop21.device
       27ms dev-loop18.device
       27ms snap-gtk\x2dcommon\x2dthemes-1535.mount
       26ms dev-loop13.device
       26ms dev-loop16.device
       26ms dev-loop17.device
       26ms snap-localsend-32.mount
       26ms dev-loop7.device
       26ms dev-loop14.device
       25ms systemd-journald.service
       25ms dev-loop15.device
       25ms dev-loop11.device
       25ms dev-loop12.device
       25ms cups.service
       24ms dev-loop6.device
       24ms dev-loop5.device
       24ms dev-loop10.device
       24ms dev-loop9.device
       23ms snap-mesa\x2d2404-1165.mount
       23ms dev-loop4.device
       23ms wpa_supplicant.service
       23ms dev-loop2.device
       23ms dev-loop3.device
       23ms systemd-rfkill.service
       22ms initrd-parse-etc.service
       22ms dev-loop0.device
       22ms dev-loop8.device
       22ms dev-loop1.device
       21ms plymouth-switch-root.service
       21ms snap-prompting\x2dclient-104.mount
       20ms snapd.socket
       20ms modprobe@configfs.service
       20ms systemd-battery-check.service
       20ms snap-snap\x2dstore-1270.mount
       20ms systemd-binfmt.service
       19ms snap-snap\x2dstore-1300.mount
       19ms console-setup.service
       18ms openvpn.service
       18ms systemd-tmpfiles-setup.service
       18ms snap-snapd-25577.mount
       18ms plymouth-start.service
       17ms alsa-restore.service
       17ms modprobe@fuse.service
       17ms systemd-user-sessions.service
       17ms dracut-pre-udev.service
       17ms dracut-pre-mount.service
       17ms snap-snapd-25935.mount
       17ms initrd-udevadm-cleanup-db.service
       16ms setvtrgb.service
       16ms user-runtime-dir@1000.service
       16ms dev-hugepages.mount
       16ms snap-snapd\x2ddesktop\x2dintegration-315.mount
       16ms dev-mqueue.mount
       15ms run-lock.mount
       15ms snap-snapd\x2ddesktop\x2dintegration-343.mount
       14ms sys-kernel-debug.mount
       14ms sys-kernel-tracing.mount
       14ms modprobe@efi_pstore.service
       14ms snap-thunderbird-933.mount
       13ms snap-thunderbird-959.mount
       13ms tmp.mount
       12ms systemd-fsck-root.service
       12ms systemd-tmpfiles-setup-dev-early.service
       12ms systemd-backlight@backlight:intel_backlight.service
       11ms systemd-remount-fs.service
       10ms proc-sys-fs-binfmt_misc.mount
       10ms systemd-sysctl.service
        9ms keyboard-setup.service
        8ms kmod-static-nodes.service
        8ms systemd-backlight@leds:asus::kbd_backlight.service
        8ms rtkit-daemon.service
        8ms initrd-cleanup.service
        8ms modprobe@drm.service
        7ms swap.img.swap
        7ms systemd-modules-load.service
        6ms systemd-udev-load-credentials.service
        5ms systemd-random-seed.service
        5ms systemd-tmpfiles-setup-dev.service
        4ms ufw.service
        3ms sys-fs-fuse-connections.mount
GPU hang on Intel Alder Lake Xe (i915) with Chrome and VMware 3D accelerated under Ubuntu 24.04.4 https://askubuntu.com/questions/1564036/gpu-hang-on-intel-alder-lake-xe-i915-with-chrome-and-vmware-3d-accelerated-und

Hï,

I encountered GPU hang issues on Ubuntu 24.04.4 with an Intel Alder Lake Iris Xe (GT2) GPU. This affects both Chrome (GPU compositing) and VMware Workstation (3D accelerated graphics), and may impact other applications that use hardware graphics acceleration. Cela m'est arrivé après une mise à jour de mon PC ce matin, et quel mauvaise surprise d'être tombé pile au moment ou ubuntu 24.04.4...

At first, I thought this was related to a kernel update, but it wasn’t, since I kept the same kernel. My reasoning led me to believe it was likely related to a graphics driver… I’m far from an expert in this area, but I’ve summarized some information here that I hope will help others who might be in the same situation.

System and GPU info

uname -a
# Linux computer 6.11.0-29-generic

lspci -k | grep -A 3 VGA
# 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c)
#     Subsystem: Dell Alder Lake-UP3 GT2 [Iris Xe Graphics]
#     Kernel driver in use: i915
#     Kernel modules: i915, xe
  • Driver: i915 (manages Xe internally)
  • Xe is the GPU architecture, not a separate driver.

Debug flow

sudo dmesg | grep -i i915

Key excerpts for Chrome:

i915 0000:00:02.0: [drm] Found ALDERLAKE_P display version 13.00
i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0
i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[drm] GPU HANG: ecode 12:1:e75ffefe, in chrome [PID]
[drm] chrome[PID] context reset due to GPU hang
[drm] GPU HANG: ecode 12:1:e75ffefe, in main-mks [PID]
[drm] main-mks[PID] context reset due to GPU hang

These GPU HANG messages correspond to i915 context resets.

  • The kernel in use (6.11.0-29-generic) had been stable for several months and was not updated during my recent apt upgrade. In fact .. GPU hangs appeared after a recent the upgrade and reboot process.
  • This suggests the issue is not kernel-related, but likely related to i915/Mesa handling of Xe GPU features.

Remediation (workarounds)

Chrome:

VMware Workstation:

VMware Workstation unrecoverable error: (svga)
ISBRendererComm: Lost connection to mksSandbox (PID)
A log file is available in "/home/$HOME/vmware/<vm>.log".
You can request support using VMware support tools.

I’m not sure who to contact to get this fixed in i915 upstream, but feel free to forward this report to the relevant developers or community.

Problems with importing Firewall CA Certificate https://askubuntu.com/questions/1564035/problems-with-importing-firewall-ca-certificate

We have Sophos Firewall and need to import its CA certificate into the system’s Trusted CA store as websites give an "Untrusted Certificate Error" upon connecting to the VPN. The websites load normally after importing the same certificate in Windows machines.

Troubleshooting done so far:

  1. Copied the SSL_CA.crt file to the /usr/local/share/ca-certificates/ directory and running sudo update-ca-certificates, the output shows “1 added”

  2. Verified that the:

    • Certificate is present in: /usr/local/share/ca-certificates/

    • Certificate is a CA:

      • openssl x509 -in /usr/local/share/ca-certificates/SSL_CA.crt -text -noout --> CA:TRUE
    • Issuer is correct:

      echo | openssl s_client -connect github.com:443 -servername github.com 2>/dev/null | openssl x509 -noout -issuer
      
  3. Running quick diagnostic test using curl gave an error:

    $ curl https://google.com
    curl: (60) SSL certificate problem: self-signed certificate in certificate chain. More details here: https://curl.se/docs/sslcerts.html. 
    curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it.
    To learn more about this situation and how to fix it, please visit the web page mentioned above.
    
  4. We do not wish to bypass certificate validation, as this is not recommended:

    git config --global http.sslVerify false
    

The Workaround is to import the certificate in browser's Trusted Certificate and websites load correctly

But we face an untrusted server error in GitHub shiftkey:

GitHub Desktop cannot verify the identity of api.github.com. The certificate (*.github.com) is invalid or untrusted. This may indicate attackers are trying to steal your data.

What could be the root cause and the proper fix in this case? Because I believe the certificate is not being recognized/trusted by the system.

pulseaudio/pavucontrol on chromebook bookworm 12 for audacity [closed] https://askubuntu.com/questions/1564034/pulseaudio-pavucontrol-on-chromebook-bookworm-12-for-audacity

relative newb here on all issues linux. heres the problem; i used to use virtual cable in conjunction with audacity on windows; direct sound recording...worked a treat. im trying to set up similar on a lenovo chromebook (bookworm 12) and have had no luck pairing up pulse audio pavucontrol to do the same. i have downloaded pavu many times, via 'tarballs' and also flatpak, but it never goes to the app drawer, never an icon; its on the system but not accessible. can anyone with interminable patience suggest a few things i can try (long shot i know, but what the hell; good samaritans do exist...ya just gotta find 'em). many thanks to anyone who replies

Remote Desktop won't connect when Ubuntu PC is not connected to a screen https://askubuntu.com/questions/1564033/remote-desktop-wont-connect-when-ubuntu-pc-is-not-connected-to-a-screen

I use three PCs:

  1. A desktop PC running Ubuntu 25.10, using Wayland.

  2. A laptop running Ubuntu 24.04.

  3. A laptop running Windows 11.

I want to use Remote Desktop to connect to the PC 1 (the desktop running Ubuntu 25.10).

I use this KVM switch to switch my 24-inch screen between the three computers.

What I want to do is to have my big monitor screen attach to one of the laptops (PCs 2 or 3), and then connect from there to PC 1 using Remote Desktop.

My problem is that I can't connect using Remote Desktop to PC 1 unless the big monitor is connected to it. When I set the KVM switch to one of the laptops, there is no screen connected to the desktop (PC 1) and it doesn't allow RDP connections when that happens. It disconnects me as soon as I enter my credentials. Or if I'm using an existing RDP connection to the PC while it's displaying on the screen, it disconnects as soon as I switch my screen to another computer. Is there a setting to allow RDP connections without the screen attached?

Note: Not a duplicate of "Ubuntu 22.04 remote desktop headless?". That question is about connecting without having to login first. That's not my problem at all; I'm happy, if necessary, to login first and then connect remotely. My issue is how to connect when a screen is not connected to the PC, which the other question doesn't cover.

System stopped charging battery after sys upgrade https://askubuntu.com/questions/1564022/system-stopped-charging-battery-after-sys-upgrade

Well my old laptop is a Dell Latitude E6510

Current OS is Linux 6.8.0-94-generic

Ubuntu 22.04.5 LTS

Yesterday Feb 14 there was a small system upgrade. And after the upgrade the laptop will not charge the battery.

The battery is only 2 months old. With the power supply plugged into the laptop the percentage of the battery state is unchanged (52%).

I tried the Dell tricks but nothing.

Has anyone seen this ?

Regards

Bill Beck

SOLVED - Ubuntu Server 24.04 - kernel 6.17.0-14: Ethernet stopped working after 6 months https://askubuntu.com/questions/1564008/solved-ubuntu-server-24-04-kernel-6-17-0-14-ethernet-stopped-working-after

I have a Mini PC called Beelink Mini S12 that I use as Media Server. I has Ubuntu Server 24.04.4 LTS with 6.17.0-14-generic kernel on it.

I did all setups like 6 months ago and after that never had to touch it again. it was 100% working well and stable until yesterday when I was not able to connect into it anymore.

Today after some investigation I found that it had lost the Ethernet connect and as I was using it connected into my router via cable I lost the access. I re-enabled the WiFi temporally to be able to work on it until I found and fixed the issue with Ethernet, but after trying everything I'm still stuck and I don't have my Ethernet connection back.

Here is some prints from my setup/Ethernet:

Results of lsb_release –a:

Ubuntu/Kernel

My network interfaces:

interfaces

Network hardware Realtek RTL8111/8168/8211/8411:

realtek

Driver updated to use r8168-dkms:

driver

netplan that normally as only the Ethernet part and I leave the WiFi commented out:

netplan

I have no idea what is going as it was working before and I didn't update anything (at least not manually by myself).

Ubuntu Budgie, OpenRazer, and Secure Boot https://askubuntu.com/questions/1563684/ubuntu-budgie-openrazer-and-secure-boot

I recently cleared my laptop of Windows and installed Ubuntu Budgie 24.04.3 LTS. It is a 2018 Razer Blade 15 Adv. I have two problems.

  1. I installed OpenRazer, which also includes enrolling a MOK. It seems to randomly forget the MOK. It cannot load OpenRazer until I re-enroll the MOK again. Is there something that would remove the MOK automatically?

  2. Sometimes the system will lock up tight and I have to force reboot. The special key (PrtSc) to talk directly to the kernel doesn't work to reboot. I have to force power off. The special key works when not frozen. Also with this comes the MOK being removed from the boot and OpenRazer not loading. Where would I look to figure out what is causing these lock ups? I have checked the logs, but nothing jumps out.

How to install gcc-14 on Ubuntu 22.04 and 24.04? https://askubuntu.com/questions/1513160/how-to-install-gcc-14-on-ubuntu-22-04-and-24-04

I successfully used the instructions from https://linuxize.com/post/how-to-install-gcc-compiler-on-ubuntu-18-04/ to upgrade gcc version before, but they don't work for gcc-14. How do I install gcc-14 and g++-14 on Ubuntu 22.04 and 24.04?

Grub doesn't detect Windows 10 and os-prober shows no output (tried existing solutions) https://askubuntu.com/questions/1471899/grub-doesnt-detect-windows-10-and-os-prober-shows-no-output-tried-existing-sol

I'm facing an issue with Grub not detecting my Windows 10 installation. I have come across a similar question on this forum, but unfortunately, the suggested solutions haven't worked for me.

When I run sudo fdisk -l, the following output is displayed:

/dev/nvme0n1p1           2048    1187839   1185792   579M  7 HPFS/NTFS/exFAT
/dev/nvme0n1p2        1187840  832756596 831568757 396.5G  7 HPFS/NTFS/exFAT
/dev/nvme0n1p3      999071744 1000210431   1138688   556M 27 Hidden NTFS WinRE
/dev/nvme0n1p4      832757758  999071743 166313986  79.3G  5 Extended
/dev/nvme0n1p5 *    832757760  833808383   1050624   513M ef EFI (FAT-12/16/32)
/dev/nvme0n1p6      833810432  999071743 165261312  78.8G 83 Linux

I have already tried the following steps, as recommended in a similar question:

  • Reinstalling os-prober.
  • Updating Grub.
  • Disabling Secure Boot.

However, despite these attempts, Windows 10 is still not showing up in the Grub menu during boot.

I would greatly appreciate any further assistance or alternative solutions to resolve this issue.

[22.04][EHL] can not shutdown and reboot https://askubuntu.com/questions/1405223/22-04ehl-can-not-shutdown-and-reboot

I've installed Ubuntu 22.04 on EHL platform, when I trying to reboot or shutdown, system will hang up and could not shutdown or reboot. This issue also existed on 20.04 and 21.10. Is there anyone can help to resolve this issue?

Network Manager settings not sticking after reboot https://askubuntu.com/questions/1378885/network-manager-settings-not-sticking-after-reboot

I'm attempting to automatically establish a VPN connection after reboot. I created the profile via the network manager GUI and everything works well. I can use nm-connection-editor to edit the ethernet (and wifi) config to check the "Automatically connect to VPN." If I restart either interface (wlan0 or eth0), the VPN connection will be established.

When I reboot, however, the VPN connection is not established over eth0. When I re-run nm-connection-editor, the auto connect to VPN box is now unchecked. If I re-check it and restart the interface, the VPN is once again automatically established. Rebooting again reverts the setting. Each time I check that box after rebooting, a NEW config file is generated in /etc/NetworkManager/system-connections. It starts with netplan-eth0, then netplan- and gets a 1-up number with each new save.

netplan-eth0-626dd384-8b3d-3690-9511-192b2c79b3fd-1.nmconnection
netplan-eth0-626dd384-8b3d-3690-9511-192b2c79b3fd.nmconnection
netplan-eth0.nmconnection

The wireless connection actually works flawlessly. If I disable the wired connection and use only wifi, the VPN is established immediately upon rebooting.

All of my troubleshooting of netplan and all the options in NetworkManager have come up empty. I'm trying to set up a raspi to send to a relative and want it to establish a vpn connection by just plugging it in to ethernet, so I need it to work with the wired connection. Any help is appreciated.

Below is a paste of netplan-eth0.nmconnection. Note that it is the "secondaries" option that ties the VPN to this interface. If I had to guess, NetworkManager is ignoring this config for eth0 after rebooting.

[connection]
id=netplan-eth0
uuid=626dd384-8b3d-3690-9511-192b2c79b3fd
type=ethernet
interface-name=eth0
metered=2
permissions=
secondaries=f3f0c99a-c2c5-47fd-9bce-9104f3665dfc;
timestamp=1638470039

[ethernet]
mac-address-blacklist=
wake-on-lan=0

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=eui64
dns-search=
method=ignore
How would I know if I'm using PulseAudio, ALSA, or Jack? https://askubuntu.com/questions/1292895/how-would-i-know-if-im-using-pulseaudio-alsa-or-jack

Ubuntu 20.04.1 (upgraded from Ubuntu 16.04 -> 18.04 -> 20.04 if that matters)...

I have just done default install plus gnome-session-flashback and other non-audio related packages (Gimp, Blender, etc). Aside from Yoshimi soft synthesizer, I have not intentionally played with or installed any additional audio [things], whatever PulseAudio, ALSA, Jack are.

How would I know if I'm using PulseAudio, ALSA, or Jack? For example dmesg output mentions none of the three, where else do I check?

(needed to move along this question along, as per a follow-up question in the comments)

Windows SMB shares no longer accessible in Ubuntu 19.04 https://askubuntu.com/questions/1179846/windows-smb-shares-no-longer-accessible-in-ubuntu-19-04

Upon returning from a recent trip, my Ubuntu 19.04 autofs no longer mounts the cifs Windows 10 shares. When I click the Windows 10 machine in Nautilus under Other Locations, I get the error, Unable to access location, Failed to retrieve share list from server, Network dropped connection on reset. Does this have to do with SMB v1 and some Windows update? On my android phone, the file manager could also no longer connect to the Windows 10 machine, but after I installed an SMB v2 add-on, the phone can now connect to it. In my Ubuntu smb.conf file, I added min protocol = SMB2, but that did not fix it. Is there a way to get my autofs to mount the cifs shares again? I prefer to not go the fstab route, rather I want to keep using autofs if possible.

Duplicate screen on Nvidia not working https://askubuntu.com/questions/912139/duplicate-screen-on-nvidia-not-working

I have an issue with multi-screen on my new computer with Ubuntu 16.04.

My new computer is a Dell Inspiron 15 7000 Gaming. http://www.dell.com/fr/p/inspiron-15-7567-laptop/pd?oc=cn56705&model_id=inspiron-15-7567-laptop

I installed the proprietary driver for my Nvidia graphics card. I can switch between my Intel GPU and my Nvidia graphics card.

The problem is when I want to connect an other screen. First it only works when the Nvidia graphics card is selected, not the Intel GPU, but maybe that's normal.

Now with the Nvidia graphics card all work greatein mirror mode, but when I want to duplicate screen both displays are going to the wrong resolution with no mouse control on my primary screen and strange mouse control on duplicate screen (I can't make correct screenshot, but you can imagine what is a screen with a completely wrong resolution.

I have searched a lot for what going on and the only think I have found is that my built in screen have no settings in Nvidia Settings.

https://i.sstatic.net/lDWax.jpg

In this webpage I have found I see both configurations and not one:

Do you have any idea of what is wrong with my computer?

Other screenshot information and Xorg.conf and Xorg.0.log:

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
    BusID "PCI:0@0:2:0"
    Option "AccelMethod" "None"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Link to pastebin: https://pastebin.com/D4ckLAY3

Nvidia Quadro K2200 on Ubuntu 16.04.1 LTS Possible? https://askubuntu.com/questions/868071/nvidia-quadro-k2200-on-ubuntu-16-04-1-lts-possible

So I'm a n00bie to Ubuntu/Linux. I've been trying to get a Quadro K2200 to work with the most recent update to Ubuntu, due to my Windows installation causing me more grief than necessary. I've spent the past two weeks looking at tutorials, resources, etc. Is it even possible to get the K2200 to work with this version of Ubuntu? If so, does anybody know any tips or tricks to possibly get it to work from a clean installation? I know support is supposed to be rough around the edges for the Quadros but I've heard other people have gotten different cards in that series to work, so I'm not sure what's going on. Any assistance would be greatly appreciated.

How to get Ubuntu to recognize Nvidia GTX 860M graphics card? [duplicate] https://askubuntu.com/questions/838954/how-to-get-ubuntu-to-recognize-nvidia-gtx-860m-graphics-card

I just upgraded to Ubuntu 16.10 and my laptop has both an Intel GPU and Nvidia GTX 860M.

I know Ubuntu 15.10 recognized my card because I was creating images using the Processing application with image dimensions > 10K. Now I get an error saying the card is limited to 8192 as a max dimension.

Running the command lspci I get the following relevant output:

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)

Running the command glxinfo, I get the following relevant output:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Haswell Mobile  (0x416) OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile

When I run the command nvidia-settings I get the following text output:

(nvidia-settings:3831): WARNING:  
PRIME: Failed to execute child process "/usr/bin/prime-supported" (No such file or directory)
** Message: PRIME: is it supported? no

ERROR: nvidia-settings could not find the registry key file. This file
       should have been installed along with this driver at
       /usr/share/nvidia/nvidia-application-profiles-key-documentation. The
       application profiles will continue to work, but values cannot be
       prepopulated or validated, and will not be listed in the help text.
       Please see the README for possible values and descriptions. 

(nvidia-settings:3831): 
Gtk-CRITICAL: gtk_widget_get_preferred_width_for_height: assertion 'height >= 0' failed 
(nvidia-settings:3831): 
Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width 10 and height -5 
(nvidia-settings:3831): 
Gtk-CRITICAL **: gtk_widget_get_preferred_width_for_height: assertion 'height >= 0' failed 
(nvidia-settings:3831): 
Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 10 and height -5 
(nvidia-settings:3831): 
Gtk-CRITICAL **: gtk_widget_get_preferred_width_for_height: assertion 'height >= 0' failed (nvidia-settings:3831): 
Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 10 and height -5 
(nvidia-settings:3831): 
Gtk-CRITICAL **: gtk_widget_get_preferred_width_for_height: assertion 'height >= 0' failed 
(nvidia-settings:3831): 
Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 10 and height -5 
(nvidia-settings:3831): 
Gtk-CRITICAL **: gtk_widget_get_preferred_width_for_height: assertion 'height >= 0' failed 
(nvidia-settings:3831): 
Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 10 and height -2

Addition: Here is the output of command lshw -C display.

 *-display UNCLAIMED
       description: 3D controller
       product: GM107M [GeForce GTX 860M]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a2
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress cap_list
       configuration: latency=0
       resources: memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f7000000-f707ffff
  *-display
       description: VGA compatible controller
       product: 4th Gen Core Processor Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 06
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:29 memory:f7400000-f77fffff memory:d0000000-dfffffff ioport:f000(size=64)

Here is a screenshot of the NVIDIA X Server Settings:

nvidia app screenshot

Second monitor detected but appear to be "off" https://askubuntu.com/questions/551683/second-monitor-detected-but-appear-to-be-off

I have been enjoying dual monitors using Xubuntu with Nvidia driver 340.58 for some time now. However, suddenly one of the monitors stops working. In nvidia-setting panel it just appears as "Off" and I couldn't change any settings.

Screenshot of nvidia-settings:

https://i.sstatic.net/FBFCR.png

And the result of xrandr says DP-1 was not disconnected but has no modes.

xrandr: Output DP-1 is not disconnected but has no modes
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
DVI-I-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm
   1920x1080      60.0*+
   1680x1050      60.0  
   1440x900       59.9  
   1280x1024      75.0     60.0  
   1280x960       60.0  
   1280x800       59.8  
   1280x720       60.0  
   1152x864       75.0  
   1024x768       75.0     70.1     60.0  
   800x600        75.0     72.2     60.3     56.2  
   640x480        75.0     59.9  
DP-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected (normal left inverted right x axis y axis)

Any idea what might cause the problem?

make command not working ERROR 2 https://askubuntu.com/questions/501115/make-command-not-working-error-2

I was trying to install Realtek_RTS5229_Linux_Driver_v1.07 which I downloaded from [here][1]

When I run the make command I get the following error:-

make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-32-generic'
make: *** [LINUX] Error 2

I have 64 bit Ubuntu 12.04 LTS installed.

Permission when running script in Vagrant using Vagrantfile https://askubuntu.com/questions/470690/permission-when-running-script-in-vagrant-using-vagrantfile

I have created a vagrant box for running rails applications and I have managed to create it manually.

My next step was to create a shell script that I can include in the Vagrantfile so when creating new boxes all installation will be done automatically.

But when I reach the line:

source ~/.bash_profile 

I get this error

mkdir: cannot create directory `/home/vagrant/.rbenv/shims': Permission denied
mkdir: cannot create directory `/home/vagrant/.rbenv/versions': Permission denied

Works fine from CLI

Any ideas?

UPDATE

I have fixed the mkdir error and the script runs from end to end with no apparent errors.

Now when I vagrant ssh and check my home directory I do not find any of the git repos I downloaded and installed using my script nor .bash_profile hence I can not rbenv

Any ideas why this may happen - what am I doing wrong?

vagrant@precise64:~$ ls -a
.   .bash_history    .cache          .profile  .sudo_as_admin_successful  .veewee_version
..  .bash_logout   .bashrc        postinstall.sh  .ssh      .vbox_version
vagrant@precise64:~$ 

this is setup.sh:

# Update sources:
sudo apt-get -y update

# Install development tools:
sudo apt-get -y install build-essential

# Packages required for compilation of some stdlib modules
sudo apt-get -y install tklib 

# Extras for RubyGems and Rails:
sudo apt-get -y install zlib1g-dev libssl-dev

# Readline Dev on Ubuntu:
sudo apt-get -y install libreadline-gplv2-dev

# Install some nokogiri dependencies:
sudo apt-get -y install libxml2 libxml2-dev libxslt1-dev

# Install Git
sudo apt-get -y install git-core 

# Install Sqlite
sudo apt-get -y install sqlite3 libsqlite3-dev 

# Install Make
sudo apt-get -y install make

# Install NodeJS (Required for Rails)
sudo apt-get -y install python-software-properties
sudo add-apt-repository -y ppa:chris-lea/node.js
sudo apt-get -y update
sudo apt-get -y install curl nodejs

# Install RBENV
git clone https://github.com/sstephenson/rbenv.git ~/.rbenv
touch ~/.bash_profile
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile
echo 'eval "$(rbenv init -)"' >> ~/.bash_profile
source ~/.bash_profile

# Install Ruby 2.1.0
git clone https://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build

sudo sh ~/.rbenv/plugins/ruby-build/install.sh
rbenv install 2.1.0
rbenv rehash
rbenv global 2.1.0

# Install gems for Rails
# gem install rdoc
gem install bundler
# gem install rake 
gem install sqlite3 -v '1.3.9'
gem install rails
rbenv rehash

Many thanks in advance.

Ubuntu 14.04 DVD drive won't work https://askubuntu.com/questions/459105/ubuntu-14-04-dvd-drive-wont-work

I just got a new DVD drive that I know works because it live boots another distribution. When I put a dvd into the drive it repeatedly tries and fails to spin up, and Ubuntu doesn't recognize that there is a dvd in the drive.

Here is the lshw output with:

No dvd in the drive:

*-cdrom
         description: DVD reader
         product: CDW/DVD TS-L462C
         vendor: TSSTcorp
         physical id: 0.0.0
         bus info: scsi@0:0.0.0
         logical name: /dev/cdrom
         logical name: /dev/sr0
         version: TO10
         capabilities: removable audio cd-r cd-rw dvd
         configuration: ansiversion=5 status=nodisc

With a dvd in the drive:

*-cdrom
         description: DVD reader
         product: CDW/DVD TS-L462C
         vendor: TSSTcorp
         physical id: 0.0.0
         bus info: scsi@0:0.0.0
         logical name: /dev/cdrom
         logical name: /dev/sr0
         version: TO10
         capabilities: removable audio cd-r cd-rw dvd
         configuration: ansiversion=5 status=nodisc

What should I do to get it running correctly?

How do I install Catalyst drivers for ATI Mobillity Radeon X1400 in 12.04? https://askubuntu.com/questions/317106/how-do-i-install-catalyst-drivers-for-ati-mobillity-radeon-x1400-in-12-04

I'm trying to install drivers in Ubuntu 12.04 for my ATI Mobility Radeon X1400 and haven't worked out how to yet. I'm not new to Ubuntu but now that I want to play TF2 on it I need Catalyst. Can someone please tell me how to do this, thanks.

How to send terminal command to a TTY terminal https://askubuntu.com/questions/194293/how-to-send-terminal-command-to-a-tty-terminal

I am looking for a way to send an executed command to a TTY terminal. For example, let us say that I open the gnome-terminal and on the window I type sudo aptitude update && sudo aptitude upgrade.

How can I send this to a TTY terminal instead of working with it in the TTY7 GUI environment?

Wireless not working on desktop with Asus USB-N13 (B1) wireless adapter https://askubuntu.com/questions/186829/wireless-not-working-on-desktop-with-asus-usb-n13-b1-wireless-adapter

I am trying to connect my desktop to a wireless network. I have purchased an ASUS USB-N13 B1 adapter. I have followed instructions for installing drivers and disabling conflicting drivers. I have thoroughly searched and could not find a solution. The adapter is recognized and powered on. I have entered the ssid and password information into the wireless network configuration. Other machines can connect to this wireless network, and the machine can connect online via ethernet without issue. Here is the output of some commands which summarize my configuration, and might give some clues :

~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"

~$ uname -a                                                                               
Linux petra 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

~$ lsusb                                                
Bus 001 Device 006: ID 0b05:17ab ASUSTek Computer, Inc.

~$ dmesg
[ 1883.823150] wlan0: authenticate with 48:5b:39:e7:25:5e (try 1)
[ 1884.020027] wlan0: authenticate with 48:5b:39:e7:25:5e (try 2)
[ 1884.220025] wlan0: authenticate with 48:5b:39:e7:25:5e (try 3)
[ 1884.420023] wlan0: authentication with 48:5b:39:e7:25:5e timed out

Any assistance would be appreciated as I have been trying to get this machine online for several weeks now to no avail.

Sincerely, Michael.

Update : running some commands to test for a blocked wireless adapter, as suggested in the answers, seems to indicate that blocking is not the problem

~$ rfkill list all                                                             
1: phy1: Wireless LAN
    Soft blocked: no
    Hard blocked: no
~$ rfkill unblock all                                                          
~$ sudo service network-manager restart                                        
network-manager stop/waiting
network-manager start/running, process 3839

The system periodically prompts me to re-enter the network password, despite never successfully connecting. I am not making any errors in entering the network information. This network has a repeater. Is it possible that the repeater is somehow causing a problem with the connection, by having two hardware devices for the same network?

Any additional help would be greatly appreciated

Update :

Changed the wireless setup to WPA ( used to be WEP ). This seems unlikely to be the root of the problem but at least WPA is more secure. After this change, and disabling ipv6, I feel that the system is closer to working. Now, network manager will start on startup even if the machine is not plugged in to a wired connection. Wireless seems to start and I can see several of the networks available in my area. Also, it will try to connect to the network about 3 times ( prompting for a password each time ). After the third time, it gives up and disables wireless.

Some guesses then, are: -- signal strength is too low. this is unlikely as the problem persists even with the repeater very near the adapter -- confusion relating to the repeater : two sources with different mac addresses? perhaps it is alternately trying to connect to the main router and the repeater or something, and getting confused ? -- configuration or driver problems ? -- device is just plain broken ?

Some interesting behavior that may help get to the root of the problem. If I start up the computer with both the wireless adapter and a wired connection to the repeater, I am able to get internet connectivity, even after disconnecting the wired connection. However, this wired connection seems to be necessary to initiate a working wireless connection, as the machine cannot connect until the wired connection is first established.

If I reboot the machine, connectivity is lost. If I reboot the repeater, connectivity is also lost.

Update : cross posted to ubuntu forums, but no new information there yet. I'm going to try stepping through the installation process from the beginning again. ( I had some more updates but they were lost due to unreliable internet connectivity, basically, re-installing from scratch failed due to compile errors and none of several fixes that I found worked )

You would think that this would be a good sign, but there is no wireless connectivity:

wlan0     IEEE 802.11bg  ESSID:"[[REDACTED]]"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 48:5B:39:E7:25:5E   
          Bit Rate:54 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=100/100  Signal level=100/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Update : I don't know why, but if I boot without the wired connection and then run

sudo service network-manager restart

once the computer starts up, I seem to get a wireless connection. So, it looks like its just a matter of making sure the wireless starts correctly. I'm not sure how to explain other behaviors, but I feel like I'm closer to a solution.

What's the absolute path of an icon declared in a .desktop file? https://askubuntu.com/questions/66396/whats-the-absolute-path-of-an-icon-declared-in-a-desktop-file

In a .desktop file you can declare an icon, however it's not clear how this translates to an icon on disk:

Icon=eric  

Where on the filesystem can I find this icon?

Related to this question: