<jaeger>
The last build succeeded so hopefully it's good, but since it's automated I haven't tested it every time
<brian|lfs>
fair enough
<brian|lfs>
I deleted my iso off my drive downloading again
<brian|lfs>
I have gigabit internet so non issue
<jaeger>
OK, yeah, it's showing me the list of disk (only one in that case)
<jaeger>
booted it, it goes through: language -> keyboard layout -> start clonezilla -> device_image mode -> samba server -> beginner mode -> save disk -> name of the image -> list of disks
<jaeger>
for reference
<brian|lfs>
ok so its behaving like it should for you but not on my end how odd
<brian|lfs>
well maybe it just doesn't support zen4 yet lol
<jaeger>
Much newer than my version, probably... but I also don't have a 7000-series CPU
<jaeger>
I would fully expect it to work fine using the amd64 ISO and the fact that it boots and runs makes a CPU issue at least somewhat unlikely
<brian|lfs>
ya agree its probably bitlocker or someshit lol
<jaeger>
I ask again, is the drive encrypted?
<brian|lfs>
no clue if it is
<brian|lfs>
but starting to wonder
<jaeger>
Well, if it is, I would not expect clonezilla to be able to see individual partitions in the encrypted device
<jaeger>
But you said both single and multiple so I'm just guessing
<brian|lfs>
the CRUX updated ISO is good its just a Rufus thing I had to write it in DD mode instead of the default
<jaeger>
yeah, stick with dd mode for that and it should work every time, theoretically
<brian|lfs>
it don't seem to boot on the threadripper machine eventually kernel paniced
<brian|lfs>
it had errors about USB
<jaeger>
Can you post the full error output somewhere? A picture would work
<brian|lfs>
email address pictures are in my email?
<brian|lfs>
are you still there?
<jaeger>
If you're asking for an email to send a picture, jaeger@crux.ninja - or use imgur.com or similar, either way
<brian|lfs>
ok email sent
<brian|lfs>
lets see how long it takes to get to you
<jaeger>
already here
<jaeger>
Not sure what to make of that... clearly some usb issues but I'm not sure if that's responsible for the hang. That __iommu_queue_command_sync bit looks more suspicious. Maybe try disabling iommu to see if it boots
<jaeger>
Either by disabling it in the BIOS/UEFI or adding "amd_iommu=off" to the boot command line
<brian|lfs>
how would I disable iommu
<brian|lfs>
ah ok cool I'll give that a shot
<jaeger>
Might or might not help, just a guess
<brian|lfs>
if not just wrote arch iso to another flash drive I'll have to just mount the crux iso and isntall that way
<brian|lfs>
no kernel panic and never boots either
<brian|lfs>
just keeps giving the USB error over and over lol
<jaeger>
bummer
<brian|lfs>
and complains about each nvme device
<brian|lfs>
how do I disable nouveau from grub I forget arch doesn't like the nouveau driver
<brian|lfs>
guess the card is too old
<jaeger>
Not sure, check the parameters for the nouveau module in the kernel docs, I guess
<brian|lfs>
its nouveau.modeset=0
<brian|lfs>
I got the arch iso booted and ssh started
<brian|lfs>
ok I've got the crux flash drive mounted how would I install all the packages from anothjer linux live environment
<jaeger>
couple of ways... you could use the pkgutils tarball from the ISO to install the packages, or you can just untar the ones you want into the destination... but the latter option won't have a package database so you'd need to fix that later
<brian|lfs>
ok I"m using pkgutils figured it out
<brian|lfs>
I have notes form a long time ago on doing that
<brian|lfs>
pkgadd -r /mnt $p 4.84s user 0.28s system 27% cpu 18.703 total
<brian|lfs>
omg 27% cpu usage lol
<brian|lfs>
ok this is weird I don't see any data
<brian|lfs>
jsut a couple empty folders like etc
<jaeger>
odd
brian__ has joined #crux
brian|lfs has quit [Ping timeout: 245 seconds]
brian__ is now known as brian|lfs
<brian|lfs>
jaeger, how would I extract all the packages to install them since pkgadd didn't seem to work?
<brian|lfs>
I have the packages moounted in /root/crux
<jaeger>
What command did you use with pkgadd? It should work
SiFuh has quit [Remote host closed the connection]
<jaeger>
Something like: for P in /path/to/packages/*.pkg.tar.xz; do pkgadd -r /mnt ${P}; done
SiFuh has joined #crux
<jaeger>
They're just tarballs, though, so you can just use "tar Jxf" or "bsdtar xf" if needed
<brian|lfs>
ok then how would I register them as being installed
<jaeger>
after the system is working, pkgadd them again with -f
<brian|lfs>
ah ok that makes perfect sense
<brian|lfs>
how would I untar a whole folder full of files just a wild card like ^
<jaeger>
for F in *.pkg.tar.xz; do bsdtar -C /mnt -xf ${F}; done <-- something like that
<brian|lfs>
much better I guess pkgadd was broken extracting it on the arch iso
<brian|lfs>
ok installed and booted and flash drive moutned what opeions do I need with pkgadd t reinstall everything
<brian|lfs>
I figured it out not sure why -u didn't work for pkgadd all well
<jaeger>
-u wouldn't work if there wasn't a package db yet since it needs to know what's installed to upgrade
<brian|lfs>
I made a db manually with touch earlier odd
<brian|lfs>
I've never seen a kernel compile so fast as with 128 cores
<jaeger>
Well, touch would create it but not populate it with existing packages
<brian|lfs>
to sleep CRUX seems to be working fine maybe the kernel on the ISO is jsut too old who knows
dlcusa has quit [Ping timeout: 260 seconds]
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
tarxvfz has joined #crux
ardo has joined #crux
aardo has quit [Ping timeout: 260 seconds]
lavaball has joined #crux
ppetrov^ has joined #crux
tarxvfz has quit [Remote host closed the connection]
zorz has joined #crux
<r0ni>
so rust/cargo-c won't build with libgit2-1.8.0... is there something revdep isn't picking up i should rebuild? i jus keep downgrading libgit2 and build what i need then upgrade it... but wtf there has to be something i'm missing
<cruxbridge>
<tim> r0ni: can't confirm. is your rustc broken because of it? => rebuild rust
<r0ni>
i just rebuilt cargo-c bout to try revdep and then build rust and see
<r0ni>
i'm thinking there's something wrong with the arm64 ports but i'm just not sure what yet
<r0ni>
yep no matter what cargo wants libgit2.so.1.7
lavaball has quit [Remote host closed the connection]
<cruxbridge>
<tim> cargo is part of the rust package
<cruxbridge>
<tim> what does "revdep -vvv rust" return?
<r0ni>
i'm assuming the arm64 is using a bin 1.76 to build 1.77 and it deps off the old libgit2
<cruxbridge>
<tim> Oo
<cruxbridge>
<tim> so
<r0ni>
i can't find a way out of this circle lol
<cruxbridge>
<tim> if your rustc is broken and the Pkgfile might currently not catch that, you need to remove rust first then rebuild it. reason is that the Pkgfile tries to use system rust, if its available
<cruxbridge>
<tim> I need to check the logic for that
<cruxbridge>
<tim> it builds and runs just fine on my pi4 aarch64 fwiw
<r0ni>
hrm ok so rm rust and reinstall.
<r0ni>
its building!
<cruxbridge>
<tim> great
<braewoods__>
cruxbridge, your imitation of tim is spot on :P
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
dlcusa has joined #crux
<cruxbridge>
<tim> braewoods__: :>
tarxvfz has joined #crux
<r0ni>
revdep is now building cargo-c properly, so all seems well
ivandi has quit [Quit: WeeChat 4.2.1]
lavaball has joined #crux
ivandi has joined #crux
darfo_ has quit [Ping timeout: 264 seconds]
zorz has quit [Quit: leaving]
zorz has joined #crux
darfo has joined #crux
darfo_ has joined #crux
ppetrov^ has quit [Quit: Leaving]
darfo has quit [Ping timeout: 245 seconds]
tarxvfz has quit [Ping timeout: 260 seconds]
darfo_ has quit [Ping timeout: 256 seconds]
darfo has joined #crux
farkuhar has joined #crux
tarxvfz has joined #crux
lavaball has quit [Remote host closed the connection]