<mnkydeth>
So, I think I am just installing Crux wrong on arm. Do I image the file to the emmc/microsd or do I need to write to a usb stick first then install like I was going through a traditional Crux install?
<beerman>
the former
<beerman>
i just wanted to say that i received the gps module today, so i will probably try to get that running tomorrow
guido_rokepo has joined #crux-arm
<mnkydeth>
hmm, k ... I keep getting the searching for boot device then it tries each one over and over. I am trying with a Compute Module 4 on the official IO Board.
<mnkydeth>
I'll poke around a bit more.
<beerman>
have you formatted your boot device correctly?
<beerman>
i'll grant that the documentation is not extremely clear and might be done better (though i always hope somebody else hears that call naturally and steps in to do that), but oh well
<mnkydeth>
I was going back and r-reading what Jaeger said. Seems I don't have it formatted correctly. I was using the raspberry pi software to write to the image.
<beerman>
i am not sure the "rpi software" (dunno which one you mean and if they even have their own official one and so on) would work because we just distribute tars here, and last time i checked they use img format which requires you to write them byte by byte to the drive
<beerman>
gimme a second and i'll pull of the partition table and stuff from my rpi using parted
<beerman>
please mind: a) fat32 for boot b) the flags
<beerman>
i doubt gpt plays any role but that works perfectly fine using a ssd to boot from with no sd card installed (provided the rpi firmware is updated enough to support it)
<beerman>
you take the tars, you unpack them on the root of your sdcard with both partitions mounted
<beerman>
anyway, gotta go, if you have any other questions feel free to drop them here to have them answered (sometime)
<mnkydeth>
Of course, thanks
guido_rokepo has quit [Quit: guido_rokepo]
<mnkydeth>
Well, I've made it further then I have so far. Instead of getting searching for boot device. I am getting a PANIC: VFS: Unable to mount root fs on unknown-block(179,2)
<jaeger>
Yeah, to clarify, there's not a crux-arm image to write directly to the SD card
<mnkydeth>
When the sdcard is in my machie it is recognized as sda. So... I made 512M sda1 fat32, sda2 16G swap and the remaining space was formatted as ext4.
<mnkydeth>
Yeah, I'm going throuhg the motions now at least. :)
<mnkydeth>
Maybe I shouldn't have the swap to keep more accurate with your example.
<jaeger>
When you move it to the rpi it'll likely be /dev/mmcblk0
<jaeger>
so boot would be /dev/mmcblk0p1 and / would be /dev/mmcblk0p2
<jaeger>
You can also have swap if you want to, just adjust the partition numbers as needed
<jaeger>
I usually put swap on an external USB drive if I need it
<mnkydeth>
So, I havn't looked yet. Is there a config.txt and such where I can adjust this?
<jaeger>
yes, that'll be in /boot - if you're referencing my comments from that IRC log link it's in the zip file from the raspberrypi firmware github repo
<jaeger>
Also on that same link you can see my cmdline.txt and an ix.io link for config.txt
<mnkydeth>
Ahh k, thanks. I havn't read up that far just yet. But I'm getting there then.
<jaeger>
No worries
<beerman>
i just put raspbian on the sd card and try to set it up for the ntp source
<beerman>
updating... takes a lot of time... 😄
<beerman>
(for binaries that is)
<beerman>
thinking about it, and looking at that gps module... why do i even bother with rpi, i can just chuck that into my nas and call it a day
<beerman>
that way i wouldn't need to run a new network cable, + occupy another power socket.. mh
<jaeger>
yeah
<beerman>
problem there is that it already has the zigbee stick connected and i noticed with another esp that having that connected it starts shuffling /dev/ttyUSB{0,1} and my containers don't come up correctly 😄 i dunno, the pi could have a space, running cables won't be more than 10 minutes of work.. i dunno 😄 first i'll try it on the pi and see how that runs I guess
<beerman>
its almost done installing the software so why not
<jaeger>
I tried my first module with USB and could have done that anywhere, but since it didn't work I also wanted to try gpio pins, hence the pi
<jaeger>
Then the second one I just went straight to the pi as it was already configured
<beerman>
yeah, not sure, the NMEA is always not doing anything for chrony, but gpsmon shows a TOFF value and it seems to be working
<jaeger>
opt-arm64/llvm looks to have a signature mismatch
<beerman>
oh ok, something inside the rest of the default debian config