Re: only 3 of 4GB memory available on amd64 8.1-RC1
On Sat, Jun 19, 2010 at 9:16 PM, Andreas Tobler wrote: > Hi all, > > I got my hands on a t60 with 4GB of RAM (BIOS displays it) > > And I installed 8.1-RC1 on it: > > FreeBSD 8.1-RC1 #0: Mon Jun 14 13:40:28 UTC 2010 > r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.76-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x6f6 Family = 6 Model = f Stepping = 6 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 4294967296 (4096 MB) > avail memory = 3092344832 (2949 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > > > > Do I need to configure something special to get the full 4GB of memory? > > I only found the PAE hint, but this is for x86 machines, right? > I think this BIOS specific, may be video rezerv FreeBSD 9.0-CURRENT #0 r208284: Wed May 19 09:34:15 MSD 2010 and...@my_book:/home/andrey/obj/obj/home/andrey/src_head/sys/MY_BOOK amd64 WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f2 Family = 6 Model = f Stepping = 2 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 3339923456 (3185 MB) ___ 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: only 3 of 4GB memory available on amd64 8.1-RC1
On Sun, Jun 20, 2010 at 12:26 AM, Andriy Gapon wrote: > on 19/06/2010 20:16 Andreas Tobler said the following: >> Hi all, >> >> I got my hands on a t60 with 4GB of RAM (BIOS displays it) > > Yes, PAE is for what we call in FreeBSD land "i386". > "x86" we use for both i386 and amd64. > > Now, to the rest. > I recently investigated this topic myself, so I can share what I learned. > The first thing you'd want to have is SMAP information. > You can get it at the loader prompt with 'smap' command. > It is also reported by kernel during a verbose boot, but it is only printed to > console; it is not saved to dmesg, because it is printed before msgbuf is > created. >... > That's about all. > I am curious as to what you would discover about your system - please share > with us. > > -- > Andriy Gapon > Hello My notebook Toshiba U200-10H Install 4Gb(2+2) bios detect 3,... not all SMAP tipe=01 base= len=0009fc00 tipe=02 base=0009fc00 len=0400 tipe=02 base=000e len=ee00 tipe=04 base=000eee00 len=0200 tipe=02 base=000ef000 len=00011000 tipe=01 base=0010 len=cf69 tipe=02 base=cf79 len=0001 tipe=02 base=cf7a len=0006 tipe=02 base=cf80 len=0080 tipe=02 base=fec0 len=00018000 tipe=02 base=fec2 len=8000 tipe=02 base=fed0 len=0400 tipe=02 base=fed14000 len=6000 tipe=02 base=fed1c000 len=00074000 tipe=02 base=feda len=0002 tipe=02 base=fee0 len=1000 tipe=02 base=ffb0 len=0010 tipe=02 base=ffe0 len=0020 FreeBSD 9.0-CURRENT #1 r209362: Sun Jun 20 21:44:27 MSD 2010 and...@my_book:/usr/obj/home/andrey/src_head/sys/MY_BOOK amd64 CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.76-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f2 Family = 6 Model = f Stepping = 2 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 4294967296 (4096 MB) Physical memory chunk(s): 0x1000 - 0x0009bfff, 634880 bytes (155 pages) 0x0126a000 - 0xc95dafff, 3359051776 bytes (820081 pages) avail memory = 3339898880 (3185 MB) full dmesg+debug http://www.suahbsd.org/dmesg.boot.dbg ___ 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: change in uname -a behaviour between 12-ALPHA5 and 12-ALPHA7
See WITH_REPRODUCIBLE_BUILD https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071125.html On Wed, Sep 26, 2018 at 4:23 PM, tech-lists wrote: > Hello, > > uname -a used to show a string including the date and where the kernel was > compiled: > > FreeBSD 12.0-ALPHA5 #0 r338518: Fri Sep 7 02:13:14 UTC 2018 > r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > > It no longer does: > > root@REDACTED:/etc# uname -a > FreeBSD REDACTED.REDACTED.org 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338903 > REDACTED amd64 > > How can I get the old behaviour back? > > thanks, > > -- > J. > ___ > 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: leaked swap?
On Mon, Mar 18, 2019 at 6:23 PM Andriy Gapon wrote: > > > First, a note that this was observed on a system that runs a fairly old > current > (~ 1 year old) with a fairly long uptime (> 6 months). > I noticed that the system was nearly out of memory, 98% of swap was in use, > there was less than 1 GB of free memory, several GBs of each of active, > inactive > and laundry memory, and many GBs of wired (mostly ZFS). > I decided to pro-actively reboot the system, but to speed that up I put the > system to the single-user mode (via shutdown) and then back to multi-user. So, > there was no real hardware reboot and the kernel kept running. However, all > userland processes were terminated. > > To my surprise, even while in the single-user mode the swap utilization didn't > go below 70%. Also, laundry memory remained in multi-GB area, but let's > ignore > this for now. > > I think that the swap could be used only for anonymous memory, so I expected > it > go to zero after the shutdown to the single user mode. > Does anyone have any ideas? > Maybe that's something that has already been fixed? > If not, any ideas on what to look for? > Thanks! > Not this? ZFS use wired and not clean only reboot? https://reviews.freebsd.org/D7538?id=25108 ___ 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"
r346941 boot environment in loader broken?
In loader not work change boot environment, sub menu open, change not work, simple reset 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"
Re: Booting anything after r352057 kills console
On Mon, Sep 23, 2019 at 11:51 PM Poul-Henning Kamp wrote: > > > In message > > , Warner Losh writes: > > >We are working on making drm ports less problematic on upgrade... > > Yes, I know. > > But when you track current, it seems that it takes a port-reinstall > to get on that wagon... > beadm/bectl rules 1) make world/kernel 2) install in new BE 3) make new pkg drm 4) install it in new BE too 5) activate 6) reboot ___ 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"
Bhyve ACPICA 20191018 crach guests
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241399 tested r353887 and r354013, freebsd and linux bhyve guests lldb -c /bhyve.core /usr/sbin/bhyve (lldb) target create "/usr/sbin/bhyve" --core "/bhyve.core" Core file '/bhyve.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'bhyve', stop reason = signal SIGABRT * frame #0: 0x0008007fa50a libc.so.7`__sys_thr_kill at thr_kill.S:4 frame #1: 0x0008007f9eb4 libc.so.7`__raise(s=6) at raise.c:52:10 frame #2: 0x00080076de39 libc.so.7`abort at abort.c:67:8 frame #3: 0x0008007e8131 libc.so.7`__assert(func=, file=, line=, failedexpr=) at assert.c:51:2 frame #4: 0x0021fb42 bhyve`main(argc=, argv=) at bhyverun.c:1190:3 frame #5: 0x0021b10f bhyve`_start(ap=, cleanup=) at crt1.c:76:7 (lldb) quit cbsd bstart debian-cbsd cloud-init: enabled init_systap: waiting for link: em0 VRDP is enabled. VNC bind/port: 127.0.0.1:5900 For attach VM console, use: vncviewer 127.0.0.1:5900 Resolution: 1024x768. bhyve renice: 1 Execute master script: cloud_init_set_netname.sh :: /cbsd/jails-system/debian-cbsd/master_prestart.d/cloud_init_set_netname.sh Waiting for PID.. PID: 0 /tmp/bhyve.QRxK8qZ 53: [0001] ProcessorId : FF Error6313 -Invalid field label detected ^ (found "ProcessorId" expected "Processor ID") /tmp/bhyve.QRxK8qZ 57: [0001] Interrupt : 01 Error6313 - Invalid field label detected ^ (found "Interrupt" expected "Interrupt Input LINT") Assertion failed: (error == 0), function main, file /usr/src/usr.sbin/bhyve/bhyverun.c, line 1190. fbuf frame buffer base: 0x84360 [sz 16777216] stdio -l bootrom,/usr/local/cbsd/upgrade/patch/efi.fd debian-cbsd - Please use for debug: sh /usr/local/cbsd/share/bhyverun.sh -c /cbsd/jails-system/debian-cbsd/bhyve.conf ___ 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: console screen saver broken? -current
On Thu, Dec 11, 2014 at 8:42 PM, Alfred Perlstein wrote: > Up until a few months ago the following added to /etc/rc.conf would blank > the screen: > > # /etc/rc.conf > saver="green" > allscreens_flags="-t 60" > > Now that no longer works. > > Can someone explain how to restore the power saving screen saver please? > > It doesn't seem obvious from the docs or anything else. > > Are the current "green_saver.ko" and other screen saver modules still able > to blank the screen? > > Do splash screen work? > > -Alfred > See https://wiki.freebsd.org/Newcons?highlight=%28syscons%29 screensaver No ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
lighttpd crush the system after r274463
Hello,
I'm use lighttpd+SPAWNFCGI for moinmoin wiki.
Before r274463 work fine, after update r275317 and CURRENT system
crushed after start any python CGI script.
For test i'm install py27-flup and start simple
#!/usr/local/bin/python2.7
def myapp(environ, start_response):
start_response('200 OK', [('Content-Type', 'text/plain')])
return ['Hello World!\n']
if __name__ == '__main__':
from flup.server.fcgi import WSGIServer
WSGIServer(myapp).run()
Perl CGI test script work fine.
Workaround FreeBSD-r275317 and later
lighttpd-1.4.35_5
Options:
BZIP2 : on
DOCS : on
FAM: on
GDBM : off
IPV6 : on
LDAP : off
LIBEV : on
LUA: on
MEMCACHE : off
MYSQL : off
MYSQLAUTH : off
NODELAY: on
OPENSSL: on
SPAWNFCGI : on
VALGRIND : off
WEBDAV : off
Shared Libs required:
libpcre.so.1
liblua-5.1.so
libfam.so.0
libev.so.4
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x8
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x809d44bd
stack pointer = 0x28:0xfe00f77df700
frame pointer = 0x28:0xfe00f77df730
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 658 (lighttpd)
[ thread pid 658 tid 100067 ]
Stopped at sbappendstream_locked+0x2d: cmpq$0,0x8(%r14)
db> bt
Tracing pid 658 tid 100067 td 0xf8000ba3e940
sbappendstream_locked() at sbappendstream_locked+0x2d/frame 0xfe00f77df730
sbappendstream() at sbappendstream+0x3c/frame 0xfe00f77df760
tcp_usr_send() at tcp_usr_send+0x1ab/frame 0xfe00f77df7e0
sosend_generic() at sosend_generic+0x40b/frame 0xfe00f77df8a0
soo_write() at soo_write+0x42/frame 0xfe00f77df8d0
dofilewrite() at dofilewrite+0x88/frame 0xfe00f77df920
kern_writev() at kern_writev+0x68/frame 0xfe00f77df970
sys_writev() at sys_writev+0x36/frame 0xfe00f77df9a0
amd64_syscall() at amd64_syscall+0x25a/frame 0xfe00f77dfab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe00f77dfab0
--- syscall (121, FreeBSD ELF64, sys_writev), rip = 0x80164cb8a, rsp =
0x7fffa658, rbp = 0x7fffe6
c0 ---
___
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: lighttpd crush the system after r274463
On Fri, Dec 19, 2014 at 11:46 PM, Gleb Smirnoff wrote: > On Fri, Dec 19, 2014 at 08:41:54PM +0100, Guido Falsi wrote: > G> On 12/19/14 19:28, Adrian Chadd wrote: > G> > Hm, glebius? Any ideas? > > I was quite busy last week, doing defense of my thesis. Now it is > done, and I will look at the problem ASAP. > > -- > Totus tuus, Glebius. I found the problem seems to commit https://svnweb.freebsd.org/base/head/sys/kern/uipc_socket.c?r1=274712&r2=274711&pathrev=274712 if revert this, and rebuild kernel, system work fine. ___ 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: Haswell CPU Feature
On Tue, Jan 6, 2015 at 4:24 AM, Sean Bruno wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 01/05/15 16:57, Neel Natu wrote: >> Congratulations, you have the ability to debug the Haswell silicon >> > HA! > > Is this turned on purposefully (its a feature of the CPU) or is this > turned on unintentionally and is a bug in manufacturing? > > sean My desktop i5-4570 contain this flag too Origin="GenuineIntel" Id=0x306c3 Family=0x6 Model=0x3c Stepping=3 Features=0xbfebfbff Features2=0x7ffafbff,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND> ___ 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"
EFI boot loader regression?
Hello, I'm use system with EFI boot loader on Lenovo X220. Old EFI loader work fine if BIOS set any boot priority UEFI or Legacy first. Starting around December last year, system not boot if set UEFI boot first. http://bsdnir.info/files/efi/ screenshots and working version boot loader For the cleanliness of experiment, as a new loader I downloaded and test FreeBSD-11.0-CURRENT-amd64-20150421-r281832-memstick.img ___ 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"
am335x-bone.dts not exist
# uname -a FreeBSD des.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r283306: Sat May 23 11:56:46 MSK 2015 root@des.local:/usr/obj/usr/src/sys/GENERIC amd64 I'm build BEAGLEBONE with crochet. build error Mounting UFS partition 1 at /usr/obj/_.mount.freebsd Installing U-Boot from : /usr/local/share/u-boot/u-boot-beaglebone Error: beaglebone.dts:29.1-2 syntax error FATAL ERROR: Unable to parse input tree file /usr/src/sys/boot/fdt/dts/arm/beaglebone.dts contain #include "am335x-bone.dts" but this file not existence. Need use am335x-evm.dts or else? ___ 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: am335x-bone.dts not exist
On Tue, May 26, 2015 at 1:19 AM, Tim Kientzle wrote: > >> On May 25, 2015, at 8:25 AM, Warner Losh wrote: >> >>> >>> On May 24, 2015, at 7:44 PM, Tim Kientzle wrote: >>> >>>> >>>> On May 24, 2015, at 12:55 AM, Oleksandr Tymoshenko >>>> wrote: >>>> >>>> >>>>> On May 24, 2015, at 12:12 AM, Garrett Cooper >>>>> wrote: >>>>> >>>>> On May 24, 2015, at 0:07, Oleksandr Tymoshenko wrote: >>>>> >>>>>>> On May 23, 2015, at 7:21 PM, Andrey Fesenko wrote: >>>>>>> >>>>>>> # uname -a >>>>>>> FreeBSD des.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r283306: Sat >>>>>>> May 23 11:56:46 MSK 2015 >>>>>>> root@des.local:/usr/obj/usr/src/sys/GENERIC amd64 >>>>>>> >>>>>>> I'm build BEAGLEBONE with crochet. >>>>>>> >>>>>>> build error >>>>>>> >>>>>>> Mounting UFS partition 1 at /usr/obj/_.mount.freebsd >>>>>>> Installing U-Boot from : /usr/local/share/u-boot/u-boot-beaglebone >>>>>>> Error: beaglebone.dts:29.1-2 syntax error >>>>>>> FATAL ERROR: Unable to parse input tree >>>>>>> >>>>>>> >>>>>>> file /usr/src/sys/boot/fdt/dts/arm/beaglebone.dts contain #include >>>>>>> "am335x-bone.dts" but this file not existence. Need use am335x-evm.dts >>>>>>> or else? >>>>>> >>>>>> >>>>>> am335x-bone.dts in in sys/gnu/dts/arm/, it's a file provided by vendor >>>>>> (TI) >>>>>> >>>>>> I guess crochet does not have this path as include path when compiling >>>>>> dts files. >>>>> >>>>> Pardon me for being a bit daft potentially, but shouldn’t #include work >>>>> for all dts files (look for #include in this doc: >>>>> http://events.linuxfoundation.org/sites/events/files/slides/petazzoni-device-tree-dummies.pdf >>>>> )? >>>>> Thanks! >>>>> >>>> >>>> >>>> #include in dts file is handled by cpp(1). /include/ is handled >>>> by dtc I believe >>>> >>>> You can take a look at how FreeBSD compiles dts files in >>>> sys/tools/fdt/make_dtb.sh >>>> >>>> crochet does not have cpp stage of compilation and before my TI >>>> code/devicetree refactoring none of the dts files referenced in >>>> crochet used #include. That's why problem never appeared. >>>> >>>> Fix is just a matter of fixing freebsd_install_fdt in lib/freebsd.sh. >>>> If nobody beats me to it I'll try to fix it and submit pull request to Tim. >>> >>> I’m testing a fix for this now. >>> >>> Thanks for providing such detailed information. >> >> Is there any reason the standard dts to dtb script isn’t being used instead >> of enshrining another copy of that outside the tree which may break if/when >> we need to enhance the current script? > > Until recently, this didn’t seem necessary; it was a lot simpler to just > invoke dtc. > > But times change: https://github.com/freebsd/crochet/commit/22d7555 > > Tim > It's working :) % uname -a FreeBSD bb.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r283544: Tue May 26 01:54:44 MSK 2015 root@des.local:/usr/obj/arm.armv6/usr/src/sys/BEAGLEBONE-V6 arm ___ 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"
[BeagleBone Black] not bootable emmc after D2646?
Hello, Booting from emmc possible only if you have installed sdcard (u-boot start from sdcard) if stop boot and set loaderdev='mmc 1' system boot emmc. Without this, when sdcard slot empty, in terminal i'm see (u-boot not start) It looks like this is due to https://reviews.freebsd.org/D2646 # uname -a FreeBSD bb.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r283948: Wed Jun 3 18:45:48 MSK 2015 root@des.local:/usr/obj/arm.armv6/usr/src/sys/BEAGLEBONE-V6 arm for copy to emmc uses # sh copy-to-emmc.sh copying succes, fix fstab (remove lables) # cat /etc/fstab /dev/mmcsd1s1 /boot/msdos msdosfs rw,noatime 0 0 /dev/mmcsd1s2a / ufs rw,noatime 1 1 md/tmpmfs rw,noatime,-s30m 0 0 md/var/logmfs rw,noatime,-s15m 0 0 md/var/tmpmfs rw,noatime,-s5m 0 0 root@bb:~ # fdisk mmcsd1 *** Working on device /dev/mmcsd1 *** parameters extracted from in-core disklabel are: cylinders=233 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=233 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA)) start 1024, size 4096 (2 Meg), flag 80 (active) beg: cyl 0/ head 31/ sector 2; end: cyl 1/ head 27/ sector 5 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 5120, size 3745792 (1829 Meg), flag 0 beg: cyl 1/ head 27/ sector 6; end: cyl 887/ head 127/ sector 33 The data for partition 3 is: The data for partition 4 is: # fsck_msdosfs /dev/mmcsd1s1 ** /dev/mmcsd1s1 ** Phase 1 - Read and Compare FATs ** Phase 2 - Check Cluster Chains ** Phase 3 - Checking Directories ** Phase 4 - Checking for Lost Files 10 files, 1180 free (2360 clusters) # diskinfo -v /dev/mmcsd1 /dev/mmcsd1 512 # sectorsize 1920991232 # mediasize in bytes (1.8G) 3751936 # mediasize in sectors 524288 # stripesize 0 # stripeoffset 98E43448# Disk ident. # gpart show => 63 7698369 mmcsd0 MBR (3.7G) 63 4095 1 !12 [active] (2.0M) 4158 7688130 2 freebsd (3.7G) 7692288 6144 - free - (3.0M) => 0 7688130 mmcsd0s2 BSD (3.7G) 0 66- free - (33K) 66 7688064 1 freebsd-ufs (3.7G) ___ 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"
acpi_ibm boot panic
Hello, After update r283989 and r284106 system crush if /boot/loader.conf contain acpi_ibm_load="YES" if comment this line, boot success. Screenshot http://bsdnir.info/files/acpi_ibm_crush.png ___ 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: acpi_ibm boot panic
On Sun, Jun 7, 2015 at 8:05 PM, Allan Jude wrote: > On 2015-06-07 10:58, Allan Jude wrote: >> On 2015-06-07 10:50, Allan Jude wrote: >>> On 2015-06-07 08:25, Andrey Fesenko wrote: >>>> Hello, >>>> After update r283989 and r284106 system crush if /boot/loader.conf >>>> contain acpi_ibm_load="YES" if comment this line, boot success. >>>> Screenshot http://bsdnir.info/files/acpi_ibm_crush.png >>>> ___ >>>> 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" >>>> >>> >>> I am getting the same thing on my Lenovo T530 as well >>> >> >> The problem seems to be r283678 by rpaulo@, I am trying to debug it now. >> > > I have proposed a patch that solves the issue on my system here: > > https://reviews.freebsd.org/D2750 > Thanks, this patch work fine for my X220 ___ 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: acpi_ibm boot panic
On Mon, Jun 8, 2015 at 9:10 PM, Rui Paulo wrote: > The patch looks fine (goto or no-goto). I'm curious as to why you have no > SMBIOS strings though. Are you EFI-booting? Did you upgrade EFI so that it > exports SMBIOS strings to kenv? I recently fixed this problem in EFI. I'm testing first version, without ngie@ changes. EFI bootloader + ZFS root system (boot in ufs) ___ 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"
pw after r284118 not execute -V
Hello, /usr/sbin/pw useradd -n user -s /bin/csh -g wheel -w yes -V /usr/obj/_.mount.freebsd/etc/ -d /usr/home/user make not user with /usr/obj/_.mount.freebsd/etc/ but creates it in the main system /etc ___ 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"
geom classe's geom_*.so installed /usr/lib/ instead of /lib/geom (crochet build)
Hello, I'm build CURENT (r284408) for arm with crochet. all geom lasse's geom_*.so installed /usr/lib/ instead of /lib/geom /usr/obj/_.installworld.armv6.log ... ===> sbin/geom/class/cache (install) install -s -o root -g wheel -m 444 geom_cache.so /usr/obj/_.mount.freebsd/usr/lib install -o root -g wheel -m 444 gcache.8.gz /usr/obj/_.mount.freebsd/usr/share/man/man8 /sbin/gcache -> /sbin/geom ===> sbin/geom/class/concat (install) install -s -o root -g wheel -m 444 geom_concat.so /usr/obj/_.mount.freebsd/usr/lib install -o root -g wheel -m 444 gconcat.8.gz /usr/obj/_.mount.freebsd/usr/share/man/man8 ... after boot see root@r-pi:~ # gpart show gpart: Unknown command: show. usage: gpart help gpart list [-a] [name ...] gpart status [-ags] [name ...] gpart load [-v] gpart unload [-v] root@r-pi:~ # cp /usr/lib/geom_* /lib/geom/ root@r-pi:~ # gpart show => 63 7698369 mmcsd0 MBR (3.7G) 6334776 1 !12 [active] (17M) 34839 1918286 2 freebsd (937M) 1953125 5745307 - free - (2.7G) => 0 1918286 mmcsd0s2 BSD (937M) 0 105- free - (53K) 105 1918080 1 freebsd-ufs (937M) 1918185 101- free - (51K) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CURRENT] r 285785: vt_core.c:(.text+0x42f): undefined reference to vt_logo_sprite_height'
On Wed, Jul 22, 2015 at 8:38 AM, O. Hartmann wrote: > Recent sources (r285785) do not buildkernel due to the bug/error shown below: > > [...] > linking kernel > vt_core.o: In function `vtterm_cnprobe': > /usr/src/sys/dev/vt/vt_core.c:(.text+0x42f): undefined reference to > `vt_logo_sprite_height' /usr/src/sys/dev/vt/vt_core.c:(.text+0x46b): undefined > reference to > `vt_logo_sprite_height' /usr/src/sys/dev/vt/vt_core.c:(.text+0x4c5): undefined > reference to > `vt_logo_sprite_height' /usr/src/sys/dev/vt/vt_core.c:(.text+0x51b): undefined > reference to > `vt_logo_sprite_height' /usr/src/sys/dev/vt/vt_core.c:(.text+0x57d): undefined > reference to `vt_logo_sprite_height' > vt_core.o:/usr/src/sys/dev/vt/vt_core.c:(.text+0x2870): more undefined > references to `vt_logo_sprite_height' follow vt_core.o: In function > `vt_flush': /usr/src/sys/dev/vt/vt_core.c:(.text+0x4fb8): undefined reference > to `vtterm_draw_cpu_logos' vt_core.o: In function > `vt_scrollmode_kbdevent': /usr/src/sys/dev/vt/vt_core.c:(.text+0x5963): > undefined reference to > `vt_logo_sprite_height' /usr/src/sys/dev/vt/vt_core.c:(.text+0x5a98): > undefined > reference to `vt_logo_sprite_height' *** [kernel] Error code 1 > > This commit 285765 and 285766 (D2181) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201751 ___ 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"
Not load some moduls (zfs.ko vmm.ko) with loader.conf BUG 201679?
Current build not usable kernel (if use zfs on root system) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x13e0b30 data=0x1... +0x17ac14] /boot/entropy size=0x1000 /boot/kernel/zfs.ko | elf64_obj_loadimage: read failed (success load other .ko) Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... more details https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201679 ___ 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"
New i915 graphic and WXGA
Hello, i'm test new driver https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Linux%203.8 My monitor have WXGA+ 16:10 1440 900, not correct detected, only 4:3 Modeline. Full log https://bsdnir.info/files/Xorg.i915_01-16.log CPU: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (3192.68-MHz K8-class CPU) vgapci0@pci0:0:2:0: class=0x03 card=0xd0001458 chip=0x04128086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller' class = display subclass = VGA ___ 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"
EFI zfs loader and beadm?
Hello, I'm test EFI boot ZFSroot with BE, this not support now? svn 2965489 If i build simplest system http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/ # zfs get -r mountpoint efifpool NAME PROPERTYVALUE SOURCE efifpool mountpoint /mnt/efifpool default => 40 30712240 da0 GPT (15G) 40 16001 efi (800K) 1640 307106322 freebsd-zfs (15G) 30712272 8 - free - (4.0K) system boot nice If make BE env # zfs get -r mountpoint efiwpool NAME PROPERTYVALUE SOURCE efiwpool mountpoint none local efiwpool/ROOT mountpoint none inherited from efiwpool efiwpool/ROOT/initmountpoint legacy local efiwpool/ROOT/init@init mountpoint - - efiwpool/ROOT/init/boot mountpoint /media/bootlocal efiwpool/ROOT/init/tmpmountpoint /media/tmp local efiwpool/ROOT/init/usrmountpoint /media/usr local efiwpool/ROOT/init/usr@init mountpoint - - efiwpool/ROOT/init/usr/home mountpoint /media/usr/home inherited from efiwpool/ROOT/init/usr efiwpool/ROOT/init/usr/home@init mountpoint - - efiwpool/ROOT/init/varmountpoint /media/var local efiwpool/ROOT/init/var@init mountpoint - - efiwpool/ROOT/init/var/crash mountpoint /media/var/crash inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/db mountpoint /media/var/db inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/db/pkg mountpoint /media/var/db/pkg inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/empty mountpoint /media/var/empty inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/logmountpoint /media/var/log inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/mail mountpoint /media/var/mail inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/runmountpoint /media/var/run inherited from efiwpool/ROOT/init/var efiwpool/ROOT/init/var/tmpmountpoint /media/var/tmp inherited from efiwpool/ROOT/init/var system not boot. Not found /boot/loader.efi (in BE system real path efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init (blank in BE system) loader found this (but not found /boot/kernel) I can copy this and get a similar system https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184#c15 (with out msdos kernel part), but this ruin BE update mechanism ___ 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: EFI zfs loader and beadm?
On Wed, Mar 9, 2016 at 6:48 PM, Eric van Gyzen wrote: > On 03/09/2016 09:40, Andrey Fesenko wrote: >> Hello, >> I'm test EFI boot ZFSroot with BE, this not support now? >> svn 2965489 >> >> If i build simplest system >> http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/ >> >> # zfs get -r mountpoint efifpool >> NAME PROPERTYVALUE SOURCE >> efifpool mountpoint /mnt/efifpool default >> >> => 40 30712240 da0 GPT (15G) >> 40 16001 efi (800K) >> 1640 307106322 freebsd-zfs (15G) >> 30712272 8 - free - (4.0K) >> >> system boot nice >> >> If make BE env >> >> # zfs get -r mountpoint efiwpool >> NAME PROPERTYVALUE SOURCE >> efiwpool mountpoint none local >> efiwpool/ROOT mountpoint none >> inherited from efiwpool >> efiwpool/ROOT/initmountpoint legacy local >> efiwpool/ROOT/init@init mountpoint - - >> efiwpool/ROOT/init/boot mountpoint /media/bootlocal >> efiwpool/ROOT/init/tmpmountpoint /media/tmp local >> efiwpool/ROOT/init/usrmountpoint /media/usr local >> efiwpool/ROOT/init/usr@init mountpoint - - >> efiwpool/ROOT/init/usr/home mountpoint /media/usr/home >> inherited from efiwpool/ROOT/init/usr >> efiwpool/ROOT/init/usr/home@init mountpoint - - >> efiwpool/ROOT/init/varmountpoint /media/var local >> efiwpool/ROOT/init/var@init mountpoint - - >> efiwpool/ROOT/init/var/crash mountpoint /media/var/crash >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/db mountpoint /media/var/db >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/db/pkg mountpoint /media/var/db/pkg >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/empty mountpoint /media/var/empty >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/logmountpoint /media/var/log >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/mail mountpoint /media/var/mail >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/runmountpoint /media/var/run >> inherited from efiwpool/ROOT/init/var >> efiwpool/ROOT/init/var/tmpmountpoint /media/var/tmp >> inherited from efiwpool/ROOT/init/var >> >> system not boot. >> >> Not found /boot/loader.efi (in BE system real path >> efiwpool/ROOT/init/boot/loader.efi) if copy this efiwpool/ROOT/init >> (blank in BE system) loader found this (but not found /boot/kernel) I >> can copy this and get a similar system >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184#c15 (with out >> msdos kernel part), but this ruin BE update mechanism > > Your dataset hierarchy is not what beadm expects. Specifically, you > have /boot separate from /, which I imagine is causing your problem. > /boot should be part of /. Also, you have several file systems in the > BE that are usually not in it; I doubt this is part of your boot > failure, though. > > For reference, here is my layout, which is mostly the same as the > default installation: > > NAME USED AVAIL REFER MOUNTPOINT > zroot 117G 108G96K none > zroot/ROOT 14.8G 108G96K none > zroot/ROOT/10.2 444K 108G 6.35G / > zroot/ROOT/103beta 14.8G 108G 8.75G / > zroot/ROOT/103beta1 8K 108G 8.17G / > zroot/ROOT/103beta3 8K 108G 8.75G / > zroot/home 97.8G 108G 94.9G /home > zroot/usr3.36G 108G96K /usr > zroot/usr/ports 985M 108G 736M /usr/ports > zroot/usr/src2.40G 108G 2.19G /usr/src > zroot/var2.19M 108G96K /var > zroot/var/audit96K 108G96K /var/audit > zroot/var/crash96K 108G96K /var/crash > zroot/var/log1.15M 108G 420K /var/log > zroot/var/mail360K 108G 120K /var/mail > zroot/var/tmp 416K 108G 144K /var/tmp > > Eric If remove efiwpool/ROOT/init/boot and copy his content on efiwpool/ROOT/init my scheme work fine too. /usr /var /home and other included in BE for consistent boot system (CURRENT world may not boot with kernel other rev), and old home snapshot sometimes useful for backup/restore ___ 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: EFI zfs loader and beadm?
On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: > Make sure you are running the latest snapshot of current or 10.3 as well, as > the MFC commits were in early February for 10-stable > >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> efiwpool/ROOT/init my scheme work fine too. >> /usr /var /home and other included in BE for consistent boot system >> (CURRENT world may not boot with kernel other rev), and old home >> snapshot sometimes useful for backup/restore >> ___ % uname -a FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: Wed Mar 9 01:16:17 MSK 2016 root@des.local:/usr/obj/usr/src/sys/X220 amd64 ___ 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: EFI zfs loader and beadm?
On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > presumably it boots now? > > On 10 March 2016 at 11:01, Andrey Fesenko wrote: >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: >> > Make sure you are running the latest snapshot of current or 10.3 as >> > well, as >> > the MFC commits were in early February for 10-stable >> > >> >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> >> efiwpool/ROOT/init my scheme work fine too. >> >> /usr /var /home and other included in BE for consistent boot system >> >> (CURRENT world may not boot with kernel other rev), and old home >> >> snapshot sometimes useful for backup/restore >> >> ___ >> >> % uname -a >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: >> Wed Mar 9 01:16:17 MSK 2016 >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > > My current working config % mount efiwpool/ROOT/init0 on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs, local, multilabel) efiwpool/ROOT/init0/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) efiwpool/ROOT/init0/usr on /usr (zfs, local, noatime, nfsv4acls) efiwpool/ROOT/init0/usr/home on /usr/home (zfs, local, noatime, nfsv4acls) efiwpool/ROOT/init0/var on /var (zfs, local, noatime, nfsv4acls) efiwpool/ROOT/init0/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/db on /var/db (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/db/pkg on /var/db/pkg (zfs, local, noatime, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/db/tlpkg on /var/db/tlpkg (zfs, local, noatime, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/empty on /var/empty (zfs, local, noatime, noexec, nosuid, read-only, nfsv4acls) efiwpool/ROOT/init0/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/mail on /var/mail (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/run on /var/run (zfs, local, noatime, noexec, nosuid, nfsv4acls) efiwpool/ROOT/init0/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls) => 40 234441568 ada1 GPT (112G) 40 1600 1 efi (800K) 1640 234439960 2 freebsd-zfs (112G) 234441600 8- free - (4.0K) % zfs get -r mountpoint efiwpool NAME PROPERTY VALUE SOURCE efiwpool mountpoint none local efiwpool/ROOT mountpoint none inherited from efiwpool efiwpool/ROOT/initmountpoint legacy local efiwpool/ROOT/init/tmpmountpoint /tmp local This work fine, booted, beadm create new env, activate them, see boot menu and select BE. % beadm list BEActive Mountpoint Space Created init - - 420.7M 2016-03-09 02:57 init0 NR / 35.9G 2016-03-10 05:00 If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) system not booted, efi loader (first stage) see only my pool, not found /boot/loader.efi ___ 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: EFI zfs loader and beadm?
On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: > As Eric said you cant have /boot on a separate dataset as the whole loader > bootstrap isnt designed too look for it on the dataset defined by bootfs. > Remember no other datasets are mounted at that stage of the bootstrap. > > You could maybe bodge something by manually playing around with the bootfs > property, symlinks and rootfs variables in the loader.conf. But why would > you want to do this? It's more work and non standard, and will break a lot? > > > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: >> >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: >> > presumably it boots now? >> > >> > On 10 March 2016 at 11:01, Andrey Fesenko wrote: >> >> >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: >> >> > Make sure you are running the latest snapshot of current or 10.3 as >> >> > well, as >> >> > the MFC commits were in early February for 10-stable >> >> > >> >> >> >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> >> >> efiwpool/ROOT/init my scheme work fine too. >> >> >> /usr /var /home and other included in BE for consistent boot system >> >> >> (CURRENT world may not boot with kernel other rev), and old home >> >> >> snapshot sometimes useful for backup/restore >> >> >> ___ >> >> >> >> % uname -a >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: >> >> Wed Mar 9 01:16:17 MSK 2016 >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 >> > >> > >> >> My current working config >> % mount >> >> >> This work fine, booted, beadm create new env, activate them, see boot >> menu and select BE. >> >> % beadm list >> BEActive Mountpoint Space Created >> init - - 420.7M 2016-03-09 02:57 >> init0 NR / 35.9G 2016-03-10 05:00 >> >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) >> system not booted, efi loader (first stage) see only my pool, not >> found /boot/loader.efi > > It probably does not matter, as bootfs have snapshots (BE), just wanted to make it more clear (having taken significant mountpoint /boot, /usr, /var... in zfs dataset) and was surprised why the system does not boot It is clear that as long as the functionality is experimental and under development, but would like to see where the full instructions on its implementation / restrictions, at least as early as has been described https://wiki.freebsd.org/RootOnZFS ___ 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: EFI zfs loader and beadm?
On Fri, Mar 11, 2016 at 10:52 AM, krad wrote: > Its also worth pointing that if you decouple the userland from the kernel > files you no longer have a boot environment, as all the basic stuff to boot > the os isn't contained within the bootfs. I'm still struggling to see why > /boot needs to be on a different dataset, its just a bit of a linuxism. > > On 10 March 2016 at 19:23, Trond Endrestøl > wrote: >> >> On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: >> >> > On Thu, Mar 10, 2016 at 6:11 PM, krad wrote: >> > > As Eric said you cant have /boot on a separate dataset as the whole >> > > loader >> > > bootstrap isnt designed too look for it on the dataset defined by >> > > bootfs. >> > > Remember no other datasets are mounted at that stage of the bootstrap. >> > > >> > > You could maybe bodge something by manually playing around with the >> > > bootfs >> > > property, symlinks and rootfs variables in the loader.conf. But why >> > > would >> > > you want to do this? It's more work and non standard, and will break a >> > > lot? >> > > >> > > >> > > >> > > On 10 March 2016 at 12:11, Andrey Fesenko wrote: >> > >> >> > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: >> > >> > presumably it boots now? >> > >> > >> > >> > On 10 March 2016 at 11:01, Andrey Fesenko >> > >> > wrote: >> > >> >> >> > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad wrote: >> > >> >> > Make sure you are running the latest snapshot of current or 10.3 >> > >> >> > as >> > >> >> > well, as >> > >> >> > the MFC commits were in early February for 10-stable >> > >> >> > >> > >> >> >> >> > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on >> > >> >> >> efiwpool/ROOT/init my scheme work fine too. >> > >> >> >> /usr /var /home and other included in BE for consistent boot >> > >> >> >> system >> > >> >> >> (CURRENT world may not boot with kernel other rev), and old >> > >> >> >> home >> > >> >> >> snapshot sometimes useful for backup/restore >> > >> >> >> ___ >> > >> >> >> > >> >> % uname -a >> > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 >> > >> >> r296548: >> > >> >> Wed Mar 9 01:16:17 MSK 2016 >> > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 >> > >> > >> > >> > >> > >> >> > >> My current working config >> > >> % mount >> > >> >> > >> >> > >> This work fine, booted, beadm create new env, activate them, see boot >> > >> menu and select BE. >> > >> >> > >> % beadm list >> > >> BEActive Mountpoint Space Created >> > >> init - - 420.7M 2016-03-09 02:57 >> > >> init0 NR / 35.9G 2016-03-10 05:00 >> > >> >> > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) >> > >> system not booted, efi loader (first stage) see only my pool, not >> > >> found /boot/loader.efi >> > > >> > > >> > >> > It probably does not matter, as bootfs have snapshots (BE), just >> > wanted to make it more clear (having taken significant mountpoint >> > /boot, /usr, /var... in zfs dataset) and was surprised why the system >> > does not boot >> > >> > It is clear that as long as the functionality is experimental and >> > under development, but would like to see where the full instructions >> > on its implementation / restrictions, at least as early as has been >> > described https://wiki.freebsd.org/RootOnZFS >> >> If you keep /boot as a separate dataset/filesystem, with >> efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not >> see a /boot directory inside that dataset. The files and directories >> from /boot will be presented as living in /, the local root directory >> of that dataset. >> >> You could create a /boot/boot symlink pointing to . (dot), but it's >> better to let /boot be part of the regular boot environment, pretty >> similar to what you would find on a UFS system using a separate root >> filesystem. >> why? On the contrary, my scheme involves the entire system as a single BE (including home) > linuxism Is unlikely, to rather an attempt to use all the features ZFS. ZFS also many possible settings for each dataset/FS (compression, atime, exec..) Probably for /boot many of them unnecessary, but such separate extra snapshots, can would not be harmful ___ 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: rpi-b leds
On Mon, Aug 22, 2016 at 1:29 PM, Daniel Braniss wrote: > Hi, > I see that now both leds on the rpi-2 are operational, > any chance it can happen on the rpi-b too? > A year or two ago, rpi-b had operational leds, it's make not working after rework fdt/std layer ___ 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: rpi-b leds
On Tue, Aug 23, 2016 at 1:00 AM, Luiz Otavio O Souza wrote: > On 22 August 2016 at 08:55, Andrey Fesenko wrote: >> On Mon, Aug 22, 2016 at 1:29 PM, Daniel Braniss wrote: >>> Hi, >>> I see that now both leds on the rpi-2 are operational, >>> any chance it can happen on the rpi-b too? >>> >> >> A year or two ago, rpi-b had operational leds, it's make not working >> after rework fdt/std layer > > I tested the leds on two different rpi-b and the leds are working. > Maybe you are talking about the b+ model ? > > The ACT or OK led for the old boards (< b+) are wired to gpio 16. The > b+ has two leds, they are wired to pins 47 and 35. > > For a quick fix, edit your dts and the leds will work. > > Can you check the board revision for your rpi ? (sysctl hw.board.revision) > > These are the ones I tested: > > hw.board.revision: 3 > hw.board.revision: 14 > > Tested with r301978. > > Luiz Sorry for misinformation Raspberry Pi Model B (Rev 2.0, 512Mb): hw.board.revision: 15 leds work after complete boot ___ 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: i915kms breakage
On Fri, Apr 28, 2017 at 10:10 PM, Maurizio Vairani wrote: > 2017-04-22 14:47 GMT+02:00 Domagoj Stolfa : > >> Hello, >> >> ever since I've merged yesterday, it would seem that the i915kms driver >> panics every time it is loaded. Unfortunately, I am not able to provide >> a dump of the panic, as I am unable to see what the panic is, or what is >> even going on as a matter of fact due to my screen being overtaken by >> a driver that has just panicked. call doadump() does not seem to work >> either. >> >> Is anyone else having these problems, or know where the issue might be >> occurring? >> >> The same happens with 12.0-CURRENT r317513 updated yesterday. The laptop > is a Samsung NP270E5E with Intel Graphics 4000, > http://www.samsung.com/us/computer/pcs/NP270E5E-K02US-specs > -- i5 r317402 and r317437 run only single mode, after r317561 work Xorg again :) ___ 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: make buildworld broken at r317821 (libsysdecode)
On Fri, May 5, 2017 at 8:41 PM, Kyle Evans wrote:
> On Fri, May 5, 2017 at 9:31 AM, Kyle Evans wrote:
>
>> On May 5, 2017 8:39 AM, "Dimitry Andric" wrote:
>>
>>
>> This appears to be caused by bsdgrep. :-/ The build for lib/libsysdecode
>> uses a shell script, mkioctls, to generate a ioctl.c file at build time.
>> This script contains the following fragment:
>>
>> ioctl_includes=$(
>> cd $includedir
>> find -H -s * -name '*.h' | \
>> egrep -v '(.*disk.*|net/pfvar|net/if_pfsync)\.h' | \
>> xargs egrep -l \
>> '^#[]*define[ ]+[A-Za-z_][A-Za-z0-9_]*[ ]+_IO[^a-z0-9_]' |
>> awk '{printf("#include <%s>\\n", $1)}'
>> )
>>
>> The idea is that all headers are searched for defines of ioctl macros,
>> which start with _IO. The -l option to egrep is used to print only the
>> matching filenames, not the matched content itself.
>>
>> However, this option seems to be broken in bsdgrep, as it *does* display
>> the matched content:
>>
>> $ gnugrep -l printf /usr/include/stdio.h
>> /usr/include/stdio.h
>>
>> $ bsdgrep -l printf /usr/include/stdio.h
>> #define __SSTR 0x0200 /* this is an sprintf/snprintf string */
>> /usr/include/stdio.h
>>
>> I did a quick check, and this option seems to have been accidentally
>> broken by r317703 [1] ("bsdgrep: fix -w flag matching with an empty
>> pattern").
>>
>> Ed, Kyle, any idea where the problem might be?
>>
>> -Dimitry
>>
>> [1] https://svnweb.freebsd.org/base?view=revision&revision=317703
>>
>>
>> Hi,
>>
>> This is addressed by https://reviews.freebsd.org/D10607
>>
>
> FYI- This has now been committed as r317842. Apologies for the breakage,
> and thanks for the reports!
Build not fixed (but is built slightly, a little more) :(
# uname -a
FreeBSD des.local 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r317592: Sat
Apr 29 21:32:04 MSK 2017 root@des.local:/usr/obj/usr/src/sys/DES
amd64
# svnlite info
Path: .
Working Copy Root Path: /usr/src
URL: https://svn0.eu.freebsd.org/base/head
Relative URL: ^/head
Repository Root: https://svn0.eu.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 317842
Node Kind: directory
Schedule: normal
Last Changed Author: emaste
Last Changed Rev: 317842
Last Changed Date: 2017-05-05 20:35:05 +0300 (Fri, 05 May 2017)
# make -j1 buildworld
make[1]: "/usr/src/Makefile.inc1"
line 160: SYSTEM_COMPILER: Determined that CC=cc matches the source
tree. Not bootstrapping a cross-compiler.
...
===> lib/clang/libllvmminimal (obj,all,install)
/usr/obj/usr/src/tmp/usr/src/lib/clang/libllvmminimal created for
/usr/src/lib/clang/libllvmminimal
/usr/obj/usr/src/tmp/usr/src/lib/clang/libllvmminimal/Support created
for /usr/src/lib/clang/libllvmminimal
/usr/obj/usr/src/tmp/usr/src/lib/clang/libllvmminimal/TableGen created
for /usr/src/lib/clang/libllvmminimal
c++ -O2 -pipe -I/usr/src/lib/clang/include
-I/usr/src/contrib/llvm/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD
-D__STDC_LIMIT_M
ACROS -D__STDC_CONSTANT_MACROS
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\"
-DLLVM_HOST_TRIPLE=\"x86_64-unknow
n-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\"
-ffunction-sections -fdata-sections -MD -MF.depend.Support_APInt.o
-MTSupport/APInt.o -Qunused-arguments
-I/usr/obj/usr/src/tmp/legacy/usr/include -std=c++11 -fno-exceptions
-fno-rtti -stdli
b=libc++ -Wno-c++11-extensions -c
/usr/src/contrib/llvm/lib/Support/APInt.cpp -o Support/APInt.o
c++: error: unable to execute command: Segmentation fault (core
dumped)
c++: error: clang frontend command failed due to signal (use -v to see
invocation)
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on
LLVM 4.0.0)
Target: x86_64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /usr/bin
c++: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.freebsd.org/submit/ and include the crash backtrace, p$
eprocessed source, and associated run script.
...
___
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: make buildworld broken at r317821 (libsysdecode)
On Sat, May 6, 2017 at 2:52 AM, Ngie Cooper wrote: > On Fri, May 5, 2017 at 4:43 PM, Cy Schubert wrote: > > ... > >> You have a bad DIMM. I had this same problem on my laptop but not on my >> servers downstairs. That suggested that since all four machines were >> running the same software the difference between them was hardware. >> Replacing the memory in my laptop made this problem go away. >> >> I have a question for you. Do you use ZFS? ZFS exercises memory quite >> aggressively. I also had this problem when I replaced my UFS filesystems >> with ZFS on my testbed many moons ago. It even suffered random kernel >> panics. Here again, replacing the memory resolved the issue. > > We need more information first before saying "bad hardware" -- in > particular, was the machine overtaxed, were the input files proper, > etc? > > I'm asking because clang has a number of bugs in bugzilla where the > host ran out of memory trying to compile things and clang didn't fail > gracefully when allocating memory, handling inputs, etc. > > Thanks, > -Ngie Sorry, really my root ZFS pool is corrupt :( ___ 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 9.0-BETA3 Available...
On Thu, Sep 29, 2011 at 5:42 AM, Ken Smith wrote: > > > The 9.0-RELEASE cycle will be tracked here: > > http://wiki.freebsd.org/Releng/9.0TODO > > though the schedule listed there is still way off. We'll re-work the > schedule some time soon. > Last updated: 16 August 2011. :( ___ 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: About FreeBSD 9.0 release note
On Wed, Oct 19, 2011 at 2:07 AM, Hiroki Sato wrote: > Hideki Yamamoto wrote > in : > > hy> Hi, > hy> > hy> Does someone know where is the draft of FreeBSD 9.0 release note? > hy> I would like to check if there is a description about new functions > hy> about MLDv2 is included or not. > hy> I think the below feature should be included in the release note as > hy> IPv6 network is getting popular. > hy> > hy> - > hy> MFC r200871: > hy> Use ALLOW_NEW_SOURCES and BLOCK_OLD_SOURCES to signal a join or leave > hy> with SSM MLDv2 by default. > hy> This is current practice and complies with RFC 4604, as well as being > hy> required by production IPv6 networks in Japan. > hy> The behaviour may be disabled by setting the net.inet6.mld.use_allow > hy> sysctl/tunable to 0. > hy> - > > I am already working on the relnotes and the above will be included > as an improvement of the IPv6 stack. > If you're not complicated. Maybe we should put a draft on the wiki? ___ 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 9.0-RC1 Available...
On Sun, Oct 23, 2011 at 7:43 AM, Ken Smith wrote: > > The 9.0-RELEASE cycle will be tracked here: > > http://wiki.freebsd.org/Releng/9.0-TODO > link error, need http://wiki.freebsd.org/Releng/9.0TODO still no actual information on this page. Branch status not actual. ___ 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"
gptboot rewrite, bootonce, etc.
This work if use ZFS? My issues "Root on ZFS & GPT and boot to ufs partition" http://lists.freebsd.org/pipermail/freebsd-fs/2012-January/013514.html I test # gpart show => 34 625142381 ada0 GPT (298G) 34128 1 freebsd-boot (64k) 162 26621952 2 freebsd-ufs [bootonce,bootme] (12G) 266221148388608 3 freebsd-swap (4.0G) 35010722 590131693 4 freebsd-zfs (281G) system ada0p2 not boot. ___ 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"
AR9285 not see n-channels
I have # uname -a FreeBSD beastie.mydomain.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r243259: Mon Nov 19 09:28:08 MSK 2012 root@beastie.mydomain.local:/usr/obj/usr/src/sys/W_BOOK amd64 # grep ATH /usr/src/sys/amd64/conf/W_BOOK options ATH_ENABLE_11N options ATH_DEBUG options ATH_DIAGAPI pciconf ath0@pci0:5:0:0:class=0x028000 card=0xe016105b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9285 Wireless Network Adapter (PCI-Express)' class = network # ifconfig -v wlan0 list channel Channel 1 : 2412 MHz 11b Channel 7 : 2442 MHz 11g ht/20 Channel 1 : 2412 MHz 11g Channel 8 : 2447 MHz 11b Channel 1 : 2412 MHz 11g ht/20Channel 8 : 2447 MHz 11g Channel 2 : 2417 MHz 11b Channel 8 : 2447 MHz 11g ht/20 Channel 2 : 2417 MHz 11g Channel 9 : 2452 MHz 11b wi-fi router have and enable n-mode (linksys e4200) How to turn on or activate n-mode? ___ 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: AR9285 not see n-channels
On Thu, Dec 13, 2012 at 4:32 AM, Adrian Chadd wrote: > What's 'ifconfig wlan0' and 'ifconfig wlan0 list sta' look like? > > > > adrian > > > On 12 December 2012 15:51, Andrey Fesenko wrote: >> I have >> # uname -a >> FreeBSD beastie.mydomain.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 >> r243259: Mon Nov 19 09:28:08 MSK 2012 >> root@beastie.mydomain.local:/usr/obj/usr/src/sys/W_BOOK amd64 >> # grep ATH /usr/src/sys/amd64/conf/W_BOOK >> options ATH_ENABLE_11N >> options ATH_DEBUG >> options ATH_DIAGAPI >> >> pciconf >> ath0@pci0:5:0:0:class=0x028000 card=0xe016105b chip=0x002b168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR9285 Wireless Network Adapter (PCI-Express)' >> class = network >> >> >> # ifconfig -v wlan0 list channel >> Channel 1 : 2412 MHz 11b Channel 7 : 2442 MHz 11g >> ht/20 >> Channel 1 : 2412 MHz 11g Channel 8 : 2447 MHz 11b >> Channel 1 : 2412 MHz 11g ht/20Channel 8 : 2447 MHz 11g >> Channel 2 : 2417 MHz 11b Channel 8 : 2447 MHz 11g >> ht/20 >> Channel 2 : 2417 MHz 11g Channel 9 : 2452 MHz 11b >> >> >> wi-fi router have and enable n-mode (linksys e4200) >> How to turn on or activate n-mode? # ifconfig wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 58:6d:8f:fa:d9:505 12 72M 27.50 2079 31872 EP AQEHTRS RSN HTCAP WME WPS # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 4c:0f:6e:4b:4e:f5 inet 192.168.1.41 netmask 0xff00 broadcast 192.168.1.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid hometest channel 12 (2467 MHz 11g ht/20) bssid 58:6d:8f:fa:d9:50 regdomain 101 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 bmiss 7 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 4 shortgi wme burst roaming MANUAL ___ 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: AR9285 not see n-channels
On Thu, Dec 13, 2012 at 4:44 AM, Adrian Chadd wrote: > Yup. It's doing 11n rates. > > Compile and run athstats, it'll tell you how many aggregate frames are being > sent and received. > > > > Adrian > > Sent from my Palm Pre on AT&T > > ________ > On Dec 12, 2012 4:39 PM, Andrey Fesenko wrote: > > On Thu, Dec 13, 2012 at 4:32 AM, Adrian Chadd wrote: >> What's 'ifconfig wlan0' and 'ifconfig wlan0 list sta' look like? >> >> >> >> adrian >> >> >> On 12 December 2012 15:51, Andrey Fesenko wrote: >>> I have >>> # uname -a >>> FreeBSD beastie.mydomain.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 >>> r243259: Mon Nov 19 09:28:08 MSK 2012 >>> root@beastie.mydomain.local:/usr/obj/usr/src/sys/W_BOOK amd64 >>> # grep ATH /usr/src/sys/amd64/conf/W_BOOK >>> options ATH_ENABLE_11N >>> options ATH_DEBUG >>> options ATH_DIAGAPI >>> >>> pciconf >>> ath0@pci0:5:0:0: class=0x028000 card=0xe016105b chip=0x002b168c >>> rev=0x01 hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> device = 'AR9285 Wireless Network Adapter (PCI-Express)' >>> class = network >>> >>> >>> # ifconfig -v wlan0 list channel >>> Channel 1 : 2412 MHz 11b Channel 7 : 2442 MHz 11g ht/20 >>> Channel 1 : 2412 MHz 11g Channel 8 : 2447 MHz 11b >>> Channel 1 : 2412 MHz 11g ht/20 Channel 8 : 2447 MHz 11g >>> Channel 2 : 2417 MHz 11b Channel 8 : 2447 MHz 11g ht/20 >>> Channel 2 : 2417 MHz 11g Channel 9 : 2452 MHz 11b >>> >>> >>> wi-fi router have and enable n-mode (linksys e4200) >>> How to turn on or activate n-mode? > > # ifconfig wlan0 list sta > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 58:6d:8f:fa:d9:50 5 12 72M 27.5 0 2079 31872 EP AQEHTRS > RSN HTCAP WME WPS > # ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 4c:0f:6e:4b:4e:f5 > inet 192.168.1.41 netmask 0xff00 broadcast 192.168.1.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > ssid hometest channel 12 (2467 MHz 11g ht/20) bssid 58:6d:8f:fa:d9:50 > regdomain 101 indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 bmiss 7 > scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 4 shortgi wme > burst roaming MANUAL # ./athstats 526213 data frames received 10205data frames transmit 79 short on-chip tx retries 103 long on-chip tx retries 16 tx failed 'cuz too many retries 220 mib overflow interrupts MCS7 current transmit rate 1watchdog timeouts 42 beacon miss interrupts 23154rx failed 'cuz of bad CRC 56 rx failed 'cuz of PHY err 56 illegal service 1638 periodic calibrations -0/+0TDMA slot adjust (usecs, smoothed) 56 rssi of last ack 50 avg recv rssi -96 rx noise floor 13 phantom beacon misses 6569 tx frames through raw api 1460 A-MPDU sub-frames received 183 Half-GI frames received 183 40MHz frames received 2397 CRC errors for non-last A-MPDU subframes 3151 Frames transmitted with HT Protection 25 A-MPDU sub-frame TX attempt success 2first step level 1OFDM weak signal detect 268 listen time 190 ANI increased spur immunity 174 ANI decrease spur immunity 2ANI enabled OFDM weak signal detect 3517 ANI disabled OFDM weak signal detect 3515 ANI disabled CCK weak signal threshold 4ANI increased first step level 2ANI decreased first step level 154772 cumulative OFDM phy error count 528256 cumulative CCK phy error count 851 ANI forced listen time to zero 26 missing ACK's 78 RTS without CTS 3135 successful RTS 65747bad FCS 473007 beacons received 53 average rssi (beacons only) 35 average rssi (all rx'd frames) 48 average rssi (ACKs only) Antenna profile: [0] tx10173 rx4 [1] tx0 rx 526209 # ./athaggrstats 17 single frames scheduled 9aggregate frames scheduled 1217 single frames scheduled due to low HWQ depth Aggregate size profile: 0:0 1:0 2:6 3:2 4:0 5:0 6:0 7:1 8:0 9:0 10:0 11:0 ___ 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: AR9285 not see n-channels
On Thu, Dec 13, 2012 at 4:55 AM, Adrian Chadd wrote: > .. yup, you're doing 11n! Welcome! > > > > Adrian > > On 12 December 2012 16:54, Andrey Fesenko wrote: >> On Thu, Dec 13, 2012 at 4:44 AM, Adrian Chadd wrote: >>> Yup. It's doing 11n rates. >>> >>> Compile and run athstats, it'll tell you how many aggregate frames are being >>> sent and received. >>> >>> >>> >>> Adrian >>> >>> Sent from my Palm Pre on AT&T >>> >>> >>> On Dec 12, 2012 4:39 PM, Andrey Fesenko wrote: >>> >>> On Thu, Dec 13, 2012 at 4:32 AM, Adrian Chadd wrote: >>>> What's 'ifconfig wlan0' and 'ifconfig wlan0 list sta' look like? >>>> >>>> >>>> >>>> adrian >>>> >>>> >>>> On 12 December 2012 15:51, Andrey Fesenko wrote: >>>>> I have >>>>> # uname -a >>>>> FreeBSD beastie.mydomain.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 >>>>> r243259: Mon Nov 19 09:28:08 MSK 2012 >>>>> root@beastie.mydomain.local:/usr/obj/usr/src/sys/W_BOOK amd64 >>>>> # grep ATH /usr/src/sys/amd64/conf/W_BOOK >>>>> options ATH_ENABLE_11N >>>>> options ATH_DEBUG >>>>> options ATH_DIAGAPI >>>>> >>>>> pciconf >>>>> ath0@pci0:5:0:0: class=0x028000 card=0xe016105b chip=0x002b168c >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Atheros Communications Inc.' >>>>> device = 'AR9285 Wireless Network Adapter (PCI-Express)' >>>>> class = network >>>>> >>>>> >>>>> # ifconfig -v wlan0 list channel >>>>> Channel 1 : 2412 MHz 11b Channel 7 : 2442 MHz 11g ht/20 >>>>> Channel 1 : 2412 MHz 11g Channel 8 : 2447 MHz 11b >>>>> Channel 1 : 2412 MHz 11g ht/20 Channel 8 : 2447 MHz 11g >>>>> Channel 2 : 2417 MHz 11b Channel 8 : 2447 MHz 11g ht/20 >>>>> Channel 2 : 2417 MHz 11g Channel 9 : 2452 MHz 11b >>>>> >>>>> >>>>> wi-fi router have and enable n-mode (linksys e4200) >>>>> How to turn on or activate n-mode? >>> >>> # ifconfig wlan0 list sta >>> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >>> 58:6d:8f:fa:d9:50 5 12 72M 27.5 0 2079 31872 EP AQEHTRS >>> RSN HTCAP WME WPS >>> # ifconfig wlan0 >>> wlan0: flags=8843 metric 0 mtu 1500 >>> ether 4c:0f:6e:4b:4e:f5 >>> inet 192.168.1.41 netmask 0xff00 broadcast 192.168.1.255 >>> nd6 options=29 >>> media: IEEE 802.11 Wireless Ethernet MCS mode 11ng >>> status: associated >>> ssid hometest channel 12 (2467 MHz 11g ht/20) bssid 58:6d:8f:fa:d9:50 >>> regdomain 101 indoor ecm authmode WPA2/802.11i privacy ON >>> deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 bmiss 7 >>> scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 4 shortgi wme >>> burst roaming MANUAL >> >> # ./athstats >> 526213 data frames received >> 10205data frames transmit >> 79 short on-chip tx retries >> 103 long on-chip tx retries >> 16 tx failed 'cuz too many retries >> 220 mib overflow interrupts >> MCS7 current transmit rate >> 1watchdog timeouts >> 42 beacon miss interrupts >> 23154rx failed 'cuz of bad CRC >> 56 rx failed 'cuz of PHY err >> 56 illegal service >> 1638 periodic calibrations >> -0/+0TDMA slot adjust (usecs, smoothed) >> 56 rssi of last ack >> 50 avg recv rssi >> -96 rx noise floor >> 13 phantom beacon misses >> 6569 tx frames through raw api >> 1460 A-MPDU sub-frames received >> 183 Half-GI frames received >> 183 40MHz frames received >> 2397 CRC errors for non-last A-MPDU subframes >> 3151 Frames transmitted with HT Protection >> 25 A-MPDU sub-frame TX attempt success >> 2first step level >> 1OFDM weak signal detect >> 268 listen time >> 190 ANI increased spur immunity >> 174 ANI decrease spur immunity >> 2ANI enabled OFDM weak signal detect >> 3517 ANI disabled OFDM weak signal detect >> 3515 ANI disab
Re: AR9285 not see n-channels
On Thu, Dec 13, 2012 at 5:33 AM, Adrian Chadd wrote: > Hi, > > The AR9285 is a 2GHz only NIC. > > The channel list shows 11b, 11bg, HT20 and HT40 channels. > > It all looks right, why don't you think it is? > > > Adrian > > > On 12 December 2012 17:32, Andrey Fesenko wrote: >> On Thu, Dec 13, 2012 at 4:55 AM, Adrian Chadd wrote: >>> .. yup, you're doing 11n! Welcome! >>> >>> >>> >>> Adrian >>> >>> On 12 December 2012 16:54, Andrey Fesenko wrote: >>>> On Thu, Dec 13, 2012 at 4:44 AM, Adrian Chadd >>>> wrote: >>>>> Yup. It's doing 11n rates. >>>>> >>>>> Compile and run athstats, it'll tell you how many aggregate frames are >>>>> being >>>>> sent and received. >>>>> >>>>> >>>>> >>>>> Adrian >>>>> >>>>> Sent from my Palm Pre on AT&T >>>>> >>>>> >>>>> On Dec 12, 2012 4:39 PM, Andrey Fesenko wrote: >>>>> >>>>> On Thu, Dec 13, 2012 at 4:32 AM, Adrian Chadd wrote: >>>>>> What's 'ifconfig wlan0' and 'ifconfig wlan0 list sta' look like? >>>>>> >>>>>> >>>>>> >>>>>> adrian >>>>>> >>>>>> >>>>>> On 12 December 2012 15:51, Andrey Fesenko wrote: >>>>>>> I have >>>>>>> # uname -a >>>>>>> FreeBSD beastie.mydomain.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 >>>>>>> r243259: Mon Nov 19 09:28:08 MSK 2012 >>>>>>> root@beastie.mydomain.local:/usr/obj/usr/src/sys/W_BOOK amd64 >>>>>>> # grep ATH /usr/src/sys/amd64/conf/W_BOOK >>>>>>> options ATH_ENABLE_11N >>>>>>> options ATH_DEBUG >>>>>>> options ATH_DIAGAPI >>>>>>> >>>>>>> pciconf >>>>>>> ath0@pci0:5:0:0: class=0x028000 card=0xe016105b chip=0x002b168c >>>>>>> rev=0x01 hdr=0x00 >>>>>>> vendor = 'Atheros Communications Inc.' >>>>>>> device = 'AR9285 Wireless Network Adapter (PCI-Express)' >>>>>>> class = network >>>>>>> >>>>>>> >>>>>>> # ifconfig -v wlan0 list channel >>>>>>> Channel 1 : 2412 MHz 11b Channel 7 : 2442 MHz 11g ht/20 >>>>>>> Channel 1 : 2412 MHz 11g Channel 8 : 2447 MHz 11b >>>>>>> Channel 1 : 2412 MHz 11g ht/20 Channel 8 : 2447 MHz 11g >>>>>>> Channel 2 : 2417 MHz 11b Channel 8 : 2447 MHz 11g ht/20 >>>>>>> Channel 2 : 2417 MHz 11g Channel 9 : 2452 MHz 11b >>>>>>> >>>>>>> >>>>>>> wi-fi router have and enable n-mode (linksys e4200) >>>>>>> How to turn on or activate n-mode? >>>>> >>>>> # ifconfig wlan0 list sta >>>>> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >>>>> 58:6d:8f:fa:d9:50 5 12 72M 27.5 0 2079 31872 EP AQEHTRS >>>>> RSN HTCAP WME WPS >>>>> # ifconfig wlan0 >>>>> wlan0: flags=8843 metric 0 mtu >>>>> 1500 >>>>> ether 4c:0f:6e:4b:4e:f5 >>>>> inet 192.168.1.41 netmask 0xff00 broadcast 192.168.1.255 >>>>> nd6 options=29 >>>>> media: IEEE 802.11 Wireless Ethernet MCS mode 11ng >>>>> status: associated >>>>> ssid hometest channel 12 (2467 MHz 11g ht/20) bssid 58:6d:8f:fa:d9:50 >>>>> regdomain 101 indoor ecm authmode WPA2/802.11i privacy ON >>>>> deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 bmiss 7 >>>>> scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 4 shortgi wme >>>>> burst roaming MANUAL >>>> >>>> # ./athstats >>>> 526213 data frames received >>>> 10205data frames transmit >>>> 79 short on-chip tx retries >>>> 103 long on-chip tx retries >>>> 16 tx failed 'cuz too many retries >>>> 220 mib overflow interrupts >>>> MCS7 current transmit rate >>>> 1watchdog timeouts >>>> 42 beacon miss interrupts >>>> 23154rx failed 'cuz of bad
Re: x220 notes
On Wed, Mar 14, 2012 at 11:15 PM, Hannes Mehnert wrote: > Ciao, > > On 03/14/2012 00:38, matt wrote: >> I have brightness control through raw acpi..."\_BCL" and friends seem to >> do nothing. >> >> Most of the video methods differentiate between \VIGD (which seems to be >> a check for integrated graphics vs optimus, but that's still a guess) >> If \VIGD is true, brightness commands are sent to the EC, where they >> don't seem to do much yet. This is probably where we could enable >> something via EC/ibm-acpi? >> If \VIGD is false, brightness commands are handled in ACPI, although >> coarsely, via \VBRC. >> >> \VBRC seems to allow control over the backlight, at least, so those of >> you with sore eyes or the 3-cell battery may have some success using the >> acpi_call port (Danger!) >> kldload acpi_call >> acpi_call -p '\VBRC' -i n (where n is 0-10) > > Great news! Works for me. n is actually 0-16 (plus any other value which > turns the backlight off (-1 or 17 eg). > > > Thanks, > > Hannes Thanks, acpi_call -p '\VBRC' -i n [0-15] work fine, if set 17 black screen :) And other problems. 1) wi-fi standart rtl8192cu - not work change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS dev.acpi_ibm.0.wlan: 1 <- read only hardware switch work, not send mesage 2) sound # cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: (play/rec) pcm1: (play/rec) default pcm2: (play) pcm3: (play) pcm4: (play) sound headphones only, if set sysctl hw.snd.default_unit=0 and restart application, on's speakers (if remove headphones). Automatic switching possible? 2.2) sound control in mplayer automatic fine work multimedia key multimedia key and system mixer, and sysctl not work xev data VolUP, VolDn, mute (release event similar) KeyPress event, serial 27, synthetic NO, window 0x1e1, root 0x120, subw 0x0, time 210234226, (623,634), root:(623,650), state 0x10, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0x1e1, root 0x120, subw 0x0, time 210235273, (623,634), root:(623,650), state 0x10, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0x1e1, root 0x120, subw 0x0, time 210241638, (623,634), root:(623,650), state 0x10, keycode 140 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False 3) ACPI work poorly 191 0x81f01000 37c7 acpi_video.ko 201 0x81f05000 330f acpi_ibm.ko 211 0x81f09000 1fc acpi_call.ko # sysctl -a | grep ibm acpi_ibm0: on acpi0 acpi_ibm0: detached acpi_ibm0: on acpi0 dev.acpi_ibm.0.%desc: IBM ThinkPad ACPI Extras dev.acpi_ibm.0.%driver: acpi_ibm dev.acpi_ibm.0.%location: handle=\_SB_.PCI0.LPC_.EC__.HKEY dev.acpi_ibm.0.%pnpinfo: _HID=LEN0068 _UID=0 dev.acpi_ibm.0.%parent: acpi0 dev.acpi_ibm.0.initialmask: 2060 dev.acpi_ibm.0.availmask: 134217727 dev.acpi_ibm.0.events: 1 dev.acpi_ibm.0.eventmask: 134217727 dev.acpi_ibm.0.hotkey: 3353 dev.acpi_ibm.0.lcd_brightness: 0 <- not work dev.acpi_ibm.0.volume: 0 <- not work dev.acpi_ibm.0.mute: 0 <- not work dev.acpi_ibm.0.thinklight: 0 <- work fine :) dev.acpi_ibm.0.bluetooth: 0 <- work LED (bt not use, not test) dev.acpi_ibm.0.wlan: 1 <- read only dev.acpi_ibm.0.fan_speed: 3880 <- not work or read only dev.acpi_ibm.0.fan_level: 0 dev.acpi_ibm.0.fan: 1 LED HDD may be work blink infrequently SSD :) 3) video work acceptable WITH_NEW_XORG=true WITH_KMS=true from terminal adjustable brightness acpi_call -p '\VBRC' -i n [0-15] I would like to consolidate these actions on the standard key # cat /var/run/devd.pipe !system=ACPI subsystem=IBM type=\_SB_.PCI0.LPC_.EC__.HKEY notify=0x10 ( Fn+Home) !system=ACPI subsystem=IBM type=\_SB_.PCI0.LPC_.EC__.HKEY notify=0x11 (Fn+End) 4) mouse Xorg with out config standard trackpad and other work fine if hook up USB mouse not work Jan 27 17:53:23 x220 kernel: ugen1.3: at usbus1 Jan 27 17:53:23 x220 kernel: ums0: on usbus1 Jan 27 17:53:23 x220 kernel: ums0: 8 buttons and [XYZ] coordinates ID=0 and disconnect Jan 27 17:53:42 x220 kernel: ugen1.3: at usbus1 (disconnected) Jan 27 17:53:42 x220 kernel: ums0: at uhub3, port 2, addr 3 (disconnected) 5) suspend/resume not test while, if there is a manual will be grateful Trick, to work without xorg.conf :) # cat /home/andrey/.xsession /usr/local/bin/xset +fp /usr/local/lib/X11/fonts/terminus-font/ <- need some applications xkbset -b <- hate beep setxkbmap -layout "us,ru" -option "grp:caps_toggle,grp_led:caps" <- for two layouts and indication ... <-favorite WM % uname -a FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r
Re: x220 notes
On Thu, Jan 31, 2013 at 8:56 AM, Thomas Mueller wrote: > Excerpt from Andrey Fesenko : > >> And other problems. >> 1) wi-fi >> standart rtl8192cu - not work >> change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS >> dev.acpi_ibm.0.wlan: 1 <- read only >> hardware switch work, not send mesage > > What did you try to make rtl8192cu work? Did you try NDIS? > > I have Hiro USB wireless adapter with rtl8191s chip, am still trying, on and > off, to get it to work. > > OpenBSD has urtwn driver that should work, ported to NetBSD, but why not > FreeBSD? ALso, there is a Linux driver. > > Tom NDIS failed to raise working version. Win driver terrible ~5 firmware and other. urtwn such as usb devices and no porting FreeBSD only dirty hack http://lists.freebsd.org/pipermail/freebsd-wireless/2012-November/002539.html just wanted to get wi-fi n-mode :) actively developed now like only ath. ___ 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"
SDL No available video device (sdl12 installed)
Hello, do not run the game using sdl. % uname -a FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r246229: Sat Feb 2 17:42:00 UTC 2013 andrey@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 # cat /etc/make.conf WITH_NEW_XORG=true WITH_KMS=true X.Org X Server 1.10.6 Release Date: 2012-02-10 intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2+) # pkg info | grep ^sdl sdl-1.2.15_2,2 Cross-platform multimedia development API sdl_gfx-2.0.23 SDL graphics drawing primitives and other support functions sdl_image-1.2.12_1 A simple library to load images of various formats as SDL surfaces sdl_mixer-1.2.12_2 A sample multi-channel audio mixer library sdl_net-1.2.8 A small sample cross-platform networking library sdl_pango-0.1.2_7 SDL_Pango is the SDL API to the Pango text rendering engine of GNOME 2.x sdl_ttf-2.0.11 A library to use TrueType fonts to render text in SDL applications % sdl-config --version 1.2.15 % sdl-config --libs -L/usr/local/lib -Wl,-rpath,/usr/local/lib -lSDL -pthread % sdl-config --cflags -I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1 -D_REENTRANT % ufo ... --- video initialization --- Video SDL_Init failed: No available video device % openttd -I OpenGFX -S OpenSFX -M OpenMSX Error: Couldn't find any suitable video driver % openttd -I OpenGFX -S OpenSFX -M OpenMSX -v sdl Error: Unable to load driver 'sdl'. The error was: No available video device ___ 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 completely on IPv6, without IPv4?
On Wed, Mar 28, 2012 at 12:09 PM, O. Hartmann wrote: > Hello. > > Is FreeBSD 10.0-CURRENT capable/ready to be run as a IPv6-only system? I > read some time ago that to be run still some portions of the IPv4-code > is needed to be compiled into the system/kernel. > http://wiki.freebsd.org/IPv6Only ;) ___ 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
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 ___ 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
On Wed, Jun 27, 2012 at 12:42 PM, 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 > - digital camera > - produce a crash dump (possible only after a certain point in boot sequence) > FreeBSD X220 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r237631 https://lh4.googleusercontent.com/-WRY8xDPlJk4/T-rQt79wm7I/D1c/Ix6X8dkyX9k/s868/IMG_4147.jpg In the VirtualBox this system boot no error. ___ 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
On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko wrote: > On Wed, Jun 27, 2012 at 12:42 PM, 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 >> - digital camera >> - produce a crash dump (possible only after a certain point in boot sequence) >> > > FreeBSD X220 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r237631 > > https://lh4.googleusercontent.com/-WRY8xDPlJk4/T-rQt79wm7I/D1c/Ix6X8dkyX9k/s868/IMG_4147.jpg > > In the VirtualBox this system boot no error. FreeBSD bsdx220 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r237635M: Wed Jun 27 13:51:55 MSK 2012 root@bsdx220:/usr/obj/usr/src/sys/GENERIC amd64 if use patch http://people.freebsd.org/~jkim/evxfgpe.diff boot no error ___ 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"
GPU_KMS still not working CURRENT X220
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 # 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 # kldstat Id Refs AddressSize Name 1 23 0x8020 15d3268 kernel 21 0x81a12000 a9f3 fuse.ko 31 0x81a1d000 690a4i915kms.ko 41 0x81a87000 1ba2 iicbb.ko 54 0x81a89000 1dd7 iicbus.ko 61 0x81a8b000 1cd5 iic.ko 71 0x81a8d000 32271drm2.ko # sysctl -a | grep hw.dri | less hw.dri.0.name: i915 0x9c hw.dri.0.vm: hw.dri.0.clients: hw.dri.0.vblank: hw.dri.0.info.i915_capabilities: gen: 6 hw.dri.0.info.i915_gem_objects: 8 objects, 4636672 bytes hw.dri.0.info.i915_gem_gtt:0xfe00084cca00: p 4KiB 0001 0001 0 0 snooped (LLC) (gtt offset: , size: 1000) (p mappable) hw.dri.0.info.i915_gem_active: Active: hw.dri.0.info.i915_gem_flushing: Flushing: hw.dri.0.info.i915_gem_inactive: Inactive: hw.dri.0.info.i915_gem_pinned: Pinned: hw.dri.0.info.i915_gem_deferred_free: Deferred free: hw.dri.0.info.i915_gem_pageflip: No flip due on pipe A (plane A) hw.dri.0.info.i915_gem_request: No requests hw.dri.0.info.i915_gem_seqno: Current sequence (render ring): 0 hw.dri.0.info.i915_gem_fence_regs: Reserved fences = 0 hw.dri.0.info.i915_gem_interrupt: North Display Interrupt enable: 8c248080 hw.dri.0.info.i915_gem_hws: 0x: 0x 0x 0x 0x hw.dri.0.info.i915_gem_hws_blt: 0x: 0x 0x 0x 0x hw.dri.0.info.i915_gem_hws_bsd: 0x: 0x 0x 0x 0x hw.dri.0.info.i915_ringbuffer_data: : hw.dri.0.info.i915_ringbuffer_info: Ring render ring: hw.dri.0.info.i915_bsd_ringbuffer_data: : hw.dri.0.info.i915_bsd_ringbuffer_info: Ring gen6 bsd ring: hw.dri.0.info.i915_blt_ringbuffer_data: : hw.dri.0.info.i915_blt_ringbuffer_info: Ring blt ring: hw.dri.0.info.i915_error_state: no error state collected hw.dri.0.info.i915_rstdby_delays: w/ctx: 0, w/o ctx: 0 hw.dri.0.info.i915_cur_delayinfo: GT_PERF_STATUS: 0x0d83 hw.dri.0.info.i915_delayfreq_table: P00VIDFREQ: 0x (VID: 0) hw.dri.0.info.i915_inttoext_table: INTTOEXT01: 0x hw.dri.0.info.i915_drpc_info: RC information accurate: yes hw.dri.0.info.i915_emon_status: Not supported hw.dri.0.info.i915_ring_freq_table: GPU freq (MHz) Effective CPU freq (MHz) hw.dri.0.info.i915_gfxec: GFXEC: 0 hw.dri.0.info.i915_fbc_status: FBC disabled: no outputs hw.dri.0.info.i915_sr_status: self-refresh: disabled hw.dri.0.info.i915_gem_framebuffer: fbcon size: 1366 x 768, depth 24, 32 bpp, obj 0xfe000846da00: p 4128KiB 0041 0 0 uncached (gtt offset: 00064000, size: 00408000) (p mappable) hw.dri.0.info.i915_gen6_forcewake_count_info: forcewake count = 0 hw.dri.0.info.i915_swizzle_info: bit6 swizzle for X-tiling = bit9/bit10 hw.dri.0.info.i915_ppgtt_info: GFX_MODE: 0x0a00 hw.dri.0.info.i915_gem_wired_pages: 1132 hw.dri.0.wedged: 0 hw.dri.0.max_freq: 1300 hw.dri.0.cache_sharing: 0 hw.dri.0.sync_exec: 0 hw.dri.0.fix_mi: 0 hw.dri.0.intr_pf: 0 hw.dri.0.busid: pci::00:02.0 hw.dri.0.modesetting: 1 hw.dri.debug: 2 hw.dri.notyet: 0 hw.dri.vblank_offdelay: 5000 hw.dri.timestamp_precision: 20 # less /var/log/messages Jun 28 17:32:17 bsdx220 kernel: drmn0: on vgapci0 Jun 28 17:32:17 bsdx220 kernel: info: [drm] MSI enabled 1 message(s) Jun 28 17:32:17 bsdx220 kernel: info: [drm] AGP at 0xe000 256MB Jun 28 17:32:17 bsdx220 kernel: iicbus0: on iicbb0 addr 0xff Jun 28 17:32:17 bsdx220 kernel: iic0: on iicbus0 Jun 28 17:32:17 bsdx220 kernel: iic1: on iicbus1 Jun 28 17:32:17 bsdx220 kernel: iicbus2: on iicbb1 addr 0xff Jun 28 17:32:17 bsdx220 kernel: iic2: on iicbus2 Jun 28 17:32:17 bsdx220 kernel: iic3: on iicbus3 Jun 28 17:32:17 bsdx220 kernel: iicbus4: on iicbb2 addr 0xff Jun 28 17:32:17 bsdx220 kernel: iic4: on iicbus4 Jun 28 17:32:17 bsdx220 kernel: iic5: on iicbus5 Jun 28 17:32:17 bsdx220 kernel: iicbus6: on iicbb3 addr 0xff Jun 28 17:32:17 bsdx220 kernel: iic6: on iicbus6 Jun 28 17:32:17 bsdx220 kernel: iic7: on iicbus7 Jun 28 17:32:17 bsdx220 kernel: iicbus8: on iicbb4 addr 0xff Jun 28 17:32:17 bsdx220 kernel: iic8: on iicbus8 Jun 28 17:32:17 bsdx220 kernel: iic9: on iicbus9 Jun 28 17:32:17
Re: GPU_KMS still not working CURRENT X220
On Thu, Jun 28, 2012 at 8:15 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 >> >> # 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. > > 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. > -- > R. Kevin Oberman, Network Engineer > E-mail: kob6...@gmail.com Thank you so much, it worked :) necessary as it is written in the wiki ___ 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: newcons comming
On Fri, Oct 25, 2013 at 4:18 PM, Aleksandr Rybalko wrote: > Hello fellow hackers! > > I finally reach the point when I can work with newcons instead of > syscons on my laptop. Yes, I know it still buggy and have a lot of > ... Yes, it's build and work # uname -a FreeBSD x220.local 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r257111M: Fri Oct 25 19:27:50 MSK 2013 andrey@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 :) In the single user ugly Can not read termcap database: Using dumb terminal settings In the multy user mode: Switch Xorg to consol and back is correct. spam log % tail /var/log/messages Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0xc0086457, nr=0x57, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x20006458, nr=0x58, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 last message repeated 5 times Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x800c645f, nr=0x5f, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x8020645d, nr=0x5d, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x80406469, nr=0x69, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:i915_gem_execbuffer2] buffers_ptr 80340a400 buffer_count 2 len 0058 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x800c645f, nr=0x5f, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0xc0086457, nr=0x57, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x20006458, nr=0x58, dev 0xf80006682800, auth=1 In the console login jumps up, but it works correctly. If ScrlLk console blink. ___ 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"
[xhci] USB 3.0 not working, bug or feature usb/179342?
# uname -a FreeBSD desktop.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r263711: Tue Mar 25 15:49:11 MSK 2014 root@desktop.local:/usr/obj/usr/src/sys/MY_DES amd64 usbconfig list | grep "5.0Gbps" ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) and USB3 flash drive ugen2.4: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (498mA) full list http://pastie.org/8963116 dmesg debug mode xhci0: Intel Lynx Point USB 3.0 controller mem 0xf042-0xf042 irq 16 at device 20.0 on pci0 xhci0: attempting to allocate 1 MSI vectors (8 supported) msi: routing MSI IRQ 265 to local APIC 0 vector 60 xhci0: using IRQ 265 for MSI xhci0: MSI enabled xhci0: 32 byte context size. xhci0: Port routing mask set to 0x usbus0 on xhci0 xhci0: usbpf: Attached ... uhub0: 21 ports with 21 removable, self powered Root mount waiting for: usbus0 xhci0: Port routing mask set to 0x usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) ugen0.2: Unknown at usbus0 (disconnected) uhub_reattach_port: could not allocate new device ___ 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: [xhci] USB 3.0 not working, bug or feature usb/179342?
On Sat, Mar 29, 2014 at 4:37 AM, Andrey Fesenko wrote: > and USB3 flash drive > ugen2.4: at usbus2, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON (498mA) > full list http://pastie.org/8963116 I apologize for panic after additional searches proper BIOS configuration able to identify flash drive as USB3 ugen0.2: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (224mA) while writing speed test file with ramdisk is almost unchanged :( # dd if=/dev/random of=/mnt/ramdisck/test.file bs=10m count=198 2076180480 bytes transferred in 28.443097 secs (72994178 bytes/sec) # dd if=/mnt/ramdisck/test.file of=/mnt/usb3/test.file bs=10m count=198 2076180480 bytes transferred in 222.810014 secs (9318165 bytes/sec) # dd if=/mnt/ramdisck/test.file of=/mnt/usb2/test.file bs=10m count=198 2076180480 bytes transferred in 248.585099 secs (8351991 bytes/sec) ___ 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: [xhci] USB 3.0 not working, bug or feature usb/179342?
On Sat, Mar 29, 2014 at 9:46 PM, Adrian Chadd wrote: > Try read tests? > > Adrian > > On Mar 29, 2014 10:20 AM, "Andrey Fesenko" wrote: >> >> On Sat, Mar 29, 2014 at 4:37 AM, Andrey Fesenko >> wrote: >> > and USB3 flash drive >> > ugen2.4: at usbus2, cfg=0 md=HOST >> > spd=HIGH (480Mbps) pwr=ON (498mA) >> > full list http://pastie.org/8963116 >> >> I apologize for panic after additional searches proper BIOS >> configuration able to identify flash drive as USB3 >> >> ugen0.2: at usbus0, cfg=0 md=HOST >> spd=SUPER (5.0Gbps) pwr=ON (224mA) >> >> while writing speed test file with ramdisk is almost unchanged :( >> >> # dd if=/dev/random of=/mnt/ramdisck/test.file bs=10m count=198 >> 2076180480 bytes transferred in 28.443097 secs (72994178 bytes/sec) >> # dd if=/mnt/ramdisck/test.file of=/mnt/usb3/test.file bs=10m >> count=198 >> 2076180480 bytes transferred in 222.810014 secs (9318165 bytes/sec) >> # dd if=/mnt/ramdisck/test.file of=/mnt/usb2/test.file bs=10m >> count=198 >> 2076180480 bytes transferred in 248.585099 secs (8351991 bytes/sec) # dd if=/mnt/usb2/test.file of=/mnt/ramdisck/test.file bs=10m count=198 2076180480 bytes transferred in 1.354000 secs (1533368050 bytes/sec) # dd if=/mnt/usb3/test.file of=/mnt/ramdisck/test.file bs=10m count=198 2076180480 bytes transferred in 1.498134 secs (1385844184 bytes/sec) probably need to try something different as tested. flash spec http://www.kingston.com/datasheets/dt100g3_us.pdf only 10MB/ sec.* write :) Strangely, the flash drive is not always defined, after mount USB2 mode it took two times reboot :( on the notebook USB2-only USB (UFS) <-> SSD (ZFS) # dd if=/mnt/usb3/test.file of=/tank/test.file bs=10m count=198 2076180480 bytes transferred in 57.370256 secs (36189144 bytes/sec) # dd if=/tank/test.file of=/mnt/usb3/test.file bs=10m count=198 2076180480 bytes transferred in 245.685052 secs (8450577 bytes/sec) ___ 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"
SATA2 mode on SATA3 SSD (marvell controller) after boot
Hello, ada2: ATA-8 SATA 3.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) need tuning? or change SSD? motherboard gigabyte z87mx-d3h all ports SATA-3, port change does not change the situation hdd SATA-3 recognized correctly ada3: ATA-9 SATA 3.x device ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) another ssd ada2: ATA-8 SATA 3.x device ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) if disconnect ssd pr 17 14:07:08 desktop kernel: ahcich3: DISCONNECT requested Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset... Apr 17 14:07:08 desktop kernel: ahcich3: SATA connect timeout time=1us status= Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset: device not found Apr 17 14:07:08 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 lun 0 Apr 17 14:07:08 desktop kernel: pass3: s/n P0242921 detached Apr 17 14:07:08 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 Apr 17 14:07:08 desktop kernel: ada3: s/n P0242921 detached Apr 17 14:07:08 desktop kernel: (pass3:ahcich3:0:0:0): Periph destroyed Apr 17 14:07:08 desktop kernel: (ada3:ahcich3:0:0:0): Periph destroyed Apr 17 14:07:18 desktop kernel: ahcich3: CONNECT requested Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset... Apr 17 14:07:18 desktop kernel: ahcich3: SATA connect time=8000us status=0133 Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device found Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device ready after 0ms Apr 17 14:07:18 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 Apr 17 14:07:18 desktop kernel: GEOM: new disk ada3 Apr 17 14:07:18 desktop kernel: ada3: ATA-8 SATA 3.x device Apr 17 14:07:18 desktop kernel: ada3: Serial Number P0242921 Apr 17 14:07:18 desktop kernel: ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) Apr 17 14:07:18 desktop kernel: ada3: Command Queueing enabled Apr 17 14:07:18 desktop kernel: ada3: 122104MB (250069680 512 byte sectors: 16H 63S/T 16383C) Apr 17 14:07:18 desktop kernel: ada3: Previously was known as ad10 Apr 17 14:07:18 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 lun 0 Apr 17 14:07:18 desktop kernel: pass3: ATA-8 SATA 3.x device Apr 17 14:07:18 desktop kernel: pass3: Serial Number P0242921 Apr 17 14:07:18 desktop kernel: pass3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) Apr 17 14:07:18 desktop kernel: pass3: Command Queueing enabled # uname -a FreeBSD desktop.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r263932: Sun Mar 30 15:43:01 MSK 2014 root@desktop.local:/usr/obj/usr/src/sys/MY_DES amd64 ___ 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: SATA2 mode on SATA3 SSD (marvell controller) after boot
On Thu, Apr 17, 2014 at 2:10 PM, Andrey Fesenko wrote: > if disconnect ssd > pr 17 14:07:08 desktop kernel: ahcich3: DISCONNECT requested > Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset... > Apr 17 14:07:08 desktop kernel: ahcich3: SATA connect timeout > time=1us status= > Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset: device not found > Apr 17 14:07:08 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 lun 0 > Apr 17 14:07:08 desktop kernel: pass3: s/n > P0242921 detached > Apr 17 14:07:08 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 > Apr 17 14:07:08 desktop kernel: ada3: s/n > P0242921 detached > Apr 17 14:07:08 desktop kernel: (pass3:ahcich3:0:0:0): Periph destroyed > Apr 17 14:07:08 desktop kernel: (ada3:ahcich3:0:0:0): Periph destroyed > Apr 17 14:07:18 desktop kernel: ahcich3: CONNECT requested > Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset... > Apr 17 14:07:18 desktop kernel: ahcich3: SATA connect time=8000us > status=0133 > Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device found > Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device ready after 0ms > Apr 17 14:07:18 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 > Apr 17 14:07:18 desktop kernel: GEOM: new disk ada3 > Apr 17 14:07:18 desktop kernel: ada3: ATA-8 > SATA 3.x device > Apr 17 14:07:18 desktop kernel: ada3: Serial Number P0242921 > Apr 17 14:07:18 desktop kernel: ada3: 600.000MB/s transfers (SATA 3.x, > UDMA6, PIO 8192bytes) > Apr 17 14:07:18 desktop kernel: ada3: Command Queueing enabled > Apr 17 14:07:18 desktop kernel: ada3: 122104MB (250069680 512 byte > sectors: 16H 63S/T 16383C) > Apr 17 14:07:18 desktop kernel: ada3: Previously was known as ad10 > Apr 17 14:07:18 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 lun 0 > Apr 17 14:07:18 desktop kernel: pass3: ATA-8 > SATA 3.x device > Apr 17 14:07:18 desktop kernel: pass3: Serial Number P0242921 > Apr 17 14:07:18 desktop kernel: pass3: 600.000MB/s transfers (SATA > 3.x, UDMA6, PIO 8192bytes) > Apr 17 14:07:18 desktop kernel: pass3: Command Queueing enabled > > > # uname -a > FreeBSD desktop.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r263932: > Sun Mar 30 15:43:01 MSK 2014 > root@desktop.local:/usr/obj/usr/src/sys/MY_DES amd64 Is it possible camcontrol repeat behavior as physical disable/enable or enable SATA 3.x mode? camcontrol negotiate only report not set new mode. # camcontrol negotiate pass2 Current parameters: (pass2:ahcich3:0:0:0): SATA revision: 2.x (pass2:ahcich3:0:0:0): ATA mode: UDMA6 (pass2:ahcich3:0:0:0): ATAPI packet length: 0 (pass2:ahcich3:0:0:0): PIO transaction length: 8192 (pass2:ahcich3:0:0:0): PMP presence: 0 (pass2:ahcich3:0:0:0): Number of tags: 32 (pass2:ahcich3:0:0:0): SATA capabilities: 0030 (pass2:ahcich3:0:0:0): tagged queueing: enabled ___ 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: SATA2 mode on SATA3 SSD (marvell controller) after boot
On Sun, Apr 20, 2014 at 11:44 PM, Alexander Motin wrote: > On 20.04.2014 22:31, Andrey Fesenko wrote: >> >> On Thu, Apr 17, 2014 at 2:10 PM, Andrey Fesenko >> wrote: >>> >>> if disconnect ssd >>> pr 17 14:07:08 desktop kernel: ahcich3: DISCONNECT requested >>> Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset... >>> Apr 17 14:07:08 desktop kernel: ahcich3: SATA connect timeout >>> time=1us status= >>> Apr 17 14:07:08 desktop kernel: ahcich3: AHCI reset: device not found >>> Apr 17 14:07:08 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 >>> lun 0 >>> Apr 17 14:07:08 desktop kernel: pass3: s/n >>> P0242921 detached >>> Apr 17 14:07:08 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun >>> 0 >>> Apr 17 14:07:08 desktop kernel: ada3: s/n >>> P0242921 detached >>> Apr 17 14:07:08 desktop kernel: (pass3:ahcich3:0:0:0): Periph destroyed >>> Apr 17 14:07:08 desktop kernel: (ada3:ahcich3:0:0:0): Periph destroyed >>> Apr 17 14:07:18 desktop kernel: ahcich3: CONNECT requested >>> Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset... >>> Apr 17 14:07:18 desktop kernel: ahcich3: SATA connect time=8000us >>> status=0133 >>> Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device found >>> Apr 17 14:07:18 desktop kernel: ahcich3: AHCI reset: device ready after >>> 0ms >>> Apr 17 14:07:18 desktop kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun >>> 0 >>> Apr 17 14:07:18 desktop kernel: GEOM: new disk ada3 >>> Apr 17 14:07:18 desktop kernel: ada3: ATA-8 >>> SATA 3.x device >>> Apr 17 14:07:18 desktop kernel: ada3: Serial Number P0242921 >>> Apr 17 14:07:18 desktop kernel: ada3: 600.000MB/s transfers (SATA 3.x, >>> UDMA6, PIO 8192bytes) >>> Apr 17 14:07:18 desktop kernel: ada3: Command Queueing enabled >>> Apr 17 14:07:18 desktop kernel: ada3: 122104MB (250069680 512 byte >>> sectors: 16H 63S/T 16383C) >>> Apr 17 14:07:18 desktop kernel: ada3: Previously was known as ad10 >>> Apr 17 14:07:18 desktop kernel: pass3 at ahcich3 bus 0 scbus3 target 0 >>> lun 0 >>> Apr 17 14:07:18 desktop kernel: pass3: ATA-8 >>> SATA 3.x device >>> Apr 17 14:07:18 desktop kernel: pass3: Serial Number P0242921 >>> Apr 17 14:07:18 desktop kernel: pass3: 600.000MB/s transfers (SATA >>> 3.x, UDMA6, PIO 8192bytes) >>> Apr 17 14:07:18 desktop kernel: pass3: Command Queueing enabled >>> >>> >>> # uname -a >>> FreeBSD desktop.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r263932: >>> Sun Mar 30 15:43:01 MSK 2014 >>> root@desktop.local:/usr/obj/usr/src/sys/MY_DES amd64 >> >> >> Is it possible camcontrol repeat behavior as physical disable/enable >> or enable SATA 3.x mode? >> camcontrol negotiate only report not set new mode. >> >> # camcontrol negotiate pass2 >> Current parameters: >> (pass2:ahcich3:0:0:0): SATA revision: 2.x >> (pass2:ahcich3:0:0:0): ATA mode: UDMA6 >> (pass2:ahcich3:0:0:0): ATAPI packet length: 0 >> (pass2:ahcich3:0:0:0): PIO transaction length: 8192 >> (pass2:ahcich3:0:0:0): PMP presence: 0 >> (pass2:ahcich3:0:0:0): Number of tags: 32 >> (pass2:ahcich3:0:0:0): SATA capabilities: 0030 >> (pass2:ahcich3:0:0:0): tagged queueing: enabled > > > camcontrol negotiate can limit maximal SATA mode, but not specify it > exactly. Unless you limited it previously, there should be no limitation set > and HBA should negotiate it freely. The limitations could be read/set with > `camcontrol negotiate pass2 -U`, and affect operation after following > `camcontrol reset ...`. > > -- > Alexander Motin system this installer usb image without limitation # uname -a FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r264634: Fri Apr 18 08:25:11 MSK 2014 andrey@desktop.local:/usr/obj/usr/src/sys/GENERIC amd64 root@:~ # camcontrol negotiate pass2 -U User parameters: (pass2:ahcich3:0:0:0): SATA revision: 0.x (pass2:ahcich3:0:0:0): ATA mode: NONE (pass2:ahcich3:0:0:0): ATAPI packet length: 0 (pass2:ahcich3:0:0:0): PIO transaction length: 8192 (pass2:ahcich3:0:0:0): PMP presence: 0 (pass2:ahcich3:0:0:0): Number of tags: 32 (pass2:ahcich3:0:0:0): SATA capabilities: 0030 (pass2:ahcich3:0:0:0): tagged queueing: enabled root@:~ # camcontrol reset pass2 Reset of bus 0 was successful root@:~ # camcontrol negotiate pass2 Current parameters: (pass2:ahcich3:0:0:0): SATA revision: 2.x (pass2:ahcich3:0:0:0): ATA mode: UDMA6 (pass2:ahcich3:0:0:0): ATAPI packet length: 0 (pass2:ahcich3:0:0:0): PIO transaction length: 8192 (pass2:ahcich3:0:0:0): PMP presence: 0 (pass2:ahcich3:0:0:0): Number of tags: 32 (pass2:ahcich3:0:0:0): SATA capabilities: 0030 (pass2:ahcich3:0:0:0): tagged queueing: enabled ___ 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: SATA2 mode on SATA3 SSD (marvell controller) after boot
On Mon, Apr 21, 2014 at 12:05 AM, Alexander Motin wrote:
>
> Then it is a question to hardware or firmware not an OS driver.
>
> --
> Alexander Motin
Thanks for the tips
try to change to another, it seems some problems with the firmware
In the linux (grml)
Sata-3 hdd have section
Standards:
Supported: 9 8 7 6 5
Likely used: 9
# hdparm -I /dev/sdc
/dev/sdc:
ATA device, with non-removable media
Model Number: PLEXTOR PX-128M5S
Serial Number: P0242921
Firmware Revision: 1.05
Transport: Serial, ATA8-AST, SATA II Extensions, SATA
Rev 2.6, SATA Rev 3.0
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 4a
Supported: 8 7 6 5 & some of 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 250069680
LBA48 user addressable sectors: 250069680
Logical Sector size: 512 bytes
Physical Sector size: 512 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 122104 MBytes
device size with M = 1000*1000: 128035 MBytes (128 GB)
cache/buffer size = unknown
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
*SMART feature set
Security Mode feature set
*Power Management feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*DOWNLOAD_MICROCODE
SET_MAX security extension
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*64-bit World wide name
*Segmented DOWNLOAD_MICROCODE
*Gen1 signaling speed (1.5Gb/s)
*Gen2 signaling speed (3.0Gb/s)
*Gen3 signaling speed (6.0Gb/s)
*Native Command Queueing (NCQ)
*Host-initiated interface power management
*Phy event counters
*DMA Setup Auto-Activate optimization
Device-initiated interface power management
*Software settings preservation
unknown 78[8]
*SMART Command Transport (SCT) feature set
*SCT Write Same (AC2)
*SCT Error Recovery Control (AC3)
*SCT Features Control (AC4)
*SCT Data Tables (AC5)
*Data Set Management TRIM supported (limit 8 blocks)
Security:
supported
not enabled
not locked
frozen
not expired: security count
supported: enhanced erase
6min for SECURITY ERASE UNIT. 6min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 500230310017df1b
NAA : 5
IEEE OUI: 002303
Unique ID : 10017df1b
Checksum: correct
after reconnect SSD this information not change, but syslog
2014-04-21T00:23:21.223409+00:00 grml kernel: [3.482230] ata4:
SATA link up 3.0 Gbps (SStatus 123 SControl 300)
2014-04-21T00:23:21.223410+00:00 grml kernel: [3.482375] Switched
to clocksource tsc
2014-04-21T00:23:21.223410+00:00 grml kernel: [3.484803] ata4.00:
ATA-8: PLEXTOR PX-128M5S, 1.05, max UDMA/133
2014-04-21T00:23:21.223413+00:00 grml kernel: [3.484804] ata4.00:
250069680 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
...
2014-04-21T00:43:52.004962+00:00 grml kernel: [ 1199.327857] ata4:
SError: { DevExch }
2014-04-21T00:43:52.004962+00:00 grml kernel: [ 1199.327860] ata4:
hard resetting link
2014-04-21T00:43:52.728949+00:00 grml kernel: [ 1200.048622] ata4:
SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2014-04-21T00:43:52.728953+00:00 grml kernel: [ 1200.051217] ata4.00:
ATA-8: PLEXTOR PX-128M5S, 1.05, max UDMA/133
2014-04-21T00:43:52.728954+00:00 grml kernel: [ 1200.051219] ata4.00:
250069680 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
___
freebsd-curr
ZFS bug or feature
After detach ada0 and attach him (reboot between that) boot only one disk Apr 17 13:33:52 x220 kernel: ada0 at ahcich2 bus 0 scbus0 target 0 lun 0 Apr 17 13:33:52 x220 kernel: ada0: ATA-8 SATA 2.x device Apr 17 13:33:52 x220 kernel: ada0: Serial Number OCZ-J8928HU1G10KR9XM Apr 17 13:33:52 x220 kernel: ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 17 13:33:52 x220 kernel: ada0: Command Queueing enabled Apr 17 13:33:52 x220 kernel: ada0: 114473MB (234441648 512 byte sectors: 1H 63S/T 65535C) Apr 17 13:33:52 x220 kernel: ada0: Previously was known as ad4 After attach ada0 im see this # camcontrol devlist at scbus0 target 0 lun 0 (ada0,pass0) at scbus1 target 0 lun 0 (ada1,pass1) # zpool status pool: x220pool state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 42.4M in 0h0m with 0 errors on Thu Apr 17 13:48:42 2014 config: NAME STATE READ WRITE CKSUM x220pool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 diskid/DISK-OCZ-J8928HU1G10KR9XMs1a ONLINE 0 0 0 ada0s1a ONLINE 0 0 0 errors: No known data errors # gpart show => 63 468862065 ada0 MBR (224G) 63 234441585 1 freebsd (112G) 234441648 234420480 2 freebsd (112G) =>0 234441585 ada0s1 BSD (112G) 0 234441585 1 freebsd-zfs (112G) => 63 234441585 diskid/DISK-OCZ-J8928HU1G10KR9XM MBR (112G) 63 234441585 1 freebsd [active] (112G) =>0 234441585 diskid/DISK-OCZ-J8928HU1G10KR9XMs1 BSD (112G) 0 234441585 1 freebsd-zfs (112G) Apr 17 13:48:43 x220 kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 Apr 17 13:48:43 x220 kernel: ada0: ATA-8 SATA 3.x device Apr 17 13:48:43 x220 kernel: ada0: Serial Number 124079271802000A Apr 17 13:48:43 x220 kernel: ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) Apr 17 13:48:43 x220 kernel: ada0: Command Queueing enabled Apr 17 13:48:43 x220 kernel: ada0: 228936MB (468862128 512 byte sectors: 16H 63S/T 16383C) Apr 17 13:48:43 x220 kernel: ada0: Previously was known as ad4 Apr 17 13:48:43 x220 kernel: ada1 at ahcich2 bus 0 scbus1 target 0 lun 0 Apr 17 13:48:43 x220 kernel: ada1: ATA-8 SATA 2.x device Apr 17 13:48:43 x220 kernel: ada1: Serial Number OCZ-J8928HU1G10KR9XM Apr 17 13:48:43 x220 kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 17 13:48:43 x220 kernel: ada1: Command Queueing enabled Apr 17 13:48:43 x220 kernel: ada1: 114473MB (234441648 512 byte sectors: 1H 63S/T 65535C) Apr 17 13:48:43 x220 kernel: ada1: Previously was known as ad6 # zpool history -il | tail -6 2014-04-17.13:33:51 [txg:8004153] open pool version 5000; software version 5000/5; uts 11.0-CURRENT 115 amd64 [on x220.local] 2014-04-17.13:48:36 [txg:8004321] open pool version 5000; software version 5000/5; uts 11.0-CURRENT 115 amd64 [on x220.local] 2014-04-17.13:48:41 [txg:8004324] scan setup func=2 mintxg=8004151 maxtxg=8004320 [on x220.local] 2014-04-17.13:48:42 [txg:8004325] scan done complete=1 [on x220.local] 2014-04-17.13:53:53 zpool clear x220pool [user 0 (root) on x220.local] ___ 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: ZFS bug or feature
On Tue, Apr 22, 2014 at 8:23 PM, Tom Evans wrote: > > I'm confused, what is the bug or feature? Has it added the disk with > the wrong label? You can correct that with an zpool export x220pool / > zpool import -d /dev/diskid x220pool > gpart see only one disk ada0 (OCZ), if believe camcontrol ada0 (Corsair) - OCZ (ada1) why zpool status see two disk and not error x220pool - root file system I'm would not like to break it ___ 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: ZFS bug or feature
On Tue, Apr 22, 2014 at 9:31 PM, Thomas Hoffmann wrote: > In /boot/loader.conf: > kern.geom.label.disk_ident.enable=0 > > will disable the use of disk ids. > > -Tom Yes it helped :) I apologize for a small panic, then looked more closely again, and so everything was more or less normal ___ 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: Booting from ZFS root on MBR layout fails on ThinkPad X61s
On Wed, Apr 16, 2014 at 2:01 AM, Sevan / Venture37 wrote: > Hi, > I decided to wipe away the disk in my X61s & start afresh with a new > install of FreeBSD-Current at the same time switching to root on ZFS > (previously /boot was on UFS). > I've been unsuccessful in being able get the system to boot, after > trying various combinations of > https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition I switched back to > using the install menu option & just switching from GPT to MBR > (everything else as default). > Once install completes & the system reboots, the system hangs at a prompt. > > I was pointed to a post regarding modifying partition ID's by Allan > Jude as there seems to have been an issue with ThinkPads & FreeBSD in > the past. This also didn't work & caused the system to reset. > > What should be my next step for trying to debug this issue? > > > Sevan / Venture37 It seems there are some problems with compatibility :( I'm have X220 my config # camcontrol devlist at scbus0 target 0 lun 0 (ada0,pass0) at scbus1 target 0 lun 0 (ada1,pass1) % gpart show => 63 468862065 ada0 MBR (224G) 63 234441585 1 freebsd (112G) 234441648 234420480 2 freebsd (112G) =>0 234441585 ada0s1 BSD (112G) 0 234441585 1 freebsd-zfs (112G) => 63 234441585 ada1 MBR (112G) 63 234441585 1 freebsd [active] (112G) =>0 234441585 ada1s1 BSD (112G) 0 234441585 1 freebsd-zfs (112G) system ZFS mirror x220pool (ada0s1a ada1s1a) boot only ada1 (msata) disk. Boot with GPT not work, black screen and reboot without any menu. When I used HDD as ada1 boot with him work MBR method Might be worth trying to boot from UEFI but it's still an experimental method https://wiki.freebsd.org/UEFI ___ 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: mdoc warning: .Fx: Unknown FreeBSD version `10' (#181)
On Sat, Mar 16, 2013 at 8:59 PM, deeptech71 wrote: > When running ``man script'' (world r248258), I get: > > mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) > > (and the whole man page, which quickly hides the warning). reproduce # whereis man man: /usr/bin/man /usr/share/man/man1/man.1.gz /usr/src/usr.bin/man # uname -a FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248378: Sun Mar 17 00:11:12 MSK 2013 andrey@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 % man script | head -1 mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) SCRIPT(1) FreeBSD General Commands Manual SCRIPT(1) not correct macros .Fx may be fix % diff script.1 script.1.orig 181c181 < .Fx 10.0 . --- > .Fx 10 . mandoc without this error ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel build fails on ARM: Cannot fork: Cannot allocate memory
On Wed, Jun 19, 2013 at 10:15 PM, Zbyszek Bodek wrote: > Hello, > > I've been trying to compile the kernel on my ARMv7 platform using the > sources from the current FreeBSD HEAD. > > make buildkernel <.> -j5 > > 1/2 builds fails in the way described below: > -- > ing-include-dirs -fdiagnostics-show-option -nostdinc -I. > -I/root/src/freebsd-arm-superpages/sys > -I/root/src/freebsd-arm-superpages/sys/contrib/altq > -I/root/src/freebsd-arm-superpages/sys/contrib/libfdt -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -mno-thumb-interwork -ffreestanding -Werror > /root/src/freebsd-arm-superpages/sys/ufs/ffs/ffs_snapshot.c > Cannot fork: Cannot allocate memory > *** [ffs_snapshot.o] Error code 2 > 1 error > *** [buildkernel] Error code 2 > 1 error > *** [buildkernel] Error code 2 > 1 error > 5487.888u 481.569s 7:35.65 1310.0% 1443+167k 1741+5388io 221pf+0w > -- > -j5 tricky :) I think it is necessary to build one may be in two streams, as well as make the swap ___ 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"
RaspberryPi (ARMv6) after update EABI not build perl
Hi, anyone succeeded build perl for eabi? my rpi make results in an error equally for all perl version #define PERL_FPU_INIT (void)fpsetmask(0) ^ 1 warning generated. LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 cc -pthread -Wl,-E -fstack-protector -L/usr/local/lib -o miniperlgv.o toke.o perly.o pad.o regcomp.o dump.o util.o mg.o reentr.o mro.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o miniperlmain.o opmini.o perlmini.o -lm -lcrypt -lutil LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -w -Ilib -MExporter -e '' || /usr/bin/make minitest longjmp botch. Abort trap (core dumped) LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl -Ilib make_patchnum.pl Updating 'git_version.h' and 'lib/Config_git.pl' longjmp botch. *** Signal 6 Stop. make: stopped in /usr/ports/lang/perl5.14/work/perl-5.14.4 *** Error code 1 (ignored) You may see some irrelevant test failures if you have been unable to build lib/Config.pm, or the Unicode data files. cd t && (rm -f perl; /bin/ln -s ../miniperl perl) && LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./perl TEST base/*.t comp/*.t cmd/*.t run/*.t io/*.t re/*.t op/*.t uni/*.t >> make failed for lang/perl5.14 ===>>> Aborting update ===>>> Killing background jobs Terminated ===>>> You can restart from the point of failure with this command line: portmaster lang/perl5.14 ===>>> Exiting ___ 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: RaspberryPi (ARMv6) after update EABI not build perl
Sory, # uname -a FreeBSD raspberry-pi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253414M: Wed Jul 17 16:12:39 MSK 2013 andrey@my_book.local:/home/andrey/obj/arm.armv6/usr/src/sys/RPI-B-IPv6 arm system compile clang On Thu, Jul 18, 2013 at 10:15 PM, Andrey Fesenko wrote: > Hi, anyone succeeded build perl for eabi? my rpi make results in an > error equally for all perl version > > #define PERL_FPU_INIT (void)fpsetmask(0) > ^ > 1 warning generated. > LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 cc -pthread > -Wl,-E -fstack-protector -L/usr/local/lib -o miniperlgv.o toke.o > perly.o pad.o regcomp.o dump.o util.o mg.o reentr.o mro.o keywords.o > hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o > doio.o regexec.o utf8.o taint.o deb.o universal.o globals.o perlio.o > perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_sort.o > miniperlmain.o opmini.o perlmini.o -lm -lcrypt -lutil > LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl > -w -Ilib -MExporter -e '' || /usr/bin/make minitest > longjmp botch. > Abort trap (core dumped) > LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl > -Ilib make_patchnum.pl > Updating 'git_version.h' and 'lib/Config_git.pl' > longjmp botch. > *** Signal 6 > > Stop. > make: stopped in /usr/ports/lang/perl5.14/work/perl-5.14.4 > *** Error code 1 (ignored) > > You may see some irrelevant test failures if you have been unable > to build lib/Config.pm, or the Unicode data files. > > cd t && (rm -f perl; /bin/ln -s ../miniperl perl) && > LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./perl TEST > base/*.t comp/*.t cmd/*.t run/*.t io/*.t re/*.t op/*.t uni/*.t > t/base/cond.longjmp botch. > FAILED--no leader found > Failed a basic test (base/cond.t) -- cannot continue. > longjmp botch. > *** Signal 6 (ignored) > /bin/ln -s perldelta.pod pod/perl5144delta.pod > LD_LIBRARY_PATH=/usr/ports/lang/perl5.14/work/perl-5.14.4 ./miniperl > -Ilib autodoc.pl > longjmp botch. > *** Signal 6 > > Stop. > make: stopped in /usr/ports/lang/perl5.14/work/perl-5.14.4 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/lang/perl5.14 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/lang/perl5.14 > > ===>>> make failed for lang/perl5.14 > ===>>> Aborting update > > ===>>> Killing background jobs > Terminated > > ===>>> You can restart from the point of failure with this command line: >portmaster lang/perl5.14 > > ===>>> Exiting ___ 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"
Not work ATH (AR9285) after update
Hello, i'm horrible news, after update my notebook not nave wi-fi :( full update system, build and install world and kernel. # uname -a FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253562: Tue Jul 23 14:44:07 MSK 2013 root@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 # grep ATH /usr/src/sys/amd64/conf/W_BOOK options ATH_ENABLE_11N options ATH_DEBUG options ATH_DIAGAPI ath0@pci0:3:0:0:class=0x028000 card=0x1a891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9285 Wireless Network Adapter (PCI-Express)' class = network # ifconfig ath0: flags=8843 metric 0 mtu 2290 ether 00:25:d3:7b:94:87 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8c43 metric 0 mtu 1500 ether 00:25:d3:7b:94:87 inet6 fe80::225:d3ff:fe7b:9487%wlan0 prefixlen 64 scopeid 0x4 nd6 options=23 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 8 (2447 MHz 11g) regdomain 33411 country RU indoor ecm authmode WPA1+WPA2/802.11i privacy MIXED deftxkey UNDEF txpower 20 bmiss 7 scanvalid 60 protmode CTS wme burst roaming MANUAL # ifconfig wlan0 list scan SSID/MESH IDBSSID CHAN RATE S:N INT CAPS APT-SPB2b8:a3:86:4a:75:6a6 54M -92:-96 100 EP HTCAP WPA RSN WME WPS THD1 74:ea:3a:d1:37:46 10 54M -85:-96 100 EP RSN HTCAP WME Balt1 00:90:4c:c1:00:001 54M -90:-96 100 EP RSN TP-LINK_904D2A 64:70:02:90:4d:2a 11 54M -94:-96 100 EPS RSN HTCAP WME ATH WPS /var/log/messages ... Jul 23 15:34:24 x220 wpa_supplicant[669]: wlan0: CTRL-EVENT-TERMINATING Jul 23 15:34:24 x220 kernel: wlan0: Ethernet address: 00:25:d3:7b:94:87 Jul 23 15:34:24 x220 devd: Executing '/etc/pccard_ether wlan0 start' Jul 23 15:34:24 x220 wpa_supplicant[2563]: Successfully initialized wpa_supplicant Jul 23 15:34:24 x220 wpa_supplicant[2571]: Successfully initialized wpa_supplicant Jul 23 15:34:24 x220 wpa_supplicant[2571]: ctrl_iface exists and seems to be in use - cannot override it Jul 23 15:34:24 x220 wpa_supplicant[2571]: Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore Jul 23 15:34:24 x220 wpa_supplicant[2571]: Failed to initialize control interface '/var/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again. Jul 23 15:34:24 x220 wpa_supplicant[2571]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Jul 23 15:34:24 x220 wpa_supplicant[2571]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Jul 23 15:34:24 x220 root: /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Jul 23 15:34:24 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Jul 23 15:34:24 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan Jul 23 15:34:25 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Jul 23 15:34:25 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan Jul 23 15:34:26 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Jul 23 15:34:26 x220 kernel: ath0: ath_reset_grablock: didn't finish after 10 iterations Jul 23 15:34:26 x220 kernel: ath0: ath_reset_grablock: warning, recursive reset path! Jul 23 15:34:26 x220 kernel: ath0: ath_reset: concurrent reset! Danger! Jul 23 15:34:26 x220 kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing Jul 23 15:34:26 x220 kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing Jul 23 15:34:26 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan Jul 23 15:34:27 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Jul 23 15:34:27 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan Jul 23 15:34:29 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Jul 23 15:34:29 x220 kernel: ath0: ath_reset_grablock: didn't finish after 10 iterations Jul 23 15:34:29 x220 kernel: ath0: ath_reset_grablock: warning, recursive reset path! ___ 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: Not work ATH (AR9285) after update
On Tue, Jul 23, 2013 at 5:13 PM, Adrian Chadd wrote: > .. are two copies of wpa_supplicant running? > > > > -adrian > > On 23 July 2013 06:09, Andrey Fesenko wrote: >> Hello, >> i'm horrible news, after update my notebook not nave wi-fi :( >> full update system, build and install world and kernel. >> >> # uname -a >> FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253562: Tue >> Jul 23 14:44:07 MSK 2013 >> root@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 >> >> # grep ATH /usr/src/sys/amd64/conf/W_BOOK >> options ATH_ENABLE_11N >> options ATH_DEBUG >> options ATH_DIAGAPI >> >> ath0@pci0:3:0:0:class=0x028000 card=0x1a891a3b chip=0x002b168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR9285 Wireless Network Adapter (PCI-Express)' >> class = network >> >> # ifconfig >> ath0: flags=8843 metric 0 mtu 2290 >> ether 00:25:d3:7b:94:87 >> nd6 options=21 >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >> status: associated >> wlan0: flags=8c43 >> metric 0 mtu 1500 >> ether 00:25:d3:7b:94:87 >> inet6 fe80::225:d3ff:fe7b:9487%wlan0 prefixlen 64 scopeid 0x4 >> nd6 options=23 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 8 (2447 MHz 11g) >> regdomain 33411 country RU indoor ecm authmode WPA1+WPA2/802.11i >> privacy MIXED deftxkey UNDEF txpower 20 bmiss 7 scanvalid 60 >> protmode CTS wme burst roaming MANUAL >> # ifconfig wlan0 list scan >> SSID/MESH IDBSSID CHAN RATE S:N INT CAPS >> APT-SPB2b8:a3:86:4a:75:6a6 54M -92:-96 100 EP HTCAP >> WPA RSN WME WPS >> THD1 74:ea:3a:d1:37:46 10 54M -85:-96 100 EP RSN HTCAP WME >> Balt1 00:90:4c:c1:00:001 54M -90:-96 100 EP RSN >> TP-LINK_904D2A 64:70:02:90:4d:2a 11 54M -94:-96 100 EPS RSN >> HTCAP WME ATH WPS >> >> /var/log/messages >> ... >> Jul 23 15:34:24 x220 wpa_supplicant[669]: wlan0: CTRL-EVENT-TERMINATING >> Jul 23 15:34:24 x220 kernel: wlan0: Ethernet address: 00:25:d3:7b:94:87 >> Jul 23 15:34:24 x220 devd: Executing '/etc/pccard_ether wlan0 start' >> Jul 23 15:34:24 x220 wpa_supplicant[2563]: Successfully initialized >> wpa_supplicant >> Jul 23 15:34:24 x220 wpa_supplicant[2571]: Successfully initialized >> wpa_supplicant >> Jul 23 15:34:24 x220 wpa_supplicant[2571]: ctrl_iface exists and seems >> to be in use - cannot override it >> Jul 23 15:34:24 x220 wpa_supplicant[2571]: Delete >> '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore >> Jul 23 15:34:24 x220 wpa_supplicant[2571]: Failed to initialize >> control interface '/var/run/wpa_supplicant'. You may have another >> wpa_supplicant process already running or the file was left by an >> unclean termination of wpa_supplicant in which case you will need to >> manually remove this file before starting wpa_supplicant again. >> Jul 23 15:34:24 x220 wpa_supplicant[2571]: ioctl[SIOCS80211, op=26, >> val=0, arg_len=0]: Operation not supported >> Jul 23 15:34:24 x220 wpa_supplicant[2571]: ioctl[SIOCS80211, op=26, >> val=0, arg_len=0]: Operation not supported >> Jul 23 15:34:24 x220 root: /etc/rc.d/wpa_supplicant: WARNING: failed >> to start wpa_supplicant >> Jul 23 15:34:24 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, >> val=0, arg_len=128]: Operation now in progress >> Jul 23 15:34:24 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan >> Jul 23 15:34:25 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, >> val=0, arg_len=128]: Operation now in progress >> Jul 23 15:34:25 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan >> Jul 23 15:34:26 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, >> val=0, arg_len=128]: Operation now in progress >> Jul 23 15:34:26 x220 kernel: ath0: ath_reset_grablock: didn't finish >> after 10 iterations >> Jul 23 15:34:26 x220 kernel: ath0: ath_reset_grablock: warning, >> recursive reset path! >> Jul 23 15:34:26 x220 kernel: ath0: ath_reset: concurrent reset! Danger! >> Jul 23 15:34:26 x220 kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing >> Jul 23 15:34:26 x220 kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing >> Jul 23 15:34:26 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan >
Re: Not work ATH (AR9285) after update [SOLVED]
On Tue, Jul 23, 2013 at 6:21 PM, Adrian Chadd wrote: > Ok, so. > > On 23 July 2013 07:12, Andrey Fesenko wrote: > >>>> i'm horrible news, after update my notebook not nave wi-fi :( >>>> full update system, build and install world and kernel. > > What did it used to run? > > # grep wlan0 /etc/rc.conf wlans_ath0="wlan0" ifconfig_wlan0="WPA DHCP" ifconfig_wlan0_ipv6="inet6 accept_rtadv" >>>> Jul 23 15:34:27 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP >>>> scan >>>> Jul 23 15:34:29 x220 wpa_supplicant[2572]: ioctl[SIOCS80211, op=103, >>>> val=0, arg_len=128]: Operation now in progress >>>> Jul 23 15:34:29 x220 kernel: ath0: ath_reset_grablock: didn't finish >>>> after 10 iterations >>>> Jul 23 15:34:29 x220 kernel: ath0: ath_reset_grablock: warning, >>>> recursive reset path! > > Your previous log indicated multiple copies of wpa_supplicant. That > should be investigated. > >> Not, >> root@x220:~ # ps -A | grep wpa >> 671 - Ss 0:00.73 /usr/sbin/wpa_supplicant -s -B -i wlan0 -c >> /etc/wpa_suppl >> >> Start, or restart work standart >> # /etc/rc.d/netif restart >> this scheme work fine ~year or half year. >> Although of course the chip AR9285 is not very stable, especially in >> combination with some AP. > > That's why I updated the support. It's much more stable now. Except if > you somehow get >1 wpa_supplicant instances running. > >> >> Hm... intresting boot messages >> ... >> Jul 23 17:47:06 x220 kernel: ath0: mem >> 0xf240-0xf240 irq 17 at device 0.0 on pci3 >> Jul 23 17:47:06 x220 kernel: [ath] AR9285 Main LNA config: LNA1 >> Jul 23 17:47:06 x220 kernel: [ath] AR9285 Alt LNA config: LNA2 >> Jul 23 17:47:06 x220 kernel: [ath] LNA diversity disabled, Diversity disabled >> Jul 23 17:47:06 x220 kernel: ath0: [HT] enabling HT modes >> Jul 23 17:47:06 x220 kernel: ath0: [HT] 1 stream STBC receive enabled >> Jul 23 17:47:06 x220 kernel: ath0: [HT] 1 RX streams; 1 TX streams >> Jul 23 17:47:06 x220 kernel: ath0: AR9285 mac 192.2 RF5133 phy 14.0 >> Jul 23 17:47:06 x220 kernel: ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0 > > x220 - is this a thinkpad? Or what kind of laptop is it? > > Have you added this card in yourself? Are both antennas connected? > > The EEPROM settings disable diversity. Thus, the transmit path is > always LNA1, the receive path is always LNA1. So, it should at least > have that antenna connected. > Yes it's thinkpad X220 :) :( hacked BIOS for remove wite list, yes antenna connected card installed near yea ago and all this time working for startup on the rc.conf >> old log >> Jul 2 13:30:02 x220 kernel: ath0: mem >> 0xf240-0xf240 irq 17 at device 0.0 on pci3 >> Jul 2 13:30:02 x220 kernel: ath0: [HT] enabling HT modes >> Jul 2 13:30:02 x220 kernel: ath0: [HT] 1 stream STBC receive enabled >> Jul 2 13:30:02 x220 kernel: ath0: [HT] 1 RX streams; 1 TX streams >> Jul 2 13:30:02 x220 kernel: ath0: AR9285 mac 192.2 RF5133 phy 14.0 >> Jul 2 13:30:02 x220 kernel: ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0 > > What's the svn revision on that? > FreeBSD 10.0-CURRENT #0 r249991 >> and old style reconnect >> Jul 2 14:15:33 x220 wpa_supplicant[516]: CTRL-EVENT-DISCONNECTED >> bssid=58:6d:8f:fa:d9:50 reason=0 >> Jul 2 14:15:33 x220 kernel: wlan0: link state changed to DOWN >> Jul 2 14:15:35 x220 wpa_supplicant[516]: Trying to associate with >> 58:6d:8f:fa:d9:50 (SSID='hometest' freq=2472 MHz) >> Jul 2 14:15:35 x220 wpa_supplicant[516]: Associated with 58:6d:8f:fa:d9:50 >> Jul 2 14:15:35 x220 kernel: wlan0: link state changed to UP >> Jul 2 14:15:35 x220 kernel: ath0: ath_rate_tx_complete: ts_rate=27 >> ts_finaltsi=0 >> Jul 2 14:15:35 x220 kernel: ath0: bad series0 hwrate 0x1b, tries 1 >> ts_status 0x0 >> Jul 2 14:15:35 x220 kernel: ath0: ath_rate_tx_complete: ts_rate=27 >> ts_finaltsi=0 >> Jul 2 14:15:35 x220 kernel: ath0: bad series0 hwrate 0x1b, tries 1 >> ts_status 0x0 >> Jul 2 14:15:35 x220 wpa_supplicant[516]: WPA: Key negotiation >> completed with 58:6d:8f:fa:d9:50 [PTK=CCMP GTK=CCMP] >> Jul 2 14:15:35 x220 wpa_supplicant[516]: CTRL-EVENT-CONNECTED - >> Connection to 58:6d:8f:fa:d9:50 completed (reauth) [id=0 id_str=] >> Jul 2 14:15:35 x220 dhclient: New IP Address (wlan0): 192.168.1.22 >> Jul 2 14:15:35 x220 dhclient: New Subnet Mask (wlan0): 255.255.255.0 >> Jul 2 14:15:35 x220 dhclient: New Broadcast Address (wlan0): 192.168.1.255 >>
RaspberryPi crash/freez random time after ~r253751
Hello, System work stable after migration EABI ~r20130716 (+fix build perl port) after make new images r253751 and r253847 system (RPi) freez after random time building ports. got to collect a backtrace log http://pastebin.com/Bbn9ka4N > uname -a FreeBSD raspberry-pi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253847M: Thu Aug 1 03:54:07 MSK 2013 andrey@my_book.local:/home/andrey/obj/arm.armv6/usr/src/sys/RPI-B-IPv6 arm ___ 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: RaspberryPi crash/freez random time after ~r253751
On Fri, Aug 2, 2013 at 5:09 PM, Andrey Fesenko wrote: > Hello, > > System work stable after migration EABI ~r20130716 (+fix build perl port) > after make new images r253751 and r253847 system (RPi) freez after > random time building ports. > > got to collect a backtrace log http://pastebin.com/Bbn9ka4N > >> uname -a > FreeBSD raspberry-pi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253847M: > Thu Aug 1 03:54:07 MSK 2013 > andrey@my_book.local:/home/andrey/obj/arm.armv6/usr/src/sys/RPI-B-IPv6 > arm after patch http://people.freebsd.org/~andrew/trapframe_align.diff system boot, random time building ports crash system bt log http://pastebin.com/jBJFf8Zt ___ 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"
Spam in console after r336593 (NFS mounted)
Hello. After https://svnweb.freebsd.org/base?view=revision&revision=336593 any make action starting spam errors (svn not work on NFS mounted partitions) svn: E155016: The working copy database at '/usr/src' is corrupt. svn: E155016: The working copy database at '/usr/src' is corrupt. make[2]: "/usr/src/release/Makefile.ec2" line 24: warning: "/usr/local/bin/svn info --show-item last-changed-revision /usr/sr c/release/.." returned non-zero status svn: E155016: The working copy database at '/usr/src' is corrupt. svn: E155016: The working copy database at '/usr/src' is corrupt. make[2]: "/usr/src/release/Makefile.ec2" line 24: warning: "/usr/local/bin/svn info --show-item last-changed-revision /usr/sr c/release/.." returned non-zero status ___ 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"
EFI loader failure, after 20191114-r354699 Z87MX-D3H
Hello, Around starting 20191114 r354699 (memstick tested), my desktop not boot normally. Boot only loader menu (black and white mode) after start i'm see load modules, after this monitor gray, and 15-20s disabled, system block not disable but run silently. system not boot. If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 release, system boot normally My notebook x220 work fine any loaders. desktop BIOS Information Vendor: American Megatrends Inc. Version: F2 Release Date: 05/03/2013 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z87MX-D3H Version: To be filled by O.E.M. Serial Number: To be filled by O.E.M. UUID: 03de0294-0480-057d-0c06-7a0700080009 Wake-up Type: Power Switch SKU Number: To be filled by O.E.M. Family: To be filled by O.E.M. ___ 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: EFI loader failure, after 20191114-r354699 Z87MX-D3H
On Thu, Nov 28, 2019 at 1:24 PM Eugene Grosbein wrote: > > 28.11.2019 16:43, Andrey Fesenko wrote: > > > Hello, > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > boot normally. Boot only loader menu (black and white mode) after > > start i'm see load modules, after this monitor gray, and 15-20s > > disabled, system block not disable but run silently. system not boot. > > So loader works. Try breaking to loader prompt and do: > > set hw.vga.acpi_ignore_no_vga=1 > boot > Hm new test, new problems. Old and new efi, if breaking to loader prompt work only alphabet keys, nums not work :) (on notebook loader work fine) If make echo 'hw.vga.acpi_ignore_no_vga=1' > /boot/loader.conf on flash, and reboot, not fix boot. ___ 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: EFI loader failure, after 20191114-r354699 Z87MX-D3H
On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > > hi! > > I did try to reach you, but mail did bounce back… > > unicast ping me:) > > rgds, > toomas > > > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > > > > Hello, > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > boot normally. Boot only loader menu (black and white mode) after > > start i'm see load modules, after this monitor gray, and 15-20s > > disabled, system block not disable but run silently. system not boot. > > > > If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > > release, system boot normally > > > This video boot second version (Name: "loader.efi") 545 KB https://bsdnir.info/files/efi_fail.mp4 ___ 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: EFI loader failure, after 20191114-r354699 Z87MX-D3H
On Thu, Nov 28, 2019 at 9:20 PM Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 1:24 PM Eugene Grosbein wrote: > > > > 28.11.2019 16:43, Andrey Fesenko wrote: > > > > > Hello, > > > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > > boot normally. Boot only loader menu (black and white mode) after > > > start i'm see load modules, after this monitor gray, and 15-20s > > > disabled, system block not disable but run silently. system not boot. > > > > So loader works. Try breaking to loader prompt and do: > > > > set hw.vga.acpi_ignore_no_vga=1 > > boot > > > > Hm new test, new problems. Old and new efi, if breaking to loader > prompt work only alphabet keys, nums not work :) (on notebook loader > work fine) > If make > echo 'hw.vga.acpi_ignore_no_vga=1' > /boot/loader.conf > > on flash, and reboot, not fix boot. Correction number and underline work, but set hw.vga.acpi_ignore_no_vga not fix boot ___ 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: EFI loader failure, after 20191114-r354699 Z87MX-D3H
Fixed On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: > > > > On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > > > hi! > > I did try to reach you, but mail did bounce back… > > unicast ping me:) > > rgds, > toomas > > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > > Hello, > > Around starting 20191114 r354699 (memstick tested), my desktop not > boot normally. Boot only loader menu (black and white mode) after > start i'm see load modules, after this monitor gray, and 15-20s > disabled, system block not disable but run silently. system not boot. > > If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > release, system boot normally > > > > This video boot second version (Name: "loader.efi") 545 KB > https://bsdnir.info/files/efi_fail.mp4 > > > 403 Forbidden > > :=) > > rgds, > toomas ___ 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: EFI loader failure, after 20191114-r354699 Z87MX-D3H
On Thu, Nov 28, 2019 at 11:31 PM Toomas Soome wrote: > > > > > On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: > > > > Fixed > > > > Thanks. And yea, that one is nasty. I have some guess but nothing too solid… > it may take time to get figured out. > > Have you tested BIOS boot? > > rgds, > toomas > > > On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: > >> > >> > >> > >> On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > >> > >> On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > >> > >> > >> hi! > >> > >> I did try to reach you, but mail did bounce back… > >> > >> unicast ping me:) > >> > >> rgds, > >> toomas > >> > >> On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > >> > >> Hello, > >> > >> Around starting 20191114 r354699 (memstick tested), my desktop not > >> boot normally. Boot only loader menu (black and white mode) after > >> start i'm see load modules, after this monitor gray, and 15-20s > >> disabled, system block not disable but run silently. system not boot. > >> > >> If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > >> release, system boot normally > >> > >> > >> > >> This video boot second version (Name: "loader.efi") 545 KB > >> https://bsdnir.info/files/efi_fail.mp4 > >> > >> > >> 403 Forbidden > >> > >> :=) > >> > >> rgds, > >> toomas > BIOS boot fine, loader colored, installer start normal. ___ 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"
13-Current not format efi partition
bsdinstall script, work in 2019
PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs / }
#!/bin/sh -x
# Make diskname independante
gpart modify -l freebsd-boot -i 1 ada0
gpart modify -l efi -i 2 ada0
gpart modify -l root -i 3 ada0
# Make EFI happy
mount_msdosfs /dev/gpt/efi /media/
mkdir -p /media/EFI/BOOT/
cp /boot/loader.efi /media/EFI/BOOT/BOOTX86.efi
umount /media/
FreeBSD-13.0-CURRENT-amd64-20200206-r357606-disc1.iso not format efi partition
___
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: 13-Current not format efi partition
ср, 12 февр. 2020 г., 06:23 Thomas Mueller :
> from Andrey Fesenko:
>
> > bsdinstall script, work in 2019
>
> PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs
> / }
> #!/bin/sh -x
> # Make diskname independante
> gpart modify -l freebsd-boot -i 1 ada0
> gpart modify -l efi -i 2 ada0
> gpart modify -l root -i 3 ada0
> # Make EFI happy
> mount_msdosfs /dev/gpt/efi /media/
> mkdir -p /media/EFI/BOOT/
> cp /boot/loader.efi /media/EFI/BOOT/BOOTX86.efi
> umount /media/
>
> > FreeBSD-13.0-CURRENT-amd64-20200206-r357606-disc1.iso not format efi
> partition
>
>
> Booting by UEFI would not use or need a freebsd-boot partition.
>
freebsd-boot it's another bug :) it's create automatically, anyway
Add newfs_msdos /dev/gpt/efi fix new behavior installer, but why
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Sun, Mar 8, 2020 at 12:02 AM Michael Tuexen wrote: > > > > > On 7. Mar 2020, at 21:37, Michael Gmelin wrote: > > > > > > > >> On 7. Mar 2020, at 19:01, Michael Tuexen wrote: > >> > >> > >>> > On 7. Mar 2020, at 18:18, Michael Gmelin wrote: > > > > > On 7. Mar 2020, at 18:08, Michael Tuexen wrote: > > > > > > On 7. Mar 2020, at 16:46, Michael Gmelin wrote: > > > > > > > >> On Sat, 07 Mar 2020 11:30:58 -0400 > >> Waitman Gobble wrote: > >> > >> On 2020-03-07 05:10, Ronald Klop wrote: > >>> On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey > >>> wrote: > >>> > On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > > On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey > > wrote: > >> > >> Any workarounds in the meantime? This must affect a lot of > >> people, including those who use 12-: > >> > >> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of > >> FreeBSD:12:amd64 > >> pkg: repository FreeBSD contains packages with wrong ABI: > >> FreeBSD:12.0:amd64 > > > > Still broken for me on 12.1. > > Strange. Mine cleared up automatically the following day. > > It's also strange how few replies I have received. Two private > messages (why?), yours, and that was it. You'd think that people > would be screaming. > > Greg > >>> > >>> > >>> I'm not screaming because I'm settling with the situation and > >>> starting to make workarounds. > >>> And wondering where the official communication of the community is. > >>> Nothing about this situation on www.freebsd.org. All information > >>> about the situation seems scattered through the mailinglists. > >>> > >>> Things are working for me on 13-CURRENT again, but still broken on > >>> 12.1-RELEASE. See attachment. > >>> > >>> Ronald. > >>> ___ > >>> 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" > >> > >> > >> Did you try: > >> pkg update -f > >> > >> > >> I installed 12.1 on a new laptop yesterday, I have not experienced > >> issues with pkg. > >> > > > > This was only an issue on the "latest" branch. If you don't alter > > "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly" > > branch, which fortunately wasn't affected. > > Any idea what is wrong on a stable/12 machine: > > tuexen@stable12:~ % sudo pkg update > Password: > Updating FreeBSD repository catalogue... > pkg: repository meta has wrong version 2 > pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Fetching meta.txz: 100%916 B 0.9kB/s00:01 > pkg: repository meta has wrong version 2 > repository FreeBSD has no meta file, using default settings > Fetching packagesite.txz: 100%6 MiB 586.4kB/s00:11 > pkg: repository meta has wrong version 2 > pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Unable to open created repository FreeBSD > Unable to update repository FreeBSD > Error updating repositories! > tuexen@stable12:~ % sudo pkg update -f > Updating FreeBSD repository catalogue... > pkg: repository meta has wrong version 2 > pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Fetching meta.txz: 100%916 B 0.9kB/s00:01 > pkg: repository meta has wrong version 2 > repository FreeBSD has no meta file, using default settings > Fetching packagesite.txz: 100%6 MiB 645.0kB/s00:10 > pkg: repository meta has wrong version 2 > pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Unable to open created repository FreeBSD > Unable to update repository FreeBSD > Error updating repositories! > tuexen@stable12:~ % sudo pkg upgrade > Updating FreeBSD repository catalogue... > pkg: repository meta has wrong version 2 > pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Fetching meta.txz: 100%916 B 0.9kB/s00:01 > pkg: repository meta has wrong version 2 > repository FreeBSD has no meta file, using default settings > Fetching packagesite.txz: 100%6 MiB 586.4kB/s00:11 > pkg: repository meta has wrong version 2 > pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Unable to open created repository FreeBSD > Unable to update repository FreeBSD > Error updating repositories! > tuexen@stable12:~ % uname -U > 1201512 > tuex
Re: what 3rd party boot mgr is required to boot multiple freebsd versions?
On Tue, Mar 17, 2020 at 1:24 AM Chris wrote: > > I'm attempting to boot multiple versions of FreeBSD. > I started with an install of older 11 with a (u)efi > boot partition installed. I then grabbed an current 11 > usbstick, and installed that. Which stated it needed to > install a (u)efi boot partition. I let it do it. But the > new (additional) install doesn't show up at boot. Altho > my UEFI BIOS sees it. > I guess there are just too many uefi bios versions, > and too many changes in the FreeBSD uefi boot code > to expect consistent results over the long haul. > Should I just convert the 1st efi (GPT) boot partition > to a PMBR, and delete the second efi partition. Or is > there a recommended bootmanager I can use to boot multiple > versions of FreeBSD? Windows? > upgrade system and use https://www.freebsd.org/cgi/man.cgi?query=efibootmgr&sektion=8&manpath=freebsd-release-ports ;) ___ 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: EFI loader failure, after 20191114-r354699 Z87MX-D3H
On Thu, Nov 28, 2019 at 11:31 PM Toomas Soome wrote: > > > On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: > > > > Fixed > > > > Thanks. And yea, that one is nasty. I have some guess but nothing too solid… > it may take time to get figured out. > > Have you tested BIOS boot? > > rgds, > toomas > > > On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: > >> > >> > >> > >> On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > >> > >> On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > >> > >> > >> hi! > >> > >> I did try to reach you, but mail did bounce back… > >> > >> unicast ping me:) > >> > >> rgds, > >> toomas > >> > >> On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > >> > >> Hello, > >> > >> Around starting 20191114 r354699 (memstick tested), my desktop not > >> boot normally. Boot only loader menu (black and white mode) after > >> start i'm see load modules, after this monitor gray, and 15-20s > >> disabled, system block not disable but run silently. system not boot. > >> > >> If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > >> release, system boot normally > >> > >> > >> > >> This video boot second version (Name: "loader.efi") 545 KB > >> https://bsdnir.info/files/efi_fail.mp4 > >> > >> > >> 403 Forbidden > >> > >> :=) > >> > >> rgds, > >> toomas > New news ;) r359151 i'm make memstick with custom refind /mnt/ `-- EFI |-- BOOT | |-- bootx64.efi - refind |-- freebsd | `-- loader.efi - freebsd not boot |-- freebsd_lua | `-- loader_lua.efi - not boot |-- freebsd_simple | `-- loader_simp.efi - boot fine ___ 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: When will the FreeBSD (u)EFI work?
On Sat, Mar 28, 2020 at 12:53 AM Chris wrote: > > On an experiment of the FreeBSD EFI implementation. I installed > a copy of releng/12 from install media. Which left me with: > # gpart show ada0 > => 40 312581728 ada0 GPT (149G) > 40 409600 1 efi (200M) > 409640 31047680 2 freebsd-ufs (15G) >31457320768 3 freebsd-swap (3.7G) >74788904 237792864- free - (141G) > > On this Intel based system, I can stab the F12 key to pick > my UEFI bootable OS, or let it boot according to the order > I setup in the BIOS. So far, so good. > I needed a copy of releng/13 to also work with. Installed a copy > from install media. Which left me with: > # gpart show ada0 > => 40 312581728 ada0 GPT (149G) > 40 409600 1 efi (200M) > 409640 31047680 2 freebsd-ufs (15G) >31457320768 3 freebsd-swap (3.7G) >39137320 532480 4 efi (260M) >39669800 35119104 5 freebsd-ufs (17G) >74788904 237792864- free - (113G) > I *assumed* that the install would activate the new install, and I > would boot straight into it. But no. I am still on the previous > install, and worse, I can't get into the new install -- even if > picking it via stabbing the F12 key. I *still* end up in the previous > install. So looking at what might be causing it. I found the following: > # releng/12 > # mount -t msdosfs /dev/ada0p1 /mnt/ > > # ls /mnt/efi/boot/ > BOOTx64.efi > startup.nsh > > # cat /mnt/efi/boot/startup.nsh > BOOTx64.efi > > # umount /mnt/ > > releng/13 > # mount -t msdosfs /dev/ada0p4 /mnt/ > > # ls /mnt/EFI/freebsd/ > loader.efi > > Why the difference? When will FreeBSD (u)EFI work as expected? > > Thanks in advance for any insights! > Require only single efi part See https://forums.freebsd.org/threads/two-freebsd-installations-and-efi.73968/ ___ 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: ZFS: destroying snapshots without compromising boot environments
On Sat, Mar 28, 2020 at 10:30 AM Graham Perrin wrote: > > I imagine that some of the 2019 snapshots below are redundant. > > Can I safely destroy any of them? > > $ zfs list -t snapshot > NAME USED AVAIL > REFER MOUNTPOINT > copperbowl/ROOT/Waterfox@2020-03-20-06:19:4567.0M - 59.2G - > copperbowl/ROOT/r359249b@2019-08-18-04:04:535.82G - 40.9G - > copperbowl/ROOT/r359249b@2019-08-18-11:28:314.32G - 40.7G - > copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 9.43G - 43.4G - > copperbowl/ROOT/r359249b@2019-09-19-20:03:265.13G - 43.3G - > copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 7.67G - 44.6G - > copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 7.66G - 55.2G - > copperbowl/ROOT/r359249b@2020-01-11-14:15:477.41G - 56.2G - > copperbowl/ROOT/r359249b@2020-03-17-21:57:1712.0G - 59.2G - > copperbowl/iocage/releases/12.0-RELEASE/root@jbrowsers 8K - 1.24G - > copperbowl/poudriere/jails/head@clean328K - 1.89G - > $ beadm list > BE Active Mountpoint Space Created > Waterfox - - 12.2G 2020-03-10 18:24 > r357746f - -1.3G 2020-03-20 06:19 > r359249b NR / 148.9G 2020-03-28 01:19 > $ beadm list -aDs > BE/Dataset/Snapshot Active Mountpoint > Space Created > > Waterfox >copperbowl/ROOT/Waterfox - - 137.0M > 2020-03-10 18:24 > r359249b@2020-03-17-21:57:17 - - 59.2G > 2020-03-17 21:57 >copperbowl/ROOT/Waterfox@2020-03-20-06:19:45 - - 67.0M > 2020-03-20 06:19 > > r357746f >copperbowl/ROOT/r357746f - -1.2G > 2020-03-20 06:19 > Waterfox@2020-03-20-06:19:45 - - 59.2G > 2020-03-20 06:19 > > r359249b >copperbowl/ROOT/r359249b@2019-08-18-04:04:53 - -5.8G > 2019-08-18 04:04 >copperbowl/ROOT/r359249b@2019-08-18-11:28:31 - -4.3G > 2019-08-18 11:28 >copperbowl/ROOT/r359249b@2019-09-13-18:45:27-0 - -9.4G > 2019-09-13 18:45 >copperbowl/ROOT/r359249b@2019-09-19-20:03:26 - -5.1G > 2019-09-19 20:03 >copperbowl/ROOT/r359249b@2019-09-24-20:45:59-0 - -7.7G > 2019-09-24 20:45 >copperbowl/ROOT/r359249b@2020-01-09-17:05:57-0 - -7.7G > 2020-01-09 17:05 >copperbowl/ROOT/r359249b@2020-01-11-14:15:47 - -7.4G > 2020-01-11 14:15 >copperbowl/ROOT/r359249b@2020-03-17-21:57:17 - - 12.0G > 2020-03-17 21:57 >copperbowl/ROOT/r359249b NR / 59.0G > 2020-03-28 01:19 > $ beadm destroy ? ;) ___ 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: When will the FreeBSD (u)EFI work?
On Sat, Mar 28, 2020 at 12:14 PM Toomas Soome wrote: > > > > > On 28. Mar 2020, at 05:28, Chris wrote: > > > > On Fri, 27 Mar 2020 18:31:50 -0700 bsd-li...@bsdforge.com > > <mailto:bsd-li...@bsdforge.com> said > > > >> On Fri, 27 Mar 2020 17:27:27 -0600 Warner Losh i...@bsdimp.com said > >> > On Fri, Mar 27, 2020 at 4:54 PM Chris wrote: > >> > > > On Sat, 28 Mar 2020 01:10:37 +0300 Andrey Fesenko f0and...@gmail.com > >> > > > said > >> > > > >> > > > On Sat, Mar 28, 2020 at 12:53 AM Chris > >> > > > wrote: > >> > > > > > >> > > > > On an experiment of the FreeBSD EFI implementation. I installed > >> > > > > a copy of releng/12 from install media. Which left me with: > >> > > > > # gpart show ada0 > >> > > > > => 40 312581728 ada0 GPT (149G) > >> > > > > 40 409600 1 efi (200M) > >> > > > > 409640 31047680 2 freebsd-ufs (15G) > >> > > > >31457320768 3 freebsd-swap (3.7G) > >> > > > >74788904 237792864- free - (141G) > >> > > > > > >> > > > > On this Intel based system, I can stab the F12 key to pick > >> > > > > my UEFI bootable OS, or let it boot according to the order > >> > > > > I setup in the BIOS. So far, so good. > >> > > > > I needed a copy of releng/13 to also work with. Installed a copy > >> > > > > from install media. Which left me with: > >> > > > > # gpart show ada0 > >> > > > > => 40 312581728 ada0 GPT (149G) > >> > > > > 40 409600 1 efi (200M) > >> > > > > 409640 31047680 2 freebsd-ufs (15G) > >> > > > >31457320768 3 freebsd-swap (3.7G) > >> > > > >39137320 532480 4 efi (260M) > >> > > > >39669800 35119104 5 freebsd-ufs (17G) > >> > > > >74788904 237792864- free - (113G) > >> > > > > I *assumed* that the install would activate the new install, and I > >> > > > > would boot straight into it. But no. I am still on the previous > >> > > > > install, and worse, I can't get into the new install -- even if > >> > > > > picking it via stabbing the F12 key. I *still* end up in the > >> > > > > previous > >> > > > > install. So looking at what might be causing it. I found the > >> > following: > >> > > > > # releng/12 > >> > > > > # mount -t msdosfs /dev/ada0p1 /mnt/ > >> > > > > > >> > > > > # ls /mnt/efi/boot/ > >> > > > > BOOTx64.efi > >> > > > > startup.nsh > >> > > > > > >> > > > > # cat /mnt/efi/boot/startup.nsh > >> > > > > BOOTx64.efi > >> > > > > > >> > > > > # umount /mnt/ > >> > > > > > >> > > > > releng/13 > >> > > > > # mount -t msdosfs /dev/ada0p4 /mnt/ > >> > > > > > >> > > > > # ls /mnt/EFI/freebsd/ > >> > > > > loader.efi > >> > > > > > >> > > > > Why the difference? When will FreeBSD (u)EFI work as expected? > >> > > > > > >> > > > > Thanks in advance for any insights! > >> > > > > > >> > > > > >> > > > Require only single efi part > >> > > > > >> > > > See > >> > > > > >> > > > >> > https://forums.freebsd.org/threads/two-freebsd-installations-and-efi.73968/ > >> > > Thanks for they reply, and link, Andrey! > >> > > Well that confirms it. FreeBSD, unlike other OS implementations, will > >> > > not > >> > > permit booting your chosen "version" via EFI. > >> > > Firstly, *huge* thanks for your informative reply, Warner! > >> > It does today. If you use efibootmgr, you can boot exactly what you > >> > want. I > >> > do it all the time... Though your BIOS may overwrite the EFI vars if you > >> > set too many (I'm looking
Re: ZFS BE not booting
On Thu, May 28, 2020 at 5:26 PM marco wrote: > > On Thu, May 28, 2020 at 07:56:10AM +, you (marco) sent the following to > [freebsd-current] : > > make[1]: stopped in /usr/src > > *** [installworld] Error code 2 > > > > make: stopped in /usr/src > > > > make: stopped in /usr/src > > > > Not sure how I ended up in that situation exactly. > > Think I'm going to destroy that r360723 BE for now and create a new one > > for a later revision and do the build world, kernel and install kernel > > dance and will make notes of all the steps I've taken should the update > > fail at some point. > > > > I decided creating a new BE for r361307 and am now running that revision > using the following steps: > > - destroyed the BE > - created a new one for r361307 and activated it > - rebooted > - updated /usr/src to r361307 > - make buildworld > - make buildkernel > - make installkernel > - portsnap fetch update > - make reinstall of graphics/drm-current-kmod > - mergemaster -Fp > - reboot > - make installworld > - mergemaster -Fi > - make delete-old > - final reboot > > [~] bectl list -aDs > BE/Dataset/Snapshot Active Mountpoint Space Created > > r359556 > zroot/ROOT/r359556 - - 440K > 2020-04-03 20:05 > zroot/ROOT/r361307@2020-05-28-07:40:34-0 - - 6.35G > 2020-05-28 07:40 > > r361307 > zroot/ROOT/r361307 NR / 19.7G > 2020-05-28 07:40 > r361307@2020-05-28-07:40:34-0 - - 6.35G > 2020-05-28 07:40 > too more reboot make buildworld make buildkernel beadm create xxx beadm mount xxx /mnt make installkernel DESTDIR=/mnt mergemaster -Fp -D /mnt make installworld DESTDIR=/mnt mergemaster -Fi -D /mnt make delete-old DESTDIR=/mnt make delete-old-libs DESTDIR=/mnt make reinstall of graphics/drm-current-kmod (add key destdir) beadm umount xxx beadm activate xxx reboot ___ 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"
UFS Resize Not Working Bug 253754
Hello long time not work growfs root 13.0-BETA4 and Current, bhyve and vmware check. Bump https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253754 ___ 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"
Possible regression stuck after poweroff 13-CURRENT
FreeBSD 13.0-BETA4 (CURRENT long time many month) shutdown -p now (poweroff, acpi stop) not stop bhyve maybe over virtualization (host windows virtualbox), reboot work fine https://64.media.tumblr.com/6a1b267b6dfa4d04c7d72fd88ba6e752/9c2e7d3110ca9df4-9a/s640x960/8120345e7062cc26ac2b331b3bbe6b590705d32c.png on host endless run process 29366 root 37 211 M52M kqread 1 7:04 100.92% bhyve: gmirror (bhyve) ___ 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: update to RC4 from RC3 shutdown regression
On Wed, Mar 31, 2021 at 7:37 PM Glen Barber wrote: > > On Wed, Mar 31, 2021 at 11:22:58AM -0500, Antonio Olivares wrote: > > On Wed, Mar 31, 2021 at 11:03 AM Glen Barber wrote: > > > > > > On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote: > > > > Dear all, > > > > > > > > after updating to RC4 with > > > > # freebsd-update -r upgrade 13.0RC4 > > > > When I shutdown, I get error messages AE_??? PCI > > > > > > > > > > > > Press any key to reboot > > > > > > > > It shutdown before from 13.0-BETA4 updated all the way to RC3. I can > > > > save a > > > > screenshot if needed. Thanks. > > > > > > Please do. > > > > > > > Dear Sir, > > > > I shutdown today to see if I got the same message, but I did not. If > > I do encounter this again, I will do my best to save a screenshot and > > post it. > > > > Okay, thank you. > Hello my build box kvm-efi (centos edk2.git-ovmf-x64 0-20201222.1581.g98ff7e3c63) buider start endless freeze reboot and shutdown -p now (set hw.efi.poweroff=0 not fix) virtualbox windows host, reboot work fine shutdown -p require set hw.efi.poweroff=0 FreeBSD new uefi-edk2-bhyve g20210214,2 work fine, uefi-edk2-bhyve-0.2_1,1 shutdown -p require set hw.efi.poweroff=0 (not regression RC3) ___ 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: update to RC4 from RC3 shutdown regression
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698 bug with screen panic CURRENT snapshot On Thu, Apr 1, 2021 at 2:03 PM Antonio Olivares wrote: > > On Wednesday, March 31, 2021, Glen Barber wrote: > > On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote: > >> Dear all, > >> > >> after updating to RC4 with > >> # freebsd-update -r upgrade 13.0RC4 > >> When I shutdown, I get error messages AE_??? PCI > >> > >> > >> Press any key to reboot > >> > >> It shutdown before from 13.0-BETA4 updated all the way to RC3. I can > save a > >> screenshot if needed. Thanks. > > > > Please do. > > > > Glen > > > > I managed.to save a picture but on an older phone(flip flop mickey mouse > phone). I will try to attach here. I just shutdown from xfce menu( after > adding some code that permits this). > > Best Regards, > > Antonio > > > > > ___ > 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: EFI boot partition overwritten
On Fri, Jul 16, 2021 at 3:15 PM Thomas Laus wrote: > > Since CURRENT receives more updates to the EFI boot loader than the > release versions, there should be instructions in the CURRENT > 'usr/src/UPDATING' file on how to update the EFI bootcode. > Old systems have little efi part 800K or smaller and require creating new, end of disk or cut swap.
