Fwd: dbus broken?
Wenn einem gar niets meer einfällt, schreit man auch nix. Mijn mute reminder! Begin doorgestuurd bericht: > Van: "Lizbeth Mutterhunt, Ph.D" > Datum: 24 april 2023 om 08:58:54 CEST > Aan: current-us...@freebsd.org > Onderwerp: dbus broken? > > As I tried the CURRENT Image from Aor., 4th, I recognised the dbus Package > is broken, Even in Building from Ports. > > The Image from 20th Apr. is ok again. Something went wrong on Apr. 4th > (missing dbus config). > > Just for information purpose, now everything is fine again on my Acer > Vhromebook 314! > > Thx for patience! > > Liz > > Wenn einem gar niets meer einfällt, schreit man auch nix. Mijn mute reminder!
akonadiconsole and SQL 57
hi people, first at the moment I have to short-cut my web as not at home and /etc/rc.conf doesn't take my wlan0 interface; I changed rooter IP to 192.168.8.1 and edited /etc/wpa_supplicant.conf. but still at booting the field with the web stays "". I have mysql at startup. after recent update on my grandmas notebook I have problems with loading kmail. Here's an excerpt of kmail start: org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: DB initializer done Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Assertion failed: (param->buffer_length != 0), function setup_one_fetch_function, file /wrkdirs/usr/ports/databases/mysql57-client/work/mysql-5.7.34/libmysql/libmysql.c, line 4112. QSocketNotifier: Invalid socket 6 and type 'Read', disabling... KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = akonadiserver path = /usr/local/bin pid = 5695 KCrash: Arguments: /usr/local/bin/akonadiserver KCrash: Attempting to start /usr/local/lib/libexec/drkonqi akonaditest: org.kde.pim.akonadiserver: Failed to connect to database! org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/var/run/user/1001/akonadi/mysql.socket' (2) QMYSQL: Unable to connect" org.kde.pim.akonadiserver: Shutting down AkonadiServer... when reopening the akonadi-console I don't get a connection to PAM and can't enter my password. User 1001 doesn't exist, maybe SQL group? I had a quite similiar problem one update before in march from sql-client and sql-to be solved with a simple Q in [MYSQL] the local SQL-config; but this time it is much more trickier. any help? lizbeth
no graphics on a Dell Vostro 131
so, it's my great-grandma and has since recent update of the glib package the following problem when trying to start the DE or even lightdm, sddm, cdm... the reference output of X is: ld-elf.so.1: /usr/local/lib/libglib-2.0.so0: Undefined symbol "eventfd@FBSD1_6" what I did so far: a) make kernel and userspace b) trying to compile devel/glib20 with an error something like cant't find textbook.xsl to be downloaded although there. c) trying to rebuild the linker, errors on compile: the above error message. When trying to add hald to /etc/rc.conf I get the same error message! Is the linker dead or is it the new version 2.66.7_1 of glib? what to do now? slim works but doesn't start any session (Plasma, GNOME, XFCE4). Starting plasma manually: same error. Any help appreciated, Lizbeth ___ 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"
ghostBSD-CURRENT?
hi again, now world is installed and mergemaster done I get every time I try to command pkg: cannot determine local path. built pkg or pkg-devel from /ports/ports-mgmt pkg can't be installed as /usr/local/etc/bash_completion/_pkg.bash exists --- error 70. rm'ing doesn't help! tar -xfv pkg.tgz leads to the same output "cannot determine local path"! what now? lizbeth ___ 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"
in between freeBSD and ghostBSD
hiya,
have this: https://www.unitedbsd.com/d/310-ghostbsd-to-be-made-current
what do you think of it? laptop still compiling (29 hours for the
userspace mostly llvm and clang). I think a good idea is a "('pkg update
-f '*')", compiling from which ports. in ghostBSD it's simply pkg
install ports but the freeBSD checked out with .svn.
will post results here (maybe from the other netBSD if nothing works),
inkl. the crash-trace from the drm-kmod-current; how about
drm-kmod-devel? there's a binary for ghostBSD but I get a kernel panic
when loading the driver; stacktrace to be rescued and brought to netBSD.
any suggestions or tipps for that kinda situation?
lizbeth
___
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"
funny thing with the drm0
After having had some near-death-experiences in Greece I'm back to my screens. As horizon arises, BSD gets up --- and if it is 3 a.m.! :-) But this is the experience with my Dell Vostro on 13 current: After finally recompiling the kernel with the drm-module inside and the trick of injecting the device IWNFW I get a *nice* message a bootup: Aug 19 02:51:10 current kernel: info: [drm] Initialized drm 1.1.0 20060810 Aug 19 02:51:10 current kernel: drmn0: on vgapci0 Aug 19 02:51:10 current kernel: info: [drm] Memory usable by graphics device = 2048M Aug 19 02:51:10 current kernel: info: [drm] MTRR allocation failed. Graphics performance may suffer. Aug 19 02:51:10 current kernel: intel_iicbb0 on drmn0 Aug 19 02:51:10 current kernel: iicbus0: on iicbb_nostop0 addr 0x1 Aug 19 02:51:10 current kernel: iic0: on iicbus0 Aug 19 02:51:10 current kernel: iicbus1: on intel_gmbus0 Aug 19 02:51:10 current kernel: iic1: on iicbus1 Aug 19 02:51:10 current kernel: intel_iicbb1 on drmn0 Aug 19 02:51:10 current kernel: iicbus2: on iicbb_nostop1 addr 0x12 Aug 19 02:51:10 current kernel: iic2: on iicbus2 Aug 19 02:51:10 current kernel: iicbus3: on intel_gmbus1 Aug 19 02:51:10 current kernel: iic3: on iicbus3 Aug 19 02:51:10 current kernel: intel_iicbb2 on drmn0 Aug 19 02:51:10 current kernel: iicbus4: on iicbb_nostop2 addr 0x12 Aug 19 02:51:10 current kernel: iic4: on iicbus4 Aug 19 02:51:10 current kernel: iicbus5: on intel_gmbus2 Aug 19 02:51:10 current kernel: iic5: on iicbus5 Aug 19 02:51:10 current kernel: intel_iicbb3 on drmn0 Aug 19 02:51:10 current kernel: iicbus6: on iicbb_nostop3 addr 0x12 Aug 19 02:51:10 current kernel: iic6: on iicbus6 Aug 19 02:51:10 current kernel: iicbus7: on intel_gmbus3 Aug 19 02:51:10 current kernel: iic7: on iicbus7 Aug 19 02:51:10 current kernel: intel_iicbb4 on drmn0 Aug 19 02:51:10 current kernel: iicbus8: on iicbb_nostop4 addr 0x12 Aug 19 02:51:10 current kernel: iic8: on iicbus8 Aug 19 02:51:10 current kernel: iicbus9: on intel_gmbus4 Aug 19 02:51:10 current kernel: iic9: on iicbus9 Aug 19 02:51:10 current kernel: intel_iicbb5 on drmn0 Aug 19 02:51:10 current kernel: iicbus10: on iicbb_nostop5 addr 0x12 And furthermore: Aug 19 02:51:10 current kernel: info: [drm] MSI enabled 1 message(s) Aug 19 02:51:10 current kernel: info: [drm] Supports vblank timestamp caching Rev 1 (10.10.201> Aug 19 02:51:10 current kernel: info: [drm] Driver supports precise vblank timestamp query. Aug 19 02:51:10 current kernel: intel_sdvo_ddc_proxy921920 on drmn0 Aug 19 02:51:10 current kernel: intel_sdvo_ddc_proxy921920: detached Aug 19 02:51:10 current kernel: drm_iic_dp_aux0 on drmn0 Aug 19 02:51:10 current kernel: drmn0: taking over the fictitious range 0xe000-0xf000 Aug 19 02:51:10 current kernel: info: [drm] Connector LVDS-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.LVDS-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: info: [drm] Connector VGA-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.VGA-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: info: [drm] Connector HDMI-A-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.HDMI-A-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: info: [drm] Connector DP-1: get mode from tunables: Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.modes.DP-1 Aug 19 02:51:10 current kernel: info: [drm] - kern.vt.fb.default_mode Aug 19 02:51:10 current kernel: fbd0 on drmn0 Aug 19 02:51:10 current kernel: WARNING: Device "fb" is Giant locked and may be deleted before> Aug 19 02:51:10 current kernel: VT: Replacing driver "vga" with new "fb". ug 19 02:51:10 current kernel: info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0 so far so good, quality of text in grafics 1368x1024 is perfectly initialized. but now, when starting xinit or lightdm or sddm or whatever I get a kernel panic: Dump header from device: /dev/ada0p4 Architecture: i386 Architecture Version: 4 Dump Length: 97792 Blocksize: 512 Compression: none Dumptime: 2020-08-19 02:49:00 +0200 Hostname: current Magic: FreeBSD Text Dump Version String: FreeBSD 13.0-CURRENT #2 r364350: Tue Aug 18 20:18:40 CEST 2020 root@current:/usr/obj/usr/src/i386.i386/sys/MIRANDA Panic String: vm_page_assert_xbusied: page 0x72bd024 not exclusive busy @ /usr/src/sys/vm/vm> Dump Parity: 2773167169 Bounds: 1 Dump Status: good /var/crash/vmcore.0 not found First thing I think is kern options: options WITNESS_SKIPSPIN options WITNESS I disabled device HYPERV but this can't be the reason, kern is being compiled with clang. To disable WITNESS would be one way I think but this can't be the yellw of the egg, isn't it? Another thing but I guess having
Re: Kernel-Crash when working with ubt0
On Friday, 30 August 2019 21:50:28 CEST Maksim Yevmenkin wrote: > [trimming the list of recipients] > good like this, so many mails gonna unsubscribe the list - many problems and bugs as far as eye reaches... > On Fri, Aug 30, 2019 at 12:08 PM Miranda Maria Sophie Van den > > Breukelingen wrote: > > works for me as far as pairing concernes (with patch -C > .diff.txt > > > > option LOCK_PROFILING > > option WITNESS > > > > is on in kern.config. My problem presists in the following form: > > > > l2control -a c0:7a:a5:00:c7:11 read_channel_list > > l2control: Could not bind socket, bdaddr=c0:7a:a5:00:c7:11: Network is > > down > > can you please tell what 'c0:7a:a5:00:c7:11' is? is this a remove address? this is a Q13 - headphone - button it's unique with BT; recompiled kernel with the patch but internal stack is just available when you do the service start at least 5-6 times and then there's no info about the stack. Now I know how to apply a patch, what work must it be to write one! > looking at your previous emails, i *think*, 'c0:7a:a5:00:c7:11' is a > remote address. if this is the case, then, l2control is not going to > work. from the l2control(8) man page > > == > -a local > Connect to the local device with the specified BD_ADDR or name. > Example: -a 00:01:02:03:04:05 or -a bt_device. > == > > more specifically, the read_channel_list command will list l2cap > channels open on the local device. sometimes I get the read_channel_list open with one "port"; sometimes i doesn't. Sir Dice knows why! > i'm not exactly sure what are you trying to do here. connect BT-audio > > l2ping is ok; > > ok. this tells me that hci and l2cap communication works yes, differently with 0 bytes or 16 bytes depending on the device. > > So, what to do with the "network down" - problem? > > you have asked l2control to bind to the *local* bd_addr > (c0:7a:a5:00:c7:11). and since there is no *local* bluetooth device > with this bd_addr, l2control returns "network down". l2control will > only work for *local* bd_addr's I'm week with the whole /usr/local - at Arch on the dual boot machine I did a rm -Rf of /usr/local - since then you have to do a pacman with the --force commannd when updating packages. The meaning of this directory is differntly used with linux and bsd. I really don't know, what's the difference between them; natrually a bluetooth- box that I can hold in my hands is loacally - but remote??? like LAN and WAN? MAN, I guess, like the switch between 192.168.8.1 and 10.42.0.1 on 192.168.8.100 here! This address has to be "converted" into "BT-latin" and been connected like this. but how? 'bluetooth-control scan' is a good script but it doesn't connect, just pairs - and with the MagicBox there are a few more steps between binding and connecting. If there's time - and it is, as it is weekend - I'm gonna have a look what google tells me about A2DP and freeBSD. In the meantime I have a corrupt and infected mach_kernel at my VM (kvm on freeBSD is under heavy development, I don't think bhyve can replace it; anyway, the Mac Maverick doesn't run with freeBSD and VirtualBox is just the last thing I'm thinking of; I disabled hyperv on kernel). gonna write again when there are results. > thanks it's up to me to say "thank you"! > max miranda ___ 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-Crash when working with ubt0
On Monday, 26 August 2019 23:35:25 CEST maksim yevmenkin wrote: > > On Aug 26, 2019, at 9:14 AM, Warner Losh wrote: > > > > Is it from read_connection_list? If so I have a 'patch' that I'm using but > > haven't committed because it's just too gross: drop the lock before the > > copyout and pick it up again after... > > Hmm... interesting > > I only took a brief look at it. I suppose I can ensure user space address is > wired and then copyout() can be called with mutex held > > It’s odd that I’ve never seen this before. I’m traveling at the moment will > take a closer look this later this week > > Thanks > Max Sorry for late reply, suffering on a "VPN-Jetlag". Here's the promised vmcore.o(last)[1] on pastepin. It's not a "mini"-dump at all but a huge skirt up to the heals :-) as it has 360M of text and the editor loads about ten minutes on grandmother's laptop with her 70 years after 36 hours of being online. The options are with DEBUG=-g and VERBOSE set in the config. With the ubt1, a 2070X stack by Asus it's probably the kernel driver I'd have to parse into the kernel as here at linux a quarrel about it is for years systematically delaunching "bills driver"; you get the patch as a .zip file on Arch, not as a .deb or .tar.gz or whatever and it must be compiled by hand; after that you'd to reboot and install the A2DP-fix and than you can pray (where ever you want to and think it might help you) with the initial pulseaudio- connect at boottime (sometimes it just doesn't recognize the adapter) - so as a LiLo- substitute I prefer EFI-Clover not the GRUB-stuff that doesn't work at all for BSD for many, many times) and I really don't know how many hours I spent with "sudo bluetoothctl" and on kernel builts for this 'Ubitek Magic Box'. Hope someone can think it over, I know it's old hardware but she'd (the laptop) to to spend 50 mankind-years in bills slavery when I got her finally - probably one of the SALVAGED - messages at fsck -y in single mode :-) So take care of it, it's not the way I normally act to sent guys boxing about and for the box but much more than beeing dead can't happen, can it? - This happened to my cat "Rambo" who just flew away from me and went straight away under a car - buhuhuhu so far for the revenge thoughts, 'svn up' is good at this, subversion is much better than git --diff, which really doens't work at all here. Yours, Miranda [1] pastebin.com/SB0HWHyz ___ 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-Crash when working with ubt0
On Monday, 26 August 2019 09:21:53 CEST Hans Petter Selasky wrote: > Do you have a backtrace? > > --HPS Yup! Have a look at this sniplet: https://pastebin.com/bkNkThAd MvB ___ 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"
