Re: how to solve the problem to install R?
when i make configure ,there is a wrong output,how can i do now?
Downloaded 689.8 kilobytes in 3:35 seconds. (3.19 KB/s)
=== Found saved configuration for png-1.5.12
= SHA256 Checksum mismatch for libpng-1.5.12.tar.xz.
= SHA256 Checksum OK for libpng-1.5.12-apng.patch.gz.
=== Giving up on fetching files: libpng-1.5.12.tar.xz
Make sure the Makefile and distinfo file (/usr/ports/graphics/png/distinfo)
are up to date. If you are absolutely sure you want to override this
check, type make NO_CHECKSUM=yes [other args].
*** Error code 1
Stop in /usr/ports/graphics/png.
*** Error code 1
Stop in /usr/ports/graphics/png.
*** Error code 1
Stop in /usr/ports/graphics/png.
*** Error code 1
Stop in /usr/ports/math/R.
*** Error code 1
Stop in /usr/ports/math/R.
2012/8/26 Polytropon free...@edvax.de
{ Re-including list, hope that's okay. }
On Sun, 26 Aug 2012 00:14:37 -0400, contro opinion wrote:
# cd /usr/ports/math/R
[root@sea /usr/ports/math/R]# make configure
=== R-2.15.1 is marked as broken: The PDF_MANUALS option cannot be
used,
because print/texinfo is incompatible with print/teTeX-base.
*** Error code 1
Stop in /usr/ports/math/R.
how can i do now?
I have the same port version here, and I can get to the
configuration menu. First of all, make sure you have done
# make rmconfig
And then you should see no error message when doing
# make configure
And in the menu, do _not_ select PDF_MANUALS. Having
examined the port's Makefile for the BROKEN variable
and other options that might trigger it, it seems
that the R port has significant problems regarding
its documentation.
++
| Options for R 2.15.1 |
| ++ |
| | [ ] ATLAS Use ATLAS instead of BLAS/LAPACK | |
| | [X] GHOSTSCRIPT [dev2]bitmap() graphics devices | |
| | [X] ICU Use ICU for collation in multibyte locales | |
= | | [X] INFO_MANUALS GNU info manuals | |
| | [X] JPEG jpeg() graphics device | |
| | [ ] LETTER_PAPER US Letter paper | |
| | [X] LIBR R shared library and a dynamically-linked R | |
| | [X] PANGOCAIROcairo and pango graphics support | |
| | [X] PCRE_PORT Use devel/pcre instead of the bundled PCRE | |
= | | [ ] PDF_MANUALS PDF manuals (requires TeX) | |
| | [X] PNG png() graphics device| |
| | [X] TCLTK tcltk package| |
| | [X] THREADS Threading support| |
| | [X] X11 X11() graphics device| |
| || |
+-++-+
| [ OK ] Cancel|
++
Then you should be able to continue building (will possibly pull
gcc 4.6.3, this is the point where I stopped testing it myself.
If this doesn't work, again remove the configuration and re-enter
it by make configure: Then deselect INFO_MANUALS also. As I
said, the port's Makefile shows:
.if ${PORT_OPTIONS:MINFO_MANUALS} ${PORT_OPTIONS:MDOCS}
ALL_TARGET+=info
INFO= R-FAQ R-admin R-data R-exts R-intro R-lang
.endif
.if ${PORT_OPTIONS:MPDF_MANUALS} ${PORT_OPTIONS:MDOCS}
BROKEN =The PDF_MANUALS option cannot be used, because\
print/texinfo is incompatible with print/teTeX-base
BUILD_DEPENDS +=pdftex:${PORTSDIR}/print/teTeX-base \
texi2dvi:${PORTSDIR}/print/texinfo
ALL_TARGET+=pdf
CONFIGURE_ENV +=INSTALL_INFO=${LOCALBASE}/bin/install-info \
MAKEINFO=${LOCALBASE}/bin/makeinfo
INSTALL_TARGET+=install-pdf
PLIST_SUB+= PDF_MANUAL=
.else
PLIST_SUB+= PDF_MANUAL=@comment
.endif
.endif # LIBR_SLAVEPORT
.endif # !LIBRMATH_SLAVEPORT
Keywords are MDOCS and MINFO_MANUALS here. So if the problem
might be inherited from other ports (mdoc related?), you could
do
# make rmconfig-recursive
followed by
# make config-recursive
to visit and carefully check all configuration screens that might
have an option that triggers the BROKEN mechanism, possibly
related to some info, texinfo, teTex or other dependency for the
documentation of R.
Finally, you could try to install R from package (via pkg_add -r).
The Makefile doesn't define RDEPS (runtime dependencies), so that
should be relatively easy. The LaTeX
Re: how to solve the problem to install R?
On Sun, 26 Aug 2012 08:41:35 -0400, contro opinion wrote: when i make configure ,there is a wrong output,how can i do now? That's impossible. Are you sure your ports collection is properly updated and complete? The screenshot I've inserted has been directly copied from the terminal. As R has settable options, make configure (_after_ make rmconfig to limit the possibilities of mistakes) is supposed to bring up the configuration dialog I showed. Then you proceed to show messages from a make or make install command: Downloaded 689.8 kilobytes in 3:35 seconds. (3.19 KB/s) === Found saved configuration for png-1.5.12 = SHA256 Checksum mismatch for libpng-1.5.12.tar.xz. = SHA256 Checksum OK for libpng-1.5.12-apng.patch.gz. === Giving up on fetching files: libpng-1.5.12.tar.xz Make sure the Makefile and distinfo file (/usr/ports/graphics/png/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 Stop in /usr/ports/graphics/png. *** Error code 1 Stop in /usr/ports/graphics/png. *** Error code 1 Stop in /usr/ports/graphics/png. *** Error code 1 Another problem with png (libpng is a dependency of R). Make sure your ports tree is up to date. Don't forget to # make clean prior to any new build attempt. As I said, I've partially checked things here on my system, and I get the configuration dialog and can even get around the BROKEN warning by deselecting PDF_MANUALS. Start in a clean environment. Follow the steps as described in the manuals (e. g. man 7 ports) and The FreeBSD Handbook and you should be fine. In _worst_ case, try # pkg_add -r R to do a binary install. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how to solve the problem to install R?
[root@sea ~]# cd /usr/ports/math/R [root@sea /usr/ports/math/R]# make install clean === R-2.15.1 is marked as broken: The PDF_MANUALS option cannot be used, because print/texinfo is incompatible with print/teTeX-base. *** Error code 1 Stop in /usr/ports/math/R. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to solve the problem to install R?
On Sat, 25 Aug 2012 21:32:55 -0400, contro opinion wrote: [root@sea ~]# cd /usr/ports/math/R [root@sea /usr/ports/math/R]# make install clean === R-2.15.1 is marked as broken: The PDF_MANUALS option cannot be used, because print/texinfo is incompatible with print/teTeX-base. *** Error code 1 Stop in /usr/ports/math/R. Enter the command # make configure and deselect the PDF_MANUALS option. (Not tested!) This should leave you with GNU info manuals if you keep that option selected. Then repeat the installation command. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to solve the problem to install R?
{ Re-including list, hope that's okay. }
On Sun, 26 Aug 2012 00:14:37 -0400, contro opinion wrote:
# cd /usr/ports/math/R
[root@sea /usr/ports/math/R]# make configure
=== R-2.15.1 is marked as broken: The PDF_MANUALS option cannot be used,
because print/texinfo is incompatible with print/teTeX-base.
*** Error code 1
Stop in /usr/ports/math/R.
how can i do now?
I have the same port version here, and I can get to the
configuration menu. First of all, make sure you have done
# make rmconfig
And then you should see no error message when doing
# make configure
And in the menu, do _not_ select PDF_MANUALS. Having
examined the port's Makefile for the BROKEN variable
and other options that might trigger it, it seems
that the R port has significant problems regarding
its documentation.
++
| Options for R 2.15.1 |
| ++ |
| | [ ] ATLAS Use ATLAS instead of BLAS/LAPACK | |
| | [X] GHOSTSCRIPT [dev2]bitmap() graphics devices | |
| | [X] ICU Use ICU for collation in multibyte locales | |
= | | [X] INFO_MANUALS GNU info manuals | |
| | [X] JPEG jpeg() graphics device | |
| | [ ] LETTER_PAPER US Letter paper | |
| | [X] LIBR R shared library and a dynamically-linked R | |
| | [X] PANGOCAIROcairo and pango graphics support | |
| | [X] PCRE_PORT Use devel/pcre instead of the bundled PCRE | |
= | | [ ] PDF_MANUALS PDF manuals (requires TeX) | |
| | [X] PNG png() graphics device| |
| | [X] TCLTK tcltk package| |
| | [X] THREADS Threading support| |
| | [X] X11 X11() graphics device| |
| || |
+-++-+
| [ OK ] Cancel|
++
Then you should be able to continue building (will possibly pull
gcc 4.6.3, this is the point where I stopped testing it myself.
If this doesn't work, again remove the configuration and re-enter
it by make configure: Then deselect INFO_MANUALS also. As I
said, the port's Makefile shows:
.if ${PORT_OPTIONS:MINFO_MANUALS} ${PORT_OPTIONS:MDOCS}
ALL_TARGET+=info
INFO= R-FAQ R-admin R-data R-exts R-intro R-lang
.endif
.if ${PORT_OPTIONS:MPDF_MANUALS} ${PORT_OPTIONS:MDOCS}
BROKEN =The PDF_MANUALS option cannot be used, because\
print/texinfo is incompatible with print/teTeX-base
BUILD_DEPENDS +=pdftex:${PORTSDIR}/print/teTeX-base \
texi2dvi:${PORTSDIR}/print/texinfo
ALL_TARGET+=pdf
CONFIGURE_ENV +=INSTALL_INFO=${LOCALBASE}/bin/install-info \
MAKEINFO=${LOCALBASE}/bin/makeinfo
INSTALL_TARGET+=install-pdf
PLIST_SUB+= PDF_MANUAL=
.else
PLIST_SUB+= PDF_MANUAL=@comment
.endif
.endif # LIBR_SLAVEPORT
.endif # !LIBRMATH_SLAVEPORT
Keywords are MDOCS and MINFO_MANUALS here. So if the problem
might be inherited from other ports (mdoc related?), you could
do
# make rmconfig-recursive
followed by
# make config-recursive
to visit and carefully check all configuration screens that might
have an option that triggers the BROKEN mechanism, possibly
related to some info, texinfo, teTex or other dependency for the
documentation of R.
Finally, you could try to install R from package (via pkg_add -r).
The Makefile doesn't define RDEPS (runtime dependencies), so that
should be relatively easy. The LaTeX dependency seems to be a
build dependency (see Makefile excerpt above).
If you don't have success with any advice, maybe file a ports PR.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem in install
While I am installing FreeBSD 8.2-STABLE, when I finish with disklabel, and then says Last chance, then to accept I get the following message: Unable to find device node for / dev/ad4s1b in / dev! The creation of filesystem Will be aborted. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem in install
On Sat, 5 Nov 2011, masayoshi wrote: --- On Sun, 6/11/11, Zantgo zan...@gmail.com wrote: From: Zantgo zan...@gmail.com Subject: Problem in install To: freebsd-questions@FreeBSD.org freebsd-questions@freebsd.org Received: Sunday, 6 November, 2011, 4:06 AM While I am installing FreeBSD 8.2-STABLE, when I finish with disklabel, and then says Last chance, then to accept I get the following message: Unable to find device node for / dev/ad4s1b in / dev! The creation of filesystem Will be aborted. Hi Though I?am noob, I searched FreeBSD forum. http://forums.freebsd.org/showthread.php?t=1675 I believe this is exactly correct. If this does not do it, recreate the partition (step 1) and select the write option rather than quit. Under conditions I do not understand the partition table does not get written when reformatting a disk when just selecting quit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
USB problem during install
I was just running a check to see if I could install FreeBSD on my tv server and check the driver situation, but the cdboot failed with a usb issue- address not found. This occurred for 7.1, 7.0, and even 6.4. In my search I found many different reasons why it could be, but they were several years old (related to 5.x etc). Its always the same address 0x7fef1620, and I believe its the same port too. Currently the usb devices connected are an APC UPS, a Shintaro usb wireless keyboard with builtin mouse, a multi card reader, and I have two dvico tuner cards (dual fusions) which a dual dibcomms on each card connected to the system via their own usb chip. Based on my observations its actually hard to say which port is the problem, as the drivers are loaded and fork their own processes, so the error can show up later. Any ideas? Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[Fwd: USB problem during install]
---BeginMessage--- I was just running a check to see if I could install FreeBSD on my tv server and check the driver situation, but the cdboot failed with a usb issue- address not found. This occurred for 7.1, 7.0, and even 6.4. In my search I found many different reasons why it could be, but they were several years old (related to 5.x etc). Its always the same address 0x7fef1620, and I believe its the same port too. Currently the usb devices connected are an APC UPS, a Shintaro usb wireless keyboard with builtin mouse, a multi card reader, and I have two dvico tuner cards (dual fusions) which a dual dibcomms on each card connected to the system via their own usb chip. Based on my observations its actually hard to say which port is the problem, as the drivers are loaded and fork their own processes, so the error can show up later. Any ideas? Cheers ---End Message--- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem of install 7.0 on notebook
7.0-beta2-amd64's boot stop at the same place as beta1.5. 2007/11/3, Zhang hw [EMAIL PROTECTED]: Thank you, David! The verbose logging messages: --- pcib2: ACPI PCI-PCI bridge at device 4.0 on pci0 pcib2: domain 0 pcib2: secondary bus 16 pcib2: subordinate bus 16 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xcc00-0xcc0f pcib2: no prefetched decode pcib2: could not get PCI interrupt routing table for \_SB_.C08B.C24F - AE_NOT_FOUND pci16: ACPI PCI bus on pcib2 pci16: domain=0, physical bus=16 found- vendor=0x14e4, dev=0x1693, revid=0x02 domain=0, bus=16, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16, (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xcc00, size 16, enabled pcib2: requested memory range 0xcc00-0xcc00: good pcib0: matched entry for 0.4.INTA pcib0: slot 4 INTA hardwired to IRQ16 pcib2: slot 0 INTA is routed to irq 16 -- This is the last screen shown, and I write it here handy. 2007/11/2, David Yeske [EMAIL PROTECTED]: On 11/2/07, Zhang hw [EMAIL PROTECTED] wrote: I have now could work on my notebook with freebsd 6.2-release and 6.3-prerelease, but there are still some problems such as acpi. So I want to have a try of freebsd 7.0-beta-1.5, but I can't install it, the boot process stop at pci probing: pcib2:PCI-PCI brige at device 4.0 on pci0 pci16:PCI-PCI bus on pcib2 if acpi enable, it maybe show as: pcib2:ACPI PCI-PCI brige... pci16:ACPI... my cpu is athlon 64x2, I've tried both amd64 and i386 versions. Help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] What happens if you boot verbose? That might better indicate where the kernel is hanging. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem of install 7.0 on notebook
Thank you, David! The verbose logging messages: --- pcib2: ACPI PCI-PCI bridge at device 4.0 on pci0 pcib2: domain 0 pcib2: secondary bus 16 pcib2: subordinate bus 16 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xcc00-0xcc0f pcib2: no prefetched decode pcib2: could not get PCI interrupt routing table for \_SB_.C08B.C24F - AE_NOT_FOUND pci16: ACPI PCI bus on pcib2 pci16: domain=0, physical bus=16 found- vendor=0x14e4, dev=0x1693, revid=0x02 domain=0, bus=16, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16, (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xcc00, size 16, enabled pcib2: requested memory range 0xcc00-0xcc00: good pcib0: matched entry for 0.4.INTA pcib0: slot 4 INTA hardwired to IRQ16 pcib2: slot 0 INTA is routed to irq 16 -- This is the last screen shown, and I write it here handy. 2007/11/2, David Yeske [EMAIL PROTECTED]: On 11/2/07, Zhang hw [EMAIL PROTECTED] wrote: I have now could work on my notebook with freebsd 6.2-release and 6.3-prerelease, but there are still some problems such as acpi. So I want to have a try of freebsd 7.0-beta-1.5, but I can't install it, the boot process stop at pci probing: pcib2:PCI-PCI brige at device 4.0 on pci0 pci16:PCI-PCI bus on pcib2 if acpi enable, it maybe show as: pcib2:ACPI PCI-PCI brige... pci16:ACPI... my cpu is athlon 64x2, I've tried both amd64 and i386 versions. Help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] What happens if you boot verbose? That might better indicate where the kernel is hanging. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem of install 7.0 on notebook
Quoting Jonathan Horne [EMAIL PROTECTED]: Quoting David Yeske [EMAIL PROTECTED]: On 11/2/07, Zhang hw [EMAIL PROTECTED] wrote: I have now could work on my notebook with freebsd 6.2-release and 6.3-prerelease, but there are still some problems such as acpi. So I want to have a try of freebsd 7.0-beta-1.5, but I can't install it, the boot process stop at pci probing: pcib2:PCI-PCI brige at device 4.0 on pci0 pci16:PCI-PCI bus on pcib2 if acpi enable, it maybe show as: pcib2:ACPI PCI-PCI brige... pci16:ACPI... my cpu is athlon 64x2, I've tried both amd64 and i386 versions. Help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] What happens if you boot verbose? That might better indicate where the kernel is hanging. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] without the -j, this appears to be wherei am hanging up: uipc_syscalls.o(.text+0x3c1): In function `sctp_generic_recvmsg': /usr/src/sys/kern/uipc_syscalls.c:2600: undefined reference to `sctp_sorecvmsg' uipc_syscalls.o(.text+0x21a2): In function `sctp_generic_sendmsg_iov': /usr/src/sys/kern/uipc_syscalls.c:2478: undefined reference to `sctp_lower_sosend' uipc_syscalls.o(.text+0x249d): In function `sctp_generic_sendmsg': /usr/src/sys/kern/uipc_syscalls.c:2371: undefined reference to `sctp_lower_sosend' uipc_syscalls.o(.text+0x266c): In function `sctp_peeloff': /usr/src/sys/kern/uipc_syscalls.c:2238: undefined reference to `sctp_can_peel_off' uipc_syscalls.o(.text+0x28e6):/usr/src/sys/kern/uipc_syscalls.c:2279: undefined reference to `sctp_do_peeloff' rtsock.o(.text+0xb7d): In function `rt_newaddrmsg': /usr/src/sys/net/rtsock.c:897: undefined reference to `sctp_addr_change' in_proto.o(.data+0xa8): undefined reference to `sctp_input' in_proto.o(.data+0xb0): undefined reference to `sctp_ctlinput' in_proto.o(.data+0xb4): undefined reference to `sctp_ctloutput' in_proto.o(.data+0xbc): undefined reference to `sctp_init' in_proto.o(.data+0xc8): undefined reference to `sctp_drain' in_proto.o(.data+0xcc): undefined reference to `sctp_usrreqs' in_proto.o(.data+0xdc): undefined reference to `sctp_input' in_proto.o(.data+0xe4): undefined reference to `sctp_ctlinput' in_proto.o(.data+0xe8): undefined reference to `sctp_ctloutput' in_proto.o(.data+0xfc): undefined reference to `sctp_drain' in_proto.o(.data+0x100): undefined reference to `sctp_usrreqs' in_proto.o(.data+0x110): undefined reference to `sctp_input' in_proto.o(.data+0x118): undefined reference to `sctp_ctlinput' in_proto.o(.data+0x11c): undefined reference to `sctp_ctloutput' in_proto.o(.data+0x130): undefined reference to `sctp_drain' in_proto.o(.data+0x134): undefined reference to `sctp_usrreqs' *** Error code 1 Stop in /usr/obj/usr/src/sys/HPDC7100. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] my apologies all, the above reply did not pertain to this thread. please exuse me while i finish the rest of my coffee!! -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] This message was sent using IMP, the Internet Messaging Program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem of install 7.0 on notebook
Quoting David Yeske [EMAIL PROTECTED]: On 11/2/07, Zhang hw [EMAIL PROTECTED] wrote: I have now could work on my notebook with freebsd 6.2-release and 6.3-prerelease, but there are still some problems such as acpi. So I want to have a try of freebsd 7.0-beta-1.5, but I can't install it, the boot process stop at pci probing: pcib2:PCI-PCI brige at device 4.0 on pci0 pci16:PCI-PCI bus on pcib2 if acpi enable, it maybe show as: pcib2:ACPI PCI-PCI brige... pci16:ACPI... my cpu is athlon 64x2, I've tried both amd64 and i386 versions. Help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] What happens if you boot verbose? That might better indicate where the kernel is hanging. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] without the -j, this appears to be wherei am hanging up: uipc_syscalls.o(.text+0x3c1): In function `sctp_generic_recvmsg': /usr/src/sys/kern/uipc_syscalls.c:2600: undefined reference to `sctp_sorecvmsg' uipc_syscalls.o(.text+0x21a2): In function `sctp_generic_sendmsg_iov': /usr/src/sys/kern/uipc_syscalls.c:2478: undefined reference to `sctp_lower_sosend' uipc_syscalls.o(.text+0x249d): In function `sctp_generic_sendmsg': /usr/src/sys/kern/uipc_syscalls.c:2371: undefined reference to `sctp_lower_sosend' uipc_syscalls.o(.text+0x266c): In function `sctp_peeloff': /usr/src/sys/kern/uipc_syscalls.c:2238: undefined reference to `sctp_can_peel_off' uipc_syscalls.o(.text+0x28e6):/usr/src/sys/kern/uipc_syscalls.c:2279: undefined reference to `sctp_do_peeloff' rtsock.o(.text+0xb7d): In function `rt_newaddrmsg': /usr/src/sys/net/rtsock.c:897: undefined reference to `sctp_addr_change' in_proto.o(.data+0xa8): undefined reference to `sctp_input' in_proto.o(.data+0xb0): undefined reference to `sctp_ctlinput' in_proto.o(.data+0xb4): undefined reference to `sctp_ctloutput' in_proto.o(.data+0xbc): undefined reference to `sctp_init' in_proto.o(.data+0xc8): undefined reference to `sctp_drain' in_proto.o(.data+0xcc): undefined reference to `sctp_usrreqs' in_proto.o(.data+0xdc): undefined reference to `sctp_input' in_proto.o(.data+0xe4): undefined reference to `sctp_ctlinput' in_proto.o(.data+0xe8): undefined reference to `sctp_ctloutput' in_proto.o(.data+0xfc): undefined reference to `sctp_drain' in_proto.o(.data+0x100): undefined reference to `sctp_usrreqs' in_proto.o(.data+0x110): undefined reference to `sctp_input' in_proto.o(.data+0x118): undefined reference to `sctp_ctlinput' in_proto.o(.data+0x11c): undefined reference to `sctp_ctloutput' in_proto.o(.data+0x130): undefined reference to `sctp_drain' in_proto.o(.data+0x134): undefined reference to `sctp_usrreqs' *** Error code 1 Stop in /usr/obj/usr/src/sys/HPDC7100. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] This message was sent using IMP, the Internet Messaging Program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problem of install 7.0 on notebook
I have now could work on my notebook with freebsd 6.2-release and 6.3-prerelease, but there are still some problems such as acpi. So I want to have a try of freebsd 7.0-beta-1.5, but I can't install it, the boot process stop at pci probing: pcib2:PCI-PCI brige at device 4.0 on pci0 pci16:PCI-PCI bus on pcib2 if acpi enable, it maybe show as: pcib2:ACPI PCI-PCI brige... pci16:ACPI... my cpu is athlon 64x2, I've tried both amd64 and i386 versions. Help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem of install 7.0 on notebook
On 11/2/07, Zhang hw [EMAIL PROTECTED] wrote: I have now could work on my notebook with freebsd 6.2-release and 6.3-prerelease, but there are still some problems such as acpi. So I want to have a try of freebsd 7.0-beta-1.5, but I can't install it, the boot process stop at pci probing: pcib2:PCI-PCI brige at device 4.0 on pci0 pci16:PCI-PCI bus on pcib2 if acpi enable, it maybe show as: pcib2:ACPI PCI-PCI brige... pci16:ACPI... my cpu is athlon 64x2, I've tried both amd64 and i386 versions. Help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] What happens if you boot verbose? That might better indicate where the kernel is hanging. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone.
wheel 230, 0 Jan 7 18:18 devstat dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 fd crw--- 1 root wheel 250, 0 Jan 7 18:18 fido crw-r- 1 root operator 252, 0 Jan 7 18:18 geom.ctl crw--- 1 root wheel 248, 14 Jan 7 18:18 io lrwxr-xr-x 1 root wheel6 Jan 7 18:18 kbd0 - atkbd0 crw--- 1 root wheel 7, 0 Jan 7 18:18 klog crw-r- 1 root kmem 249, 1 Jan 7 18:18 kmem lrwxr-xr-x 1 root wheel 12 Jan 7 18:18 log - /var/run/log crw--- 1 root wheel 237, 0 Jan 7 18:18 lpt0 crw--- 1 root wheel 237, 128 Jan 7 18:18 lpt0.ctl crw--- 1 root wheel 231, 0x00ff Jan 7 18:18 mdctl crw-r- 1 root kmem 249, 0 Jan 7 18:18 mem dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 net lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net1 - net/rl0 lrwxr-xr-x 1 root wheel9 Jan 7 18:18 net2 - net/plip0 lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net3 - net/lo0 crw--- 1 root wheel 253, 0 Jan 7 18:18 network crw--- 1 root wheel 232, 1 Jan 7 18:18 nfs4 crw-rw-rw- 1 root wheel 2, 2 Jan 7 18:18 null crw-r--r-- 1 root wheel 246, 0 Jan 7 18:18 pci crw--- 1 root wheel 236, 0 Jan 7 18:18 ppi0 crw-rw-rw- 1 root wheel 234, 1 Jan 7 18:18 psm0 crw-rw-rw- 1 root wheel 245, 0 Jan 7 18:18 random lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stderr - fd/2 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdin - fd/0 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdout - fd/1 crw--- 1 root wheel 247, 128 Jan 7 18:18 sysmouse crw--- 1 root wheel 239, 0 Jan 7 18:18 ttyd0 crw--- 1 root wheel 239, 1 Jan 7 18:18 ttyd1 crw--- 1 root wheel 238, 32 Jan 7 18:18 ttyid0 crw--- 1 root wheel 238, 33 Jan 7 18:18 ttyid1 crw--- 1 root wheel 238, 64 Jan 7 18:18 ttyld0 crw--- 1 root wheel 238, 65 Jan 7 18:18 ttyld1 crw--- 1 root tty 233, 0 Jan 7 18:21 ttyv0 crw--- 1 root wheel 233, 1 Jan 7 18:18 ttyv1 crw--- 1 root wheel 233, 2 Jan 7 18:18 ttyv2 crw--- 1 root wheel 233, 3 Jan 7 18:18 ttyv3 crw--- 1 root wheel 233, 4 Jan 7 18:18 ttyv4 crw--- 1 root wheel 233, 5 Jan 7 18:18 ttyv5 crw--- 1 root wheel 233, 6 Jan 7 18:18 ttyv6 crw--- 1 root wheel 233, 7 Jan 7 18:18 ttyv7 crw--- 1 root wheel 233, 8 Jan 7 18:18 ttyv8 crw--- 1 root wheel 233, 9 Jan 7 18:18 ttyv9 crw--- 1 root wheel 233, 10 Jan 7 18:18 ttyva crw--- 1 root wheel 233, 11 Jan 7 18:18 ttyvb crw--- 1 root wheel 233, 12 Jan 7 18:18 ttyvc crw--- 1 root wheel 233, 13 Jan 7 18:18 ttyvd crw--- 1 root wheel 233, 14 Jan 7 18:18 ttyve crw--- 1 root wheel 233, 15 Jan 7 18:18 ttyvf crw-r--r-- 1 root operator 241, 0 Jan 7 18:18 ugen0 crw-r--r-- 1 root operator 241, 1 Jan 7 18:18 ugen0.1 crw-r--r-- 1 root operator 241, 2 Jan 7 18:18 ugen0.2 crw-r--r-- 1 root operator 241, 3 Jan 7 18:18 ugen0.3 lrwxr-xr-x 1 root wheel6 Jan 7 18:18 urandom - random crw-rw 1 root operator 240, 255 Jan 7 18:18 usb crw-rw 1 root operator 240, 0 Jan 7 18:18 usb0 crw--- 1 root operator 229, 0 Jan 7 18:18 xpt0 crw-rw-rw- 1 root wheel 2, 12 Jan 7 18:18 zero FreeBSD v.5.3. problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone. 1. kernel_config.txt, Kernel_config.hints.txt - Compiled kernel with this setting(file) 2. boot_defaults_loader.conf.txt - This is a file from /boot/defaults.conf 3. etc_rc.conf.txt - This is a file from /etc/rc.conf 4. var_log_messages.txt - This is a log file from /var/log/messages 5. console_out_usbdevs_v.txt- Command usbdevs -s after run in console out text conteined in this file 6. dmesg.txt - Conteind data out after run programm dmesg in console 7. ls_dev.txt - conteined data out after run command ls /dev device /dev/ucom0 not created in any way. What me do with my problem say me please. sanc you.Jan 7 18:18:20 backup kernel: Copyright (c) 1992-2004 The FreeBSD Project. Jan 7 18:18:20 backup kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 7 18:18:20 backup kernel: The Regents of the University of California. All rights reserved. Jan 7 18:18:20 backup kernel: FreeBSD 5.3-RELEASE #0: Wed Jan 4 08:23:58 UTC 2006 Jan 7 18:18:20 backup kernel: [EMAIL PROTECTED]:/usr/src/sys/i386/compile/gooroo Jan 7 18:18:20 backup kernel: module_register: module uhub/ugen already exists! Jan 7 18:18:20 backup kernel: Module uhub/ugen failed to register: 17 Jan 7 18:18:20 backup kernel: module_register: module uhub/uhid already exists! Jan 7 18:18:20 backup kernel: Module uhub/uhid failed to register: 17 Jan 7 18:18:20 backup kernel
Re: Problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone.
On Sat, 2006-01-07 at 17:10, [EMAIL PROTECTED] wrote: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I would send your question in the message as I and I guess most of the recipients of this list don't accept attachments. Nor will the mail archives. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone.
wheel 230, 0 Jan 7 18:18 devstat dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 fd crw--- 1 root wheel 250, 0 Jan 7 18:18 fido crw-r- 1 root operator 252, 0 Jan 7 18:18 geom.ctl crw--- 1 root wheel 248, 14 Jan 7 18:18 io lrwxr-xr-x 1 root wheel6 Jan 7 18:18 kbd0 - atkbd0 crw--- 1 root wheel 7, 0 Jan 7 18:18 klog crw-r- 1 root kmem 249, 1 Jan 7 18:18 kmem lrwxr-xr-x 1 root wheel 12 Jan 7 18:18 log - /var/run/log crw--- 1 root wheel 237, 0 Jan 7 18:18 lpt0 crw--- 1 root wheel 237, 128 Jan 7 18:18 lpt0.ctl crw--- 1 root wheel 231, 0x00ff Jan 7 18:18 mdctl crw-r- 1 root kmem 249, 0 Jan 7 18:18 mem dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 net lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net1 - net/rl0 lrwxr-xr-x 1 root wheel9 Jan 7 18:18 net2 - net/plip0 lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net3 - net/lo0 crw--- 1 root wheel 253, 0 Jan 7 18:18 network crw--- 1 root wheel 232, 1 Jan 7 18:18 nfs4 crw-rw-rw- 1 root wheel 2, 2 Jan 7 18:18 null crw-r--r-- 1 root wheel 246, 0 Jan 7 18:18 pci crw--- 1 root wheel 236, 0 Jan 7 18:18 ppi0 crw-rw-rw- 1 root wheel 234, 1 Jan 7 18:18 psm0 crw-rw-rw- 1 root wheel 245, 0 Jan 7 18:18 random lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stderr - fd/2 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdin - fd/0 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdout - fd/1 crw--- 1 root wheel 247, 128 Jan 7 18:18 sysmouse crw--- 1 root wheel 239, 0 Jan 7 18:18 ttyd0 crw--- 1 root wheel 239, 1 Jan 7 18:18 ttyd1 crw--- 1 root wheel 238, 32 Jan 7 18:18 ttyid0 crw--- 1 root wheel 238, 33 Jan 7 18:18 ttyid1 crw--- 1 root wheel 238, 64 Jan 7 18:18 ttyld0 crw--- 1 root wheel 238, 65 Jan 7 18:18 ttyld1 crw--- 1 root tty 233, 0 Jan 7 18:21 ttyv0 crw--- 1 root wheel 233, 1 Jan 7 18:18 ttyv1 crw--- 1 root wheel 233, 2 Jan 7 18:18 ttyv2 crw--- 1 root wheel 233, 3 Jan 7 18:18 ttyv3 crw--- 1 root wheel 233, 4 Jan 7 18:18 ttyv4 crw--- 1 root wheel 233, 5 Jan 7 18:18 ttyv5 crw--- 1 root wheel 233, 6 Jan 7 18:18 ttyv6 crw--- 1 root wheel 233, 7 Jan 7 18:18 ttyv7 crw--- 1 root wheel 233, 8 Jan 7 18:18 ttyv8 crw--- 1 root wheel 233, 9 Jan 7 18:18 ttyv9 crw--- 1 root wheel 233, 10 Jan 7 18:18 ttyva crw--- 1 root wheel 233, 11 Jan 7 18:18 ttyvb crw--- 1 root wheel 233, 12 Jan 7 18:18 ttyvc crw--- 1 root wheel 233, 13 Jan 7 18:18 ttyvd crw--- 1 root wheel 233, 14 Jan 7 18:18 ttyve crw--- 1 root wheel 233, 15 Jan 7 18:18 ttyvf crw-r--r-- 1 root operator 241, 0 Jan 7 18:18 ugen0 crw-r--r-- 1 root operator 241, 1 Jan 7 18:18 ugen0.1 crw-r--r-- 1 root operator 241, 2 Jan 7 18:18 ugen0.2 crw-r--r-- 1 root operator 241, 3 Jan 7 18:18 ugen0.3 lrwxr-xr-x 1 root wheel6 Jan 7 18:18 urandom - random crw-rw 1 root operator 240, 255 Jan 7 18:18 usb crw-rw 1 root operator 240, 0 Jan 7 18:18 usb0 crw--- 1 root operator 229, 0 Jan 7 18:18 xpt0 crw-rw-rw- 1 root wheel 2, 12 Jan 7 18:18 zero FreeBSD v.5.3. problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone. 1. kernel_config.txt, Kernel_config.hints.txt - Compiled kernel with this setting(file) 2. boot_defaults_loader.conf.txt - This is a file from /boot/defaults.conf 3. etc_rc.conf.txt - This is a file from /etc/rc.conf 4. var_log_messages.txt - This is a log file from /var/log/messages 5. console_out_usbdevs_v.txt- Command usbdevs -s after run in console out text conteined in this file 6. dmesg.txt - Conteind data out after run programm dmesg in console 7. ls_dev.txt - conteined data out after run command ls /dev device /dev/ucom0 not created in any way. What me do with my problem say me please. sanc you.Jan 7 18:18:20 backup kernel: Copyright (c) 1992-2004 The FreeBSD Project. Jan 7 18:18:20 backup kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 7 18:18:20 backup kernel: The Regents of the University of California. All rights reserved. Jan 7 18:18:20 backup kernel: FreeBSD 5.3-RELEASE #0: Wed Jan 4 08:23:58 UTC 2006 Jan 7 18:18:20 backup kernel: [EMAIL PROTECTED]:/usr/src/sys/i386/compile/gooroo Jan 7 18:18:20 backup kernel: module_register: module uhub/ugen already exists! Jan 7 18:18:20 backup kernel: Module uhub/ugen failed to register: 17 Jan 7 18:18:20 backup kernel: module_register: module uhub/uhid already exists! Jan 7 18:18:20 backup kernel: Module uhub/uhid failed to register: 17 Jan 7 18:18:20 backup kernel
Problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone.
wheel 230, 0 Jan 7 18:18 devstat dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 fd crw--- 1 root wheel 250, 0 Jan 7 18:18 fido crw-r- 1 root operator 252, 0 Jan 7 18:18 geom.ctl crw--- 1 root wheel 248, 14 Jan 7 18:18 io lrwxr-xr-x 1 root wheel6 Jan 7 18:18 kbd0 - atkbd0 crw--- 1 root wheel 7, 0 Jan 7 18:18 klog crw-r- 1 root kmem 249, 1 Jan 7 18:18 kmem lrwxr-xr-x 1 root wheel 12 Jan 7 18:18 log - /var/run/log crw--- 1 root wheel 237, 0 Jan 7 18:18 lpt0 crw--- 1 root wheel 237, 128 Jan 7 18:18 lpt0.ctl crw--- 1 root wheel 231, 0x00ff Jan 7 18:18 mdctl crw-r- 1 root kmem 249, 0 Jan 7 18:18 mem dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 net lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net1 - net/rl0 lrwxr-xr-x 1 root wheel9 Jan 7 18:18 net2 - net/plip0 lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net3 - net/lo0 crw--- 1 root wheel 253, 0 Jan 7 18:18 network crw--- 1 root wheel 232, 1 Jan 7 18:18 nfs4 crw-rw-rw- 1 root wheel 2, 2 Jan 7 18:18 null crw-r--r-- 1 root wheel 246, 0 Jan 7 18:18 pci crw--- 1 root wheel 236, 0 Jan 7 18:18 ppi0 crw-rw-rw- 1 root wheel 234, 1 Jan 7 18:18 psm0 crw-rw-rw- 1 root wheel 245, 0 Jan 7 18:18 random lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stderr - fd/2 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdin - fd/0 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdout - fd/1 crw--- 1 root wheel 247, 128 Jan 7 18:18 sysmouse crw--- 1 root wheel 239, 0 Jan 7 18:18 ttyd0 crw--- 1 root wheel 239, 1 Jan 7 18:18 ttyd1 crw--- 1 root wheel 238, 32 Jan 7 18:18 ttyid0 crw--- 1 root wheel 238, 33 Jan 7 18:18 ttyid1 crw--- 1 root wheel 238, 64 Jan 7 18:18 ttyld0 crw--- 1 root wheel 238, 65 Jan 7 18:18 ttyld1 crw--- 1 root tty 233, 0 Jan 7 18:21 ttyv0 crw--- 1 root wheel 233, 1 Jan 7 18:18 ttyv1 crw--- 1 root wheel 233, 2 Jan 7 18:18 ttyv2 crw--- 1 root wheel 233, 3 Jan 7 18:18 ttyv3 crw--- 1 root wheel 233, 4 Jan 7 18:18 ttyv4 crw--- 1 root wheel 233, 5 Jan 7 18:18 ttyv5 crw--- 1 root wheel 233, 6 Jan 7 18:18 ttyv6 crw--- 1 root wheel 233, 7 Jan 7 18:18 ttyv7 crw--- 1 root wheel 233, 8 Jan 7 18:18 ttyv8 crw--- 1 root wheel 233, 9 Jan 7 18:18 ttyv9 crw--- 1 root wheel 233, 10 Jan 7 18:18 ttyva crw--- 1 root wheel 233, 11 Jan 7 18:18 ttyvb crw--- 1 root wheel 233, 12 Jan 7 18:18 ttyvc crw--- 1 root wheel 233, 13 Jan 7 18:18 ttyvd crw--- 1 root wheel 233, 14 Jan 7 18:18 ttyve crw--- 1 root wheel 233, 15 Jan 7 18:18 ttyvf crw-r--r-- 1 root operator 241, 0 Jan 7 18:18 ugen0 crw-r--r-- 1 root operator 241, 1 Jan 7 18:18 ugen0.1 crw-r--r-- 1 root operator 241, 2 Jan 7 18:18 ugen0.2 crw-r--r-- 1 root operator 241, 3 Jan 7 18:18 ugen0.3 lrwxr-xr-x 1 root wheel6 Jan 7 18:18 urandom - random crw-rw 1 root operator 240, 255 Jan 7 18:18 usb crw-rw 1 root operator 240, 0 Jan 7 18:18 usb0 crw--- 1 root operator 229, 0 Jan 7 18:18 xpt0 crw-rw-rw- 1 root wheel 2, 12 Jan 7 18:18 zero FreeBSD v.5.3. problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone. 1. kernel_config.txt, Kernel_config.hints.txt - Compiled kernel with this setting(file) 2. boot_defaults_loader.conf.txt - This is a file from /boot/defaults.conf 3. etc_rc.conf.txt - This is a file from /etc/rc.conf 4. var_log_messages.txt - This is a log file from /var/log/messages 5. console_out_usbdevs_v.txt- Command usbdevs -s after run in console out text conteined in this file 6. dmesg.txt - Conteind data out after run programm dmesg in console 7. ls_dev.txt - conteined data out after run command ls /dev device /dev/ucom0 not created in any way. What me do with my problem say me please. sanc you.Jan 7 18:18:20 backup kernel: Copyright (c) 1992-2004 The FreeBSD Project. Jan 7 18:18:20 backup kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 7 18:18:20 backup kernel: The Regents of the University of California. All rights reserved. Jan 7 18:18:20 backup kernel: FreeBSD 5.3-RELEASE #0: Wed Jan 4 08:23:58 UTC 2006 Jan 7 18:18:20 backup kernel: [EMAIL PROTECTED]:/usr/src/sys/i386/compile/gooroo Jan 7 18:18:20 backup kernel: module_register: module uhub/ugen already exists! Jan 7 18:18:20 backup kernel: Module uhub/ugen failed to register: 17 Jan 7 18:18:20 backup kernel: module_register: module uhub/uhid already exists! Jan 7 18:18:20 backup kernel: Module uhub/uhid failed to register: 17 Jan 7 18:18:20 backup kernel
Problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone.
wheel 230, 0 Jan 7 18:18 devstat dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 fd crw--- 1 root wheel 250, 0 Jan 7 18:18 fido crw-r- 1 root operator 252, 0 Jan 7 18:18 geom.ctl crw--- 1 root wheel 248, 14 Jan 7 18:18 io lrwxr-xr-x 1 root wheel6 Jan 7 18:18 kbd0 - atkbd0 crw--- 1 root wheel 7, 0 Jan 7 18:18 klog crw-r- 1 root kmem 249, 1 Jan 7 18:18 kmem lrwxr-xr-x 1 root wheel 12 Jan 7 18:18 log - /var/run/log crw--- 1 root wheel 237, 0 Jan 7 18:18 lpt0 crw--- 1 root wheel 237, 128 Jan 7 18:18 lpt0.ctl crw--- 1 root wheel 231, 0x00ff Jan 7 18:18 mdctl crw-r- 1 root kmem 249, 0 Jan 7 18:18 mem dr-xr-xr-x 2 root wheel 512 Jan 7 18:18 net lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net1 - net/rl0 lrwxr-xr-x 1 root wheel9 Jan 7 18:18 net2 - net/plip0 lrwxr-xr-x 1 root wheel7 Jan 7 18:18 net3 - net/lo0 crw--- 1 root wheel 253, 0 Jan 7 18:18 network crw--- 1 root wheel 232, 1 Jan 7 18:18 nfs4 crw-rw-rw- 1 root wheel 2, 2 Jan 7 18:18 null crw-r--r-- 1 root wheel 246, 0 Jan 7 18:18 pci crw--- 1 root wheel 236, 0 Jan 7 18:18 ppi0 crw-rw-rw- 1 root wheel 234, 1 Jan 7 18:18 psm0 crw-rw-rw- 1 root wheel 245, 0 Jan 7 18:18 random lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stderr - fd/2 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdin - fd/0 lrwxr-xr-x 1 root wheel4 Jan 7 18:18 stdout - fd/1 crw--- 1 root wheel 247, 128 Jan 7 18:18 sysmouse crw--- 1 root wheel 239, 0 Jan 7 18:18 ttyd0 crw--- 1 root wheel 239, 1 Jan 7 18:18 ttyd1 crw--- 1 root wheel 238, 32 Jan 7 18:18 ttyid0 crw--- 1 root wheel 238, 33 Jan 7 18:18 ttyid1 crw--- 1 root wheel 238, 64 Jan 7 18:18 ttyld0 crw--- 1 root wheel 238, 65 Jan 7 18:18 ttyld1 crw--- 1 root tty 233, 0 Jan 7 18:21 ttyv0 crw--- 1 root wheel 233, 1 Jan 7 18:18 ttyv1 crw--- 1 root wheel 233, 2 Jan 7 18:18 ttyv2 crw--- 1 root wheel 233, 3 Jan 7 18:18 ttyv3 crw--- 1 root wheel 233, 4 Jan 7 18:18 ttyv4 crw--- 1 root wheel 233, 5 Jan 7 18:18 ttyv5 crw--- 1 root wheel 233, 6 Jan 7 18:18 ttyv6 crw--- 1 root wheel 233, 7 Jan 7 18:18 ttyv7 crw--- 1 root wheel 233, 8 Jan 7 18:18 ttyv8 crw--- 1 root wheel 233, 9 Jan 7 18:18 ttyv9 crw--- 1 root wheel 233, 10 Jan 7 18:18 ttyva crw--- 1 root wheel 233, 11 Jan 7 18:18 ttyvb crw--- 1 root wheel 233, 12 Jan 7 18:18 ttyvc crw--- 1 root wheel 233, 13 Jan 7 18:18 ttyvd crw--- 1 root wheel 233, 14 Jan 7 18:18 ttyve crw--- 1 root wheel 233, 15 Jan 7 18:18 ttyvf crw-r--r-- 1 root operator 241, 0 Jan 7 18:18 ugen0 crw-r--r-- 1 root operator 241, 1 Jan 7 18:18 ugen0.1 crw-r--r-- 1 root operator 241, 2 Jan 7 18:18 ugen0.2 crw-r--r-- 1 root operator 241, 3 Jan 7 18:18 ugen0.3 lrwxr-xr-x 1 root wheel6 Jan 7 18:18 urandom - random crw-rw 1 root operator 240, 255 Jan 7 18:18 usb crw-rw 1 root operator 240, 0 Jan 7 18:18 usb0 crw--- 1 root operator 229, 0 Jan 7 18:18 xpt0 crw-rw-rw- 1 root wheel 2, 12 Jan 7 18:18 zero FreeBSD v.5.3. problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone. 1. kernel_config.txt, Kernel_config.hints.txt - Compiled kernel with this setting(file) 2. boot_defaults_loader.conf.txt - This is a file from /boot/defaults.conf 3. etc_rc.conf.txt - This is a file from /etc/rc.conf 4. var_log_messages.txt - This is a log file from /var/log/messages 5. console_out_usbdevs_v.txt- Command usbdevs -s after run in console out text conteined in this file 6. dmesg.txt - Conteind data out after run programm dmesg in console 7. ls_dev.txt - conteined data out after run command ls /dev device /dev/ucom0 not created in any way. What me do with my problem say me please. sanc you.Jan 7 18:18:20 backup kernel: Copyright (c) 1992-2004 The FreeBSD Project. Jan 7 18:18:20 backup kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 7 18:18:20 backup kernel: The Regents of the University of California. All rights reserved. Jan 7 18:18:20 backup kernel: FreeBSD 5.3-RELEASE #0: Wed Jan 4 08:23:58 UTC 2006 Jan 7 18:18:20 backup kernel: [EMAIL PROTECTED]:/usr/src/sys/i386/compile/gooroo Jan 7 18:18:20 backup kernel: module_register: module uhub/ugen already exists! Jan 7 18:18:20 backup kernel: Module uhub/ugen failed to register: 17 Jan 7 18:18:20 backup kernel: module_register: module uhub/uhid already exists! Jan 7 18:18:20 backup kernel: Module uhub/uhid failed to register: 17 Jan 7 18:18:20 backup kernel
Re: Problem in install USB data cabel (based on prolific 2303 chip) for Siemens C72 mobile phone.
On Saturday, 7 January 2006 at 19:10:33 +0200, [EMAIL PROTECTED] wrote: On Saturday, 7 January 2006 at 21:12:04 +0200, [EMAIL PROTECTED] wrote: On Saturday, 7 January 2006 at 21:12:04 +0200, [EMAIL PROTECTED] wrote: On Saturday, 7 January 2006 at 21:14:19 +0200, [EMAIL PROTECTED] wrote: # This is loader.conf - a file full of useful variables that you can # set to change the default load behavior of your system. Only yesterday I replied to another message of yours suggesting that you should read http://www.lemis.com/questions.html. You appear not to have done so. There you would have read: When submitting a question to FreeBSD-questions, consider the following points: 1. Remember that nobody gets paid for answering a FreeBSD question. They do it of their own free will. You can influence this free will positively by submitting a well-formulated question supplying as much relevant information as possible. You can influence this free will negatively by submitting an incomplete, illegible, or rude question. ... 6. Specify as much information as possible. * In nearly every case, it's important to know the version of FreeBSD you're running. This is particularly the case for FreeBSD-CURRENT, where you should also specify the date of the sources, though of course you shouldn't be sending questions about -CURRENT to FreeBSD-questions. * With any problem which could be hardware related, tell us about your hardware. In case of doubt, assume it's possible that it's hardware. What kind of CPU are you using? How fast? What motherboard? How much memory? What peripherals? * If you get error messages, don't say I get error messages, say (for example) I get the error message 'No route to host'. You have driven this problem to extremes by not specifying any problem at all. 7. If you do all this, and you still don't get an answer, there could be other reasons. For example, the problem is so complicated that nobody knows the answer, or the person who does know the answer was offline. If you don't get an answer after, say, a week, it might help to re-send the message. If you don't get an answer to your second message, though, you're probably not going to get one from this forum. Resending the same message again and again will only make you unpopular. You sent the same message four times in two hours. You didn't state a problem, so you were lucky to get any kind of reply at all. You won't get a solution to your problem until you describe it. Please don't send any more messages until you have something to say. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgpZ3wGlIwcD0.pgp Description: PGP signature
Re: Problem with install GCC4.2
Stop in /usr/ports/lang/gcc42. --- Sorry for big log, but I do not know what I need to send. What I need to do? 2. I update src and ports throught cvsup. Please explain me, how I can update may system to FreeBSD 6.0 Stable? What I need to change in my supfile and do after this? My supfile --- *default host=cvsup5.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs *default tag=RELENG_5 *default delete use-rel-suffix *default compress src-all ports-all tag=. doc-all tag=. --- -- Best regards, Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] change RELENG_5 to RELENG_6 -- Димитър Василев Dimitar Vassilev GnuPG key ID: 0x4B8DB525 Keyserver: pgp.mit.edu Key fingerprint: D88A 3B92 DED5 917E 341E D62F 8C51 5FC4 4B8D B525 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with install GCC4.2
Hallo all! I have a FreeBSD 5.3. 1. Try to install the GCC 4.2 from ports, but I get a error(see a attachment log.gz). What I need to do? 2. I update src and ports throught cvsup. In attachment cvsup.gz my supfile. Please explain me, how I can update may system to FreeBSD 6.0 Stable? What I need to change in my supfile and do after this? -- Best regards. Anton___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem: cannot install on Dell 400SC
Looks to me as if the SCSI controller card is buggy. Try disabling search other LUNS. OK. I did that with no noticable difference. I did notice, though, in monkeying around that the fdisk did appear to write the boot block. When I let it go on and boot without any CD or floppy in it, the FreeBSD boot record attempted to start and of course, couldn't find a kernel since one hadn't been written. So, I tried again and first had Partition Magic make two slices with a DOS Fat32 on the first and the second unformatted, then had the FreeBSD installer write the FreeBSD MBR and it seemed to do so just fine, even though the newfses still failed on the partitions, so no filesystems were built and nothing installed. When I rebooted, it came up with the typical FreeBSD MBR question F1 - DOS F2 - FreeBSD Hittint F2 made it read the FreeBSD boot block on the second slice. But, of course it couldn't really boot any farther than that because no filesystems or kernel were there. So, it still makes me thing that FreeBSD can talk at least some to that combination of LSIL 53C1030 controller and Fujitsu hard disk. It writes the slice table, label, MBR and boot block. But, then it can't do anything else. Any other [positive] suggestions will be appreciated. jerry BSDBoy -Original Message- Is the SCSI channel terminated properly? What is the LUN of the HDD? The SCSI cable appears to be terminated. It has a terminator block on the end of the cable just past the hard drive. As for the LUN, I think it would be '0' on channel 'B' if I am making sense of the BIOS screen. Once I get that close to the hardware, I am getting out of my level. It has a setting that says scan LUNs greater than 0 and that is set to yes by default. The SCSI itself appears to be set to LUN 7, by the way. jerry BSDBoy Hi, I am hoping someone can give us some clues about this problem. A couple of us have done some searching, but found nothing that bears directly on it. Maybe some different search clues might also help. I am hoping for more than just it won't work, because... but, even a conclusive one of those would get us off the point - which begins to dig in after a while... Sorry this is rather long, but I wanted to include anything that might possibly be relevant. Here goes. One of our sites recently purchased a Dell Poweredge 400SC and wants to run our school district network server system on it. Our system is currently based on FreeBSD 4.9 with some modifications to control the initial installation and aid in system management. We have it running on a number of other Dell Poweredge machines but not this particular model and especially not the LSIL SCSI controller. It has a 2.4G Celeron CPU, 1 GB Memory Planar PE400SC, A/N, 2 Motherboard LSI Logics 53C1030 SCSI controller Fujitsu 36GB MAP337NP SCSI U320, 10K, 68 Pin connector hard drive. + NIC, IDE controller, CDROM, Tape drive, etc. Although this model was not our recommendation, it would look like, on paper, that it should at least, function. But,,, We cannot get any FreeBSD system to install on it, not ours or even a straight FreeBSD 4.9 or 5.2.1 system - and I just tried 4.10 too with the same result. It reads the CD, boots into the sysinstall or our install system just fine. It appears to do the fdisk and disklabel just fine. Then it hangs or appears to hang trying to do the newfs. It puts out the message about writing superblocks and then nothing more comes out - no list of superblocks of any kind, not even the first. I have made up variations on our version of sysinstall with additional messages but have not gotten any information that means anything to me. After a wait of several minutes it writes stuff to the ALT console. If I let it set long enough (hours) it puts out a failed message. I didn't have any MS install media handy, But did have my Partition Magic emergency boot floppies around so I used them to take a look after having attempted to do first our install, then FreeBSD 4.9 and finally FreeBSD 5.2.1. PM quite happily looked at things and recognized the FreeBSD slice (which, of course it called a partition). So, I deleted the slice and created two and used the FreeBSD install CD to attempt to install on the second slice (da0s2) which it seemed happy to do.After checking again with PM and seeing that the new slicing had the FreeBSD id one it I popped in another FreeBSD cd and sysinstall happily read up that label with all the FreeBSD partitions (a,b,e,f,g,h) that I had made. So, FreeBSD can obviously write some part of the disk. But, newfs still would get to writing superblocks and then nothing more happened. That is the thing that seems odd to me. It does write to some part of the disk,
Re: Problem: cannot install on Dell 400SC
Is the SCSI channel terminated properly? What is the LUN of the HDD? The SCSI cable appears to be terminated. It has a terminator block on the end of the cable just past the hard drive. As for the LUN, I think it would be '0' on channel 'B' if I am making sense of the BIOS screen. Once I get that close to the hardware, I am getting out of my level. It has a setting that says scan LUNs greater than 0 and that is set to yes by default. The SCSI itself appears to be set to LUN 7, by the way. jerry BSDBoy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerry McAllister Sent: Wednesday, June 09, 2004 4:57 To: [EMAIL PROTECTED] Cc: Jerry McAllister Subject: Problem: cannot install on Dell 400SC Hi, I am hoping someone can give us some clues about this problem. A couple of us have done some searching, but found nothing that bears directly on it. Maybe some different search clues might also help. I am hoping for more than just it won't work, because... but, even a conclusive one of those would get us off the point - which begins to dig in after a while... Sorry this is rather long, but I wanted to include anything that might possibly be relevant. Here goes. One of our sites recently purchased a Dell Poweredge 400SC and wants to run our school district network server system on it. Our system is currently based on FreeBSD 4.9 with some modifications to control the initial installation and aid in system management. We have it running on a number of other Dell Poweredge machines but not this particular model and especially not the LSIL SCSI controller. It has a 2.4G Celeron CPU, 1 GB Memory Planar PE400SC, A/N, 2 Motherboard LSI Logics 53C1030 SCSI controller Fujitsu 36GB MAP337NP SCSI U320, 10K, 68 Pin connector hard drive. + NIC, IDE controller, CDROM, Tape drive, etc. Although this model was not our recommendation, it would look like, on paper, that it should at least, function. But,,, We cannot get any FreeBSD system to install on it, not ours or even a straight FreeBSD 4.9 or 5.2.1 system - and I just tried 4.10 too with the same result. It reads the CD, boots into the sysinstall or our install system just fine. It appears to do the fdisk and disklabel just fine. Then it hangs or appears to hang trying to do the newfs. It puts out the message about writing superblocks and then nothing more comes out - no list of superblocks of any kind, not even the first. I have made up variations on our version of sysinstall with additional messages but have not gotten any information that means anything to me. After a wait of several minutes it writes stuff to the ALT console. If I let it set long enough (hours) it puts out a failed message. I didn't have any MS install media handy, But did have my Partition Magic emergency boot floppies around so I used them to take a look after having attempted to do first our install, then FreeBSD 4.9 and finally FreeBSD 5.2.1. PM quite happily looked at things and recognized the FreeBSD slice (which, of course it called a partition). So, I deleted the slice and created two and used the FreeBSD install CD to attempt to install on the second slice (da0s2) which it seemed happy to do.After checking again with PM and seeing that the new slicing had the FreeBSD id one it I popped in another FreeBSD cd and sysinstall happily read up that label with all the FreeBSD partitions (a,b,e,f,g,h) that I had made. So, FreeBSD can obviously write some part of the disk. But, newfs still would get to writing superblocks and then nothing more happened. That is the thing that seems odd to me. It does write to some part of the disk, enough to write label information. But, it does not seem to be able to do any other type of write to the disk. So, are the writes so different that a controller can handle one and not the other? There are several LSIL SCSI controllers listed in the hardware list and some in the 53C series, but not exactly 53C1030. Can the write be enough similar to handle labels, but not other stuff? One of the other people in our group put Linux on it - Debian I believe - and it appeared to install and write the disk just fine. So, I take that to mean that it isn't really just a flawed disk, though I suppose that is still possible. So, here is a blow-by-blow using any of the FreeBSD RELEASE cds I happen to have handy (4.9. 5.2.1 and 4.10). Basically, everything looks like it is going fine until after I select commit. It happily puts up a message on the curses screen saying Making a new root filesystem on /dev/da0s1a Then it stops and appears to do no more - at least for a long time. Here are the ALT-F2 console messages from when it starts to operate on the disk: |DEBUG: Scanning disk da0 for root filesystem |DEBUG: Scanning disk
Problem: cannot install on Dell 400SC
Hi, I am hoping someone can give us some clues about this problem. A couple of us have done some searching, but found nothing that bears directly on it. Maybe some different search clues might also help. I am hoping for more than just it won't work, because... but, even a conclusive one of those would get us off the point - which begins to dig in after a while... Sorry this is rather long, but I wanted to include anything that might possibly be relevant. Here goes. One of our sites recently purchased a Dell Poweredge 400SC and wants to run our school district network server system on it. Our system is currently based on FreeBSD 4.9 with some modifications to control the initial installation and aid in system management. We have it running on a number of other Dell Poweredge machines but not this particular model and especially not the LSIL SCSI controller. It has a 2.4G Celeron CPU, 1 GB Memory Planar PE400SC, A/N, 2 Motherboard LSI Logics 53C1030 SCSI controller Fujitsu 36GB MAP337NP SCSI U320, 10K, 68 Pin connector hard drive. + NIC, IDE controller, CDROM, Tape drive, etc. Although this model was not our recommendation, it would look like, on paper, that it should at least, function. But,,, We cannot get any FreeBSD system to install on it, not ours or even a straight FreeBSD 4.9 or 5.2.1 system - and I just tried 4.10 too with the same result. It reads the CD, boots into the sysinstall or our install system just fine. It appears to do the fdisk and disklabel just fine. Then it hangs or appears to hang trying to do the newfs. It puts out the message about writing superblocks and then nothing more comes out - no list of superblocks of any kind, not even the first. I have made up variations on our version of sysinstall with additional messages but have not gotten any information that means anything to me. After a wait of several minutes it writes stuff to the ALT console. If I let it set long enough (hours) it puts out a failed message. I didn't have any MS install media handy, But did have my Partition Magic emergency boot floppies around so I used them to take a look after having attempted to do first our install, then FreeBSD 4.9 and finally FreeBSD 5.2.1. PM quite happily looked at things and recognized the FreeBSD slice (which, of course it called a partition). So, I deleted the slice and created two and used the FreeBSD install CD to attempt to install on the second slice (da0s2) which it seemed happy to do.After checking again with PM and seeing that the new slicing had the FreeBSD id one it I popped in another FreeBSD cd and sysinstall happily read up that label with all the FreeBSD partitions (a,b,e,f,g,h) that I had made. So, FreeBSD can obviously write some part of the disk. But, newfs still would get to writing superblocks and then nothing more happened. That is the thing that seems odd to me. It does write to some part of the disk, enough to write label information. But, it does not seem to be able to do any other type of write to the disk. So, are the writes so different that a controller can handle one and not the other? There are several LSIL SCSI controllers listed in the hardware list and some in the 53C series, but not exactly 53C1030. Can the write be enough similar to handle labels, but not other stuff? One of the other people in our group put Linux on it - Debian I believe - and it appeared to install and write the disk just fine. So, I take that to mean that it isn't really just a flawed disk, though I suppose that is still possible. So, here is a blow-by-blow using any of the FreeBSD RELEASE cds I happen to have handy (4.9. 5.2.1 and 4.10). Basically, everything looks like it is going fine until after I select commit. It happily puts up a message on the curses screen saying Making a new root filesystem on /dev/da0s1a Then it stops and appears to do no more - at least for a long time. Here are the ALT-F2 console messages from when it starts to operate on the disk: |DEBUG: Scanning disk da0 for root filesystem |DEBUG: Scanning disk da0 for swap filesystem |Warning: Block size and bytes per inode restrict cylinders per group to 89 | |/dev/da0s1a1048576 Sectors in 256 Cylinders of 1 tracks, 4096 sectors | 512,0 MG in 3 cylinder groups (89 c/g, 178.00 MG/g, 21632 i/g) | |Super-block backups (for fsck -b #) at: | | Here we get a long wait | |mpt1: time out on request index = 0xfe sequence=0x00e8 |mpt1: Status 0001; Mask 0001; Doorbell 2400 |request State on CHip |SCSI IO Request @ 0xc038b0b0 | Chain Offset 0x10 | Msg Flags 0x00 | Msg Content 0x00fe | Bus: 0 | TargetID 0 | Sense Buffer Length 32 | LUN: 0x0 | Control 0x0106 WRITE SIMPLEQ |
Problem to install 5.2.1 on SATA disk chipset VT8237
Hi, Freebsd Release 5.2.1 i've bought a Gigabyte GA-7VM400MF-P with the chipset VIA KM400 and VIA VT8237 for the controller i've harddrive on the sata controller, and boot sysinstall from the cdrom, all start well but the harddrives aren't recognized..? there is no disks... so after, i've tried this trick: i've installed freebsd on the harddisk attached to the ata controller and reboot with the hardrive on the sata controller, but it doesn't work ... Someone has got another the solution ? why freebsd doesn't recognize the SATA disk in my case ? thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disk problem at install (Signal 11).
Hi, I've just come to install FreeBSD 5.1-RELEASE on a new machine. It's got four disks in it, but right now I'm only working with one (ad0), which is a 30GB disk that's been lying about for a bit. I'm getting: DEBUG: Scanning disk ad0 for swap partitions ad0: hard error cmd=read fsbn 0 status=51 error=04 DEBUG: Signal 11 caught! That's bad! on the debug console just after I hit okay after defining my slices. I'm guessing this is a hardware problem (well, the ``hard error'' gives that away) but does anybody know if this is very serious, or... ? Can I work around it, or is the disk for the bin? Thanks very much, -lewiz. -- I was so much older then, I'm younger than that now. --Bob Dylan, 1964. -| msn:[EMAIL PROTECTED] | jab:[EMAIL PROTECTED] | url:http://lewiz.net |- pgp0.pgp Description: PGP signature
Re: Disk problem at install (Signal 11).
On Sun, Sep 14, 2003 at 12:49:22AM +0100, Lewis Thompson wrote: Hi, I've just come to install FreeBSD 5.1-RELEASE on a new machine. It's got four disks in it, but right now I'm only working with one (ad0), which is a 30GB disk that's been lying about for a bit. I'm getting: DEBUG: Scanning disk ad0 for swap partitions ad0: hard error cmd=read fsbn 0 status=51 error=04 DEBUG: Signal 11 caught! That's bad! on the debug console just after I hit okay after defining my slices. I'm guessing this is a hardware problem (well, the ``hard error'' gives that away) but does anybody know if this is very serious, or... ? Can I work around it, or is the disk for the bin? The disk is failing..pitch it. Kris pgp0.pgp Description: PGP signature
Re: Disk problem at install (Signal 11).
On Sat, Sep 13, 2003 at 06:01:37PM -0700, Kris Kennaway wrote: On Sun, Sep 14, 2003 at 12:49:22AM +0100, Lewis Thompson wrote: DEBUG: Scanning disk ad0 for swap partitions ad0: hard error cmd=read fsbn 0 status=51 error=04 DEBUG: Signal 11 caught! That's bad! The disk is failing..pitch it. Bah! How did I know you'd say that! Ho-hum *CRASH*. Thanks very much, -lewiz. -- I was so much older then, I'm younger than that now. --Bob Dylan, 1964. -| msn:[EMAIL PROTECTED] | jab:[EMAIL PROTECTED] | url:http://lewiz.net |- pgp0.pgp Description: PGP signature
Re: problem with install
On Thu, Feb 13, 2003 at 10:41:17PM -0800, joseph grundy wrote: I just went through the bios, I can only change acpi from state 1 to state 3 both still give the same problem. I don't know what else I can do, unless there is a way to install without acpi somehow. Sorry forget what i have suggested for it is wrong. You said that you have tried it with 4.x releases as well, they dont have apci support at all, so the problem can't be there. cheers, tom To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: problem with install
Hi Joseph, You can disable the ACPI module in the boot process. When you see the message Hit enter or wait 10 seconds to boot press enter and type: unset acpi_load boot This way, the installation will happen without load the module ACPI. Hope this helps. Cheers, Marcos Silva Rio - Brazil -Mensagem original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Em nome de joseph grundy Enviada em: sexta-feira, 14 de fevereiro de 2003 03:41 Para: [EMAIL PROTECTED] Assunto: RE: problem with install I just went through the bios, I can only change acpi from state 1 to state 3 both still give the same problem. I don't know what else I can do, unless there is a way to install without acpi somehow. Joseph Hello how would I disable acpi? I do not know what it goes to in the bios. Thanks Hi, On Thu, Feb 13, 2003 at 09:55:49PM -0800, joseph grundy wrote: I am having problems trying to install FreeBSD. I have installed in before on different machines, but now this is the only one I have. I would like to have FreeBSD as my main OS on the machine. When I put in the bootable cd and restart the computer, I get to the boot section where it says Hit enter or wait 9 seconds to boot I hit enter and get the follow /boot/kernel/acpi.ko test=0x3985c data=0x1978+0xb2k sysms=[0x4+0x6010+0x4+0x7994 ] then the line below it is spinning and stops and freezes. it seems that there is a problem with the acpi kernel module. Can you disable acpi in you bios? If yes, try booting without acpi. Or maybe you can disable some modules in the boot loader menu (but im not sure about that). I have tried 4.2, 4.4, 4.7. and 5.0 releases all lock in the same place. I have windows 2000 server on first 40 gigs of a 60 gig HD. Inside the machine are Intel 850 MV motherboard 2 256 sticks of rambus and 2 dummy cards to terminate unused memory slots geforce 3 Audigy Plat Intel 10/100 pro NIC adaptec 2940 scsi card dvd player ( used for install ) cdrw scsi cd rom scsi secondary 60 gig HD Sorry, these are just suggestions as i dont know where the problem really is... cheers, tom To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message **PRIVILEGED AND CONFIDENTIAL INFORMATION** The information contained in this document is intended solely for use by the persons or entities identified above. This electronically transmitted document contains privileged and confidential information including information which may be protected by the attorney-client and/or work product privileges. If you are not the intended recipient, be aware that any disclosure, copying, distribution or other use of the contents of this transmission is prohibited. If you received this transmission in error, please delete this message without making a copy. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: problem with install
Since you have tried FBSD 4.3, 4.4, 4.7, 5.0 I would say that the problem is not an FBSD problem but a problem with the hard ware of the box you are installing FBSD onto. From your description of what you have done to fix the problem, I can see that you started to use the process of elimination method to debug the problem. You need to continue using this method. First of all I have never heard of ever needing dummy cards to terminate unused memory slots. Remove them. Also strip down your PC to bare bones. Remove SCSI control card from PC PCI bus and unplug power supplies from all SCSI devices. Only have IDE hard drive and IDE CDROM drive and install FBSD to see if it works. If that works then you know you have problem with SCSI control card. If SCSI control is old style ISA card you may have bio's irq assignment problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of joseph grundy Sent: Friday, February 14, 2003 12:56 AM To: [EMAIL PROTECTED] Subject: problem with install I am having problems trying to install FreeBSD. I have installed in before on different machines, but now this is the only one I have. I would like to have FreeBSD as my main OS on the machine. When I put in the bootable cd and restart the computer, I get to the boot section where it says Hit enter or wait 9 seconds to boot I hit enter and get the follow /boot/kernel/acpi.ko test=0x3985c data=0x1978+0xb2k sysms=[0x4+0x6010+0x4+0x7994 ] then the line below it is spinning and stops and freezes. I have tried 4.2, 4.4, 4.7. and 5.0 releases all lock in the same place. I have windows 2000 server on first 40 gigs of a 60 gig HD. Inside the machine are Intel 850 MV motherboard 2 256 sticks of rambus and 2 dummy cards to terminate unused memory slots geforce 3 Audigy Plat Intel 10/100 pro NIC adaptec 2940 scsi card dvd player ( used for install ) cdrw scsi cd rom scsi secondary 60 gig HD Now I have tried with 3com nic instead, I have taken all cards out and only had graphics, primary HD and cd rom. I also updated the BIOS of the Motherboard and I still get the same freeze in the same spot. I don't know what might be the problem I have looked all over and tried many things, I have been working on this install for 2 days now. Any idea's or help, I would be grateful Joseph **PRIVILEGED AND CONFIDENTIAL INFORMATION** The information contained in this document is intended solely for use by the persons or entities identified above. This electronically transmitted document contains privileged and confidential information including information which may be protected by the attorney-client and/or work product privileges. If you are not the intended recipient, be aware that any disclosure, copying, distribution or other use of the contents of this transmission is prohibited. If you received this transmission in error, please delete this message without making a copy. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: problem with install
I believe some types of RAM need a terminator card in some slots on some mobos ... IIRC, RDRAM often ran into this, particularly when the mobo could use multiple types of RAM. -Matt On Fri, 2003-02-14 at 12:07, JoeB wrote: Since you have tried FBSD 4.3, 4.4, 4.7, 5.0 I would say that the problem is not an FBSD problem but a problem with the hard ware of the box you are installing FBSD onto. From your description of what you have done to fix the problem, I can see that you started to use the process of elimination method to debug the problem. You need to continue using this method. First of all I have never heard of ever needing dummy cards to terminate unused memory slots. Remove them. Also strip down your PC to bare bones. Remove SCSI control card from PC PCI bus and unplug power supplies from all SCSI devices. Only have IDE hard drive and IDE CDROM drive and install FBSD to see if it works. If that works then you know you have problem with SCSI control card. If SCSI control is old style ISA card you may have bio's irq assignment problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of joseph grundy Sent: Friday, February 14, 2003 12:56 AM To: [EMAIL PROTECTED] Subject: problem with install I am having problems trying to install FreeBSD. I have installed in before on different machines, but now this is the only one I have. I would like to have FreeBSD as my main OS on the machine. When I put in the bootable cd and restart the computer, I get to the boot section where it says Hit enter or wait 9 seconds to boot I hit enter and get the follow /boot/kernel/acpi.ko test=0x3985c data=0x1978+0xb2k sysms=[0x4+0x6010+0x4+0x7994 ] then the line below it is spinning and stops and freezes. I have tried 4.2, 4.4, 4.7. and 5.0 releases all lock in the same place. I have windows 2000 server on first 40 gigs of a 60 gig HD. Inside the machine are Intel 850 MV motherboard 2 256 sticks of rambus and 2 dummy cards to terminate unused memory slots geforce 3 Audigy Plat Intel 10/100 pro NIC adaptec 2940 scsi card dvd player ( used for install ) cdrw scsi cd rom scsi secondary 60 gig HD Now I have tried with 3com nic instead, I have taken all cards out and only had graphics, primary HD and cd rom. I also updated the BIOS of the Motherboard and I still get the same freeze in the same spot. I don't know what might be the problem I have looked all over and tried many things, I have been working on this install for 2 days now. Any idea's or help, I would be grateful Joseph **PRIVILEGED AND CONFIDENTIAL INFORMATION** The information contained in this document is intended solely for use by the persons or entities identified above. This electronically transmitted document contains privileged and confidential information including information which may be protected by the attorney-client and/or work product privileges. If you are not the intended recipient, be aware that any disclosure, copying, distribution or other use of the contents of this transmission is prohibited. If you received this transmission in error, please delete this message without making a copy. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Matt Smith [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
problem with install
I am having problems trying to install FreeBSD. I have installed in before on different machines, but now this is the only one I have. I would like to have FreeBSD as my main OS on the machine. When I put in the bootable cd and restart the computer, I get to the boot section where it says Hit enter or wait 9 seconds to boot I hit enter and get the follow /boot/kernel/acpi.ko test=0x3985c data=0x1978+0xb2k sysms=[0x4+0x6010+0x4+0x7994 ] then the line below it is spinning and stops and freezes. I have tried 4.2, 4.4, 4.7. and 5.0 releases all lock in the same place. I have windows 2000 server on first 40 gigs of a 60 gig HD. Inside the machine are Intel 850 MV motherboard 2 256 sticks of rambus and 2 dummy cards to terminate unused memory slots geforce 3 Audigy Plat Intel 10/100 pro NIC adaptec 2940 scsi card dvd player ( used for install ) cdrw scsi cd rom scsi secondary 60 gig HD Now I have tried with 3com nic instead, I have taken all cards out and only had graphics, primary HD and cd rom. I also updated the BIOS of the Motherboard and I still get the same freeze in the same spot. I don't know what might be the problem I have looked all over and tried many things, I have been working on this install for 2 days now. Any idea's or help, I would be grateful Joseph **PRIVILEGED AND CONFIDENTIAL INFORMATION** The information contained in this document is intended solely for use by the persons or entities identified above. This electronically transmitted document contains privileged and confidential information including information which may be protected by the attorney-client and/or work product privileges. If you are not the intended recipient, be aware that any disclosure, copying, distribution or other use of the contents of this transmission is prohibited. If you received this transmission in error, please delete this message without making a copy. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: problem with install
Hi, On Thu, Feb 13, 2003 at 09:55:49PM -0800, joseph grundy wrote: I am having problems trying to install FreeBSD. I have installed in before on different machines, but now this is the only one I have. I would like to have FreeBSD as my main OS on the machine. When I put in the bootable cd and restart the computer, I get to the boot section where it says Hit enter or wait 9 seconds to boot I hit enter and get the follow /boot/kernel/acpi.ko test=0x3985c data=0x1978+0xb2k sysms=[0x4+0x6010+0x4+0x7994 ] then the line below it is spinning and stops and freezes. it seems that there is a problem with the acpi kernel module. Can you disable acpi in you bios? If yes, try booting without acpi. Or maybe you can disable some modules in the boot loader menu (but im not sure about that). I have tried 4.2, 4.4, 4.7. and 5.0 releases all lock in the same place. I have windows 2000 server on first 40 gigs of a 60 gig HD. Inside the machine are Intel 850 MV motherboard 2 256 sticks of rambus and 2 dummy cards to terminate unused memory slots geforce 3 Audigy Plat Intel 10/100 pro NIC adaptec 2940 scsi card dvd player ( used for install ) cdrw scsi cd rom scsi secondary 60 gig HD Sorry, these are just suggestions as i dont know where the problem really is... cheers, tom To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: problem with install
Hello how would I disable acpi? I do not know what it goes to in the bios. Thanks -Original Message- From: Thomas Spreng [mailto:[EMAIL PROTECTED]] Sent: Thu 2/13/2003 10:10 PM To: [EMAIL PROTECTED] Cc: Subject: Re: problem with install Hi, On Thu, Feb 13, 2003 at 09:55:49PM -0800, joseph grundy wrote: I am having problems trying to install FreeBSD. I have installed in before on different machines, but now this is the only one I have. I would like to have FreeBSD as my main OS on the machine. When I put in the bootable cd and restart the computer, I get to the boot section where it says Hit enter or wait 9 seconds to boot I hit enter and get the follow /boot/kernel/acpi.ko test=0x3985c data=0x1978+0xb2k sysms=[0x4+0x6010+0x4+0x7994 ] then the line below it is spinning and stops and freezes. it seems that there is a problem with the acpi kernel module. Can you disable acpi in you bios? If yes, try booting without acpi. Or maybe you can disable some modules in the boot loader menu (but im not sure about that). I have tried 4.2, 4.4, 4.7. and 5.0 releases all lock in the same place. I have windows 2000 server on first 40 gigs of a 60 gig HD. Inside the machine are Intel 850 MV motherboard 2 256 sticks of rambus and 2 dummy cards to terminate unused memory slots geforce 3 Audigy Plat Intel 10/100 pro NIC adaptec 2940 scsi card dvd player ( used for install ) cdrw scsi cd rom scsi secondary 60 gig HD Sorry, these are just suggestions as i dont know where the problem really is... cheers, tom To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message **PRIVILEGED AND CONFIDENTIAL INFORMATION** The information contained in this document is intended solely for use by the persons or entities identified above. This electronically transmitted document contains privileged and confidential information including information which may be protected by the attorney-client and/or work product privileges. If you are not the intended recipient, be aware that any disclosure, copying, distribution or other use of the contents of this transmission is prohibited. If you received this transmission in error, please delete this message without making a copy. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: problem with install
I just went through the bios, I can only change acpi from state 1 to state 3 both still give the same problem. I don't know what else I can do, unless there is a way to install without acpi somehow. Joseph Hello how would I disable acpi? I do not know what it goes to in the bios. Thanks Hi, On Thu, Feb 13, 2003 at 09:55:49PM -0800, joseph grundy wrote: I am having problems trying to install FreeBSD. I have installed in before on different machines, but now this is the only one I have. I would like to have FreeBSD as my main OS on the machine. When I put in the bootable cd and restart the computer, I get to the boot section where it says Hit enter or wait 9 seconds to boot I hit enter and get the follow /boot/kernel/acpi.ko test=0x3985c data=0x1978+0xb2k sysms=[0x4+0x6010+0x4+0x7994 ] then the line below it is spinning and stops and freezes. it seems that there is a problem with the acpi kernel module. Can you disable acpi in you bios? If yes, try booting without acpi. Or maybe you can disable some modules in the boot loader menu (but im not sure about that). I have tried 4.2, 4.4, 4.7. and 5.0 releases all lock in the same place. I have windows 2000 server on first 40 gigs of a 60 gig HD. Inside the machine are Intel 850 MV motherboard 2 256 sticks of rambus and 2 dummy cards to terminate unused memory slots geforce 3 Audigy Plat Intel 10/100 pro NIC adaptec 2940 scsi card dvd player ( used for install ) cdrw scsi cd rom scsi secondary 60 gig HD Sorry, these are just suggestions as i dont know where the problem really is... cheers, tom To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message **PRIVILEGED AND CONFIDENTIAL INFORMATION** The information contained in this document is intended solely for use by the persons or entities identified above. This electronically transmitted document contains privileged and confidential information including information which may be protected by the attorney-client and/or work product privileges. If you are not the intended recipient, be aware that any disclosure, copying, distribution or other use of the contents of this transmission is prohibited. If you received this transmission in error, please delete this message without making a copy. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
