Exaga, I think my english does not help in explaining :)
In my /lib/firmware I don't have this file, and I can't find any reference of it neither in my old packages nor in the new one, and also on raspbian ( that I have d/loaded and installed to be sure that it wasn't an hardware problem ). It is not referenced in /var/adm/removed_packages and so is missing anywhere on the Pi. I will download your, and put it in the right directory but as far as I can tell it seems that is not such an important file. I case I miss something, my problem is with eth0, not on wifi. ( sorry to repeat this but in previous thread someone misunderstood the problem due to my bad english). And, for what I understand, in which package ( txz ) this file should be found ? Thanks a lot for you help. Pigi |
Quote:
brcmfmac43455-sdio.raspberrypi,4-model-b.txt = instructions for wireless device on RPi4 - has no effect on Ethernet. ;) OK! First thing to do as 'root' user is .... (this is an example - yours will be different) Code:
root@slackware:~# ifconfig -a Take a look to see if you have any Ethernet card in the list (eth*). If your Ethernet card is listed as 'eth0' - or 'eth1' like above - then get the MAC address of 'eth*'... Code:
root@slackware:~# nano -w /etc/udev/rules.d/70-persistent-net.rules Example - if b8:27:eb:35:b9:4e is the MAC address... Code:
# USB device 0x0424:0xec00 (usb) Then reboot the RPi4 device. When you use 'ifconfig -a' command and if there is NO Ethernet card listed... Code:
root@slackware:~# dmesg -t -l err > /tmp/dmesg_error.log Paste the output of 'dmesg' here for me to read please. If it works after rebooting no need to do anything else! :cool: |
From raspian boot, without any device connected on USB port I can see that my eth0 has dc:a6:32:35:7c:c4 as Mac address.
From "ifconfig -a | grep ether | grep 7c:c4" no one of my interfaces ha this mac address. In my udev rules file I have: Code:
root@casa:~# grep eth /etc/udev/rules.d/70-persistent-net.rules eth0 hs not his reference, but that's fine. It will get the first free eth ;) It does not seem to be an udev problem. If I look in the dmesg from the raspbian boot I can see: Code:
grep eth dmsg.raspbian If I search in my actual boot dmesg I can't find any reference to bcmgenet: Code:
root@casa:~# grep bcmgenet dmesg.latest If I search for my mac address on dmesg from raspbian I see: Code:
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:95:7C:C4 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=385f3658-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait Code:
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=1024 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:95:7C:C4 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 dwc_otg.lpm_enable=0 console=tty1 nofont root=/dev/sda3 rootfstype=ext4 rootwait ro cgroup_enable=memory In the kernel ( running ) config the bcmgenet is present and statically compiled: Code:
root@casa:~# gunzip -c /proc/config.gz | grep -i GENET Here the dmesg from last boot. And, in case you wanna give look, here the dmesg from raspbian: https://pastebin.com/TThAGixL Thanks again Pigi |
Quote:
So... just to clarify so we're understanding each other... the '/etc/udev/rules.d/70-persistent-net.rules' file you quoted contains NO 'eth0' device. Those listed are 'eth1' and 'eth2' and they do not have matching MAC addresses. Therefore, you need to carry out what I asked you to do in the previous post and you need to get rid of one of the entries in that file. Please do that and let me know how it goes, and if you need any further assistance then just post a reply. |
Exaga, I can't get rid of the lines in file, as I have those two interfaces and need them ( well at least one ).
My setup is the following: Code:
ISP-router I can, eventually, and just for test disconnect everything ( except for the SSD ), force an exit in rc.local ( where I start most part of my services ), do the tests, output the dmesg in a file but after that I have to have those lines otherwise my setup won't work and I'm disconnected from internet :doh: Do you want me to put the line with the mac address in /etc/udev/rules.d/70-persistent-net.rules ? Pigi |
Quote:
This is an easy fix when it happens to me (takes a couple of minutes at most) and we're already well into the second DAY deliberating over it ... so the choice is yours what you do from here. I would assume if you've gone to all this trouble of setting up such a configuration successfully then you would not require any help or advice from someone like me. |
Forget about MAC addresses for now. This is a misconfiguration issue. Remove everything from /etc/udev/rules.d/70-persistent-net.rules and save it to a separate file. That way you can restore your settings. Reboot. Report what ifconfig -a lists back here. Do not worry about having internet access while you troubleshoot.
How many network interfaces do you have? What static IP address are you setting for your internal network interface(s)? Do you not have a wireless network interface? What is its address? Which is your public internet facing network hardware? I believe your missing "eth0" is simply being renamed to either "eth1" or "eth2". |
Quote:
[EDIT] if it were me I'd probably try removing 'eth2' and changing 'eth1' to 'eth0' and going from there with one of the MAC addresses. Sooner or later it's going to hit the right one. Could be that 'eth0' has shifted to 'eth1' and 'eth1' has shifted to 'eth2'. If not then 'eth2' used to be 'eth0' and just needs renaming to 'eth0'. [EDIT #2] [sarcasm] oh wait but there's another NIC involved that... [/sarcasm] |
Quote:
So it's going to be... Code:
root@casa:~# nano -w /etc/udev/rules.d/70-persistent-net.rules Code:
root@casa:~# nano -w /etc/udev/rules.d/70-persistent-net.rules |
I think you can actually empty that file and the Pi will use the correct network interfaces after a reboot. I have never needed to use or edit that file and make my own persistant rules on any router.
|
Quote:
[EDIT] the order the interfaces initialise might also be a factor. I think they are processed in listed order so the primary NIC will need to be first in line for that. |
Quote:
|
Mac address for my eth0 is dc:a6:32:35:7c:c4
I have emptied the udev file, as suggested, removed any usb interface and rebooted the Pi. Th only thing connected to usb was the SSD disk Everything not tied to normal slackware configuration has been disabled. This is the ifconfig, after reboot: Code:
https://pastebin.com/ei1jzbTG Exaga I wasn't meaning to offend, in case it could have seemed. |
Quote:
I've been on slackware since slackware 4 and have got some experience in troubleshooting this udev problem. I've fighted with udev since it appears far long time ago :) What happens is that eth0 does not appears at boot with this installation and ( sorry Exaga if I repeat ) appears with another. Also, the mac address of my eth0 is dc:a6:32:35:7c:c4 No one of my interfaces has this mac address and nowhere in my rc.script/whatever I do change the mac address of any interface. Code:
root@casa:~# ifconfig -a | egrep "flags|ether" |
Quote:
Code:
root@casa:~# nano -w /etc/udev/rules.d/70-persistent-net.rules |
All times are GMT -5. The time now is 09:01 PM. |