| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40) | 00:30 | |
| minute | ok, built mutter and gnome-shell from git on reform, and they work | 00:37 |
|---|---|---|
| - mtm (QUIT: Ping timeout: 252 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 01:02 | |
| - ajr (QUIT: Quit: WeeChat 3.7) (~ajr@user/ajr) | 02:17 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 03:08 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 05:49 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 05:51 | |
| + MajorBiscuit (~MajorBisc@145.94.153.3) | 09:57 | |
| * wielaard -> mjw | 10:11 | |
| + bgs (~bgs@212-85-160-171.dynamic.telemach.net) | 10:14 | |
| + S0rin (~S0rin@user/s0rin) | 12:35 | |
| mjw | minute, Missed you at Fosdem. It was so chaotic, but certainly fun. Also I already have my mnt reform of course. But it would have been nice to tell you in person how much I like it. So lets just virtually say the reform rocks, thanks! :) | 12:49 |
| mjw | Hope you had a good time. | 12:49 |
| - mtm (QUIT: Ping timeout: 248 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 13:03 | |
| minute | mjw: thank you very much! it was very crowded and chaotic, but worth it! | 13:10 |
| - S0rin (QUIT: Ping timeout: 248 seconds) (~S0rin@user/s0rin) | 13:43 | |
| + S0rin (~S0rin@user/s0rin) | 13:57 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 15:10 | |
| pandora[m] | <mjw> "minute, Missed you at Fosdem. It..." <- I couldn’t even find the MNT booth 🙈 | 15:20 |
| mjw | He was "embedded" :) | 15:22 |
| mjw | https://mastodon.social/@mntmn/109808024287105873 | 15:26 |
| mjw | I did walk past a couple of times, but was either in a hurry to get to some talk and/or it was very crowded and I couldn't even reach the stand. | 15:27 |
| minute | pandora[m]: there was no mnt booth! | 15:49 |
| pandora[m] | That may explain my inability to find it :D | 15:58 |
| minute | xktr: are you here? asking because of your som debugging problems | 16:07 |
| xktr | Yessir. | 16:44 |
| xktr | And to reduce my ignorance by taking in the technical discussions. I obviously have a lot to learn! | 16:46 |
| minute | xktr: cool, i just wrote you back via the support system btw | 17:12 |
| xktr | minute: Affirmative! I'll get it set up and try it out here in a moment. Thanks again! | 17:26 |
| xktr | minute: To start, should I be using a particular system image? v3? Or something more recent than that? | 17:39 |
| minute | xktr: well, v3 is really only a moniker for something we have been using for a long time now, where we changed the whole approach to a cleaner integration with debian | 17:40 |
| xktr | At the moment, I have v2 system and recovery on two USB sticks. | 17:40 |
| minute | v2 is highly unrecommended | 17:40 |
| minute | xktr: here are the latest images https://source.mnt.re/reform/reform-system-image/-/jobs/1119/artifacts/browse/reform2-imx8mq/ | 17:41 |
| xktr | Understood! I still have v3 system and recovery images -- which one should I write first to run the steps you provided? | 17:41 |
| minute | xktr: i would use rescue v3. if you have a v3 lying around, it should be fine. | 17:41 |
| xktr | Rescue it is! | 17:41 |
| xktr | I'll pull from your link to make sure I'm totally aligned. | 17:42 |
| minute | xktr: ok cool. also check the version numbers of vmlinuz/initrd after flashing to usb stick | 17:42 |
| minute | xktr: in my guide i wrote 6.1, but not sure if that is correct for the latest version atm | 17:42 |
| minute | so you might need to adjust the filenames in the load commands | 17:43 |
| xktr | ACTION nods | 17:46 |
| xktr | Understood! | 17:46 |
| xktr | Downloading reform-rescue-system.img.gz; that'll take a bit. | 17:51 |
| + andreas-e (~Andreas@2001:861:c4:f2f0::c64) | 17:55 | |
| + ae (~Andreas@2001:861:c4:f2f0::c64) | 17:55 | |
| - andreas-e (QUIT: Client Quit) (~Andreas@2001:861:c4:f2f0::c64) | 17:56 | |
| - ae (QUIT: Client Quit) (~Andreas@2001:861:c4:f2f0::c64) | 17:56 | |
| + andreas-e (~Andreas@2001:861:c4:f2f0::c64) | 17:56 | |
| - andreas-e (QUIT: Client Quit) (~Andreas@2001:861:c4:f2f0::c64) | 17:57 | |
| + andreas-e (~Andreas@2001:861:c4:f2f0::c64) | 17:57 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:40) | 18:23 | |
| - MajorBiscuit (QUIT: Ping timeout: 260 seconds) (~MajorBisc@145.94.153.3) | 18:26 | |
| + ajr (~ajr@user/ajr) | 19:04 | |
| xktr | minute: I gave the steps a try and they all seem to work except for booti at the end. This is what I get: | 19:17 |
| xktr | => booti 0x40480000 0x44000000 0x50000000 | 19:18 |
| xktr | Moving Image from 0x40480000 to 0x40600000, end=42060000 | 19:18 |
| xktr | Wrong Ramdisk Image Format | 19:18 |
| xktr | Ramdisk image is corrupt or invalid | 19:18 |
| minute | mhmm | 19:18 |
| minute | actually you could try without a ramdisk first, not sure how critical the modules are | 19:19 |
| minute | i.e. you can try booti 0x40480000 - 0x50000000 | 19:19 |
| xktr | That seems to work: | 19:20 |
| xktr | => booti 0x40480000 - 0x50000000 | 19:20 |
| xktr | Moving Image from 0x40480000 to 0x40600000, end=42060000 | 19:20 |
| xktr | ## Flattened Device Tree blob at 50000000 Booting using the fdt blob at 0x50000000 Using Device Tree in place at 0000000050000000, end 000000005000c58a | 19:20 |
| xktr | Starting kernel ... | 19:20 |
| minute | booting or not? | 19:20 |
| xktr | It seemed to hang there for a few seconds, and it reset itself. | 19:21 |
| minute | oh. | 19:21 |
| xktr | Back to the => uboot prompt. | 19:21 |
| minute | ah, looks like one has to pass the size for the ramdisk | 19:22 |
| minute | see here https://u-boot.readthedocs.io/en/v2021.04/usage/booti.html#example | 19:22 |
| xktr | ACTION opens the URL | 19:23 |
| minute | they load the ramdisk last, and after load the size is in the variable $filesize | 19:23 |
| minute | if you do: print fdt_addr_r | 19:23 |
| minute | is that set? and print kernel_addr_r and print ramdisk_addr_r ? | 19:23 |
| minute | if they are set, then you can use these variables instead of the magic constants i gave you | 19:24 |
| xktr | Those three don't appear to be set: | 19:26 |
| xktr | => print fdt_addr_r | 19:26 |
| xktr | ## Error: "fdt_addr_r" not defined | 19:26 |
| xktr | => print kernel_addr_r | 19:26 |
| xktr | ## Error: "kernel_addr_r" not defined | 19:26 |
| xktr | => print ramdisk_addr_r | 19:26 |
| xktr | ## Error: "ramdisk_addr_r" not defined | 19:26 |
| xktr | => | 19:26 |
| minute | ok, old u-boot | 19:26 |
| xktr | ACTION nods | 19:27 |
| minute | if you do: setenv fdt_addr_r 0x50000000 | 19:27 |
| minute | and then saveenv, does that work? | 19:27 |
| xktr | ACTION gives it a try | 19:28 |
| xktr | => setenv fdt_addr_r 0x50000000 | 19:29 |
| xktr | => saveenv | 19:29 |
| xktr | Saving Environment to MMC... Writing to MMC(0)... OK | 19:29 |
| minute | ah nice | 19:29 |
| xktr | :D | 19:29 |
| minute | so we can set these variables and save them for later use | 19:29 |
| minute | so you can do: setenv kernel_addr_r 0x40480000; setenv ramdisk_addr_r 0x44000000 | 19:29 |
| minute | and saveenv again | 19:30 |
| minute | now, booting should be: load usb 0 $fdt_addr_r dtb; load usb 0 $kernel_addr_r vmlinuz... (substitute the filename); load usb 0 $ramdisk_addr_r initrd... (substitute the filename) | 19:31 |
| minute | and if those all work: booti $kernel_addr_r $ramdisk_addr_r:$filesize $fdt_addr_r | 19:31 |
| xktr | I set those envs, saved, powered off, and powered on. Saw the keyboard and trackball keys light up and there's video! It showed the kernel init, and a bunch of these lines: | 19:34 |
| xktr | "begin: Running /scripts/local-block ... done." | 19:34 |
| xktr | Then ends up at a busybox prompt. | 19:34 |
| xktr | (initramfs), for about a half a minute, then resets. | 19:34 |
| xktr | It's already done it three times. | 19:35 |
| minute | oh! | 19:35 |
| minute | well, that's progress | 19:35 |
| xktr | Amen! :D | 19:35 |
| minute | the reset is not so good. i wonder why it does that. sounds like watchdog | 19:35 |
| xktr | There's nothing useful being output on the serial connectien. | 19:36 |
| minute | ah. in my above instructions, i did not include the setenv bootargs ... line. did you enter it anyway, or not, this time? | 19:36 |
| xktr | I haven't touched that one yet. Here's what it's currently set to: | 19:37 |
| xktr | => printenv bootargs | 19:37 |
| xktr | bootargs=ro no_console_suspend cma=512M pci=nomsi ro no_console_suspend cma=512M pci=nomsi console=ttymxc0,115200 console=ttymxc0,115200 console=tty1 console=ttymxc0,115200 console=ttymxc0,115200 console=tty1 | 19:37 |
| minute | oh, strange. these are from boundary i guess | 19:38 |
| xktr | Lemme set it to what you gave me and give it another shot. | 19:38 |
| minute | yup | 19:38 |
| xktr | It's thinking! | 19:40 |
| xktr | I set bootargs to what you sent and saved it. Trying a boot from poweroff. | 19:43 |
| minute | thinking? | 19:43 |
| xktr | Yeah, the usb stick access light was blinking. | 19:44 |
| minute | but you didn't get any output after booti or...? | 19:44 |
| xktr | It appeared to start to boot, but reset. I'm trying it again. | 19:45 |
| xktr | started file system check daemon to report status | 19:46 |
| xktr | That's what it seems to be working on at the moment. | 19:46 |
| xktr | Console font changed to the debian default. | 19:46 |
| xktr | usb light is blinking still. | 19:47 |
| xktr | reached target emergency mode | 19:47 |
| xktr | this is the furthes I've gotten with this so far! | 19:47 |
| xktr | Emergency mode has been reached | 19:47 |
| xktr | :) | 19:48 |
| xktr | "press enter for maintenance or press ctrl-d to continue" | 19:49 |
| minute | ok, press enter | 19:49 |
| minute | then do /usr/sbin/reform-flash-rescue | 19:50 |
| xktr | the laptop keyboard and fromebuffer aren't responding, but the serial console did. | 19:51 |
| minute | hmmm, that's strange | 19:51 |
| xktr | ACTION runs /usr/sbin/reform-flash-rescue | 19:51 |
| minute | hold on | 19:51 |
| minute | actually cancel that command. | 19:51 |
| xktr | heh, I was gonna say: | 19:51 |
| xktr | root@reform:~# /usr/sbin/reform-flash-rescue | 19:51 |
| xktr | /boot/flash.bin doesn't exist | 19:51 |
| minute | well, that's good. it's possible that we need to make you one for 2GB ram | 19:51 |
| minute | you have a 2GB module, right? | 19:52 |
| xktr | Yessir! | 19:52 |
| minute | ok, hang on | 19:53 |
| xktr | Aye Sir! | 19:57 |
| minute | ok, CONFIG_DDR_MB is the magic thingie... lets see | 19:57 |
| xktr | :D | 19:58 |
| minute | building you a new flash.bin | 19:58 |
| minute | do you have ethernet? | 19:59 |
| minute | xktr: i mean, do you have ethernet connected to the reform? so you could download a file. otherwise you will need to boot again after importing the file | 19:59 |
| minute | xktr: anyway, here is a u-boot for you for 2GB: http://dump.mntmn.com/flash.bin.2gb | 20:01 |
| minute | xktr: actually with this, you could try booting directly from SD card another try. but it might be a hassle | 20:02 |
| - mjw (QUIT: Killed (NickServ (GHOST command used by markw!~wielaard@gnu.wildebeest.org))) (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:02 | |
| minute | xktr: but IIRC sd card booting did not output anything? | 20:02 |
| + wielaard (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:02 | |
| xktr | minute: responding in order: No ethernet at the moment, but I can rustle up a switch and cables if needs be; will pull the flash.bin.2gb, and I'll write it with "dd if=flash.bin of=/dev/sdx bs=1024 seek=33"(right?); correct on SD booting, when the SOM is set to on, there's no activity on the serial console whatsoever. | 20:04 |
| xktr | minute: I don't mind hassle, so whatever you need done, just say the word! | 20:05 |
| xktr | ok, flash image pulled, and writing now... | 20:07 |
| minute | xktr: ok, lets ignore the SD booting then. the dd write command is correct. but we will also need the file itself | 20:07 |
| minute | xktr: can you mount the second partition of the usb stick? | 20:07 |
| minute | (on your non-reform computer) | 20:07 |
| xktr | minute: Yep, will do! | 20:07 |
| minute | xktr: does it have a /boot? (my guess is it should have an empty /boot) | 20:08 |
| minute | xktr: if it has, you can copy flash.bin.2gb there, but rename it flash.bin | 20:08 |
| minute | xktr: for good measure, also mount the first partition and copy the new flash.bin there (overwriting the old one that is there) | 20:09 |
| xktr | minute: confirmed there's a boot/ in sda2, but it's empty. | 20:09 |
| minute | (should be on the root of the first partition) | 20:09 |
| xktr | will do! | 20:09 |
| minute | ok so this should be something for reform-flash-rescue to work with, then. | 20:10 |
| xktr | ok, the 2gb flash.bin has been put in part2/boot/ and overwrote flash.bin in part1/boot/ | 20:12 |
| minute | oh, part1 has a boot? | 20:12 |
| minute | and there was no flash.bin on the root of part1, yes? | 20:13 |
| xktr | sorry, I mistyped -- part1 appears to have the boot assets -- here's the directory: | 20:14 |
| xktr | boot.scr | 20:14 |
| xktr | config-6.1.0-reform2-arm64 | 20:14 |
| xktr | dtb | 20:14 |
| xktr | dtb-6.1.0-reform2-arm64 | 20:14 |
| xktr | dtbs | 20:14 |
| xktr | flash.bin | 20:14 |
| xktr | initrd.img-6.1.0-reform2-arm64 | 20:14 |
| xktr | lost+found | 20:14 |
| xktr | System.map-6.1.0-reform2-arm64 | 20:14 |
| xktr | vmlinuz-6.1.0-reform2-arm64 | 20:14 |
| xktr | I overwrote that flash.bin with the 2gb one you provided. | 20:14 |
| xktr | part2 is what appears to have a traditional root directory scheme. | 20:15 |
| xktr | usr, etc, dev, etc | 20:16 |
| xktr | so I replaced flash.bin in part1 and put flash.bin in part2/boot/ | 20:16 |
| minute | good | 20:17 |
| minute | this is fine | 20:17 |
| minute | so, try booting again (like last time when it worked), enter emergency shell and then try /usr/bin/reform-flash-rescue again. | 20:18 |
| xktr | Roger that! | 20:18 |
| xktr | Here goes! | 20:20 |
| xktr | lsblk: /dev/mmcblk0p1: not a block device | 20:26 |
| xktr | lsblk: /dev/mmcblk0p2: not a block device | 20:26 |
| xktr | WARNING: This overwrites the bootloader on the eMMC rescue disk with the | 20:26 |
| xktr | backup stored as /boot/flash.bin! | 20:26 |
| xktr | Are you sure you want to proceed? [y/N] | 20:26 |
| xktr | say yes here? | 20:26 |
| minute | hmm, can you cancel and do lsblk and paste the output here? | 20:27 |
| xktr | yep, sec... | 20:27 |
| minute | just wanna make sure it'll write to the correct disk | 20:27 |
| xktr | root@reform:/usr/bin# lsblk | 20:27 |
| xktr | NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS | 20:27 |
| xktr | sda 8:0 1 15.1G 0 disk | 20:27 |
| xktr | ├─sda1 8:1 1 488M 0 part | 20:27 |
| xktr | └─sda2 8:2 1 2G 0 part / | 20:27 |
| xktr | mmcblk0 179:0 0 14.6G 0 disk | 20:27 |
| xktr | nvme0n1 259:0 0 953.9G 0 disk | 20:27 |
| xktr | mmcblk0boot0 179:256 0 4M 1 disk | 20:27 |
| xktr | mmcblk0boot1 179:512 0 4M 1 disk | 20:27 |
| minute | ah yeah | 20:27 |
| minute | mmcblk0 is not partitioned, so it's fine | 20:27 |
| minute | (mmcblk0 is the emmc) | 20:27 |
| xktr | ACTION nods | 20:27 |
| xktr | Suss! | 20:28 |
| minute | well yeah, if you had network now | 20:28 |
| minute | the script could do that for you | 20:28 |
| minute | but i'm not sure how much of that works in emerg mode. maybe it just works though | 20:28 |
| minute | i.e. plug in ethernet and dhclient eth0 | 20:28 |
| xktr | Should I wait until I have access to a live ethernet connection and try then? | 20:29 |
| minute | well i'm thinking, you have the usb stick | 20:30 |
| minute | it has the same content | 20:30 |
| xktr | Give it a shot then? | 20:31 |
| minute | this could work: `dd if=/dev/sda of=/dev/mmcblk0 status=progress` | 20:31 |
| minute | sda is a bit bigger than mmcblk0 but interesting data is only in the first 2.5G | 20:32 |
| minute | but also, you can and should run /usr/sbin/flash-rescue and say yes to the first question, to get the bootloader updated. | 20:32 |
| xktr | Affirmative! | 20:33 |
| xktr | Running flash-rescue.. | 20:33 |
| xktr | 1027+1 records in | 20:34 |
| xktr | 1027+1 records out | 20:34 |
| xktr | 1052488 bytes (1.1 MB, 1.0 MiB) copied, 0.284873 s, 3.7 MB/s | 20:34 |
| xktr | Bootloader was successfully written to /dev/mmcblk0boot0. | 20:34 |
| xktr | Do you want to download and install the latest sysimage-v3 to eMMC as well? | 20:34 |
| xktr | This step needs a working internet connection and either wget or curl installed. | 20:34 |
| xktr | WARNING: This overwrites partitions on eMMC, deleting all data. | 20:34 |
| xktr | Are you sure you want to proceed? [y/N] | 20:34 |
| xktr | Said yes to the first question nad no to #2 | 20:35 |
| xktr | Running dd... now | 20:35 |
| xktr | s/nad/no | 20:35 |
| xktr | dd is running now. | 20:35 |
| minute | cool | 20:37 |
| xktr | If dd gets past 2.5GB, should I exit it out, or let it run until it fills mmcblk0? | 20:42 |
| xktr | Looks like its up to 6GB and counting. | 20:43 |
| minute | i think you can let it run | 20:44 |
| xktr | Aye, I'll leave it alone then | 20:44 |
| xktr | more fun: | 20:46 |
| xktr | 7316759040 bytes (7.3 GB, 6.8 GiB) copied, 564 s, 13.0 MB/s[ 1391.280105] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s | 20:46 |
| xktr | [ 1391.294619] sd 0:0:0:0: [sda] tag#0 Sense Key : Hardware Error [current] | 20:46 |
| xktr | [ 1391.306592] sd 0:0:0:0: [sda] tag#0 Add. Sense: No additional sense information | 20:46 |
| xktr | [ 1391.319063] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 da 60 d8 00 00 10 00 | 20:46 |
| xktr | [ 1391.331486] I/O error, dev sda, sector 14311640 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 | 20:46 |
| minute | meh | 20:46 |
| xktr | [ 1422.463283] usb 3-1: reset high-speed USB device number 2 using xhci-hcd | 20:46 |
| xktr | [ 1427.811152] usb 3-1: device descriptor read/64, error -110 | 20:46 |
| xktr | [ 1443.427152] usb 3-1: device descriptor read/64, error -110 | 20:46 |
| xktr | [ 1443.671151] usb 3-1: reset high-speed USB device number 2 using xhci-hcd | 20:46 |
| xktr | [ 1449.059150] usb 3-1: device descriptor read/64, error -110 | 20:46 |
| minute | ok, instability with the usb device | 20:47 |
| minute | at least you were able to copy a bunch of stuff | 20:47 |
| minute | and flash the bootloader. | 20:47 |
| xktr | ...aaand it kernel panicked | 20:47 |
| xktr | here comes the reset | 20:47 |
| minute | i wonder what happens if you reset now | 20:47 |
| minute | do you get u-boot output over serial? | 20:47 |
| xktr | I do, and it's it's familiar: | 20:48 |
| xktr | U-Boot SPL 2018.07 MNT Reform 2023-01-25 (Feb 08 2023 - 20:00:28 +0100) | 20:48 |
| xktr | Setting voltages | 20:48 |
| xktr | config to do 3200 1d training. | 20:48 |
| xktr | Training FAILED | 20:48 |
| xktr | config to do 667 1d training. | 20:48 |
| xktr | Training FAILED | 20:48 |
| xktr | config to do 3200 2d training. | 20:48 |
| minute | argh | 20:48 |
| xktr | Training FAILED | 20:48 |
| xktr | ARM_PLL 1000 MHz | 20:48 |
| xktr | SYS_PLL1_800 799 MHz | 20:48 |
| xktr | SYS_PLL1_400 399 MHz | 20:48 |
| xktr | SYS_PLL1_266 266 MHz | 20:48 |
| xktr | SYS_PLL1_200 199 MHz | 20:48 |
| xktr | SYS_PLL1_160 159 MHz | 20:48 |
| xktr | SYS_PLL1_133 133 MHz | 20:48 |
| xktr | SYS_PLL1_100 99 MHz | 20:48 |
| xktr | SYS_PLL1_80 79 MHz | 20:49 |
| xktr | SYS_PLL1_40 39 MHz | 20:49 |
| xktr | SYS_PLL2_1000 999 MHz | 20:49 |
| xktr | SYS_PLL2_500 499 MHz | 20:49 |
| xktr | SYS_PLL2_333 333 MHz | 20:49 |
| xktr | SYS_PLL2_250 249 MHz | 20:49 |
| xktr | SYS_PLL2_200 199 MHz | 20:49 |
| xktr | SYS_PLL2_166 166 MHz | 20:49 |
| xktr | SYS_PLL2_125 124 MHz | 20:49 |
| xktr | SYS_PLL2_100 99 MHz | 20:49 |
| xktr | SYS_PLL2_50 49 MHz | 20:49 |
| xktr | SYS_PLL3 25 MHz | 20:49 |
| xktr | UART1 25 MHz | 20:49 |
| xktr | USDHC1 199 MHz | 20:49 |
| xktr | QSPI 399 MHz | 20:49 |
| xktr | It's dead, Jim | 20:49 |
| minute | ok, it is possible to revive it but not with reform unfortunately. i am confused why the training wouldn't work though, as i've made you a bin for a 2G module | 20:50 |
| minute | (it would be possible to fix it ~if~ your sd card boot was working, but alas, it is not) | 20:51 |
| minute | i suggest we make you a UPS label and mail the whole thing to us, and i will fix it | 20:52 |
| xktr | If you think the SOM can be reset with one fo those Nitrogen carrier boards that Mouser sells, I can pick one of those up too. | 20:53 |
| minute | xktr: yes, you can do that with those. but they're quite pricey, no? | 20:54 |
| xktr | But whatever makes it easy for you. I'm grateful for your help. | 20:54 |
| xktr | EUR 212 -- ehhh | 20:57 |
| xktr | can I PM you? | 20:57 |
| minute | xktr: PMs are not so good because hard for me to track later. i would suggest continuing the support case. we'll make you a UPS label and i will take a look. i think that's better because the SD stuff needs to be fixed anyway | 20:58 |
| xktr | Understood. Should I send the 4GB SOM along as well? | 20:59 |
| minute | xktr: sure, that would be good | 20:59 |
| xktr | I'll wait for your emails then and continue the support case. | 21:00 |
| xktr | Vielen dank, mein Herr! | 21:00 |
| minute | sure, sorry that it didn't work out | 21:00 |
| xktr | Good things come to those who wait. :) | 21:00 |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 21:48 | |
| - buckket (QUIT: Quit: buckket) (~buckket@pdp8.buckket.org) | 21:52 | |
| + buckket (~buckket@pdp8.buckket.org) | 22:05 | |
| - andreas-e (QUIT: Quit: Leaving) (~Andreas@2001:861:c4:f2f0::c64) | 22:15 | |
| minute | datapoint: keyboard uses 0.25W power. 0W when sleeping | 22:20 |
| - bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net) | 22:46 | |
| - Gooberpatrol66 (QUIT: Read error: Connection reset by peer) (~Gooberpat@user/gooberpatrol66) | 22:53 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 22:56 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40) | 23:19 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!