lost devices in 8.3
hi, I'm trying to upgrade this old opteron box, which is running 8.2, but when booting 8.3 the disks disappear. with 8.2: ... atapci1@pci0:0:7:1: class=0x01018a card=0x74691022 chip=0x74691022 rev=0x03 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'UltraATA/133 Controller (AMD-8111)' class = mass storage subclass = ATA ... atapci0@pci0:3:5:0: class=0x010400 card=0x61141095 chip=0x31141095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SATALink/SATARaid Controller (Sil 3114)' class = mass storage subclass = RAID but none on 8.3: none0@pci0:0:7:1: class=0x01018a card=0x74691022 chip=0x74691022 rev=0x03 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'UltraATA/133 Controller (AMD-8111)' class = mass storage subclass = ATA ... none3@pci0:3:5:0: class=0x018000 card=0x31141095 chip=0x31141095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SATALink/SATARaid Controller (Sil 3114)' class = mass storage and the only diff in the configuration is that 8.3 has: options ATA_CAM nodeviceata nodeviceatadisk # ATA disk drives nodeviceataraid # ATA RAID drives nodeviceatapicd # ATAPI CDROM drives nodeviceatapifd # ATAPI floppy drives nodeviceatapist # ATAPI tape drives cheers, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: lost devices in 8.3
On Sun, Apr 22, 2012 at 12:17:45PM +0300, Daniel Braniss wrote: hi, I'm trying to upgrade this old opteron box, which is running 8.2, but when booting 8.3 the disks disappear. with 8.2: ... atapci1@pci0:0:7:1: class=0x01018a card=0x74691022 chip=0x74691022 rev=0x03 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'UltraATA/133 Controller (AMD-8111)' class = mass storage subclass = ATA ... atapci0@pci0:3:5:0: class=0x010400 card=0x61141095 chip=0x31141095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SATALink/SATARaid Controller (Sil 3114)' class = mass storage subclass = RAID but none on 8.3: none0@pci0:0:7:1: class=0x01018a card=0x74691022 chip=0x74691022 rev=0x03 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'UltraATA/133 Controller (AMD-8111)' class = mass storage subclass = ATA ... none3@pci0:3:5:0: class=0x018000 card=0x31141095 chip=0x31141095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SATALink/SATARaid Controller (Sil 3114)' class = mass storage and the only diff in the configuration is that 8.3 has: options ATA_CAM nodevice ata You need device ata. nodevice atadisk # ATA disk drives nodevice ataraid # ATA RAID drives nodevice atapicd # ATAPI CDROM drives nodevice atapifd # ATAPI floppy drives nodevice atapist # ATAPI tape drives Marius ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: scanlogd doesnt start anymore after upgrade from 8.2 to 8.3 cause of USB
Claudius wrote: If you are using packet filter, echo hw.usb.no_pf=1 /boot/loader.conf http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065421.html Hope this helps. Thanks! | echo hw.usb.no_pf=1 /boot/loader.conf did the trick. That helped. I'm a bit puzzled to see a disrupive change like this merged to a Stable-branch without a heads-up and without documentation how to disable it. regards, hilko PS: forgot to mention I'm not subsricbed to this list. Please keep me CCed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: scanlogd doesnt start anymore after upgrade from 8.2 to 8.3 cause of USB
Did you recompile your ports so this would go away ? More than likely some of your system is running against libpcap installed from ports etc... This happens. You should also expect these things to happen in an upgrade when you leave software behind. On Sun, Apr 22, 2012 at 05:47:24PM +0200, Hilko Meyer wrote: Claudius wrote: If you are using packet filter, echo hw.usb.no_pf=1 /boot/loader.conf http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065421.html Hope this helps. Thanks! | echo hw.usb.no_pf=1 /boot/loader.conf did the trick. That helped. I'm a bit puzzled to see a disrupive change like this merged to a Stable-branch without a heads-up and without documentation how to disable it. regards, hilko PS: forgot to mention I'm not subsricbed to this list. Please keep me CCed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- - (2^(N-1)) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: scanlogd doesnt start anymore after upgrade from 8.2 to 8.3 cause of USB
Jason Hellenthal schrieb: Did you recompile your ports so this would go away ? That was the first thing I tried. Didn't helped. More than likely some of your system is running against libpcap installed from ports etc... This happens. No libcap from ports installed. And both affected programs linked to systemlibpcap: hilko@falko:~ ldd /usr/sbin/tcpdump /usr/sbin/tcpdump: libpcap.so.7 = /lib/libpcap.so.7 (0x28112000) libcrypto.so.6 = /lib/libcrypto.so.6 (0x2813f000) libc.so.7 = /lib/libc.so.7 (0x2829a000) hilko@falko:~ ldd /usr/local/bin/scanlogd /usr/local/bin/scanlogd: libpcap.so.7 = /lib/libpcap.so.7 (0x2808f000) libc.so.7 = /lib/libc.so.7 (0x280bc000) You should also expect these things to happen in an upgrade when you leave software behind. Thats true, but that wasn't the case here. In my understanding it's related to this from the 8.3-Releasenotes: | The FreeBSD usb(4) subsystem now supports USB packet filter. This allows | to capture packets which go through each USB host controller. The | implementation is almost based on bpf(4) code. The userland program | usbdump(8) has been added.[r221174] After that 'netstat -i' shows usbus entries. And it seens the contributed libcap doesn't know how to handle that. regards, hilko ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RELENG_8 still identifies itself as 8.3-PRERELEASE
A RELENG_8 system built this morning still identifies itself as 8.3-PRERELEASE. Any chance of this becoming 8.3-STABLE soon? While this is entirely cosmetic, it does cause me issues at $JOB. -- Adrian Wontroba A fool and his money soon go partying. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 still identifies itself as 8.3-PRERELEASE
Hi,
On Sun, Apr 22, 2012 at 10:59:02PM +0100, Adrian Wontroba wrote:
A RELENG_8 system built this morning still identifies itself as
8.3-PRERELEASE.
Any chance of this becoming 8.3-STABLE soon? While this is entirely
cosmetic, it does cause me issues at $JOB.
If this is a problem for you at $JOB, the attached patch will fix the
version output until the change is made in the official sources.
Glen
Index: sys/conf/newvers.sh
===
--- sys/conf/newvers.sh (revision 234589)
+++ sys/conf/newvers.sh (working copy)
@@ -32,7 +32,7 @@
TYPE=FreeBSD
REVISION=8.3
-BRANCH=PRERELEASE
+BRANCH=STABLE
if [ X${BRANCH_OVERRIDE} != X ]; then
BRANCH=${BRANCH_OVERRIDE}
fi
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 still identifies itself as 8.3-PRERELEASE
On 22. Apr 2012, at 21:59 , Adrian Wontroba wrote: A RELENG_8 system built this morning still identifies itself as 8.3-PRERELEASE. Any chance of this becoming 8.3-STABLE soon? While this is entirely cosmetic, it does cause me issues at $JOB. Fixed. -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 still identifies itself as 8.3-PRERELEASE
On Sun, Apr 22, 2012 at 10:39:44PM +, Bjoern A. Zeeb wrote: On 22. Apr 2012, at 21:59 , Adrian Wontroba wrote: A RELENG_8 system built this morning still identifies itself as 8.3-PRERELEASE. Any chance of this becoming 8.3-STABLE soon? While this is entirely cosmetic, it does cause me issues at $JOB. Fixed. Thanks! Thanks also for the suggestions from others. -- Adrian Wontroba ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: GEOM_PART: integrity check failed (mirror/gm0, MBR) on FreeBSD 8.3-RELEASE
On 20.04.2012 22:43, Mark Knight wrote: I just did a source upgrade from 8.2 to 8.3. System boots but has this warning: GEOM_PART: integrity check failed (mirror/gm0, MBR) Google points to issues with FreeBSD 9 and the need to migrate to GPT but I wasn't expecting this with 8.3! It is not necessary to migrate to GPT. You should understand why it is happens. You can enable verbose boot mode and you will see why it complains. Are there any quick fixes to eliminate this warning or is it safe to ignore please? sudo gpart list: Geom name: mirror/gm0 modified: false state: CORRUPT last: 976773166 first: 63 1. Name: mirror/gm0s1 Mediasize: 500107829760 (465G) Consumers: 1. Name: mirror/gm0 Mediasize: 500107861504 (465G) The problem is that mirror/gm0 provides only 500107861504 bytes, but the MBR expects 500107829760 + 32256 bytes. -- WBR, Andrey V. Elsukov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
