Date: Sun, 6 Jun 1999 14:07:48 +0100 From: "Steve Howe" <steve.howe@lhowe.freeserve.co.uk> To: "Mark Ovens" <markov@globalnet.co.uk> Cc: <freebsd-questions@FreeBSD.org> Subject: Re: Ex-buffoon seeks ATAPI CDROM advice Message-ID: <000b01beb01d$b96fbac0$f8b3883e@default> References: <001301beaf78$4f666700$67b4883e@default> <19990606103813.A254@marder-1>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Hi, yeah, sorry about the lack of diagnostics before. I've done some tech support in my time and I guess the previous message was about as helpful as the "****ing systems ****ed!" Sorry about the length of this, it's unavoidable! Herewith the dmesg output: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.8-RELEASE #0: Sat Jun 5 16:15:31 BST 1999 root@myname.my.domain:/usr/src/sys/compile/MYKERNEL CPU: Pentium II (quarter-micron) (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,<b16>,<b17>,MMX,<b24>> real memory = 67108864 (65536K bytes) avail memory = 63746048 (62252K bytes) Probing for devices on PCI bus 0: chip0 <generic PCI bridge (vendor=8086 device=7190 subclass=0)> rev 2 on pci0:0:0 chip1 <generic PCI bridge (vendor=8086 device=7191 subclass=4)> rev 2 on pci0:1:0 chip2 <Intel 82371AB PCI-ISA bridge> rev 2 on pci0:7:0 chip3 <Intel 82371AB IDE interface> rev 1 on pci0:7:1 chip4 <Intel 82371AB USB interface> rev 1 int d irq ?? on pci0:7:2 chip5 <Intel 82371AB Power management controller> rev 2 on pci0:7:3 pci0:9: VIA Technologies, device=0x3043, class=network (ethernet) int a irq ?? [no driver assigned] Probing for devices on PCI bus 1: vga0 <VGA-compatible display device> rev 92 on pci1:0:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff psm0 at 0x60-0x64 irq 12 on motherboard psm0: model MouseMan+, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): <QUANTUM Bigfoot TX8.0AT> wd0: 7665MB (15698592 sectors), 15574 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa npx0 flags 0x1 on motherboard npx0: INT 16 interface changing root device to wd0s2e And this is the kernel that generated it: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # <URL:http://www.FreeBSD.ORG/>; # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.77.2.28 1998/09/26 17:36:14 wpaul Exp $ # # machine "i386" cpu "I686_CPU" ident MYKERNEL maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem #options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 #controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM #device wfd0 #IDE floppy (LS-120) # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. #controller ncr0 #controller amd0 #controller ahb0 #controller ahc0 #controller dpt0 #controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr options DPT_MEASURE_PERFORMANCE # Required by DPT driver?? #options DPT_VERIFY_HINTR # Some hardware must have it! #options DPT_TRACK_CCB_STATES # Some hardware must have it! #options DPT_HANDLE_TIMEOUTS # Some hardware must have it! #options DPT_TIMEOUT_FACTOR=4 # Some hardware needs more #controller scbus0 #device sd0 #device od0 #See LINT for possible `od' options. #device st0 #device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? disable # Advanced Power Management #options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 #device fxp0 #device tl0 #device tx0 #device vx0 #device xl0 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port? net irq? vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr #device cs0 at isa? disable port 0x300 net irq ? vector csintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 pseudo-device ppp 1 pseudo-device vn 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM thanks for all help, Steve ----- Original Message ----- From: Mark Ovens To: Steve Howe Cc: freebsd-questions@FreeBSD.org Sent: 06 June 1999 10:38 Subject: Re: Ex-buffoon seeks ATAPI CDROM advice On Sat, Jun 05, 1999 at 06:24:19PM +0100, Steve Howe wrote: > Hi, > > first thanks to Oscar, Mark, Chris, Woody & Doug for the > useful advice last time I mailed this group. I eventually > successfully installed FreeBSD from a DOS (spit) partition. > > I am now able to do some unixy things. Hoorah! > > But now I want to get my hands on the ports residing on the > CDROMs. > > I am still having trouble getting the kernel to recognise > my CDROM though. > > As Doug pointed out last time round an ATAPI IDE CDROM, > while not supported in the novice installation, > is referenced in the GENERIC kernel. > > So in the MYKERNEL version (which I have now succesfully > built and installed 6 times!) I have uncommented-out the: > > options ATAPI > options ATAPI_STATIC > device wcd0 > > entries, while leaving, as advised on the web site, the > > controller wdc1 > disk wd2 > disk wd3 > > options which actually point at the relevant controller. > > At boot-up time however the kernel seems to make no attempt > to resolve the wcd0 device I've told it to in MYKERNEL, and > consequently I am not able to mount it after I've logged in. > You need to include the boot messages in your mail. Type ``dmesg'' at the prompt and include the output in your mail, then we will have a clue as to what is happening :-) > I had a search round the website and found one link which seemed > to suggest that the ATAPI interface was experimental and should be > regarded as alpha. So is this a problem in 2.2.8? > Uh, it was back in the 2.1 days, in 2.2.8 it is stable although IDE/ATAPI seems to be one of those variable standards (some devices are more standard than others). There are cases where one make of IDE disk won't run as slave to another make. With CD-ROMs it is sometimes the case that they won't work when slaved to a HD, or are the slave when there is no master on the same channel. > Most advice gratefully received, > > thanks, > > Steve Howe > Harpenden > England (0 Sweden 0) > > -- FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://www.users.globalnet.co.uk/~markov _______________________________________________________________ Mark Ovens, CNC Apps Engineer, Radan Computational Ltd. Bath UK CAD/CAM solutions for Sheetmetal Working Industry mailto:marko@uk.radan.com http://www.radan.com [-- Attachment #2 --] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.2314.1000" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV>Hi,</DIV> <DIV> </DIV> <DIV>yeah, sorry about the lack of diagnostics before. I've done some tech support in my time and </DIV> <DIV>I guess the previous message was about as helpful as the "****ing systems ****ed!"</DIV> <DIV> </DIV> <DIV>Sorry about the length of this, it's unavoidable!</DIV> <DIV> </DIV> <DIV>Herewith the dmesg output:</DIV> <DIV> </DIV> <DIV>Copyright (c) 1992-1998 FreeBSD Inc.<BR>Copyright (c) 1982, 1986, 1989, 1991, 1993<BR>The Regents of the University of California. All rights reserved.<BR>FreeBSD 2.2.8-RELEASE #0: Sat Jun 5 16:15:31 BST 1999<BR><A href="mailto:root@myname.my.domain:/usr/src/sys/compile/MYKERNEL">root@myname.my.domain:/usr/src/sys/compile/MYKERNEL</A><BR>CPU: Pentium II (quarter-micron) (451.02-MHz 686-class CPU)<BR>Origin = "GenuineIntel" Id = 0x652 Stepping=2<BR>Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,<BR>MCA,CMOV,<b16>,<b17>,MMX,<b24>><BR>real memory = 67108864 (65536K bytes)<BR>avail memory = 63746048 (62252K bytes)<BR>Probing for devices on PCI bus 0:<BR>chip0 <generic PCI bridge (vendor=8086 device=7190 subclass=0)> rev 2 on pci0:0:0<BR>chip1 <generic PCI bridge (vendor=8086 device=7191 subclass=4)> rev 2 on pci0:1:0<BR>chip2 <Intel 82371AB PCI-ISA bridge> rev 2 on pci0:7:0<BR>chip3 <Intel 82371AB IDE interface> rev 1 on pci0:7:1<BR>chip4 <Intel 82371AB USB interface> rev 1 int d irq ?? on pci0:7:2<BR>chip5 <Intel 82371AB Power management controller> rev 2 on pci0:7:3<BR>pci0:9: VIA Technologies, device=0x3043, class=network (ethernet) int a irq ?? [no driver assigned]<BR>Probing for devices on PCI bus 1:<BR>vga0 <VGA-compatible display device> rev 92 on pci1:0:0<BR>Probing for devices on the ISA bus:<BR>sc0 at 0x60-0x6f irq 1 on motherboard<BR>sc0: VGA color <16 virtual consoles, flags=0x0><BR>sio0 at 0x3f8-0x3ff irq 4 on isa<BR>sio0: type 16550A<BR>sio1: configured irq 3 not in bitmap of probed irqs 0<BR>sio1 not found at 0x2f8<BR>lpt0 at 0x378-0x37f irq 7 on isa<BR>lpt0: Interrupt-driven port<BR>lp0: TCP/IP capable interface<BR>lpt1 not found at 0xffffffff<BR>psm0 at 0x60-0x64 irq 12 on motherboard<BR>psm0: model MouseMan+, device ID 0<BR>fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa<BR>fdc0: FIFO enabled, 8 bytes threshold<BR>fd0: 1.44MB 3.5in<BR>wdc0 at 0x1f0-0x1f7 irq 14 on isa<BR>wdc0: unit 0 (wd0): <QUANTUM Bigfoot TX8.0AT><BR>wd0: 7665MB (15698592 sectors), 15574 cyls, 16 heads, 63 S/T, 512 B/S<BR>wdc1 at 0x170-0x177 irq 15 on isa<BR>npx0 flags 0x1 on motherboard<BR>npx0: INT 16 interface<BR>changing root device to wd0s2e<BR></DIV> <DIV>And this is the kernel that generated it:</DIV> <DIV> </DIV> <DIV>#<BR># GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks<BR>#<BR># For more information read the handbook part System Administration -> <BR># Configuring the FreeBSD Kernel -> The Configuration File. <BR># The handbook is available in /usr/share/doc/handbook or online as<BR># latest version from the FreeBSD World Wide Web server <BR># <<A href="http://www.FreeBSD.ORG/">URL:http://www.FreeBSD.ORG/</A>><BR>#<BR># An exhaustive list of options and more detailed explanations of the <BR># device lines is present in the ./LINT configuration file. If you are <BR># in doubt as to the purpose or necessity of a line, check first in LINT.<BR>#<BR># $Id: GENERIC,v 1.77.2.28 1998/09/26 17:36:14 wpaul Exp $<BR># <BR># <BR>machine "i386"<BR>cpu "I686_CPU"<BR>ident MYKERNEL<BR>maxusers 32</DIV> <DIV> </DIV> <DIV>options MATH_EMULATE #Support for x87 emulation<BR>options INET #InterNETworking<BR>options FFS #Berkeley Fast Filesystem<BR>#options NFS #Network Filesystem<BR>#options MSDOSFS #MSDOS Filesystem<BR>options "CD9660" #ISO 9660 Filesystem<BR>options PROCFS #Process filesystem<BR>options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!]<BR>options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device<BR>options BOUNCE_BUFFERS #include support for DMA bounce buffers<BR>options UCONSOLE #Allow users to grab the console<BR>options FAILSAFE #Be conservative<BR>options USERCONFIG #boot -c editor<BR>options VISUAL_USERCONFIG #visual boot -c editor</DIV> <DIV> </DIV> <DIV>config kernel root on wd0</DIV> <DIV> </DIV> <DIV>controller isa0<BR>#controller eisa0<BR>controller pci0<BR>controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr<BR>disk fd0 at fdc0 drive 0<BR>disk fd1 at fdc0 drive 1<BR># Unless you know very well what you're doing, leave ft0 at drive 2, or<BR># remove the line entirely if you don't need it. Trying to configure<BR># it on another unit might cause surprises, see PR kern/7176.<BR>#tape ft0 at fdc0 drive 2</DIV> <DIV> </DIV> <DIV>options "CMD640" # work around CMD640 chip deficiency<BR>controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr<BR>disk wd0 at wdc0 drive 0<BR>disk wd1 at wdc0 drive 1</DIV> <DIV> </DIV> <DIV>controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr<BR>disk wd2 at wdc1 drive 0<BR>disk wd3 at wdc1 drive 1<BR>options ATAPI #Enable ATAPI support for IDE bus<BR>options ATAPI_STATIC #Don't do it as an LKM<BR>device wcd0 #IDE CD-ROM<BR>#device wfd0 #IDE floppy (LS-120)<BR># A single entry for any of these controllers (ncr, ahb, ahc, amd) is<BR># sufficient for any number of installed devices.</DIV> <DIV> </DIV> <DIV>#controller ncr0<BR>#controller amd0<BR>#controller ahb0<BR>#controller ahc0<BR>#controller dpt0<BR>#controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr<BR>#controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr<BR>#controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr<BR>#controller aic0 at isa? port 0x340 bio irq 11 vector aicintr<BR>#controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr<BR>#controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr<BR>#controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr<BR>options DPT_MEASURE_PERFORMANCE # Required by DPT driver??<BR>#options DPT_VERIFY_HINTR # Some hardware must have it!<BR>#options DPT_TRACK_CCB_STATES # Some hardware must have it!<BR>#options DPT_HANDLE_TIMEOUTS # Some hardware must have it!<BR>#options DPT_TIMEOUT_FACTOR=4 # Some hardware needs more<BR>#controller scbus0</DIV> <DIV> </DIV> <DIV>#device sd0<BR>#device od0 #See LINT for possible `od' options.<BR>#device st0<BR>#device cd0 #Only need one of these, the code dynamically grows<BR>#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr<BR>#device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr<BR>#controller matcd0 at isa? port 0x230 bio<BR>#device scd0 at isa? port 0x230 bio<BR># syscons is the default console driver, resembling an SCO console<BR>device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr<BR># Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver<BR>#device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint<BR>#options XSERVER # support for X server<BR>#options FAT_CURSOR # start with block cursor<BR># If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines<BR>#options PCVT_SCANSET=2 # IBM keyboards are non-std</DIV> <DIV> </DIV> <DIV># Mandatory, don't remove<BR>device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr<BR>#<BR># Laptop support (see LINT for more options)<BR>#<BR>#device apm0 at isa? disable # Advanced Power Management<BR>#options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS<BR># PCCARD (PCMCIA) support<BR>#controller card0<BR>#device pcic0 at card?<BR>#device pcic1 at card?</DIV> <DIV> </DIV> <DIV>device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr<BR>device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr<BR>device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr<BR>device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr</DIV> <DIV> </DIV> <DIV>device lpt0 at isa? port? tty irq 7 vector lptintr<BR>device lpt1 at isa? port? tty<BR>#device mse0 at isa? port 0x23c tty irq 5 vector mseintr<BR>device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr<BR># Order is important here due to intrusive probes, do *not* alphabetize<BR># this list of network interfaces until the probes have been fixed.<BR># Right now it appears that the ie0 must be probed before ep0. See<BR># revision 1.20 of this file.<BR>#device de0<BR>#device fxp0<BR>#device tl0<BR>#device tx0<BR>#device vx0<BR>#device xl0</DIV> <DIV> </DIV> <DIV>#device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr<BR>#device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr<BR>#device ep0 at isa? port 0x300 net irq 10 vector epintr<BR>#device ex0 at isa? port? net irq? vector exintr<BR>#device fe0 at isa? port 0x300 net irq ? vector feintr<BR>#device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr<BR>#device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr<BR>#device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr<BR>#device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr<BR>#device cs0 at isa? disable port 0x300 net irq ? vector csintr</DIV> <DIV> </DIV> <DIV>pseudo-device loop<BR>pseudo-device ether<BR>pseudo-device log<BR>pseudo-device sl 1<BR>pseudo-device ppp 1<BR>pseudo-device vn 1<BR>pseudo-device tun 1<BR>pseudo-device pty 16<BR>pseudo-device gzip # Exec gzipped a.out's</DIV> <DIV> </DIV> <DIV># KTRACE enables the system-call tracing facility ktrace(2).<BR># This adds 4 KB bloat to your kernel, and slightly increases<BR># the costs of each syscall.<BR>options KTRACE #kernel tracing<BR># This provides support for System V shared memory.<BR>#<BR>options SYSVSHM</DIV> <DIV> </DIV> <DIV>thanks for all help,</DIV> <DIV> </DIV> <DIV>Steve<BR></DIV> <BLOCKQUOTE style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV> <DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> <A href="mailto:markov@globalnet.co.uk" title=markov@globalnet.co.uk>Mark Ovens</A> </DIV> <DIV style="FONT: 10pt arial"><B>To:</B> <A href="mailto:steve.howe@lhowe.freeserve.co.uk" title=steve.howe@lhowe.freeserve.co.uk>Steve Howe</A> </DIV> <DIV style="FONT: 10pt arial"><B>Cc:</B> <A href="mailto:freebsd-questions@FreeBSD.org" title=freebsd-questions@FreeBSD.org>freebsd-questions@FreeBSD.org</A> </DIV> <DIV style="FONT: 10pt arial"><B>Sent:</B> 06 June 1999 10:38</DIV> <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: Ex-buffoon seeks ATAPI CDROM advice</DIV> <DIV><BR></DIV>On Sat, Jun 05, 1999 at 06:24:19PM +0100, Steve Howe wrote:<BR>> Hi,<BR>> <BR>> first thanks to Oscar, Mark, Chris, Woody & Doug for the <BR>> useful advice last time I mailed this group. I eventually<BR>> successfully installed FreeBSD from a DOS (spit) partition.<BR>> <BR>> I am now able to do some unixy things. Hoorah! <BR>> <BR>> But now I want to get my hands on the ports residing on the <BR>> CDROMs.<BR>> <BR>> I am still having trouble getting the kernel to recognise <BR>> my CDROM though. <BR>> <BR>> As Doug pointed out last time round an ATAPI IDE CDROM, <BR>> while not supported in the novice installation,<BR>> is referenced in the GENERIC kernel.<BR>> <BR>> So in the MYKERNEL version (which I have now succesfully <BR>> built and installed 6 times!) I have uncommented-out the:<BR>> <BR>> options ATAPI<BR>> options ATAPI_STATIC<BR>> device wcd0<BR>> <BR>> entries, while leaving, as advised on the web site, the <BR>> <BR>> controller wdc1<BR>> disk wd2<BR>> disk wd3<BR>> <BR>> options which actually point at the relevant controller.<BR>> <BR>> At boot-up time however the kernel seems to make no attempt <BR>> to resolve the wcd0 device I've told it to in MYKERNEL, and <BR>> consequently I am not able to mount it after I've logged in.<BR>> <BR><BR>You need to include the boot messages in your mail. Type ``dmesg''<BR>at the prompt and include the output in your mail, then we will<BR>have a clue as to what is happening :-)<BR><BR>> I had a search round the website and found one link which seemed<BR>> to suggest that the ATAPI interface was experimental and should be <BR>> regarded as alpha. So is this a problem in 2.2.8?<BR>> <BR><BR>Uh, it was back in the 2.1 days, in 2.2.8 it is stable although<BR>IDE/ATAPI seems to be one of those variable standards (some devices<BR>are more standard than others). There are cases where one make of<BR>IDE disk won't run as slave to another make. With CD-ROMs it is<BR>sometimes the case that they won't work when slaved to a HD, or<BR>are the slave when there is no master on the same channel.<BR><BR>> Most advice gratefully received,<BR>> <BR>> thanks,<BR>> <BR>> Steve Howe<BR>> Harpenden<BR>> England (0 Sweden 0)<BR>> <BR>> <BR><BR>-- <BR> FreeBSD - The Power To Serve <A href="http://www.freebsd.org">http://www.freebsd.org</A><BR> My Webpage <A href="http://www.users.globalnet.co.uk/~markov">http://www.users.globalnet.co.uk/~markov</A><BR>_______________________________________________________________<BR>Mark Ovens, CNC Apps Engineer, Radan Computational Ltd. Bath UK<BR>CAD/CAM solutions for Sheetmetal Working Industry<BR><A href="mailto:marko@uk.radan.com">mailto:marko@uk.radan.com</A> <A href="http://www.radan.com">http://www.radan.com</A><BR><BR></BLOCKQUOTE></BODY></HTML>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000b01beb01d$b96fbac0$f8b3883e>