Re: RTL8125: wont stay up
On 20/08/2024 04:14, Larry Rosenman wrote: shows up, doesn't ping -- ifconfig up brings it back for ~4 packets ifconfig_re0="DHCP" ifconfig_re0_ipv6="inet6 accept_rtadv" ipv6_activate_all_interfaces="AUTO" rtsold_enable="YES" 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as well. Ideas You might try disabling checksum offload and report the result: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275882#c44 -- Alex Dupre
Re: Removing fdisk and bsdlabel (legacy partition tools)
Ed Maste wrote: > I would like to disconnect these from the build, and subsequently > remove them. I'm in favour of this change. Having different tools (some modern and updated, others deprecated and limited) in base to do the same task can confuse the users. If possible move them to ports for people still using them, with a clear deprecation warning. -- Alex Dupre
Re: Proposal: Disable compression of newsyslog by default
Xin Li wrote: > Inspired by D42961, I propose that we move forward with disabling the > compression by default in newsyslog, as implemented in > https://reviews.freebsd.org/D43169 I like the possibility to entirely disable compression on log files, or to select a specific compression algorithm, but I don't think we should disable compression by default because there is a filesystem that supports compression. -- Alex Dupre
Re: [HEADSUP] making /bin/sh the default shell for root
+100 for keeping this behavior on default config ;-) On 22/09/21 15:00, Renato Botelho wrote: > +1 for keeping this behavior on default config > > On 22/09/21 06:19, Daniel Morante via freebsd-current wrote: >> Will history/completion continue to work the same way? (for example >> typing part of the command, pressing UP and having it complete based >> on history) -- Alex Dupre
Re: network performance over 1GBps links degraded
Gary Jennejohn wrote: > I have two computers, both with 1Gbps interfaces plugged into a > 1Gb switch. One computer is running FreeBSD HEAD and the other > some version of Linux. Under FreeBSD I have re0 and under Linux > I don't know what the hardware is. > > I noticed that the transfer speed has dropped to only about > 12MBps. I'm used to seeing about 27MBps during the ftp > transfers. Do you see "re0: watchdog timeout" errors? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 -- Alex Dupre ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 10.0-RC5 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Dupre ha scritto: > # freebsd-update install No updates are available to install. Run > '/usr/sbin/freebsd-update fetch' first. Ok, please ignore my message. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlLO1eIACgkQgRXp2M5fVU3hIgCfWuYq3ZgTiXP8IXnM2idTQZSk XBgAoJY8TKTlijXyWpz117YZu5metAju =8SvU -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: FreeBSD 10.0-RC5 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Glen Barber ha scritto: > The fifth RC build of the 10.0-RELEASE release cycle is now > available on the FTP servers for the amd64, i386, ia64, powerpc, > powerpc64 and sparc64 architectures. I've upgraded one of my machine from 9.2 to 10.0-RC5 via freebsd-update, but it didn'seem to have worked (yes, I updated 9.2 to latest patch release before upgrading). After the first 'freebsd-update install' and rebooting: # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 10.0-RC5 from update2.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 10.0-RC5-p0. # uname -a FreeBSD ripple.andxor.it 10.0-RC5 FreeBSD 10.0-RC5 #0 r260430: Wed Jan 8 05:10:04 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # cc -v Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlLO1ZAACgkQgRXp2M5fVU1GiACfQZbNc3DUg4BZD55r3ljoqyLa JrYAoO3gmOtAkkf1l4NQRmcwfXI/OfLw =nRva -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: FreeBSD 10.0-BETA2 now available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Glen Barber ha scritto: > For this announcement, I felt it was safer to include the > instructions from the EN verbatim; for future 10.0 builds, it will > be less verbose. The problem was that the instructions were not verbatim, you omitted (perhaps by mistake) the following very important lines: === 1) Upgrade your system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date. 2) To update your present system via a source code patch: === so the announcement had only the source patch instructions and a '3)' point without 1 and 2 :-) - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlJvb60ACgkQgRXp2M5fVU0F5wCg+/WDmcsk+p+hmwJV/pT8xuzM aWAAn0CeQmKve+QgIhz8j1aeVYdB2wdQ =/pTo -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: FreeBSD 10.0-BETA2 now available
Glen Barber ha scritto: Important note to freebsd-update(8) users: Please be sure to follow the instructions in the EN-13:04.freebsd-update errata notice here before upgrading the system to 10.0-BETA2: I'd say these instructions extracted partially from the advisory are very very confusing as written. If you have a 8.x or 9.x RELEASE all you have to do is updating to the latest minor-release-patchset and then do a 'freebsd-update upgrade -r 10.0-BETA2', like for every other major release upgrade. I don't know who will manually patch a binary update tool if it's building FreeBSD from sources, but anyway it should be the last note while in the announcement it seems to be the only way to do the upgrade. -- Alex Dupre ___ 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: Proposal: multi-instance and self-contained rc.d script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiroki Sato ha scritto: > 1. Multi-instance support > > In the implementation, load_rc_config() reads variables for all > instances and run_rc_command() runs each instance in order. When > doing "rc.d/foo stop", run_rc_command() stops the instances in > reverse order. I haven't looked at the implementation, but a useful feature that's usually missing is these multi-instance implementations and that is available in the multi-rc.d scripts scenario (take tomcat7 rc script as an example) is the ability to start/stop a single instance. Not always the instances are related each other, sometime they serve completely different purposes/applications and would be very useful to allow starting/stopping them independently. If we can get the best from the two implementations it'll be a win-win solution. > 2. Self-contained rc.d script I like the idea of defaults inside the scripts, but I like also a file that lists all available knobs with default values. If it can be automatically generated from the scripts for human reading purpose only, I'll appreciate it. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlHRXDUACgkQgRXp2M5fVU2C5QCfbRJAmtDUwJVid45FyWU1TSgr SF4An26x5n4nq7qI12C57TdvaB9hFjuq =IErn -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: www/apache24: ports like lang/php5 or devel/subversion are disturbed by the apache24 port!
Olli Hauer ha scritto:
> It will take a while until php is really apache24 ready.
>
> Work is in progress on php upstream.
>
> One of the issues is that APXS does not provide the
> MPM model which is needed for php and others to build.
Can you try the following patch, please?
Index: bsd.php.mk
===
--- bsd.php.mk (revision 315696)
+++ bsd.php.mk (working copy)
@@ -60,9 +60,8 @@
HTTPD?= ${LOCALBASE}/sbin/httpd
.if exists(${HTTPD})
-APXS?= ${LOCALBASE}/sbin/apxs
-APACHE_MPM!=${APXS} -q MPM_NAME
-. if ${APACHE_MPM} == "worker" || ${APACHE_MPM} == "event"
+APACHE_THR!=${HTTPD} -V | ${GREP} threaded
+. if ${APACHE_THR:Myes}
PHP_EXT_DIR:= ${PHP_EXT_DIR}-zts
. endif
.elif defined(APACHE_PORT) && (${APACHE_PORT:M*worker*} != "" ||
${APACHE_PORT:M*event*} != "")
--
Alex Dupre
___
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: Re-sizable UFS project
Ermal Luçi ha scritto: > some time ago the FreeBSD Foundation published/approved a project for live > resizing of UFS filesystems. > Does any know if the project was successful and any outcome from it? http://lists.freebsd.org/pipermail/svn-src-head/2012-November/042539.html -- Alex Dupre ___ 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: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
Baptiste Daroussin ha scritto: > On of the thing I forgot and kan@ has added is a prompt for the user in case > it > is going to bootstrap. So, removing the prompt will make everybody happy? :-) What about a prompt with timeout? "This is the first time pkg is run, I'll start bootstrapping in 10 seconds. Press CTRL-C now to abort" -- Alex Dupre ___ 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: fast bcopy...
Luigi Rizzo ha scritto:
For small blocks and multiples of 32-64 bytes, i noticed that
the following is a lot faster (breaking even at about 1 KBytes)
static inline void
fast_bcopy(void *_src, void *_dst, int l)
{
uint64_t *src = _src;
uint64_t *dst = _dst;
for (; l> 0; l-=32) {
*dst++ = *src++;
*dst++ = *src++;
*dst++ = *src++;
*dst++ = *src++;
}
}
DJB influence? :-)
--
Alex Dupre
___
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: graid hit the tree
Alexander Motin ha scritto: You can choose. Their functionality is comparable, but with graid: ... Yes, as I supposed, so the answer is 'yes'. Obviously it needs a lot of testing. Thanks for your work. -- Alex Dupre ___ 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: graid hit the tree
Alexander Motin ha scritto: I've just committed the new GEOM-based software RAID driver (graid) into the HEAD [1]. Brave testers are welcome. :) Supposing they are equally stable, is it now better to use graid instead of gmirror (et similar)? -- Alex Dupre ___ 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"
Regarding pciids
I created hackish scripts to generate pci_vendors file from Boemler and Mares (pciids.sf.net) lists. I haven't found the Hart list. The results of the scripts are here: http://www.alexdupre.com/pci_vendors/mares.txt http://www.alexdupre.com/pci_vendors/boemler.txt http://www.alexdupre.com/pci_vendors/mares-boemler.txt http://www.alexdupre.com/pci_vendors/boemler-mares.txt The first two are generated from single lists, the last two are combined, with different preference order. -- Alex Dupre ___ 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: DHCP server in base
David DEMELIER ha scritto: > I was surprised to see that there is no DHCP server in base, obviously > it's not difficult to fetch the net/isc-dhcp31-server package but for > people that would like to setup a new server on FreeBSD quickly they > will take some time to learn how packages framework works or ports and > it can be annoying. If you (people) don't know how to use ports/packages probably you shouldn't use FreeBSD. And I hardly think that installing a port requires more knowledge than correctly configuring a DHCP server. Then, why 3.1 and not 4.1? Why not bundling also apache? etc., etc. -- Alex Dupre ___ 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: using cupsd instead of base lpr [was Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1 (solved)]
Tom Evans ha scritto: > make delete-old removes old deprecated files, not files that weren't > built because of src.conf options. I think you are wrong: http://www.freebsd.org/cgi/cvsweb.cgi/src/tools/build/mk/OptionalObsoleteFiles.inc?rev=1.66 -- Alex Dupre ___ 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: Having a problem with security/libassuan-1 when compiling gnupg.
Kevin Oberman ha scritto: 5. opensc ale@ has indicated that he would prefer to wait to update his port until a new version that supports assuan 2.0.0 is released. Update: the signer plugin (that requires libassuan) will be removed in opensc 0.12 release. OK. I see dirmgr and gnupg are now ready for libausaan V2.0.0, but I also have opensc installed and MUST have it working. If I upgrade to libassuan-2.0.0, will that break opensc? I assume, since it was not a shared library, that this will not be a problem, but I wanted to be sure. You are safe. -- Alex Dupre ___ 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: Switchover to CAM ATA?
Freddie Cash ha scritto: >> So what is the public opinion: Is the lack of ataraid(4) fatal or we can >> live without it? Lack of ataraid means no more arX devices, right? I'd say it's not fatal for HEAD, but it is for a -STABLE branch. > ataraid(4) has served it's > purpose, tiding us over until GEOM RAID facilities were in place. Now it's > time for it to be retired. It doesn't seem to me that sysinstall supports gmirror or gstripe, so even if they could be better, currently I think many users still use ataraid for simple installations with mirrored disks. -- Alex Dupre ___ 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: ATAng issues status report
Saturday, October 25, 2003, 7:51:58 AM, you wrote: >>> * Resume fails, hanging with drive light on. Last event: 2003/10/2 >>> Appears to be a lost interrupt during reset. >> >> I've just committed some changes that makes suspend/resume work just >> fine on the notebooks I have access to. > > This works great for me! I have suspended/resumed to S3 many times now, > no problems. Still problems with a Compaq Armada M700. During resume it freezes on resetting ata1, after done ata0. An information that may be useful: about one/two weeks ago the booting process was halting for 30 seconds on ata1 (where no devices are attached), while with the latest commits it doesn't halt anymore. -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: Just type 'mv * /dev/null'. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone seeing any NFS lockups/weirdness with latest (ish) current??
Thursday, October 23, 2003, 7:09:28 PM, you wrote: Ml> Anyone else seeing weird behavior? Yes, I saw this on two 4.8-STABLE machines some time ago (about 2 months)...not only with nfs, with smbfs too...I didn't find out the problem and I gave upif I remember correctly, the downloads were ok, but the extract phases locked the machine in the identical way. -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: vi needs to be upgraded to vii ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PC Card Ethernet attach fails in -CURRENT (FA410TX on ThinkPad 240X)
I have a NetGear FA410TX, but seems a little different, and it works perfectly on yesterday -current: Attach: ed1: at port 0x120-0x13f irq 11 function 0 config 32 on pccard0 ed1: address 00:80:c8:8b:c1:7a, type Linksys (16 bit) miibus1: on ed1 lxtphy0: on miibus1 lxtphy0: 100baseFX, 100baseFX-FDX, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Detach: ed1: detached lxtphy0: detached miibus1: detached -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: popper unable to process jumbo kernel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng and CF cards
Monday, September 8, 2003, 11:48:55 AM, you wrote: Sl> DOH! things are not going weel this morning, this patch should be right: Tested your patch, but it's exactly the same as before. -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: Plumber mistook routing panel for decorative wall fixture ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng and CF cards
Monday, September 8, 2003, 11:48:55 AM, you wrote: Sl> DOH! things are not going weel this morning, this patch should be right: I didn't try your patch, yet, but I can report some other phantom drives with ataNG. The system is still the net4501 board. With Sandisk 32MB CF: ata0-master: pio=0x09 wdma=0x udma=0x cable=40pin ad0: FAILURE - SETFEATURES status=51 error=4 ad0: FAILURE - SETFEATURES status=51 error=4 GEOM: create disk ad0 dp=0xc0d46770 ad0: ATA-0 disk at ata0-master ad0: 30MB (62720 sectors), 490 C, 4 H, 32 S, 512 B ad0: 1 secs/int, 1 depth queue, ??? GEOM: new disk ad0 [0] f:80 typ:4 s(CHS):0/1/1 e(CHS):489/3/32 s:32 l:62688 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 16384 length 32096256 end 32112639 With Hitachi 8MB CF: ata0-slave: pio=0x08 wdma=0x udma=0x cable=40pin ata0-master: pio=0x09 wdma=0x udma=0x cable=40pin ad0: FAILURE - SETFEATURES status=51 error=4 ad0: FAILURE - SETFEATURES status=51 error=4 GEOM: create disk ad0 dp=0xc0d46770 ad0: ATA-0 disk at ata0-master ad0: 7MB (15744 sectors), 246 C, 2 H, 32 S, 512 B ad0: 1 secs/int, 1 depth queue, ??? GEOM: new disk ad0 ad1: WARNING - SETFEATURES recovered from missing interrupt [0] f:80 typ:1 s(CHS):0/1/1 e(CHS):245/1/32 s:32 l:15712 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 16384 length 8044544 end 8060927 ad1: WARNING - SETFEATURES recovered from missing interrupt GEOM: create disk ad1 dp=0xc0d46670 ad1: ATA-0 disk at ata0-slave Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc028517b stack pointer = 0x10:0xc0315c44 frame pointer = 0x10:0xc0315cc4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 18 panic: integer divide fault -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: firewall needs cooling ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE boot loader
I found the issue. I was doing: cd /usr/src/sys/boot make depend make cp /usr/src/sys/boot/i386/pxeldr/pxeboot /tftpboot This works os -stable, but not on -current (dunno why)...the pxeboot is created without problems, but doesn't work. However, building world as usual creates a working pxeboot in /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: Netscape has crashed ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE boot loader
This is the exact output: CLIENT MAC ADDR: 00 00 24 C1 2D F0 CLIENT IP: 10.0.0.36 MASK: 255.255.255.0 DHCP IP: 10.0.0.1 GATEWAY IP: 10.0.0.4 PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader POST: 012345... rebooting...the pxeboot has been built only with CPUTYPE=i486 CFLAGS="-O -pipe" (from /etc/make.conf) BOOT_COMCONSOLE_SPEED=57600 -DLOADER_TFTP_SUPPORT (on command line) parameters. With -STABLE no problems arise. -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: We need a licensed electrician to replace the light bulbs in the computer room. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PXE boot loader
I was trying to boot my net4501 board with PXE. This worked like a charm with pxeboot compiled on -STABLE, but using -CURRENT to build it my net4501 continuously reboot just after the DHCP/TFTP phase (it appears something like "POST12345" and then reboots). Any hint? -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: The Usenet news is out of date ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
