I’ve been trying to migrate away from Ubuntu on my laptop to Suse and I’ve been having a heck of a time. So far, it’s been a total failure.
I have both a USB and boot DVD. When I try to boot to them, I am greeted with the OpenSuse boot menu. Once I select an option, it tells me it can’t find any partitions on the medium and crashes. Both the USB and DVD work flawlessly on my other computers.
I tried to work around this by removing the harddrive from the laptop and installing OpenSuse on it through another computer. After installing OpenSuse and putting the harddrive back into the computer, I was able to boot from it… Once. After I update, logging into OpenSuse results in a kernel panic.
I have no idea what is going on here. Ubuntu installs and works well enough. No problems during installation, all though the Ubuntu seems remarkably sluggish on my AMD A6 processor.
Is there some kind of work around for this? I really want to migrate away from Ubuntu. I like OpenSuse much better.
at boot screen press e
find the line startting with linux. go to the real end of line. best use end key since the line takes up several lines on the screen
add a space then nomodeset
press f10 to continue boot.
Install proprietary AMD driver at your first chance
Does this fix the kernel issue upon logging in after installation or does it fix the usb issue? I can post the usb error message tonight. It baffles me.
I’d be curious to know if there were any partitions on the media that should have been found, or was it indeed empty. If there were none then the crash may be unrelated to the message. However, if there were partitions that should have been ID’d but were not then there’s likely a serious issue that is certainly not video related.
I tried to work around this by removing the hard drive from the laptop and installing OpenSuse on it through another computer. After installing OpenSuse and putting the harddrive back into the computer, I was able to boot from it… Once. After I update, logging into OpenSuse results in a kernel panic…
Sounds to me like it could be a separate issue, likely a problem with the update.