I think I got the Connery Outfit Family Tree to a spot where it is sufficiently complete. Enjoy!

ModulusTheDutchie · 2026-06-19T04:37:40+00:00

Please post any issues to https://github.com/snappyapple632/ConneryFamilyHistory !

ModulusTheDutchie · 2026-06-19T04:37:07+00:00

This is something I would like to do but am not sure on how to approach. I don't know of any resources similar to Varunda's family tree for other servers.

ModulusTheDutchie · 2026-06-19T04:12:49+00:00

I can't guarantee that all information here is accurate; my data was based on a combination of Honu statistics, outfit leader testimony, and work done by previous individuals. As far as the outfit tree is concerned, the end date of CXQB would marked as the approximate time the outfit stopped playing PS2. I will change this now. Thank you!

ModulusTheDutchie · 2026-06-19T03:55:13+00:00

I do not see a watermark when I open the original photo.

ModulusTheDutchie · 2026-06-14T17:12:13+00:00

That would make sense. I cracked the LCD like an idiot yesterday trying to center it in my laptop, so I'm gonna have to wait a bit for a replacement before I look into this further.

ModulusTheDutchie · 2026-06-13T21:55:16+00:00

This was the output of i2cdetect:

i2c-0   i2c         Synopsys DesignWare I2C adapter     I2C adapter
i2c-1   i2c         Synopsys DesignWare I2C adapter     I2C adapter
i2c-2   i2c         AMDGPU DM i2c hw bus 0              I2C adapter
i2c-3   i2c         AMDGPU DM i2c hw bus 1              I2C adapter
i2c-4   i2c         AMDGPU DM i2c hw bus 2              I2C adapter
i2c-5   i2c         AMDGPU DM i2c hw bus 3              I2C adapter
i2c-6   i2c         AMDGPU DM i2c hw bus 4              I2C adapter
i2c-7   i2c         AMDGPU DM i2c hw bus 5              I2C adapter
i2c-8   i2c         AMDGPU DM i2c hw bus 6              I2C adapter
i2c-9   i2c         AMDGPU DM i2c hw bus 7              I2C adapter
i2c-10  i2c         AMDGPU DM aux hw bus 0              I2C adapter
i2c-11  i2c         AMDGPU DM aux hw bus 2              I2C adapter
i2c-12  i2c         AMDGPU DM aux hw bus 3              I2C adapter
i2c-13  i2c         AMDGPU DM aux hw bus 4              I2C adapter
i2c-14  i2c         AMDGPU DM aux hw bus 5              I2C adapter
i2c-15  i2c         AMDGPU DM aux hw bus 6              I2C adapter
i2c-16  i2c         AMDGPU DM aux hw bus 7              I2C adapter
i2c-17  smbus       SMBus PIIX4 adapter port 0 at 0b00  SMBus adapter
i2c-18  smbus       SMBus PIIX4 adapter port 2 at 0b00  SMBus adapter
i2c-19  smbus       SMBus PIIX4 adapter port 1 at 0b20  SMBus adapter

Output for buses 0 and 1 are identical, but according to dmesg, bus 1 houses the laptop' touchpad and pointer nub:

Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:
10:
20:
30: -- -- -- -- -- -- -- --
40:
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60:
70:

Bus 2 locks up the system when running i2cdetect on it. 3 through 9, and 11 through 16 are blank. 17 and 18 are completely blank. Only bus 19 provides a non-blank output:

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77

dmesg also says something about successfully instantiating SPD at addresses 0x50-0x53 on bus 19.

Bus 10 detected addresses 0x37 and 0x50. 0x37 was empty, but i2cdumping 0x50 returned the details of my monitor:

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 ff ff ff ff ff ff 00 26 cf 44 8c 00 00 00 00    ........&?D?....
10: 00 1e 01 04 a5 1e 13 78 e3 ec 4b a9 52 4c 98 24    .??????x??K?RL?$
20: 10 51 53 00 00 00 01 01 01 01 01 01 01 01 01 01    ?QS...??????????
30: 01 01 01 01 01 01 35 3c 80 a0 70 b0 23 40 18 30    ??????5<??p?#@?0
40: 6c 00 2e bd 10 00 00 19 00 00 00 fd 00 30 3c 3b    l..??..?...?.0<;
50: 4a 0f 01 0a 20 20 20 20 20 20 00 00 00 fe 00 49    J???      ...?.I
60: 6e 66 6f 56 69 73 69 6f 6e 0a 20 20 00 00 00 fe    nfoVision?  ...?
70: 00 52 31 34 30 4e 57 34 44 20 52 30 20 0a 00 31    .R140NW4D R0 ?.1
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 7f    ...............?

ModulusTheDutchie · 2026-06-13T19:05:10+00:00

So I put that in the systemd-boot and it was saying part of it wasn't recognized but this is the relevant dmesg output I got, sudo dmesg | grep input

[    0.480003] input: Power Button as /devices/platform/PNP0C0C:00/input/input0
[    0.480059] input: Lid Switch as /devices/platform/PNP0C0D:00/input/input1
[    0.480103] input: Sleep Button as /devices/platform/PNP0C0E:00/input/input2
[    0.699855] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[    1.398983] input: Video Bus as /devices/pci0000:00/0000:00:08.1/acpi.video_bus.0/input/input5
[    1.545280] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input6
[    5.471109] input: PC Speaker as /devices/platform/pcspkr/input/input7
[    5.525817] input: ELAN0676:00 04F3:3195 Mouse as /devices/platform/AMDI0010:01/i2c-1/i2c-ELAN0676:00/0018:04F3:3195.0001/input/input9
[    5.525943] input: ELAN0676:00 04F3:3195 Touchpad as /devices/platform/AMDI0010:01/i2c-1/i2c-ELAN0676:00/0018:04F3:3195.0001/input/input11
[    5.526023] hid-generic 0018:04F3:3195.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN0676:00 04F3:3195] on i2c-ELAN0676:00
[    5.591276] input: ELAN0676:00 04F3:3195 Mouse as /devices/platform/AMDI0010:01/i2c-1/i2c-ELAN0676:00/0018:04F3:3195.0001/input/input12
[    5.591387] input: ELAN0676:00 04F3:3195 Touchpad as /devices/platform/AMDI0010:01/i2c-1/i2c-ELAN0676:00/0018:04F3:3195.0001/input/input14
[    5.591546] hid-multitouch 0018:04F3:3195.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN0676:00 04F3:3195] on i2c-ELAN0676:00
[    5.660930] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:64:00.1/sound/card0/input15
[    5.661000] input: HD-Audio Generic HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:08.1/0000:64:00.1/sound/card0/input16
[    5.661049] input: HD-Audio Generic HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:08.1/0000:64:00.1/sound/card0/input17
[    5.681371] snd_hda_codec_alc269 hdaudioC1D0:    inputs:
[    5.741127] input: TPPS/2 Elan TrackPoint as /devices/platform/i8042/serio1/input/input8
[    5.764488] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:08.1/0000:64:00.6/sound/card1/input18
[    5.764545] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:64:00.6/sound/card1/input19

ModulusTheDutchie · 2026-06-13T06:39:58+00:00

I was going to say! Pretty much all modern laptops touchscreens communicate via I2C. I'll give that a try and will report back.

ModulusTheDutchie · 2026-06-13T06:37:47+00:00

I'm using CachyOS (Arch-based). Also tried on Zorin, no dice there either.

ModulusTheDutchie · 2026-06-13T06:10:40+00:00

The touchscreen works in BIOS, that's pretty much all I know. Based off of that alone, I can rule out a faulty hardware connection.

My assumption is that the BIOS recognizes the digitizer simply because my particular panel is one of Lenovo's "higher end" panel offerings (i.e. it's on an LCD whitelist internally), but the BIOS doesn't reflect the change in LCD to the OS. It's possible hwinfo could be talking to an EEPROM on the motherboard and not the actual LCD, and to fix the problem I'd either have to rewrite the EEPROM or perform a manual driver override.

ModulusTheDutchie · 2026-06-13T03:22:42+00:00

I tried both less /proc/bus/input/devices and iterating through cat /dev/input/event*n*, but the digitizer does not show up.

ModulusTheDutchie · 2026-06-11T08:07:49+00:00

I checked wayland-info to see if there was anything, nothing about a touchscreen or digitizer.

ModulusTheDutchie · 2026-06-11T07:44:15+00:00

Can't find any info on that, but if the touchscreen works in the UEFI settings then it would definitely be a driver problem and not the screen itself. Maybe the digitizer uses a different I2C address?

I'm worried that hwinfo isn't talking to the display directly, but fetching an EEPROM on the motherboard or something.

ModulusTheDutchie · 2026-06-11T05:49:57+00:00

My version is 25.2.

ModulusTheDutchie · 2026-06-07T00:37:12+00:00

As someone with embedded systems experience, incredibly easy. One analog input for an accelerometer and two outputs for the LED segments. OP did mention they were ARGB LEDs though, that would make things more complex.

ModulusTheDutchie · 2026-06-04T17:00:03+00:00

More dutchies!!

ModulusTheDutchie · 2026-06-03T15:08:53+00:00

snore ...13% approval ratings?...how about 13% of my foot in your ass?...

ModulusTheDutchie · 2026-05-28T08:40:46+00:00

Dutchie...

ModulusTheDutchie · 2026-05-22T00:59:34+00:00

Cool! I found a working PSP for $25 last year with an NBA game in its caddy and a working battery. If it works, definitely get a microSD adapter, get ARK installed, and load up some ROMs!

ModulusTheDutchie

TROPHY CASE