Re: APU2C4 information (was Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4)
Am Sat, 3 Sep 2016 13:38:14 -0700 Adrian Chaddschrieb: > hi, > > no, ar988x is 11ac, and i haven't finished the port. > > > -a > But anyway it is a nice ring to my eyes/ears to see/read, that you're working on it ;-) My thank you in advance! Kind regards, Oliver > > On 3 September 2016 at 06:36, O. Hartmann wrote: > > Am Sat, 3 Sep 2016 15:25:17 +0200 > > Guido Falsi schrieb: > > > >> On 09/03/16 15:11, O. Hartmann wrote: > >> > Am Sat, 3 Sep 2016 14:01:15 +0200 > >> > Michael Tuexen schrieb: > >> > > >> >>> On 03 Sep 2016, at 13:24, Guido Falsi wrote: > >> >>> > >> >>> On 09/03/16 13:08, Michael Tuexen wrote: > >> > On 03 Sep 2016, at 12:55, Oliver Böttcher > >> > wrote: > >> > > >> > Am Freitag, den 02.09.2016, 22:09 +0200 schrieb Guido Falsi: > >> >> I think you should open a bug report and post the number here so > >> >> feedback about this can be collected there. > >> > > >> > Bug report filed [1]. I just noticed that the serial console is not > >> > working on >=11.0 > >> > > >> > The update from 10.3 to 11.0 worked but has no output opon boot in > >> > 11.0. > >> I'm running FreeBSD head on an apu2c4 without any problems, the serial > >> console is working. > >> > >> However, I do have > >> > >> console="comconsole" > >> comconsole_speed="115200" > >> > >> in /boot/loader.conf. > >> It is not using ZFS and it is booting from an m-SATA SSD. Which boot > >> device > >> are you using? > >> > >> >>> > >> >>> SO it looks like a default configuration issue. > >> >>> > >> >>> This can explain why my custom nanobsd images work, I have a console > >> >>> configuration in loader there. > >> >> The default console speed of the apu2 is 115200, the one from FreeBSD > >> >> isn't. > >> >> Without the above setting you have to use 115200 first to see the BIOS > >> >> output > >> >> and than change the speed to whatever FreeBSD uses as its default. Using > >> >> the above settings you can use the same speed for both. > >> >> > >> >> Best regards > >> >> Michael > >> >>> > >> >>> -- > >> >>> Guido Falsi > >> >>> ___ > >> >>> freebsd-current@freebsd.org mailing list > >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> >>> To unsubscribe, send any mail to > >> >>> "freebsd-current-unsubscr...@freebsd.org" > >> >> > >> > > >> > I do not want to "kidnap/threadnap" the thread, but I have a question: > >> > My APU 2C4 > >> > is underway and I'm curious about whether it would boot via UEFI or not? > >> > > >> > >> I don't think it has UEFI support. These boards come with a traditional > >> old style BIOS. > > > > All right. It is coreboot, if not mistaken and I read something about a > > UEFI support > > there, but forgot whether this is futural agenda or real by now. > > > >> > >> > > >> > I also ordered mine with a Atheros AR9882 based WiFi card and I'm also > >> > curious > >> > about whether this chip is working with 12-CURRENT or not. The AR9880, > >> > more > >> > powerful and newer, seems also available for this APU, but it is more > >> > expensive > >> > and I didn't took the risc ... > > > > I checked the WiFi webpage at FreeBSD.org and these specific adapters are > > not > > mentioned there. The support of AP capable WiFi adapters is rather limited > > (to > > Atheros types), on Linux, more adapters seem to provide the AP > > functionality. > > Therefore, my question. > >> > >> I don't know this device. Atheros cards have very good support in > >> general through the ath(4) driver, if you know the PCI ID of the device > >> you can check in the sources if it's known. > >> > > I'll check and report back ;-) > > > > Thank you very much. > > > > Oliver > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" pgp9szrOLQIiV.pgp Description: OpenPGP digital signature
Re: APU2C4 information (was Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4)
hi, no, ar988x is 11ac, and i haven't finished the port. -a On 3 September 2016 at 06:36, O. Hartmannwrote: > Am Sat, 3 Sep 2016 15:25:17 +0200 > Guido Falsi schrieb: > >> On 09/03/16 15:11, O. Hartmann wrote: >> > Am Sat, 3 Sep 2016 14:01:15 +0200 >> > Michael Tuexen schrieb: >> > >> >>> On 03 Sep 2016, at 13:24, Guido Falsi wrote: >> >>> >> >>> On 09/03/16 13:08, Michael Tuexen wrote: >> > On 03 Sep 2016, at 12:55, Oliver Böttcher >> > wrote: >> > >> > Am Freitag, den 02.09.2016, 22:09 +0200 schrieb Guido Falsi: >> >> I think you should open a bug report and post the number here so >> >> feedback about this can be collected there. >> > >> > Bug report filed [1]. I just noticed that the serial console is not >> > working on >=11.0 >> > >> > The update from 10.3 to 11.0 worked but has no output opon boot in >> > 11.0. >> I'm running FreeBSD head on an apu2c4 without any problems, the serial >> console is working. >> >> However, I do have >> >> console="comconsole" >> comconsole_speed="115200" >> >> in /boot/loader.conf. >> It is not using ZFS and it is booting from an m-SATA SSD. Which boot >> device >> are you using? >> >> >>> >> >>> SO it looks like a default configuration issue. >> >>> >> >>> This can explain why my custom nanobsd images work, I have a console >> >>> configuration in loader there. >> >> The default console speed of the apu2 is 115200, the one from FreeBSD >> >> isn't. >> >> Without the above setting you have to use 115200 first to see the BIOS >> >> output >> >> and than change the speed to whatever FreeBSD uses as its default. Using >> >> the above settings you can use the same speed for both. >> >> >> >> Best regards >> >> Michael >> >>> >> >>> -- >> >>> Guido Falsi >> >>> ___ >> >>> freebsd-current@freebsd.org mailing list >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >>> To unsubscribe, send any mail to >> >>> "freebsd-current-unsubscr...@freebsd.org" >> >> >> > >> > I do not want to "kidnap/threadnap" the thread, but I have a question: My >> > APU 2C4 is >> > underway and I'm curious about whether it would boot via UEFI or not? >> >> I don't think it has UEFI support. These boards come with a traditional >> old style BIOS. > > All right. It is coreboot, if not mistaken and I read something about a UEFI > support > there, but forgot whether this is futural agenda or real by now. > >> >> > >> > I also ordered mine with a Atheros AR9882 based WiFi card and I'm also >> > curious about >> > whether this chip is working with 12-CURRENT or not. The AR9880, more >> > powerful and >> > newer, seems also available for this APU, but it is more expensive and I >> > didn't took >> > the risc ... > > I checked the WiFi webpage at FreeBSD.org and these specific adapters are not > mentioned > there. The support of AP capable WiFi adapters is rather limited (to Atheros > types), on > Linux, more adapters seem to provide the AP functionality. Therefore, my > question. > >> >> I don't know this device. Atheros cards have very good support in >> general through the ath(4) driver, if you know the PCI ID of the device >> you can check in the sources if it's known. >> > I'll check and report back ;-) > > Thank you very much. > > Oliver ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: APU2C4 information (was Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4)
Am Sat, 3 Sep 2016 15:25:17 +0200 Guido Falsischrieb: > On 09/03/16 15:11, O. Hartmann wrote: > > Am Sat, 3 Sep 2016 14:01:15 +0200 > > Michael Tuexen schrieb: > > > >>> On 03 Sep 2016, at 13:24, Guido Falsi wrote: > >>> > >>> On 09/03/16 13:08, Michael Tuexen wrote: > > On 03 Sep 2016, at 12:55, Oliver Böttcher > > wrote: > > > > Am Freitag, den 02.09.2016, 22:09 +0200 schrieb Guido Falsi: > >> I think you should open a bug report and post the number here so > >> feedback about this can be collected there. > > > > Bug report filed [1]. I just noticed that the serial console is not > > working on >=11.0 > > > > The update from 10.3 to 11.0 worked but has no output opon boot in > > 11.0. > I'm running FreeBSD head on an apu2c4 without any problems, the serial > console is working. > > However, I do have > > console="comconsole" > comconsole_speed="115200" > > in /boot/loader.conf. > It is not using ZFS and it is booting from an m-SATA SSD. Which boot > device > are you using? > > >>> > >>> SO it looks like a default configuration issue. > >>> > >>> This can explain why my custom nanobsd images work, I have a console > >>> configuration in loader there. > >> The default console speed of the apu2 is 115200, the one from FreeBSD > >> isn't. > >> Without the above setting you have to use 115200 first to see the BIOS > >> output > >> and than change the speed to whatever FreeBSD uses as its default. Using > >> the above settings you can use the same speed for both. > >> > >> Best regards > >> Michael > >>> > >>> -- > >>> Guido Falsi > >>> ___ > >>> freebsd-current@freebsd.org mailing list > >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> To unsubscribe, send any mail to > >>> "freebsd-current-unsubscr...@freebsd.org" > >> > > > > I do not want to "kidnap/threadnap" the thread, but I have a question: My > > APU 2C4 is > > underway and I'm curious about whether it would boot via UEFI or not? > > I don't think it has UEFI support. These boards come with a traditional > old style BIOS. All right. It is coreboot, if not mistaken and I read something about a UEFI support there, but forgot whether this is futural agenda or real by now. > > > > > I also ordered mine with a Atheros AR9882 based WiFi card and I'm also > > curious about > > whether this chip is working with 12-CURRENT or not. The AR9880, more > > powerful and > > newer, seems also available for this APU, but it is more expensive and I > > didn't took > > the risc ... I checked the WiFi webpage at FreeBSD.org and these specific adapters are not mentioned there. The support of AP capable WiFi adapters is rather limited (to Atheros types), on Linux, more adapters seem to provide the AP functionality. Therefore, my question. > > I don't know this device. Atheros cards have very good support in > general through the ath(4) driver, if you know the PCI ID of the device > you can check in the sources if it's known. > I'll check and report back ;-) Thank you very much. Oliver pgpHv46y53ZmG.pgp Description: OpenPGP digital signature