#linuxcnc Logs
Mar 07 2025
#linuxcnc Calendar
01:04 AM Deejay: moin
01:20 AM lcnc-relay: <meisterdippel@> moin
01:23 AM xxcoder: wow one of jt chickens learned how to get on irc
01:26 AM -!- #linuxcnc mode set to +v by ChanServ
01:37 AM -!- #linuxcnc mode set to +v by ChanServ
04:51 PM roycroft: my last router cutter has just arrived for making my window casing
04:51 PM roycroft: so hopefully i can get that done this weekend
05:05 PM acer is now known as _unreal_
05:10 PM rdtsc: well the latest flash of 6.12.11 (onto a 256GB card) ran exactly once, would not connect to Ethernet, froze during reboot, and lost critical system files upon reboot.
05:10 PM rdtsc: Rpi5B: 11 Me: 0
05:14 PM rdtsc: the latest flash of 6.1.61-rt15 (onto a 64GB card) did exactly what the first one did - kernel panic 0.3s into boot
05:16 PM roycroft: it's the weekend!
05:20 PM rdtsc: You're right I'm gonna crack a 03BEER or two. Cheers
05:44 PM rdtsc: ccatlett84, just a note that nmcli isn't installed on the 6.12.11 image
06:10 PM lcnc-relay: <ccatlett1984@> Noted. Ugh.
06:13 PM rdtsc: so I backed up my "running-sans-spi" 6.12.11 SD card, re-flashed it same 6.12.11, but before trying it, ejected and reinserted it. The ROOTFS partition was not viewable. Gparted it as being 6.0GB (with over 100GB free after - 128GB card). So enlarged it to the rest of the size -32MB. NOW it is visible on the PC, uggh
06:14 PM * rdtsc wishes the stars would just align a little in my favor
06:23 PM lcnc-relay: <ccatlett1984@> Not that I wish you pain,but I'm happy it wasn't just my experience
06:29 PM rdtsc: tried re-flashed 6.12.11 - same SPI behavior - SPI enabled, latest mesaflash, refuses to talk to 7c80
06:30 PM rdtsc: ok here is the real test... reinstalling rpi4b
06:36 PM lcnc-relay: <big_kevin420@> you should check it with linuxcnc
06:37 PM lcnc-relay: <big_kevin420@> also what was the kernel panic and how new is your rpi5
06:43 PM rdtsc: yep, rpi4b works fine - has /dev/spidev0.0 and mesaflash 3.4.9 works fine.
06:45 PM rdtsc: built mesflash 3.5.11 there, works fine
06:45 PM rdtsc: either this rpi5 RP1 chip is dead, or something is seriously borked in firmware/drivers
06:45 PM lcnc-relay: <big_kevin420@> the relationship between rpi4/5 and mesaflash is unrelated to cnc function
06:46 PM lcnc-relay: <big_kevin420@> it just points further to a non linuxcnc relatyed driver configuration issue
06:46 PM rdtsc: apparently a very new version is required for rpi5 - just making sure newest runs on 4 too
06:46 PM lcnc-relay: <big_kevin420@> the realtest is if linuxcnc loads,
06:47 PM rdtsc: tried linuxcnc twice in Rpi5 - no-go either time (and no mesaflash)
06:47 PM rdtsc: this calls for more 03beeeeeeeeer
06:49 PM lcnc-relay: <big_kevin420@> mesaflash using spidev would work on probably anything, its pretty platfoprm agnostic
06:49 PM rdtsc: is there some way I can definitively test the rpi5 RP1 chip?
06:50 PM lcnc-relay: <big_kevin420@> yeah load linuxcnc
06:50 PM lcnc-relay: <ccatlett1984@> You are using spix, correct?
06:50 PM rdtsc: hahaha
06:50 PM lcnc-relay: <big_kevin420@> no, im serious
06:51 PM rdtsc: it never gets that far ccatlett1984... hostmo2 tries to talk to spi, gets nothing, gives up
06:51 PM lcnc-relay: <ccatlett1984@> If you like, I'd be happy to go down to the mill, and rebuild a mess of flash from current source and verify that it still works on my machine.
06:51 PM lcnc-relay: <ccatlett1984@> Mesaflash
06:51 PM lcnc-relay: <ccatlett1984@> Speech to text is sometimes terrible.
06:52 PM rdtsc: oh you don't have to do that. might be facing a broken rp1 chip
06:52 PM lcnc-relay: <big_kevin420@> well thats where you need tio focus your efforts on is seeing if linuxcnc actually works
06:52 PM lcnc-relay: <ccatlett1984@> I mean, it won't hurt anything on my mill.
06:52 PM lcnc-relay: <big_kevin420@> why would the rp1 chip be broken
06:53 PM lcnc-relay: <big_kevin420@> did something happen?
06:53 PM rdtsc: no idea, but I've never gotten as much as a peep out of spi on it... oh and I see this in dmesg: [ 0.943220] rp1-pio 1f00178000.pio: error -ENOENT: failed to contact RP1 firmware
06:54 PM lcnc-relay: <big_kevin420@> thats the string you need to follow
06:54 PM lcnc-relay: <big_kevin420@> how new is your rpi5
06:55 PM lcnc-relay: <skunkworks8841@> pcw-home: I hate cui capacitive encoders.. I thought this would be a good use of one of these..
06:55 PM lcnc-relay: <skunkworks8841@> https://photos.app.goo.gl/WyDxavoi2NBNPG797
06:55 PM lcnc-relay: <skunkworks8841@> that is 250rpm of wobble.
06:56 PM rdtsc: yuck.... stick a schmitt-trigger logic gate after it :)
06:56 PM lcnc-relay: <skunkworks8841@> I guess I could low-pass it.. and see if that helps.. but that adds delay
06:57 PM lcnc-relay: <skunkworks8841@> it must not be linear in its rotation
06:57 PM rdtsc: just bought the rpi5 last week... came with firmware from 2024/09 on it
06:57 PM lcnc-relay: <big_kevin420@> k
06:57 PM lcnc-relay: <big_kevin420@> you said you did update it or no?
06:57 PM rdtsc: SW schmitt trigger = likely 100ns delay
06:58 PM rdtsc: Sw https://www.ti.com/product/SN74LVC2G17
06:58 PM lcnc-relay: <ccatlett1984@> i'm running much newer firmware than that
06:58 PM lcnc-relay: <ccatlett1984@> on my pi5
06:58 PM rdtsc: I updated it to 2025/1/20 or something, no change
07:00 PM lcnc-relay: <ccatlett1984@> vcgencmd bootloader_version
07:00 PM lcnc-relay: 2025/01/22 00:16:51
07:00 PM lcnc-relay: version a77530632346c8ac1d579fa3c369f9980401e821 (release)
07:00 PM lcnc-relay: timestamp 1737505011
07:00 PM lcnc-relay: ... long message truncated: https://jauriarts.org/_heisenbridge/media/jauriarts.org/rrEocmpGRnzvNRHsCfXdiPmq/r6XnU7Neiw8 (6 lines)
07:00 PM rdtsc: yep I think we have the same ver
07:00 PM rdtsc: just cut some air with the rpi4b... man that thing is much slower
07:01 PM rdtsc: wonder if it could be a power problem... should 'scope it
07:01 PM lcnc-relay: <ccatlett1984@> you think that's fast, boot from SSD, omg it's a completely different world
07:01 PM lcnc-relay: <ccatlett1984@> I'm running 5.1v to the pi5, via usb-c
07:01 PM rdtsc: looked at the NVME hats for it... but wouldn't work with the ribbon cable
07:02 PM lcnc-relay: <ccatlett1984@> oh yes they do 😄
07:03 PM lcnc-relay: <ccatlett1984@> https://www.amazon.com/dp/B0CXPGJ2F8 this one fits, and works great
07:03 PM rdtsc: was looking at pishop.us - maybe they didn't have the right one :) the flex cable would block my airflow though also - decided it wasn't absolutely necessary
07:03 PM lcnc-relay: <ccatlett1984@> I did shave the side of the ribbon cable a hair, for standoff clearance
07:04 PM rdtsc: tight fit, that's for sure
07:04 PM lcnc-relay: <ccatlett1984@> yep.
07:04 PM lcnc-relay: <ccatlett1984@> on to mesaflash, according to a git pull, i'm still up to date with my local copy
07:06 PM rdtsc: SW that buffer has a delay of about 6ns :)
07:07 PM rdtsc: mesaflash must be 3.5.11 latest then :)
07:09 PM lcnc-relay: <big_kevin420@> what is the build datwe of the image?
07:09 PM lcnc-relay: <ccatlett1984@> really should have a new "release" on that repo, current is 3.4.9 from 2023
07:10 PM rdtsc: Kevin, 2025/1/27 for the latest https://www.linuxcnc.org/iso/
07:13 PM lcnc-relay: <big_kevin420@> did you do apt-upgrade?
07:14 PM rdtsc: of course :)
07:16 PM lcnc-relay: <big_kevin420@> every time you tried?
07:16 PM lcnc-relay: <big_kevin420@> like every iso you tried
07:17 PM rdtsc: could only try 6.12.11 - the earlier one always kernel panics at boot
07:18 PM rdtsc: pcw-home, do you know, were there any 7c80's made which may not be able to power a rpi5 + keyboard + mouse + pendant + monitor touch? (monitor itself has its own 12V power supply) - maybe I havea power prob
07:19 PM rdtsc: no usbc supplies to test with, although do have some bench supplies
07:20 PM lcnc-relay: <big_kevin420@> im going to give it a guess and say no
07:20 PM lcnc-relay: <big_kevin420@> i think he probably rated it for the rpi3 when he made it
07:20 PM lcnc-relay: <big_kevin420@> 2.5v is for sure not enough
07:21 PM lcnc-relay: <big_kevin420@> 2.5a
07:21 PM rdtsc: ok I'll put the rpi5 back in, get it ssh-able, and disconnect everything I can
07:24 PM lcnc-relay: <ccatlett1984@> he told me that he has it working with a pi5, but i dont trust it for full power draw, i have a separate 12v psu for a flood pump, and am using a step-down transformer for the pi
07:25 PM lcnc-relay: <ccatlett1984@> i haven't cut the 5v lead going to the mesa board, but am seriously considering it, as i dont want to backfeed the mesa card with more than 5.0v, and the pi likes 5.1-ish
07:31 PM xxcoder: https://www.youtube.com/watch?v=fu4ceiCWS4I bit interesting project
07:31 PM lcnc-relay: <big_kevin420@> i dont doubt he has it working with a pi5, but if the rating is what it says in the manual, then he is doing a very minimal setup
07:31 PM lcnc-relay: <big_kevin420@> theres also this note
07:31 PM lcnc-relay: <big_kevin420@> 5V CURRENT FOR HOST ---- 2.5A No ext load
07:33 PM lcnc-relay: <big_kevin420@> clet, how do you power your with the rpi5?
07:33 PM lcnc-relay: <big_kevin420@> do you have scren and stuff?
07:39 PM Tom_L: kinda makes me wanna get a pi5 and try this
07:40 PM * rdtsc hands Tom a pile of his hair
07:42 PM Tom_L: i've got a 7i90 i could spi
07:42 PM Tom_L: and have on the rpi4
07:42 PM Tom_L: got a cable somewhere still
07:42 PM Tom_L: same spi pinout on both??
07:42 PM lcnc-relay: <big_kevin420@> yeah\
07:42 PM lcnc-relay: <big_kevin420@> rdtsc this image? rpi-5-debian-bookworm-6.12.11-arm64-ext4-2025-01-27-0140.img.xz
07:43 PM rdtsc: yessir kevin
07:43 PM lcnc-relay: <big_kevin420@> k
07:45 PM lcnc-relay: <big_kevin420@> 2 things im not going to do is apt-upgrade or update eeprom
07:46 PM Tom_L: aww c'mon..
07:47 PM Tom_L: somebody has to figure out if it works
07:47 PM Tom_L: mirror another sd
07:47 PM Tom_L: does the rpi5 use the same downloader as the rpi4?
07:47 PM Tom_L: for the image
07:48 PM lcnc-relay: <big_kevin420@> uhhhh
07:48 PM lcnc-relay: <big_kevin420@> the image to sd thing?
07:48 PM lcnc-relay: <ccatlett1984@> yes, rpi imager is the same
07:48 PM Tom_L: yes and no they are not the same
07:48 PM Tom_L: No, the Raspberry Pi 4 downloader is not the same as the Raspberry Pi 5 downloader. The Raspberry Pi 5 requires a 64-bit Bookworm image, while the Pi 4 can use either 32-bit or 64-bit images.
07:48 PM Tom_L: i think AI is full of shit
07:49 PM lcnc-relay: <big_kevin420@> oh dif images yeah
07:49 PM lcnc-relay: <big_kevin420@> but the tool is the same
07:49 PM Tom_L: well i knew that
07:49 PM lcnc-relay: <ccatlett1984@> it's the same download / writing tool
07:49 PM lcnc-relay: <ccatlett1984@> also, a pi4 (must be 64bit) image, will run on a pi5
07:49 PM Tom_L: oh?
07:49 PM Tom_L: even with the different spi?
07:49 PM lcnc-relay: <ccatlett1984@> not saying that all the things will work (they wont), but it will boot
07:49 PM Tom_L: chips..
07:49 PM lcnc-relay: <ccatlett1984@> spi is one of the things that won't work
07:49 PM Tom_L: that's not working then
07:50 PM lcnc-relay: <ccatlett1984@> for our use case, yes. in many applications, no
07:50 PM Tom_L: for a chicken timer?
07:50 PM Tom_L: :)
07:50 PM lcnc-relay: <ccatlett1984@> or klipper, or anything that doesn't use spi
07:50 PM lcnc-relay: <ccatlett1984@> lots of uses
07:51 PM lcnc-relay: <ccatlett1984@> am i correct that mesaflash can't talk to a card, if linuxcnc is running (using that card)?
07:52 PM Tom_L: true
07:53 PM lcnc-relay: <ccatlett1984@> kk, have to go kill linuxcnc to test the fresh pull of mesaflash
07:54 PM Tom_L: maybe undocumented tip: --device somerandomname will produce a list of devices
07:54 PM lcnc-relay: <ccatlett1984@> confirmed, latest still works on the 7c80
07:54 PM lcnc-relay: sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid
07:54 PM lcnc-relay: Configuration Name: HOSTMOT2
07:54 PM lcnc-relay: General configuration information:
07:54 PM lcnc-relay: ... long message truncated: https://jauriarts.org/_heisenbridge/media/jauriarts.org/OiHlmMJFCGHjHKjCVodsEBeg/LH1wIasdUec (9 lines)
07:54 PM Tom_L: cool
07:57 PM lcnc-relay: <big_kevin420@> hmm looks like this sd card is from 2021....not sure how important it is if i hjavent touched it in years
07:57 PM lcnc-relay: <big_kevin420@> probably just some stupid backup or something. \
07:57 PM lcnc-relay: <ccatlett1984@> is it legit sandisk, or no-name crap?
07:58 PM lcnc-relay: <big_kevin420@> kingstonm
07:58 PM lcnc-relay: <big_kevin420@> just gotta unmount the usb sticks, just incase
07:59 PM lcnc-relay: <big_kevin420@> alright, im gonna go watch jeopardy and it should be loaded by then
08:00 PM Tom_L: all mine are sandisk
08:00 PM lcnc-relay: <big_kevin420@> i really need to label these
08:00 PM lcnc-relay: <big_kevin420@> there is a bag of sd cards i have...some i put marker dots on...all different nice cards
08:00 PM lcnc-relay: <big_kevin420@> i dont remember which ones were important
08:01 PM Tom_L: yeah i lose track of the 'marks'
08:01 PM lcnc-relay: <big_kevin420@> i need to put marks on the ones that stop working
08:01 PM lcnc-relay: <big_kevin420@> i replaced on the other day on a no boot sdcard thats been running for years
08:01 PM lcnc-relay: <big_kevin420@> but i put it back in the bag
08:02 PM Tom_L: you should get rid of the ones that stop working or stuff em in a camera
08:02 PM lcnc-relay: <big_kevin420@> yeah i probably ment to check it "later"
08:07 PM rdtsc: tried rpi5 with no usb devices connected and wifi power saving enabled - same
08:07 PM rdtsc: thinking i might 'scope the power and see what's actually happening
08:07 PM Tom_L: is there a particular rpi5 'kit' to look for?
08:08 PM Tom_L: board psu etc
08:08 PM rdtsc: I got mine from pishop.us - if that means anything :)
08:08 PM Tom_L: avoid it?
08:08 PM Tom_L: :)
08:08 PM rdtsc: yeah dunno - maybe I have power probs, dunno yet
08:09 PM Tom_L: they can't use the rpi4 psu can they?
08:09 PM Tom_L: takes more power...
08:09 PM Tom_L: ?
08:10 PM lcnc-relay: <ccatlett1984@> pi5 has a higher amp draw at full load
08:10 PM Tom_L: 5A vs 3A..
08:31 PM rdtsc: can see in dmesg [ 0.455362] rp1 0000:01:00.0: chip_id 0x20001927 <-- that value appears to be correct, so it at least sees the rp1
08:37 PM Tom_L: on the pi5, what's that little plug next to the usb c plug marked 'bat'?
08:37 PM Tom_L: backup?
08:39 PM rdtsc: external battery to keep date and time when powered off I think
08:45 PM pcw-home: The 7C80 5V power is marginal for the RPI5 especially it you want to run anything other than a keyboard
08:46 PM pcw-home: I would use the USB C power or supply 5V to the AUX CPU power connector
08:49 PM pcw-home: When I next do a board rev I'll bump the 5V supply current up
08:49 PM lcnc-relay: <ccatlett1984@> the AUX CPU connector, i'd be concerned of backfeeding
08:51 PM lcnc-relay: <ccatlett1984@> pi's want more than 5v, and i dont think the mesa will like that
08:52 PM Tom_L: ccatlett, what do you mean? i thought the usb c was 5v
08:52 PM lcnc-relay: <ccatlett1984@> official pi power bricks are 5.1v~
08:52 PM xxcoder: C hve standards for various voltage
08:52 PM xxcoder: if I recall right anyway
08:52 PM xxcoder: ah yes 5 to 20v
08:53 PM lcnc-relay: <ccatlett1984@> https://github.com/raspberrypi/documentation/blob/develop/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc#power-supply
08:54 PM roycroft: a good rule of thumb is that for most circuits, the power should be within 10% of the spec, so for a 5v circuit, 4.5v to 5.5v will generally work
08:54 PM roycroft: there are circuits where the voltage is more critical, of course
08:55 PM roycroft: i seriously doubt that is the case with the main power to an rpi
08:55 PM lcnc-relay: <ccatlett1984@> anything under 5.0v and the pi bitches
08:56 PM roycroft: but is that because of undervoltage, or because the power supply cannot provide enough current?
08:56 PM roycroft: as the voltage drops the current needs to increase to perform the same amount of work
08:56 PM Tom_L: https://www.amazon.com/CanaKit-Raspberry-Essentials-Starter-Kit/dp/B0CVQT445P
08:56 PM Tom_L: looking at that
08:56 PM lcnc-relay: <ccatlett1984@> my step down is capable of 10A, so it's not a current issue
08:56 PM Tom_L: psu says 45w
08:56 PM Tom_L: stock is 27
08:57 PM rdtsc: "On all models of Raspberry Pi since the Raspberry Pi B+ (2014) except the Zero range, there is low-voltage detection circuitry that will detect if the supply voltage drops below 4.63V (±5%). This will result in an entry being added to the kernel log." no such message in dmesg
08:57 PM xxcoder: so bit under 40 amps
08:57 PM xxcoder: errm bit under 5 amp I meant
08:57 PM lcnc-relay: <ccatlett1984@> if i adjust the voltage on my step down to 5.0v, it throws that warning
08:57 PM lcnc-relay: <ccatlett1984@> 5.1v is great
08:57 PM roycroft: which indicates that the rpi should still operate at a 5% voltage variance
08:58 PM Tom_L: always gotta be an oddball out there
08:58 PM rdtsc: ccatlett1984's rpi5 runs "hot" :) mine is running on three cylinders
08:58 PM roycroft: i honestly would be astonished if the rpi has a design spec of 5v and will not function if the voltage drops below the spec
08:59 PM roycroft: there's no need to design it that way, and the rpi engineers know that folks will be supplying power from thousands, probably hundreds of thousands, of cheap, consumer grade power supplies of varying and often marginal performance specs
09:00 PM roycroft: it would be stupid to design it so that the voltage spec is the absolute floor
09:00 PM Tom_L: with marginal results
09:00 PM xxcoder: indeed roy
09:00 PM lcnc-relay: <ccatlett1984@> as someone that came here from the klipper (fdm printer) world, pi's get unstable at anything lower than 5.1v
09:00 PM roycroft: the product would not be marketable
09:00 PM lcnc-relay: <ccatlett1984@> hence why they have the "official" brick
09:00 PM Tom_L: locking you into their product :)
09:01 PM Tom_L: .... apple
09:01 PM lcnc-relay: <ccatlett1984@> or an adjustable step-down
09:01 PM roycroft: i've run many with random power supplies and never had a problem
09:01 PM roycroft: i don't think i've ever bought an "official" rpi power brick
09:02 PM roycroft: i'm not claiming that the rpi actually does behave the way you describe
09:02 PM roycroft: i've been astonished before
09:03 PM lcnc-relay: <ccatlett1984@> it's a common issue on the klipper side of things
09:06 PM roycroft: i don't know much about klipper, other than what it is
09:06 PM roycroft: does it run on the pi, or does it use an octopi server to interface with it?
09:07 PM Tom_L: is the hdmi cable the same on both?
09:08 PM lcnc-relay: <ccatlett1984@> part runs on the stm32 mcu, part runs on the pi, along with moonraker (the middleware) and the UI of choice (moonraker, fluidd, octoprint)
09:08 PM roycroft: ok
09:08 PM roycroft: so what feeds power to the pi?
09:08 PM roycroft: does it use a dedicated power supply?
09:08 PM lcnc-relay: <ccatlett1984@> yep, or step down from the 24v psu that runs the rest of the printer
09:09 PM roycroft: hmm
09:09 PM roycroft: odd that this one use case sees this problem, and i've never experienced it nor have i heard of anyone else experiencing it until just now
09:10 PM lcnc-relay: <ccatlett1984@> klipper is doing UART over usb for talking to the mcu
09:10 PM roycroft: i'm trying to wrap my head around what might be particular to the klipper environment that would cause the issue
09:10 PM lcnc-relay: <ccatlett1984@> and typically the v5 wire on the usb cable is cut
09:10 PM lcnc-relay: <ccatlett1984@> so you can't backfeed the mcu
09:12 PM roycroft: now i think that when i have a chance i need to set up a rpi with a variable voltage power supply and see what happens when i drop it below 5v
09:13 PM roycroft: the room where my electronics bench lives is a work area at the moment, though, and it will probably be a week before the project i'm working on there is done so that i can get to the bench
09:13 PM roycroft: but i am curious, and will try to do some testing
09:14 PM roycroft: and will be prepared to be astonished :)
09:18 PM rdtsc: no voltage logs in dmesg, no "square in corner of display", no notice of any power issue. not finding a good test point for scoping power (the IDC cable covers a lot)
09:22 PM rdtsc: lets see, there is 5.033V on the TB15 Alt CPU Power connector, with a small 60mm fan connected to it, with 13mV AC ripple as measured by a Fluke 87 V meter (only good to some kHz)
09:23 PM rdtsc: getting late here, will remove the fan and scope that connector in the morn
09:25 PM rdtsc: might be able to bump up the voltage by tweaking the DC-DC but would rather not if at all possible
09:27 PM rdtsc: this gets good reviews, but like ccatlett1984 says, worrying about backfeeding https://argon40.com/products/argon-pwr-gan-usb-c-pd-power-supply-27-watts
09:30 PM rdtsc: p.s. it's a 60x15mm 12V fan, running at 5V - just enough air to keep the pi cool
09:35 PM pcw-home: rdtsc: What actual issue do you have?
09:35 PM rdtsc: rpi5 seems to run fine, but mesaflash and linuxcnc do not see the 7c80
09:36 PM pcw-home: Is it an older 7C80?
09:37 PM rdtsc: dunno, bought it in 2023 I think
09:37 PM rdtsc: 9/10/2022
09:38 PM pcw-home: Some had proto 7C80 firmware installed so may need to be updated
09:39 PM rdtsc: ok will try that with the pi4b in the morn :)
09:39 PM pcw-home: They do work on RPI4s
09:40 PM rdtsc: never had to touch it - just worked (with the pi4)
09:41 PM pcw-home: Yeah that was the problem The proto firmware has a different CS pin, that happened to work on the RPI4
09:42 PM rdtsc: no CS certainly would explain the lack of any communication :)
09:42 PM pcw-home: so not noticed (all the distributed firmware was OK but the firmware on our initialization PC was bad
09:43 PM pcw-home: sorry for the problem
09:43 PM rdtsc: hopefully that is all it is, will be a welcome relief actually
09:44 PM pcw-home: Sounds like it (especially since neither Mesaflash nor LinuxCNC see the card)
09:46 PM rdtsc: ok thank you, must get some sleep
10:02 PM lcnc-relay: <big_kevin420@> i hope thats the case because it took me all 5 minutes to go from ejecting the new sdcard image from my pc to a running mesa7c81
10:03 PM lcnc-relay: <big_kevin420@> everything works as it should with the latest image
10:03 PM memleak: what's a counter strike pin?
10:04 PM lcnc-relay: <big_kevin420@> the thing on the back of the cd case from the 90's used to install 1.6
10:04 PM lcnc-relay: <ccatlett1984@> lol
10:05 PM memleak: :D
10:05 PM lcnc-relay: <big_kevin420@> wait, is it actually a cs thing?
10:05 PM memleak: thanks for playing!
10:05 PM lcnc-relay: <big_kevin420@> it looks like some shit you get in csgo
10:06 PM lcnc-relay: <big_kevin420@> hmm looks like i have a 10 year csgo pin
10:07 PM lcnc-relay: <big_kevin420@> honestly im not crazy about using this offical linuxcnc debian image for RPi
10:09 PM lcnc-relay: <big_kevin420@> eventhought it was the fastest setup im done so far on an RPi. no screen stuff to mess with, it just worked
10:10 PM lcnc-relay: <ccatlett1984@> yeah, i had to do "things" to get the rpi firmware update tool to run
10:11 PM lcnc-relay: <big_kevin420@> hmm im not doign that with the debian image
10:13 PM lcnc-relay: <big_kevin420@> ill just put a dot on this SD card so I know its the rpi5 debian image, and ill just put it back in the bag of sd cards
10:13 PM lcnc-relay: <ccatlett1984@> lol
10:14 PM lcnc-relay: <big_kevin420@> hmm so can rdtsc just use the rpi4 and mesaflash to load the production firmware?
10:15 PM lcnc-relay: <ccatlett1984@> that's what i had to do with mine
10:15 PM lcnc-relay: <big_kevin420@> ahh i kept thinking you downgraded to a 4 for some other reason
10:15 PM pcw-home: Yes, if that's the issue (and he never changed the pre-installed firmware on the RPI4)
10:16 PM lcnc-relay: <big_kevin420@> thats what I hope, i forgot to check for that error he reported
10:20 PM lcnc-relay: <big_kevin420@> ah ok, he said the message was from dmsg
10:20 PM lcnc-relay: <big_kevin420@> not from linuxcnc
10:20 PM lcnc-relay: <ccatlett1984@> rdtsc, here is the cmd's for flashing the correct firmware
10:20 PM lcnc-relay: https://forum.linuxcnc.org/27-driver-boards/54899-pi5-mesa-7c80-working?start=30#317999
10:21 PM lcnc-relay: <big_kevin420@> i think its benign the error in dmsg and the upstream update just ignores the error
10:21 PM lcnc-relay: <big_kevin420@> dmesg: [ 0.943220] rp1-pio 1f00178000.pio: error -ENOENT: failed to contact RP1 firmware
11:12 PM memleak: i don't know why it cares that there isn't a ears-nose-throat doctor
11:49 PM memleak: qtpyvcp on the pyside6 branch is moving along nicely