getting out of bridge mode
by Michael Hennebry
I'm running F38 with an Arris router provided by Midcontinent.
The connection is by ethernet cable.
Somehow the router got into bridge mode which turns off wifi.
I've tried to login to turn off bridge mode.
No go.
I eventually get a popup saying the operation timed out.
After dismissing the popup, I get another popup saying
that the reason was that the router connection was lost.
ping 8.8.8.8
succeeds.
How do I figure out what is going on?
What do I do about it?
Power cycling has not helped.
How many young goats do I need?
--
Michael hennebry(a)mail.cs.ndsu.NoDak.edu
"SCSI is NOT magic. There are *fundamental technical
reasons* why it is necessary to sacrifice a young
goat to your SCSI chain now and then." -- John Woods
6 days, 8 hours
Re: OT: SFTP with lftp
by Jonathan Billings
On May 21, 2024, at 05:01, Frederic Muller <fred(a)cm17.com> wrote:
> I thought someone here could help me out. I am using lftp to automate some file copy on Ubuntu 20.04. The originating server is switching to SFTP and I have about a week for testing. It works fine by default with F40.
>
> On ubuntu it seems by default lftp is not compiled with sftp support as I didn't get any trace of libssl.so using ldd.
>
> I then removed it, compiled a new version with sftp support, checked with ldd for libssl.so and got it but it is still not working. Any idea what could be the problem then, or how to further troubleshoot?
>
By “SFTP” do you mean FTP over SSL/TLS, or the OpenSSH “sftp” backend which runs over the SSH protocol? Two completely different protocols.
I suspect that lftp just calls out to the OpenSSH sftp binary if it uses SSH.
--
Jonathan Billings
6 days, 15 hours
After f39 upgrade sddm broken on 1 system
by Go Canes
I recently upgraded 5 systems from f38 to f39. 4 of the 5 are fine,
but on 1 sddm is broken. There is no text and sometimes the areas
that should be text are a pinkish-purple color.
I googled and saw suggestions about locale and dejavu fonts, but as
near as I can tell this system has the EN locale and dejavu fonts
installed.
journalctl does show some interesting errors:
[...] sddm-greeter[1367]: QOpenGLShader::link: error: Exceeded max nr
indirect texture lookups (5/4)
[...] sddm-greeter[1367]: shader compilation failed:
[...] sddm-greeter[1367]: QOpenGLShader::link: error: Exceeded max nr
indirect texture lookups (5/4)
[...] sddm-greeter[1367]:
QOpenGLShaderProgram::uniformLocation(matrix): shader program is not
linked
[...] sddm-greeter[1367]:
QOpenGLShaderProgram::uniformLocation(textureScale): shader program is
not linked
[...] sddm-greeter[1367]:
QOpenGLShaderProgram::uniformLocation(color): shader program is not
linked
[...] sddm-greeter[1367]:
QOpenGLShaderProgram::uniformLocation(alphaMin): shader program is not
linked
[...] sddm-greeter[1367]:
QOpenGLShaderProgram::uniformLocation(alphaMax): shader program is not
linked
[...] sddm-greeter[1367]:
QOpenGLShaderProgram::uniformLocation(fontScale): shader program is
not linked
[...] sddm-greeter[1367]:
QOpenGLShaderProgram::uniformLocation(vecDelta): shader program is not
linked
Any suggestions as to what to check for?
6 days, 19 hours
Can't Boot 6.8.* Kernels
by Garry T. Williams
I have one system that fails to boot any 6.8 kernel. The failure is
that the boot sequence halts with a single message on the console:
Booting `Fedora Linux (6.8.9-200.fc39.x86_64) 39 (KDE Plasma)'
and the console cursor simply blinks two blank lines down from this
message.
The last kernel that will boot on this system is
6.8.10-300.fc40.x86_64. I have two other Fedora systems that do not
have any problem booting the 6.8 kernels. This leads me to believe
that something on this particular system is causing the problem.
Any ideas?
garry@vfr$ sudo dmidecode -t system
[sudo] password for garry:
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: Precision Tower 3420
Version: Not Specified
Serial Number: HQ83ND2
UUID: 4c4c4544-0051-3810-8033-c8c04f4e4432
Wake-up Type: Power Switch
SKU Number: 06C7
Family: Precision
Handle 0x0005, DMI type 12, 5 bytes
System Configuration Options
Option 1: Default string
Handle 0x0006, DMI type 15, 35 bytes
System Event Log
Area Length: 4 bytes
Header Start Offset: 0x0000
Header Length: 2 bytes
Data Start Offset: 0x0002
Access Method: Indexed I/O, one 16-bit index port, one 8-bit data port
Access Address: Index 0x046A, Data 0x046C
Status: Invalid, Not Full
Change Token: 0x00000000
Header Format: No Header
Supported Log Type Descriptors: 6
Descriptor 1: End of log
Data Format 1: OEM-specific
Descriptor 2: End of log
Data Format 2: OEM-specific
Descriptor 3: End of log
Data Format 3: OEM-specific
Descriptor 4: End of log
Data Format 4: OEM-specific
Descriptor 5: End of log
Data Format 5: OEM-specific
Descriptor 6: End of log
Data Format 6: OEM-specific
Handle 0x0008, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
garry@vfr$ sudo dmidecode -t bios
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: 2.15.0
Release Date: 03/25/2020
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 2.15
Handle 0xF032, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 2
en|US|iso8859-1
<BAD INDEX>
Currently Installed Language: en|US|iso8859-1
--
Garry T. Williams
1 week
Need system to run 24/7
by Robert McBroom
This thread has been on before but I lost it. I need my system to run
long simulations without my intervention. It keeps going to a reboot
intermittently. The program has recovery that all is not lost with a
shutdown but the time getting back to check on the system. Don't
remember the setting to tell fedora what to do for always on systems.
1 week
F40: strange network issue after upgrade of laptop from F39
by Ranjan Maitra
Hi,
I have a strange issue after upgrading a laptop (Dell XPS 13, 2013 edition). That is that I am connected (whether through WiFi or ethernet cable) to a university network which claims after the upgrade that the laptop is no longer registered. I went through the registration process again through the browser (and was told: why are you registering this machine again, it is registered, simply restart the network/reboot) but the problem does not go away. I upgraded a desktop on the same ethernet switch and this problem did not go show up there (I am using that to write this email).
I should mention that the network on this upgraded laptop works fine when I take the laptop home and connect.
So what could be the problem? I have not had such an issue with installations and upgrades for 40.5 versions of Fedora (the 0.5 is for RH9 that I think I used mid-2003 to late 2003 before Fedora Core 1). How do I troubleshoot this?
Many thanks in advance for any suggestions, and best wishes,
Ranjan
1 week, 2 days
F40: strange network issue after upgrade of laptop from F39
by R. G. Newbury
On 2024-05-23 19:20, users-request(a)lists.fedoraproject.org wrote:
> F40: strange network issue after upgrade of laptop from
> F39
> To:users@lists.fedoraproject.org
> Message-ID:<088547fa-c5dd-49f3-86a0-a09dba72a773(a)sieb.net>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 5/23/24 3:32 PM, Ranjan Maitra via users wrote:
>> I have a strange issue after upgrading a laptop (Dell XPS 13, 2013 edition). That is that I am connected (whether through WiFi or ethernet cable) to a university network which claims after the upgrade that the laptop is no longer registered. I went through the registration process again through the browser (and was told: why are you registering this machine again, it is registered, simply restart the network/reboot) but the problem does not go away. I upgraded a desktop on the same ethernet switch and this problem did not go show up there (I am using that to write this email).
> What are they using to identify the computer?
> What is happening with the networking that isn't working? No DHCP
> response, no network traffic, etc.
Ignore the browser for the moment. Go into Network Connections and see
if your install is cloning a random MAC address. I *suspect* that the
registration "feature" may be checking against the MAC address, while
the browser passes through the SSID + password only. Just a guess but I
have had the same problem with my android cellphone getting a
DHCP-served address instead of the expected static IP due to a random
MAC address.
Geoff
1 week, 3 days
audit features
by Billy Kay
Hi,
I've used FreeIPA on and off with various versions. Currently we are using ipa-server-common-4.10.0-8.
With the environment growing larger and having more engineers working with the setup, I would like have some way to audit / track of changes in everything from user, user groups, HBAC and sudo rules. I wonder if anyone has experience with auditing the changes. Any suggestion how to archive this?
Thanks
Billy
1 week, 4 days