Ubuntu Images (Pinebook) 0.5.2-59 [May 25] | Ubuntu Minimal (PINE A64(+)) 0.5.2-59 [May 25] | Armbian - Ubuntu (SOPINE) 5.27 [May 22] | Android 7.1 (PINE A64(+)) v0.3.5-r61 [May 15] | Android 7.1 (Pinebook) v0.3.5-r61 [May 15] | Q4OS (Pinebook) 1803 [May 15] | Installer 2.0.0-beta.2 [May 13]

Getting Started | Visit the WIKI | IRC Logs | Forum Rules/Policy


NIC not visible after kernel update
#1
Hi,

Long-time lurker, first time poster.  I have been doing some work with my Pine64 2GB and came across the kernel-update.sh script and as I was having issues (and was hoping some missing kernel modules would be in the later release), I ran the script which determined that there was an update and it duly installed it.

Upon rebooting the Pine, everything came back but the network!  It doesn't appear to see the NIC at all now.
I had been previously forcing eth0 to 100MB F/D due to the gigabit issues, so I don't think it's related as even with the network connected, it doesn't even flash the connectivity LED any more to acknowledge a cable connected.


Is this a known problem?

I'll try again with a new memory card and the original image to rule out a hardware issue, but is there a way I can wind back the new kernel to the one which I was previously running before the script? Does it back up the original kernel folder?

It's difficult to use the Pine via the HDMI as it oversizes so badly that you can't read what you are typing at the bottom of the screen, so I've only done limited investigation at this stage so I'm not even sure exactly which version of kernel it has installed (whatever the latest is as of today I guess)

Thanks in advance.
Reply
#2
Not sure what happened, but after looking through pine64_update_kernel.sh and checking what files it had updated to get to 3.10.104-1 and reversing those files back to 3.10.102.2 eth0 is now working again.

Stranger still, since going back to the previous kernel, the NIC fails to work if I leave my line in /etc/network/interfaces which was working before to force the NIC to 100Mb !!

Now, I have to wait for it to fail 1000Mb, then use ethtool via SSH to fix to 100Mb for that boot session.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
Question Debian Jessie with 4.x.y kernel and complete hardware support? Spark 2 461 04-24-2017, 09:56 PM
Last Post: Spark
  Debian Jessie Images (3.10.102 BSP Kernel) New Release lenny.raposo-pine64.pro 257 66,503 04-12-2017, 10:54 AM
Last Post: dontpostalot
  Adding a missing kernel module spz2k 8 642 01-10-2017, 06:22 AM
Last Post: xalius
  [SOLVED]Problem Compiling modules: Recipe | kernel-headers not found acenos 0 273 12-14-2016, 09:11 AM
Last Post: acenos
  After update - won't power up with HDMI connected UnixOutlaw 6 610 09-09-2016, 01:43 PM
Last Post: janeku
  Debian Jessie (4.7.0-rc1 Kernel) Images fire219 4 2,487 07-20-2016, 02:36 PM
Last Post: umiddelb
  i2c-bus kernel modules robertvaldimarsson 15 853 06-07-2016, 01:48 PM
Last Post: robertvaldimarsson
  Debian kernel upgrade question jl_678 2 613 04-18-2016, 05:54 PM
Last Post: jl_678

Forum Jump:


Users browsing this thread: 1 Guest(s)