Re: [Leaf-devel] Re: Booting Flash on PCMCIA follow-up
Johan Ugander wrote: I'm not using 2.4.x for other reasons. I'd really like to get this to work under 2.2... Matt, THANK YOU! This cleared up a lot. I feel reeeally close to a solution. So close, yet so far. Any ideas? /johan Well, apparently, he tried a few things that didn't work. I wonder if he read the following: http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-5.html It explains the low level driver details of how the CardBus bridge attempts to get a PCI interrupt. It'd be better to hash through those easy options like specifying irq's and port address or reserving irq's for ISA use in the BIOS rather than getting into edge triggered vs level triggered interrupts, and hacking at ide.c. It'd be nice if we could have seen the dmesg output from the system boot. Matt ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] Re: Booting Flash on PCMCIA follow-up
Matt Schalit writes: Mike Noyes wrote: At 2002-02-12 16:33 +, Johan Ugander wrote: Charles Steinkuehler writes: Sounds like interrupts aren't getting routed properly once linux takes over the hardware... Yes, this seems to be the problem. I've altered every bios setting imaginable and I still can't get it to work. This is the sole problem remaining in my attempts. I've tried turning off the on-board IDE, I've tried pretty much every setting. I disabled floppy and FDC all together. It's booting right now as we speak...trudging through unnumerable 'interrupt lost' listings as it's trying to get the packages up. hdk is there, and it sees it, and it accesses it, it just loses the interrupt. ANY ideas, and any experience with the problem under ANY sort of circumstances would be greatly appreciated. If you've ever recieved an 'interrupt lost' output, and fixed it somehow, please tell so that I may try and learn from your solution. So we have several things going on here. Let's see if we can summarize them, quoting Johan from his threads: I am looking to boot from a pcmcia flash card on an embedded pc (pc/104) with bios level pcmcia boot support. Oh, and by the way, my pc/104 pcmcia bridge is the tri-m aaeon pcm3115b http://www.tri-m.com/products/aaeon/manual/pcm3115b.pdf Ok, so he's not using a regular IBM PC/clone 486 or Pentium sort of mainboard, but rather a special micro mainboard called an embedded pc/104. He never tells us his LEAF version. Alrighty then. Let's figure it's a 2.2 kernel, maybe Dachstein. Yes, I am using 2.2.16, sorry about that. The system is a pentium 133 embedded pc/104 with 20MB of RAM. I can shed more light on that if needed. Later we have: it is a compact flash device... 8MB... a fullsize pcmcia card. I also have a 16MB smaller camera-format compact flash card, which fits into a pcmcia adapter Much later we have the description of the 16 MB one he's trying to boot these days: hdk: Hitachi CV 7.1.1, ATA Disk drive hdk: IRQ probe failed (0) ide5 at 0x160-0x167, 0x366 on irq 12 hdk: Hitachi CV 7.1.1, 15MB w/ 1kB Cache, CHS 246/4/32 So he has two PC Cards. Let's start with a definition of PCMCIA, as the folks at the PCMCIA would appreciate it. Every device of this nature is a PC Card and plugs into PC Card slots. Devices and slots should no longer be called PCMCIA cards or PCMCIA slots. The PCMCIA requests this. What does 'PCMCIA' mean and who is the PCMCIA? Personal Computer Memory Card International Association and it was established in 1991 to standardize flash memory addin cards. Just memory cards back then, no I/O. The standards were enhanced in 1994 and to include the PC CardATA specification for dealing with PC Card disk devices and PC Card Flash disk devices. That 1994 2.1 specification included improvements for the Card Information Structure, too. The CIS is the layer that interfaces to the mainboard bios so that you can hotplug PC Card devices and get things recognized. All the time these were 16-bit devices. Then in 1995 they released the CardBus specification for PC Cards giving them a 32-bit bus interfacing directly to the PCI bus via the CardBus bridge. More on that in another post. I apologize for misusing the lingo. =[ He said his card was a: Hitachi CV 7.1.1, 15MB w/ 1kB Cache, CHS 246/4/32 I wonder what his feelings are on this paragraph out of the pcm3115b manual pdf, page 6-6, He mentions this A: vs. D: issue later, though not in detail. Ok, let's wait on discussing it. Well that 15MB card is actually 16..and appears as C: under windows...but lets hold on that topic. Again going back to: hdk: IRQ probe failed (0) ide5 at 0x160-0x167, 0x366 on irq 12 hdk: Hitachi CV 7.1.1, 15MB w/ 1kB Cache, CHS 246/4/32 Using the 16MB card, he gets irq 12. Sounds like the mouse to me. That can't be good. Then he says: I then rebooted on the ide'd compact flash... 8MB card on the outer pcmcia slot. I got into the box, and trying to mount hdk, it gave an almost enless amount of 'hdk: lost interrupt' before working. But he doesn't show us what interrupt it was assigned. If it takes a known and spoken-for interrupt, that set's off bells and whistles. 12, 13, 14, 8, 6, 2, 1, are often taken or not ok to use, even if the usual device is disabled. Sorry, it was taking 12. The ide0 [actual ide, not pc card ide] was taking 14. Conclusions --- The bios complication of 15 being A: and 15 being C: seems to be nonexistant. The problem was the top and bottom slot. Ok. He noticed what I pointed out. It's the slot that matters. Still, given two PC Cards he got hdk irrespective of the size. I don't quite get the details of this, but it may be an extension of his IRQ problem. As I mentioned in another
[Leaf-devel] Re: Booting Flash on PCMCIA follow-up
Charles Steinkuehler writes: Questions - How do I get past the end_request errors being produced for the flash, which seems to be looking for a (nonexistant) floppy? I'm not 100% sure, but what I think is happening: Syslinux is booting, and loading the kernel and initial ramdisk. Then /linuxrc starts running. The /linuxrc script tries to mount the boot= device (as specified on the kernel command line), and if it can't find it, it starts fishing for a boot device, by going through the device list in /var/lib/lrpkg/root.mount. Silly me, I forgot the create the /dev nodes on the embedded side. I had added them to root.mount, yet I forgot to add the mknod commands to linuxrc. I have this problem resolved. Now onto the interrupt issue... NOTE: Unless you're using very non-standard init scripts and boot procedure, you shouldn't have to mess with rdev. The root= and boot= settings in the kernel command line are what matter... Yes, I realized that rdev'ing the kernel wasn't necissary, thanks. The 'lost interrupt' repeats seem to be caused by some sort of slowness on the pcmcia bus and/or an irq problem. How can this be addressed? This I don't know about (I don't work much with notebooks or PCMCIA)...are you sure linux is talking to your PCMCIA controller properly? Sounds like interrupts aren't getting routed properly once linux takes over the hardware... Yes, this seems to be the problem. I've altered every bios setting imaginable and I still can't get it to work. This is the sole problem remaining in my attempts. I've tried turning off the on-board IDE, I've tried pretty much every setting. I disabled floppy and FDC all together. It's booting right now as we speak...trudging through unnumerable 'interrupt lost' listings as it's trying to get the packages up. hdk is there, and it sees it, and it accesses it, it just loses the interrupt. ANY ideas, and any experience with the problem under ANY sort of circumstances would be greatly appreciated. If you've ever recieved an 'interrupt lost' output, and fixed it somehow, please tell so that I may try and learn from your solution. thanks, johan ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Re: Booting Flash on PCMCIA follow-up
At 2002-02-12 16:33 +, Johan Ugander wrote: Charles Steinkuehler writes: Sounds like interrupts aren't getting routed properly once linux takes over the hardware... Yes, this seems to be the problem. I've altered every bios setting imaginable and I still can't get it to work. This is the sole problem remaining in my attempts. I've tried turning off the on-board IDE, I've tried pretty much every setting. I disabled floppy and FDC all together. It's booting right now as we speak...trudging through unnumerable 'interrupt lost' listings as it's trying to get the packages up. hdk is there, and it sees it, and it accesses it, it just loses the interrupt. ANY ideas, and any experience with the problem under ANY sort of circumstances would be greatly appreciated. If you've ever recieved an 'interrupt lost' output, and fixed it somehow, please tell so that I may try and learn from your solution. Johan, I did a quick search on Google, and it looks like this a common problem. I was unable to locate a solution. http://google.com/search?hl=enq=pcmcia+%22lost+interrupt%22 -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf.sourceforge.net/content.php?menu=1000page_id=4 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Re: Booting Flash on PCMCIA follow-up
Mike Noyes wrote: At 2002-02-12 16:33 +, Johan Ugander wrote: Charles Steinkuehler writes: Sounds like interrupts aren't getting routed properly once linux takes over the hardware... Yes, this seems to be the problem. I've altered every bios setting imaginable and I still can't get it to work. This is the sole problem remaining in my attempts. I've tried turning off the on-board IDE, I've tried pretty much every setting. I disabled floppy and FDC all together. It's booting right now as we speak...trudging through unnumerable 'interrupt lost' listings as it's trying to get the packages up. hdk is there, and it sees it, and it accesses it, it just loses the interrupt. ANY ideas, and any experience with the problem under ANY sort of circumstances would be greatly appreciated. If you've ever recieved an 'interrupt lost' output, and fixed it somehow, please tell so that I may try and learn from your solution. Johan, I did a quick search on Google, and it looks like this a common problem. I was unable to locate a solution. http://google.com/search?hl=enq=pcmcia+%22lost+interrupt%22 So we have several things going on here. Let's see if we can summarize them, quoting Johan from his threads: I am looking to boot from a pcmcia flash card on an embedded pc (pc/104) with bios level pcmcia boot support. Oh, and by the way, my pc/104 pcmcia bridge is the tri-m aaeon pcm3115b http://www.tri-m.com/products/aaeon/manual/pcm3115b.pdf Ok, so he's not using a regular IBM PC/clone 486 or Pentium sort of mainboard, but rather a special micro mainboard called an embedded pc/104. He never tells us his LEAF version. Alrighty then. Let's figure it's a 2.2 kernel, maybe Dachstein. Later we have: it is a compact flash device... 8MB... a fullsize pcmcia card. I also have a 16MB smaller camera-format compact flash card, which fits into a pcmcia adapter Much later we have the description of the 16 MB one he's trying to boot these days: hdk: Hitachi CV 7.1.1, ATA Disk drive hdk: IRQ probe failed (0) ide5 at 0x160-0x167, 0x366 on irq 12 hdk: Hitachi CV 7.1.1, 15MB w/ 1kB Cache, CHS 246/4/32 So he has two PC Cards. Let's start with a definition of PCMCIA, as the folks at the PCMCIA would appreciate it. Every device of this nature is a PC Card and plugs into PC Card slots. Devices and slots should no longer be called PCMCIA cards or PCMCIA slots. The PCMCIA requests this. What does 'PCMCIA' mean and who is the PCMCIA? Personal Computer Memory Card International Association and it was established in 1991 to standardize flash memory addin cards. Just memory cards back then, no I/O. The standards were enhanced in 1994 and to include the PC CardATA specification for dealing with PC Card disk devices and PC Card Flash disk devices. That 1994 2.1 specification included improvements for the Card Information Structure, too. The CIS is the layer that interfaces to the mainboard bios so that you can hotplug PC Card devices and get things recognized. All the time these were 16-bit devices. Then in 1995 they released the CardBus specification for PC Cards giving them a 32-bit bus interfacing directly to the PCI bus via the CardBus bridge. More on that in another post. What does PCMCIA not mean? Pretty Confusing. May Cause Intense Anxiety -- Bruce Bennet People Cannot Memorize Computer Industry Acronyms. -- unknown Personal Computer Marketers Can't Invent Acronyms -- unknown He said his card was a: Hitachi CV 7.1.1, 15MB w/ 1kB Cache, CHS 246/4/32 I wonder what his feelings are on this paragraph out of the pcm3115b manual pdf, page 6-6, 'Note When using an ATA HDD or ATA Flash card with Boot ROM v.2.0x, the size of the card determines whether it boots as drive A or drive C. If the card is less than 15 MB, it will boot as drive A and the floppy disk will become B; if greater than 15 MB it will boot as drive C and your hard drive will become D. This means that Flash cards (which are typically less than 15 MB) will boot as A, and ATA HDD cards (typically greater than 15 MB) will boot as drive C.' He mentions this A: vs. D: issue later, though not in detail. Ok, let's wait on discussing it. Again going back to: hdk: IRQ probe failed (0) ide5 at 0x160-0x167, 0x366 on irq 12 hdk: Hitachi CV 7.1.1, 15MB w/ 1kB Cache, CHS 246/4/32 Using the 16MB card, he gets irq 12. Sounds like the mouse to me. That can't be good. Then he says: I then rebooted on the ide'd compact flash... 8MB card on the outer pcmcia slot. I got into the box, and trying to mount hdk, it gave an almost enless amount of 'hdk: lost interrupt' before working. But he doesn't show us what interrupt it was assigned. If it takes a known and spoken-for interrupt, that set's off bells and whistles. 12, 13, 14, 8, 6, 2, 1, are often taken or not ok to use, even if the
