I updated to the 18.08 Genode release, built a Sculpt image, then booted it on my Dell Latitude 6430u laptop. I discovered that the WiFi driver, which worked in 18.05 (Sculpt TC) no longer works properly. In particular, the WiFi driver detects the access points and can connect to them, but doesn't get an IP address. I tried multiple access points, both my wireless router and my phone. With my phone, I used a clean lowercase alphabetic SSID ("bensphone"), to avoid any issues with problematic characters. I am using an Intel Ultimate-N 6300 wireless card.. Wired networking still works.
Hello Ben,
* Nobody III hungryninja101@gmail.com [2018-08-30 23:38:47 -0600]:
I updated to the 18.08 Genode release, built a Sculpt image, then booted it on my Dell Latitude 6430u laptop. I discovered that the WiFi driver, which worked in 18.05 (Sculpt TC) no longer works properly. In particular, the WiFi driver detects the access points and can connect to them, but doesn't get an IP address. I tried multiple access points, both my wireless router and my phone. With my phone, I used a clean lowercase alphabetic SSID ("bensphone"), to avoid any issues with problematic characters. I am using an Intel Ultimate-N 6300 wireless card.. Wired networking still works.
as noted in the release notes, support for 6000er cards has regressed with the new driver. The cause is still unknown and we are working on a fix.
(It looks like some kind of race or timing issue as most of the time the packets submitted to the firmware are not acknowledged but sometimes it works just fine and the behaviour is influenced by debug messages.)
Regards,
Okay, it looks like I missed that earlier. Is there an issue open on GitHub?
On Fri, Aug 31, 2018 at 2:05 AM Josef Söntgen < josef.soentgen@genode-labs.com> wrote:
Hello Ben,
- Nobody III hungryninja101@gmail.com [2018-08-30 23:38:47 -0600]:
I updated to the 18.08 Genode release, built a Sculpt image, then booted
it
on my Dell Latitude 6430u laptop. I discovered that the WiFi driver,
which
worked in 18.05 (Sculpt TC) no longer works properly. In particular, the WiFi driver detects the access points and can connect to them, but
doesn't
get an IP address. I tried multiple access points, both my wireless
router
and my phone. With my phone, I used a clean lowercase alphabetic SSID ("bensphone"), to avoid any issues with problematic characters. I am
using
an Intel Ultimate-N 6300 wireless card.. Wired networking still works.
as noted in the release notes, support for 6000er cards has regressed with the new driver. The cause is still unknown and we are working on a fix.
(It looks like some kind of race or timing issue as most of the time the packets submitted to the firmware are not acknowledged but sometimes it works just fine and the behaviour is influenced by debug messages.)
Regards,
Josef Söntgen Genode Labs
http://www.genode-labs.com/ · http://genode.org/ _______________________________________________ Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users
I opened an issue on GitHub: https://github.com/genodelabs/genode/issues/2973
On Fri, Aug 31, 2018 at 1:33 PM Nobody III hungryninja101@gmail.com wrote:
Okay, it looks like I missed that earlier. Is there an issue open on GitHub?
On Fri, Aug 31, 2018 at 2:05 AM Josef Söntgen < josef.soentgen@genode-labs.com> wrote:
Hello Ben,
- Nobody III hungryninja101@gmail.com [2018-08-30 23:38:47 -0600]:
I updated to the 18.08 Genode release, built a Sculpt image, then
booted it
on my Dell Latitude 6430u laptop. I discovered that the WiFi driver,
which
worked in 18.05 (Sculpt TC) no longer works properly. In particular, the WiFi driver detects the access points and can connect to them, but
doesn't
get an IP address. I tried multiple access points, both my wireless
router
and my phone. With my phone, I used a clean lowercase alphabetic SSID ("bensphone"), to avoid any issues with problematic characters. I am
using
an Intel Ultimate-N 6300 wireless card.. Wired networking still works.
as noted in the release notes, support for 6000er cards has regressed with the new driver. The cause is still unknown and we are working on a fix.
(It looks like some kind of race or timing issue as most of the time the packets submitted to the firmware are not acknowledged but sometimes it works just fine and the behaviour is influenced by debug messages.)
Regards,
Josef Söntgen Genode Labs
http://www.genode-labs.com/ · http://genode.org/ _______________________________________________ Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users
-
Josef Söntgen -
Nobody III