Ami Sapphire's Notices
  • Login

  • Public

    • Public
    • Groups
    • Popular
    • People

Notices by Clarissa Walker (amisapphire@cwcyrix.nsupdate.info), page 7

  1. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 08-Apr-2023 23:22:59 EDT Clarissa Walker Clarissa Walker
    Started messing with my MiniDisc stuff again yesterday, mainly the Sony MZ-R900 and Sharp MD-MT831 units.

    For the Sharp unit, I wanted to know how long the original Li-Ion battery lasted: it was about 9 hours! As for the Sony MZ-R900, it was a pretty short test run. Unit is fine.

    Also redone a MiniDisc with more proper music files and created a new MiniDisc with the Sony MZ-DN430; it has been relegated to solely be a NetMD recorder now.

    Also for today, it was to test the rest of the MD portable collection. So far:

    Sony MZ-R37: fine. Previously, it was noisy, but it is quiet now. Odd.
    Sony MZ-R500: repaired corner crack near the ENTER button.
    Sony MZ-N510: fine.
    Sony MZ-E33 (black): Severe skipping on all tracks on one MD. Cleaning the lens did not work, but simply greasing the track where the laser is located worked; no more skipping.
    Sony MZ-E33 (white gold): I preemptively greased the laser track like the black version of the unit, and it is now fine.
    In conversation Saturday, 08-Apr-2023 23:22:59 EDT from web permalink
  2. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 08-Apr-2023 23:09:45 EDT Clarissa Walker Clarissa Walker
    Went back to the MIDI box yesterday. Started playing some FLAC and WAVE files and realized the music sounded a tad off; some channels were off balance.


    Stuff done to the machine so far since the last maintenance run:

    * The sound card's audio jacks needed some contact cleaner.
    * The sticky optical drive door needed rectifying.
    * The RAM sticks needed cleaning.
    * System drive defragmentation.

    Reference: http://cwcyrix.nsupdate.info/gnu-social/public/notice/55
    In conversation Saturday, 08-Apr-2023 23:09:45 EDT from web permalink

    Attachments

    1. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Friday, 31-Mar-2023 21:48:53 EDT - Ami Sapphire's Notices
      The MIDI Box running Windows 98 Second Edition on an ASUS P55T2P4 board has had a CMOS/RTC issue for about two years, and more recently had issues booting in rare occasion; also had temp corruption within BIOS (would show Unknown CPU for AMD K6-2/500). Date/Time would also revert to Jan 02 1980 at 12:00 AM (and in more recent times, while Windows was running as well), though other CMOS data remained. The board was pretty much fine before the 24-pin socket replacement, because the first replacement socket was a hack job (clipped 32-pin socket with edge bodge), and the original soldered Dallas CMOS/RTC's battery was long dead. Procedure for the board: Change CMOS/RTC to a spare - boot issues were gone though Reflash BIOS and properly clear CMOS - no real change Painstakingly remove board from old case and reflow the replacement socket - this seems to have fixed the issues It's been a little over a week, and the aforementioned issues have not yet returned.
  3. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 05-Apr-2023 10:46:24 EDT Clarissa Walker Clarissa Walker
    Total bandwidth limit on the server has been clipped a bit; rate limit remains the same, however. This shouldn't affect the response rate of the server much.

    Now, the only thing is to wait for the mid-split upgrade so the total upload would be higher than 10Mb (avg)/sec.
    In conversation Wednesday, 05-Apr-2023 10:46:24 EDT from web permalink
  4. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 04-Apr-2023 09:37:53 EDT Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    This one I caught a few hours ago: happened while archiving some Nintendo 64 ROMs.

    Miraculously, the initial transfer from two days ago did not corrupt any of them (those are big endian; also lucky, because there is no local mirror...), but copying them for the byte-swapped conversion set directly on the server corrupted one ROM in that copied set. This is becoming much less frequent, at least.

    Checked RAID5 status, array is fine. This issue shows up over a wireless network; should try wired network and local transfer... and probably examine the SATA ports on the motherboard, among other things (which I may eventually replace anyway).
    In conversation Tuesday, 04-Apr-2023 09:37:53 EDT from web permalink
  5. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 03-Apr-2023 21:01:00 EDT Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    Found the telltale sign re: bad data cable... it was on RAID5 drive 2 (layout: 0 - 1 - 2 - 3; drives are in order of manufacture date). That particular 4TB drive now has a UDMA CRC Error Count of 1, a recent happening during a bunch of large file transfers.

    Since I replaced them all, this may no longer be an issue right now.
    In conversation Monday, 03-Apr-2023 21:01:00 EDT from web permalink
  6. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 03-Apr-2023 20:05:12 EDT Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    Almost forgot, was running into some file corruption issues for some time on the rebuilt file server.

    First noticed the issue when I was creating some slipstreamed Windows XP CDs to use on the programmer machine.

    It became worse when I was transferring data to that same server to store No-Intro ROMs; almost 20 ROM archives had bad CRC errors and the GBA pack had one corrupted file which wasn't present on the main laptop.

    I eventually replaced all four data cables with some I bought a few years ago and were in storage for a bit less. Those replacements were originally meant for a compile box, but the box is now a laptop instead. ๐Ÿ˜

    I haven't run into the corruption issue since, but I'll keep watch for it. This is why I originally use an external hard drive to do initial work on, then send it to the file server later, but the external drives are not on hand right now.
    In conversation Monday, 03-Apr-2023 20:05:12 EDT from web permalink
  7. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 03-Apr-2023 19:51:44 EDT Clarissa Walker Clarissa Walker
    Finally, I have started updating my No-Intro set... from September 2018 to a more recent set, ranging from 2021 - 2023, depending on the set.

    Around January 2023, homebrew, pirate, and aftermarket stuff is no longer included by default. In my opinion, this is good, because is would be initially assumed that original commercial ROM and disk images would be present.

    However, they can be added back in with different settings. I separated the aftermarket ones from the original sets in the /alt/ directory for now; may move those to /aftermarket/. Someday, I will grab the pirate ones as well; those need different settings.
    In conversation Monday, 03-Apr-2023 19:51:44 EDT from web permalink
  8. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Friday, 31-Mar-2023 21:48:53 EDT Clarissa Walker Clarissa Walker
    The MIDI Box running Windows 98 Second Edition on an ASUS P55T2P4 board has had a CMOS/RTC issue for about two years, and more recently had issues booting in rare occasion; also had temp corruption within BIOS (would show Unknown CPU for AMD K6-2/500). Date/Time would also revert to Jan 02 1980 at 12:00 AM (and in more recent times, while Windows was running as well), though other CMOS data remained.

    The board was pretty much fine before the 24-pin socket replacement, because the first replacement socket was a hack job (clipped 32-pin socket with edge bodge), and the original soldered Dallas CMOS/RTC's battery was long dead.

    Procedure for the board:
    Change CMOS/RTC to a spare - boot issues were gone though
    Reflash BIOS and properly clear CMOS - no real change
    Painstakingly remove board from old case and reflow the replacement socket - this seems to have fixed the issues

    It's been a little over a week, and the aforementioned issues have not yet returned.
    In conversation Friday, 31-Mar-2023 21:48:53 EDT from web permalink
  9. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 02-Mar-2023 08:46:53 EST Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    Mar 2: One of the devs (Felix Fietkau) shows up. After some troubleshooting, he has eventually patched it.

    Commit:
    https://github.com/openwrt/openwrt/commit/9307c27539805de021fb7163f6ad6dc08992331b
    In conversation Thursday, 02-Mar-2023 08:46:53 EST from web permalink

    Attachments

    1. kernel: fix mtk dsa tag padding ยท openwrt/openwrt@9307c27
      The padding intended to avoid corrupted non-zero padding payload was accidentally adding too many padding bytes, tripping up some setups. Fix this by using eth_skb_pad instead. Fixes #11942. Signe...
  10. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 01-Mar-2023 06:27:27 EST Clarissa Walker Clarissa Walker
    This is what I was dealing with for the past near two months:
    https://github.com/openwrt/openwrt/issues/11942
    https://forum.openwrt.org/t/unable-to-connect-to-outside-internet-with-dumb-ap-coniguration/147483

    Timeline:
    Jan 5: Obtain Linksys E8450, convert it to OpenWrt, run into connectivity issue
    Jan 6 - Jan 14: Initial troubleshooting and notes, flash OpenWrt 22.03.0-rc1; this delays wireless network migration
    Jan 14 - Jan 16: Initial look into source code
    Jan 16: Find forum thread on OpenWrt forums
    Jan 26 -29: Second look into source code and more testing finds this issue was actually introduced in 22.03.0-rc2
    Feb 5: Issue filed
    Feb 20: workaround introduced by xNUTx
    Feb 23: someone runs into same issue on OPNsense LAN bridge
    Feb 26: xNUTx realizes they were on bridged LAN (accidental confirmation)
    Feb 27: Third look into source code finds suspect commit
    Feb 27 - Feb 28: Removing suspect commit fixes issue
    Mar 1: Fully migrated to new setup running patched 22.03.3
    In conversation Wednesday, 01-Mar-2023 06:27:27 EST from web permalink

    Attachments

    1. ARP/broadcast issues for wireless clients on Mediatek-based routers using OpenWrt as dumb AP in pfSense/OPNsense bridged LAN firewall setups on 22.03.3 release, present since OpenWrt 22.03.0-rc2 ยท Issue #11942 ยท openwrt/openwrt
      Describe the bug In OpenWRT 23.03.3, though the issue has been present since OpenWrt 22.03.0-rc2, if a Mediatek-based unit is set up as a dumb AP using this guide and is connected to a pfSense or O...
    2. Unable to connect to outside internet with Dumb AP coniguration
      Hey all, just got a pfSense router configured for my whole house, but as we already had a Belkin RT3200 with OpenWRT flashed I figured I'd reuse it as an AP. pfSense is configured on the LAN side with an Intel I350-T4 with all four ports in a network bridge (we have no switch currently, we're going to be getting one but for now we had no explicit need for one). The RT3200 is plugged into this card and therein the LAN Bridge, alongside all other LAN devices. I followed the Dummy Access Point con...
  11. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 04-Feb-2023 05:55:31 EST Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    Supposedly a FreeBSD change requires you enable link-local on bridged LAN in order for IPv6 to work since 13.0; before this version, it was not needed.

    Probably a proper check for people that do not want a link-local address showing up in devices for which the network in question is not utilizing IPv6 at all, which makes some logical sense.

    As it stands, the migration to OPNsense 23.1 is truly a success.
    In conversation Saturday, 04-Feb-2023 05:55:31 EST from web permalink
  12. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 02-Feb-2023 06:49:14 EST Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    ...Apparently IPv6 routing is broken in recent OPNsense versions with bridged LAN ports (and IPv4 to some extent) so we're back on OPNsense 21.1.9, but on an SSD instead! So a success, except for that routing problem, I guess.

    You would have to use a proper switch for extra ports from now on, at least until that issue gets fixed.
    In conversation Thursday, 02-Feb-2023 06:49:14 EST from web permalink
  13. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Wednesday, 01-Feb-2023 07:28:20 EST Clarissa Walker Clarissa Walker
    Took a while to even get OPNsense running because I couldn't remember which USB stick was which in BIOS, lol. One of them actually says PMAP; quite confusing, really.

    The migration to OPNsense 23.1 was a success. The firewall now uses an SSD that is GPT/EFI partitioned instead of an HDD that is MBR/BIOS partitioned.

    Now I can use the HDD for something else, finally.
    In conversation Wednesday, 01-Feb-2023 07:28:20 EST from web permalink
  14. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Monday, 30-Jan-2023 15:40:43 EST Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    Glad I waited. Quite a few bugs have been fixed; just in time for the February 1 upgrade! ๐Ÿ˜Š
    In conversation Monday, 30-Jan-2023 15:40:43 EST from web permalink
  15. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Sunday, 29-Jan-2023 15:53:56 EST Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    There's an ETA now! Wednesday, February 1, 2023.

    OPNsense was released January 26; plenty of time for bugs and oversights to watch out for.
    In conversation Sunday, 29-Jan-2023 15:53:56 EST from web permalink
  16. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 14-Jan-2023 23:45:09 EST Clarissa Walker Clarissa Walker
    Finally migrating the FTP Archives data from the (frankly busted) 500GB Hitachi laptop HDD to the main file server. Next is the historical server data on another HDD. The new router I recently bought makes this possible.
    In conversation Saturday, 14-Jan-2023 23:45:09 EST from web permalink
  17. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Saturday, 14-Jan-2023 23:31:17 EST Clarissa Walker Clarissa Walker
    OPNsense 23.1 is approaching fast.

    I am going to migrate the firewall that is handling all connections, especially this very server, from old-ish reliable 21.1.9 to the latest future 23.1 in February.

    This requires manual setup and not an upgrade, so some downtime is expected. No ETA on when this will be done just yet.
    In conversation Saturday, 14-Jan-2023 23:31:17 EST from web permalink
  18. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 12-Jan-2023 02:34:09 EST Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    Okay, the system lives once again. Yeah, I freaked out because there is years of stuff not on the main server yet from that Windows install. Thinking the cumulative Windows update was actually installing despite the WinApp saying Downloading 100% after other updates that require reboot have installed (and you could restart the system in the process). Pressing Restart the System does interrupt this install process after confirmation...
    In conversation Thursday, 12-Jan-2023 02:34:09 EST from web permalink
  19. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 12-Jan-2023 01:20:11 EST Clarissa Walker Clarissa Walker
    in reply to
    • Clarissa Walker
    Restoring the Windows 10 partition was a success. No more odd system hangups and stuff seems to download from Windows Update normally. Now to see what happens after this. So odd. If this happens again (somehow), may as well use a Linux distro on it; I still have all the data for the Windows install.
    In conversation Thursday, 12-Jan-2023 01:20:11 EST from web permalink
  20. Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Thursday, 12-Jan-2023 00:01:07 EST Clarissa Walker Clarissa Walker
    Not the greatest week, lol.

    Bought a Linksys E8450 recently and ran into a showstopping bug regarding wireless clients and communication on later OpenWrt 22.03 releases and even very recent snapshot versions. Flashed 22.03.0-rc1 and wireless communication and clients now work normally without the static ARP workaround. This took a week to troubleshoot, too.

    After all that, the Intel NUC's SSD's Windows partition really became corrupted. Luckily, I mirrored the entire disk a month prior. Actually, that backup is the most recent because it hadn't been used since last month; I was testing Kubuntu 22.10 in live mode on the NUC, then eventually went back to Windows 10. Ran a Windows update, then it wouldn't boot after a restart. ๐Ÿ˜ฎ Now, I'm restoring just the Windows partition to see what would happen.
    In conversation Thursday, 12-Jan-2023 00:01:07 EST from web permalink
  • After
  • Before

User actions

  • Subscribe
  • List
Clarissa Walker

Clarissa Walker

Detroit, MI

http://cwcyrix.nsupdate.info

Hobbyist computer tweaker/repairperson, webmistress, procrastinator. Does things on my own time. Also known as CW Cyrix.

Tags
  • (None)

Following 0

    Followers 0

      Groups 0

        Statistics

        User ID
        1
        Member since
        21 Nov 2022
        Notices
        172
        Daily average
        0

        Feeds

        • Activity Streams
        • RSS 1.0
        • RSS 2.0
        • Atom
        • FOAF
        • Help
        • About
        • FAQ
        • Privacy
        • Source
        • Version
        • Contact

        Ami Sapphire's Notices is a social network. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.

        Creative Commons Attribution 3.0 All Ami Sapphire's Notices content and data are available under the Creative Commons Attribution 3.0 license.