Didn't know one can contribute without an account. I thought it's something 'bout email address
comments
Not certain, but that sidebar might be github account contributors, and the commit "contributors" may not have github accounts.
Are you sure the drive heads are properly aligned? I don't remember the program name, but I vaguely remember loosening the stepper motor on my drive and ever so slightly moving it to get the drive heads aligned. The program included a reference disk for analyzing the alignment, so that may not be an option here.
Thanks! 🙏💞
Vinegar, then isopropyl to clean the battery contacts.
And I'll bet it needs a new belt.
Lots of people on YouTube doing these kinds of repairs. Techmoan, msmadlemon, etc.
I bet it says something about being unable to enumerate the device
yep, apparently that's the problem. Could it be that the monitor is gobbling up all that power? It's a 240Hz one so I wouldn't be surprised if that was the case, but I'm not unplugging a monitor lol
I'll consider investing in a powered USB hub.
marko@markubuntu ~> sudo dmesg | grep -C 29 enumer
[ 3.818789] usb 1-3.4: device descriptor read/64, error -32
[ 3.869213] ata3: SATA link down (SStatus 0 SControl 300)
[ 3.996762] usb 1-3.4: device descriptor read/64, error -32
[ 4.170726] usb 1-3.4: new full-speed USB device number 5 using xhci_hcd
[ 4.189134] ata4: SATA link down (SStatus 0 SControl 300)
[ 4.201574] r8169 0000:08:00.0 enp8s0: renamed from eth0
[ 4.220607] usbcore: registered new interface driver usbhid
[ 4.220609] usbhid: USB HID core driver
[ 4.222243] input: Razer Razer BlackWidow V4 X as /devices/pci0000:00/0000:00:08.1/0000:11:00.4/usb5/5-2/5-2:1.0/0003:1532:0293.0001/input/input3
[ 4.271813] usb 1-3.4: device descriptor read/64, error -32
[ 4.272707] hid-generic 0003:1532:0293.0001: input,hidraw0: USB HID v1.11 Keyboard [Razer Razer BlackWidow V4 X] on usb-0000:11:00.4-2/input0
[ 4.272924] input: Razer Razer BlackWidow V4 X Keyboard as /devices/pci0000:00/0000:00:08.1/0000:11:00.4/usb5/5-2/5-2:1.1/0003:1532:0293.0002/input/input4
[ 4.323873] input: Razer Razer BlackWidow V4 X as /devices/pci0000:00/0000:00:08.1/0000:11:00.4/usb5/5-2/5-2:1.1/0003:1532:0293.0002/input/input5
[ 4.324011] hid-generic 0003:1532:0293.0002: input,hidraw1: USB HID v1.11 Keyboard [Razer Razer BlackWidow V4 X] on usb-0000:11:00.4-2/input1
[ 4.324120] input: Razer Razer BlackWidow V4 X as /devices/pci0000:00/0000:00:08.1/0000:11:00.4/usb5/5-2/5-2:1.2/0003:1532:0293.0003/input/input6
[ 4.324213] hid-generic 0003:1532:0293.0003: input,hidraw2: USB HID v1.11 Mouse [Razer Razer BlackWidow V4 X] on usb-0000:11:00.4-2/input2
[ 4.324316] hid-generic 0003:1532:0293.0004: hiddev0,hidraw3: USB HID v1.11 Device [Razer Razer BlackWidow V4 X] on usb-0000:11:00.4-2/input3
[ 4.452764] usb 1-3.4: device descriptor read/64, error -32
[ 4.560169] usb 1-3-port4: attempt power cycle
[ 5.146808] usb 1-3.4: new full-speed USB device number 6 using xhci_hcd
[ 5.174973] usb 1-3.4: Device not responding to setup address.
[ 5.406988] usb 1-3.4: Device not responding to setup address.
[ 5.611717] usb 1-3.4: device not accepting address 6, error -71
[ 5.613661] usb 1-3.4: WARN: invalid context state for evaluate context command.
[ 5.683842] usb 1-3.4: new full-speed USB device number 7 using xhci_hcd
[ 5.710980] usb 1-3.4: Device not responding to setup address.
[ 5.942986] usb 1-3.4: Device not responding to setup address.
[ 6.147735] usb 1-3.4: device not accepting address 7, error -71
[ 6.149614] usb 1-3.4: WARN: invalid context state for evaluate context command.
[ 6.152258] usb 1-3-port4: unable to enumerate USB device
[ 8.553478] fbcon: Taking over console
[ 8.553996] Console: switching to colour frame buffer device 240x67
[ 8.769107] usb 1-8: New USB device found, idVendor=048d, idProduct=5702, bcdDevice= 0.01
[ 8.769113] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8.769115] usb 1-8: Product: ITE Device
[ 8.769117] usb 1-8: Manufacturer: ITE Tech. Inc.
[ 8.786789] hid-generic 0003:048D:5702.0005: hiddev1,hidraw4: USB HID v1.12 Device [ITE Tech. Inc. ITE Device] on usb-0000:0f:00.0-8/input0
[ 15.749895] EXT4-fs (dm-1): mounted filesystem 37e57b70-dbe4-4e55-9af7-ed514e5cf047 ro with ordered data mode. Quota mode: none.
[ 15.837638] systemd[1]: Inserted module 'autofs4'
[ 15.855668] systemd[1]: systemd 255.4-1ubuntu8.17 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[ 15.855673] systemd[1]: Detected architecture x86-64.
[ 15.856075] systemd[1]: Hostname set to <markubuntu>.
[ 16.023441] systemd[1]: Queued start job for default target graphical.target.
[ 16.036840] systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe.
[ 16.037294] systemd[1]: Created slice system-systemd\x2dcryptsetup.slice - Encrypted Volume Units Service Slice.
[ 16.037595] systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
[ 16.037850] systemd[1]: Created slice user.slice - User and Session Slice.
[ 16.037889] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[ 16.038032] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[ 16.038042] systemd[1]: Expecting device dev-disk-by\x2duuid-6EB3\x2d82A4.device - /dev/disk/by-uuid/6EB3-82A4...
[ 16.038046] systemd[1]: Expecting device dev-disk-by\x2duuid-ed41e766\x2d0995\x2d47db\x2d96eb\x2dd73ce6aa7373.device - /dev/disk/by-uuid/ed41e766-0995-47db-96eb-d73ce6aa7373...
[ 16.038050] systemd[1]: Expecting device dev-disk-by\x2duuid-fea91bb1\x2d1514\x2d41a6\x2d9816\x2d759e877b02ac.device - /dev/disk/by-uuid/fea91bb1-1514-41a6-9816-759e877b02ac...
[ 16.038060] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
[ 16.038073] systemd[1]: Reached target remote-fs.target - Remote File Systems.
[ 16.038078] systemd[1]: Reached target slices.target - Slice Units.
[ 16.038085] systemd[1]: Reached target snapd.mounts-pre.target - Mounting snaps.
[ 16.038097] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
[ 16.038143] systemd[1]: Listening on dm-event.socket - Device-mapper event daemon FIFOs.
[ 16.038200] systemd[1]: Listening on lvm2-lvmpolld.socket - LVM2 poll daemon socket.
I know that other models have one for the radio, so that's probably it.
Thanks! I did indeed find not one but two adjustable potentiometers. I wonder what the other one is for... Radio tuning or volume?
White vinegar is better than alcohol for cleaning battery corrosion. Battery acid is actually a base, so the acidic vinegar neutralizes it.
Another thing worth noting is that these things usually have a screw somewhere that adjusts playback speed. Though, it doesn't always look like a screw. You may find that you have to adjust it after you get the new belt.
Sorry for spamming you. Bada bing bada boom.
Whaaaa?😅
I mean, only one ear working is what makes a walkman a walkman.
Opened it up again and found the culprit for issue #1 🤣

Done! Forgot to mention, that it also has an AM/FM receiver and that's how I checked the audio.
For issue 2, Can you clean the tape head?
That's awesome!
So unfortunately there seem to be two symptoms:
- The spinning units do not rotate - need to change the rubber band?
- There is only sound in one ear (right) - I did clean the headphone jack...
Thanks! The belt seems to have a pretty forward config!

Once you get the battery working, check how the belt is. Hopefully it's easy to change.
What's wrong with it / what are you having trouble with?
Kinda hard to offer advice without knowing what the difficulty is.
Congrats! Most people learn slower.
My first thought is a driver issue. Full disclosure, I am not an IT person. Also I don't have experience with Linux.
I have a Razer DeathAdder V3 that doesn't poll at over 60 Hz unless it is unplugged and replugged subsequent to every boot.
My takeaway was that deciding to try a Razer was an educational experience and what I learned was not to make my next mouse a Razer.
Razer sucks. I had someone with a similar problem 20 years ago. Their whole PC would not boot if the mouse was plugged in. Never found a solution other than to unplug the Razer mouse and plug in after boot. In their case, OS doesn't matter because it was happening during POST (power-on self-test).
There may be a firmware update on the mouse or possibly USB-related setting in BIOS that can mitigate.
That brings back memories. Dino Eggs, and Satan's Hollow got the most screen time, even though things like Impossible Mission and Beachhead |I were more actoin and actual speech for sounds.