guido_rokepo has quit [Remote host closed the connection]
guido_rokepo has joined #crux
ppetrov^ has quit [Quit: Leaving]
DaViruz has quit [Ping timeout: 268 seconds]
DaViruz has joined #crux
ppetrov^ has joined #crux
harthan has joined #crux
harthan has quit [Client Quit]
guido_rokepo has quit [Quit: guido_rokepo]
guido_rokepo has joined #crux
guido_rokepo has quit [Remote host closed the connection]
guido_rokepo has joined #crux
mnkydeth has joined #crux
<mnkydeth>
So, I just built a new rig using a Xeon 2495x. I'm having a problem with the Crux install. After it loads the kernel and goes to the automatic login. I get, module is unknown, INIT: Id "c1" respawning too fast: disabled for 5 minutes. I'm not sure how to fix this issue from the boot ISO. I am using it on a usb stick, fyi.
<mnkydeth>
Switching to different tty's they are also unresponsive.
<mnkydeth>
I have tried the release 3.7 ISO and the updated crux.ninja ISO.
<mnkydeth>
The install process works as expected on several other machines I have. So, I have a feeling it's something specific with this new platform.
<mnkydeth>
Hmm, I did use Fedora writer to write the iso to usb stick.
<SiFuh>
Just use dd
<mnkydeth>
Yep, trying it now
<mnkydeth>
brb, testing
mnkydeth has quit [Quit: leaving]
mnkydeth has joined #crux
<mnkydeth>
Thank you ... Guess I am no longer using Fedora media writer
<mnkydeth>
I was able to get to the command line and start the install process.
<jaeger>
mnkydeth: I just fixed and built another updated ISO for this issue
<jaeger>
Just about to boot it to verify
<mnkydeth>
Ok, I honestly thought it was something specific with my new build. I can't say I ever ran into that problem before. And, it seemed like a common thing in the google searches. But no real ways to fix a boot/install ISO. That I could see.
<mnkydeth>
I'll stick with dd for now. I only use Fedora Media writer on my HTPC that has a windows install.
<jaeger>
I don't think this should have affected the release ISO but I'll go back and double check... the current issue was caused by pam_unix.so from linux-pam linking against libnsl which wasn't available in the ISO boot
<jaeger>
Oh, I didn't see the comment about the install process working on other machines, heh. Well, in either case the latest updated ISO was broken due to this pam_unix.so link.
<jaeger>
Otherwise it probably was a funky write to USB or something
<mnkydeth>
Yeah, as soon as I went to a Linux machine and did the dd write the Crux ISO worked as intended.