Broadcom BCM4310 USB Controller (Wifi)
Hello, I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the above chip is still not supported. I am wrong? Any other idea how to get Wifi working on this mini laptop? Thanks in advance matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Wednesday, October 27, 2010 a las 05:10:32PM +, Alberto Villa escribió: > On Wed, Oct 27, 2010 at 5:07 PM, Scot Hetzel wrote: > > Where did you get your bcmwl5 driver? If you downloaded it from Acer, > > it should work. If you downloaded it from anywhere else then this > > might be why it didn't work for you. > > i don't remember, actually. anyway i thought the 5 was the driver > version, i've just understood that it's the windows version :P > i'll try the acer one, thanks for the suggestion! I could no get any bcmwl5 driver from Acer, only bcmwl6 version (which is also installed in Win7 in my laptop). I have even asked Broadcom, but they pointed me back to my dealer, to the reseller of the Acer laptop. And asking them, they pointed to Acer. If someone has an bcmwl5 from Acer, please contact me off-list. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Wednesday, October 27, 2010 a las 12:12:09PM -0500, Scot Hetzel escribió: > > Where did you get your bcmwl5 driver? If you downloaded it from Acer, > > it should work. If you downloaded it from anywhere else then this > > might be why it didn't work for you. > > > > Just noticed that you didn't specify your computer manufacture. The > above would only work for Matthias Apitz. > > You just need to download the driver from the manufacture of your computer. Why is this? Isn't it just the Wifi chip which matters? Could you sheet a bit light on this? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel escribió: > On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa wrote: > > On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol wrote: > >> NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 > >> driver. Note 5 vs 6 in driver name. > >> Editing inf files will give you nothing. > > > > i've tried that driver, but apparently it doesn't support my card... > > loading the .ko doesn't show anything... > > Where did you get your bcmwl5 driver? If you downloaded it from Acer, > it should work. If you downloaded it from anywhere else then this > might be why it didn't work for you. Following Scot's hint (thanks for this) I downloaded today morning the WinXP x86 driver zip archive from www.Acer.com and built the bcmwl5_sys.ko with ndisgen(8). The system panics on early boot stages when the kmod was pulled in via loader.conf. If the system is up, you can kldload the module fine and the interface ndis0 appears and even the card gets associated with the AP (i.e. wpa_supplicant(8) must work fine). The ifconfig(8) shows the interface as: ndis0: flags=8843 metric 0 mtu 2290 ether 90:4c:e5:00:06:ce media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated and the Wifi indicator light of the laptop is green. But: # dhclient ndis0 ifconfig: ioctl (SIOCAIFADDR): Invalid argument ndis0: not found and the same is with # ifconfig ndis0 192.168.2.200 All this is with a 8-CURRENT kernel/system as of May 2009. I will now build a USB key from HEAD and will continue testing. Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Thursday, October 28, 2010 a las 12:07:10PM +, Paul B Mahol escribió: > > # dhclient ndis0 > > ifconfig: ioctl (SIOCAIFADDR): Invalid argument > > ndis0: not found > > > > and the same is with > > > > # ifconfig ndis0 192.168.2.200 > > > > All this is with a 8-CURRENT kernel/system as of May 2009. I will now build > > a > > USB key from HEAD and will continue testing. > > > > On 9/8 CURRENT you create wlanX with ifconfig(8) and operate on them. Stupid I am. Of course. I forgot this in the happyness that ndis0 came up :-( > But note that such old CURRENT have few bugs in NDISulator. > > For example scan results are incomplete and scanning can trigger panic > in some situations. > If you use wpa_supplicant -Dndis you will never encounter such problems. I've checked my old man page and the one of HEAD ... -D is not explained in the man page of wpa_supplicant(8), but in its help: # /usr/sbin/wpa_supplicant --help | fgrep -- -D wpa_supplicant: illegal option -- - -i -c [-C] [-D] [-p] \ [-N -i -c [-C] [-D] \ -D = driver name wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf Thanks for the hint matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Thursday, October 28, 2010 a las 12:07:10PM +, Paul B Mahol escribió: > > # ifconfig ndis0 192.168.2.200 > > > > All this is with a 8-CURRENT kernel/system as of May 2009. I will now build > > a > > USB key from HEAD and will continue testing. > > > > On 9/8 CURRENT you create wlanX with ifconfig(8) and operate on them. > > But note that such old CURRENT have few bugs in NDISulator. > > For example scan results are incomplete and scanning can trigger panic > in some situations. > If you use wpa_supplicant -Dndis you will never encounter such problems. I booted the 8-CURRENT this morning, loaded the module with kldload(8) and wlan0 came up by its own (I did not realized this yesterday). I have in rc.conf: wlans_ndis0="wlan0" ifconfig_wlan0="WPA DHCP" wpa_supplicant(8) started after kldload, and associated the interface with my AP; had to do the DHCP by hand, don't know why? For the moment all seems to be fine. Thanks for guiding me through this to all. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Friday, October 29, 2010 a las 07:07:18AM +, Paul B Mahol escribió: > On Fri, Oct 29, 2010 at 6:34 AM, Scot Hetzel wrote: > > On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz wrote: > >> I booted the 8-CURRENT this morning, loaded the module with kldload(8) and > >> wlan0 came up by its own (I did not realized this yesterday). I have in > >> rc.conf: > >> > >> wlans_ndis0="wlan0" > >> ifconfig_wlan0="WPA DHCP" > >> > >> wpa_supplicant(8) started after kldload, and associated the > >> interface with my AP; had to do the DHCP by hand, don't know why? > >> > > The problem is that the Broadcom NDIS driver is generating connection > > events, but nothing is relaying that information to the wpa_supplicant > > daemon. Since the wpa_supplicant daemon doesn't see a connection > > event, it retries connecting > > > > I had created a patch in PR 113915 which solves this problem: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=113915 > > > > Give it a try, if it solves your problem submit a followup to the PR. > > Hmm, ndis_events are required if you use -Dndis and wpa/rsn and need > to get event of PMKIDs. > For other uses it is of no use. The wpa_supplicant(8) which comes up after loading the NDIS kmod with kldload(8) is launched with -Dndis; I checked this this morning; will try the patch proposed by Scott; matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
having 'src' and 'obj' in some other place
Hello, I compiled a 9-CURRENT from SVN but having it in a non default place, in /home/guru/9-CURRENT/src. To compile kernel and world I set MAKEOBJDIRPREFIX to /home/guru/9-CURRENT/obj and all went fine. Then I installed kernel und world to the USB key using DESTDIR set to /mnt. Because the idea is to use the USB key for further installation a copied the 'src' and 'obj' to it as well with: # cp -Rp /home/guru/9-CURRENT/src /mnt/usr # cp -Rp /home/guru/9-CURRENT/obj /mnt/usr The USB key boots fine. From this USB key I now wanted to install the system to a partitioned hard disk, again with something like: # cd /usr/src # make installworld DESTDIR=/mnt where below /mnt now the file system of the disk was mounted. This failed with messages about 'install: ... not found' and the way around was to move /usr/src again on the USB key to a faked location of /home/guru/9-CURRENT/src, and as well 'obj'. After this all went fine. Question: Why is this so hardwired bound to the original location of 'src' and 'obj'? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
9-CURRENT: ports/net/kdenetwork3 does not compile
Hello,
$ uname -a
FreeBSD tinyCurrent 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r21: Thu Oct 28
10:56:32 CEST 2010
with /usr/ports from CVS October, 30;
compiling KDE3 gives:
...
gmake[4]: Entering directory
`/usr/ports/net/kdenetwork3/work/kdenetwork-3.5.10/ktalkd/ktalkd'
c++ -DHAVE_CONFIG_H -I. -I../.. -I../../kopete/protocols/gadu/libgadu
-I/usr/local/include -I/usr/local/include -DHAVE_KDE -D_THREAD_SAFE -pthread
-DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include
-I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE -D_LARGE_FILES=1
-Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2
-pipe -fno-strict-aliasing -Wno-non-virtual-dtor -fno-exceptions -fno-check-new
-fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION -MT find_user.o -MD -MP -MF .deps/find_user.Tpo -c -o
find_user.o find_user.cpp
find_user.cpp: In function 'int find_user(char*, char*, char*)':
find_user.cpp:344: error: aggregate 'utmp ubuf' has incomplete type and cannot
be defined
gmake[4]: *** [find_user.o] Error 1
The code in find_user.cpp reads:
...
#endif /*UTMP_AND_PROC_FIND_USER*/
#else /*not PROC_FIND_USER*/
int find_user(char *name, char *tty, char *disp) {
struct utmp ubuf;<<<<<<<<<<<<<< line 344
int status;
FILE *fd;
struct stat statb;
char ftty[20+UT_LINESIZE];
char ttyFound[UT_LINESIZE] = "";
char dispFound[UT_HOSTSIZE+1] = "";
if (!(fd = fopen(_PATH_UTMP, "r"))) {
fprintf(stderr, "talkd: can't read %s.\n", _PATH_UTMP);
return (FAILED);
}
Something wrong with 'struct utmp ubuf' in HEAD?
Thanks
mattihas
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
KDE 3.5.10_6 compiled (was Re: 9-CURRENT: ports/net/kdenetwork3 does not compile)
Just for the records: After applying the patch for net/kdenetwork3 from
Ed (thanks again for this), the port x11/kde3 (3.5.10_6) compiled fine
on -CURRENT without further tweakings; and it comes up fine too :-)
I've two smaller problems to investigate
1) I can't zapp the Xorg server with CTRL-ALT-BS (I've checked with
xev(1) that the keys are working)
2) after KDE shutdown, the X server restarts again in background and I
must kill the X proc manually...
Any ideas about this?
Thanks
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
laptop Acer Aspire One D250 / snd_hda(4) && internal mic not recording
Hello, I have the above modell running 9-CURRENT, but can't get the build-in mic recording, only the jack for the mic in the headset records fine in Skype; here are the output of /dev/sndstat and mixer(1): $ cat /dev/sndstat FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: (play/rec) default pcm1: (rec) $ mixer Mixer vol is currently set to 66:66 Mixer pcm is currently set to 40:40 Mixer mic is currently set to 70:70 Mixer mix is currently set to 74:74 Mixer rec is currently set to 75:75 Mixer igainis currently set to 57:57 Mixer ogainis currently set to 65:65 Recording source: mic mixer(1) let me set for recoding only 'mic' or 'rec'. I'm attaching as well the output of verbose messages grep'ed for pcm and hdac. Btw: Is there some tutorial for the settings mentioned in snd_hda(4), I don't understand the man page without more background info :-( Btw II: Is there some test recording software that let me just record from /dev/dspX and play it back (to not use Skype for such tests)? Thanks in advance for any help matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ hdac0: OSS: pcm (pcm) hdac0: OSS: pcm, mix pcm0: at cad 0 nid 1 on hdac0 pcm0: +--+ pcm0: | DUMPING PCM Playback/Record Channels | pcm0: +--+ pcm0: pcm0: Playback: pcm0: pcm0: Stream cap: 0x0001 pcm0: PCM pcm0: PCM cap: 0x000e0560 pcm0: 16 20 24 bits, 44 48 96 192 KHz pcm0: DAC: 2 pcm0: pcm0: Record: pcm0: pcm0: Stream cap: 0x0001 pcm0: PCM pcm0: PCM cap: 0x000e0560 pcm0: 16 20 24 bits, 44 48 96 192 KHz pcm0: ADC: 8 pcm0: pcm0: +---+ pcm0: | DUMPING Playback/Record Paths | pcm0: +---+ pcm0: pcm0: Playback: pcm0: pcm0: nid=20 [pin: Speaker (Fixed)] pcm0: | pcm0: + <- nid=12 [audio mixer] [src: pcm, mix] pcm0: | pcm0: + <- nid=2 [audio output] [src: pcm] pcm0: + <- nid=11 [audio mixer] [src: mix] pcm0: pcm0: nid=33 [pin: Headphones (Green Jack)] pcm0: | pcm0: + <- nid=12 [audio mixer] [src: pcm, mix] pcm0: | pcm0: + <- nid=2 [audio output] [src: pcm] pcm0: + <- nid=11 [audio mixer] [src: mix] pcm0: pcm0: Record: pcm0: pcm0: nid=8 [audio input] pcm0: | pcm0: + <- nid=35 [audio mixer] [src: mic, mix] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] pcm0: + <- nid=11 [audio mixer] [src: mix] pcm0: pcm0: Input Mix: pcm0: pcm0: nid=11 [audio mixer] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] pcm0: pcm0: +-+ pcm0: | DUMPING Volume Controls | pcm0: +-+ pcm0: pcm0: Master Volume (OSS: vol) pcm0:| pcm0:+- ctl 1 (nid 2 out):-64/0dB (65 steps) pcm0:+- ctl 14 (nid 12 in 0): mute pcm0:+- ctl 15 (nid 12 in 1): mute pcm0:+- ctl 22 (nid 20 in ):mute pcm0:+- ctl 34 (nid 33 in ):mute pcm0: pcm0: PCM Volume (OSS: pcm) pcm0:| pcm0:+- ctl 1 (nid 2 out):-64/0dB (65 steps) pcm0:+- ctl 14 (nid 12 in 0): mute pcm0: pcm0: Microphone Volume (OSS: mic) pcm0:| pcm0:+- ctl 27 (nid 24 out):0/30dB (4 steps) pcm0:+- ctl 45 (nid 35 in 0): mute pcm0: pcm0: Recording Level (OSS: rec) pcm0:| pcm0:+- ctl 4 (nid 8 in 0): -16/30dB (32 steps) + mute pcm0:+- ctl 45 (nid 35 in 0): mute pcm0:+- ctl 53 (nid 35 in 8): mute pcm0: pcm0: Input Mix Level (OSS: mix) pcm0:| pcm0:+- ctl 6 (nid 11 in 0): -34/12dB (32 steps) + mute pcm0:+- ctl 15 (nid 12 in 1): mute pcm0:+- ctl 53 (nid 35 in 8): mute pcm0: pcm0: Input Monitoring Level (OSS: igain) pcm0:| pcm0:+- ctl 15 (nid 12 in 1): mute pcm0: pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "mic": pcm0: Mixer "mix": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "ogain": pcm0: clone manager: deadline=750ms flags=0x801e pcm0: sndbuf_setmap 3e20, 4000; 0xe472d000 -> 3e20 pcm0: sndbuf_setmap 3e21, 4000; 0xe473d000 -> 3e21 pcm1: at cad 0 nid 1 on hdac0 pcm1: +--+ pcm1: | DUMPING PCM Playback/Record Channels | pcm1: +--+ pcm1: pcm1: Record: pcm1: pcm1: Stream cap: 0x0001 pcm1: PCM pcm1: PCM cap: 0x000e0560 pcm1: 16 20 24 bits, 44 48 96 192 KHz pcm1: ADC: 9 pcm1: pcm1: +-
Re: laptop Acer Aspire One D250 / snd_hda(4) && internal mic not recording
El día Friday, November 05, 2010 a las 12:46:50AM +0200, Alexander Motin escribió: > Matthias Apitz wrote: > > > > mixer(1) let me set for recoding only 'mic' or 'rec'. I'm attaching as > > well the output of verbose messages grep'ed for pcm and hdac. > > Your CODEC configured to provide built-in microphone on separate device > pcm1. You may record from there (Skype allows to choose device) or > reconfigure CODEC using hints. In Skype in let me choose between /dev/dsp /dev/dsp0 /dev/dsp1 When I set mic to /dev/dsp0 it records from the jack (headphone mic), when I set it to /dev/dsp1 there is no recording. And the mixer for the pcm1 says: # mixer -f /dev/mixer1 Mixer rec is currently set to 100:100 Mixer monitor is currently set to 100:100 Recording source: monitor Would you be so kind and give me the lines for reconfigure CODEC using hints? I'm really lost in this. Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: laptop Acer Aspire One D250 / snd_hda(4) && internal mic not recording
El día Friday, November 05, 2010 a las 01:13:15AM +0200, Alexander Motin escribió: > Matthias Apitz wrote: > > El día Friday, November 05, 2010 a las 12:46:50AM +0200, Alexander Motin > > escribió: > >> Matthias Apitz wrote: > >>> mixer(1) let me set for recoding only 'mic' or 'rec'. I'm attaching as > >>> well the output of verbose messages grep'ed for pcm and hdac. > >> Your CODEC configured to provide built-in microphone on separate device > >> pcm1. You may record from there (Skype allows to choose device) or > >> reconfigure CODEC using hints. > > > > In Skype in let me choose between > > /dev/dsp > > /dev/dsp0 > > /dev/dsp1 > > > > When I set mic to /dev/dsp0 it records from the jack (headphone mic), > > when I set it to /dev/dsp1 there is no recording. And the mixer for the > > pcm1 says: > > > > # mixer -f /dev/mixer1 > > Mixer rec is currently set to 100:100 > > Mixer monitor is currently set to 100:100 > > Recording source: monitor > > That's strange. I would expect it working. > > > Would you be so kind and give me the lines for reconfigure CODEC using > > hints? I'm really lost in this. > > OK, try this: > hint.hdac.0.cad0.nid18.config="as=2 seq=1" Thank you. The result of this is: 1) mixer(1) is now showing a line 'monitor' in addition and as recording source: # mixer Mixer vol is currently set to 83:83 Mixer pcm is currently set to 78:78 Mixer mic is currently set to 87:87 Mixer mix is currently set to 81:81 Mixer rec is currently set to 65:65 Mixer igainis currently set to 78:78 Mixer ogainis currently set to 65:65 Mixer monitor is currently set to 87:87 Recording source: mix, monitor 2) in Skype I can only choos between /dev/dsp and /dev/dsp0 and /dev/mixer1 does not exist anymore; 3) recording still works only from jack, not from build-in mic; 4) if I set 'mixer =rec monitor' it does not even record from the jack; I even checked the BIOS if there is something to disable the mic, but it isn't. Thanks for your help in any case. Btw: If this does matter, it is with kernel r21. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
utmpx (was: Re: 9-CURRENT: ports/net/kdenetwork3 does not compile)
Hello, I found another port lacking utmpx support: # cd /usr/ports/security/chkrootkit # make ===> chkrootkit-0.49 is marked as broken: fails to build with new utmpx. *** Error code 1 matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: laptop Acer Aspire One D250 / snd_hda(4) && internal mic not recording
El día Friday, November 05, 2010 a las 12:46:50AM +0200, Alexander Motin
escribió:
> Matthias Apitz wrote:
> > ...
> > Btw II: Is there some test recording software that let me just record
> > from /dev/dspX and play it back (to not use Skype for such tests)?
>
> dd? :) Also audio/rawrec.
Indeed, a
# dd if=/dev/dsp0.0 > file
records and
# cat file > /dev/dsp0.0
plays fine the recorded voice... but only from Jack :-(
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: laptop Acer Aspire One D250 / snd_hda(4) && internal mic not recording
El día Friday, November 05, 2010 a las 01:13:15AM +0200, Alexander Motin escribió: > > # mixer -f /dev/mixer1 > > Mixer rec is currently set to 100:100 > > Mixer monitor is currently set to 100:100 > > Recording source: monitor > > That's strange. I would expect it working. > > > Would you be so kind and give me the lines for reconfigure CODEC using > > hints? I'm really lost in this. > > OK, try this: > hint.hdac.0.cad0.nid18.config="as=2 seq=1" I've tried this and a lot of other hint.hdac for which I now have some kind of understanding... all with no luck; it is only recording noice (not silense, but noise). I think there is something wrong either with the hardware or something in the driver, because searching in Google for "acer aspire one mic" I found a lot of complaints about the internal mic not working, for example in Ubuntu it needs some special tweaking: http://ubuntuforums.org/showthread.php?t=952568 https://help.ubuntu.com/community/AspireOneAOD250 (the last one speaks about some alsa driver) What do you think about? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: laptop Acer Aspire One D250 / snd_hda(4) && internal mic not recording
El día Thursday, November 04, 2010 a las 11:23:36PM +0100, Matthias Apitz
escribió:
>
>
> Hello,
>
> I have the above modell running 9-CURRENT, but can't get the build-in
> mic recording, only the jack for the mic in the headset records fine in
> Skype;
...
I have another mini laptop, for years already, an EeePC 900 in which the
internal mic works fine. I thought it would be a good idea to look in
detail what the diff is between, because both are using snd_hda(4) for
sound. It turned out, surprise I never realized this, that the EeePC has
the same problem, but the other way around: only the internal mic is
recording and the jack does not. Per default both mic (nid 24 and 25) are in
association 2:
hdac0: nid 24 0x01a19820 as 2 seq 0 Mic Jack jack 1 loc 1 colorPink
misc 8
hdac0: nid 25 0x99a3092f as 2 seq 15 Mic Fixed jack 3 loc 25 color Unknown
misc 9
I'm attaching both verbose messages of hdac, maybe some snd_hda(4)
expert understands from the diff of both what the problem in both is.
Thanks
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
hdac0: mem
0x5834-0x58343fff irq 16 at device 27.0 on pci0
hdac0: HDA Driver Revision: 20100226_0142
hdac0: attempting to allocate 1 MSI vectors (1 supported)
hdac0: using IRQ 256 for MSI
hdac0: Caps: OSS 4, ISS 4, BSS 0, NSDO 1, 64bit, CORB 256, RIRB 256
hdac0: Probing codec #0...
hdac0: HDA Codec #0: Realtek ALC272
hdac0: HDA Codec ID: 0x10ec0272
hdac0:Vendor: 0x10ec
hdac0:Device: 0x0272
hdac0: Revision: 0x00
hdac0: Stepping: 0x01
hdac0: PCI Subvendor: 0x022f1025
hdac0: Found audio FG nid=1 startnode=2 endnode=36 total=34
hdac0:
hdac0: Processing audio FG cad=0 nid=1...
hdac0: GPIO: 0x4002 NumGPIO=2 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1
hdac0: nid 17 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 18 0x99a30930 as 3 seq 0 Mic Fixed jack 3 loc 25 color
Unknown misc 9
hdac0: nid 19 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 20 0x99130110 as 1 seq 0 Speaker Fixed jack 3 loc 25 color
Unknown misc 1
hdac0: nid 21 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 22 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 23 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 24 0x03a19820 as 2 seq 0 Mic Jack jack 1 loc 3 color
Pink misc 8
hdac0: nid 25 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 26 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 27 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 29 0x4016892d as 2 seq 13 Speaker None jack 6 loc 0 color
Purple misc 9
hdac0: nid 30 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1
hdac0: nid 33 0x0321401f as 1 seq 15Headphones Jack jack 1 loc 3 color
Green misc 0
hdac0: Patched pins configuration:
hdac0: nid 17 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 18 0x99a30930 as 3 seq 0 Mic Fixed jack 3 loc 25 color
Unknown misc 9
hdac0: nid 19 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 20 0x99130110 as 1 seq 0 Speaker Fixed jack 3 loc 25 color
Unknown misc 1
hdac0: nid 21 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 22 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 23 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 24 0x03a19820 as 2 seq 0 Mic Jack jack 1 loc 3 color
Pink misc 8
hdac0: nid 25 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 26 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 27 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 29 0x4016892d as 2 seq 13 Speaker None jack 6 loc 0 color
Purple misc 9 [DISABLED]
hdac0: nid 30 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color
Black misc 1 [DISABLED]
hdac0: nid 33 0x0321401f as 1 seq 15Headphones Jack jack 1 loc 3 color
Green misc 0
hdac0: 3 associations found:
hdac0: Association 0 (1) out:
hdac0: Pin nid=20 seq=0
hdac0: Pin nid=33 seq=15
hdac0: Association 1 (2) in:
hdac0: Pin nid=24 seq=0
hdac0: Association 2 (3) in:
hdac0: Pin nid=18 seq=0
hdac0: Tracing association 0 (1)
hdac0: Pin 20 traced to
Re: laptop Acer Aspire One D250 / snd_hda(4) && internal mic not recording
El día Friday, November 05, 2010 a las 01:13:15AM +0200, Alexander Motin escribió: > Matthias Apitz wrote: > > El día Friday, November 05, 2010 a las 12:46:50AM +0200, Alexander Motin > > escribió: > >> Matthias Apitz wrote: > >>> mixer(1) let me set for recoding only 'mic' or 'rec'. I'm attaching as > >>> well the output of verbose messages grep'ed for pcm and hdac. > >> Your CODEC configured to provide built-in microphone on separate device > >> pcm1. You may record from there (Skype allows to choose device) or > >> reconfigure CODEC using hints. > > > > In Skype in let me choose between > > /dev/dsp > > /dev/dsp0 > > /dev/dsp1 > > > > When I set mic to /dev/dsp0 it records from the jack (headphone mic), > > when I set it to /dev/dsp1 there is no recording. And the mixer for the > > pcm1 says: > > > > # mixer -f /dev/mixer1 > > Mixer rec is currently set to 100:100 > > Mixer monitor is currently set to 100:100 > > Recording source: monitor > > That's strange. I would expect it working. > > > Would you be so kind and give me the lines for reconfigure CODEC using > > hints? I'm really lost in this. > > OK, try this: > hint.hdac.0.cad0.nid18.config="as=2 seq=1" Hi Alexander, While trying to get understandig of the verbose boot messages of snd_hda(4), I found the following which seems to match the problem (only recording from Jack): hdac0: nid 18 0x99a30930 as 3 seq 0 Mic Fixed jack 3 loc 25 color Unknown misc 9 ... hdac0: nid 24 0x03a19820 as 2 seq 0 Mic Jack jack 1 loc 3 color Pink misc 8 i.e. the nid's are 18 (internal mic) and 24 (Jack); But in the DUMPING's Playback/Record Paths the nid=18 and nid=24 look different: 24: pcm0: Record: pcm0: pcm0: nid=8 [audio input] pcm0: | pcm0: + <- nid=35 [audio mixer] [src: mic, mix] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] pcm0: + <- nid=11 [audio mixer] [src: mix] pcm0: pcm0: Input Mix: pcm0: pcm0: nid=11 [audio mixer] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] 18: pcm1: Record: pcm1: pcm1: nid=9 [audio input] pcm1: | pcm1: + <- nid=34 [audio mixer] [src: monitor] pcm1: | pcm1: + <- nid=18 [pin: Mic (Fixed)] [src: monitor] (there is no 'Input Mix:' section part for nid=18) Can this cause the problem? What else could I debug to nail this down? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
snd_hda(4): speaker DISABLED after update to 9-CURRENT
Hello, I've installed 9-CURRENT on a laptop which worked fine before with 7.0-REL, concerning the sound via snd_hda(4). Now there is only sound coming out from the headphone jack and I don't see how to enable the speaker again. Btw: Why is this now so different on the same hardware with the same driver? $ cat /dev/sndstat FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: (play/rec) default pcm1: (rec) pcm2: (rec) I'm attaching as well the grep'ed dmesg output for 'hdac' and 'pcm'. Could someone please give me a hint how to get the speaker working again? Thanks in advance matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ hdac0: OSS: pcm (pcm) hdac0: OSS: pcm (pcm) hdac0: OSS: pcm (pcm) hdac0: OSS: pcm (pcm) hdac0: OSS: pcm (pcm) hdac0: OSS: pcm, speaker, line, mic, monitor hdac0: OSS: pcm, speaker, line, mic, monitor hdac0: OSS: pcm, speaker, line, mic, monitor hdac0: OSS: pcm, speaker, line, mic, monitor pcm0: at cad 1 nid 1 on hdac0 pcm0: +--+ pcm0: | DUMPING PCM Playback/Record Channels | pcm0: +--+ pcm0: pcm0: Playback: pcm0: pcm0: Stream cap: 0x0001 pcm0: PCM pcm0: PCM cap: 0x000e0160 pcm0: 16 20 24 bits, 44 48 96 KHz pcm0: DAC: 2 4 3 5 6 pcm0: pcm0: Record: pcm0: pcm0: Stream cap: 0x0005 pcm0: AC3 PCM pcm0: PCM cap: 0x001e0160 pcm0: 16 20 24 32 bits, 44 48 96 KHz pcm0: ADC: 10 pcm0: pcm0: +---+ pcm0: | DUMPING Playback/Record Paths | pcm0: +---+ pcm0: pcm0: Playback: pcm0: pcm0: nid=20 [pin: Line-out (Green Jack)] pcm0: | pcm0: + <- nid=12 [audio mixer] [src: pcm, speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=2 [audio output] [src: pcm] pcm0: + <- nid=11 [audio mixer] [src: speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] pcm0: + <- nid=25 [pin: Mic (Pink Jack)] [src: monitor] pcm0: + <- nid=26 [pin: Line-in (Blue Jack)] [src: line] pcm0: + <- nid=29 [beep widget] [src: speaker] pcm0: pcm0: nid=22 [pin: Line-out (Orange Jack)] pcm0: | pcm0: + <- nid=14 [audio mixer] [src: pcm, speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=4 [audio output] [src: pcm] pcm0: + <- nid=11 [audio mixer] [src: speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] pcm0: + <- nid=25 [pin: Mic (Pink Jack)] [src: monitor] pcm0: + <- nid=26 [pin: Line-in (Blue Jack)] [src: line] pcm0: + <- nid=29 [beep widget] [src: speaker] pcm0: pcm0: nid=21 [pin: Line-out (Black Jack)] pcm0: | pcm0: + <- nid=13 [audio mixer] [src: pcm, speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=3 [audio output] [src: pcm] pcm0: + <- nid=11 [audio mixer] [src: speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] pcm0: + <- nid=25 [pin: Mic (Pink Jack)] [src: monitor] pcm0: + <- nid=26 [pin: Line-in (Blue Jack)] [src: line] pcm0: + <- nid=29 [beep widget] [src: speaker] pcm0: pcm0: nid=23 [pin: Line-out (Grey Jack)] pcm0: | pcm0: + <- nid=15 [audio mixer] [src: pcm, speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=5 [audio output] [src: pcm] pcm0: + <- nid=11 [audio mixer] [src: speaker, line, mic, monitor] pcm0: | pcm0: + <- nid=24 [pin: Mic (Pink Jack)] [src: mic] pcm0: + <- nid=25 [pin: Mic (Pink Jack)] [src: monitor] pcm0: + <- nid=26 [pin: Line-in (Blue Jack)] [src: line] pcm0: + <- nid=29 [beep widget] [src: speaker] pcm0: pcm0: nid=30 [pin: SPDIF-out (Black Jack)] pcm0: | pcm0: + <- nid=6 [audio output] [src: pcm] pcm0: pcm0: Record: pcm0: pcm0: nid=10 [audio input] pcm0: | pcm0: + <- nid=31 [pin: SPDIF-in (Orange Jack)] [src: dig1] pcm0: pcm0: +-+ pcm0: | DUMPING Volume Controls | pcm0: +-+ pcm0: pcm0: Master Volume (OSS: vol) pcm0:| pcm0:+- ctl 12 (nid 12 out):-64/0dB (65 steps) pcm0:+- ctl 13 (nid 12
Re: snd_hda(4): speaker DISABLED after update to 9-CURRENT
El día Saturday, February 26, 2011 a las 01:52:02PM -0500, Eitan Adler escribió: > On Sat, Feb 26, 2011 at 11:58 AM, Matthias Apitz wrote: > > Could someone please give me a hint how to get the speaker working again? > > Try changing sysctl hw.snd.default_unit=0/1/2 Thanks, but this was my first check as well and does not help. I started to play around with the device.hints(5) config and here is what I figured out: It took me some tine to realize that 'cad0' is the modem, while the real audio is 'cad1'. So I set in device.hints(5): # kenv | fgrep hdac hint.hdac.0.cad1.nid20.config="as=1 seq=15 device=Headphones" hint.hdac.0.cad1.nid28.config="as=2 seq=0 device=Speaker" which is to be seen in the verbose logging on boot as: # dmesg | fgrep hdac | more ... hdac0: Found modem FG nid=1 startnode=2 endnode=38 total=36 hdac0: Probing codec #1... hdac0: HDA Codec #1: Realtek ALC880 hdac0: HDA Codec ID: 0x10ec0880 hdac0:Vendor: 0x10ec hdac0:Device: 0x0880 hdac0: Revision: 0x08 hdac0: Stepping: 0x00 hdac0: PCI Subvendor: 0x107c1734 hdac0: Found audio FG nid=1 startnode=2 endnode=34 total=32 hdac0: hdac0: Processing modem FG cad=0 nid=1... hdac0: hdac0: Processing audio FG cad=1 nid=1... hdac0: GPIO: 0x4002 NumGPIO=2 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 hdac0: nid 20 0x01014010 as 1 seq 0 Line-out Jack jack 1 loc 1 color Green misc 0 hdac0: Patching pin config nid=20 0x01014010 -> 0x0121401f ... hdac0: nid 28 0x41f0 as 15 seq 0 Speaker None jack 1 loc 1 color Black misc 1 hdac0: Patching pin config nid=28 0x41f0 -> 0x4120 i.e. the above device.hints(5) are realized by snd_hda(4); but than it says: hdac0: Patched pins configuration: hdac0: nid 20 0x0121401f as 1 seq 15Headphones Jack jack 1 loc 1 color Green misc 0 ... hdac0: nid 28 0x4120 as 2 seq 0 Speaker None jack 1 loc 1 color Black misc 1 [DISABLED] why is 'nid 28' DISABLED? in the user-land the situation is like this: there are 3 mixer (/dev/mixer0..2) and of course I checked if they are all fully up, with one exeption: # mixer -f /dev/mixer2 Recording source: monitor i.e. the recording level can't be controlled, why? there are the following /dev/dsp* devices: # ls /dev/dsp* /dev/dsp0.0 /dev/dsp0.1 /dev/dsp1.0 /dev/dsp2.0 and with Skype (or also just with dd(1)) recording can be done from the device /dev/dsp2 and audio is coming out from /dev/dsp0 (but only through the headphone Jack). What can I do to make the Speaker of the laptop working? The Speaker itself works, for example without any application it just echoes back what from the internal microphone or from the headset micro is coming. Thanks in advance mattias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
updating my pordriere oven to latest CURRENT
Hello,
I'm short before updating my poudriere oven, a Dell PowerEdge r210, from
r318593 to r338641. I have there a ZFS in use for poudriere, created
with:
# zpool create poudriere /dev/da1
and set in /usr/local/etc/poudriere.conf:
ZPOOL=poudriere
ZROOTFS=/poudriere
# zpool list
NAMESIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT
poudriere 278G 3.90G 274G -13% 1% 1.00x ONLINE -
# mount
/dev/da0p2 on / (ufs, local, journaled soft-updates)
devfs on /dev (devfs, local, multilabel)
poudriere on /poudriere (zfs, local, nfsv4acls)
poudriere/poudriere on /poudriere/poudriere (zfs, local, nfsv4acls)
poudriere/poudriere/jails on /poudriere/poudriere/jails (zfs, local, nfsv4acls)
...
Before running 'make installkernel' ... and later updating the poudriere
tool itself from ports too, I wanted to ask if I have to take care about
anything before. I've read src/UPDATING between the above mentioned versions and
can't see anything, i.e. the zpool should be fine after the update too.
Any comments on this? Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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"
CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4
Hello, I have here a reproducible Segmentation fault in staging phase of the port x11/kde-workspace-kde4; the full log file is here: http://www.unixarea.de/kde-workspace-kde4-4.11.22_26.log The first few lines and the end of the log are below; any comments or hints how to nail this down? Thanks matthias =>> Building x11/kde-workspace-kde4 build started at Fri Sep 21 05:23:49 CEST 2018 port directory: /usr/ports/x11/kde-workspace-kde4 package name: kde-workspace-kde4-4.11.22_26 building for: FreeBSD freebsd-r338641-ports-20180920-job-03 12.0-ALPHA5 FreeBSD 12.0-ALPHA5 1200084 amd64 maintained by: k...@freebsd.org Makefile ident: $FreeBSD: head/x11/kde-workspace-kde4/Makefile 479538 2018-09-11 18:34:27Z zeising $ Poudriere version: 3.2.99.20180601 Host OSVERSION: 1200084 Jail OSVERSION: 1200084 Job Id: 03 ---Begin Environment--- SHELL=/bin/csh OSVERSION=1200084 UNAME_v=FreeBSD 12.0-ALPHA5 1200084 UNAME_r=12.0-ALPHA5 BLOCKSIZE=K MAIL=/var/mail/root STATUS=1 HOME=/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin LOCALBASE=/usr/local USER=root LIBEXECPREFIX=/usr/local/libexec/poudriere POUDRIERE_VERSION=3.2.99.20180601 MASTERMNT=/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref POUDRIERE_BUILD_TYPE=bulk PACKAGE_BUILDING=yes SAVED_TERM=screen GID=0 UID=0 PWD=/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref/.p/pool P_PORTS_FEATURES=FLAVORS SELECTED_OPTIONS MASTERNAME=freebsd-r338641-ports-20180920 SCRIPTPREFIX=/usr/local/share/poudriere OLDPWD=/usr/local/poudriere/data/.m/freebsd-r338641-ports-20180920/ref/.p SCRIPTPATH=/usr/local/share/poudriere/bulk.sh POUDRIEREPATH=/usr/local/bin/poudriere ---End Environment--- ---Begin Poudriere Port Flags/Env--- PORT_FLAGS= PKGENV= FLAVOR= DEPENDS_ARGS= MAKE_ARGS= ---End Poudriere Port Flags/Env--- ---Begin OPTIONS List--- ===> The following configuration options are available for kde-workspace-kde4-4.11.22_26: GLES=on: OpenGL ES 2.0 support in kwin and kinfocenter GPS=on: GPS geolocation via gpsd KACTIVITY=on: Activity Manager daemon UPOWER=on: Power management via UPower WALLPAPERS=on: Install official KDE wallpapers > Multimedia support via Phonon GSTREAMER=off: Multimedia via Phonon-GStreamer VLC=on: Multimedia via Phonon-VLC > Options available for the group PLASMA PYTHON=off: Python plasmoids support RUBY=off: Ruby plasmoids support ===> Use 'make config' to modify these settings ---End OPTIONS List--- --MAINTAINER-- k...@freebsd.org --End MAINTAINER-- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- ... -- Installing: /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/apps/kstyle/themes/qtplastique.themerc -- Installing: /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/apps/kstyle/themes/qtwindows.themerc -- Installing: /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/apps/kstyle/themes/qtgtk.themerc gmake[1]: Leaving directory '/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/.build' install -l rs /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde4 /bin/mkdir -p /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions install -m 0644 /usr/ports/x11/kde-workspace-kde4/files/kde4.desktop /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions > Compressing man pages (compress-man) ===> Staging rc.d startup script(s) === === ===> Building package for kde-workspace-kde4-4.11.22_26 Child process pid=81309 terminated abnormally: Segmentation fault *** Error code 1 Stop. make: stopped in /usr/ports/x11/kde-workspace-kde4 =>> Cleaning up wrkdir ===> Cleaning for kde-workspace-kde4-4.11.22_26 build of x11/kde-workspace-kde4 | kde-workspace-kde4-4.11.22_26 ended at Fri Sep 21 05:40:40 CEST 2018 build time: 00:16:51 !!! build failure encountered !!! -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub signature.asc Description: PGP signature
Re: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4
El día Friday, September 21, 2018 a las 06:54:25AM +0200, Matthias Apitz escribió: > > Hello, > > I have here a reproducible Segmentation fault in staging phase of the > port x11/kde-workspace-kde4; the full log file is here: > http://www.unixarea.de/kde-workspace-kde4-4.11.22_26.log > > The first few lines and the end of the log are below; any comments or > hints how to nail this down? Thanks I filed a PR re/ ports: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231532 but I think the culprit is the base system because the component which segfaults is 'pkg-static': ... === ===> Building package for kde-workspace-kde4-4.11.22_26 Child process pid=67229 terminated abnormally: Segmentation fault *** Error code 1 /var/log/messages: Sep 21 09:19:51 jet kernel: pid 67229 (pkg-static), uid 65534: exited on signal 11 As this is running in a poudriere jail, how could I get a core file of this? matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4
El día Friday, September 21, 2018 a las 10:08:57AM +0200, Matthias Apitz escribió: > I filed a PR re/ ports: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231532 > > but I think the culprit is the base system because the component which > segfaults is 'pkg-static': > > ... > === > ===> Building package for kde-workspace-kde4-4.11.22_26 > Child process pid=67229 terminated abnormally: Segmentation fault > *** Error code 1 > > /var/log/messages: > > Sep 21 09:19:51 jet kernel: pid 67229 (pkg-static), uid 65534: exited on > signal 11 > > As this is running in a poudriere jail, how could I get a core file of > this? This is ofc a bit wrong because poudriere is installing the port to have pkg: === ===> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg - not found ===> Installing existing package /packages/All/pkg-1.10.5_3.txz [freebsd-r338641-ports-20180920-job-03] Installing pkg-1.10.5_3... [freebsd-r338641-ports-20180920-job-03] Extracting pkg-1.10.5_3: .. done I will remove this pkg /packages/All/pkg-1.10.5_3.txz again and will poudriere ask to build ports-mgmt/pkg-devel instead of this, because this is already on level 1.10.99. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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: CURRENT r338641 with poudriere-devel: seg fault on building x11/kde-workspace-kde4
El día Friday, September 21, 2018 a las 11:17:59AM +0200, Matthias Apitz escribió: > === > ===> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg - > not found > ===> Installing existing package /packages/All/pkg-1.10.5_3.txz > [freebsd-r338641-ports-20180920-job-03] Installing pkg-1.10.5_3... > [freebsd-r338641-ports-20180920-job-03] Extracting pkg-1.10.5_3: .. > done > > I will remove this pkg /packages/All/pkg-1.10.5_3.txz again and will > poudriere ask to build ports-mgmt/pkg-devel instead of this, because > this is already on level 1.10.99. I found no way that poudriere uses ports-mgmt/pkg-devel, it always compiles again ports-mgmt/pkg before kde-workspace-kde4-4.11.22_26, which crashes :-( Any hints? matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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"
r338641 && /dev/cyapa0: moused does not show pointer on console
Hello, I've booted a fresh r338641 from an USB key on my Acer C720, and have the required modules loaded at boot (cyapa and ig4) and the values for cyapa in /boot/device.hints, as I do use them in r314251. The moused is running as /usr/sbin/moused -p /dev/cyapa0 -t ps/2 but no mouse pointer is written on the console. If I do # cat /dev/cyapa0 on TP movements, bytes can be read by cat(1). And trussing the PID of the moused shows too that it is reading bytes. What could be wrong? matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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: r338641 && /dev/cyapa0: moused does not show pointer on console
El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz escribió: > > Hello, > > I've booted a fresh r338641 from an USB key on my Acer C720, and have > the required modules loaded at boot (cyapa and ig4) and the values for cyapa > in > /boot/device.hints, as I do use them in r314251. The moused is running as > > /usr/sbin/moused -p /dev/cyapa0 -t ps/2 > > but no mouse pointer is written on the console. If I do > > # cat /dev/cyapa0 > > on TP movements, bytes can be read by cat(1). And trussing the PID of > the moused shows too that it is reading bytes. > > What could be wrong? additional information: when I do load *after* boot # kldload i915kms the mouse pointer appears and can be moved. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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: r338641 && /dev/cyapa0: moused does not show pointer on console
El día Monday, September 24, 2018 a las 12:46:17PM +0300, Michael Gmelin
escribió:
> > What could be wrong?
>
> Do you by any chance use vt(4) in vga textmode (hw.vga.textmode=1)?
>
> vt doesn’t support hardware mouse cursors, so no cursor in text mode (see
> https://wiki.freebsd.org/Newcons)
>
Thanks. When I remove hw.vga.textmode=1 the mouse pointer comes up and
works.
Re/ i915kms, I have to load it with kldload by hand. If I load it via
loader.conf, the cyapa devices (both) say 'Unable to bring the device
out of bootstrap'.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
___
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: r338641 && /dev/cyapa0: moused does not show pointer on console
El día Monday, September 24, 2018 a las 09:01:34PM +0200, Michael Gmelin escribió: > >> On 24/09/2018 13:21, Matthias Apitz wrote: > >> Re/ i915kms, I have to load it with kldload by hand. If I load it via > >> loader.conf, the cyapa devices (both) say 'Unable to bring the device > >> out of bootstrap'. > > > > That's probably because you use device hints to configure cyapa, but i2c bus > > numbers are different depending on whether the kms driver is loaded or not > > (because it also creates i2c buses). > > > > Try to remove the hints and to use chromebook_platform(4) instead. Thanks, I will test chromebook_platform_load="YES" > Also, I think the preferred way to load i915kms is to use kld_list (might be > unrelated, but still). > > pkg install drm-next-kmod > sysrc kld_list="/boot/modules/i915kms.ko" Thanks too. On my laptop in production I do use a handmade script /usr/local/etc/rc.d/loadi915kms to load the module at late time. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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"
mkimg(1) creates a file in TMPDIR until no space left
Hello, I'm using a copy of src/release/amd64/make-memstick.sh to build from a complete root in /usr/local/r338641/root.r338641 (result of make installworld and installkernel to this dir) for testing purpose a memstick image and write this with dd(1) to an USB key of ~32 GByte. I'm using a copy of this script because I want to define the size of the UFS in the image to have there enough free space to install later after boot as well packages to test them. The modification is only setting '-M 50331648b -m 50331648b' for the file system created with mkfs(8). Here is what is running exactly: # TMPDIR=/usr/tmp export TMPDIR # ./make-memstick.sh /usr/local/r338641/root.r338641 /usr/local/r338641/memstick.im + makefs -B little -M 50331648b -m 50331648b -o 'label=FreeBSD_Install' -o 'version=2' /usr/local/r338641/memstick.im.part /usr/local/r338641/root.r338641 Calculated size of `/usr/local/r338641/memstick.im.part': 25769803776 bytes, 24530 inodes Extent size set to 32768 /usr/local/r338641/memstick.im.part: 24576.0MB (50331648 sectors) block size 32768, fragment size 4096 using 28 cylinder groups of 901.44MB, 28846 blks, 1024 inodes. super-block backups (for fsck -b #) at: 192, 1846336, 3692480, 5538624, 7384768, 9230912, 11077056, 12923200, 14769344, 16615488, 18461632, 20307776, 22153920, 2464, 25846208, 27692352, 29538496, 31384640, 33230784, 35076928, 36923072, 38769216, 40615360, 42461504, 44307648, 46153792, 4736, 49846080, Populating `/usr/local/r338641/memstick.im.part' Image `/usr/local/r338641/memstick.im.part' complete + rm /usr/local/r338641/root.r338641/etc/fstab + rm /usr/local/r338641/root.r338641/etc/rc.conf.local + mkimg -C 28G -s mbr -b /usr/local/r338641/root.r338641/boot/mbr -p 'efi:=/usr/local/r338641/root.r338641/boot/boot1.efifat' -p 'freebsd:-mkimg -C 28G -s bsd -b /usr/local/r338641/root.r338641/boot/boot -p freebsd-ufs:=/usr/local/r338641/memstick.im.part' -a 2 -o /usr/local/r338641/memstick.im ... While the cascade of mkimg(1) is running a *big* temp file is created, which at the end eats up all memory of the disk: # ls -lh /usr/local/r338641 /usr/tmp /usr/local/r338641: total 25172008 -rwxr-xr-x 1 root wheel 1.3K Sep 29 16:41 make-memstick.sh -rw-r--r-- 1 root wheel 0B Sep 29 16:50 memstick.im -rw-r--r-- 1 root wheel24G Sep 29 16:50 memstick.im.part drwxr-xr-x 18 root wheel 512B Sep 24 07:11 root.r338641 /usr/tmp: total 11307168 -rw--- 1 root wheel 456G Sep 29 17:01 mkimg-LmntlL<<< 456G !!! -rw--- 1 root wheel 0B Sep 29 16:50 mkimg-yfU8Lr /: write failed, filesystem is full /: write failed, filesystem is full But the 'memstick.im' is created fine at the end: # ls -lh /usr/local/r338641 /usr/tmp /usr/local/r338641: total 2591752 -rwxr-xr-x 1 root wheel 1.3K Sep 29 16:41 make-memstick.sh -rw-r--r-- 1 root wheel24G Sep 29 17:22 memstick.im drwxr-xr-x 18 root wheel 512B Sep 24 07:11 root.r338641 /usr/tmp: total 0 And the UBS stick produced from 'memstick.im' with dd(1) boots fine and the root file system has around 20 GB free space. Why it is mkimg(1) creating such a big temp. file? matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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"
PR id=231810
Hello, Can some kind soul please modify this PR to reflect the Version and the affected people: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 Thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub signature.asc Description: PGP signature
Re: PR id=231810
El día Sunday, September 30, 2018 a las 08:12:17PM +1000, Kubilay Kocak escribió: > On 30/09/2018 5:52 pm, Matthias Apitz wrote: > > > > Hello, > > > > Can some kind soul please modify this PR to reflect the Version and the > > affected people: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 > > > > Thanks > > > > matthias > > > > Hi Matthias, > > I've updated the Severity, but the Version is better left at the lowest > (earliest) reported/confirmed version, to ensure it gets merged back to > the relevant stable branch. Hello Kubilay, At work we use Atlassian's JIRA as bugtracking system. This allows to set multiple versions affected by a single issue. Doesn't bugzilla allow this? Thanks anyway for changing the Severity. If someone needs me for some test to nail down this, I have a system for this. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub 13. August 2018: Manchmal möchte ich nun einen AUSREISEANTRAG stellen. August 13, 2018: Sometimes I'd like to ask for an exit permission now. ___ 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"
debugging a run of poudriere-bulk
Hello, I'm trying to nail down PR 231532 of a port which fails to build in poudriere. In the last phase of the ports build, while creating the pkg of the built port with pkg-static, this crashes: # tail /usr/local/poudriere/data/logs/bulk/freebsd-r338641-ports-20180920/2018-10-03_11h32m17s/logs/kde-workspace-kde4-4.11.22_26.log Child process pid=85086 terminated abnormally: Segmentation fault *** Error code 1 Stop. make: stopped in /usr/ports/x11/kde-workspace-kde4 =>> Cleaning up wrkdir # grep 85086 /var/log/messages Oct 3 11:44:01 jet kernel: pid 85086 (pkg-static), uid 65534: exited on signal 11 How can I enter the jail interactively in the moment after the crash to rerun and debug pkg-static? When I run 'poudriere bulk -i ...' the port builds fine: # poudriere bulk -i -J 1 -j freebsd-r338641 -p ports-20180920 x11/kde-workspace-kde4 # cd /usr/ports/x11/kde-workspace-kde4 # make package gmake[1]: Leaving directory '/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/.build' install -l rs /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/bin/startkde4 /bin/mkdir -p /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions install -m 0644 /usr/ports/x11/kde-workspace-kde4/files/kde4.desktop /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions > Compressing man pages (compress-man) ===> Staging rc.d startup script(s) ===> Building package for kde-workspace-kde4-4.11.22_26 cp: /packages/All/kde-workspace-kde4-4.11.22_26.txz: Read-only file system *** Error code 1 Stop. make: stopped in /usr/ports/x11/kde-workspace-kde4 # cd /usr/ports/x11/kde-workspace-kde4 # ls -l total 42 -rw-r--r-- 1 root wheel5480 Sep 20 05:16 Makefile -rw-r--r-- 1 root wheel 225 Sep 20 05:16 distinfo drwxr-xr-x 2 root wheel 30 Sep 20 05:16 files -rw-r--r-- 1 root wheel 219 Sep 20 05:16 pkg-descr -rw-r--r-- 1 root wheel 100336 Sep 20 05:16 pkg-plist # ls -la /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg total 17921 drwxr-xr-x 2 root wheel64 Oct 3 09:13 . drwxr-xr-x 7 root wheel 960 Oct 3 09:13 .. -rw-r--r-- 1 root wheel 18346688 Oct 3 09:13 kde-workspace-kde4-4.11.22_26.txz # scp -p /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz guru@192.168.2.35:/tmp -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub 13. August 2018: Ich würde gern einen AUSREISEANTRAG stellen. August 13, 2018: I'd like to ask for an exit permit of this country. signature.asc Description: PGP signature
Re: debugging a run of poudriere-bulk
El día miércoles, octubre 03, 2018 a las 01:41:14p. m. +0200, Matthias Apitz
escribió:
>
> Hello,
>
>
> I'm trying to nail down PR 231532 of a port which fails to build in
> poudriere. In the last phase of the ports build, while creating the pkg
> of the built port with pkg-static, this crashes:
When I do run pudriere bulk with -vv options, it says only:
[00:02:40] [01] [00:01:51] Status x11/kde-workspace-kde4 |
kde-workspace-kde4-4.11.22_26: build
[00:10:41] [01] [00:09:52] Status x11/kde-workspace-kde4 |
kde-workspace-kde4-4.11.22_26: run-depends
[00:10:46] [01] [00:09:57] Status x11/kde-workspace-kde4 |
kde-workspace-kde4-4.11.22_26: stage
[00:11:42] [01] [00:10:53] Status x11/kde-workspace-kde4 |
kde-workspace-kde4-4.11.22_26: package
[00:11:46] [01] [00:10:57] Finished x11/kde-workspace-kde4 |
kde-workspace-kde4-4.11.22_26: Failed: package
[00:11:46] Stopping 1 builders
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October 3: Day of German Unity? No! Day of taking over the GDR.
3. Oktober: Tag der Deutschen Einheit? Nein! DDR-Anschlusstag.
signature.asc
Description: PGP signature
Re: debugging a run of poudriere-bulk
I added the following lines to /usr/local/share/poudriere/bulk.sh to get the env vars into the environment of pkg(8): export DEBUG_LEVEL=4 export DEBUG_SCRIPTS=TRUE export DEVELOPER_MODE=TRUE export PKG_CREATE_VERBOSE=TRUE With these the port builds fine: # tail -f /usr/local/poudriere/data/logs/bulk/freebsd-r338641-ports-20180920/2018-10-03_22h03m46s/logs/kde-workspace-kde4-4.11.22_26.log ... DBG(1)[94432]> PkgConfig: loading repositories in /etc/pkg/ DBG(1)[94432]> PKgConfig: loading /etc/pkg//FreeBSD.conf DBG(1)[94432]> PkgConfig: parsing key 'FreeBSD' DBG(1)[94432]> PkgConfig: parsing repository object FreeBSD DBG(1)[94432]> PkgConfig: loading repositories in /usr/local/etc/pkg/repos/ DBG(1)[94432]> Creating package from stage directory: '/wrkdirs/usr/ports/x11/kde-workspace-kde4/wor k/stage' DBG(1)[94432]> Parsing manifest from '+MANIFEST' DBG(3)[94432]> Manifest: found key: 'name' ... DBG(2)[94432]> Packing file '/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/wallpapers/stripes.png.desktop' DBG(2)[94432]> Packing file '/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/share/xsessions/kde4.desktop' DBG(2)[94432]> Packing file '/wrkdirs/usr/ports/x11/kde-workspace-kde4/work/stage/usr/local/etc/rc.d/kdm4' packing files [2126]... done packing directories [0]: . done === =>> Cleaning up wrkdir ===> Cleaning for kde-workspace-kde4-4.11.22_26 build of x11/kde-workspace-kde4 | kde-workspace-kde4-4.11.22_26 ended at Wed Oct 3 22:15:54 CEST 2018 build time: 00:11:21 i.e. the pkg-static does not crash. And now? matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October 3: Day of German Unity? No! Day of taking over the GDR. 3. Oktober: Tag der Deutschen Einheit? Nein! DDR-Anschlusstag. signature.asc Description: PGP signature
Re: debugging a run of poudriere-bulk
El día miércoles, octubre 03, 2018 a las 11:06:55p. m. +0200, Tobias C. Berner
escribió:
> Moin moin
>
> Unfortunately it is very hard to help here when not being able to reproduce
> the issue :/
> Have you tried wiping all the packages in poudriere's repo? -- i.e. -c --
> maybe you're pkg package is just hosed.
Tobias,
The problem *is* reproducible, even in the build clusters of freebsd.org
(see pkg-fallout messages). It is only (until now) not debug-able.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October 3: Day of German Unity? No! Day of taking over the GDR.
3. Oktober: Tag der Deutschen Einheit? Nein! DDR-Anschlusstag.
signature.asc
Description: PGP signature
Re: debugging a run of poudriere-bulk
El día Thursday, October 04, 2018 a las 01:14:55PM +0930, Shane Ambler escribió: > > How can I enter the jail interactively in the moment after the crash to > > rerun and > > debug pkg-static? > > Using > > poudriere testport -j -p -i -o > > will drop you into the jail after the build stops, you then rerun make > manually, check build logs... Logging out will then continue on and > clean up the jail. You can also use -I instead of -i and it leaves the > jail in place so you can manually connect to and stop the jail. > > Note that poudriere uses a clean jail with only deps listed for the > port, you can add extra BUILD_DEPENDS to get extra ports (gdb valgrind) > installed with the test build. Thanks! One should read man pages completely in advance and not only the part of 'poudriere bulk ...'. I did so and in nthis case the crash occurs *after* the package is complete: ... > Checking for pkg-plist issues (check-plist) ===> Parsing plist ===> Checking for items in STAGEDIR missing from pkg-plist ===> Checking for items in pkg-plist which are not in STAGEDIR ===> No pkg-plist issues found (check-plist) =>> Checking for staging violations... done === ===> Building package for kde-workspace-kde4-4.11.22_26 file sizes/checksums [2126]: .. done packing files [2126]: .. done packing directories [0]: . done === =>> Recording filesystem state for preinst... done === ===> Installing for kde-workspace-kde4-4.11.22_26 ===> Checking if kde-workspace-kde4 already installed ===> Registering installation for kde-workspace-kde4-4.11.22_26 Child process pid=75639 terminated abnormally: Segmentation faul *** Error code 139 Stop. make: stopped in /usr/ports/x11/kde-workspace-kde4 === [00:13:29] Installing packages [00:13:29] Installing run-depends for x11/kde-workspace-kde4 | kde-workspace-kde4-4.11.22_26 # ls -l /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz -rw-r--r-- 1 nobody wheel 18338720 Oct 4 14:02 /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz Poudriere installs the package 'pkg' into the jail to could make use of 'pkg-static' (and other tools). Maybe it would be an idea to create outside a special version of this package which have a special version of 'pkg-static' in this, for example a shellsript with the name pkg-static which is something like: #!/bin/sh echo $0 $* > /tmp/pkg-static-args.$$ truss -o /tmp/pkg-static.$$ /usr/local/sbin/pkgstatic.exec $* to get more information about the crash. Other ideas? matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. ___ 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: kdelibs-kde4 is marked as broken on FreeBSD 13.0: incompatible with base SSL ...
El día lunes, diciembre 24, 2018 a las 01:16:40p. m. +0100, Adriaan de Groot escribió: > On Monday, 24 December 2018 11:24:59 CET Jan Beich wrote: > > g...@unixarea.de writes: > > > I know that KDE4 will be removed from ports by the end of the year, > > > that's why I wanted to update my CURRENT and ports right now before > > > this. I now find that one of the fundamental ports (x11/kdelibs-kde4) is > > > marked as broken... > > > > > > Is there a fix for this (for example using SSL from ports and not from > > > base). The alternative would be reset my poudriere oven to a 19 of > > > September (my last build with KDE4). > > > > Try adding DEFAULT_VERSIONS+=ssl=openssl to make.conf(5) and commenting > > out BROKEN_FreeBSD_13 in kdelibs-kde4/Makefile. > > What Jan said will *probably* work. We (kde@) do not have the person-hours to > chase this. You'll want a ports tree from last week, since we've been > updating > KDE4-era ports to their current releases recently, if you're particularly > attached to the unmaintained stuff. > > [ade] Thanks to you both (Jan and Adriaan) for your help and your work in general! It's a pity that KDE4 is unmaintained (upstream and in FreeBSD) because it does fine for me and many others for many years. From time to time I have to use KDE5 at work on SUSE Linux workstations and it's rather strange to use this as a C(K)ommon Desktop Environment, to be honestly. That's why I see a lot of mails and PR, for example https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233182 expressing the same. Anyway, I will try to get it compiled based on your hint, and if not either return to a September version or switch to KDE5. Thanks again. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
unknown (doubled?) poudriere jail below /usr/obj/usr/local/...
Hello,
I've update on December 23 an amd64 system to r342378 and
created a new ZFS jail and ports within poudriere with:
# poudriere jail -c -j freebsd-r342378 -m svn+http -v head@r342378
# poudriere ports -c -p ports-20181223 -m svn -U svn://svn.freebsd.org/ports/
The relevant values from poudriere.conf are:
ZPOOL=poudriere
#NO_ZFS=yes
ZROOTFS=/poudriere
BASEFS=/usr/local/poudriere
POUDRIERE_DATA=${BASEFS}/data
Since then I compiled some 1800 ports with:
# poudriere bulk -f /usr/local/etc/poudriere-list -J 4 -j freebsd-r342378 -p
ports-20181223
All went fine.
While checking something, I now see the poudriere jail also below
/usr/obj/usr/local:
[root@jet ~]# ls -li /usr/local/poudriere/jails/
/usr/obj/usr/local/poudriere/jails/
/usr/local/poudriere/jails/:
total 3
4 drwxr-xr-x 17 root wheel 21 Mar 4 2017 freebsd-r314251
4 drwxr-xr-x 18 root wheel 22 Dec 23 21:30 freebsd-r342378
/usr/obj/usr/local/poudriere/jails/:
total 4
31300766 drwxrwxr-x 3 root wheel 512 Dec 23 19:22 freebsd-r342378
The mounts are:
[root@jet ~]# mount
/dev/da0p2 on / (ufs, local, journaled soft-updates)
devfs on /dev (devfs, local, multilabel)
poudriere on /poudriere (zfs, local, nfsv4acls)
poudriere/poudriere on /poudriere/poudriere (zfs, local, nfsv4acls)
poudriere/poudriere/jails on /poudriere/poudriere/jails (zfs, local, nfsv4acls)
poudriere/poudriere/ports on /poudriere/poudriere/ports (zfs, local, nfsv4acls)
poudriere/mydata on /usr/home/guru/zdata (zfs, local, nfsv4acls)
poudriere/mydata/r338641 on /usr/home/guru/zdata/r338641 (zfs, local, nfsv4acls)
poudriere/poudriere/jails/freebsd-r314251 on
/usr/local/poudriere/jails/freebsd-r314251 (zfs, local, noatime, nfsv4acls)
poudriere/poudriere/jails/freebsd-r342378 on
/usr/local/poudriere/jails/freebsd-r342378 (zfs, local, noatime, nfsv4acls)
poudriere/poudriere/ports/ports-20170304 on
/usr/local/poudriere/ports/ports-20170304 (zfs, local, noatime, nfsv4acls)
poudriere/poudriere/ports/ports-20181223 on
/usr/local/poudriere/ports/ports-20181223 (zfs, local, noatime, nfsv4acls)
What does this structure below '/usr/obj/usr/local/poudriere/jails/'
mean? Can I remove this?
Thanks for some light on this.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars,
Druschba
instead of Nazis, to live instead of to survive.
signature.asc
Description: PGP signature
Re: unknown (doubled?) poudriere jail below /usr/obj/usr/local/...
El día Wednesday, December 26, 2018 a las 09:49:20AM +0100, Matthias Apitz escribió: > > Hello, > > I've update on December 23 an amd64 system to r342378 and > created a new ZFS jail and ports within poudriere with: > > # poudriere jail -c -j freebsd-r342378 -m svn+http -v head@r342378 > # poudriere ports -c -p ports-20181223 -m svn -U svn://svn.freebsd.org/ports/ > > The relevant values from poudriere.conf are: > > I did (just for test) a 2nd jail creation as: # poudriere jail -c -j freebsd-r342378test -m svn+http -v head@r342378 this checks out the source tree to /usr/local/poudriere/jails/freebsd-r342378test/usr/src and compiles it to /usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr ... one can also see this in the run of the compiler, here an example: ... c++ -O2 -pipe -I/usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm -I/usr/local/poudriere/jails/freebsd-r342378test/usr/src/lib/clang/include -I/usr/local/poudriere/jails/freebsd-r342378test/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd13.0\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd13.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr/src/amd64.amd64/tmp\" -DLLVM_TARGET_ENABLE_X86 -DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser -DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter -DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler -DLLVM_NATIVE_TARGET=LLVMInitializeX86Target -DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo -DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.X86FoldTablesEmitter.o -MTX86FoldTablesEmitter.o -Qunused-arguments -I/usr/obj/usr/local/poudriere/jails/freebsd-r342378test/usr/src/amd64.amd64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions -c /usr/local/poudriere/jails/freebsd-r342378test/usr/src/contrib/llvm/utils/TableGen/X86FoldTablesEmitter.cpp -o X86FoldTablesEmitter.o ... Is this pollution of /usr/obj with the poudriere jail intention? And can this be removed later? For my original jail 'freebsd-r342378' I moved away '/usr/obj/usr/local' to '/local-UNKNOWN' and the jail is still working fine (compiled fice hours www/chromium). Please, poudriere folks help me to understand this? Is this new with some version (I have not found anything in /usr/ports/UPDATING or in the man page). It was not this way in version r314251 (in March 2017). Thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
r342378 fails sometimes on boot mounting root (error 2)
Hello, I've setup a new r342378 (December 23) for amd64 onto an external disk with this procedure: # grep da0 /var/log/messages ... Dec 28 14:20:01 c720-r314251 kernel: da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 Dec 28 14:20:01 c720-r314251 kernel: da0: Fixed Direct Access SPC-4 SCSI device Dec 28 14:20:01 c720-r314251 kernel: da0: Serial Number 575854314134383033483150 Dec 28 14:20:01 c720-r314251 kernel: da0: 400.000MB/s transfers Dec 28 14:20:01 c720-r314251 kernel: da0: 953837MB (1953458176 512 byte sectors) Dec 28 14:20:01 c720-r314251 kernel: da0: quirks=0x2 # gpart destroy -F da0 da0 destroyed # gpart create -s gpt da0 da0 created # gpart add -t freebsd-boot -s 512k -a4k -l extboot da0 da0p1 added # gpart bootcode -b /boot/pmbr -p /boot/gptboot -i1 da0 partcode written to da0p1 bootcode written to da0 # gpart add -t freebsd-ufs -l extrootfs -b 1m -s 256g da0 da0p2 added # gpart add -t freebsd-swap -l extswap -a 1m -s 2g da0 da0p3 added # gpart add -t freebsd-ufs -l extbackupfs -a 1m da0 da0p4 added # newfs -U /dev/gpt/extrootfs # newfs -U /dev/gpt/extbackupfs # gpart set -a active da0 active set on da0 # gpart show -l da0 =>40 1953458096 da0 GPT (931G) 4010241 extboot (512K) 1064 984 - free - (492K) 2048 5368709122 extrootfs (256G) 536872960 41943043 extswap (2.0G) 541067264 14123888644 extbackupfs (673G) 19534561282008 - free - (1.0M) # mount /dev/gpt/extrootfs /mnt # cd /usr/src # make installworld DESTDIR=/mnt # make installkernel DESTDIR=/mnt # make distrib-dirs DESTDIR=/mnt # make distribution DESTDIR=/mnt # cd ~guru/C720 # cp -p rc.conf /mnt/etc # cp -p c720.kbd/mnt/etc # cp -p sysctl.conf /mnt/etc # cp -p loader.conf /mnt/boot/ # cp -p device.hints/mnt/boot/ # cat > /mnt/etc/fstab
Re: r342378 fails sometimes on boot mounting root (error 2)
El día viernes, diciembre 28, 2018 a las 09:07:49a. m. -0700, Ian Lepore escribió: > Try setting vfs.mountroot.timeout= in loader.conf to a value long > enough to let the usb drive get probed reliably. The default is 3 > seconds, maybe a value like 5 or 10 would work better for you. > > -- Ian Thanks. I did so, but this does not help. When I does not work even after 20 secs it fails to mount. After a lot of boot attempts I have the following picture: 1. It always mounts fine when verbose message is selected. 2. It mounts fine when the line below about 'umass0:1:0: Attached to ... ' is printed, if it is not, the mount fails later after 20 secs waiting; here is a working boot: ... uhub1: 2 ports with 2 removable, self powered uhub0: 13 ports with 13 removable, self powered ugen0.2: at usbus0 ugen0.3: at usbus0 ugen0.4: at usbus0 umass0 on uhub0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x8000 umass0:1:0: Attached to scbus1 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ACS-2 ATA SATA 3.x device ada0: Serial Number C196530955 ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 1024bytes) ada0: Command Queueing enabled ada0: 244198MB (500118192 512 byte sectors) GEOM: new disk ada0 pass0 at ahcich0 bus 0 scbus0 target 0 lun 0 pass0: ACS-2 ATA SATA 3.x device pass0: Serial Number C196530955 pass0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 1024bytes) pass0: Command Queueing enabled pass1 at umass-sim0 bus 0 scbus1 target 0 lun 0 pass1: Fixed Direct Access SPC-4 SCSI device pass1: Serial Number 575854314134383033483150 pass1: 40.000MB/s transfers pass2 at umass-sim0 bus 0 scbus1 target 0 lun 1 da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 575854314134383033483150 da0: 40.000MB/s transfers da0: 953837MB (1953458176 512 byte sectors) da0: quirks=0x2 pass2: Fixed Enclosure Services SPC-4 SCSI device pass2: Serial Number 575854314134383033483150 pass2: 40.000MB/s transfers ses0 at umass-sim0 bus 0 scbus1 target 0 lun 1 ses0: Fixed Enclosure Services SPC-4 SCSI device ses0: Serial Number 575854314134383033483150 ses0: 40.000MB/s transfers ses0: SCSI-3 ENC Device GEOM: new disk da0 da0: Delete methods: WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/gpt/extrootfs [rw,noatime]... atrtc0: providing initial system time start_init: trying /sbin/init ... -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ 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"
stop in make installworld: ld-elf.so.1: symbol lstat1@FBSD_1.5 not found
Hello,
I'm updating the usual way a system from r314251 the the actual CURRENT.
The 'make installworld' failes in single user mode with:
ld-elf.so.1: /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin/rm:
Undefined symbol lstat1@FBSD_1.5
What can I do?
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ ☎
+49-176-38902045
___
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: stop in make installworld: ld-elf.so.1: symbol lstat1@FBSD_1.5 not found
On Mon, 31 Dec 2018 12:27:55 +0100, Matthias Apitz wrote: > > Hello, > > I'm updating the usual way a system from r314251 to tje actual CURRENT > r342378. > The 'make installworld' failes in single user mode with: > > ld-elf.so.1: /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin/rm: > Undefined symbol lstat1@FBSD_1.5 > > What can I do? As I had no other idead, I run the 'make installworld' again, now with success. What does this mean? matthias -- Sent using Dekko from my Ubuntu device http://www.unixarea.de/+49 176 38902045 ___ 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: stop in make installworld: ld-elf.so.1: symbol lstat1@FBSD_1.5 not found
On Mon, 31 Dec 2018 13:12:15 +, Dimitry Andric wrote: > On 31 Dec 2018, at 13:08, Matthias Apitz wrote: >> >> On Mon, 31 Dec 2018 12:27:55 +0100, Matthias Apitz wrote: >>> >>> Hello, >>> >>> I'm updating the usual way a system from r314251 to tje >>> actual CURRENT r342378. >>> The 'make installworld' failes in single user mode with: >>> >>> ld-elf.so.1: /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin/rm: >>> Undefined symbol lstat1@FBSD_1.5 >>> >>> What can I do? >> >> As I had no other idead, I run the 'make installworld' again, >> now with success. >> >> What does this mean? > > I think what may have happened was the following. > > The "legacy" rm which failed was likely a symlink to /bin/rm, like so: > > $ ls -l /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin/rm > lrwxr-xr-x 1 dim dim 7 2018-12-29 16:22:12 > /usr/obj/usr.old/src/amd64.amd64/tmp/legacy/usr/bin/rm@ -> > /bin/rm > > For some reason, /bin/rm may have been overwritten before your > /lib/libc.so.7, which caused the "Undefined symbol" error from > ld-elf.so.1. > > Alternatively, installing /lib/libc.so.7 may have failed without the > Makefile noticing it, after which the first /bin/rm would show that same > error. > > When you re-ran "make installworld", the installation of /lib/libc.so.7 > likely succeeded, and after that the symlinked commands in > /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin which used new symbols > started to work. > I still have two identical updates scheduled, based on extactly the same src and precompiled obj tree. I will investigate the next and file a PR. matthias -- Sent using Dekko from my Ubuntu device http://www.unixarea.de/+49 176 38902045 ___ 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"
r342378: usbconfig takes 3-5 minutes to read the bus
I updated my amd64 laptop Acer C720 from r314251 to r342378. The OpenPGP Card HID Global OMNIKEY 6121 was working in r314251 nicely and after withdraw and re-insert GnuPG was just asking for the PIN again and access to the ciphered material or signing keys was fine. Now with r342378, it works only after boot but not after withdraw/re-insert anymore. To separate the problem from GnuPG and it's software stack, I have here some small tests with usbconfig(8). First usbconfig reads fine the bus, but then it takes 3-5 minutes to get any results, see below. Please, what can I check or enable to get additional logs for the problem. Thanks # uname -a FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC amd64 # usbconfig list ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) # usbconfig -d ugen0.4 list ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) # usbconfig -d ugen0.4 dump_device_desc ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x076b idProduct = 0x6632 bcdDevice = 0x0103 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x bNumConfigurations = 0x0001 From now it takes 3++ minutes to get the information from USB: # date ; usbconfig -d ugen0.4 dump_device_desc ; date Tue Jan 1 11:51:55 CET 2019 ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x076b idProduct = 0x6632 bcdDevice = 0x0103 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x bNumConfigurations = 0x0001 Tue Jan 1 11:54:59 CET 2019 # date ; usbconfig -d ugen0.4 dump_device_desc ; date Tue Jan 1 14:30:19 CET 2019 ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x076b idProduct = 0x6632 bcdDevice = 0x0103 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x bNumConfigurations = 0x0001 Tue Jan 1 14:34:05 CET 2019 # tail -f /var/log/messages ... Jan 1 14:34:30 c720-r342378 kernel: ugen0.4: at usbus0 (disconnected) Jan 1 14:34:36 c720-r342378 kernel: ugen0.4: at usbus0 # date ; usbconfig -d ugen0.4 dump_device_desc ; date Tue Jan 1 14:34:46 CET 2019 ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x076b idProduct = 0x6632 bcdDevice = 0x0103 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x bNumConfigurations = 0x0001 Tue Jan 1 14:39:13 CET 2019 -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. ___ 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: ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ"
El día viernes, diciembre 28, 2018 a las 12:55:32p. m. -0800, Cy Schubert escribió: > In message il.com> > , Antoine Brodin writes: > > On Fri, Dec 28, 2018 at 8:39 PM Graham Perrin > > wrote: > > > > > > On Fri, 28 Dec 2018 at 16:31, Emiel Kollof > > > wrot > > e: > > > > > > > Confirmed with Chromium on my CURRENT box: > > > > > > ⦠> > > > > > Thanks folks. Should I report it as a bug with devel/glib20? > > > > Hi, > > > > I think it's a regression in the toolchain (the problem doesn't occur > > on 11.2 or 12.0), so it should be reported to freebsd-toolchain@ > > No issue here however I rebuilt glib on Dec 21. I see the same with www/chromium on r342378 and ports, both from Dec 23. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
Re: r342378: usbconfig takes 3-5 minutes to read the bus
El día miércoles, enero 02, 2019 a las 09:44:06a. m. +0100, Hans Petter Selasky escribió: > On 1/1/19 2:51 PM, Matthias Apitz wrote: > > Now with r342378, it works only after boot but not after withdraw/re-insert > > anymore. To separate the problem from GnuPG and it's software stack, I have > > here some > > small tests with usbconfig(8). First usbconfig reads fine the bus, but then > > it takes 3-5 minutes to get any results, see below. > > Did you update the user-space libusb aswell? I did a complete 'make installworld' and they look updated: $ ls -l /usr/lib/libusb* -r--r--r-- 1 root wheel 573256 31 dic. 12:19 /usr/lib/libusb_p.a -r--r--r-- 1 root wheel 541506 31 dic. 12:19 /usr/lib/libusb.a lrwxr-xr-x 1 root wheel 11 31 dic. 12:33 /usr/lib/libusb.so -> libusb.so.3 -r--r--r-- 1 root wheel 98016 31 dic. 12:33 /usr/lib/libusb.so.3 -r--r--r-- 1 root wheel 73910 31 dic. 12:19 /usr/lib/libusbhid_p.a -r--r--r-- 1 root wheel 71390 31 dic. 12:19 /usr/lib/libusbhid.a lrwxr-xr-x 1 root wheel 14 31 dic. 12:33 /usr/lib/libusbhid.so -> libusbhid.so.4 -r--r--r-- 1 root wheel 23720 31 dic. 12:33 /usr/lib/libusbhid.so.4 At boot time a process is launched by devd(8) which reads the OpenPGP card and this works fine and has the device open: $ ps ax | grep pcs 501 v0- S 0:00,22 /usr/local/sbin/pcscd --debug --foreground # lsof -p 501 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME pcscd 501 root cwd VDIR 0,113 10242 / pcscd 501 root rtd VDIR 0,113 10242 / pcscd 501 root txt VREG 0,113 121992 15279826 /usr/local/sbin/pcscd pcscd 501 root txt VREG 0,113 151560 29294355 /libexec/ld-elf.so.1 pcscd 501 root txt VREG 0,11398016 29294906 /usr/lib/libusb.so.3 pcscd 501 root txt VREG 0,11327640 29294864 /usr/lib/librt.so.1 pcscd 501 root txt VREG 0,113 135712 29293769 /lib/libthr.so.3 pcscd 501 root txt VREG 0,113 2063072 29294412 /lib/libc.so.7 pcscd 501 root txt VREG 0,113 135192 1905 /usr/local/lib/pcsc/drivers/ifd-ccid.bundle/Contents/FreeBSD/libccid.so pcscd 501 root0r VCHR 0,43 0t0 43 /dev/null pcscd 501 root1u VREG 0,113 3568882411580 / (/dev/ada0p2) pcscd 501 root2u VREG 0,113 3568882411580 / (/dev/ada0p2) pcscd 501 root3u VREG 0,113 3568882411580 / (/dev/ada0p2) pcscd 501 root4u PIPE 0xf800162fd8e816384 ->0xf800162fda50 pcscd 501 root5u PIPE 0xf800162fda500 ->0xf800162fd8e8 pcscd 501 root6u unix 0xf800164036d0 0t0 /var/run/pcscd/pcscd.comm pcscd 501 root7u unix 0xf80016feaa38 0t0 /var/run/pcscd/pcscd.comm pcscd 501 root9u PIPE 0xf800162fd2f816384 ->0xf800162fd460, cnt=2, in=2 pcscd 501 root 10u PIPE 0xf800162fd4600 ->0xf800162fd2f8 pcscd 501 root 11u PIPE 0xf800162f28e816384 ->0xf800162f2a50 pcscd 501 root 12u PIPE 0xf800162f2a500 ->0xf800162f28e8 pcscd 501 root 13u VCHR 0,87 0t0 87 /dev/usb/0.4.0 pcscd 501 root 14u VCHR 0,87 0t0 87 /dev/usb/0.4.0 $ gpg2 --card-status Reader ...: Identiv uTrust 3512 SAM slot Token (55511725600891) 00 00 Application ID ...: D2760001240102010005532B Version ..: 2.1 Manufacturer .: ZeitControl Serial number : 532B Name of cardholder: Matthias Apitz ... When I withdraw the OpenPGP card devd(8) hooks kill that proc and restarts a new one on card insert. But this new proc hangs. The same happens when I disable the devd(8) start of this proc and start the same proc from a shell (for debugging). This hangs too. Looks like something makes the USB stack broken after the point where devd(8) can launch fine the first proc of pcscd. > Any error messages in dmesg? Nothing. Only on boot it sees the card: Jan 2 11:25:39 c720-r342378 kernel: ugen0.1: <0x8086 XHCI root HUB> at usbus0 Jan 2 11:25:39 c720-r342378 kernel: ugen1.1: at usbus1 Jan 2 11:25:39 c720-r342378 kernel: ugen1.2: at usbus1 Jan 2 11:25:39 c720-r342378 kernel: ugen0.2: at usbus0 Jan 2 11:25:39 c720-r342378 kernel: ugen0.3: at usbus0 Jan 2 11:25:39 c720-r342378 kernel: ugen0.4: at usbus0 matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
Re: r342378: usbconfig takes 3-5 minutes to read the bus
El día miércoles, enero 02, 2019 a las 12:37:37p. m. +0100, Hans Petter Selasky escribió: > > Nothing. Only on boot it sees the card: > > And you are using the latest version of pcsd ? Yes. Compiled with all ports from December 23. > > > Jan 2 11:25:39 c720-r342378 kernel: ugen0.1: <0x8086 XHCI root HUB> at > > usbus0 > > Jan 2 11:25:39 c720-r342378 kernel: ugen1.1: at > > usbus1 > > Jan 2 11:25:39 c720-r342378 kernel: ugen1.2: > 0x8000> at usbus1 > > Jan 2 11:25:39 c720-r342378 kernel: ugen0.2: at > > usbus0 > > Jan 2 11:25:39 c720-r342378 kernel: ugen0.3: > 0xe056> at usbus0 > > Jan 2 11:25:39 c720-r342378 kernel: ugen0.4: > Token> at usbus0 > > There has been some changes in libusb recently . After card removal and insert devd(8) starts a new pcsd: Jan 2 16:39:11 c720-r342378 kernel: ugen0.4: at usbus0 Jan 2 16:39:11 c720-r342378 root[13636]: CCID uTrust, type: ATTACH, system: USB, subsystem: INTERFACE Jan 2 16:39:11 c720-r342378 root[13637]: /usr/local/sbin/pcscd --debug --foreground This sits hanging on /dev/usb/1.1.0: # lsof -p 13639 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME pcscd 13639 root cwd VDIR 0,113 10242 / pcscd 13639 root rtd VDIR 0,113 10242 / pcscd 13639 root txt VREG 0,113 121992 15279826 /usr/local/sbin/pcscd pcscd 13639 root txt VREG 0,113 151560 29294355 /libexec/ld-elf.so.1 pcscd 13639 root txt VREG 0,11398016 29294906 /usr/lib/libusb.so.3 pcscd 13639 root txt VREG 0,11327640 29294864 /usr/lib/librt.so.1 pcscd 13639 root txt VREG 0,113 135712 29293769 /lib/libthr.so.3 pcscd 13639 root txt VREG 0,113 2063072 29294412 /lib/libc.so.7 pcscd 13639 root0r VCHR 0,43 0t0 43 /dev/null pcscd 13639 root1u VCHR 0,43 0t0 43 /dev/null pcscd 13639 root2u VCHR 0,43 0t0 43 /dev/null pcscd 13639 root3u unix 0xf800609ff6d0 0t0 ->0xf800163fa368 pcscd 13639 root4u PIPE 0xf8004f13c2f816384 ->0xf8004f13c460 pcscd 13639 root5u PIPE 0xf8004f13c4600 ->0xf8004f13c2f8 pcscd 13639 root6u unix 0xf80072b03a38 0t0 /var/run/pcscd/pcscd.comm pcscd 13639 root7u PIPE 0xf8004e5422f816384 ->0xf8004e542460 pcscd 13639 root8u PIPE 0xf8004e5424600 ->0xf8004e5422f8 pcscd 13639 root9u PIPE 0xf8004e50900016384 ->0xf8004e509168 pcscd 13639 root 10u PIPE 0xf8004e5091680 ->0xf8004e509000 pcscd 13639 root 11u VCHR 0,52 0t0 52 /dev/usb/1.1.0 pcscd 13639 root 12u VCHR 0,52 0t0 52 /dev/usb/1.1.0 (note: the older working proc had open /dev/usb/0.4.0) > What does "procstat -ak" output. Does it hang on any "usb" functions? # ps ax | grep pcs 13639 - I 0:00,01 /usr/local/sbin/pcscd --debug --foreground 13967 4 S+ 0:00,01 grep pcs # procstat -k 13639 PIDTID COMMTDNAME KSTACK 13639 100287 pcscd - mi_switch sleepq_switch sleepq_catch_signals sleepq_wait_sig _sleep pipe_read dofileread kern_readv sys_read amd64_syscall fast_syscall_common 13639 100821 pcscd - mi_switch sleepq_switch sleepq_catch_signals sleepq_wait_sig _sleep pipe_read dofileread kern_readv sys_read amd64_syscall fast_syscall_common 13639 100822 pcscd - mi_switch sleepq_switch sleepq_catch_signals sleepq_wait_sig _sx_xlock_hard _sx_xlock usbd_enum_lock_sig usb_ref_device usb_open devfs_open VOP_OPEN_APV vn_open_vnode vn_open_cred kern_openat amd64_syscall fast_syscall_common matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. ___ 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"
uname -a output without svn revision number
Hello,
I've compiled CURRENT from svn and this gave me as 'uname -a' output:
FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC amd64
Now I've had do modify a source file (to nail down some problem) and the
revision number went away from the output; it now says:
FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC amd64
Why is this? I've read in UPDATING that:
...
20180913:
Reproducible build mode is now on by default, in preparation for
FreeBSD 12.0. This eliminates build metadata such as the user,
host, and time from the kernel (and uname), unless the working tree
corresponds to a modified checkout from a version control system.
The previous behavior can be obtained by setting the /etc/src.conf
knob WITHOUT_REPRODUCIBLE_BUILD.
...
But this does not explain why now the SVN revision number went away.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars,
Druschba
instead of Nazis, to live instead of to survive.
signature.asc
Description: PGP signature
Re: uname -a output without svn revision number
El día viernes, enero 04, 2019 a las 07:52:40a. m. +0100, Dimitry Andric escribió: > On 4 Jan 2019, at 06:52, Matthias Apitz wrote: > > > > I've compiled CURRENT from svn and this gave me as 'uname -a' output: > > > > FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT r342378 GENERIC > > amd64 > > > > Now I've had do modify a source file (to nail down some problem) and the > > revision number went away from the output; it now says: > > > > FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC amd64 > > > > Why is this? I've read in UPDATING that: > > > > ... > > > > But this does not explain why now the SVN revision number went away. > > For me, it doesn't go away, but shows an "M" suffix, instead. In > /usr/obj/usr/src/sys/GENERIC/vers.c it shows: > > #define VERSTR "FreeBSD 13.0-CURRENT r342593M \n" > > What is the output of sh /usr/src/sys/conf/newvers.sh for you? $ ls -l /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c -rw-r--r-- 1 root wheel 1919 3 ene. 11:59 /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c $ tail -12 /usr/obj/usr/src/amd64.amd64/sys/GENERIC/vers.c #define SCCSSTR "@(#)FreeBSD 13.0-CURRENT GENERIC" #define VERSTR "FreeBSD 13.0-CURRENT GENERIC\n" #define RELSTR "13.0-CURRENT" char sccs[sizeof(SCCSSTR) > 128 ? sizeof(SCCSSTR) : 128] = SCCSSTR; char version[sizeof(VERSTR) > 256 ? sizeof(VERSTR) : 256] = VERSTR; char compiler_version[] = "FreeBSD clang version 7.0.1 (tags/RELEASE_701/final 349250) (based on LLVM 7.0.1)"; char ostype[] = "FreeBSD"; char osrelease[sizeof(RELSTR) > 32 ? sizeof(RELSTR) : 32] = RELSTR; int osreldate = 135; char kern_ident[] = "GENERIC"; $ sh /usr/src/sys/conf/newvers.sh I did around 11:50 am (i.e. the mod time of vers.c matches) a 'make buildkernel NO_CLEAN=yes' matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
Re: uname -a output without svn revision number
El día viernes, enero 04, 2019 a las 09:30:05a. m. -0500, Ed Maste escribió: > It looks like some aspects of this have been broken since r308789. Do > you happen to have a git or hg tree higher up in the directory > hierarchy? For example, ~/.git, and ~/src/freebsd/...? I'll have a fix > for that case soon. No, nothing. > > If that's not the case, please run (from the src toplevel dir) > > sh -x sys/conf/newvers.sh >newvers.log 2>&1 I looked into the script sys/conf/newvers.sh and I think I understand now the problem. I compiled /usr/src on some other faster server and moved /usr/src and /usr/obj to my netbook as tar-archive to update kernel and userland there. To save space on the netbook I excluded /usr/src/.svn which is causing now the absence of the revision number. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive. signature.asc Description: PGP signature
Re: CFT: FreeBSD Package Base
Why this thread has to go to all these lists? I receive any mail 5 times! matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub N € I N zur EU! "Gegen das EU-Europa der Banken, Konzerne und Kriegstreiber. Für ein soziales und friedliches Europa der Völker." DKP signature.asc Description: PGP signature
Re: FreeBSD and Coreboot
El día Monday, May 27, 2019 a las 11:13:46AM -0400, Eric McCorkle escribió:
> Hello everyone,
>
> I'm through enough of my job change that I can start working on FreeBSD
> again. One thing I've had on my list to examine is using FreeBSD with
> coreboot, so I wanted to put out a call for anyone who has done work on
> this, or knows anything about it.
Hello Eric,
I don't know if this is something which has to do with your project.
Since 2015 I use an Acer C720 Chromebook with FreeBSD (CURRENT) this has
AFAIK coreboot with SeaBIOS and works just fine.
Just to let you know.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!
___
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"
building x11-wm/plasma5-kwin w/ poudriere results in out of swap space
Hello, I'm build the latest port svn checkout (June 10) on r342378 with poudriere and (after isolating it) have the problem that building x11-wm/plasma5-kwin runs reproducible out of swap during 'configure' phase: [00:00:49] Cleaning the build queue [00:00:49] Sanity checking build queue [00:00:49] Processing PRIORITY_BOOST [00:00:50] Balancing pool [00:00:50] Recording filesystem state for prepkg... done [00:00:52] Building 1 packages using 1 builders [00:00:52] Starting/Cloning builders [00:00:54] Hit CTRL+t at any time to see build progress and stats [00:00:54] [01] [00:00:00] Building x11-wm/plasma5-kwin | plasma5-kwin-5.15.5 load: 0.95 cmd: sh 19376 [piperd] 67.68r 0.00u 0.00s 0% 3932k [freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s] [parallel_build:] Queued: 1 Built: 0 Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 1 Time: 00:01:40 [01]: x11-wm/plasma5-kwin | plasma5-kwin-5.15.5 build-depends (00:01:06 / 00:01:08) [00:02:02] Logs: /usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s load: 0.52 cmd: wc 26535 [piperd] 0.10r 0.00u 0.00s 0% 2656k [freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s] [parallel_build:] Queued: 1 Built: 0 Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 1 Time: 00:03:27 [01]: x11-wm/plasma5-kwin | plasma5-kwin-5.15.5 configure (00:01:17 / 00:02:55) [00:03:49] Logs: /usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s ^C[00:04:13] Error: Signal SIGINT caught, cleaning up and exiting Is this a known issue? Or should I investigate deeper which process it is? matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub May, 9: Спаси́бо освободители! Thank you very much, Russian liberators! - End forwarded message - -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub May, 9: Спаси́бо освободители! Thank you very much, Russian liberators! ___ 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: building x11-wm/plasma5-kwin w/ poudriere results in out of swap space
El día Thursday, June 13, 2019 a las 04:38:25PM +0800, Martin Wilke escribió: > On 2019-06-11 14:59, Matthias Apitz wrote: > >Hello, > > > >I'm build the latest port svn checkout (June 10) on r342378 with > >poudriere and (after isolating it) have the problem that building > >x11-wm/plasma5-kwin runs reproducible out of swap during 'configure' > >phase: > > > >[00:00:49] Cleaning the build queue > >[00:00:49] Sanity checking build queue > >[00:00:49] Processing PRIORITY_BOOST > >[00:00:50] Balancing pool > >[00:00:50] Recording filesystem state for prepkg... done > >[00:00:52] Building 1 packages using 1 builders > >[00:00:52] Starting/Cloning builders > >[00:00:54] Hit CTRL+t at any time to see build progress and stats > >[00:00:54] [01] [00:00:00] Building x11-wm/plasma5-kwin | > >plasma5-kwin-5.15.5 > >load: 0.95 cmd: sh 19376 [piperd] 67.68r 0.00u 0.00s 0% 3932k > >[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s] > >[parallel_build:] Queued: 1 Built: 0 Failed: 0 Skipped: 0 Ignored: > >0 Tobuild: 1 Time: 00:01:40 > > [01]: x11-wm/plasma5-kwin | plasma5-kwin-5.15.5 > >build-depends (00:01:06 / 00:01:08) > >[00:02:02] Logs: > >/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s > >load: 0.52 cmd: wc 26535 [piperd] 0.10r 0.00u 0.00s 0% 2656k > >[freebsd-r342378-ports-20190610] [2019-06-11_07h49m10s] > >[parallel_build:] Queued: 1 Built: 0 Failed: 0 Skipped: 0 Ignored: > >0 Tobuild: 1 Time: 00:03:27 > > [01]: x11-wm/plasma5-kwin | plasma5-kwin-5.15.5 configure > > (00:01:17 / 00:02:55) > >[00:03:49] Logs: > >/usr/local/poudriere/data/logs/bulk/freebsd-r342378-ports-20190610/2019-06-11_07h49m10s > >^C[00:04:13] Error: Signal SIGINT caught, cleaning up and exiting > > > >Is this a known issue? Or should I investigate deeper which process it > >is? > > This problem is not only for plasma5 its random happened since import of > clang8. I have not found any real solution for it. Hello Martin, Thanks for replying. The issue is not randomly, but affects all ports using a QML tool 'qmlplugindump' which allocates 12 GByte memory. It is this bug issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232736 I attached yesterday a poudriere log file for the port misc/kf5-purpose which also shows the same problem with 'qmlplugindump'. The poudriere log also says, that clang7 is used: ... === ===> Configuring for kf5-purpose-5.58.0 ===> Performing out-of-source build /bin/mkdir -p /wrkdirs/usr/ports/misc/kf5-purpose/work/.build -- The C compiler identification is Clang 7.0.1 -- The CXX compiler identification is Clang 7.0.1 -- Check for working C compiler: /usr/bin/clang -- Check for working C compiler: /usr/bin/clang -- works ... matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub May, 9: Спаси́бо освободители! Thank you very much, Russian liberators! ___ 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"
signal 11 for 'conftest' && poudriere jails
While running poudriere jails on a very recent CURRENT:
FreeBSD jet 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r349041: Sat Jun 15 07:45:13
CEST 2019 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
I see messages about signal 11 for 'conftest'. The uid 65534 (nobody)
let me think in poudriere, because there is nothing else running on this
box:
Jun 16 19:31:46 jet kernel: pid 55572 (conftest), jid 23, uid 65534: exited on
signal 11 (core dumped)
Jun 16 19:37:25 jet su[98388]: guru to root on /dev/pts/2
Jun 16 20:01:32 jet kernel: pid 26452 (conftest), jid 25, uid 65534: exited on
signal 11 (core dumped)
Jun 16 20:02:26 jet kernel: pid 54189 (conftest), jid 25, uid 65534: exited on
signal 11 (core dumped)
Jun 16 20:14:09 jet kernel: pid 86215 (conftest), jid 23, uid 65534: exited on
signal 11 (core dumped)
Jun 16 20:31:06 jet ntpdate[79734]: step time server 130.149.17.21 offset
0.309740 sec
Jun 16 20:38:39 jet kernel: pid 61044 (conftest), jid 25, uid 65534: exited on
signal 11 (core dumped)
Jun 16 20:45:29 jet kernel: pid 24274 (conftest), jid 31, uid 65534: exited on
signal 11 (core dumped)
Jun 16 21:31:06 jet ntpdate[99262]: step time server 130.149.17.21 offset
0.309141 sec
Jun 16 22:31:06 jet ntpdate[27064]: step time server 130.149.17.21 offset
0.309090 sec
Jun 16 23:31:06 jet ntpdate[1088]: step time server 130.149.17.21 offset
0.309793 sec
Jun 16 23:51:38 jet kernel: pid 10847 (java), jid 29, uid 65534, was killed:
out of swap space
Jun 17 00:31:06 jet ntpdate[6936]: step time server 130.149.17.21 offset
0.308939 sec
Jun 17 00:32:58 jet su[10397]: guru to root on /dev/pts/4
Jun 17 00:38:22 jet su[28548]: guru to root on /dev/pts/2
Jun 17 01:31:06 jet ntpdate[39553]: step time server 130.149.17.21 offset
0.309018 sec
Jun 17 01:41:23 jet kernel: pid 81104 (conftest), jid 26, uid 65534: exited on
signal 11 (core dumped)
Jun 17 02:17:29 jet kernel: pid 9625 (conftest), jid 29, uid 65534: exited on
signal 11 (core dumped)
Jun 17 02:21:56 jet kernel: pid 36351 (conftest), jid 29, uid 65534: exited on
signal 11 (core dumped)
What does this mean? What is 'conftest' at all?
matthias
...
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!
signature.asc
Description: PGP signature
sh.core in HOME of the user on system shutdown
Hello, I run 11-CURRENT r269739 on my i386 netbook. After (clean) shutdown I always have a core file 'sh.core' in the (only) logged in users HOME; the backtrace is ofc unuseable: (gdb) bt #0 0x282152f8 in fwrite () from /lib/libc.so.7 #1 0x280978db in el_gets () from /lib/libedit.so.7 #2 0x28099746 in el_gets () from /lib/libedit.so.7 #3 0x080536a1 in ?? () #4 0x2880d300 in ?? () #5 0x08066ac8 in _CurrentRuneLocale () #6 0x53f564a4 in ?? () #7 0x in ?? () Is it a known issue or is it worth to compile the libs with -g? Thx matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: printing text file with LPD - non-printable characters
El día Sunday, October 05, 2014 a las 10:41:43AM -0700, Beeblebrox escribió:
> I have two LPD errors
> 1. I see two characters being replaced by strings on the hard copy (the {â}
> below is an {a^}). This happens on the first page and not on following
> pages.
> instead of " I get: â\200\234 (235 for trailing ")
> instead of ' I get: â\200\231
> 2. All non-english characters get garbled, on all pages. These are
> characters like ç, ö, etc.
>
> With these two seemingly separate errors, I can't figure out whether this is
> an lpr or enscript error.
First of all check, what encoding has your text file, UTF-8 or ISO or
...?
Then run the file through the filter
$ /usr/local/bin/enscript -o - < file > out
and check the resulting file 'out'.
I do not know enscript, but guess that it should produce Postscript from
your input file.
I moved the thread by setting Reply-To: to the normal freebsd-question@
list;
matthias
--
Matthias Apitz | /"\ ASCII Ribbon Campaign:
E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | X- No proprietary attachments
phone: +49-170-4527211 | / \ - Respect for open standards
| en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: printing text file with LPD - non-printable characters
El día Tuesday, October 14, 2014 a las 01:19:42AM -0700, Beeblebrox escribió: > Enscript does not support UTF-8 formatted text files, so it's not usable in > this case. > > One solution, "is to use paps, instead of Enscript, for converting UTF-8 > encoded text to PostScript." > http://www.linuxfromscratch.org/blfs/view/svn/pst/enscript.html > > ... We are using in production environments CUPS in the version 1.4.3; this has a component 'texttops' which supports UTF-8 encoded text (only) and prints UTF-8 nicely on the fly. We have a special enhancement of the used fonts to support most EU languages. HIH matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: printing text file with LPD - non-printable characters
El día Tuesday, October 14, 2014 a las 02:26:37AM -0700, Beeblebrox escribió: > > We are using in production environments CUPS in the version 1.4.3; > > this has a component 'texttops' which supports UTF-8 encoded text > > (only) and prints UTF-8 nicely on the fly. > > Thanks for the input. > Unfortunately, CUPS has been broken for me since May/14. > (http://freebsd.1045724.n5.nabble.com/print-cups-base-web-interface-broken-amp-unable-to-print-td5918098.html#a5922974) > > Installed CUPS components: > cups-base-1.7.3_1, cups-client-1.7.3_2, cups-image-1.7.3_1, cups-pdf-2.6.1_1, > cups-pstoraster-8.15.4_8, gutenprint-cups-5.2.10 This is one of the reasons we stick with 1.4.3. matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: printing text file with LPD - non-printable characters
El día Tuesday, October 14, 2014 a las 03:07:10AM -0700, Beeblebrox escribió: > @Matthias: I'm not '@Matthias', but Matthias, and I think, the @ sign is normaly used to express user@host or @domain; > > This is one of the reasons we stick with 1.4.3. > > How? Did you create a self-maintained port for it? > How did you overcome the problem of CUPS-dependent ports pulling in 1.7.3 in > poudriere? I compile it directly from source, also on non-FreeBSD hosts (Linux and SPARC) and ship it to our customers. matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD && TCP stealth
Hello, Is there any work started or in progress to implement TCP stealth in our kernel as proposed to IETF in https://datatracker.ietf.org/doc/draft-kirsch-ietf-tcp-stealth/ The idea is that the client put some magic value in the ISN of the first SYN pkg which is derived from a secret the client and the server share. The server can check the ISN and decide if it will answer the SYN pkg or do a RST, for example. Vy 73 matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD && TCP stealth
El día Monday, October 20, 2014 a las 09:25:28AM +0200, Matthias Apitz escribió: > > Hello, > > Is there any work started or in progress to implement TCP stealth in our > kernel as proposed to IETF in > > https://datatracker.ietf.org/doc/draft-kirsch-ietf-tcp-stealth/ > > The idea is that the client put some magic value in the ISN of the first > SYN pkg which is derived from a secret the client and the server share. > The server can check the ISN and decide if it will answer the SYN pkg or > do a RST, for example. For Linux wip see also: https://gnunet.org/knock matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
makefs && gpart (...)
Hello,
I have a small question and a small request re/ makefs && gpart:
There is a script src/release/i386/make-memstick.sh to create an image
from a full directory tree; the tree is result of
make installworld DESTDIR=/tree
make installkernel DESTDIR=/tree
the script mainly does:
...
makefs -B little -o label=FreeBSD_Install ${2} ${1}
if [ $? -ne 0 ]; then
echo "makefs failed"
exit 1
fi
rm ${1}/etc/fstab
unit=$(mdconfig -a -t vnode -f ${2})
if [ $? -ne 0 ]; then
echo "mdconfig failed"
exit 1
fi
gpart create -s BSD ${unit}
gpart bootcode -b ${1}/boot/boot ${unit}
gpart add -t freebsd-ufs ${unit}
mdconfig -d -u ${unit}
As you can see, it does makefs first, and after this it creates the
gpart structure in the image (i.e. in its memory file system).
Why is this in this order and where exactly starts the file system
created by makefs?
The request is: it would also be nice if 'make-memstick.sh' would allow
to pass from the command line some values for the size of the file
system to be created in the image; I modified it to fit my needs as:
size=15482880b
...
makefs -B little -M ${size} -m ${size} -f 40
Thanks
matthias
--
Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211
1989-2014: The Wall was torn down so that we go to war together again.
El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez.
Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: makefs && gpart (...)
El día Thursday, January 01, 2015 a las 09:23:06AM -0800, Nathan Whitehorn
escribió:
>
> On 01/01/15 03:48, Matthias Apitz wrote:
> > gpart add -t freebsd-ufs ${unit}
> > mdconfig -d -u ${unit}
> >
> > As you can see, it does makefs first, and after this it creates the
> > gpart structure in the image (i.e. in its memory file system).
> > Why is this in this order and where exactly starts the file system
> > created by makefs?
>
>
> This is a quirk of BSD disklabels: the first partition can start at
> address 0 and the first 16 sectors of UFS2 file systems are reserved for
> the label headers. It's not portable to other partition schemes. For
> -CURRENT, this script has been replaced, by the way, and doesn't use BSD
> labels anymore.
> -Nathan
I'm on -HEAD (r272526) and the script remains unchanged there. Thanks
anyway for your feedback.
matthias
--
Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211
1989-2014: The Wall was torn down so that we go to war together again.
El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez.
Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Acer C720 Chromebook (was: Re: looking for new netbook)
El día Thursday, November 27, 2014 a las 10:43:42AM +0100, Matthias Apitz escribió: > I'm looking for a new netbook laptop; my old EeePC 900 (from 2008) has > to short battery time, and the Acer Aspire One D250 has a problem with the > display (from time to time goes completely white, the system is running, > but one has to reboot to get an image again); > > What I want is more or less: > > -- 1-2 GByte RAM > -- 1024x600 display, ~10 inch > -- 50++ GByte SSD disk > -- normal QWERTY/Z keyboard (i.o. no tablet) > -- Wifi supported in head > -- USB ports for UMTS dongle > -- and of course, it should run FreeBSD; > > Any pointers to a modern device? Some week ago I have asked the above question and with the free time during the change of the year I can now answer it an I want to share some experiences: I found the Acer C720 Chromebook with the following technical data: -- 2 GByte RAM (soldered on board, not update-able) -- 2 core CPU, each 1.4 GHz -- display 1366x768, ~11 inch, very nicely support by Xorg VESA driver -- Wifi Atheros AR946x/AR948x, supported by ah(4) -- sound supported by snd_hda(4) -- 16 GByte SSD, can be swapped by, for example, MTS400 M.2 SSD 128GB SATA III, MLC (128 GByte) I will attach a dmesg output; The problem was: 1. It needs take apart the device to unlock the BIOS protection to be able to use a SeaBIOS for legacy boot from SSD or USB; 2. One needs some patches against -HEAD; All this is very good documented by the author of the patches, Michael Gmelin, in his blog: http://blog.grem.de/pages/c720.html Thanks to him for this work and his helping hand during my first steps with this nice device. I think, the patches should be incorporated into SVN, at the moment they are against -HEAD as of January 5th. The keyboard of the C720, in principle a normal PC105, mine with German layout QWERTZ, is a bit tricky: it has - only F-keys from F1 to F10 and they are labeled with symbols for the ChromeOS applications; - no hardware power-off (only by an ACPI key which is situated where F11 would be, i.e. right above the Backspace key, you see the risk :-) ) - no Windows key which could be used as Modifier-key in X11; - no PageUP/DOWN keys - no 'blue Fn' key for additional functions (like audio or brightnes) In his blog Michael documents as well ways to help out of this. It now runs very nicely -HEAD (still booted from an USB stick because I'm waiting for the 128 GByte SSD to swap it). I'm really surprised about the battery: lasts for 6-8 hours. Wow!!! HIH matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 1989-2014: The Wall was torn down so that we go to war together again. El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez. Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen. Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #0 r272526M: Thu Jan 1 05:30:48 CET 2015 guru@vm-poudriere-r269739:/usr/local/acerC720/obj/usr/local/acerC720/src/sys/GENERIC i386 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 VT: running with driver "vga". CPU: Intel(R) Celeron(R) 2955U @ 1.40GHz (1396.79-MHz 686-class CPU) Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 Stepping=1 Features=0xbfebfbff Features2=0x45daebbf,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,RDRAND> AMD Features=0x2c10 AMD Features2=0x21 Structured Extended Features=0x2603 XSAVE Features=0x1 VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 2079817728 (1983 MB) avail memory = 2014519296 (1921 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 ioapic0 irqs 0-39 on motherboard kbd1 at kbdmux0 module_register_init: MOD_LOAD (vesa, 0xc0f98550, 0) error 19 random: initialized acpi0: on motherboard acpi0: Power Button (fixed) hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 Event timer "HPET5" frequency 14318180 Hz quality 440 Event timer "HPET6" frequency 14318180 Hz quality 440 cpu0: on acpi0 cpu1: on acpi0 atrtc0: port
kernel: MCA: CPU 0 COR (1) internal parity error
Hello,
I'm running since some days a recent -HEAD r276659 on an Acer C720
Chromebook which works very nicely and fast (I really have never seen
such a fast KDE4 desktop).
>From time to time (let's say 2-3 times a day) I see messages like this
in /var/log/messages:
Jan 16 12:04:24 c720-r276659 kernel: MCA: Bank 0, Status 0x904f0005
Jan 16 12:04:24 c720-r276659 kernel: MCA: Global Cap 0x0c07, Status
0x
Jan 16 12:04:24 c720-r276659 kernel: MCA: Vendor "GenuineIntel", ID 0x40651,
APIC ID 0
Jan 16 12:04:24 c720-r276659 kernel: MCA: CPU 0 COR (1) internal parity error
the kernel is:
# uname -a
FreeBSD c720-r276659 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r276659M: Tue Jan 6
12:55:25 CET 2015
guru@vm-poudriere-r269739:/usr/local/acerC720/obj/usr/local/acerC720/src/sys/GENERIC
i386
i.e. the i386 version (because I compile everything in a VM)
Are the above messages really a hardware problem?
Thanks
matthias
--
Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211
1989-2014: The Wall was torn down so that we go to war together again.
El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez.
Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel: MCA: CPU 0 COR (1) internal parity error
El día Friday, January 16, 2015 a las 03:04:52PM -0500, Eric van Gyzen escribió: > On 01/16/2015 14:45, Matthias Apitz wrote: > > Jan 16 12:04:24 c720-r276659 kernel: MCA: Bank 0, Status 0x904f0005 > > Jan 16 12:04:24 c720-r276659 kernel: MCA: Global Cap 0x0c07, > > Status 0x > > Jan 16 12:04:24 c720-r276659 kernel: MCA: Vendor "GenuineIntel", ID > > 0x40651, APIC ID 0 > > Jan 16 12:04:24 c720-r276659 kernel: MCA: CPU 0 COR (1) internal parity > > error > > Try ports/sysutils/mcelog. I have installed that port and launched it as # mcelog > mcelog.txt ... mcelog: Unsupported new Family 6 Model 45 CPU: only decoding architectural errors mcelog: Unsupported new Family 6 Model 45 CPU: only decoding architectural errors mcelog: Unsupported new Family 6 Model 45 CPU: only decoding architectural errors ... (the messages are STDERR); in 'mcelog.txt' it has for the last event from /var/log/messages: Jan 17 18:23:54 c720-r276659 kernel: MCA: Bank 0, Status 0x904f0005 Jan 17 18:23:54 c720-r276659 kernel: MCA: Global Cap 0x0c07, Status 0x Jan 17 18:23:54 c720-r276659 kernel: MCA: Vendor "GenuineIntel", ID 0x40651, APIC ID 0 Jan 17 18:23:54 c720-r276659 kernel: MCA: CPU 0 COR (1) internal parity error the following lines (the uptime matches): ... HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor MCE 32 CPU 0 BANK 0 TSC 36eec80fd688 [at 1397 Mhz 0 days 12:0:41 uptime (unreliable)] MCG status: MCi status: Error enabled MCA: Unknown Error 5 STATUS 904f0005 MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Questions: a) Is the output of mcelog valid (regardless of the msg on STDERR of 'unsupported model')? b) Is it worth to contact the dealer or wait until it is broken completely? Thanks matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 1989-2014: The Wall was torn down so that we go to war together again. El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez. Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CURRENT] r277641 fails to installworld: routing_test: No such file or directory
El día Saturday, January 24, 2015 a las 01:49:58PM +0100, O. Hartmann escribió:
> Most recent sources fail to install with the error below. CURRENT is amd64
> and at r277641:
>
>
> ===> etc/tests/rc.d (install)
> install -o root -g wheel -m 555 routing_test
> /usr/tests/etc/rc.d/routing_test
> install: /usr/tests/etc/rc.d/routing_test: No such file or directory
> *** Error code 71
I'm facing right now (13:52 CET) the same with creating the jail for
poudriere with
poudriere jail -c -j freebsd-head -m svn+http -v head
after 2 hours all is rolled back :-(
not even the checked out tree is left :-(
matthias
--
Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211
1989-2014: The Wall was torn down so that we go to war together again.
El Muro ha sido derribado para que nos unimos en ir a la guerra otra vez.
Diese Grenze wurde aufgehoben damit wir gemeinsam wieder in den Krieg ziehen.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Acer C720 random complete power-off
Hello, I run HEAD i386 on an Acer C720 netbook (the so called Cromebook), which works pretty much fine and very fast. The device is used on a daily basis with 18++ hours uptime a day. >From time to time (since January exactly 5 times) I faced a complete randomly power-off of the device. Please, do not think in the usual suspects of CPU heat or power drain. I monitor in a file every time the exact device situation, which is here: http://www.unixarea.de/c720-crashes.html In /var/log/messages are no indications, and if the system would have written something in its last second, it is perhaps rolled back by the fsck on reboot. What I wanted to ask here: Is there any way to read any information out of local memory buffers when the system comes up again or any other way to understand what could cause this problem. I have to admit, that until now I was never present with my eyes when it happened, I was always somehow a way from the display (running KDE4), and when I returned to it, I found it black. Thanks in advance. matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ping not working after upgrading to -CURRENT
El día Friday, May 01, 2015 a las 11:20:24AM +0200, Olivier Cochard-Labbé escribió: > On Thu, Apr 30, 2015 at 5:28 PM, Edvard Fagerholm wrote: > > > > > ping: unable to limit access to system.dns service: File exists > > > > Any ideas? > > > > > What's your exact revision number ? > I didn't meet the problem on r282220, but I've got the same problem on > r282296. Maybe you might run ping under truss(1) to see what it is missing, like: # truss -o /tmp/ping.tr ping www.muc.de matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 +49-176-38902045 "Wenn der Mensch von den Umständen gebildet wird, so muß man die Umstände menschlich bilden." "Si el hombre es formado por las circunstancias entonces es necesario formar humanamente las circunstancias", Karl Marx in Die heilige Familie / La sagrada familia (MEW 2, 138) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
after login through serial line, open(2) on /dev/tty hangs
Hello, I'm preparing something for an exposition on some Vintage Computer Event and connected an old original VT102 to my netbook running CURRENT. See here: http://www.unixarea.de/freebsd-vt102.jpg The system is r276659 on i386. The VT102 is connected through an USB-serial adapter and getty spawns nicely login: to /dev/cuaU0. Login works as well, but only with /bin/csh as login-shell, not with /bin/sh. After some digging, I figured out that the real problem is the hanging open(2) syscall on /dev/tty: no proc can't open this file after login through /dev/cuaU0.. More details in the issue in bugzilla: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200445 What part of the kernel should I instrument with more debugging log to get light into this problem? Any other ideas? Thanks matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 +49-176-38902045 "Wenn der Mensch von den Umständen gebildet wird, so muß man die Umstände menschlich bilden." "Si el hombre es formado por las circunstancias entonces es necesario formar humanamente las circunstancias", Karl Marx in Die heilige Familie / La sagrada familia (MEW 2, 138) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: after login through serial line, open(2) on /dev/tty hangs
El día Wednesday, May 27, 2015 a las 11:57:56AM +0200, Ed Schouten escribió: > 2015-05-27 8:01 GMT+02:00 Matthias Apitz : > > The VT102 is connected through an USB-serial adapter and getty spawns > > nicely login: to /dev/cuaU0. > > /dev/cua* should be used to 'call out' on a TTY. They're not intended > to run gettys on. Please /dev/ttyU0 instead. :-) > > I suspect that opening /dev/tty blocks, for the reason that the > terminal you use doesn't provide any modem status lines. /dev/cua* > 'works' in your case, because those device nodes ignore modem status. > You can disable checking for this by using "3wire.9600" instead of > "std.9600" in /etc/ttys. See gettytab(5) for more details. > Thanks! it works with "3wire.9600" and ttyU0; this message was now written on the VT102 with mutt and vim :-) matthias -- Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ +49-170-4527211 +49-176-38902045 "Wenn der Mensch von den Umständen gebildet wird, so muß man die Umstände menschlich bilden." "Si el hombre es formado por las circunstancias entonces es necesario formar humanamente las circunstancias", Karl Marx in Die heilige Familie / La sagrada familia (MEW 2, 138) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
duration of buildworld
Hello, Yesterday I grabbed r285885 from SVN and launched a # make -j2 buildworld which is still running after 19 hours on a server of 2 CPU of the type Intel(R) Core(TM)2 Extreme CPU X9100 @ 3.06GHz and 4 GByte memory. Last time in January with r276659 on the same host it took only some 8 hours, IIRC. Is there anything wrong of what could cause this change of the build time? Thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: duration of buildworld
El día Monday, July 27, 2015 a las 07:58:04AM +0200, Matthias Apitz escribió: > > Hello, > > Yesterday I grabbed r285885 from SVN and launched a > > # make -j2 buildworld > > which is still running after 19 hours on a server of 2 CPU of the type > Intel(R) Core(TM)2 Extreme CPU X9100 @ 3.06GHz and 4 GByte memory. > > Last time in January with r276659 on the same host it took only some 8 > hours, IIRC. > > Is there anything wrong of what could cause this change of the build > time? It terminated right now after nearly 24h. I never saw such a long build. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: duration of buildworld
El día Monday, July 27, 2015 a las 03:00:06PM +0300, Slawa Olhovchenkov escribió: > On Mon, Jul 27, 2015 at 07:58:04AM +0200, Matthias Apitz wrote: > > > > > Hello, > > > > Yesterday I grabbed r285885 from SVN and launched a > > > > # make -j2 buildworld > > > > which is still running after 19 hours on a server of 2 CPU of the type > > Intel(R) Core(TM)2 Extreme CPU X9100 @ 3.06GHz and 4 GByte memory. > > > > Last time in January with r276659 on the same host it took only some 8 > > hours, IIRC. > > > > Is there anything wrong of what could cause this change of the build > > time? > > May be swap trashing on clang compilation? This pointed in the right direction. I have had 6x 1 GByte additional swap partitions to plain files mounted (because I needed this to get the eclipse port compiled within poudriere). After changing the fstab and reboot, the 'make buildkernel' takes only half an hour. Why is this? matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: duration of buildworld
El día Monday, July 27, 2015 a las 10:34:10PM +0300, Slawa Olhovchenkov escribió: > > This pointed in the right direction. I have had 6x 1 GByte additional > > swap partitions to plain files mounted (because I needed this to get > > the eclipse port compiled within poudriere). After changing the fstab and > > reboot, the 'make buildkernel' takes only half an hour. > > > > Why is this? > > swap to ZFS volume don't work some time ago (don't know about current > status). > May be swap to file on ZFS don't work also? I do not use ZFS. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: duration of buildworld
El día Tuesday, July 28, 2015 a las 09:20:38AM +0100, David Chisnall escribió:
> It sounds as if the swap was working (as the build took a long time, it
> didn’t run out of memory). My guess would be that, before the reboot,
> something had wired (or, if not, then touched frequently enough to keep it in
> core) a large chunk of memory, which forced the swapping. Swap files are
> expected to be slower than swap partitions (though if you’re swapping to a
> disk, the seek times are likely to dominate in both cases).
>
> I don’t suppose there’s capture of the output of top from before the reboot?
No, I did not saved it.
When I started the buildworld, I started in parallel already a poudriere
jail to build around 1600 ports. Later, when I realized that the
buildworld took so long, I stopped (killed) the poudriere jail.
IIRC the "swapctl -l" showed before the boot that the swap files have been
used.
I could re-create the situation on next buildworld.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045
No! Nein! ¡No! Όχι! -- Ευχαριστούμε!
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
make installworld DESTDIR=/mnt failes
Hello,
I have a CURRENT r285885 in /usr/home/guru/r285885/src and
/usr/home/guru/r285885/obj
ready for make install into a new target root mounted as /mnt;
the installation should (and allways) worked as
# sh
# cd /usr/home/guru/r285885/src
# MAKEOBJDIRPREFIX=/usr/home/guru/r285885/obj export MAKEOBJDIRPREFIX
# make installworld DESTDIR=/mnt
# make installkernel DESTDIR=/mnt
# make distrib-dirs DESTDIR=/mnt
# make distribution DESTDIR=/mnt
but this time the installworld failes after some time with:
...
install -s -o root -g wheel -m 555 primes /mnt/usr/bin/primes
===> games/random (install)
install -s -o root -g wheel -m 555 random /mnt/usr/bin/random
install -o root -g wheel -m 444 random.6.gz /mnt/usr/share/man/man6
===> games/tests (install)
install -o root -g wheel -m 444 /usr/home/guru/r285885/src/tests/Kyuafile
/mnt/usr/tests/games/Kyuafile
===> cddl (install)
===> cddl/lib (install)
===> cddl/lib/drti (install)
make[6]:
/usr/home/guru/r285885/obj/usr/home/guru/r285885/src/cddl/lib/drti/.depend, 79:
ignoring stale .depend for
/home/guru/r285885/obj/usr/home/guru/r285885/src/tmp/usr/include/unistd.h
...
cc -O2 -pipe
-I/usr/home/guru/r285885/src/cddl/lib/drti/../../../sys/cddl/compat/opensolaris
-I/usr/home/guru/r285885/src/cddl/lib/drti/../../../cddl/compat/opensolaris/include
-I/usr/home/guru/r285885/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/head
-I/usr/home/guru/r285885/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/lib/libctf/common
-I/usr/home/guru/r285885/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/lib/libdtrace/common
-I/usr/home/guru/r285885/src/cddl/lib/drti/../../../sys/cddl/contrib/opensolaris/uts/common
-DPIC -fpic -DNEED_SOLARIS_BOOLEAN -std=gnu99 -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type
-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
-Wold-style-definition -Wno-pointer-sign -Wno-unknown-pragmas
-Wmissing-variable-declarations -Wthread-safety -Wno-empty-body
-Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c
/usr/home/guru/r285885/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/lib/libdtrace/common/drti.c
-o drti.o
In file included from
/usr/home/guru/r285885/src/cddl/lib/drti/../../../cddl/contrib/opensolaris/lib/libdtrace/common/drti.c:27:
/usr/home/guru/r285885/src/cddl/lib/drti/../../../cddl/compat/opensolaris/include/unistd.h:33:15:
fatal error: 'unistd.h' file not found
#include_next
^
1 error generated.
*** Error code 1
Stop.
Why it is ignoring the .depend file and tries to compile something
again?
cd /usr/home/guru/r285885/obj/usr/home/guru/r285885/src/cddl/lib/drti
la -la
total 17
drwxr-xr-x 2 root wheel 512 Aug 2 09:01 .
drwxr-xr-x 13 root wheel 512 Jul 26 10:11 ..
-rw-r--r-- 1 root wheel 7350 Jul 26 20:12 .depend
-rw-r--r-- 1 root wheel 6300 Jul 26 20:14 libdrti-dummy.a
ls -l
/usr/home/guru/r285885/obj/usr/home/guru/r285885/src/tmp/usr/include/unistd.h
-rwxr-xr-x 1 root wheel 18911 Jul 26 09:08
/usr/home/guru/r285885/obj/usr/home/guru/r285885/src/tmp/usr/include/unistd.h
date
Sun Aug 2 09:12:01 UTC 2015
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045
No! Nein! ¡No! Όχι! -- Ευχαριστούμε!
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: make installworld DESTDIR=/mnt failes
El día Sunday, August 02, 2015 a las 11:29:32AM +0200, Matthias Apitz escribió: ># make installworld DESTDIR=/mnt > > but this time the installworld failes after some time with: > > ... > install -s -o root -g wheel -m 555 primes /mnt/usr/bin/primes > ===> games/random (install) > install -s -o root -g wheel -m 555 random /mnt/usr/bin/random > install -o root -g wheel -m 444 random.6.gz /mnt/usr/share/man/man6 > ===> games/tests (install) > install -o root -g wheel -m 444 /usr/home/guru/r285885/src/tests/Kyuafile > /mnt/usr/tests/games/Kyuafile > ===> cddl (install) > ===> cddl/lib (install) > ===> cddl/lib/drti (install) > make[6]: > /usr/home/guru/r285885/obj/usr/home/guru/r285885/src/cddl/lib/drti/.depend, > 79: ignoring stale .depend for > /home/guru/r285885/obj/usr/home/guru/r285885/src/tmp/usr/include/unistd.h > ... I found the problem: The system where the 'make installworld' was running, have had no sym link from /home --> usr/home and that's why the file /home/guru/r285885/obj/usr/home/guru/r285885/src/tmp/usr/include/unistd.h from .depend could not be checked. A big pitfall :-( matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: make installworld DESTDIR=/mnt failes
El día Sunday, August 02, 2015 a las 03:47:53PM +0200, Matthias Apitz escribió: > El día Sunday, August 02, 2015 a las 11:29:32AM +0200, Matthias Apitz > escribió: > > ># make installworld DESTDIR=/mnt > > > > but this time the installworld failes after some time with: > > > > ... > > install -s -o root -g wheel -m 555 primes /mnt/usr/bin/primes > > ===> games/random (install) > > install -s -o root -g wheel -m 555 random /mnt/usr/bin/random > > install -o root -g wheel -m 444 random.6.gz /mnt/usr/share/man/man6 > > ===> games/tests (install) > > install -o root -g wheel -m 444 /usr/home/guru/r285885/src/tests/Kyuafile > > /mnt/usr/tests/games/Kyuafile > > ===> cddl (install) > > ===> cddl/lib (install) > > ===> cddl/lib/drti (install) > > make[6]: > > /usr/home/guru/r285885/obj/usr/home/guru/r285885/src/cddl/lib/drti/.depend, > > 79: ignoring stale .depend for > > /home/guru/r285885/obj/usr/home/guru/r285885/src/tmp/usr/include/unistd.h > > ... > > I found the problem: The system where the 'make installworld' was > running, have had no sym link from /home --> usr/home and that's why the > file /home/guru/r285885/obj/usr/home/guru/r285885/src/tmp/usr/include/unistd.h > from .depend could not be checked. A big pitfall :-( I was asking me, why that happened (for the 1st time) and investigated one of the older boot keys which I always produce nearly the same way to pollute other hardware with new systems/kernels... I always compile/install world and kernel into some DESTDIR and make from that a bootable USB key with the script /usr/src/release/amd64/make-memstick.sh The fundamental mistake I did this time was having the src and obj below /usr/home/guru/r285885/[src|obj] and not below /usr/local//[src|obj]. This way the .depend files contain references to /usr/home/... and to /home/... files, which will not work if /home does not exist as a sym link to usr/home Lesion learned. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Intel Haswell support - Any updates?
El día Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, Johannes escribió: > Same here. I would personally definitely buy new hardware from Intel if > FreeBSD worked on it (not vesa...) > ... What dow you have against vesa? I run CURRENT on some Acer C720 Chromebooks with Haswell chipset in Vesa mode. And you will not note it. I have never ever had such a fast desktop (KDE4) before. I can live fine with Vesa until Haswell suport is there. matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ 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: Intel Haswell support - Any updates?
El día Thursday, September 17, 2015 a las 11:02:07AM -0400, Kris Moore escribió: > On 09/17/2015 09:48, Matthias Apitz wrote: > > El día Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, > > Johannes escribió: > > > >> Same here. I would personally definitely buy new hardware from Intel if > >> FreeBSD worked on it (not vesa...) > >> ... > > What dow you have against vesa? I run CURRENT on some Acer C720 > > Chromebooks with Haswell chipset in Vesa mode. And you will not note it. > > I have never ever had such a fast desktop (KDE4) before. I can live fine > > with Vesa until Haswell suport is there. > > > > matthias > > BTW, have you tried the xf86-video-scfb driver? It works much better > than vesa here. The only catch is you have to be booted UEFI with CSM > disabled. Using it on my X1 Carbon, gets 3k resolution properly and > everything. Thanks to Glen Barber for bringing that to my attention. The Chromebook Acer C720 does not has UEFI; it runs Coreboot with SeaBIOS as payload. The Xorg runs fine without any xorg.conf file, just detects the video as Vesa with 1366x768 resolution, the max of the 11" screen of this netbook. matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ 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: Intel Haswell support - Any updates?
El día Thursday, September 17, 2015 a las 11:23:06AM -0700, Russell L. Carter
escribió:
> Do you have 802.11n and hibernate working on that c720? I put linux on
> mine for that reason. Although despite immense efforts I can't get
> the trackpad to be detected. I tried bringing up 10.2 on it but
> couldn't get it to boot.
You must run a ver y recent -HEAD; Wifi is fine, but most of the time I
use some Ubuntu phone attached to USB tethered as router to mobile
Internet (as right now). hibernate is not working, AFAIK, without
Haswell support; the touchpad works too; you must learn to use it
because it has not any button and so you must know where to tic to get
left or right button :-)
> These things are just awesome. 4G memory
> + i3 + 6hr battery for $240 delivered.
exactly; since I own the C720, I do not think anymore in where is the next power
outlet :-)
and it is fast, very fast, perhaps due to the SSD;
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
No! Nein! ¡No! Όχι! -- Ευχαριστούμε!
___
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: Intel Haswell support - Any updates?
El día Thursday, September 17, 2015 a las 08:57:20PM +0200, Matthias Apitz
escribió:
> > These things are just awesome. 4G memory
> > + i3 + 6hr battery for $240 delivered.
>
> exactly; since I own the C720, I do not think anymore in where is the next
> power
> outlet :-)
$ uptime
9:37PM up 2:02, 4 users, load averages: 0,31 0,28 0,26
$ sysctl -a | fgrep battery.life
hw.acpi.battery.life: 63
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
No! Nein! ¡No! Όχι! -- Ευχαριστούμε!
___
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: Intel Haswell support - Any updates?
El día Thursday, September 17, 2015 a las 11:42:01PM +0200, Nikola Pajkovsky
escribió:
> Do not run those commands in X, otherwise it hangs.
>
> $ vidcontrol -i mode | grep 1920
> 383 (0x17f) 0x000f G 1920x1080x32 D 8x16 0xa 64k 64k 0xe000
> 8100k
On my C720 the above cmd does not give any usefull information:
mode# flags typesize font window linear buffer
--
0 (0x000) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
1 (0x001) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
2 (0x002) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
3 (0x003) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
4 (0x004) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
5 ...
507 (0x1fb) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
508 (0x1fc) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
509 (0x1fd) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
510 (0x1fe) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
511 (0x1ff) 0x T 0x0 0x402653478 0x280996d6 131362k 0k
0x 0k
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
No! Nein! ¡No! Όχι! -- Ευχαριστούμε!
___
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"
sendmail && sasl
Hello, I have always compiled sendmail for sasl the following way: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html - install port security/cyrus-sasl2 - config line in /usr/local/lib/sasl2/Sendmail.conf pwcheck_method: saslauthd - install port security/cyrus-sasl2-saslauthd, - edit /etc/rc.conf: saslauthd_enable="YES" - restart daemon with # /usr/local/etc/rc.d/saslauthd start - recompile sendmail with /etc/make.conf set to SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL SENDMAIL_LDFLAGS=-L/usr/local/lib SENDMAIL_LDADD=-lsasl2 # cd /usr/src/lib/libsmutil # make cleandir && make obj && make # cd /usr/src/lib/libsm # make cleandir && make obj && make # cd /usr/src/usr.sbin/sendmail # make cleandir && make obj && make && make install ... But now on r285885 it is unwilling to start with: # /etc/rc.d/sendmail restart sendmail not running? (check /var/run/sendmail.pid). Starting sendmail. 421 4.0.0 sasl_server_init failed! [generic failure] Any idea what I'm missing? Thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ 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: sendmail && sasl
On Tuesday, 1 December 2015 16:58:25 CET, Matthias Apitz wrote: ... - config line in /usr/local/lib/sasl2/Sendmail.conf pwcheck_method: saslauthd This was just a typo, the colon : was missing, sorry for the noise; matthias -- Sent from my Ubuntu phone http://www.unixarea.de/ ___ 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"
pkg does not update the repo catalogue
Hello,
This is with 11-CURRENT and ports from July this year; I have the
packages which I build with poudriere on some other host in a dir
/usr/PKGDIR.20150726 and added 8 new packages there, the total number is
now 1691:
# ls *.txz | egrep -v 'packagesite.txz|meta.txz|digests.txz' | wc -l
1691
My repo definition is:
# cat /usr/local/etc/pkg/repos/myrepo.conf
FreeBSD: {
url: "file:/usr/PKGDIR.20150726",
enabled: true,
}
When I now want to update the 8 new packages to the repo catalogue, they
are not added (i.e. the number stays with 1683 and I also can not
install them with 'pkg instal ...'):
# pkg -v
1.5.5
# pkg -R /usr/local/etc/pkg/repos/ update -f
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%260 B 0.3kB/s00:01
Fetching packagesite.txz: 100% 382 KiB 391.6kB/s00:01
Processing entries: 100%
FreeBSD repository update completed. 1683 packages processed.
What I'm missing here?
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
___
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: pkg does not update the repo catalogue
El día Monday, December 07, 2015 a las 10:14:24AM +, Matthew Seaman
escribió:
> On 12/07/15 08:50, Matthias Apitz wrote:
> >
> > Hello,
> >
> > This is with 11-CURRENT and ports from July this year; I have the
> > packages which I build with poudriere on some other host in a dir
> > /usr/PKGDIR.20150726 and added 8 new packages there, the total number is
> > now 1691:
> >
> > # ls *.txz | egrep -v 'packagesite.txz|meta.txz|digests.txz' | wc -l
> > 1691
> >
> > My repo definition is:
> >
> > # cat /usr/local/etc/pkg/repos/myrepo.conf
> >FreeBSD: {
> >url: "file:/usr/PKGDIR.20150726",
> >enabled: true,
> >}
>
> There's no need to label your custom repo as 'FreeBSD' -- in fact, it's
> probably better for you to use a distinct name, as the repo.conf files
> accumulate for the same repo tag. In this case you've possibly
> inadvertently got pkg checking the pkg signatures against the default
> FreeBSD repository keys, which isn't going to work for locally built
> packages.
>
> Just change the tag in the repo.conf to 'myrepo' and then check what
> pkg(8) sees overall by running 'pkg -vv'. You'll need to do a pkg
> upgrade -f after that.
>
> If you don't want to use the standard FreeBSD repo at all then you can
> add a /usr/local/etc/repos/FreeBSD.conf containing
>
> FreeBSD: { enabled: no }
I did both: renamed the entry to myrepo and added a new file:
# ls -l /usr/local/etc/pkg/repos/
total 8
-rw-r--r-- 1 root wheel 26 7 dic 11:30 FreeBSD.conf
-rw-r--r-- 1 root wheel 114 7 dic 11:21 myrepo.conf
# cat /usr/local/etc/pkg/repos/*
FreeBSD: { enabled: no }
myrepo: {
url: "file:/usr/PKGDIR.20150726",
enabled: true,
}
Now 'pkg -vv' shows only myrepo; the 'pkg upgrade -f' ended up with
reinstallation of all ~1000 packages;
but all this did not solved the problem;
> If changing the repo tag doesn't fix the problem, try turning on some
> debugging output:
>
>env DEBUG_LEVEL=4 pkg update -f
The output of STDERR is here: http://www.unixarea.de/pkg-stderr.txt
(4 MByte, 100.000 lines)
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
___
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: pkg does not update the repo catalogue
El día Monday, December 07, 2015 a las 11:31:40AM +, Matthew Seaman escribió: > H it seems fairly clear to me that the 8 new packages aren't in > the repo catalogue that you're downloading. You built the repo using > poudriere? Poudriere does some fun'n'games with symbolic links to > achieve an atomic repo update, which means there is actually a history > of previous versions of the repo kept. You'll see a directory structure > like this: > > ... Maybe I wasn't clear enough. I copied only the packages to the new system (my netbook) some weeks ago, and created the catalogue with # pkg repo /usr/PKGDIR.20150726 and installed the packages; Today I built 8 packages more, copied them over too and was (may be in error) expecting to add these 8 new packages to the catalogue with 'pkg update -f' Seems that I just have to reuse 'pkg repo ' Thanks for your hints. matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ 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: "libssl.so.8" not found
El día Sunday, December 13, 2015 a las 10:40:22PM -0800, Russell Haley escribió: > Hi There, > > I am trying to bring up an Arm image off the FreeBSD website for my > hummingboard. The problem seems to be when I run pkg the system installs > the latest version - 1.6.2, and then fails with: > > Shared object "libssl.so.8" not found, required by "pkg" > > I've seen this in NextBSD, and DesktopBSD and even on my previous arm image > but I was able to get around the problem by creating links from libssl.so.7 > to libssl.so.8. I have had the same issue on r285885 with ports as well from July this year and pkg 1.5.5 ... I accidently updated pkg to 1.6.x which could not find libssl.so.8; I forced back to 1.5.5 with an older pkg-static and now pkg complains about it database, but still works: $ pkg info pkg pkg: warning: database version 32 is newer than libpkg(3) version 31, but still compatible pkg-1.5.5 I don't know why pkg 1.6.2 was produced with this recent libssl.so.8; it should have been done more conservative, IMHO matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ 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"
kernel && poudriere jails
Hello, I have on a Dell M5500 my poudriere jails for amd64; the host system is at the moment r276659 (January 2015) and the jails are: r276659 (January 2015) + ports r392920 (July 2015) r276659 (January 2015) + ports r403255 (December 2015) I'm right now updating the host to r292778 (as of today) and will run new jails: r285885 (August 2015) + ports r403255 (December 2015) r292778 (December 2015) + ports xxx (January 2016) My question is: will the two old jails based on r276659 still work on a host r292778? Thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ 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: kernel && poudriere jails
El día Monday, December 28, 2015 a las 10:56:04AM +0800, Julian Elischer escribió: Julian, Thanks for your feedback; ... > On 28/12/2015 1:48 AM, Matthias Apitz wrote: > > Hello, > > > > I have on a Dell M5500 my poudriere jails for amd64; the host system btw: it is a M4400, not M5500; > > is at the moment r276659 (January 2015) and the jails are: > > > > r276659 (January 2015) + ports r392920 (July 2015) > > r276659 (January 2015) + ports r403255 (December 2015) > > > > I'm right now updating the host to r292778 (as of today) and will run > > new jails: > > > > r285885 (August 2015) + ports r403255 (December 2015) > > r292778 (December 2015) + ports xxx (January 2016) > > > > My question is: will the two old jails based on r276659 still work on a > > host r292778? > > My experience is that you are more likely to have problems in your > existing setup because you should always try keep the kernel newer > than the newest jail. but in the actual case the kernel of the host equals the jails; and it worked/works fine; > your new stup shoud just work. > ok; so I will continue with the update; thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ 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"
panic while booting the official ISO 11-CUR-amd64-20151217-r292413
Hello, I downloaded the ISO for the above version and when I boot it in a VMWare it panics reproduceable after trying to mount the root; see the message captured in the last screens: http://www.unixarea.de/panic-01.jpg http://www.unixarea.de/panic-02.jpg Any comments or hints? matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ 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: panic while booting the official ISO 11-CUR-amd64-20151217-r292413
El día Monday, December 28, 2015 a las 02:12:29PM +0100, Matthias Apitz
escribió:
>
> Hello,
>
> I downloaded the ISO for the above version and when I boot it in a
> VMWare it panics reproduceable after trying to mount the root; see the
> message captured in the last screens:
>
> http://www.unixarea.de/panic-01.jpg
> http://www.unixarea.de/panic-02.jpg
>
> Any comments or hints?
The downloaded VMWare image .vmdk of the same revision r292413 boots
fine;
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
___
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: Can't install 11 .iso images in virtual box
On Tuesday, 29 December 2015 17:01:28 CET, Glen Barber wrote: On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote: disk1.iso has kernel panic during boot. And bootonly.iso boots but after downloading kernel and base it says that there is the incorrect checksum, and it needs to downlodagain. Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso This is because we can only store (currently) one version of the distribution sets on FTP, and the most recent build (from last night) is syncing to the mirrors currently. What was the panic message for disc1.iso? I do not recall seeing a panic with that image when I tested the last set of builds. Glen I had the same problem yesterday and got a reply that this is a known bug, check the archive of the list: matthias -- Sent from my Ubuntu phone http://www.unixarea.de/ ___ 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"
interrupt and resume poudriere jail creation
Hello,
I'm creating a new -CURRENT jail for poudriere with:
# poudriere jail -c -j freebsd-r292778 -m svn+http -v head@r292778
The src/ is checked out via SVN and it is already compiling the jail
for two hours, but I have to interrupt it for some network problem here
and I did the mistake to start it in a SSH session :-(
Is there a way like -DNO_CLEAN when compiling 'make buildkernel' to
resume the compilation in the jail at the point of the interrupt?
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎
+49-176-38902045
___
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"
poudriere ports -c ... checks out the base system instead of the ports
Hello, I run into the following problem: # poudriere version 3.2-pre (installed from ports) # pkg info dialog4ports-0.1.5_2 Console Interface to configure ports pkg-1.6.2 Package manager poudriere-devel-3.1.99.20151204 Port build and test system # uname -a FreeBSD poudriere-amd64 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r292778: Mon Dec 28 05:45:37 CET 2015 root@poudriere-amd64:/usr/local/r292778/obj/usr/local/r292778/src/sys/GENERIC amd64 When I now want to creat the ports it does not checkout the ports tree, but the base system: # poudriere ports -c -v -p ports-20151230 -m svn+http [00:00:00] >> Checking out the ports tree... Ausr/local/poudriere/ports/ports-20151230/sys Ausr/local/poudriere/ports/ports-20151230/sys/kern Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_ktr.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_fork.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/init_main.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_sharedpage.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/subr_prf.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/subr_taskqueue.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_sig.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_thr.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_sysctl.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/vfs_bio.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/sys_process.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_rctl.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_thread.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_tc.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_physio.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_time.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/kern_linker.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/subr_uio.c Ausr/local/poudriere/ports/ports-20151230/sys/kern/imgact_aout.c ^Csvn: E200015: Caught signal - Forwarded message from Matthias Apitz - Date: Wed, 30 Dec 2015 08:16:48 +0100 From: Matthias Apitz To: freebsd-po...@freebsd.org Subject: running poudriere jail -c ... and poudriere ports -c ... in parallel Hello, Last night I was creating a new jail and ports with poudriere this way: # poudriere jail -c -j freebsd-r292778 -m svn+http -v head@r292778 # poudriere ports -c -p ports-20151229 -m svn+http -B head the latter in parallel from another session because the creation of the jail took some hours (4:28h on my Dell M4400); when I wanted to start the jail this morning the usual way, it says: # poudriere bulk -f /usr/local/etc/poudriere-list -J 4 -j freebsd-r292778 -p ports-20151229 [00:00:00] >> Creating the reference jail... done [00:00:19] >> Mounting system devices for freebsd-r292778-ports-20151229 [00:00:19] >> Mounting ports/packages/distfiles [00:00:19] >> Using packages from previously failed build [00:00:19] >> Mounting packages from: /usr/local/poudriere/data/packages/freebsd-r292778-ports-20151229 /etc/resolv.conf -> /usr/local/poudriere/data/.m/freebsd-r292778-ports-20151229/ref/etc/resolv.conf [00:00:19] >> Starting jail freebsd-r292778-ports-20151229 make: cannot open /usr/ports/Mk/bsd.port.mk. [00:00:19] >> Cleaning up [00:00:19] >> Umounting file systems I looked into this and it turned out that the dir /usr/local/poudriere/ports/ports-20151229 does not contain a checked out ports tree, but something which looks a the base system (I forgot to make a 'svnlite info' there). What does this mean? Is it somehow not allowed to run the both commands in parallel? I could not see any hint about this in the man page. matthias -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 ___ 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" - End forwarded message - -- Matthias Apitz, ✉ g...@unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045 «(über die DDR)... Und allein dieser Mangel (an Sozialismus) und nichts anderes führte zum Tod. Und wer da nicht trauert, hat kein Herz, und wer da nicht neu anpackt, hat auch keins verdient.» «(sobre la RDA)... Y solo esta escasez (de socialismo) y no otra cosa, le llevó a la muerte. Y quien no está de luto, no tiene corazón, y quien no se lanza a luchar de nuevo, no se merece corazón.», junge Welt del 3 de octubre 2015, p. 11 ___ 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"
