Rising amounts of crap on this mailing list

[Marcel Bischoff]

Dear mailing list admins,

I’m receiving an increasing amount of crap (mainly Spam and unrequested 
Bugzilla updates and now: support ticket auto-responses?) via this mailing 
list. It has risen to amounts that they disrupt my workflow and I may have to 
unsubscribe. I’d appreciate it if there was some official communication 
regarding do’s and don’t on this list. It will not deter spammers but may keep 
real people thinking about the impact of their decisions – before they do them. 
Although that’s probably also pointless, given the presence of Chinese language 
support ticket auto-responses.

Anyway, in this case, there should be options for the moderators to block 
certain servers, addresses and users.

Looking forward to hearing from you.

Best,
Marcel

> On 4. Jun 2018, at 03:34, CustomerSupport  wrote:
> 
> 
> ___
> 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"

___
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: Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)

[Tobias C. Berner]

Hi there

Qt4 has nothing to do with this. The issue is caused by upgrading Qt5 from
5.9.4 to 5.10.1 without also rebuilding the Qt5 using
applications/libraries :)


mfg Tobias

On 31 May 2018 at 16:37, tech-lists  wrote:

> Hello lists,
>
> context: 11.2-PRERELEASE #0 r333458 / ports r471194
>
> with xpdf I get the following error:
>
> Cannot mix incompatible Qt library (version 0x50904) with this library
> (version 0x50a01),Abort (core dumped)
>
> I seem to have both qt4-4.8.7 and qt5-5.10.1 installed. I didn't install
> these directly though, seems they've been installed as dependencies of
> other ports. I'm using MATE desktop.
>
> I've tried reinstalling xfdf via pkg and the port with the same result. Is
> this a known problem/how can I fix? Have found no fix yet from GIS, most
> seem to point to deleting and reinstalling everything.
>
> thanks,
> --
> J.
> ___
> freebsd-po...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
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: Rising amounts of crap on this mailing list

[Jamie Landeg-Jones]

> Anyway, in this case, there should be options for the moderators to block 
> certain servers, addresses and users.

Whilst I agree, the thing that makes my use of these lists less effective is
the indiscriminate top posting and even worse, the total lack of reply-trimming.

Cheers, Jamie
___
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: Handheld Inkjet Printer with 3.5 Inch Touch Screen

[kelly]

Dear Manager,


Good day!


We independently developed a handheld inkjet printer with good quality, which 
is widely used and popular throughout different countries. Hope the below 
product can help you save the costs.


Following is one of our model:
Item: Handheld Inkjet Printer with Solvent Ink (Quick Dry)


- With 3.5 inch touchable screen that you can edit the contents directly via 
screen or imported the contents from U-disk.
- Upgraded and more function than the product in market.
- It can print on different kinds of materials, such as papers, cartons, 
plastics, glasses, woods, stones, walls, steels pipes, metals, cables, film 
materials, etc.
- It can print Chinese, English letters, numbers, QR code, scan code, barcode, 
batch code, expiry date, time, counter, symbols, logo, marks, small pictures 
etc.
-We have large data store up to 200 messages.
- portable and convenient to use.
- Quick dry, environmental ink and do not easy to erase by water.


Any interests please contact us for more information.We can show you our 
brochure and video. We can provide you sample,too!


Thanks and Regards,
--

Kelly Chen
Sales Representative
Shenzhen Swaroniki Technology Co., Ltd. 
Mobile & Whatsapp:86-13266685669
Skype: kelly_3167
Web:www.beshengprinters.com
___
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: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

[Martin.Ambroz]

> Hi,
>
> Could folks please help boot-test the most recent 12.0-CURRENT amd64 memstick 
> images on various hardware?  Note, this is not a request to install 12.0-
> CURRENT, only a boot-test with various system knobs tweaked.
>
> The most recent images are available at:
> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img
> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img
>
> We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we would 
> like to get this included in the upcoming 11.2-RELEASE if the change that > 
> had been committed addresses several boot issues reported recently.
>
> Please help test, and report back (both successes and failures).
>
> Thanks,
>
> Glen

Went well on Lenovo Thinkpad X250, Fujitsu Celsius W530 and Lenovo ThinkCentre 
M710s.

Martin

___
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"

FreeBSD 11.2-RC1 announce link is broken

[Yuval Pavel Zholkover]

Hello,

The announce link at
https://www.freebsd.org/news/newsflash.html#event20180602:01 is pointing at
the wrong url:
https://lists.freebsd.org/pipermail/freebsd-stable/2018-May/089053.html
instead of
https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089053.html
(May vs. June).

Thanks!
___
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: FreeBSD 11.2-RC1 announce link is broken

[Glen Barber]

On Mon, Jun 04, 2018 at 09:28:37PM +0300, Yuval Pavel Zholkover wrote:
> Hello,
> 
> The announce link at
> https://www.freebsd.org/news/newsflash.html#event20180602:01 is pointing at
> the wrong url:
> https://lists.freebsd.org/pipermail/freebsd-stable/2018-May/089053.html
> instead of
> https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089053.html
> (May vs. June).
> 
> Thanks!

Fixed.  It will be effective the next website build (usually about 10
minutes).

Thank you for the report.

Glen



signature.asc
Description: PGP signature

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

[Ian FREISLICH]

On 05/30/2018 11:50 AM, Glen Barber wrote:

Hi,

Could folks please help boot-test the most recent 12.0-CURRENT amd64
memstick images on various hardware?  Note, this is not a request to
install 12.0-CURRENT, only a boot-test with various system knobs
tweaked.

The most recent images are available at:
https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img
https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img

We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we
would like to get this included in the upcoming 11.2-RELEASE if the
change that had been committed addresses several boot issues reported
recently.

Please help test, and report back (both successes and failures).


Coincidentally, I was trying to install these on a very old 10" Dell 
Lattitude with an Atom N550 CPU.  Both images booted to the beastie menu 
but hung loading the kernel.  The only way I could get it to boot was to 
manually load the kernel at the loader prompt and boot. I was also 
unsuccessful performing a network install due to what I think was the 
download filesystem being read only.  I was able to install from the 
bundled distribution.


Ian

--

___
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: Fwd: 11.2-Beta3 fails to boot: legacy mode ZFS

[Allan Jude]

When you say it "failed at ZFS", what do you mean?

There will be multiple 'boot prompts' as well.

The system starts up, and boot1/boot2 happen. This is where you'll get 
the first GELI password prompt.


This will start the loader, which draws the beastie menu. After the 
menu, the kernel modules indicated in /boot/loader.conf are loaded, then 
the text 'booting' is displayed, and the screen is cleared, and the 
kernel starts loading.


Later on you get the mount-root prompt if something goes wrong.

Query: Do you happen to have VirtualBox or the nVidia driver kernel 
modules loaded? This was causing problems for some other people, where 
the system would boot up, but instantly panic once the VirtualBox 
networking driver was loaded, since the vbox driver module needs to be 
compiled against the 11.2 source code to work with an 11.2 kernel.


If this doesn't seem to be the problem:
Can you send the contents of /boot/loader.conf, /etc/rc.conf, 'zpool 
list' and 'zfs list'


On 2018-06-03 11:28 PM, Warner Losh wrote:

I think this is on your side of the wall...

Warner

-- Forwarded message -
From: David Samms mailto:dsa...@nw-ds.com>>
Date: Sun, Jun 3, 2018, 7:08 PM
Subject: 11.2-Beta3 fails to boot: legacy mode ZFS
To: mailto:freebsd-stable@freebsd.org>>


Hello,

Background:
-
System was originally installed with an 11.0 CD. At the time I tried to
get UEFI to work, but ended up booting in legacy/BIOS mode. Upgrading to
11.1 was uneventful. The system has a single SSD with full disk
encryption and ZFS. Again, nothing special, just the user selectable
install options from the 11.0 CD.

Current Failure:
--
After running "freebsd-update upgrade -r 11.2-BETA3" the system failed
on reboot. Disk encryption keys can be entered, boot prompt appears,
boot starts but fails at ZFS. Reboots with no info sent to the console.

Luckily, selecting kernel.old at the boot prompt works fine.

Any ideas? Need more info? What can I do to help track down the bug?

Thank you

--
David Samms
___
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 
"



--
Allan Jude
___
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: Fwd: 11.2-Beta3 fails to boot: legacy mode ZFS

[David Samms]

All,

My first response appears not to have made the list, so am reposting. 
The problem is SOLVED however. The system in question is an Intel 
s1200kb with Xeon processor but no COM port, only USB so console access 
is not available. Make debugging more difficult.


On 06/04/18 13:59, Allan Jude wrote:

When you say it "failed at ZFS", what do you mean?


Sorry for the poor description. I get all the normal boot prompts and 
the system starts to boot then suddenly without any error message or 
output to the console, reboots. The last text I can see is...


ZFS...

This occurs very early in the boot cycle and way before mounting / or 
going into single user mode



There will be multiple 'boot prompts' as well.

The system starts up, and boot1/boot2 happen. This is where you'll get 
the first GELI password prompt.


This will start the loader, which draws the beastie menu. After the 
menu, the kernel modules indicated in /boot/loader.conf are loaded, then 
the text 'booting' is displayed, and the screen is cleared, and the 
kernel starts loading.


Reboots HERE. Before mount-root prompt.


Later on you get the mount-root prompt if something goes wrong.

Query: Do you happen to have VirtualBox or the nVidia driver kernel 
modules loaded? This was causing problems for some other people, where 
the system would boot up, but instantly panic once the VirtualBox 
networking driver was loaded, since the vbox driver module needs to be 
compiled against the 11.2 source code to work with an 11.2 kernel.


If this doesn't seem to be the problem:
Can you send the contents of /boot/loader.conf, /etc/rc.conf, 'zpool 
list' and 'zfs list'


Allan, thank you so much for this suggestion. Commenting out all ports 
based kernel modules resolved the problem. In the past upgrades I have 
had ports based kernel modules fail to load or crash when used, but I 
have never seen the loading of a ports based kernel modules crash the 
boot process.


Would suggest "we" make it clear in the upgrade instructions to disable 
ALL optional kernel modules. I expect Nvidia to fail and require a 
recompile before working with a new version of FreeBSD, but in the past 
I have always been able to boot to single user mode.


Thank you guys for terrific support!


On 2018-06-03 11:28 PM, Warner Losh wrote:

I think this is on your side of the wall...

Warner

-- Forwarded message -
From: David Samms mailto:dsa...@nw-ds.com>>
Date: Sun, Jun 3, 2018, 7:08 PM
Subject: 11.2-Beta3 fails to boot: legacy mode ZFS
To: mailto:freebsd-stable@freebsd.org>>


Hello,

Background:
-
System was originally installed with an 11.0 CD. At the time I tried to
get UEFI to work, but ended up booting in legacy/BIOS mode. Upgrading to
11.1 was uneventful. The system has a single SSD with full disk
encryption and ZFS. Again, nothing special, just the user selectable
install options from the 11.0 CD.

Current Failure:
--
After running "freebsd-update upgrade -r 11.2-BETA3" the system failed
on reboot. Disk encryption keys can be entered, boot prompt appears,
boot starts but fails at ZFS. Reboots with no info sent to the console.

Luckily, selecting kernel.old at the boot prompt works fine.

Any ideas? Need more info? What can I do to help track down the bug?

Thank you

--
David Samms
___
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 
"






--
David Samms
___
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"