Yesterday it was all running, but on booting today I have neither wireless nor wired ethernet. I did update for new packages yesterday while on ired system but cannot see why that should break things.
On Toshiba Protege Z30-A. I usually use wireless but today it is persistently down. Checked viayast2 lan and the sttings are right, ip address, route, password… but ifconfig does not show it (but does show wired despite it being set to manual and is not connected). Attempts to bring it up fail
ifup wlp2s0
wicked: device wlp2s0 failed: call to org.opensus.Network.Wireless.changeDevice() failed: General failure
wlp2s0 device-not-running
iwconfig shows the wlp2s0 but not active
Also tried using the wired connection but it is dead too; does not respond to ifup
I did once get a message about SIOCSIFFLAGS:Operation not possible due to RF-kill
It is not on the DVD so that is harder. Not sure how to grab but will look.
It says it is running 3.16.3-1.gd2bbe7f but I also have 3.16.4-9.g78842b in /boot. No ideawhy it did not boot the newer kernel. It does not offer me a choice on booting either. Could this mismatch matter?
As far as I can tell no it does not. I am still getting used to the machine – replacing a Lenovo which has such a switch. and also a breaking keyboard and defective mouse keys
I see no grub menu at all (very odd!). I get an advert from Toshiba, blank screen, a short message that some intel register was not accessable, another blank screen and quickly the xdm log on screen.
I have been wondering why there as no grub menu as I can see entries in the config file in /boot
Hi
Fire up YaST -> System -> Bootloader and check the entries there, in the options it may be hidden and no time out. Also if not multi-booting I would uncheck the box to look for another os.
Ok What files system?? BTRFS?? Do you use hibernate? There is a problem using BTRFS and hibernating. When done the boot goes straight in not giving a menu since it is a recovery from hibernation. The problem is the grub can read BTRFS but can not write it so can not flip the switch to say no hibernate so even if you shut down next grub thinks it as coming from hibernation. If you use BTRFS and plan to hibernate the computer probably safest to is to have a separate boot partition for mated ext2/4. The final may or may not have a work around that supposedly fixes the problem with a hack
Yes it is btfs as that was default. I hibernate once but not since and was not planning to do it. Question is how to recover, beyond waiting fot 13.2 release; if that fixed it I would not mind.