Re: PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

On Thu, Oct 27, 2016 at 4:33 PM, Tomasz CEDRO <to...@cedro.info> wrote: > After make install from ports-mgmt/pkg update and install works fine. > Clearly problem with bootstrap only. Sorry! INSTALL DOES NOT WORK TOO. "Connection reset by peer". Server problem then..? --

Re: PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

Ugh, I am in a new place, some filtering on the wire it looks, no problem after VPN to a different location. FALSE ALERT SORRY! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list

Re: PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

After make install from ports-mgmt/pkg update and install works fine. Clearly problem with bootstrap only. Is this a bug or feature? :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list

PKG bootstrap problem on FreeBSD 11.0-RELEASE-p1

Hey, I have just installed 11.0-RELEASE-p1 r306420 and I cannot bootstrap the PKG :-( Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly, please wait... Error fetching. Both IP and DNS are working.. -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: PKG bootstrap FreeBSD 11.0 / VBox NAT problem

Just for the curious. I am testing on VirtualBox (Version 5.1.8 r111374 (Qt5.5.1), macOS 10.12.1 host). Cannot bootstrap PKG on a host with NAT enabled.I have noticed this problem occurs only when NAT is enabled in VBox. When I use Bridged interface there is no problem. I have noticed that

UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

Hello! I have noticed that I cannot use Xorg anymore on UEFI box with 11.0-RELEASE. I get (EE) no screens found, before Xorg terminates. X Server 1.17.4 (RELEASE 2015-10-28). This happens on my new HYPERBOOK SL502VR (P650RP6-G) with nVidia GTX1060 and INTEL and VESA does not finding any screen.

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

On Wed, Jan 4, 2017 at 5:08 PM, Tomasz CEDRO <to...@cedro.info> wrote: > Some clue: DO NOT USE VESA DRIVER! USE SCFB ON UEFI HARDWARE :-) Although SCFB driver did some switch I have black screen both on laptop and virtualbox.. -- CeDeROM, SQ7MHZ, http://www.tomek.c

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

On Wed, Jan 4, 2017 at 3:47 PM, Tomasz CEDRO <to...@cedro.info> wrote: > I have noticed that I cannot use Xorg anymore on UEFI box with 11.0-RELEASE. > I get (EE) no screens found, before Xorg terminates. > X Server 1.17.4 (RELEASE 2015-10-28). Some clue: DO NOT USE VESA DRIVER! U

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

On Wed, Jan 4, 2017 at 5:25 PM, Tomasz CEDRO <to...@cedro.info> wrote: > Although SCFB driver did some switch I have black screen both on > laptop and virtualbox.. It was some stuff loading really long in the background. After recreating the setup it works! You can use `Xor

Re: UEFI Xorg (EE) no screens found on FreeBSD 11.0-RELEASE

On Wed, Jan 4, 2017 at 5:54 PM, Tomasz CEDRO <to...@cedro.info> wrote: > USE SCFB ON UEFI HARDWARE INSTEAD VESA AS FALLBACK! :-) this also only works as root.. :\ -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.or

if_iwm crashes kernel when loaded from /boot/loader.conf

Hello, I noticed a problem when loading if_iwm from /boot/loader.conf kernel crashes as it cannot load module firmware dead loop occurs. Adding iwm8000Cfw before if_iwm does not help. Loading if_iwm on a running system works fine and gives operational wifi. Intel Corporation Wireless 8260

Re: crashes after upgrade to 11.1-RELEASE AMD64 / libgcc5

Here too! I did a fresh install on a second partition the same machine, no problem observed.. for some reason freebsd-upgrade -r fails to create a stable system or there is some sort of base/pkg mismatch after... -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Sep 13, 2017 15:58, "Mr. Binary"

Re: automount usb msdosfs no partition table

i cannot format that device, as its the "firmware feature" that it has no partition table.. i would have to fix the firmware.. but it would be nice to automount it anyway as macos, linux and windoze can :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: automount usb msdosfs no partition table

On Mon, Oct 9, 2017 at 8:59 PM, Scott Bennett <benn...@sdf.org> wrote: > Tomasz CEDRO <to...@cedro.info> wrote: >> i cannot format that device, as its the "firmware feature" that it has no >> partition table.. i would have to fix the firmware.. but it wo

automount usb msdosfs no partition table

Hello world :-) I need to configure automount for a testing machine. It seems to work fine, except for two issues: 1. Mount point does not disappear after device disappears, what makes things harder to script when device is gone. automount -c does not remove the mountpoint, only restarting the

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

Why so short End-Of-Life? Why so many fast and short releases? What for? Why pushing problems to production? What was wrong with having one well tested stable system for a long time? 12.0 was a problematic release. 12.1 brings even more problems. To be honest X11 Video Acceleration DRM mess and

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

wt., 18 lut 2020, 10:20 użytkownik Steve O'Hara-Smith napisał: > On Tue, 18 Feb 2020 04:23:35 +0100 > Tomasz CEDRO wrote: > > > Why so short End-Of-Life? Why so many fast and short releases? What for? > > The new(ish) release and support policy has been announced

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

On Wed, Feb 19, 2020 at 8:24 PM Bengt Ahlgren wrote: > Tomasz CEDRO writes: > > Another problem is the VirtualBox virtualization that is not really > > usable anymore. I am aware of closed-source VBox Guest Additions > > problem. My VM works fine for a first minute or

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

Hello Ed, thanks for your input :-) On Tue, Feb 18, 2020 at 3:46 PM Ed Maste wrote: > > 12.0 was a problematic release. 12.1 brings even more problems. > > The major issue with 12.1 is a problem with the Intel graphics kernel > module, and fixing that was held up by both 12.0 and 12.1 being >

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

On Tue, Feb 18, 2020 at 3:51 PM Ed Maste wrote: > > On Tue, 18 Feb 2020 at 05:37, Tomasz CEDRO wrote: > > > > Maybe its a time to give OpenBSD a try.. > > I really don't understand this comment, either. Certainly give OpenBSD > a try and if it fits your needs bett

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

On Sun, Apr 5, 2020 at 7:53 PM Ruslan Garipov wrote: > > I wrongly assumed that release will simply update this svn repo that I > > am working on.. but it fetches HEAD.. so I was trying to build > > 13/HEAD/CURRENT on 12/STABLE/RELEASE that have different ABI thus bad > > syscall.. and I need

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

Summing up the time cost for a clean svn co and make buildkernel buildworld release is around 75minutes while the chroot build with release(7) is around 100minutes for my hardware setup. Builds using make are more reasonable for driver fixes because then I can only rebuild small part of the code

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

On Wed, Apr 8, 2020 at 8:19 PM Ruslan Garipov wrote: > > I need to see how it works with `make release` :-) > This is what I meant when saying "you can build the source tree for > 13.0-CURRENT on 12.1-RELEASE"; sorry if I've confused you. No worries, my little confusion came from `make release`

/usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

Hello world :-) I would like to build a 12-STABLE (/usr/src contains svn.freebsd.org/base/stable/12) locally on strong machine (24CPU 127GB RAM 12-1-RELEASE AMD64), then test changes on my local machine (panasonic toughbook i5 laptop 12.1-RELEASE AMD64). This will be used for testing kernel

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

Hello Ruslav and thank you for your feedback! :-) On Sun, Apr 5, 2020 at 3:07 PM Ruslan Garipov wrote: > On 4/4/2020 7:50 PM, Tomasz CEDRO wrote: > > 1. Is it a good build / testing environment? Maybe there is a simpler > > / better way to cross compile binaries and test on

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

On Sun, Apr 5, 2020 at 4:59 PM Ruslan Garipov wrote: > I'm sorry, I forgot to ask how do you call /usr/src/release/release.sh? > Do you pass a configuration file to this script? > > By default /usr/src/release/release.sh checks out the source tree for > the CURRENT branch

Re: URGENT: Microsoft overwrites boot loader!

czw., 16 lip 2020, 22:20 użytkownik Don Wilde napisał: > That's the last time I will allow this, and I'm calling those [deleted]s > tomorrow to give them a piece of my mind. After that I will erase every > vestige of that obscene OS from my disk. > I did that long time ago :-) I have one

Re: 12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so

Hello PARV :-) On 27.01.2021 12:52, parv/freebsd wrote: > What is the git commit hash (for others)? For the 12.2-RELEASE: # git branch main * releng/12.2 stable/12 # git log --pretty=oneline | head 97eb1441ca7b602510a81fd512d830563998b3e7 PS/2 Synaptics touchpad identification fix.

Re: 12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so

On 27.01.2021 19:31, parv/freebsd wrote: # git log --pretty=fuller --grep libuutil release/12.2.0. .stable/12 commit 30ec3f368d Author:     Eugene Grosbein AuthorDate: Dec.2020.1206-1622 + Commit:     Eugene Grosbein CommitDate: Dec.2020.1206-1622 +     MFC r364027

12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so

Hello world! I cannot buildworld for 12.2-RELEASE. Using /usr/src as svn or git no matter (its set to releng/12.2). Did clean /usr/obj. Any hints welcome :-) # uname -a FreeBSD hexagon 12.2-RELEASE-p1 FreeBSD 12.2-RELEASE-p1 GENERIC amd64 # /usr/bin/time -h make buildkernel buildworld

Re: Dell XPS 8940 SATA and NVMe disk controller not recognized

On Sun, Apr 4, 2021, 00:10 Karl Dunn wrote: > That worked, precisely as it did for you: gpart list shows partitions > and drives much to my expectations, and Win10 no longer boots. I can > boot windows by setting the BIOS config back to RAID. That's not much > of a pain. Now to try installing

Re: Dell XPS 8940 SATA and NVMe disk controller not recognized

Hello :-) You may take a look at http://bsd-hardware.info/ report your hardware issues and see if other people have it working :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list