Before doing too much on suggestions to this point,
Recommend simply ensuring your system’s integrity first with a simple system update
zypper up
Reason is that for many years now I’ve found that YaST has worked fine with numerous Ruby versions without any code modification.
Was one of the first things I verified when I first started using rbenv and a few times periodically since.
If you’re using rbenv,
That should be OK.
Just set your global version to whatever you’re like.
alex@linux-ofwi:~> sudo LANG=C zypper refresh
[sudo] пароль для root:
Repository 'Ruby base project (openSUSE_Leap_15.2)' is up to date.
Repository 'Ruby Extensions (openSUSE_Leap_15.2)' is up to date.
Repository 'google-chrome' is up to date.
Repository 'packman' is up to date.
Repository 'Non-OSS Repository' is up to date.
Repository 'Main Repository' is up to date.
Repository 'Main Update Repository' is up to date.
Repository 'Update Repository (Non-Oss)' is up to date.
Repository 'PostgreSQL and related packages (openSUSE_Leap_15.2)' is up to date.
Repository 'Sublime Text - x86_64 - Stable' is up to date.
All repositories have been refreshed.
alex@linux-ofwi:~> sudo LANG=C zypper up
Loading repository data...
Reading installed packages...
The following 23 package updates will NOT be installed:
gstreamer-plugins-bad gstreamer-plugins-bad-lang libavcodec58 libavformat58 libavutil56 libgstadaptivedemux-1_0-0 libgstbadaudio-1_0-0
libgstbasecamerabinsrc-1_0-0 libgstcodecparsers-1_0-0 libgstisoff-1_0-0 libgstmpegts-1_0-0 libgstphotography-1_0-0 libgstsctp-1_0-0
libgsturidownloader-1_0-0 libgstwayland-1_0-0 libgstwebrtc-1_0-0 libswresample3 libxine2 libxine2-pulse ruby2.5-rubygem-abstract_method
vlc-codec-gstreamer vlc-lang vlc-vdpau
Nothing to do.
tsu2, I installed rbenv as described here. And it worked great. But after the system upgrade it was broke…
Okay, that’s not a big problem. I made a new config in the folder
/etc/sysconfig/network
manually and it works.
alex@linux-ofwi:~> curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-doctor | bash
Checking for `rbenv' in PATH: /home/alex/.rbenv/bin/rbenv
Checking for rbenv shims in PATH: OK
Checking `rbenv install' support: /home/alex/.rbenv/plugins/ruby-build/bin/rbenv-install (ruby-build 20200401-2-g504f6e6)
Counting installed Ruby versions: 4 versions
Checking RubyGems settings: OK
Auditing installed plugins: OK
alex@linux-ofwi:~> rbenv install -l
1.8.5-p52
1.8.5-p113
1.8.5-p114
...
Information for package rp-pppoe:
---------------------------------
Repository : Main Repository
Name : rp-pppoe
Version : 3.12-lp152.6.37
Arch : x86_64
Vendor : openSUSE
Installed Size : 410.9 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : rp-pppoe-3.12-lp152.6.37.src
Summary : A PPP Over Ethernet Redirector for PPPD
Description :
rp-pppoe is a user-space redirector which permits the use of PPPoE
(Point-to-Point Protocol Over Ethernet) with Linux. PPPoE is used by
many ADSL service providers.
$ sudo pppoe-setup
Welcome to the PPPoE client setup. First, I will run some checks on
your system to make sure the PPPoE client is installed properly...
LOGIN NAME
Enter your Login Name (default alex):
INTERFACE
Enter the Ethernet interface connected to the PPPoE modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethX, where 'X' is a number.
(default eth0): enp1s0
Do you want the link to come up on demand, or stay up continuously?
If you want it to come up on demand, enter the idle time in seconds
after which the link should be dropped. If you want the link to
stay up permanently, enter 'no' (two letters, lower-case.)
NOTE: Demand-activated links do not interact well with dynamic IP
addresses. You may have some problems with demand-activated links.
Enter the demand value (default no):
DNS
Please enter the IP address of your ISP's primary DNS server.
If your ISP claims that 'the server will provide dynamic DNS addresses',
enter 'server' (all lower-case) here.
If you just press enter, I will assume you know what you are
doing and not modify your DNS setup.
Enter the DNS information here:
PASSWORD
Please enter your Password: # szt, как было сказано ранее.
Please re-enter your Password: # szt, как было сказано ранее.
USERCTRL
Please enter 'yes' (three letters, lower-case.) if you want to allow
normal user to start or stop DSL connection (default yes):
FIREWALLING
Please choose the firewall rules to use. Note that these rules are
very basic. You are strongly encouraged to use a more sophisticated
firewall setup; however, these will provide basic security. If you
are running any servers on your machine, you must choose 'NONE' and
set up firewalling yourself. Otherwise, the firewall rules will deny
access to all standard servers like Web, e-mail, ftp, etc. If you
are using SSH, the rules will block outgoing SSH connections which
allocate a privileged source port.
The firewall choices are:
0 - NONE: This script will not set any firewall rules. You are responsible
for ensuring the security of your machine. You are STRONGLY
recommended to use some kind of firewall rules.
1 - STANDALONE: Appropriate for a basic stand-alone web-surfing workstation
2 - MASQUERADE: Appropriate for a machine acting as an Internet gateway
for a LAN
Choose a type of firewall (0-2):
Start this connection at boot time
Do you want to start this connection at boot time?
Please enter no or yes (default no):yes
** Summary of what you entered **
Ethernet Interface: enp1s0
User name: szt
Activate-on-demand: No
DNS: Do not adjust
Firewalling: STANDALONE
User Control: yes
Accept these settings and adjust configuration files (y/n)? y
Adjusting /etc/sysconfig/network-scripts/ifcfg-ppp0
Adjusting /etc/ppp/chap-secrets and /etc/ppp/pap-secrets
(But first backing it up to /etc/ppp/chap-secrets.bak)
(But first backing it up to /etc/ppp/pap-secrets.bak)
Congratulations, it should be all set up!
Type '/sbin/ifup ppp0' to bring up your xDSL link and '/sbin/ifdown ppp0'
to bring it down.
Type '/sbin/pppoe-status /etc/sysconfig/network-scripts/ifcfg-ppp0'
to see the link status.
Congrats on finding your problem,
Do you still connect using PPPoe?
It’s curious that you needed to remove your interface file, but was not supposed to be used only manually and not on bootup.
It’d be interesting if maybe PPPoe was radically changed from 15.1 > 15.2.
Yes.
Tsu2, I’m ashamed.
It’s funny, and I laugh with you … but it’s ‘tears behind the smile’. The reality is that PPPoE is the basic protocol for a state-owned Russian ISP (RosTeleCom). And I have no alternative. Nearly.
Right. The Internet from Rostelecom is very unstable. Therefore, PPPoE is not enabled at on bootup.
I am using this modem now: WLTUBA-107 (Wi-Fi modem Yota 4G LTE). Perhaps you can tell me how to connect this modem correctly and safely for OpenSUSE Leap 15.2 ?
3: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ac:50:43:1a:ee:fd brd ff:ff:ff:ff:ff:ff
inet 192.168.0.100/24 brd 192.168.0.255 scope global eth2
valid_lft forever preferred_lft forever
??
Did the most recent page for this thread somehow get chopped off, and didn’t last post before this include a linked image of the device?
In any case, I’ll try to repost what I posted before from memory…
I haven’t had to sue one of these phone wireless modems and dialup from my laptop for a very long time, since earlier days of 3G. Today, the most common way I and others have connected to a phone carrier is to use an phone, and for many, many versions now Android phones don’t act as a modem but as a gateway so that your device whatever it may be (laptop?) can simply be tethered or local hotspot. At least where I am, dialup isn’t completely eliminated but it’s a long time since I or anyone I’ve personally helped or supported actually used a product that didn’t “just work” because the vendor already had it pre-configured.
I did a search on your device and returned many results how to overcome various problems but since you had it working in 15.1, I assume you had already worked through the worst of problems.
Inspecting what you posted, there is probably no problem using a script to generate a ppp0 interface file like what you did, but I see that it ordinarily is used to set up a DSL connection while your connection seems to be CDMA LTE (or some type of GSM/GPRS). Although not likely a critical error it does suggest that although your ppp0 interface file provides basic ppp settings, there might be some settings specific to your actual use that might benefit. Unfortunately, I can’t find an interface file posted by anyone who used your device (but you should search to see if something exists). The closest I came was the ArchWiki for setting up GSM/GPRS
And there is some cryptic documentation about PPP you might find partly helpful.
Probably the important thing to know is that as expected although you can set up PPP settings in YaST, if you use Network Manager those settings may not be used and instead use setting stored in the Network Manager connection https://doc.opensuse.org/documentation/leap/reference/single-html/book.opensuse.reference/index.html
But there is still a bit of a mystery why your system had a problem with this interface file while upgrading.
I would not have expected it to cause a problem if things were working before.
Thanks for the info.
Only in one thing you did not understand me, I apologize for my poor English. My new modem does not use PPPoE, it is a different technology.
If the modem is plugged into the usb slot, when I turn on the PC I get these errors on boot: