I'm trying to print duplex on my Samsung M2070 Printer. I installed the driver from the Samsung website with the provided install.sh and then added the printer to the system in the Printers section of the System Preferences. I see the Printer in LibreOffice Writer, and I can print with it, but there isn't a duplex function in the print window (On Win7 there is a Checkbox). Do you have any ideas? **Update** I clicked on "Print" in LibreOffice and then "Properties" and "Paper". I saw the disabled duplex combobox. I thought on a driver issue, so i went to CUPS administration to check my driver. It wrote, that my driver is able to print duplex.

According to Gnome / Nautilus, these files reside at: mtp://[usb:001,007] But: $ cd mtp://[usb:001,007] bash: cd: mtp://[usb:001,007]: No such file or directory And df -h doesn't list it. While lsusb suggests it's there: Bus 001 Device 008: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)

Sorry about this but I'm a "newbe" at this. Would not have bothered anyone but I have need of a webcam under the present global circumstances. The only one I have is this old one (SAMSUNG TV camera model VG-STC3000/ZA). I am GUESSING that drivers are missing or something but I have no idea how to solve the problem. I'm using ubuntu 18.04.4 LTS). When I use a webcam tester I get something about permissions not allowing the use of the webcam. Any help to make it work would be most appreciated.

I have a very old Samsung SCX-3205 printer/copier/scanner. It scans fine and works fine. HOWEVER, when I print with CUPS, it stops scanning. "scanimage -L" tells for the first run after printing that the device is still there, but the next run it cannot find it anymore. I have done a strace, check the differences: Non-working case: ppoll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8, events=POLLOUT}], 3, {tv_sec=60, tv_nsec=0}, NULL, 8) = 1 ([{fd=6, revents=POLLIN}], left {tv_sec=59, tv_nsec=4341630}) ioctl(8, USBDEVFS_DISCARDURB, 0x55933dbfb0) = 0 timerfd_settime(6, 0, {it_interval={tv_sec=0, tv_nsec=0}, it_value={tv_sec=0, tv_nsec=0}}, NULL) = 0 ppoll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8, events=POLLOUT}], 3, {tv_sec=60, tv_nsec=0}, NULL, 8) = 1 ([{fd=8, revents=POLLOUT}], left {tv_sec=59, tv_nsec=999980518}) ioctl(8, USBDEVFS_REAPURBNDELAY, 0x7fc9c97a50) = 0 timerfd_settime(6, 0, {it_interval={tv_sec=0, tv_nsec=0}, it_value={tv_sec=0, tv_nsec=0}}, NULL) = 0 ioctl(8, USBDEVFS_REAPURBNDELAY, 0x7fc9c97a50) = -1 EAGAIN (Resource temporarily unavailable) ioctl(8, USBDEVFS_CLEAR_HALT, 0x7fc9c97cb4) = 0 ioctl(8, USBDEVFS_CLEAR_HALT, 0x7fc9c97eb4) = 0 ioctl(8, USBDEVFS_CLEAR_HALT, 0x7fc9c97eb4) = 0 ioctl(8, USBDEVFS_RELEASEINTERFACE, 0x7fc9c97e5c) = 0 Working case: ppoll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8, events=POLLOUT}], 3, {tv_sec=60, tv_nsec=0}, NULL, 8) = 1 ([{fd=8, revents=POLLOUT}], left {tv_sec=59, tv_nsec=999981204}) ioctl(8, USBDEVFS_REAPURBNDELAY, 0x7ff3d45d80) = 0 timerfd_settime(6, 0, {it_interval={tv_sec=0, tv_nsec=0}, it_value={tv_sec=0, tv_nsec=0}}, NULL) = 0 ioctl(8, USBDEVFS_REAPURBNDELAY, 0x7ff3d45d80) = -1 EAGAIN (Resource temporarily unavailable) ioctl(8, USBDEVFS_CLEAR_HALT, 0x7ff3d461e4) = 0 ioctl(8, USBDEVFS_CLEAR_HALT, 0x7ff3d461e4) = 0 ioctl(8, USBDEVFS_RELEASEINTERFACE, 0x7ff3d4618c) = 0 So I can see there is extra ppoll ("fd=6, revents=POLLIN") in the mix for the failing case. FD is from here: timerfd_create(CLOCK_MONOTONIC, TFD_CLOEXEC|TFD_NONBLOCK) = 6 I'm running a Alpine Linux 3.15.0 on Raspberry Pi 4 Model B Rev 1.1.

I'm having a problem with a Samsung TV as a monitor. Thank you for any insight: debian + xorg + RTX4090 + qn700b + (HDMI 2.1 cable seems good) Problem: when waking the TV and computer, I can't get it back to 8k again? It becomes stuck at 4k. --- Symptoms: - Initially, a black screen when TV/computer are turned back on (either order). - Ctrl-alt-f1/f2/etc wakes screen into 4k, and then I can ctrl-alt-f7 back to graphical tty, but I lost 8k and now it's stuck at 4k (tv correctly still in Samsung game mode). - sudo nvidia-settings doesn't allow 8k (only 4k appears in dropdown) - downloading EDID via nvidia-settings and forcing in xorg doesn't work? Not sure how to tell. - cvt and xrandr --newmode etc / --addmode "HDMI-0" 7680x4320at60 fails with BadMatch (invalid parameter attributes), major opcode 140 RANDR, minor opcode 18 RRAddOutputMode. (I know I can set Option "DPMS" "false" and various Options "fooTime" "off" in xorg or xset -dpms and keep the monitor on 24/7, or restart the window manager/X/etc as a workaround, but wish to otherwise fix this without losing WM state, without an irreversible firmware update if possible.) Thank you for any insight! Xorg.0.log: Validated MetaModes: "7680x4320+0+0{AllowGSYNCCompatible=On}" .. MetaMode "HDMI-0:7680x4320" could not be re-validated against the current hardware configuration; removing. .. Setting mode "DPY-0:7680x4320+0+0{AllowGSYNCCompatible=On}" .. Setting mode "DPY-0:nvidia-auto-select+0+0{AllowGSYNCCompatible=On}" xorg.conf: Section "Monitor" .. Option "DPMS" "false" Option "PreferredMode" "7680x4320" EndSection Section "Device" .. Option "ModeValidation" "AllowNonEdidModes" EndSection Section "Screen" .. Option "CustomEDID" "GPU-0.HDMI-0:/path/to/edid.txt" Option "metamodes" "7680x4320 +0+0 {AllowGSYNCCompatible=On}" Option "ConnectToAcpid" "False" # https://bbs.archlinux.org/viewtopic.php?id=262207 SubSection "Display" Virtual 7680 4320 Depth 24 EndSubSection EndSection

I installed Ubuntu 22.04 on my Samsung Galaxy Book 2 (NP750XED) by following the official instructions and it works perfectly until I turn the computer off. After boot, when reaching the login prompt, the system abruptly goes to sleep. I can wake up the system again, but it will quickly go to sleep again, stuck in a perpetual loop.

I've used btrfs for my encrypted partitions (luks) on Samsung EVO SSDs. The disks failed faster than expected. How can I assess whether e.g. ext4 would be more reliable on these disks for my usage, or what usage is more likely to contribute to their wear level? ## Background After about 2 year of use as root and home disk on my desktop PC, my Samsung SSD 870 EVO 500GB started failing, with hundreds of bad blocks and thousands of uncorrectable errors:

$ sudo smartctl -a /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.2.15-100.fc36.x86_64] (local build)

=== START OF INFORMATION SECTION ===
Device Model:     Samsung SSD 870 EVO 500GB
Firmware Version: SVT01B6Q

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Self-test execution status:      ( 121) The previous self-test completed having
                                        the read element of the test failed.

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  9 Power_On_Hours          0x0032   096   096   000    Old_age   Always       -       19378
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       69
177 Wear_Leveling_Count     0x0013   098   098   000    Pre-fail  Always       -       44
183 Runtime_Bad_Block       0x0013   065   065   010    Pre-fail  Always       -       200
187 Uncorrectable_Error_Cnt 0x0032   099   099   000    Old_age   Always       -       2696
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       59
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       83504703737

The disk was rather busy, but well under the [warranty limits](https://semiconductor.samsung.com/consumer-storage/support/warranty/) of 5 years or 300 TB TBW. Its predecessor was a Samsung 850 EVO 250 GB and was in a similar state after 5 years of use. Maybe the new disk was just worse than the previous, but I started wondering whether there's a common factor. One thing they shared is that I've installed Fedora on them, and recently Fedora started using btrfs by default (at least for luks filesystems), instead of ext4 (I believe the previous disk had ext4 most of its life). Fedora 38 for example creates this layout by default:

$ lsblk
NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda                   8:0    0 465,8G  0 disk  
├─sda1                8:1    0   600M  0 part  /boot/efi
├─sda2                8:2    0     1G  0 part  /boot
└─sda3                8:3    0 464,2G  0 part  
  └─luks- 253:0    0 464,2G  0 crypt /home
                     /
$ mount | grep luks
/dev/mapper/luks- on / type btrfs (rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/root)
/dev/mapper/luks- on /home type btrfs (rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/home)
$ mount | grep sda
/dev/sda2 on /boot type ext4 (rw,relatime,seclabel)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)

A few years back it was similar but without [compression](https://btrfs.readthedocs.io/en/latest/Compression.html) and some other btrfs parameters. The btrfs documentation, after a discussion of COW (copy on write), contains a number of [warnings on SSDs](https://btrfs.readthedocs.io/en/latest/Hardware.html#solid-state-drives-ssd) : > Writing “too much” distinct data (e.g. encrypted) may render the internal deduplication ineffective and lead to a lot of rewrites and increased wear of the memory cells. > It’s not possible to reliably determine the expected lifetime of an SSD due to lack of information about how it works or due to lack of reliable stats provided by the device. > Only users who consume 50 to 100% of the SSD’s actual lifetime writes need to be concerned by the write amplification of btrfs DUP metadata. So it sounds like I've reached over 50 % of the disks' actual lifetime despite my writes being an order of magnitude less than what promised by the warranty, and I *should* worry about SSD wear with btrfs. ### Usage patterns I now notice that you're supposed to run a [btrfs scrub](https://btrfs.readthedocs.io/en/latest/Scrub.html) monthly and also after events like power outages: > The user is supposed to run it manually or via a periodic system service. The recommended period is a month but could be less. I never did that. The most frequently accessed files get checked and repaired anyway at some point. My files which got corrupted tended to be on the older and less accessed side. (It would be strange if this mattered though. Another SSD of mine with luks+lvm+ext4 has over 10k powercycles, according to SMART, and no issues whatsoever.) ## Possible ideas It's common for people to advise against running databases or other similarly write-intensive loads on btrfs. I don't know how true/current said advice is, but I don't run any database on my PC. On the other hand, the previous disk's most devastating failures where in a region used by Thunderbird for its message storage (which was a few GB worth of mbox files; I've since switched to Maildir). I wonder whether there are some database-like loads on my PC which I could do without, or move to another filesystem. (I've already disabled baloo.) Is there some benchmarking tool or utility to tell which applications are producing most writes (or most potential wear) to the filesystem? Alternatively, is there a benchmarking tool or utility to stress test a certain filesystem-disk combination and see the impact on the disk's self-reported wear in the various cases?

I would like to use a Samsung multifunction laser printer as a local, USB-connected printer, from a recently-installed Parrot Security 5.3 OS, a security-hardened version of Debian. The Samsung Universal Print & Scan Driver v.1 for Linux is provided via the HP website (HP now services Samsung printers) and is installed by executing a shell script. The driver requires CUPS to be installed, so I first successfully installed CUPS and then successfully installed the Samsung printer driver. The terminal informed me that both the CUPS backend (for the printer driver) and the SANE backend (for the scan driver) were successfully registered and both cups and udev successfully started and that the installation was successful. Since this is a local, cable-connected printer and not a network printer, I did not ask the shell script to configure the firewall. (Parrot considers CUPS to be a security risk and therefore disables it by default, however it works properly when the service is started.) My problem is that the printer is nowhere recognized when I plug in the cable: no system scanning for drivers, etc. When I verified with the CUPS web interface whether any printer was recognized, there wasn't any printer that was recognized. However I am reluctant to use the CUPS web interface since its localhost:631 interface uses http only, and not https, which I consider to be antediluvian in today's world. An additional problem is that the MATE System Control Center used by Parrot OS does not seem to have a specific panel for printers, as Ubuntu seems to have.I still don't understand why CUPS does not recognize the printer driver despite having been successfully integrated into the CUPS backend (same for scan driver). I also tried to install gutenprint drivers to see if my printer would recognize them. Unfortunately, Parrot OS does not allow me to install them due to unmet dependency issues (but that is a different problem) - so no gutenprint. Could anyone please help me on how I could get my system to recognize the printer/ scanner without using CUPS over an unsecured web interface? Please know that I am new to Linux, so please be precise in your answers so that I can look something up if I don't understand it. Thanks a bundle !

I recently got my hands on an old Samsung CLX 3180 laser printer. It seems to work quite well with the "Generic PCL Laser Printer" driver. Unfortunately, though, it doesn't print in color. I've tried to use the "system-config-printer" tool but there I only see the advanced option "print-color-mode: monochrome" as depicted below: There is no color option. Using the official ULD HP drivers or general HP drivers doesn't help either. These drivers don't result in a working configuration and I can't even print a test page using those. Any help or ideas are highly appreciated.

## Disclaimer I'm not robbing someone, didn't rob someone in the past and don't plan to do so anytime soon. ## Situation Imagine I own a Samsung 2.5" SSD (850, 860 or the like) which is encrypted. If it's a software encryption like Bitlocker, FileVault or VeraCrypt, I can simply reformat the disk and should be fine. But these Samsung SSDs also come with a AES-256Bit hardware encryption and I don't know the PW. **I'm not interested in the data that might be on the disk (or not).** ## Question How do I erase the hardware-encrypted disk without having the PW? My only goal is to repurpose the SSD, not getting access to the data itself.

I was thumbing through a couple of distros and found one that had samsung and jodin3 preinstalled and on the Live desktop. Does anyone know what distro this is? I was going to reload it but lost it in the shuffle. Ultimately, I'll be flashing old phones on one computer(as a hobby) and testing android linux hybrids on SSD convertibles with without keyboards/OR/bad touchscreens (for fun). Also old iPads and phones. Any suggestions welcome. Thanks in advance.

The latest Samsung driver from the vendor page General: https://support.hp.com/hk-en/drivers/selfservice/samsung-xpress-sl-m2070-laser-multifunction-printer-series/16450377 Details of the driver: https://support.hp.com/hk-en/drivers/selfservice/swdetails/samsung-xpress-sl-m2070-laser-multifunction-printer-series/16450377/swItemId/fp-191129-2 uld_V1.00.39_01.17.tar.gz does not list any appropriate driver ppd file under cups (http://localhost:631/admin) or in the ubuntu "Select Printer Driver" menu: When printing I get error messages like, when using the wrong driver: SPL ERROR - Please use the proper driver. POSITION : 0x0 (0) SYSTEM : h6fwsim/xl_op LINE : 206 VERSION : SPL 5.73 06-16-2013 ERROR CODE : 11-1113 or %! userdict dup(\004)cvn{}put (\004\004)cvn{}put /cups_handleerror { $error /ne Which ppd file should or could I use instead?

I have a Samsung 870 EVO 1TB SSD that seems to disppear at random times when installing or attempting to use my OS. It has happened on multiple different distros, but not on Windows. All SMART tests come back with great results. I know there is a bug related to some Samsung SSDs that was supposedly fixed. I'm not sure if there are other bug reports, but here's the one I found: https://bugzilla.kernel.org/show_bug.cgi?id=203475 If the answer to the question in the title is "no", is there a way to apply this fix before I've even had the chance to install a distro to disk? I'm really only guessing that this might be the problem since it works perfectly fine in a Windows environment, and there aren't any worrisome SMART results.

I made sure to check Intel's support page and download the firmware just in case the kernel didn't contain it (it did) and then I went on to apply all the usual advice for troubleshooting wifi cards that won't load. Everything looks fine, except that the card doesn't load. Ethernet works fine, wifi works fine if I use a TPlink USB key. *-network DISABLED description: Wireless interface product: Centrino Wireless-N 100 vendor: Intel Corporation physical id: 0 bus info: pci@0000:05:00.0 logical name: wlp5s0 version: 00 serial: [REMOVED] width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.13.12-200.fc34.x86_64 firmware=39.31.5.1 build 32895 100-5.uco latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:31 memory:f0100000-f0101fff The other two network devices are: *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@0000:09:00.0 logical name: enp9s0 version: 00 serial: [REMOVED] capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair resources: irq:29 memory:f0200000-f0203fff ioport:2000(size=256) *-network description: Wireless interface physical id: 2 bus info: usb@1:1 logical name: wlp0s29f7u1 serial: [REMOVED] capabilities: ethernet physical wireless configuration: broadcast=yes driver=r8188eu driverversion=5.13.12-200.fc34.x86_64 ip=[REMOVED] multicast=yes wireless=IEEE 802.11bgn Likewise, here's the module list. I'm at my wits' end here. Pointers would be appreciated. Module Size Used by snd_seq_dummy 16384 0 snd_hrtimer 16384 1 r8188eu 479232 0 lib80211 16384 1 r8188eu nft_fib_inet 16384 1 nft_fib_ipv4 16384 1 nft_fib_inet nft_fib_ipv6 16384 1 nft_fib_inet nft_fib 16384 3 nft_fib_ipv6,nft_fib_ipv4,nft_fib_inet nft_reject_inet 16384 4 nf_reject_ipv4 16384 1 nft_reject_inet nf_reject_ipv6 20480 1 nft_reject_inet nft_reject 16384 1 nft_reject_inet nft_ct 20480 10 nft_chain_nat 16384 4 ip6table_nat 16384 0 ip6table_mangle 16384 0 ip6table_raw 16384 0 ip6table_security 16384 0 iptable_nat 16384 0 nf_nat 49152 3 ip6table_nat,nft_chain_nat,iptable_nat nf_conntrack 163840 2 nf_nat,nft_ct nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack iptable_mangle 16384 0 iptable_raw 16384 0 iptable_security 16384 0 ip_set 61440 0 nf_tables 253952 240 nft_ct,nft_reject_inet,nft_fib_ipv6,nft_fib_ipv4,nft_chain_nat,nft_reject,nft_fib,nft_fib_inet nfnetlink 20480 3 nf_tables,ip_set ip6table_filter 16384 0 ip6_tables 36864 5 ip6table_filter,ip6table_raw,ip6table_nat,ip6table_mangle,ip6table_security iptable_filter 16384 0 sunrpc 647168 1 iTCO_wdt 16384 0 at24 24576 0 intel_pmc_bxt 16384 1 iTCO_wdt gpio_ich 16384 0 iTCO_vendor_support 16384 1 iTCO_wdt samsung_laptop 24576 0 iwldvm 270336 0 mac80211 1142784 1 iwldvm uvcvideo 118784 0 coretemp 20480 0 libarc4 16384 1 mac80211 videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc iwlwifi 352256 1 iwldvm videobuf2_v4l2 36864 1 uvcvideo videobuf2_common 69632 4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops snd_hda_codec_realtek 155648 1 videodev 278528 3 videobuf2_v4l2,uvcvideo,videobuf2_common snd_hda_codec_generic 98304 1 snd_hda_codec_realtek ledtrig_audio 16384 1 snd_hda_codec_generic cfg80211 1007616 4 iwldvm,iwlwifi,mac80211,r8188eu joydev 28672 0 snd_hda_intel 57344 2 pcspkr 16384 0 snd_intel_dspcfg 28672 1 snd_hda_intel snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg mc 65536 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common snd_hda_codec 172032 3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek i2c_i801 32768 0 i2c_smbus 20480 1 i2c_i801 lpc_ich 28672 0 snd_hda_core 110592 4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hwdep 16384 1 snd_hda_codec rfkill 32768 4 samsung_laptop,cfg80211 snd_seq 90112 7 snd_seq_dummy snd_seq_device 16384 1 snd_seq snd_pcm 135168 3 snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm snd 110592 15 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm soundcore 16384 1 snd acpi_cpufreq 32768 1 fuse 167936 3 zram 24576 2 ip_tables 28672 5 iptable_filter,iptable_security,iptable_raw,iptable_nat,iptable_mangle i915 2867200 3 i2c_algo_bit 16384 1 i915 drm_kms_helper 290816 1 i915 cec 61440 2 drm_kms_helper,i915 drm 630784 4 drm_kms_helper,i915 serio_raw 20480 0 sky2 73728 0 video 57344 2 i915,samsung_laptop From the journalctl, it's always Aug 26 12:45:55 MiniSamsung wpa_supplicant: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-100 Aug 26 12:46:55 MiniSamsung NetworkManager: [1629996415.3046] device (wlp5s0): set-hw-addr: set MAC address to F2:46:25:48:D0:17 (scanning) Aug 26 12:46:55 MiniSamsung kernel: iwlwifi 0000:05:00.0: Radio type=0x0-0x0-0x3 Aug 26 12:46:56 MiniSamsung kernel: iwlwifi 0000:05:00.0: Could not load the uCode section Aug 26 12:46:58 MiniSamsung kernel: iwlwifi 0000:05:00.0: Failed to run INIT ucode: -5 Aug 26 12:46:58 MiniSamsung kernel: iwlwifi 0000:05:00.0: Unable to initialize device. Aug 26 12:46:58 MiniSamsung NetworkManager: [1629996418.1368] platform-linux: do-change-link: failure changing link: failure 5 (Input/output error) Aug 26 12:51:48 MiniSamsung wpa_supplicant: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-100 Aug 26 12:51:55 MiniSamsung NetworkManager: [1629996715.2492] device (wlp5s0): set-hw-addr: set MAC address to BE:F7:0E:CD:51:C5 (scanning) Aug 26 12:51:55 MiniSamsung kernel: iwlwifi 0000:05:00.0: Radio type=0x0-0x0-0x3 Aug 26 12:51:55 MiniSamsung kernel: iwlwifi 0000:05:00.0: Could not load the uCode section Aug 26 12:51:58 MiniSamsung NetworkManager: [1629996718.1100] platform-linux: do-change-link: failure changing link: failure 5 (Input/output error) Aug 26 12:51:58 MiniSamsung kernel: iwlwifi 0000:05:00.0: Failed to run INIT ucode: -5 Aug 26 12:51:58 MiniSamsung kernel: iwlwifi 0000:05:00.0: Unable to initialize device. Aug 26 12:51:58 MiniSamsung wpa_supplicant: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-100 I tried reconfiguring it using the nm-cli Aug 26 13:00:01 MiniSamsung sudo: usenet : TTY=pts/0 ; PWD=/home/usenet ; USER=root ; COMMAND=/usr/bin/networkctl reconfigure wlp5s0 Aug 26 13:00:01 MiniSamsung audit: CRED_REFR pid=3991 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Aug 26 13:00:01 MiniSamsung sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Aug 26 13:00:01 MiniSamsung audit: USER_START pid=3991 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Aug 26 13:00:01 MiniSamsung audit: USER_END pid=3991 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Aug 26 13:00:01 MiniSamsung audit: CRED_DISP pid=3991 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Aug 26 13:00:01 MiniSamsung sudo: pam_unix(sudo:session): session closed for user root Aug 26 13:00:10 MiniSamsung wpa_supplicant: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-100 My final attempt gave this: Aug 26 14:43:41 MiniSamsung wpa_supplicant: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-100 Aug 26 14:45:42 MiniSamsung NetworkManager: [1630003542.2232] device (wlp5s0): set-hw-addr: set MAC address to 7E:2A:E0:B5:43:E5 (scanning) Aug 26 14:45:42 MiniSamsung kernel: iwlwifi 0000:05:00.0: Radio type=0x0-0x0-0x3 Aug 26 14:45:42 MiniSamsung kernel: iwlwifi 0000:05:00.0: Could not load the uCode section Aug 26 14:45:44 MiniSamsung systemd: systemd-hostnamed.service: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit systemd-hostnamed.service has successfully entered the 'dead' state. Aug 26 14:45:45 MiniSamsung audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Aug 26 14:45:45 MiniSamsung kernel: iwlwifi 0000:05:00.0: Failed to run INIT ucode: -5 Aug 26 14:45:45 MiniSamsung kernel: iwlwifi 0000:05:00.0: Unable to initialize device. Aug 26 14:45:45 MiniSamsung wpa_supplicant: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-100 Aug 26 14:45:45 MiniSamsung NetworkManager: [1630003545.0122] platform-linux: do-change-link: failure changing link: failure 5 (Input/output error) Aug 26 14:45:45 MiniSamsung audit: BPF prog-id=84 op=UNLOAD Aug 26 14:45:45 MiniSamsung audit: BPF prog-id=83 op=UNLOAD Aug 26 14:45:45 MiniSamsung wpa_supplicant: wlp5s0: CTRL-EVENT-SCAN-FAILED ret=-100 lscpi gave 05:00.0 Network controller: Intel Corporation Centrino Wireless-N 100 Subsystem: Intel Corporation Centrino Wireless-N 100 BGN Kernel driver in use: iwlwifi Kernel modules: iwlwifi systemd network devices gave ● 3: wlp5s0 Link File: /usr/lib/systemd/network/99-default.link Network File: n/a Type: wlan State: off (unmanaged) Path: pci-0000:05:00.0 Driver: iwlwifi Vendor: Intel Corporation Model: Centrino Wireless-N 100 (BGN) HW Address: 16:c8:03:78:53:87 HW Permanent Address: 78:92:9c:49:b5:d0 (Intel Corporate) MTU: 1500 (min: 256, max: 2304) QDisc: mq IPv6 Address Generation Mode: none WiFi access point: (null) (00:00:00:00:00:00) Queue Length (Tx/Rx): 4/1 Activation Policy: up Rx Packets: 0 Tx Packets: 0 Rx Bytes: 0 Tx Bytes: 0 Rx Errors: 0 Tx Errors: 0 Rx Dropped: 0

I started recently to look up for a way to permanently disable my wifi, bluetooth, NFS, Network and GPS. Unfortunately I didnt find a proper method to do that. There was the option to physically break the hardwares, but I didnt want to risk that, if I get something wrong there I wouldnt have a 2nd chance. Except of that, there was only some ways to disable the wifi but it was easy to re-enable it again. Anyways I figured out, that I need to root my device in order to remove hardware files, but the problem is I dont know WHICH files would be okay to remove. I'm using a samsung galaxy s8 with Android 9 Pie Till now I rooted my device twice and deleted hardware files, the first time I deleted wifi hardware files from the system/etc/permissions folder. That lead to brick my phone. The second time I deleted hardware files of bluetooth and nfc from: system/lib system/lib64 system/vendor/etc/init system/vendor/etc system/vendor/lib64 system/vendor/permessions surprisingly it worked, I totally disabled bluetooth and nfc. Then I wanted to proceed to remove gps (I figured out S8 aint using gps but gnss) so I removed the gnss files and folders. But this time, it bricked my phone, so I had to reinstall the samsung firmware again and now I rooted my device again. Before I start trying again, I would like to ask you, if any of you have some knowledge about this and if there is any no-go files, which I should never remove or smth. I dont really just want to try out over and over, it is taking much time to do all this... I hope somebody can help me out. Additionally, do any of you know how the network hardware is called? basically the hardware which lets you call people or just the hardware which connects to a network provider. -------------------------------------------------------------------------- The reason why I want to do this shouldnt be important right? but if you want to know why: I want to keep my privacy. I want to be able to connect to the internet only via ethernet cable and also I want to use my device more as a map to plan routes, camera, calc etc. ALOT of other people want to do this too, but nobody (after searching for over 20 hours) had the right solution. Every way I found, it was possible to reenable it easily. Thank you for taking your time and reading my issue! I hope you can help!! I will give an update about this anyways!

I've got an old Android phone with broken display and I'd like to get the data (in particular photos) out of it. I connected it to my computer but it did not mount automatically and mount says that "no medium found". With dmesg and lsusb I see that it is connected. Could anyone help me to mount it and get access the data?

$ dmesg

usb 1-1.2: new high-speed USB device number 12 using ehci-pci
usb-storage 1-1.2:1.0: USB Mass Storage device detected
scsi host6: usb-storage 1-1.2:1.0
scsi 6:0:0:0: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
scsi 6:0:0:1: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
sd 6:0:0:0: [sdb] Attached SCSI removable disk
sd 6:0:0:1: [sdc] Attached SCSI removable disk

$ lsusb

Bus 001 Device 012: ID 04e8:681d Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone

$ sudo mount /dev/sdb /mnt/pphone/

mount: /mnt/pphone: no medium found on /dev/sdb.

$ sudo lsblk -alp

/dev/sda    8:0    0 465,8G  0 disk
/dev/sda1   8:1    0   3,7G  0 part [SWAP]
/dev/sda2   8:2    0 275,8G  0 part
/dev/sda3   8:3    0   200M  0 part /boot/efi
/dev/sda4   8:4    0 186,1G  0 part /
/dev/sdb    8:16   1         0 disk
/dev/sdc    8:32   1         0 disk

I have a samsung core prime and mint 18.1 and I'm trying to copy pictures from my phone and SD card to my computer, when I plugged it in the folders with pictures are there but i can't open them or move them, It froze my entire computer until I unplugged it. How do I do transfer my stuff? Edit: When I tried switching it to ptp mode it showed me my pictures in the folders but i still couldn't move them, it said i had 2 samsungs and showed them as cameras on desktop. I installed and tried gmtp but it crashed when i tried to connect my phone

I have just installed Chromium OS on an old 32bit Samsung N130 netbook. I used the latest 32bit image (60.0.3112.102) from Arnold the Bat. Using the lscpi command , I found that it has the Realtek RTL8192E/RTL8192SE Wifi NIC which is listed as supported in the release notes. When I try to switch the wifi on using the normal settings it just doesn't go on. Having looked into this, I found that this chipset had given problems for people with this laptop before in other Linux distributions. I have encountered similar problems in the past trying to get Broadcom WiFi to work when installing Ubuntu or Debian on older Apple hardware and it could be fixed by installing an application to extract the firmware and install it e.g fwcutter I know that Chromium OS is Gentoo-based and I do not know the best way to proceed to check if the right driver is installed and to make sure that the wifi can be activated. I have read that Gentoo is for more advanced users and I miss apt-get! When I next get the chance, I will try installing Ubuntu, saving the /lib/firmware folder and then reinstall Chromium and merge the firmware folder with the Ubuntu one. It might work... Following the advice from Emmanuel Rosa below: Trying to emerge/install linux-firmware...

I'm using the printer Samsung M2825ND in my home network. It worked great so far, as well as on Linux as on Windows, but since I re-installed Arch Linux on my laptop, I cannot print any longer. Here's how I set it up: I installed, activated and started cups and avahi: pacman -S cups cups-filters ghostscript systemctl enable org.cups.cupsd.service systemctl start org.cups.cupsd.service pacman -S nss-mdns systemctl enable avahi-daemon.service systemctl start avahi-daemon.service In the file /etc/nsswitch.conf, I extended the line hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns to hosts: files mymachines myhostname mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns as described on the Arch Linux Wiki . Then I downloaded the pxlmono-Samsung driver , which I used earlier, and moved it to /usr/share/cups/model/samsung.ppd. Then I figured out the parameters with lpinfo: $ lpinfo -m | grep samsung samsung.ppd Samsung M262x 282x Series PXL driverless:ipp://samsung.local:631/ipp/print Samsung M262x 282x Series, driverless, cups-filters 1.21.2 $ sudo lpinfo -v network ipp network socket network beh network http network https network lpd network ipps network dnssd://samsung._printer._tcp.local/ network lpd://192.168.178.10/ network ipp://samsung.local:631/ipp/print There are different network options, and since I always used dnssd so far, I configure it that way: $ sudo lpadmin -p samsung -E -v 'dnssd://samsung._printer._tcp.local/' -m samsung.ppd I set the printer as my default, use A4 as paper size and activate long-edge duplex printing: $ lpoptions -d samsung $ lpoptions -o PageSize=A4 $ lpoptions -o sides=two-sided-long-edge $ lpoptions device-uri=ipp://samsung._ipp._tcp.local/ PageSize=A4 printer-info=samsung printer-location printer-make-and-model='Samsung M262x 282x Series' printer-type=16810068 sides=two-sided-long-edge But when I try to print a document using lpr document.txt, the file is just stuck in the queue with any other information. How can I find the error here?

I have a Samsung 840 PRO Series SSD and want to update its firmware in order to find an alternative solution for [this problem](https://unix.stackexchange.com/questions/333635/enabling-synchronous-trim-only) . I downloaded "Samsung Magician Software for Enterprise SSD" from [this page](http://www.samsung.com/semiconductor/minisite/ssd/download/tools.html) because Samsung only offers magician for consumer SSDs for Windows. According to the top reply on [this reddit post](https://www.reddit.com/r/linux/comments/2nrwu9/updating_samsung_evo_840_ssd_firmware_from_linux/) , it should work. However, upon trying to determine my SSD's ID, magician claims to have found no Samsung SSDs, even though the one and only storage medium currently attached to my laptop is the SSD mentioned in the first paragraph. # ./magician -L ================================================================================================ Samsung(R) SSD Magician DC Version 2.0 Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved. ================================================================================================ Magician is now configuring the environment for LSI MegaRAID SAS. Magician is now configuring the environment for LSI SAS IT/IR Controller. Magician is now configuring the environment for LSI SAS IT/IR2 Controller. Magician is now configuring the environment for LSI SAS IT/IR3 Controller. ---------------------------------------------------------------------------- | Disk | Model | Serial | Firmware | Capacity | Drive | Total Bytes | | Number | | Number | | | Health | Written | ---------------------------------------------------------------------------- No Samsung SSD found!