[no subject]
Hi, As a heads up, it appears that some sysctl output is broken on CURRENT... please see this bug for more details: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192544 . Thank you! -Garrett ___ 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:
On 08/10/14 08:05, Garrett Cooper wrote: Hi, As a heads up, it appears that some sysctl output is broken on CURRENT... please see this bug for more details: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192544 . Thank you! -Garrett Hi, Should be fixed now. This is a bug in the network driver code and not my sysctl patch! Thank you! --HPS ___ 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: uefi boot on Apple Mac
If you're interested, you can try out the following ISO: https://www.dropbox.com/s/srbunx0agrokcs3/freebsd-current-uefi-bios-amd64.iso The image was built on Friday 8th of August for the amd64 platform. I tested out the EFI part on VirtualBox (UEFI 2.X) and my MacBook Pro 17 inch from 2011 (EFI 1.10), and as far as EFI goes, I successfully booted the image on both my Mac and VirtualBox (however, booting the image from BIOS using my Mac was a different story). So, as I said, as far as (U)EFI goes, the image should work on UEFI 2.X based PC's and EFI 1.10 based Macs. On 12/07/14 19:22, Nathan Whitehorn wrote: I'd point out that, as of last week, the standard -CURRENT ISOs (and generate-release.sh script) make EFI-bootable media by default. All the snapshots should have this done already, for instance. -Nathan I wasn't aware of that, but thanks for the info. :) On 07/12/14 03:09, Anders Bolt-Evensen wrote: I also got a message like that when I booted from a USB stick on a MacBookPro8,3 (17 inch, late 2011). I fixed it by creating a custom ISO image and burned that onto a DVD using an external DVD drive. The UEFI installer boots fine from this external DVD drive. Here is how I did it: Genereste an ISO with the FreeBSD-CURRENT kernel, mount the ISO and copy all files from the root directory in the ISO and unmount cd /usr/src/release sh ./generate-release.sh # You may have to run “make buildworld” and be connected to the internet to install required ports. mount -t cd9660 /scratch/R/release/FreeBSD-something-disc1.iso /mnt mkdir freebsd_generic_installer #Files copied to the directory in the next command will be copied to a new ISO in step 3 cp -R /mnt/ freebsd_generic_installer/ umount /mnt 2. Create a FAT filesystem image and place the loader in it in the default path that UEFI will look for (the following steps are copied from https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI): dd if=/dev/zero of=efiboot.img bs=4k count=100 mdconfig -a -t vnode -f efiboot.img newfs_msdos -F 12 -m 0xf8 /dev/md0 mount -t msdosfs /dev/md0 /mnt mkdir -p /mnt/efi/boot cp loader.efi /mnt/efi/boot/bootx64.efi umount /mnt mdconfig -d -u 0 3. Create the custom ISO image. Please make sure that the entry in freebsd_generic_installer/etc/fstab matches the label you choose in the command below. makefs -t cd9660 -o bootimage='i386;efiboot.img' -o no-emul-boot -o rockridge -o label=“FREEBSD_UEFI_INSTALL -o publisher=test uefi-test.iso freebsd_generic_installer/ To get the example in the command above to work, please make sure that the entry in freebsd_generic_installer/etc/fstab reads /dev/iso9660/FREEBSD_UEFI_INSTALL/cd9660ro0 0 4. Burn the image to DVD, reboot your system and choose “EFI Boot”. Note that unless you are using a EFI console like rEFIt or rEFInd, you may have to kind of wait a couple of minutes while the kernel is loading before anything appears on the screen. On 04/07/14 16:34, Huang Wen Hui wrote: Hi, On my MacbookPro11,3, I got this error message: http://sw.gddsn.org.cn/freebsd/uefi.jpg cheers, Huang WenHui 2014-07-04 22:13 GMT+08:00 Ed Maste ema...@freebsd.org: On 24 May 2014 19:39, Rafael Espíndola rafael.espind...@gmail.com wrote: Yes, I got that in the mac laptops I tried, it worked on a Mac Pro. It might be the frame buffer corruption that Ed Maste was mentioning. I purchased a new MacBook Air yesterday (model identifier MacBookAir6,2). UEFI boot and vt(4) worked correctly. (My image included Rafael's patch; I haven't tried a boot without.) I also committed a change to display the framebuffer parameters (address, dimensions, etc.) on boot, in order to help identify the source of this issue. If you have a moment can you build a new USB stick image and give it a try? -Ed ___ 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 ___ 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 ___ 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: No bootable device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/09/2014 10:32, Mehmet Erol Sanliturk wrote: the installed systems are not bootable , and the last sentence on the screen is the following : No bootable device -- insert boot disk and press any key If you installed into GPT partitions like this: $ gpart show ada0 = 34 488397101 ada0 GPT (233G) 34 1038 1 freebsd-boot (519K) 1072 455081984 2 freebsd-ufs (217G) 455083056 33314079 3 freebsd-swap (16G) Try to make GPT in MBR as bootable (active) partition: $ fdisk -s /dev/ada0 /dev/ada0: 484521 cyl 16 hd 63 sec PartStartSize Type Flags 1: 1 488397167 0xee 0x80 $ fdisk -p /dev/ada0 # /dev/ada0 g c484521 h16 s63 p 1 0xee 1 488397167 a 1 This is an known issue on HP laptops. Eric -BEGIN PGP SIGNATURE- Version: GnuPG v2 iF4EAREIAAYFAlPn9uUACgkQSfBQu3oOwYwdtgD9ENIhnJ0Tp6KxJkzz0BbohaDB 2XCkL7za/CiQY6RruvUBAI7cnMucMKcTJCSQF+pHcyljemm+eF2ZtGd70Loh6a86 =aA2H -END PGP SIGNATURE- ___ 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: No bootable device
On Sun, 10 Aug 2014, Eric L. Camachat wrote: /usr/local/libexec/ppf_verify: pgp command failed gpg: Signature made Sun Aug 10 16:49:09 2014 MDT gpg:using DSA key 0x49F050BB7A0EC18C gpg: Can't check signature: No public key -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/09/2014 10:32, Mehmet Erol Sanliturk wrote: the installed systems are not bootable , and the last sentence on the screen is the following : No bootable device -- insert boot disk and press any key If you installed into GPT partitions like this: $ gpart show ada0 = 34 488397101 ada0 GPT (233G) 34 1038 1 freebsd-boot (519K) 1072 455081984 2 freebsd-ufs (217G) 455083056 33314079 3 freebsd-swap (16G) Try to make GPT in MBR as bootable (active) partition: $ fdisk -s /dev/ada0 /dev/ada0: 484521 cyl 16 hd 63 sec PartStartSize Type Flags 1: 1 488397167 0xee 0x80 $ fdisk -p /dev/ada0 # /dev/ada0 g c484521 h16 s63 p 1 0xee 1 488397167 a 1 This is an known issue on HP laptops. The simpler version is gpart set -a active ada0 There are multiple possible issues. This one is due to strict compliance with the GPT standard. Another problem is when a BIOS system does weird things based on an MBR partition type. Some Lenovo systems do that. When that is the problem, using MBR partitioning rather than the PMBR from GPT can work. ___ 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
No bootable device
( This is the resend of http://lists.freebsd.org/pipermail/freebsd-current/2014-August/051617.html with additions . ) Dears All , When FreeBSD 9.1 amd64 Stable ( 2013-04-28 , r 250 009 , .iso ) , FreeBSD 9.2 amd64 Release ( .iso ) are installed with following steps , they are producing bootable and very well working systems : Install Partitioning : Guided , Partition : Entire disk Partition Editor : Finish Confirmation : Commit Final Configuration : Exit Manual Configuration : No Complete : Reboot When the same steps applied to the following installs on the SAME computer and HDD - : FreeBSD 9.3 amd64 Release ( .iso ) , FreeBSD 10.0 amd64 Release ( .iso ) , - FreeBSD 10.0 amd64 Stable ( 2014-06-30 , r 268 038 , .iso ) , FreeBSD 10.0 amd64 Stable ( 2014-07-12 , r 268 571 , .iso ) , FreeBSD 11.0 amd64 Current ( 2014-08-04 , r 269 497 , Disk 1 , iso ) , the installed systems are not bootable , and the last sentence on the screen is the following : No bootable device -- insert boot disk and press any key . I have applied the following steps to make the FreeBSD 10.0 amd64 Release installation bootable : I have booted the computer by the Release DVD , from the Install Shell LiveCD , I have selected Shell , and entered gpart set -a active ada0 reboot with respect to advise giving in http://lists.freebsd.org/pipermail/freebsd-current/2014-August/051623.html by Warren Block . The installed system booted successfully from the HDD . Thank you very much . Mehmet Erol Sanliturk ___ 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
Child suspend/resume
Hi all,
The attached patch is completely untested, due to lack of existing
suspendable hardware (no x86 machines). It does compile cleanly against
head, though. I don't think it should change any behavior, I tried to
keep the essence of the code path the same.
It was suggested that I break up my multipass suspend/resume code into
incremental parts, so this is part one. It adds a
BUS_SUSPEND_CHILD/BUS_RESUME_CHILD, as well as helper functions,
bus_generic_suspend_child()/bus_generic_resume_child(), and modifies
the PCI driver to use this new facility.
I'd like some feedback, and testing of this, to make sure I didn't
break anything.
Thanks,
JustinIndex: sys/kern/bus_if.m
===
--- sys/kern/bus_if.m (revision 269798)
+++ sys/kern/bus_if.m (working copy)
@@ -670,3 +670,25 @@
device_t _child;
u_int _irq;
} DEFAULT null_remap_intr;
+
+/**
+ * @brief Suspend a given child
+ *
+ * @param _dev the parent device of @p _child
+ * @param _child the device to suspend
+ */
+METHOD int suspend_child {
+ device_t _dev;
+ device_t _child;
+} DEFAULT bus_generic_suspend_child;
+
+/**
+ * @brief Resume a given child
+ *
+ * @param _dev the parent device of @p _child
+ * @param _child the device to resume
+ */
+METHOD int resume_child {
+ device_t _dev;
+ device_t _child;
+} DEFAULT bus_generic_suspend_child;
Index: sys/kern/subr_bus.c
===
--- sys/kern/subr_bus.c (revision 269798)
+++ sys/kern/subr_bus.c (working copy)
@@ -135,6 +135,7 @@
#define DF_DONENOMATCH 0x20 /* don't execute DEVICE_NOMATCH again */
#define DF_EXTERNALSOFTC 0x40 /* softc not allocated by us */
#define DF_REBID 0x80 /* Can rebid after attach */
+#define DF_SUSPENDED 0x100 /* Device is suspended. */
u_int order; /** order from device_add_child_ordered() */
void *ivars; /** instance variables */
void *softc; /** current driver's variables */
@@ -3631,6 +3632,37 @@
}
/**
+ * @brief Default function for suspending a child device.
+ *
+ * This function is to be used by a bus's DEVICE_SUSPEND_CHILD().
+ */
+int
+bus_generic_suspend_child(device_t dev, device_t child)
+{
+ int error;
+
+ error = DEVICE_SUSPEND(child);
+
+ if (error == 0)
+ dev-flags |= DF_SUSPENDED;
+ return (error);
+}
+
+/**
+ * @brief Default function for resuming a child device.
+ *
+ * This function is to be used by a bus's DEVICE_RESUME_CHILD().
+ */
+int
+bus_generic_resume_child(device_t dev, device_t child)
+{
+ DEVICE_RESUME(child);
+
+ dev-flags = ~DF_SUSPENDED;
+ return (0);
+}
+
+/**
* @brief Helper function for implementing DEVICE_SUSPEND()
*
* This function can be used to help implement the DEVICE_SUSPEND()
@@ -3646,12 +3678,12 @@
device_t child, child2;
TAILQ_FOREACH(child, dev-children, link) {
- error = DEVICE_SUSPEND(child);
+ error = BUS_SUSPEND_CHILD(dev, child);
if (error) {
for (child2 = TAILQ_FIRST(dev-children);
child2 child2 != child;
child2 = TAILQ_NEXT(child2, link))
-DEVICE_RESUME(child2);
+BUS_RESUME_CHILD(dev, child2);
return (error);
}
}
@@ -3670,7 +3702,7 @@
device_t child;
TAILQ_FOREACH(child, dev-children, link) {
- DEVICE_RESUME(child);
+ BUS_RESUME_CHILD(dev, child);
/* if resume fails, there's nothing we can usefully do... */
}
return (0);
Index: sys/dev/pci/pci.c
===
--- sys/dev/pci/pci.c (revision 269798)
+++ sys/dev/pci/pci.c (working copy)
@@ -162,6 +162,8 @@
DEVMETHOD(bus_child_pnpinfo_str, pci_child_pnpinfo_str_method),
DEVMETHOD(bus_child_location_str, pci_child_location_str_method),
DEVMETHOD(bus_remap_intr, pci_remap_intr_method),
+ DEVMETHOD(bus_suspend_child, pci_suspend_child),
+ DEVMETHOD(bus_resume_child, pci_resume_child),
/* PCI interface */
DEVMETHOD(pci_read_config, pci_read_config_method),
@@ -3614,12 +3616,11 @@
#endif
static void
-pci_set_power_children(device_t dev, device_t *devlist, int numdevs,
-int state)
+pci_set_power_child(device_t dev, device_t child, int state)
{
- device_t child, pcib;
struct pci_devinfo *dinfo;
- int dstate, i;
+ device_t pcib;
+ int dstate;
/*
* Set the device to the given state. If the firmware suggests
@@ -3629,74 +3630,74 @@
* are handled separately.
*/
pcib = device_get_parent(dev);
- for (i = 0; i numdevs; i++) {
- child = devlist[i];
- dinfo = device_get_ivars(child);
- dstate = state;
- if (device_is_attached(child)
- PCIB_POWER_FOR_SLEEP(pcib, dev, dstate) == 0)
- pci_set_powerstate(child, dstate);
- }
+ dinfo = device_get_ivars(child);
+ dstate = state;
+ if (device_is_attached(child)
+ PCIB_POWER_FOR_SLEEP(pcib, dev, dstate) == 0)
+ pci_set_powerstate(child, dstate);
}
int
-pci_suspend(device_t dev)
+pci_suspend_child(device_t dev, device_t child)
{
- device_t child, *devlist;
struct pci_devinfo *dinfo;
- int error, i, numdevs;
+ int
