This is my first go at OpenSUSE. My Linux background below*, after my RC1 installation feedback here. (Relevant hardware: MSI 890GX-G65 mainboard + GTX550Ti)
(1) First installation, after it got to the part where the console says “kexec … attempting to start kernel without reboot” (or similar), the screen turns into garbage. It’s not locked up, because pressing ALT+Fkey changes it to different looking garbage. Pressing the reset button lets the installation continue, but …
(2) Then when it reaches the part where it says it’s going to reboot again, it just stops on the pretty logo screen, and the system is alive and well. I tried “shutdown” and ctrl-alt-del to no avail. “sync” and reset button again.
(3) Networking worked during the install, but was dead and needed re-kicking after the install.
Rough install, but otherwise once the system was actually up and running, everything seems fine and dandy.
Question: Which tool/command should I run to upgrade from RC1 RPMs to the release versions later?
(* Started out on OSF/1, then a looong time M-ndr-ke/M-ndr-va KDE user, after the meltdown bailed to K-b-ntu for quite a while, not bad but didn’t really like it entirely, so I tried the recent F-dora beta for the last couple weeks which is a huge disaster. So here I am with openSUSE now, trying to avoid returning to M-ndr-ke/M-geia.)
On 11/02/2011 08:36 AM, xorbe wrote:
> (* Started out on OSF/1, then a looong time M-ndr-ke/M-ndr-va KDE user,
> after the meltdown bailed to K-b-ntu for quite a while, not bad but
> didn’t really like it entirely, so I tried the recent F-dora beta for
> the last couple weeks which is a huge disaster. So here I am with
> openSUSE now, trying to avoid returning to M-ndr-ke/M-geia.)
i don’t know where you have been but Mandrake, Mandrivia, Kbuntu,
Fedora, Red Hat, Debian, Puppy and many others are not considered “dirty
words” here…rather they are choices that you are free to make…and,
most here will encourage you to use what works for you…
so, as a person new to openSUSE why not install the current system
(11.4) rather than the release candidate for 12.1 which is KNOWN to
still have bugs (otherwise someone somewhere would call it “GOLD MASTER”
or just openSUSE 12.1)
so, i guess you downloaded and tried to install from the DVD, all the
old head testers discovered last week that the DVD install is
broken–throw away that disk…so, either you need to do more reading or
install the currently supported 11.4, and then move to 12.1 when it is
ready (which for me will be sometime next spring, after all the early
adopters have discovered the majority or bugs remaining in the “GOLD
MASTER”…
or you could try a 12.1 RC 1 live disk on a sandbox (i absolutely would
not try it on a machine with my ‘real’ data at risk)…
On 11/02/2011 03:06 AM, xorbe wrote:
>
> Ah, I found the magic commands:
>
>
> Code:
> --------------------
> sudo zypper refresh
> sudo zypper dup
> --------------------
Those are the correct commands.
Let me give you a slightly different view from that of DenverD. I am a member of
the openSUSE Testing Core Team, thus I have a special interest in testing each
new version. For the past two cycles (11.4 and 12.1), I have tested the early
Milestones in VirtualBox VMs. Beginning with MS4, I do an installation in a
physical machine using one of my disk partitions used for testing purposes. If
tests show the system to be usable for my workload, which is kernel development
on wireless drivers, then I give the new version access to my regular /home.
This step occurred at MS5 for 11.4 and 12.1. I keep a boot entry to get back to
the previous version; however, I only needed to boot into 11.4 once after
installing 12.1 MS5. I will continue to “zypper dup” right up to the Gold Master.
Now the caveats: As a kernel developer, I absolutely cannot allow my kernel to
be tainted by any driver that uses a binary blob. That means no “wl” driver for
a Broadcom card, and no proprietary graphics drivers. For my nVidia adapter, the
“nv” 2-D accelerated driver is sufficient, although nouveau is now working quite
well for my hardware; however, YMMV.
If you find a graphics problem when booting into the GUI, always remember the
“nomodeset” option for the boot line.
(Nonono … it just keeps the web search results a little more clean. I wasn’t suggesting they were banned terms! btw this thread is now the #6 result for “Kbuntu installation woes”, ha!)
Ahh, so I’m late to the broken DVD installer party, oh well! It got the job done regardless, which is impressive.
On 11/02/2011 03:16 PM, Larry Finger wrote:
>
> Let me give you a slightly different view from that of DenverD.
and, thank you for that post…interesting…
i guess (with the free time i have) set myself up to do milestone
testing…but, i still think i’d want a sandbox…wow, what an easy
way to justify another machine!!
–
DD
openSUSE®, the “German Automobiles” of operating systems
2/3 of the problems I reported here for RC1 are present in 12.1 final. Display garbled on 550Ti during installation, and had to manually reset the computer twice during installation because it fails to restart itself. Networking worked without having to manually poke at it though.
On 11/29/2011 02:26 AM, xorbe wrote:
>
> 2/3 of the problems I reported here for RC1 are present in 12.1 final.
> Display garbled on 550Ti during installation, and had to manually reset
> the computer twice during installation because it fails to restart
> itself. Networking worked without having to manually poke at it
> though.
>
> Well, it’s installed. lol!
Please report the bug numbers that you filed on RC1.
On 11/29/2011 02:56 PM, xorbe wrote:
>
> It was implied above that the issues were already known with the gravely
> broken RC1 DVD installer, but I guess they were different issues. Heh!
If you have not yet figured it out, the developers do not hang out here - too
much time wasted. If there is not a bug reported at bugzilla.novell.org, the
problem will never be fixed.
well, sometimes developers read here, but it is unlikely to be the one maintaining the software in question.
https://bugzilla.novell.com/show_bug.cgi?id=726653 is the known kexec hang
but the others could be unknown issues, that are worth checking with other Linux Distributions and if they also happen there, reporting it upstream would be best… but this is often a hard task for users, so filiing it on bugzilla.novell.com and hoping for some developer to manage the rest could also work.