daily builds.
Hello. Don't have public access to daily builds since 20140525. Ilia.
Re: daily builds.
On Tue, Jun 10, 2014 at 11:47:08AM +0400, Ilia Zykov wrote: > Hello. > Don't have public access to daily builds since 20140525. The bulk build cluster is undergoing hardware maintenance, which took a bit longer than planned. It should be ready available again soon, and then be as fast as never before ;-) Martin
Re: suspend/resume friendly laptop
On Tue, Jun 10, 2014 at 12:17:35PM +0900, k...@wide.ad.jp wrote: > I'm afraid if this inquiry is a little bit off topic. Not at all. > In my Lenovo X61, suspend/resume doesn't work well in NetBSD 6.1 and > NetBSD 6.99 regardless of the value of > hw.acpi.sleep.vbios > hw.acpi.acpivga0.bios_switch > in non-X11 environment and X11 environment (vesa driver is in use). I have X61s and X60s, both of which can suspend and resume. At least this worked very well for the 6.X series, but for today's -current resume occasionally hangs. Actually, not resuming itself (i.e., the system comes back to life) but indeed the graphics (vesa) do not always resume. I have no idea what causes this non-deterministic behavior, but vesa is a suspect. I would also appreciate hints on how this could be even debugged. > Any information is appreciated but I'd prefer if such laptops are > still available in the market (in brand new shape), and if they are > less than 2kg/4lb. Minor hardware change (such as replacing PCIe-mini > wireless lan card -- it may not be available in Lenovo) is acceptable. I think after the big Intel/X.org/KMS/whatnot thing is resolved, it becomes much easier to start more systematic investigations. - Jukka.
Re: suspend/resume friendly laptop
On Tue, Jun 10, 2014 at 12:17:35PM +0900, k...@wide.ad.jp wrote: > In my Lenovo X61, suspend/resume doesn't work well in NetBSD 6.1 and > NetBSD 6.99 regardless of the value of > hw.acpi.sleep.vbios > hw.acpi.acpivga0.bios_switch > in non-X11 environment and X11 environment (vesa driver is in use). Can you be more descriptive of what does (not) work? Joerg
daily CVS update output
Updating src tree: P src/doc/CHANGES P src/doc/TODO P src/doc/TODO.i18n P src/external/bsd/openpam/dist/doc/man/openpam.3 P src/external/bsd/openpam/dist/doc/man/pam.3 P src/share/man/man4/man4.x86/vmx.4 P src/sys/arch/arm/samsung/exynos5_reg.h P src/sys/arch/bebox/stand/boot/sd.c P src/sys/arch/prep/stand/boot/sd.c P src/sys/arch/sparc64/sparc64/clock.c P src/sys/arch/sparc64/sparc64/cpu.c P src/sys/arch/x86/x86/x86_autoconf.c P src/sys/dev/pci/agp_i810.c P src/sys/dev/pci/agp_i810var.h P src/sys/fs/tmpfs/tmpfs_mem.c P src/sys/fs/tmpfs/tmpfs_vfsops.c P src/sys/net/if.c P src/sys/net/if_ether.h P src/sys/net/if_ethersubr.c P src/sys/netinet6/mld6.c P src/tests/dev/scsipi/Makefile P src/tests/dev/sysmon/Makefile P src/tests/fs/kernfs/Makefile P src/tests/fs/msdosfs/t_snapshot.c P src/tests/fs/nfs/Makefile P src/tests/fs/nullfs/Makefile P src/tests/fs/ptyfs/Makefile P src/tests/fs/puffs/Makefile P src/tests/fs/umapfs/Makefile P src/tests/fs/union/Makefile P src/tests/kernel/Makefile P src/tests/kernel/tty/Makefile P src/tests/lib/libc/sys/Makefile P src/tests/lib/semaphore/pthread/Makefile P src/tests/libexec/Makefile P src/tests/modules/Makefile P src/tests/net/bpf/Makefile P src/tests/net/bpfilter/Makefile P src/tests/net/carp/Makefile P src/tests/net/icmp/Makefile P src/tests/net/if/Makefile P src/tests/net/if_loop/Makefile P src/tests/net/net/Makefile P src/tests/rump/rumpkern/Makefile P src/tests/rump/rumpkern/h_server/Makefile P src/tests/rump/rumpvfs/Makefile P src/usr.sbin/ifmcstat/Makefile P src/usr.sbin/ifmcstat/ifmcstat.c P src/usr.sbin/ypbind/ypbind.c Updating xsrc tree: Killing core files: Running the SUP scanner: SUP Scan for current starting at Wed Jun 11 03:09:22 2014 SUP Scan for current completed at Wed Jun 11 03:10:13 2014 SUP Scan for mirror starting at Wed Jun 11 03:10:13 2014 SUP Scan for mirror completed at Wed Jun 11 03:13:49 2014 Updating release-5 src tree (netbsd-5): Updating release-5 xsrc tree (netbsd-5): Running the SUP scanner: SUP Scan for release-5 starting at Wed Jun 11 03:22:42 2014 SUP Scan for release-5 completed at Wed Jun 11 03:22:50 2014 Updating release-6 src tree (netbsd-6): Updating release-6 xsrc tree (netbsd-6): Running the SUP scanner: SUP Scan for release-6 starting at Wed Jun 11 03:43:58 2014 SUP Scan for release-6 completed at Wed Jun 11 03:44:10 2014 Updating file list: -rw-rw-r-- 1 srcmastr netbsd 41715124 Jun 11 03:53 ls-lRA.gz
Re: Loading firmware for USB device after boot
> On Fri, Jun 06, 2014 at 04:27:00AM +, Thomas Mueller wrote: > > Is it possible to load firmware for a USB device subsequent to boot? > This is the drivers responsability (via the firmload(9) API). > > In this case, the USB device is a wireless network adapter, Atheros > > AR9271, on motherboard but apparently the boot process is too > > impatient. Sometimes the firmware is loaded, but most of the time not. > Please file a PR with useable details, this is a driver bug. > Martin I lost the needed dmesg.boot message because I used the USB-stick installations of NetBSD-current amd64 and i386 to install NetBSD-current on the new replacement hard drive on the other computer, but will get back to it. Does the firmload(9) API give up too soon, before the device has time to respond? Again, sending this is delayed now by the FreeBSD wireless connection, Hiro H50191 USB-stick wireless adapter, device rsu, bugging out. But sometimes athn0 loads and connects successfully with ifconfig athn0 up wpa_supplicant -B -i athn0 -c /etc/wpa_supplicant.conf dhcpcd athn0 I am now at 6.99.43 I notice there was no reference at all to athn0 on the live USB built from source 6.99.13, so I don't know when this was added, couldn't find it in CHANGES file. Tom
