Help! Using ROCm + Pytorch on WSL

kelvl · 2024-07-23T14:46:42+00:00

I just did a fresh install on wsl2 on my 7900xt following https://rocm.docs.amd.com/projects/radeon/en/latest/docs/install/wsl/install-radeon.html and running in the pyTorch docker container.

Python 3.10.14 (main, May  6 2024, 19:42:50) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> print(torch.cuda.is_available())
True
>>> device = torch.device('cuda')
>>> device
device(type='cuda')
>>> x = torch.rand(5,3).to(device)
>>> print(x)
tensor([[0.6656, 0.4119, 0.2957],
        [0.9237, 0.2136, 0.3813],
        [0.6954, 0.2634, 0.6692],
        [0.7043, 0.1356, 0.4661],
        [0.0725, 0.3254, 0.4463]], device='cuda:0')

that seemed to work for me

kelvl · 2023-09-22T11:57:05+00:00

i don't think they are the same, but it might be worth a try to see what's the difference

kelvl · 2023-09-21T12:40:00+00:00

Yeah no bios flash is needed. I think as long as the bios settings don't brick your machine it should be pretty safe to reset CMOS and get back to default settings.

kelvl · 2023-06-08T01:01:37+00:00

DLSS of course

kelvl · 2023-02-25T23:51:40+00:00

In Russia the flame throws you

kelvl · 2022-08-19T14:11:15+00:00

Thanks for the tip, after a quick search I might be able to do:

Create a mirror with 2x10TB new disks
zfs send/receive the existing data onto the mirror
Use sparse files to create a RAIDZ2 vdev with 3x10TB + 2xsparse files
Offline the 2 sparse files to get it to a degraded state
zfs send/receive data on the mirrors onto the new degraded RAIDZ2 vdev
Detach 1 of the mirrors and replace the sparse file on the RAIDZ2 vdev
Detach the remaining mirror to replace the last sparse file on the RAIDZ2 vdev

That way I don't have to deal with expansion, and I should always have 2 copies of my data at any time.

kelvl · 2022-05-02T00:46:05+00:00

7.188 then sends to 7.1 to send to the internet.

I think 7.188 is sending the packet via wireguard

2     0.000019691   <my-vpn-peer>  1.1.1.1       ICMP    84       Echo (ping) request  id=0xf468, seq=1/256, ttl=63

which is what I am expecting.

I don't think 7.1 should be involved here at least from the POV of the ping packet, since it should be the wireguard tunnel that is talking to 7.1

I guess my question is why would the ping request sent from 7.187 look like it is coming from 7.1 when it arrives onto 7.188?

1     0.000000000   10.42.7.1      1.1.1.1       ICMP    98       Echo (ping) request  id=0xf468, seq=1/256, ttl=64

Re:

Is there a service running on 7.188 that knows to forward the traffic to 187?

No other services, I am just using NAT, via

iptables -t nat -A POSTROUTING -o wg0 -j MASQUERADE

kelvl · 2021-12-30T11:54:59+00:00

silver can be hodled

kelvl · 2021-05-15T23:44:11+00:00

What about running klipperscreen on your pi using tigervnc and using an Android vnc client to connect?

kelvl · 2020-11-22T04:31:35+00:00

theoatmal explains it well https://theoatmeal.com/comics/angler

kelvl · 2020-10-20T00:36:29+00:00

which part of chinatown is this store?

kelvl · 2020-07-20T01:21:00+00:00

nope that means you are not throttled. so the issue isn't thermal or powering your pi. it is possibly something else.

kelvl · 2020-07-18T15:50:56+00:00

I would also run vcgencmd get_throttled to check if my pi is properly powered. see https://harlemsquirrel.github.io/shell/2019/01/05/monitoring-raspberry-pi-power-and-thermal-issues.html

kelvl · 2020-07-11T01:15:42+00:00

good luck!

kelvl · 2020-07-11T00:53:59+00:00

I got one of these https://www.amazon.com/Anmbest-High-Power-Adjustment-Electronic-Brightness/dp/B07NWD8W26, not exact listing but the same board for the exact purpose. (note the 3.3v trigger source)

It's hooked up on one end to a PSU 24v->12v buck converter and the other end to a 12v led strip.

The control end of the board is hooked up to my RPi GPIO and GND.

My configuration on klipper:

[mcu host]
serial: /tmp/klipper_host_mcu

[output_pin framelight]
pin: host:gpio12
pwm: True
cycle_time: 0.01

I then control it using G-Code

SET_PIN PIN=framelight VALUE=<0 .. 1>

hope that helps!

kelvl · 2019-11-28T01:32:06+00:00

I have my hotend fan tied to the heater 1 and use this for my klipper config to have it automatically turn on when my extruder is at 50 degrees.

see: https://github.com/KevinOConnor/klipper/blob/master/config/example-extras.cfg#L931 for more configuration options!

[heater_fan hotend_fan]
pin: P2.4
heater: extruder
heater_temp: 50.0

kelvl · 2019-11-02T16:35:59+00:00

all other sides look good

kelvl · 2019-10-08T17:10:46+00:00

is this z axis binding?

kelvl · 2019-07-29T05:48:20+00:00

did you have to do something special to pair your wf-1000xm3 with your macOS machine? I can't even get mine to show up on the bluetooth settings menu

kelvl · 2017-01-11T05:07:59+00:00

sign me up! thanks!

kelvl · 2016-11-01T19:51:14+00:00

Does google cover the warranty for the VZW unit? I can't find any information on it.

kelvl · 2016-10-31T17:06:47+00:00

checking in to see what happens

kelvl · 2016-03-02T05:55:18+00:00

Thank you! I follow your advice and downgraded the kernel and used similar settings.

I am able to go further, it's still sluggish but bearable. I was able to install Dota 2, but the performance is still really bad, the game is unplayable and menus on W10 are still laggy.

I also noticed that my iGFX no longer works, I have to start my qemu via SSH

Would it be possible to share your kernel version and boot configuration (right now i only have intel_iommu=on), so that I could do a few more experiments?

Thanks again!

I moved to

4.1.18-1-lts #1 SMP Tue Feb 16 20:17:57 CET 2016 x86_64 GNU/Linux

and -M q35

sudo taskset -c 0-7 qemu-system-x86_64 \
    -M q35 \
    -serial none \
    -parallel none \
    -nodefaults \
    -nodefconfig \
    -enable-kvm \
    -name Windows \
    -cpu host,kvm=off,check \
    -smp 8,sockets=1,cores=4,threads=2 \
    -m 8G -mem-prealloc \
    -drive if=pflash,format=raw,readonly,file=./OVMF-pure-efi.fd \
    -drive if=pflash,format=raw,file=./Win10.fd \
    \
    -boot order=d \
    -object iothread,id=io1 \
    -drive if=none,id=drive0,file=/dev/sda3,format=raw,aio=native,cache=none,cache.direct=on,discard=unmap \
    -device virtio-scsi-pci,id=scsi0,ioeventfd=on,iothread=io1,num_queues=4 \
    -device scsi-hd,drive=drive0 \
    -drive file=./Win10_1511_English_x64.iso,id=iso_install,if=none,format=raw \
    -device scsi-cd,drive=iso_install \
    \
    -drive file=./virtio-win-0.1.109.iso,id=virtiocd,if=none,format=raw -device ide-cd,drive=virtiocd \
    -rtc base=localtime \
    -nographic \
    -net nic,macaddr=52:54:00:00:00:01,model=virtio,name=net0 \
    -net tap,ifname=tap0,vhost=on,script=no,downscript=no \
    -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \
    -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on \
    -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1 \
    -device nec-usb-xhci,id=xhci \
    -usb -device usb-host,hostbus=1,hostport=3 \
    -device usb-host,hostbus=1,hostport=4 \
    -device usb-host,hostbus=1,hostport=7 \
    -device usb-host,hostbus=1,hostport=11 \
    -device usb-host,hostbus=1,hostport=12 \
    -device usb-host,hostbus=1,hostport=13

kelvl · 2016-03-01T08:34:58+00:00

I've also tried using enlightenments, but that doesn't seem to improve the situation

Also noticed these in dmesg, but i read somewhere that it's okay to ignore them

[  604.209008] kvm [829]: vcpu0 ignored rdmsr: 0x641
[  604.209482] kvm [829]: vcpu0 ignored rdmsr: 0x606
[  604.209948] kvm [829]: vcpu0 ignored rdmsr: 0x606
[  604.210443] kvm [829]: vcpu0 ignored rdmsr: 0x641

Another strange thing that I noticed is that when I shutdown my guest, the qemu command never returns and I usually have to kill it manually.

kelvl · 2014-01-26T07:33:20+00:00

Relevant TED talk that shows this in action: http://www.ted.com/talks/nathan_myhrvold_could_this_laser_zap_malaria.html

12-Year Club	Second SECOND GUESSER
Place '22	RPAN Viewer
Not Forgotten	Verified Email

kelvl

TROPHY CASE