braewoods has quit [Remote host closed the connection]
braewoods has joined #crux
<brian|lfs>
hello all
<brian|lfs>
just installed CRUX latest kernel 6.5.7 and can't get my interl 25V to work
<brian|lfs>
it shows the nic but unfunctioanl with our without DHCP
<brian|lfs>
any ideads
<ukky>
upload output of 'ip link show'
<jaeger>
'lspci | grep -i net' might help, too
<brian|lfs>
how would I upload with no internet lol
<brian|lfs>
if I have no device in net will it try every device it sees
<jaeger>
Those should be pretty short, could just re-type them or take a phone picture or something
<jaeger>
dhcpcd does do multiple devices if it can
<ukky>
dhcpcd handles multiple networks only when no specific interface is specified on the command line. If specified, then only that interface is handled. Unless -M options is specified (then all interfaces are handled)
<ukky>
brian|lfs: copy-paste here output of 'ps axf | grep -v grep | grep dhcpcd', and 'lspci | grep -i net'
<jaeger>
ukky: have you tried pgrep? for example 'pgrep -lfa dhcpcd'
<ukky>
jaeger: I know commands I am using sometimes are not efficient :-)
<brian|lfs>
ya I know I tried with and without dhcp
<brian|lfs>
and its not working the nic
<brian|lfs>
I don't think its loading correctly in CRUX became the device names are completely different in debian
<ukky>
dhcpcd will manage all network devices, no need to specify specific interface name
<ukky>
but you have to set TYPE to DHCP
<ukky>
are your network drivers compiled-in, or loaded as modules? are you starting them if modules?
<brian|lfs>
ya I know I tried a specific name with dhcp befoe
<brian|lfs>
there modules
<brian|lfs>
while in debian how do I see what modules
<ukky>
use lsmod to see modules loaded
<brian|lfs>
copy of my modules
<brian|lfs>
I see the wired one what would the wireless card be called
<brian|lfs>
I mean I see the wireless what would the wired be called
<ukky>
Your WiFi PCIe device is 00:14.3, and your wired PCIe device is 08:00.0
<brian|lfs>
ok so where do I put module names to load them
<ukky>
udev should auto-load them. If not, then you have to figure out why. /etc/modules and /etc/modules.conf are usually where modules are loaded from at boot.
<ukky>
you can try manually loading your network modules and then restart /etc/rc.d/net to see if it fixes network issue
<brian|lfs>
good points
<brian|lfs>
I just created /etc/modules-load.d and add what I think are my network drivers
<brian|lfs>
going to reboot and see what happens
<brian|lfs>
its another machine so I'm not getting booted
<jaeger>
ukky: all good, just mentioning it in case you didn't know about it
<jaeger>
brian|lfs: 'lspci -k' can also tell you which module is in use by a specific device, so if it works when booted into another distribution, check that and see if it exists in your kernel config
<ukky>
jaeger: I actually didn't know about pgrep. Too many things to remember.
<jaeger>
I know the feeling
<ukky>
brian|lfs: Kernel modules in CRUX are loaded from /etc/rc.modules, which is called from /etc/rc.
<brian|lfs>
I figured it out
<brian|lfs>
my modduels where all compressed as xz which I guess CRUX doesn't support out of the box
<brian|lfs>
so no modules were loading
<ukky>
brian|lfs: You have two options: 1) Adjust your kernel options to work with CRUX; 2) Patch CRUX ports to work with your kernel options
<brian|lfs>
ya I know
<brian|lfs>
but would most people prefer their modules compressed
<brian|lfs>
wouldn't
<ukky>
depends on many things. my elf binaries, all of them, are not even stripped, as I prefer to keep debug info.
<brian|lfs>
I probably should of made a list of all the packages that need their footprints updated.all well
<brian|lfs>
other then that no issues everything built fine