Re: btxld not found

2021-02-19 Thread Marek Zarychta 
W dniu 29.01.2020 o 16:35, Nick Hibma pisze:
>>
 Could anyone explain to me what I am doing wrong? make installworld fails 
 each time with the following error

 ===> stand/i386/libi386 (install)
 ===> stand/i386/loader_4th (install)
 strip -R .comment -R .note -o loader_4th.bin loader_4th.sym
 btxld -v -f aout -e 0x20 -o loader_4th -l 
 /usr/obj/usr/src/i386.i386/stand/i386/btx/btxldr/btxldr  -b 
 /usr/obj/usr/src/i386.i386/stand/i386/btx/btx/btx loader_4th.bin
 make[6]: exec(btxld) failed (No such file or directory)
 *** Error code 1

 This is with source of last week. I had this problem before (from old 
 sources) and fixed it by specifying the full path to btxld in the 
 stand/i386/*/Makefile.
>>>
>>> Yes, this is most likely your clock(s) being off.  At installworld time,
>>> it should *not* start rebuilding your loader.
>>>
>>> Usually this happens if you build on one machine, and install on
>>> another, while the install machine's time is behind the build machine's
>>> time.  But it can also happens on one machine, for instance if you
>>> start in single user mode, and the clock is not yet synchronized.
>>>
>>> -Dimitry
>>>
>> Dimitry, 
>>
>> My VirtualBox VMs do have a tendency to lag when I am not using them for a 
>> while. I've adjusted time and started ntpd. In the past that would not fix 
>> the time lag permanently.
>>
>> I'll do a fresh buildworld and see whether that completes.
>>
>> Nick
> 
> Nope, make buildworld && make installworld results in, so I guess the job 
> ordering suggestion is a better one (VM with 2 processors on a variably 
> loaded laptop, no -j option, time accurate):
> 
> install   -o root -g wheel -m 444   mbr /boot/mbr
> ===> stand/i386/pmbr (install)
> install   -o root -g wheel -m 444   pmbr /boot/pmbr
> ===> stand/i386/boot0 (install)
> install   -o root -g wheel -m 444   boot0 /boot/boot0
> ===> stand/i386/boot0sio (install)
> install   -o root -g wheel -m 444   boot0 /boot/boot0sio
> ===> stand/i386/btx (install)
> ===> stand/i386/btx/btx (install)
> ===> stand/i386/btx/btxldr (install)
> ===> stand/i386/btx/lib (install)
> ===> stand/i386/boot2 (install)
> objcopy -S -O binary boot1.out boot1
> objcopy -S -O binary boot2.out boot2.bin
> btxld -v -E 0x2000 -f bin -b 
> /usr/obj/usr/src/i386.i386/stand/i386/btx/btx/btx -l boot2.ldr  -o boot2.ld 
> -P 1 boot2.bin
> make[6]: exec(btxld) failed (No such file or directory)
> *** Error code 1
> 
> ...
> 
> {e}nick@fimkjecurrent:/usr/src % sudo find / -name btxld -type f -ls
> 1908308   48 -r-xr-xr-x1 root wheel   
> 22988 Jan 27 23:37 /usr/sbin/btxld
> 3441268   52 -rwxr-xr-x1 root wheel   
> 25816 Jan 29 16:09 
> /usr/obj/usr/src/i386.i386/usr.sbin/btxld/btxld
> {e}nick@fimkjecurrent:/usr/src % date
> Wed Jan 29 16:30:21 CET 2020
> {e}nick@fimkjecurrent:/usr/src % make -dA
> ...
> Global:MFLAGS =   -d A
> job_pipe -1 -1, maxjobs 1, tokens 1, compat 1
> ...


I am still running into this occasionally on amd64 with 13.0-STABLE,
especially while updating from src and obj directories exported over
NFS, but it happens sometimes also for locally mounted src and obj.


===> stand/i386/mbr (install)
install   -o root -g wheel -m 444   mbr /boot/mbr
===> stand/i386/pmbr (install)
install   -o root -g wheel -m 444   pmbr /boot/pmbr
===> stand/i386/boot0 (install)
install   -o root -g wheel -m 444   boot0 /boot/boot0
===> stand/i386/boot0sio (install)
install   -o root -g wheel -m 444   boot0 /boot/boot0sio
===> stand/i386/boot2 (install)
objcopy -S -O binary boot2.out boot2.bin
objcopy: open boot2.bin failed: Read-only file system
*** Error code 1

Running make buildworld with only one job solves the issue. I am
building with WITH_META_MODE=yes, so I work around this by subsequent
builds:
make -sj32 buildworld && make -s buildworld


-- 
Marek Zarychta



OpenPGP_signature
Description: OpenPGP digital signature

Warm boot of the axge USB device fails

2021-02-19 Thread Bakul Shah 
This is on a 13.0-STABLE system but this was also a problem while 13.0 was 
-current.

If I warmboot (reboot) the system the axge USB GbE driver fails:

# dmesg|grep axge
Feb 19 15:03:00 motile kernel: axge0 on uhub1
Feb 19 15:03:00 motile kernel: axge0:  on usbus0
Feb 19 15:03:00 motile kernel: axge0: attaching PHYs failed


If coldboot the system the device connects fine:

# dmesg|grep axge
Feb 19 16:03:42 motile kernel: axge0 on uhub1
Feb 19 16:03:42 motile kernel: axge0:  on usbus0
Feb 19 16:03:42 motile kernel: miibus2:  on axge0
Feb 19 16:03:42 motile kernel: ue1:  on axge0

Interesting that the second line in each case is different. Is there a 
workaround for this?

Thanks!
___
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: webcamd not started automatically

2021-02-19 Thread Hans Petter Selasky 

On 2/18/21 5:27 PM, Jakob Alvermark wrote:

On 2/18/21 4:49 PM, Steve Wills wrote:

Hi,

On 2/18/21 9:14 AM, Jakob Alvermark wrote:
It used to start webcamd for both of them, now it is only started for 
the built in Chicony.


I have a similar problem. I have 3 cameras (one Logitech and two USB 
UVD things) and now it only starts webcamd for one. I can start it 
manually for the other two. I don't have the details now, but it 
seemed like when I started it for the second or third device, it said 
it was already running until I tried again.



Yes, there is something going on when you try to start multiple instances.

My cameras are at ugen1.7 and ugen2.4

# service webcamd start ugen1.7
webcamd 4778 - - Attached to ugen1.7[0]
# service webcamd start ugen2.4
webcamd already running?  (pid=4779).
# service webcamd stop
Stopping webcamd.
Waiting for PIDs: 4779
# service webcamd start ugen2.4
webcamd 4830 - - Attached to ugen2.4[0]
# service webcamd start ugen1.7
webcamd already running?  (pid=4831).

# ls /var/run/webcamd.*
/var/run/webcamd.1.7.0.pid    /var/run/webcamd.2.4.0.pid

# cat /var/run/webcamd.1.7.0.pid
4778

# cat /var/run/webcamd.2.4.0.pid
4830



Can you show:

ls /var/run/webcamd* for every step you do?

--HPS

___
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: freebsd-update(8) without an echo of "You must be root to run this."

2021-02-19 Thread Chris Rees 
Hey,

On 16 February 2021 08:53:29 GMT, Graham Perrin  wrote:
>
>
>         echo "You must be root to run this."
>
>Below: is this my PEBKAM, or (with a system that is preconfigured to 
>deny login as root) _should_ there be an echo of the requirement to run
>
>as root?
>
>
>
>mowa219-gjp4-vm-hellosystem-eol-freebsd% su -
>Password:
>su: Sorry
>mowa219-gjp4-vm-hellosystem-eol-freebsd% sudo grep LOCKED 
>/etc/master.passwd
>root:*LOCKED*:0:0::0:0:Charlie &:/root:/bin/csh
>mowa219-gjp4-vm-hellosystem-eol-freebsd% sudo freebsd-update upgrade -r

Sudo means that you are root.  *LOCKED* just disables the root password.

Chris
___
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: Strange anomaly when Netgear A6100 - AC600 Dual Band WiFi USB Mini Adapter plugged in on boot

2021-02-19 Thread Steven Friedrich 
On Thursday, 18 February 2021 16:35:48 EST Daniel Stevenson wrote:
> On Thursday, February 18th, 2021 at 04:40, Steven Friedrich 
 wrote:
> > Starting devd.
> > 
> > Cannot 'start' webcamd. Set webcamd_enable to YES in /etc/rc.conf or use
> > 
> > 'onestart' instead of 'start'.
> > 
> > There's nothing in /etc/rc.conf to invoke webcam. Nothing in
> > /etc/devd.conf
> > 
> > (AFAIK). I haven't modified devd.conf
> > 
> > If I unplug the adapter and reboot, no message about webcam appears.
> > 
> > Here's the device as reported by pciconf -lv
> > 
> > none6@pci0:2:0:0: class=0x028000 card=0x831a103c chip=0xc82110ec
> > 
> > rev=0x00 hdr=0x00
> > 
> > vendor = 'Realtek Semiconductor Co., Ltd.'
> > 
> > device = 'RTL8821CE 802.11ac PCIe Wireless Network Adapter'
> > 
> > class = network
> > 
> > Here's the dmesg
> > 
> > ugen0.2:  at usbus0
> > 
> > rtwn0 on uhub0
> > 
> > rtwn0: <802.11ac WLAN Adapter > on usbus0
> > 
> > rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R
> 
> Whether or not you have a line in your /etc/rc.conf that says
> webcamd_enable="NO", webcamd is disabled by default.  You have to
> override this by setting webcamd_enable="YES".
You misinterpreted my post.

I don't want webcam.

I get this errant message because I have a USB network adapter plugged in on 
boot.

I believe this is related to /usr/src/UPDATING entry 20180211:
20180211:
devmatch functionality has been turned on in devd. It will 
automatically
load drivers for unattached devices. This may cause unexpected drivers 
to
be loaded. Please report any problems to current@ and i...@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"