16.04 LTS install issues

Support & Help Requests
,
#1

I am unable to install Mate 16.04 LTS due to two key issues.
(1) I use a UK keyboard, not a US keyboard and so am unable tu try out 16.04 LTS without resorting to a command line to set the keyboard up.
(2) I am unable to get the video driver to work in anything other than 640x480 (by using nomodeset and radeon.modeset=0 options) and most of the windows just don’t work in this resolution. All the buttons to apply things are off the bottom of the display.

The hardware is a Commell LV386 (AMD G-T56N based system).

PCI Devices

-PCI Devices-
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Complex
VGA compatible controller               : Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] (prog-if 00 [VGA controller])
PCI bridge              : Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Port (prog-if 00 [Normal decode])
PCI bridge              : Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Port (prog-if 00 [Normal decode])
PCI bridge              : Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Port (prog-if 00 [Normal decode])
PCI bridge              : Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Port (prog-if 00 [Normal decode])
SATA controller         : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) (prog-if 01 [AHCI 1.0])
USB controller          : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI])
USB controller          : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI])
USB controller          : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI])
USB controller          : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI])
SMBus           : Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42)
ISA bridge              : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
PCI bridge              : Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) (prog-if 01 [Subtractive decode])
USB controller          : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller (prog-if 10 [OHCI])
PCI bridge              : Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) (prog-if 00 [Normal decode])
PCI bridge              : Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) (prog-if 00 [Normal decode])
PCI bridge              : Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2) (prog-if 00 [Normal decode])
PCI bridge              : Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 3) (prog-if 00 [Normal decode])
USB controller          : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI])
USB controller          : Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI])
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 0 (rev 43)
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 1
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 2
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 3
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 4
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 6
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 5
Host bridge             : Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 7
Ethernet controller             : Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
Ethernet controller             : Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
Ethernet controller             : Intel Corporation 82583V Gigabit Network Connection
Ethernet controller             : Intel Corporation 82583V Gigabit Network Connection
Serial controller               : Oxford Semiconductor Ltd Device c208 (prog-if 02 [16550])

<tt>  4000-40ff </tt>           : Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] (prog-if 00 [VGA controller])

Any help on how to force the video to 1280x1024x24 (The settings I use for uBuntu 10.04 LTS and Mate 14.04 LTS when I got that working by forcing various linux command line settings).

#2

Hi @Mark,

how did you create your boot media and did you follow this advice?:

When you boot and you see this symbol, press any key to enter the menu, press F3 for keyboard and then F6 for boot parameters:

Try “acpi=off”?. :smiley:

https://help.ubuntu.com/community/BootOptions

#3

Hi Wolfman,

Installation media: 4GB USB Stick created from the MATE install image:

ubuntu-mate-16.04-desktop-amd64.iso

The uBuntu 10.04 LTS GUI app was used to do the creation.

The system is using EFI boot so it skips all the options you get to
changes things that you get when using legacy boot :(.

I will try acpi=off but this may not solve the issue as I need acpi=on
to get some of the other bits of hardware set up properly.

In 14.04 LTS I managed to get things to work without setting nomodeset.
This no-longer works so I am going to look at what has changed in the
Kernel drivers and apply various hardware specific fixes needed for my
hardware. Most of these were developed for the 3.2 series kernels so may
not be applicable but it all looks like a NULL pointer deference in the
radeon DRM code. For the 3.2 series kernels, radeon_dp_getsinktype in
atombios_dp.c failed to validate dig_connector->dp_i2c_bus before use
resulting in a NULL pointer deference.

Regards
Mark.

#4

Hi Mark,

could you not try switching “EFI” off or have you already tried that?. :smiley:

#5

Hi again,

Turning EFI off is easier said than done as I would have to disconnect
the uBuntu 10.04 LTS SSD that I don’t want to trash just yet :).

It would also not make much difference to the primary issue of the GUI
crashing. It is a NULL pointer dereference bug (probably caused by some
incorrect BIOS code - got at the info via serial debug :slight_smile: ).

[    8.358195] BUG: unable to handle kernel NULL pointer dereference at 
0000000000000409
[    8.366104] IP: [<ffffffffc02024da>] radeon_dp_getsinktype+0x1a/0x30 
[radeon]
[    8.416805] PGD 0
[    8.418841] Oops: 0000 [#1] SMP
[    8.422104] Modules linked in: hid_generic e1000e psmouse amdkfd 
usbhid uas amd_iommu_v2 ptp radeon(+) pps_core e1000(+) hid i2c_algo_bit 
ttm drm_kms_helper usb_storage syscopyarea sysfillrect sysimgblt ahci 
fb_sys_fops libahci drm video fjes
[    8.444029] CPU: 0 PID: 131 Comm: systemd-udevd Not tainted 
4.4.0-22-generic #40-Ubuntu
[    8.452036] Hardware name: AMD Corporation EBrazos 
Platform/Persimmon, BIOS LV-683 Version: 1.1 02/14/2012
[    8.461708] task: ffff88014780be80 ti: ffff880147888000 task.ti: 
ffff880147888000
[    8.469194] RIP: 0010:[<ffffffffc02024da>]  [<ffffffffc02024da>] 
radeon_dp_getsinktype+0x1a/0x30 [radeon]
[    8.478850] RSP: 0018:ffff88014788b850  EFLAGS: 00010246
[    8.484179] RAX: 0000000000000000 RBX: ffff88003485f000 RCX: 
0000000000000000
[    8.491321] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 
ffff88003485f000
[    8.498469] RBP: ffff88014788b850 R08: 0000000000000000 R09: 
ffffffffc004aff6
[    8.505602] R10: ffffea0000d5e540 R11: 0000000000000000 R12: 
0000000000000001
[    8.506137] e1000 0000:05:0b.0 eth1: (PCI:33MHz:32-bit) 00:03:1d:09:3b:61
[    8.506142] e1000 0000:05:0b.0 eth1: Intel(R) PRO/1000 Network Connection
[    8.526299] R13: ffff8800351f4080 R14: ffff880035120000 R15: 
ffff8801478e7000
[    8.533441] FS:  00007f4ed97678c0(0000) GS:ffff88014ec00000(0000) 
knlGS:0000000000000000
[    8.541525] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    8.547263] CR2: 0000000000000409 CR3: 0000000149f2d000 CR4: 
00000000000006f0
[    8.554396] Stack:
[    8.556412]  ffff88014788b888 ffffffffc01c27a6 ffff88003485f050 
ffff88003485f000
[    8.563867]  0000000000000003 ffff88003574e000 0000000000000001 
ffff88014788b8e8
[    8.571329]  ffffffffc00ccd95 ffff88014788b920 ffffffffc01a9319 
ffff8801478e6200
[    8.578789] Call Trace:
[    8.581289]  [<ffffffffc01c27a6>] radeon_dp_detect+0x206/0x2b0 [radeon]
[    8.587918]  [<ffffffffc00ccd95>] 
drm_helper_probe_single_connector_modes_merge_bits+0x235/0x4d0 
[drm_kms_helper]
[    8.598217]  [<ffffffffc01a9319>] ? atombios_crtc_disable+0x39/0x350 
[radeon]
[    8.605356]  [<ffffffffc00cd043>] 
drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper]
[    8.614508]  [<ffffffffc00d990e>] 
drm_fb_helper_initial_config+0xae/0x420 [drm_kms_helper]
[    8.622816]  [<ffffffffc01cd16e>] radeon_fbdev_init+0xee/0x110 [radeon]
[    8.629471]  [<ffffffffc01c726f>] radeon_modeset_init+0x43f/0xa10 
[radeon]
[    8.636391]  [<ffffffffc019f513>] radeon_driver_load_kms+0x123/0x220 
[radeon]
[    8.643565]  [<ffffffffc0035397>] drm_dev_register+0xa7/0xb0 [drm]
[    8.649765]  [<ffffffffc00379cd>] drm_get_pci_dev+0x8d/0x1e0 [drm]
[    8.655985]  [<ffffffffc019b3e0>] radeon_pci_probe+0xa0/0xb0 [radeon]
[    8.662438]  [<ffffffff81439dc5>] local_pci_probe+0x45/0xa0
[    8.668006]  [<ffffffff8143b203>] pci_device_probe+0x103/0x150
[    8.673841]  [<ffffffff8154c6e2>] driver_probe_device+0x222/0x4a0
[    8.679939]  [<ffffffff8154c9e4>] __driver_attach+0x84/0x90
[    8.685519]  [<ffffffff8154c960>] ? driver_probe_device+0x4a0/0x4a0
[    8.691787]  [<ffffffff8154a30c>] bus_for_each_dev+0x6c/0xc0
[    8.697445]  [<ffffffff8154be9e>] driver_attach+0x1e/0x20
[    8.702845]  [<ffffffff8154b9db>] bus_add_driver+0x1eb/0x280
[    8.708504]  [<ffffffff8154d2f0>] driver_register+0x60/0xe0
[    8.714077]  [<ffffffff814396ec>] __pci_register_driver+0x4c/0x50
[    8.720191]  [<ffffffffc0037c00>] drm_pci_init+0xe0/0x110 [drm]
[    8.726104]  [<ffffffffc030d000>] ? 0xffffffffc030d000
[    8.731288]  [<ffffffffc030d09d>] radeon_init+0x9d/0xb2 [radeon]
[    8.737297]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
[    8.742955]  [<ffffffff811cee51>] ? __vunmap+0x91/0xe0
[    8.748093]  [<ffffffff811eaf83>] ? kmem_cache_alloc_trace+0x183/0x1f0
[    8.754622]  [<ffffffff8118c233>] do_init_module+0x5f/0x1cf
[    8.760193]  [<ffffffff81109e67>] load_module+0x1667/0x1c00
[    8.765764]  [<ffffffff81106410>] ? __symbol_put+0x60/0x60
[    8.771252]  [<ffffffff81212820>] ? kernel_read+0x50/0x80
[    8.776651]  [<ffffffff8110a644>] SYSC_finit_module+0xb4/0xe0
[    8.782395]  [<ffffffff8110a68e>] SyS_finit_module+0xe/0x10
[    8.787970]  [<ffffffff818252f2>] entry_SYSCALL_64_fastpath+0x16/0x71
[    8.794404] Code: 41 5d 41 5e 41 5f 5d c3 66 0f 1f 84 00 00 00 00 00 
0f 1f 44 00 00 55 48 8b 87 a0 03 00 00 45 31 c0 31 d2 be 01 00 00 00 48 
89 e5 <0f> b6 88 09 04 00 00 48 8b 07 48 8b 78 28 e8 23 f6 ff ff 5d c3
[    8.814354] RIP  [<ffffffffc02024da>] radeon_dp_getsinktype+0x1a/0x30 
[radeon]
[    8.821645]  RSP <ffff88014788b850>
[    8.825135] CR2: 0000000000000409
[    8.828551] ---[ end trace 9fce5ace7679b4a0 ]---

I am trying a kernel rebuild (not easy on a USB stick with 640x480 only)
with a patch that fixes the symptom (and worked with the 3.2 series
kernels). I will put the updated driver onto the USB stick and see what
happens. If all is the OK I will push the very short patch via launchpad
as it should not break anything and avoids having to work back until I
find out what is actually broken (far to complicated to sort out why the
DDC itc bus pointer is NULL. Better left to a radeon developer to sort
out how it can happen and if required, get me to test various debug
patches).

Regards
Mark.

2 Likes
#6

Hi Mark,

this is for SIS graphics but might work in your case too, it will give you a higher res for now at least!:

#7

Hi Wolfman,

No joy with the VESA driver hack.

I eventually got a set up on a USB disk that allowed me to do a proper
kernel build from the 4.4.0_22 sources (using a different computer).

There were four radeon drm files where it was possible to get a NULL
pointer dereference due to the assumption that all connectors have DDC.

After changing these files to eliminate the invalid assumption, I built
up a tweaked generic kernel and installed onto my modified uBuntu-MATE
LiveCD USB stick. This solved the issue I was having so I have edited
the subject line accordingly.

I have attached a patch with the Kernel changes (xz compressed):

file validate_ddc_bus_before_use.patch.xz
md5sum 2d8fc654881b2e0025ba4e337ca9ffa3
sha256 b4cdb65ded6c004a4f7e93df0a7683ab516cc2c5ac4e9b3d5abd9ed0196e3b22

I have also raised a launchpad bug
(https://bugs.launchpad.net/bugs/1587885).

Hopefully this will go through to the Kernel and an updated set of ISO
images can be created. Until then I will use my hacked USB install stick.

The next step is to generate a proper modified debian style kernel that
I can install in place of the default generic kernels as there are other
hardware related changes that I need (work around BIOS/ACPI bugs and a
Kernel serial driver bug fix/enhancement for OxPCI/PCIe boards).

Regards
Mark.

1 Like