Quantcast
Channel: Ubuntu Forums - Hardware
Viewing all 20190 articles
Browse latest View live

touchpad gestures not working

$
0
0
fresh install on a brand new laptop everything seems to work out of the box
but... touchpad gestures are not working

anyway to check this out?

Server + Ruby on Rails - Chromebook vs Raspberry Pi 4 ???

$
0
0
Thank you in advance for your help!


I want to install Ubuntu Server + Ruby on Rails.


Would a Chromebook or Raspberry Pi 4 be a better inexpensive platform for this?


Thank you!

[ubuntu] fan always working

$
0
0
I updated my Ubuntu to 19.10. Since then, every 40 seconds the fan starts working for 5 seconds and stops. This happens after I start a X session, even if I have no application started. Doesn't happen if I only login in the console.

I use Cinnamon. The top command shows the cinnamon process is using around 3% of CPU. Sometimes goes to 10% of the CPU. But doesn't seem to be related with the fan.

The sensors command shows that the temperature is always rising above 50°C immediatly before the fan starts working:

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +53.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +49.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +100.0°C, crit = +100.0°C)
Core 2: +49.0°C (high = +100.0°C, crit = +100.0°C)
Core 3: +49.0°C (high = +100.0°C, crit = +100.0°C)

Since then, I tried other window managers. The problem persists, but with different times. The given values are average, and not very precise, but the fan always starting working at regular intervals:
xfce: 90 seconds
Gnome and Unity: 180 seconds

I also tried a live usb installation to boot in Ubuntu 18.04, similar to what I had before the update. The fan problem didn't happen, and the sensors command shows that the temperatures never rises above 40°C.

This is very annoying because I always expect the computer to be quiet when it is not doing any intensive processing. Please tell if you need any more information to help diagnose and solve this problem.

[ubuntu] Power Supply or Motherboard

$
0
0
One of my computers is dead. I tested the PS with a paper clip. I attached two fans to it. They all spun. Next, i tested that PS on my working computer. It was dead. What is going on?

Can't change SATA mode from optane

$
0
0
I bought a laptop which has this ssd https://www.westerndigital.com/produ...s/pc-sn520-ssd
bios sata mode is set to Optane without raid, and Ubuntu installer doesn't detect the ssd. I've searched in Google and you have to change the mode in BIOS but i cant do so. I've also read that you can change it in windows 10 but I didn't really understand how, could someone help me? Thanks in advance.

Lubuntu Laptop - Suspend via terminal = no issue. Suspend via closed lit = issue

$
0
0
Hardware: Compaq Presario M2000 (Service tag M2105US p/n: EC214UA#ABA)
(Manual: https://data2.manualslib.com/pdf2/28...d4817c58f23449 )

Symptom:
Code:

sudo systemctl suspend
works as intended. System suspends (fans off / display off. Keystroke wakes system - login prompted)

Close lid - system suspends(?) Open Lid/Keystroke - Fans Spin, Display is back lit, but no image, and no known key prompts display text on screen.

Issue has only existed since changing from xubuntu to Lubuntu.

Code:

  • x@x:~$ lsusb
  • Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  • Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  • Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  • x@x:~$ lsb_release -d
  • Description:    Ubuntu 18.04.3 LTS

As always, thank you all for your help! Any and all suggestions/requests, just let me know!

:mrgreen: <-Me...Green as Green can be when it comes to Linux!

PAC7302 Camera Drivers & Software

$
0
0
Our college has a number of digital microscopes and endoscopes that use PAC7302 sensors. Although based on old technology these instruments are fairly new and we don't want (and can't afford) to replace them.

We are looking to use these on Ubuntu 18.04 LTS and Kubuntu 19.10. I have read elsewhere that GSPCA supports PAC7302 but references look out of date.

Can anyone recommend drivers and a good software application that would be best for this class of device and application?

Bugged default drivers for Radeon HD 6650M in 18.04 LTS. What to do next?

$
0
0
Hola good folks,

So, I have a laptop with...

  • CPU ---- Intel Core i3-2310m (Sandybridge Mobile)
  • iGPU --- Intel HD Graphics 3000 (Sandybridge Mobile)
  • dGPU -- Radeon HD 6650M (TeraScale 2 (VLIW5) "Evergreen" - Northern Islands)


Well... the default drivers that ship with Ubuntu (Kubuntu, actually) 18.04 LTS are pretty bugged for this system. Near as I can tell, the drivers for the dGPU don't properly support OpenGL somewhere around OpenGL 3.1 and up. This is most reproducible with Blender, wherever I invoke the Eevee render, as this requires OpenGL 3.3+ to work properly.

If it was *JUST* 3D, I wouldn't have too much problems with it, but there are also issues with the desktop environment. Window frames will sometimes get flickering ghost images of what's under them when they are moved (broken transparency), or disappear entirely. With MPV player (Probably also using OpenGL) if I pause the video, or rapidly minimize/maximize the window, the video gets stuck in a short , flickery loop. Sometimes this will cause the backdrop to go all black too. If I do enough screwing around, eventually the graphical problems will get to the point of making the desktop unrecognizable, unstable, and I am left with no choice but to restart.

Here is some more details.

  • The package that seems to be supplying my drivers is Mesa (v19.0.8). (This is just userland OpenGL though, right?)
  • The actual 3D driver is r600g, which should be correct for the TeraScale 2 - Northern Islands. (Mesa matrix decoder ring doesn't find the "HD 6650m", but does find the "HD 6650" as r600g/TeraScale 2)
  • Command "lspci" lists my GPU as [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] (rev ff) (For a time, I believe this was showing up as TURKS, not Whistler. Hopefully that means it's being worked on!?)
  • Command "lsmod" lists the Kernel module as "radeon"
  • "modinfo radeon" does not show "Whistler" as an available firmware. I have no idea what it's actually using!


Some other notes, in order of preference.

  • I have working switchable graphics; DRI_PRIME=n works very well. (And I'd like to keep it that way)
  • I'm using KDE Plasma DE. (And I'd like to keep it that way)
  • I'm using Kubuntu 18.04 LTS. (And I'd like to keep it that way)


The reason I'm here is that I'm not really sure what to do about this? On the one hand, everything seems to be using the best available option. On the other hand, it's not working right. Is this a Mesa problem, a r600g problem, or a kernel module problem? The fglrx.ko module possibly (probably) has the correct firmware, but that's depreciated since Kernel version 4.4, and I'm on 4.15. How do I even work with this? Do I need to switch distros/versions? Or is that even going to work? Can I shoehorn in fglrx.ko? Or is that even going to work? Is this a known problem, and a fix is on the way? Will there even be a fix? Do I have to just live with this?

:confused:

I'd like to at least get the dedicated GPU working 100%. Worst case, seems like I (a) switch distros to use an older kernel, (b) disable the iGPU/switchable graphics, and (c) take the power usage hit. I *REALLY* don't want to have to do this . . .

Lubuntu 19.04 will not connect to Visible r2 phone

$
0
0
Tried connecting the R2 without a driver.
I could send a file from the desktop to the phones giant memory card, (256GB) but only one file @ a time.
It would not create directories or copy anything inside a directory.
I then installed the drover for Linux included with the phone.
After a ton of reboots, trying it every way possible...even trying linux file transfer program...no good.

Anyone encountered this?
It blows my mind Linux does not snap right to one another. Kind of insane.

[ubuntu] S.M.A.R.T. Data Conundrum. Opinions Please.

$
0
0
I have a 7 Ubuntu 18.04 LTS machines with the same specs including 4 - 1TB hard drives in arrays. A few of the drives kept dropping out, I suspected that the power connection to the drive was not good since I could not feel the drive spinning. I fiddled with the power connections and got the drives to run reliably. Those problems seem to have been bad patch cables. I also decided to monitor the situation and see if the drive was at fault. On two of the drives I had began getting indications that the drives were failing due "Spinup Retry Count". I even bought replacement drives, however before I could get around to replacing them the S.M.A.R.T. data returned to normal and the "Spinup Retry Count" is now at 0. I'm using Gnome-disks to read the S.M.A.R.T data.

I know the safe thing to do is replace the drives but it also seems to me that the drives are actually fine. It seem that the S.M.A.R.T. date is reset from time to time, which I wasn't aware of until now.

What's you Opinion?

unable to lead NVIDIA Corporation GM107M [GeForce GTX 960M]

$
0
0
I have been trying to get this graphics card to work on ubuntu for over a year now with no luck, but i think now i am able.
Not too long ago my nvidia drivers were blacklisted under the following command...

Code:

jdosio@2io-01:~$ sudo cat /var/log/gpu-manager.log
[sudo] password for jdosio:
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/5.0.0-37-generic/updates/dkms
Found nvidia module: nvidia-drm.ko
Looking for amdgpu modules in /lib/modules/5.0.0-37-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? no
Is nouveau blacklisted? yes
Is nvidia kernel module available? yes
Is amdgpu kernel module available? no
Vendor/Device Id: 8086:191b
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:139b
BusID "PCI:2@0:0:0"
Is boot vga? no
Error: can't access /sys/bus/pci/devices/0000:02:00.0/driver
The device is not bound to any driver.
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
    card0-HDMI-A-1
output 1:
    card0-eDP-1
Number of connected outputs for /dev/dri/card0: 2
Does it require offloading? yes
last cards number = 2
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2
Has the system changed? No
Intel IGP detected
Intel hybrid system
Creating /usr/share/X11/xorg.conf.d/11-nvidia-prime.conf
Setting power control to "on" in /sys/bus/pci/devices/0000:02:00.0/power/control
Loading nvidia with "no" parameters

which clearly is no longer blacklisted and is also loaded,
trying

Code:

jdosio@2io-01:~$ nvidia-detector
none

Not sure what that means exactly if it said before it was loaded but to be fair i was not quite sure what loaded ment in that context either to be honest.
Anyway trying to switch to the nvidia driver through the regular nvidia-settings panel has not worked, currently my settings say i am using "Intel® HD Graphics 530 (Skylake GT2)" for "graphics", anyone know what i should do to get the nvidia 430 driver to run ?

[ubuntu] Bluetooth connect and reconnects constantly

$
0
0
Hello. I bought some new Bluetooth earbuds. Soundpeats Truengine 2. They connect via Bluetooth, work for a few seconds and then start pairing again. They connect and disconnect continuously. It is interesting because I have a pair of Soundpeats Truecapules that work flawlessly. I am also using 2 other Bluetooth speakers without a problem. Any ideas what might be going on here?

Thank you in advance for your help.

[ubuntu] Understanding Psensor

$
0
0
I hope that this is not an inane question. I really don't understand what the Psensor is displaying it seems to repeat the same thing.
Attached Images

[ubuntu] Unable to find what's wasting all my partition storage

$
0
0
This is really odd. I discovered my root partition was full when I was trying to use TAB on terminal and was getting error which ended up bash unable to write on disk, because it was full.

I have one partition for /boot, one for swap, one for / and one for /home.

Confirming on GPated, / has 100GB size, and 5,79GB free after I deleted some stuff specially on /var/cache.

But QDirStat reports / with a size o 8,5GB. df repots:

Code:

/dev/sda3                102686324    96615528    811600 100% /
ll:

Code:

$ ll
total 109
drwxr-xr-x  25 root  root    4096 nov 15 06:10 ./
drwxr-xr-x  25 root  root    4096 nov 15 06:10 ../
drwxr-xr-x  2 root  root    4096 nov  8 06:57 bin/
drwxr-xr-x  4 root  root    1024 nov 27 06:52 boot/
drwxr-xr-x  2 root  root    4096 jul 24 19:08 cdrom/
drwxr-xr-x  19 root  root    4400 nov  4 12:55 dev/
drwxr-xr-x 150 root  root  12288 dez 11 16:50 etc/
drwxr-xr-x  5 root  root    4096 jul 24 20:14 home/
lrwxrwxrwx  1 root  root      32 nov 15 06:10 initrd.img -> boot/initrd.img-5.0.0-36-generic
lrwxrwxrwx  1 root  root      32 nov 15 06:10 initrd.img.old -> boot/initrd.img-5.0.0-35-generic
drwxr-xr-x  23 root  root    4096 jul 24 21:38 lib/
drwxr-xr-x  2 root  root    4096 fev  9  2019 lib64/
drwx------  2 root  root  16384 jul 24 19:06 lost+found/
drwxr-xr-x  3 root  root    4096 jul 24 19:19 media/
drwxr-xr-x  2 root  root    4096 fev  9  2019 mnt/
drwxr-xr-x  3 root  root    4096 jul 24 21:38 opt/
dr-xr-xr-x 352 root  root      0 out 20 18:09 proc/
drwx------  4 root  root    4096 jul 24 19:45 root/
drwxr-xr-x  43 root  root    1480 dez 11 16:49 run/
drwxr-xr-x  2 root  root  12288 out 12 18:35 sbin/
drwxr-xr-x  8 hikari hikari  4096 out 18 13:28 share/
drwxr-xr-x  12 root  root    4096 jul 25 01:49 snap/
drwxr-xr-x  2 root  root    4096 fev  9  2019 srv/
dr-xr-xr-x  13 root  root      0 dez  8 17:06 sys/
drwxrwxrwt  20 root  root    4096 dez 11 16:55 tmp/
drwxr-xr-x  11 root  root    4096 ago  9 15:33 usr/
drwxr-xr-x  17 root  root    4096 set 19 17:16 var/
lrwxrwxrwx  1 root  root      29 nov 15 06:10 vmlinuz -> boot/vmlinuz-5.0.0-36-generic
lrwxrwxrwx  1 root  root      29 nov 15 06:10 vmlinuz.old -> boot/vmlinuz-5.0.0-35-generic

Is there any way of finding out what's wasting over 90GB?

[ubuntu] i7-1065G7 with Dell WD19TB : It cannot detect second monitor

$
0
0
Hi.

I'm using XPS 2in1 7390 (Icelake: i7-1065G7 - Gen 11 GPU) with WD19TB (thunderbolt 3 docking station).

It's working well the extend display while the two monitors are being detected fully .

But Ubuntu 19.10 cannot detect the second monitor and display as only mirror mode.

The drivers are latest.


Quote:

$ sudo lspci
00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Device 8a52 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
00:05.0 Multimedia controller: Intel Corporation Device 8a19 (rev 03)
00:07.0 PCI bridge: Intel Corporation Device 8a1d (rev 03)
00:07.2 PCI bridge: Intel Corporation Device 8a21 (rev 03)
00:0d.0 USB controller: Intel Corporation Device 8a13 (rev 03)
00:0d.2 System peripheral: Intel Corporation Device 8a17 (rev 03)
00:0d.3 System peripheral: Intel Corporation Device 8a0d (rev 03)
00:12.0 Serial controller: Intel Corporation Device 34fc (rev 30)
00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
00:14.3 Network controller: Intel Corporation Device 34f0 (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30)
00:15.3 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #3 (rev 30)
00:16.0 Communication controller: Intel Corporation Device 34e0 (rev 30)
00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 30)
00:1d.7 PCI bridge: Intel Corporation Device 34b7 (rev 30)
00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
00:1f.3 Audio device: Intel Corporation Device 34c8 (rev 30)
00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI Controller (rev 30)
2c:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
2d:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
2d:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
2e:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] (rev 06)
59:00.0 Non-Volatile memory controller: Device 1e0f:0001
5a:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)

Please let me know your idea.

Thanks in advance,

Dell WD19TB Dock - Failed to Authorize Device

$
0
0
I have a Dell XPS 13 7390 "Developer Edition" that came from Dell installed with 18.04.3 LTS. We ordered a WD19TB Thunderbolt dock to connect peripherals and I can't get it working right. When I first plugged in the dock, an external HDMI monitor connection worked correctly, but none of the USB 3 ports worked, nor did the gigabit ethernet. When I looked in devices -> Thunderbolt, I saw that the system had detected the dock, but that it was in a "pending" state:



I clicked on the dock name in that screen and this dialog popped up, asking me to "authorize and connect" to the dock:



I click the "authorize and connect" button, and after typing in my sudo password, I got another dialog stating "Failed to authorize device: kernel error."



After this, back on the devices->Thunderbolt screen, the dock shows with an error:



Dell support directed me to this forum for assistance. Are there any special drivers that I have to install? What do I have to do to get this WD19TB dock working?

Cannot use iGPU and stuck in software rendering

$
0
0
I recently built a new system using an ASrock Rack E3C246D4U motherboard and a Xeon E-2288g. The box has no GPU installed and my intention is to use the iGPU that comes with the CPU. I installed Ubuntu 19.10 (desktop version) via the IPMI and rebooted only to have the system freezes at a purple screen. Couple more reboots and the same result… When it is in this state, the directly connected keyboard and mouse are unresponsive as are the virtual ones via the IPMI interface—well, sometimes the mouse will wiggle around but the keyboard might as well be unplugged. The only way that I have been able to get it to fully boot and bring up Gnome is to add nomodeset via the GRUB edit feature when booting and then permanently add it to the grub file once the system is up. (I also removed the quiet-splash flag from the grub file so that I could better see what was going on during boot.) Now it boots but I am stuck with a 640x480, 8-bt color, slow as dirt UI because the iGPU is being bypassed in favor of software rendering. Does anyone have ideas on how I can regain the use of the iGPU and avoid the freezing of the system?


Other things to note. Once I was able to get it up and running, I did do a sudo apt update/ apt upgrade AND set the default graphics in the BIOS to use the iGPU.


Also (I am a bit new to Linux) where can I find information on what gets disabled when nomodeset is applied and or find system logs of possible errors/conflicts occurring at boot?

Many thanks in advance for any and all ideas and support offered!

Problem setting up Canon printer

$
0
0
I'm setting up my laptop after converting to Ubuntu 19.10 from windows and having difficulty with the printer. I have a Canon Pixma 8520. Trying to set it up through CUPS and the printer is not responding. The printer and laptop are on a wireless network. i installed the driver from a Deb file because I couldn't find one for my printer from the list on the Ubuntu install.

In CUPS I set up the printer and driver, calling it Canonxx, It is set up with the ip address found in the terminal by pinging myprinter.

The other canonpixma i set up in CUPS with the IP address I found on the printer's screen.

When I searched for network printers in CUPS I did not see any, so I set both up manually using the IP addresses above.

After setting them up I checked in the terminal and got the following:

Code:

$ lpstat -a
canonpixma accepting requests since Thu 12 Dec 2019 08:05:50 PM PST
CanonXX accepting requests since Thu 12 Dec 2019 08:08:12 PM PST

and

Code:

$ ping myprinter
PING myprinter.Home (198.105.244.23) 56(84) bytes of data.

when I check the Canonxx printer in CUPS I get

Quote:

CanonXX (Processing, Accepting Jobs, Not Shared)
Driver: Canon TR8500 series Ver.5.50 (color, 2-sided printing)
Connection: http://198.105.244.23
But I cant print anything. Nothing on the canonpixma and with the CanonXX, first I get a message that I am connected to the printer and then that the printer is not responding.

I'm just getting started in Linux so am probably missing a simple step. Can anyone point me in the direction of how to correctly set up my printer?

Cannot access flash-drive/usb-drive

$
0
0
My USB flash drive is no longer working after using it at one of this self-service-photo-print-machines. The software on that machine crashed when I was scrolling through my photos on my flash drive and just wanted to change the viewing order of the files. I was not able to read anything from the flash drive after that crash.

Inserting the drive on my Ubuntu 18.04.3 LTS and looking into the /var/log/syslog, I see the following (related) error messages:

Code:

    kernel: [2661765.200803] usb-storage 4-1:1.0: USB Mass Storage device detected
    kernel: [2661765.201724] scsi host6: usb-storage 4-1:1.0
    mtp-probe: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-1"
    mtp-probe: bus: 4, device: 9 was not an MTP device
    upowerd[2591]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:1.0
    upowerd[2591]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb4/4-1
    org.xfce.FileManager[2344]: thunar-volman: Unsupported USB device type "usb".
    org.xfce.FileManager[2344]: thunar-volman: Unsupported USB device type "usb-storage".
    kernel: [2661766.632180] scsi 6:0:0:0: Direct-Access    JetFlash Transcend 64GB  1100 PQ: 0 ANSI: 6
    kernel: [2661766.632813] sd 6:0:0:0: Attached scsi generic sg2 type 0
    kernel: [2661766.634459] sd 6:0:0:0: [sdb] 123404288 512-byte logical blocks: (63.2 GB/58.8 GiB)
    kernel: [2661766.635203] sd 6:0:0:0: [sdb] Write Protect is off
    kernel: [2661766.635205] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
    kernel: [2661766.636058] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    kernel: [2661766.640941] scsi_io_completion: 4 callbacks suppressed
    kernel: [2661766.640944] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    kernel: [2661766.640947] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
    kernel: [2661766.640949] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
    kernel: [2661766.640952] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
    kernel: [2661766.640953] print_req_error: 4 callbacks suppressed

The flash drive seems to be recognized, although the size is wrong, it has 128 GB.

After those messages, however, the Buffer I/O error appears:

Code:

    kernel: [2661766.640954] print_req_error: I/O error, dev sdb, sector 0
    kernel: [2661766.640957] buffer_io_error: 3 callbacks suppressed
    kernel: [2661766.640958] Buffer I/O error on dev sdb, logical block 0, async page read
    kernel: [2661766.641870] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    kernel: [2661766.641873] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
    kernel: [2661766.641875] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
    kernel: [2661766.641877] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00

The following part is repeated 8 times:

Code:

    kernel: [2661766.641878] print_req_error: I/O error, dev sdb, sector 0
    kernel: [2661766.641881] Buffer I/O error on dev sdb, logical block 0, async page read
    kernel: [2661766.642774] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    kernel: [2661766.642776] sd 6:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current]
    kernel: [2661766.642777] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
    kernel: [2661766.642778] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00

The final part is as follows:

Code:

    kernel: [2661766.649002] print_req_error: I/O error, dev sdb, sector 24
    kernel: [2661766.649004] Buffer I/O error on dev sdb, logical block 3, async page read
    kernel: [2661766.650832]  sdb: unable to read partition table
    kernel: [2661766.653438] sd 6:0:0:0: [sdb] Attached SCSI removable disk
    org.xfce.FileManager[2344]: thunar-volman: Unknown block device type "disk".
    colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1

I am worried about the unable to read partition table part, but that might be related to the Buffer I/O message.

I have no idea how to restore my flash drive, as # smartctl -a /dev/sdb results only in

Code:

    /dev/sdb: Unknown USB bridge [0x8564:0x1000 (0x1100)]
    Please specify device type with the -d option.

Manually setting the type with # smartctl -d scsi -a /dev/sdb gives the following output (local time and serial number removed as they should not be important)

Code:

    === START OF INFORMATION SECTION ===
    Vendor:              JetFlash
    Product:              Transcend 64GB
    Revision:            1100
    Compliance:          SPC-4
    User Capacity:        63.182.995.456 bytes [63,1 GB]
    Logical block size:  512 bytes
    LU is fully provisioned
    scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
    Logical Unit id:      0x00010200000608040x2020030102060804error: SCSI name string
    Device type:          disk
    scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
    SMART support is:    Available - device has SMART capability.
    SMART support is:    Disabled
    Temperature Warning:  Disabled or Not Supported

    === START OF READ SMART DATA SECTION ===
    SMART Health Status: OK
    Current Drive Temperature:    0 C
    Drive Trip Temperature:        0 C

    Error Counter logging not supported

    scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
    Device does not support Self Test logging

Again, wrong size.

Any suggestions how I could try to get access to my flash-drive are greatly appreciated!

Very annoying lag Linux Ubuntu 18.04.3 LTS with external display from Samsung

$
0
0
Hi all,

I'm new to this forum and wanted to solve this problem as much as I could no my own but it's starting to get reeeally annoying now.

So I have an HP Omen with an Intel® Core™ i7-8750H CPU @ 2.20GHz × 12 processor and GeForce GTX 1060/PCIe/SSE2 graphicscard.
I configured as a dual boot. Study on WIndows, developing on Linux. The problem is an enormous lag when working under Linux 18.04.3. It's almost not workable anymore.

Does this have something to with my current drivers or maybe in the NVIDIA X server settings?

The Samsung model is: S24F 352FHU

Hoping you guys got the answer :)

Cris

Viewing all 20190 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>