Redlab not recogniced in MAX

Hello
I have a redlab 1208ls. My software is labview 2011. The drivers and lib is installed for labview with the redlab software.
But it is not realy working.
In the MAX the redlab is not found.
Also the programm"devices and interface" in max is not listed.
Could you please help me?
Best regards
Micha

Hi Wassermann,
as the RedLab is no hardware made by NI it will not be recognized by MAX! MAX is used to configure NI hardware!
You have to install the LV driver and use it's VIs that came with the RedLab. That's it…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Similar Messages

  • PCI 7330 not recognized in Windows 7

    When I transferred my 7330 motion controller board to another PC, it is not recognized in MAX. Windows system put it as unknown PCI board. 
    The PC runs on Windows 7. LabVIEW 2010 and MAX 4.7 were installed. What could be the reason for the 7330 not being recognized?
    Thanks.

    Yes, I found out why. When I install the device drivers, I always install the default selected drivers. So it must be that NI-Motion driver is not included in those defaults. The second time, I specifically selected to install NI-Motion;now the board is recognized well. 
    It's trivial, but another thing learned. Thanks for the reply. I also posted this on the hardware forum. 

  • Why are my PXI cards not recognized by Windows or MAX?

    I have a PXI-1045 chassis connected to a PC through MXI-4.  When I turn the chassis and PC on with a PXI card in slot 2, the message "Windows could not load the installer for DAQDevice.  Contact your hardware vendor for assistance." appears, and the PXI card is not recognized (it is scene by Windows as an unidentifiable PCI Devices, though I have a DAQmx installed).
    More details:
    Windows XP
    LabVIEW 8.0 installed
    TestStand 4.0 installed
    Latest DAQmx 8.XX installed
    NI Scope installed
    NI CAN installed
    MXI-4 PCI card installed in PC and recognized by Windows (as PCI-PCI bridge, and MXI-4 Device)
    I identified PXI chassis 1045 in MAX and on subsequent boot up saw that MAX complained about pxisys or some other ini file (in the chassis status area of the screen) so I configured it as 'other' then put in the PXI-resorce CD and selected the ini file for PXI-1045, MAX no longer complains about pxisys and instead says the chassis is configured properly
    If I have nothing but the PXI MXI-4 card installed in the PXI system and boot up the chassis then the PC, I get no errors
    If I have a card in slot two (I've tried PXI-6509 Industrial Digital IO, PXI-2569 Relay Module, and PXI-5102 Digital Oscilliscope) and boot the chassis then PC, the message "Windows could not load the installer for DAQDevice.  Contact your hardware vendor for assistance." shows up when Windows boots and Windows sees a PCI Device but can't identify any drivers for it. 

    Hello,
    Can you post a screenshot of the problem? Are you switching on the chassis first or the PC? Please make sure that you switch ON chassis and then boot the PC. This typically happens when you have a corrupted installation.  I would suggest downloading the latest version of driver from here and re-installing it.
    Please uninstall all the driver software from computer before installing the new software.
    http://digital.ni.com/softlib.nsf/websearch/d31d46​fffb745eca862571490053eab8
    Thanks,
    Kalyan
    Applications Engineer
    National Instruments

  • Mydaq does not recognized max

    Hi. When I open the Daq Assistant on Lab View it gives me a "No supported devices found" message, the labView works just fine but it does not recognized the myDaq. And before It did worked, What can I do?

    If you are using Measurement & Automation Explorer 5.0 or later, you could try resetting your configuration data by clicking the following menu option. It may solve your issue if MAX has been corrupted. Just a note, resetting your configuration data will clear any saved devices/scales you have. 
    Also, what operating system are you running?
    Regards,
    Ian K.
    Applications Engineer
    National Instruments

  • Monitor not recognized by Mac anymore?????

    Hi
    This is big and what is APPLE doing to solve this issue??
    I just copy some posts from the forum to show how big this issue is, there is 8 more pages with the same problem, and i am one of them!!!!
    HELP!!!! WE ARE FREAKING OUT HERE AND NEED A SOLUTION!!!
    Yes, me. I have an HP w2207 who worked with my 3 y.o. old MacBook (OS 10.4.??) via the DVI-port flawlessly. Then bought a brandnew MacBook Pro with 10.6.X and the external monitor stopped being recognized. It works now that I have changed the connection to the VGA-port of the monitor (and bought yet another adapter for the MacBook Pro) but the quality is not what I'm used to.
    MacBook Pro Mac OS X (10.6.1) HP w2207 external monitor
    MattLTH
    Posts: 15
    From: Salt Lake City, UT USA
    Registered: Dec 4, 2007
    Re: External monitor not recognized!
    Posted: Dec 1, 2009 1:29 PM in response to: cruzcj
    Reply Email
    Yes. I've tried 7 different Macs including a MacBook Pro with Snow Leopard (10.6.2) and my external monitor doesn't work with it either.
    For me here's a recap:
    Installed SL on a Mac Pro connected to a 23" Cinema via DVI and Olevia 537 via HDMI Input #1 and now that input no longer works with Mac computers.
    Reinstalled 10.5.8 on the Mac Pro and HDMI #1 still didn't work, so I plugged the Mac into HDMI #2 and it worked.
    Reinstalled SL on the Mac Pro connected to a 23" Cinema via DVI and Olevia 537 via HDMI Input #2 and now that input no longer works with Mac computers.
    Since then, every device (PCs, DVD Players, Video Cameras, etc...) I connect to either of the HDMI inputs work fine. However, neither HDMI input works with ANY of the 7 different Macs (regardless of OS version) I've tried, except for a 10-year-old G4 running Panther or Tiger.
    The monitor had previously worked with the MacPro (HDMI input #1) and a G5 (HDMI input #2) for almost 2 years.
    When I plug the MacPro into any other monitor via HDMI, it works fine. Same thing with the G5.
    My theory is still that the installer for Snow Leopard somehow made my monitor's HDMI inputs incompatible with Macs. I'm so frustrated that I'm ready to buy a new monitor, but since there's no guarantee that a new monitor won't be adversely affected by Snow Leopard, I'm still dubious.
    Matt
    MacPro, MacBook Pro, PowerMac G5 Mac OS X (10.6.2)
    Stephen Darling...
    Posts: 59
    From: London, UK
    Registered: Sep 24, 2004
    Re: External monitor not recognized!
    Posted: Dec 5, 2009 8:22 AM in response to: Roger Kaufmann
    Reply Email
    Another "me too" post...
    Not sure exactly when it stopped working (since I don't use it every day) but my Viewsonic VX2455wm stopped working with my MacBook recently too. Checked with another MacBook (six months newer than my Late 2006 model) and that exhibited the same problem. Both machines have fully patched Snow Leopard installs. Both started with Tiger. Mine is regularly connected to the external monitor, the other has never been connected. I'm connecting using a DVI cable and a mini-DVI-DVI adapter.
    The monitor appears to work correctly. I've checked with a Windows laptop connected on the VGA port. I want to test with another DVI-enabled machine to see whether or not its the cable.
    MacBook C2D 2Ghz Mac OS X (10.6.2) iPhone
    cruzcj
    Posts: 4
    From: California
    Registered: Nov 28, 2009
    Re: External monitor not recognized!
    Posted: Dec 13, 2009 10:38 PM in response to: Stephen Darling...
    Reply Email
    My wife's 15" MBP arrived on Wednesday. Connected it tonight to her new Dell 23" ST2310 via a MiniDisplayPort to VGA and it works fine.
    MacBook Pro 15" 2.8GHz Mac OS X (10.6.2)
    Gaston55
    Posts: 4
    From: Sweden
    Registered: Dec 15, 2009
    Re: External monitor not recognized!
    Posted: Dec 15, 2009 12:06 AM in response to: Roger Kaufmann
    Reply Email
    Hi Guys
    I have the same problem with my new Dell 2209WAf. It worked fine before i changed from L to SL.
    I didn't know what happened so i have spend hours and hours to resolve the problem.
    Hours with Mac support and friends didn't change anything, i still cant make my Dell to work, or show up in preferences. I am working as a photographer and this issue is a real problem.
    I just heard from Mac Support that Apple is working on it.....well, doesn't help us with the problem today.
    So Apple, DO SOMETHING ABOUT THIS! NOW! this problem should NEVER showed up, this is something you should have fixed before telling all the Macers to upgrade!!!
    Macbook Pro Mac OS X (10.6.2)
    RWildman465
    Posts: 2
    From: Illinois
    Registered: Dec 16, 2009
    Re: External monitor not recognized!
    Posted: Dec 16, 2009 1:18 PM in response to: Gaston55
    Reply Email
    Experiencing the same issues. However, on bit different hardware.
    I'm using the XLR8 ProView USB input devices. Using these devices on a mixture of 10.5.8 and 10.6.2 systems (2 MacBooks, 2 Mac Mini and 1 iMac).
    I can confirm the following:
    When attempting to mirror video, or extend the desktop, using a mini-DVI to S-Video/Composite device on OSX 10.6.2 no video is sent to the mini-DVI device (inputing into the XLR8).
    When attempting to mirror video, or extend the desktop, using a mini-DVI to S-Video/Composite device on OSX 10.5.8 video is sent to the mini-DVI device (inputing into the XLR8).
    Let me also state, that the mini-DVI port on the Mac Mini's do work. They have been connected to 19" monitors and working without issue. Today, the mini-DVI devices were replaced with minidisplay port devices, which are use in conjunction with the mini-DVI ports.
    It would appear, in my case, that the problem is that the mini-DVI port on both the MacBook and Mac Mini, running 10.6.2, as a secondary display device is not operating properly.
    iMac Mac OS X (10.6.2)
    Todd Camp
    Posts: 2
    From: Chicago
    Registered: Dec 19, 2009
    Re: External monitor not recognized!
    Posted: Dec 23, 2009 12:41 PM in response to: RWildman465
    Reply Email
    Same problems here. I reloaded OS 10.4.6 which is what shipped with my MBP1,2 17" 2.16 Intel Core Duo 2GB ram and after installing that, i was able to select 1920x1080 for my external HP w2338h, DVI-VGA, never been able to connect DVI-HDMI. On SL, the max rez I was able to "use" was 1600x1200 which looked horrible. So this leads me to suspect that this must be an issue with SL.
    I spoke with Apple Tech support on Sat and was no help. The only suggestion was that I take my MBP and Monitor to the Apple Store. Those of you who are fortunate enough to live in Chicago in the winter, then you know that option really isn't that feasible, it is but just a giant pain.
    Early 2006 MBP 17" Mac OS X (10.6.2)
    Salm0n
    Posts: 1
    From: Minneapolis
    Registered: Dec 27, 2009
    Re: External monitor not recognized!
    Posted: Dec 27, 2009 9:57 AM in response to: Todd Camp
    Reply Email
    I have an iMac 9,1 Intel Core 2 Duo that I bought last June. It came with Leopard, but I upgraded to Snow Leopard. Currently, it's running 10.6.2. My HP w2207 Widescreen monitor works perfectly with it using the DVI port on the HP and the mini-display (not mini-DVI) port on the iMac.
    However, I just bought the top-of-the-line iMac 11,1 Intel Core i5 QuadCore three days ago and it crashes nearly every time that it wakes from "sleep" when the HP w2207 is connected to it. It doesn't even recognize that the w2207 is connected to it. Additionally, when the w2207 is connected, it (a) looks terrible - very dim and very granular, and (b) causes the iMac QuadCore to operate very sluggishly. When I disconnect the HP w2207, the iMac QuadCore is lightning-fast.
    Much like my older iMac, the QuadCore is running 10.6.2 and I'm using the mini-display port.
    iMac 11,1 & iMac 9,1 Mac OS X (10.6.2)
    Marjorie Colletta
    Posts: 20
    Registered: Mar 17, 2005
    Re: External monitor not recognized!
    Posted: Jan 6, 2010 6:07 PM in response to: Roger Kaufmann
    Reply Email
    This is a Me too post, I have a MacBook and NEC Multisync Monitor that worked fine before I upgraded to 10.6.2. I've tried to get it to work without any luck. I've written NEC to see if they have a solution.
    MacBook 2 GHz Intel Core 2 Duo Mac OS X (10.6.2)
    davej147
    Posts: 12
    Registered: Jun 1, 2006
    Re: External monitor not recognized!
    Posted: Jan 11, 2010 6:24 AM in response to: Roger Kaufmann
    Reply Email
    Another me too post. I have a new 17" MacBook Pro with 10.6.2 installed. Trying to connect to an HPL2245wg - sometimes it works flawlessly - other times not at all. Some mornings I spend 30 -40 minutes rebooting, unplugging and plugging the monitor, Detecting Displays, changing the Graphics Card (Energy settings) - all to no avail. Very, very frustrating Apple - please figure out what is going on with this issue....and get it fixed!
    17" MacBook Pro Mac OS X (10.6.2) Very happily gave all my XP-stuff away!
    Anteck
    Posts: 2
    From: Australia
    Registered: Sep 30, 2009
    Re: External monitor not recognized!
    Posted: Jan 20, 2010 2:31 PM in response to: Roger Kaufmann
    Reply Email
    Wow, me too. Did a minor software update (apple released it) last night, got on this morning and BANG - my main 24" Dell display is NOT working.
    This is ******, apple have surely f**ked up here. It's never had a hitch, ever, since i bought it 9 months ago.
    We are all reporting the same thing - software update, and then no working external display...
    APPLE???
    Macbook Pro 2.2 15" Mac OS X (10.6.2)
    Zedog
    Posts: 13
    Registered: Aug 10, 2006
    Re: External monitor not recognized!
    Posted: Jan 20, 2010 2:59 PM in response to: Roger Kaufmann
    Reply Email
    I seem to have found a fix for myself. I was having terrible issues with the screen blinking and flickering constantly. I tried to reset the SMC with everything unplugged and the computer would not reboot at that point on it's own which led me eventually to reinstalling SL.
    Reinstalling SL is quite painless actually as it installs on top of your profile. After reinstalling I ran software update which installs the cumulative upgrades. Now I usually don't have any problems but must follow the instructions to run in clamshell mode to the letter.
    After a week of running in clamshell mode I started having an issue with the dock not lining up so I put the computer to sleep, disconnected the monitor and restarted with nothing connected. After that, followed the clamshell mode instructions again and have been working fine again all week.
    I've also disabled my screen-saver, and deleted the windowserver preferences as part of my debug process but not sure if that has contributed to my new found stability.
    http://support.apple.com/kb/HT3131
    Mac OS X (10.6.2)
    pragmaik
    Posts: 2
    From: Duisburg
    Registered: Apr 16, 2008
    Re: External monitor not recognized!
    Posted: Jan 21, 2010 1:08 AM in response to: Roger Kaufmann
    Reply Email
    Me too. I have a MacBook Pro 2,2 running the latest Snow Leopard 10.6.2. After I have installed yesterday's security patch it does not recognize external displays on the DVI port any longer. Tried it with a 23" DELL at the office and a 23" Samsung at home. Both have worked without any problems for years.
    I am curious to learn how this behavior is related to security...

    Gaston,
    This is not the correct Feedback venue for your issue.
    Please select an appropriate product from those displayed HERE and use the corresponding form to communicate to the correct department.
    ali b

  • PXI System does not appear in MAX 4.0

    Hello,
    My system comprises LabVIEW RT 7.0, target PXI-8176 controller in PXI-1000B chassis, PXI-6608, PXI-6711, NI-4472, PXI-6704, PXI-6527, PXI-8423/4, PXI-8422/4.  This has been stable for two years. I recently solved an RS-485 2-wire mode configuration problem, using information in a discussion forum thread, by upgrading to NI-VISA 3.4.1 and NI-Serial 2.5.5.  MAX 4.0 was installed as part of this process.  Everything seemed to work fine.  I instructed a distant customer to do the same, but they experienced some difficulty. To ensure we were working from the same starting point, I re-initialized my PXI system, using PXI Format Hard Drive Disk, version 7.0, from MAX 4.0.  I configured TCP IP address, and re-installed the RT software on the PXI controller.
    Next, I attempted to configure the PXI controller and chassis, in MAX, to update the pxisys.ini file, but the PXI System (Unidentified) does not appear under Remote System>>IP address>>Devices and Interfaces.  Similarly for the serial ports.  This worked before, but I cannot get this back.  What is wrong?
    Best regards,
    RonC

    Hello S. Bassett
    The controller is definitely booting in RT mode -- I can still run my applications on the RT target.  VISA seems configured properly also, I can make VISA calls without error in the application.
    In fact, the RT system seems to work correctly, and I contemplated leaving it as it is. However, the fact that MAX does not recognize the PXI system makes me nervous, and I cannot do some of the things I may want to do, for example independently configure RS-485 port wire mode in MAX (the ports do not show up either).  Traditional DAQ configuration in MAX works.
    After your last post, I found a brief reference in MAX Help that indicated "PXI Services" had to be downloaded before the chassis could be configured.  But there are no other mentions of what PXI Services is, what it does, or how to install them. PXI Services does not show up as RT Software in MAX. In the Windows Add/Remove Programs control panel in Windows, in the National Instruments software section, there are two apparently related entries:
    - NI PXI Platform Services for LabVIEW Real-Time 1.5.1
    - NI PXI Platform Services for Windows 1.5.1
    But, I cannot get these to install on the RT target.  Not knowing what was causing the problem, I uninstalled everything from  National Instruments, deleted all folders, and reformatted the PXI platform.  There was one problem during this process -- after uninstalling NI-Serial 2.5.5, it does not get removed from the Add/Remove programs control panel.  There is still a registry key that the uninstaller did not remove -- presumably this is the problem.
    I have rebuilt everything, but could not get NI-Serial to install -- the installer thinks there is a newer installed on the RT target (there isn't) and refuses to install NI-Serial 2.5.5.  So right now, I cannot install NI-SERIAL (any version), or remove the 'existing' NI_SERIAL, because it isn't actually there, and there is no uninstaller.
    Otherwise, everything seems to be back to where it was before I "upgraded" to NI-VISA 3.4.1.  This was NI-VISA 3.0, LV RT 7.0, and MAX 3.0.2.  I have not yet been able to install NI-Serial, so I cannot yet see if I have also restored my original problem -- the one that led me to have to upgrade NI-VISA and NI-SERIAL in the first place.
    Most importantly, there is now a "PXI Services v1.1.2" installed on the RT target.  I am quite sure the problem with MAX 4.0 not recognizing my PXI system has to do with the absence of this driver on the RT target.
    Thanks again for your interest and help,
    RonC

  • Xmas Nano not recognized by iTunes and ejecting crashes iMac HARD!

    I hooked up my new 8Gb Nano and was notified I had to upgrade iTunes. Did that. Then a dialog box popped up telling me the Nano was not recognized and advising to disconnect and reconnect it. After doing this a half dozen times it was finally recognized. Tried to sync with iTunes and it froze on selection #19. Had to FORCE QUIT iTunes. As the Nano was telling me it is connected and needs to be ejected I did that in FINDER and the iMac had a hard crash. Had to force a power-down. I went through this absurdity 5 times with iTunes starting a sync at #19 then after deleting #19, it froze at selection #11, deleted that and it froze at #1. After each freeze and my tying to eject the Nano and getting 5 hard crashes I finally went to bed!
    Today I trashed iTunes, downloaded it again and hooked up nano. Nothing. It was not recognized by iTunes but showed up in FINDER and the DESKTOP. Quit iTunes. I ignored ejecting it, disconnected it. Started iTunes again connected the Nano and got the spinning color wheel for about ten minutes. While I searched the net for solutions it finally stopped spinning but, the Nano is not listed in iTunes! It shows up on the desktop and in finder and the Nano is telling me it is connected and needs to be ejected. I'll try to eject it next but I'm sending this now as I've no confidence the mac won't have another hard crash!
    This is pretty disappointing. I finally talked my brother in-law into abandoning the PC (as I did last year after a zillion years of PC frustration) and consider getting a new iMac. "All you have to do is hook up your Mac and it just works!!!" From what I'm seeing here and other places, the Nano/iTunes problem is not unusual, BUT I'm seeing nothing from Apple to address this issue. Is Apple becoming the next Microsoft? Who needs this crap?
    Does there have to be a mass return of Nano's to get Apple's attention? I know mine goes back tomorrow!
    Max in Houston

     
    gltg wrote:
    Running Windows XP professional SP3 and itunes 10.2.
    I have followed every troubleshooting page on the apple support site yet my ipod nano 6th gen is not recognized by itunes
    I have spent 3 days messing with my pc and have made no real progress.
    Then it's time to call Apple tech support while you are still under warranty.  Every iPod comes with complimentary, single-incident telephone technical support within 90 days of your iPod purchase.   If you also purchased AppleCare, then your warranty is extended for technical support and hardware coverage for two years from the original purchase date of your iPod.
    U.S. iPod and Mac technical support: 1-800-APL-CARE (1-800-275-2273)

  • CD drive not recognized & Very slow boot process.

    (I posted this in the newbie forum, but got no answer, so I give it another go)
    Hi all,
    After a few years alternating between gentoo and debian, feeling they were ok, but not exactly what I wanted, I found Arch, and now I am happy. It feels just right. I am still very new, but I am already quite sure I'll settle here.
    But happyness and warm feelings asides, I have a 2 problems I'd like to get some help about.
    problem 1: my CD drive is not recognized. my hard drive and its partitions show up correctly, but I don't get a cd drive.
    problem 2: On the boot process, a lot of time (2 minutes or so) is spend scanning the ATA bus. relevant messages are as follow (plus a few lines before and after just to give context)
    Code:
    Freeing unused kernel memory: 256k freed
    Time: acpi_pm clocksource has been installed.
    ACPI: Unable to derive IRQ for device 0000:00:10.0
    ACPI: PCI Interrupt 0000:00:10.0[A]: no GSI
    ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x2000 irq 14
    ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x2008 irq 15
    scsi0 : pata_ali
    ata1.00: ATA-5, max UDMA/100, 78140160 sectors: LBA
    ata1.00: ata1: dev 0 multi count 16
    ata1.00: configured for UDMA/100
    scsi1 : pata_ali
    ata2.00: ATAPI, max UDMA/33
    ata2.00: configured for UDMA/33
    scsi 0:0:0:0: Direct-Access     ATA      IC25N040ATCS04-0 CA4O PQ: 0 ANSI: 5
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2: port is slow to respond, please be patient (Status 0xd0)
    ata2: soft resetting port
    ata2.00: model number mismatch 'QSI CD-RW/DVD-ROM SBW-241' != ''
    ata2.00: disabled
    ata2: soft resetting port
    ata2.00: ATAPI, max UDMA/33
    ata2.00: configured for UDMA/33
    ata2: EH complete
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2: port is slow to respond, please be patient (Status 0xd0)
    ata2: soft resetting port
    ata2.00: configured for UDMA/33
    ata2: EH complete
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2: port is slow to respond, please be patient (Status 0xd0)
    ata2: soft resetting port
    ata2.00: configured for UDMA/33
    ata2: EH complete
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2: port is slow to respond, please be patient (Status 0xd0)
    ata2: soft resetting port
    ata2.00: configured for UDMA/33
    ata2: EH complete
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    problem 2 and 3 are probably related, and linked to the new pata system in the kernel, but I don't really know anything about it, and my understanding of the mkinitcpio is very very limited. here is mine anyway, comments stripped.
    Code:
    MODULES="pata_ali"
    BINARIES=""
    FILES=""
    HOOKS="base udev autodetect pata usbinput keymap filesystems"
    I had it with
    Code:
    MODULES="pata_ali ata_generic"
    and with scsi in the HOOKS as the result of the install, but the behavior was exactly the same.
    Oh, and the machine I am using is a 4 year old laptop. Nothing in there is scsi or sata.
    I hope anyone can help me with those.
    Thanks

    Hi, I'm a "newbie" too. Coming from Gentoo/Debian. Installed Arch this week and I think it could be just the distro I have been looking for.
    I too had the same problem and think it's related to the pata modules. ¿Did you have to use the legacy-ide option when installing from the CD? I'm using old hardware (4 year old laptop) and had the same symptoms you are describing. I exchanged pata with ide in mkinitcpio.conf. My MODULES and HOOKS looks like this:
    MODULES="ide_disk ata_generic"
    HOOKS="base udev autodetect ide keymap filesystems" (deleted scsi and sata also because I don't think I need them).
    Then run mkinitcpio.
    I also had to change my device names in /etc/fstab from:
    /dev/sda2 / ext3 defaults 0 1
    /dev/sda5 swap swap defaults 0 0
    to:
    /dev/hda2 / ext3 defaults 0 1
    /dev/hda5 swap swap defaults 0 0
    And finally /boot/grub/menu.lst from:
    kernel /boot/vmlinuz26 root=/dev/sda2 ro
    to
    kernel /boot/vmlinuz26 root=/dev/hda2 ro
    ¿Any experienced user can confirm that I'm doing the right thing? I didn't find documentation in the wiki for old systems. Only the mention of an ide-legacy option.
    Hope it helps.
    Last edited by Malakin (2007-04-29 02:29:31)

  • ES1946 (Solo) Audio controller not recognized

    Dear all,
    ES1946 (Solo) Audio controller is not recognized on my box. I examined dmesg, it said:
    es1938: OPL3 not detected at 0x1090
    I've listed my dmesg and rc.conf below. Could anyone kindly look into it, and give me a hint to solve this problem?
    Best regards,
    Wen
    dmesg
    Linux version 2.6.26-ARCH (root@T-POWA-LX) (gcc version 4.3.2 (GCC) ) #1 SMP PREEMPT Tue Sep 9 10:15:21 UTC 2008
    PAT disabled. Not yet verified on this CPU type.
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000000bff0000 (usable)
    BIOS-e820: 000000000bff0000 - 000000000bfffc00 (ACPI data)
    BIOS-e820: 000000000bfffc00 - 000000000c000000 (ACPI NVS)
    BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
    0MB HIGHMEM available.
    191MB LOWMEM available.
    Entering add_active_range(0, 0, 49136) 0 entries of 256 used
    Zone PFN ranges:
      DMA             0 ->     4096
      Normal       4096 ->    49136
      HighMem     49136 ->    49136
    Movable zone start PFN for each node
    early_node_map[1] active PFN ranges
        0:        0 ->    49136
    On node 0 totalpages: 49136
      DMA zone: 32 pages used for memmap
      DMA zone: 0 pages reserved
      DMA zone: 4064 pages, LIFO batch:0
      Normal zone: 352 pages used for memmap
      Normal zone: 44688 pages, LIFO batch:7
      HighMem zone: 0 pages used for memmap
      Movable zone: 0 pages used for memmap
    DMI 2.3 present.
    ACPI: RSDP 000F6B60, 0014 (r0 PTLTD )
    ACPI: RSDT 0BFFD520, 002C (r1 PTLTD    RSDT          0  LTP        0)
    ACPI: FACP 0BFFFB65, 0074 (r1 IBM    TP240           2 PTL     F4240)
    ACPI: DSDT 0BFFD54C, 2619 (r1    PTL    BX-TJ        0 MSFT  100000B)
    ACPI: FACS 0BFFFFC0, 0040
    ACPI: BOOT 0BFFFBD9, 0027 (r1 PTLTD  $SBFTBL$        0  LTP        1)
    ACPI: PM-Timer IO Port: 0x8008
    Allocating PCI resources starting at 10000000 (gap: 0c000000:f3f80000)
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    SMP: Allowing 0 CPUs, 0 hotplug CPUs
    PERCPU: Allocating 39464 bytes of per cpu data
    NR_CPUS: 16, nr_cpu_ids: 1
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 48752
    Kernel command line: root=/dev/sda8 ro
    Local APIC disabled by BIOS -- you can enable it with "lapic"
    mapped APIC to ffffb000 (0118d000)
    Enabling fast FPU save and restore... done.
    Initializing CPU#0
    PID hash table entries: 1024 (order: 10, 4096 bytes)
    Detected 365.025 MHz processor.
    Console: colour VGA+ 80x25
    console [tty0] enabled
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Memory: 189624k/196544k available (2120k kernel code, 6384k reserved, 744k data, 264k init, 0k highmem)
    virtual kernel memory layout:
        fixmap  : 0xffee4000 - 0xfffff000   (1132 kB)
        pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
        vmalloc : 0xcc800000 - 0xff7fe000   ( 815 MB)
        lowmem  : 0xc0000000 - 0xcbff0000   ( 191 MB)
          .init : 0xc03d3000 - 0xc0415000   ( 264 kB)
          .data : 0xc031225e - 0xc03cc380   ( 744 kB)
          .text : 0xc0100000 - 0xc031225e   (2120 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    CPA: page pool initialized 1 of 1 pages preallocated
    SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    Calibrating delay using timer specific routine.. 731.57 BogoMIPS (lpj=1218523)
    Security Framework initialized
    Capability LSM initialized
    Mount-cache hash table entries: 512
    CPU: L1 I cache: 16K, L1 D cache: 16K
    CPU: L2 cache: 128K
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    Checking 'hlt' instruction... OK.
    SMP alternatives: switching to UP code
    Freeing SMP alternatives: 9k freed
    ACPI: Core revision 20080321
    ACPI: Checking initramfs for custom DSDT
    ACPI: setting ELCR to 0200 (from 0a20)
    weird, boot CPU (#0) not listedby the BIOS.
    SMP motherboard not detected.
    Local APIC not detected. Using dummy APIC emulation.
    SMP disabled
    Brought up 1 CPUs
    Total of 1 processors activated (731.57 BogoMIPS).
    net_namespace: 652 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: PCI BIOS revision 2.10 entry at 0xfd9e5, last bus=0
    PCI: Using configuration type 1 for base access
    Setting up standard PCI resources
    ACPI: EC: Look up EC in DSDT
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S3 S4 S5)
    ACPI: Using PIC for interrupt routing
    ACPI: EC: non-query interrupt received, switching to interrupt mode
    ACPI: EC: GPE = 0x9, I/O: command/status = 0x66, data = 0x62
    ACPI: EC: driver started in interrupt mode
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:07.3: quirk: region 8000-803f claimed by PIIX4 ACPI
    pci 0000:00:07.3: quirk: region 2180-218f claimed by PIIX4 SMB
    pci 0000:00:07.3: PIIX4 devres I PIO at 0398-0399
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 14)
    ACPI: Power Resource [PFAN] (off)
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp 00:09: can't evaluate _PRS: 12321<6>pnp: PnP ACPI: found 13 devices
    ACPI: ACPI bus type pnp unregistered
    PCI: Using ACPI for IRQ routing
    NetLabel: Initializing
    NetLabel:  domain hash size = 128
    NetLabel:  protocols = UNLABELED CIPSOv4
    NetLabel:  unlabeled traffic allowed by default
    system 00:05: iomem range 0xe0000-0xfffff could not be reserved
    system 00:05: iomem range 0xfff80000-0xffffffff could not be reserved
    system 00:06: ioport range 0x4d0-0x4d1 has been reserved
    system 00:06: ioport range 0x8000-0x803f has been reserved
    system 00:06: ioport range 0x2180-0x218f has been reserved
    system 00:06: ioport range 0x398-0x399 has been reserved
    PCI: Bus 1, cardbus bridge: 0000:00:0a.0
      IO window: 0x00001800-0x000018ff
      IO window: 0x00001c00-0x00001cff
      PREFETCH window: 0x10000000-0x13ffffff
      MEM window: 0x14000000-0x17ffffff
    ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
    PCI: setting IRQ 11 as level-triggered
    ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
    NET: Registered protocol family 2
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs... done
    Freeing initrd memory: 540k freed
    Simple Boot Flag at 0x40 set to 0x1
    IBM machine detected. Enabling interrupts during APM calls.
    apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    apm: overridden by ACPI.
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 371
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:00:00.0: Limiting direct PCI/PCI transfers
    pci 0000:00:09.0: Boot video device
    isapnp: Scanning for PnP cards...
    Switched to high resolution mode on CPU 0
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    serial 00:08: activated
    00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    input: Macintosh mouse button emulation as /class/input/input0
    PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUS] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    registered taskstats version 1
    Freeing unused kernel memory: 264k freed
    No dock devices found.
    input: AT Translated Set 2 keyboard as /class/input/input1
    SCSI subsystem initialized
    libata version 3.00 loaded.
    ata_piix 0000:00:07.1: version 2.12
    scsi0 : ata_piix
    scsi1 : ata_piix
    ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1040 irq 14
    ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1048 irq 15
    ata1.00: ATA-5: HITACHI_DK23CA-10, 00H5A0G1, max UDMA/100
    ata1.00: 19640880 sectors, multi 16: LBA
    ata1.00: configured for UDMA/33
    scsi 0:0:0:0: Direct-Access     ATA      HITACHI_DK23CA-1 00H5 PQ: 0 ANSI: 5
    Driver 'sd' needs updating - please use bus_type methods
    sd 0:0:0:0: [sda] 19640880 512-byte hardware sectors (10056 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 0:0:0:0: [sda] 19640880 512-byte hardware sectors (10056 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 < sda5 sda6 sda7 sda8 >
    sd 0:0:0:0: [sda] Attached SCSI disk
    ReiserFS: sda8: found reiserfs format "3.6" with standard journal
    ReiserFS: sda8: using ordered data mode
    ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
    ReiserFS: sda8: checking transaction log (sda8)
    ReiserFS: sda8: Using r5 hash to sort names
    rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, y3k
    ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
    PCI: setting IRQ 5 as level-triggered
    ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
    es1938: OPL3 not detected at 0x1090
    gameport: ES1938 is pci0000:00:0b.0/gameport0, io 0x10a0, speed 1084kHz
    ACPI: EC: GPE storm detected, disabling EC GPE
    ACPI: AC Adapter [ACAD] (on-line)
    ACPI: Battery Slot [BAT1] (battery absent)
    input: Power Button (FF) as /class/input/input2
    ACPI: Power Button (FF) [PWRF]
    input: Sleep Button (CM) as /class/input/input3
    ACPI: Sleep Button (CM) [SBTN]
    input: Lid Switch as /class/input/input4
    ACPI: Lid Switch [LID]
    ACPI: Transitioning device [FAN] to D3
    ACPI: PNP0C0B:00 is registered as cooling_device0
    ACPI: Fan [FAN] (off)
    ACPI: CPU0 (power states: C1[C1] C2[C2])
    ACPI: ACPI0007:00 is registered as cooling_device1
    ACPI: Processor [CPU0] (supports 8 throttling states)
    ACPI: LNXTHERM:01 is registered as thermal_zone0
    ACPI: Thermal Zone [THRM] (64 C)
    Marking TSC unstable due to: TSC halts in idle.
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    input: PC Speaker as /class/input/input5
    Yenta: CardBus bridge found at 0000:00:0a.0 [1014:019a]
    Yenta: Using CSCINT to route CSC interrupts to PCI
    Yenta: Routing CardBus interrupts to PCI
    Yenta TI: socket 0000:00:0a.0, mfunc 0x012c1272, devctl 0x64
    Yenta: ISA IRQ mask 0x0498, PCI irq 11
    Socket status: 30000010
    pccard: PCMCIA card inserted into slot 0
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    PPP generic driver version 2.4.2
    piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
    piix4_smbus 0000:00:07.3: IBM system detected; this module may corrupt your serial eeprom! Refusing to load module!
    piix4_smbus: probe of 0000:00:07.3 failed with error -1
    input: ImPS/2 Generic Wheel Mouse as /class/input/input6
    NET: Registered protocol family 23
    USB Universal Host Controller Interface driver v3.0
    ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
    ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
    uhci_hcd 0000:00:07.2: UHCI Host Controller
    uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
    uhci_hcd 0000:00:07.2: irq 11, io base 0x00001060
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    cs: IO port probe 0x100-0x3af: clean.
    cs: IO port probe 0x3e0-0x4ff: clean.
    cs: IO port probe 0x820-0x8ff: clean.
    cs: IO port probe 0xc00-0xcf7: clean.
    cs: IO port probe 0xa00-0xaff: clean.
    cs: memory probe 0xa0000000-0xa0ffffff: clean.
    pcmcia: registering new device pcmcia0.0
    lp: driver loaded but no devices found
    eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:40:26:5c:d8:21
    nsc-ircc 00:09: can't evaluate _CRS: 12321
    nsc-ircc 00:09: activation failed
    nsc-ircc: probe of 00:09 failed with error -5
    nsc-ircc, Found chip at base=0x398
    nsc-ircc, Wrong chip version ff
    ppdev: user-space parallel port driver
    parport_pc 00:07: reported by Plug and Play ACPI
    parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
    lp0: using parport0 (interrupt-driven).
    Clocksource tsc unstable (delta = -77266143 ns)
    Adding 200772k swap on /dev/sda7.  Priority:-1 extents:1 across:200772k
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    eth0: no IPv6 routers present
    tun: Universal TUN/TAP device driver, 1.6
    tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
    tun0: Disabled Privacy Extensions
    usb 1-1: new full speed USB device using uhci_hcd and address 2
    usb 1-1: configuration #1 chosen from 1 choice
    Initializing USB Mass Storage driver...
    scsi2 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usb-storage: device found at 2
    usb-storage: waiting for device to settle before scanning
    scsi 2:0:0:0: Direct-Access              USB DISK 28X     PMAP PQ: 0 ANSI: 0 CCS
    sd 2:0:0:0: [sdb] 4030464 512-byte hardware sectors (2064 MB)
    sd 2:0:0:0: [sdb] Write Protect is off
    sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
    sd 2:0:0:0: [sdb] Assuming drive cache: write through
    sd 2:0:0:0: [sdb] 4030464 512-byte hardware sectors (2064 MB)
    sd 2:0:0:0: [sdb] Write Protect is off
    sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
    sd 2:0:0:0: [sdb] Assuming drive cache: write through
    sdb: sdb1
    sd 2:0:0:0: [sdb] Attached SCSI removable disk
    sd 2:0:0:0: Attached scsi generic sg1 type 0
    usb-storage: device scan complete
    /etc/rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="localtime"
    USEDIRECTISA="yes"
    TIMEZONE="Asia/Saigon"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(8390 pcnet_cs slhc pcnet_cs snd-mixer-oss snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-midi-event snd-seq snd-hwdep snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-mpu401-uart snd-opl3-lib snd-es1938 soundcore)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="fang.ntu.edu.vn"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    #   - prefix an entry in INTERFACES with a ! to disable it
    #   - no hyphens in your interface names - Bash doesn't like it
    # DHCP:     Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255"
    INTERFACES=(eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    #   - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.1.1"
    ROUTES=(gateway)
    # Enable these network profiles at boot-up.  These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    #   - set to 'menu' to present a menu during boot-up (dialog package required)
    #   - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    #   - prefix a daemon with a ! to disable it
    #   - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng network netfs crond)

    hi!
    did you read this?
    http://tascam.com/i-414-232-128-0-4A15AD91.pdf
    can be found here: http://tascam.com/products/fireone;9,14,104,19.html
    regards,
    m.

  • Iphoto videos not recognized

    It appears that iMovie does not recognize videos in my iPhoto libraries that are on my external hard drive.
    I am wanting to transfer all my videos to DVD now.... but over time my hard drive has been maxed out, so iPhoto libraries have been taken off year by year.  So, even now, I have all years of photos on an external drive to just leave enough space for all my videos and 2011 photos to remain on my hard drive.
    Is it that my iPhoto library MUST be on my hard drive for iMovie to recognize? 
    I tried exporting my iPhoto movies from iPhoto to a folder on my hard drive and then import into iMovie, but it said the file type was not recognized or something along that sort.  I had gone to iMovie help and it indicated I needed to have Quicktime 7 installed... I have Quicktime 10 installed....
    It isn't format because it is the same camera creating the movies in previous years and my 2011 iPhoto library.

    I am having a similar problem.  I recently downloaded iLife 11 and now imovie says that my movies in iphoto are not compatible and they are not showing in imovie.  I'm using the same camera that I've used for my previous movies and it has always worked before.
    I can import them one by one, but it's a long process.  I thought that the newer version was supposed to make things easier.
    Any help would be much appreciated.

  • FEX 2232TM not recognized by Nexus 5010P

    Hi there,
    I don't have any clue what this problem might be so please help.
    I have a brandnew FEX 2232TM which is connected to a NEXUS 5010P running the following firmware:
    oftware
      BIOS:      version 1.5.0
      loader:    version N/A
      kickstart: version 5.2(1)N1(1)
      system:    version 5.2(1)N1(1)
      power-seq: Module 1: version v1.2
      BIOS compile time:       11/30/10
      kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.1.bin
      kickstart compile time:  7/12/2012 19:00:00 [07/13/2012 02:08:13]
      system image file is:    bootflash:///n5000-uk9.5.2.1.N1.1.bin
      system compile time:     7/12/2012 19:00:00 [07/13/2012 03:23:16]
    According to the Cisco download page it is the latest version and should definitely support the 2232TM.
    The problem is that the FEX is completely not recognized by the parent Nexus.
    It is connected via 8 FET modules. But when ich check the light on both sides I only have light on the NEXUS side never on the FEX side on all modules.
    From my understanding this should be the root cause of the issue because no light = no link.
    I tried standard 10GBase-SR and Twinax cables as well. Same behavior - the FEX is not recognized.
    The status LED if of course orange on the FEX.
    This is the FEX related config ont he NEXUS:
    feature fex
    fex 101
      pinning max-links 8
      description "FEX0101"
    interface Ethernet1/1
      switchport mode fex-fabric
      fex associate 101
    interface Ethernet1/2
      switchport mode fex-fabric
      fex associate 101
    interface Ethernet1/3
      switchport mode fex-fabric
      fex associate 101
    interface Ethernet1/4
      switchport mode fex-fabric
      fex associate 101
    interface Ethernet1/5
      switchport mode fex-fabric
      fex associate 101
    interface Ethernet1/6
      switchport mode fex-fabric
      fex associate 101
    interface Ethernet1/7
      switchport mode fex-fabric
      fex associate 101
    interface Ethernet1/8
      switchport mode fex-fabric
      fex associate 101
    Can anyone give me a hint what I am missing here??
    Any help is really appreciated.
    Thanks a lot!

    I have a two lab switches running 5.2.1.N1.1 and connected in vpc with 2232TM and I am able to see the fex online without any problems. One side I have SFP-10G-SR and other side I have 3M Cisco Twinax cable.
    here is the output from my lab,
    5010-1# show fex
      FEX         FEX           FEX                       FEX
    Number    Description      State            Model            Serial
    100        FEX0100                Online    N2K-C2232TM-10GE   SSI15380CPM
    5010-1# show fex 100 detail
    FEX: 100 Description: FEX0100   state: Online
      FEX version: 5.2(1)N1(1) [Switch version: 5.2(1)N1(1)]
      FEX Interim version: 5.2(1)N1(1)
      Switch Interim version: 5.2(1)N1(1)
      Extender Serial: SSI15380CPM
      Extender Model: N2K-C2232TM-10GE,  Part No: 73-13626-03
      Card Id: 164, Mac Addr: 28:94:0f:2e:12:82, Num Macs: 64
      Module Sw Gen: 21  [Switch Sw Gen: 21]
      post level: complete
      Pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth1/1
      FCoE Admin: false
      FCoE Oper: true
      FCoE FEX AA Configured: false
      Fabric interface state:
        Po100 - Interface Up. State: Active
        Eth1/1 - Interface Up. State: Active
      Fex Port        State  Fabric Port
    5010-1# show interface e1/1 transceiver details
    Ethernet1/1
        transceiver is present
        type is  SFP-H10GB-CU3M rev A
        name is CISCO-MOLEX INC
        part  number is 74752-9026
        revision is A
        serial number is  MOL12240343
        nominal bitrate is 12000 MBit/sec
        Link  length supported for copper is 3 m
        cisco id is --
         cisco extended id number is 4
    DOM is not supported
    5010-2# show fex
      FEX         FEX           FEX                       FEX
    Number    Description      State            Model            Serial
    100        FEX0100                Online    N2K-C2232TM-10GE   SSI15380CPM
    5010-2# show fex 100 detail
    FEX: 100 Description: FEX0100   state: Online
      FEX version: 5.2(1)N1(1) [Switch version: 5.2(1)N1(1)]
      FEX Interim version: 5.2(1)N1(1)
      Switch Interim version: 5.2(1)N1(1)
      Extender Serial: SSI15380CPM
      Extender Model: N2K-C2232TM-10GE,  Part No: 73-13626-03
      Card Id: 164, Mac Addr: 28:94:0f:2e:12:82, Num Macs: 64
      Module Sw Gen: 21  [Switch Sw Gen: 21]
      post level: complete
      Pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth1/1
      FCoE Admin: false
      FCoE Oper: true
      FCoE FEX AA Configured: false
      Fabric interface state:
        Po100 - Interface Up. State: Active
        Eth1/1 - Interface Up. State: Active
      Fex Port        State  Fabric Port
    5010-2# show interface e1/1 transceiver details
    Ethernet1/1
        transceiver is present
        type is 10Gbase-SR
        name is CISCO-AVAGO
        part number is SFBR-7700SDZ-CS2
        revision is B5
        serial number is AGD133133S4
        nominal bitrate is 10300 MBit/sec
        Link length supported for 50/125um OM2 fiber is 82 m
        Link length supported for 50/125um OM3 fiber is 300 m
        Link length supported for 62.5/125um fiber is 26 m
        cisco id is --
        cisco extended id number is 4
               SFP Detail Diagnostics Information (internal calibration)
                    Current              Alarms                  Warnings
                    Measurement     High        Low         High          Low
      Temperature   44.18 C        75.00 C     -5.00 C     70.00 C        0.00 C
      Voltage        3.26 V         3.63 V      2.97 V      3.46 V        3.13 V
      Current        6.48 mA       10.50 mA     2.50 mA    10.50 mA       2.50 mA
      Tx Power       -2.62 dBm       1.69 dBm  -11.30 dBm   -1.30 dBm     -7.30 dBm
      Rx Power       -2.80 dBm --    1.99 dBm  -13.97 dBm   -1.00 dBm     -9.91 dBm
      Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    So dont believe we have any interoperability issue with 5010 and 2232TM here. Before we swap out this fex, can you please open a case with Cisco support or let me know when you are available and I can do a webex to look at this switch to see if there is something more to this problem than what we already know ?
    Thanks,
    Vinayak

  • ---   disk not recognized by this computer  ----

    I have the G4 tower with a dvd burner, and I recently
    bought a floppy drive read/write. [t-max? external teac]
    Files which were prior saved onto floppy get an error msg:
    ' disk not recognized by this computer ' 'format now? '
    these were claris works files, saved via apple IIg onto
    apple formatted 1.4 mb disks, which are now un readable.
    suggestions ?
    oh .. the unit IS working OK to save jpegs, claris 5 files now.. on my current system.....
    but floppys previously [1990's] formatted are not readable.

    Reader Gerrie E. Cooper has a stash of old floppies that contain fonts from Adobe, Agfa, and other companies. It’s bad enough that the fonts are stored on this prehistoric media, but said media is of the 800KB variety. He wonders what course to take.
    I’m afraid that the answer is to find an old Mac (an SE on up to a beige Power Mac G3 will do the trick), insert the floppies into that Mac’s drive, create disk images of the floppies, and then copy the images to the current Mac. Third-party USB floppy drives support 1.4MB HD floppies but not double-density 800KB disks.

  • 7332 is not detected in MAX

    Hi,
    We have a PCI NI7332 motion controller purchased with us. We installed the drivers and softwares  from the cd that comes with the package. The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. When i tried to connect an encoder and read it in MAX nothing is happening.  Do i have to change any setting when using the board for the first time?
    With regards,
    Jerry

    Jerry, 
    I don't quite understand this:
    " The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. "
    I'm assuming that the board just isn't showing up in NI-MAX.  If you are running Windows, I would go to the Device Manager on your machine and make sure the computer is recognizing it first (I'm not familiar with the Mac equivalent of this).  If the computer is not recognizing it as a piece of hardward installed on the motherborrd, there may be a bad connection.  Restarting the computer is also not a bad idea just to make sure everything is operating correctly.
    Hope you get it figured out.
    Adam

  • Time Machine not recognizing full space available on NAS.

    I recently purchsed and set up an Iomega Storcenter ix4-200d NAS with Time Machine support.  The NAS has 8 TB storage total, with ~4.6 TB available.
    I have TIme Machine support turned on in the Storcenter, assigned to a folder called "Time-Machine."  In my OSX Time Machine preferences, I select the "Time-Machine" folder on my NAS as the back-up disk, and my Mac connects to it just fine.
    The challenge is Time Machine returns an error saying there isn't enough space on the backup disk to complete the backup.
    For some reason, Time Machine is only recognizing 536.36 GB of space available on the backup disk, even though there are ~4.6 TB available.  I tried manually moving my iTunes media folder (~700 GB) to the "Time-Machine" folder on my NAS to see if the Iomega NAS was arbitrarily setting a max size to a Time Machine folder.  I was able to manually move just under 1 TB of data to the same "Time-Machine" folder that Time Machine says only has 536.36 GB of space.
    I tried deleting the Time-Machine store on my NAS, turning Time Machine support off, then turning it back off and creating a new "Time-Machine" folder.  I did this several times and still get the same behavior.
    I even tried running Time Machine piecemeal, excluding larger folders at first and running a back-up, to see if maybe Time Machine wasn't liking that large of an initial backup.  This worked, and then I gradually removed some exclusions and ran back-ups again, so each back-up size was never more than 200 GBs or so.  However, after several back-ups, I received the same error message saying there wasn't enough space on the backup disk when the total sparsbundle size reached 536.36 GBs.
    Since I can manually move more than 536.36 GB of data to the backup disk, I'm guessing it must be something with Time Machine not recognizing the full space available on the NAS.
    Any ideas?  Has anyone seen this before?

    Hello,
    not that it helps, but I see the same on the exact same configuration. My message is also about not having enough space, ip-to exactly the same amount of room being available (only 536.36 GB available)?
    I tried everything, including a full reset of the StorCenter, but to no avail. The timemachine backup used to work, however I thought that this was just because it didn't exceed the limit of one physical disk in the StorCenter (I've got 4 x 1 TB).
    What is strange is that the original author has 2TB disks and still has the same problem? So it likely isn't related to the physical disk size. It seems like the maximum backup can only be 536.36 GB ??

  • Hardware not recognized when installed via an image

    In our labs we use a lot of computers with various NI cards in it. All the computers are the same. The installation of the computers is done via an image over a network. When a new image is loaded, the hardware in the PC is not recognized, even if the computer configuration is exactly the same as on the image. An administrator has to log in every single computer, to run MAX. How can this be done automatically?

    Hello sillyprimate
    As I understand it you wish to get your 128gb SSD to be recognized by your HP Pavilion dv6-7029wm. Unfortunately, as per the HP Pavilion dv6 Entertainment PC Maintenance and Service Guide for your computer located here your computer supports only the 160-GB drive SSD. This would be why it is not being recognized by your computer.
    I hope this helps resolve your issue. Thank you for posting on the HP Forums. Have a great day!
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    Dunidar
    I work on behalf of HP
    Find out a bit more about me by checking out my profile!
    "Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Maybe you are looking for