#archlinux32 | Logs for 2025-04-25
Back
[00:48:45] -!- tippfehlr9 has joined #archlinux32
[00:49:22] -!- _phrik_ has joined #archlinux32
[00:49:22] -!- phrik has quit [Killed (NickServ (GHOST command used by _phrik_))]
[00:49:24] _phrik_ is now known as phrik
[00:50:44] -!- socksins1 has quit [Ping timeout: 276 seconds]
[00:51:22] -!- tippfehlr has quit [Ping timeout: 276 seconds]
[00:51:29] tippfehlr9 is now known as tippfehlr
[00:52:08] -!- socksins1 has joined #archlinux32
[01:03:05] -!- lithium_pt has joined #archlinux32
[01:03:43] -!- lithiumpt has quit [Ping timeout: 245 seconds]
[01:42:48] -!- drathir_tor has quit [Ping timeout: 264 seconds]
[01:44:30] -!- drathir_tor has joined #archlinux32
[05:29:39] -!- jacobk has quit [Ping timeout: 276 seconds]
[05:30:02] -!- jacobk has joined #archlinux32
[06:12:34] -!- ssserpent has quit [Ping timeout: 260 seconds]
[06:15:27] -!- srvntx has quit [Remote host closed the connection]
[06:15:51] -!- srvntx has joined #archlinux32
[09:04:17] -!- jacobk has quit [Ping timeout: 248 seconds]
[09:04:46] -!- jacobk has joined #archlinux32
[11:18:36] <KitsuWhooa> It's over https://lore.kernel.org
[11:18:36] <phrik> Title: Making sure you're not a bot! (at lore.kernel.org)
[11:28:40] <Xogium> well, that sucks
[11:28:58] <Xogium> I get where they come from, but still
[11:34:36] <Xogium> KitsuWhooa: oh by the way I *finally* got a system running on this bloody hardware I was trying to work on the other day
[11:34:53] <KitsuWhooa> what ended up being the problem?
[11:35:10] <Xogium> the rs232 console output was mangled... For a very dumb reason: vortex86ex doesn't like my rs232 to usb adapter from ftdi
[11:35:25] <KitsuWhooa> that sounds very odd
[11:35:53] <Xogium> yep it is, but once I took it out of there and switched to a real rs232 -- I got one on my tower, lucky me, everything just worked
[11:36:04] <Xogium> well, not quite as simple as that but at least I found out why it wouldn't boot up
[11:36:06] <KitsuWhooa> modern boards still have rs232
[11:36:11] <KitsuWhooa> not many people know :p
[11:36:35] <KitsuWhooa> do go on
[11:36:35] <Xogium> yeah I had to figure out where the com port internal was on the mobo
[11:38:39] <Xogium> so what I actually tried, instead of making straight for i486 of archlinux32, since the iso is not a finished product, was to boot up a vm in qemu as i686, and then install the i486 rootfs from there onto a virtual disk. Then I grabbed it and fixed it all up for use on the real hardware, converting to img and dd-ing that
[11:38:52] <KitsuWhooa> ah
[11:39:03] <Xogium> there's just one big problem
[11:40:16] <Xogium> the kernel itself appears to run fine, but the second it tries to run init from the initramfs? Invalid opcode
[11:40:39] <KitsuWhooa> uhhhh
[11:41:03] <KitsuWhooa> so you're saying non i486 code made it into systemd? :p
[11:41:11] <KitsuWhooa> wouldn't surprise me
[11:41:13] <Xogium> not systemd, busybox for init by default
[11:41:21] <KitsuWhooa> oh, right
[11:42:15] <Xogium> I'm unsure what is really going on granted, but in the end I had to use buildroot, with a couple of kernel config options enabled, mainly to get access to hardware. This thing is really, really weird
[11:42:23] <Xogium> really messed up
[11:42:45] <Xogium> pemtium pro subarch seems to be agreeing with it, kernel-wise
[11:43:02] <Xogium> https://paste.xogium.me
[11:43:57] <Xogium> it is basically a i686 family cpu except it's not and isn't standard in what instructions it even offers
[11:44:04] <Xogium> so it actually runs i586 code
[11:44:14] <KitsuWhooa> mhm
[11:44:44] <Xogium> what a very strange beast
[11:45:29] <Xogium> I suspect the issue with the usb to rs232 was actually flow control. Either the vortex did something the adapter didn't like, or the other way around. Maybe the hardware flow control of the adapter is too smart for the SoC
[11:46:27] <KitsuWhooa> is it legit ftdi?
[11:46:31] <Xogium> I never had issue with the adapter before, with anything I used it with
[11:46:43] <KitsuWhooa> sounds like it'd be an issue with a fake
[11:47:51] <Xogium> yeah, I know, but this thing isn't fake, or at least if it is one, then they went to the extreme of faking the brand vid/pid of usb
[11:47:56] <Xogium> Bus 001 Device 003: ID 0403:6015 FTDI Chipi-X
[11:48:23] <KitsuWhooa> Ah, it's not an FT2232
[11:48:35] <KitsuWhooa> there were pretty good fakes of those
[11:48:40] <KitsuWhooa> https://lkml.org
[11:48:41] <phrik> Title: LKML: russ.dill@gmail ...: [PATCH] usb: serial: Perform verification for FTDI FT232R devices (at lkml.org)
[11:48:54] <Xogium> oh dear yeah I remember
[11:49:06] <Xogium> and ftdi is very aggressive towards fakes
[11:49:49] <KitsuWhooa> if they made a patch that just warns you that you have a fake, that'd have been nice
[11:49:53] <KitsuWhooa> but no, they wanted to brick them
[11:50:01] <Xogium> yeah tht's nasty
[11:51:21] <Xogium> I tend to always buy the genuine brand honestly, for a lot of things I get. I'd rather pay a bit more and be safe in the knowledge that I have the genuine product, not a cheap knock off that could be trouble
[11:51:34] <Xogium> but I also can understand people who buy fakes even on purpose
[12:00:20] <KitsuWhooa> I just wish they weren't "fakes" but rather their own products
[12:00:23] <KitsuWhooa> I'm sure there's a market for them
[12:00:31] <Xogium> yeah
[12:00:43] <KitsuWhooa> I think the FTDI situation got so bad that even reputable sellers got fakes without realising
[12:00:59] <Xogium> yeah, same with sd cards can happen
[12:01:08] <Xogium> a third of the sandisk sd card are fakes
[12:08:40] -!- ssserpent has joined #archlinux32
[18:39:39] -!- jacobk has quit [Ping timeout: 260 seconds]
[18:40:14] -!- jacobk has joined #archlinux32
[19:50:41] -!- jacobk has quit [Ping timeout: 248 seconds]
[19:51:21] -!- jacobk has joined #archlinux32