Re: http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)?

[Mark Millard]

On 2016-Nov-7, at 1:16 PM, Brad Davis  wrote:

> On Mon, Nov 07, 2016 at 12:19:24PM -0800, Mark Millard wrote:
>> It looks like http://pkg.freebsd.org is still back as of head being 
>> 11-CURRENT: http://pkg.freebsd.org shows only
> 
> Correct.  I wrote up some details on how to use the 11 packages here:
> 
> http://www.raspbsd.org/raspberrypi.html
> 
> 
> Regards,
> Brad Davis

Thanks. That helped me get to the next issue to figure out.

I eventually found that https://wiki.freebsd.org/arm64/rpi3 has a "Package 
Repo" section with the alternate ABI information for pkg and also how to get 
port builds going (putting an ld in place) --as if the material was RPI3 
specific. https://wiki.freebsd.org/arm64/rpi3 says:

> There is no package repo for 12-CURRENT, but the package repo for 11 can be 
> used on 12-CURRENT by telling pkg to use the FreeBSD 11 aarch64 ABI: 
> 
> env ABI=FreeBSD:11:aarch64 pkg bootstrap
> 
> Once pkg is bootstrapped, you can add this to /usr/local/etc/pkg.conf: 
> 
> ABI = "FreeBSD:11:aarch64";
> 
> If you want to build your own ports or packages, you'll need to install the 
> aarch64-binutils package and link /usr/bin/ld to 
> /usr/local/bin/aarch64-freebsd-ld: 
> 
> # pkg install aarch64-binutils
> # ln /usr/local/bin/aarch64-freebsd-ld /usr/bin/ld
> 
> Note that if you're building directly on the RPI3, you will definitely want 
> to use either USB storage or NFS. Building on the sdcard will likely wear the 
> sdcard out. 

(I have the root filesystem on a USB SSD.)

My context is a Pine64+ 2GB --which https://wiki.freebsd.org/arm64 does not 
even mention as covered by TARGET_ARCH=aarch64 . But crochet is set up for 
pine64's and uses TARGET_ARCH=aarch64 style builds.


===
Mark Millard
markmi at dsl-only.net

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Uppercase RE matching problems in FreeBSD 11

[Mark Martinec]

2016-11-06 22:49, Stefan Bethke wrote:

So what do I set my LANG and LC variables to?  I do want UTF-8, but I
do also want my scripts to continue to work.  Clearly, en_US.UTF-8 is
not what I want.  Is it C.UTF-8?




Or do I set LANG=en_US.UTF-8 and LC_COLLATE=C?


Yes, that is the safest bet. The LANG sets a default, but the
LC_COLLATE, LC_TIME, LC_NUMERIC and LC_MONETARY should better
be set to "C" to overrule the LANG in their domains.

Leave the LC_ALL undefined or empty, as this one overrules
every other locale setting (unless you really want everything
to be set to "C").

  Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)?

[Brad Davis]

On Mon, Nov 07, 2016 at 12:19:24PM -0800, Mark Millard wrote:
> It looks like http://pkg.freebsd.org is still back as of head being 
> 11-CURRENT: http://pkg.freebsd.org shows only

Correct.  I wrote up some details on how to use the 11 packages here:

http://www.raspbsd.org/raspberrypi.html


Regards,
Brad Davis

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Uppercase RE matching problems in FreeBSD 11

[Charles Swiger]

On Nov 6, 2016, at 1:49 PM, Stefan Bethke  wrote:
> Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin :
>> That works for POSIX locale aka C aka ASCII only world
> 
> So what do I set my LANG and LC variables to?  I do want UTF-8, but I do also 
> want my scripts to continue to work.  Clearly, en_US.UTF-8 is not what I 
> want.  Is it C.UTF-8?  Or do I set LANG=en_US.UTF-8 and LC_COLLATE=C?

If you want to use a UTF8 locale, then you must start using character classes 
like '[:upper:]' and '[:lower:]' because those will-- or at least "should", 
modulo bugs-- properly handle the collation issues including for languages 
which do not possess a 1-1 mapping between upper and lower case letters.

Someone with a German email address is presumably familiar with ß / Eszett...?  
:-)

Regards,
-- 
-Chuck

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)?

[Mark Millard]

It looks like http://pkg.freebsd.org is still back as of head being 11-CURRENT: 
http://pkg.freebsd.org shows only

• freebsd:11:aarch64:64

(as http://pkg.freebsd.org/freebsd%3A11%3Aaarch64%3A64 ).

So on 12-CURRENT pkg bootstrapping gets:

> # pkg
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:aarch64/latest, 
> please wait...
> pkg: Error fetching 
> http://pkg.FreeBSD.org/FreeBSD:12:aarch64/latest/Latest/pkg.txz: Not Found
> A pre-built version of pkg could not be found for your system.
> Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'.

but ld is also missing at this stage so one cannot link anything --and pkg is 
not a route to make an ld available.

So how does one currently bootstrap a 12-CURRENT pkg for aarch64 (context: 
pine64+ 2GB)?

Create a /usr/local/etc/pkg/repos/FreeBSD.conf to reference FreeBSD:11:aarch64 
? That just reports the wrong architecture is being attempted:

> # pkg
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:11:aarch64/latest, 
> please wait...
> Verifying signature with trusted certificate pkg.freebsd.org.2013102301... 
> done
> pkg-static: Warning: Major OS version upgrade detected.  Running "pkg-static 
> install -f pkg" recommended
> Installing pkg-1.9.2...
> pkg-static: wrong architecture: FreeBSD:11:aarch64 instead of 
> FreeBSD:12:aarch64
> 
> Failed to install the following 1 package(s): /tmp//pkg.txz.zkdHp2


pkg-static install -f pkg fetches meta.txz and packagesite.txz first but then 
also reports "wrong architecture":

> # pkg-static install -f pkg
> pkg-static: Warning: Major OS version upgrade detected.  Running "pkg-static 
> install -f pkg" recommended
> Updating FreeBSD repository catalogue...
> Fetching meta.txz: 100%944 B   0.9kB/s00:01
> Fetching packagesite.txz: 100%4 MiB   4.3MB/s00:01
> Processing entries:   0%
> pkg-static: wrong architecture: freebsd:11:aarch64:64 instead of 
> FreeBSD:12:aarch64
> pkg-static: repository FreeBSD contains packages with wrong ABI: 
> freebsd:11:aarch64:64
> Processing entries: 100%
> Unable to update repository FreeBSD
> All repositories are up-to-date.
> pkg-static: Repository FreeBSD cannot be opened. 'pkg update' required
> pkg-static: No packages available to install matching 'pkg' have been found 
> in the repositories




Context details (was cross built from amd64 head -r308247):

> # uname -apKU
> FreeBSD pine64 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r308247M: Thu Nov  3 
> 07:10:44 PDT 2016 
> markmi@FreeBSDx64:/usr/local/src/crochet/work/obj/arm64.aarch64/usr/src/sys/GENERIC-NODBG
>   arm64 aarch64 1200014 1200014


> # svnlite info /usr/ports | grep "Re[lv]"
> Relative URL: ^/head
> Revision: 424540
> Last Changed Rev: 424540



===
Mark Millard
markmi at dsl-only.net

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

[Harry Schmalzbauer]

Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 09:12 (localtime):
> Hi,
> 
>> Am 07.11.2016 um 09:04 schrieb Harry Schmalzbauer :
>>> create the EFI boot volume like this?
>>>
>>> gpart add -t efi -l efi -a 512k -s 512k 
>>> newfs_msdos /dev/gpt/efi
>>> mount_msdosfs /dev/gpt/efi /mnt
>>> mkdir -p /mnt/efi/boot
>>> cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi
>>
>> You are missing startup.nsh...
>> See
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282
> 
> Care to elaborate? This is what we use in production - all
> systems booting just fine ;-)

Of course you can boot UEFI systems without startup.nsh, but it does
offers another way processing the boot sequence – the most sensible in
my opinion.
And it's what FreeBSD Releng-Team decided to provide out of the box, so
heplful hint's shouldn't do it any other.

-Harry

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ath0 associated, wlan0 not associated

[Lars Engels]

On Sat, Nov 05, 2016 at 01:00:56PM -0400, George Mitchell wrote:
> On 11/05/16 01:05, Adrian Chadd wrote:
> > nope, sorry.  There's a lot of work in the -11 wifi stack and drivers.
> > 
> > 
> > -a
> > 
> > [...]
> 
> Okay, I downloaded and installed 11.0-RELEASE on a spare slice, and
> dmesg tells me the following (with regard to ath0):
> 
> 
> ath0:  mem 0xf0a0-0xf0a7 irq 36 at
> device 0.0 on pci2
> ath0: WB335 2-ANT card detected
> ath0: Bluetooth Antenna Diversity card detected
> ath0: [HT] enabling HT modes
> ath0: [HT] enabling short-GI in 20MHz mode
> ath0: [HT] 1 stream STBC receive enabled
> ath0: [HT] 1 RX streams; 1 TX streams
> ath0: QCA9565 mac 704.1 RF5110 phy 2523.1
> ath0: 2GHz radio: 0x; 5GHz radio: 0x
> 
> But ifconfig tells me there is no "ath0" interface ... Does 11.0
> handle wifi in some unfamiliar manner?  -stable-unsubscr...@freebsd.org"

"sysctl net.wlan.devices" should show ath0


pgpx2bZIyeWe1.pgp
Description: PGP signature

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

[Harry Schmalzbauer]

 Bezüglich Harry Schmalzbauer's Nachricht vom 07.11.2016 09:04 (localtime):
> Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 08:10 (localtime):
>> Hi, all,
>>
>>> Am 06.11.2016 um 18:14 schrieb Dimitry Andric :
>>>
>>> Please do, so it is not forgotten.  It is relatively easy to change the
>>> volume label, by editing sys/boot/efi/boot1/generate-fat.sh, and then
>>> regenerating the FAT templates.
>> Why use the pre-generated image at all when you can easily
> It's what bsdinstall seems to do, which left the system unbootable, not
> what I do.
>
>
>> create the EFI boot volume like this?
>>
>> gpart add -t efi -l efi -a 512k -s 512k 

And you possibly run into other firmware problems by again using EFI as
label.
I don't know the standards, but it's obvious that at least one
unexpected label/path interference causes problems, so it's better not
to provoke another one which possibly affects only very few
implementations, but causes needless trouble.
Better use something like 'gpart add -t efi -l A-uefiLOADER  -a 512k -s
512k ' (resulting in /dev/gpt/A-uefiLOADER to be used insteaad
of /dev/gpt/efi for the following commands)

I personally prefer the "A-" prefix is to describe that it's the 1st
mirror component… Change it to whatever you like.

>> newfs_msdos /dev/gpt/efi
>> mount_msdosfs /dev/gpt/efi /mnt
>> mkdir -p /mnt/efi/boot
>> cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi

-Harry

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

[Patrick M. Hausen]

Hi,

> Am 07.11.2016 um 09:04 schrieb Harry Schmalzbauer :
>> create the EFI boot volume like this?
>> 
>> gpart add -t efi -l efi -a 512k -s 512k 
>> newfs_msdos /dev/gpt/efi
>> mount_msdosfs /dev/gpt/efi /mnt
>> mkdir -p /mnt/efi/boot
>> cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi
> 
> You are missing startup.nsh...
> See
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282

Care to elaborate? This is what we use in production - all
systems booting just fine ;-)

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

[Harry Schmalzbauer]

Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 08:10 (localtime):
> Hi, all,
> 
>> Am 06.11.2016 um 18:14 schrieb Dimitry Andric :
>>
>> Please do, so it is not forgotten.  It is relatively easy to change the
>> volume label, by editing sys/boot/efi/boot1/generate-fat.sh, and then
>> regenerating the FAT templates.
> 
> Why use the pre-generated image at all when you can easily

It's what bsdinstall seems to do, which left the system unbootable, not
what I do.


> create the EFI boot volume like this?
> 
> gpart add -t efi -l efi -a 512k -s 512k 
> newfs_msdos /dev/gpt/efi
> mount_msdosfs /dev/gpt/efi /mnt
> mkdir -p /mnt/efi/boot
> cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi

You are missing startup.nsh...
See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214282

-Harry
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"