Menu
▾
▴
devil-linux-discuss
|
From: Jan H. P. <jh...@jh...> - 2014-03-18 23:07:18
|
Hi everyone, I'm currently setting up a new router and I run into a strange issue. After I created the build I first used it to upgrade a running router. This was perfectly fine. The configuration was picked up just fine and everything worked again. Now I have a new router with some special motherboard with a CF slot and 8 1G interfaces. Very nice for a router. I took a CF card, put the install on this CF card on partition 1 (400G) and on a second partition (100G) I put the configuration set. The system boots fine but then ..... It is not able to find the configuration on the second partition of the CF card and it looks like it doesn't see the CF card at all. I have to put in a USB stick with the complete content of the CDROM and the configuration set to be able to get it working because it still searches for the CDROM while everything should be on the CF card. If I put in a USB stick with just the configuration set it will start searching for the Devil-Linux CDROM and it won't find it and then it fails. Does anyone have a sollution for this? Jan Hugo Prins |
|
From: Jan H. P. <jh...@jh...> - 2014-03-18 23:10:12
|
The sizes of the disks are 400MB and 100MB and not 400GB and 100GB. It's just a 500MB CF card. Jan Hugo On 03/19/2014 12:07 AM, Jan Hugo Prins wrote: > Hi everyone, > > I'm currently setting up a new router and I run into a strange issue. > After I created the build I first used it to upgrade a running router. > This was perfectly fine. The configuration was picked up just fine and > everything worked again. > > Now I have a new router with some special motherboard with a CF slot and > 8 1G interfaces. Very nice for a router. I took a CF card, put the > install on this CF card on partition 1 (400G) and on a second partition > (100G) I put the configuration set. The system boots fine but then ..... > > It is not able to find the configuration on the second partition of the > CF card and it looks like it doesn't see the CF card at all. > > I have to put in a USB stick with the complete content of the CDROM and > the configuration set to be able to get it working because it still > searches for the CDROM while everything should be on the CF card. If I > put in a USB stick with just the configuration set it will start > searching for the Devil-Linux CDROM and it won't find it and then it fails. > > Does anyone have a sollution for this? > > Jan Hugo Prins > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Andrzej O. <an...@ma...> - 2014-03-19 00:49:09
|
Jan Hugo Prins wrote: > Hi everyone, > > I'm currently setting up a new router and I run into a strange issue. > After I created the build I first used it to upgrade a running router. > This was perfectly fine. The configuration was picked up just fine and > everything worked again. > > Now I have a new router with some special motherboard with a CF slot and > 8 1G interfaces. Very nice for a router. Dear Jan Hugo, This is probably a completely new motherboard (by the way, show off what the MBs). > I took a CF card, put the > install on this CF card on partition 1 (400G) and on a second partition > (100G) I put the configuration set. The system boots fine but then ..... > > It is not able to find the configuration on the second partition of the > CF card and it looks like it doesn't see the CF card at all. > > I have to put in a USB stick with the complete content of the CDROM and > the configuration set to be able to get it working because it still > searches for the CDROM while everything should be on the CF card. If I > put in a USB stick with just the configuration set it will start > searching for the Devil-Linux CDROM and it won't find it and then it fails. I wrote on a Devil-linux-Develop list, that the new MBs have USB 3.0 controllers instead of USB 2.0 and for this chips xHCI host driver is required. This driver is by default compiled with the kernel as a module. BIOS sees the USB storage device and can boot. The kernel sees them only when udev loads device drivers. This happens when a configuration is already unpacked on a ramdisk and the CD is mounted. For configuration was seen when on USB 3.0 mass storage device, xHCI driver must be loaded before, which requires either modification scripts in the initrd and addition the driver to the initrd or static linking xHCI driver to the kernel via CONFIG_USB_XHCI_HCD=y setting. Heiko made this change to CVS on my request at February 8. > Does anyone have a sollution for this? Try D-L compiled after that date, or compile D-L yourself with current sources. If this is not possible for you, please contact me on priv and I will give you link to my mod compilation - you will see if this works for you. Regards Andrzej Odyniec --- Ta wiadomość e-mail jest wolna od wirusów i złośliwego oprogramowania, ponieważ ochrona avast! Antivirus jest aktywna. http://www.avast.com |
|
From: Jan H. P. <jh...@jh...> - 2014-03-19 13:17:32
Attachments:
cb8902_quicksetup_v.1.0.pdf
|
Hi Andrzej, > This is probably a completely new motherboard (by the way, show off what the MBs). > Not completely new. The board I'm working with at the moment is an Aewin CB-8902 board and the board is probably about 5 or 6 years old. Attached is some board information. > I wrote on a Devil-linux-Develop list, that the new MBs have USB 3.0 > controllers instead of USB 2.0 and for this chips xHCI host driver is > required. This driver is by default compiled with the kernel as a module. > > BIOS sees the USB storage device and can boot. The kernel sees them only when > udev loads device drivers. This happens when a configuration is already > unpacked on a ramdisk and the CD is mounted. For configuration was seen when > on USB 3.0 mass storage device, xHCI driver must be loaded before, which > requires either modification scripts in the initrd and addition the driver to > the initrd or static linking xHCI driver to the kernel via > CONFIG_USB_XHCI_HCD=y setting. > > Heiko made this change to CVS on my request at February 8. Although the problem is probably not the same (no USB 3.0) the solution might indeed be something I have to look at. I would need to find out what driver I need to compile static into my kernel. The build I created was from somewhere in the beginning of this month, I would guess that your change is allready in it. Let me quickly check .... build/dist/dist/devil-linux-1.6.5-2014-03-10-pentium4/DL-kernel-config:CONFIG_USB_XHCI_HCD=y So indeed, this one is in it. I will have to do some digging. > Try D-L compiled after that date, or compile D-L yourself with current > sources. If this is not possible for you, please contact me on priv and I will > give you link to my mod compilation - you will see if this works for you. Thanks, Jan Hugo Prins |
|
From: Andrzej O. <an...@ma...> - 2014-03-20 17:28:37
|
Jan Hugo Prins wrote: > Hi Andrzej, > > >>This is probably a completely new motherboard (by the way, show off what the MBs). >> > > > Not completely new. The board I'm working with at the moment is an Aewin > CB-8902 board and the board is probably about 5 or 6 years old. Attached > is some board information. > >>I wrote on a Devil-linux-Develop list, that the new MBs have USB 3.0 >>controllers instead of USB 2.0 and for this chips xHCI host driver is >>required. This driver is by default compiled with the kernel as a module. >> Dear Jan Hugo, Well, a quick installation guide has nothing about the CF controller. We also have a question: how long will live capacitors on the board, since it already has six years? I was expecting, CF controller is connected as Mass Storage device via USB but you can see that it does not. However, the scenario is as described, which means that the initial stage of the boot is missing appropriate driver and the kernel does not see CF card. When later CD is mounted and all modules are present in filesystems, udev loads the appropriate drivers and CF card will be displayed. You need to determine which module is responsible for access to CF eg reading lspci, lsmod, watching /proc/bus, /proc/scsi etc under full system (when a CD is already mounted (with the default configuration or the configuration loaded from the CD as well) and CF is visible. As you suspected a module, remove it using rmmod and then check whether the device CF disappeared and then load it back using modprobe and check if it had come again. Then you can try to compile the apropriate driver as linked statically into the kernel. This is simplest way; when driver is linked into the kernel, device is present immediatelly after kernel is loaded, without modules from initrd and explicite loading this modules by init script. If you are not prepared for such a compilation, let me know about needed module and I will try to compile an experimental mod for you. Regards Andrzej Odyniec --- Ta wiadomość e-mail jest wolna od wirusów i złośliwego oprogramowania, ponieważ ochrona avast! Antivirus jest aktywna. http://www.avast.com |
|
From: <gd...@tx...> - 2014-03-20 18:26:37
|
You might also want to try a CF to ATA adapter which is what I am using to boot Devil Linux from a CF card. All they are are small PC boards with the correct connectors to allow the CF device to be plugged into a standard motherboard ATA hard drive connector. They also require power, normally from a standard 3 1/2" power supply connector (not SATA) because the standard MB ATA connector does not have power pins. After that they look just like a normal hard drive to the OS so no unusual drivers are needed. I have been using onefor quite a while now with no problems. I did a quick check on Ebay and they are available for about $7 USD with shipping included, They are also available from more local suppliers but they usually cost between $10 and $15. I use a Secure Digital card connected to the computer using a USB card reader for the configuration file because it has a write protect tab and mounts read-only with the tab in the locked position. The only time this device is mounted (mine shows up as /dev/sda1 using fdisk, the CF card shows up as /dev/hda1) is when the computer is booting or while the save-config script is running so it can be removed, unlocked/locked, and re-installed, as needed. One note of caution. Not all USB card readers report the state of the lock tab and none of them that I've seen advertise if they do or not. It is easy enough to find out if they do or not but not until after you bought it which I found out the hard way of course :( ---- Andrzej Odyniec <an...@ma...> wrote: > Jan Hugo Prins wrote: > Hi Andrzej, > > >>This is probably a completely new motherboard (by the way, show off what the MBs). >> > > > Not completely new. The board I'm working with at the moment is an Aewin > CB-8902 board and the board is probably about 5 or 6 years old. Attached > is some board information. > >>I wrote on a Devil-linux-Develop list, that the new MBs have USB 3.0 >>controllers instead of USB 2.0 and for this chips xHCI host driver is >>required. This driver is by default compiled with the kernel as a module. >> Dear Jan Hugo, Well, a quick installation guide has nothing about the CF controller. We also have a question: how long will live capacitors on the board, since it already has six years? I was expecting, CF controller is connected as Mass Storage device via USB but you can see that it does not. However, the scenario is as described, which means that the initial stage of the boot is missing appropriate driver and the kernel does not see CF card. When later CD is mounted and all modules are present in filesystems, udev loads the appropriate drivers and CF card will be displayed. You need to determine which module is responsible for access to CF eg reading lspci, lsmod, watching /proc/bus, /proc/scsi etc under full system (when a CD is already mounted (with the default configuration or the configuration loaded from the CD as well) and CF is visible. As you suspected a module, remove it using rmmod and then check whether the device CF disappeared and then load it back using modprobe and check if it had come again. Then you can try to compile the apropriate driver as linked statically into the kernel. This is simplest way; when driver is linked into the kernel, device is present immediatelly after kernel is loaded, without modules from initrd and explicite loading this modules by init script. If you are not prepared for such a compilation, let me know about needed module and I will try to compile an experimental mod for you. Regards Andrzej Odyniec --- Ta wiadomość e-mail jest wolna od wirusów i złośliwego oprogramowania, ponieważ ochrona avast! Antivirus jest aktywna. http://www.avast.com ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
