#archlinux32 | Logs for 2025-04-28

Back
[02:43:09] -!- jacobk has quit [Ping timeout: 276 seconds]
[07:13:15] -!- texus has joined #archlinux32
[07:14:58] -!- ssserpent has quit [Ping timeout: 245 seconds]
[10:37:28] -!- sL1pKn07 has quit [Ping timeout: 245 seconds]
[10:38:06] -!- lithium_pt has quit [Ping timeout: 272 seconds]
[11:13:34] -!- abouvier has quit [Ping timeout: 260 seconds]
[11:35:52] -!- abouvier has joined #archlinux32
[14:35:09] -!- titus_livius has joined #archlinux32
[14:38:42] -!- buildmaster has joined #archlinux32
[14:54:59] -!- jacobk has joined #archlinux32
[14:59:48] -!- zxrom has joined #archlinux32
[15:00:07] <zxrom> genirq Flags mismatch irq 9. 00000080 (b43) vs. 00002080 (acpi)
[15:00:15] <zxrom> Is this curable? Which way should I dig?
[15:00:58] <zxrom> b43-phy0 ERROR: Cannot request IRQ-9
[15:15:48] -!- drathir_tor has quit [Ping timeout: 264 seconds]
[15:17:11] -!- drathir_tor has joined #archlinux32
[15:42:14] -!- sL1pKn07 has joined #archlinux32
[15:56:40] -!- T`aZ has quit [Ping timeout: 272 seconds]
[15:57:59] -!- T`aZ has joined #archlinux32
[16:11:45] -!- jacobk has quit [Ping timeout: 276 seconds]
[16:16:44] <KillerWasp> zxrom: you mean fixable.
[16:18:19] <KillerWasp> seem you only must change the number value.
[16:22:58] <zxrom> KillerWasp, I don't know what to do. Wi-Fi doesn't work.
[16:25:06] <KillerWasp> https://www.webopedia.com
[16:25:08] <phrik> Title: What are IRQ Numbers? | Webopedia (at www.webopedia.com)
[16:25:29] <KillerWasp> like IRQ-9 don't have nothing by default. what device you're trying use?
[16:27:05] <KillerWasp> zxrom: https://bbs.archlinux.org
[16:27:06] <phrik> Title: Disabling irq #9 / Kernel & Hardware / Arch Linux Forums (at bbs.archlinux.org)
[16:27:13] <KillerWasp> if you don't use anything.
[16:28:17] <zxrom> Broadcom BCM4318
[16:28:35] <zxrom> cat /proc/interrupts
[16:28:58] <zxrom> 9: 13865 IO-APIC 21-fasteol acpi
[16:29:46] <zxrom> The error occurs when I try to turn on the wireless network.
[16:29:56] <KillerWasp> zxrom: the error appear from the kernel boot? You can continue or are stuck in kernel panic?
[16:30:02] <zxrom> It worked well on older kernels.
[16:30:14] <KillerWasp> oooh....
[16:30:44] <KillerWasp> that's explain much....
[16:31:17] <KillerWasp> I now want to kick the balls of the Kernel developers.
[16:31:37] <zxrom> The kernel does not crash. Work continues. I only see a log in the journal with a stack of calls.
[16:32:18] <zxrom> Where can I download packages with old kernels?
[16:32:39] <KillerWasp> zxrom: your only option is take the firmware of the old kernel that you know are work fine, and use in the new kernel. And maybe you must mess with the codes of C.
[16:33:03] <KillerWasp> zxrom: from https://kernel.org
[16:33:04] <phrik> Title: The Linux Kernel Archives (at kernel.org)
[16:33:36] <zxrom> I meant a ready compiled package. On this old laptop the kernel will be compiled for a day.
[16:33:53] <KillerWasp> i can foresee much pain in the future with this problem. 🙁
[16:34:08] <zxrom> Shit happens.
[16:34:23] <zxrom> I'm on the verge of removing ArchLinux32 from this laptop.
[16:34:53] <KillerWasp> zxrom: you know if arch64 work fine with the wifi?
[16:35:08] <zxrom> This is my mood because of this mistake.
[16:35:29] <KillerWasp> zxrom: not's a mistake, it's a conspiracy.
[16:35:34] <zxrom> I have never worked with aarch64
[16:36:52] <zxrom> Lately I've been increasingly looking at Linux as a piece of shit. After 10 years of using Arch as my main OS.
[16:37:29] <KillerWasp> I also have the same problem, and I'm using an old version of the kernel to be able to use the wifi without problem, and if I remember well, even if I use 64 bits the kernel returns the same problem with the wifi, as the only option is to use an old version of the kernel.
[16:37:50] <KillerWasp> zxrom: i'm agree with you. -_-U
[16:38:00] <zxrom> This laptop is only 32 bit.
[16:38:27] <KillerWasp> 😔
[16:38:33] <zxrom> Shit happens.
[16:39:47] <KillerWasp> With which you know that everything is intentional, it's not accidental. The reports about problems with the Wi-Fi were already made, many times, but they don't want to fix.
[16:41:20] <KillerWasp> The only way to fix it is to reversing the changes in the kernel codes on parts that they break.
[16:42:49] -!- Xogium has parted #archlinux32
[16:42:55] <KillerWasp> I would have done it for a long time, if I had a new machine to make changes in the kernel and test it, it requires many reset too.
[16:43:09] <zxrom> They want us to pay for new hardware and software, preferably every month.
[16:43:30] <KillerWasp> zxrom: yes. Like happen with the mobiles.
[16:44:32] <zxrom> I remember with nostalgia the times of Windows XP on this laptop, when everything worked without cataclysms. Once you installed the drivers and you are doing your business.
[16:45:33] <KillerWasp> zxrom: you can maintain the old kernel, you don't need make a update.
[16:48:55] <KillerWasp> If you have problems knowing what packages reverse, you can get a list of old versions from the pacman log, if you have problems with GLIBC you can install the force packages from chroot in another system like a Live CD, and if you have problems trying to get old packages you can get it from the source code with its PKGBUILD.
[16:49:33] -!- sL1pKn07 has quit [Ping timeout: 245 seconds]
[16:50:04] <KillerWasp> Once you have restored your old system with your old kernel, it's not touched again.
[16:50:22] <zxrom> It would be better to be able to just download old packages from the archive. Like downgrade linux.
[16:51:18] <KillerWasp> yes, it's a downgrade linux. Take care of this way because you can break easy all the system by the fault of glibc.
[16:53:18] <KillerWasp> I think that the Downgrade in glibc is the last thing you should do after all other packages, that way you will not have problems with glibc.
[16:55:29] <KillerWasp> you can begin with the packages from 'pacman -Si base'
[16:57:15] <KillerWasp> except for archlinux32-keyring, you can maintain updated.
[16:58:59] <zxrom> I'm trying to set up a network.
[17:00:05] <KillerWasp> zxrom: btw, you're use 'wpa_supplicant' for wi-fi?
[17:00:40] <KillerWasp> it's a wi-fi card in your machine?
[17:01:50] <KillerWasp> you say something about of laptop, i guess if where exist the problem.
[17:02:00] <zxrom> KillerWasp, Yes, but I already removed it and tried to install iwd. The problem is the same.
[17:03:22] <zxrom> Now I'm trying to figure out for the first time how to set up packet routing via cable on another machine.
[17:04:20] <KillerWasp> you can do with wpa_cli later of wpa_supplicant in memory. At least in my machine don't present the problem with the old kernel.
[17:05:37] <zxrom> Copy the old kernel to me on a file sharing site, please.
[17:05:44] <KillerWasp> lol
[17:05:50] <zxrom> What?
[17:06:01] <zxrom> This is the easiest way.
[17:06:42] <zxrom> /var/cache/pacman/pkg/linux*
[17:06:54] <KillerWasp> I thought it was a joke. You ask me all the binary, and with all the confidence in a murderous wasp. ;S
[17:06:58] <zxrom> I deleted them because I didn't have enough space on my laptop.
[17:07:42] <zxrom> What's the problem? There is a signature in a separate file.
[17:08:00] <KillerWasp> zxrom: what version you're need?
[17:10:42] <zxrom> KillerWasp, linux-lts 5.15.90-1.0
[17:11:22] <zxrom> linux-lts-headers too
[17:11:27] <KillerWasp> mmmm... near... i have linux-lts 5.15.44
[17:11:41] <KillerWasp> i guess also is useful
[17:11:48] <zxrom> ive me what is this
[17:12:02] <zxrom> give me what you have :D
[17:12:22] <zxrom> Shit!
[17:12:32] <KillerWasp> zxrom: ok. i only have linux-lts, and linux-firmware, but not the headers.
[17:12:56] <zxrom> linux-headers ?
[17:13:10] <KillerWasp> linux-api-headers
[17:13:41] <zxrom> Share what you have!
[17:17:31] <KillerWasp> wait
[17:17:39] <zxrom> OK
[20:10:37] -!- jacobk has joined #archlinux32
[21:34:30] -!- bill-auger has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
[22:44:56] -!- bill-auger has joined #archlinux32
[23:48:06] -!- sL1pKn07 has joined #archlinux32