I’m sorry, but since this PC is a DIY build, it doesn’t have a brand name, so I can only provide a simple hardware list. I can not get the log file since it cannot boot.
After switching to a PC Gateway SX2860, it was able to boot successfully.
On the DIY PC that failed to boot, I noticed that the first two lines of text displayed at startup were much larger than usual.
It feels like the display resolution could not be properly detected.
However, when using Volumio 3, it can boot normally. It might be a hardware compatibility issue, so I will run it on another PC instead. Thank you.
Please read the first post again, you can give us at least the „inxi“ information and „lshw“, without it you will not get support.
We are not in a guessing game for your hw here, you must understand.
@Jersinger
the information you supplied is not enough for us to diagnose your problem.
Could you please read the following post and supply the requested information, using the wifi set up?
The “inxi” information will give us a complete hw report and the log may show why the Realtek ethernet driver is not working.
The log returns a URL, post it here please.
The reason why I was asking that information was because I wanted to know what the system reports. What the specs say is not what I needed, can find that myself on the net.
Your board specs does not seem to show onboard wlan, so how did you connect? Using a dongle?
When using wifi or ethernet, only one of the two will be active. Have you tried booting without the wifi dongle?
Still surprised the log didn‘t work, we might need to try something else.
However, it is Xmas time, so community support maybe slow the next few days.
Thanks… For the Wifi, I am using a MiniPCIe Card that is an AX210. These board are very specific kind of boards made for usually one task. I want to be able to support wifi and hard wired.
I will try without the PCI card…but that’s not the result I am looking for.
@Jersinger
While connected with wifi, you were able to start a log (but it did not finish).
On the same dev page, you would be able to enable ssh and then log in using user ‘volumio’ and password ‘volumio’ from a remote system (windows or linux).
Done that, execute
Then, either connect a fat32 formatted usb stick to the machine and copy the file to it, or use another linux or windows system to browse the network and fetch the file from your system, in one of the cases, in order to attach the logfile to this thread.
Do you have a keyboard and monitor connected?
In that case please attach a fat32 formatted usb stick, boot WITHOUT the wifi card.
Then ctrl-F1, which will give you a console.
Login with volumio/volumio, redirect the journalctl -b command to a file as shown a few posts above and copy it to the usb stick.
Please upload the file here.
well as you do not show the logs I requested, my support will be limited.
Again, no wlan board, boot with only eth connected. You decide. Reason: I wish to see eth to go past ‘carrier up’, without being overtaken by wifi.
v4.084 a must, fixing earlier network issues.
Thank you for that.
From the log it appears the driver gets loaded correctly, the interface works but then the carrier goes lost and while trying to bring up the device, no link beat is detected:
$ cat volumio-log.txt | grep eth0
cat volumio-log.txt | grep eth0
Dec 28 09:57:43 volumio1 kernel: r8169 0000:02:00.0 eth0: RTL8168h/8111h, 00:30:18:03:c7:fc, XID 541, IRQ 128
Dec 28 09:57:43 volumio1 kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Dec 28 09:57:44 volumio1 systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device - /sys/subsystem/net/devices/eth0...
Dec 28 09:57:45 volumio1 systemd[1]: Found device sys-subsystem-net-devices-eth0.device - RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (RTL8111/8168 PCI Express Gigabit Ethernet controller).
Dec 28 09:57:45 volumio1 systemd[1]: Started ifup@eth0.service - ifup for eth0.
Dec 28 09:57:47 volumio1 kernel: r8169 0000:02:00.0 eth0: Link is Down
Dec 28 09:57:47 volumio1 dhcpcd[684]: eth0: waiting for carrier
Dec 28 09:57:47 volumio1 dhcpcd[684]: eth0: carrier acquired
Dec 28 09:57:47 volumio1 dhcpcd[684]: eth0: IAID 18:03:c7:fc
Dec 28 09:57:47 volumio1 dhcpcd[684]: eth0: adding address fe80::c2ed:f5ec:26e5:9eeb
Dec 28 09:57:47 volumio1 dhcpcd[684]: control command: dhcpcd eth0
Dec 28 09:57:47 volumio1 dhcpcd[684]: eth0: carrier lost
Dec 28 09:57:47 volumio1 sh[846]: eth0=eth0
Dec 28 09:57:50 volumio1 ifplugd(eth0)[1121]: ifplugd 0.28 initializing.
Dec 28 09:57:50 volumio1 ifplugd(eth0)[1121]: Using interface eth0/00:30:18:03:C7:FC with driver <r8169> (version: 6.12.57-volumio)
Dec 28 09:57:50 volumio1 ifplugd(eth0)[1121]: Using detection mode: SIOCETHTOOL
Dec 28 09:57:50 volumio1 ifplugd(eth0)[1121]: Initialization complete, link beat not detected.
Dec 28 09:57:50 volumio1 ifplugd[1065]: start eth0...done.
Usually this means there is no connection with a switch or router, could you check your cable and your switch/ router. Are any leds blinking? On the switch/ router and PC?
Then it is possible, that the r8169 driver has an issue with this RTL8111H revision. Some installations (other linux systems) seem to have blacklisted the r8169 driver (preventing it from loading) and using an r8168 driver instead. I’m not sure if we can do that, need time to check this.