#
…

2021-07-29

00:04MTecknologyThat question went a bit over my head, particularly the *util stuff. I don't care to leave mac on here either (if it's not required, I think I read that m1n1 is sorta mini s/unix/mac/).
00:06marcanMTecknology: you probably want to leave macos on there for updates, we're going to recommend dual-boot for a long while until we figure out a way to do firmware updates from linux
00:06alyssamarcan: aren't you supposed to be asleep
00:07marcanI just woke up
00:08pipcet[m]sorry about that. I think all you need to play with m1n1 is the .macho, boot into recovery mode, open a terminal, run *util in the right order and with the right parameters, and reboot. you definitely do want to keep macos around on the nvme, though
00:08marcanMTecknology: but yeah, right now the recommended thing to do is follow the dev guide to get things installed
00:08marcanthe main purpose of the dev guide is to get people to install a second macos partition to replace with linux; our installer will eventually do that without the macos step, but for now this is how it goes
00:09MTecknologyDoes the dev guide still apply to a dual boot?
00:09marcanthe dev guide gives you a dual boot environment
00:10marcanand the reason for that is that dual-booting is a low level feature on these machines; you need multiple "native" macOS installs (from the POV of the machine) to do it sanely
00:10marcanright *now* it doesn't matter much and you can do what pipcet[m] says and just stuff m1n1 on top of a single macOS install
00:10pipcet[m]when in doubt, listen to marcan :-)
00:10MTecknologywhew... if I were still drinking (unfortunate project name for me... many fond memories where that beer was involved), I'd be grabbing a few cans of asahi to drink while reading the guide
00:11marcaneventually there will be some curl|sh thing that does everything for you :)
00:11alyssateetotalist noises
00:11marcananyway, the dual boot thing will start mattering soon, among other things because I'm going to be requiring people to use specific macOS versions as a base (for firmware ABI reasons; it's unstable) and because the SEP will be very unhappy if two OSes try to use the security stuff in one context
00:12marcanbasically Apple designed the thing for dual-boot at *their* level and we have to use it if we want to keep things sane :)
00:12MTecknologyWhy do I suspect that even underneath, they treat every minor revision number as an excuse for absolutely any changes they feel like?
00:13marcanhalf the firmwares are part of the OS boot bundle, so yes, they don't care about stability
00:13MTecknologyjust like golang! :P
00:13marcanin fact, uh, I've been ranting about this recently but the way they did their display controller firmware is to just take their driver and move *half* of the classes to firmware, then build an RPC mechanism that lets them call back methods on the other side, in both directions, with multiple execution threads even
00:14marcanso it's literally an IOKit driver split down the middle, one side in firmware
00:14marcanyou can imagine how stable that is :p
00:14marcan(and yes this is going to be fun to support in linux)
00:14marcanthis is why I've decided there will be "blessed" macOS bootloader bundles (=firmware bundles) that Linux supports
00:15marcanno way I'm handling every time they touch the ABI in a point release
00:15marcanthankfully none of this matters if you do native dual-boot, as the OSes have separate bundles, so the real macOS install can be updated separately
00:16marcanthe eventual installer will prompt you for a bundle/version to use out of the list of blessed ones, and handle installing all that without involving a full macOS install
00:17marcanand the idea is that it'll prompt you for a distro image to install out of a list of supported ones (whatever people feel like maintaining), or you can just install the base m1n1+u-boot and make space on the partition table, and then handle the actual distro install like on any other ARM64 UEFI system, since you could boot from USB after that point
00:19MTecknologyany thoughts toward disk encryption? Will it be possible to use native mac utilities for that?
00:20* MTecknologyis getting excited and starts going through the documentation
00:20marcanI'm not sure how that's done at the NVMe level, but at the very lease you could hook the SEP into dm-crypt and get secureboot-tied disk encryption that way
00:20marcanusing the native acceleration would require more research
00:21marcanI think macOS does some fun stuff with per-file keys and such, or can (for iOS use cases), which is one reason why they extended (=broke in incompatible ways) their NVMe implementation
00:22marcan(this isn't new, the x86 macs with T2 already had this)
00:22marcaneventually I want to get PAM integration with the SEP so you can use hardware password verification, Touch ID, and all that from linux
00:23marcanparticularly interested in whether we can us ed25519 keys in that framework; right now you can create ecdsa ssh keys on macOS backed by the SEP, because that's all their user API supports, but I think the low level API probably does ed25519 too
00:32alyssamarcan: itmt
00:32alyssaDCP stream? 👀
00:32marcanbreakfast first :p
00:39MTecknologyrevive, eh?
00:40MTecknologythat's an interesting feature only possible by limiting the hardware your OS can run on
00:42MTecknologywow... I now wish I got the 500GB model.
00:48MTecknologyAccording to the disk utility, I'm only using 15.4 GB. Can I just make my first command 'diskutil apfs resizeContainer disk0s2 50GB' instead and leave the rest the same?
00:49marcanMTecknology: 50GB is not enough to update macOS
00:49marcantheir updater is insanely inefficient
00:49marcanyou need at least 70GB to keep it updatable
00:50marcanre: revive, all the DFU stuff is already supported on linux with idevicerestore
00:50marcanif you totally brick the thing (= wipe nvme including 1TR), you need to restore that way
00:51marcanwhich means plugging it into another linux box with a USB cable and running idevicerestore, for us :)
00:51marcanthankfully the libimobiledevice guys already implemented M1 support into it some time ago
00:53MTecknologythere isn't going to be a whole lot of room for linux after 70 for the main os plus 70 for the stub... I had planned (and might still plan on) trying to run my work VM from within linux on this hardware.
00:54MTecknologyI'll just appreciate it that much more when it's no longer needed. :D
00:59MTecknologycrud, I didn't read far enough in advance of running commands and just ran the addPartition commands. I didn't realize I should have been looking at diskutil list to figure out what the right disk name was.
01:00alyssaraise your paw if you're sleepy shepherd 🐶
01:01MTecknologyI /think/ it looks like the docs are perfect for a default setup so they worked anyway. At least, I see that the LR volume created is 104 GB, which is what I expected. 70+70+1+104 == 245 ~= 250 GB
01:02* MTecknologyreads more betterer from now on
01:02MTecknology(+5 GB recovery)
01:03alyssaMTecknology: my chromebook is 32gb and it's good
01:03alyssa100gb for linux sounds delux
01:04MTecknologyRDR2 is already over 100 GB, and you can't expect me to not be playing that through linux on M1, can you?
01:05alyssamarcan: Is it safe to downsize to the stub partition post install btw?
01:06MTecknologyred dead redemtion 2; a game that actually has better performance through valve's compatibility layer than on native windows
01:09milek7and crashes every 2 hours
01:11MTecknologylucky bastards... once it starts crashing for me, it doesn't stop crashing. At best, I might get 5 minutes without rebooting back into windows and back into linux to clear whatever with nvidia
01:11MTecknologyor something like that... irunno
01:12MTecknologyWhen it actually works, I can get weeks of play time (I leave it loaded once it's working) without a crash.
01:15MTecknologyWhat crash were you referring to?
01:15marcanalyssa: yes, but you won't be able to update it further
01:16marcanthough at this point, by the time I start writing the DCP driver and fixing the firmware version required, I'll probably spend a few days writing an install/update script that can avoid having to do a full macos install
01:16marcanbeen thinking a lot about that in the background, just haven't started writing the code :)
01:17marcanmrkajetanp_: eventual stubs will be <5GB
01:17marcanjust needs to be enough for the paired recovery (new thingy required in 12.0...) and the bootloader/firmware blobs
01:17marcaner , MTecknology
01:21flying_sausages has quit []
01:22flying_sausages has joined #asahi
01:29MTecknologyyep, that'll be quite the savings indeed
01:42chadmedmarcan: 70GB? i cant believe how inefficient macos has become. i remember back in the day when i got snow leopard running on my phenom ii pc off a single layer installer dvd and a 16gb root partition. bringing across all the ios apis really has been a mistake
01:49alyssamarcan: Cool. Speaking of, did you eat breakfast? 😇
02:10MTecknologyThe craziest part of 70 GB is how the final install isn't /that/ big.
02:10hashcheck has joined #asahi
02:12chadmedmacos userspace is based on gentoo now, and so it requires space for all the sources to be downloaded and built :-P
02:26MTecknologyawe... "If everything went well, you can restart and boot into m1n1!" --> "Custome kernel failed to boot."
02:27MTecknologyoh, I missed a step, where was that..
02:29MTecknologyah, the thing I thought I missed was the environment variable for the other option.
02:31PhilippvK has joined #asahi
02:34phiologe has quit [Ping timeout: 480 seconds]
02:56hashcheck has quit [Quit: Textual IRC Client: www.textualapp.com]
03:19marcanchadmed: it's their updater. it has to download the update once, then install it to a snapshot, on top of the existing OS
03:19marcanso that's 3 copies if you're counting
03:19marcanand I think there's probably another one needed for some silly reason
03:20marcanalyssa: I did now :p
03:20alyssamarcan: Nom
03:58klangelooking forward to finally joining the club... between august 9th and 11th, because I had to have an US-QWERTY keyboard instead of a JIS one that would have been in stock locally... also maybe that joke about 'm1 toaruos when' might be less of a joke
04:27yuyichao_ has quit [Ping timeout: 480 seconds]
05:07yuyichao has joined #asahi
05:07quarkyalice has joined #asahi
05:51quarkyalice has quit [Ping timeout: 480 seconds]
05:51bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:14svenmarcan: no, it isn't. that's where the hack part comes in ;)
06:14marcansven: lol, then what is it?
06:14marcanlike a binlog?
06:14svenit's called Log just because it also needs a buffer
06:14svensomething like that, yes
06:15marcanis the ring buffer structure the same?
06:15svenjust that get buffer request is the same
06:16svenkdebug is more fun i think. it should contain tracepoints somehow
06:17svenalso, please double check the endpoint id -> class assignment. iirc they were wrong at some point and i'm not sure i fixed them
06:18svenand i think it'll be fine for dcp probably, but syslog is a little bit more complex
06:18sventhe init message sends a max number of entries and the length of the syslog messages
06:19svenit's not just constant 0xa0 or whatever
06:20marcanI know that
06:20marcanthat's in the tracer
06:20marcanwhich you didn't share code with :D
06:20svenoh, is it? but then you fixed it at some point
06:20svenit used to be constant 0xa0 in there
06:21svenit's hardcoded for dcp
06:21svenbut it's different for other asc
06:22svendoesn't matter for DCP unless they change it ;)
06:23sven#define APPLE_RTKIT_SYSLOG_N_ENTRIES GENMASK(7, 0)
06:23sven#define APPLE_RTKIT_SYSLOG_MSG_SIZE GENMASK(31, 24)
06:24svenmarcan :further down
06:25svenand the 0x80 is the msg size
06:25sven+ the header which is always 0x20
06:25sven0x80 + 0x20 = 0xa0
06:26svenmarcan: 31, 24
06:26sven(might be larger, but who knows)
06:35svenmarcan: i think at least 3 is wrong there fwiw
06:36sveni think crash is 1
06:36svenand 3 is this kdebug thing
06:39sveni think if you don't start some it'll hang
06:40sven(at least for the system endpoints)
06:47hashcheck has joined #asahi
06:52MTecknologyhrm... where was I, before my cat decided to get hurt and crap all over a room (plus a vet visit)?
06:55MTecknologyI have my mac mini booted up to m1n1 with the last line saying 'Running proxy...' I built linux from the asahi/linux branch, grabbed the debian initrd, and.... I'm getting a python error. Definitely not the kind of error I expected getting so close to what should be actually running something.
07:02svenmarcan: send 0x22 or 0x40 to the crashlog ep
07:02sventhat's "force crash"
07:02svenwith 0x40 it even survives
07:02svenit'll just send a crashlog and continue
07:03jixMTecknology: the pypi package is called pyserial not serial AFAICT
07:03MTecknologyrm -rf ~/.pip_dir; then replacing that pip install serial w/ pyserial seems to have worked. Now it's complaining about 'could not open port /dev/ttyACM0:' which I imagine has to do with the thunderbolt cable or something.
07:03MTecknologyjix: nice, thanks! :)
07:04svenmarcan: just after the DART
07:04svendart offset + 0x4000 or so
07:04svenit's not in the device tree though but i believe that's this DAPF thing
07:05svendepends on the device
07:05sveniirc TLB cache thing was before?
07:05MTecknologyWith this thing booted up to m1n1, if I connect my (linux) laptop to the thunderbolt port closest to the power plug using a cable that I'm super confident is a proper thunderbolt cable (but possibly not that spec thing...), should I expect to see something showing up in dmesg?
07:06MTecknology(spec thing --> SBU1/2 pins)
07:07MTecknologyI had two 4k displays running using this same cable, so I'm pretty confident about everything except that bit.
07:07marcanMTecknology: you don't need to use any fancy cables for USB mode, which I presume is what you want to use
07:07marcanthat's only if the other side is another M1 Mac and you want serial
07:07_jannau_connect the cable before booting the mac mini
07:07marcanany standard USB cable will do
07:07svenmarcan: my notes say the regs might be [config, sid, start (64bit), end (64bit)]
07:08svendunno how accurate that is
07:08MTecknologyYeah, usb mode
07:08sveni never got this to work correctly
07:10MTecknologyooooh, there's the usb device!
07:10_jannau_MTecknology: the cable needs to be connected before booting the mac mini
07:11svenmarcan: can you check if you can write these? i believe the DAPF lockdown bit is different from the DART lockdown bit
07:11MTecknologyaye, thanks for mentioning that. I just got to the installer! :D
07:12bisko has joined #asahi
07:13svennot sure if that's correct :D
07:13MTecknologyno keyboard... I saw something about not being able to use the on-board usb-a ports, so I thought using my dock (thunderbolt/usb-c) would work.
07:14svenso on ANS it asks for a physical address and then also sends the same one back but that's expected because it goes through SART
07:14marcandocks definitely won't work
07:14marcanthere is no thunderbolt support
07:14marcannor is USB-PD really in shape
07:14svenon SMC it never asks for an address, it just sends me an address in that mmio shared memory window
07:14marcanyou should use a dumb USB hub
07:14_jannau_MTecknology: thunderbolt/pci-e will not work. USB-C should work but has the same contraint of being connected at boot
07:16svenmarcan: i think i messed up the endpoints :D
07:16svenmaybe 3 gets the two messages
07:16svenremember how i called this a "hack"? :P
07:16sventhat crash_soft/hard should go into crashlog though
07:19MTecknology_jannau_: I assume that means "usb-c should work, but not via any usb-c/tb dock"?
07:22MTecknologyI don't have any hub, and the one I used to have was flaky on the best of days. I was going to live with just the keyboard if it had to be connected at boot, but my only usb-a->c adapter is one of those tiny things, so... thanks to apples brilliant orientation of those ports, I can only stick exactly one device in the port closest to the power plug.
07:23MTecknologywhich I need for booting up, so... it seems to proceed further I kinda have to get that dumb hub.
07:24MTecknologyMost docks are basically just a not-dumb usb hub, aren't they?
07:27_jannau_MTecknology: a tb dock will not work unless it can be somehow forced into usb3 mode on the dock side
07:29MTecknologyheheh... that just made me wonder if I can "force" it to usb3 mode by using a cheap cable.
07:29MTecknology(cheap + no tb claim)
07:32_jannau_the hub looks like it is USB 3.0 only and should work fine
07:33svenmarcan: 32 bit at most
07:33sventechnically it can do more
07:33svenbut i haven't seen any device with more than 32 address lines connected
07:34svenin an older iphone there's a DART with 4k pages which required more iirc
07:34sventhere's even a bypass DAPF bit in the TCR fwiw
07:41MTecknology_jannau_: excellent, it'll be here on tuesday :)
07:43* MTecknologyshould make some docs notes now before forgetting where I stumbled... may as well make a pull request from all of the extra help/info. :)
07:50aleasto has joined #asahi
08:14amwAre all these modules asc, dcp purely tracing functions at the moment?
08:35bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:36ella-0[m] has joined #asahi
08:36bisko has joined #asahi
08:40bisko has quit []
08:41bisko has joined #asahi
08:43bisko has quit []
08:48bisko has joined #asahi
09:00bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:09hashcheck has quit [Quit: Textual IRC Client: www.textualapp.com]
09:15norwoodites has joined #asahi
09:16pinskia has quit [Remote host closed the connection]
09:53pinskia has joined #asahi
09:59norwoodites has quit [Ping timeout: 480 seconds]
10:56bisko has joined #asahi
11:49marcanI'll jump back on stream shortly
12:06svenyou can also NMI the coprocessor if the crashlog msg is too slow fwiw. write32(asc_base + 0x10004, 0x11) followed by write32(asc_base + 0x10024, 0x1) i think
12:33cth451_desktop has quit [Remote host closed the connection]
12:33cth451_desktop has joined #asahi
12:50dougallanyone know if it's possible to load modified AGX (or other) firmware? I'm not clear on whether or not that's a security boundary
12:51marcandougall: unlikely
12:51marcanI think everything preloaded by iBoot is locked
12:51alyssaso what's the agx firmware buddy about
12:51marcanold code
12:51marcanfrom before they started doing this
12:52alyssaapple sure are special
12:52marcanthere's also a whole display driver that doesn't use DCP, you know
12:52alyssamarcan: The good news is that with all this firmware tucked away in iBoot, Asahi GNU/Linux-libre will be FSF endorsed 😂
12:52marcanas long as you don't want wifi
12:53alyssait's a mac mini
12:53alyssawhy would i want wifi
12:55_jannau_or bluetooth
12:56klangewhy is wifi so universally cursed... [don't answer that, I know it's radio transmission laws / paranoia about them]
12:58pipcet[m]I'm a bit surprised Apple actually licensed a broadcom chip instead of doing their own thing entirely, though.
13:00marcanit's not licensed, it's just a broadcom chip
13:00marcanthey've been using broadcom for wifi since time immemorial
13:00marcan(and for other things)
13:01dougall(thanks - bit of a shame from the perspective of exploring the hardware, but probably to be expected since that's effectively what intel and nvidia do)
13:02pipcet[m]it's a broadcom chip that's decidedly weird compared to the others, though, and I don't think that's just different firmware
13:03marcanapple have also been customizing firmware for ages (see: AirDrop etc)
13:04_jannau_in addition developing their own 5G modem has probably much higher priority than wifi/bt
13:06Ariadneprobably not
13:06Ariadnethere’s no business case for it
13:06alyssaAriadne: apple fabs otoh...
13:06Ariadneapple fabs i could see
13:19phireit's really hard to start a fab, would take years
13:19phireTSMC would know the whole time that apple was 'replacing' them
13:22alyssa phire: Even if they did know... boiling frog, right?
13:23phireas far as I know, TSMC aren't vindictive or anti-competive
13:23alyssabecause they have no viable competitors? :P
13:23phireThey are current fabbing intel chips
13:33phireI do wonder if Apple gets paranoid in their interactions, assuming that other companies will treat Apple like they treat everyone else
13:50Ariadnemodems though, like there are many options that are good on the market now (almost all from qualcomm :p)
13:50Ariadnedoesn’t make sense to make a modem
13:50Ariadneintel has some decent SKUs too
13:50Ariadnequectel also, but apple won’t ever use quectel
13:54cth451_desktop has quit [Remote host closed the connection]
13:55cth451_desktop has joined #asahi
14:04pinskia has quit [Remote host closed the connection]
14:05pinskia has joined #asahi
14:08yuyichao has quit [Quit: Konversation terminated!]
14:23bps has quit [Ping timeout: 480 seconds]
14:36roxfan2 has joined #asahi
14:42roxfan has quit [Ping timeout: 480 seconds]
14:42roxfan has joined #asahi
14:44roxfan2 has quit [Ping timeout: 480 seconds]
14:59alyssa /join #dri-devel
15:00yuyichao has joined #asahi
15:06bps has joined #asahi
15:06arndAriadne: I don't think Intel has any modem development left, maybe they just retained the rights to keep selling the old SKUs to existing customers?
15:07Ariadneno idea. most of the modems we deal with in alpine are either quectel or qualcomm
15:08Ariadnetho i could be wrong on that claim, should verify with the pmOS crew to see what their picture looks like
15:09arndI thought quectel just uses qualcomm chips
15:15Ariadnethey might
15:16Ariadnethey do use qmi
15:16Ariadnei assumed they were knockoff chips
15:16arndIIRC most others that build their own chips (spreadtrum->unisoc, samsung, via->intel, infinion->intel->apple, hisilicon, mediatek) license the DSP plus 4g/5g software stack from CEVA
15:22Ariadnei mean i just interact with these things, i admittedly don’t fully understand the supply chain
15:33bps has quit [Ping timeout: 480 seconds]
15:33alyssamarcan: You'll need to swap/present
15:34alyssa(to "flush" the changes)
15:35hablerentand[m]What USB-C to USB-A adapter/hub do you use for keyboard support? I still have not been able to get the USB keyboard to work on my mac mini, and I'd like to rule out that it is not an adapter issue. Thanks in advance!
15:35alyssamarcan: Otherwise if you change multiple properties in a row and you're unlucky with the timing w.r.t vsync you'll get a junk frame in the middle
15:36Spectrejan[m] is now known as GatekeeperJanwithoutBeer[m]
15:40alyssanot just the "first swap", I expect a swap is needed for changing any property at any time
15:40alyssabecause, again, junk otherwise.
15:40svenhablerentand[m]: preferably some adapter that's as dumb as possible
15:43svenessentially only usb 2 works until i get around to writing the full phy driver
15:45svenunrelated to that, can i just download some $random-distro userland from somewhere? i wanna use nvme-cli and adding that to my initrd sounds painful
15:45alyssasven: arch linux arm has a generic arm64 rootfs
15:45svenperfect!
15:46alyssadidn't try on the M1 but should Just Work if you're supplying the kernel
15:46svensounds good. i should probably also switch to a sane .config though
15:54alyssasven: I posted mine yesterday, it's yours with working systemd and usb net
15:56svenok. let's see.
15:58sven[ 0.448653] apple-mailbox 277400000.mbox: syslog message: nvme_admin_ans2.c:2729: Invalid namespace 0 <-- i wonder what that's about. afaik this, 0 should be valid namespace :/
15:59sven*as far as i understand this
16:17pipcet[m]really? I have no namespace 0 on the M1, and no namespace 0 on the intel machine...
16:23bps has joined #asahi
16:26svenoh.... it starts at 1 :D
16:26svenyeah, okay, that epxplains it
16:26sven*explains
16:28jannausven: https://gist.github.com/jannau/0af6697bb8b08a847ecc32a8a3d3a4f2 is based on the arch linux arm distro config
16:28jannauthe generic arch linix arm rootfs works without problems
16:30alyssasven: duh, it's M1, not M0 /s
16:38svenah, ofc!
16:59jbowen has quit [Quit: leaving]
18:42robinp has quit [Remote host closed the connection]
19:37bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:37bisko has joined #asahi
19:44bisko has quit [Quit: Textual IRC Client: www.textualapp.com]
20:00Raqbit has joined #asahi
20:40aleasto has quit [Ping timeout: 480 seconds]
20:40aleasto has joined #asahi
20:47svenpipcet[m]: you've had some issues with nvme, haven't you? any simple way to reproduce them?
20:47sven'cause i've been trying to break it but it's been surprisingly stable so far
20:48sventhe worst i managed to do were these syslog message when trying to read from one of the other two namespaces:
20:48svenapple-mailbox 277400000.mbox: syslog message: util.c:4121: element=PANICLOG written size=2097152, host request trimmed to end of written content
20:48svenapple-mailbox 277400000.mbox: syslog message: util.c:4145: Util read unmap element: 8, lba: 512, size : 24
21:28roxfan2 has joined #asahi
21:34roxfan has quit [Ping timeout: 480 seconds]
21:42kenzie has quit [Quit: The Lounge - https://thelounge.chat]
21:48kenzie has joined #asahi
22:19grange_c has quit [Ping timeout: 480 seconds]
22:19hl` has joined #asahi
22:30grange_c has joined #asahi
23:29aleasto has quit [Quit: Konversation terminated!]
23:40alyssasven: +"coprocessor sent shmem buffer with 0x%zx bytes at 0x%llx outside of the configured region 0x%llx...0x%llx",
23:40alyssaPRIx64 instead of %llx methinks
23:40alyssathough i guess the kernel has prior art for either
23:42alyssa+/* A2I = Application Processor (i.e. we) to I/O Processor (i.e. usually RTKit) */
23:43alyssaNit: change (i.e. we) to (us) and (i.e. usually RTKit) to (usually RTKit)
23:59yuyichao has quit [Ping timeout: 480 seconds]
…