Hi everyone, I updated tumbleweed as usual a couple of days ago, after downloading 1.3GB of data I booted into my familiar desktop as usual. No problems, I thought. It became immediately apparent that I couldn’t do anything but look at the wallpaper! Neither the mouse or keyboard will do anything.
I downloaded the 12.2 DVD and ran updates. Updating with the tumbleweed repositories only enabled results in another 329MB diownloaded and a frozen screen with a message window saying updates have been found in opensuse -12.2 non-oss repo.
Updating again with tumbleweed repos disabled and 12.2 repos enabled results in another 1.3GB downloaded and
Updating with all repos enabled results in
In all installs it takes 10-12 minutes analyzing the linux partitions. I have a quad-core 2.3Ghz Phenom with 4 GB of ram and this seems like a long time
I have limited knowledge about the details of the software here, but I know the device drivers are in the kernel and it seems to me that downgrading the kernel from 3.5.2 to 3.4.6 may be what broke the drivers. I’m hoping that when the tumbleweed repos are up again, in a few days weeks?, upgrading back to the 3.5 kernel will fix everything. I’m also thinking that you might want to wait updating tumbleweed user until the new release software is tested and working in factory with the current tumbleweed kernel. This would put tumbleweed users a few days(weeks) behind on a version update but result in a stable and useful system.
I suppose I could just go with a completely new install, but I’m interested in what is happening with tumbleweed. I’ve been using it almost since it started with excellent results. The only hiccup was with dolphin after a KDE update which necessitated a switch to konqueror for awhile. I suppose this is mainly a FYI post, though if you have any ideas on restarting mouse and keyboard input I’d be interested. If anyone knows when the tumbleweed repos will be back up that would be good to know too.
I took too long editing, didn’t know there was a time limit, but Updating again with tumbleweed repos disabled and 12.2 repos enabled results in another 1.3GB downloaded and a boot into a white screen with black speckles everywhere and no input, thought hitting the off button does shut it down and the “escape” key shows the shutdown dialogue.
Everything works fine booting with the iso’s. They have limited options for removing, disabling, or enabling different repos when you install. I tried several different combos to no effect. Everything works until the install is finished, then the mouse and keyboard go dead. The live KDE CD is the same way, setup works then when the OS loads input fails. I tried several other things but finally got tired of playing with it and ran Killdisk and zeroed the drive. A fresh install of 12.2 from a DVD did the same thing, so it’s not a Tumbleweed problem and means opensuse 12.2 will not run on my computer. It’s has a Gigabyte 790X mobo with a Phenom 9650 quadcore, Nvidea 9500 card, and 4GB of 800 DDR, quite capable, but nothing fancy. 2 months late and a disaster of a release. USB2 is nothing new and should work.
I should probably post a new thread in the opensuse forum, but I’m tired of wasting my time and disappointed. I don’t see any fixes until the next release anyway, updating from the iso’s during install has limited options. I need an updated iso that installs a system that works with USB2.
I ran Killdisk again and then did a clean install of Sabayon 10 KDE. It works fine, using their 3.5 kernel and KDE 4.9. Sabayon is becoming a very good distro, several years ago It had problems with a left-handed mouse, but that’s been fixed for awhile, maybe that’s the problem with opensuse 12.2 now, the left handed preferences confuse and freeze the system??? Probably not though, since the live KDE CD is useless too. Sabayon has a rolling release model like tumbleweed. They seem to update KDE sooner and tumbleweed updates the kernel a little faster. At the moment Sabayon works, opensuse doesn’t.
That sounds like an easy choice and I would probably stay with it if it works for you (I probably am a bit too used to yast though).
I had similar problems (no keyboard or mouse after boot) when I once updated TW. But in my case it was a bug in the 3.5.0 kernel which was solved as soon as I installed another kernel (which unfortunately was a bit cumbersome, as at that time I was not keeping the old kernel when installing new ones)
I need an updated iso that installs a system that works with USB2.
I guess that will take a while since 12.2 was released just some days ago, though it is strange that nothing similar has been reported so far. Maybe a search in bugzilla would shed some light? Or you could report it there?
I was using the 3.5.2 kernel with tumbleweed before I updated and it worked fine. It’s strange this isn’t more common, though you had the same problem. How did you install anything without a mouse or keyboard? I like yast too, but Sabayon works with rigo their new package manager. I may research bugzilla and report it later. I could also install an old 12.1 KDE iso and update it with tumbleweed later. It might be fixed after a couple of months. I have another box with a 3500 Llano and tumbleweed at 12.i and kernel 3.5.2. I’ll try running a live CD and then clone the drive if it works. I can update the clone and use it if it’s still working, then put the spare 12.1 in the phenom system and just not update it for awhile. Just don’t have time to get into it for awhile though. Lots of options, they just take time. Thanks for your thoughts.
How did you install anything without a mouse or keyboard?
I had to use the installation DVD (It was 12.1 then) (installation->upgrade existing system->package manager, and then I installed the 3.1.* kernel-desktop), afterwards I changed my yast configuration to allow multiple kernels and updated the kernel to 3.4.x using the SAKC script. It is described in more detail here http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/477037-no-keyboard-after-update-kernel-3-5-a.html
My problems with the 3.5. kernels disappeared as soon as 3.5.1 was released. If it really is just a kernel thing in your case, I don’t think you would have to wait with updating. The most important thing is to configure multiple kernels as soon as you get the system running, so you have a fallback if an update does not work out as expected.
I don’t think the kernel is causing my problems anymore. I used almost every kernel in the 3.4 series and tumbleweed had got to 3.5.2 before the update and everything worked. It’s something in the 12.2 release causing the problems, maybe systemd? It gets blamed for everything anyway. When 12.2 would not work for me even when installed to an empty disk and it’s the 3.4 kernel it seemed that it must be 12.2 package(s). I guess I’m mainly disappointed that such an old tech like USB2 would cause such major problems.
Thanks for the link. I’ll look into doing that when I get opensuse up and running again, though I’ll probably be lazy and just clone another system. That worked surprisingly well going from a Phenom and Nvidea to a llano APU. I want to see if the reverse is true. Having another kernel on hand would be a good thing though. I make sure the cases I buy have transverse mounted hard drives to simplify adding and removing them.
When 12.2 would not work for me even when installed to an empty disk and it’s the 3.4 kernel it seemed that it must be 12.2 package(s). I guess I’m mainly disappointed that such an old tech like USB2 would cause such major problems.