Ever since I upgraded to Ubuntu 24.04.1, my wifi has disappeared and irregularly disconnects. I could only use the LAN cable to connect to the internet.
How can I fix this problem permanently?
I am using a custom-built PC with an ASUS motherboard. I am trying to get the audio working on my system. Currently I have no sound at all coming from my HDMI speakers (connected to my monitor).
I have uploaded Ubuntu several times and tried a few methods of solving the problem (such as using the Nvidia driver, loading the Nvidia control panel, and switching between pipewire and pulseaudio).
So far I have come up empty.
A web search provides dozens of possible solutions. Which one should I try?
Hardware Model: ASUS EX-B760M-V5 D4
Memory: 32.0 GiB
Processor: Intel Core i5-14400F × 16
Graphics: NV106
Disk capacity: 992.2 GB
Firmware version: 1402
OS name: Ubuntu 24.04.3 LTS
OS Build: (null)
OS Type: 64-bit
GNOME version: 46
Windowing system: Wayland
Kernel version: Linux 6.14.0-37-generic
NVIDIA GK208B GeForceGT710
Currently set on Nouveau display (nvidia-driver-470 listed as available)
I have had trouble with ZFS snapshots causing problems with ubuntu updates in the past and had to manually remove snapshots which was not easy.
Now it's not allowing me to update portainer because it can't remove the old container do to problems with the ZFS snapshots. People with the same issue had to start over from scratch but I would prefer not to do that as 2 of the containers (not portainer) were very difficult to setup.
Is there a way to convert to another fs ?
If not, the other way would be to create a new VM ubuntu with traditional FS and then while portainer is still running on old system migrate over.
I am not in a super hurry and this is not mission critical by any means but would prefer not to start over.
Thank you.
I'm running standard 'Ubuntu 25.10 Desktop' fully updated.
I just received an update for 'iperf3' (something i never heard of) and it asked if I wanted to run it as a demon at startup. As a fool I just clicked the tickbox and carried on.
From what I now understand, 'iperf3' is for performance testing of network connections. Is it necessary to run as a demon for a basic user. ie: someone who just checks email and surfs the web?
If not, how do i disable it from being run at startup? Is it part of standard Ubuntu or did I somehow install it inadvertently in the past?
Update: I've gone and checked 4 other installs I have access to and 3/4 have iperf3 installed but not active [service --status-all] shows them existing but they have a '-' in front of them. So I'm guessing it is a standard issue service.
As for stopping it run as a demon at startup, I used 'synaptic package manager' to do a 'complete removal' and then reinstalled it.
It is a bit of a brute force method, adjusting a setting would have been better & I still would like to know how.
Thanks.
I am hitting a wall trying to configure a dual GPU setup on a B550/Ryzen platform running Ubuntu. I am facing a persistent Memory Mapped I/O (MMIO) resource allocation issue where the kernel cannot assign BAR addresses for the second GPU, leading to can't assign; no space errors.
Hardware Specs:
CPU: AMD Ryzen 7 5800X
Mobo: B550 Chipset [INSERT YOUR MOTHERBOARD MODEL HERE]
GPU 1: NVIDIA RTX 4060
GPU 2: NVIDIA RTX 5060 (New gen)
PSU: 850W
OS: Ubuntu (Kernel 6.x generic)
Driver: Manual install of NVIDIA-Linux-x86_64-580.126.09.run (Required for 5060 support)
The Problem: When booting with default BIOS settings, only one GPU is enumerated correctly. The second GPU fails with BAR allocation errors in dmesg. When I attempt to fix this by enabling "Above 4G Decoding" in BIOS, the system fails to mount the NVMe drive or panics during boot unless I use specific kernel parameters, and even then, I lose the proprietary driver binding.
Logs & Symptoms:
1. The BAR Error (dmesg output): Without 4G decoding, the kernel clearly sees the device but cannot map the memory:
Bash
[ 0.666193] pci 0000:07:00.0: BAR 1 [mem size 0x10000000 64bit pref]: can't assign; no space
[ 0.666195] pci 0000:07:00.0: BAR 1 [mem size 0x10000000 64bit pref]: failed to assign
[ 0.666196] pci 0000:07:00.0: VF BAR 2 [mem size 0x10000000 64bit pref]: can't assign; no space
NVRM: BAR1 is 0M @ 0x0 (PCI:0000:04:00.0)
2. The IOMMU/Disk Conflict: If I Enable Above 4G Decoding and Disable CSM (UEFI only), the boot process hangs with filesystem errors, losing access to the NVMe block devices:
Bash
/var/lib/snapd/snaps/firefox_2356.snap: Can't lookup blockdev
[FAILED] Failed to mount Mount unit for firefox.
[FAILED] Failed to mount Mount unit for snapd.
What I have tried so far:
BIOS Settings:
Above 4G Decoding: Enabled
Re-Size BAR: Auto/Enabled
CSM: Disabled
Kernel Parameters:
Tried pci=realloc: Did not resolve the no space error.
Tried iommu=soft: This allows the system to boot with "Above 4G Decoding" enabled (bypassing the blockdev error), BUT nvidia-smi fails to detect devices, or the system falls back to llvmpipe (software rendering) with a zoomed-in resolution.
Display Manager:
/etc/gdm3/custom.conf (WaylandEnable=false).Driver Installation:
Purged all apt nvidia packages.
Running the .run file for driver 580.126.09.
Installation completes successfully in Recovery Mode (Root Shell), but upon rebooting with iommu=soft, the driver doesn't seem to bind correctly to the cards.
The Question: How can I properly expose the BAR address space for both cards on a B550/Ryzen platform without breaking the NVMe/IOMMU controller? Is there a specific combination of GRUB parameters (e.g., pci=noalloc, iommu=pt, amd_iommu=on) that allows 4G decoding to coexist with a functional NVIDIA driver on this chipset?
Any insights on how to escape this loop would be appreciated.
Using Xubuntu 24.04 with Samsung 860 evo 1TB SSD on desktop PC. Here is the smartctl command I must use to find the SSD temperature (with output):
marsdenf@marsdenf-Desktop:~$ sudo smartctl -a /dev/sda | grep -i temp
190 Airflow_Temperature_Cel 0x0032 068 052 000 Old_age Always - 32
The temperature is the last number in the output ("32"). Is there a way to have the terminal output only the temperature number with nothing else before it? I want to use a command in genmon to show only the number. (Apparently hddtemp is not available for Xubuntu 24.04.) Thanks in advance.
The article:
How to create a separate home partition after installing Ubuntu under single / partition
This article discusses how to create a new home partition say after an erase-and-install installation of Ubuntu 25.10 Legacy.
However, how is it possible that all the normal files associated with the home directory, specific to a new user name especially?
There may be the usual files like /home/user/.bashrc but these might refer to the actual name of the user so they need to be user-specific according to everything that needs to be updated?
What is the complete list of user-specific files and home-specific files, and how can these be updated?
Maybe after the erase install completes there is an equivalent to the Apple OS-10 Archive and Install where the user-directory is rebuilt from scratch, but the operating system is left intact?
Should one boot again to the startup disk and create another boot aside from the main erase install boot with all the user-specific information and then merge the two so the first erase install installation remains after?
I appreciate recommendations about the cleanest way to go about this. I am hoping to resolve an issue with just one of the computers I have that I complete the installation of Ubuntu 25.10 in UEFI mode, set the computer BIOS to UEFI, and cannot boot since the operating system is reportedly on the monitor as not found by the computer BIOS, even when selecting the startup disk partition from the BIOS boot menu. That same disk boots fine on other computers in UEFI mode.
So I am currently booted LIVE from 25.10 in Legacy mode, and I am planning on an a Legacy Erase-Install as the simplest possible installation to test whether this computer can at least boot from that, before rolling back to Ubuntu Version 24.04.3 LTS to try an erase install there.
I had tried to use a program to fix the boot before, using boot-repair like:
https://discourse.ubuntu.com/t/new-install-of-25-04-does-not-boot/60343/4
But that did not resolve the problem either, with the same issue that this particular computer could not find the operating system (or even GRUB also?).
Thank you everyone in the community for your insight and advice!
Stephen
I'm looking for a GUI screen video with audio capture app for Ubuntu 24.04 running on Wayland. Search on Ask Ubuntu pulls up stuff 10-15 years old with things no longer in existence, the same with search engines.
Ubuntu Software only has recording junk. Most do not even open, have no GUI, or open and lock up like they're not working with Wayland.
That print screen thing only records video. no audio.
VLC says it can capture the desktop, but has no record button or way to select.
I can use my laptop's HDMI output to record screen to my DVD recorder, bring the burned DVD to the laptop, and use Handbrake to make mp4 recordings. It seems there should be something more user friendly.
I tried OBS Studio and got this:
I'm running Ubuntu 24.04.3 LTS using a Logitech M325S mouse and a K750 keyboard. Most of the time they work fine, but they go through periods where they are very slow, or jerky, or miss signals altogether. I am running Solaar (1.1.11+dfsg+2) to manage Logitech devices. Is there something else I can do that with? Is anyone else having any trouble? If not, are they running something else instead of Solaar?
Output of fwupdmgr:
HP HP EliteBook 665 16 inch G11 Notebook PC
│
├─HP 5MP Camera:
│ Device ID: 377eb704f59a32dc0c615859a9e7bb66246a732d
│ Current version: 0.7
│ Vendor: Chicony (USB:0x04F2)
│ Serial Number: 0001
│ GUID: ac588922-ba28-5efc-bd16-5a8fbe669e09 ← USB\VID_04F2&PID_B7E9
│ Device Flags: • Updatable
│ • Can tag for emulation
│
├─Ryzen 7 Pro 7735U with Radeon Graphics:
│ │ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │ Vendor: AMD
│ │ GUIDs: 52f8f9af-1ca9-5352-bef4-ceb232c888a5 ← CPUID\PRO_0&FAM_19&MOD_44
│ │ e94372a3-3ffb-5d1c-a579-c415b7313e52 ← CPUID\PRO_0&FAM_19&MOD_44&STP_1
│ │ Device Flags: • Internal device
│ │
│ ├─Secure Processor:
│ │ Device ID: c54ab0237d7a8db8c717b68e0be78e4374a2a079
│ │ Current version: 00.28.00.73
│ │ Bootloader Version: 00.28.00.73
│ │ Vendor: AMD (PCI:0x1022)
│ │ GUID: 9844da3e-1df2-52fe-9413-d4378af6221e ← PCI\VEN_1022&DEV_1649
│ │ Device Flags: • Internal device
│ │ • Can tag for emulation
│ │
│ └─System Management Unit (SMU):
│ Device ID: db0330716216c629bb2c07256e5d018f499eb6ce
│ Summary: Microcontroller used within CPU/APU program 4
│ Current version: 69.67.0
│ Vendor: AMD
│ GUID: 79307ae6-a2ea-52e1-bf56-6abbaf3547ad ← /sys/devices/platform/AMDI0007:00
│ Device Flags: • Internal device
│ • Can tag for emulation
│
├─SBAT:
│ Device ID: 6469856584e2f5873b2f148302e46c9313c7d054
│ Summary: Generation number based revocation mechanism
│ Current version: 1.7.4
│ Vendor: OS:ubuntu-core
│ GUID: 009def40-8820-52da-8435-8353cfe3d72c ← UEFI\OS_ubuntu-core&VAR_SbatLevelRT
│ Device Flags: • Updatable
│ • Needs a reboot after installation
│ • Signed Payload
│
├─SK hynix PC801 HFS001TEJ9X101N:
│ Device ID: 04e17fcf7d3de91da49a163ffe4907855c3648be
│ Summary: NVM Express solid state drive
│ Current version: HPS1
│ Vendor: PCI:0x1C5C
│ Serial Number: AME5N006013505J3T
│ GUIDs: bcfb6135-158b-5c97-a08c-a76de6c90dc4 ← NVME\VEN_1C5C&DEV_1959
│ 021c33a7-8b6a-5ec2-a388-4c472df55c3f ← NVME\VEN_1C5C&DEV_1959&SUBSYS_1C5C1959
│ b0e8345f-66fe-5a95-b9e5-7c5d15902d17 ← SK hynix PC801 HFS001TEJ9X101N
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
│ • Can tag for emulation
│
├─System Firmware:
│ │ Device ID: 5ac99b4cc4602bcdcdebe24d7b22da95d44a7711
│ │ Summary: UEFI System Resource Table device (updated via NVRAM)
│ │ Current version: 17104896
│ │ Minimum Version: 1
│ │ Vendor: HP (DMI:HP)
│ │ Update State: Success
│ │ GUID: 27b49886-41a0-4955-38a3-92f903b1b283
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • System requires external power source
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │ Device Requests: • Message
│ │
│ ├─HP UEFI Secure Boot PK:
│ │ Device ID: 6924110cde4fa051bfdc600a60620dc7aa9d3c6a
│ │ Summary: UEFI Platform Key
│ │ Current version: 2017
│ │ Vendor: HP Inc.
│ │ GUIDs: a8179545-9ab4-5347-a45f-e35b1a12ed11 ← UEFI\VENDOR_HP-Inc.&NAME_HP-UEFI-Secure-Boot-PK
│ │ 3906d7cb-dd6d-5a75-ae08-5ec6fca77c46 ← UEFI\CRT_9BF772D66DF309A55F193437F0B99A6AB1BA6711
│ │ Device Flags: • Internal device
│ │
│ ├─UEFI Key Exchange Key:
│ │ │ Device ID: 2a4c23bfb79b5dabe474cb7b1b3e604645d6f9c6
│ │ │ Device Flags: • Internal device
│ │ │
│ │ ├─HP UEFI Secure Boot KEK:
│ │ │ Device ID: 84cabb1dce2a14c89c23fd80885530c7a877ca39
│ │ │ Current version: 2017
│ │ │ Vendor: HP Inc. (UEFI:HP Inc.)
│ │ │ GUIDs: 5cff761c-d054-5fd0-a5a7-1091b6eebe69 ← UEFI\VENDOR_HP-Inc.&NAME_HP-UEFI-Secure-Boot-KEK
│ │ │ cc14b9a4-557c-59dd-b154-e040b1d67517 ← UEFI\CRT_3421767E92415862B897D24D9B408A81A8AF375F
│ │ │ Device Flags: • Internal device
│ │ │ • Updatable
│ │ │ • Needs a reboot after installation
│ │ │ • Device is usable for the duration of the update
│ │ │ • Signed Payload
│ │ │ • Can tag for emulation
│ │ │
│ │ └─KEK CA:
│ │ Device ID: b7a1d3d90faa1f6275d9a98da4fb3be7118e61c7
│ │ Current version: 2023
│ │ Vendor: Microsoft (UEFI:Microsoft)
│ │ GUIDs: 814e950f-1449-566a-a190-42c9d3a3a2df ← UEFI\VENDOR_Microsoft&NAME_Microsoft-KEK-CA
│ │ cd94ec34-7163-5f27-8549-1bd4b7872ae8 ← UEFI\CRT_DEC64D7746D983DB3774829A00BF829D9F19E9CF
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • Needs a reboot after installation
│ │ • Device is usable for the duration of the update
│ │ • Signed Payload
│ │ • Can tag for emulation
│ │
│ ├─UEFI Signature Database:
│ │ │ Device ID: 0352a8acc949c7df21fec16e566ba9a74e797a97
│ │ │ Device Flags: • Internal device
│ │ │
│ │ ├─HP UEFI Secure Boot DB:
│ │ │ Device ID: c8fe97acb1ac2ff598a3a255dd2b760ed1f870c9
│ │ │ Current version: 2024
│ │ │ Vendor: HP Inc. (UEFI:HP Inc.)
│ │ │ GUIDs: c57348fa-61fc-54a1-a8ba-148bdbe4bde5 ← UEFI\VENDOR_HP-Inc.&NAME_HP-UEFI-Secure-Boot-DB
│ │ │ c9538d57-d8ec-53f2-9710-597dea0d4cbd ← UEFI\CRT_121B33FA80A23170F18C7CA279D835D3D0E38D4D
│ │ │ Device Flags: • Internal device
│ │ │ • Updatable
│ │ │ • Needs a reboot after installation
│ │ │ • Signed Payload
│ │ │ • Can tag for emulation
│ │ │
│ │ ├─UEFI CA:
│ │ │ Device ID: 5bc922b7bd1adb5b6f99592611404036bd9f42d0
│ │ │ Current version: 2023
│ │ │ Vendor: Microsoft (UEFI:Microsoft)
│ │ │ GUIDs: 26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
│ │ │ 308281c7-d0c5-52e0-8c1a-810540de03df ← UEFI\CRT_7CD7437C555F89E7C2B50E21937E420C4E583E80
│ │ │ Device Flags: • Internal device
│ │ │ • Updatable
│ │ │ • Needs a reboot after installation
│ │ │ • Signed Payload
│ │ │ • Can tag for emulation
│ │ │
│ │ └─Windows UEFI CA:
│ │ Device ID: d31da5f926c6d962ed810b284fab5a2ef623007b
│ │ Current version: 2023
│ │ Vendor: Microsoft (UEFI:Microsoft)
│ │ GUIDs: 914015a8-9d92-5462-9a9b-f2b361e4faae ← UEFI\VENDOR_Microsoft&NAME_Windows-UEFI-CA
│ │ 89a825bf-78b5-5f1c-905b-e982b2f02584 ← UEFI\CRT_A794240D25F0CCB2EC8142DC2F7411890717DEAD
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • Needs a reboot after installation
│ │ • Signed Payload
│ │ • Can tag for emulation
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI revocation database
│ Current version: 20250902
│ Minimum Version: 20250902
│ Vendor: Microsoft (UEFI:Microsoft)
│ Install Duration: 1 second
│ GUIDs: 7689caf4-c147-5c67-bff9-5dbe59a441bd ← UEFI\CRT_C8B4C6D9755968B6DEB48D4768DD5E9020D3FF4ADC9A62521F54252DD4241678&ARCH_X64
│ d07ff664-b0e1-5f4e-a723-d7fbcbfcb94f ← UEFI\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_X64
│ f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
│ Device Flags: • Internal device
│ • Updatable
│ • Supported on remote server
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Only version upgrades are allowed
│ • Signed Payload
│ • Can tag for emulation
│
├─TPM:
│ Device ID: 1d8d50a4dbc65618f5c399c2ae827b632b3ccc11
│ Current version: 7.2.3.1
│ Vendor: Nuvoton (TPM:NTC)
│ GUIDs: fac1c8f3-73c8-5cd6-8330-07a3690b5140 ← TPM\VEN_NTC&DEV_0000
│ bf68887b-e3d9-5572-9a02-0d34979502c7 ← TPM\VEN_NTC&MOD_NPCT75x"!"8rls
│ e9ccc1dc-960a-5e09-afe9-e59a904b776d ← TPM\VEN_NTC&DEV_0000&VER_2.0
│ bc8b2f06-5f89-5b3a-bc74-976e0329f53b ← TPM\VEN_NTC&MOD_NPCT75x"!"8rls&VER_2.0
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device can recover flash failures
│ • Signed Payload
│ • Can tag for emulation
│
├─UEFI Device Firmware:
│ Device ID: 904f9e062b08a03a7337f7f6cbff53b799344c3e
│ Summary: UEFI System Resource Table device (updated via NVRAM)
│ Current version: 335609856
│ Minimum Version: 1
│ Vendor: DMI:HP
│ Update State: Success
│ GUID: b58cfc31-3a86-6286-a620-f2a1c6c03ac2
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ Device Requests: • Message
│
├─UEFI Device Firmware:
│ Device ID: b970edafffcf075cf953e5efebbf2595bf98f1db
│ Summary: UEFI System Resource Table device (updated via NVRAM)
│ Current version: 335609856
│ Minimum Version: 1
│ Vendor: DMI:HP
│ Update State: Success
│ GUID: ca1146a5-1403-4385-9661-619f4e9eefbb
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ Device Requests: • Message
│
└─UEFI Device Firmware:
Device ID: e97608be1da5b9d742670ca8c3c4f515bc10646a
Summary: UEFI System Resource Table device (updated via NVRAM)
Current version: 935603970
Minimum Version: 1
Vendor: DMI:HP
Update State: Success
GUID: aaa08f4f-bc42-40c2-adf8-aa5a3e62e8e5
Device Flags: • Internal device
• Updatable
• System requires external power source
• Needs a reboot after installation
• Device is usable for the duration of the update
Device Requests: • Message
I'm having trouble to get a fresh manual installation of Ubuntu 24.04. Upon inspecting it from initramfs, the crypttab file has been edited during the initrd generation process, namely the keyfile path has been modified and leading / has been replaced with /FIXME-initramfs-rootmnt as shown below.
(initramfs) cat cryptroot/crypttab
luks-keystore UUID=18fe90ef-34b7-4100-bed2-c90d01412485 none luks,discard,readonly,initramfs,tries=0
luks-swap UUID=e7418d11-0ed6-4e70-8a76-b0146642ae07 /FIXME-initramfs-rootmnt/dev/mapper/luks-keystor
e luks,discard,keyfile-size=4096,initramfs
luks-root UUID=f561bb85-db00-4e2d-b837-d5b0bca043c2 /FIXME-initramfs-rootmnt/dev/mapper/luks-keystor
e luks,discard,keyfile-size=4096,initramfs
(initramfs) cat /mnt/etc/crypttab
luks-keystore UUID=18fe90ef-34b7-4100-bed2-c90d01412485 none luks,discard,reado
nly,initramfs,tries=0
luks-swap UUID=e7418d11-0ed6-4e70-8a76-b0146642ae07 /dev/mapper/luks-keystore luks,discard,key
file-size=4096,initramfs
luks-root UUID=f561bb85-db00-4e2d-b837-d5b0bca043c2 /dev/mapper/luks-keystore luks,discard,key
file-size=4096,initramfs
(initramfs)
What can I do from this initramfs environment to recover the system? I am able to mount and chroot into the actual root and run update-initramfs, but it would still produce initrd.img with the same faulty crypttab. How can I make it package the crypttab as is, ideally straight from this manual chroot environment via initrd?
It detects when I use lsusb but can't run fprintd-enroll
fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
sudo systemctl start fprintd && sudo systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
Active: active (running) since Mon 2024-07-08 15:22:30 IST; 3s ago
Docs: man:fprintd(1)
Main PID: 90113 (fprintd)
Tasks: 6 (limit: 9114)
Memory: 1.6M (peak: 2.5M)
CPU: 72ms
CGroup: /system.slice/fprintd.service
└─90113 /usr/libexec/fprintd
Jul 08 15:22:30 bhanu-vardhan-reddy-Vostro-3500 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jul 08 15:22:30 bhanu-vardhan-reddy-Vostro-3500 fprintd[90113]: Creating TOD wrapper for goodix-tod (Goodix Fingerprint Sensor 53xc) driver
Jul 08 15:22:30 bhanu-vardhan-reddy-Vostro-3500 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
There is an amazing thread on this here - Installing Broadcom Wireless Drivers
Which sadly does not mention the 4464 adaptors. My machine (a 2018 Macbook Pro with an intel chip has the following)
Network controller [0280]: Broadcom Inc. and subsidiaries BCM4364 802.11ac Wireless Network Adapter [14e4:4464] (rev 03)
Subsystem: Apple Inc. BCM4364 802.11ac Wireless Network Adapter [106b:07bf]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 255
Region 0: Memory at 81400000 (64-bit, non-prefetchable) [disabled] [size=32K]
Region 2: Memory at 81000000 (64-bit, non-prefetchable) [disabled] [size=4M]
Capabilities: <access denied>
Kernel modules: brcmfmac
The adaptor is not listed in the various responses, and I have tried all the options to no avail - still no wifi!
Output of sudo dmesg | grep brcm gives :
[ 2.306318] usbcore: registered new interface driver brcmfmac
[ 2.306471] brcmfmac 0000:03:00.0: enabling device (0000 -> 0002)
[ 2.416065] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b2-pcie for chip BCM4364/3
[ 2.417728] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN-u-7.5-X0.bin failed with error -2
[ 2.418243] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN-u-7.5.bin failed with error -2
[ 2.418276] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN-u.bin failed with error -2
[ 2.418307] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-HRPN.bin failed with error -2
[ 2.418337] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai-X0.bin failed with error -2
[ 2.418367] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.apple,kauai.bin failed with error -2
[ 2.418398] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4364b2-pcie.bin failed with error -2
[ 2.418401] brcmfmac 0000:03:00.0: brcmf_pcie_setup: Dongle setup failed
[ 2.418418] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
[ 3.070049] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
Does anyone have an idea how to make this work with the 14e4:4464 version?
Thank you so much!
I had attached the Ubuntu ISO to Virtual Storage option via IPMI (Supermicro) and booted via USB. The ISO is booting up and going directly to "Try Ubuntu" instead of actual installation. It does not prompt for the installation methods/options.
Once the "Try Ubuntu" is available and when I try to start the actual installation, it is failing with "You need at least 8.6 GB disk space to install Ubuntu". Can someone tell me the best way to install Ubuntu via IPMI?
A while ago I tried to install Ubuntu alongside my school laptop to to see what it was. I deleted it eventually since the laptop didn't like the dual boot (Ubuntu didn't boot a couple of times). Now, after a couple of years just using Windows, I wanted to use Ubuntu as the only OS on my laptop. I used a live USB, installed everything, and when prompted to restart I did, only to find out it didn't boot. I used the USB again because I thought I did something wrong, but when I chose the option to install Ubuntu, it asked me if I wanted to overwrite the existing Ubuntu operating system. I did, since I thought the first install might be corrupted or something, but when I tried to boot the laptop after installing the fresh version, it still wouldn't boot.
My question is (after this whole story): What am I doing wrong? The BIOS doesn't recognize an OS on my hard drive I think. I saw other threads that said to use Boot-Repair, but I got an error that said that the system is in BIOS compatible mode or something like that. I also tried to see how the partitions are divided using GParted. I am attaching a screenshot, because I think there is something wrong in the partitions with the GRUB bootloader or something like that, but I don't have the knowledge to understand what I'm looking for.
GParted:
I have an Acer Predator Triton 700 and it does not have option to disable Intel RST (Rapid Storage Technology) in the BIOS. What should I do?
I have been struggling to start my webcam as i need to clear an interview with a video conferencing. I updated the OS from 18.04 to 20.04 but still I get the message No device found when I try to open cheese. Below is the output of the command lsusb
nik@nik:/$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Below are some commands executed
nik@nik:/$ sudo modprobe uvcvideo
nik@nik:/$
niket@nik:/$ sudo modprobe vfe_v4l2
modprobe: FATAL: Module vfe_v4l2 not found in directory
/lib/modules/5.4.0-81-generic
niket@nik:/$ sudo modprobe gc2035
modprobe: FATAL: Module gc2035 not found in directory /
lib/modules/5.4.0-81-generic
Can someone clarify me if webcam drivers are not there or how do I need to resolve this problem. I have looked into lot of online docs and applied them but still cannot resolve this issue.
I just made a decision and deleted the Windows partition, but now I have Windows 10 in the grub menu although I updated grub. My Windows 10 and Ubuntu are both installed as EFI systems, and I know both of them had a partition they used, but I don't know how to delete Windows boot files to delete Windows completely from grub and my UEFI firmware.
GParted:
As you see, /dev/sda2 is an EFI system partition.
My laptop has two drives:
I have to issues which are as follows:
GRUB loads when I boot into Ubuntu and shows a Windows option but when I select that option, nothing happens. I know that I can use BIOS to boot into windows using windows boot manager but why can't I do it from GRUB? This code shows the Windows section from the GRUB config file:
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "MS Windows" {
insmod part_gpt
insmod search_fs_uuid
insmod ntfs
insmod chain
}
Also the sudo os-prober command in the terminal doesn't return anything. I have a feeling this is related to the second problem.
When I boot into Ubuntu, it can't seem to find my SSD. It can only detect the hard drive that has Ubuntu installed on it. This is what I get when I type the following command in the terminal:
sudo parted -l
Its output is:
Model: ATA ST1000LM035-1RK1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 135MB 134MB Microsoft reserved partition msftres
2 135MB 866GB 866GB ntfs Basic data partition msftdata
3 866GB 867GB 650MB fat32 boot, esp
4 867GB 969GB 102GB ext4
5 969GB 991GB 21.5GB ext4
6 991GB 1000GB 9665MB linux-swap(v1)
Is there a way I can access my SSD from Linux and boot into Windows from GRUB or do I have to open BIOS every time I start my computer and choose where I want to boot?
I am having trouble connecting to wifi after installing Ubuntu to dual boot alongside Windows 10. I have followed everything in this guide, Wi-Fi not working on Lenovo ThinkPad E570 (Realtek RTL8821CE)
The only thing that is holding me back is not being able to disable Secure Boot. In my BIOS, there is nothing labeled "Secure Boot". I did fast boot, but that didn't change anything. Do you have any recommendations?
Though I have gone through quite a few threads on AskUbuntu (1, 2, 3), and elsewhere, I'm little confuse on how to proceed.
I'd like to completely remove ufw, delete all iptables chains and rules, for a fresh start with nftables firewall in Ubuntu MATE 19.04
If I understand correctly (from the threads I have linked), I need to run the following:
sudo systemctl reset ufw
sudo systemctl disable ufw
sudo apt purge ufw gufw
sudo iptables -F
sudo iptables -Z
Then ?
for i in `iptables -L INPUT --line-numbers |grep '[0-9].*ufw' | cut -f 1 -d ' ' | sort -r `; do iptables -D INPUT $i ; done
for i in `iptables -L FORWARD --line-numbers |grep '[0-9].*ufw' | cut -f 1 -d ' ' | sort -r `; do iptables -D FORWARD $i ; done
for i in `iptables -L OUTPUT --line-numbers |grep '[0-9].*ufw' | cut -f 1 -d ' ' | sort -r `; do iptables -D OUTPUT $i ; done
for i in `iptables -L | grep 'Chain .*ufw' | cut -d ' ' -f 2`; do iptables -X $i ; done
The questions I have are:
(1) How do I "disable or deactivate" iptables so it doesn't interfere with Nftables firewall later on.
(2) In addition to removing ufw, should I remove iptables too:
sudo apt remove --auto-remove iptables
(3) Then proceed with installing and configuring nftables, is this the correct order?
I have a PC called 'Windows' and it runs W10 home. I installed Ubuntu and samba on PC 'Ubuntu' and created a shared map.
I can ping in both directions.
I see PC 'Ubuntu' from PC 'Windows' with nbtstat and both have the same workgroup name.
But I do not see PC 'Ubuntu' in my PC 'Windows' network map, even after stopping the firewall on 'Windows'.
On 'Ubuntu' PC I have not installed a firewall yet.
My purpose is to work on PC 'Ubuntu' files from PC 'Windows'. Any idea's on how to proceed?
I using Ubuntu 14.04
I installed fbterm using
sudo apt-get install fbterm
But when I type sudo fbterm
There is a message
stdin isn't a interactive tty!
Is that message an error? Or is something wrong?
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+
ii fbterm 1.7-2 amd64 A fast framebuffer based terminal emulator for Linux
I have a system to learn on and I am new to Linux. I deleted the shared directory thinking the login keyring was there. Then I updated, listed and deleted the ftpmaster@ubuntu, thinking that was the keyring keeping me from what I am trying to do - which is get online; I cannot type in the passphrase to my router without being asked to put in the old keyring, which I thought I knew btw.
After having issues with a black screen (nomodeset resolved this) now the system gets stuck on booting. I tried to boot without splash and quiet. It boots normally to some point and then simply stops (the console also flickers for some time). I tried nomodeset in my VM where it boots without this and now I'm having the same issue there as on my real machine. If I remove nomodeset it boots up normally.
My VM is hanging on boot.
Starting Detect the available GPUs and deal with any system changes...
[ OK ] Started Regular background program processing daemon.
Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
[ OK ] Started Snappy daemon.
[ OK ] Started System Logging Service.
[ OK ] Started Ubuntu live CD installer.
[ OK ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
[ OK ] Started Thermal Daemon Service.
[ OK ] Started Detect the available GPUs and deal with any system changes.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started Network Manager.
[ OK ] Started Save/Restore Sound Card State.
[ OK ] Started Raise network interfaces.
[ OK ] Started LSB: Record successful boot for GRUB.
[ OK ] Started LSB: daemon to balance interrupts for SMP systems.
[ OK ] Started LSB: automatic crash report generation.
[ OK ] Started LSB: Speech Dispatcher.
[ OK ] Started Login Service.
Starting Network Manager Script Dispatcher Service...
Starting Authenticate and Authorize Users to Run Privileged Tasks...
[ OK ] Reached target Network.
[ OK ] Started Make remote CUPS printers available locally.
Starting Permit User Sessions...
Starting Network Name Resolution...
[ OK ] Started Permit User Sessions.
[ OK ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[ OK ] Started Accounts Service.
Starting Run passwd -d to ensure AccountsService properties are set correctly...
Starting Hold until boot process finishes up...
[ OK ] Started Hold until boot process finishes up.
Starting Set console scheme...
[ OK ] Started Set console scheme.
[ OK ] Created slice system-getty.slice.
[ OK ] Started Run passwd -d to ensure AccountsService properties are set correctly.
[ OK ] Started Modem Manager.
[ OK ] Started Network Manager Script Dispatcher Service.
Starting Hostname Service...
Starting GNOME Display Manager...
[ OK ] Started GNOME Display Manager.
[ OK ] Started Network Name Resolution.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes...
Starting Notify bootloader that boot was successful...
[ OK ] Started Update UTMP about System Runlevel Changes.
[ OK ] Started Notify bootloader that boot was successful.
[ OK ] Started Hostname Service.
In my VM it occurs with EFI enabled and disabled.
Reposting the question from: https://unix.stackexchange.com/q/314129/193223
I recently upgraded from Ubuntu 14.04 to 16.04 after which the display manager stopped working.
Assuming it's due to the init systems, I tried to switch back to upstart by following the instructions given on this page:
https://wiki.ubuntu.com/SystemdForUpstartUsers
It didn't work.
newton@gravity:~$ sudo systemctl status lightdm
● lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/display-manager.service.d
└─xdiagnose.conf
Active: inactive (dead) (Result: exit-code) since Mon 2016-10-03 19:04:26 EDT; 13min ago
Docs: man:lightdm(1)
Process: 3533 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
Process: 3528 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS)
Main PID: 3533 (code=exited, status=1/FAILURE)
Oct 03 19:04:26 newton systemd[1]: lightdm.service: Failed with result 'exit-code'.
Oct 03 19:04:26 newton systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Oct 03 19:04:26 newton systemd[1]: Stopped Light Display Manager.
Oct 03 19:04:26 newton systemd[1]: lightdm.service: Start request repeated too quickly.
Oct 03 19:04:26 newton systemd[1]: Failed to start Light Display Manager.
Oct 03 19:09:02 newton systemd[1]: Stopped Light Display Manager.
journalctl shows issues with PAM kwallet.
$ sudo journalctl -e -u lightdm
...
systemd[1]: Starting Light Display Manager...
systemd[1]: Started Light Display Manager.
lightdm[26952]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
lightdm[26952]: PAM adding faulty module: pam_kwallet.so
lightdm[26952]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
lightdm[26952]: PAM adding faulty module: pam_kwallet5.so
lightdm[26952]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: lightdm.service: Unit entered failed state.
systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
systemd[1]: lightdm.service: Failed with result 'exit-code'.
...
Here's the content of /var/log/lightdm/lightdm.log;
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.18.2, UID=0 PID=26937
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.01s] DEBUG: DisplayServer x-0: Launching X Server
[+0.01s] DEBUG: Launching process 26944: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1007 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1009 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1006 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1005 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1002 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1011 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1008 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1003 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1004 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1010 added
[+0.23s] DEBUG: Got signal 10 from process 26944
[+0.23s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+0.23s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+0.23s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.23s] DEBUG: Session pid=26952: Started with service 'lightdm-greeter', username 'lightdm'
[+0.25s] DEBUG: Session pid=26952: Authentication complete with return value 0: Success
[+0.25s] DEBUG: Seat seat0: Session authenticated, running command
[+0.25s] DEBUG: Session pid=26952: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+0.25s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.25s] DEBUG: Session pid=26952: Logging to /var/log/lightdm/seat0-greeter.log
[+0.27s] DEBUG: Activating VT 7
[+0.27s] DEBUG: Activating login1 session c17
[+0.27s] DEBUG: Seat seat0 changes active session to c17
[+0.27s] DEBUG: Session c17 is already active
[+0.37s] DEBUG: Greeter closed communication channel
[+0.37s] DEBUG: Session pid=26952: Exited with return value 0
[+0.37s] DEBUG: Seat seat0: Session stopped
[+0.37s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+0.37s] DEBUG: Seat seat0: Stopping
[+0.37s] DEBUG: Seat seat0: Stopping display server
[+0.37s] DEBUG: Sending signal 15 to process 26944
[+0.50s] DEBUG: Process 26944 exited with return value 0
[+0.50s] DEBUG: DisplayServer x-0: X server stopped
[+0.50s] DEBUG: Releasing VT 7
[+0.50s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+0.50s] DEBUG: Seat seat0: Display server stopped
[+0.50s] DEBUG: Seat seat0: Stopped
[+0.50s] DEBUG: Required seat has stopped
[+0.50s] DEBUG: Stopping display manager
[+0.50s] DEBUG: Display manager stopped
[+0.50s] DEBUG: Stopping daemon
[+0.50s] DEBUG: Exiting with return value 1
Any other debugging tips that I need to try?
I am currently running Ubuntu 12.0.4 on a 64 bit machine. I have an AM335X development board. Along with the kit came the compressed kernel (linux 3,2), rootfs, u-boot, and ARM cross compiler (arm-2010q1).
I uncompressed everything to a sub folder (/home/brent/work).
I have added the following to my .bashrc file:
PATH=/home/brent/work/arm-2010q1/bin:$PATH
CROSS_COMPILE=arm-none-linux-gnueabi-
I have also installed the following:
sudo apt-get install ia32-libs
When I go to built u-boot I am doing the following (per instructions that came with the kit):
brent@brent~/work/u-boot$ sudo make distclean
awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
brent@brent~/work/u-boot$ sudo make myd_am335x_lcd4.3_config
awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
Configuring for myd_am335x_lcd4.3 - Board: myd_am335x, Options: DISPLAY_LCD43
brent@brent~/work/u-boot$ sudo make
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk
/bin/bash: line 3: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk.dep
/bin/bash: line 3: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
/bin/bash: arm-none-linux-gnueabi-ld: command not found
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
arm-none-linux-gnueabi-gcc -DDO_DEPS_ONLY \
-g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -I/home/brent/CropVentures/u-boot/include -fno-builtin -ffreestanding -nostdinc -isystem -pipe -DCONFIG_ARM -D__ARM__ -march=armv5 -Wall -Wstrict-prototypes \
-o lib/asm-offsets.s lib/asm-offsets.c -c -S
/bin/bash: arm-none-linux-gnueabi-gcc: command not found
make: *** [lib/asm-offsets.s] Error 127
I have verified the binary is located at /home/brent/work/arm-2010q1/bin
I am also not sure why I need to have sudo as part of the command? If I do not I get a permissions error.
Any help or information on what I am doing wrong would be greatly appreciated.
I recently bought the asus USB-N53 wireless adapter, and want to install the latest driver for it. It comes with instructions of how to install the driver from the files provided, but I can't use makefile, so can't install the driver correctly. These are the instructions from the readme file included:
=======================================================================
tar -jxvf 2011_1003_RT3572_Linux_STA_v2.5.0.0.DPO.tar.bz2
go to ./2011_1003_RT3572_Linux_STA_v2.5.0.0.DPO directory.
switch to super user. ** for Fedora
$ su
** for Ubuntu
$ sudo su
in Makefile
set the "MODE = STA" in Makefile and chose the TARGET to Linux by set "TARGET = LINUX"
define the linux kernel source include file path LINUX_SRC
modify to meet your need.
in os/linux/config.mk
define the GCC and LD of the target machine
define the compiler flags CFLAGS
modify to meet your need.
** Build for being controlled by NetworkManager or wpa_supplicant wext functions
Please set HAS_WPA_SUPPLICANT=y and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y.
=> #> cd wpa_supplicant-x.x
=> #> ./wpa_supplicant -Dwext -ira0 -c wpa_supplicant.conf -d
** Build for being controlled by WpaSupplicant with Ralink Driver
Please set HAS_WPA_SUPPLICANT=y and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n.
=> #> cd wpa_supplicant-0.5.7
=> #> ./wpa_supplicant -Dralink -ira0 -c wpa_supplicant.conf -d
compile driver source code $ make
=======================================================================
load driver
$ make install
plug in USB dongle.
=======================================================================
Can somebody help me to use makefile to install the driver?
EDIT:
When I ran uname -R, the terminal outputted 3.2.0-58-generic-pae.
When I ran lsusb, the terminal outputted:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 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 001 Device 002: ID 0ac8:3450 Z-Star Microelectronics Corp.
Bus 001 Device 004: ID 0b05:179d ASUSTek Computer, Inc.
Bus 003 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
Bus 002 Device 002: ID 05fc:0231 Harman Multimedia
I'm using Ubuntu 13.04 on a Dell E6410.
Dell E6410 comes with a default WiFi adapter: Intel Centrino Advanced-N 6200.
I additionally plugged in a Realtek rtl8192cu adapter
I can clearly see which adapter is being used from the top-right side of Ubuntu 13.04 ---- the network configuration icon, however I'm wondering, is there a way to show in the bash by using command line that:
How many WiFi adapters on my system for now? ifconfig only shows there are 2 WiFi adapters, and I can see wlan1 is being used, but which adapter corresponds to wlan1 and which adapter corresponds to wlan0?
I can clearly see the MAC addresses of two WiFi adapters, but lsusb only shows the connected USB devices without showing their MAC address, and the default WiFi adapter coming with the laptop is not a USB device. lshw takes me such a long time to show clearly the MAC address for the Centrino Advanced-N 6200 and the MAC address for Realtek rtl8192cu.
Is there a simple but direct way to compare both WiFi devices?
I downloaded the ubuntu-12.10-desktop-amd64.iso, then I created a bootable USB stick using the guide from here. I booted from the USB stick, then after the Ubuntu logo and some circles loaded beneath it, nothing happened and my laptop started making some weird noise, so I booted the USB again, but this time with acpi=off, noapic and nolapic enabled. This time the booting process went past the circle loading thing, but halted, and the weird noise started again.
The boot process stopped and got stuck at a black screen with the following boot messages:
with channel with regulatory rule:
[ 79.033232] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mB),
[ 79.033282] cfg80211: Updating information on frequency 2457 MHz for a 20
with channel with regulatory rule:
[ 79.033337] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBl, 1
[ 79.033387] cfg80211: Updating information on frequency 2462 MHz for a 20
with channel with regulatory rule:
[ 79.033441] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBl, 19
[ 79.033492] cfg80211: Updating information on frequency 2467 MHz for a 20
with channel with regulatory rule:
[ 79.033546] cfg80211: 2457000 KHz - 2482000 KHz @ 20000 KHz), (N/A mBl, 190
[ 79.033596] cfg80211: Updating information on frequency 2472 MHz for a 20 M
with channel with regulatory rule:
[ 79.033650] cfg80211: 2457000 KHz - 2482000 KHz @ 20000 KHz), (N/A mBl, 1900
[ 79.033701] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that's a 20 MHz wide channel
[ 79.038078] cfg80211: Ignoring regulatory request Set by core since the drive uses its own custom regulatory domain
[ 79.093384] ieee80211 phy0: >Selected rate control algorithm 'minstrel_ht'
Why isn't the OS booting properly?
I had an intermittent issue (which resolves itself spontaneously, after using a different connection for a while) that caused Internet requests to fail, with one particular wireless network. After about 5 requests after associating with an AP, ping would report the error
ping: sendmsg: No buffer space available
just as in Wifi connected but no data transfer: "ping: sendmsg: No buffer space available".
In case it's relevant, I'm seeing with a Centrino Ultimate-N 6300 [8086:4238] wireless interface on a Thinkpad X201. Bug #836250 is possibly related.
While I can work around this issue, I was wondering: What does this error message mean? In particular, what buffer is it talking about?