Re: #includes and #defined
Hi, On Fri, 10 Aug 2018 07:53:19 -0600 Warner Losh wrote: > On Thu, Aug 9, 2018 at 11:51 PM, Erich Dollansky < > freebsd.ed.li...@sumeritec.com> wrote: > > > On Fri, 10 Aug 2018 12:40:48 +0800 > > blubee blubeeme wrote: > > > > > > > > What about the architecture name is it recommended to use x86_64 > > > or amd64? > > > > my clang reports on an Intel CPU: > > > > #define __amd64 1 > > #define __amd64__ 1 > > #define __x86_64 1 > > #define __x86_64__ 1 > > > > as defined. > > > > It reports > > > > #define __aarch64__ 1 > > > > on an 64 bit ARM CPU. > > > > 'man 7 arch' will tell you these things: better late than never. I still trust a compiler more than the documentation. Erich ___ 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: #includes and #defined
Hi, On Fri, 10 Aug 2018 12:40:48 +0800 blubee blubeeme wrote: > On Fri, Aug 10, 2018 at 8:28 AM Erich Dollansky < > freebsd.ed.li...@sumeritec.com> wrote: > > > Hi, > > > > On Fri, 10 Aug 2018 08:01:42 +0800 > > blubee blubeeme wrote: > > > > > What's the proper way to define and include FreeBSD amd64 in GNU > > > Makefiles > > > > > > Do we define FreeBSD as x86_64 or amd64 also is it __FreeBSD__, > > > FreeBSD__, or __FreeBSD > > > > > > I've seen all of the above looking through different projects. > > > > clang defines '__FreeBSD__' > > > > Erich > > > > What about the architecture name is it recommended to use x86_64 or > amd64? my clang reports on an Intel CPU: #define __amd64 1 #define __amd64__ 1 #define __x86_64 1 #define __x86_64__ 1 as defined. It reports #define __aarch64__ 1 on an 64 bit ARM CPU. Erich ___ 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: #includes and #defined
Hi, On Fri, 10 Aug 2018 08:01:42 +0800 blubee blubeeme wrote: > What's the proper way to define and include FreeBSD amd64 in GNU > Makefiles > > Do we define FreeBSD as x86_64 or amd64 also is it __FreeBSD__, > FreeBSD__, or __FreeBSD > > I've seen all of the above looking through different projects. clang defines '__FreeBSD__' Erich ___ 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: programs like gdb core dump
Hi, here we are: http://sumeritec/FreeBSD/fortune.core http://sumeritec/FreeBSD/gdb.core The fortune core is from the same source as the now running system. The gdb core should be but I am not 100% sure. Revision: Revision: 337343 Erich On Wed, 8 Aug 2018 08:57:06 -0700 John Baldwin wrote: > On 8/7/18 7:00 PM, Erich Dollansky wrote: > > Hi, > > > > On Tue, 7 Aug 2018 11:59:11 -0700 > > John Baldwin wrote: > > > >> On 8/6/18 8:11 PM, Erich Dollansky wrote: > >>> On Mon, 6 Aug 2018 15:57:53 -0700 > >>> John Baldwin wrote: > >>> > >>>> On 8/4/18 4:38 PM, Erich Dollansky wrote: > > > >>>>> Bad system call (core dumped) > >>>> > >>>> Did you upgrade from stable/11 with a world that is still > >>>> stable/11? If so, did you make sure your kernel config includes > >>>> COMPAT_FREEBSD11? (GENERIC should include this) > >>>> > >>> > >>> I never have had a machine running 11. This machine is on 12 since > >>> 2 or 3 years. I will check if this configuration was properly set > >>> on that machine. > >> > >> Ahh, a fairly old 12 world with a recent 12 kernel will still need > >> COMPAT_FREEBSD11. > >> > > > > even when kernel and world are on '1200076' as provided by uname > > -U/-K, COMPAT_FREEBSD11 is required at the moment. The system is > > currently on r337343. > > Hmm, plain 12.0 binaries that are up to date should not need > COMPAT_FREEBSD11. Do you have any of the core dumps from before handy? > ___ 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: programs like gdb core dump
Hi, On Tue, 7 Aug 2018 11:59:11 -0700 John Baldwin wrote: > On 8/6/18 8:11 PM, Erich Dollansky wrote: > > On Mon, 6 Aug 2018 15:57:53 -0700 > > John Baldwin wrote: > > > >> On 8/4/18 4:38 PM, Erich Dollansky wrote: > >>> Bad system call (core dumped) > >> > >> Did you upgrade from stable/11 with a world that is still > >> stable/11? If so, did you make sure your kernel config includes > >> COMPAT_FREEBSD11? (GENERIC should include this) > >> > > > > I never have had a machine running 11. This machine is on 12 since > > 2 or 3 years. I will check if this configuration was properly set > > on that machine. > > Ahh, a fairly old 12 world with a recent 12 kernel will still need > COMPAT_FREEBSD11. > even when kernel and world are on '1200076' as provided by uname -U/-K, COMPAT_FREEBSD11 is required at the moment. The system is currently on r337343. Thanks! Erich ___ 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: programs like gdb core dump
Hi, On Tue, 7 Aug 2018 00:09:15 -0400 Allan Jude wrote: > On 2018-08-06 23:11, Erich Dollansky wrote: > >>> The message is always: > >>> > >>> Bad system call (core dumped) > > compare the output of: `uname -K` and `uname -U` > both outputs are 1200076 I got just access to that machine again. I will check it configuration. Erich ___ 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: programs like gdb core dump
Hi, On Mon, 6 Aug 2018 15:57:53 -0700 John Baldwin wrote: > On 8/4/18 4:38 PM, Erich Dollansky wrote: > > Hi, > > > > I compiled me yesterday this system: > > > > 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r337285: > > > > When restarting fortune core dumps. When trying to load the core > > dump, gdb core dumps. > > > > The message is always: > > > > Bad system call (core dumped) > > > > Trying to install ports results in the same effect. > > > > Erich > > Did you upgrade from stable/11 with a world that is still stable/11? > If so, did you make sure your kernel config includes COMPAT_FREEBSD11? > (GENERIC should include this) > I never have had a machine running 11. This machine is on 12 since 2 or 3 years. I will check if this configuration was properly set on that machine. Thanks! Erich ___ 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: svn commit: r337340 - in head: [This broke all ci.freebsd.org 's FreeBSD-head-*-build 's, clang based and gcc 4.2.1 based]
Hi,
this works now but now I am back to this:
Updating ./version.texi
--- ./m4.info ---
restore=: && backupdir=".am$$" && am__cwd=`pwd` &&
CDPATH="${ZSH_VERSION+.}:" && cd . && rm -rf $backupdir && mkdir
$backupdir && if (/usr/bin/makeinfo --no-split --version) >/dev/null
2>&1; then for f
2>in ./m4.info ./m4.info-[0-9] ./m4.info-[0-9][0-9] ./m4.i[0-9]
./m4.i[0-9][0-9];
2>do if test -f $f; then mv $f $backupdir; restore=mv; else :; fi;
2>done; else :; fi && cd "$am__cwd"; if /usr/bin/makeinfo
2>--no-split -I . -o ./m4.info ./m4.texi; then rc=0;
2>CDPATH="${ZSH_VERSION+.}:" && cd .; else rc=$?;
2>CDPATH="${ZSH_VERSION+.}:" && cd . && $restore $backupdir/* `echo
2>"././m4.info" | sed 's|[^/]*$||'`; fi; rm -rf $backupdir; exit $rc
2>Bad system call (core dumped) *** [./m4.info] Error code 140
make[4]: stopped in /usr/ports/devel/m4/work/m4-1.4.18/doc
Erich
On Sat, 04 Aug 2018 22:23:56 -0600
Brad Davis wrote:
> On Sat, Aug 4, 2018, at 9:48 PM, Brad Davis wrote:
> > On Sat, Aug 4, 2018, at 7:43 PM, Mark Millard wrote:
> > > > Author: brd
> > > > Date: Sat Aug 4 22:41:17 2018
> > > > New Revision: 337340
> > > > URL:
> > > > https://svnweb.freebsd.org/changeset/base/337340
> > > >
> > > >
> > > > Log:
> > > > Move autofs related configs to usr.sbin/autofs/
> > > >
> > > > This is prep for pkgbase to have config files tagged as such.
> > > >
> > > > Approved by: will (mentor)
> > > > Differential Revision:
> > > > https://reviews.freebsd.org/D16492
> > > . . .
> > >
> > > This broke all the ci.freebsd.org builds of freebsd-head-*-build .
> > >
> > > Using FreeBSD-head-powerpc64-build as an example:
> > > #6826 (for -r337399 ) worked but #6827 (for -r337400 )
> > > fails with:
> > >
> > > (cd /usr/src/etc; make -DDB_FROM_SRC __MAKE_CONF=/dev/null
> > > SRCCONF=/
> > > workspace/freebsd-ci/jobs/FreeBSD-head-powerpc64-build/src.conf
> > > etc- examples) cd /usr/src/etc; install -N /usr/src/etc -o root
> > > -g wheel -m 444 crontab devd.conf devfs.conf ddb.conf
> > > dhclient.conf disktab fbtab gettytab group hosts
> > > hosts.allow hosts.equiv libalias.conf libmap.conf
> > > login.access login.conf mac.conf motd netconfig networks
> > > newsyslog.conf nsswitch.conf phones profile protocols
> > > rc.bsdextended rc.firewall remote rpc services sysctl.conf
> > > syslog.conf termcap.small etc.powerpc/ttys amd.map auto_master
> > > ftpusers inetd.conf /usr/src/usr.bin/locate/locate/locate.rc
> > > hosts.lpd printcap / usr/src/usr.bin/mail/misc/mail.rc ntp.conf
> > > pf.os rc.sendmail csh.cshrc csh.login csh.logout regdomain.xml
> > > nsmb.conf opieaccess /usr/obj/usr/
> > > src/powerpc.powerpc64/release/dist/base/usr/share/examples/etc
> > > install: auto_master: No such file or directory *** Error code 71
> > >
> > > Stop.
> > > make[8]: stopped in /usr/src/etc
> > > *** Error code 1
> > >
> > >
> > >
> > > Stop.
> > > make[7]: stopped in /usr/src/share/examples
> > > *** Error code 1
> > >
> > > Stop.
> > > make[6]: stopped in /usr/src/share/examples
> > > *** Error code 1
> > >
> > > Stop.
> > > make[5]: stopped in /usr/src/share
> > > *** Error code 1
> > >
> > > Stop.
> > > make[4]: stopped in /usr/src
> > > *** Error code 1
> > >
> > > Stop.
> > > make[3]: stopped in /usr/src
> > > *** Error code 1
> > >
> > > Stop.
> > > make[2]: stopped in /usr/src
> > > *** Error code 1
> > >
> > > Stop.
> > > make[1]: stopped in /usr/src
> > > *** Error code 1
> > >
> > > Stop.
> > > make: stopped in /usr/src/release
> >
> > Testing the fix..
>
> Fix committed in r337342. Sorry for the noise.
>
>
> Regards,
> Brad Davis
> ___
> 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"
___
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: Ethernet troubles with X230
Hi, On Sun, 5 Aug 2018 12:18:24 +0200 Dhananjay Balan wrote: > Hi, > > I have a problems with ethernet on my laptop (X230). pciconf(8) > identifies the device as Intel 82579LM Gigabit Network Connection > (Lewisville). > > 1. Resuming after a long suspend (~5hr), sometimes the > machine can't get a DHCP IP. > > 2. After suspend, the ethernet device starts reporting no carrier, > eventhough the cables are plugged in and if I plug it to a different > box, they would work > > I can reproduce both on 12.0-CURRENT #17 r336576. But not sure when > they started. > > I have seen this behaviour with 2 routeres running three firmwares at > the other end. > 1. Easybox (linux 2.x?) > 2. Edgerouter lite running stock fw (linux 2.x) and 12-CURRENT (~3 > months old) > > For Problem (1) DHCP lease: > ifconfig shows: > em0: flags=8843 metric 0 mtu > 1500 > options=81249b > ether xx:xx:xx:xx:xx:xx inet 0.0.0.0 netmask 0xff00 broadcast > 255.255.255.255 media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > > It still can't get an ip if I invoke service netif restart > > em0: flags=8843 metric 0 mtu > 1500 > options=81249b > ether xx:xx:xx:xx:xx:xx inet 0.0.0.0 netmask 0xff00 broadcast > 255.255.255.255 media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > > If I try running dhclient manually, > > [dhananjay:~] 1 % sudo dhclient em0 > dhclient already running, pid: 14305. > exiting. > [dhananjay:~] 1 % sudo kill 14305 > [dhananjay:~] % sudo dhclient em0 > DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 10 > DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 17 > DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 9 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > > For (2) For status no carrier > em0: flags=8c03 metric 0 mtu > 1500 > options=81249b > ether xx:xx:xx:xx:xx:xx media: Ethernet autoselect > status: no carrier > nd6 options=29 > > and dmesg keeps repeating > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > > > The only solution I have found so far is to just reboot the laptop and > then everything starts working. FWIW the router led never blinks (no > data transfers during DHCPDISCOVER). I am not sure how to debug this. > when I ran into this problem, I delete the IP address 0.0.0.0, kill dhclient and start a new dhclient. As we used fixed IP addresses for em0, the problem comes up only on wlan. Erich ___ 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"
programs like gdb core dump
Hi, I compiled me yesterday this system: 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r337285: When restarting fortune core dumps. When trying to load the core dump, gdb core dumps. The message is always: Bad system call (core dumped) Trying to install ports results in the same effect. Erich ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD has a politics problem
Hi, On Sun, 18 Mar 2018 06:43:47 +0100 "Meixner, Johannes" wrote: > You must have never been to Southern Germany or Austria. and Alaska. Erich ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD has a politics problem
Hi, On Sun, 18 Mar 2018 01:08:41 + Kate Dawson wrote: > Actually you sound like you come from under a bridge. You know... > "Trolling" it just shows your low education level. You could have checked maps.google.com. But you did not. Erich > > xxx > > On Sun, Mar 18, 2018 at 07:21:44AM +0800, Erich Dollansky wrote: > > Hi, > > > > just one word. I am from Kissing. My neighbours are from Fucking. I > > bet, the 'CoC' people will discriminate me and my neighbours now. > > > > Erich > > ___ > > freebsd-advoc...@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-advocacy > > To unsubscribe, send any mail to > > "freebsd-advocacy-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD has a politics problem
Hi, just one word. I am from Kissing. My neighbours are from Fucking. I bet, the 'CoC' people will discriminate me and my neighbours now. Erich ___ 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 CPU design flaw - FreeBSD affected?
Hi, On Thu, 4 Jan 2018 15:33:46 +0100 Stefan Esser wrote: > Am 04.01.18 um 12:56 schrieb Darren Reed: > > On 4/01/2018 11:51 AM, Mark Heily wrote: > >> On Jan 2, 2018 19:05, "Warner Losh" wrote: > >> > >> The register article says the specifics are under embargo still. > >> That would make it hard for anybody working with Intel to comment > >> publicly on the flaw and any mitigations that may be underway. It > >> would be unwise to assume that all the details are out until the > >> embargo lifts. > >> > >> > >> Details of the flaws are now published at: > >> > >> https://meltdownattack.com > > > > The web page has both: meltdown and spectre. > > Most people are only talking about meltdown which doesn't hit AMD. > > spectre impacts *both* Intel and AMD. > > > > SuSE are making available a microcode patch for AMD 17h processors > > that disables branch prediction: > > > > https://lists.opensuse.org/opensuse-security-announce/2018-01/msg4.html > > > > Disabling branch prediction will have a very noticeable effect on > execution speed in general (while split page tables only affect > programs that perform system calls at a high frequency). > > I have not fully read the Meltdown and Spectre papers, yet, but I do > assume, that the attack at the branch prediction tries to counter > KASLR, which we do not support at all in FreeBSD. > > So, I guess, we do not have to bother with disabling of branch > prediction in FreeBSD for the time being? > an attack on KASLR will not work, but any other attack will be get data from the kernel out. So, FreeBSD is affected but not by the attacks which will work on the other operating systems. Information still can be extracted. Erich ___ 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 names
Hi, On Thu, 14 Dec 2017 00:51:54 -0500 Allan Jude wrote: > On 12/14/2017 00:47, blubee blubeeme wrote: > > When you boot into FreeBSD and you can select kernels, there's only > > 2 options: > > default and kernel.old > > > > Is there a way to have better output and support multiple kernels > > without having to login to the system and running uname -v or > > something like that? > > > > Would it be possible to add options for more kernels from that boot > > menu? ___ > > 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" > > The list is controlled by the /boot/loader.conf variable kernels= > which defaults to "kernel kernel.old" > > I have a patch almost ready to land that will search all > subdirectories of /boot for a file named 'kernel' and add the names > of those directories to the list, such that the list will basically > be autogenerated. > > It currently contains too much copy/pasted code, and I just need to > clean it up a bit: https://reviews.freebsd.org/D11886 > > It was originally designed as part of my contributions towards > packaged base, where pkg will keep the last N (default to 5 I think) > kernel packages you have installed around, incase an upgrade goes bad. > > This feature will work on any filesystem supported by the loader. > this is a cool feature. Testing will become a lot easier then. Erich ___ 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: HEADS UP: caution required with updates using custom kernels
Hi, On Thu, 23 Jun 2016 21:07:51 + Brooks Davis wrote: > Kernel config minimalists and those running aarch64 and riscv systems > will want to head this UPDATING message. > > In practice, if you're fairly up to date, doing installworld before > installkernel will also work (I've tested that case from ALPHA4), but > is always somewhat risky. > there is another scenario in which you will use a word starting with an f followed by three letters. I did a normal update, compiled a custom kernel but did not re-compile my own application. As the application is required for the start of the machine, I was left with a system which could not be used. So, downgrading it, recompile the kernel with the compatibility option, compile the program and then it should work again is the way. Erich > -- Brooks > > - Forwarded message from Brooks Davis - > > Date: Thu, 23 Jun 2016 21:02:05 + (UTC) > From: Brooks Davis > To: src-committ...@freebsd.org, svn-src-...@freebsd.org, > svn-src-h...@freebsd.org > Subject: svn commit: r302152 - head > > Author: brooks > Date: Thu Jun 23 21:02:05 2016 > New Revision: 302152 > URL: https://svnweb.freebsd.org/changeset/base/302152 > > Log: > Add an UPDATING entry for the pipe() -> pipe2() transition. > > Approved by:re (gjb) > Sponsored by: DARPA, AFRL > > Modified: > head/UPDATING > > Modified: head/UPDATING > == > --- head/UPDATING Thu Jun 23 20:59:13 2016(r302151) > +++ head/UPDATING Thu Jun 23 21:02:05 2016(r302152) > @@ -31,6 +31,14 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 11 > disable the most expensive debugging functionality run > "ln -s 'abort:false,junk:false' /etc/malloc.conf".) > > +20160622: > + The the libc stub for the pipe(2) system call has been > replaced with > + a wrapper which calls the pipe2(2) system call and the > pipe(2) is now > + only implemented by the kernels which include "options > + FREEBSD10_COMPAT" in their config file (this is the default). Shouldn't it read 'COMPAT_FREEBSD10'? Erich ___ 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"
Compiling 11 on a Raspberry B+ 2 failes
Hi, I am trying to compile HEAD on a Raspberry and get always the following error. Of course, compiling revision 302017 on amd64 works. Erich Last Changed Rev: 301974 /usr/src/lib/csu/arm/crt1.c:(.text+0xb4): relocation truncated to fit: R_ARM_CALL against symbol `atexit' defined in .text section in /usr/lib/libc.a(atexit.o) /usr/src/lib/csu/arm/crt1.c:(.text+0xbc): relocation truncated to fit: R_ARM_CALL against symbol `_init_tls' defined in .text section in /usr/lib/libc.a(tls.o) /usr/src/lib/csu/arm/crt1.c:(.text+0xcc): relocation truncated to fit: R_ARM_CALL against symbol `atexit' defined in .text section in /usr/lib/libc.a(atexit.o) /usr/src/lib/csu/arm/crt1.c:(.text+0x174): relocation truncated to fit: R_ARM_CALL against symbol `exit' defined in .text section in /usr/lib/libc.a(exit.o) /usr/lib/crt1.o: In function `finalizer': /usr/src/lib/csu/arm/crt1.c:(.text+0x1ec): relocation truncated to fit: R_ARM_JUMP24 against symbol `_fini' defined in .fini section in /usr/lib/crti.o c++: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. bmake[4]: stopped in /usr/src.head/usr.bin/clang/clang *** Error code 1 Stop. bmake[3]: stopped in /usr/src.head/usr.bin/clang *** Error code 1 Stop. bmake[2]: stopped in /usr/src.head *** Error code 1 Stop. bmake[1]: stopped in /usr/src.head *** Error code 1 Stop. make: stopped in /usr/src.head [raspberry2]~/System (root) > ___ freebsd-...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
how to avoid warning: use of old-style cast [-Wold-style-cast]
Hi, when compiling on FreeBSD 11, I get some warnings as mentioned in the subject. What is the recommended way to avoid them? Some examples are: FIONREAD or SIG_IGN. The machine: FreeBSD raspberry2.alogt.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r291495: Tue Dec 1 09:13:20 UTC 2015 r...@releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/RPI2 arm Should we edit the include files? Any other ideas? Erich ___ 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: how do I downgrade from 11-current to 10-stable
Hi, On Sun, 31 May 2015 10:01:48 +0200 Fabian Keil wrote: > Erich Dollansky wrote: > > > On Sat, 30 May 2015 05:52:56 -0400 > > Aryeh Friedman wrote: > > > > > My desktop machine is 11-current and I want to down grade it to > > > 10-stable how do I do this without needing a reinstall? > > > > > > > I did this several times from sources. Be aware of one problem which > > could be fatal. If you created a encrypted partition with GELI and > > you downgrade, the older version might not be able to handle the > > encryption of the newer version. This is not mentioned in the > > documentation. > > The "[h]ighest GELI metadata version supported by the given > FreeBSD version" is documented in geli(8)'s history section. > it happened to me just shortly after 10 was released, that I tried to read a GELI partition with 9.0 which is supposed to work according to the manual but did not work for me. After installing 10 on the affected machine, everything worked. After seeing some notes on the page of my favorit search engine that this is known, I did not bother to do anything else. Should I check when I have time if this is still the case with 10.1? Erich ___ 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: how do I downgrade from 11-current to 10-stable
Hi, On Sat, 30 May 2015 05:52:56 -0400 Aryeh Friedman wrote: > My desktop machine is 11-current and I want to down grade it to > 10-stable how do I do this without needing a reinstall? > I did this several times from sources. Be aware of one problem which could be fatal. If you created a encrypted partition with GELI and you downgrade, the older version might not be able to handle the encryption of the newer version. This is not mentioned in the documentation. There might be also a catch with the mix of kernel/world. To avoid problems there, I ran both the installation of kernel and the world in one go. Erich ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
Hi, On Fri, 15 Aug 2014 12:01:30 -0700 Craig Rodrigues wrote: > On Wed, Aug 13, 2014 at 6:34 PM, Russell L. Carter > wrote: > > > One complaint I have about the FreeBSD project, is that the core > project contributors and developers rely too much on > e-mail for communication. This certainly works, and I use it too, but > new and casual users getting into FreeBSD > may get lost in the maze of FreeBSD mailing lists. It would be nice > if more of the core project contributors mailing lists have two advantages I would not like to miss. A) people can create their own archive and use it when they are offline B) Google & Co. offer good search tools to search the online archives > used the web forums ( http://forums.freebsd.org ), since stuff like I also noticed while travelling that some locations block the forum. Ok, it is rare. > that shows up nicely in web searches, and it is easier This is also true for the e-mails. Erich ___ 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 laptop compatibility list web page?
Hi, On Thu, 2 Oct 2014 01:48:39 -0700 Craig Rodrigues wrote: > Hi, > > I e-mailed Lukas Ertl about I think that you to the wrong URL. The university of vienna is here: http://www.univie.ac.at Erich ___ 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: Should we make WITHOUT_LIB32=yes the default for 11-RELEASE?
Hi, On Mon, 5 May 2014 22:07:06 -0400 Adam McDougall wrote: > On most amd64 systems I run, I usually set WITHOUT_LIB32=yes > in /etc/src.conf because I don't need them. This weekend I did a > stock install on an older AMD64 Core 2 Duo minipc and a buildworld of > 10-STABLE took almost two hours with LIB32 and CLANG since much of it > gets compiled twice. > > Is it time to deprecate LIB32 in -current for 11-RELEASE? I realize this is a good idea. Just document it properly. So everybody can still use it. Erich ___ 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: need info about newcons in jails
Hi, On Sat, 03 May 2014 07:15:14 -0400 Fbsd8 wrote: > Hello list. > > Looking for information about using newcons as the terminal driver in > xorg for desktop in a jail. > > Can only find this https://wiki.freebsd.org/Newcons > > Has anybody gotten it to work in a jail? I just used my FreeBSD 10 machine to test this. It works as expected. Erich ___ 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: When to rebuild world?
Hi, On Wed, 9 Apr 2014 06:43:36 +0530 (IST) Saju Ravindran Pillai wrote: > > Hello, I have just started tracking freebsd-current on a spare > machine. I am going through my first buildworld to update from > -stable to -current. > > Do I need to buildworld everytime I 'svn update' (atleast weekly). Or > will src/UPDATING tell me when a buildworld is actually needed? > UPDATING tells you nothing about the parts which got updated. If you want to save time, you would have to check which files are updated. As it is rare that only kernel files are updated, I always compile both the world and the kernel. Erich ___ 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: IXP700 AHCI fails to initialize
Hi, ok, I do not know of a working solution. But something like this happened to me too. I simply could not get newer FreeBSD versions working on old hardware. I have had to stick then with 7 until a lightning put an end to the affected machine. You still have one other chance. Try 9. My strategy in upgrading is also very simple. When I get a new machine, I install CURRENT and stick with the branch it will become later until this branch is not supported anymore. It saved me a lot of hassles as I normally have to do just one big version jump if the machine gets real old I have have to switch version. Erich On Sat, 1 Mar 2014 22:00:52 +0400 Yuriy Taraday wrote: > Hello. > > I currently have FreeBSD 8.3 on my home server and it works fine but > it's time to upgrade at last (new ath and new ipfw especially allure > me). I've decided to go straight to 10.0 and reinstall system from > scratch to purge all legacy unrelated configs and other stuff. > > The problem I faced is as follows. I have a (rather old) motherboard > with integrated SATA controller that presents in the OS as IXP700. In > 8.3 it works fine. I have 2 disks attached to it: one with all my > data and another one destined to be new system disk. I also have one > IDE disk installed that is currently used as system disk. > > When I booted from USB stick with 10.0, I couldn't see any SATA disks > in the system. I dug into dmesg and found this: > http://pastebin.com/wv2A0MUE As it seems AHCI controller or disks are > not responding to commands and timeouts eventually. > > A friend suggested to try CURRENT image. I went > with FreeBSD-11.0-CURRENT-amd64-VT-20140222-r262336-mini-memstick.img > and got almost the same error: http://pastebin.com/0iGaSWUD > The error repeats and never stops (looks like CURRENT images have > different config) but it is essentially the same. > > I've googled the problem but found only notes about how IXP700 is > really bad and pointers that cabling might be the problem. But I have > absolutely no problems with 8.3, so it looks like some regression > during further development (shift to CAM, maybe?). > > Please help me to identify and fix the problem. > ___ 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 10.0-RC5 Now Available
Hi, I upgraded this morning to FreeBSD X220.alogt.com 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #7 r260489: Fri Jan 10 08:25:55 WITA 2014 er...@x220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 just to find out that the mouse is not working under X anymore. The ports are from revision 336079. I have an X220. Neither the internal stick nor the external USB connected Logitech Trackman work. Both work outside X. X logs these mouse related messages: [ 315.926] (==) intel(0): Silken mouse enabled [ 316.960] (II) config/hal: Adding input device Trackball [ 316.960] (II) LoadModule: "mouse" [ 316.961] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 316.977] (II) Module mouse: vendor="X.Org Foundation" [ 316.977]compiled for 1.12.4, module version = 1.9.0 [ 316.977]Module class: X.Org XInput Driver [ 316.977]ABI class: X.Org XInput driver, version 16.0 [ 316.977] (II) Using input driver 'mouse' for 'Trackball' [ 316.977] (**) Trackball: always reports core events [ 316.977] (**) Option "Device" "/dev/ums0" [ 316.977] (==) Trackball: Protocol: "Auto" [ 316.977] (**) Trackball: always reports core events [ 316.977] (EE) xf86OpenSerial: Cannot open device /dev/ums0 Device busy. [ 316.977] (EE) Trackball: cannot open input device [ 316.977] (EE) PreInit returned 2 for "Trackball" [ 316.977] (II) UnloadModule: "mouse" [ 316.991] (II) config/hal: Adding input device PS/2 Mouse [ 316.991] (II) Using input driver 'mouse' for 'PS/2 Mouse' [ 316.991] (**) PS/2 Mouse: always reports core events [ 316.991] (**) Option "Device" "/dev/psm0" [ 316.991] (==) PS/2 Mouse: Protocol: "Auto" [ 316.991] (**) PS/2 Mouse: always reports core events [ 316.991] (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. [ 316.991] (EE) PS/2 Mouse: cannot open input device [ 316.991] (EE) PreInit returned 2 for "PS/2 Mouse" [ 316.991] (II) UnloadModule: "mouse" This are the X message I get when running X on an older release candidate: [ 111.171] (II) config/hal: Adding input device PS/2 Mouse [ 111.171] (II) LoadModule: "mouse" [ 111.171] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so [ 111.181] (II) Module mouse: vendor="X.Org Foundation" [ 111.181]compiled for 1.12.4, module version = 1.9.0 [ 111.181]Module class: X.Org XInput Driver [ 111.181]ABI class: X.Org XInput driver, version 16.0 [ 111.181] (II) Using input driver 'mouse' for 'PS/2 Mouse' [ 111.181] (**) PS/2 Mouse: always reports core events [ 111.181] (**) Option "Device" "/dev/sysmouse" [ 111.181] (==) PS/2 Mouse: Protocol: "Auto" [ 111.181] (**) PS/2 Mouse: always reports core events [ 111.181] (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 [ 111.181] (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 [ 111.181] (**) PS/2 Mouse: Buttons: 5 [ 111.181] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/psm_0" [ 111.181] (II) XINPUT: Adding extended input device "PS/2 Mouse" (type: MOUSE, id 7) [ 111.181] (**) PS/2 Mouse: (accel) keeping acceleration scheme 1 [ 111.181] (**) PS/2 Mouse: (accel) acceleration profile 0 [ 111.181] (**) PS/2 Mouse: (accel) acceleration factor: 2.000 [ 111.181] (**) PS/2 Mouse: (accel) acceleration threshold: 4 [ 111.181] (II) PS/2 Mouse: SetupAuto: hw.iftype is 4, hw.model is 0 [ 111.182] (II) PS/2 Mouse: SetupAuto: protocol is SysMouse The same X worked perfectly with any FreeBSD 10 since BETA1. When I change xorg.conf and disable moused, I am able to get the internal mouse (stick) working but not the external one. The external mouse is recognised by the system when disconnected and reconnected but not by X. It also works outside X. I will update the ports tree tonight or tomorrow morning to see what will happen then. Erich On Thu, 9 Jan 2014 11:18:18 -0500 Glen Barber wrote: > > Changes between -RC4 and -RC5 include: > > o Fix an IPv4 multicast regression. > > o Fixes OpenSSL for CVE-2013-4353, CVE-2013-6449, CVE-2013-6450. > > o Revert a change to the kinfo_file structure to preserve ABI. > > o Fix a race condition which could prevent the file descriptor table > from being properly updated. > ___ 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: 10-RC2 current wireless link aggregation not working correctly
Hi, On Tue, 17 Dec 2013 17:02:03 -0800 Xin Li wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 12/17/13 09:34, Allan Jude wrote: > > If I am am understanding correctly, Dan and Nikolai say that just > > running 'ifconfig' brings the lagg back to life. Why would that > > make a difference at all? Running ifconfig with no parameters > > shouldn't be changing anything. > > I don't really believe these claim. it does not work with iwn and em. > > I had similar issue in the past and found an 'arp -a -d' would "fix" It also does not work. The machine is running FreeBSD 10.0 RC2. Erich ___ 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: Issues in compiling apache server on one machine and transfer to second
Hi, On Tue, 12 Nov 2013 13:54:25 +0530 swapnil vaidya wrote: > Hi All, > I have 2 linux machine. you might be on the wrong mailing list. This here is for FreeBSD. > I have compiled apache 2.4.6 on one of the linux machine with > following commands: > ./configure --prefix=/usr/apache--with-ssl=/usr/local/ssl --enable-ssl > --enable-modules="all" --enable-mods-shared="most" > make > make install > > This has installed apache on this machine and it works fine. > However when i copy this apache (where it got installed) folder on > other linux machine. > I am getting following error while starting httpd with following > commad: command: > httpd -k start > > error: > > /httpd: symbol lookup error: /usr/papache/lib/libapr-1.so.0: undefined > symbol: dlopen > > Can you please help me to understand what is going wrong. It looks really strange to me. Erich ___ 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: svn error during 'make buildkernel'?
Hi, On Sat, 3 Aug 2013 22:04:56 -0400 Glen Barber wrote: > On Sun, Aug 04, 2013 at 08:10:09AM +0800, Erich Dollansky wrote: > > doesn't this show again that svn came a bit early? > > No, it shows that people do not keep their third-party software up to > date. you want to say, that it is true what Windows people say is true, that Linus/Unix people do not work with their machines but are busy compiling their kernel? I want to work with my computer. I also want to be able to do updates of the kernel alone when I read here of a fix in the kernel that bugs me just as it was possible with cvs. I hope We all can soon do this again. Erich > > Glen > ___ 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: svn error during 'make buildkernel'?
Hi, On Sat, 3 Aug 2013 15:17:02 -0700 Steve Kargl wrote: > On Sat, Aug 03, 2013 at 05:43:13PM -0400, Glen Barber wrote: > > On Sat, Aug 03, 2013 at 02:30:23PM -0700, Steve Kargl wrote: > > > On Sat, Aug 03, 2013 at 05:08:58PM -0400, Glen Barber wrote: > > > > On Sat, Aug 03, 2013 at 02:03:49PM -0700, Steve Kargl wrote: > > > > > I updated my /usr/src with subversion from ports: > > > > > > > > > > % pkg info | grep subver > > > > > subversion-1.7.9_1 Version control system > > > > > > > > > > 'make buildworld' completed as expected. 'make buildkernel' > > > > > seems to complete, but I'm seeing > > > > > > > > > > :> hack.c > > > > > cc -shared -nostdlib hack.c -o hack.So > > > > > rm -f hack.c > > > > > MAKE=make sh /usr/src/sys/conf/newvers.sh MOBILE > > > > > svn: E155036: The working copy at '/usr/src' > > > > > is too old (format 29) to work with client version '1.8.0 > > > > > (r1490375)' (expects format 31). You need to upgrade the > > > > > working copy first. > > > > > > > > > > > > > > Why is svn being run during 'make buildkernel'? More > > > > > importantly, why is the freshly built svn in /usr/obj being > > > > > invoked when it has not previously been installed and > > > > > so /usr/src may indeed be in a older, yet valid, format? > > > > > > > > > > > > > src/sys/conf/newvers.sh sets the svn revision, which is printed > > > > by uname(1). > > > > > > > > devel/subversion is at version 1.8.x, so you should upgrade your > > > > installed port. Or you can use /usr/bin/svnlite directly, and > > > > run: > > > > > > > > # /usr/bin/svnlite upgrade /usr/src > > > > > > > > > > Thanks. > > > > > > Looks like an entry in /usr/src/UPDATING is missing if > > > /usr/bin/svn* is forcing an obsolscence of a functioning > > > installed port. > > > > > > > The port was at 1.8.x before I added the additional lookup of > > svnlite to the script. > > My installed port was at 1.7.9. I can't find anywhere that > states that one must immediately upgrade to a new version > when a port's maintainer updates it. I've banged my head > against the ports collection dependency idiocy too often > to chase after every update. > > > There really is no need for UPDATING entry, since 1.7.9 is > > deprecated, and the behavior you have seen is not a fatal > > error with the buildkernel process. > > Installing a freshly built kernel when an ERROR message appears > within the last 10 lines of 'make buildkernel' seems like a > rather dumb thing do. > > > BTW, you should upgrade devel/subversion anyway, since there are > > security vulnerabilities. > > 1.7.9 works/worked fine for updating my /usr/src and my personal > svn repository. The change to use svnlite in newvers.sh should > have an entry in UPDATING to alert users that have a too old > svn port that they need to upgrade. I go as far to suggest that > that the script should look for svn in the path before it looks > for svnlite. > doesn't this show again that svn came a bit early? I wait only for the day, when two versions are needed. One for the ports, one for FreeBSD itself. Let us hope that this is all ironed out until 10 is released. I see the need to integrate svn into the base system. But this should not force to keep also the ports current. At least it should not confuse users when they keep the ports a bit older. I am aware of that we are talking of current here and I am aware of solutions for this problem. Erich ___ 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"
Problem with X, Intel integrated graphics and drm ...
Hi, since I upgraded away from FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r252491M: Wed Jul 3 08:45:23 CIT 2013 to FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #5 r253048M: Tue Jul 9 11:21:48 CIT 2013 er...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 I get this in Xorg.0.log which was not there before: FreeType: couldn't find encoding 'iso8859-13' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADC.TTF' [ 21736.957] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/ahronbd.ttf' [ 21737.124] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/ahronbd.ttf' [ 21758.395] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/amazonen.ttf' [ 21771.138] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/calibriz.ttf' [ 21783.650] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/frank.ttf' [ 21794.146] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/kunstshm.ttf' [ 21829.041] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/kunstshm.ttf' [ 21837.470] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/kunstshm.ttf' [ 21845.380] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/kunstshm.ttf' [ 21850.479] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/ahronbd.ttf' [ 21852.510] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADCI.TTF' [ 21852.520] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/lucon.ttf' [ 21855.945] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADCI.TTF' [ 21867.661] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADCI.TTF' [ 21885.381] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADCI.TTF' [ 21893.325] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADCI.TTF' [ 21893.325] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/lucon.ttf' [ 21902.660] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/palabi.ttf' [ 21906.663] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/palabi.ttf' [ 21910.339] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/palabi.ttf' [ 21917.686] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADCI.TTF' [ 21917.687] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/lucon.ttf' [ 21927.186] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/WindowsFonts/MYRIADCI.TTF' [ 21927.186] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/lucon.ttf' [ 21932.510] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsaz.ttf' [ 21955.685] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsaz.ttf' [ 21961.984] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsaz.ttf' [ 21965.813] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsai.ttf' [ 21970.656] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 21994.783] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 21999.138] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22002.488] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22005.670] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22007.834] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22009.677] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22011.825] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22014.092] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22016.646] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22019.186] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsa.ttf' [ 22021.553] FreeType: couldn't find encoding 'ascii-0' for '/usr/local/lib/X11/fonts/Windows-7-Fonts/angsai.ttf' [ 22024.
Re: Crashes with current on X220
Hi, On Sat, 6 Jul 2013 21:50:20 -0700 Adrian Chadd wrote: > Can you try installing some 10-amd64 snapshots between then and now, > and see roughly when it was introduced? I tried to upgrade my machine since March with the same result. But .. > > There's been a lot of ACPI changes over the last 6 months. It wouldn't > surprise me to find one or more of those messed things up. > ... I installed this FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r252491M: Wed Jul 3 08:45:23 CIT 2013 r...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 and the machine runs for nearly 2 days including X without these problems. With other words, you fixed it without knowing. Erich > > > -adrian > > On 5 July 2013 17:14, Erich Dollansky wrote: > > Hi, > > > > I updated my rock solid FreeBSD 10 installation from what was > > current this January to > > > > FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2 > > r252491M: Wed Jul 3 08:45:23 CIT 2013 > > r...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 > > > > I have since then frequent crashes. Nothing is seen on the screen. > > The mouse does not move, the caps lock key does not switch the > > light. I have restarted the machine last evening without doing > > anything else. No X, just plain FreeBSD before logging on. The > > machine might has done a fsck. The machine was frozen this morning. > > > > Does anybody else has this experience too? > > > > Erich > > ___ > > 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-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: Crashes with current on X220
Hi, On Sat, 06 Jul 2013 21:20:03 -0700 matt wrote: > On 07/06/13 19:40, Super Bisquit wrote: > > Look in the mailing list for "Fixing X220 Video the right way." > > > > Did I miss something? I'm not sure it's related at all...? you are right. But it did not crash anymore since this FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r252491M: Wed Jul 3 08:45:23 CIT 2013 r...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 There is a new problem, but it is minor and I will report only after testing with todays release. Erich > > > Matt > > ___ > 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Crashes with current on X220
Hi, I updated my rock solid FreeBSD 10 installation from what was current this January to FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r252491M: Wed Jul 3 08:45:23 CIT 2013 r...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 I have since then frequent crashes. Nothing is seen on the screen. The mouse does not move, the caps lock key does not switch the light. I have restarted the machine last evening without doing anything else. No X, just plain FreeBSD before logging on. The machine might has done a fsck. The machine was frozen this morning. Does anybody else has this experience too? Erich ___ 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: Fatal trap 3: breakpoint instruction fault
Hi, On Thu, 23 May 2013 10:25:24 +0700 Erich Dollansky wrote: > I updated my system over night. It suddenly reboots and I find some 20 > entries like this in /var/log/message: I have had to give up using this kernel after it crashed all the while. I will now doing updates of my kernel and report back when this problem disappeared. I did not see these messages any more in /var/log/messages. Erich > > May 23 10:05:28 X220 kernel: Fatal trap 3: breakpoint instruction > fault while in kernel mode > May 23 10:05:28 X220 kernel: cpuid = 0; apic id = 00 > May 23 10:05:28 X220 kernel: instruction pointer = > 0x20:0x80809f7e > May 23 10:05:28 X220 kernel: stack pointer= > 0x28:0xff82336de7c0 > May 23 10:05:28 X220 kernel: frame pointer= > 0x28:0xff82336de7e0 > May 23 10:05:28 X220 kernel: code segment = base 0x0, > limit 0xf, type 0x1b > May 23 10:05:28 X220 kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 > May 23 10:05:28 X220 kernel: processor eflags = IOPL = 0 > May 23 10:05:28 X220 kernel: current process = 2043 (chrome) > May 23 10:05:28 X220 kernel: trap number = 3 > May 23 10:05:28 X220 kernel: > panic: breakpoint instruction fault > May 23 10:05:28 X220 kernel: cpuid = 0 > May 23 10:05:28 X220 kernel: KDB: enter: panic > May 23 10:05:28 X220 kernel: > May 23 10:05:28 X220 kernel: > > All messages have chrome as the current process but different values > for IP and SP. > > uname -a says: > > FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #24 > r250918: Thu May 23 09:00:07 WIT 2013 > er...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 > > Is this a known problem? > > All I could find at the Internet is a bit old and not related to > chrome at all. > > Erich > ___ > 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-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: Fatal trap 3: breakpoint instruction fault
Hi, On Thu, 23 May 2013 07:23:33 +0300 Konstantin Belousov wrote: > On Thu, May 23, 2013 at 10:25:24AM +0700, Erich Dollansky wrote: > > uname -a says: > > > > FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #24 > > r250918: Thu May 23 09:00:07 WIT 2013 > > er...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 > Do you have ddb compiled in ? If yes, did you used it before the did you mean if ddb support is compiled in? Yes, the support is compiled in. Erich ___ 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: Fatal trap 3: breakpoint instruction fault
Hi, On Thu, 23 May 2013 07:23:33 +0300 Konstantin Belousov wrote: > On Thu, May 23, 2013 at 10:25:24AM +0700, Erich Dollansky wrote: > > Hi, > > > > I updated my system over night. It suddenly reboots and I find some > > 20 entries like this in /var/log/message: > > > > May 23 10:05:28 X220 kernel: Fatal trap 3: breakpoint instruction > > fault while in kernel mode > > May 23 10:05:28 X220 kernel: cpuid = 0; apic id = 00 > > May 23 10:05:28 X220 kernel: instruction pointer= > > 0x20:0x80809f7e > > May 23 10:05:28 X220 kernel: stack pointer = > > 0x28:0xff82336de7c0 > > May 23 10:05:28 X220 kernel: frame pointer = > > 0x28:0xff82336de7e0 > > May 23 10:05:28 X220 kernel: code segment = base 0x0, > > limit 0xf, type 0x1b > > May 23 10:05:28 X220 kernel: = DPL 0, pres 1, long 1, def32 0, gran > > 1 May 23 10:05:28 X220 kernel: processor eflags = IOPL = 0 > > May 23 10:05:28 X220 kernel: current process = 2043 (chrome) > > May 23 10:05:28 X220 kernel: trap number = 3 > > May 23 10:05:28 X220 kernel: > > panic: breakpoint instruction fault > > May 23 10:05:28 X220 kernel: cpuid = 0 > > May 23 10:05:28 X220 kernel: KDB: enter: panic > > May 23 10:05:28 X220 kernel: > > May 23 10:05:28 X220 kernel: > > > > All messages have chrome as the current process but different values > > for IP and SP. > > > > uname -a says: > > > > FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #24 > > r250918: Thu May 23 09:00:07 WIT 2013 > > er...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 > Do you have ddb compiled in ? If yes, did you used it before the > breakpoint trap was reported ? to be honest, I do not know if ddb is compiled in. The main problem would be that this is currently only machine. It also has no serial links. Just USB and Ethernet. > > Did you used gdb or strace in the usermode before the trap ? > No debugger of any kind was running. Let me tell you what I normally do when I start this machine. It has an Intel i7 CPU and as such it uses KMS. - log-on as a normal user. - start X - start a few xterms - start wireless network in one of them - start chrome to log-on onto the LAN of the client - start claws mail - start arora I think that I did not come further as I remember to get a message from my daughter as the last activity of the machine in chrome. The screen went black then and the machine started to reboot. I think that there is not much helpful information I could give. I work since then much longer without any problems. Erich > > > > Is this a known problem? > > > > All I could find at the Internet is a bit old and not related to > > chrome at all. > > > > Erich > > ___ > > 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Fatal trap 3: breakpoint instruction fault
Hi, I updated my system over night. It suddenly reboots and I find some 20 entries like this in /var/log/message: May 23 10:05:28 X220 kernel: Fatal trap 3: breakpoint instruction fault while in kernel mode May 23 10:05:28 X220 kernel: cpuid = 0; apic id = 00 May 23 10:05:28 X220 kernel: instruction pointer= 0x20:0x80809f7e May 23 10:05:28 X220 kernel: stack pointer = 0x28:0xff82336de7c0 May 23 10:05:28 X220 kernel: frame pointer = 0x28:0xff82336de7e0 May 23 10:05:28 X220 kernel: code segment = base 0x0, limit 0xf, type 0x1b May 23 10:05:28 X220 kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 May 23 10:05:28 X220 kernel: processor eflags = IOPL = 0 May 23 10:05:28 X220 kernel: current process = 2043 (chrome) May 23 10:05:28 X220 kernel: trap number = 3 May 23 10:05:28 X220 kernel: panic: breakpoint instruction fault May 23 10:05:28 X220 kernel: cpuid = 0 May 23 10:05:28 X220 kernel: KDB: enter: panic May 23 10:05:28 X220 kernel: May 23 10:05:28 X220 kernel: All messages have chrome as the current process but different values for IP and SP. uname -a says: FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #24 r250918: Thu May 23 09:00:07 WIT 2013 er...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 Is this a known problem? All I could find at the Internet is a bit old and not related to chrome at all. Erich ___ 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: Computers Won't Turn Off or Reboot
Hi, On Tue, 23 Apr 2013 15:50:58 -0700 Kevin Oberman wrote: > On Tue, Apr 23, 2013 at 3:26 AM, Artyom Mirgorodskiy < > artyom.mirgorod...@gmail.com> wrote: > > > I have similar problem when start X server with intel driver. > > > > On Monday 22 April 2013 18:50:37 Shawn Webb wrote: > > > Hey All, > > > > > > I'm on r249745 on amd64. For the past few weeks, my box hasn't > > > been able > > to > > > completely turn off or reboot. The box sits at the console at the > > > "All buffers synced" message. I'm running root on ZFS in a > > > two-disk mirror setup. No kernel panics or dumps or anything. > > > > > > Let me know if there's anything I can do or more information you > > > need. > > > > > > Thanks, > > > > > > Shawn > > > > > > > I am seeing the same thing on my 9.1-STABLE box. It was running a > kernel from Jan. 27, but after updating on April 16 (r249571M), I > can't get it to shut down. I am running KMS, so it's hard to tell > just where it is hanging and a GENERIC kernel patched for the new > kernel fusefs implementation found in head. The system shuts down > cleanly if X has not started and also if shutdown is done soon after > it is started. I suspect that the issue only shows up if I write to > an NTFS volume. The hang occurs whether or not the fuse systems have > been unmounted. > > System is an amd64 kernel on a Core5i-2520M ThinkPad T520. 4G memory. > Generic kernel EXCEPT that I am running the kernel fusefs > implementation from head. > > Do any of the other reporters of this use fuse? I do not use any Windows related stuff an see the same behaviour on 10. Erich ___ 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: Computers Won't Turn Off or Reboot
Hi, On Mon, 22 Apr 2013 15:56:53 -0700 Adrian Chadd wrote: > CAn you trace down a rough subversion commit id window between when it > worked and didn't work? > I reported this for a kernel compiled 13.03.13. It looks to me that the problem is there much longer. I also have an AMD machine with an older 10 from last summer. When both machines have been on the same version, the AMD machine never crashed but the Intel machine crashed very often on shutdown. Crash means that the screen went black and it did not respond to network and keyboard. The Intel machine never crashes for me when I do not start X. You know that after starting X the console does not come back on Intel machines. So, it is hard to tell what is going on except that the machine does not power off and does not respond. I know that this information is not very helpful. I am travelling most of the time and as long as I am travelling, I only have access to the Intel machine. Erich > > On 22 April 2013 15:50, Shawn Webb wrote: > > Hey All, > > > > I'm on r249745 on amd64. For the past few weeks, my box hasn't been > > able to completely turn off or reboot. The box sits at the console > > at the "All buffers synced" message. I'm running root on ZFS in a > > two-disk mirror setup. No kernel panics or dumps or anything. > > > > Let me know if there's anything I can do or more information you > > need. > > > > Thanks, > > > > Shawn > > ___ > > 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-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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
X220 note: crash at shutdown -p now
Hi, I noticed frequent crashes when i power off my X220. I got used to it until I did some reboots without a single crash. I shut down the machine with shutdown -p now uname says: FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #23: Sat Feb 23 17:24:19 WIT 2013 er...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 I noticed that very often, the file /boot/loader.conf is empty when the machine is started again later. Is there a way I could help to find the source of the problem? Erich ___ 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: Question on building from sources.
Hi, On Sat, 30 Mar 2013 19:05:47 -0400 Super Bisquit wrote: > Okay. I already have 10.0 on the machine from a year ago. What I have this sounds a bit old. > come up against is CLANG_IS_CC ="no" when trying to build run(4). > What is the current state of clang as cc compiler on ppc32? <-- This > needs to be fixed first. I do not use FreeBSD on any thing else but AMD64. > Thanks for the replies and sorry for any noise. Isn't the noise the idea behind this mailing list? Erich ___ 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: Question on building from sources.
Hi, On Fri, 29 Mar 2013 22:03:11 -0400 Glen Barber wrote: > On Fri, Mar 29, 2013 at 09:31:12PM -0400, Super Bisquit wrote: > > I have my QuickSilver and no internet connection. I have a few > > questions. 1. Do I download the latest for PowerPC(32bit) and then > > download the sources according to the Makefile. > > For ports, yes, you will to do 'make fetch' or 'make fetch-recursive' > for third-party software you want to install. > yes. > > 3. Has anyone else done this before? If yes, then what were your > > results? > > > > It is painful. My suggestion is to identify everything you absolutely > need, and do from a separate machine with internet access: > I do this all the while as I have only random Internet connection. But I do this only for amd64. It works most of the time. Expect some returns to the machine with an Internet connection. > Note that if anything is missing, build will fail at compile time on > the internet-less machine. This should only be a problem for the ports. The sources can easily be downloaded in one go. Erich ___ 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: X220 loses keyboard when Logitech USB wireless adaptor is unplugged
Hi, On Mon, 25 Mar 2013 15:26:54 +0100 Andreas Nilsson wrote: > On Mon, Mar 25, 2013 at 3:24 PM, Erich Dollansky < > erichsfreebsdl...@alogt.com> wrote: > > > What does a 'usbconfig devlist' before and after unplugging show? > do you mean this? Before usbconfig dump_info ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, 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 (0mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (200mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (98mA) after: ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, 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 (0mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (200mA) Erich ___ 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: X220 loses keyboard when Logitech USB wireless adaptor is unplugged
Hi, On Mon, 25 Mar 2013 09:07:14 -0400 (EDT) Daniel Eischen wrote: > On Mon, 25 Mar 2013, Erich Dollansky wrote: > > > Hi, > > > > On Mon, 25 Mar 2013 19:21:05 +0700 > > Erich Dollansky wrote: > > > >> As you can see, I took the adaptor connected to ugne0.3 out. In > >> addition, the keyboard ukbd0 was disconnected too. When I put the > >> adaptor back in, the keyboard comes back too. As you can imagine, > >> it is a bit hard to unplug the built-in keyboard on a notebook. > >> > > the situation changes when I do not use X and KMS. I can do with the > > Logitech adaptor what I want but the keyboard stays connected. The > > moment I start X, it is back to the behaviour from above. > > Can you use, or are you using, moused? Tell X to use sysmouse. > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection > I did this and do not see a difference. The log file says: Mar 25 21:17:09 X220 kernel: ugen1.2: at usbus1 (disconnected) Mar 25 21:17:09 X220 kernel: ukbd0: at uhub1, port 3, addr 1 (disconnected) Mar 25 21:17:09 X220 kernel: ums0: at uhub1, port 3, addr 1 (disconnected) Mar 25 21:17:09 X220 kernel: uhid0: at uhub1, port 3, addr 1 (disconnected) Mar 25 21:17:25 X220 kernel: ugen1.2: at usbus1 Mar 25 21:17:25 X220 kernel: ukbd0: on usbus1 Mar 25 21:17:25 X220 kernel: kbd2 at ukbd0 Mar 25 21:17:25 X220 kernel: ums0: on usbus1 Mar 25 21:17:25 X220 kernel: ums0: 16 buttons and [XYZT] coordinates ID=2 Mar 25 21:17:25 X220 kernel: uhid0: on usbus1 Still, the keyboard ukdb0 gets disconnected together with the mouse. Erich ___ 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: X220 loses keyboard when Logitech USB wireless adaptor is unplugged
Hi, On Mon, 25 Mar 2013 19:21:05 +0700 Erich Dollansky wrote: > As you can see, I took the adaptor connected to ugne0.3 out. In > addition, the keyboard ukbd0 was disconnected too. When I put the > adaptor back in, the keyboard comes back too. As you can imagine, it > is a bit hard to unplug the built-in keyboard on a notebook. > the situation changes when I do not use X and KMS. I can do with the Logitech adaptor what I want but the keyboard stays connected. The moment I start X, it is back to the behaviour from above. Erich ___ 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"
X220 loses keyboard when Logitech USB wireless adaptor is unplugged
Hi, I just got this from /var/log/messages: Mar 25 19:12:01 X220 kernel: ugen0.3: at usbus0 (disconnected) Mar 25 19:12:01 X220 kernel: ukbd0: at uhub3, port 2, addr 3 (disconnected) Mar 25 19:12:01 X220 kernel: ums0: at uhub3, port 2, addr 3 (disconnected) Mar 25 19:12:01 X220 kernel: uhid0: at uhub3, port 2, addr 3 (disconnected) Mar 25 19:12:09 X220 kernel: ugen0.3: at usbus0 Mar 25 19:12:09 X220 kernel: ukbd0: on usbus0 Mar 25 19:12:09 X220 kernel: kbd2 at ukbd0 Mar 25 19:12:09 X220 kernel: ums0: on usbus0 Mar 25 19:12:09 X220 kernel: ums0: 16 buttons and [XYZT] coordinates ID=2 Mar 25 19:12:09 X220 kernel: uhid0: on usbus0 As you can see, I took the adaptor connected to ugne0.3 out. In addition, the keyboard ukbd0 was disconnected too. When I put the adaptor back in, the keyboard comes back too. As you can imagine, it is a bit hard to unplug the built-in keyboard on a notebook. uname -a says: FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #23: Sat Feb 23 17:24:19 WIT 2013 er...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 Any thing I could do to help fix this? Erich ___ 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: multi-homing in freebsd
Hi, On Sat, 9 Mar 2013 03:04:00 -0500 Yasir hussan wrote: > i just want to run multiple IPs for single network card in freebsd it should work with alias of ifconfig Erich > > On Sat, Mar 9, 2013 at 2:55 AM, Yasir hussan > wrote: > > > Hi, > > > > Does anyone know usage of multi-homing in freebsd, if YES kindly > > guid me how i can test it on my own PC. > > > > Thanks > > > ___ > 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-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: Fixing X220 Video The Right Way
Hi, On Wed, 27 Feb 2013 15:27:36 -0500 John Baldwin wrote: > On Wednesday, February 27, 2013 1:35:43 pm matt wrote: > > On 02/27/13 09:00, John Baldwin wrote: > > > If that is true, it's because your BIOS is lying. Do you have a > > > URL to your ASL lying around already? > > Too big for pastebin :( +500k > > > > https://docs.google.com/file/d/0B6YlMzJxarGbVnotLUdNWWNTVG8/edit?usp=sharing > > the X220 have a switchable GPU (e.g. it has built-in Intel graphics, it has. > but also has an Nvidia GPU or some such?). If so, I imagine that No, it does not. > PCI0.VID is the Intel graphics and PEG is the non-Intel. The output > of 'pciconf -lcv' would be useful to determine that. If both PCI > devices exist you shoudl have both acpi_video0 and acpi_video1. > However, it may be that the acpi_video driver doesn't cope well with > having multiple devices. > Erich PS Here is the output: hostb0@pci0:0:0:0: class=0x06 card=0x21da17aa chip=0x01048086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '2nd Generation Core Processor Family DRAM Controller' class = bridge subclass = HOST-PCI cap 09[e0] = vendor (length 12) Intel cap 0 version 1 vgapci0@pci0:0:2:0: class=0x03 card=0x21da17aa chip=0x01268086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '2nd Generation Core Processor Family Integrated Graphics Controller' class = display subclass = VGA cap 05[90] = MSI supports 1 message enabled with 1 message cap 01[d0] = powerspec 2 supports D0 D3 current D0 cap 13[a4] = PCI Advanced Features: FLR TP none0@pci0:0:22:0: class=0x078000 card=0x21da17aa chip=0x1c3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '6 Series/C200 Series Chipset Family MEI Controller' class = simple comms cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 05[8c] = MSI supports 1 message, 64 bit uart2@pci0:0:22:3: class=0x070002 card=0x21da17aa chip=0x1c3d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '6 Series/C200 Series Chipset Family KT Controller' class = simple comms subclass = UART cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit em0@pci0:0:25:0:class=0x02 card=0x21ce17aa chip=0x15028086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82579LM Gigabit Network Connection' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 13[e0] = PCI Advanced Features: FLR TP ehci0@pci0:0:26:0: class=0x0c0320 card=0x21da17aa chip=0x1c2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '6 Series/C200 Series Chipset Family USB Enhanced Host Controller' class = serial bus subclass = USB cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] = PCI Advanced Features: FLR TP hdac0@pci0:0:27:0: class=0x040300 card=0x21da17aa chip=0x1c208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '6 Series/C200 Series Chipset Family High Definition Audio Controller' class = multimedia subclass = HDA cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 05[60] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[70] = PCI-Express 1 root endpoint max data 128(128) FLR link x0(x0) ecap 0002[100] = VC 1 max VC1 ecap 0005[130] = Root Complex Link Declaration 1 pcib1@pci0:0:28:0: class=0x060400 card=0x21da17aa chip=0x1c108086 rev=0xb4 hdr=0x01 vendor = 'Intel Corporation' device = '6 Series/C200 Series Chipset Family PCI Express Root Port 1' class = bridge subclass = PCI-PCI cap 10[40] = PCI-Express 2 root port slot max data 128(128) link x0(x1) speed 0.0(5.0) cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0x21da17aa cap 01[a0] = powerspec 2 supports D0 D3 current D0 pcib2@pci0:0:28:1: class=0x060400 card=0x21da17aa chip=0x1c128086 rev=0xb4 hdr=0x01 vendor = 'Intel Corporation' device = '6 Series/C200 Series Chipset Family PCI Express Root Port 2' class = bridge subclass = PCI-PCI cap 10[40] = PCI-Express 2 root port slot max data 128(128) link x1(x1) speed 2.5(5.0) cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0x21da17aa cap 01[a0] = powerspec 2 supports D0 D3 current D0 pcib3@pci0:0:28:3: class=0x060400 card=0x21da17aa chip=0x1c168086 rev=0xb4 hdr=0x01 vendor = 'Intel Corporation' device = '6 Series/C200 Series Chipset Family PCI Express Root Port 4' class = bridge subclass = PCI-PCI cap 10[40] = PCI-Express 2 root port slot max data 128(128) link x0(x1) speed 0.0(5.0) cap 05[80] = MSI supports 1 message
Re: gpart, slice starts at 0
Hi, On Sun, 17 Feb 2013 09:11:48 -0700 (MST) Warren Block wrote: > On Sun, 17 Feb 2013, Erich Dollansky wrote: > > >>> gpart destroy -F da0 > >>> diskinfo da0 > >>> dd if=/dev/zero of=/dev/da0 bs=512 count=34 > >>> dd if=/dev/zero of=/dev/da0 bs=512 count=34 seek=312581774 > >> > >> Someone here on the lists (I unfortunately forget who) showed a > >> sneaky easier way to do this: > >> > >> gpart destroy -F da0 > >> gpart create -s gpt da0 > >> gpart destroy -F da0 > >> > > This did not make a difference. > > It's an easier way to destroy the backup table at the end of the > disk, whether one was there before or not, without having to > calculate the location. ok, so, I should keep this then. > > >>> gpart show -p da0 > >>> gpart create -s MBR da0 > >>> gpart add -t freebsd da0 > >>> gpart show -p da0 > >>> gpart show -p da0s1 > >>> gpart set -a active -i 1 da0 > >>> # > >>> # The following line always gives an error: > >>> # > >>> # gpart create -s BSD da0s1 > >> > >> 'destroy' is not recursive. It destroys the geom found on the > >> device given, but does not write to any geoms inside those geoms. > >> > > This is obvious. What surprises me is that create does not write a > > new and empty description to the disk. > > It does, but not being recursive, it does not destroy the geoms > inside the one given to the command (da0). You had: > >da0 (MBR) > da0s1 (bsdlabel) > > After the destroy, it became >da0 (null) > da0s1 (bsdlabel) It seems that we talk here about the same with very different words. The effect comes from the fact that the entries are always on the same location on a disk. The advantage is that repartitioning a disk stills leaves some room for recovery. > > This can happen with any of the setups where there are geoms inside > other geoms. > > >> The second part of your question, about da0 starting a block zero: > >> > >>> [X220]...Appl/Some Tools (root) > gpart show da0 > >>> => 63 312581745 da0 MBR (149G) > >>> 63 3125817451 freebsd [active] (149G) > >>> > >>> [X220]...Appl/Some Tools (root) > gpart show da0s1 > >>> =>0 312581745 da0s1 BSD (149G) > >>> 0 312581745 - free - (149G) > >> > >> That shows slice one starts at block 63, standard for MBR. The > >> space inside the slice (da0s1) starts at block 0 *of the slice*. > > > > This is a bit confusing for me but it does not really matter as > > long as the programs get it straight. > > This is again because of the geom inside a geom setup. The actual > start block is the start of the slice (block 63) plus the start of > the FreeBSD partition inside the slice (currently 0). When you > create FreeBSD partitions inside da0s1, they will have nonzero > offsets from the start of the slice. There are examples shown here: > http://forums.freebsd.org/showpost.php?p=206204&postcount=11 And I saw there how to overcome the alignment problems. It is so simple. Just understanding it was not so simple for me. Thanks! Erich > ___ > 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-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: gpart, slice starts at 0
Hi, On Sat, 16 Feb 2013 08:44:50 -0700 (MST) Warren Block wrote: > On Sat, 16 Feb 2013, Erich Dollansky wrote: > > > I did this to get a disk partitioned: > > > > #!/bin/tcsh > > Gah! > it is a generated script. > > gpart destroy -F da0 > > diskinfo da0 > > dd if=/dev/zero of=/dev/da0 bs=512 count=34 > > dd if=/dev/zero of=/dev/da0 bs=512 count=34 seek=312581774 > > Someone here on the lists (I unfortunately forget who) showed a > sneaky easier way to do this: > > gpart destroy -F da0 > gpart create -s gpt da0 > gpart destroy -F da0 > This did not make a difference. > > gpart show -p da0 > > gpart create -s MBR da0 > > gpart add -t freebsd da0 > > gpart show -p da0 > > gpart show -p da0s1 > > gpart set -a active -i 1 da0 > > # > > # The following line always gives an error: > > # > > # gpart create -s BSD da0s1 > > 'destroy' is not recursive. It destroys the geom found on the device > given, but does not write to any geoms inside those geoms. > This is obvious. What surprises me is that create does not write a new and empty description to the disk. > MBR/bsdlabel puts FreeBSD partitions inside MBR slices. > > So da0 has been erased, but the bsdlabel blocks for da0s1 are still > present. If you recreate da0, da0s1 will magically reappear. > This is what I struggeled with all the time. > Destroy the FreeBSD disklabel stuff in the slices first: >gpart destroy -F da0s1 And this was the solution. Thanks! > > Or instead, use GPT partitioning to avoid dealing with the problem of > one type of partitions inside a different type of partitions. GPT > makes disk partitioning a lot easier. I am bit tired of having to read handbooks/manuals whenever I get a new device. Out of this, I am currently writing a small program which allows me easy 'formatting' of the device. MBR is just one option the program has. I will publish it when it is really working as I want it to. It will take some time as I do this on the side only. > > The second part of your question, about da0 starting a block zero: > > > [X220]...Appl/Some Tools (root) > gpart show da0 > > => 63 312581745 da0 MBR (149G) > > 63 3125817451 freebsd [active] (149G) > > > > [X220]...Appl/Some Tools (root) > gpart show da0s1 > > =>0 312581745 da0s1 BSD (149G) > > 0 312581745 - free - (149G) > > That shows slice one starts at block 63, standard for MBR. The space > inside the slice (da0s1) starts at block 0 *of the slice*. This is a bit confusing for me but it does not really matter as long as the programs get it straight. Erich > ___ > 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-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: gpart, slice starts at 0
Hi, On Sat, 16 Feb 2013 14:51:22 +0700 Erich Dollansky wrote: > > I did this to get a disk partitioned: > > #!/bin/tcsh > ### > # > # File name: FormatSamsung160GB > # > # Description:This script formats a thumb drive connected as > da0 # > ### > # > gpart destroy -F da0 > diskinfo da0 > dd if=/dev/zero of=/dev/da0 bs=512 count=34 > dd if=/dev/zero of=/dev/da0 bs=512 count=34 seek=312581774 if I wipe out 100% of the disk here, it all works as expected. Can we assume that there is a problem in gpart? Erich > gpart show -p da0 > gpart create -s MBR da0 > gpart add -t freebsd da0 > gpart show -p da0 > gpart show -p da0s1 > gpart set -a active -i 1 da0 > # > # The following line always gives an error: > # > # gpart create -s BSD da0s1 > gpart bootcode -b /boot/mbr da0 > gpart bootcode -b /boot/boot da0s1 > gpart show -p da0 > gpart show -p da0s1 > gpart add -t freebsd-ufs -s 512MB -l Samsung160GBroot da0s1 > > The script results in this output: > > FormatSamsung160GB > da0 destroyed > da0 512 160041885696312581808 0 0 19457 > 255 63 34+0 records in > 34+0 records out > 17408 bytes transferred in 0.012732 secs (1367260 bytes/sec) > 34+0 records in > 34+0 records out > 17408 bytes transferred in 0.023717 secs (733983 bytes/sec) > gpart: No such geom: da0. > da0 created > da0s1 added > => 63 312581745da0 MBR (149G) > 63 312581745 da0s1 freebsd (149G) > > =>0 312581745 da0s1 BSD (149G) > 0 312581745 - free - (149G) > > active set on da0s1 > bootcode written to da0 > bootcode written to da0s1 > => 63 312581745da0 MBR (149G) > 63 312581745 da0s1 freebsd [active] (149G) > > =>0 312581745 da0s1 BSD (149G) > 0 312581745 - free - (149G) > > gpart: Invalid argument > [X220]...Appl/Some Tools (root) > gpart show da0 > => 63 312581745 da0 MBR (149G) > 63 3125817451 freebsd [active] (149G) > > [X220]...Appl/Some Tools (root) > gpart show da0s1 > =>0 312581745 da0s1 BSD (149G) > 0 312581745 - free - (149G) > > I have now two problems which I do not understand. First, why do I > need this line and why does it fail? > > gpart create -s BSD da0s1 > > Second, why does this slice start at 0? > > =>0 312581745 da0s1 BSD (149G) > 0 312581745 - free - (149G) > > I use this as an starting point: > > http://www.wonkity.com/~wblock/docs/html/disksetup.html > > It worked for me some time ago. > > Did I miss something very, very simple? > > Erich > ___ > 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
gpart, slice starts at 0
Hi, I did this to get a disk partitioned: #!/bin/tcsh ### # # File name:FormatSamsung160GB # # Description: This script formats a thumb drive connected as da0 # ### # gpart destroy -F da0 diskinfo da0 dd if=/dev/zero of=/dev/da0 bs=512 count=34 dd if=/dev/zero of=/dev/da0 bs=512 count=34 seek=312581774 gpart show -p da0 gpart create -s MBR da0 gpart add -t freebsd da0 gpart show -p da0 gpart show -p da0s1 gpart set -a active -i 1 da0 # # The following line always gives an error: # # gpart create -s BSD da0s1 gpart bootcode -b /boot/mbr da0 gpart bootcode -b /boot/boot da0s1 gpart show -p da0 gpart show -p da0s1 gpart add -t freebsd-ufs -s 512MB -l Samsung160GBroot da0s1 The script results in this output: FormatSamsung160GB da0 destroyed da0 512 160041885696312581808 0 0 19457 255 63 34+0 records in 34+0 records out 17408 bytes transferred in 0.012732 secs (1367260 bytes/sec) 34+0 records in 34+0 records out 17408 bytes transferred in 0.023717 secs (733983 bytes/sec) gpart: No such geom: da0. da0 created da0s1 added => 63 312581745da0 MBR (149G) 63 312581745 da0s1 freebsd (149G) =>0 312581745 da0s1 BSD (149G) 0 312581745 - free - (149G) active set on da0s1 bootcode written to da0 bootcode written to da0s1 => 63 312581745da0 MBR (149G) 63 312581745 da0s1 freebsd [active] (149G) =>0 312581745 da0s1 BSD (149G) 0 312581745 - free - (149G) gpart: Invalid argument [X220]...Appl/Some Tools (root) > gpart show da0 => 63 312581745 da0 MBR (149G) 63 3125817451 freebsd [active] (149G) [X220]...Appl/Some Tools (root) > gpart show da0s1 =>0 312581745 da0s1 BSD (149G) 0 312581745 - free - (149G) I have now two problems which I do not understand. First, why do I need this line and why does it fail? gpart create -s BSD da0s1 Second, why does this slice start at 0? =>0 312581745 da0s1 BSD (149G) 0 312581745 - free - (149G) I use this as an starting point: http://www.wonkity.com/~wblock/docs/html/disksetup.html It worked for me some time ago. Did I miss something very, very simple? Erich ___ 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: 7+ days of dogfood
Hi Erik, On Mon, 11 Feb 2013 12:43:17 +0100 Erik Cederstrand wrote: => Den 11/02/2013 kl. 00.38 skrev Erich Dollansky > : > > > On Sun, 10 Feb 2013 15:57:01 +0100 > > Erik Cederstrand wrote: > > > >> And as long as there is no automatic can taster doing quality > >> assurance of the produced cans, then foul cans will go unnoticed > >> until a dog pukes all over the carpet :-) > >> > > Isn't this the idea of HEAD? > > It's certainly not the idea of HEAD that everyone should experience > the same bugs, compile errors, runtime errors and even have old bugs > pop up again repeatedly. It may be the consequence of running HEAD, > but certainly not the idea. > ok, I agree that developers could react faster some times. But, isn't it more important that the errors are caught at all? > >> For this to change, we really need to catch up on years of neglect > >> in e.g. src/tools/regression/. I really applaud the people doing > >> the thankless job of changing this. > >> > > I do not believe that this all can be automated. > > I'm not saying that testing is all-or-nothing. OS testing is not > easy, and many tests are impractical or expensive if they require > real hardware in complicated setups. How do you reliably test an IEEE > 802.11s mesh implementation? Or scheduling on huge servers that are > too expensive to purchase? I think that is one of the reasons that > FreeBSD has not caught up on automated testing and continuous > integration. But regression tests are useful even though they don't > give 100% code coverage. Currently, you can't even "make test" in > src/tools/regression/ and run the tests that are there. Apart from > the compile-tests done by the tinderboxes, I'm not aware of any > coordinated effort to systematically do runtime or even performance > testing of FreeBSD. > So, the best is still if people like me are eating dog food and start complaining? Do not get me wrong here. I do not complain about the fact that there might be an error, I want to help poin-point the error with my complaint. Erich ___ 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: 7+ days of dogfood
Hi, On Mon, 11 Feb 2013 11:48:11 +0100 Fabian Keil wrote: > Steve Kargl wrote: > > > My conclusion: on at least my not-so-new laptop, FreeBSD-10 can > > be used in a desktop environment if one takes some care during the > > installation. > > I'm using CURRENT on my also-no-so-new laptop since FreeBSD 7 > (I think) and came to the same conclusion. > I did this during 6.x time but got stuck then with 6.x and never went back until last May/June. > It's unfortunate that the builworld time roughly trippled since > 2010 but I guess that's progress and a more powerful system > should fix it. I certainly welcome clang in general, though. > Trippled? Are you sure? I have the feeling it is much worse than this. Was it in 2009 when I could compile world in a few minutes on my quad core. The same machine takes now hours despite having more memory. I run currently my desktop and my notebook on 10. If I stick with my policy, I would stay with 10 until 12 would be available. On the other side, it feels so outdated not to have something like the most current version. Erich ___ 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: 7+ days of dogfood
Hi, On Sun, 10 Feb 2013 15:57:01 +0100 Erik Cederstrand wrote: > Den 10/02/2013 kl. 02.30 skrev Erich Dollansky > : > > > I am on dog food since last May/June. How should I phrase it? Every > > can tastes different. Most cans have a perfect taste but some cans > > are really off. > > And as long as there is no automatic can taster doing quality > assurance of the produced cans, then foul cans will go unnoticed > until a dog pukes all over the carpet :-) > Isn't this the idea of HEAD? > For this to change, we really need to catch up on years of neglect in > e.g. src/tools/regression/. I really applaud the people doing the > thankless job of changing this. > I do not believe that this all can be automated. Erich ___ 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: 7+ days of dogfood
Hi, On Sat, 9 Feb 2013 16:07:23 -0800 Steve Kargl wrote: > actual real-world conditions. In his words, FreeBSD should "eat its > own dogfood." The new installation on FreeBSD.org, of course, would I am on dog food since last May/June. How should I phrase it? Every can tastes different. Most cans have a perfect taste but some cans are really off. So, when I see a bad can, I go back to my old can, wait a day and get me then a new can. This is then - most likely - good again. This is the real reason why it is not possible to run important machines on dog food. If one can is bad, the machine is down. As FreeBSD.org sits next to the canning machine, it can run on dog food. Erich ___ 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: gpart resize vs. cache?
Hi, On Sun, 3 Feb 2013 12:06:41 -0800 Tim Kientzle wrote: > I'm tinkering with a disk image that automatically > fills whatever media you put it onto. But I'm having > trouble with gpart resize failing. > > Disk layout: >MBR with two slices mmcsd0s1 and mmcsd0s2 >bsdlabel with one partition mmcsd0s2a > > Before I can use growfs, I have two gpart resize operations: > > 1) gpart resize -i 2 mmcsd0 > > 2) gpart resize -i 1 mmcsd0s2 > > Step 1 resizes mmcsd0s2 and always succeeds. > > Step 2 resizes mmcsd0s2a and always fails > with "No space on device." > I used a gpart show between in a different situation. The script did not work without it. When I entered the same commands from the command line, they all worked. So, things could be related to cache or delayed writes. Erich ___ 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 10, booting from USB failes
Hi, I have several thumb drives and had disks. To be able to exchange the hard disks, all devices are bootable. I have tested the setup some time ago and it did not give me problems to boot from the external media via USB. I will take two hard disks as an example: => 63 976773105 ada0 MBR (465G) 63 1953- free - (976k) 2016 976771152 1 freebsd (465G) =>0 976771152 ada0s1 BSD (465G) 0 1024 1 freebsd-ufs (4.9G) 1024 32768000 2 freebsd-swap (15G) 43008000 1024 4 freebsd-ufs (4.9G) 53248000 1024 5 freebsd-ufs (4.9G) 63488000 10240 6 freebsd-ufs (48G) 165888000 810883144 7 freebsd-ufs (386G) 976771144 8 - free - (4.0k) => 34 976773098 da0 GPT (465G) 341281 freebsd-boot (64k) 162 6 - free - (3.0k) 168 104857602 freebsd-ufs (5.0G) 10485928 335544323 freebsd-swap (16G) 44040360 104857604 freebsd-ufs (5.0G) 54526120 104857605 freebsd-ufs (5.0G) 65011880 1048576006 freebsd-ufs (50G) 169869480 8069036487 freebsd-ufs (384G) 976773128 4 - free - (2.0k) The system started from ada0. It fails to start from da0 now. Before I switch the disks, does anybody know of something which causes the problem? If this matters, I did this with an X220 ThinkPad. Erich ___ 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: X on ThinkPad X220 with chrome or firefox goes blank
Hi, On Mon, 17 Dec 2012 11:44:59 +0200 Artyom Mirgorodskiy wrote: > Did you try to rebuild xorg-server with latest clang patch? (this > patch commited 2-3 days ago) it seems that my X server was a bit too old. I just upgraded and all works fine now? Thanks! Erich > > On Monday 17 December 2012 08:40:37 Erich Dollansky wrote: > > Hi, > > > > I updated my notebook over the last couple of days and have now > > problems starting chrome and firefox. The effect is that the screen > > turns blury leaving hard to recognose characters on a white screen > > after starting any of these applications. > > > > I can use Ctrl-Alt-F2 to come back to the terminal. Of course, this > > is now a flight in the dark. After entering Ctrl-C and restart X, I > > get a new X running until I start firefox or chrome again. > > > > Applications like Claws Mail, Arora or xterm work without problems. > > > > I do not see anything different in the log file of X. > > > > Does anybody have a clue what could cause this? > > > > I will recompile and reinstall all my ports now to see what will > > come out there. > > > > Erich > > ___ > > 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-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: X on ThinkPad X220 with chrome or firefox goes blank
Hi, On Mon, 17 Dec 2012 11:44:59 +0200 Artyom Mirgorodskiy wrote: > Did you try to rebuild xorg-server with latest clang patch? (this > patch commited 2-3 days ago) I do not know as I updated the ports tree around this time. Let me do it again. Thanks for the hint. Erich > > On Monday 17 December 2012 08:40:37 Erich Dollansky wrote: > > Hi, > > > > I updated my notebook over the last couple of days and have now > > problems starting chrome and firefox. The effect is that the screen > > turns blury leaving hard to recognose characters on a white screen > > after starting any of these applications. > > > > I can use Ctrl-Alt-F2 to come back to the terminal. Of course, this > > is now a flight in the dark. After entering Ctrl-C and restart X, I > > get a new X running until I start firefox or chrome again. > > > > Applications like Claws Mail, Arora or xterm work without problems. > > > > I do not see anything different in the log file of X. > > > > Does anybody have a clue what could cause this? > > > > I will recompile and reinstall all my ports now to see what will > > come out there. > > > > Erich > > ___ > > 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-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
X on ThinkPad X220 with chrome or firefox goes blank
Hi, I updated my notebook over the last couple of days and have now problems starting chrome and firefox. The effect is that the screen turns blury leaving hard to recognose characters on a white screen after starting any of these applications. I can use Ctrl-Alt-F2 to come back to the terminal. Of course, this is now a flight in the dark. After entering Ctrl-C and restart X, I get a new X running until I start firefox or chrome again. Applications like Claws Mail, Arora or xterm work without problems. I do not see anything different in the log file of X. Does anybody have a clue what could cause this? I will recompile and reinstall all my ports now to see what will come out there. Erich ___ 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: looking for help from ppp users
Hi, On Sat, 15 Dec 2012 01:14:10 -0500 Eitan Adler wrote: > On 3 December 2012 10:41, Gary Palmer wrote: > > While not commenting on the correctness of the current contents, > > the userland PPP section of the FAQ appears to mostly deal with > > dialup modems. I suspect more people use it now to do PPPoA or > > PPPoE for some form of DSL link and there probably needs to be some > > effort to address the differences. > > I've never used PPP in any sense. Any chance I could enlist you to > help write some content? I could turn it into docbook, edit it, etc. > > > let me share my experience with ppp and one CDMA 'modem' we have to use in Indonesia. First, what makes it work in ppp.conf: set device /dev/cuaU0.0 set ctsrts off set login set dial set authname internet@ceria set authkey ceria set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns# set dns servers in resolv.conf nat enable yes nat deny_incoming yes set phone #777 The fun starts with the first start and after each restart of the modem after the battery went empty. It simply does not work after above's commands are entered manually one by one. There is no useful error message except that the modem either sends the wrong authentication information to the server or something else makes it drop the connection after this information is sent when doing it via the script. If I manually enter these commands, it works from the start. Of course, this is a problem caused by the modem but mentioning this in the handbook could help others in this strange situation. Erich ___ 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: compiler info in kernel identification string
Hi, On Wed, 14 Nov 2012 00:43:03 +0100 Mateusz Guzik wrote: > Hello, > > avg@ suggested to include compiler version in the kernel so that it's > present in uname (and one can easly tell what was used to compile it). > > Here is my attempt: > http://people.freebsd.org/~mjg/patches/newvers-compiler.diff > > Basically adds compiler name and version/revision after revision of > system sources. > > Sample output from dirty git sources: > gcc: > FreeBSD 10.0-CURRENT #7 r242962=264d569-dirty(gcc-4.2.1-20070831): Wed > Nov 14 00:11:51 CET 2012 > > clang: > FreeBSD 10.0-CURRENT #8 r242962=264d569-dirty(clang-r162107): Wed Nov > 14 00:12:26 CET 2012 > > Sample output from svn with gcc: > FreeBSD 10.0-CURRENT #1 r243006:243007M(gcc-4.2.1-20070831): Wed Nov > 14 00:41:23 CET 2012 > > I have no strong opinions on format, I just want this information > easly accessible. > > Comments? > this is a good idea! Erich ___ 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: November 5th is Clang-Day
Hi, On Thu, 1 Nov 2012 21:59:17 -0700 Steve Kargl wrote: > On Thu, Nov 01, 2012 at 10:29:45PM -0500, Brooks Davis wrote: > > - Not all libm tests pass. More work by subject matter experts is > >required to create tests cases for LLVM developers. Most > > problems are not expected to be major in practice given that LLVM > > is being used for scientific computing in a number of products > > including Cray's FORTRAN compiler, most OpenCL compilers, and the > > Julia language. > > Is there a knob to continue to use GCC as the default compiler? > > The above statement is somewhat troubling to those of us > who use FreeBSD as computational nodes. > > BTW, the name of the language is "Fortran". It's been "Fortran" > for the last 30-something years. I never realised the name change. It seems that I am not alone with this. Erich ___ 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: Unable to load i915kms
Hi,
On Sun, 29 Jul 2012 15:21:36 +0800
Denny Lin wrote:
> > How do the wrong modules get loaded?
>
> Thanks for all the help guys. The problem was the result of my own
> stupidity.
>
> I went through some code trying to find out why the wrong modules were
> loaded, and I discovered that I previously commented out this line in
> x11-drivers/xf86-video-intel/Makefile:
> EXTRA_PATCHES+= ${PATCHDIR}/extra-i915kms
so, wrong name --> wrong modules. This simple.
Erich
___
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: Unable to load i915kms
Hi, On Sat, 28 Jul 2012 21:49:18 -0700 Kevin Oberman wrote: > You are working too hard from old information. Do not attempt to load > i915kms.ko. Do not attempt to load drm2.ko. For the past months the > drivers have been fixed to automatically load all needed drivers and > kernel modules when Xorg is started. My Sandybridge behaves just like How do the wrong modules get loaded? > your system if I try to manually load i915kms.ko. Screen goes black > and that is the end. It still works for me. You know, never change a winning team. There seem to be small differences between the CPU/GPUs. Erich ___ 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: Unable to load i915kms
Hi, On Sun, 29 Jul 2012 12:20:13 +0800 Denny Lin wrote: > On Sun, Jul 29, 2012 at 10:59:54AM +0700, Erich Dollansky wrote: > > this seems to be wrong: > > > > > 131 0x8167a000 7019 i915.ko > > > 141 0x81682000 111c4drm.ko > > > > > From my machine: > > > > 21 0x817e4000 aee0 sem.ko > > 31 0x81a12000 9db3 linprocfs.ko > > 41 0x81a1c000 587a5linux.ko > > 51 0x81a75000 3900 ums.ko > > 61 0x81a79000 2b0d uhid.ko > > 71 0x81a7c000 1b7a1ng_btsocket.ko > > 81 0x81a98000 ba58 netgraph.ko > > 91 0x81aa4000 118b ng_bluetooth.ko > > 101 0x81aa6000 a9f3 fuse.ko > > 111 0x81ab1000 69298i915kms.ko > > 121 0x81b1b000 1ba2 iicbb.ko > > 134 0x81b1d000 1ddb iicbus.ko > > 141 0x81b1f000 1cd5 iic.ko > > 151 0x81b21000 32386drm2.ko > > 161 0x81b54000 241 acpi_call.ko > > > > So, why did drm.ko and i915.ko make it into your kernel? > > Both are built by default, but only drm.ko and i915.ko are loaded > automatically. i915kms.ko has to loaded manually: > http://lists.freebsd.org/pipermail/freebsd-x11/2012-May/011857.html > ok, try to use my script: http://www.alogreentechnologies.com/freebsd/XonX220 I do not know what this script will do when drm and i915 are already loaded. > I do have i915kms and drm2.ko, but every time I try to load > i915kms.ko, the computer blacks out. The black screen is normal if you do not start X. > > > > I have WITH_KMS=YES and WITH_NEW_XORG=YES in /etc/make.conf. I > > > also rebuilt xorg-* and xf86-video-intel after updating to > > > r238858. > > > > > > Xorg previously worked on my laptop with all.14.3.patch on top of > > > -CURRENT from around mid-April, so I'm not sure what went wrong. > > > > > I did not touch this machine since 16.07.12. > > > > Maybe your patches affected something. Can you download a fresh > > source tree? > > I used a new checkout when I updated to r238858, so this shouldn't be > a problem. > It could be that the two loaded modules cause the problem. Erich ___ 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: Unable to load i915kms
Hi, On Sun, 29 Jul 2012 09:53:50 +0800 Denny Lin wrote: > > I updated to r238858 yesterday, but I was unable to load i915kms (I > tried loading it manually and putting it in /boot/loader.conf). The > computer becomes unresponsive and the screen turns black in either > case. I'm using the GENERIC kernel with WITNESS and INVARIANTS > disabled. > > Output of pciconf -lvb: > vgapci1@pci0:0:2:0: class=0x03 card=0x15f21043 > chip=0x01168086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' > device = '2nd Generation Core Processor Family Integrated > Graphics Controller' class = display > subclass = VGA > bar [10] = type Memory, range 64, base 0xdd40, size > 4194304, enabled bar [18] = type Prefetchable Memory, range 64, > base 0xb000, size 268435456, enabled bar [20] = type I/O Port, > range 32, base 0xe000, size 64, enabled > > Modules loaded at boot: > Id Refs AddressSize Name > 1 38 0x8020 12c57f0 kernel > 21 0x814c6000 70a8 acpi_video.ko > 31 0x814ce000 6568 cuse4bsd.ko > 41 0x81612000 cea0 geom_eli.ko > 51 0x8161f000 1abc1crypto.ko > 61 0x8163a000 a4f9 zlib.ko > 71 0x81645000 15e2 fdescfs.ko > 81 0x81647000 3daf linprocfs.ko > 91 0x8164b000 1eeb2linux.ko > 101 0x8166a000 2393 ums.ko > 111 0x8166d000 17d3 uhid.ko > 121 0x8166f000 a9f3 fuse.ko this seems to be wrong: > 131 0x8167a000 7019 i915.ko > 141 0x81682000 111c4drm.ko > From my machine: 21 0x817e4000 aee0 sem.ko 31 0x81a12000 9db3 linprocfs.ko 41 0x81a1c000 587a5linux.ko 51 0x81a75000 3900 ums.ko 61 0x81a79000 2b0d uhid.ko 71 0x81a7c000 1b7a1ng_btsocket.ko 81 0x81a98000 ba58 netgraph.ko 91 0x81aa4000 118b ng_bluetooth.ko 101 0x81aa6000 a9f3 fuse.ko 111 0x81ab1000 69298i915kms.ko 121 0x81b1b000 1ba2 iicbb.ko 134 0x81b1d000 1ddb iicbus.ko 141 0x81b1f000 1cd5 iic.ko 151 0x81b21000 32386drm2.ko 161 0x81b54000 241 acpi_call.ko So, why did drm.ko and i915.ko make it into your kernel? > I have WITH_KMS=YES and WITH_NEW_XORG=YES in /etc/make.conf. I also > rebuilt xorg-* and xf86-video-intel after updating to r238858. > > Xorg previously worked on my laptop with all.14.3.patch on top of > -CURRENT from around mid-April, so I'm not sure what went wrong. > I did not touch this machine since 16.07.12. Maybe your patches affected something. Can you download a fresh source tree? Erich ___ 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: (void)foo or __unused foo ?
Hi, On Fri, 27 Jul 2012 11:38:24 +0200 Luigi Rizzo wrote: > In writing cross platform code I often have to deal with function > arguments or variables that are not used on certain platforms. > In FreeBSD:sys/cdefs.h we have > if I understand you right here, it is you own code that has to run on different platforms. I can only tell what we are doing since a long long time. We have one file which handles all these things in one central location. This makes all other files independent of the platform but this one file might needs some work when a new platform comes in or things change on one platform. > Any disadvantage or objection to selectively use this form > in our kernel code for parts that need to work on multiple > platforms ? This concept also works inside a kernel, driver or in the world. The concept should then be limited to the module. Erich ___ 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: machine freezes when using USB disk and X
Hi, On Wed, 25 Jul 2012 16:13:04 +0200 Hans Petter Selasky wrote: > On Wednesday 25 July 2012 14:54:08 Erich Dollansky wrote: > > > > I have strange problem which I can reproduce. > > > > When I copy some 100GB to a disk via USB when X is not active, it > > works without any problems. > > > > When I copy some 100GB to a disk via USB when X is running, the > > machine freezes. It does not react to keyboard, mouse and network > > actions. > > > > When I use only X on the same machine and do the same copy via > > network, the machine behaves as expected. > > > > What could I do to locate the problem? > > > > Erich > > > > PS > > > > uname says: > > > > FreeBSD AMD620.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #38: > > Sat Jul 21 06:58:49 WIT 2012 > > You might want to check what interrupts are shared. Might be an IRQ > problem. it does not look like. As it was working before since 8.0 without problems, I cannot imagine that this is the real problem even if they would be shared. I do not expect a solution for this. It is more or less a hint for developers working in the affected areas that there might be something wrong. Erich ___ 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"
machine freezes when using USB disk and X
Hi, I have strange problem which I can reproduce. When I copy some 100GB to a disk via USB when X is not active, it works without any problems. When I copy some 100GB to a disk via USB when X is running, the machine freezes. It does not react to keyboard, mouse and network actions. When I use only X on the same machine and do the same copy via network, the machine behaves as expected. What could I do to locate the problem? Erich PS uname says: FreeBSD AMD620.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #38: Sat Jul 21 06:58:49 WIT 2012 ___ 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: usb plugin msg class
Hi, On Friday 20 July 2012 21:34:42 Fbsd8 wrote: > In 8.x and older when I plugged in my usb thumb drive I got some > messages on the console. But in 9.0 and 9.1 those message no longer show > up on my console. I have a custom /etc/syslog.conf > > Did the message class of those usb plug-in message change between 8.x > and 9.x? IE as defined in /etc/syslog.conf > > If their in a new class what is it? I do not know. I only know that it works with the following configuration: # $FreeBSD$ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit/dev/console *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog lpr.info/var/log/lpd-errs ftp.info/var/log/xferlog cron.* /var/log/cron *.=debug/var/log/debug.log *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log #console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work #*.*/var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.*@loghost # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !ppp *.* /var/log/ppp.log !* The file is the from a default installation of 10. Erich ___ 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: Script to monitor battery status on X220
Hi, On Friday 20 July 2012 16:13:56 Matthias Apitz wrote: > El día Friday, July 20, 2012 a las 03:45:23PM +0700, Erich Dollansky escribió: > > > > ... > > > Is it necessary to poll? Usually devd generates an event when the > > > battery status and/or percentage changes. Just read the events from > > > /var/run/devd.pipe. > > > > > this is a good idea. I did not like this solution either but did not get a > > better idea when I did it. > > I wrote and used something similar for my netbook EeePC 900; it turned > out that the battery is not showing the remaining capacity in a linear this is also true on the X220. > way; the last 5% are 'consumed' in a few seconds, i.e. below 20% I > polled every 2 seconds; I did some tests until I ended at the 2%. There was always enough energy left in the battery to restart the machine. I wonder anyway how they do it. I developed battery monitors a long time ago. As the voltage drop is not linear and the tolerances are very high. They might calibrate each battery when it reaches certain levels. Erich ___ 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: Script to monitor battery status on X220
Hi, On Friday 20 July 2012 12:31:08 Lars Engels wrote: > On Fri, Jul 20, 2012 at 10:04:59AM +0700, Erich Dollansky wrote: > > Hi, > > > > I forget yesterday to share these two scripts: > > > > http://www.alogreentechnologies.com/freebsd/checkbattery > > > > checks the battery status of an X220 and shuts the machine down when the > > battery falls to 2% or below. > > > > The status is checked every minute. > > > > It calls the following script to shut the machine down: > > > > http://www.alogreentechnologies.com/freebsd/poweroff > > > > You must run the first script as root to enable it to power the machine off > > at the end. > > > > I found that the battery life of my machine was higher using a simple > > window manager like blackbox compared to things like GNOME or KDE. This > > might depend on the usage pattern. > > > > Erich > > Is it necessary to poll? Usually devd generates an event when the > battery status and/or percentage changes. Just read the events from > /var/run/devd.pipe. > this is a good idea. I did not like this solution either but did not get a better idea when I did it. Erich ___ 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"
Script to monitor battery status on X220
Hi, I forget yesterday to share these two scripts: http://www.alogreentechnologies.com/freebsd/checkbattery checks the battery status of an X220 and shuts the machine down when the battery falls to 2% or below. The status is checked every minute. It calls the following script to shut the machine down: http://www.alogreentechnologies.com/freebsd/poweroff You must run the first script as root to enable it to power the machine off at the end. I found that the battery life of my machine was higher using a simple window manager like blackbox compared to things like GNOME or KDE. This might depend on the usage pattern. Erich ___ 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: two scripts for X220 users
Hi, On Thursday 19 July 2012 23:30:20 Kevin Oberman wrote: > On Thu, Jul 19, 2012 at 6:06 AM, Erich Dollansky > wrote: > > > > http://www.alogreentechnologies.com/freebsd/setbrightness > > > I am curious about the reason you load i915kms before starting X, when I started with it, it was necessary. You know how it is with something that works. Better do not change it. Erich ___ 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"
two scripts for X220 users
Hi, I would like to share two scripts I found useful running FreeBSD on an X220 with Intel KMS. Script to start X: http://www.alogreentechnologies.com/freebsd/XonX220 starts X after it loaded i915kms and acpi_call. The machine must have /usr/ports/sysutils/acpi_call installed. This script was inspired by http://wiki.freebsd.org/Intel_GPU Script to set LCD brightness: http://www.alogreentechnologies.com/freebsd/setbrightness sets the brightness of the LCD. As I only have one X220 with an Intel CPU, the scripts have not been tested on any other machine. Feel free to use them and comment on them. Erich ___ 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: Erratic USB mouse behaviour when wireless is down and USB hard disk connected
Hi, On Monday 16 July 2012 20:07:27 Hans Petter Selasky wrote: > On Monday 16 July 2012 14:47:04 Erich Dollansky wrote: > > Hi, > > > > On Sunday 15 July 2012 15:25:10 Adrian Chadd wrote: > > > Sounds like bluetooth coexistence? > > > > the problem are only there when the network goes down while being used. > > When the network is down when I start the machine and when the network is > > up and running, the problem is not there. > > > > This makes it so weird for me. > > > > Ok, after a restart the problem was solved. But, are we really used to > > restart FreeBSD because of things like this? > > > > What does "top" and "vmstat -i" say. I think this is more a hardware problem > than software problem, like lost/shared interrupts. Maybe the IRQ is not > properly masked when downing the network interface. I did not think of vmstat at that moment of time. Top did not show me anything which was completely out. Do not worry too much. I hoped to give a hint here for a programmer who might has noticed something like this. I hope to do some testing soon. Erich ___ 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: Erratic USB mouse behaviour when wireless is down and USB hard disk connected
Hi, On Sunday 15 July 2012 15:25:10 Adrian Chadd wrote: > Sounds like bluetooth coexistence? > the problem are only there when the network goes down while being used. When the network is down when I start the machine and when the network is up and running, the problem is not there. This makes it so weird for me. Ok, after a restart the problem was solved. But, are we really used to restart FreeBSD because of things like this? Erich ___ 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: Erratic USB mouse behaviour when wireless is down and USB hard disk connected
Hi, On Friday, July 13, 2012 09:10:16 PM Bernhard Schmidt wrote: > On Fri, Jul 13, 2012 at 2:04 PM, Erich Dollansky > > wrote: > > Hi, > > > > I know that this is not a very helpful information. > > > > I have an Lenovo X220 running 10 from some 2 weeks ago. I just noticed > > that the USB mouse (a wireless Logitech Trackman) becomes unusable when > > the wireless (iwn) is not able to connect to the access point and a USB > > hard disk is plugged in. Even when no data are transferred the USB mouse > > is unusable. > > Which frequency is the mouse working on? something in the 2.4GHz region? > > I remember having lots of fun at $office with the mouse of colleague. > It used channel 6 and the amount of traffic generating over wireless > LAN had direct influence on the accuracy of his mouse activity ;) > > Anyways, if you have the chance to switch to another channel, give it a > shot. I have to check on this. As the channels of the network here are fixed, this only can happen when the network is down. As I said, I can test it next week. Erich ___ 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"
Erratic USB mouse behaviour when wireless is down and USB hard disk connected
Hi, I know that this is not a very helpful information. I have an Lenovo X220 running 10 from some 2 weeks ago. I just noticed that the USB mouse (a wireless Logitech Trackman) becomes unusable when the wireless (iwn) is not able to connect to the access point and a USB hard disk is plugged in. Even when no data are transferred the USB mouse is unusable. The built-in track-point behaves just normal. When I turn off the wireless network via the hardware switch, the system stays usable as expected even under heavy hard disk access. If it was not something else I have missed, the only difference was the access point which went down when I noticed the problem. Please understand this just as a hint to the developers of the sub-systems which could cause the problem. As this network here is not mine, I am not able to do any tests with it. If somebody has an idea what could be tested, tell me please. I will have access to 'my' network the coming week again. Erich ___ 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"
'HAL_INT_RXHP' undeclared (first use in this function)
Hi, I updated my source tree a few hours ago and get now error messages like the one above while compiling /usr/src/sys/dev/ath/if_ath.c 'HAL_INT_RXHP' and 'HAL_INT_RXLP' seem to be totally unknown. There is one comment regarding the first of them. Google does not much either: 'Your search - HAL_INT_RXHP - did not match any documents. ' Who knows more about the values to be used for them? Erich ___ 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: side note on the X220 running CURRENT: head phone jack works
Hi, On Friday, July 06, 2012 03:24:34 AM Kevin Oberman wrote: > On Wed, Jul 4, 2012 at 8:49 PM, Erich Dollansky > wrote: > > Hi, > > > > there have been some people here - including me - wondering whether the > > head phone jack works. Yes, it does. > > > > I just have had the chance to connect the head phone jack. It works when > > vlc is set to use /dev/dsp1.0. > > > > Using /dev/dsp0.1 brings sound to the built-in speakers. > > The "proper" fix is to add the following to /boot/loader.conf: it is the general way as it should work with all applications. > # Out : speaker + headphones > hint.hdac.0.cad0.nid25.config="as=1 seq=15" > # In : mic + external mic > hint.hdac.0.cad0.nid35.config="as=2" > hint.hdac.0.cad0.nid27.config="as=2 seq=15" > I added this to the loader.conf file and will test when I will get my hands on the equipment. Thanks! Erich ___ 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"
side note on the X220 running CURRENT: head phone jack works
Hi, there have been some people here - including me - wondering whether the head phone jack works. Yes, it does. I just have had the chance to connect the head phone jack. It works when vlc is set to use /dev/dsp1.0. Using /dev/dsp0.1 brings sound to the built-in speakers. Erich ___ 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: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hi, On Sunday, July 01, 2012 01:58:49 PM Matthias Apitz wrote: > El día Sunday, July 01, 2012 a las 06:29:28AM +0700, Erich Dollansky escribió: > > > > and no older versions. I will install the USB booted system to harddisk > > > and hope when booted from disk and not from USB the keyboard is working. > > > > > I installed the system r235646 to disk and it shows the same problem: no > keyboard; > ok. > > if 7.4 still runs but not anything after 8.0, it is most likely what I have > > written. Some USB hardware is not supported anymore in 8 and later. > > > > I would install the old one just to see You will also know wat hwardware > > is used there and how it is supported. > > > > This might be the faster route before starting debugging something which is > > not there. > > I said already that it works with a r21 version, CURRENT from > October 2010; so I booted this again and concerning keyboard, here is > the diff: Of course, I have read it but forgot about it then. > > r21: > > atkbdc0: at port 0x60,0x64 on isa0 > > r235646: > > $ fgrep -i kb /tmp/dmesg-r235646.txt > atkbd: the current kbd controller command byte 0065 > atkbd: keyboard ID 0x41ab (2) > sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) > atkbdc0 failed to probe at port 0x60 on isa0 It must be the probing routine then. My keyboard here is at acpi but not on isa0. Is all in the kernel which is needed for isa? It should be, but a check could help. > So the question is: why the is not > detected anymore in r235646, while it is in r21? > Maybe the hints from man will help you: Kernel configuration: options KBD_RESETDELAY=N options KBD_MAXWAIT=N options KBDIO_DEBUG=N device atkbdc Are they still there? /boot/device.hints: hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" I do not know if some defaults have changed. Erich ___ 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: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hi, On Saturday, June 30, 2012 10:11:31 PM Matthias Apitz wrote: > El día Saturday, June 30, 2012 a las 01:49:58PM +0700, Erich Dollansky > escribió: > > > > > Can you try FreeBSD 7.4 or 8.3? > > > > It is sad to say but some times support for older hardware gets cut out for > > whatever reason. > > The IT guy of my company found this laptop in the attic and because > it has no Wifi, nobody is interested in using it anymore. As I said, > I could make use of it as a build machine and for this it must run CURRENT > and no older versions. I will install the USB booted system to harddisk > and hope when booted from disk and not from USB the keyboard is working. > if 7.4 still runs but not anything after 8.0, it is most likely what I have written. Some USB hardware is not supported anymore in 8 and later. I would install the old one just to see You will also know wat hwardware is used there and how it is supported. This might be the faster route before starting debugging something which is not there. Erich ___ 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: problem with top
Hi, On Sunday, July 01, 2012 06:51:41 AM AN wrote: > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #23 r237852: Sat Jun 30 > 18:45:27 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > After a recent upgrade, I am seeing a formatting issue with top. > > top -SPH -s 1: > > last pid: 26011; load averages: 3.61, 2.80, 1.56 up > 0+00:23:30 19:48:46 > 268 processes: 6 running, 245 sleeping, 17 waiting > CPU 0: 22.0% user, 0.0% nice, 0.8% system, 0.8% interrupt, 76.4% idle > CPU 16877.6ctive, 2313M Inact, 6.3M Wired, 3 0.8 Cache, 1440M65.4, 7674M > Free > CPU 2: 28.3% user, 0.0% nice, 2.4% system, 0.0% interrupt, 69.3% idle > CPU 3: 36.2% user, 0.0% nice, 1.6% system, 0.0% interrupt, 62.2% idle > Mem: 455M Active, 2302M Inact, 3151M Wired, 3900K Cache, 1440M Buf, 7943M > Free > Swap: 20G Total, 20G Free > > > Seems like the entry for CPU 1 is wrong. I also noticed this but thought it is of temporary nature. The data of CPU 1 is getting overwritten by the data of the memory usage. Erich ___ 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: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hi, On Saturday, June 30, 2012 01:25:33 PM Matthias Apitz wrote: > El día Friday, June 29, 2012 a las 04:45:57PM +0200, Hans Petter Selasky > escribió: > > > On Friday 29 June 2012 15:34:23 Matthias Apitz wrote: > > > Hello, > > > > > > I have a boot-able USB key with r235646 which works fine in all my > > > laptops so far; today I got as a gift an older FS Amilo D 7830 which has > > > enough resources to use it as new build machine (1 GByte RAM, 80 GByte > > > disk). I booted it with from the USB key and after the system is up it > > > does not echo or react on any key-press; before booting the keys are > > > working, for example in the menu to boot into single user etc. > > > > > > What could be the problem? > > > > > > I will later configure that the USB booted system brings Ethernet and > > > SSH up, maybe I can see something when I can login via SSH... > > I have just for beeing curios booted an older USB key with r21 > (from October 2010) and the keyboard just works as it should; > I have had a problem like this before. I have had to stick with an older FreeBSD version on this machine. Can you try FreeBSD 7.4 or 8.3? It is sad to say but some times support for older hardware gets cut out for whatever reason. Erich ___ 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: GPU_KMS still not working CURRENT X220
Hi, On Thursday, June 28, 2012 11:15:54 PM Kevin Oberman wrote: > On Thu, Jun 28, 2012 at 8:45 AM, Andrey Fesenko wrote: > > I have lenovo thinkpad x220 > > > > # uname -a > > FreeBSD bsdx220 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r237683: Thu Jun > > 28 08:41:40 MSK 2012 root@bsdx220:/usr/obj/usr/src/sys/MY_INTEL > > amd64 it works for me with this: FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #7: Thu Jun 28 09:09:16 WIT 2012 > > > > # pciconf -lvb > > vgapci0@pci0:0:2:0: class=0x03 card=0x21da17aa chip=0x01268086 > > rev=0x09 hdr=0x00 > >vendor = 'Intel Corporation' > >device = '2nd Generation Core Processor Family Integrated > > Graphics Controller' > >class = display > >subclass = VGA > >bar [10] = type Memory, range 64, base 0xf000, size 4194304, > > enabled > >bar [18] = type Prefetchable Memory, range 64, base 0xe000, > > size 268435456, enabled > >bar [20] = type I/O Port, range 32, base 0x6000, size 64, enabled > > > > After # kldload i915kms screen is black, if # kldunload i915kms panic > > Don't do this. It has been clearly stated that i915kms my not be > unloaded and that attempting to unload it WILL panic the system. > > Also, don't load i945kms. This WILL lock up the system with a blank screen. > it works for me. I use this kind of script to start X: sudo kldload i915kms sudo kldload acpi_call sudo chmod 666 /dev/acpi startx > The modules required are autoloaded during Xorg initialization. Just > make absolutely sure that you have the latest version of > xf-video-intel. (If you installed a rather early version of the KMS > code, it is possible that you have two xf-video.intel* ports in your > tree, thought I don't expect this is the case. This could be the real reason why it fails But I must say that it hangs on rare occasions. It might has to do with playing with the mouse or the keyboard during the start-up phase of X. At least, I did not notice a freeze when I did not play around with them during the start of X. Erich ___ 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: Panic on current from yesterday during boot
Hi, On Wednesday 27 June 2012 23:20:09 Jung-uk Kim wrote: > On 2012-06-27 07:07:40 -0400, Andriy Gapon wrote: > > on 27/06/2012 13:44 Andrey Fesenko said the following: > >> On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko > >> wrote: > >>> On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon > >>> wrote: > Committed as r237652: > > http://svnweb.freebsd.org/base?view=revision&revision=237652 > I updated my sources around midnight (GMT) and compiled them again. The system then booted without any problems. Perfect! Erich ___ 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: Panic on current from yesterday during boot
Hi, On Wednesday 27 June 2012 15:42:43 Andriy Gapon wrote: > on 27/06/2012 11:39 Erich Dollansky said the following: > > Anyway, What would be a save way to get a trace to a disk as I do not have a > > backup system with me? > > Assuming I understand the question correctly your options are: > - remote console (serial/firewire/etc) from another machine this is the problem as I do not have it here. > - digital camera So, this is really the only option then. The photos I really have. Would you still need them? I do not think so after seeing the other post. > - produce a crash dump (possible only after a certain point in boot sequence) I think that this was too early. Erich ___ 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: Panic on current from yesterday during boot
Hi, On Wednesday 27 June 2012 13:20:10 Andriy Gapon wrote: > on 27/06/2012 08:27 Andrey Fesenko said the following: > > On Wed, Jun 27, 2012 at 9:06 AM, Erich Dollansky > > wrote: > >> Hi, > >> > >> I am getting a panix when I boot a newly compiled system with sources > >> downloaded yesterday. The panic was still there with the sources from > >> three days ago. > >> > >> The panic regards /usr/src/sys/vm/uma_core/c line 2040. > >> > >> The machine is a Lenovo X220. I do not expect anything specific loaded yet > >> as I load the Intel KMS module manually after the system is up and running > >> on the console. > >> > > > > confirm faced with the same error > > FreeBSD X220 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r237565 > > You haven't provided a full stack trace, but let me take a guess: > http://article.gmane.org/gmane.os.freebsd.devel.cvs/477167 this is a direct hit. > Perhaps this could be useful. I assume that you do not need one then. Anyway, What would be a save way to get a trace to a disk as I do not have a backup system with me? Erich ___ 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"
Panic on current from yesterday during boot
Hi, I am getting a panix when I boot a newly compiled system with sources downloaded yesterday. The panic was still there with the sources from three days ago. The panic regards /usr/src/sys/vm/uma_core/c line 2040. The machine is a Lenovo X220. I do not expect anything specific loaded yet as I load the Intel KMS module manually after the system is up and running on the console. How could I help you there? I would need some hand holding there as I am travelling at the moment and have only this machine with me without much documentation available. Moving back to this FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Thu Jun 21 14:29:15 WIT 2012 solves the problem for me. Erich ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 07 June 2012 12:58:59 Hartmann, O. wrote: > On 06/07/12 11:17, Daniel Kalchev wrote: > > > > > > On 07.06.12 02:09, Erich wrote: > >>> Those "minor" issues are, having the recent mess in front of my eyes, a > >>> simple "negative exaggeration". What is that "price worth", if the > >>> system is faulting and rendered useless or partially useless? > >>> > >> just do what was recommended in this thread: wait. > > ... well, I will pass this to those who fund my research. Wait. Yes ... > the right answer. to make them ban FreeBSD from all of their projects? > > >> > >> Tell this ones to a commercial client. They will use words on you for > >> which use you get a life ban on this list. > > Not even commercial clients ... I have the impression that the people > who are using FreeBSD MUST be professionals in any way - or just > adventurers. This impression can be emphazized by picking up some of the > comments made here. > I am back to BSD since around ten years. I never really left Unix since I started with it during the last days of the Seventies. It amazes me most that this kind of people always have been there. I made then some fun with them when they have been on the suppliers side. I think they have forgotten why Unix is there in the first place. > > > > > If you are not qualified enough to handle issues like this, you would be > > better to avoid offering your "integration services" to anyone. Or, of > > you dare to -- you fully deserve those people yelling at you, or worse.. > > > > Those who use FreeBSD to offer integration services and are qualified do > > not whine, neither they wait. Those people do what the promised to do: > > provide the customer with the requested solution. > > ... in some cases this needs the deep knowledge of all ports/software > provided and used and this is simply impossible, or at least null > convergent probability. It is not possible but it is also not needed. Why create a hurdle when there is a simple way around it? > > In some cases I see a dicrepancy between what is reality and what is > predicated. If it comes to the evidence, that something has been > mismanaged, then there is always this allmighty excuse: FreeBSD is a > volunteer system developed by volunteers blabla. I'm also a volunteer > using FreeBSD! And I spend a lot of time trying to help. > This all they say sounds always so one-sided. As being the perfect human is the standard. > But at some points this gets very frustrating! Totally corrupted ports > (not FreeBSD itself!), and so a corrupted system, no fallback mechanism > although the problem is there for decades by now (as stated in this thread). Which alone makes a big joke out of these answers. > In my case, just for instance, we/I use FreeBSD as server AND client to > avoid loads of work having to many different OSes. We and it is definit > use OpenLDAP as the users's housekeeping backend. > Thunderbird is NOT working with OpenLDAP (which is, I asume, an Ok, I do not like LDAP for 'private' reasons and as such it is not on any of the machines under my control. But even then, hey, you are joking? > important piece of a modern multiuser environment and part of "the power > to serve"). I personally live with this problem now for almost a year, > since I can circumvent the crash of Thunderbird by starting Firefox > prior to Thunderbrd and start Thunderbird while Firefox is starting. > This behaviour is very strange and it is obviously well known to those > who use a similar environment. I also do not use Thunderbird as my primary e-mail client because of its erratic behaviour. > And this problem occurs on EVERY new setup I made using LDAP as the > backend. > I wonder why you are still using FreeBSD then. Especially with these kind of comments around. > There is a open PR, there are some hints (not working for me), there are > some notes in the mailing list. > > Obviously, FreeBSd is rarely used in such an environment or is stuck > with ancient NIS/YP setups, I do not know. I must say, luckily, I have had to give in when it came to the company's public server. It uses Linux and does not have any of these issues. > > I only can ask the list herein - since the "professionals" in our > computer center of the campus are in most cases in Linux. > Sad to say. > > Well, to come back to the subject: Why Are You NOT Using FreeBSD? > > I guess there are plenty of reasons as well as there are plenty of > reasons of the opposit. But one very frustrating scaring thing is the > arrogancy of several people here - leveling out the great help of those > who wish to help. When they are successful in keeping people away, there position is stronger then. Anyway, I joined this thread more for the fun until I realised that it should be possible to put the salty finger into this big wound of FreeBSD. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/li
Re: Why Are You NOT Using FreeBSD?
Hi, On 06 June 2012 9:21:22 Sean Cavanaugh wrote: > > Overall I see it as packages are flat stable at the cost of being out of > date, and ports are current but not guaranteed to compile without > intervention. The Maintainers do give a very good shot to make them stable > but sometimes one person cannot maintain millions of lines of code and not > make a glitch occasionally, or make it out on time when a dependency > changes. isn't the date of the packages the date of the last release of the branch? Aren't the chances high then to get a working ports tree? You can follow the discussion about this subject for at least 10 years back. The result is always the same. In parallel is the discussion why so little people are using FreeBSD. Do you understand what I want to say? Erich ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 03 June 2012 PM 4:46:40 Jakub Lach wrote: > > just the base system is > > the only part that needs to be unified, everything else can be > > installed from source. > > You really don't know what you are talking about, do you? the chicken and the egg Erich ___ 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: X220 and all.14.5.patch
Hi, On Sunday 06 May 2012 16:30:25 Andriy Gapon wrote: > on 06/05/2012 12:15 Erich Dollansky said the following: > > Hi, > > > > On Sunday 06 May 2012 15:04:08 Andriy Gapon wrote: > >> on 06/05/2012 03:03 Erich Dollansky said the following: > >>> > >>> On Saturday 05 May 2012 04:40:50 matt wrote: > >>>> On 05/03/12 22:12, Artem Tuchinsky wrote: > >>>>> > >>> I will investigate further now. > >> > >> Do you try to compile i915 driver into kernel? > > > > yes. > > > >> Do you not have "device drm" in kernel config? > > > > yes. > > Just a note, in case it was not obvious, all concrete drm drivers (i915, > radeondrm, etc) require the drm driver. yes, I know and put both into the kernel configuration. Erich ___ 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: X220 and all.14.5.patch
Hi, On Sunday 06 May 2012 15:04:08 Andriy Gapon wrote: > on 06/05/2012 03:03 Erich Dollansky said the following: > > > > On Saturday 05 May 2012 04:40:50 matt wrote: > >> On 05/03/12 22:12, Artem Tuchinsky wrote: > >>> > > I will investigate further now. > > Do you try to compile i915 driver into kernel? yes. > Do you not have "device drm" in kernel config? yes. > > In any case I suggest that you use i915 as a module, but make sure that you > compile the module as a part of kernel build (e.g. via MODULES_OVERRIDE unless > you already build all the modules). I can try this later. A client will keep me busy for a few days now. Erich ___ 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"
