Re: ch341-uart - ttyUSBx disconnecting???

2023-11-29 Thread Steve Underwood

Hi Jeffrey,

I have a CH341 UART connected to this machine (Fedora 37 x86_64). Its 
stable, and has never caused me any real problems. However, my log looks 
slightly different. I get this:


Nov 29 13:43:34 haswell kernel: usb 1-4: new full-speed USB device 
number 12 using xhci_hcd
Nov 29 13:43:34 haswell kernel: usb 1-4: New USB device found, 
idVendor=1a86, idProduct=7523, bcdDevice= 2.64
Nov 29 13:43:34 haswell kernel: usb 1-4: New USB device strings: Mfr=0, 
Product=2, SerialNumber=0

Nov 29 13:43:34 haswell kernel: usb 1-4: Product: USB Serial
Nov 29 13:43:34 haswell kernel: ch341 1-4:1.0: ch341-uart converter detected
Nov 29 13:43:34 haswell kernel: usb 1-4: ch341-uart converter now 
attached to ttyUSB0


The bcdDevice field is different. That sounds like a big difference in 
revision numbers. Maybe we have different devices from the CH341 family. 
Maybe there is some compatibility issue there. Maybe you just have a 
dirty USB connector, or some other bad connection problem.


Steve


On 29/11/2023 02:55, Jeffrey Ross via users wrote:
I'm trying to connect an Arduino to my system (Fedora 38 - 
6.5.12-200.fc38.x86_64) that uses a ch341 serial uart.


I've been searching around and found issues on other distributions and 
the "brltty" application, since I don't need braille I removed the 
application but the problem remains.  I have also found a different 
driver called "CH341SER"  so I tried unloading the existing ch341 
module and installing CH341SER (module shows up as ch34x) but other 
than tainting the kernel it made no different so I unloaded the module.


I have been unable find anything specific to Fedora or anything 
relatively new but it appears to be a common issue across multiple 
distributions.


Any pointers would be appreciated, see below for dmesg output.

Thanks,
Jeff


[  268.820420] usb 1-9.3.7: new full-speed USB device number 50 using 
xhci_hcd
[  268.897931] usb 1-9.3.7: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice=81.34
[  268.897947] usb 1-9.3.7: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0

[  268.897953] usb 1-9.3.7: Product: USB Serial
[  268.907342] ch341 1-9.3.7:1.0: ch341-uart converter detected
[  268.908444] usb 1-9.3.7: ch341-uart converter now attached to ttyUSB0
[  272.084557] usb 1-9.3.7: USB disconnect, device number 50
[  272.084964] ch341-uart ttyUSB0: ch341-uart converter now 
disconnected from ttyUSB0

[  272.085012] ch341 1-9.3.7:1.0: device disconnected
[  274.196380] usb 1-9.3.7: new full-speed USB device number 51 using 
xhci_hcd
[  274.273474] usb 1-9.3.7: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice=81.34
[  274.273489] usb 1-9.3.7: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0

[  274.273495] usb 1-9.3.7: Product: USB Serial
[  274.282837] ch341 1-9.3.7:1.0: ch341-uart converter detected
[  274.283898] usb 1-9.3.7: ch341-uart converter now attached to ttyUSB0
[  277.716513] usb 1-9.3.7: USB disconnect, device number 51
[  277.716910] ch341-uart ttyUSB0: ch341-uart converter now 
disconnected from ttyUSB0
[  277.716956] ch341 1-9.3.7:1.0: device disconnected 

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread olivares33561 via users
Dear fellow fedora users,

upon updating and rebooting the new kernel refuses to boot or just hangs.  How 
do I troubleshoot this issue?
I have to boot 6.5.12-300 so I can use the computer.

Thanks in Advance,


Antonio 

Sent from ProtonMail, encrypted email based in Switzerland.

Sent with Proton Mail secure email.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: ch341-uart - ttyUSBx disconnecting???

2023-11-29 Thread Jeffrey Ross via users
I should have added, I tried several USB cables and the device works 
without an issue on a Windows 11 system.


On 11/29/23 8:50 AM, Steve Underwood wrote:

Hi Jeffrey,

I have a CH341 UART connected to this machine (Fedora 37 x86_64). Its 
stable, and has never caused me any real problems. However, my log 
looks slightly different. I get this:


Nov 29 13:43:34 haswell kernel: usb 1-4: new full-speed USB device 
number 12 using xhci_hcd
Nov 29 13:43:34 haswell kernel: usb 1-4: New USB device found, 
idVendor=1a86, idProduct=7523, bcdDevice= 2.64
Nov 29 13:43:34 haswell kernel: usb 1-4: New USB device strings: 
Mfr=0, Product=2, SerialNumber=0

Nov 29 13:43:34 haswell kernel: usb 1-4: Product: USB Serial
Nov 29 13:43:34 haswell kernel: ch341 1-4:1.0: ch341-uart converter 
detected
Nov 29 13:43:34 haswell kernel: usb 1-4: ch341-uart converter now 
attached to ttyUSB0


The bcdDevice field is different. That sounds like a big difference in 
revision numbers. Maybe we have different devices from the CH341 
family. Maybe there is some compatibility issue there. Maybe you just 
have a dirty USB connector, or some other bad connection problem.


Steve


On 29/11/2023 02:55, Jeffrey Ross via users wrote:
I'm trying to connect an Arduino to my system (Fedora 38 - 
6.5.12-200.fc38.x86_64) that uses a ch341 serial uart.


I've been searching around and found issues on other distributions 
and the "brltty" application, since I don't need braille I removed 
the application but the problem remains.  I have also found a 
different driver called "CH341SER"  so I tried unloading the existing 
ch341 module and installing CH341SER (module shows up as ch34x) but 
other than tainting the kernel it made no different so I unloaded the 
module.


I have been unable find anything specific to Fedora or anything 
relatively new but it appears to be a common issue across multiple 
distributions.


Any pointers would be appreciated, see below for dmesg output.

Thanks,
Jeff


[  268.820420] usb 1-9.3.7: new full-speed USB device number 50 using 
xhci_hcd
[  268.897931] usb 1-9.3.7: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice=81.34
[  268.897947] usb 1-9.3.7: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0

[  268.897953] usb 1-9.3.7: Product: USB Serial
[  268.907342] ch341 1-9.3.7:1.0: ch341-uart converter detected
[  268.908444] usb 1-9.3.7: ch341-uart converter now attached to ttyUSB0
[  272.084557] usb 1-9.3.7: USB disconnect, device number 50
[  272.084964] ch341-uart ttyUSB0: ch341-uart converter now 
disconnected from ttyUSB0

[  272.085012] ch341 1-9.3.7:1.0: device disconnected
[  274.196380] usb 1-9.3.7: new full-speed USB device number 51 using 
xhci_hcd
[  274.273474] usb 1-9.3.7: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice=81.34
[  274.273489] usb 1-9.3.7: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0

[  274.273495] usb 1-9.3.7: Product: USB Serial
[  274.282837] ch341 1-9.3.7:1.0: ch341-uart converter detected
[  274.283898] usb 1-9.3.7: ch341-uart converter now attached to ttyUSB0
[  277.716513] usb 1-9.3.7: USB disconnect, device number 51
[  277.716910] ch341-uart ttyUSB0: ch341-uart converter now 
disconnected from ttyUSB0
[  277.716956] ch341 1-9.3.7:1.0: device disconnected 

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread olivares33561 via users


> Dear fellow fedora users,
> 
> upon updating and rebooting the new kernel refuses to boot or just hangs. How 
> do I troubleshoot this issue?
> I have to boot 6.5.12-300 so I can use the computer.
> 
> Thanks in Advance,
> 
> 
> Antonio
> 
> Sent from ProtonMail, encrypted email based in Switzerland.
> 
> Sent with Proton Mail secure email.
> 
> --

I ran a command to check for the new updates:

kernel-modules-core-6.6.2-201.fc39.x86_64
kernel-core-6.6.2-201.fc39.x86_64
kernel-modules-6.6.2-201.fc39.x86_64
kernel-modules-extra-6.6.2-201.fc39.x86_64
kernel-headers-6.6.2-201.fc39.x86_64
kernel-devel-6.6.2-201.fc39.x86_64
olivares@fedora:~$ sudo dnf remove kernel-6.6*
[sudo] password for olivares: 
Dependencies resolved.

 PackageArchitecture   Version   RepositorySize

Removing:
 kernel x86_64 6.6.2-201.fc39@updates   0  

Transaction Summary

Remove  1 Package

Freed space: 0  
Is this ok [y/N]: n
Operation aborted.
olivares@fedora:~$ 

I see that the size of the kernel is 0.  How is that possible?


Best Regards,


Antonio 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread stan via users
On Wed, 29 Nov 2023 14:28:02 +
olivares33561 via users  wrote:

> Dear fellow fedora users,
> 
> upon updating and rebooting the new kernel refuses to boot or just
> hangs.  How do I troubleshoot this issue? I have to boot 6.5.12-300
> so I can use the computer.

It is possible that the kernel actually made it far enough in boot that
the journal is started, but there is still a problem.  In that
case look at the boot log in journalctl,
journalctl -b 0
or look at any other recent messages if it wasn't boot that caused the
issue,
journalctl -r

If that doesn't give anything useful, then turn off rhgb and quiet in
the kernel command line so that the messages during boot show up.  Then
you can see where exactly it is failing, and might even see why.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread Patrick O'Callaghan
On Wed, 2023-11-29 at 14:28 +, olivares33561 via users wrote:
> Dear fellow fedora users,
> 
> upon updating and rebooting the new kernel refuses to boot or just
> hangs.  How do I troubleshoot this issue?
> I have to boot 6.5.12-300 so I can use the computer.

Not enough information to go on. What actually happens? Do you see
anything onscreen? What happens if you remove the rhgb parameter from
the boot line?

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread George N. White III
On Wed, Nov 29, 2023 at 10:28 AM olivares33561 via users <
users@lists.fedoraproject.org> wrote:

> Dear fellow fedora users,
>
> upon updating and rebooting the new kernel refuses to boot or just hangs.
> How do I troubleshoot this issue?
> I have to boot 6.5.12-300 so I can use the computer.
>

Others have already asked for details from journalctl and removing "rhgb
quiet".  You can also use 
when booting to see the messages.

Are you using non-free packages with akmods?  One common issue with
command-line updates is rebooting
before the non-free package install is complete.

-- 
George N. White III
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread olivares33561 via users

On Wednesday, November 29th, 2023 at 8:49 AM, Patrick O'Callaghan 
 wrote:


> On Wed, 2023-11-29 at 14:28 +, olivares33561 via users wrote:
> 
> > Dear fellow fedora users,
> > 
> > upon updating and rebooting the new kernel refuses to boot or just
> > hangs. How do I troubleshoot this issue?
> > I have to boot 6.5.12-300 so I can use the computer.
> 
> 
> Not enough information to go on. What actually happens? Do you see
> anything onscreen? What happens if you remove the rhgb parameter from
> the boot line?
> 
> poc
> --
> ___

I restart and boot with rhgb quiet removed I see 
[ OK ] ...
.
but at the end there is a line that says
[ OK ] Reached target sysinit.target - System Initialization.


and it just stays there indefinitely.  I will restart under previous kernel and 
remove this one.  And retest when another comes by.  

Best Regards,


Antonio 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread olivares33561 via users
On Wednesday, November 29th, 2023 at 8:56 AM, George N. White III 
 wrote:


> On Wed, Nov 29, 2023 at 10:28 AM olivares33561 via users 
>  wrote:
> 
> > Dear fellow fedora users,
> > 
> > upon updating and rebooting the new kernel refuses to boot or just hangs. 
> > How do I troubleshoot this issue?
> > I have to boot 6.5.12-300 so I can use the computer.
> 
> 
> Others have already asked for details from journalctl and removing "rhgb 
> quiet". You can also use 
> when booting to see the messages.
> 
> Are you using non-free packages with akmods? One common issue with 
> command-line updates is rebooting
> before the non-free package install is complete.
> 
> --

Your mail to 'users@lists.fedoraproject.org' with the subject

Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

Is being held until the list moderator can review it for approval.

The message is being held because:

The message is larger than the 60 KB maximum size

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.

NOTE: If your message has been held due to size, please consider this
a rejection and a friendly request to reduce the size and resend.  The
list moderators will not approve such messages.

If you are attaching logs or command output, please trim it to a
minimal amount (we can ask for more context, if needed).

If you are attaching an image, please crop it to reduce their size.

Also keep in mind that attachments will be encoded by your mail client
(usually via base64) and this encoding increases the size by as much
as 33%.

output of command was big.  No proprietary blobs in kernel.  Using intel hdmi 
output.  
$ sudo lspci
00:00.0 PCI bridge: Intel Corporation Device 4c53 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation RocketLake-S GT1 [UHD 
Graphics 730] (rev 04)
00:04.0 Signal processing controller: Intel Corporation Device 4c03 (rev 01)
00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal 
Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host 
Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C 
Controller #0
00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
00:17.0 RAID bus controller: Intel Corporation Comet Lake PCH-H RAID
00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0)
00:1f.0 ISA bridge: Intel Corporation H470 Chipset LPC/eSPI Controller
00:1f.3 Audio device: Intel Corporation Device f1c8
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600 (rev 
21)

Everything just worked before 6.6 kernel.  

Best Regards,


Antonio 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread George N. White III
On Wed, Nov 29, 2023 at 11:01 AM olivares33561 via users <
users@lists.fedoraproject.org> wrote:

>
> On Wednesday, November 29th, 2023 at 8:49 AM, Patrick O'Callaghan <
> pocallag...@gmail.com> wrote:
>
>
> > On Wed, 2023-11-29 at 14:28 +, olivares33561 via users wrote:
> >
> > > Dear fellow fedora users,
> > >
> > > upon updating and rebooting the new kernel refuses to boot or just
> > > hangs. How do I troubleshoot this issue?
> > > I have to boot 6.5.12-300 so I can use the computer.
> >
> >
> > Not enough information to go on. What actually happens? Do you see
> > anything onscreen? What happens if you remove the rhgb parameter from
> > the boot line?
> >
> > poc
> > --
> > ___
>
> I restart and boot with rhgb quiet removed I see
> [ OK ] ...
> .
> but at the end there is a line that says
> [ OK ] Reached target sysinit.target - System Initialization.
>
>
> and it just stays there indefinitely.  I will restart under previous
> kernel and remove this one.  And retest when another comes by.
>

Have you looked at journalclt?  6.6.2-201.fc39.x86_64 works for many of us,
so it could help to identify what is different about your
system.  The next step after "systemd[1]: Reached target sysinit.target -
System Initialization." is attaching storage devices.
Some storage devices have "quirks" that kernel usually works around. For
example:

kernel: nvme nvme0: missing or invalid SUBNQN field.

I would take a close look at journalctl entries for a successful boot
following the "sysiinit.target" line for informative messages.
You can also check specific devices in the Linux Hardware Database -- some
have comments that suggest kernel command-line
options to enable dodgy hardware.

-- 
George N. White III
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread old sixpack13
...
> olivares@fedora:~$ sudo dnf remove kernel-6.6*
...

you should use
sudo dnf remove kernel-core-x.y.z

to get rid of all packages belonging to the kernel
kernel-core is a meta package
===
I also own a RocketLake-S.
No problems here

any error message during kernel install ?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs

2023-11-29 Thread olivares33561 via users




Sent from ProtonMail, encrypted email based in Switzerland.

Sent with Proton Mail secure email.

On Wednesday, November 29th, 2023 at 9:28 AM, old sixpack13 
 wrote:


> ...
> 
> > olivares@fedora:~$ sudo dnf remove kernel-6.6*
> 
> ...
> 
> you should use
> sudo dnf remove kernel-core-x.y.z
> 
> to get rid of all packages belonging to the kernel
> kernel-core is a meta package
> ===
> I also own a RocketLake-S.
> No problems here
> 
> any error message during kernel install ?
> --

Done!

Nov 29 09:02:16 fedora systemd[1]: Startup finished in 15.627s (firmware) + 
9.754s (loader) + 1.195s (kernel) + 5.821s (initrd) + 32.093s (userspace) = 
1min 4.493s.
Nov 29 09:10:43 fedora sudo[3477]: olivares : TTY=pts/3 ; 
PWD=/home/olivares/Downloads/kerTeX/Documents/Documents/mptmp ; USER=root ; 
COMMAND=/bin/dnf remove kernel-headers-6.6.2-201.fc39.x86_64 
kernel-devel-6.6.2-201.fc39.x86_64 kernel-modules-core-6.6.2-201.fc39.x86_64 
kernel-core-6.6.2-201.fc39.x86_64 kernel-modules-6.6.2-201.fc39.x86_64 
kernel-6.6.2-201.fc39.x86_64 kernel-modules-extra-6.6.2-201.fc39.x86_64
Nov 29 09:11:26 fedora sudo[3512]: olivares : TTY=pts/3 ; 
PWD=/home/olivares/Downloads/kerTeX/Documents/Documents/mptmp ; USER=root ; 
COMMAND=/bin/dnf remove kernel-6.6.2-201.fc39.x86_64
Nov 29 09:12:53 fedora sudo[3560]: olivares : TTY=pts/3 ; 
PWD=/home/olivares/Downloads/kerTeX/Documents/Documents/mptmp ; USER=root ; 
COMMAND=/bin/dnf remove kernel-core-6.6.2-201.fc39.x86_64

will run Linux fedora 6.5.12-300.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 
22:44:24 UTC 2023 x86_64 GNU/Linux
until a 6.6.X fedora kernel actually boots and works on this pc.  

Best Regards,


Antonio 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: vlc alternative?

2023-11-29 Thread Alex
> ps ax | grep -E 'tty2|pts/21' and see what is starting it on those
> terminals.
>

Virtually everything started after logging in.

I contacted silicondust support, and they said any application that
supports DNLA will work, but apparently weren't able to tell me how vlc
specifically is being spawned. It's definitely launched by HDHomeRun, but I
can't find anything in the documentation or any local config files that
describes how that's happening.

Their documentation appears to indicate you have to first set the UDP port
after starting vlc, but that's not even necessary with the way it's somehow
configured on my system.

Any ideas greatly appreciated.

Thanks,
Alex





>
> On Mon, Nov 27, 2023 at 7:19 PM Alex  wrote:
> >
> > Hi,
> >
> > On Mon, Nov 27, 2023 at 5:14 PM ToddAndMargo via users <
> users@lists.fedoraproject.org> wrote:
> >>
> >> On 11/27/23 09:29, Alex wrote:
> >> > Hi,
> >> > I'm using vlc with my hdhomerun TV tuner, but vlc has a problem that
> >> > hasn't been fixed for a really long time. Does anyone have a
> >> > recommendation for a similar app I can use for streaming?
> >> >
> >> > I'm really only otherwise familiar with mplayer, but I don't think it
> >> > supports streaming in this way where I can connect it to a socket
> like I
> >> > can with vlc.
> >> >
> >> > btw, the vlc error involves messages like these:
> >> >
> >> > [7fb3a4001130] ts demux error: libdvbpsi error (PSI decoder): TS
> >> > discontinuity (received 10, expected 9) for PID 112
> >> >
> >> > Thanks,
> >> > Alex
> >>
> >> Hi Alex,
> >>
> >> I could ot stand all the bugs in vlc so I switched to SMPlayer.
> >> I stream music all the time.
> >>
> >> Here is my keeper on SMPlayer:
> >
> >
> > That is very helpful, thanks. I already had RPM Fusion installed, and
> now also have smplayer installed.
> >
> > However, my HDHomeRun config appears to be linked directly to vlc, and I
> don't know how to change it to instead spawn smplayer.
> >
> > $ ps ax|grep vlc
> > 2963508 tty2 Sl+0:03 /usr/bin/vlc --started-from-file
> > 2964260 pts/21   Sl+0:01 vlc --deinterlace=-1 udp://@127.0.0.1:5000
> >
> > Where is it getting this config info from? I've tried resetting the vlc
> config, and have searched through the menus looking for something related
> to UDP 5000 and don't see anything. I've also tried to figure out how
> HDHomeRun is launching vlc from a file(?), but also don't see anything
> there, unless it's talking about the socket...
> >
> > Any ideas greatly appreciated.
> > Thanks,
> > Alex
> >>
> >>
> > --
> > ___
> > users mailing list -- users@lists.fedoraproject.org
> > To unsubscribe send an email to users-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> > Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Openh264, ffmpeg,etc.

2023-11-29 Thread Ger van Dijck

Hi Fedora/Linux Lovers,

I have the impression that the problems with Fedora-Cisco-Openh264 and 
FFmpeg gives me the idea  of  "The ever continued story of 
Coronationstreet".


When I do an dnf update I get the following message:


Fedora 39 openh264 (From Cisco)-x86_64 Errors during downloading for 
fedora-cisco-openh264.


Statuscode 404 for 
https://codecs/fedoraproject.org/openh264/39/x86_64/repodata/repomd.xml 
(IP 18.133.140.134).


Cannot download repodata/repomd.xml : All mirrors were tried.

Failed to download metadata for "fedora-cisco-openh264".



I found a solution in downloading  Repo Terra 39 Fedora  and could 
install openh264  :  And all , you dont believe it functioned.



I had a very helpsome discussion with Tom Horsley, Samual Sieb,Jef 
Walton and Go Cames.




When giving dnf info openh264 I got from Terra 39 Fedora installed 
packages : Repos Terra 39 Fedora openh264 Fedora URL 
https://www.openh264.org


License:BSD.

UPDATED:

DNfdagora did sent a messsage on November 24.11.2023 to update some 
objects and in this list :


gstreamer1-plugin-openh264-1.22.7-2.fc39.x86_64

openh264-2.4.0-1.fc39.x86_64


INStALLED:

openh264-2.4.0-2.fc39.x86_64




After this execised nothing did functioned anymore.


Dnfdagora did sent a message on November 25.11.2023 to update objects 
and in this list:



UPDATED:

libde265-1.0.13-1.fc39.86_64


After that


INSTLALLED:


gstreamer1-plugin-openh264-1.22.7-2.fc39.86_64

ffmpeg-libs-3.3.6-3.4.x86_64

ffmpeg-3.3.6-3.4.x86_64

libavdevice-3.3.6-3.4.x86_64


UPDATED:


ffmpeg-libs-6.0.1-3.fc39.x86_64

ffmpeg-6.0.1-3.fc39.x86_64

libavdevice-6.0.1-3.fc39.X86_64



And all runs : Thanks God.



Is there in this (Unix) world someone (Abe Ye Kanobi ?) who can and is 
willing to solve this problem ?





Ger van Dijck
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: vlc alternative?

2023-11-29 Thread Roger Heflin
if you installed their software then it could be doing anything.  it
is very likely that they do not have anyone still around who remembers
what the software does.  You would have to look at it and see if it is
a bunch of scripts and/or how it works.

I use my HDhomeruns via mythtv.  The hardest part of mythtv is the
initial setup, once you get it setup about all I have had to do is
update the channel list and/or run a scan every so often because the
broadcast channels keep changing frequencies.

On Wed, Nov 29, 2023 at 10:03 AM Alex  wrote:
>
>
>> ps ax | grep -E 'tty2|pts/21' and see what is starting it on those terminals.
>
>
> Virtually everything started after logging in.
>
> I contacted silicondust support, and they said any application that supports 
> DNLA will work, but apparently weren't able to tell me how vlc specifically 
> is being spawned. It's definitely launched by HDHomeRun, but I can't find 
> anything in the documentation or any local config files that describes how 
> that's happening.
>
> Their documentation appears to indicate you have to first set the UDP port 
> after starting vlc, but that's not even necessary with the way it's somehow 
> configured on my system.
>
> Any ideas greatly appreciated.
>
> Thanks,
> Alex
>
>
>
>
>>
>>
>> On Mon, Nov 27, 2023 at 7:19 PM Alex  wrote:
>> >
>> > Hi,
>> >
>> > On Mon, Nov 27, 2023 at 5:14 PM ToddAndMargo via users 
>> >  wrote:
>> >>
>> >> On 11/27/23 09:29, Alex wrote:
>> >> > Hi,
>> >> > I'm using vlc with my hdhomerun TV tuner, but vlc has a problem that
>> >> > hasn't been fixed for a really long time. Does anyone have a
>> >> > recommendation for a similar app I can use for streaming?
>> >> >
>> >> > I'm really only otherwise familiar with mplayer, but I don't think it
>> >> > supports streaming in this way where I can connect it to a socket like I
>> >> > can with vlc.
>> >> >
>> >> > btw, the vlc error involves messages like these:
>> >> >
>> >> > [7fb3a4001130] ts demux error: libdvbpsi error (PSI decoder): TS
>> >> > discontinuity (received 10, expected 9) for PID 112
>> >> >
>> >> > Thanks,
>> >> > Alex
>> >>
>> >> Hi Alex,
>> >>
>> >> I could ot stand all the bugs in vlc so I switched to SMPlayer.
>> >> I stream music all the time.
>> >>
>> >> Here is my keeper on SMPlayer:
>> >
>> >
>> > That is very helpful, thanks. I already had RPM Fusion installed, and now 
>> > also have smplayer installed.
>> >
>> > However, my HDHomeRun config appears to be linked directly to vlc, and I 
>> > don't know how to change it to instead spawn smplayer.
>> >
>> > $ ps ax|grep vlc
>> > 2963508 tty2 Sl+0:03 /usr/bin/vlc --started-from-file
>> > 2964260 pts/21   Sl+0:01 vlc --deinterlace=-1 udp://@127.0.0.1:5000
>> >
>> > Where is it getting this config info from? I've tried resetting the vlc 
>> > config, and have searched through the menus looking for something related 
>> > to UDP 5000 and don't see anything. I've also tried to figure out how 
>> > HDHomeRun is launching vlc from a file(?), but also don't see anything 
>> > there, unless it's talking about the socket...
>> >
>> > Any ideas greatly appreciated.
>> > Thanks,
>> > Alex
>> >>
>> >>
>> > --
>> > ___
>> > users mailing list -- users@lists.fedoraproject.org
>> > To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> > Fedora Code of Conduct: 
>> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> > List Archives: 
>> > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>> > Do not reply to spam, report it: 
>> > https://pagure.io/fedora-infrastructure/new_issue
>> --
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>> Do not reply to spam, report it: 
>> https://pagure.io/fedora-infrastructure/new_issue
>
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of 

Re: Openh264, ffmpeg,etc.

2023-11-29 Thread Jeffrey Walton
On Wed, Nov 29, 2023 at 12:38 PM Ger van Dijck  wrote:
>
> Hi Fedora/Linux Lovers,
>
> I have the impression that the problems with Fedora-Cisco-Openh264 and
> FFmpeg gives me the idea  of  "The ever continued story of
> Coronationstreet".
>
> When I do an dnf update I get the following message:
>
> Fedora 39 openh264 (From Cisco)-x86_64 Errors during downloading for
> fedora-cisco-openh264.
>
> Statuscode 404 for
> https://codecs/fedoraproject.org/openh264/39/x86_64/repodata/repomd.xml
> (IP 18.133.140.134).
>
> Cannot download repodata/repomd.xml : All mirrors were tried.
>
> Failed to download metadata for "fedora-cisco-openh264".
>
> I found a solution in downloading  Repo Terra 39 Fedora  and could
> install openh264  :  And all , you dont believe it functioned.
>
> I had a very helpsome discussion with Tom Horsley, Samual Sieb,Jef
> Walton and Go Cames.
>
> When giving dnf info openh264 I got from Terra 39 Fedora installed
> packages : Repos Terra 39 Fedora openh264 Fedora URL
> https://www.openh264.org
>
> License:BSD.
>
> UPDATED:
>
> DNfdagora did sent a messsage on November 24.11.2023 to update some
> objects and in this list :
>
> gstreamer1-plugin-openh264-1.22.7-2.fc39.x86_64
>
> openh264-2.4.0-1.fc39.x86_64
>
>
> INStALLED:
>
> openh264-2.4.0-2.fc39.x86_64
>
> After this execised nothing did functioned anymore.
>
> Dnfdagora did sent a message on November 25.11.2023 to update objects
> and in this list:
>
> UPDATED:
>
> libde265-1.0.13-1.fc39.86_64
>
> After that
>
> INSTLALLED:
>
>
> gstreamer1-plugin-openh264-1.22.7-2.fc39.86_64
>
> ffmpeg-libs-3.3.6-3.4.x86_64
>
> ffmpeg-3.3.6-3.4.x86_64
>
> libavdevice-3.3.6-3.4.x86_64
>
> UPDATED:
>
> ffmpeg-libs-6.0.1-3.fc39.x86_64
>
> ffmpeg-6.0.1-3.fc39.x86_64
>
> libavdevice-6.0.1-3.fc39.X86_64
>
> And all runs : Thanks God.
>
> Is there in this (Unix) world someone (Abe Ye Kanobi ?) who can and is
> willing to solve this problem ?

I'm not sure about your specific problem, but... I usually follow

on Fedora to get Firefox working as expected.

Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Openh264, ffmpeg,etc.

2023-11-29 Thread Ralf Corsépius



Am 29.11.23 um 18:58 schrieb Jeffrey Walton:

I'm not sure about your specific problem, but...


The origin of his problem is cisco's server often being poorly reachable.

Ralf
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: vlc alternative?

2023-11-29 Thread Tim via users
On Wed, 2023-11-29 at 11:02 -0500, Alex wrote:
> I contacted silicondust support, and they said any application that
> supports DNLA will work, but apparently weren't able to tell me how
> vlc specifically is being spawned. It's definitely launched by
> HDHomeRun, but I can't find anything in the documentation or any
> local config files that describes how that's happening.

If you open VLC's media information window (in the tools menu), when it
is connected, does it give you any useful info about the stream it's
currently playing?

DNLA is a set of (alleged) standards about home network streaming.  I
might guess it needs mDNS (Avahi/ZeroConf) working for the source
device to be automatically found by any player devices.  It seemed to
be working that way when I used a smart TV to look at files on a NAS
with a media server built into it (as to how it found the NAS drives by
itself).

My dabbling with this kind of thing is quite out of date.  A friend
used some Western Digital media players connected to his TV set, many
years ago.  They'd find his media store (NAS drives, if I remember
correctly, though could have been SMB shares), and the WD media players
would trawl through the available contents generating an on-screen menu
of things to watch.

I could guess that their box has some kind of webserver that you may be
able to aim VLC at (using the box's IP address).

-- 
 
NB:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
 
The following system info data is generated fresh for each post:
 
uname -rsvp
Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53
UTC 2023 x86_64
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue