Date: Mon, 16 Jul 2018 10:06:49 +0200 From: Ruben <mail@osfux.nl> To: Stefan Bethke <stb@lassitu.de> Cc: freebsd-stable@freebsd.org Subject: Re: MMC problem on APU2 with 11.2 Message-ID: <76761a83-2150-82aa-f54f-123278ef0932@osfux.nl> In-Reply-To: <559B4E8F-B972-4B57-8750-9EC767676C4D@lassitu.de> References: <3249944b-b463-5d7e-fcea-6de5ed394814@osfux.nl> <e0b5e210-2007-20a6-e9d0-6871d3ddfff9@menhennitt.com.au> <9dac175b-05f3-dbaa-8ea6-047b99a87e24@osfux.nl> <13BC6F2D-C369-43BC-A097-EB8CDDA71CD3@lassitu.de> <619064d4-c3fc-e8c9-b7c2-a91cd16ad1fd@osfux.nl> <559B4E8F-B972-4B57-8750-9EC767676C4D@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Stefan, What kind of device are you trying to connect? I'm not a contributer to FreeBSD code (so please don't expect any patches from me) but if its something I happen to have lying around somewhere I might be able to reproduce your problem. Kind regards, Ruben On 07/16/2018 08:22 AM, Stefan Bethke wrote: > Am 15.07.2018 um 13:32 schrieb Ruben <mail@osfux.nl>: >> I remember reading somewhere that PC Engines recommends running the "legacy" version of the firmware if the OS is FreeBSD/PFSense etc. Perhaps worth a try to "upgrade" to the legacy series of firmware? > I’ve just tried with 4.0.18, and the US3 ports don’t work any better. Instead, the EHCI controller complains about not being able to set up the device properly. I went back to 4.8.0.1. > > > Stefan >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76761a83-2150-82aa-f54f-123278ef0932>