July 2023 - openSUSE Project - openSUSE Mailing Lists

Intel Wireless
by Chuck Payne 26 Jul '23

26 Jul '23

Guys, I am trying to get a Beelink N100 up and running, it uses Intel wireless. Which seems to be a nightmare on most distro. I have installed kernel-firmware-iwlwifi-20230707-1.1.noarch, and the os see the device 3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000 link/ether 6e:86:90:2b:64:f8 brd ff:ff:ff:ff:ff:ff permaddr a4:f9:33:9b:46:19 altname wlp0s20f3 But every times it's tries to connect to the network I get a kernel panic 5.528349] iwlwifi 0000:00:14.3: FW error in SYNC CMD STA_CONFIG_CMD [ 75.528353] CPU: 2 PID: 39 Comm: kworker/u8:1 Tainted: G W 6.4.4-1-default #1 openSUSE Tumbleweed 84c714c4274a8c7b58b7c0b8a39180dfcb953157 [ 75.528356] Hardware name: AZW MINI S/MINI S, BIOS ADLNV104 02/06/2023 [ 75.528358] Workqueue: phy1 ieee80211_iface_work [mac80211] [ 75.528418] Call Trace: [ 75.528420] <TASK> [ 75.528423] dump_stack_lvl+0x47/0x60 [ 75.528428] iwl_trans_txq_send_hcmd+0x310/0x420 [iwlwifi 1cb8d45c26bc31474d01f13f34c96edb41b6977a] [ 75.528452] ? __pfx_autoremove_wake_function+0x10/0x10 [ 75.528456] iwl_trans_send_cmd+0x66/0x100 [iwlwifi 1cb8d45c26bc31474d01f13f34c96edb41b6977a] [ 75.528477] iwl_mvm_send_cmd_pdu+0x62/0xb0 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528506] iwl_mvm_mld_cfg_sta.isra.0+0x18f/0x210 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528530] iwl_mvm_mld_update_sta+0x73/0xe0 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528550] iwl_mvm_mac_sta_state_common+0x16a/0x970 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528573] iwl_mvm_mld_mac_sta_state+0x48/0x70 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528593] ? __pfx_iwl_mvm_mld_add_sta+0x10/0x10 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528613] ? __pfx_iwl_mvm_mld_update_sta+0x10/0x10 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528633] ? __pfx_iwl_mvm_mld_rm_sta+0x10/0x10 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528652] ? __pfx_iwl_mvm_mld_mac_ctxt_changed+0x10/0x10 [iwlmvm e7a3f15e1964004e821fd2b81fe8415ee32141f5] [ 75.528673] drv_sta_state+0x85/0x540 [mac80211 080e5f105b808bcae3a34e034be591cb7b98b76a] [ 75.528721] sta_info_move_state+0x1c2/0x290 [mac80211 080e5f105b808bcae3a34e034be591cb7b98b76a] [ 75.528771] ieee80211_rx_mgmt_assoc_resp+0xc17/0x1ea0 [mac80211 080e5f105b808bcae3a34e034be591cb7b98b76a] [ 75.528841] ieee80211_sta_rx_queued_mgmt+0xa0/0x910 [mac80211 080e5f105b808bcae3a34e034be591cb7b98b76a] [ 75.528903] ? __switch_to_asm+0x3e/0x80 [ 75.528907] ? finish_task_switch.isra.0+0x94/0x2f0 [ 75.528909] ? __schedule+0x3e6/0x14b0 [ 75.528912] ieee80211_iface_work+0x305/0x450 [mac80211 080e5f105b808bcae3a34e034be591cb7b98b76a] [ 75.528969] process_one_work+0x207/0x420 [ 75.528972] worker_thread+0x4e/0x3b0 [ 75.528975] ? __pfx_worker_thread+0x10/0x10 [ 75.528978] kthread+0xe5/0x120 [ 75.528980] ? __pfx_kthread+0x10/0x10 [ 75.528983] ret_from_fork+0x29/0x50 [ 75.528986] </TASK> [ 75.528988] iwlwifi 0000:00:14.3: STA_CONFIG_CMD send failed, ret=0xfffffffb [ 75.528990] iwlwifi 0000:00:14.3: Failed to update sta link 0 [ 75.528993] wlo1: failed to move station 24:4b:fe:41:09:ec to desired state [ 75.528997] iwlwifi 0000:00:14.3: Failed to trigger RX queues sync (-5) [ 75.964040] iwlwifi 0000:00:14.3: Couldn't send the SESSION_PROTECTION_CMD: -5 [ 75.964046] iwlwifi 0000:00:14.3: Failed to send flush command (-5) [ 75.964094] iwlwifi 0000:00:14.3: Failed to send MAC_CONFIG_CMD (action:2): -5 [ 75.964096] iwlwifi 0000:00:14.3: failed to update MAC a4:f9:33:9b:46:19 [ 75.964102] iwlwifi 0000:00:14.3: Failed to send LINK_CONFIG_CMD (action:2): -5 [ 75.964107] iwlwifi 0000:00:14.3: PHY ctxt cmd error. ret=-5 [ 75.983293] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination [ 76.080755] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f [ 76.080802] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 76.080853] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90 [ 76.080905] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10 [ 76.081977] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 I am running the latest tumbleweed snapshot # VERSION="20230724" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20230724" I am not sure which Intel wireless it's using, the docs only state Built-in Wifi 6 802.11ax. Is there something I am missing with the Intel wireless? For now I am using a generic Realtek USB so I have some wifi. -- Terror PUP a.k.a Chuck "PUP" Payne ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- Terrorpup openSUSE Ambassador/openSUSE Member skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 openSUSE Community Member since 2008.

3 2

Community Meeting: Week 29 & ALP Architecture Meeting
by ddemaio openSUSE 17 Jul '23

17 Jul '23

Hi all, The ALP meeting will be on Tuesday. It starts at 14:30 UTC. If there nothing to discuss this week, we can decide to cut the ALP meeting short. Next week and going forward from there, Richard should be able to expand more of the discussion. I, however, will not be around for the next couple weeks starting next week since I'm off on a road trip. Meeting 2 is schedule for Thursdays at 19:00 UTC. Again, after this week, I won't be there, but this week we will either go over enhancing the documentation for packaging or further expand on the videos discussion. Read last week's info or get meeting notes at https://etherpad.opensuse.org/p/weeklymeeting Meetings takes place in https://meet.opensuse.org/meeting You can see a list of the items where project's need help at https://etherpad.opensuse.org/p/help v/r Doug

1 0

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by openSUSE Meeting Reminder 15 Jul '23

15 Jul '23

Hello all, The biweekly board conf call will be held in two days at 13:00 Europe/Berlin time (CET = UTC+1) Meeting will be in the regular Board Meeting Room https://meet.opensuse.org/OSBoard Current Topics: https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting Board Members: If you cannot participate, please advise by replying to this mail.

1 0

Transparency and decision making in the openSUSE community
by Günter Dachs 14 Jul '23

14 Jul '23

28 78

SUSE's announcement around choice this morning
by Gerald Pfeifer 13 Jul '23

13 Jul '23

Hi folks, SUSE just issued a press release on an exciting development around Linux which Dirk-Peter van Leeuwen (or simply DP, CEO of SUSE) complemented with a blog: https://www.suse.com/news/SUSE-Preserves-Choice-in-Enterprise-Linux/ https://www.suse.com/c/at-suse-we-make-choice-happen/ DP and Thomas (Di Giacomo, who many of you know) are in Asia right now engaging with customers, yet offered to respond to questions you may have. So, any questions of yours related to this announcement, simply drop me a note, indicate whether you want to remain anonymous or not, and I'll compile a list and share it with them my Friday night (CEST). As always I am available, too, directly and here. Gerald -- Dr. Gerald Pfeifer <gp(a)suse.com>, CTO @SUSE + chair @openSUSE

6 7

FAQ to help with rumors from spreading
by ddemaio openSUSE 11 Jul '23

11 Jul '23

Hi all, We made an faq should anyone start asking questions about the RHEL fork, confuse things or make up things. We don't want rumors to spread, so please provide this link should you see any confusion. https://en.opensuse.org/openSUSE:Faq v/r Doug

2 1

Community Meeting: Week 28 & ALP Architecture Meeting
by ddemaio 10 Jul '23

10 Jul '23

Hi all, The ALP meeting will be on Tuesday. It starts at 14:30 UTC. There is nothing that else that has been brought up other than https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Linarite We will need a little bit more information about this but know it's a similar idea to https://en.opensuse.org/openSUSE:ALP/Workgroups/GrassyKnoll Feel free to present if you have an idea with regard to what was presented here - https://youtu.be/-y2ewBG62J4 Meeting 2 is schedule for Thursdays at 19:00 UTC, which we would like to further expand on the videos discussed two weeks ago. Read last week's info or get meeting notes at https://etherpad.opensuse.org/p/weeklymeeting Neeting takes place in https://meet.opensuse.org/meeting You can see a list of the items where project's need help at https://etherpad.opensuse.org/p/help v/r Doug

1 0

Transparency and decision making in the openSUSE community
by Günter Dachs 06 Jul '23

06 Jul '23

Dear community, I would like to inform myself about the decision making in the openSUSE community. And probably start a discussion about it as well. A couple of days ago I posted a reminder on reddit that pride month is over and that the mods shouldn't forget to update the logo to the regular one. When you hover the mouse over the logo it changes to the one with the pride flag. Which is great for pride month. But I don't see any reason to have this permanently. To my knowledge the logo was always a temporary thing that is changed at special occasions and holidays. To my knowledge each time this occasion is over we switch back to the default logo. Shortly after my post got removed. With no explanation and no reason. Upon asking one of the mods in private he told me I should generally message the mods and not make a post and that this particular person didn't remove it and I need to contact the mods in general. I have to say that I actually wasn't aware that I can message all mods of a subreddit. And I agree that this would have been the proper way. The next time I will definitely do it. But I don't see this as a justification to remove my post. I continued to message the mods in general and then a longer discussion with one of them started. Where they explained that the community had several posts that were about the pride flag in the past and that they just removed my post because of negative experiences with posts regarding the flag in the past. I don't think it's fair to remove posts from individuals just because another person did a post that touched the topic before but was using rules breaking content. I feel like openSUSE is a community and we should listen and respect each other. Not censor people quietly. After several messages back and forth I was pointing out again that I just wanted to highlight that pride month is over and remind the mods to switch back, since they said that last time they forgot this for one year.. I was curious why they are not doing it now and I was told they don't tolerate the intolerant. In the whole situation nobody was intolerant :-) I have nothing against the usage of the pride flag during pride month! In the whole conversation I felt like stuff is put into my mouth that I didn't say at all. Just because you had certain experiences with some people you don't need to judge who starts a certain topic by the same book. I was pretty disappointed with the whole situation and it made me think: If they have so many people in the community who speak about the logo change. Why do they resist it in pretense of defending something/someone? Nobody is attacking LGBTIQ+ people. OpenSUSE is a community distribution and it seems the community isn't heard? Their posts removed if they don't fit the opinion of some mods? Shouldn't the mods follow concrete rules and guidelines and not act arbitrary? OpenSUSE is the makers distribution. I offered in the conversation several times to volunteer as a mod and change the logo myself. I got no response to that. I would like to know who is deciding what the official community representation on reddit for our project should look like. In my opinion it should be the openSUSE community. I didn't find any poll, discussion or anything like that regarding using certain logos. But now I got the impression that several people asked for a logo change and were silenced. Is the what you understand as open community work? I propose to create a poll on each social media platform and use on each platform the result of the poll. Or to ask the openSUSE contributors, members or general community of their opinion. I dislike that a handful of people make the decision and ignore, and even harrass other members. The slogan is that openSUSE is the makers distribution. But it looks like that right you are not allowed to make a change that you would like to see. openSUSE is an open welcoming community for everybody. And to reflect this we need to respect everybody. And use our neutral logos and artwork. To increase our respect to everybody, we can set signs during certain evens/periods. Using pride flags during pride month. Using the cross during Christmas. This artwork is extra work. And needs to be contributed by the community. So if someone makes it we should take it, if it is not part of a damaging or forbidden group/ideology (like Nazism). Mods need to be neutral and defend the code of conduct and rules of the specific social media platform. Not decide what they like and don't like and remove accordingly. Everything else is just pretense. Power in the hands of a view. Who don't want to listen and respect the opinion of others who have different ideas about the project. Yours, Günter

2 1

Updating English wiki
by Natasha Ament 06 Jul '23

06 Jul '23

Hi, During my translation work I found some of the English wiki's not being up to spec some of the pages are however locked. Is it possible to grant me access to those as well? Kind regards, Natasha

2 1

openSUSE Board meeting minutes 2023-07-03
by Maurizio Galli 05 Jul '23

05 Jul '23

= Board Meeting Monday 2023-07-03 13:00 CEST = * Present: Doug, Gerald, Mau, Patrick, Gertjan, Neal * Excused: * Missed: * This week's report to be sent by: Mau * Guests: == Missing meeting minutes == * Board meeting of 19/06/2023 was interrupted due to technical issues. Minutes were not released as topics needed to be readdressed. * Added missing minutes from April to June to the Wiki == openSUSE promotions after recent Red Hat announcements == * Received a question/concerns on a post promoting openSUSE after recent Red Hat announcements * Looked at that specific post and feel that it was not crossing any lines * However the general agreement is to focus on openSUSE's virtues and advantages in general, reason why openSUSE social media accounts did not re-share memes on this topic in circulation * AI Gertjan will respond to original reporter == Formal Complaint Process == * Doug proposed the following: ** Create a formal process for people. ** Formal complaint needs to be filed at https://code.opensuse.org/project/coc/new_issue Either public or private ** Submitters are asked to: *** List all the facts and reasoning for the complaint *** Provide context, text and screenshots if neccessary *** Provide a self reflective paragraph of any interactions with the person violating the code of conduct *** Provide a potential course of action to resolve the situation * Specific discussions around: ** Do we use a single central place? General consensus for that. ** How do we cover complaints against a board members for example? Could such a thing be included in the above procedure? Yes, by means of reporting via a proxy (i.e board member of your choice). * Practical example - the GCC project asks the following in its CoC complaints process: ** Your contact info (so we can get in touch with you if we need to follow up) ** Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well. ** When and where the incident occurred. Please be as specific as possible. ** Your account of what occurred. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link. ** Any extra context you believe existed for the incident. ** If you believe this incident is ongoing. ** Any other information you believe we should have.) VOTE: Who is in favor of putting a formal complaint process deascribed above ? AGREED (+6, 0, -0): Formal complaint process as described to be implemented and Code of Conduct page needs to be updated to reflect this. AI: Implementation done by Doug, Neal, Mau == AI Language Models using openSUSE forums == * Should this be a topic of discussion based on language training models (reddit's recent discussion) * There are potential legal and financial repercussions on this topic. Board Meeting ends at 14:00 CEST.

1 0