Ubuntu 18.04 -> 18.10 doesn't boot
After an upgrade from 18.04 to 18.10, my ubuntu does not boot and just losing the signal after the grub.
I cat login with "nomodeset" but then the resolution is lower and can't be changed.
Here are my graphic card details. It was working perfectly before the last updates using the Ubuntu 18.04 default driver.
> lspci -vnn | grep VGA -A 12
>
> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
> (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cedar
> [Radeon HD 5000/6000/7350/8350 Series] [1043:035e] Flags: bus master,
> fast devsel, latency 0, IRQ 10 Memory at e0000000 (64-bit,
> prefetchable) [size=256M] Memory at f7dc0000 (64-bit,
> non-prefetchable) [size=128K] I/O ports at c000 [size=256] Expansion
> ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied>
> Kernel modules: radeon
The used graphic driver is:
llvmpipe (LLVM 7.0, 128 bits)
The mesa current driver version is:
OpenGL version string: 3.1 Mesa 18.2.2
I also tried the ppa:oibaf/graphics-drivers and also the Mesa 18.3. . It is still not booting without the nomodeset and the resolution stays unchangeable.
The kernel version is : 4.18.0.15.16
I also installed the 4.20.7 kernel but same exit on boot problem.
I am not a gamer so I do not need special 3D capabilities.
UPDATE:
I've created a 18.10 installation USB and tried booting from it to try Ubuntu from the USB. The USB starts and shows 2 icons at the bottom but then loses the signal to the screen before even showing the firs menu.
So, I created a 18.04 installation USB (18.04.2) but the same lost signal problem happened.
I can't even install the 18.04 again.
It looks like there was a driver or kernel change that created this problem already in the 18.04 distribution.
UPDATE 2
I can only login with nomodeset. Here is the output from
sudo lshw -c video
> *-display UNCLAIMED
> description: VGA compatible controller
> product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
> vendor: Advanced Micro Devices, Inc. [AMD/ATI]
> physical id: 0
> bus info: pci@0000:01:00.0
> version: 00
> width: 64 bits
> clock: 33MHz
> capabilities: pm pciexpress msi vga_controller bus_master cap_list
> configuration: latency=0
> resources: memory:e0000000-efffffff memory:f7dc0000-f7ddffff ioport:c000(size=256) memory:c0000-dffff
Any ideas what to try?
Thanks a lot
boot radeon amd-graphics 18.10 mesa
asked Feb 11 at 19:01
DrorastaDrorasta
3816
add a comment |
After an upgrade from 18.04 to 18.10, my ubuntu does not boot and just losing the signal after the grub.
I cat login with "nomodeset" but then the resolution is lower and can't be changed.
Here are my graphic card details. It was working perfectly before the last updates using the Ubuntu 18.04 default driver.
> lspci -vnn | grep VGA -A 12
>
> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
> (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cedar
> [Radeon HD 5000/6000/7350/8350 Series] [1043:035e] Flags: bus master,
> fast devsel, latency 0, IRQ 10 Memory at e0000000 (64-bit,
> prefetchable) [size=256M] Memory at f7dc0000 (64-bit,
> non-prefetchable) [size=128K] I/O ports at c000 [size=256] Expansion
> ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied>
> Kernel modules: radeon
The used graphic driver is:
llvmpipe (LLVM 7.0, 128 bits)
The mesa current driver version is:
OpenGL version string: 3.1 Mesa 18.2.2
I also tried the ppa:oibaf/graphics-drivers and also the Mesa 18.3. . It is still not booting without the nomodeset and the resolution stays unchangeable.
The kernel version is : 4.18.0.15.16
I also installed the 4.20.7 kernel but same exit on boot problem.
I am not a gamer so I do not need special 3D capabilities.
UPDATE:
I've created a 18.10 installation USB and tried booting from it to try Ubuntu from the USB. The USB starts and shows 2 icons at the bottom but then loses the signal to the screen before even showing the firs menu.
So, I created a 18.04 installation USB (18.04.2) but the same lost signal problem happened.
I can't even install the 18.04 again.
It looks like there was a driver or kernel change that created this problem already in the 18.04 distribution.
UPDATE 2
I can only login with nomodeset. Here is the output from
sudo lshw -c video
> *-display UNCLAIMED
> description: VGA compatible controller
> product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
> vendor: Advanced Micro Devices, Inc. [AMD/ATI]
> physical id: 0
> bus info: pci@0000:01:00.0
> version: 00
> width: 64 bits
> clock: 33MHz
> capabilities: pm pciexpress msi vga_controller bus_master cap_list
> configuration: latency=0
> resources: memory:e0000000-efffffff memory:f7dc0000-f7ddffff ioport:c000(size=256) memory:c0000-dffff
Any ideas what to try?
Thanks a lot
boot radeon amd-graphics 18.10 mesa
asked Feb 11 at 19:01
DrorastaDrorasta
3816
1
The upgrade was a bad idea. I suggest to re-install 18.04 LTS.
– Pilot6
Feb 16 at 12:58
add a comment |
After an upgrade from 18.04 to 18.10, my ubuntu does not boot and just losing the signal after the grub.
I cat login with "nomodeset" but then the resolution is lower and can't be changed.
Here are my graphic card details. It was working perfectly before the last updates using the Ubuntu 18.04 default driver.
> lspci -vnn | grep VGA -A 12
>
> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
> (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cedar
> [Radeon HD 5000/6000/7350/8350 Series] [1043:035e] Flags: bus master,
> fast devsel, latency 0, IRQ 10 Memory at e0000000 (64-bit,
> prefetchable) [size=256M] Memory at f7dc0000 (64-bit,
> non-prefetchable) [size=128K] I/O ports at c000 [size=256] Expansion
> ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied>
> Kernel modules: radeon
The used graphic driver is:
llvmpipe (LLVM 7.0, 128 bits)
The mesa current driver version is:
OpenGL version string: 3.1 Mesa 18.2.2
I also tried the ppa:oibaf/graphics-drivers and also the Mesa 18.3. . It is still not booting without the nomodeset and the resolution stays unchangeable.
The kernel version is : 4.18.0.15.16
I also installed the 4.20.7 kernel but same exit on boot problem.
I am not a gamer so I do not need special 3D capabilities.
UPDATE:
I've created a 18.10 installation USB and tried booting from it to try Ubuntu from the USB. The USB starts and shows 2 icons at the bottom but then loses the signal to the screen before even showing the firs menu.
So, I created a 18.04 installation USB (18.04.2) but the same lost signal problem happened.
I can't even install the 18.04 again.
It looks like there was a driver or kernel change that created this problem already in the 18.04 distribution.
UPDATE 2
I can only login with nomodeset. Here is the output from
sudo lshw -c video
> *-display UNCLAIMED
> description: VGA compatible controller
> product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
> vendor: Advanced Micro Devices, Inc. [AMD/ATI]
> physical id: 0
> bus info: pci@0000:01:00.0
> version: 00
> width: 64 bits
> clock: 33MHz
> capabilities: pm pciexpress msi vga_controller bus_master cap_list
> configuration: latency=0
> resources: memory:e0000000-efffffff memory:f7dc0000-f7ddffff ioport:c000(size=256) memory:c0000-dffff
Any ideas what to try?
Thanks a lot
boot radeon amd-graphics 18.10 mesa
asked Feb 11 at 19:01
DrorastaDrorasta
3816
After an upgrade from 18.04 to 18.10, my ubuntu does not boot and just losing the signal after the grub.
I cat login with "nomodeset" but then the resolution is lower and can't be changed.
Here are my graphic card details. It was working perfectly before the last updates using the Ubuntu 18.04 default driver.
> lspci -vnn | grep VGA -A 12
>
> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
> (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cedar
> [Radeon HD 5000/6000/7350/8350 Series] [1043:035e] Flags: bus master,
> fast devsel, latency 0, IRQ 10 Memory at e0000000 (64-bit,
> prefetchable) [size=256M] Memory at f7dc0000 (64-bit,
> non-prefetchable) [size=128K] I/O ports at c000 [size=256] Expansion
> ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied>
> Kernel modules: radeon
The used graphic driver is:
llvmpipe (LLVM 7.0, 128 bits)
The mesa current driver version is:
OpenGL version string: 3.1 Mesa 18.2.2
I also tried the ppa:oibaf/graphics-drivers and also the Mesa 18.3. . It is still not booting without the nomodeset and the resolution stays unchangeable.
The kernel version is : 4.18.0.15.16
I also installed the 4.20.7 kernel but same exit on boot problem.
I am not a gamer so I do not need special 3D capabilities.
UPDATE:
I've created a 18.10 installation USB and tried booting from it to try Ubuntu from the USB. The USB starts and shows 2 icons at the bottom but then loses the signal to the screen before even showing the firs menu.
So, I created a 18.04 installation USB (18.04.2) but the same lost signal problem happened.
I can't even install the 18.04 again.
It looks like there was a driver or kernel change that created this problem already in the 18.04 distribution.
UPDATE 2
I can only login with nomodeset. Here is the output from
sudo lshw -c video
> *-display UNCLAIMED
> description: VGA compatible controller
> product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
> vendor: Advanced Micro Devices, Inc. [AMD/ATI]
> physical id: 0
> bus info: pci@0000:01:00.0
> version: 00
> width: 64 bits
> clock: 33MHz
> capabilities: pm pciexpress msi vga_controller bus_master cap_list
> configuration: latency=0
> resources: memory:e0000000-efffffff memory:f7dc0000-f7ddffff ioport:c000(size=256) memory:c0000-dffff
Any ideas what to try?
Thanks a lot
boot radeon amd-graphics 18.10 mesa
boot radeon amd-graphics 18.10 mesa
asked Feb 11 at 19:01
DrorastaDrorasta
3816
asked Feb 11 at 19:01
DrorastaDrorasta
3816
edited Feb 24 at 15:46
Drorasta
asked Feb 11 at 19:01
DrorastaDrorasta
3816
asked Feb 11 at 19:01
DrorastaDrorasta
3816
asked Feb 11 at 19:01
DrorastaDrorasta
3816
3816
1
The upgrade was a bad idea. I suggest to re-install 18.04 LTS.
– Pilot6
Feb 16 at 12:58
add a comment |
1
The upgrade was a bad idea. I suggest to re-install 18.04 LTS.
– Pilot6
Feb 16 at 12:58
1
1
The upgrade was a bad idea. I suggest to re-install 18.04 LTS.
– Pilot6
Feb 16 at 12:58
The upgrade was a bad idea. I suggest to re-install 18.04 LTS.
– Pilot6
Feb 16 at 12:58
add a comment |
1 Answer
1
active
oldest
votes
Start Ubuntu with "nomodeset" than go to Software Update > Settings > Additional Drivers and look for entries here. Ubuntu should auto-detect drivers that will suit your graphic card.
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
I do log in using nomodeset because it's the only option, but there are no additional drivers detected. Usually, the correct drivers are the mesa drivers but there is probably a problem with their update or with the kernel update of Ubuntu.
– Drorasta
Feb 13 at 12:28
AMD proprietary drivers for these cards don't support new releases.
– Pilot6
Feb 16 at 12:57
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117458%2fubuntu-18-04-18-10-doesnt-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Start Ubuntu with "nomodeset" than go to Software Update > Settings > Additional Drivers and look for entries here. Ubuntu should auto-detect drivers that will suit your graphic card.
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
I do log in using nomodeset because it's the only option, but there are no additional drivers detected. Usually, the correct drivers are the mesa drivers but there is probably a problem with their update or with the kernel update of Ubuntu.
– Drorasta
Feb 13 at 12:28
AMD proprietary drivers for these cards don't support new releases.
– Pilot6
Feb 16 at 12:57
add a comment |
Start Ubuntu with "nomodeset" than go to Software Update > Settings > Additional Drivers and look for entries here. Ubuntu should auto-detect drivers that will suit your graphic card.
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
I do log in using nomodeset because it's the only option, but there are no additional drivers detected. Usually, the correct drivers are the mesa drivers but there is probably a problem with their update or with the kernel update of Ubuntu.
– Drorasta
Feb 13 at 12:28
AMD proprietary drivers for these cards don't support new releases.
– Pilot6
Feb 16 at 12:57
add a comment |
Start Ubuntu with "nomodeset" than go to Software Update > Settings > Additional Drivers and look for entries here. Ubuntu should auto-detect drivers that will suit your graphic card.
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
Start Ubuntu with "nomodeset" than go to Software Update > Settings > Additional Drivers and look for entries here. Ubuntu should auto-detect drivers that will suit your graphic card.
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
answered Feb 13 at 11:08
Cristian VrinceanuCristian Vrinceanu
1005
1005
I do log in using nomodeset because it's the only option, but there are no additional drivers detected. Usually, the correct drivers are the mesa drivers but there is probably a problem with their update or with the kernel update of Ubuntu.
– Drorasta
Feb 13 at 12:28
AMD proprietary drivers for these cards don't support new releases.
– Pilot6
Feb 16 at 12:57
add a comment |
I do log in using nomodeset because it's the only option, but there are no additional drivers detected. Usually, the correct drivers are the mesa drivers but there is probably a problem with their update or with the kernel update of Ubuntu.
– Drorasta
Feb 13 at 12:28
AMD proprietary drivers for these cards don't support new releases.
– Pilot6
Feb 16 at 12:57
I do log in using nomodeset because it's the only option, but there are no additional drivers detected. Usually, the correct drivers are the mesa drivers but there is probably a problem with their update or with the kernel update of Ubuntu.
– Drorasta
Feb 13 at 12:28
I do log in using nomodeset because it's the only option, but there are no additional drivers detected. Usually, the correct drivers are the mesa drivers but there is probably a problem with their update or with the kernel update of Ubuntu.
– Drorasta
Feb 13 at 12:28
AMD proprietary drivers for these cards don't support new releases.
– Pilot6
Feb 16 at 12:57
AMD proprietary drivers for these cards don't support new releases.
– Pilot6
Feb 16 at 12:57
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117458%2fubuntu-18-04-18-10-doesnt-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The upgrade was a bad idea. I suggest to re-install 18.04 LTS.
– Pilot6
Feb 16 at 12:58