Re: New Optane AIC does not show up in FreeBSD until . . . ?
On Tue, Feb 16, 2021 at 1:48 AM Harry Schmalzbauer wrote: > Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: > > On 2021-Feb-13, at 16:40, Warner Losh wrote: > > > >> Are you aware of gpart create? > >> > >> Warner > > From which I derive that I had an implicit, incorrect > > assumption that gpart show would in some way list > > everything available that gpart could manipulate > > (including for use in creation). > > 'geom disk status' is my first choice for such a case. > Even nvd(4) should show up I think, nda(4) just changes the access path, > not geom(8) integration, afaik. > nvd and nda are mutually exclusive block device interfaces to the nvme driver. As far as geom is concerned, they are no different than da, ada or any of the other block device drivers we have that use the geom interface. sysctl kern.disks is a briefer version of that. Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-16, at 02:22, Harry Schmalzbauer wrote: > Am 16.02.2021 um 11:08 schrieb Mark Millard: >> On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: >>> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh wrote: > Are you aware of gpart create? > > Warner From which I derive that I had an implicit, incorrect assumption that gpart show would in some way list everything available that gpart could manipulate (including for use in creation). >>> >>> 'geom disk status' is my first choice for such a case. >>> Even nvd(4) should show up I think, nda(4) just changes the access path, >>> not geom(8) integration, afaik. > > ... >> Thanks for the alternatives to sysctl kern.disks >> and to nvmecontrol devlist for making a list to >> compare to gpart show output in order to find >> what gpart show does not list (but can manipulate). > > gpart(8) doesn't enumerate disks without any supported partition scheme > present. > You can create new partition schemes with the help of gpart(8), but it's imho > correct not to show them, because 'gpart show' is meant to give information > about (existing) partition schemes - no scheme no info; thus your vanilla > disk is "unknown" to gpart(8). > > I remember that I always thought the geom(8) disk class is kind of hidden - > especially since the man page misses listing DISK in the > "Currently available classes which are aware of geom(8)" section! > > The "show" command was enriched to contain valuable details, such as NAA. > So 'geom disk' turned into one of the most useful mass storage admin > commands. imho. > Maybe somebody should correct the aforementioned man page section and add add > any hint in the SEE ALSO section, because there is no gdisk(8) aequivalent, > like for all other geom classes... > > -harry > > P.S. Put it on my loger-term todo to file a bug report with a proposed man > page diff... Looks like "geom -t" output avoids me having to compare two outputs to find mismatches in the list of names: its output is sufficient to identify the name(s) for drives that do not have the scheme information (and the names of those that do). This at least helps cut down what I have to coordinate, especially when only one device is in question. For example, ada2 in the below has only DISK and one DEV line, not multiple DEV's, no PART line, nor other such: . . . ada0 DISK ada0 ada0 PART ada0s1 ada0s1 DEV ada0 PART ada0s2 ada0s2 DEV ada0 DEV ada1 DISK ada1 ada1 PART ada1p1 ada1p1 DEV ada1 DEV ada2 DISK ada2 ada2 DEV da0DISK da0 da0 PART da0p1 da0p1 DEV da0 PART da0p2 da0p2 LABEL ntfs/VirtMachs ntfs/VirtMachs DEV da0p2 DEV da0 DEV . . . So I can infer that I need a gpart create on ada2 . (Presumes I know from the naming that the device is not analogous to a cd-drive with no media in the drive.) The output does span the nvd* devices. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
Am 16.02.2021 um 11:08 schrieb Mark Millard: On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh wrote: Are you aware of gpart create? Warner From which I derive that I had an implicit, incorrect assumption that gpart show would in some way list everything available that gpart could manipulate (including for use in creation). 'geom disk status' is my first choice for such a case. Even nvd(4) should show up I think, nda(4) just changes the access path, not geom(8) integration, afaik. ... Thanks for the alternatives to sysctl kern.disks and to nvmecontrol devlist for making a list to compare to gpart show output in order to find what gpart show does not list (but can manipulate). gpart(8) doesn't enumerate disks without any supported partition scheme present. You can create new partition schemes with the help of gpart(8), but it's imho correct not to show them, because 'gpart show' is meant to give information about (existing) partition schemes - no scheme no info; thus your vanilla disk is "unknown" to gpart(8). I remember that I always thought the geom(8) disk class is kind of hidden - especially since the man page misses listing DISK in the "Currently available classes which are aware of geom(8)" section! The "show" command was enriched to contain valuable details, such as NAA. So 'geom disk' turned into one of the most useful mass storage admin commands. imho. Maybe somebody should correct the aforementioned man page section and add add any hint in the SEE ALSO section, because there is no gdisk(8) aequivalent, like for all other geom classes... -harry P.S. Put it on my loger-term todo to file a bug report with a proposed man page diff... ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote: > Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: >> On 2021-Feb-13, at 16:40, Warner Losh wrote: >> >>> Are you aware of gpart create? >>> >>> Warner >> From which I derive that I had an implicit, incorrect >> assumption that gpart show would in some way list >> everything available that gpart could manipulate >> (including for use in creation). > > 'geom disk status' is my first choice for such a case. > Even nvd(4) should show up I think, nda(4) just changes the access path, not > geom(8) integration, afaik. Looks like "geom disk status" and "geom disk list" both list "disks" that do not have a partition scheme and spans the nvd* disks. (I only tested destroying a partition scheme on an ada* and then seeing what was displayed. I do not want to destroy such on any nvd* as stands.) "geom disk list" shows Mediasize and descr, which at times could be handy for identification, at least when the pair are unique in the system. Thanks for the alternatives to sysctl kern.disks and to nvmecontrol devlist for making a list to compare to gpart show output in order to find what gpart show does not list (but can manipulate). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current: On 2021-Feb-13, at 16:40, Warner Losh wrote: Are you aware of gpart create? Warner From which I derive that I had an implicit, incorrect assumption that gpart show would in some way list everything available that gpart could manipulate (including for use in creation). 'geom disk status' is my first choice for such a case. Even nvd(4) should show up I think, nda(4) just changes the access path, not geom(8) integration, afaik. -harry ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-13, at 17:38, Warner Losh wrote: > On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote: > > On 2021-Feb-13, at 16:40, Warner Losh wrote: > > > Are you aware of gpart create? > > > > Warner > > From which I derive that I had an implicit, incorrect > assumption that gpart show would in some way list > everything available that gpart could manipulate > (including for use in creation). > > So I need to find such a drive another way, something > I was not even trying to do. > > That answers my question. Thanks. > > Nvmecontrol devlist is a good place to start. Or sysctl kern.disks > Turns out that sysctl kern.disks would not have directly helped on its own because the drive was replacing another: the set of names listed would be unchanged: # sysctl kern.disks kern.disks: da6 da5 cd0 da4 da3 da2 da1 da0 ada2 ada1 ada0 nvd5 nvd4 nvd3 nvd2 nvd1 nvd0 (I'd know it was one of the nvd*'s.) So for sysctl kern.disks use I'd need to look for a name (a nvd*) that gpart show had not listed and that would be the new one. So: use both commands. Good to know. nmvecontrol devlist does get into nvmeN/nvmeNns1 vs. the nvdN names listed in gpart show, and so for more complicated name matching. But, again, involves finding an unmatched name. In the actual context, the type and size happened to be unique and that would have made identification easy from nmvecontrol devlist output. Thanks for the notes, Mark > > >> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current > >> wrote: > >> I plugged in a new Optane and booted FreeBSD on the > >> ThreadRipper 1950X system but FreeBSD did not show > >> the drive in gpart show. (It is unique by size in the > >> context and so would be hard to miss for anything > >> that listed sizes. Lack of listing a size would also > >> stand out.) > >> > >> So I did what I've done in the past: shutdown FreeBSD, > >> boot Windows 10, go to its disk management utility, > >> answer its prompt for MBR vs. GPT for the new device > >> (picking GPT), shutdown Windows 10. Then boot FreeBSD > >> again --and the new drive shows up. > >> > >> Is there a way to avoid the round trip through > >> Windows 10 (or any other such round trip going > >> outside FreeBSD)? I'm just curious if I've missed > >> something: My work around enables my activity. > >> > >> > >> FYI, FreeBSD based on main 3acea07c1873 : > >> > >> # ~/fbsd-based-on-what-freebsd-main.sh > >> merge-base: 3acea07c1873b1e4042f4a4fa8668745ee59f15b > >> merge-base: CommitDate: 2021-02-08 19:15:21 + > >> c1845d00f818 (HEAD -> mm-src) mm-src snapshot for mm's patched build in > >> git context. > >> 3acea07c1873 (pure-src) Restore the augmented strlen commentary > >> FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT > >> mm-src-n244686-c1845d00f818 GENERIC-NODBG amd64 amd64 144 144 > >> > >> But this is not a new thing, more of a "still true" > >> thing. > > === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote: > > On 2021-Feb-13, at 16:40, Warner Losh wrote: > > > Are you aware of gpart create? > > > > Warner > > From which I derive that I had an implicit, incorrect > assumption that gpart show would in some way list > everything available that gpart could manipulate > (including for use in creation). > > So I need to find such a drive another way, something > I was not even trying to do. > > That answers my question. Thanks. > Nvmecontrol devlist is a good place to start. Or sysctl kern.disks Mark > > > >> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current < > freebsd-current@freebsd.org> wrote: > >> I plugged in a new Optane and booted FreeBSD on the > >> ThreadRipper 1950X system but FreeBSD did not show > >> the drive in gpart show. (It is unique by size in the > >> context and so would be hard to miss for anything > >> that listed sizes. Lack of listing a size would also > >> stand out.) > >> > >> So I did what I've done in the past: shutdown FreeBSD, > >> boot Windows 10, go to its disk management utility, > >> answer its prompt for MBR vs. GPT for the new device > >> (picking GPT), shutdown Windows 10. Then boot FreeBSD > >> again --and the new drive shows up. > >> > >> Is there a way to avoid the round trip through > >> Windows 10 (or any other such round trip going > >> outside FreeBSD)? I'm just curious if I've missed > >> something: My work around enables my activity. > >> > >> > >> FYI, FreeBSD based on main 3acea07c1873 : > >> > >> # ~/fbsd-based-on-what-freebsd-main.sh > >> merge-base: 3acea07c1873b1e4042f4a4fa8668745ee59f15b > >> merge-base: CommitDate: 2021-02-08 19:15:21 + > >> c1845d00f818 (HEAD -> mm-src) mm-src snapshot for mm's patched build in > git context. > >> 3acea07c1873 (pure-src) Restore the augmented strlen commentary > >> FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT > mm-src-n244686-c1845d00f818 GENERIC-NODBG amd64 amd64 144 144 > >> > >> But this is not a new thing, more of a "still true" > >> thing. > > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
On 2021-Feb-13, at 16:40, Warner Losh wrote: > Are you aware of gpart create? > > Warner >From which I derive that I had an implicit, incorrect assumption that gpart show would in some way list everything available that gpart could manipulate (including for use in creation). So I need to find such a drive another way, something I was not even trying to do. That answers my question. Thanks. Mark >> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current >> wrote: >> I plugged in a new Optane and booted FreeBSD on the >> ThreadRipper 1950X system but FreeBSD did not show >> the drive in gpart show. (It is unique by size in the >> context and so would be hard to miss for anything >> that listed sizes. Lack of listing a size would also >> stand out.) >> >> So I did what I've done in the past: shutdown FreeBSD, >> boot Windows 10, go to its disk management utility, >> answer its prompt for MBR vs. GPT for the new device >> (picking GPT), shutdown Windows 10. Then boot FreeBSD >> again --and the new drive shows up. >> >> Is there a way to avoid the round trip through >> Windows 10 (or any other such round trip going >> outside FreeBSD)? I'm just curious if I've missed >> something: My work around enables my activity. >> >> >> FYI, FreeBSD based on main 3acea07c1873 : >> >> # ~/fbsd-based-on-what-freebsd-main.sh >> merge-base: 3acea07c1873b1e4042f4a4fa8668745ee59f15b >> merge-base: CommitDate: 2021-02-08 19:15:21 + >> c1845d00f818 (HEAD -> mm-src) mm-src snapshot for mm's patched build in git >> context. >> 3acea07c1873 (pure-src) Restore the augmented strlen commentary >> FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT >> mm-src-n244686-c1845d00f818 GENERIC-NODBG amd64 amd64 144 144 >> >> But this is not a new thing, more of a "still true" >> thing. > === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Optane AIC does not show up in FreeBSD until . . . ?
Are you aware of gpart create? Warner On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current < freebsd-current@freebsd.org> wrote: > I plugged in a new Optane and booted FreeBSD on the > ThreadRipper 1950X system but FreeBSD did not show > the drive in gpart show. (It is unique by size in the > context and so would be hard to miss for anything > that listed sizes. Lack of listing a size would also > stand out.) > > So I did what I've done in the past: shutdown FreeBSD, > boot Windows 10, go to its disk management utility, > answer its prompt for MBR vs. GPT for the new device > (picking GPT), shutdown Windows 10. Then boot FreeBSD > again --and the new drive shows up. > > Is there a way to avoid the round trip through > Windows 10 (or any other such round trip going > outside FreeBSD)? I'm just curious if I've missed > something: My work around enables my activity. > > > FYI, FreeBSD based on main 3acea07c1873 : > > # ~/fbsd-based-on-what-freebsd-main.sh > merge-base: 3acea07c1873b1e4042f4a4fa8668745ee59f15b > merge-base: CommitDate: 2021-02-08 19:15:21 + > c1845d00f818 (HEAD -> mm-src) mm-src snapshot for mm's patched build in > git context. > 3acea07c1873 (pure-src) Restore the augmented strlen commentary > FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT > mm-src-n244686-c1845d00f818 GENERIC-NODBG amd64 amd64 144 144 > > But this is not a new thing, more of a "still true" > thing. > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
New Optane AIC does not show up in FreeBSD until . . . ?
I plugged in a new Optane and booted FreeBSD on the ThreadRipper 1950X system but FreeBSD did not show the drive in gpart show. (It is unique by size in the context and so would be hard to miss for anything that listed sizes. Lack of listing a size would also stand out.) So I did what I've done in the past: shutdown FreeBSD, boot Windows 10, go to its disk management utility, answer its prompt for MBR vs. GPT for the new device (picking GPT), shutdown Windows 10. Then boot FreeBSD again --and the new drive shows up. Is there a way to avoid the round trip through Windows 10 (or any other such round trip going outside FreeBSD)? I'm just curious if I've missed something: My work around enables my activity. FYI, FreeBSD based on main 3acea07c1873 : # ~/fbsd-based-on-what-freebsd-main.sh merge-base: 3acea07c1873b1e4042f4a4fa8668745ee59f15b merge-base: CommitDate: 2021-02-08 19:15:21 + c1845d00f818 (HEAD -> mm-src) mm-src snapshot for mm's patched build in git context. 3acea07c1873 (pure-src) Restore the augmented strlen commentary FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n244686-c1845d00f818 GENERIC-NODBG amd64 amd64 144 144 But this is not a new thing, more of a "still true" thing. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[PATCH] Locking for aic(4)
Still working on patches for drivers from the last century. The latest installment is a patch for aic(4). It should apply to 8 and 9 as well as HEAD. Please ensure INVARIANTS is enabled during testing. http://www.FreeBSD.org/~jhb/patches/aic_locking.patch -- John Baldwin ___ 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: Lost second channel of AIC-7896
"Justin T. Gibbs" wrote: After upgrading my system from 13'th December to latest -current, the ahc driver doesn't attach to onboard AIC-7896 second channel anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right persons. Dmesg: Can you send me the output of "pciconf -l" on this system? My guess is that your MB vendor did not use the correct subsystem ID for the aic7896 to enable the second channel. We only recently started to pay attention to this. What MB is this? My system doesn't find any scsi controllers. Tyan thunder... I think burst[3:02pm]-=sudo pciconf -l hostb0@pci0:0:0:class=0x06 card=0x chip=0x71908086 rev=0x03 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x chip=0x71918086 rev=0x03 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x chip=0x71108086 rev=0x02 hdr=0x00 atapci0@pci0:7:1: class=0x010180 card=0x chip=0x71118086 rev=0x01 hdr=0x00 uhci0@pci0:7:2: class=0x0c0300 card=0x chip=0x71128086 rev=0x01 hdr=0x00 none0@pci0:7:3: class=0x068000 card=0x chip=0x71138086 rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 ahc1@pci0:11:1: class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 fxp0@pci0:13:0: class=0x02 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 -- Russell Cattelan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lost second channel of AIC-7896
Can you send me the output of "pciconf -l" on this system? My guess is that your MB vendor did not use the correct subsystem ID for the aic7896 to enable the second channel. We only recently started to pay attention to this. What MB is this? My system doesn't find any scsi controllers. Are you sure that your drives aren't just attached to the second port? Have you tried a current since Friday? I committed a fix for the original problem that was reported. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lost second channel of AIC-7896
On Sat, Jan 06, 2001 at 15:02:45 -0600, Russell Cattelan wrote: "Justin T. Gibbs" wrote: After upgrading my system from 13'th December to latest -current, the ahc driver doesn't attach to onboard AIC-7896 second channel anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right persons. Dmesg: Can you send me the output of "pciconf -l" on this system? My guess is that your MB vendor did not use the correct subsystem ID for the aic7896 to enable the second channel. We only recently started to pay attention to this. What MB is this? My system doesn't find any scsi controllers. Tyan thunder... I think burst[3:02pm]-=sudo pciconf -l [ ... ] ahc0@pci0:11:0: class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 ahc1@pci0:11:1: class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 [ ... ] Looks like you have a 7896 there. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Lost second channel of AIC-7896
After upgrading my system from 13'th December to latest -current, the ahc driver doesn't attach to onboard AIC-7896 second channel anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right persons. Dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Jan 5 15:42:56 EET 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/Myhakas.SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268435456 (262144K bytes) avail memory = 257298432 (251268K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc03c5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03c509c. Pentium Pro MTRR support enabled VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6954 (c0006954) VESA: Matrox Graphics Inc. npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443GX host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga_pci0: VGA-compatible display device mem 0xfd80-0xfdff,0xfe2fc000-0xfe2f,0xf200-0xf3ff irq 16 at device 0.0 on pci1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at 7.2 (no driver attached) Timecounter "PIIX" frequency 3579545 Hz pci0: bridge, PCI-unknown at 7.3 (no driver attached) ahc0: Adaptec aic7896/97 Ultra2 SCSI adapter port 0xe400-0xe4ff mem 0xfebfc000-0xfebfcfff irq 16 at device 11.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs pci0: mass storage, SCSI at 11.1 (no driver attached) pcm0: AudioPCI ES1371 port 0xed80-0xedbf irq 18 at device 12.0 on pci0 fxp0: Intel Pro 10/100B/100+ Ethernet port 0xee80-0xeebf mem 0xfe80-0xfe8f,0xfebfd000-0xfebfdfff irq 19 at device 13.0 on pci0 fxp0: Ethernet address 00:e0:81:10:50:32 fxp1: Intel Pro 10/100B/100+ Ethernet port 0xef00-0xef3f mem 0xfea0-0xfeaf,0xfebfe000-0xfebfefff irq 17 at device 15.0 on pci0 fxp1: Ethernet address 00:90:27:54:57:26 ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xef80-0xef9f irq 18 at device 18.0 on pci0 ed0: address 00:e0:29:6d:14:19, type NE2000 (16 bit) atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 sc0: System console at flags 0x100 on isa0 sc0: VGA 9 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 BRIDGE 990810, have 4 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.e0.81.10.50.32 -- index 2 type 6 phy 0 addrl 6 addr 00.90.27.54.57.26 -- index 3 type 6 phy 0 addrl 6 addr 00.e0.29.6d.14.19 ad0: 14649MB IBM-DTLA-307015 [29765/16/63] at ata0-master tagged UDMA33 ad1: 35772MB IBM-DPTA-353750 [72680/16/63] at ata1-master tagged UDMA33 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 1 lun 0 da0: QUANTUM VIKING II 4.5WSE 5520 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc0 bus 0 target 2 lun 0 da1: QUANTUM VIKING II 4.5WSE 5520 Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) SMP: AP CPU #1 Launched! now fxp0 promisc ON if_flags 0x8943 bdg_flags 0x5 now fxp1 promisc ON if_flags 0x8943 bdg_flags 0x5 now ed0 promisc ON if_flags 0x8943 bdg_flags 0x5 Pciconf: hostb0@pci0:0:0
Re: Lost second channel of AIC-7896
After upgrading my system from 13'th December to latest -current, the ahc driver doesn't attach to onboard AIC-7896 second channel anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right persons. Dmesg: Can you send me the output of "pciconf -l" on this system? My guess is that your MB vendor did not use the correct subsystem ID for the aic7896 to enable the second channel. We only recently started to pay attention to this. What MB is this? -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lost second channel of AIC-7896
On Fri, Jan 05, 2001 at 07:48:36AM -0700, "Justin T. Gibbs" [EMAIL PROTECTED] wrote: Can you send me the output of "pciconf -l" on this system? My guess is that your MB vendor did not use the correct subsystem ID for the aic7896 to enable the second channel. We only recently started to pay attention to this. What MB is this? It's Tyan Thunderbolt, S1837-UANG. hostb0@pci0:0:0:class=0x06 card=0x chip=0x71a08086 rev=0x00 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x chip=0x71a18086 rev=0x00 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x chip=0x71108086 rev=0x02 hdr=0x00 atapci0@pci0:7:1: class=0x010180 card=0x chip=0x71118086 rev=0x01 hdr=0x00 none0@pci0:7:2: class=0x0c0300 card=0x chip=0x71128086 rev=0x01 hdr=0x00 none1@pci0:7:3: class=0x068000 card=0x chip=0x71138086 rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 none2@pci0:11:1:class=0x01 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 pcm0@pci0:12:0: class=0x040100 card=0x13711274 chip=0x13711274 rev=0x06 hdr=0x00 fxp0@pci0:13:0: class=0x02 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 fxp1@pci0:15:0: class=0x02 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 ed0@pci0:18:0: class=0x02 card=0x201110b8 chip=0x802910ec rev=0x00 hdr=0x00 vga_pci0@pci1:0:0: class=0x03 card=0x19f8102b chip=0x0525102b rev=0x03 hdr=0x00 -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AIC-7890 problems with kernel build
I've had this problem for the past couple of days (I went a while between updates of my kernel since I was busy installing a new disk and moving OSes around). Just after the "waiting for SCSI devices to settle" message, I'll get a number of SCB errors (which I don't have written down, unfortunately), and then eventually a panic. This is with ACPI enabled... if I don't enable ACPI, it will proceed immediately to the panic. The panic is a "Trap 12: page fault in kernel mode". with "interrupt mask: cam - SMP: XXX", and "Stopped at ahc_match_scb + 0x9d movl 0x2c(%eax), %eax" I apologize for the exceedingly lameassed manner of this bug report, I don't have serial ports enabled on this machine and don't know of a more effective means to get the details. With the kernel debugger, I get a stack trace similar to the following: ahc_match_scb(c0e7e000, c0e8e230, 0, 41, 0, 9, 1) ahc_search_qinfifo(c0e7e000, 0, 41, 0, 9, 1, 0, 1) ahc_timeout(c0e8e168, 4000, 0, 0, ) softclock(0, 18, c02b0010, 10, ) doreti_swi() I can dig up my kernel config and a "functional" dmesg as soon as I get back via the saved good kernel. For the record, this is via the onboard AIC-7890 on a Tyan Thunder/100 dual processor board running an SMP kernel. -- Brandon Hume- hume - BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
On Mon, 4 Sep 2000, Brandon Hume wrote: Just after the "waiting for SCSI devices to settle" message, I'll get a number of SCB errors (which I don't have written down, unfortunately), and then eventually a panic. This is with ACPI enabled... if I don't enable ACPI, it will proceed immediately to the panic. Sounds similar to what I'm getting; after a boot I get a load of the following: ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) ahc1: ahc_intr - referenced scb not valid during SELTO (31, 139) followed by a panic: (probe0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0xb panic: Waiting List inconsistency. SCB index == 255, yet numscbs == 20 (Being a technophobe I decided to write these down rather than dig out a breakout box to capture the serial port output!) Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) Lots of other blurb about "can't allocate register resources" for just about anything on the PCI bus, as I recall. Chris. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Chris Hedley writes: On Mon, 4 Sep 2000, Brandon Hume wrote: Just after the "waiting for SCSI devices to settle" message, I'll get a number of SCB errors (which I don't have written down, unfortunately), and then eventually a panic. This is with ACPI enabled... if I don't enable ACPI, it will proceed immediately to the panic. Sounds similar to what I'm getting; after a boot I get a load of the following: I'll add a third to that. The SCB errors don't seem to depend on ACPI; they didn't happen on the update on Sept 1, but did on Sept 2. Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) Not quite the same. I've got a SuperMicro SMP Xeon system with an onboard 7890. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
On Mon, 4 Sep 2000, Brandon Hume wrote: Sounds similar to what I'm getting; after a boot I get a load of the following: ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) That's what I get... although I get SELTO (31, 0) Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 Mine's a GX, with a 7895 also (not 7890, oops...) controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) My working kernel was built 1 PM ADT on the 26th, so there's a slightly narrower window. Lots of other blurb about "can't allocate register resources" for just about anything on the PCI bus, as I recall. I think that's a double-probe problem mentioned on the commit list. Dunno if it would be related. Here's the kernel config and functional-dmesg I promised. dmesg: --- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Aug 26 13:00:17 ADT 2000 [EMAIL PROTECTED]:/build/src/sys/compile/JASHUGAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM real memory = 134086656 (130944K bytes) avail memory = 126570496 (123604K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "JASHUGAN" at 0xc03e1000. Pentium Pro MTRR support enabled md0: Malloc disk apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443GX host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: Intel 82443GX host to PCI bridge at 0.0 pcib2: Intel 82443GX (440 GX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib2 pci1: Matrox MGA G400 AGP graphics accelerator at 0.0 irq 16 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xef80-0xef9f irq 19 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: Logitech, Inc. Camera, rev 1.00/1.00, addr 2 uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 3 uhub1: 4 ports with 4 removable, bus powered ukbd0: Sun Microsystems Type 6 USB, rev 1.00/1.01, addr 4, iclass 3/1 kbd1 at ukbd0 ums0: Logitech USB-PS/2 Mouse, rev 1.00/1.10, addr 5, iclass 3/1 ums0: 3 buttons and Z dir. Timecounter "PIIX" frequency 3579545 Hz pci0: Intel 82371AB Power management controller at 7.3 pcib3: DEC 21152 PCI-PCI bridge at device 16.0 on pci0 pci2: PCI bus on pcib3 pci2: 3Dfx Voodoo 2 graphics accelerator at 4.0 pci2: unknown card (vendor=0x11d1, dev=0x01f7) at 5.0 irq 17 fxp0: Intel Pro 10/100B/100+ Ethernet port 0xef40-0xef5f mem 0xfea0-0xfeaf,0xfd2ff000-0xfd2f irq 19 at device 17.0 on pci0 fxp0: Ethernet address 00:e0:81:10:24:79 ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xe400-0xe4ff mem 0xfebfe000-0xfebfefff irq 16 at device 18.0 on pci0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xe800-0xe8ff mem 0xfebff000-0xfebf irq 16 at device 18.1 on pci0 ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs pcm0: Creative EMU10K1 port 0xef20-0xef3f irq 16 at device 19.0 on pci0 pcib1: Intel 82443GX host to AGP bridge on motherboard pci3: PCI bus on pcib1 isa0: too many memory ranges fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 unknown: PNP0303 can't assign resources unknown: PNP0700 can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IPsec: Initialized Security Association Processing. IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled SMP: AP CPU #1 Launched! acd0: DVD-ROM CREATIVEDVD-ROM DVD2240E 03/18/98 at ata0-master using WDMA2 Waiting 7 seconds
Re: AIC-7890 problems with kernel build
Hi, And, of course, the kernel config... a fair amount of crap still not trimmed out, but the only difference between this config and the one used to build the functional kernel is apm commented out and ACPI added, which I've already tried reversing without much difference. All I can say is that acpi is initilized after pcib and its children are attached so I don't think ACPI code affects PCI stuff... # Power management support (see LINT for more options) #device apm deviceacpi Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code isn't compiled in your kernel. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code As I mentioned, I've already done so. I know ACPI isn't causing the panic, but it does seem to change the BEHAVIOR of the panic. (I get the errors mentioned by the previous poster with ACPI, while without I proceed directly to the panic). -- Brandon Hume- hume - BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ - Solaris Snob and general NOCMonkey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Mitsuru IWASAKI writes: All I can say is that acpi is initilized after pcib and its children are attached so I don't think ACPI code affects PCI stuff... # Power management support (see LINT for more options) #device apm device acpi Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code isn't compiled in your kernel. That was the first thing I tried when mine failed. It didn't make any difference - I saw the same failure (the page fault, not the SCB errors). FWIW, my working kernel was built August 26, 10:05 GMT. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7890 problems with kernel build
Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code isn't compiled in your kernel. That was the first thing I tried when mine failed. It didn't make any difference - I saw the same failure (the page fault, not the SCB errors). Ah, I haven't read previous mails. I'm sorry about that. # Now I can go to my bed :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC card not recognised?
In article [EMAIL PROTECTED] you wrote: I get the following: pci0: unknown card (vendor=0x9004, dev=0x5078) at 8.0 irq 11 Nothing has changed in this area for some time and the id for this card is in the table of supported devices. Do you get any additional information from a boot -v? -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AIC card not recognised?
I get the following: pci0: unknown card (vendor=0x9004, dev=0x5078) at 8.0 irq 11 from a machine that has: # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp # Qlogic family device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) in it's kernel (with a recent cvsup). I would expect an ahc0 to come up there. It's the Adaptec 2920. I had this in a 3.x machine for quite a long time and it showed up as an ahc0. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
In message [EMAIL PROTECTED] Osamu MIHARA writes: : Is anybody here working on driver for AIC-7899, Ataptec's Ultra160 : SCSI controller??? I thought that Justin just did commits for this. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
On Wed, Feb 02, 2000 at 11:00:56AM +0900, Osamu MIHARA wrote: Is anybody here working on driver for AIC-7899, Ataptec's Ultra160 SCSI controller??? It's working fine here: ahc1: Adaptec 29160 Ultra160 SCSI adapter port 0xb400-0xb4ff mem 0xdf80-0xdf800fff irq 11 at device 12.0 on pci0 OptionMode = 3 ahc1: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs This is under a recent current. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
On Wed, Feb 02, 2000 at 03:07:13PM -0500, Brandon Gale wrote: I was under the impression that although the driver functions properly, the speed is still at 80MB/sec, and not the full 160MB/sec. Correct? I can't say as there are only U2 drives connected. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AIC-7899 SCSI Driver?
Is anybody here working on driver for AIC-7899, Ataptec's Ultra160 SCSI controller??? -- Osamu MIHARA // NEC Printers Division To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
On Wed, Feb 02, 2000 at 11:00:56 +0900, Osamu MIHARA wrote: Is anybody here working on driver for AIC-7899, Ataptec's Ultra160 SCSI controller??? It should work fine under -current. It will only work at Ultra2 speeds right now, Ultra160 support is coming, though. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
It will only work at Ultra2 speeds right now, Ultra160 support is coming, though. To be fair, the sym driver already supports Ultra3. And Qlogic Ultra3 support is coming too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC-7899 SCSI Driver?
On Tue, Feb 01, 2000 at 20:11:38 -0800, Matthew Jacob wrote: It will only work at Ultra2 speeds right now, Ultra160 support is coming, though. To be fair, the sym driver already supports Ultra3. And Qlogic Ultra3 support is coming too. Yes, I should have qualified that. "Ultra160 support for the Adaptec chips is coming." Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
Luoqi Chen wrote: I cannot compile a kernel. It reports the following errors: Did the patch files.diff apply cleanly? It should add one line to each of the sys/conf/files and sys/i386/conf/files.i386, please make sure they are there. The patches did not apply cleanly (maybe I should take a better look at the patch command), but a quick glance at the diff file revealed the two lines to be added. I added them manually, but still the problem exists. Then I took it another step further, and added aic.c and aic.o in the Makefile in the compile directory. This is not how it is supposed to be, I think, but now it compiles. I used the latest files on the site (21 october), and some improvement is noticed, but it still does not work. I only tested the new code under STABLE. When booting with the scanner switched on, it is being recognised and the boot continues, but sane does not recognise it (which it does when the scanner is connected to the on-board controller). When sane is trying to recognise the scanner, a the following line is written in the logs: Oct 22 16:04:39 diabolo /kernel: ccb 0xc0dec800 sense failed 2 A camcontrol rescan times out with the following message: (probe6:aic0:0:6:0): ccb 0xc0df1c00 - timed out I moved then the Philips CD writer (not the greatest of all SCSI devices, but it works) to the aic controller, but then the machine hangs at boot time with a lot of time out messages like: (probe17:aic0:0:2:2): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:2): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:3): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:3): ccb 0xc0dffe00 - timed out ... (probe17:aic0:0:2:7): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:7): ccb 0xc0dffe00 - timed out Between each set of identical lines the CD recorder reinitializes and there is some time (~15s) between the two identical lines. Hope this helps a bit :-) Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 [EMAIL PROTECTED] | 5600 MB Eindhoven, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
aic driver (thanks!) and cdrom
Thanks very much for this driver, Luoqi. I am using it in a -current built from October 14 sources, with a new kernel of course. The cdrom produces the following, though: Oct 22 14:14:35 two /kernel: Waiting 15 seconds for SCSI devices to settle Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:2): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:2): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:3): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:3): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:4): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:4): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:5): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:5): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: Creating DISK da0 Oct 22 14:14:35 two /kernel: Creating DISK da1 Oct 22 14:14:35 two /kernel: Creating DISK cd0 Oct 22 14:14:35 two /kernel: changing root device to da1s2a Oct 22 14:14:35 two /kernel: da0 at aic0 bus 0 target 0 lun 0 Oct 22 14:14:35 two /kernel: da0: QUANTUM VIKING 4.5 NSE 880R Fixed Direct Access SCSI-2 device Oct 22 14:14:35 two /kernel: da0: 5.000MB/s transfers (5.000MHz, offset 8) Oct 22 14:14:35 two /kernel: da0: 4345MB (8899737 512 byte sectors: 64H 32S/T 4345C) Oct 22 14:14:35 two /kernel: da1 at aic0 bus 0 target 1 lun 0 Oct 22 14:14:35 two /kernel: da1: Quantum VP32170 89TC Fixed Direct Access SCSI-2 device Oct 22 14:14:35 two /kernel: da1: 5.000MB/s transfers (5.000MHz, offset 8) Oct 22 14:14:35 two /kernel: da1: 2069MB (4238640 512 byte sectors: 64H 32S/T 2069C) Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): got CAM status 0x20c Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): fatal error, failed to attach to device Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): lost device Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): removing device entry Annelise To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
hooray! aic driver works!
i have just tried the latest version of aic cam driver by Luoqi, and it seems that all significant problems were solved. aic0 at port 0x340-0x35f irq 9 on isa0 ... Waiting 15 seconds for SCSI devices to settle (probe0:aic0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occurred (probe0:aic0:0:0:1): INQUIRY. CDB: 12 20 0 0 24 0 (probe0:aic0:0:0:1): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): INQUIRY. CDB: 12 40 0 0 24 0 (probe0:aic0:0:0:2): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:2): Logical unit not supported (probe0:aic0:0:0:3): INQUIRY. CDB: 12 60 0 0 24 0 (probe0:aic0:0:0:3): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:3): Logical unit not supported (probe0:aic0:0:0:4): INQUIRY. CDB: 12 80 0 0 24 0 (probe0:aic0:0:0:4): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:4): Logical unit not supported (probe0:aic0:0:0:5): INQUIRY. CDB: 12 a0 0 0 24 0 (probe0:aic0:0:0:5): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:5): Logical unit not supported (probe0:aic0:0:0:6): INQUIRY. CDB: 12 c0 0 0 24 0 (probe0:aic0:0:0:6): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:6): Logical unit not supported (probe0:aic0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:aic0:0:0:7): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:7): Logical unit not supported ... Creating DISK cd0 cd0 at aic0 bus 0 target 0 lun 0 cd0: PINNACLE RCD-1000 2.35 Removable Worm SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [261890 x 2048 byte records] drive mounts without any problems and correctly reads data from CD-ROMS. great work, Luoqi! thank you very much! sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
Luoqi Chen wrote: I compiled a kernel for -stable, but was unable to boot from it. Does anyone know if there is any incompatibility between the -current boot loader and a -stable kernel? AFAIK, there is no difference between them (the loaders :). Try from boot2. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "People call him Neutron Star, 'cuz he's so dense lights bends around him." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
Luoqi Chen wrote: I compiled a kernel for -stable, but was unable to boot from it. Does anyone know if there is any incompatibility between the -current boot loader and a -stable kernel? AFAIK, there is no difference between them (the loaders :). Try from boot2. It was not the loader, it was the config file. I used a -current config file without those spl levels, no wonder the machine hung at its earliest convenience... -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "People call him Neutron Star, 'cuz he's so dense lights bends around him." -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: luoqi's aic driver problem
On Tue, 19 Oct 1999, Luoqi Chen wrote: i've tried new "camfied" aic driver today and failed. here is a brief report. results: aic controller was successfully found by the kernel, but after "Waiting 15 seconds for SCSI devices to settle" message it said the following: The request sense command clobbered the original command, I've changed the code from doing that, please download a new copy of aic.c file. i have just tried it. the kernel boots successfully: aic0 at port 0x340-0x35f irq 9 on isa0 ... Waiting 15 seconds for SCSI devices to settle [here the CD-ROM drive flashes with its busy LED] (probe0:aic0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occurred (probe0:aic0:0:0:1): INQUIRY. CDB: 12 20 0 0 24 0 (probe0:aic0:0:0:1): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): INQUIRY. CDB: 12 40 0 0 24 0 (probe0:aic0:0:0:2): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:2): Logical unit not supported (probe0:aic0:0:0:3): INQUIRY. CDB: 12 60 0 0 24 0 (probe0:aic0:0:0:3): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:3): Logical unit not supported (probe0:aic0:0:0:4): INQUIRY. CDB: 12 80 0 0 24 0 (probe0:aic0:0:0:4): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:4): Logical unit not supported (probe0:aic0:0:0:5): INQUIRY. CDB: 12 a0 0 0 24 0 (probe0:aic0:0:0:5): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:5): Logical unit not supported (probe0:aic0:0:0:6): INQUIRY. CDB: 12 c0 0 0 24 0 (probe0:aic0:0:0:6): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:6): Logical unit not supported (probe0:aic0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:aic0:0:0:7): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:7): Logical unit not supported ... cd0 at aic0 bus 0 target 0 lun 0 cd0: PINNACLE RCD-1000 2.35 Removable Worm SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [1 x 77747 byte records] but, unfortunately, scsi probe precedure seems to be relatively unstable. _sometimes_ (often enough) the kernel doesn't boot with the following diagnostics: (probe0:aic0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occured (probe0:aic0:0:0:1): INQURY. CDB: 12 20 0 0 24 0 (probe0:aic0:0:0:1): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): INQURY. CDB: 12 40 0 0 24 0 (probe0:aic0:0:0:2): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:2): Logical unit not supported ccb 0xc0a23400 - timed out ccb 0xc0a23400 - timed out however, even after successful boot, the kernel traps after attempts to mount CD-ROM (mount_cd9660 /dev/cd0c /mnt). here is debug diags: (cd0:aic0:0:0:0): Vendor Specific Command. CDB: 43 0 0 0 0 0 b5 0 64 0 (cd0:aic0:0:0:0): ILLEGAL REQUEST asc:25,0 (cd0:aic0:0:0:0): Logical unit not supported (cd0:aic0:0:0:0): Vendor Specific Command. CDB: 43 0 0 0 0 0 b5 0 64 0 (cd0:aic0:0:0:0): ILLEGAL REQUEST asc:25,0 (cd0:aic0:0:0:0): Logical unit not supported (cd0:aic0:0:0:0): ccb 0xc0a23400 - timed out (cd0:aic0:0:0:0): ccb 0xc0a23400 - timed out then mount_cd9660 dies (cannot be killed with kill -9). (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out Was there a long period between these two messages and the previous ones? yes, it was. what is possible reason of such behaviour and what should i try to do to make my aic/cdrom combination working? For now you could add a quirk entry for this drive to prevent multi-lun probing, ok, but how? :) sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
I also tried to experiment with the aic driver (and also failed, little similar to Ilya's problems) Configuration: Asus P2B-DS motherboard with dual PII-350, 128 Mb of memory, running 4.0-19990918-CURRENT. Adaptec AIC 7890 on-board U2W SCSI controller. Adaptec AVA 1505 (AIC 6360Q) isa SCSI controller. Connected to the isa card is a scanner (Genius Colorpage-I, announcing itself as a Microtek Scanmaker II) which is properly terminated and has SCSI id6. Kernel settings: controller aic0 at isa? port 0x340 irq 11 The controller is successfully found at boot time, but the boot `hangs' (or has a lrge timeout) with: (probe21:aic0:0:6:0)ccb 0xc0c01e00 - timed out (probe21:aic0:0:6:0)ccb 0xc0c01e00 - timed out Both messages appear shortly after each other and then the scanner seems to reinitialize. If I boot with the scanner switched off, the startup is completed normally. If I then switch on the scanner, let it initialize, and issue a `camcontrol rescan 1', the command never completes and is not killable. The command `camcontrol rescan 0' completes normally after which a `camcontrol devlist' correctly lists IBM DCAS-34330W S65A at scbus0 target 0 lun 0 (pass0,da0) IMS CDD2000/00 1.26 at scbus0 target 2 lun 0 (pass1,cd0) as devices. What puzzles me is why the probe at the aic0 wants to look at bus 0. Shouldn't that be bus 1? Or should I add a scbus1 line in my config file (I think of this while I type, I will try this when I have sent this message) TIA Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 [EMAIL PROTECTED] | 5600 MB Eindhoven, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re[2]: luoqi's aic driver problem
Hello Oliver, Wednesday, October 20, 1999, 4:12:37 AM, you wrote: OF Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory it is just Celeron 333A overclocked up to 416 MHz (5 x 83.5). Best regards, Ilyamailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: luoqi's aic driver problem
cd0 at aic0 bus 0 target 0 lun 0
cd0: PINNACLE RCD-1000 2.35 Removable Worm SCSI-2 device
cd0: 3.300MB/s transfers
cd0: cd present [1 x 77747 byte records]
^
These numbers don't look right...
but, unfortunately, scsi probe precedure seems to be relatively
unstable. _sometimes_ (often enough) the kernel doesn't boot with the
following diagnostics:
I have fixed a few places that might have caused the timeout problem.
Could you download the new code and try again? Would you also add these
debug options to your config file?
options CAMDEBUG
options CAM_DEBUG_BUS=-1
options CAM_DEBUG_TARGET=-1
options CAM_DEBUG_LUN=-1
options CAM_DEBUG_FLAGS="CAM_DEBUG_INFO|CAM_DEBUG_TRACE|CAM_DEBUG_CDB"
what is possible reason of such behaviour and what should i try to do to
make my aic/cdrom combination working?
For now you could add a quirk entry for this drive to prevent multi-lun
probing,
ok, but how? :)
Add this entry to the xpt_quirk_table in cam/cam_xpt.c,
{
{ T_WORM, SIP_MEDIA_REMOVABLE, "PINNACLE", "RCD*", "*" },
CAM_QUIRK_NOLUNS, /*mintags*/0, /*maxtags*/0
},
sincerely,
ilya naumov (at work)
Thanks for trying the driver out, I really appreciate your patience. Since I
don't have the hardware myself, I have to rely on your help.
Thanks
-lq
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
I also tried to experiment with the aic driver (and also failed, little similar to Ilya's problems) Could you download the new set of files and see if it helps? as devices. What puzzles me is why the probe at the aic0 wants to look at bus 0. Shouldn't that be bus 1? Or should I add a scbus1 line in my config file (I think of this while I type, I will try this when I have sent this message) I think this bus number is only used to differentiate the individual channels of multi-channel cards. What people usually refer to as bus id is actually the path id, unique for each hba + bus number combination. TIA Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 [EMAIL PROTECTED] | 5600 MB Eindhoven, The Netherlands Thanks -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
Luoqi Chen wrote: I've ported it to -stable, but I don't have a machine to test it, please if you could. The code is in http://www.freebsd.org/~luoqi/aic/stable, apply patch files.diff, copy aic_isa.c to i386/isa, the rest goes to dev/aic. I cannot compile a kernel. It reports the following errors: Did the patch files.diff apply cleanly? It should add one line to each of the sys/conf/files and sys/i386/conf/files.i386, please make sure they are there. It looks as though aic.c is not compiled in. B.T.W., in fist line of aic.c a reference to aic.h is placed, but that file is not present in your directory. aic.h is generated by config, it should be present in the kernel compile directory. I compiled a kernel for -stable, but was unable to boot from it. Does anyone know if there is any incompatibility between the -current boot loader and a -stable kernel? TIA Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 [EMAIL PROTECTED] | 5600 MB Eindhoven, The Netherlands Thanks -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
luoqi's aic driver problem
i've tried new "camfied" aic driver today and failed. here is a brief report. my configuration: Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory Adaptec AIC-6360 SCSI controller (port 0x340 irq 9), irq 9 is reserved for Legacy/ISA card in bios setup Pinnacle 1000 CD writer (with SCSI device ID set to 0) kernel settings: options "CD9660" options "CD9660_ROOT" options SCSI_DELAY=15000 controller scbus0 controller aic0 at isa? port 0x340 irq 9 device cd0 at aic? results: aic controller was successfully found by the kernel, but after "Waiting 15 seconds for SCSI devices to settle" message it said the following: (probe0:aic0:0:0:0): REQUEST SENSE. CDB: 3 0 0 0 20 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occured (probe0:aic0:0:0:1): REQUEST SENSE. CDB: 3 4 0 0 12 0 (probe0:aic0:0:0:1): ILLEGAL REQEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out after that my system just hangs. what is possible reason of such behaviour and what should i try to do to make my aic/cdrom combination working? thank you in advance. sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: luoqi's aic driver problem
i've tried new "camfied" aic driver today and failed. here is a brief report. my configuration: Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory Adaptec AIC-6360 SCSI controller (port 0x340 irq 9), irq 9 is reserved for Legacy/ISA card in bios setup Pinnacle 1000 CD writer (with SCSI device ID set to 0) kernel settings: options "CD9660" options "CD9660_ROOT" options SCSI_DELAY=15000 controller scbus0 controller aic0 at isa? port 0x340 irq 9 device cd0 at aic? should be just "device cd0" results: aic controller was successfully found by the kernel, but after "Waiting 15 seconds for SCSI devices to settle" message it said the following: (probe0:aic0:0:0:0): REQUEST SENSE. CDB: 3 0 0 0 20 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occured (probe0:aic0:0:0:1): REQUEST SENSE. CDB: 3 4 0 0 12 0 (probe0:aic0:0:0:1): ILLEGAL REQEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported The request sense command clobbered the original command, I've changed the code from doing that, please download a new copy of aic.c file. (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out Was there a long period between these two messages and the previous ones? Please try the new aic.c file, it will print out if a different command is holding up the scsi bus. after that my system just hangs. The timeout handling code is flaky, I need to understand how it should work a little better. what is possible reason of such behaviour and what should i try to do to make my aic/cdrom combination working? For now you could add a quirk entry for this drive to prevent multi-lun probing, until we figure out what went wrong. thank you in advance. sincerely, ilya naumov (at work) -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: luoqi's aic driver problem
Probably a Celeron 333a running at an 83.5Mhz FSB. DS Ilya Naumov wrote in list.freebsd-current: Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory Please excuse me -- what is a "Celeron 416A"? Regards Oliver Fromme To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Chris Dillon wrote: Should this apply cleanly to -stable? If so, I'll give it a shot when I get home. I'll answer my own question (which, oddly enough, still hasn't made it to the list after about two hours). I forgot about newbus. It doesn't work, of course, and my Clue Quotient(TM) isn't high enough to backport this to -stable. I think I'll teach myself how to do this next weekend, if nobody else gets to it. :-) I've ported it to -stable, but I don't have a machine to test it, please if you could. The code is in http://www.freebsd.org/~luoqi/aic/stable, apply patch files.diff, copy aic_isa.c to i386/isa, the rest goes to dev/aic. -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
aic driver camified
After the recent signal related changes, the pre-cam kernel I saved a long time ago no longer works with (even statically compiled) user applications, which meant I had no way to access my files on an old disk hanging off an aic6360 card. So I decided to bite the bullet and camify the aic driver myself (I've long given up hope someone else would do it.) The source is at http://www.freebsd.org/~luoqi/aic. Copy the source files into sys/dev/aic, apply the patch files.diff to sys/conf/files. Don't forget to add the controller aic0 line back to your config file. Since I don't have *any* documentation on the chip or card, except for the existing source code (FreeBSD/NetBSD/Linux), and my knowledge of our cam implementation is quite limited, so consider this code extremely experimental and use at your own risk. DMA is not supported, sync transfer is supported but not tested, neither pnp nor pccard is supported. My card doesn't support any of these, so there's not much I could do, I hope sopme of you could fill in the blanks. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Luoqi Chen wrote: DMA is not supported, sync transfer is supported but not tested, neither pnp nor pccard is supported. My card doesn't support any of these, so there's not much I could do, I hope sopme of you could fill in the blanks. Looks pretty good. I'll whip up an MCA front end and try it out when I get home. I suspect someone will want a PCCARD front end as well. I'll write it if someone will work with me on testing. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Luoqi Chen wrote: After the recent signal related changes, the pre-cam kernel I saved a long time ago no longer works with (even statically compiled) user applications, which meant I had no way to access my files on an old disk hanging off an aic6360 card. So I decided to bite the bullet and camify the aic driver myself (I've long given up hope someone else would do it.) Luoqi, you are a god. I bow to thee. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
I suspect someone will want a PCCARD front end as well. I'll write it if someone will work with me on testing. You have a guinie pig^W^Wtester. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Luoqi Chen wrote: After the recent signal related changes, the pre-cam kernel I saved a long time ago no longer works with (even statically compiled) user applications, which meant I had no way to access my files on an old disk hanging off an aic6360 card. So I decided to bite the bullet and camify the aic driver myself (I've long given up hope someone else would do it.) WOOHOO!! I'll be your guinea pig for trying this on -stable if you like. All I have is a ZIP drive to test things with. If it would make any difference, I could also borrow a Yamaha 4260 CD writer and a Sony SDT-S5200 DDS2 drive. The source is at http://www.freebsd.org/~luoqi/aic. Copy the source files into sys/dev/aic, apply the patch files.diff to sys/conf/files. Don't forget to add the controller aic0 line back to your config file. Should this apply cleanly to -stable? If so, I'll give it a shot when I get home. -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: aic driver camified
On Mon, 18 Oct 1999, Chris Dillon wrote: Should this apply cleanly to -stable? If so, I'll give it a shot when I get home. I'll answer my own question (which, oddly enough, still hasn't made it to the list after about two hours). I forgot about newbus. It doesn't work, of course, and my Clue Quotient(TM) isn't high enough to backport this to -stable. I think I'll teach myself how to do this next weekend, if nobody else gets to it. :-) -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AIC
On Sun, Apr 11, 1999 at 11:29:09AM -0500, Bob Willcox wrote: On Wed, Mar 31, 1999 at 12:28:47PM -0800, Brian Beattie wrote: On Wed, 31 Mar 1999, Warner Losh wrote: The aic driver will likely oneday be ported. However, no one has come forward to do it. It is a highly desirable driver to have (even if Umm, I'm still working on the aic driver. Slowly, but working on it. writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. Not having a pcmcia slot or card, I am not sure about support for this. I have both and would be willing to test it on my laptop. If you need a desktop tester of the new AIC driver, give me a shout. Upgrading to 3.0 broke my CDROM and internal Zip drive :-( N -- Bagel: The carbohydrate with the hole To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
On Wed, Mar 31, 1999 at 12:28:47PM -0800, Brian Beattie wrote: On Wed, 31 Mar 1999, Warner Losh wrote: The aic driver will likely oneday be ported. However, no one has come forward to do it. It is a highly desirable driver to have (even if Umm, I'm still working on the aic driver. Slowly, but working on it. writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. Not having a pcmcia slot or card, I am not sure about support for this. I have both and would be willing to test it on my laptop. -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
th , 01 ÁÐÒ 1999, Daniel C. Sobral wrote: Granted, we don't have a driver for that controller either, but the programming manual is readily available from LSI Logic. Seems to me that NetBSD has a driver for it, based on a Linux driver. (Been a while since I looked into it, so I may be misremembering.) It seems programming manuals for the AIC 6[23]60 are also available, and there is even a FreeBSD driver for it... :-) and it is too popular controller to ignore it at all. how ironic - older 2.2.x do support it, but newer 3.1/4.0 does not. i guess that many people have to use 2.2.8 on their old hardware instead of much more progressive 3.1 due to this problem only. and it's a pity :( sincerely, ilya naumov (at work) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
In article 99040212091200.24...@camel.avias.com, Ilya Naumov ca...@avias.com wrote: how ironic - older 2.2.x do support it, but newer 3.1/4.0 does not. What is ironic about that? Old OS versions support old hardware, and new OS versions support new hardware. It makes perfect sense to me. John My Sun 3/180 supported SMD disks, but FreeBSD doesn't! Polstra -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
On Thu, Apr 01, 1999 at 11:55:23AM +0900, Daniel C. Sobral wrote: Brian Beattie wrote: writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. Not having a pcmcia slot or card, I am not sure about support for this. Once aic6[23]60 is working, the PCMCIA stuff is easily done. However, the sad fact is that the development is less than active on this driver. It is a fact, sad? Im not sure. except for the pccard stuff there is much better stuff than the 6x60 based hardware. But there are *no* alternatives for notebooks, except parallel port SCSI. This isn't true. The 3.0 version of Newtek's Bus Toaster uses a Symbios 53C500 chip. I think Newtek still makes them... Granted, we don't have a driver for that controller either, but the programming manual is readily available from LSI Logic. Seems to me that NetBSD has a driver for it, based on a Linux driver. (Been a while since I looked into it, so I may be misremembering.) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
Steven Plite wrote: But there are *no* alternatives for notebooks, except parallel port SCSI. This isn't true. The 3.0 version of Newtek's Bus Toaster uses a Symbios 53C500 chip. I think Newtek still makes them... I meant that there are no alternatives available in 3.x. Granted, we don't have a driver for that controller either, but the programming manual is readily available from LSI Logic. Seems to me that NetBSD has a driver for it, based on a Linux driver. (Been a while since I looked into it, so I may be misremembering.) It seems programming manuals for the AIC 6[23]60 are also available, and there is even a FreeBSD driver for it... :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org nothing better than the ability to perform cunning linguistics To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
On Tue, 30 Mar 1999 18:34:08 +0200, Leif Neland wrote: Is it doomed forever? Grrr, I think the whole reason it was removed was to avoid questions like this. ;-) The removed aic driver is not under active development, and there are no plans to revive it in the foreseeable future. See? :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
The aic driver will likely oneday be ported. However, no one has come forward to do it. It is a highly desirable driver to have (even if writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. However, the sad fact is that the development is less than active on this driver. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
On Wed, 31 Mar 1999, Warner Losh wrote: The aic driver will likely oneday be ported. However, no one has come forward to do it. It is a highly desirable driver to have (even if Umm, I'm still working on the aic driver. Slowly, but working on it. writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. Not having a pcmcia slot or card, I am not sure about support for this. However, the sad fact is that the development is less than active on this driver. It is a fact, sad? Im not sure. except for the pccard stuff there is much better stuff than the 6x60 based hardware. Brian Beattie| The only problem with beat...@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
Brian Beattie wrote: writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. Not having a pcmcia slot or card, I am not sure about support for this. Once aic6[23]60 is working, the PCMCIA stuff is easily done. However, the sad fact is that the development is less than active on this driver. It is a fact, sad? Im not sure. except for the pccard stuff there is much better stuff than the 6x60 based hardware. But there are *no* alternatives for notebooks, except parallel port SCSI. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Yes, I am an agent of Satan, but my duties are largely ceremonial. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
On Tue, 30 Mar 1999, Sheldon Hearn wrote: On Tue, 30 Mar 1999 17:28:06 +0400, Ilya Naumov wrote: i wonder what is the situation with AIC driver now? we're suffering without it :) All traces of it have been completely removed from CURRENT. You should follow your cvs mail. :-) Is it doomed forever? Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: aic
On Sun, Mar 21, 1999 at 08:27:36PM +, Dan Moschuk wrote: Any hope of the aic driver gracing -current anytime soon? I'm really itching to port my burning software over. No one ever bothered to port the aic driver to the new CAM interface in 3.0 and 4.0. Since I know you're capable of it, I'm simply going to direct you to the appropriate mailing list (freebsd-scsi) and look away... ;) Otherwise, you're stuck with 2.2. It's not so bad, I'm running it on this laptop (since pccard doesn't work w/ -current or 3.1-R, I use 2.2.8 and PAO). Cheers, -- Dan Moschuk (tfreak...@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company If at first you don't succeed, redefine success -- Nathan Dorfman nat...@rtfm.net The statements and opinions in my Unix Admin @ Frontline Communicationspublic posts are mine, not FCC's. The light at the end of the tunnel is the headlight of an approaching train. --/usr/games/fortune To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
aic
Any hope of the aic driver gracing -current anytime soon? I'm really itching to port my burning software over. Cheers, -- Dan Moschuk (tfreak...@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company If at first you don't succeed, redefine success To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
aic driver status
For everybody who has been waiting for me finish the aic driver I thought I should give a status report. My move is mostly complete and I am trying to get back to working in the aic driver. Unfortunately I have run into hardware problems. Having just bought a house I can not afford to run out and buy all new hardware. I am currently trying to diagnose the problem, (it could be one or more of: controller, cpu, memory, motherboard). While I would still like to do the driver myself, if there is anybody out there who is itching to work on it themselves you might get in touch with me. Brian Beattie| The only problem with beat...@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: aic (adaptec 152x) still not supported in -current?
I'd love to see the aic supported, mostly for my notebook. However, no one seems to have a confluance of time, information and talent to write the driver, or even port the other one in all its gory. If CAMed aic driver is available, SlimSCSI support is very easy. First of all, we need CAMed aic driver. -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: aic (adaptec 152x) still not supported in -current?
Kenneth D. Merry wrote: At the moment, looking in LINT, it looks like aic still isn't supported. Is that true? Does anyone know whether it will be? It's true that it isn't supported yet. We are planning on supporting it. Brian Beattie is the one working on it, you should probably ask him how it is coming along. I have no idea when support will appear. If you want SCSI support any time soon, I would suggest getting a supported card. An ISA Advansys card might be a good, cheap substitute for your 6360/6260 board. I was under the impression that SlimSCSI was 152x-compatible. PCMCIA SCSI support is very lacking in FreeBSD-current. (Soon to be -stable!) -- Daniel C. Sobral(8-DCS) d...@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
aic (adaptec 152x) still not supported in -current?
Hello, When CAM was integrated someone reported that the aic driver was not ready yet for CAM, but that Brian Beattie beat...@aracnet.com is working on it. At the moment, looking in LINT, it looks like aic still isn't supported. Is that true? Does anyone know whether it will be? Thanks, -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know p...@xs4all.nl | the Netherlands| what I'm doing. ---+-+- Running FreeBSD-3.0 UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: aic (adaptec 152x) still not supported in -current?
Peter Mutsaers wrote... Hello, When CAM was integrated someone reported that the aic driver was not ready yet for CAM, but that Brian Beattie beat...@aracnet.com is working on it. Right. At the moment, looking in LINT, it looks like aic still isn't supported. Is that true? Does anyone know whether it will be? It's true that it isn't supported yet. We are planning on supporting it. Brian Beattie is the one working on it, you should probably ask him how it is coming along. I have no idea when support will appear. If you want SCSI support any time soon, I would suggest getting a supported card. An ISA Advansys card might be a good, cheap substitute for your 6360/6260 board. Ken -- Kenneth Merry k...@plutotech.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: aic (adaptec 152x) still not supported in -current?
If you want SCSI support any time soon, I would suggest getting a supported card. An ISA Advansys card might be a good, cheap substitute for your 6360/6260 board. Adaptec SlimSCSI is major PC-Card SCSI-IF, it is based on aic6360. Now, aic not supported yet, so Note-PC user can't use any PC-Card SCSI-IF. In PAO, another PC-Card SCSI-IF supported, but these are 2.2-stable only, not yet CAMed. -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: aic (adaptec 152x) still not supported in -current?
In message 199901190613.paa06...@chandra.eatell.msr.prug.or.jp NAKAGAWA Yoshihisa writes: : Adaptec SlimSCSI is major PC-Card SCSI-IF, it is based on : aic6360. Now, aic not supported yet, so Note-PC user can't use any : PC-Card SCSI-IF. I'd love to see the aic supported, mostly for my notebook. However, no one seems to have a confluance of time, information and talent to write the driver, or even port the other one in all its gory. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
