search for: sym0

...SIGNED MESSAGE----- Hash: SHA1 This seems to be an old problem, but I haven't found much about it. SuSE mentions "hwprobe=-pci" but, as far as I know, CentOS doesn't use it. This does stop the machine from booting (mounting /) quite a few times. Logs: SCSI subsystem initialized sym0: <895> rev 0x2 at pci 0000:00:13.0 irq 177 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: SCSI BUS has been reset. scsi0 : sym-2.1.18j Using cfq io scheduler Vendor: WDIGTL Model:...

Greetings I'm trying to install FreeBSD on a HP Cluster Server. But when I boot with the CD's ( 4.4, 4.8 & 5.0 ), it will boot all the way upto "Wait 15 seconds for SCSI devices to settle" and then it immedialty give the following message: (noperiph:sym0:0:-1:-1):SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1):SCSI BUS reset delivered. After this the machine is basically unresponsive/dead. Any idea what could be causing this and what I could do to fix it ? e.

....0 on pci1 tl0: Ethernet address: 00:08:c7:78:08:57 miibus0: <MII bus> on tl0 nsphy0: <DP83840 10/100 media interface> on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto tlphy0: <ThunderLAN 10baseT media interface> on miibus0 tlphy0: 10base2/BNC, 10base5/AUI sym0: <875> port 0x6000-0x60ff mem 0x40000000-0x40000fff,0x40001400-0x400014ff irq 11 at device 9.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking dc0: <Intel 21143 10/100BaseTX> port 0x6400-0x647f mem 0x40001000-0x400013ff irq 9 at device 10.0 on pci1 dc0: Ethernet address: 00:4...

...0: <LSILogic MegaRAID 1.53> mem 0xf6010000-0xf601ffff irq 20 at device 2.1 on pci3 amr0: <Series 466> Firmware F.02.02, BIOS B.02.01, 16MB RAM aac0: <Adaptec SCSI RAID 2410SA> mem 0xf8000000-0xfbffffff irq 23 at device 5.0 on pci3 aac0: [FAST] aac0: Adaptec Raid Controller 2.0.0-1 sym0: <896> port 0x2000-0x20ff mem 0xf6004000-0xf60043ff,0xf6000000-0xf6001fff irq 24 at device 6.0 on pci3 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPT...

...#1 intpin 13 -> irq 2 IOAPIC #1 intpin 12 -> irq 16 IOAPIC #1 intpin 2 -> irq 17 IOAPIC #1 intpin 7 -> irq 18 pcib1: <PCI-PCI bridge> at device 0.1 on pci0 pci1: <PCI bus> on pcib1 IOAPIC #1 intpin 1 -> irq 19 pci1: <display, VGA> at device 0.0 (no driver attached) sym0: <896> port 0xf800-0xf8ff mem 0xfeafe000-0xfeafffff,0xfeafac00-0xfeafafff irq 2 at device 1.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-40, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS....

...nderstand what is going on here. THe device /dev/da0s1a exists. I compiled the new kernel using the same kernel config file I used to compile my 4.7RELEASE kernel. My old kernel boots the system just fine. The computer is a Compaq Proliant 1600. The SCSI device is detected as follows during boot: sym0: <875> port 0x2000-0x20ff mem 0xc6fff000-0xc6ffffff,0xc6ffdf00-0xc6ffdfff irq 9 at device 9.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking da0 at sym0 bus 0 target 0 lun 0 In my kernel configuration file I have this line device sym # NCR/Symbios Logic (newer chipsets)...

...y on channel 2. During boot, I can see all disks being identified first by the machine itself and then in the early part of the process (something scrolls by talking about BIOS drive numbering). However, the result is not 8 drives but 5 in total in a mix between the channels, see below. da0 at sym0 bus 0 target 0 lun 0 da0: <COMPAQ AB00931B92 3AS8> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da4 at sym1 bus 0 target 4 lun 0 da4: <COMPAQ MAB3091SC 0814>...

Hello, I tried to install Yamaha cdrw at FreeBSD 5.1. At 4.8 stable all was Ok. Now I have in kernel configuration sym device. But cdrecord shows message "No such file or directory. Cannot open SCSI driver". Maybe I must have /dev/sym0 device or something else? If yes, then how to create it with help of devfs? There are no much info in devfs's manual. -- Oleg Shevtsov

I'm building another server and must decide on scsi card the tekram looks very promising to me but need to know if it will be supported or not in 4.8 or 5.1. server will be used of mysql / apache. any info or suggestions as to scsi cards would be great. thx in advance. Sign, Eriq

...his kernel? The reason I'm trying to compile an new kernel is that my system uses a LSI Logic/Symbios Logic 53c875 SCSI controller (information obtained from "System Tools/Hardware Browser" menu in GNOME) and I keep getting a bunch of errors like the following in my system logs: sym0:0:0:phase change 6-7 11 at 12856b84 resid=2. I read somewhere that by compiling a new kernel (2.6.11, I think), this problem might go away and I wanted my system to run as efficiently so decided to compile a new kernel. Am I doing the right thing? Thanks! Sincerely Jose

i trust i am still new in freebsd, after go through all mail and book, = now seem to be more close, i got 3 server and a notebook to play with, = install no problem. cvsup not problem.make buildworld not problem. make = build kernel become,every machine i got different error code 1,=20 1-one got system full=20 2-one showing this sometime=20 > anyone know the best way to be one time success,not

...000. VESA: v2.0, 1024k memory, flags:0x0, mode table:0xc02ff602 (1000022) VESA: ATI MACH64 Pentium Pro MTRR support enabled npx0: <math processor> on motherboard npx0: INT 16 interface pcib0: <Intel 82443BX host to PCI bridge (AGP disabled)> on motherboard pci0: <PCI bus> on pcib0 sym0: <875> port 0x2000-0x20ff mem 0xc6aff000-0xc6afffff,0xc6afaf00-0xc6afafff irq 10 at device 6.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x2400-0x24ff mem 0xc6afe000-0xc6afefff,0xc6afae00-0xc6afaeff irq 11 at device 6.1 on pci0 sym1: No NVRAM, ID 7, Fas...

Hi, Updated to current bk today, and my machine stopped booting ... I''ve tracked it down to the apic changes from end of last week. cset 1.1307 boots fine, 1.1308 doesn''t. Diff of the boot messages is below. Full logs are also attached. Gerd --- log-1.1307 2005-04-21 14:40:57.372885027 +0200 +++ log-1.1308 2005-04-21 14:38:52.236553392 +0200 @@ -7,7 +7,7 @@

...) anymore (the loader could), it can't see the root partition. These Compaq Proliants don't have a real BIOS configuration without installing a DOS partition on your system drive, so you just can't set the boot device to IDE. The 4.8 kernel recognizies the proliant's SCSI as a sym0 and sym1 devices (875 is in parenthesis, and I believe it's the chipset number). Question being, anybody experienced anything similar with Compaq proliants not seeing the system disk when booting from a floppy or the primary system disk (SCSI)? We're going to try and rever to an older...

...I bridge (vendor=8086 device=5200)> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pci0: <unknown card> (vendor=0x8086, dev=0x5201) at 1.1 irq 9 pci0: <NVidia Riva Ultra Vanta TNT2 graphics accelerator> at 2.0 irq 5 pci0: <unknown card> (vendor=0x0e11, dev=0xa0f0) at 12.0 sym0: <875> port 0x2000-0x20ff mem 0xc4fd0000-0xc4fd0fff,0xc4fe0000-0xc4fe00ff irq 10 at device 13.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x2400-0x24ff mem 0xc4fb0000-0xc4fb0fff,0xc4fc0000-0xc4fc00ff irq 15 at device 13.1 on pci0 sym1: No NVRAM, ID 7, F...

....0 on pci1 tl0: Ethernet address: 00:08:c7:9f:78:1e miibus0: <MII bus> on tl0 nsphy0: <DP83840 10/100 media interface> on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto tlphy0: <ThunderLAN 10baseT media interface> on miibus0 tlphy0: 10base2/BNC, 10base5/AUI sym0: <875> port 0x2000-0x20ff mem 0xc6eff000-0xc6efffff,0xc6efcf00-0xc6efcfff i rq 9 at device 9.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x2400-0x24ff mem 0xc6efe000-0xc6efefff,0xc6efce00-0xc6efceff i rq 10 at device 9.1 on pci1 sym1: No NVRAM, ID 7, Fa...

...;PCI bus> on pcib1 > > pci0: <unknown card> (vendor=0x8086, dev=0x5201) at 1.1 > irq > > 9 > > pci0: <NVidia Riva Ultra Vanta TNT2 graphics accelerator> > at > > 2.0 irq 5 > > pci0: <unknown card> (vendor=0x0e11, dev=0xa0f0) at 12.0 > > sym0: <875> port 0x2000-0x20ff mem > > 0xc4fd0000-0xc4fd0fff,0xc4fe0000-0xc4fe00ff irq 10 at > device > > 13.0 on pci0 > > sym0: No NVRAM, ID 7, Fast-20, SE, parity checking > > sym1: <875> port 0x2400-0x24ff mem > > 0xc4fb0000-0xc4fb0fff,0xc4fc0000-0xc4fc00f...

...hci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1 [ 2.351257] uhci_hcd 0000:00:01.2: irq 11, io base 0x0000c140 [ 2.351428] hub 1-0:1.0: USB hub found [ 2.351431] hub 1-0:1.0: 2 ports detected [ 2.352073] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 2.353482] sym0: <895a> rev 0x0 at pci 0000:00:05.0 irq 11 [ 2.355767] sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking [ 2.361853] virtio-pci 0000:00:03.0: irq 40 for MSI/MSI-X [ 2.361890] virtio-pci 0000:00:03.0: irq 41 for MSI/MSI-X [ 2.361918] virtio-pci 0000:00:03.0: irq 43 for MSI/MSI-X...