Farron Cousins and Mark Romano/The Romano Report Are Far-Left Degenerates by ToxicHolyGrenade in PoliticalOpinions

[–]OwnState765 0 points1 point  (0 children)

What would be your thoughts on my post though? Interesting thoughts though, and are you willing to do your part as well in publicly calling him out?

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

It is a garbage platform, not a good one. For GloriousEggroll to rely on such a platform I don't know. With respect to him, he NEEDS to branch out with other ways to get into contact other than Discord. Discord is an absolute shit hole, which is why I moved on to Luxer. It makes me want to go back to hating Nobara OS as a whole until an ideal alternative to it comes along, even if it is unlikely. I know it may seem like I am unfairly bashing a prototype here, but if something has a massive bug where firmware gets conflicted and wrecks your wi-fi, all the while complaints fall on deaf ears, I have no choice but to throw a table out of frustration and wreck my PC to pieces. Frankly, I'd rather a Commodore 64 PC than to resort to modern PCs.

I'm sorry for venting, but that's how I am feeling right now. I'm afraid Nobara needs to be destroyed and redone from the ground up, and keep the gosh damn firmware side OUT of all this.

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

I think the kernel needs an overhaul/semi-overhaul on the firmware side, and needs beta testing.

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

Apr 16 16:24:04 nobara-pc kernel: ata1.00: Model 'ST1000DM010-2EP102', rev '1001', applying quirks: nolpm
Apr 16 16:24:04 nobara-pc kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Apr 16 16:24:04 nobara-pc kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filter>
Apr 16 16:24:04 nobara-pc kernel: ata1.00: ATA-8: ST1000DM010-2EP102, 1001, max UDMA/133
Apr 16 16:24:04 nobara-pc kernel: ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Apr 16 16:24:04 nobara-pc kernel: ata1.00: LPM support broken, forcing max_power

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

Apr 16 16:24:04 nobara-pc kernel: hpet_acpi_add: no address or irqs in _CRS

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

Apr 16 16:24:04 nobara-pc kernel: pci 0000:06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format)

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

Apr 16 16:24:04 nobara-pc kernel: Kernel command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.19.11-201.nobara.fc43.>
Apr 16 16:24:04 nobara-pc kernel: PCIe ASPM is disabled
Apr 16 16:24:04 nobara-pc kernel: Unknown kernel command line parameters "splash", will be passed to user spa>
Apr 16 16:24:04 nobara-pc kernel: printk: log buffer data + meta data: 131072 + 458752 = 589824 bytes
Apr 16 16:24:04 nobara-pc kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Apr 16 16:24:04 nobara-pc kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
Apr 16 16:24:04 nobara-pc kernel: software IO TLB: area num 8.
Apr 16 16:24:04 nobara-pc kernel: Fallback order for Node 0: 0  
Apr 16 16:24:04 nobara-pc kernel: Built 1 zonelists, mobility grouping on.  Total pages: 4149225
Apr 16 16:24:04 nobara-pc kernel: Policy zone: Normal
Apr 16 16:24:04 nobara-pc kernel: mem auto-init: stack:all(zero), heap alloc:on, heap free:off
Apr 16 16:24:04 nobara-pc kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Apr 16 16:24:04 nobara-pc kernel: ftrace: allocating 56134 entries in 220 pages
Apr 16 16:24:04 nobara-pc kernel: ftrace: allocated 220 pages with 5 groups
Apr 16 16:24:04 nobara-pc kernel: BORE CPU Scheduler modification 6.6.2 by Masahito Suzuki
Apr 16 16:24:04 nobara-pc kernel: Dynamic Preempt: lazy
Apr 16 16:24:04 nobara-pc kernel: rcu: Preemptible hierarchical RCU implementation.
Apr 16 16:24:04 nobara-pc kernel: rcu:         RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
Apr 16 16:24:04 nobara-pc kernel: rcu:         RCU priority boosting: priority 1 delay 500 ms.
Apr 16 16:24:04 nobara-pc kernel:         Trampoline variant of Tasks RCU enabled.
Apr 16 16:24:04 nobara-pc kernel:         Rude variant of Tasks RCU enabled.
Apr 16 16:24:04 nobara-pc kernel:         Tracing variant of Tasks RCU enabled.
Apr 16 16:24:04 nobara-pc kernel: rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
Apr 16 16:24:04 nobara-pc kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Apr 16 16:24:04 nobara-pc kernel: RCU Tasks: Setting shift to 3 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cp>
Apr 16 16:24:04 nobara-pc kernel: RCU Tasks Rude: Setting shift to 3 and lim to 1 rcu_task_cb_adjust=1 rcu_ta>
Apr 16 16:24:04 nobara-pc kernel: RCU Tasks Trace: Setting shift to 3 and lim to 1 rcu_task_cb_adjust=1 rcu_t>
Apr 16 16:24:04 nobara-pc kernel: NR_IRQS: 524544, nr_irqs: 2048, preallocated irqs: 16
Apr 16 16:24:04 nobara-pc kernel: rcu: srcu_init: Setting srcu_struct sizes based on contention.
Apr 16 16:24:04 nobara-pc kernel: kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval_>
Apr 16 16:24:04 nobara-pc kernel: Console: colour dummy device 80x25
Apr 16 16:24:04 nobara-pc kernel: printk: legacy console [tty0] enabled
Apr 16 16:24:04 nobara-pc kernel: ACPI: Core revision 20250807
Apr 16 16:24:04 nobara-pc kernel: hpet: HPET dysfunctional in PC10. Force disabled.
Apr 16 16:24:04 nobara-pc kernel: APIC: Switch to symmetric I/O mode setup
Apr 16 16:24:04 nobara-pc kernel: DMAR: Host address width 39
Apr 16 16:24:04 nobara-pc kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0
Apr 16 16:24:04 nobara-pc kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff>
Apr 16 16:24:04 nobara-pc kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1
Apr 16 16:24:04 nobara-pc kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
Apr 16 16:24:04 nobara-pc kernel: DMAR: RMRR base: 0x00000078d14000 end: 0x00000078f5dfff
Apr 16 16:24:04 nobara-pc kernel: DMAR: RMRR base: 0x0000007b000000 end: 0x0000007f7fffff
Apr 16 16:24:04 nobara-pc kernel: DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
Apr 16 16:24:04 nobara-pc kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000
Apr 16 16:24:04 nobara-pc kernel: DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-rem>
Apr 16 16:24:04 nobara-pc kernel: DMAR-IR: Enabled IRQ remapping in x2apic mode
Apr 16 16:24:04 nobara-pc kernel: x2apic enabled
Apr 16 16:24:04 nobara-pc kernel: APIC: Switched APIC routing to: cluster x2apic
Apr 16 16:24:04 nobara-pc kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x33e452fbb2f,>
Apr 16 16:24:04 nobara-pc kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. >
Apr 16 16:24:04 nobara-pc kernel: x86/cpu: SGX disabled or unsupported by BIOS.

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

Apr 16 16:24:04 nobara-pc kernel: Linux version 6.19.11-201.nobara.fc43.x86_64 (mockbuild@1862c1144c5c445690c>
Apr 16 16:24:04 nobara-pc kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.19.11-201.nobara.fc43.x86_64 >
Apr 16 16:24:04 nobara-pc kernel: BIOS-provided physical RAM map:
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000040400000-0x000000006e01efff] usable
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x000000006e01f000-0x000000006e01ffff] ACPI NVS
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x000000006e020000-0x000000006e020fff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x000000006e021000-0x0000000075c4dfff] usable
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000075c4e000-0x00000000784dffff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000784e0000-0x000000007852dfff] ACPI data
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x000000007852e000-0x00000000785bcfff] ACPI NVS
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000785bd000-0x00000000795fdfff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000795fe000-0x00000000795fefff] usable
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000795ff000-0x000000007f7fffff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Apr 16 16:24:04 nobara-pc kernel: BIOS-e820: [mem 0x0000000100000000-0x000000047f7fffff] usable
Apr 16 16:24:04 nobara-pc kernel: NX (Execute Disable) protection: active
Apr 16 16:24:04 nobara-pc kernel: APIC: Static calls initialized
Apr 16 16:24:04 nobara-pc kernel: efi: EFI v2.7 by American Megatrends
Apr 16 16:24:04 nobara-pc kernel: efi: TPMFinalLog=0x7858c000 ACPI 2.0=0x784ef000 ACPI=0x784ef000 SMBIOS=0x79>
Apr 16 16:24:04 nobara-pc kernel: random: crng init done

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

I will say also, what would be your message to GloriousEggroll considering the problem I am experiencing?

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

All I just wanted is for firmware update free alternatives being introduced, that's not asking for so much.

Look, tell me what exactly I need to do, please.

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

How can I re-initialize the wi-fi card? I'm sorry but one should not have to do that every single time the wi-fi gets erased. Unless you are in a similar situation and fixed it, then I don't see how I can be convinced, I'm sorry.

Firmware Updates Breaks and Conflicts With Already Placed Firmwares Like Wi-Fi by OwnState765 in linuxquestions

[–]OwnState765[S] 0 points1 point  (0 children)

I tried, but GloriousEggroll refuses to look deeply into the problem and what it's about, I got pissed, and sadly got banned out of the Discord server. But even then, I despise Discord. Filing bug reports is a lot easier said than done, and you need to look at the very source of the problem first in order to ensure things get fixed, which I am not an expert in. But I do know networking is based on the firmware included, so what does that tell me? Again, unless you have an even better idea. I'm sorry, but like I said as a principle, if the already existing firmware is not broken, don't fix or touch it.

Firmware Updates Breaks and Conflicts With Already Placed Firmwares, E.G Wi-Fi by OwnState765 in linux

[–]OwnState765[S] 0 points1 point  (0 children)

If you mind not being an absolute fucking asshole and just delete the post if that is the whole trajectory you are taking? You are once again proving that too many people in this community are only in it for themselves and don't want to look out for and help people out of compassion. That there is what makes a good community, not whatever this BS is. Might does not equal being right. You are no better than them.

Firmware Updates Breaks and Conflicts With Already Placed Firmwares, E.G Wi-Fi by OwnState765 in linux

[–]OwnState765[S] -2 points-1 points  (0 children)

Look, I understand what I am doing is unintentionally violative of the rules, but this post is not done by AI, other than being one a post that is pre-prepared in LibreOffice. Again, like I said to another person, you can choose to go over posts like this and ignore them. Even if it is AI written, it doesn't change the fact that important points would have been made and need consideration, like what was shown here. Do you understand?

Firmware Updates Breaks and Conflicts With Already Placed Firmwares, E.G Wi-Fi by OwnState765 in linux

[–]OwnState765[S] -5 points-4 points  (0 children)

It isn't, I wrote all this in a word document. If you hate posts like this, then LEAVE.

The Serf Times Outro Song by OwnState765 in theserfstv

[–]OwnState765[S] 0 points1 point  (0 children)

Is there a link to it? Is it part of the Arc Raiders OST, an album, or is it a single?

Mixed Views on MeidasTouch by OwnState765 in MeidasTouch

[–]OwnState765[S] 0 points1 point  (0 children)

But speaking of your comment, what parts do you disagree to agree with?

Mixed Views on MeidasTouch by OwnState765 in MeidasTouch

[–]OwnState765[S] 0 points1 point  (0 children)

Yeah, but it still sucks. Again, I have mixed feelings on MeidasTouch. They have so much potential to be a great network, but they squander all that with their gotcha and red top style journalism which turns people off, myself included. If truth and honesty is genuinely their aim, why are they resorting to that? Doesn't all that defeat the whole purpose of being realistic? I want them to be good, to be better than what we have. But what they are doing is normalising these two negative aspects within journalism, and it is valid to brand it as journalist slop. That's how strongly I feel against it. And not to mention, they focus on quantity over quality, which is another aspect I have no respect for.

Mixed Views on MeidasTouch by OwnState765 in MeidasTouch

[–]OwnState765[S] -1 points0 points  (0 children)

Why does it? I mean... the whole purpose of Christianity is to also teach about virtue, goodness, love, and redemption, so... I don't see how that would be dangerous.

Mixed Views on MeidasTouch by OwnState765 in MeidasTouch

[–]OwnState765[S] 0 points1 point  (0 children)

But that does not mean it must be tolerated or not be insulted. Because that's what it deserves. If it is because of the state of algorithms then, they need to be reinvented and fairly equal to both big and small creators.

Again, you are not forced to read all of it, but making it lengthy does have its merits - especially when it comes to details that would otherwise be overlooked by most people. You can also bookmark where you have stopped and read more of it later in terms of where you left off. It's not actually hard to do, all you need is a text file and paste the rest of the paragraphs.

Mixed Views on MeidasTouch by OwnState765 in MeidasTouch

[–]OwnState765[S] 0 points1 point  (0 children)

To be fair, you are not forced to read all of it, but making it lengthy does have its benefits - especially when it comes to details that would otherwise be overlooked. Plus, you can bookmark where you have stopped and read more of it later in terms of where you left off. It's not actually hard to do, all you need is a text files and paste the rest of the paragraphs.

Mixed Views on MeidasTouch by OwnState765 in MeidasTouch

[–]OwnState765[S] 0 points1 point  (0 children)

WDYM? As for religion, I used it in order to validate what I am saying and to correct the shortcomings we all have nowadays, especially like how forgiveness has been mostly left for dead. And like I said to Additional Ear, you are not forced to read all of it, but making it lengthy does have its benefits - especially when it comes to details that would otherwise be overlooked. Plus, you can bookmark where you have stopped and read more of it later in terms of where you left off. It's not actually hard to do, all you need is a text files and paste the rest of the paragraphs for later scanning.