Fedora 32 and Wireshark
by Earl Ramirez
Dear All,
After upgrading from Fedora 31 to 32 I am no longer able to launch
wireshark as it fails trying to find local interfaces. Based on my
troubleshooting it appears to be an issue with permission, the
application was reinstalled and downgraded; however, that did not
resolve the issue. A new account was created and I still encountered
Wireshark crashing while trying to find local interfaces.
I concluded that it is indeed a permission issue because I can launch
the application with the root account or by calling sudo wireshark from
the terminal. My login is a member of the wireshark group and I can see
the local interfaces if I execute /usr/bin/dumpcap -D or
/usr/bin/wireshark -D. At the same time if I execute sudo -u <username>
wireshark the application works. Has anyone experience this behaviour
after upgrading from F31 to F32? Additionally, I installed a vanilla
F32 VM and and wireshark worked but after updating it I am seeing the
same behaviour.
--
Earl Ramirez <earlaramirez(a)gmail.com>
4 years, 1 month
After fresh F32 installation, Areca raid disk cannot be seen
by Gian Luca Franceschin
During the installation I saw the Areca raid disk but after installation it was not visible. The controller was recognized but no disks attached to it. I spoke with Areca Taiwan and I started testing. I first installed F28 and it worked properly. The raid disk was recognized and accessible. I upgraded to F29 and the raid disk was no t visible anymore. The same with F30, F31 and F32. Did someone had the same problem?
Any suggestion?
4 years, 1 month
Re: (fedora) Re: Upgrade F31 -> F32 ended in freeze
by Jouk Jansen
Samuel Sieb wrote on 22-MAY-2020 10:32:36.96
>On 5/22/20 12:23 AM, Jouk Jansen wrote:
>> I tried an upgrade form F31 to F32 using dnf command line. All went well and
>> I rebooted into the upgrade process. Here I got a freeze: After 20 hours
>> looking at "Starting system upgrade. This may take a while" I canceled the
>> process. Luckely, I was able to boot "normally" into F31 after that.
>How did you "cancel the process"?
By "resetting" the computer
>> What may have went wrong?
>>
>> Or how can I "debug" this problem
>Try running "dnf system-upgrade log --number=-1".
[root@vleegert ~]# dnf system-upgrade log --number=-1
Error: Cannot find logs with this index.
Jouk
Pax, vel iniusta, utilior est quam iustissimum bellum.
(free after Marcus Tullius Cicero (106 b.Chr.-46 b.Chr.)
Epistularum ad Atticum 7.1.4.3)
Touch not the cat bot a glove
>------------------------------------------------------------------------------<
Jouk Jansen
joukj(a)hrem.nano.tudelft.nl
Technische Universiteit Delft tttttttttt uu uu ddddddd
Kavli Institute of Nanoscience tttttttttt uu uu dd dd
Nationaal centrum voor HREM tt uu uu dd dd
Lorentzweg 1 tt uu uu dd dd
2628 CJ Delft tt uu uu dd dd
Nederland tt uu uu dd dd
tel. 31-15-2782272 tt uuuuuuu ddddddd
>------------------------------------------------------------------------------<
4 years, 1 month
Re: (fedora) Re: Upgrade F31 -> F32 ended in freeze
by Jouk Jansen
Hi,
Oops I gave the command on the wrong machine. Now I get
dnf system-upgrade log --number=-1
.....
May 21 15:57:09 vlinder dnf[1839]: texlive-a5comb noarch 9:svn17020.4-19.fc32 >
May 21 15:57:09 vlinder dnf[1839]: texlive-abbr noarch 9:svn15878.0-19.fc32 >
May 21 16:02:21 vlinder systemd-journald[518]: Suppressed 4319 messages from dnf-system-upgrade.service
May 21 16:02:21 vlinder dnf[1839]: Total size: 25 G
May 21 16:02:21 vlinder dnf[1839]: Downloading Packages:
May 21 16:05:08 vlinder kernel: perf: interrupt took too long (3264 > 3131), lowering kernel.perf_event_max_sample_rate to 61000
May 21 16:10:48 vlinder dnf[1839]: Running transaction check
May 21 16:13:37 vlinder dnf[1839]: Transaction check succeeded.
May 21 16:13:37 vlinder dnf[1839]: Running transaction test
When I canceled the "upgrade" is was May 22 08.30.00.
But that is was "Running transaction test" I already knew
Jouk
Pax, vel iniusta, utilior est quam iustissimum bellum.
(free after Marcus Tullius Cicero (106 b.Chr.-46 b.Chr.)
Epistularum ad Atticum 7.1.4.3)
Touch not the cat bot a glove
>------------------------------------------------------------------------------<
Jouk Jansen
joukj(a)hrem.nano.tudelft.nl
Technische Universiteit Delft tttttttttt uu uu ddddddd
Kavli Institute of Nanoscience tttttttttt uu uu dd dd
Nationaal centrum voor HREM tt uu uu dd dd
Lorentzweg 1 tt uu uu dd dd
2628 CJ Delft tt uu uu dd dd
Nederland tt uu uu dd dd
tel. 31-15-2782272 tt uuuuuuu ddddddd
>------------------------------------------------------------------------------<
4 years, 1 month
Upgrade F31 -> F32 ended in freeze
by Jouk Jansen
Hi All
I tried an upgrade form F31 to F32 using dnf command line. All went well and
I rebooted into the upgrade process. Here I got a freeze: After 20 hours
looking at "Starting system upgrade. This may take a while" I canceled the
process. Luckely, I was able to boot "normally" into F31 after that.
What may have went wrong?
Or how can I "debug" this problem
regards
Jouk
Pax, vel iniusta, utilior est quam iustissimum bellum.
(free after Marcus Tullius Cicero (106 b.Chr.-46 b.Chr.)
Epistularum ad Atticum 7.1.4.3)
Touch not the cat bot a glove
>------------------------------------------------------------------------------<
Jouk Jansen
joukj(a)hrem.nano.tudelft.nl
Technische Universiteit Delft tttttttttt uu uu ddddddd
Kavli Institute of Nanoscience tttttttttt uu uu dd dd
Nationaal centrum voor HREM tt uu uu dd dd
Lorentzweg 1 tt uu uu dd dd
2628 CJ Delft tt uu uu dd dd
Nederland tt uu uu dd dd
tel. 31-15-2782272 tt uuuuuuu ddddddd
>------------------------------------------------------------------------------<
4 years, 1 month
ghost user?
by home user
f31, Gnome
Since going up to f31 in early April, every time I shut down, the shutdown GUI says "Other users are logged in.". But "who -a" shows only myself. Anyone else seeing this? What is going on?
4 years, 1 month
Lost Mate-panel
by Beartooth
Upgrading an E-series Thinkpad, a year or two old, running Fedora
31, via CLI, the upgrade kept failing with complaints about i.686 -- till
I did "dnf remove mate-*.i.686" -- then it completed, or seemed to. This
machine was behind an HDMI KVM switch, and was giving a display spread
across both its own monitor and my regular one, with four panels on each.
Since the upgrade reboot, when I KVM to the Thinkpad, I see blank
flashing panels on each monitor. There is no terminal emulator anywhere.
I've tried a couple times to reboot it to rescue mode, but it ignores
that.
I took it out from behind the KVM switch, but that didn't help.
I can get to the line at the beginning of the boot process which
is supposed to make it boot into rescue mode, but that has no effect.
Do I go looking for a live distro that may let me mount the Thpd's
hard drive and try to fix the panels somehow?
Do I just call it a total loss and install F 32 from a freshly
downloaded iso on a thumb drive?
Is there a third way?
--
Beartooth Staffwright, Not Quite Clueless Linux Power User
I have precious (very precious) little idea where up is.
4 years, 1 month
Getting U-Boot when trying to connect pollution sensors to my RPI 3 B+
running Fedora IoT 32 (latest update)
by Andrea Battaglia
Hi all,
I'm investigating and trying to make this work since a week now.
I wouldn't bother if I wasn't sure that digging deeper into this issue would take much more time than I have available atm.
So this is the scenario:
Hardware:
- Platform: RPi 3 B+
- Sensor (on the board): Pimoroni Enviro+
- Particulate Matter Sensor (connected to Enviro+): PMS5003
- SD Card: Sandisk 64Gb
Software: Fedora IoT 32 (just updated to the latest)
State of art:
I've successfully enabled and tested I2C and SPI. Drivers for the Enviro+ board run like a charm on a container manager by Podman.
The particulate Matter Sensor needs urat to be enabled, so I've made the fedora arm installer tool to enable uart for me.
Below the command issued to setup the SD card:
sudo fedora-arm-image-installer -y --image=/home/abattagl/Downloads/OS/Fedora-IoT-32-20200429.0.aarch64.raw.xz --target=rpi3 --media=/dev/sde --resizefs --addkey=/home/abattagl/.ssh/id_rsa.pub --norootpass --addconsole
I started testing uart from a fresh install and "rpm-ostree update" to avoid previous changes to the system affect the proper fuctioning of the serial port.
After the first boot of Fedora IoT and the system update I've shout id down and connected the Enviro+ sensors board.
The system booted properly after and I could see that both /dev/ttyS1 and /dev/ttyAMA0 are working at a boud rate of 9600:
[root@localhost ~]# stat /dev/ttyAMA0
File: /dev/ttyAMA0
Size: 0 Blocks: 0 IO Block: 4096 character special file
Device: 6h/6d Inode: 178 Links: 1 Device type: cc,40
Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 18/ dialout)
Context: system_u:object_r:tty_device_t:s0
Access: 2020-04-01 17:24:15.499999987 +0000
Modify: 2020-04-01 17:24:15.499999987 +0000
Change: 2020-04-01 17:24:15.499999987 +0000
Birth: -
[root@localhost ~]# stat /dev/ttyS0
File: /dev/ttyS0
Size: 0 Blocks: 0 IO Block: 4096 character special file
Device: 6h/6d Inode: 1113 Links: 1 Device type: 4,40
Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 18/ dialout)
Context: system_u:object_r:tty_device_t:s0
Access: 2020-04-01 17:24:15.249999987 +0000
Modify: 2020-04-01 17:24:15.249999987 +0000
Change: 2020-04-01 17:24:15.249999987 +0000
Birth: -
[root@localhost ~]# stat /dev/ttyS1
File: /dev/ttyS1
Size: 0 Blocks: 0 IO Block: 4096 character special file
Device: 6h/6d Inode: 1145 Links: 1 Device type: 4,41
Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 18/ dialout)
Context: system_u:object_r:tty_device_t:s0
Access: 2020-04-01 17:24:15.599999987 +0000
Modify: 2020-04-01 17:24:15.599999987 +0000
Change: 2020-04-01 17:24:15.599999987 +0000
Birth: -
The big issues happens when I connect the particulate matter sensor to the sensors board.
The RPi startup phase stops showing the U-Boot command prompt. and, of course, I haven't got the skills to debug/investigate that.
I can just guess I'm missing something.
A side note: using raspbian and the Pimoroni installation script, which, in turn, uses raspi-config to set up the system as the sensor expect, everything works fine and I'm able to query the particulate matter sensor using the python drivers.
I've tried to read the bash code of the raspi-config tool, but I'm not capable to understand ad deeply as I would.
The official documentation for the sensors says (quote):
"Note that if you're using this sensor with Raspberry Pi, then you'll need to make a couple of changes to its configuration. Type sudo raspi-config in the terminal and then under "Interfacing options" and "Serial" disable the login shell and enable the serial port hardware. Edit your /boot/config.txt file and add the lines enable_uart=1 and dtoverlay=pi3-miniuart-bt to the bottom of the file."
https://shop.pimoroni.com/products/pms5003-particulate-matter-sensor-with...
here is my config.txt file:
[root@localhost ~]# cat /boot/efi/config.txt
[pi3]
kernel=rpi3-u-boot.bin
[pi4]
kernel=rpi4-u-boot.bin
[all]
arm_64bit=1
dtparam=i2c_arm=on
dtparam=spi=on
bootcode_delay=1
gpu_mem=32
start_x=1
upstream_kernel=1
dtoverlay=upstream
dtoverlay=pi3-miniuart-bt
dtoverlay=adau7002-simple
mask_gpu_interrupt1=0x100
audio_pwm_mode=0
enable_uart=1
And the kernel args:
[root@localhost ~]# rpm-ostree kargs
net.ifnames=0 modprobe.blacklist=vc4 root=UUID=3111a58e-40ce-4a5d-9314-90d7993c97f9 ostree=/ostree/boot.1/fedora-iot/82e3a6b60b9e57a232d7bcc53ea00d8f7ec28eacc454f0391f8e5c29d671d2ed/0
Could you please provide support on this topic? It's a very interesting and technical detail to me and it's a compulsory step for a meaningful, big project I'm currently running for my company.
Many thanks in advance,
Andrea
4 years, 1 month
Newbie question on mdadm
by Patrick O'Callaghan
I recently had to throw out an old NAS I've been using for over 10
years. However I rescued the 2 HDDs and got a dual-slot USB SATA
docking station for them. To my astonishment Fedora recognised them
immediately as a RAID1 array (formatted with XFS) without me doing
anything.
However gsmartcontrol reports that one of the HDDs has internal errors.
Would it be best to correct these using mdadm (assuming they can be
corrected), and if so, how? Or should I do an offline copy with the
docking station's "clone" button?
Are there any general recommendations for monitoring these beasties? I
don't want to change anything for the time being and will be using the
thing mainly for backup, but I see there is such a thing as mdmon which
isn't currently running. Should it be? I have no previous experience
with md devices.
poc
4 years, 1 month
VLC and screen saver
by Robin Lee
Hi
I'm on Fedora 32, but this problem I have had for a while.
The thing is that sometimes when I close vlc after I've watched some
video it doesn't terminate cleanly. That is there is still a vlc
process running in the background and it prevents the screen saver from
blanking the screen. So sometimes when I wake up or come home after
being out I notice that the screen has been on all the time. Not so
good. I have to go to system monitor and find the vlc process and kill
it, then the screen saver can again do its thing.
Can anything be done about it, except always checking manually that vlc
has terminated completely?
Cheers
Robin
4 years, 1 month
