USB ethernet wake-on-LAN?
I have a new ThinkPad T14s AMD 4th gen notebook, and a USB-C ethernet adapter. I would like to be able to send wake-on-LAN to the notebook for some uses. The ethernet adapter also has a USB-C port for power delivery (so it can also charge the notebook). When the notebook is suspended, the ethernet link stays up (LEDs are lit on both it and the switch port). It also shows support for wake-on-LAN, defaulting to magic packet mode. I tried the "old-style" /proc/acpi/wakeup (which shows enabled for the USB in question) as well as /sys/bus/usb/devices/*/power/wakeup (which all defaulted to disabled, but I enabled them too). However, nothing seemed to work. I have other systems with built-in/PCIe NICs that I can wake; it's just this one with the USB (because no built-in NIC) that's a problem. The BIOS has a setting for USB wake-on-LAN with the official dock (which was enabled), but I didn't see anything else that looked relevant. Any suggestions? -- Chris Adams -- ___ 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: Python code error in F39, but not in F38
On Wed Nov22'23 02:36:35PM, Samuel Sieb wrote: > From: Samuel Sieb > Date: Wed, 22 Nov 2023 14:36:35 -0800 > To: users@lists.fedoraproject.org > Reply-To: Community support for Fedora users > Subject: Re: Python code error in F39, but not in F38 > > On 11/22/23 14:20, Ranjan Maitra via users wrote: > > On Wed Nov22'23 09:49:49PM, Barry Scott wrote: > > > From: Barry Scott > > > Date: Wed, 22 Nov 2023 21:49:49 + > > > > At this point you need get more information. > > > > > > > > What do the folllowing GDB commands print? > > > > > > > > p tstate > > > > p tstate->interp > > > > thread allow all bt > > > Doh... > > > > > > thread apply all bt > > > > > > I always type: > > > t a a bt > > > > > > and typo'ed the expansion. > > > > Thanks, here is what comes out: > > > > (gdb) p tstate->interp > > > > value has been optimized out > > (gdb) thread apply all bt > > You missed the first one: "p tstate". > My apologies, I did not include this in my cut-and-paste: (gdb) p tstate $1 = Sorry about that. All this in F39 (python 3.12, of course). Ranjan -- ___ 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: Python code error in F39, but not in F38
On 11/22/23 14:20, Ranjan Maitra via users wrote: On Wed Nov22'23 09:49:49PM, Barry Scott wrote: From: Barry Scott Date: Wed, 22 Nov 2023 21:49:49 + At this point you need get more information. What do the folllowing GDB commands print? p tstate p tstate->interp thread allow all bt Doh... thread apply all bt I always type: t a a bt and typo'ed the expansion. Thanks, here is what comes out: (gdb) p tstate->interp value has been optimized out (gdb) thread apply all bt You missed the first one: "p tstate". -- ___ 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: Python code error in F39, but not in F38
On Wed Nov22'23 09:49:49PM, Barry Scott wrote: > From: Barry Scott > Date: Wed, 22 Nov 2023 21:49:49 + > To: Community support for Fedora users > CC: Ranjan Maitra > Reply-To: Community support for Fedora users > Subject: Re: Python code error in F39, but not in F38 > > > > > On 22 Nov 2023, at 21:32, Barry Scott wrote: > > > >> Any suggestions as to what is going wrong here? > > > > At this point you need get more information. > > > > What do the folllowing GDB commands print? > > > > p tstate > > p tstate->interp > > thread allow all bt > Doh... > > thread apply all bt > > I always type: > t a a bt > > and typo'ed the expansion. Thanks, here is what comes out: (gdb) p tstate->interp value has been optimized out (gdb) thread apply all bt Thread 1 (Thread 0x77ec7740 (LWP 387946) "python"): #0 0x779e4b5b in _PyInterpreterState_GET () at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118 #1 get_state () at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:866 #2 _PyObject_Free (ctx=, p=0x56d898a0) at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:1850 #3 0x7fff9e5e292f in sip_api_free (mem=) at /usr/src/debug/sip-4.19.25-9.fc39.x86_64/siplib/siplib.c:2239 #4 sipOMFinalise (om=0x7fff9e5ff9a0 ) at /usr/src/debug/sip-4.19.25-9.fc39.x86_64/susr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pylifecycle.c:1977 #8 0x77ab6337 in Py_RunMain () at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:691 #9 0x77a7185c in Py_BytesMain (argc=, argv=) at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:743 #10 0x7764614a in __libc_start_call_main (main=main@entry=0x5160 --Type for more, q to quit, c to continue without paging-- , argc=argc@entry=4, argv=argv@entry=0x7fffdfd8) at ../sysdeps/nptl/libc_start_call_main.h:58 #11 0x7764620b in __libc_start_main_impl (main=0x5160 , argc=4, argv=0x7fffdfd8, init=, fini=, rtld_fini=, stack_end=0x7fffdfc8) at ../csu/libc-start.c:360 #12 0x5095 in _start () (gdb) Many thanks and best wishes, Ranjan -- ___ 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: Python code error in F39, but not in F38
> On 22 Nov 2023, at 21:32, Barry Scott wrote: > >> Any suggestions as to what is going wrong here? > > At this point you need get more information. > > What do the folllowing GDB commands print? > > p tstate > p tstate->interp > thread allow all bt Doh... thread apply all bt I always type: t a a bt and typo'ed the expansion. Barry-- ___ 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: Python code error in F39, but not in F38
> On 22 Nov 2023, at 20:16, Ranjan Maitra via users > wrote: > > Thanks very much for this for explaining how to run gdb on a python script! > On Python 3.12 (Fedora 39), I get, at the very end: > > Thread 1 "python" received signal SIGSEGV, Segmentation fault. > 0x779e4b5b in _PyInterpreterState_GET () > at > /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118 > 118 return tstate->interp; > (gdb) > > On Python 3.11 (Fedora 38), I get, at the very end: > > [Inferior 1 (process 199650) exited normally] > (gdb) > > Any suggestions as to what is going wrong here? At this point you need get more information. What do the folllowing GDB commands print? p tstate p tstate->interp thread allow all bt Barry -- ___ 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: Python code error in F39, but not in F38
On Tue Nov21'23 05:25:35PM, Samuel Sieb wrote: > From: Samuel Sieb > Date: Tue, 21 Nov 2023 17:25:35 -0800 > To: users@lists.fedoraproject.org > Reply-To: Community support for Fedora users > Subject: Re: Python code error in F39, but not in F38 > > On 11/19/23 10:01, Ranjan Maitra via users wrote: > > I tried: > > > > $ gdb python "./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7" > > (gdb) > > $ gdb python > (gdb) run ./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7 > -- Thanks very much for this for explaining how to run gdb on a python script! On Python 3.12 (Fedora 39), I get, at the very end: Thread 1 "python" received signal SIGSEGV, Segmentation fault. 0x779e4b5b in _PyInterpreterState_GET () at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118 118 return tstate->interp; (gdb) On Python 3.11 (Fedora 38), I get, at the very end: [Inferior 1 (process 199650) exited normally] (gdb) Any suggestions as to what is going wrong here? Many thanks and best wishes, Ranjan > ___ > 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: Python code error in F39, but not in F38
> On 22 Nov 2023, at 16:14, Ranjan Maitra via users > wrote: > > Thanks! Interesting, I wonder if that is also what has caused tensorflow to > not go up to 3.12 for now. Complex packages usually take a while to port to a new python is released. All the python packages that fedora ships have been ported to python 3.12. Why a crash in 3.12 and not 3.11? Because bugs can be tripped up on compiler changes. FYI the fortran issues do not effect python 3.12 itself, they effected packages in the scientific python world like numpy, pandas etc. But due to heroic folk they all made it to 3.12. Barry -- ___ 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: Python code error in F39, but not in F38
On Wed Nov22'23 08:12:58AM, George N. White III wrote: > From: "George N. White III" > Date: Wed, 22 Nov 2023 08:12:58 -0400 > To: Community support for Fedora users > Reply-To: Community support for Fedora users > Subject: Re: Python code error in F39, but not in F38 > > On Sun, Nov 19, 2023 at 2:02 PM Ranjan Maitra via users < > users@lists.fedoraproject.org> wrote: > > > On Sun Nov19'23 05:35:19PM, Barry wrote: > > > From: Barry > > > Date: Sun, 19 Nov 2023 17:35:19 + > > > To: Community support for Fedora users > > > > > > > > > > > > > > > It is possible that there is a bug in the code itself, but nothing > > above > > > > points to my created code. > > > > > > > > Any suggestions? Or is this a bug? > > > > > > Are you using C extensions in your code? If so I would suspect them for > > corrupting python. I think you can get into gdb inside the core file with > > coredumpctl debug. > > > > The python code calls a shared object library that is written in C. But > > why does this core dump only happen in F39 (python 3.12) and not with > > F38 (python 3.11)? > > > > There were some big changes in 3.12 (driven by the need to support Fortran > on > Windows and macOS by replacing very old gfortran version with flang-new). > I havrn't > had time to look at what is being used in linux, but you could get a quick > overview from > ldd. See: < > https://discuss.python.org/t/why-scipy-builds-for-python-3-12-on-windows-are-a-minor-miracle-especially-in-conda-forge/38270 > > > > There is also new build system, so a lot of work getting everything working > in 3.12. Meanwhile > you can run 3.11 stuff using python environments. > Thanks! Interesting, I wonder if that is also what has caused tensorflow to not go up to 3.12 for now. From what I read somewhere (I think on an archived tensorflow mailing list or something) the linux builds are up, but not the MacO$ and Windoze builds. Both of which, if I had my way, should never have been allowed even indirectly into any professional environment. Ranjan -- ___ 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: Intel NUC 12 Enthusiast Kit with Arc 770 and fedora 39
No sure this is what you're looking for, but: you can edit the kernel parameters in the boot entry. Select a boot entry from a list and press 'e' to edit. Then 'ctrl+x' to execute. That way, you can have a custom kernel option set while running the Fedora installation ISO. If that would help with the freezing during Anaconda installation, you should be halfway there. Then after installation is finished, on the new system, edit `/etc/default/grub`, which is used when a new boot entry is added, which is usually done by some Post scriptlet of the kernel, when you (re-)install / update the kernel. I did this in the past to solve different issues requiring edit of kernel parameters. e.g: echo "GRUB_CMDLINE_LINUX=\"intel_idle.max_cstate=2 i915.enable_psr=0 i915.enable_fbc=0\"" >> /etc/default/grub For example the settings in the /etc/default/grub I use, are: GRUB_TIMEOUT=1 GRUB_DISABLE_UUID=true GRUB_ENABLE_BLSCFG=true Hope this helps. Michal -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Tue, Nov 21, 2023 at 12:13 PM Patrick O'Callaghan wrote: > > On Tue, 2023-11-21 at 10:08 +0100, Gianluca Cecchi wrote: > > BTW: I have still to understand if the system will use both graphics > > cards > > (which one is primary in this case?) or if the onboard one will be > > disabled > > if using a discrete card on the Nuc. > > I've no idea what will happen with a NUC, but in my experience Fedora > will use the discrete card in preference to the IGP, unless it's > blacklisted in the boot line. > > There's a package called switcheroo-control which allows you to select > which GPU to use for specific apps, though personally I haven't had > much luck with it. > > 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 -- ___ 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: Python code error in F39, but not in F38
On Sun, Nov 19, 2023 at 2:02 PM Ranjan Maitra via users < users@lists.fedoraproject.org> wrote: > On Sun Nov19'23 05:35:19PM, Barry wrote: > > From: Barry > > Date: Sun, 19 Nov 2023 17:35:19 + > > To: Community support for Fedora users > > > > > > > > > > > It is possible that there is a bug in the code itself, but nothing > above > > > points to my created code. > > > > > > Any suggestions? Or is this a bug? > > > > Are you using C extensions in your code? If so I would suspect them for > corrupting python. I think you can get into gdb inside the core file with > coredumpctl debug. > > The python code calls a shared object library that is written in C. But > why does this core dump only happen in F39 (python 3.12) and not with > F38 (python 3.11)? > There were some big changes in 3.12 (driven by the need to support Fortran on Windows and macOS by replacing very old gfortran version with flang-new). I havrn't had time to look at what is being used in linux, but you could get a quick overview from ldd. See: < https://discuss.python.org/t/why-scipy-builds-for-python-3-12-on-windows-are-a-minor-miracle-especially-in-conda-forge/38270 > There is also new build system, so a lot of work getting everything working in 3.12. Meanwhile you can run 3.11 stuff using python environments. -- 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
