OPNsense is based on FreeBSD, OpenWrt is on Linux, so no, no wonder it doesn't happen on a different OS with different drivers, etc.
2 Likes
it makes sense, i hope there would be a solution for it
So you can't grab the log from x86? Even they might failed in similar way, but different platform has different drivers, you can't use the log from another router for analysis.
2 Likes
the problem is that i get blind because no ssh and not connection, the thing is that somehow on my 3420v5 happened the thing, i issue a download, the connection went gone, but recovered, with the x86 happens the same but i wont get the conecction back, looks like is the realtek , and makes sense what @stangri said , maybe as linux will fail, its the second time it happens to me using this router x86 thats why i switched back to opensense but rollback to openwrt because i must run a shadowsocks server urgently, and opensense does not support that for now, you have to do a crazy workaround like setting up a openvpn and wrapp around it around the shadowsocks, its crazy, however i see its possible the problem is the driver, buuut i got another adapter , a usb to lan adapter, maybe would it work? if so, is there any guide to setting up an usb driver for it? or does openwrt supports it by default? with opensense it was just plug and play, looking the same here, ahh other thing i came back to openwrt here i got you all and you anytime you can help and collab with one's problem, in opensense forums its a problem cause the solution mostly does not arrives, forum is plagued with questions and few answers, still being a good OS, is stable but lacks features
but yes i cant grab the log, i can see it from vga only
its from my other device where the bug was recreated or happened
Hook up monitor/kb, try to save the log, maybe to USB stick, then view from other PC
Without log it would be just blind guess.
My previous reply also asked you about the hardware config, you also didn't tell us, so how do we guess if some hardware might be the cause of problem? (e.g. if you tell me you use i225, then I can think of lots of failure reports regarding this ethernet)
My personal experience: Linux seems to have better driver support than FreeBSD, usually you will find that hardware working on FreeBSD (which is OPNsense based on) will also work under Linux, you just need to install driver if it's not included in kernel by default.
2 Likes
sorry, its an dell desktop intel dual core processor 2nd gen 2gb ram ddr2, intel nic on motherboard and realtek nic in pci express i dont know how to redact information, im just too shameful of my old pc, it is really old
that is why im back here to openwrt, because linux looks better , and have what i need i just was too lame/noob so i cannot configure it properly, in this month in on a test phase so im just testing what could work and what not
This is all nice chit-chat (NOT), but without putting the exact hardware specs and error logs on the table, it's not going anywhere.
3 Likes
i do not know how to recreate the problem, yesterday cluster ran 20 hours ok and now it exploded two times sadly had to reboot because i stepped on a cable, but as far as i know it happened when i hit download and it started download, solved restarting, but looks like the culprit is the realtek im mostly sure
i agree... let me see what i can try to do to recreate the thing
Do the following (it's only showing hardware so nothing to redact):
opkg update
opkg install pciutils pciids lscpu
lscpu
lspci
2 Likes
lspci
eth0 intel 82567lm-3
eth1 rtl 8100/81011/8139 pci
dmesg eth0 realtek RTL8139 is not an 8139c+ compatible chip, use 8139too
That card is slow, both in terms of its rated throughput and the actual performance on the wire (rather high-CPU), but it's been sold by the millions and was pretty much ubiquitous in all kinds of devices. The linux driver itself is solid (and yes, I still have a few of them myself), so if that card is showing problems, it's more about hardware defects than fundamental issues with the driver.
--
Yes, you will see lots of whining about the chipset and its 'suboptimal' design from the BSD camp, but the linux drivers still work - solidly.
1 Like
How about lscpu ?
But Realtek 8139 is.....really a very old and crappy one, possible to get a newer one? The newer Realtek 1G ethernet is a lot better (it will be using another Realtek driver).
i got an usb>lan adapter , does openwrt support it by default? or will have to install drivers?
i got it @4$ , did not expected that much
If you mentioned OPNsense can see it, 99% Linux can support, but there exits some crappy USB LAN as well, you can plug it to the system, then run the following
opkg install usbutils
lsusb
1 Like
lsusb shows this
8151 Realtek usb 10/100 lan ... , is crappy? it was cheap tough, still if i do a ifconfig i dont see it
8151 is not just a 10/100 LAN if I am not wrong, so I am not sure which one you are actually using.
But is there any reason you don't want to post the full output and still want us to guess? Also your title mentioned x86-64, but if your previous "ubus call system board" output is true (which I can't find the CPU from Intel), you are running 32-bit not x86-64 version of OpenWrt which is conflicting.
1 Like
i think is x64 how can i know if is 64?