Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Tim Kientzle <[EMAIL PROTECTED]>: On Monday 04 June 2007 17:46, Robin Gruyters wrote: This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. Maybe tar doesn't use the -b option when listing the content? (-t) Could you please send me details of the problem you're having? Ok, here a small setup. I create a random file with roughly size of 5MB: $ dd if=/dev/random of=archive.dmp bs=1024 count=5120 5120+0 records in 5120+0 records out 5242880 bytes transferred in 0.174116 secs (30111397 bytes/sec) Then a tar the file (with or without blocksize set) to tape: $ sudo tar -cf /dev/sa0 archive.dmp $ After that I try to read/list the tar from tape with tar -t: $ sudo mt -f /dev/sa0 rewind $ sudo tar -tf /dev/sa0 archive.dmp tar: Unrecognized archive format: Inappropriate file type or format $ I get strait away the "Unrecognized archive" message. But when I extract the archive from tape, it works perfectly: $ sudo tar -xvf /dev/sa0 x archive.dmp $ I have tested this with libarchive and tar from RELENG_6 and RELENG_6_2. No problems with libarchive and tar from RELENG_6_1. If you need more (debug) info, let me know Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgp5dVyZcTE26.pgp Description: PGP Digital Signature
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
On Monday 04 June 2007 17:46, Robin Gruyters wrote: This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. Hmmm... What can you tell us about your tape drive (driver being used?). Relevant lines from dmesg might be helpful. Tim Kientzle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6 buildkernel broken -- mfi/mpt commits
On Tue, Jun 05, 2007 at 04:54:36PM -0600, Scott Long wrote: > Jeremy Chadwick wrote: > > Seems some latest comments to mpt(4) and/or mfi(4) broke RELENG_6. > > Scott, this looks like your doing. *poke poke* :-) I've two separate > > boxes which now can't build world. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/mfi/mfi_cam.c > > Fixed, sorry about that. Confirmed: FreeBSD icarus.home.lan 6.2-STABLE FreeBSD 6.2-STABLE #0: Tue Jun 5 17:41:59 PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ICARUS i386 Thanks for the quick turnaround time! :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[releng_6 tinderbox] failure on i386/pc98
TB --- 2007-06-05 21:49:46 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-06-05 21:49:46 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2007-06-05 21:49:46 - cleaning the object tree TB --- 2007-06-05 21:50:54 - checking out the source tree TB --- 2007-06-05 21:50:54 - cd /tinderbox/RELENG_6/i386/pc98 TB --- 2007-06-05 21:50:54 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-06-05 22:02:36 - building world (CFLAGS=-O2 -pipe) TB --- 2007-06-05 22:02:36 - cd /src TB --- 2007-06-05 22:02:36 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2007-06-05 23:06:47 - generating LINT kernel config TB --- 2007-06-05 23:06:47 - cd /src/sys/pc98/conf TB --- 2007-06-05 23:06:47 - /usr/bin/make -B LINT TB --- 2007-06-05 23:06:47 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-06-05 23:06:47 - cd /src TB --- 2007-06-05 23:06:47 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jun 5 23:06:47 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> mem (cleandir) rm -f export_syms mem.ko mem.kld memdev.o mem.o memutil.o i686_mem.o k6_mem.o @ machine i386 bus_if.h device_if.h rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> mfi (cleandir) rm -f export_syms mfi.ko mfi.kld mfi.o mfi_pci.o mfi_disk.o mfi_debug.o @ machine i386 opt_mfi.h pci_if.h bus_if.h device_if.h ===> mfi/mfi_cam (clean) cd: can't cd to /src/sys/modules/mfi/mfi_cam *** Error code 2 Stop in /src/sys/modules/mfi. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-06-05 23:06:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-06-05 23:06:54 - ERROR: failed to build lint kernel TB --- 2007-06-05 23:06:54 - tinderbox aborted TB --- 1.27 user 3.96 system 4628.50 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6 buildkernel broken -- mfi/mpt commits
Jeremy Chadwick wrote: Seems some latest comments to mpt(4) and/or mfi(4) broke RELENG_6. Scott, this looks like your doing. *poke poke* :-) I've two separate boxes which now can't build world. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/mfi/mfi_cam.c Fixed, sorry about that. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_6 buildkernel broken -- mfi/mpt commits
Seems some latest comments to mpt(4) and/or mfi(4) broke RELENG_6.
Scott, this looks like your doing. *poke poke* :-) I've two separate
boxes which now can't build world.
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/mfi/mfi_cam.c
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
=== SNIP ===
Connecting to cvsup4.freebsd.org
Connected to 204.152.184.73
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed-mode data connection
Running
Updating collection src-all/cvs
Delete src/contrib/file/.FREEBSD-upgrade.swp
Edit src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml
Add delta 1.883.2.74 2007.06.04.18.26.35 bmah
Edit src/sys/conf/NOTES
Add delta 1.1325.2.33 2007.06.05.21.31.11 scottl
Edit src/sys/conf/files
Add delta 1.1031.2.62 2007.06.05.21.31.10 scottl
Edit src/sys/dev/bce/if_bce.c
Add delta 1.2.2.15 2007.06.05.01.56.08 davidch
Edit src/sys/dev/bce/if_bcereg.h
Add delta 1.1.2.6 2007.06.05.01.56.08 davidch
Edit src/sys/dev/em/if_em.c
Add delta 1.65.2.23 2007.06.05.17.44.01 jfv
Edit src/sys/dev/mfi/mfi.c
Add delta 1.3.2.6 2007.06.05.21.27.21 scottl
Checkout src/sys/dev/mfi/mfi_cam.c
Edit src/sys/dev/mfi/mfireg.h
Add delta 1.1.2.5 2007.06.05.21.27.21 scottl
Edit src/sys/dev/mfi/mfivar.h
Add delta 1.1.2.5 2007.06.05.21.27.22 scottl
Edit src/sys/dev/mpt/mpilib/mpi.h
Add delta 1.6.2.2 2007.06.05.21.32.57 scottl
Edit src/sys/dev/mpt/mpilib/mpi_cnfg.h
Add delta 1.6.2.2 2007.06.05.21.32.57 scottl
Edit src/sys/dev/mpt/mpilib/mpi_init.h
Add delta 1.6.2.2 2007.06.05.21.32.57 scottl
Edit src/sys/dev/mpt/mpilib/mpi_ioc.h
Add delta 1.6.2.2 2007.06.05.21.32.57 scottl
Delete src/sys/dev/mpt/mpilib/mpi_log_fc.h
Delete src/sys/dev/mpt/mpilib/mpi_log_sas.h
Edit src/sys/dev/mpt/mpilib/mpi_raid.h
Add delta 1.6.2.2 2007.06.05.21.32.57 scottl
Edit src/sys/dev/mpt/mpilib/mpi_sas.h
Add delta 1.2.2.2 2007.06.05.21.32.57 scottl
Edit src/sys/dev/mpt/mpilib/mpi_targ.h
Add delta 1.5.2.2 2007.06.05.21.32.57 scottl
Edit src/sys/dev/mpt/mpt.c
Add delta 1.12.2.6 2007.06.05.21.32.56 scottl
Edit src/sys/dev/mpt/mpt.h
Add delta 1.6.2.7 2007.06.05.21.32.56 scottl
Edit src/sys/dev/mpt/mpt_cam.c
Add delta 1.1.2.11 2007.06.05.21.32.56 scottl
Edit src/sys/modules/mfi/Makefile
Add delta 1.1.2.4 2007.06.05.21.31.11 scottl
Checkout src/sys/modules/mfi/mfip/Makefile
Shutting down connection to server
Finished successfully
eos# make buildkernel
--
>>> Kernel build for EOS started on Tue Jun 5 15:31:14 PDT 2007
--
{snip}
===> mem (cleandir)
rm -f export_syms mem.ko mem.kld memdev.o mem.o memutil.o i686_mem.o k6_mem.o @
machine mem.ko.debug bus_if.h device_if.h
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> mfi (cleandir)
rm -f export_syms mfi.ko mfi.kld mfi.o mfi_pci.o mfi_disk.o mfi_debug.o @
machine mfi.ko.debug opt_mfi.h pci_if.h bus_if.h device_if.h
===> mfi/mfi_cam (clean)
cd: can't cd to /usr/src/sys/modules/mfi/mfi_cam
*** Error code 2
Stop in /usr/src/sys/modules/mfi.
*** Error code 1
Stop in /usr/src/sys/modules.
*** Error code 1
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Re: Kernel panicking in 6.2 and 7-CURRENT -- interrupt issues]
On Tue, 5 Jun 2007, Ed Dotorg wrote: [EMAIL PROTECTED] wrote: On Tue, 29 May 2007 [EMAIL PROTECTED] wrote: Hello, I'm trying to install 7-CURRENT on my desktop, locally instead of on a virtual machine, and I'm running into an issue where the kernel almost always panics on boot with my motherboard (ASUS P5N-SLI E), due to some sort of interrupt assignment / probing issues. Observations: 1. 7-CURRENT (built) never properly detects the interrupts on the system. 2. 7-CURRENT (May ISO snapshot) doesn't properly detect my USB keyboard, but boots and runs sysinstall. 3. 6.2 RELEASE panics if I don't boot FreeBSD up into "safe mode", due to an issue with the ohci driver (I think the error message had something to deal with device adding / enumeration and not being able to find a memory / interrupt address). First off, if I could get some of the command line arguments to pass to the kernel to emulate safe-mode, that would be much appreciated. Second off, if anybody has any ideas on how to debug this issue, I'll go off and try to determine what the cause is. If it's anything like it was before (clean out /usr/obj, rebuild), I'll be ok. Otherwise, I'll have to purchase more parts and build another dedicated FreeBSD system :(.. Thanks, -Garrett Sorry for cross-posting so much, but this information is relevant to all of the mailing lists included. Ok I "solved" my problem, to a certain extent. Basically the ASUS P5N-E SLI motherboard (nVidia chipset) isn't bootable with FreeBSD 6.2 RELEASE without going into SAFE MODE (panics after ohci_add_done looking for a non-existent memory address, if the USB controller is enabled in the BIOS with "Legacy Mode", i.e. USB Keyboard compatible), and isn't compatible with FreeBSD 7 at all (kernel can't map IRQs properly on up-to-date CURRENT and panics in kernel mode during boot). Strangely enough the 7-CURRENT snapshot ISOs work, but then again it doesn't setup the OHCI and USB keyboard stuff properly, and I can't get any sort of input from my keyboard, obviously. The ASUS P5B-DLX motherboard (Intel chipset) is compatible with FreeBSD 6.2 and 7 though, without any hacks. Maybe someone should update some documentation on the release notes page for supported hardware? Thanks, -Garrett PS Please CC me in any communication as I'm not subscribed to doc@, stable@, or [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Greetings, I've been experiencing a similar problem. I'm installing from a 6.2 Release CD to an Abit fp-in9 sli board (nvidia nforce mcp51 disk controller and nvidia nforce mcp13 network adapter), 2 gig ddr2 ram, sata 300 disk. The install goes without problems but after rebooting, the onboard nic is not active. "nve0: failed to start NVIDIA Hardware interface". I add an fxp card, at this point 6.2 release is installed and functional and the system boots up normally. I can cvsup ports, install ports and even upgrade xorg with no problems. Although the xorg meta port (x11-drivers) caused me a little grief. I can also compile a generic or custom kernel and all is ok. My problem begins when I cvsup to releng_6 and compile a new kernel. My most recent cvsup is from yesterday 6-4-2007 although I've been fussing with this board since the middle of May. After make buildworld and make kernel (GENERIC or custom kernel) I reboot and end up at the "mountroot>" prompt where GEOM tells me that the only device available to boot from is fd0. But, if I reboot and select Safe Mode the machine comes up without problems and I can finish the steps to building the new kernel. From then on with each reboot I must select Safe Mode for the machine to come up. I get the same results whether my disk drive is a single IDE or a single SATA-300. It would be nice to get things working with this board. This is my first nvidia chipset board but it looks as though I'll be looking for one with the trusty Intel chipset. Ed The ASUS P5B DLX MB (Intel chipset) is a lot more compatible with FreeBSD, but I'm running into more issues with USB and PnP on CURRENT, so I'd be wary before making another MB purchase anytime soon, and avoid LGA775 chipset ASUS MBs for the time being until stuff stabilizes.. Then again I'm also running amd64, on CURRENT, so your experiences on STABLE will no likely be different. -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
On Tue, Jun 05, 2007 at 11:10:03PM +0100, Chris wrote: > On 04/06/07, Doug Barton <[EMAIL PROTECTED]> wrote: > >Chris wrote: > > > >> So my question remains when we have 7.0 and 6.3 both STABLE releases > >> will the ports tree not be supported in 6.3 a just released version of > >> FreeBSD? > > > >I can't help but get the impression that you're spoiling for a fight > >here, so let me ask you to take step 1, which is relax a little. > > > >You are focusing on released version numbers when you ask about ports > >support, and we generally focus on release branches. See > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html > >for more information about that. We will be supporting ports for > >RELENG_5 and _6, and RELENG_7 after it's created from what is now HEAD. > > > >Where I think the confusion is coming in is in regards to support for > >a specific version number that is older than the latest version in > >that branch. For example, support for 6.1 which is an older release on > >the RELENG_6 branch. We do our best to provide ports support for older > >versions on currently supported branches, but it's not always possible > >to do so. You can search the archives of the ports list for > >information on why just supporting 3 active branches (which will be 4 > >after RELENG_7 is branched) for over 16,000 ports is a pretty massive > >undertaking. > > > >I hope this makes the situation more clear. > > > >Doug > > > >-- > > > > This .signature sanitized for your protection > > > > > > This is what I had always thought until I was told otherwise recently > thanks. Not spoiling for a fight just trying to understand the > situation because it was dissapointing to be told last week that the > reason for a ommision in UPDATING was because 6.1 was not the latest > release. For this reason I wont dig up the quote I am just happy that > 6.3 will be supported. This is an orthogonal issue. Again, if you read the URL I gave (http://www.freebsd.org/ports/) it explains that older releases on a stable branch (whether 5.x, 6.x or soon to be 7.x) are not supported, although they may continue to work and we will accept patches from the user community to keep them working when they are accidentally broken by a change. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: release cycle
On 04/06/07, Doug Barton <[EMAIL PROTECTED]> wrote: Chris wrote: > So my question remains when we have 7.0 and 6.3 both STABLE releases > will the ports tree not be supported in 6.3 a just released version of > FreeBSD? I can't help but get the impression that you're spoiling for a fight here, so let me ask you to take step 1, which is relax a little. You are focusing on released version numbers when you ask about ports support, and we generally focus on release branches. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html for more information about that. We will be supporting ports for RELENG_5 and _6, and RELENG_7 after it's created from what is now HEAD. Where I think the confusion is coming in is in regards to support for a specific version number that is older than the latest version in that branch. For example, support for 6.1 which is an older release on the RELENG_6 branch. We do our best to provide ports support for older versions on currently supported branches, but it's not always possible to do so. You can search the archives of the ports list for information on why just supporting 3 active branches (which will be 4 after RELENG_7 is branched) for over 16,000 ports is a pretty massive undertaking. I hope this makes the situation more clear. Doug -- This .signature sanitized for your protection This is what I had always thought until I was told otherwise recently thanks. Not spoiling for a fight just trying to understand the situation because it was dissapointing to be told last week that the reason for a ommision in UPDATING was because 6.1 was not the latest release. For this reason I wont dig up the quote I am just happy that 6.3 will be supported. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Re: Kernel panicking in 6.2 and 7-CURRENT -- interrupt issues]
[EMAIL PROTECTED] wrote: > On Tue, 29 May 2007 [EMAIL PROTECTED] wrote: > >> Hello, >> I'm trying to install 7-CURRENT on my desktop, locally instead of >> on a virtual machine, and I'm running into an issue where the kernel >> almost always panics on boot with my motherboard (ASUS P5N-SLI E), due >> to some sort of interrupt assignment / probing issues. >> >> Observations: >> 1. 7-CURRENT (built) never properly detects the interrupts on the >> system. >> 2. 7-CURRENT (May ISO snapshot) doesn't properly detect my USB >> keyboard, but boots and runs sysinstall. >> 3. 6.2 RELEASE panics if I don't boot FreeBSD up into "safe mode", >> due to an issue with the ohci driver (I think the error message had >> something to deal with device adding / enumeration and not being able >> to find a memory / interrupt address). >> >> First off, if I could get some of the command line arguments to >> pass to the kernel to emulate safe-mode, that would be much >> appreciated. Second off, if anybody has any ideas on how to debug this >> issue, I'll go off and try to determine what the cause is. If it's >> anything like it was before (clean out /usr/obj, rebuild), I'll be ok. >> Otherwise, I'll have to purchase more parts and build another >> dedicated FreeBSD system :(.. >> >> Thanks, >> -Garrett > > Sorry for cross-posting so much, but this information is relevant to all > of the mailing lists included. > > Ok I "solved" my problem, to a certain extent. > > Basically the ASUS P5N-E SLI motherboard (nVidia chipset) isn't bootable > with FreeBSD 6.2 RELEASE without going into SAFE MODE (panics after > ohci_add_done looking for a non-existent memory address, if the USB > controller is enabled in the BIOS with "Legacy Mode", i.e. USB Keyboard > compatible), and isn't compatible with FreeBSD 7 at all (kernel can't > map IRQs properly on up-to-date CURRENT and panics in kernel mode during > boot). > > Strangely enough the 7-CURRENT snapshot ISOs work, but then again it > doesn't setup the OHCI and USB keyboard stuff properly, and I can't get > any sort of input from my keyboard, obviously. > > The ASUS P5B-DLX motherboard (Intel chipset) is compatible with FreeBSD > 6.2 and 7 though, without any hacks. > > Maybe someone should update some documentation on the release notes page > for supported hardware? > > Thanks, > -Garrett > > PS Please CC me in any communication as I'm not subscribed to doc@, > stable@, or [EMAIL PROTECTED] > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > -- Greetings, I've been experiencing a similar problem. I'm installing from a 6.2 Release CD to an Abit fp-in9 sli board (nvidia nforce mcp51 disk controller and nvidia nforce mcp13 network adapter), 2 gig ddr2 ram, sata 300 disk. The install goes without problems but after rebooting, the onboard nic is not active. "nve0: failed to start NVIDIA Hardware interface". I add an fxp card, at this point 6.2 release is installed and functional and the system boots up normally. I can cvsup ports, install ports and even upgrade xorg with no problems. Although the xorg meta port (x11-drivers) caused me a little grief. I can also compile a generic or custom kernel and all is ok. My problem begins when I cvsup to releng_6 and compile a new kernel. My most recent cvsup is from yesterday 6-4-2007 although I've been fussing with this board since the middle of May. After make buildworld and make kernel (GENERIC or custom kernel) I reboot and end up at the "mountroot>" prompt where GEOM tells me that the only device available to boot from is fd0. But, if I reboot and select Safe Mode the machine comes up without problems and I can finish the steps to building the new kernel. From then on with each reboot I must select Safe Mode for the machine to come up. I get the same results whether my disk drive is a single IDE or a single SATA-300. It would be nice to get things working with this board. This is my first nvidia chipset board but it looks as though I'll be looking for one with the trusty Intel chipset. Ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Intel i852GM/i855GM DRI problem
Hello guys! I have strange problem enabling DRI on Intel 855GM graphics card. Kernel shows that everything is allright but why I enable DRI in xorg.conf and startx then system freeze and reboot without any error message- /var/log/Xorg.log.0 file was not updated with error or anything similar. FreeBSD 6.2-STABLE #1: Tue Jun 5 18:49:57 EEST 2007 xorg-server-1.2.0_2,1 dri-6.5.3_1,2 kernel compiled with "makeoptions DEBUG=-g" kernel drm message: agp0: port 0xe000-0xe007 mem 0xa000-0xa7ff,0xf000-0xf007 irq 11 at device 2.0 on pci0 agp0: detected 16252k stolen memory agp0: aperture size is 128M drmsub0: : (child of agp_i810.c) on agp0 [drm:pid0:drm_load] [drm:pid0:drm_agp_init] agp_available = 1 info: [drm] AGP at 0xa000 128MB [drm:pid0:drm_ctxbitmap_next] drm_ctxbitmap_next bit : 0 [drm:pid0:drm_ctxbitmap_init] drm_ctxbitmap_init : 0 info: [drm] Initialized i915 1.5.0 20060119 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
On Monday 04 June 2007 17:46, Robin Gruyters wrote: This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. Maybe tar doesn't use the -b option when listing the content? (-t) Could you please send me details of the problem you're having? Thanks, Tim Kientzle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror on a disk with data already on it
Marc UBM Bocklet <[EMAIL PROTECTED]> wrote: > The gmirror man page says that if gmirror is used on a disk, the last > sector of that disk is overwritten with the metadata gmirror uses. > > So what I would like to know is, how risky is it to mirror a disk which > already has data on it? > > Is there a chance that I might render my system unbootable? If you follow the procedure in the Handbook, then there is no risk at all. It involves preparing one side of the mirror on the second (unused) device first, then attaching the first device to the mirror. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." -- RFC 1925 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gmirror on a disk with data already on it
Hiho! :-) The gmirror man page says that if gmirror is used on a disk, the last sector of that disk is overwritten with the metadata gmirror uses. So what I would like to know is, how risky is it to mirror a disk which already has data on it? Is there a chance that I might render my system unbootable? Is there any way to find out what data that last sector holds? Thanks in advance! :-) Bye Marc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
On Monday 04 June 2007 17:46, Robin Gruyters wrote: > This morning I have revert libarchive (src/lib/libarchive) and tar > (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) > it works fine now. > > Maybe tar doesn't use the -b option when listing the content? (-t) Maybe so, I feed mine through dd all the time so I never noticed it :) Can you please file a PR about the issue? (or take it up with Tim whom I have CCd) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpTuxDefafO2.pgp Description: PGP signature
Re: freebsd-stable Digest, Vol 209, Issue 1
From: [EMAIL PROTECTED] <[EMAIL PROTECTED] Date: 2007-6-4 下午8:00 Subject: freebsd-stable Digest, Vol 209, Issue 1 To: freebsd-stable@freebsd.org Send freebsd-stable mailing list submissions to freebsd-stable@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-stable or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-stable digest..." Today's Topics: 1. (no subject) (Jeffery Stone) 2. Re: Sysinstall replacement (Ivan Voras) 3. Re: Sysinstall replacement (Ian Smith) 4. Re: Sysinstall replacement (Craig Boston) 5. Re: Unrecognized archive format with RELENG_6_2 and RELENG_6 (Robin Gruyters) 6. Re: Sysinstall replacement (Ivan Voras) -- Message: 1 Date: 3 Jun 2007 12:07:01 -0500 From: Jeffery Stone <[EMAIL PROTECTED]> Subject: (no subject) To: freebsd-stable@freebsd.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain Hello, I am Jeffery Stone, an Artist with LemonStreet Gallery. LemonStreet Gallery. is an art gallery in London - United Kingdom. We deal on Art and Craft originating mainly from Asia. Our productsare diverse and of the highest quality, depicting 'comfort' and'real affluence'. Being that Asia's traditional crafts are getting more attention asvery important cultural assets,we are proud of our products and so we'd like to show them to the rest of the world. Thus, we are currently expanding our market base beyond Europe, into North america, USA and Africa. WHY WE NEED YOU. No doubt,doing business across borders has never been an easy task.We are currently searching for a reliable representatives who can help us establish a medium of getting to our various customers in their regions (North America & United States). The time frame it takes to have their payment checks sent to us and processed is rather long. This has caused a setback in our sales. The representatives we sought after will serve as our payment officers/contact persons in these regions, but most especially we are on HIGH demand right now for representatives in the USA. Their sole responsibility will be to receive and process payment checks on our behalf. We believe this will go a long way in bridging the gap between us (the sellers) and our customers(the buyers). At this point,we cannot overemphasize the fact that only honest, reliable and competent person(s) is/are needed by us.We will be glad to welcome you on board if you fit in and have an interest to work for us. REMUNERATION. We have a rather generous and highly competitive remuneration package for our new team of sales representatives. We offer a 10% commission on every payment made via you to us. THERE IS NO FINANCIAL OBLIGATION AT YOUR END; all we need from you is total reliability, honesty and your committiment to work for us.There are no hassles as this is a work at home opportunity and would'nt in any way interfere with your present job or status. This offer is irrespective of your qualification or present field of work. Setting you up and registering you with our company remains our responsibility. Let us know your thoughts. If interested do send promptly by email( [EMAIL PROTECTED]) the following: 1.FULL NAMES 2.CONTACT MAILING ADDRESS 3.TELEPHONE NUMBER 4.FAX NUMBER 5.OCCUPATION We look forward to working with you and will be more than pleased to give you further details. Thanks in advance. Sincerely, Jeffery Stone LemonStreet Gallery. London - UK. -- Message: 2 Date: Mon, 04 Jun 2007 00:36:15 +0200 From: Ivan Voras <[EMAIL PROTECTED]> Subject: Re: Sysinstall replacement To: freebsd-stable@freebsd.org Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="utf-8" Maxim Vetrov wrote: Hi! Are there any plans to replace sysinstall? AFAIK there is the BSDInstaller flying :-) around, is it considered as a valid option? See http://wiki.freebsd.org/finstall . -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070603/d067f6de/signature-0001.pgp -- Message: 3 Date: Mon, 4 Jun 2007 15:20:58 +1000 (EST) From: Ian Smith <[EMAIL PROTECTED]> Subject: Re: Sysinstall replacement To: Ivan Voras <[EMAIL PROTECTED]> Cc: freebsd-stable@freebsd.org Message-ID: <[EMAIL PROTECTED]> Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 4 Jun 2007, Ivan Voras wrote: Maxim Vetrov wrote: > Hi! > > Are there any plans to replace sysinstall? AFAIK there is the > BSDInstaller flying :-) around, is it considered as a vali
panic "sbdrop" after "ICMP6, packet too big"
May I bring your attention to a reproducible panic on RELENG_6, as described in kern/113359 (http://www.freebsd.org/cgi/query-pr.cgi?pr=113359). The reason for this mail is, that at present I have still the core file and can provide further information if desired. I can test patches for RELENG_6. Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
