Re: FreeBSD 9.0 - GPT boot problems?
On Sat, 24 Mar 2012 18:50:13 +0100 Christian Laursen wrote: > It sounds a bit like the BIOS thinks that since the disk uses GPT you > want to EFI boot. That could very well be the case. > As far as I know the default bootcode in the PMBR is > meant for old style BIOS booting. Hmm, I was hoping that the pmbr / gptboot would work "both ways". > Is it possible to disable EFI in your BIOS? If that is the case, that's > probably the easiest solution. No, I haven't found any place to do that. Before I installed FreeBSD on this SSD (before it was partitioned with gpart) it showed up in the BIOS under "hard drive". (Other choices are "removable drive" Now it shows up under "EFI device", and doesn't show up under "hard drive". > I'm unsure of the current state of EFI boot in FreeBSD but a little bit > of searching did not look promising. Yes, after a bit of searching I agree with you. If anyone knows of a EFI capable boot loader for FreeBSD, I'm willing to try it. Rather that, than having to deal with grub, elilo or the other stuff. -- Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 9.0 - GPT boot problems?
On 03/24/12 17:26, Torfinn Ingolfsen wrote: Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many thanks to all who made it that way), but when I try to boot the machine from the SSD afterwards, I just get this message from the BIOS: "ERROR: No boot disk has been detected or the disk has failed." I tried selecting the SSD from the boot menu (via F12) instead (it shows up as "EFI: M4-CT128M4SSD2"), but got the same message. I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest available), still no dice. It sounds a bit like the BIOS thinks that since the disk uses GPT you want to EFI boot. As far as I know the default bootcode in the PMBR is meant for old style BIOS booting. Is it possible to disable EFI in your BIOS? If that is the case, that's probably the easiest solution. I'm unsure of the current state of EFI boot in FreeBSD but a little bit of searching did not look promising. -- Christian Laursen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Can't load many network kernel module in 8.3-PREREALEASE
On Fri, 23 Mar 2012, Quentin Schwerkolt wrote: > I can't load many if_* module on FreeBSD 8.3-PRERELEASE on amd64 and i386. > I have rebuild the system from the latest source. When I try a kldload > /boot/kernel/if_*.ko I have error such as "file exist" or "exec format > error". I have no idea why you'd want to do that :) but you'll find that all the 'File exist' ones were already included in your kernel. > kldstat just after system start: > Id Refs AddressSize Name > 11 0x8010 e58280 kernel 'kldstat -v' will show all modules included in your (GENERIC?) kernel. > kldload -v /boot/kernel/if_*.ko: > kldload: can't load /boot/kernel/if_ae.ko: File exists > kldload: can't load /boot/kernel/if_age.ko: File exists > kldload: can't load /boot/kernel/if_alc.ko: File exists > kldload: can't load /boot/kernel/if_ale.ko: File exists > kldload: can't load /boot/kernel/if_an.ko: File exists > kldload: can't load /boot/kernel/if_ath.ko: Exec format error > kldload: can't load /boot/kernel/if_aue.ko: Exec format error > kldload: can't load /boot/kernel/if_axe.ko: Exec format error I'm not certain about the 'Exec format error' messages. Then below are listed the modules loaded that weren't in your kernel. > Loaded /boot/kernel/if_bridge.ko, id=2 > Loaded /boot/kernel/if_bwi.ko, id=4 [..] > Loaded /boot/kernel/if_vte.ko, id=45 > Loaded /boot/kernel/if_wpi.ko, id=46 > > kldstat after run kldload: > Id Refs AddressSize Name > 1 151 0x8010 e58280 kernel > 21 0x81012000 585a if_bridge.ko > 31 0x81018000 3534 bridgestp.ko > 41 0x8101c000 151d3if_bwi.ko [..] Now showing all modules that were loaded in addition to those in kernel. Again, 'kldstat -v' will show all of them, with details of loaded ones. cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 9.0 - GPT boot problems?
Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many thanks to all who made it that way), but when I try to boot the machine from the SSD afterwards, I just get this message from the BIOS: "ERROR: No boot disk has been detected or the disk has failed." I tried selecting the SSD from the boot menu (via F12) instead (it shows up as "EFI: M4-CT128M4SSD2"), but got the same message. I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest available), still no dice. If I use the usb stick I installed from, I can select the boot device, and actually boot from it, so there doesn't seem to be anything wrong with the SSD. I tried: kg-vm2# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 bootcode written to ada0 in case there was something wrong with the bootcode, but I still get the message "ERROR: No boot disk has been detected or the disk has failed." gpart shows this: root@kg-vm2# gpart show ada0 => 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 119537664 2 freebsd-ufs (57G) 1195378268388608 3 freebsd-swap (4.0G) 127926434 121634816 4 freebsd-ufs (58G) 249561250 508397- free - (248M) and root is on ada0p2, with swap on ada0p3: root@kg-vm2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ada0p2 56G2.3G 49G 4%/ devfs 1.0k1.0k 0B 100%/dev root@kg-vm2# swapinfo -h Device 1K-blocks UsedAvail Capacity /dev/ada0p3 4194304 0B 4.0G 0% Has anyone seen anything like this before? Any hints on what I can do? References: 1) http://sites.google.com/site/tingox/aspire_x1470_fbsd -- Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Debugging periodic scripts
On Fri, 23 Mar 2012 04:08:47 -0700 Jeremy Chadwick wrote: > Editing /etc/periodic/security/510.ipfdenied's hashbang line to use -x > doesn't change the behaviour either (maybe stderr gets sent to > /dev/null?), whether I run it by hand as a script or via "periodic > security". Use "set -x" instead of modifying the first line (I assume the script is already started with the correct shell, so the first line is ignored). I would also add "env" before and after the sourcing of the periodic.conf to see what is defined or not. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9-STABLE + Infiniband - incorrect interface counters
Hi, I'm playing with two FreeBSD 9-STABLE boxes connected via 10Gbps Infiniband (more details below) in Infiniband connected mode. I see incorrect interface statistics (e.g. in netstat output), output counters are 2x more than expected. EXAMPLE, ftp transfer of 1 GiB file: ftp> put file /dev/null local: file remote: /dev/null 229 Entering Extended Passive Mode (|||57978|) 150 Opening BINARY mode data connection for '/dev/null'. 100% |***| 953 MiB 390.43 MiB/s 00:00 ETA 226 Transfer complete. 10 bytes sent in 00:02 (390.13 MiB/s) Netstat on receiving side, counters are correct (for input): lexa@home-gw:/home/lexa# netstat -I ib1 5 input (ib1) output packets errs idrops bytespackets errs bytes colls 0 0 0 0 0 0 0 0 13955 0 0 222688126 9027 01192796 0 48921 0 0 780832960 32129 04240596 0 0 0 0 0 0 0 80 0 Sum of bytes (input) is 1003521086, as expected. Netstat on sending size, output is 2x more: lexa@new-gw:/home/lexa# netstat -I ib0 5 input (ib0) output packets errs idrops bytespackets errs bytes colls 1 0 0100 0 0 0 0 41162 0 02305210 62878 0 2008325984 0 1 0 0100 0 0 0 0 It looks like packet count is correct (13955+48921=62876, two packets missed somewhere), while byte count is exact 2x more. More details on my setup FreeBSD 9-STABLE, cvsuped today. One box is Core 2 Quad (Q9300), second one Core i7-920 1) Device MELLANOX MHEA28-XTC 10GBPS INFINIBAND HCA CARD (two port) Boot message: ib_mthca0: mem 0xfe90-0xfe9f,0xfd00-0xfd7f irq 16 at device 0.0 on pci1 ib_mthca: Mellanox InfiniBand HCA driver v1.0-ofed1.5.2 (August 4, 2010) Two cards connected via cable, no Infiniband switch 2) Kernel config: include GENERIC options OFED options SDP device ipoib options IPOIB_CM device mthca 3) Regardles of MTU settings (tried 16000, 32000, 48000), actual packed size in tcp flow is about 16000. Have not investigated it in details 4) There is no packet loss: lexa@new-gw:/home/lexa# ping -s 32000 -c 1 -f 10.1.1.1 PING 10.1.1.1 (10.1.1.1): 32000 data bytes . --- 10.1.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.157/0.225/1.758/0.156 ms -- Alex Tutubalin Web: http://blog.lexa.ru mailto:l...@lexa.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
