missing asm-x86_64 detection

2008-01-31 Thread Reinaldo Carvalho
:/# uname -a
Linux devil 2.6.22.16-amd64 #15 SMP Sat Jan 19 13:58:02 BRT 2008
x86_64 GNU/Linux

:/# cd /usr/src/linux-2.6.22
:/# patch -p1 -R < ../patch-2.6.22.16
:/# patch -p1 < ../patch-2.6.23
:/# patch -p1 < ../patch-2.6.24
:/# cd /usr/src/ ; mv linux-2.6.22 linux-2.6.24; cd linux-2.6.24
:/usr/src/linux-2.6.24# make oldconfig
:/usr/src/linux-2.6.24# make all
  CHK include/linux/version.h
  CHK include/linux/utsrelease.h
ERROR: the symlink include/asm points to asm-x86_64 but asm-x86 was expected
   set ARCH or save .config and run 'make mrproper' to fix it
make: ** [include/asm] Erro 1

:/usr/src/linux-2.6.24# cp .config ../config-2.6.24
:/usr/src/linux-2.6.24# make mrproper
  CLEAN   scripts/basic
  CLEAN   scripts/genksyms
  CLEAN   scripts/kconfig
  CLEAN   scripts/mod
  CLEAN   scripts
  CLEAN   include/config
  CLEAN   .config .config.old include/asm .version
include/linux/autoconf.h include/linux/version.h
include/linux/utsrelease.h Module.symvers
devil:/usr/src/linux-2.6.24# cp ../config-2.6.24 .config
devil:/usr/src/linux-2.6.24# make oldconfig
devil:/usr/src/linux-2.6.24# make all
scripts/kconfig/conf -s arch/x86/Kconfig
  CHK include/linux/version.h
  UPD include/linux/version.h
  CHK include/linux/utsrelease.h
  UPD include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
  CC  arch/x86/kernel/asm-offsets.s
  GEN include/asm-x86/asm-offsets.h
...

system is x86_64!

:/# grep model\ name /proc/cpuinfo
model name  : AMD Turion(tm) 64 X2
model name  : AMD Turion(tm) 64 X2

:/# uname -a
Linux devil 2.6.22.16-amd64 #15 SMP Sat Jan 19 13:58:02 BRT 2008
x86_64 GNU/Linux


-- 
Reinaldo Carvalho
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


megaraid.c, all kernel versions, problem with multi-luns

2007-05-30 Thread Reinaldo Carvalho

Hi,

I have a Dell PowerEdge Expandable RAID controller, with a hardware
Raid-5 at Channel 01 running perfectly, and a nCipher Crypter at
Channel 02.

This controller doesn't correctly detect devices (e.g. nCipher
Crypter) with multiples LUNs. Only one LUN is detected.

At another controller (e.g. Adaptec 79xx) two LUNs were detect. I
compiled 2.6.8, 2.6.18 and 2.6.21.3 to test megaraid driver and all
failed detecting two LUNs.

I think that this is a firmware problem, but i'd like have some opinions.

I read some docs
(http://www.suse.de/~garloff/linux/scsi-scan/scsi-scanning.html,
http://www.ictp.trieste.it/~radionet/nuc1996/ref/howto-html/scsi-howto-2.html)
and this problem doesn't seem to be simple.

Best regards,

More information with Dell PowerEdge Expandable RAID controller (LSI
Logic MegaRaid):

Attached devices:
Host: scsi0 Channel: 00 Id: 06 Lun: 00
 Vendor: PE/PVModel: 1x5 SCSI BP  Rev: 1.0
 Type:   ProcessorANSI  SCSI revision: 02
Host: scsi0 Channel: 01 Id: 00 Lun: 00
 Vendor: nCipher  Model: Fastness Crypto  Rev: 2*00
 Type:   ProcessorANSI  SCSI revision: 02
Host: scsi0 Channel: 02 Id: 00 Lun: 00
 Vendor: MegaRAID Model: LD 0 RAID5  279G Rev: 522A
 Type:   Direct-AccessANSI  SCSI revision: 02


14:0e.0 RAID bus controller: Dell PowerEdge Expandable RAID controller
4 (rev 06)
   Subsystem: Dell PowerEdge Expandable RAID Controller 4e/Di
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping+ SERR+ FastB2B-
   Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium

TAbort- SERR- 
   Latency: 64 (32000ns min), Cache Line Size: 64 bytes
   Interrupt: pin A routed to IRQ 22
   Region 0: Memory at d7ff (32-bit, prefetchable) [size=64K]
   Region 2: Memory at defc (32-bit, non-prefetchable) [size=256K]
   Expansion ROM at df00 [disabled] [size=128K]
   Capabilities: 

14:0e.0 0104: 1028:0013 (rev 06)


Information with Adaptec 79xx or others SCSI controllers:

Host: scsi0 Channel: 01 Id: 00 Lun: 00
 Vendor: nCipher  Model: Fastness Crypto  Rev: 2*00
 Type:   ProcessorANSI  SCSI revision: 02
Host: scsi0 Channel: 01 Id: 00 Lun: 01
 Vendor: nCipher  Model: Fastness Crypto  Rev: 2*00
 Type:   ProcessorANSI  SCSI revision: 02


--
Reinaldo Carvalho
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: megaraid.c, all kernel versions, problem with multi-luns

2007-05-30 Thread Reinaldo Carvalho

Yes CONFIG_SCSI_MULTI_LUN as build-in.

--
Reinaldo Carvalho


2007/5/30, Jesper Juhl <[EMAIL PROTECTED]>:

On 31/05/07, Reinaldo Carvalho <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a Dell PowerEdge Expandable RAID controller, with a hardware
> Raid-5 at Channel 01 running perfectly, and a nCipher Crypter at
> Channel 02.
>
> This controller doesn't correctly detect devices (e.g. nCipher
> Crypter) with multiples LUNs. Only one LUN is detected.
>
> At another controller (e.g. Adaptec 79xx) two LUNs were detect. I
> compiled 2.6.8, 2.6.18 and 2.6.21.3 to test megaraid driver and all
> failed detecting two LUNs.
>

Did you build your kernel with CONFIG_SCSI_MULTI_LUN enabled?  This
option will force the SCSI driver to probe for multiple LUN's.
Without this option only one LUN may be detected, and since that's the
common case (devices only having one LUN) people often forget about
this option :)

--
Jesper Juhl <[EMAIL PROTECTED]>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please  http://www.expita.com/nomime.html


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


3Com 3c905: Resetting the Tx ring pointer.

2007-06-03 Thread Reinaldo Carvalho
 CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Distributed Lock Manager
#
# CONFIG_DLM is not set

#
# Instrumentation Support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_MUST_CHECK=y
# CONFIG_MAGIC_SYSRQ is not set
CONFIG_UNUSED_SYMBOLS=y
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_EARLY_PRINTK=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=y

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_ECB is not set
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_LRW is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# CONFIG_CRYPTO_DEV_GEODE is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y


--
Reinaldo Carvalho
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/