** Changed in: linux-raspi2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806108
Title:
Ethernet not working on rpi3 b+
To manage notifications about this
This bug was fixed in the package linux-raspi2 - 4.15.0-1030.32
---
linux-raspi2 (4.15.0-1030.32) bionic; urgency=medium
* linux-raspi2: 4.15.0-1030.32 -proposed tracker (LP: #1806661)
* Ethernet not working on rpi3 b+ (LP: #1806108)
- lan78xx: Move enabling of EEE into PHY
This bug was fixed in the package linux-raspi2 - 4.15.0-1030.32
---
linux-raspi2 (4.15.0-1030.32) bionic; urgency=medium
* linux-raspi2: 4.15.0-1030.32 -proposed tracker (LP: #1806661)
* Ethernet not working on rpi3 b+ (LP: #1806108)
- lan78xx: Move enabling of EEE into PHY
** Also affects: linux-raspi2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did get some errors when trying to install this, but I copied the
vmlinuz and initrd to /boot/firmware and I can get an ip now.
I retried the install and still get the errors, here's the log of that:
ubuntu@ubuntu:/mnt$ sudo dpkg -i
** Description changed:
+ [Impact]
+
+ Booting this image:
+
+ http://cdimage.ubuntu.com/releases/18.04/beta/ubuntu-18.04-beta-
+ preinstalled-server-arm64+raspi3.img.xz
+
+ on a RaspberryPi 3B+, the ethernet port is not working.
+
+ Moving the EEE enabling into the PHY initialisation
Nice work on this effort Paolo!
I followed all the progress in IRC.. nice and handy that smb had a
devise to test too.
Thank you
Terry
On 12/05/2018 06:27 AM, Paolo Pisati wrote:
> And for the record, the source code for the above kernel is here:
>
>
And for the record, the source code for the above kernel is here:
https://git.launchpad.net/~p-pisati/ubuntu/+source/linux/log/?h=b-raspi2_lp1806108
and this is the actual fix:
Ok, new and final kernel:
http://people.canonical.com/~ppisati/lp1806108/
This the kernel has the hotfix for lp806108, get this tested and if it's
ok, i'll push it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please, test linux-image and linux-modules from
http://people.canonical.com/~ppisati/lp1806108/, after 'dpkg -i' both,
copy vmlinuz and initrd.img from /boot to /boot/firmware.
The image still complains on boot though:
'Failed to connect to https://changelogs.ubuntu.com/meta-release-lts.
Check
Another issue: uboot's 'saveenv' doesn't work - stop at the uboot
prompt, type 'saveenv' and the bootloader will "panic" - so there's no
way to change the bootloader environment.
And a question: why copying vmlinuz and initrd to mmcblk0p1 and then
loading from there, when we can point uboot to
@Steve
My understanding from Paul is that we're only seeing this issue
currently with the arm64 image we tested last week. While we're still
standing up the b+ automated testing infrastructure for core18 (we
currently need to working around some strange snapd behaviors), we just
tested manually
This is the first time I think we've been asked to test something on
rpi3 arm64. The core 16 images we normally test the kernel snaps on are
4.4 based. I did try this on a core18 image and was unable to reproduce
the problem, but it's not arm64. So this could be arm64 related, or as
Paolo seems to
Ok, i can reproduce the issue, and while debugging it i found something
else:
1) flash-kernel is broken
...
ubuntu@ubuntu:~$ sudo dpkg -i
linux-image-4.15.0-1029-raspi2_4.15.0-1029.31~1806108take2_arm64.deb
dpkg: warning: downgrading linux-image-4.15.0-1029-raspi2 from 4.15.0-1029.31
to
ubuntu@raspi64:~$ uname -a
Linux raspi64 4.15.0-1029-raspi2 #31-Ubuntu SMP PREEMPT Sat Nov 17 00:01:10 UTC
2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@raspi64:~$ ifconfig eth0
eth0: flags=4163 mtu 1500
inet 192.168.2.185 netmask 255.255.255.0 broadcast 192.168.2.255
inet6
Which version of the linux-raspi2 kernel last had ethernet working
reliably?
Paul, should this bug not have blocked release of 4.15.0-1029.31 to
-updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As a work-around, I've noticed on the B+ that if you keep the Ethernet
disconnected until it booting and then connect it when you see it hit
"... Networking" then it'll pick up DHCP and then run cloud-init next
happily.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: linux-raspi2 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806108
Title:
Ethernet not working on rpi3 b+
To manage notifications about
18 matches
Mail list logo
