Re: ath0 no longer attaches, cardbus problems?
On 3 September 2011 12:35, Eitan Adler li...@eitanadler.com wrote: The best way to do this is to find a known working version of the kernel and then bisect the version from the known bad and known good versions until you arrive at the breaking commit. It is easier if you look at the svn log to see which commits might matter. Yes this takes a while, but is the surest way to find the regression. You shouldn't have to try many kernels. 130,000 revisions, only a max of 18 attempts needed. :) No, you don't need a whole buildworld. Just try booting the kernel and see when it attaches. Thanks, Adrian ___ 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: ichwd0: unable to reserve GCS registers
on 03/08/2011 01:06 John Baldwin said the following:
On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
on 19/07/2011 18:16 John Baldwin said the following:
Hmm, can you get devinfo -r output from a working kernel with ichwd loaded?
You might be able to just build the kernel with 'nooptions NEW_PCIB'.
I believe that I've got a similar problem with amdsbwd(4).
It needs some resources (I/O ports) that belong to ACPI.
The problem is that the driver attaches to isa bus which is under
isab-pci-pcib and those particular resources are not assigned to the
Host-PCI
bridge.
I think that you already made a suggestion that perhaps isa bus should
directly
attach to acpi bus when acpi is available. Not sure if there are any
alternative approaches.
Can you try this:
Sorry for taking so long to reply to this.
The patch does help me with the amdsbwd watchdog driver!
I tested the patch on top of r225331.
If you would like any additional information please let me know.
--- //depot/projects/pci/sys/dev/acpica/acpi.c2011-06-25
12:05:19.0
+++ //depot/projects/pci/sys/dev/acpica/acpi.c2011-08-02
20:21:42.0
@@ -1238,7 +1238,6 @@
struct resource_list_entry *rle;
struct resource_list *rl;
struct resource *res;
-struct rman *rm;
int isdefault = (start == 0UL end == ~0UL);
/*
@@ -1291,15 +1290,29 @@
} else
res = BUS_ALLOC_RESOURCE(device_get_parent(bus), child, type, rid,
start, end, count, flags);
-if (res != NULL || start + count - 1 != end)
- return (res);
/*
* If the first attempt failed and this is an allocation of a
* specific range, try to satisfy the request via a suballocation
- * from our system resource regions. Note that we only handle
- * memory and I/O port system resources.
+ * from our system resource regions.
*/
+if (res == NULL start + count - 1 == end)
+ res = acpi_alloc_sysres(child, type, rid, start, end, count, flags);
+return (res);
+}
+
+/*
+ * Attempt to allocate a specific resource range from the system
+ * resource ranges. Note that we only handle memory and I/O port
+ * system resources.
+ */
+struct resource *
+acpi_alloc_sysres(device_t child, int type, int *rid, u_long start, u_long
end,
+u_long count, u_int flags)
+{
+struct rman *rm;
+struct resource *res;
+
switch (type) {
case SYS_RES_IOPORT:
rm = acpi_rman_io;
@@ -1311,6 +1324,7 @@
return (NULL);
}
+KASSERT(start + count - 1 == end, (wildcard resource range));
res = rman_reserve_resource(rm, start, end, count, flags ~RF_ACTIVE,
child);
if (res == NULL)
--- //depot/projects/pci/sys/dev/acpica/acpi_pcib_acpi.c 2011-07-22
18:19:55.0
+++ //depot/projects/pci/sys/dev/acpica/acpi_pcib_acpi.c 2011-08-02
20:21:42.0
@@ -541,6 +541,7 @@
{
#ifdef NEW_PCIB
struct acpi_hpcib_softc *sc;
+struct resource *res;
#endif
#if defined(__i386__) || defined(__amd64__)
@@ -549,8 +550,11 @@
#ifdef NEW_PCIB
sc = device_get_softc(dev);
-return (pcib_host_res_alloc(sc-ap_host_res, child, type, rid, start,
end,
- count, flags));
+res = pcib_host_res_alloc(sc-ap_host_res, child, type, rid, start, end,
+ count, flags);
+if (res == NULL start + count - 1 == end)
+ res = acpi_alloc_sysres(child, type, rid, start, end, count, flags);
+return (res);
#else
return (bus_generic_alloc_resource(dev, child, type, rid, start, end,
count, flags));
--- //depot/projects/pci/sys/dev/acpica/acpivar.h 2011-06-22
16:25:39.0
+++ //depot/projects/pci/sys/dev/acpica/acpivar.h 2011-08-02
20:21:42.0
@@ -382,6 +382,8 @@
struct resource *res, ACPI_RESOURCE *acpi_res);
ACPI_STATUS acpi_parse_resources(device_t dev, ACPI_HANDLE handle,
struct acpi_parse_resource_set *set, void *arg);
+struct resource *acpi_alloc_sysres(device_t child, int type, int *rid,
+ u_long start, u_long end, u_long count, u_int flags);
/* ACPI event handling */
UINT32 acpi_event_power_button_sleep(void *context);
--
Andriy Gapon
___
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: ath0 no longer attaches, cardbus problems?
On Sep 3, 2011, at 2:02 AM, Adrian Chadd adr...@freebsd.org wrote: On 3 September 2011 12:35, Eitan Adler li...@eitanadler.com wrote: The best way to do this is to find a known working version of the kernel and then bisect the version from the known bad and known good versions until you arrive at the breaking commit. It is easier if you look at the svn log to see which commits might matter. Yes this takes a while, but is the surest way to find the regression. You shouldn't have to try many kernels. 130,000 revisions, only a max of 18 attempts needed. :) No, you don't need a whole buildworld. Just try booting the kernel and see when it attaches. There's a reason I haven't upgraded this system in over a year. It takes a long time to update the src tree and a long time to build a kernel. I miss the 2.x/3.x days where you could build world on system like this in about an hour or so. -- DE___ 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
Compiling BETA2 with clang fails
Hi all. === libexec/bootpd (all) /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/bootpd.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/dovend.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/readfile.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/hash.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/dumptab.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/lookup.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/getif.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/hwaddr.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/report.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/tzone.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/bootpd/rtmsg.c /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -o bootpd bootpd.o dovend.o readfile.o hash.o dumptab.o lookup.o getif.o hwaddr.o report.o tzone.o rtmsg.o /usr/obj/usr/src/tmp/usr/lib/crt1.o: In function `_start1': /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0x94): undefined reference to `atexit' /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0x9d): undefined reference to `_init_tls' /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0xad): undefined reference to `atexit' /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0xd6): undefined reference to `exit' bootpd.o: In function `main': /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x31): undefined reference to `strrchr' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0xa2): undefined reference to `malloc' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0xe0): undefined reference to `exit' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x12a): undefined reference to `__error' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x150): undefined reference to `getsockname' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x1c7): undefined reference to `gethostname' bootpd.o: In function `.LBB0_31': /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x385): undefined reference to `sscanf' bootpd.o: In function `.LBB0_42':
Re: Compiling BETA2 with clang fails
On 2011-09-03 22:22, Volodymyr Kostyrko wrote: Hi all. === libexec/bootpd (all) ... /usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC -march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99 -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -o bootpd bootpd.o dovend.o readfile.o hash.o dumptab.o lookup.o getif.o hwaddr.o report.o tzone.o rtmsg.o /usr/obj/usr/src/tmp/usr/lib/crt1.o: In function `_start1': /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0x94): undefined reference to `atexit' /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0x9d): undefined reference to `_init_tls' /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0xad): undefined reference to `atexit' /usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0xd6): undefined reference to `exit' bootpd.o: In function `main': /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x31): undefined reference to `strrchr' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0xa2): undefined reference to `malloc' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0xe0): undefined reference to `exit' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x12a): undefined reference to `__error' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x150): undefined reference to `getsockname' /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x1c7): undefined reference to `gethostname' bootpd.o: In function `.LBB0_31': /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x385): undefined reference to `sscanf' bootpd.o: In function `.LBB0_42': /var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x44d): undefined reference to `sscanf' bootpd.o: In function `.LBB0_55': There may be some problems integrating clang into Makefiles, because if I cd to /usr/src/libexec/bootpd and run make there everything works fine. Please post your make.conf/src.conf, and any other environmental settings which may influence the build. For starters, does it still fail if you remove ccache and the non-standard CFLAGS? ___ 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: Compiling BETA2 with clang fails
03.09.2011 23:43, Dimitry Andric написав(ла):
On 2011-09-03 22:22, Volodymyr Kostyrko wrote:
Hi all.
=== libexec/bootpd (all)
...
/usr/local/libexec/ccache/world/clang -O2 -pipe -Qunused-arguments -fPIC
-march=native -DETC_ETHERS -DSYSLOG -DDEBUG -DVEND_CMU -std=gnu99
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k
-Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args
-o bootpd bootpd.o dovend.o readfile.o hash.o dumptab.o lookup.o getif.o
hwaddr.o report.o tzone.o rtmsg.o
/usr/obj/usr/src/tmp/usr/lib/crt1.o: In function `_start1':
/usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0x94): undefined reference to
`atexit'
/usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0x9d): undefined reference to
`_init_tls'
/usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0xad): undefined reference to
`atexit'
/usr/src/lib/csu/i386-elf/crt1_c.c:(.text+0xd6): undefined reference to
`exit'
bootpd.o: In function `main':
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x31): undefined
reference to `strrchr'
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0xa2): undefined
reference to `malloc'
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0xe0): undefined
reference to `exit'
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x12a): undefined
reference to `__error'
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x150): undefined
reference to `getsockname'
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x1c7): undefined
reference to `gethostname'
bootpd.o: In function `.LBB0_31':
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x385): undefined
reference to `sscanf'
bootpd.o: In function `.LBB0_42':
/var/db/ccache/tmp/bootpd.tmp.limbo.lan.76586.i:(.text+0x44d): undefined
reference to `sscanf'
bootpd.o: In function `.LBB0_55':
There may be some problems integrating clang into Makefiles, because if
I cd to /usr/src/libexec/bootpd and run make there everything works fine.
Please post your make.conf/src.conf, and any other environmental
settings which may influence the build. For starters, does it still
fail if you remove ccache and the non-standard CFLAGS?
Yes it does. It's still not the clean tree so I'll try to retest without
ccache.
I don't think ccache is really involved because as I said before when I
issue the same command from /usr/obj/usr/src/libexec/bootpd it succeeds.
/etc/make.conf follows:
CPUTYPE?=native
INSTALL:=install -C
WITHOUT_NOUVEAU:=yes
KERNCONF?=MINIMAL #GENERIC
NO_CLEAN:=yes
.if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*))
. if !defined(NOCCACHE)
# GCC 4.2
#CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/cc,1}
#CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/c++,1}
# clang
CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/clang,1}
CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/clang++,1}
CPP:=${CXX:C,^cpp,/usr/local/libexec/ccache/world/clang -E,1}
# clang without ccache
#CC:=${CC:C,^cc,clang,1}
#CXX:=${CXX:C,^c\+\+,clang++,1}
#CPP:=${CXX:C,^cpp,clang -E,1}
# Don't die on warnings
NO_WERROR=
WERROR=
# Don't forget this when using Jails!
NO_FSCHG=
. endif
.else
. if (empty(.CURDIR:M*/java/openjdk6*)
empty(.CURDIR:M*/java/openjdk7*) empty(.CURDIR:M*-kmod*)
empty(.CURDIR:M*/java/jdk16*))
#CFLAGS+= -mfpmath=sse,387
#COPTFLAGS+= -mfpmath=sse,387
. endif
.endif
WRKDIRPREFIX=/tmp/ports
DISABLE_MAKE_JOBS=true
.if ${CC:T} == clang
CFLAGS+= -Qunused-arguments -fPIC
.endif
--
Sphinx of black quartz judge my vow.
___
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
Need a README to explain items in download directory
Hi, As a new user, wanting to download FreeBSD, and maybe not wanting to read everything on the web site, I would go through these steps: (1) Go to http://www.freebsd.org/ (2) See Get FreeBSD now, click on it. (3) Skim through a lot of text on that page, which is very wordy (we can probably streamline this page) (4) Notice that there is a section: Download FreeBSD (5) Click on the ISO link Once I click on that link, I see a directory with files. For example, at ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.2/ I see: CHECKSUM.MD5 CHECKSUM.SHA256 FreeBSD-8.2-RELEASE-i386-bootonly.iso FreeBSD-8.2-RELEASE-i386-disc1.iso FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz FreeBSD-8.2-RELEASE-i386-livefs.iso FreeBSD-8.2-RELEASE-i386-memstick.img It is not clear to me which of these files I need. Do I need all of them, or just some of them? What do these files do? Can we have a README.txt file in this directory with a concise description of these files? For starters, having one line description per file would be useful: FreeBSD-8.2-RELEASE-i386-bootonly.iso - Initial boot, fits on CD, requires disc 1 FreeBSD-8.2-RELEASE-i386-disc1.iso- Installer, fits on CD, requires bootonly FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz- Complete installer, fits on DVD FreeBSD-8.2-RELEASE-i386-livefs.iso- Live file system, boot and run off of CD/DVD, used for recovery FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick I don't even know if what I listed above is correctI am just guessing. -- Craig Rodrigues rodr...@crodrigues.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: Compiling BETA2 with clang fails
On 2011-09-03 22:58, Volodymyr Kostyrko wrote:
03.09.2011 23:43, Dimitry Andric ???(??):
On 2011-09-03 22:22, Volodymyr Kostyrko wrote:
...
.if ${CC:T} == clang
CFLAGS+= -Qunused-arguments -fPIC
.endif
You should not unconditionally add -fPIC. Remove it, and try again.
(The -Qunused-arguments is fine, btw.)
___
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: Need a README to explain items in download directory
On 9/3/2011 5:11 PM, Craig Rodrigues wrote: FreeBSD-8.2-RELEASE-i386-bootonly.iso - Initial boot, fits on CD, requires disc 1 FreeBSD-8.2-RELEASE-i386-disc1.iso- Installer, fits on CD, requires bootonly FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz- Complete installer, fits on DVD FreeBSD-8.2-RELEASE-i386-livefs.iso- Live file system, boot and run off of CD/DVD, used for recovery FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick Your on the right track, lets be a little more verbose/correct 1. FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection 2. FreeBSD-8.2-RELEASE-i386-disc1.iso - Full Installer, includes all files to install base. 3. FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz - DID-sized image, includes Base+Packages (not entire collection) 4. FreeBSD-8.2-RELEASE-i386-livefs.iso - Live file system, boot and run off of CD/DVD, used for recovery # Good Enough 5. FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick # Same as above That wordy page you skimmed over, I believe it explains what these all do. It's great that your interested in FreeBSD, but keep in mind, FreeBSD isn't for the lighthearted or impatient and reading is a necessity. The handbook is almost required reading, it will answer almost all of your very basic questions. -- Chris Brennan -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) signature.asc Description: OpenPGP digital signature
Re: Need a README to explain items in download directory
On Sat, Sep 3, 2011 at 2:21 PM, Chris Brennan xa...@xaerolimit.net wrote: On 9/3/2011 5:11 PM, Craig Rodrigues wrote: FreeBSD-8.2-RELEASE-i386-bootonly.iso - Initial boot, fits on CD, requires disc 1 FreeBSD-8.2-RELEASE-i386-disc1.iso - Installer, fits on CD, requires bootonly FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz - Complete installer, fits on DVD FreeBSD-8.2-RELEASE-i386-livefs.iso - Live file system, boot and run off of CD/DVD, used for recovery FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick Your on the right track, lets be a little more verbose/correct 1. FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection 2. FreeBSD-8.2-RELEASE-i386-disc1.iso - Full Installer, includes all files to install base. 3. FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz - DID-sized image, includes Base+Packages (not entire collection) 4. FreeBSD-8.2-RELEASE-i386-livefs.iso - Live file system, boot and run off of CD/DVD, used for recovery # Good Enough 5. FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick # Same as above That wordy page you skimmed over, I believe it explains what these all do. It's great that your interested in FreeBSD, but keep in mind, FreeBSD isn't for the lighthearted or impatient and reading is a necessity. The handbook is almost required reading, it will answer almost all of your very basic questions. I agree, but it probably should be simplified in the downloads page, using the following categories, instead of using a README file: 1. LiveCD 2. DVD 3. USB http://fedoraproject.org/get-fedora might be a good start for what to write, as well as http://www.ubuntu.com/download (the Ubuntu site is incredibly user friendly -- I would choose that over the Fedora site). Thanks! -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: Need a README to explain items in download directory
Hi, We need to have a small README in the ftp directory, *and* we need to streamline the downloads web page. Some people go directly to ftp://ftp.FreeBSD.org/ to get at the download media without reading the web page, so the small README in the ftp directory is still useful. Agree with you totally about the user friendliness of the ubuntu download page. I don't have enough web skills to contribute in that area to make our page better. -- Craig Rodrigues rodr...@crodrigues.org On Sat, Sep 3, 2011 at 3:36 PM, Garrett Cooper yaneg...@gmail.com wrote: On Sat, Sep 3, 2011 at 2:21 PM, Chris Brennan xa...@xaerolimit.net wrote: On 9/3/2011 5:11 PM, Craig Rodrigues wrote: FreeBSD-8.2-RELEASE-i386-bootonly.iso - Initial boot, fits on CD, requires disc 1 FreeBSD-8.2-RELEASE-i386-disc1.iso - Installer, fits on CD, requires bootonly FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz - Complete installer, fits on DVD FreeBSD-8.2-RELEASE-i386-livefs.iso - Live file system, boot and run off of CD/DVD, used for recovery FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick Your on the right track, lets be a little more verbose/correct 1. FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection 2. FreeBSD-8.2-RELEASE-i386-disc1.iso - Full Installer, includes all files to install base. 3. FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz - DID-sized image, includes Base+Packages (not entire collection) 4. FreeBSD-8.2-RELEASE-i386-livefs.iso - Live file system, boot and run off of CD/DVD, used for recovery # Good Enough 5. FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick # Same as above That wordy page you skimmed over, I believe it explains what these all do. It's great that your interested in FreeBSD, but keep in mind, FreeBSD isn't for the lighthearted or impatient and reading is a necessity. The handbook is almost required reading, it will answer almost all of your very basic questions. I agree, but it probably should be simplified in the downloads page, using the following categories, instead of using a README file: 1. LiveCD 2. DVD 3. USB http://fedoraproject.org/get-fedora might be a good start for what to write, as well as http://www.ubuntu.com/download (the Ubuntu site is incredibly user friendly -- I would choose that over the Fedora site). Thanks! -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 ___ 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: Need a README to explain items in download directory
Hi, Thanks. Your text is better than mine, and I actually learned something from it. :) For this line: (1) FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection Does this mean that this ISO has the minimal stuff to boot, and then do an install by downloading packages over the Internet? I really don't know, that's why I'm asking. :) Do you understand enough of the release makefiles under src/release/ to propose a patch to include your README? I am not up to speed on how the release scripts figure out what files to copy to the ftp directory. BTW, I am a FreeBSD src committer, and am working on adding a section to the FreeBSD handbook, so I am quite familiar with those things. :) I am just trying to propose minor ideas to make it easier for new users to figure out how to download and install FreeBSD. :) -- Craig Rodrigues rodr...@crodrigues.org On Sat, Sep 3, 2011 at 2:21 PM, Chris Brennan xa...@xaerolimit.net wrote: Your on the right track, lets be a little more verbose/correct 1. FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection 2. FreeBSD-8.2-RELEASE-i386-disc1.iso - Full Installer, includes all files to install base. 3. FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz - DID-sized image, includes Base+Packages (not entire collection) 4. FreeBSD-8.2-RELEASE-i386-livefs.iso - Live file system, boot and run off of CD/DVD, used for recovery # Good Enough 5. FreeBSD-8.2-RELEASE-i386-memstick.img - Installer for USB memory stick # Same as above That wordy page you skimmed over, I believe it explains what these all do. It's great that your interested in FreeBSD, but keep in mind, FreeBSD isn't for the lighthearted or impatient and reading is a necessity. The handbook is almost required reading, it will answer almost all of your very basic questions. -- Chris Brennan -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) ___ 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: Need a README to explain items in download directory
On 9/3/2011 6:36 PM, Garrett Cooper wrote: http://fedoraproject.org/get-fedora might be a good start for what to write, as well as http://www.ubuntu.com/download (the Ubuntu site is incredibly user friendly -- I would choose that over the Fedora site). Thanks! -Garrett Personally, I wouldn't choose either of these, but that's just a preference, I like neither of them as a project. FreeBSD, Debian or Gentoo would be my choices. -- Chris Brennan -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) signature.asc Description: OpenPGP digital signature
Re: Need a README to explain items in download directory
On Sat, Sep 3, 2011 at 6:00 PM, Craig Rodrigues rodr...@crodrigues.orgwrote: For this line: (1) FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection Does this mean that this ISO has the minimal stuff to boot, and then do an install by downloading packages over the Internet? I really don't know, that's why I'm asking. :) While such wording may be helpful to a new user over completely absent directions, it's technically flawed. You don't need an internet connection, but rather a network connection or some other form of installation media. /nitpick -- Adam Vande More ___ 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: ath0 no longer attaches, cardbus problems?
On 3 September 2011 22:32, Daniel Eischen eisc...@vigrid.com wrote: No, you don't need a whole buildworld. Just try booting the kernel and see when it attaches. There's a reason I haven't upgraded this system in over a year. It takes a long time to update the src tree and a long time to build a kernel. I miss the 2.x/3.x days where you could build world on system like this in about an hour or so. Just build a kernel on a fast system and boot it? You don't have to boot a full buildworld+modules to see whether ath0 attaches. Adrian ___ 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: ath0 no longer attaches, cardbus problems?
Hi, If : (1) your laptop has an Ethernet jack (2) your laptop supports booting over the network via PXE (3) you have another fast machine, where you can NFS export a directory which has the output of make buildkernel / make buildworld. then you can: (1) compile the kernel on the fast machine (2) NFS export the directory with the kernel (3) try to network boot your laptop with that kernel over Ethernet, without installing FreeBSD on your laptop. I am in the middle of writing this document for contribution to the FreeBSD Handbook: http://people.freebsd.org/~rodrigc/doc/doc/en_US.ISO8859-1/books/handbook/network-pxe-nfs.html which describes how to do that. -- Craig Rodrigues rodr...@crodrigues.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: Need a README to explain items in download directory
On 9/3/2011 7:12 PM, Adam Vande More wrote: On Sat, Sep 3, 2011 at 6:00 PM, Craig Rodrigues rodr...@crodrigues.org mailto:rodr...@crodrigues.org wrote: For this line: (1) FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet Connection Does this mean that this ISO has the minimal stuff to boot, and then do an install by downloading packages over the Internet? I really don't know, that's why I'm asking. :) What this should have said was that it is a *boot-to-installer* only ISO image, designed to be burned to optical media. A *network* connection is required (LAN/WAN depending on where you will be installing from) *or* you will have to provide a 'local source[1]' for the install to pull BASE packages from. [1] Local source can be an NFS mounted partition, local hard-drive with the base packages, etc... where-ever the BASE install files are located. While such wording may be helpful to a new user over completely absent directions, it's technically flawed. You don't need an internet connection, but rather a network connection or some other form of installation media. You are correct Adam. I was a little too basic. If such a README is to be implemented, I could find myself writing some correct descriptions ... perhaps a pr is in order? -- Chris Brennan -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) signature.asc Description: OpenPGP digital signature
