Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
W dniu 2012-10-04 20:51, Lev Serebryakov pisze: Hello, Marek. You wrote 3 октября 2012 г., 23:17:35: atrtc0: AT realtime clock port 0x70-0x71 on acpi0 MS still the same in my environment, running FreeBSD 9.1 under ESXi5.1 host MS Do you have any solution? In my case it was local patch for exotic embedded chipset... Can you send me the patch so I can have a look if I don't use the same chipset ? Regards, -- Marek Salwerowicz ___ 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: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
W dniu 2012-09-19 22:22, Lev Serebryakov pisze: Hello, Freebsd-current. I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to build router's NanoBSD image, to today's morning (MSK time, GMT+4) revision. Unfortunately, I cannot provide exact version, as sources are in this unbootable VM too :) Kernel is GENERIC. VBox configuration is rather stander: 2 CPUs, ICH9, 2GB of RAM. Host is Windows 7/64bit. Booting hangs after (new?) line: atrtc0: AT realtime clock port 0x70-0x71 on acpi0 Hi, still the same in my environment, running FreeBSD 9.1 under ESXi5.1 host Do you have any solution? Regards, -- Marek Salwerowicz ___ 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: Syscons issue Intel D2700
W dniu 2012-07-15 13:31, Poul-Henning Kamp pisze: In message 5002a893.8050...@wp.pl, Marek Salwerowicz writes: W dniu 2012-07-14 19:32, Poul-Henning Kamp pisze: Try the fix I committed in r237203+r237223, that was for a D2500CC which also had bogus VGA behaviour. Thanks, Is it only available in 10-Current or in 9-Stable also ? I belive the same fix will work all the way back to FreeBSD 2.x or so when sos@ optimized syscons to use wide copies, but the code has obviously mutated a fair bit since then. It worked for me in 9.1-PRERELEASE. I've just copied the fbreg.h file modified by you from HEAD into stable sources. And, your fix works with D2500HN - thanks for help. -- Marek ___ 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: Syscons issue Intel D2700
W dniu 2012-07-14 19:32, Poul-Henning Kamp pisze: Try the fix I committed in r237203+r237223, that was for a D2500CC which also had bogus VGA behaviour. Thanks, Is it only available in 10-Current or in 9-Stable also ? -- Marek ___ 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: Syscons issue Intel D2700
Hi, W dniu 2012-02-24 05:11, matt pisze: I'm currently trying to boot an intel evaluation board (D2700) with 10-CURRENT. Installation was make installworld DESTDIR=/mnt/disk make installkernel DESTDIR=/mnt/disk make distribution DESTDIR=/mnt/disk vi /mnt/disk/fstab (added lines for root, swap) unmount /mnt/disk Boot goes fine until the kernel is loaded. Once the kernel is loaded, boot continues, however only the very bottom line is showing kernel messages...the rest of the screen still looks like loader. Once booted, a number of silly attempts with vidcontrol 80x25, vidcontrol -C, vidcontrol VESA_800x600 do not fix the situation. did you manage to fix your issue? I recently bought a D2500HN m/b and have the same problem with 9-Release (I'm trying to install it via PXE but installer menu doesn't work properly..) Regards, -- Marek ___ 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
Can't dynamically load module uart on amd64-current
Hi all, since 18th January I am not able to dynamically load UART module into kernel (the module resposnible for serial ports in PC). After: # kldload uart the dmesg says there are unrecognized interfaces. When I compile uart into kernel, everything works fine.. -- Marek Salwerowicz ___ 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: [Soekris] Soekris net5501 - how to use hardware watchdog?
Hi, Try adding option CPU_SOEKRIS Sorry, for the 5501 thats option CPU_GEODE ---Mike I have added both. Is there any possible test to check if watchdog really does reboot ? Just start /usr/sbin/watchdogd and then kill the process? -- Marek Salwerowicz ___ 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: [Soekris] Soekris net5501 - how to use hardware watchdog?
I have added both. Is there any possible test to check if watchdog really does reboot ? Just start /usr/sbin/watchdogd and then kill the process? Yes, but make sure you do kill -9, not just kill OK, it does reboot :) Thanks for your help ! -- Marek Salwerowicz ___ 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: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current
It would be nice if you enabled verbose kernel messages to get more info. Verbose log in attachment - please see it. I've meant log with problem. When you are loading modules on-fly. so5501a% sudo kldload ata so5501a% sudo kldload atapci.ko and dmesg: pci0: driver added found- vendor=0x1022, dev=0x2082, revid=0x00 domain=0, bus=0, slot=1, func=2 class=10-10-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0220, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pci0:0:1:2: reprobing on driver added found- vendor=0x168c, dev=0x0013, revid=0x01 domain=0, bus=0, slot=17, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0116, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=15 powerspec 2 supports D0 D3 current D0 pci0:0:17:0: reprobing on driver added found- vendor=0x1022, dev=0x209a, revid=0x01 domain=0, bus=0, slot=20, func=2 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02a0, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pci0:0:20:2: reprobing on driver added atapci0: AMD ATA controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0 ata0: ATA channel 0 on atapci0 ata0: reset tp1 mask=03 ostat0=60 ostat1=50 ata0: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 ata0: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=20 stat1=50 devices=0x2 ata0: Identifying devices: 0002 ata0: New devices: 0002 ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ata1: ATA channel 1 on atapci0 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: Identifying devices: ata1: New devices: found- vendor=0x1022, dev=0x2094, revid=0x02 domain=0, bus=0, slot=21, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 pci0:0:21:0: reprobing on driver added found- vendor=0x1022, dev=0x2095, revid=0x02 domain=0, bus=0, slot=21, func=1 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 pci0:0:21:1: reprobing on driver added pci1: driver added so5501a% so5501a% sudo kldload ataamd so5501a% sudo kldload atadisk dmesg: ad1: Skipping 80pin cable check ad1: Skipping 80pin cable check ad1: setting UDMA33 ad1: 7631MB LEXAR ATA FLASH CARD 20070228 at ata0-slave UDMA33 ad1: 15630048 sectors [15506C/16H/63S] 1 sectors/interrupt 1 depth queue GEOM: new disk ad1 GEOM: ad1: media size does not match label. so5501a% so5501a% sudo atacontrol list ATA channel 0: Master: no device present Slave: ad1 LEXAR ATA FLASH CARD/20070228 ATA/ATAPI revision 4 ATA channel 1: Master: no device present Slave: no device present so5501a% So now it works, I am able to mount partition at ad1 ;) -- Marek Salwerowicz ___ 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
Soekris net5501 - how to use hardware watchdog?
Hi all, what modules to kernel should I load in order to make use of hardware watchdog installed in Soekris net5501 ? AFAIK it is located in CS5536 chip, but don't know which module is responsible for access to it? I was trying to load ichwd module, but it is only Intel watchdog module? -- Marek Salwerowicz ___ 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
Soekris net5501-70 problem with loading ATA modules on FreeBSD-Current
Hi all, I am unable to dynamically load modules to support ATA disks on soekris net5501-70. I boot via PXE diskless FreeBSD-Current. In kernel config there are commented out options: #device ata #device atadisk After boot, I load modules: # kldload ata.ko # kldload atapci.ko # kldload ataamd # kldload atadisk so5501a% kldstat Id Refs AddressSize Name 1 59 0xc040 4179cc kernel 21 0xc0818000 6c50 procfs.ko 32 0xc081f000 6d80 pseudofs.ko 41 0xc0826000 68c8 geom_md.ko 51 0xc082d000 9b70 if_sis.ko 63 0xc0837000 28400miibus.ko 71 0xc086 a418 if_vr.ko 81 0xc2e78000 9000 tmpfs.ko 94 0xc2ef1000 e000 ata.ko 102 0xc2f03000 8000 atapci.ko 111 0xc2f0d000 3000 ataamd.ko 121 0xc2f17000 4000 atadisk.ko so5501a% after that, in dmesg: atapci0: AMD ATA controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0 atapci0: failed to add ata child device atapci0: failed to add ata child device And I am unable to access my HDD or CF. (see full 'dmesg' and 'kldstat -v' in attachment) After compiling kernel with options: device ata device atadisk Everything works fine. But I would like to be able to load / unload ATA modules.. -- Marek Salwerowicz so5501a% kldstat -v Id Refs AddressSize Name 1 59 0xc040 4179cc kernel (/boot/kernel.soekris/kernel) Contains modules: Id Name 71 newreno 69 if_lo 64 elf32 65 shell 70 igmp 72 nfs_common 76 krpc 75 nfslockd 74 nfs 52 devfs 77 ufs 58 g_part_bsd 60 g_part_mbr 59 g_part_ebr 83 legacy/cpu 82 nexus/legacy 66 cpu/cpufreq 39 null 106 isa/sysresource 105 nexus/ram 104 root/nexus 81 pci/geode 80 isa/pnpbios 79 io 73 nfslock 50 pci/uart 103 qpi/pcib 102 nexus/qpi 49 isa/uart 101 isa/orm 100 acpi/atdma 99 isa/atdma 98 legacy/isa 97 acpi/attimer 96 isa/attimer 38 mem 95 acpi/atrtc 94 isa/atrtc 93 acpi/atpic 92 isa/atpic 48 random 47 pty 46 pci/vgapci 45 pci/pcib 91 legacy/pir 44 pcib/pci 43 pci/isab 42 pci/ignore_pci 90 pci/pcibios_pcib 89 isa/pcibus_pnp 88 legacy/pcib 87 isa/pmtimer 86 acpi/npxisa 85 isa/npxisa 84 nexus/npx 63 isa/pnp 62 eisab/isa 61 isab/isa 41 pci/hostb 40 pci/fixup_pci 51 watchdog 78 g_class 53 g_dev 55 g_vfs 67 rootbus 57 g_part 54 g_disk 56 g_label 68 ether 21 0xc0818000 6c50 procfs.ko (/boot/kernel.soekris/procfs.ko) Contains modules: Id Name 2 procfs 32 0xc081f000 6d80 pseudofs.ko (/boot/kernel.soekris/pseudofs.ko) Contains modules: Id Name 1 pseudofs 41 0xc0826000 68c8 geom_md.ko (/boot/kernel.soekris/geom_md.ko) Contains modules: Id Name 3 g_md 51 0xc082d000 9b70 if_sis.ko (/boot/kernel.soekris/if_sis.ko) Contains modules: Id Name 35 pci/sis 34 sis/miibus 63 0xc0837000 28400miibus.ko (/boot/kernel.soekris/miibus.ko) Contains modules: Id Name 33 miibus/xmphy 32 miibus/ukphy 31 miibus/truephy 30 miibus/tlphy 29 miibus/tdkphy 28 miibus/ruephy 27 miibus/rlphy 26 miibus/rgephy 25 miibus/rdcphy 24 miibus/qsphy 23 miibus/pnaphy 22 miibus/nsphyter 21 miibus/nsphy 20 miibus/nsgphy 19 miibus/mlphy 18 miibus/lxtphy 17 miibus/jmphy 16 miibus/ip1000phy 15 miibus/inphy 14 miibus/icsphy 13 miibus/gentbi 12 miibus/xlphy 11 miibus/e1000phy 10 miibus/ciphy 9 miibus/brgphy 8 miibus/bmtphy 7
Re: Soekris net5501-70 problem with loading ATA modules onFreeBSD-Current
I think these errors caused by devices created for legacy ISA compatibility via device hints. Go to device.hints and remove all ATA stuff from there to force ATA to be detected only via PCI. Another problem I see here with module load order. Loading atapci before ataadm will make generic driver attach to controller, not specific one. Unluckily loading in different order won't help, I think, because ataamd depends on atapci and will load it automatically. Hi, we have commented these lines in device.hints: #hint.ata.0.at=isa #hint.ata.0.port=0x1F0 #hint.ata.0.irq=14 #hint.ata.1.at=isa #hint.ata.1.port=0x170 #hint.ata.1.irq=15 and now there are no errors in dmesg, but: 1. ataamd doesn't load automatically atapci.ko, so I kept the order. 2. after loading modules and # atacontrol detach ata0 # atacontrol attach ata0 I can't still see my CF connected to net5501. Is it possible to load dynamically modules or do they have to be compiled in kernel... ? -- Marek Salwerowicz ___ 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: Soekris net5501-70 problem with loading ATA modulesonFreeBSD-Current
It would be nice if you enabled verbose kernel messages to get more info. Verbose log in attachment - please see it. Is it possible to load dynamically modules or do they have to be compiled in kernel... ? It should, but I haven't used it. What for do you need to load/unload them in run time? The Soekris box are being used in computer lab by students. Normally they use diskless FreeBSD (loaded via PXE/NFS), but in some cases they might install something on CF (but in general we want to prevent them from reading / writing to CF). -- Marek Salwerowicz so5501a% cat /var/run/dmesg.boot Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #4: Sat Jan 15 23:19:52 CET 2011 a...@volt.iem.pw.edu.pl:/tmp/obj/i386.i386/usr/src/sys/SOEKRIS i386 Preloaded elf kernel /boot/kernel.soekris/kernel at 0xc08ad000. Preloaded elf module /boot/kernel.soekris/procfs.ko at 0xc08ad140. Preloaded elf module /boot/kernel.soekris/pseudofs.ko at 0xc08ad1f4. Preloaded elf module /boot/kernel.soekris/geom_md.ko at 0xc08ad2ac. Preloaded elf module /boot/kernel.soekris/if_sis.ko at 0xc08ad360. Preloaded elf module /boot/kernel.soekris/miibus.ko at 0xc08ad414. Preloaded elf module /boot/kernel.soekris/if_vr.ko at 0xc08ad4c8. Calibrating TSC clock ... TSC clock: 499912260 Hz CPU: Geode(TM) Integrated Processor by AMD PCS (499.91-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x5a2 Family = 5 Model = a Stepping = 2 Features=0x88a93dFPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX AMD Features=0xc040MMX+,3DNow!+,3DNow! Data TLB: 16 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 32 bytes/line, 1 lines/tag, 16-way associative L1 instruction cache: 64 kbytes, 32 bytes/line, 1 lines/tag, 16-way associative L2 internal cache: 128 kbytes, 32 bytes/line, 1 lines/tag, 4-way associative Write Allocate Disable real memory = 536870912 (512 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c26000 - 0x1f6b9fff, 514408448 bytes (125588 pages) avail memory = 515964928 (492 MB) bios32: Found BIOS32 Service Directory header at 0xc00fac00 bios32: Entry = 0xfac40 (c00fac40) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xac61 Other BIOS signatures found: mem: memory K6-family MTRR support enabled (2 registers) null: null device, zero device io: I/O random: entropy source, Software, Yarrow nfslock: pseudo-device pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 1 [class=06] [hdr=80] is there (id=20801022) pcibios: BIOS version 2.01 pcib0: Host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pci0: domain=0, physical bus=0 found- vendor=0x1022, dev=0x2080, revid=0x31 domain=0, bus=0, slot=1, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0220, cachelnsz=8 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x1022, dev=0x2082, revid=0x00 domain=0, bus=0, slot=1, func=2 class=10-10-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0220, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 map[10]: type Memory, range 32, base 0xa000, size 14, enabled found- vendor=0x1106, dev=0x3053, revid=0x96 domain=0, bus=0, slot=6, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xe100, size 8, enabled map[14]: type Memory, range 32, base 0xa0004000, size 8, enabled found- vendor=0x1106, dev=0x3053, revid=0x96 domain=0, bus=0, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xe200, size 8, enabled map[14]: type Memory, range 32, base 0xa0004100, size 8, enabled found- vendor=0x1106, dev=0x3053, revid=0x96 domain=0, bus=0, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port
Re: NFSv4 and pam_mount - mounting user home directories (with security?)
I think you can stick it just before return 0 in /etc/rc.d/nfsd. (I'd probably just go with the sysctl vfs.newnfs.server_min_nfsvers=4 line in this case, since you want it unconditionally?) Or, if you don't want to build a kernel with options NFSD, I think you can get nfsd.ko loaded early by fiddling with loader.conf, but I'm not volunteering to figure out what works there:-) rick Ok, that problem has been solved ;) In nfs_precmd it checks if the option in rc.conf is set. If yes, it tries to set the sysctl flag, it it fails, loads nfsd module and then sets again the sysctl flag. But I have another question - maybe you will know the answer. So I would like NFSv4 to serve user home directories across the network for all workstations, but I would like it to protect using user password Eg. on workstation I want to do: sudo mount -t nfs -o nfsv4 nfs4-server:/home/user1 /home/user1 and then I want to be asked for password of user1 at server (or in the whole network - users and passwords are stored in LDAP server and workstation and server have access to it) Is it possible to do with NFSv4? -- Marek Salwerowicz ___ 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
NFSv4 and pam_mount - mounting user home directories.
Hi, 1. I have a NFSv4-enabled server with /etc/exports like: V4: / -sec=sys /home/stud -sec=sys /etc/rc.conf: nfs_server_enable=YES nfsv4_server_enable=YES nfsuserd_enable=YES Is it possible to run ONLY NFSv4 server (without NFSv3 compatibility) ? 2. On a client station I installed pam_mount module in order to mount home directory from server automatically during logging in to station. I would like to mount it via NFSv4. In pam_mount.conf.xml I inserted: volume fstype=nfs server=free pgrp=stud path=/home/stud/%(USER) mountpoint=/home/stud/%(USER) / volume fstype=nfs server=free pgrp=prac path=/home/prac/%(USER) mountpoint=/home/prac/%(USER) / nfsmountmount_nfs -o nfsv4 %(SERVER):%(VOLUME) %(MNTPT)/nfsmount And it works, but: On a client station every user can be root, and I don't want even root to be able to mount user's home directories without giving a password (via mount_nfs command)- is it possible? After mounting there is a strange UID and GID: ls -la total 472 drwxr-xr-x 10 32767 32767 1024 8 sty 23:00 ./ drwxr-xr-x 9 root wheel512 1 wrz 2009 ../ -rw--- 1 32767 32767 0 12 cze 2010 .Xauthority drwxr-xr-x 3 32767 32767512 12 cze 2010 .cache/ -rw--- 1 32767 32767 68693 8 sty 21:11 .hist -rw--- 1 32767 32767 0 11 cze 2010 .history the UID should be 700. -- Marek Salwerowicz ___ 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: NFSv4 and pam_mount - mounting user home directories.
What I am missing ? /etc/sysctl.conf is applied before rc.d/nfs* ? That would be my guess. The sysctl's aren't setable until the modules are loaded. If you build a kernel with options NFSD in its kernel config file, then it should be setable as above, I think? (I always use sysctl manually after booting, so I don't really know how /etc/sysctl.conf works. After manually setting: salwe...@freebsd:/etc#sudo sysctl vfs.newnfs.server_max_nfsvers=4 vfs.newnfs.server_max_nfsvers: 4 - 4 salwe...@freebsd:/etc#sudo sysctl vfs.newnfs.server_min_nfsvers=4 vfs.newnfs.server_min_nfsvers: 4 - 4 salwe...@freebsd:/etc# We are still able to mount via NFSv3 (even when those two lines are commented in sysctl.conf). Any other idea.. ? -- Marek Salwerowicz ___ 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: NFSv4 and pam_mount - mounting user home directories.
It just worked for me. Try setting the sysctl before starting nfsd. If you are starting the daemons manually for a kernel that doesn't have options NFSD do: # nfsuserd # mountd -e -r # sysctl vfs.newnfs.server_min_nfsvers=4 # nfsd -e -u -t -n 8 - mountd -e loads the module, so you can do the sysctl after that and before starting the nfsd. (Or build a kernel with options NFSD and do the sysctl anytime before starting the nfsd.) rick ps: I tested the FreeBSD-8 client. Other clients may not even talk to the NFS server during mounting. For those, the mount would succeed, but subsequent use of the mount won't work. I tested it on 8.1 Release (GENERIC) i386 (two VMs): server: /etc/rc.conf: #nfsv4_server_enable=YES #nfs_server_enable=YES #nfsuserd_enable=YES made modification in /etc/exports: V4: /usr -sec=sys -network 192.168.183.0 -mask 255.255.255.0 /usr/home -sec=sys -network 192.168.183.0 -mask 255.255.255.0 nfs4-server# nfsuserd nfs4-server# mountd -e -r nfs4-server# sysctl vfs.newnfs.server_min_nfsvers=4 vfs.newnfs.server_min_nfsvers: 2 - 4 nfs4-server# nfsd -e -u -t -n 8 nfs4-server# but now client is unable to mount both nfsv4 and nfsv3: nfs4-client# mount_nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4/ [tcp] 192.168.183.131:/home: nfsd: RPCPROG_NFS: RPC: Remote system error - Connection refused ^C nfs4-client# mount_nfs 192.168.183.131:/usr/home /tmp/nfs3/ ^C (hangs for a long time) nfs4-client# -- Marek Salwerowicz ___ 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: NFSv4 and pam_mount - mounting user home directories.
Again, it works for me (using a pretty current FreeBSD client). The only difference is that I never run mount_nfs directly and would use the following command: # mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4 Assuming the client is a FreeBSD8 box on the 192.168.183.0 subnet, I don't know why it wouldn't work, except that I'd suggest trying the command the way I type it, in case that runs it with somewhat different options? rick So, I added in /etc/rc.conf: rpcbind_enable=YES reboot and again typed the commands above. and now it seems to WORK ;) : nfs4-client# mount -t nfs -o nfsv4 192.168.183.131:/home /tmp/nfs4 nfs4-client# mount -t newnfs 192.168.183.131:/home on /tmp/nfs4 (newnfs) nfs4-client# umount /tmp/nfs4 nfs4-client# mount -t nfs 192.168.183.131:/usr/home /tmp/nfs3 [tcp] 192.168.183.131:/usr/home: NFSPROC_NULL: RPC: Program/version mismatch; low version = 4, high version = 4 ^C nfs4-client# with mount_nfs command it behaves the same. Good to know if it will work with nfsv4 server started via rc.conf and sysctl values in sysctl.conf.. -- Marek Salwerowicz ___ 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: NFSv4 and pam_mount - mounting user home directories.
Good to know if it will work with nfsv4 server started via rc.conf and
sysctl values in sysctl.conf..
build a kernel with options NFSD in its config file and then try it
with that kernel, and then you'll find out...
How about patching the /etc/rc.d/nfsd script like this:
[..]
nfsd_precmd()
{
if checkyesno nfs_server_newnfs_only; then
echo 'NFS server serving only newnfs (NFSv4)=YES'
sysctl vfs.newnfs.server_min_nfsvers=4 /dev/null
fi
[..]
It checks if there is a
nfs_server_newnfs_only=YES
set in rc.conf, and if so, it runs the sysctl command.
But, after testing, it is too late (nfsd starts with NFSv3 support). Any idea
where to put that patch ?
--
Marek Salwerowicz
___
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: nfssvc not available or version mismatch (nfsv4 client)
Try loading all of the modules one-by-one. so, after loading nfssvc.ko: vm-salwerom% sudo ./nfsuserd start Starting nfsuserd. vm-salwerom% sudo ./nfscbd start Starting nfscbd. nfscbd: Can't get fully qualified host name vm-salwerom% kldstat Id Refs AddressSize Name 1 29 0x8010 711d58 kernel 21 0x80812000 85d0 procfs.ko 32 0x8081b000 9628 pseudofs.ko 41 0x80825000 68ad0if_em.ko 51 0x80a12000 2c92 geom_md.ko 61 0x80a15000 50fb tmpfs.ko 71 0x80a1b000 1fa green_saver.ko 83 0x80a1c000 381 nfssvc.ko 92 0x80a1d000 fd24 nfscommon.ko 101 0x80a2d000 2df67nfscl.ko vm-salwerom% I am able to mount via nfsv4: vm-salwerom% mount_nfs -o nfsv4 free:/home/stud/salwerom nfs vm-salwerom% mount 194.29.146.3:/ on / (nfs, read-only) devfs on /dev (devfs, local) /dev/md0 on /etc (ufs, local) procfs on /proc (procfs, local) tmpfs on /tmp (tmpfs, local) tmpfs on /var (tmpfs, local) tmpfs on /home/stud/salwerom (tmpfs, local) free:/home/stud/salwerom on /home/stud/salwerom/nfs (newnfs) vm-salwerom% The problem is how to automatically load during system boot nfssvc(.ko) ? -- Marek Salwerowicz ___ 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: nfssvc not available or version mismatch (nfsv4 client)
kldload nfssvc dmesg | tail -n 10 ? vm-salwerom% sudo kldload nfssvc kldload: can't load nfssvc: File exists but: vm-salwerom% sudo kldload nfssvc.ko vm-salwerom% dmesg | tail -n 10 em0 at 194.29.146.128 server 194.29.146.27 server name amp2 subnet mask 255.255.255.0 router 194.29.146.1 rootfs 194.29.146.3:/ rootopts nolockd hostname vm-salwerom Adjusted interface em0 SMP: AP CPU #1 Launched! Trying to mount root from nfs: []... NFS ROOT: 194.29.146.3:/ KLD nfscommon.ko: depends on nfssvc - not available or version mismatch linker_load_file: Unsupported file type KLD nfscl.ko: depends on nfssvc - not available or version mismatch linker_load_file: Unsupported file type vm-salwerom% vm-salwerom% so, why if I want to load nfssvc I have to type it with the suffix? How can I tell nfsuserd and anfscbd to try to load it with suffix during system boot? -- Marek Salwerowicz ___ 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: nfssvc not available or version mismatch (nfsv4 client)
I'm not very good at this stuff so others might need to chime in, but it looks to me like some of your kernel modules are from different builds. I always: # make KERNEL=kernel_name install after doing a kernel build, which copies the kernel and all the modules to /boot/kernel_name. I always use a kernel_name other than kernel just in case it doesn't work, then you can move it over if is seems ok. Both nfscl.ko and nfsd.ko specify nfssvc.ko as a module they depend on, so they should be loaded automagically if all the correct versions are in the /boot/kernel_name tree. (At least it works that way for me.) Kernel modules are from the same build. look at this: vm-salwerom% kldstat Id Refs AddressSize Name 1 19 0x8010 711d58 kernel 21 0x80812000 85d0 procfs.ko 32 0x8081b000 9628 pseudofs.ko 41 0x80825000 68ad0if_em.ko 51 0x80a12000 2c92 geom_md.ko 61 0x80a15000 50fb tmpfs.ko 71 0x80a1b000 1fa green_saver.ko vm-salwerom% sudo kldload nfssvc kldload: can't load nfssvc: File exists vm-salwerom% kldstat Id Refs AddressSize Name 1 19 0x8010 711d58 kernel 21 0x80812000 85d0 procfs.ko 32 0x8081b000 9628 pseudofs.ko 41 0x80825000 68ad0if_em.ko 51 0x80a12000 2c92 geom_md.ko 61 0x80a15000 50fb tmpfs.ko 71 0x80a1b000 1fa green_saver.ko vm-salwerom% sudo kldload nfssvc.ko ---the suffix is needed vm-salwerom% kldstat Id Refs AddressSize Name 1 21 0x8010 711d58 kernel 21 0x80812000 85d0 procfs.ko 32 0x8081b000 9628 pseudofs.ko 41 0x80825000 68ad0if_em.ko 51 0x80a12000 2c92 geom_md.ko 61 0x80a15000 50fb tmpfs.ko 71 0x80a1b000 1fa green_saver.ko 81 0x80a1c000 381 nfssvc.ko vm-salwerom% so I am able to load nfssvc.ko (with '.ko' suffix) ant unable to load nfssvc (without '.ko' suffix) - why ? -- Marek Salwerowicz ___ 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
nfssvc not available or version mismatch (nfsv4 client)
Hi all, I am trying to run NFSv4 client on 64bit FreeBSD 9.0-Current. I have inserted into /etc/rc.conf following lines: nfsuserd_enable=YES nfscbd_enable=YES and after restart, during boot there is a meesage: Jan 6 23:50:56 vm-salwerom root: /etc/rc: WARNING: failed to start nfsuserd Jan 6 23:50:56 vm-salwerom kernel: KLD nfscommon.ko: depends on nfssvc - not available or version mismatch Jan 6 23:50:56 vm-salwerom kernel: linker_load_file: Unsupported file type Jan 6 23:50:59 vm-salwerom root: /etc/rc: WARNING: failed to start nfscbd Jan 6 23:50:59 vm-salwerom kernel: KLD nfscl.ko: depends on nfssvc - not available or version mismatch Jan 6 23:50:59 vm-salwerom kernel: linker_load_file: Unsupported file type the file nfssvc exists: vm-salwerom% ls /boot/kernel/nfss* /boot/kernel/nfsserver.ko /boot/kernel/nfssvc.ko Is there a problem with kernel modules or something else? -- Marek Salwerowicz ___ 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
Atheros bluetooth unrecognizable 0cf3:3002
Hi, I have built-in bluetooth atheros. On ubuntu linux it is shown as (lsusb): Bus 003 Device 006: ID 0cf3:3002 Atheros Communications, Inc. Unfortunately, FreeBSD-Current can't see it as bluetooth device (despite loading ng_ubt module to kernel... ): ugen0.4: product 0x3000 vendor 0x0cf3 at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON What modules should I load into kernel to see it as bluetooth device? -- Marek Salwerowicz ___ 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
