"nomodeset" and projector

[DjSapsan]

Sorry, im from Ukraine and bad know English (and linux too)


Im on linux mint 18.3 silvia. Before had windows, then ubuntu (worked fine, but very slow) and i decided to install lightweight mint.
Hardware: HP laptop
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 21)
drivers:

dr.png

My problem: After installing i got persistent freezing after 1-5 minutes of work, cure only reboot. I decreased swap index and removed swap partition from HDD, after i noticed some improvement. But system still had freezing. After long time researching i found solution - put "nomodeset" parameter in grub. System working fine ... but. I now cant connect projector now. Im tried different solutions from internet but they won't work. Then i removed "nomodeset" and projector began work! But problem has return - my laptop freeze again... I have two option now: work without projector or use projector for single freezed picture.

How can i use projector and full-working laptop in same time?

[Hoser Rob]

I'm a bit concerned about having a package called oem-audio-hda-daily-dkms. That's basically a daily build ALSA driver. How'd that end up there?

There's also very little useful system info, copy/paste this to the terminak and copy/paste the text output here:

Code: Select all

inxi -Fxz

BTW Mint is Ubuntu based unless you installed LMDE. But the main edition has some advantages over Ubuntu, esp. the update system, Mint isn't really any faster than Ubuntu.

[DjSapsan]

Code: Select all

inxi -Fxz

Code: Select all

System:    Host: xxx Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: MATE 1.18.0 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: Hewlett-Packard product: HP 250 G4 Notebook PC v: Type1ProductConfigId
           Mobo: Hewlett-Packard model: 80C5 v: 97.45
           Bios: Insyde v: F.1E date: 12/25/2015
CPU:       Dual core Intel Celeron N3050 (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 6400
           clock speeds: max: 2160 MHz 1: 2082 MHz 2: 2132 MHz
Graphics:  Card: Intel Device 22b1 bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: fbdev (unloaded: vesa) FAILED: intel
           Resolution: 1366x768@76.00hz
           GLX Renderer: llvmpipe (LLVM 5.0, 128 bits)
           GLX Version: 3.0 Mesa 17.2.8 Direct Rendering: Yes
Audio:     Card Intel Device 2284 driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network:   Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 1000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 500.1GB (3.3% used)
           ID-1: /dev/sda model: TOSHIBA_MQ01ABF0 size: 500.1GB
Partition: ID-1: / size: 455G used: 16G (4%) fs: ext4 dev: /dev/sda2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 47.0C mobo: 27.8C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 223 Uptime: 5:16 Memory: 1540.0/3794.4MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35 

BTW Mint is Ubuntu based unless you installed LMDE. But the main edition has some advantages over Ubuntu, esp. the update system, Mint isn't really any faster than Ubuntu.

Its really faster environment for me. Chrome can open ~3 more tabs + RDP with 3 connections with same performance.

[roblm]

I would try removing the intel video driver and then the modesetting driver should be used. You’re now using the fbdev driver. Use this command: sudo apt remove xserver-xorg-video-intel

Log out and back in. Use the inxi -Gx command to check that the fbdev and vesa drivers are not loading. You should see a line similar to this but it won’t list the modesetting driver:

Display Server: X.Org 1.18:4 drivers: (unloaded: fbdev, vesa)

[DjSapsan]

Log out and back in. Use the inxi -Gx command to check that the fbdev and vesa drivers are not loading

Thanks for answer, output here
Display Server: X.Org 1.18.4 drivers: fbdev (unloaded: vesa)


[roblm]

The line from your inxi -Gx output shows the fbdev driver is loading. That should not happen now unless you still have the nomodeset parameter added to the grub file.

[DjSapsan]

The line from your inxi -Gx output shows the fbdev driver is loading. That should not happen now unless you still have the nomodeset parameter added to the grub file.

yes, but as i said, if i have no added parameter then my laptop freezing forever...

[roblm]

yes, but as i said, if i have no added parameter then my laptop freezing forever...

That was when the intel video driver was being used but now you have removed that driver, so your system should switch to using the modesetting video driver. You now want to check if the freezing occurs while using the modesetting driver. So you need to remove the nomodeset parameter from grub, or your system will switch to using the fbdev driver.

[DjSapsan]

That was when the intel video driver was being used but now you have removed that driver, so your system should switch to using the modesetting video driver. You now want to check if the freezing occurs while using the modesetting driver. So you need to remove the nomodeset parameter from grub, or your system will switch to using the fbdev driver.

I already checked - still freezing occurs. Maybe depends from spaces between words in string "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"" Maybe something else, its really weird for me...

[roblm]

"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset""

That line has double quotation marks on the end. I assume you mistakenly added the second quotation marks while adding the line to your last post? Otherwise, you would get a Syntax Error message when you tried to update grub. So you need to remove the word nomodeset and use the sudo update-grub command. Then reboot and check if the freezing occurs.

After rebooting, to verify that the modesetting driver is loaded, use this command and post the output:

Code: Select all

cat /var/log/Xorg.0.log |egrep -i "modeset|fbdev"

[DjSapsan]

I used quotes only here, i forgot about [codе][/code]. In grub there no quotes used.

Command cat /var/log/Xorg.0.log |egrep -i "modeset|fbdev" give me output

Code: Select all

[    31.879] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=cb50639e-db08-4fa7-b52a-e24402772f4b ro nomodeset acpi_osi=
[    33.434] (==) Matched modesetting as autoconfigured driver 1
[    33.434] (==) Matched fbdev as autoconfigured driver 2
[    33.435] (II) LoadModule: "modesetting"
[    33.435] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    33.472] (II) Module modesetting: vendor="X.Org Foundation"
[    33.472] (II) LoadModule: "fbdev"
[    33.473] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    33.613] (II) Module fbdev: vendor="X.Org Foundation"
[    33.722] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    33.722] (II) FBDEV: driver for framebuffer: fbdev
[    33.731] (WW) Falling back to old probe method for modesetting
[    33.732] (II) Loading sub module "fbdevhw"
[    33.732] (II) LoadModule: "fbdevhw"
[    33.732] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    33.850] (II) Module fbdevhw: vendor="X.Org Foundation"
[    33.850] (**) FBDEV(1): claimed PCI slot 0@0:2:0
[    33.850] (II) FBDEV(1): using default device
[    33.850] (II) UnloadModule: "modesetting"
[    33.850] (II) FBDEV(0): Creating default Display subsection in Screen section
[    33.850] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    33.850] (==) FBDEV(0): RGB weight 888
[    33.850] (==) FBDEV(0): Default visual is TrueColor
[    33.850] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    33.850] (II) FBDEV(0): hardware: EFI VGA (video memory: 4160kB)
[    33.850] (II) FBDEV(0): checking modes against framebuffer device...
[    33.850] (II) FBDEV(0): checking modes against monitor...
[    33.851] (--) FBDEV(0): Virtual size is 1366x768 (pitch 1366)
[    33.851] (**) FBDEV(0):  Built-in mode "current": 104.9 MHz, 60.5 kHz, 76.4 Hz
[    33.851] (II) FBDEV(0): Modeline "current"x0.0  104.92  1366 1398 1566 1734  768 772 776 792 -hsync -vsync -csync (60.5 kHz b)
[    33.851] (==) FBDEV(0): DPI set to (96, 96)
[    33.903] (**) FBDEV(0): using shadow framebuffer
[    33.952] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
[    34.099] (==) FBDEV(0): Backing store enabled
[    34.101] (==) FBDEV(0): DPMS enabled

[roblm]

I have already asked you twice to remove nomodeset from the grub file but this kernel command line from system startup shows that you still have not removed it:

[ 31.879] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=cb50639e-db08-4fa7-b52a-e24402772f4b ro nomodeset acpi_osi=

As a result, these are some of the lines that show the fbdev driver is still loading:

Code: Select all

[    33.850] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    33.850] (==) FBDEV(0): RGB weight 888
[    33.850] (==) FBDEV(0): Default visual is TrueColor
[    33.850] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)

I think you’re being confused because the modesetting driver has a similar name with the nomodeset kernel parameter.

[DjSapsan]

I have already asked you twice to remove nomodeset from the grub file but this kernel command line from system startup shows that you still have not removed it:
...
As a result, these are some of the lines that show the fbdev driver is still loading:
I think you’re being confused because the modesetting driver has a similar name with the nomodeset kernel parameter.

I already said, i cant remove parameter, because without parameter my laptop freezing every time.
If i confused, what exactly string should i use?

[roblm]

I’ve looked over all your posts again and I see no evidence that you have tested removing nomodeset after using this command to remove the intel driver: sudo apt remove xserver-xorg-video-intel

I want to see evidence that the modesetting driver is really being loaded when the cat /var/log/Xorg.0.log |egrep -i "modeset|fbdev" command is used.

[DjSapsan]

I’ve looked over all your posts again and I see no evidence that you have tested removing nomodeset after using this command to remove the intel driver: sudo apt remove xserver-xorg-video-intel

I want to see evidence that the modesetting driver is really being loaded when the cat /var/log/Xorg.0.log |egrep -i "modeset|fbdev" command is used.

Output

Code: Select all

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'xserver-xorg-video-intel' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 317 not upgraded.

You can look entire process of freezing after removing parameter
Youtube video //freezing time at 1:55

[roblm]

I didn’t ask you to use the sudo apt remove xserver-xorg-video-intel command again. You already did that, but since that time, you have not posted any info to verify that your system is using the modesetting driver, so that it can be tested to see if it works better than the intel driver in preventing freezing.

The video shows that this time the nomodeset parameter was removed from the kernel command line at startup. The desktop freezing did not occur immediately, so there was plenty of time to use the cat /var/log/Xorg.0.log |egrep -i "modeset|fbdev" command and copy it’s output.

There appears to be a communication problem here, so I’m finished with my help in this topic. Perhaps someone else may attempt to help.

[DjSapsan]

cat /var/log/Xorg.0.log |egrep -i "modeset|fbdev"

PHOTO

Impossible to select whole text, when i begin selecting text its immediately freezing. Hope i catch needed part of output.