Re: Weirdness in TTY & VT
On 0902T1712, Lundberg, Johannes wrote:
> Hi
>
> I'm porting some Linux code and have some weird behavior.
>
> In this (Linux) code fstat() and minor() is used on a /dev/tty file
> descriptor to get a tty number to map to. In FreeBSD this returns a number
> around 60-70 for st_rdev which means VT_ACTIVATE ioctl call will fail
> because it only allows values 0-12.
>
> Should not this be compatible with FreeBSD? If not, what is the FreeBSD way
> to do this?
>
> Is there some implementation missing in vt?
Device numbers don't really matter in FreeBSD. To get the current
VT number, use VT_GETACTIVE ioctl. Take a look at vidcontrol(1)
source to see how it's done ("vidcontrol -i active").
___
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: 11.0-RC2 and 12-CURRENT won't boot on apu2c4
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. Thanks 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: 11.0-RC2 and 12-CURRENT won't boot on apu2c4
> 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? Best regards Michael > > Thanks > 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" ___ 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: 11.0-RC2 and 12-CURRENT won't boot on apu2c4
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. -- 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"
Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4
> 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" smime.p7s Description: S/MIME cryptographic signature
Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4
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 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 ... Kind regards and thanks in advance, Oliver pgpp1yjghHGSa.pgp Description: OpenPGP digital signature
APU2C4 information (was Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4)
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. > > 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 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. -- 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"
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 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 pgpHv46y53ZmG.pgp Description: OpenPGP digital signature
Re: Installworld fails when /usr/bin and /usr/sbin are different FS / how to use symlinks in installworld?
Quoting Alexander Leidinger (from Sat, 03 Sep 2016 08:24:49 +0200): Quoting Bryan Drewery (from Fri, 2 Sep 2016 15:51:56 -0700): The error message is obvious, it tries to create a hardlink which is off course not possible when src and dest of the link are on different FS. My goal of an easy procedure (installworld into target datasets) doesn't work like this off course. Do we have an easy way of telling installworld to create symlinks instead of hardlinks, or alternatively a way to tell to copy instead of doing a hardlink if the install hits the cross-device case? Maybe falling back to symlink could be done. A copy-in-cross-fs-case would be the best solution, this way you don't need to care about having the right path (DESTDIR comes into the game here) specified on the comman line. I just checked, this 9.6k file the only case were a hardlink would be done outside the dataset. Changing LINKS to SYMLINKS for chown would be the most easy solution. This would work in the usual use cases (and surely in the normal FreeBSD use), but it would fail in the edge case were someone is using relative-path based execution of chgrp in a shifted-away location without using chroot and expecting it will use chown from the shifted-away location. Is this an use-case which we care about, or should we just change LINKS to SYMLINKS? Without the need to support DESTDIR, the install-argument "-l m" (hardlink if same FS, symlink if cross-FS) would have been a less intrusive option for this. Unfortunately there is no linkoption "c" for copy-if-cross-FS (and I rather modify the Makefile locally than to spend time to implement such an option for just this one case). Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgpx1v7JsLjAs.pgp Description: Digitale PGP-Signatur
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. 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"
commits between r305191 - r305211 broke zfs list
Hi. Can anybody test of output for: zfs list command on FreeBSD current after r305211 ? On my hosts his leads to zfs segfault. ___ 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 13:38:14 -0700 Adrian Chadd schrieb: > 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: commits between r305191 - r305211 broke zfs list
Hi. On 03.09.2016 23:50, Subbsd wrote: > Can anybody test of output for: > > zfs list > > command on FreeBSD current after r305211 ? On my hosts his leads to > zfs segfault. Works normally for me at r305342. Any more information? -- Alexander Motin ___ 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: commits between r305191 - r305211 broke zfs list
Out of sync kernel / world? Do you have a crash dump? On 03/09/2016 21:50, Subbsd wrote: Hi. Can anybody test of output for: zfs list command on FreeBSD current after r305211 ? On my hosts his leads to zfs segfault. ___ 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" ___ 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"
