[SOLVED] Intel G31 Chipset not working Mint 20.1

Forum rules
Before you post please read this
User avatar
SMG
Level 15
Level 15
Posts: 5593
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Intel G31 Chipset not working Mint 20.1

Post by SMG »

tuxyminty wrote:
Sun May 16, 2021 10:19 pm
Here is the link generated by the journalctl command given by you.

https://termbin.com/4xkyz
Did you try re-installing LM20 and did not update the kernal after installing it? Your earlier inxi info had 5.4.0-73 as the kernel while this log has 5.4.0-26. It is really a good idea to make sure your system has all updates when troubleshooting issues.

Code: Select all

May 17 07:44:12 SAI kernel: Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 (Ubuntu 5.4.0-26.30-generic 5.4.30)
This boot info indicated there was a kernel panic with the i915 driver which is probably why i915 did not load.

Code: Select all

May 17 07:44:12 SAI kernel: pci 0000:00:00.0: Intel G33 Chipset
May 17 07:44:12 SAI kernel: pci 0000:00:00.0: detected gtt size: 524288K total, 0K mappable
May 17 07:44:12 SAI kernel: pci 0000:00:00.0: detected 8192K stolen memory
May 17 07:44:12 SAI kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
May 17 07:44:12 SAI kernel: Console: switching to colour dummy device 80x25
May 17 07:44:12 SAI kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
May 17 07:44:12 SAI kernel: [drm] Driver supports precise vblank timestamp query.
May 17 07:44:12 SAI kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
May 17 07:44:12 SAI kernel: ------------[ cut here ]------------
May 17 07:44:12 SAI kernel: WARNING: CPU: 0 PID: 212 at drivers/gpu/drm/drm_mode_config.c:461 drm_mode_config_cleanup+0x28a/0x2e0 [drm]
May 17 07:44:12 SAI kernel: Modules linked in: i915(+) gpio_ich video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt i2c_i801 pata_acpi 8139too r8169 8139cp mii lpc_ich realtek fb_sys_fops psmouse drm floppy
May 17 07:44:12 SAI kernel: CPU: 0 PID: 212 Comm: systemd-udevd Not tainted 5.4.0-26-generic #30-Ubuntu
May 17 07:44:12 SAI kernel: Hardware name: HCL Infosystems Limited HCL Infosystems Limited BIOS For GA-G31M-ES2L /G31M-ES2L, BIOS F9h HI 06/12/2009
May 17 07:44:12 SAI kernel: RIP: 0010:drm_mode_config_cleanup+0x28a/0x2e0 [drm]
May 17 07:44:12 SAI kernel: Code: e8 0b 5d cb f3 49 8b 04 24 49 39 c4 75 5f 48 8b 45 d8 65 48 33 04 25 28 00 00 00 75 54 48 83 c4 38 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b 48 8d 75 a8 4c 89 e7 e8 f8 80 ff ff eb 10 48 8b 70 48 48 c7
May 17 07:44:12 SAI kernel: RSP: 0018:ffffb51f402a3910 EFLAGS: 00010287
May 17 07:44:12 SAI kernel: RAX: ffff924d1e535018 RBX: ffff924d0f0e02b0 RCX: 0000000000000003
May 17 07:44:12 SAI kernel: RDX: ffff924d0f0e0278 RSI: 000000007fffffff RDI: ffff924d0f0e0290
May 17 07:44:12 SAI kernel: RBP: ffffb51f402a3968 R08: ffff924d0f0e0278 R09: ffff924d139a2a88
May 17 07:44:12 SAI kernel: R10: ffffb51f402a3860 R11: ffff924d0f0e0200 R12: ffff924d0f0e0000
May 17 07:44:12 SAI kernel: R13: ffff924d0f0e02b8 R14: 0000000000000000 R15: 00000000ffffffe4
May 17 07:44:12 SAI kernel: FS:  00007fcafdb0d880(0000) GS:ffff924d20800000(0000) knlGS:0000000000000000
May 17 07:44:12 SAI kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 17 07:44:12 SAI kernel: CR2: 00007fcafda49000 CR3: 000000010fb10000 CR4: 00000000000006f0
May 17 07:44:12 SAI kernel: Call Trace:
May 17 07:44:12 SAI kernel:  ? _cond_resched+0x19/0x30
May 17 07:44:12 SAI kernel:  ? mutex_lock+0x13/0x40
May 17 07:44:12 SAI kernel:  intel_modeset_driver_remove+0xd1/0x150 [i915]
May 17 07:44:12 SAI kernel:  i915_driver_probe+0x558/0x5d0 [i915]
May 17 07:44:12 SAI kernel:  ? mutex_lock+0x13/0x40
May 17 07:44:12 SAI kernel:  i915_pci_probe+0x5a/0x140 [i915]
May 17 07:44:12 SAI kernel:  local_pci_probe+0x48/0x80
May 17 07:44:12 SAI kernel:  pci_device_probe+0x10f/0x1b0
May 17 07:44:12 SAI kernel:  really_probe+0x159/0x3e0
May 17 07:44:12 SAI kernel:  driver_probe_device+0xbc/0x100
May 17 07:44:12 SAI kernel:  device_driver_attach+0x5d/0x70
May 17 07:44:12 SAI kernel:  __driver_attach+0x8f/0x150
May 17 07:44:12 SAI kernel:  ? device_driver_attach+0x70/0x70
May 17 07:44:12 SAI kernel:  bus_for_each_dev+0x7e/0xc0
May 17 07:44:12 SAI kernel:  driver_attach+0x1e/0x20
May 17 07:44:12 SAI kernel:  bus_add_driver+0x152/0x1f0
May 17 07:44:12 SAI kernel:  driver_register+0x74/0xd0
May 17 07:44:12 SAI kernel:  __pci_register_driver+0x57/0x60
May 17 07:44:12 SAI kernel:  i915_init+0x61/0x6c [i915]
May 17 07:44:12 SAI kernel:  ? 0xffffffffc072f000
May 17 07:44:12 SAI kernel:  do_one_initcall+0x4a/0x1fa
May 17 07:44:12 SAI kernel:  ? kfree+0x224/0x240
May 17 07:44:12 SAI kernel:  ? _cond_resched+0x19/0x30
May 17 07:44:12 SAI kernel:  ? kmem_cache_alloc_trace+0x19c/0x230
May 17 07:44:12 SAI kernel:  do_init_module+0x62/0x250
May 17 07:44:12 SAI kernel:  load_module+0x10b8/0x1200
May 17 07:44:12 SAI kernel:  __do_sys_finit_module+0xbe/0x120
May 17 07:44:12 SAI kernel:  ? __do_sys_finit_module+0xbe/0x120
May 17 07:44:12 SAI kernel:  __x64_sys_finit_module+0x1a/0x20
May 17 07:44:12 SAI kernel:  do_syscall_64+0x57/0x190
May 17 07:44:12 SAI kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
May 17 07:44:12 SAI kernel: RIP: 0033:0x7fcafe08d70d
May 17 07:44:12 SAI kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 f7 0c 00 f7 d8 64 89 01 48
May 17 07:44:12 SAI kernel: RSP: 002b:00007ffe7d796e78 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
May 17 07:44:12 SAI kernel: RAX: ffffffffffffffda RBX: 00005601706496a0 RCX: 00007fcafe08d70d
May 17 07:44:12 SAI kernel: RDX: 0000000000000000 RSI: 00007fcafdf6aded RDI: 0000000000000013
May 17 07:44:12 SAI kernel: RBP: 0000000000020000 R08: 0000000000000000 R09: 0000000000000000
May 17 07:44:12 SAI kernel: R10: 0000000000000013 R11: 0000000000000246 R12: 00007fcafdf6aded
May 17 07:44:12 SAI kernel: R13: 0000000000000000 R14: 000056017063de80 R15: 00005601706496a0
May 17 07:44:12 SAI kernel: ---[ end trace 8d44439afcef31d6 ]---
Then it happened again.

Code: Select all

May 17 07:44:12 SAI kernel: [drm:drm_mode_config_cleanup [drm]] *ERROR* connector VGA-1 leaked!
May 17 07:44:12 SAI kernel: i915 0000:00:02.0: Device initialization failed (-28)
May 17 07:44:12 SAI kernel: i915 0000:00:02.0: Please file a bug on drm/i915; see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
May 17 07:44:12 SAI kernel: ------------[ cut here ]------------
May 17 07:44:12 SAI kernel: WARNING: CPU: 0 PID: 212 at drivers/gpu/drm/drm_vblank.c:421 drm_vblank_cleanup+0x4b/0x90 [drm]
May 17 07:44:12 SAI kernel: Modules linked in: i915(+) gpio_ich video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt i2c_i801 pata_acpi 8139too r8169 8139cp mii lpc_ich realtek fb_sys_fops psmouse drm floppy
May 17 07:44:12 SAI kernel: CPU: 0 PID: 212 Comm: systemd-udevd Tainted: G        W         5.4.0-26-generic #30-Ubuntu
May 17 07:44:12 SAI kernel: Hardware name: HCL Infosystems Limited HCL Infosystems Limited BIOS For GA-G31M-ES2L /G31M-ES2L, BIOS F9h HI 06/12/2009
May 17 07:44:12 SAI kernel: RIP: 0010:drm_vblank_cleanup+0x4b/0x90 [drm]
May 17 07:44:12 SAI kernel: Code: 01 00 00 49 03 bc 24 30 01 00 00 0f b6 87 50 01 00 00 84 c0 74 16 49 8b 44 24 20 8b 80 70 01 00 00 41 23 44 24 50 a8 02 74 02 <0f> 0b 48 83 c7 20 83 c3 01 e8 37 54 33 f3 41 39 9c 24 70 01 00 00
May 17 07:44:12 SAI kernel: RSP: 0018:ffffb51f402a3978 EFLAGS: 00010202
May 17 07:44:12 SAI kernel: RAX: 000000000000002b RBX: 0000000000000000 RCX: 0000000000000000
May 17 07:44:12 SAI kernel: RDX: 0000000000000001 RSI: 0000000000000086 RDI: ffff924d1e4ac000
May 17 07:44:12 SAI kernel: RBP: ffffb51f402a3988 R08: 00000000000002c9 R09: 0000000000000004
May 17 07:44:12 SAI kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff924d0f0e0000
May 17 07:44:12 SAI kernel: R13: ffff924d1fc62000 R14: 00000000ffffffe4 R15: 00000000ffffffe4
May 17 07:44:12 SAI kernel: FS:  00007fcafdb0d880(0000) GS:ffff924d20800000(0000) knlGS:0000000000000000
May 17 07:44:12 SAI kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 17 07:44:12 SAI kernel: CR2: 00007fcafda49000 CR3: 000000010fb10000 CR4: 00000000000006f0
May 17 07:44:12 SAI kernel: Call Trace:
May 17 07:44:12 SAI kernel:  drm_dev_fini+0x12/0x80 [drm]
May 17 07:44:12 SAI kernel:  i915_driver_probe+0x1b6/0x5d0 [i915]
May 17 07:44:12 SAI kernel:  ? mutex_lock+0x13/0x40
May 17 07:44:12 SAI kernel:  i915_pci_probe+0x5a/0x140 [i915]
May 17 07:44:12 SAI kernel:  local_pci_probe+0x48/0x80
May 17 07:44:12 SAI kernel:  pci_device_probe+0x10f/0x1b0
May 17 07:44:12 SAI kernel:  really_probe+0x159/0x3e0
May 17 07:44:12 SAI kernel:  driver_probe_device+0xbc/0x100
May 17 07:44:12 SAI kernel:  device_driver_attach+0x5d/0x70
May 17 07:44:12 SAI kernel:  __driver_attach+0x8f/0x150
May 17 07:44:12 SAI kernel:  ? device_driver_attach+0x70/0x70
May 17 07:44:12 SAI kernel:  bus_for_each_dev+0x7e/0xc0
May 17 07:44:12 SAI kernel:  driver_attach+0x1e/0x20
May 17 07:44:12 SAI kernel:  bus_add_driver+0x152/0x1f0
May 17 07:44:12 SAI kernel:  driver_register+0x74/0xd0
May 17 07:44:12 SAI kernel:  __pci_register_driver+0x57/0x60
May 17 07:44:12 SAI kernel:  i915_init+0x61/0x6c [i915]
May 17 07:44:12 SAI kernel:  ? 0xffffffffc072f000
May 17 07:44:12 SAI kernel:  do_one_initcall+0x4a/0x1fa
May 17 07:44:12 SAI kernel:  ? kfree+0x224/0x240
May 17 07:44:12 SAI kernel:  ? _cond_resched+0x19/0x30
May 17 07:44:12 SAI kernel:  ? kmem_cache_alloc_trace+0x19c/0x230
May 17 07:44:12 SAI kernel:  do_init_module+0x62/0x250
May 17 07:44:12 SAI kernel:  load_module+0x10b8/0x1200
May 17 07:44:12 SAI kernel:  __do_sys_finit_module+0xbe/0x120
May 17 07:44:12 SAI kernel:  ? __do_sys_finit_module+0xbe/0x120
May 17 07:44:12 SAI kernel:  __x64_sys_finit_module+0x1a/0x20
May 17 07:44:12 SAI kernel:  do_syscall_64+0x57/0x190
May 17 07:44:12 SAI kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
May 17 07:44:12 SAI kernel: RIP: 0033:0x7fcafe08d70d
May 17 07:44:12 SAI kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 f7 0c 00 f7 d8 64 89 01 48
May 17 07:44:12 SAI kernel: RSP: 002b:00007ffe7d796e78 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
May 17 07:44:12 SAI kernel: RAX: ffffffffffffffda RBX: 00005601706496a0 RCX: 00007fcafe08d70d
May 17 07:44:12 SAI kernel: RDX: 0000000000000000 RSI: 00007fcafdf6aded RDI: 0000000000000013
May 17 07:44:12 SAI kernel: RBP: 0000000000020000 R08: 0000000000000000 R09: 0000000000000000
May 17 07:44:12 SAI kernel: R10: 0000000000000013 R11: 0000000000000246 R12: 00007fcafdf6aded
May 17 07:44:12 SAI kernel: R13: 0000000000000000 R14: 000056017063de80 R15: 00005601706496a0
May 17 07:44:12 SAI kernel: ---[ end trace 8d44439afcef31d7 ]---
May 17 07:44:12 SAI kernel: i915: probe of 0000:00:02.0 failed with error -28
Both of them have i915: probe of 0000:00:02.0 failed with error -28 in common. The i915 driver was not able to make a connection with your hardware which is why it could not load. I was not able to find information about that error, but prior to the panics, there were issues related to memory allocation for PCIe devices (video is a PCIe device), so maybe that is the issue.

Code: Select all

May 17 07:44:12 SAI kernel: pci_bus 0000:00: Some PCI device resources are unassigned, try booting with pci=realloc
It's possible adding that kernel parameter may help. If you would like to try that and need directions on adding the parameter, let us know.

Given some of the other lines in the log about items not being recognized properly, I think trying LM19.2 with the 4.15 kernel may be an option to consider for your older hardware. It might be a better fit than LM20, and LM19 is supported for two more years.
A woman typing on a laptop with LM20.1 Cinnamon.
tuxyminty
Level 1
Level 1
Posts: 13
Joined: Thu May 13, 2021 6:56 am

Re: Intel G31 Chipset not working Mint 20.1

Post by tuxyminty »

Thanks SMG for all the help.

I will try version 19.2 LM. But how it worked that day and suddenly revreted back to software rendering. Either it should work or should not work. How this on off this happens. I still feel its monitor EDID issue as even windows 7 restarts after the LOGO. I used to get the same behaviour earlier. But as soon as the monitor was recognised and 1366x768 resolution became a reality everything worked that day. Windows 7 also booted without doing anything.

Now also I am in the same position. Its not because of the version. That's what I feel.
User avatar
SMG
Level 15
Level 15
Posts: 5593
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Intel G31 Chipset not working Mint 20.1

Post by SMG »

tuxyminty wrote:
Mon May 17, 2021 9:58 am
But how it worked that day and suddenly revreted back to software rendering. Either it should work or should not work. How this on off this happens.
My understanding is your rebooted, so it didn't "suddenly revert back". It was a new start and on the new start I would guess the driver panics happened so it was never initialized properly. If something is teetering on the edge of working or not working, it would not take much for it to go one way or the other, especially if this is a memory allocation issue.
tuxyminty wrote:
Mon May 17, 2021 9:58 am
I still feel its monitor EDID issue as even windows 7 restarts after the LOGO. I used to get the same behaviour earlier. But as soon as the monitor was recognised and 1366x768 resolution became a reality everything worked that day. Windows 7 also booted without doing anything.
So you are seeing the same problem with Mint that you were seeing with Windows 7? That makes it sound like there is a hardware-related issue.

If it was really a monitor EDID issue, then it would never work without special coding being added. That is not the case. It works when the correct driver is loaded. The correct driver is able to read the monitor's EDID.
A woman typing on a laptop with LM20.1 Cinnamon.
tuxyminty
Level 1
Level 1
Posts: 13
Joined: Thu May 13, 2021 6:56 am

Re: Intel G31 Chipset not working Mint 20.1

Post by tuxyminty »

SMG wrote:
Mon May 17, 2021 10:18 am
So you are seeing the same problem with Mint that you were seeing with Windows 7? That makes it sound like there is a hardware-related issue.

If it was really a monitor EDID issue, then it would never work without special coding being added. That is not the case. It works when the correct driver is loaded. The correct driver is able to read the monitor's EDID.
Solved.

Agreed about the EDID stuff. When you said hardware related, I was till now concentrating on graphics which was onboard. But I also had a PCI network card which i was not using. Thought that might be faulty. So removed it and Voila now everthing is perfect. Mint 20 Cinnanom, Ubuntu mate 20.04, windows 7 all boot into 1366x768.

In linux now intel driver is used. I915.

Thanks all especially SMG for all the help👍
User avatar
SMG
Level 15
Level 15
Posts: 5593
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Intel G31 Chipset not working Mint 20.1

Post by SMG »

tuxyminty wrote:
Mon May 17, 2021 12:37 pm
When you said hardware related, I was till now concentrating on graphics which was onboard. But I also had a PCI network card which i was not using. Thought that might be faulty. So removed it and Voila now everthing is perfect. Mint Cinnanom 30, Ubuntu mate 20.04, windows 7 all boot into 1366x768.
:shock: Wow!

When I posted the comment earlier "Given some of the other lines in the log about items not being recognized properly", I was thinking of this:

Code: Select all

May 17 07:44:12 SAI kernel: 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
May 17 07:44:12 SAI kernel: 8139cp 0000:03:00.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
May 17 07:44:12 SAI kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
May 17 07:44:12 SAI kernel: r8169 0000:02:00.0: unknown chip XID fcf
May 17 07:44:12 SAI kernel: 8139too: 8139too Fast Ethernet driver 0.9.28
May 17 07:44:12 SAI kernel: 8139too 0000:03:00.0: Chip not responding, ignoring board
May 17 07:44:12 SAI kernel: 8139too: probe of 0000:03:00.0 failed with error -5
which happened right before the first driver panic. It did not dawn on me that might relate to the graphics driver ability to load, but I now notice it is listed in the "modules linked in" log line. I learn something new all the time.

Glad you realized that might be an issue and all is now working for you.
A woman typing on a laptop with LM20.1 Cinnamon.
Post Reply