| buZz | > An implementation of the UEFI API was introduced into the Universal Boot Loader (Das U-Boot) in 2017.[75] On the ARMv8 architecture Linux distributions use the U-Boot UEFI implementation in conjunction with GNU GRUB for booting (e.g. SUSE Linux [76]), the same holds true for OpenBSD.[77] For booting from iSCSI iPXE can be used as a UEFI application loaded by U-Boot.[78] | 00:18 |
|---|---|---|
| buZz | seems to only exist on armv8? not sure | 00:19 |
| buZz | [edit] | 00:24 |
| buZz | Intel's first Itanium workstations and servers, released in 2000, implemented EFI 1.02. | 00:24 |
| buZz | Hewlett-Packard's first Itanium 2 systems, released in 2002, implemented EFI 1.10; | 00:24 |
| buZz | all that stuff is just retro enterprise :P | 00:25 |
| brolin_empey | At least on x86, Windows 10 and Windows Server 2019 can still be installed and run on a computer using BIOS instead of EFI but apparently you are discussing Windows NT 10 for ARM, not x86. | 08:28 |
| brolin_empey | Regarding what I said about the apparent demise of non-EFI motherboards somewhere after Nehalem, according to https://en.wikipedia.org/wiki/Template:Intel_processor_roadmap there are “no more non-UEFI motherboards” beginning with or after (?) Sandy Bridge. | 08:31 |
| Vajb | does any of you use any one drive client in linux? | 09:08 |
| sicelo | gmail's spam filter sucks. outlook's one is way more accurate. hope these instructions actually work for disabling gmail's filter, https://c-command.com/spamsieve/help/turning-off-the-gmail-s | 10:02 |
| sicelo | i don't know if you guys saw this, https://arstechnica.com/gadgets/2019/11/google-outlines-plans-for-mainline-linux-kernel-support-in-android/ | 10:02 |
| brolin_empey | sicelo: Every time I register a new account for something that will or may email me I usually create a new filter in my Google Mail account that says to never mark mail from the new sender for the new account as spam because otherwise ham ends up in spam because of false positives of the Google Mail spam filter. | 10:44 |
| brolin_empey | Not that it matters because I rarely play any computer game at all any more, never mind recent demanding games, but would a desktop computer with a Core i7 920 model of CPU, one of the original models of Core i7 from 2008 November, still suffice for running something like, say, Overwatch with an SSD and a somewhat recent video card? I think I have still never even tried running any local/native (not Web-based) game full-screen since I upgraded to a | 10:51 |
| brolin_empey | 3840×2160 4k UHD video monitor. | 10:51 |
| brolin_empey | I ask because apparently a refurbished desktop computer with Core i7 920 CPU, 16 GiB of main memory, 480-GB SSD, Wireless LAN controller, DVD±RW drive, some unspecified ATI video card, apparently a genuine licence for Windows 10 Professional for x86-64 sells for only 299 CAD excluding taxes but including shipping to Canada: | 11:20 |
| brolin_empey | https://www.amazon.ca/dp/B07RQW1PH6/ref=sspa_dk_detail_1?psc=1&pd_rd_i=B07RQW1PH6&pd_rd_w=9oPCr&pf_rd_p=4b7c8c1c-293f-4b1e-a49a-8787dff31bcb&pd_rd_wg=EW9h2&pf_rd_r=FRPKZVB4FJYJBCGJV6MN&pd_rd_r=acbd0125-8703-4104-b98e-a7f40b44e1ec&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEzN05PTlpERjBJQ1Q0JmVuY3J5cHRlZElkPUEwMzMwNTcyUklINlFQOFlMTzlXJmVuY3J5cHRlZEFkSWQ9QTAxNzEzMTMxQUU4SklJV1M2TVFUJndpZGdldE5hbWU9c3BfZGV0YWlsJmFjdGlvbj1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ== | 11:20 |
| brolin_empey | Yes, unfortunately it probably has at least one or two fans. It is my father, not me, who is shopping for a “new” computer. I would still rather have a fanless x86-64 computer because having a literally silent computer is awesome when you are used to always hearing a fan in a computer. | 11:43 |
| brolin_empey | Well, considering that the TDP rating of the CPU is 130 W, I guess it almost certainly has a fan on at least the CPU heatsink. | 11:44 |
| buZz | fanless 130W cpus , haha | 11:48 |
| brolin_empey | buZz: Well, a 100 W incandescent light bulb is used without a fan. | 11:50 |
| buZz | those are illegal here nowadays | 11:52 |
| brolin_empey | Because of the energy consumption or the fire risk? | 11:54 |
| Maxdamantus | The energy consumption, surely. | 11:55 |
| * Maxdamantus suspects LED bulbs would generally be a greater (though still fairly insignificant) fire risk. | 11:56 | |
| Maxdamantus | actually, nvm, that's probably not true. | 11:56 |
| Maxdamantus | actually, dunno, it might be. | 11:56 |
| Maxdamantus | because afaik LED bulbs usually just rectify the mains power, and if you end up with arcing, it's more likely to pose a fire risk on DC. | 11:57 |
| Maxdamantus | but the arcing would likely have to result from a short circuit, since they obviously don't normally use much current. | 11:58 |
| buZz | brolin_empey: energy, yeah | 11:59 |
| buZz | afaik they are still legal as heat sources | 11:59 |
| buZz | but not as lights | 11:59 |
| brolin_empey | Does a self-ballasted compact fluorescent lamp have to convert the AC from the lamp socket to DC? Or does it only use AC? | 12:04 |
| Maxdamantus | I think fluorescent lamps use high-frequency AC. | 12:05 |
| brolin_empey | If a fluorescent lamp uses alternating current, does that mean that a computer with a display with a fluorescent backlight, such as old computers with an integrated LCD that uses a CCFL backlight, has to convert the AC from the mains power supply unit to DC used by the power input connector of the computer only for the fluorescent backlight to convert the DC back to AC? Imagine if you use an inverter to power such a computer from a vehicle: the DC from the | 12:11 |
| brolin_empey | vehicle gets converted to AC by the inverter connected to the vehicle power outlet, then the computer PSU converts the AC back to DC, then the display backlight inverter converts the DC back to AC. :-D | 12:11 |
| sixwheeledbeast | This is the reality of making devices compatible with the worlds infrastructure. Conductor materials are expensive it's a way of using less materials to the load. | 13:17 |
| sixwheeledbeast | Also ICE vehicles have AC and DC supplies | 13:18 |
| sicelo | synchronizing tasks with syncevolution & radicale works, but it's a bit useless. not sure why, but Android thinks a task meant for tomorrow is due today. beats me why DAVx5 gets the date wrong, because i can see in the syncevolution logs that the date is correct, and inspecting the vcal as stored in radicale also has correct date. | 20:36 |
| sicelo | n900 applies correct date for an event created on Android/DAVx5, just doesn't show an alarm, etc. which is to be expected. | 20:54 |
| luke-jr | why? | 21:05 |
| luke-jr | DAVx5 is working fine for me, but KOrganizer doesn't like recurring events.. | 21:06 |
| sicelo | here is a task i created on N900, http://paste.debian.net/1117506/ | 21:15 |
| sicelo | please try to import it into KOrganizer, sync with DAVx5, and see what date DAVx5 shows for you. maybe something's wrong at my end | 21:16 |
| sicelo | i think i see what's wrong here .. so N900 does not include (1) timezone info in the task file, and (2) in the DUE-DATE field, leaves the time as 00:00, since that's in the alarm, defined in an X-field. DAVx5/Android on the other hand seems to expect a timezone, and a time to be in the DUEDATE field. my timezone is UTC-2, so DAVx5 says the event is due at 22:00 the previous day | 21:30 |
| luke-jr | sicelo: sounds like a N900 bug | 22:30 |
| luke-jr | obviously without a timezone specified everything should assume UTC | 22:30 |
| sicelo | ahoy! 2do on Android is happy with the N900's tasks. so i'll use that. yay | 22:35 |
| sicelo | now if only there was something to sync Notes from calendar (radicale calls it Journal. DAVx5 doesn't support it) | 22:36 |
| Maxdamantus | $ date --date="00:00" | 22:55 |
| Maxdamantus | Sat Nov 23 00:00:00 NZDT 2019 | 22:55 |
| Maxdamantus | also, I think it's fairly typical for log files to just use the local time without denoting the timezone. | 22:56 |
| sicelo | and funny enough, Android's built it calendar has no problem reading the time from N900's vcal files, even though they also don't include timezone info. but on this device (Galaxy S7), the native calendar can't do Tasks, hence OpenTasks, which was suggested by DAVx5 | 23:02 |
| Maxdamantus | also, I imagine if anything were to not use a particular timezone, it would be an alarm. | 23:03 |
| Maxdamantus | since in general, you just want the alarm to go off at a consistent time in whatever timezone you happen to be in. | 23:04 |
| sicelo | indeed | 23:07 |
| doppler | I love it when Android's calendar just like completely fucking fails to notify you of an upcoming event, spontaneously | 23:31 |
| doppler | can you tell I have missed a few appointments because of this? >:( | 23:32 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!