Re: ATA CDROM no more detected with ATA_CAM under VMWare WS
Claude Buisson wrote:
Here it is:
r...@zaza# camcontrol identify cd0 -v
pass1: Raw identify data:
0: 85c4
Attached patch should fix the issue.
--
Alexander Motin
--- sys/ata.h.prev 2010-02-03 19:41:43.0 +0200
+++ sys/ata.h 2010-02-26 11:59:24.0 +0200
@@ -51,7 +51,7 @@ struct ata_params {
#define ATA_RESP_INCOMPLETE 0x0004
/*001*/ u_int16_t cylinders; /* # of cylinders */
- u_int16_t reserved2;
+/*002*/ u_int16_t specconf; /* specific configuration */
/*003*/ u_int16_t heads; /* # heads */
u_int16_t obsolete4;
u_int16_t obsolete5;
--- cam/ata/ata_xpt.c.prev 2010-02-26 12:06:33.0 +0200
+++ cam/ata/ata_xpt.c 2010-02-26 12:17:39.0 +0200
@@ -788,11 +788,10 @@ noerror:
ata_btrim(ident_buf-serial, sizeof(ident_buf-serial));
ata_bpack(ident_buf-serial, ident_buf-serial,
sizeof(ident_buf-serial));
/* Device may need spin-up before IDENTIFY become valid. */
- if ((ident_buf-config ATA_RESP_INCOMPLETE) ||
- ((ident_buf-support.command2 ATA_SUPPORT_STANDBY)
-(ident_buf-enabled.command2 ATA_SUPPORT_STANDBY)
-(ident_buf-support.command2 ATA_SUPPORT_SPINUP)
- softc-spinup == 0)) {
+ if ((ident_buf-specconf == 0x37c8 ||
+ident_buf-specconf == 0x738c)
+ ((ident_buf-config ATA_RESP_INCOMPLETE) ||
+softc-spinup == 0)) {
PROBE_SET_ACTION(softc, PROBE_SPINUP);
xpt_release_ccb(done_ccb);
xpt_schedule(periph, priority);
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ATA CDROM no more detected with ATA_CAM under VMWare WS
Alexander Motin wrote: Claude Buisson wrote: Here it is: r...@zaza# camcontrol identify cd0 -v pass1: Raw identify data: 0: 85c4 Attached patch should fix the issue. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Everything seems OK now. Thanks !! Claude Buisson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Many many many thanks to all that develop FreeBSD.
Hi, When everything is life is just smoothly flowing by, and all is hunky-dory, some things don't get the credits they deserve. So here we go ;) Standing at the coffee machine this morning I realized that FreeBSD has been part of my professional life for already way, way too long. Before 1993 I was tinkering with CPM, SCO, sys3/5, i386, Apollo Domain, Linux 0.98 and sorts. When friends an I decided to start an ISP, then very novel, now really part of our lives. And one of the friends suggested to use FreeBSD instead of Linux. As Linux at that time was still very much in flux and really just a flying target, we were more than up for it. Because if gave us the systems that we were all too familiar with. And it really did work richt out of the box. (well almost, needed to hack on the serial driver for the 16 port card we had) The first commercial server that we deployed was running FreeBSD 1.1. I still fondly keep that CD. One of those friends has been part of the Core team (Guido van Rooij) for a while. And I'm sure that a lot of the code he hacked up to keep the ISP going ended up somewhere in the tree. The release strategy has always been a real nice service to our business. Lots of systems where kept at major_versions, until the hardware became too old. Only then to leapfrog into the most stable version at that moment. And I don't ever recall that we were disappointed in the way FreeBSD developed itself. The ISP was sold in 2000, and I started doing other things. But in 2000 just about everything the ISP was delivering ran on FreeBSD. And I remember boxing being up for over 2 years. (especially those not exposed to the public.:)) Only reason for some windows was, because business wise you can't do without. At home FreeBSD has been my friend from that same moment forward. I trashed my Linux Toys, merged to FreeBSD and never looked back. My home is now running on 2* FreeBSD's and lots of Jave-embeded devices. Again there never disappointed in what FreeBSD delivered. Recently I started a new company again, but much to my disappointment (but understandably so) the chipset supplier (NXP/Philips) delivers only support for Linux (or WinCE) and the new shop is mainly Linux oriented. Although a some of the dev-team are still FreeBSD at hart. And parts of the system are tested against FreeBSD for avoidance of too much Linux-isms. :) So when I ran into some trouble yesterday, I realized how much FreeBSD has contributed to painless computing(tm). And not just only because of the quality of the software, but also because of the support that is offered. And for that I would like to thank, compliment, free-beer-license all the people that made my life trouble free Many many many thanks to all those that make FreeBSD. --WjW ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Can not boot after r203503. Unable to open /dev/ada(1/2)p3 for writing
Hi, I have an unusual problem. Last night I tried updating from my old-ish kernel/world to an up to date version. I had been using 202500-ish successfully. I can build and install the newer world and kernel fine, but when I reboot I get the following Trying to mount root from zfs:raid250/root ZFS WARNING: Unable to open /dev/ada1p3 for writing (error=1). ZFS WARNING: Unable to open /dev/ada2p3 for writing (error=1). ROOT MOUNT ERROR. If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove the invalid options from /etc/fstab loader variables: vfs.root.mountfrom=zfs:raid250/root vfs.root.mountfrom.options=rw Im using 2 drives in a ZFS mirror configuration (ada1 and ada2 making raid250) I tried going back over the older revisions, and the last kernel that I can build and boot is 203503. It seems the changes in 203504 are what cause me the problems. Now for the weird bit, I took a friends kernel (204324) and that boots fine. I pulled his kernel configuration and built against that (I had decided to remake my kernel configuration just before I tried updating). Still I get the same error. I have checked my /etc/make.conf and that looks right. I attached my /etc/fstab and /etc/make.conf. Im using an Intel Q8300 running amd64. Anyone have any ideas? This is my work computer, so unfortunately I wont have access to it over the weekend but will be able to give more information if required on monday Cheers Paul # DeviceMountpoint FStype Options DumpPass# raid250/root/ zfs rw 0 0 raid250/usr /usrzfs rw 0 0 raid250/var /varzfs rw 0 0 raid250/tmp /tmpzfs rw,noatime 0 0 /dev/ada1p2 noneswapsw 0 0 /dev/ada2p2 noneswapsw 0 0 linproc /usr/compat/linux/proc linprocfs rw 0 0 CPUTYPE?=core2 CFLAGS= -msse3 -mmmx -O2 -fno-strict-aliasing -pipe -s CXXFLAGS+= -fconserve-space #CFLAGS= -march=native -O2 -fno-strict-aliasing -pipe -s #CXXFLAGS+= -fconserve-space -fpermissive -Wl,-rpath-link,/usr/local/lib/gcc44 #CC=gcc44 #CXX=g++44 #NO_CPU_CFLAGS= # Don't add -march=cpu to CFLAGS automatically #NO_CPU_COPTFLAGS= # Don't add -march=cpu to COPTFLAGS automatically KERNCONF=DEMOPHON MAKE_IDEA=YES BATCH=YES WITH_JADETEX=YES LOADER_ZFS_SUPPORT=YES # added by use.perl 2009-07-20 19:58:21 PERL_VERSION=5.8.9 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can not boot after r203503. Unable to open /dev/ada(1/2)p3 for writing
On Fri, Feb 26, 2010 at 02:47:06PM +, Paul Wootton wrote: Hi, I have an unusual problem. Last night I tried updating from my old-ish kernel/world to an up to date version. I had been using 202500-ish successfully. I can build and install the newer world and kernel fine, but when I reboot I get the following Trying to mount root from zfs:raid250/root ZFS WARNING: Unable to open /dev/ada1p3 for writing (error=1). ZFS WARNING: Unable to open /dev/ada2p3 for writing (error=1). ROOT MOUNT ERROR. If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove the invalid options from /etc/fstab loader variables: vfs.root.mountfrom=zfs:raid250/root vfs.root.mountfrom.options=rw Im using 2 drives in a ZFS mirror configuration (ada1 and ada2 making raid250) I tried going back over the older revisions, and the last kernel that I can build and boot is 203503. It seems the changes in 203504 are what cause me the problems. Now for the weird bit, I took a friends kernel (204324) and that boots fine. I pulled his kernel configuration and built against that (I had decided to remake my kernel configuration just before I tried updating). Still I get the same error. I have checked my /etc/make.conf and that looks right. I attached my /etc/fstab and /etc/make.conf. Im using an Intel Q8300 running amd64. Anyone have any ideas? This is my work computer, so unfortunately I wont have access to it over the weekend but will be able to give more information if required on monday Cheers Paul # DeviceMountpoint FStypeOptions DumpPass# raid250/root / zfs rw 0 0 raid250/usr /usrzfs rw 0 0 raid250/var /varzfs rw 0 0 raid250/tmp /tmpzfs rw,noatime 0 0 /dev/ada1p2 noneswapsw 0 0 /dev/ada2p2 noneswapsw 0 0 linproc /usr/compat/linux/proc linprocfs rw 0 0 CPUTYPE?=core2 CFLAGS= -msse3 -mmmx -O2 -fno-strict-aliasing -pipe -s ^^^ Are you sure you are allowed to use these flags to compile the kernel? I would try removing this line completely. CXXFLAGS+= -fconserve-space #CFLAGS= -march=native -O2 -fno-strict-aliasing -pipe -s #CXXFLAGS+= -fconserve-space -fpermissive -Wl,-rpath-link,/usr/local/lib/gcc44 #CC=gcc44 #CXX=g++44 #NO_CPU_CFLAGS= # Don't add -march=cpu to CFLAGS automatically #NO_CPU_COPTFLAGS= # Don't add -march=cpu to COPTFLAGS automatically KERNCONF=DEMOPHON MAKE_IDEA=YES BATCH=YES WITH_JADETEX=YES LOADER_ZFS_SUPPORT=YES # added by use.perl 2009-07-20 19:58:21 PERL_VERSION=5.8.9 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can not boot after r203503. Unable to open /dev/ada(1/2)p3 for writing
Alexey Shuvaev wrote: On Fri, Feb 26, 2010 at 02:47:06PM +, Paul Wootton wrote: Hi, I have an unusual problem. Last night I tried updating from my old-ish kernel/world to an up to date version. I had been using 202500-ish successfully. I can build and install the newer world and kernel fine, but when I reboot I get the following Trying to mount root from zfs:raid250/root ZFS WARNING: Unable to open /dev/ada1p3 for writing (error=1). ZFS WARNING: Unable to open /dev/ada2p3 for writing (error=1). ROOT MOUNT ERROR. If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove the invalid options from /etc/fstab loader variables: vfs.root.mountfrom=zfs:raid250/root vfs.root.mountfrom.options=rw Im using 2 drives in a ZFS mirror configuration (ada1 and ada2 making raid250) I tried going back over the older revisions, and the last kernel that I can build and boot is 203503. It seems the changes in 203504 are what cause me the problems. Now for the weird bit, I took a friends kernel (204324) and that boots fine. I pulled his kernel configuration and built against that (I had decided to remake my kernel configuration just before I tried updating). Still I get the same error. I have checked my /etc/make.conf and that looks right. I attached my /etc/fstab and /etc/make.conf. Im using an Intel Q8300 running amd64. Anyone have any ideas? This is my work computer, so unfortunately I wont have access to it over the weekend but will be able to give more information if required on monday Cheers Paul # DeviceMountpoint FStype Options DumpPass# raid250/root/ zfs rw 0 0 raid250/usr /usrzfs rw 0 0 raid250/var /varzfs rw 0 0 raid250/tmp /tmpzfs rw,noatime 0 0 /dev/ada1p2 noneswapsw 0 0 /dev/ada2p2 noneswapsw 0 0 linproc /usr/compat/linux/proc linprocfs rw 0 0 CPUTYPE?=core2 CFLAGS= -msse3 -mmmx -O2 -fno-strict-aliasing -pipe -s ^^^ Are you sure you are allowed to use these flags to compile the kernel? I would try removing this line completely. CXXFLAGS+= -fconserve-space #CFLAGS= -march=native -O2 -fno-strict-aliasing -pipe -s #CXXFLAGS+= -fconserve-space -fpermissive -Wl,-rpath-link,/usr/local/lib/gcc44 #CC=gcc44 #CXX=g++44 #NO_CPU_CFLAGS= # Don't add -march=cpu to CFLAGS automatically #NO_CPU_COPTFLAGS= # Don't add -march=cpu to COPTFLAGS automatically KERNCONF=DEMOPHON MAKE_IDEA=YES BATCH=YES WITH_JADETEX=YES LOADER_ZFS_SUPPORT=YES # added by use.perl 2009-07-20 19:58:21 PERL_VERSION=5.8.9 These options dont appear to be passed in when building a kernel. In fact -mno-sse3 and -mno-mmx are passed in to make sure that these options dont not get feed through. Here is a piece from a kernel build with these options still in my make.conf cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/dev/pccbb/pccbb_isa.c However, the world will include these options is there are in the make.conf Paul ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can not boot after r203503. Unable to open /dev/ada(1/2)p3 for writing
26.02.10, 14:47, Paul Wootton p...@fletchermoorland.co.uk: I have an unusual problem. Last night I tried updating from my old-ish kernel/world to an up to date version. I had been using 202500-ish successfully. I can build and install the newer world and kernel fine, but when I reboot I get the following Trying to mount root from zfs:raid250/root ZFS WARNING: Unable to open /dev/ada1p3 for writing (error=1). ZFS WARNING: Unable to open /dev/ada2p3 for writing (error=1). ROOT MOUNT ERROR. If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove the invalid options from /etc/fstab loader variables: vfs.root.mountfrom=zfs:raid250/root vfs.root.mountfrom.options=rw I had the same problem recently. I have ZFS-only 9.0-CURRENT-amd64. First time when i had this problem was after I added linux_load=YES in /boot/loader.conf. :-) It was only change i made. So, i rebooted again and unload linux from boot prompt. And system boots fine. I tried again with linux.ko and it failed to boot. After that i synced source tree and rebuild kernel. And after that it failed to boot with and without linux. :-) So, after that i booted from another disk and only thing that i did was: # zpool import -R /mnt z # gpart modify -l ZFS -i 3 ad4 (previous label was zfs) After that i can boot with and without linux.ko again. And I can't reproduce this bug again. -- WBR, Andrey V. Elsukov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi Weongyo, Can new siba release operate in systems like in this SVG image? System example: CPU BCM5836 + Wi-Fi BCM4318 And can we compile siba bus code without pci code? - Cut this to file.svg --- ?xml version=1.0 standalone=no? svg width=640 height=480 xmlns:xlink=http://www.w3.org/1999/xlink; xmlns=http://www.w3.org/2000/svg; !-- Created with SVG-edit - http://svg-edit.googlecode.com/ -- g titleLayer 1/title rect stroke-width=5 stroke=#00 fill=#FF id=svg_1 height=44 width=365 y=138 x=74.467/ text xml:space=preserve text-anchor=middle font-family=serif font-size=24 stroke-width=0 stroke=#00 fill=#00 id=svg_2 y=169 x=256.967SSB/text rect id=svg_3 stroke-width=5 stroke=#00 fill=#FF height=44 width=365 y=341 x=217.467/ text id=svg_4 xml:space=preserve text-anchor=middle font-family=serif font-size=24 stroke-width=0 stroke=#00 fill=#00 y=372 x=399.967SSB/text rect stroke-width=5 stroke=#00 fill=#00ff00 id=svg_5 height=50 width=115 y=50 x=72.4667/ rect stroke-width=5 stroke=#00 fill=#00ff00 id=svg_6 height=57 width=131 y=232 x=234.467/ rect stroke-width=5 stroke=#00 fill=#00ff00 id=svg_7 height=58 width=125 y=231 x=433.467/ text xml:space=preserve text-anchor=middle font-family=serif font-size=24 stroke-width=0 stroke=#00 fill=#00 id=svg_8 y=83 x=127.467MIPS/text text id=svg_9 xml:space=preserve text-anchor=middle font-family=serif font-size=24 stroke-width=0 stroke=#00 fill=#00 y=268 x=499.467MIPS/text text xml:space=preserve text-anchor=middle font-family=serif font-size=24 stroke-width=0 stroke=#00 fill=#00 id=svg_10 y=269 x=298.467PCI/text line fill=none stroke-width=5 stroke=#00 id=svg_11 y2=137 x2=127.467 y1=102 x1=127.467/ line fill=none stroke-width=5 stroke=#00 id=svg_13 y2=343 x2=296.467 y1=290 x1=297.467/ line fill=none stroke-width=5 stroke=#00 id=svg_14 y2=343 x2=499.467 y1=290 x1=499.467/ line fill=none stroke-width=5 stroke=#00 id=svg_15 y2=182 x2=299.467 y1=231 x1=299.467/ rect stroke-width=5 stroke=#00 fill=none id=svg_16 height=54 width=159 y=414 x=342.467/ text xml:space=preserve text-anchor=middle font-family=serif font-size=24 stroke-width=0 stroke=#00 fill=#00 id=svg_17 y=448 x=420.467802.11/text path stroke-width=5 stroke=#00 fill=none id=svg_18 d=m151.4,310l247.53334,0l1,-102l214,0l2,267l-466,-1l1.4,-164z/ line fill=none stroke-width=5 stroke=#00 id=svg_19 y2=412 x2=416.467 y1=386 x1=416.467/ /g /svg - Cut this to file.svg --- -- Alex RAY r...@ddteam.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Weongyo, On 2010/02/25 16:51, Weongyo Jeong wrote: FYI bwn(4) driver is committed into FreeBSD tree. I think the driver supports your LP PHY device. After cvsup please try to rebuild siba_bwn and bwn modules. Could you please test with it? Please let me know and send me your full dmesg when you encounters the following problems: - if the driver doesn't work or is unstable. - if it prints debugging or verbose messages. Great! Thanks for the work! Is it possible to MFC the work back to 8-STABLE at some point? A colleague of mine has tried to compile the code on 8-STABLE but seems that it's using some new API I guess... I've asked him to try a 9-CURRENT kernel but the Atom based netbook would take some while to compile the code =-) Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLiGVyAAoJEATO+BI/yjfBcYgH/2Ruc4z9+MsI3xvVm13YIRaH rxkRIOXCs7ViyKLPPh5bwDQiBeiOY10WL+GFxJSg/pO7NBc+gHzkJDZNt6LJtlst iKPcHPwWdxcPbCU7IhO3sIiuMa5WJfH/Aq8tAhlsovlfJwQiukZ4GuhI510q3qo1 2drYi8Z53Ad67/mExMl0gsk0QKIHK3AraQyDV/xRocqdReM+J7TvqxIi0E4dyqha SFTocul34Hht9iH25fd7WPnSUNp+HRgyA6K5hh5ylKzTf2ojsRN/9YE81C+RVDys nADEFN2w1ufbPepxJ7KURQuwTyf7MLkQdqCpKfWGyS90pDm4mh/5wLBk50rsZTs= =kums -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
