Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Brightness problems (and nomodeset?)

  1. #11
    Join Date
    Jan 2009
    Beans
    14

    Re: Brightness problems (and nomodeset?)

    Quote Originally Posted by BenginM View Post
    whilst the machine boots with nomodeset , run $ [B]lspci -knn , that should tell you the kernel driver in use for the Intel graphic .

    or better yet , run $ inxi -G , if inxi is not present ... sudo apt install inxi

    I suppose sudo lshw -C video , should detail the exact Intel graphic model ..
    Thank you! Looks like it's a "Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller"....
    Code:
    chris@bali-blue:~$ inxi -G
    Graphics:  Card: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
               Display Server: X.Org 1.19.3 drivers: vesa (unloaded: modesetting,fbdev)
               Resolution: 1368x768@0.00hz
               GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 128 bits)
               GLX Version: 3.0 Mesa 17.0.3
    chris@bali-blue:~$ sudo lshw -C video
      *-display UNCLAIMED       
           description: VGA compatible controller
           product: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
           vendor: Intel Corporation
           physical id: 2
           bus info: pci@0000:00:02.0
           version: 21
           width: 64 bits
           clock: 33MHz
           capabilities: pm msi vga_controller bus_master cap_list
           configuration: latency=0
           resources: memory:90000000-90ffffff memory:80000000-8fffffff ioport:f000(size=64) memory:c0000-dffff
    chris@bali-blue:~$ lspci -knn
    00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 21)
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [1028:0725]
    	Kernel driver in use: iosf_mbi_pci
    00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21)
    	DeviceName:  Onboard IGD
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1028:0725]
    	Kernel modules: i915
    00:0b.0 Signal processing controller [1180]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:22dc] (rev 21)
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [1028:0725]
    	Kernel driver in use: proc_thermal
    	Kernel modules: processor_thermal_device
    00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 21)
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [1028:0725]
    	Kernel driver in use: xhci_hcd
    00:1a.0 Encryption controller [1080]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:2298] (rev 21)
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [1028:0725]
    	Kernel driver in use: mei_txe
    	Kernel modules: mei_txe
    00:1b.0 Audio device [0403]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 21)
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [1028:0725]
    	Kernel driver in use: snd_hda_intel
    	Kernel modules: snd_hda_intel
    00:1c.0 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 [8086:22c8] (rev 21)
    	Kernel driver in use: pcieport
    	Kernel modules: shpchp
    00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 21)
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [1028:0725]
    	Kernel driver in use: lpc_ich
    	Kernel modules: lpc_ich
    00:1f.3 SMBus [0c05]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller [8086:2292] (rev 21)
    	Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller [1028:0725]
    	Kernel modules: i2c_i801
    01:00.0 Network controller [0280]: Intel Corporation Wireless 3160 [8086:08b3] (rev 83)
    	Subsystem: Intel Corporation Dual Band Wireless AC 3160 [8086:8470]
    	Kernel driver in use: iwlwifi
    	Kernel modules: iwlwifi
    Further updates to come!

  2. #12
    Join Date
    Jun 2010
    Location
    Underneath!
    Beans
    381
    Distro
    Xubuntu Development Release

    Re: Brightness problems (and nomodeset?)

    Code:
    Kernel driver in use: iosf_mbi_pci
    00:02.0 VGA  compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium  Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller  [8086:22b1] (rev 21)
        DeviceName:  Onboard IGD
        Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1028:0725]
        Kernel modules: i915

    VendorId: 8086
    Chipset ID: 22b1

    Then if we follow this link you will find out your chipset in the Eighth generation table which is HD Graphics 400 ... to be exact! which is supposedly supported under GNU/Linux and it looks like it has been supported since kernel 3.9

    when you run: sudo lshw -C cpu

    you should see the exact CPU ..

    ##

    Code:
    Loading
    
    The Intel kernel module should load fine automatically on system boot. 
    If it does not happen, then: 
    
    
    
    • Make sure you do not have nomodeset or vga= as a kernel parameter, since Intel requires kernel mode-setting.
    • Also, check that you have not disabled Intel by using any modprobe blacklisting within /etc/modprobe.d/ or /usr/lib/modprobe.d/.
    source: https://wiki.archlinux.org/index.php/intel_graphics

    I want you to try something , boot without nomodeset or any other parameter , when the screen goes black .. switch to a virtual console by pressing Ctrl+Alt+F3 , you have consoles from F2 to F6 , F7 is desktop session with X running , now login with your username and passd , run the following commands :

    sudo apt-get update
    sudo apt-get dist-upgrade
    sudo apt-get install --reinstall xserver-xorg-video-intel

    after that , cd to /etc/modprobe.d $ cd /etc/modprobe.d , and cat the files in there to make sure the intel i915 kernel driver is not blacklisted ,
    for example, in my system..
    sary@tru:/etc/modprobe.d$ ls -l
    total 16
    -rw-r--r-- 1 root root 154 Nov 30 2016 amd64-microcode-blacklist.conf
    -rw-r--r-- 1 root root 127 Feb 7 18:27 dkms.conf
    -rw-r--r-- 1 root root 154 Nov 10 2016 intel-microcode-blacklist.conf
    -rw-r--r-- 1 root root 379 Jul 28 2016 mdadm.conf
    sary@tru:/etc/modprobe.d$ cat intel-microcode-blacklist.conf
    # The microcode module attempts to apply a microcode update when
    # it autoloads. This is not always safe, so we block it by default.
    blacklist microcode

    if you see a line with : blacklist i915 in one of these files ,remove that line, or place a # at the begining of the line.

    now , maybe it's a good idea to add i915 to /etc/modules , as we don't know yet as to why it's not loaded therefore you get a black screen for some reason..

    so , got back to the /etc directory cd .. , and open the file with nano : sudo nano /etc/modules , type i915 in a separate line there , save by pressing Ctrl+x, select Yes , then hit enter.

    Now reboot without nomodeset , sudo reboot

    Do you still get stuck in a black screen..! if yes then we need to have a look at some logs..
    Last edited by BenginM; July 31st, 2017 at 06:12 AM. Reason: add/info
    GNU / Linux Being a newbie is no excuse for being lazy! I'm only exuding positive energy, And Always Learning Something. IRC'in Freenode #ubuntu / sary SSHin' with mosh



  3. #13
    Join Date
    Jun 2010
    Location
    Underneath!
    Beans
    381
    Distro
    Xubuntu Development Release

    Re: Brightness problems (and nomodeset?)

    excuse me , this was a duplicated post!
    Last edited by BenginM; July 31st, 2017 at 06:14 AM.
    GNU / Linux Being a newbie is no excuse for being lazy! I'm only exuding positive energy, And Always Learning Something. IRC'in Freenode #ubuntu / sary SSHin' with mosh



  4. #14
    Join Date
    Jan 2009
    Beans
    14

    Re: Brightness problems (and nomodeset?)

    Okay... I'm not getting the console when I press control-alt-F3 at the black screen, just more black. I do get the console login by pressing control-alt-F3 at the X login after booting with nomodeset.
    Last edited by chrisk0; July 31st, 2017 at 05:38 PM. Reason: For clarity in the last part.

  5. #15
    Join Date
    Jun 2010
    Location
    Underneath!
    Beans
    381
    Distro
    Xubuntu Development Release

    Re: Brightness problems (and nomodeset?)

    Intels GPU needs KMS enabled , and bootin' with nomodeset disable is it , and the brightness control.
    GNU / Linux Being a newbie is no excuse for being lazy! I'm only exuding positive energy, And Always Learning Something. IRC'in Freenode #ubuntu / sary SSHin' with mosh



  6. #16
    Join Date
    Jan 2009
    Beans
    14

    Re: Brightness problems (and nomodeset?)

    Thank you.

    I have reverted this device to Windows 10 home.

  7. #17
    Join Date
    Oct 2008
    Beans
    4

    Re: Brightness problems (and nomodeset?)

    Well, that's one way to deal with it

    Kernel 4.10.0-28 also kinda-sorta broke the brightness control on my Lenovo Thinkpad T400 with integrated sh!tty Intel graphics,

    Code:
    inxi -G
    Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller
               Display Server: X.Org 1.19.3 driver: intel Resolution: 1440x900@60.00hz
               GLX Renderer: Mesa DRI Mobile Intel GM45 Express GLX Version: 2.1 Mesa 17.0.7

    Code:
    sudo lshw -C video
      *-display:0             
           description: VGA compatible controller
           product: Mobile 4 Series Chipset Integrated Graphics Controller
           vendor: Intel Corporation
           physical id: 2
           bus info: pci@0000:00:02.0
           version: 07
           width: 64 bits
           clock: 33MHz
           capabilities: msi pm vga_controller bus_master cap_list rom
           configuration: driver=i915 latency=0
           resources: irq:32 memory:f4400000-f47fffff memory:d0000000-dfffffff ioport:1800(size=8) memory:c0000-dffff
      *-display:1 UNCLAIMED
           description: Display controller
           product: Mobile 4 Series Chipset Integrated Graphics Controller
           vendor: Intel Corporation
           physical id: 2.1
           bus info: pci@0000:00:02.1
           version: 07
           width: 64 bits
           clock: 33MHz
           capabilities: pm bus_master cap_list
           configuration: latency=0
           resources: memory:f4200000-f42fffff
    Brightness adjust (+) now has some overly fancy ramping effect instead of the usual hard stepping between the 16 brightness modes. However, turning the brightness down causes flicker and in a maximum of 4 steps completely turns off the backlight. Ramping back up doesn't work, one needs to close the lid and re-open it. Sometimes that also happens with the lock screen, where the screen is set to slowly auto-dim to the lowest value. It's not locked, but you can't really see much as the backlight is off.

    So...4.10.0-28 is bogus and needs to be avoided on older Intel machines apparently.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •