Anyone else’s Factory install hosed after latest updates? Loads slow as molasses then no networking, period. Power management also borked. Not sure how to recover?
I am not having a problem here. I’ve updated two machines, then rebooted each.
On the one with Nvidia graphics, I did need to reinstall the nvidia driver (I install the hard way). But that was expected due to a kernel update.
I think my count was somewhere around 2650 packages updated, so a substantial update.
I have not yet tried login to Gnome, but KDE seems to be fine and looks good (the dark theme from 13.1 is now changed to something that better matches the default wallpaper).
slow as molasses – because lots of folks like me are downloading and dup-ing; I did both as I want to know that the snapshot will boot on my uefi+secure boot laptop what with the new kernel.
I did a “zypper dup” and near the end, darn if it didn’t ask for the usb or CD (@sro) for a file or two; I tried a couple different DVD’s & gave up; dup stopped; then went to YAST and using software manager did an "all in this list update; being I had already retrieved most of the packages it went extremely fast.
no networking – I did the update using wireless, and on reboot, network manager showed that I had no ext connection and wireless was missing (although my parameters were still there); the kernel update broke my Broadcom WL; no problem, tomorrow, I will download Packman’s latest Broadcom WL.src and build it(hook up the ext to get it) as I did before.
no networking cont’d – Got to YAST > Network Devices > Network Services & see if it is set to Network Manager; is it on the task bar? Look for some of the posts about “Wicked” and some of the issues with it vs network manager. I have not had that issue so I’m not up on it.
Good Luck:)
I’ll be interested to see if 13.2 Bumblebee works for my Nvidia powerhouse; presently running on the builtin Intel card.
Also saw some touchscreen packages being installed; I know touchscreen launches Firefox; want to check that out more
My choice would be to download the DVD installer, and do a clean install (but preserving the home partition).
I have just done an install with the 20140928 snapshot. It went quite smoothly. I’ll note that I use “ext4” (not “btrfs”).
I made update/upgrade in two degrees for sure.
- zypper dist-upgrade --download-only
- Logout from KDE, switch to console, then under root zypper dist-upgrade.
There was more than 1700 for updating in my case. So it seemed me more safer this way.
I recently added the Factory BaSH repo as recommended on this thread;
http://lists.opensuse.org/opensuse-factory/2014-09/msg00507.html
Could this’ve caused instability?
fwiw
upgraded this pc 8 hours ago via wired link, no problems identified
upgraded a similar pc 30 minutes ago via wireless, 2312 packages changed,
- after update wireless connected ok but networkmanager showed all wifi’s
connected and could not deselect any - yast dashboard came up but nothing else worked
from terminal the following message
A880G<2014Oct02><11:51><~>
A880G:/home/michael/Downloads # yast
[BUG] Segmentation fault at 0x00000000000630
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux-gnu]
-- C level backtrace information -------------------------------------------
/usr/lib64/libruby.so.2.1(+0x1897a7) [0x7f6f23a927a7]
.
.
.
.
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html
/sbin/yast: line 440: 4064 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
A880G:/home/michael/Downloads #
Noticed in the final stage of upgrade MSfonts loaded which needed the network,
else upgrade would not complete
suggest holding off on upgrade at the moment
On 2014-10-02 10:36, fleamour wrote:
>
> I recently added the Factory BaSH repo as recommended on this thread;
You do not need that. The modified Bash is now in the factory core.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
fleamour wrote:
>
> Anyone else’s Factory install hosed after latest updates? Loads slow
> as molasses then no networking, period. Power management also borked.
> Not sure how to recover?
>
I upgraded 13.2 Factory using YaST and the factory repo’s. Something is
definitely wrong. When trying to select option to Switch System Packages
it post message something wrong with kernel upgrade packages. do want to
keep old kernel.
I answered yes. It proceed and installed 2700+ packages. Grub menu shows
new kernel as option. It will not boot, goes to command line. Calling
YaST from there also give kernel fail. message. That was after mid night
last night. Gave up will look at later today.
I’m using uefi boot with GPT but secure boot is turned off. My /root is
btrfs and /home is ext4. These were working with prior sbnapshot. Any
having an error on the kernel?
Russ
openSUSE 13.1(Linux 3.11.10-21-desktop x86_64|
Intel(R) Quad Core™ i5-4440 CPU @ 3.10GHz|8GB DDR3|
GeForce 8400GS (NVIDIA-Linux-x86_64-340.32)|KDE 4.14.1
It’s booting fine for me. Yesterday, I updated two systems. One uses UEFI with GPT but without secure-boot, and the other uses legacy MBR partitioning and booting. Both updated around 2700 packages. Both are running well.
I use “ext4” for root on both of those systems.
Today, I updated my main desktop, which use UEFI, GPT and secure-boot. This took around 4600 packages (I have “latex” and “texlive” installed). It also went well (again, with “ext4” for root file system). Soon after the update, they released 20141001, with another 400 updates. So I applied those to, and rebooted yet again. It is still working fine.
On 2014-10-02 18:04, upscope wrote:
> I answered yes. It proceed and installed 2700+ packages. Grub menu shows
> new kernel as option. It will not boot, goes to command line.
If it goes to command line, it did boot just fine
If it does not start graphical mode, that’s a different issue.
> Calling
> YaST from there also give kernel fail. message.
Which message exactly? We can’t even try to suggest something unless we
know that.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Went with defaults of btrfs & xfs home. In place upgrade no work so rolled back to month old image. Will wait dust settle then zypper dup that sucker.
Sounds like you need to install your graphics drivers again like everyone has been saying, although I don’t really know what you are saying…
There are several package name changes and conflicts in the last two repo updates, so doing dup rather than up is necessary.
Beware of snapper and btrfs. What i mean is that it might have been the sluggishness problem all along because it creates subvolumes automatically eating away your root partition and slowing down your computer. The default in snapper is to store the past 20 snapshots, which is pretty huge when doing full system upgrades.
I do not understand how to use Snapper? I just use Clonezilla.
On 2014-10-03 12:36, fleamour wrote:
>
> sunscape;2667637 Wrote:
>> Beware of snapper and btrfs. What i mean is that it might have been the
>> sluggishness problem all along because it creates subvolumes
>> automatically eating away your root partition and slowing down your
>> computer. The default in snapper is to store the past 20 snapshots,
>> which is pretty huge when doing full system upgrades.
>
> I do not understand how to use Snapper? I just use Clonezilla.
Not the same thing.
The idea with snapper is to issue a command and your machine simply
reverts to the status previous to the last update/upgrade, or even
older. Reboot required, of course.
And your data and logs remain intact. Only needed things revert.
This is a feature “on the works”. Needs to be tested and documented -
But hey! You are using factory! Thus you volunteered to test these new
brave features. YOU test it, then you tell and teach ME if it works
and how to use it.
>:-)
If it doesn’t, then again you report the developers and work it out with
them. This is Factory, you know 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
That could be very handy. Will read the documentation.
sunscape wrote:
>
> robin_listas;2667550 Wrote:
>> On 2014-10-02 18:04, upscope wrote:
>>
>> > I answered yes. It proceed and installed 2700+ packages. Grub menu
>> shows
>> > new kernel as option. It will not boot, goes to command line.
>>
>> If it goes to command line, it did boot just fine
>>
>> If it does not start graphical mode, that’s a different issue.
>>
>> > Calling
>> > YaST from there also give kernel fail. message.
>>
>> Which message exactly? We can’t even try to suggest something unless
>> we know that.
>>
>> –
>> Cheers / Saludos,
>>
>> Carlos E. R.
>> (from 13.1 x86_64 “Bottle” at Telcontar)
>
> Sounds like you need to install your graphics drivers again like
> everyone has been saying, although I don’t really know what you are
> saying…
>
> There are several package name changes and conflicts in the last two
> repo updates, so doing dup rather than up is necessary.
>
Yes but I’m not sure why. The Nvidia graphics driver (340-32) was
installed by YaST with an earlier snapshot. YaSt showed it installed. I
final to a shot last night and deleted all the Nvidia driver packages.
Reboot to multi-user level (systemctl isolate multi-user.target) and
reinstalled the Nvidia driver with the command line YaST. Works like a
charm now.
Thanks for the responses. (Sent from my 13.1 install.
Russ
openSUSE 13.1(Linux 3.11.10-21-desktop x86_64|
Intel(R) Quad Core™ i5-4440 CPU @ 3.10GHz|8GB DDR3|
GeForce 8400GS (NVIDIA-Linux-x86_64-340.32)|KDE 4.14.1
Is the Rescue CD image useful in these situations?
On 2014-10-04 17:26, fleamour wrote:
>
> Is the Rescue CD image useful in these situations?
Reinstalling the nvidia package? Doubtful.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)