●● IRC: #techbytes @ Techrights IRC Network: Wednesday, February 28, 2024 ●● ● Feb 28 [00:33] *Enviosity has quit (Ping timeout: 120 seconds) [00:39] *Enviosity (~Enviosity@freenode-2ue.6ih.pu7h8v.IP) has joined #techbytes [00:50] *u-amarsh04 has quit (Quit: Konversation terminated!) [00:55] *u-amarsh04 (~amarsh04@qezxp5nudz5uq.irc) has joined #techbytes ● Feb 28 [01:42] *Enviosity has quit (Ping timeout: 120 seconds) [01:50] *Enviosity (~Enviosity@freenode-2ue.6ih.pu7h8v.IP) has joined #techbytes [01:54] *Disconnected (Connection reset by peer). [01:54] *Now talking on #techbytes [01:54] *Topic for #techbytes is: Welcome to the official channel of the TechBytes Audiocast [01:54] *Topic for #techbytes set by schestowitz!~roy@haii6za73zabc.irc at Tue Jun 1 20:21:34 2021 [01:55] *schestowitz-TR2 (~acer-box@freenode/user/schestowitz) has joined #techbytes [01:55] *schestowitz-TR2 has quit (Quit: Konversation term) [01:55] *rianne has quit (Ping timeout: 120 seconds) [01:55] *schestowitz-TR has quit (Ping timeout: 120 seconds) [01:56] *libertybox__ (~schestowitz_log@24axkg87jqny6.irc) has joined #techbytes [01:56] *asusbox2 (~rianne@24axkg87jqny6.irc) has joined #techbytes [01:56] *rianne (~rianne@24axkg87jqny6.irc) has joined #techbytes [01:56] *rianne (~rianne@freenode-54p.goo.k31cok.IP) has joined #techbytes [01:56] *Techrights-sec (~quassel@24axkg87jqny6.irc) has joined #techbytes [01:56] *logbackup (~quassel@24axkg87jqny6.irc) has joined #techbytes [01:58] *liberty_box (~liberty@24axkg87jqny6.irc) has joined #techbytes ● Feb 28 [04:48] *jacobk has quit (Ping timeout: 2m30s) ● Feb 28 [05:13] *jacobk (~quassel@6wygwq2t5e2hw.irc) has joined #techbytes [05:25] *jacobk has quit (Ping timeout: 2m30s) [05:44] *jacobk (~quassel@838aynky6btpe.irc) has joined #techbytes ● Feb 28 [08:27] schestowitz[TR2]
  • [08:27] schestowitz[TR2]
    India continues to innovate homegrown RISC-V, launches Aries 3.0 board with an onboard Vega ET1031 CPU
    [08:27] schestowitz[TR2]
    [08:27] schestowitz[TR2]

    Now, let's talk about those specs. The CPU is 32-bit and operates at up to 100 MHz, using only 256 KB of SRAM. This doesn't come close to competing with modern Raspberry Pi solutions, but will probably be more than enough for the intended applications in IoT, toys, and so on. Some devices only need the most basic of processing.

    [08:27] schestowitz[TR2]
    [08:27] schestowitz[TR2]
    • [08:27] -TechBytesBot/#techbytes-www.tomshardware.com | India continues to innovate homegrown RISC-V, launches Aries 3.0 board with an onboard Vega ET1031 CPU | Tom's Hardware ● Feb 28 [09:23] *jacobk has quit (Ping timeout: 2m30s) [09:52] *u-amarsh04 has quit (Quit: Konversation terminated!) [09:58] *u-amarsh04 (~amarsh04@qezxp5nudz5uq.irc) has joined #techbytes ● Feb 28 [10:03] *jacobk (~quassel@32hz32it3ih2k.irc) has joined #techbytes [10:03] schestowitz[TR2] 2 [10:03] schestowitz[TR2] 3 [10:03] schestowitz[TR2] 4 [10:03] schestowitz[TR2] 5 [10:03] schestowitz[TR2] 6 [10:03] schestowitz[TR2] 7 [10:03] schestowitz[TR2] 8 [10:03] schestowitz[TR2] 9 [10:03] schestowitz[TR2] 10 [10:03] schestowitz[TR2] 11 [10:03] schestowitz[TR2] 12 [10:03] schestowitz[TR2] 13 [10:03] schestowitz[TR2] 14 [10:03] schestowitz[TR2] 15 [10:03] schestowitz[TR2] 16 [10:03] schestowitz[TR2] 17 [10:03] schestowitz[TR2] 18 [10:03] schestowitz[TR2] 19 [10:03] schestowitz[TR2] 20 [10:03] schestowitz[TR2] 21 [10:03] schestowitz[TR2] [10:03] schestowitz[TR2] 13:03 < Sompi_> Now I also noticed that on some BIOSes the boot drive number is randomly sometimes 0x80 and sometimes [10:03] schestowitz[TR2] 0x00 when booted from a USB storage stick. The number seems to be consistently the same for the same USB [10:03] schestowitz[TR2] stick and BIOS but otherwise seemingly random [10:03] schestowitz[TR2] 13:04 < Sompi_> It is a problem, because if the boot driver number is 0x00, the kernel assumes that it is booted from a [10:03] schestowitz[TR2] floppy, and does not even try using LBA or detecting the disk geometry using int13,8. Then it tries to [10:03] schestowitz[TR2] use the geometry in the FAT boot sector that of course does not work, because it is not the real geometry [10:03] schestowitz[TR2] for the USB stick. [10:03] schestowitz[TR2] 13:05 < Sompi_> How the hell do I fix that... [10:03] schestowitz[TR2] 13:06 < Sompi_> How can the USB booting be so broken on so many modern BIOSes [10:03] schestowitz[TR2] 13:07 < Sompi_> Those BIOSes just randomly decide to assign drive number 0x00 for some USB sticks, and number 0x80 for [10:03] schestowitz[TR2] some others [10:03] schestowitz[TR2] 13:07 < Sompi_> And according to the BIOS specification 0x00 should ONLY be used for floppy drive 0 [10:03] schestowitz[TR2] 13:18 < Sompi_> And because floppies are soft sectores and the BIOS doesn't know anything about their geometry, the [10:03] schestowitz[TR2] kernel has to work differently with them than it does with hard drives [10:03] schestowitz[TR2] 13:37 < Sompi_> And also those BIOSes often report that the computer has one (1) floppy drive, when in reality it has [10:03] schestowitz[TR2] none, and that breaks even more things [10:03] schestowitz[TR2] 13:42 < Sompi_> So: The BIOS reports that the computer has a floppy drive, when in reality it doesn't. The BIOS also [10:03] schestowitz[TR2] assigns drive number 0x00 to the USB drive that it's booting from. How should the kernel know that the [10:03] schestowitz[TR2] drive 0x00 is NOT the floppy drive that actually doesn't even exist, but instead a USB storage device [10:03] schestowitz[TR2] that has a hard-coded geometry that must be determined with BIOS int13,ah=8? [10:03] schestowitz[TR2] 13:42 < Sompi_> ACPI is not a solution, because it is also utterly broken on many implementations [10:17] *schestowitz-TR2 (~acer-box@24axkg87jqny6.irc) has joined #techbytes [10:38] schestowitz[TR2] > Hi Roy, hope all goes well with you. Your RSS should be [10:38] schestowitz[TR2] > picking up four new blog posts onhttps://cybershow.uk/blog/ [10:38] schestowitz[TR2] Thanks, [10:38] schestowitz[TR2] those will go into the next batch of Daily Links in techrights (later this morning). [10:38] schestowitz[TR2] Is our new site penetration-viable? [10:38] schestowitz[TR2] Regards, ● Feb 28 [12:12] *jacobk has quit (Ping timeout: 2m30s) ● Feb 28 [13:31] *psydroid2 (~psydroid@u8ftxtfux23wk.irc) has joined #techbytes [13:52] *jacobk (~quassel@8vbirkqvn4duc.irc) has joined #techbytes ● Feb 28 [14:02] *jacobk has quit (Ping timeout: 2m30s) [14:20] *jacobk (~quassel@8vbirkqvn4duc.irc) has joined #techbytes ● Feb 28 [15:01] *jacobk has quit (Ping timeout: 2m30s) [15:33] *schestowitz-TR2 has quit (Ping timeout: 2m30s) [15:38] *roy has quit (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) [15:38] *roy (~quassel@24axkg87jqny6.irc) has joined #techbytes [15:39] *schestowitz-TR (~acer-box@24axkg87jqny6.irc) has joined #techbytes [15:39] *schestowitz-TR (~acer-box@freenode/user/schestowitz) has joined #techbytes ● Feb 28 [18:11] *parsifal (~parsifal@uuar9r28yasyu.irc) has joined #techbytes ● Feb 28 [22:00] *psydroid2 has quit (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/) ● Feb 28 [23:32] *Noisytoot has quit (Ping timeout: 2m30s) [23:33] *Noisytoot (~noisytoot@tkbibjhmbkvb8.irc) has joined #techbytes [23:37] *jacobk (~quassel@6wygwq2t5e2hw.irc) has joined #techbytes