Show all posts by user
Discussions that don't fit anywhere else
Page 1 of 2 Pages: 12
Results 1 — 30 of 44
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
Problem solved in 5.0.4-1-ARCH #1 PREEMPT Sun Mar 24 23:39:21 UTC 2019 ! Network is fully working on the new kernel. It was connected to the pci bus issue, like mr Heiner Kallweit from Arch pointed out. Thanksby arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
Confirmed - kernel 5.0.0-1-ARCH #1 PREEMPT Tue Mar 5 05:19:51 UTC 2019 and exactly the same r8169 "error -5"by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
And this is not a good news... :( However hope dies last, so we'll see...by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
Did those all steps, with same result like @mpmc And modprobing r8169 module - no effect: $ sudo modprobe r8169 $ lsmod Module Size Used by adt7475 18222 0 hwmon_vid 2046 1 adt7475 hwmon 11907 1 adt7475 marvell_cesa 31895 0 i2c_mv64xxx 8110 0 nfsd 274299 13 ip_tablesby arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
uname -rv 4.20.12-1-ARCH #1 PREEMPT Tue Feb 26 01:20:37 UTC 2019 And of course still no network (with the same error message). Tried unplug and plug again the cable but either dmesg not showing anything nor the LAN led is not reacting at all (like turned off completely) I did the same on the "working" kernel, and got this: [ 97.014963] r8169 0000:01:00.0 eth0: Link is Down [by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
Yes, I also hope it will work on Debian, then as a reverence I could present it somewhere on Archlinux forum. Thanks for your work Bodhi.by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
The new kernel: uname -rv 4.20.10-1-ARCH #1 PREEMPT Sat Feb 16 00:54:41 UTC 2019 the old behaviour: dmesg | grep r816 [ 2.019182] r8169 0000:01:00.0: enabling device (0140 -> 0143) [ 2.025865] r8169 0000:01:00.0 (unnamed net_device) (uninitialized): rtl_phyar_cond == 0 (loop: 20, delay: 25). [ 2.036246] r8169: probe of 0000:01:00.0 failed with error -5by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
Yes, the 4.19.9 works without problems for me as I mentioned before. And I can understand you are a busy man, just thanks for watching this thread.by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
And you have an identical chip on your NSA310? (lspci -knn output if possible - also from the NSA310S)by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
@mpmc I wonder if you have the same motherboard as me maybe? You have the zyxel 310 or the newer 310s? Could you please show the output of this command? lspci -nn 00:01.0 PCI bridge [0604]: Marvell Technology Group Ltd. 88F6281 ARM SoC [11ab:6281] (rev 03) 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:81by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
So maybe there's a chance that somebody from the developers will notice this problem yet... I'm still waiting for next versions to try then.by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
So you have the same problem as mine - it looks, that the newer kernel isn't perfect. Nobody noticed that besides us yet? I couldn't find noone with this problem in the whole google. Weird...by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - Realtek drivers r8168/r8169 - 5 years ago
Yes, thank you.by arti74 - Debian
Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - Realtek drivers r8168/r8169 - 5 years ago
Hello ! I didn't noticed your message - I need to set up some email notifications - anyway, I'm happy to hear from you. My current - working environment: uname -rv 4.19.9-1-ARCH #1 PREEMPT Fri Dec 14 03:34:38 UTC 2018 The recent kernel (and tried all previous 4.20 versions) uname -rv 4.20.7-1-ARCH #1 PREEMPT Thu Feb 7 01:09:27 UTC 2019 Edit - maybe more useful will be to shoby arti74 - Debian
Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 5 years ago
Hello everybody. I know it is Debian mostly forum, but got great help in the past here, so I'll try again here. The problem is, that my wired network don't works since the new 4.20 kernel - either on my default r8169 drivers (built in kernel) or the installed r8168. Everything works fine in my 4.19.9 kernel. When on r8169 I get: dmesg | grep r8169 [ 1.839771] r8169 0000:01:00.0:by arti74 - Debian
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Sensors problem solved! Quick Moonman reaction for my request and in the new 4.16.9-2-ARCH kernel there's the adt7475 driver already. I modprobed it, I also the i2c-dev (I mention this because I don't remember if I did it before and sensors wasn't working right away after modprobing adt7475) The results: Next adapter: mv64xxx_i2c adapter (i2c-0) Do you want to scan it? (YES/nby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Yes indeed no NSA310 there. It's sad... There's the NSA320 but it's obviously not the same. So I assume we can do nothing more in this matter, nevertheless I'm greatful for your help with all my problems. I should find some developers of Arch and ask them to extend support also for this Zyxel device. Best wishes, Artur.by arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
According to this https://archlinuxarm.org/forum/viewtopic.php?p=31201#p31201 I should have this module: adt7475 - but I haven't. modprobe adt7475 modprobe: FATAL: Module adt7475 not found in directory /lib/modules/4.16.8-1-ARCH From the thread about nsa320: lsmod Module Size Used by i2c_mv64xxx 4654 0 adt7475 13961 0 hwmon_vidby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Quotebodhi Just unzip them all and modprobe the nsa320-hwmon and lm85. See what the kernel detects (lm85 or adt7476). It must remain gzipped, otherwise I can not modprobe it. I tried them all: $ sudo modprobe nsa320-hwmon $ sudo modprobe lm90 $ sudo modprobe lm85 $ sudo modprobe lm77 $ sudo modprobe lm75 $ sudo modprobe lm63 $ sudo modprobe hwmon $ sudo modprobe hwmon-vid $ lsmod Mby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Thank you for this. ls -l /sys/class/hwmon/hwmon0 I don't have any hwmon file in my system, beside this: sudo find / -name *hwmon* -print /usr/lib/modules/4.16.8-1-ARCH/kernel/drivers/hwmon/nsa320-hwmon.ko.gz $ ls /usr/lib/modules/4.16.8-1-ARCH/kernel/drivers/hwmon/ hwmon-vid.ko.gz lm63.ko.gz lm77.ko.gz lm90.ko.gz hwmon.ko.gz lm75.ko.gz lm85.ko.gz nsa320-hwmon.ko.gz lsby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
WOL went smooth, I'm afraid those sensors is a tough nut to crack... (at least on my Zyxel) The commands below shows something (not sure it is much of help though) $ sudo i2cdetect 0 password for rtorrent: WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0. I will probe address range 0x03-0x77. Continue? 0 1 2 3 4 5by arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
I'll try to read yet about this, but now I should go to sleep - from tomorrow I have a work marathon couple days. I wish I could let the nsa310 stay on from the morning, to have access to it from work, but as I mentioned it's not quiet and my wife probably again doesn't let me.. I should hide it deep so that it won't be heard. That's why it is important for me to instby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
When I connect an USB - the led is green. No adt74 module found.by arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Actually I found similar example of the internet here: https://archlinuxarm.org/forum/viewtopic.php?f=27&t=3708&start=90#p31201 But you're right - I may have something more LM85 related.. QuoteDTS said it is adt7476a Maybe I read somewhere that the driver is still adt7475.. There's this yet: sudo i2cdetect -l i2c-0 i2c mv64xxx_i2c adapter I2C adapteby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Thank you This is what dmesg shows: $ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.16.8-1-ARCH (builduser@leming) (gcc version 8.1.0 (GCC)) #1 PREEMPT Fri May 11 02:49:15 UTC 2018 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] OF: fdt: Macby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
I have one major problem yet to solve, and this is more connected to Archlinux and I didn't got any reply there for this. I would like to apologize if it this is not place to write about it, maybe a new thread would be necessary or something. Besides I bother you often with my problems here and I'm not sure you can do something in this matter: no sensors recognized on my machine. I almoby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
WOW - great! That was it - is working now! Thank you sooo much.by arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
I copied the disk, but it won't boot - the big one. U-Boot 2016.09.01-1 (Oct 10 2016 - 23:14:18 -0600) Arch Linux ARM Zyxel NSA310 SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out MV88E1318 PHY initialized on egiga0 IDE: Bus 0: OK Bus 1: not available Devicby arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Another great advise - thank you Bodhi!by arti74 - uBoot
Re: NAND errors - BAD eraseblocks - how to fix it? NSA310, Archlinux 4.4.97-1-ARCH, no chance for a new uBoot? - 6 years ago
Thank you! I will do it this way tomorrow and report back (I like the tar option - but I wonder if the speed is the same for both).by arti74 - uBoot
Page 1 of 2 Pages: 12