ID-3: /dev/sdc type: USB vendor: SanDisk model: SanDisk Ultra
Speed: 3.0 Gb/s rotation: 7200 rpm serial: rev: HP22 temp: 32 C Speed: 3.0 Gb/s serial: rev: 2B6Q scheme: MBR ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
G FORCE 6150 SE FULL
IF: enp0s7 state: up speed: 100 Mbps duplex: full mac: Type: network bridge driver: forcedeth v: kernel port: e480 OpenGL: renderer: llvmpipe (LLVM 11.0.0 128 bits) v: 4.5 Mesa 20.2.6ĭevice-1: NVIDIA MCP61 High Definition Audio vendor: Hewlett-Packardĭriver: snd_hda_intel v: kernel bus ID: 00:05.0 chip ID: 10de:03f0ĭevice-1: NVIDIA MCP61 Ethernet vendor: Hewlett-Packard Unloaded: fbdev,modesetting resolution: 1024x768~N/A Topology: Dual Core model: AMD Athlon II X2 250 bits: 64 type: MCPĪrch: K10 rev: 2 L1 cache: 256 KiB L2 cache: 2048 KiBįlags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 12054 Mobo: PEGATRON model: 2A99 v: 6.01 serial: V: N/A serial: Chassis: type: 3 serial: N/A Type: Desktop System: Hewlett-Packard product: HP 505B Microtower PC Results of running cmd as Sudo after booting from USB stick and running in COMPATIBILITY mode sudo inxi -Fxxxrz But when the installed OS runs the cmd fails most of the time (only inxi -G works consistently). NOTE # 2 - how about that ? If a USB "thumb" drive is used to boot LM 20.2 all variations of cmd appear to work correctly.
G FORCE 6150 SE DRIVER
But if true neither the Nvidia driver nor the Nouveau driver can resolve. (3) is it safe to assume that if other users were having similar problem a "bug report" would already have been submitted and hopefully fixed ? If not, the most likely cause might be that the old HP integrated display adapter is not properly supported by Linux Mint. (2) how will seeing resulting weird pattern on screen help fix bug ? Do different bugs cause different screen patterns ? (1) why would cmd complete normally but cause system to lockup 4 out of 5 attempts ? NOTE - cmd also locks up system identical to cmd (but continues to display properly I realize that Linux is very different from Windows but. This bug gets more curious with each attempt to resolve.
0 kommentar(er)
