Latest posts of: BP

Show Posts
Pages: [1] 2

1	Linux Stuff / Kernel / Re: 2.6.34.1 new release	on: July 27, 2010, 08:11:10 PM
cbxbiker61, just to let you know, problem was the esia reinstall. Not sure why exactly, but it seems my previous attempts were not upgrading the kernel... I gave it another try with one more option selected (which made the process freeze during previous attempts) and it worked !! ;-) Now I have 2.6.31.4 install for real and autofs install went through without a glitch. regards,

2	General Category / General Discussion / Re: New QT based installer: Enhanced Sheevaplug Installer Application (ESIA)	on: July 23, 2010, 09:16:00 PM
rooster, Good news ! Before going to bed, i thought i would give one more try to the "boot from sd" option in ESIA, and let it run all nigth. As explained in previous post it freezed twice on previous attempt when selecting that option... Now with same DOK, same files (untouched since last install), same pc, same usb port on pc, etc... go wonder, it worked !! And I think that option made the difference, because now uname -a return 2.6.34.1 !!! yeah !! ;-) Not sure what the problem was, if any... , but my take away will be "always try 3 times" ;-) the bad news is I wont be able to retry autofs install before 3 days from now... but i am positive Thanks again !

3	Linux Stuff / Kernel / Re: 2.6.34.1 new release	on: July 23, 2010, 06:51:47 PM
Hey cbxbiker61, you were rigth sir ! uname -a returned 2.6.30.2. I confirmed with MD5 signatures I used the 2.6.34.1 uImage and modules file when re-installing with ESIA... I left rooster a message (post) with some details, will see what comes out of it... I read the wiki, 2 or 3 posts and the file itself to get an overview of the ./readme procedure. Step by step seems to be changing depending of each plug exact situation... will wait a bit before taking that route, giving the ESIA couple more attempts. Many thanks to you,

4	General Category / General Discussion / Re: New QT based installer: Enhanced Sheevaplug Installer Application (ESIA)	on: July 23, 2010, 04:07:21 PM
Hi rooster, it's me again yeap, uname -a return 2.6.30.2 kernel version... I double checked and I can confirm I did the ubuntu install with ESIA using the rootfs file from your forgenet repository, the uImage and modules files from the http://sheeva.with-linux.com/sheeva/2.6.34.1 ... MD5 signature to support, I got the same as provided in the repository (the the equivalent .MD5 file for each) I thought for a moment that maybe I had to reinstall the uboot, but according to ESIA interface descriptions, kernell and modules are installed with the app. Any idea what could make ESIA not replace the kernel ? During installation, there is a box i did not checked off because freezing the installation and not mentionned in the walkthrough document. It is the "boot from mmc" just above the "backup ..." in the very last window. Wasn't sure what it was for since I already selected "install to mmc" in a previous step, and again selecting it made the process freeze at 0% forever. Hope this would help you help me :-), i am getting desperate... many thanks,

5	General Category / General Discussion / Re: New QT based installer: Enhanced Sheevaplug Installer Application (ESIA)	on: July 23, 2010, 11:09:55 AM
Rooster, cbxbiker61 pointed me that it looks like I am still running 2.6.30.2 according to the error message... Code: Starting automounter: loading autofs4 kernel module,FATAL: Could not load /lib/modules/2.6.30.2/modules.dep: No such file or directory no automount maps defined. But I reinstalled ubuntu 9.04 with ESIA using the rootfs file from your forgenet repository, along with the uImage and modules files from the http://sheeva.with-linux.com/sheeva/2.6.34.1 ... MD5 signature updated in the MANIFEST did work I think because the ESIA interface showed applications ok as opposed to broken before updating MD5. I will double check everything tonigth, and do uname -a, but would you have any clue what could cause this? Thanks again,

6	Linux Stuff / Kernel / Re: 2.6.34.1 new release	on: July 23, 2010, 10:53:08 AM
good point!! Thanks sir! I will try that uname -a tonigth... but how could this be possible? I did a complete reinstalled of ubuntu using ESIA with "uImage" and "modules" files from 2.6.34.1 ?? will double check everything tonight and let you know... best regards,

7	General Category / General Discussion / Re: New QT based installer: Enhanced Sheevaplug Installer Application (ESIA)	on: July 23, 2010, 10:44:23 AM
Thanks guys, I reinstalled Ubuntu 9.04 using ESIA + new uImage and modules file from the http://sheeva.with-linux.com/sheeva/2.6.34.1 . Everything went fine, but no luck, same message at the end of the autofs install... I post a request for help to cmxbiker61 to see if the needed modules should be "installed" or not since they show in the modules tarball. Also ask how I could install manually, and if he plan to include them (should I say "in the kernel" ?) as I understood he seems to be the master of all those new version of kernel. In the meantime, I will keep searching and reading, worst case I will have to find another solution than autofs for automounting. Will keep you posted,

8	Linux Stuff / Kernel / Re: 2.6.34.1 new release	on: July 22, 2010, 06:03:25 PM
Hi cbxbiker61, I get the following error at the end of "apt-get install autosf" ... Code: ..... Starting automounter: loading autofs4 kernel module,FATAL: Could not load /lib/modules/2.6.30.2/modules.dep: No such file or directory no automount maps defined. Processing triggers for libc6 ... ldconfig deferred processing now taking place root@ubuntu:/# Installing autosf was taking place immediately after the following "restart from scratch" steps: 1- install ubuntu 9.04 with ESIA, boot from sd card, used "uImage" and "modules" files from 2.6.34.1, evrything went fine. 2- disconnect plug power cable 3- disconnect serial cable 4- remove usb DOK 5- connect ethernet to router 6- reconnect plug power cable 7- wait 1-2 minutes 8- open SSH connection 9- login with root/nosoup4u 10- apt-get update 11- apt-get install nano 12- apt-get install samba 13- modifying smb.conf as per wiki instructions to add a shares 14- reload samba 15- change the name in the /etc/hostname 16- apt-get install autofs ...and then get the error message previously mentioned. Later I found (in fact rooster did...) "autofs.ko" and "autofs4.ko" in your modules tarball on "http://sheeva.with-linux.com/sheeva/", respectively in "sheeva-2.6.34.1-Modules.tar.gz\sheeva-2.6.34.1-Modules.tar\.\lib\modules\2.6.34.1\kernel\fs\autofs\" and "....\autofs4\" Now my question is : Since those modules are part of the same kernel package I used, are they not supposed to be installed? Why can't apt-get find it? Should I copy paste the .ko files manually somewhere? Please dont tell me I have to "compile" something, I would rather go hang myself ;-) If its not plain copy-paste for me to do, would you consider adding the modules in a not too far future? Thanks a lot,

9	General Category / General Discussion / Re: New QT based installer: Enhanced Sheevaplug Installer Application (ESIA)	on: July 21, 2010, 11:10:37 PM
Hey, me again ;-) I googled and found what is MD5, and downloaded a utility to generate the key. Should be ok. [EDIT] oups... I found later that MD5 signature were provided (the .MD5 files) along with uImage/modules.tar.gz on http://sheeva.with-linux.com/sheeva/ . No need to download a generator. For the modules in the tarball, I saw nothing even close to "autofs"... Anyone, any clue on where to find and how to install autofs specific modules would be appreciated (without reinstalling the complete rootfs of course) thanks again,

10	General Category / General Discussion / Re: New QT based installer: Enhanced Sheevaplug Installer Application (ESIA)	on: July 21, 2010, 10:49:20 PM
HI rooster, By the way, many thanks for that great great great tool for non-linux folks ;-) ! I already tried to replaced the two files uImage and modules.tar.gz with the ones from version 2.6.34.1 on that link you refer to, but then the ESIA said my apllication package on the USB DOK was broken... Now I understand it is related to the Manifest file that need to be updated. Is there anywhere a tutorial or page to read to learn how to do proceed to that MD5 signature update ? best regards,

11	General Category / General Discussion / Re: New QT based installer: Enhanced Sheevaplug Installer Application (ESIA)	on: July 21, 2010, 10:24:16 PM
Hi all, Are "autofs" related modules installed with other modules during the ESIA process ? I get the following error at the end of "apt-get install autosf" ... ..... Starting automounter: loading autofs4 kernel module,FATAL: Could not load /lib/modules/2.6.30.2/modules.dep: No such file or directory no automount maps defined. Processing triggers for libc6 ... ldconfig deferred processing now taking place root@ubuntu:/# Installing autosf was taking place immediately after the following "restart from scratch" steps: 1- install ubuntu 9.04 with ESIA, boot from sd card 2- disconnect plug power cable 3- disconnect serial cable 4- remove usb DOK 5- connect ethernet to router 6- reconnect plug power cable 7- wait 1-2 minutes 8- open SSH connection 9- login with root/nosoup4u 10- apt-get update 11- apt-get install nano 12- apt-get install samba 13- modifying smb.conf as per wiki instructions to add two shares (1 for external drive, 1 for rootfs) 14- reload samba 15- change the name in the /etc/hostname I read many post of different people mentionning autofs as a good solution for automounting usb drive on the plug, so I understand they were able to install it.... Did they load additional modules manually or did something went wrong with my install ? (I got no error message) Many thanks,

12	General Category / General Discussion / Re: Sheevaplug installer - version 1.0	on: October 05, 2009, 08:40:27 PM
Final answers... to my remaining questions : 1- Should I run “runme mmc” with SD card inserted or not? YES INSERT THE CARD PRIOR TO RUN RUNME. It seems to make no difference for the RUNME itself, got same result, but it will not work when rebooting in the following step. Console will show "MMC card not found" error messages... 3- What “uboot.bin” should I use and where exactly to download it from? IT FINALLY WORKED USING THE UBOOT ALREADY INCLUDED IN THE INSTALLER PACKAGE. Not sure what the difference would be to use another one, but it works now and will not give myself additional research for now. 8- After "ctrl+C" / unplug+reconnect miniusb / open putty session on COM14 / rest the plug : should I expect to get the exact same ouput logs in Putty session screen ?? YES AND NO : through my various attemp, inserting the sd card at different stage, I always got to the same step after the plug reset : Unable to read "/uImage" from mmc 0:1 ## Booting image at 00800000 ... Bad Magic Number Marvell>> I sudenly remembered about the "run recover1" command I read about somewhere (now I know it's in Installer wiki) and event if thinking I was not yet at a stage for the plug to understand that command I tried it... and it worked !! The following logs were practically identical to the README up to the end. Where the README example end, the plug will restart once more in real life. I think my plug is ready to install apps now. Hope the details of my experience will help someone one day...

13	General Category / General Discussion / Re: Sheevaplug installer - version 1.0	on: October 05, 2009, 05:45:22 PM
OK, made some more findings and progress :-) 1- The installer process always stopped at the same stage and error message because I did not install the "LibUSB-Win32-0.1.12.1" as per requested in the Installer README. My mistake, I thougth it was the same than the CDM 2.04.14 drivers... 2- I think the “sheevaplug.cfg” file must be a mix of older and newer version... The process only works for me with the current plug VID and PID (in my plug the "old" values). But if keeping the "old .cfg" as is, I still get JTAG errors. To go through the complete process with no error, I must also "comment out" the "JTAG related line" in the .cfg ... as per the new one does... See the mix result below. Passive, maybe this can worth a try for you ? Google and download "USBDeview" , it shows your plug current VIP and PID when conected. Code: interface ft2232 ft2232_layout sheevaplug ft2232_vid_pid 0x9e88 0x9e8f #ft2232_device_desc "SheevaPlug JTAGKey FT2232D B" jtag_khz 2000 So I now get to the "wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 112.746002s" line and must do ctrl+c to exit, but from there it is not stable at all. I dont always get the same results, and cant get the same 2-3 "reboot" logs shown in the README even when resetting the plug as per troubleshooting suggestions. I tried the 3 uboot.bin version I found just in case, with or without the SD card inserted, but nothing consistent yet. So couple questions remains : 1. Should I run “runme mmc” with SD card inserted or not? Some post here sound like I should but the README say no, and with or without, I get errors at one point... 3. What “uboot.bin” should I use and where exactly to download it from? (I mean should I find it under the exact same short simple name on the download page ? Or what exact file name am I looking for?) It finnaly worked with the on from the installer package, and did not with a more recent one found on the ressource/dowload page of this web.site... so question remains. 8. After "ctrl+C" / unplug+reconnect miniusb / open putty session on COM14 / rest the plug : should I expect to get the exact same ouput logs in Putty session screen ?? I did not so far, and never got a "clean" ending yet.. I mean with a prompt or clear message. ~~2. Should I set my “sheevaplug.cfg” file with (9e88 and 9e8f) or (0403 and 6010)? Currently my plugs shows (9e88 and 9e8f) in USBDeview.~~ ~~4. Does both COM PORT must be set the same ? (More specifically for speed and Flow Control)~~ ~~5. Should I also copy the “uboot-mmc-custom.txt” to the USB stick root ? (INSTALLER v1.0 procedure don’t ask for it, but I read it was necessary on previous version of the installer… )~~ ~~6. Does the plug need to be connected to my network router ? (INSTALLER v1.0 procedure don’t say so, but should I at this stage ?)~~ ~~7. Anything else could be the problem ?~~ I'll keep searching, but any clue or confirmation will be more then welcome :-) Thank to all,

14	General Category / General Discussion / Re: Sheevaplug installer - version 1.0	on: October 04, 2009, 04:14:29 PM
Hi all, Not wanting to waste anybody’s time here, I thought avoiding multiple “one step at a time” troubleshooting questions would be a good thing. So here is a long post, but as extensive as possible, in an attempt to make it useful for anyone more knowledgeable than me to point out where I am doing wrong… As in a previous post I just deleted because repeating myself a bit, I am having similar problem then passive ( or other pluggers in the past) but everything I found in this forum (even if solving some problems) did not make it work completely. Let’s start with the “runme mmc” logs and the error message at the end of it : Code: C:\Documents and Settings\bpelleti\My Documents\My SHeevaPlug project\SheevaPlug Installer>runme mmc ** Preparing environment variables file ... [color=green]EVERYTHING IN BETWEEN HERE IS AS PER THE INSTALLER README[/color] Burning uboot and environment variables ... This will take few minutes ... When uboot.bin is written to NAND/SD, Disconnect and connect your mini U SB cable Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release $URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $ For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS 2000 kHz jtag_nsrst_delay: 200 jtag_ntrst_delay: 200 dcc downloads are enabled [color=red]AND HERE START THE ERRORS Error: unable to open ftdi device: device not found Runtime error, file "command.c", line 469: openocd FAILED Is the mini USB cable connected? Try powering down, then replugging the Sheevaplug[/color] C:\Documents and Settings\bpelleti\My Documents\My SHeevaPlug project\SheevaPlug Installer> Now the background and everything I tried : • I am using an XP machine (that’s all I have) • I never did anything related to Linux with this machine before (or any other machine in fact) • I have CDM 2.04.16_SHEEVA usb drivers installed as described here in the wiki http://plugcomputer.org/plugwiki/index.php/Serial_terminal_program#Updating_the_Windows_Driver:_FTDI_2232. • I installed Putty for serial console • I purchased my plug 2 weeks ago, and received it 2 days ago • It looks like (but not sure it is) a newer plug. Distance between Ethernet and USB port is about an inch, but using “USBDeview” utility, my plug shows Vendor ID and Product ID being 9e88 and 9e8f. (as opposed to the expected 0403 and 6010 for the most recent ones…) • When first connected the plug to my pc, the windows XP automated driver installation ran 3 times, and each time I pointed it to the CDM 2.04.16 directory for drivers to be installed. Looks like drivers are installed OK. • I later discovered only one COM PORT (#14) showed up where other users got two. Based on findings in this forum (thanks to all) I checked the proper box in the USB Serial Converter properties and then saw both COM PORT 13 (on converter A) and 14 (on converter B) - see COM13&14picture attached. • I set both COM PORT 13 and 14 to the following parameters : 115200, 8n1 with FLOW CONTROL to NONE (also according to finding in this forum or wiki) • With those same parameters in Putty, I can open session on COM14, press “ENTER” once and then get a “debian login: ” prompt. ( I don’t know what to use as login, but I think it proves connection ok) • Still with session open on COM14 and resetting the plug with the reset button, I get a long sequence of logs. But at the end the log freeze on an error message (see here) Code: __ __ _ _ \| \/ \| __ _ _ ____ _____\| \| \| \| \|\/\| \|/ _` \| '__\ \ / / _ \ \| \| \| \| \| \| (_\| \| \| \ V / __/ \| \| \|_\| \|_\|\__,_\|_\| \_/ \___\|_\|_\| _ _ ____ _ \| \| \| \| \| __ ) ___ ___ \| \|_ \| \| \| \|___\| _ \ / _ \ / _ \\| __\| \| \|_\| \|___\| \|_) \| (_) \| (_) \| \|_ \___/ \|____/ \___/ \___/ \__\| MARVELL BOARD: SHEEVA PLUG LE U-Boot 1.1.4 (Mar 19 2009 - 16:06:59) Marvell version: 3.4.16 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CEE80 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM CS[1] base 0x10000000 size 256MB DRAM Total size 512MB 16bit width Flash: 0 kB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:512 MB CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 3 2 1 0 NAND read: device 0 offset 0x100000, size 0x400000 Reading data from 0x100000 -- 0% complete. Reading data from 0x10a000 -- 1% complete. ... Reading data from 0x4f5800 -- 99% complete. Reading data from 0x4ff800 -- 100% complete. 4194304 bytes read: OK ## Booting image at 00800000 ... Image Name: Linux-2.6.22.18 Created: 2009-03-19 9:18:16 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2106696 Bytes = 2 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.22.18 (dhaval@devbox) (gcc version 4.2.1) #1 Thu Mar 19 14:46:22 IST 2009 CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177 Machine: Feroceon-KW Using UBoot passing parameters structure Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Built 1 zonelists. Total pages: 130048 Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB 0MB 0MB = 512MB total Memory: 515456KB available (3864K code, 257K data, 104K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 CPU Interface ------------- SDRAM_CS0 ....base 00000000, size 256MB SDRAM_CS1 ....base 10000000, size 256MB SDRAM_CS2 ....disable SDRAM_CS3 ....disable PEX0_MEM ....base e8000000, size 128MB PEX0_IO ....base f2000000, size 1MB INTER_REGS ....base f1000000, size 1MB NFLASH_CS ....base fa000000, size 2MB SPI_CS ....base f4000000, size 16MB BOOT_ROM_CS ....no such DEV_BOOTCS ....no such CRYPT_ENG ....base f0000000, size 2MB Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- SHEEVA PLUG Soc: 88F6281 A0 LE Detected Tclk 200000000 and SysClk 400000000 MV Buttons Device Load Marvell USB EHCI Host controller #0: c08b8600 PEX0 interface detected no Link. PCI: bus0: Fast back to back transfers enabled SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 Time: kw_clocksource clocksource has been installed. IP route cache hash table entries: 16384 (order: 4, 65536 bytes) TCP established hash table entries: 65536 (order: 7, 524288 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 65536 bind 65536) TCP reno registered RTC registered Use the XOR engines (acceleration) for enhancing the following functions: o RAID 5 Xor calculation o kernel memcpy o kenrel memzero Number of XOR engines to use: 4 cesadev_init(c000c894) mvCesaInit: sessions=640, queue=64, pSram=f0000000 Warning: TS unit is powered off. MV Buttons Driver Load NTFS driver 2.1.28 [Flags: R/O]. JFFS2 version 2.2. (NAND) Ã‚Â© 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler anticipatory registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A Loading Marvell Ethernet Driver: o Cached descriptors in DRAM o DRAM SW cache-coherency o Single RX Queue support - ETH_DEF_RXQ=0 o Single TX Queue support - ETH_DEF_TXQ=0 o TCP segmentation offload enabled o Receive checksum offload enabled o Transmit checksum offload enabled o Network Fast Processing (Routing) supported o Driver ERROR statistics enabled o Driver INFO statistics enabled o Proc tool API enabled o Rx descripors: q0=128 o Tx descripors: q0=532 o Loading network interface(s): o eth0, ifindex = 1, GbE port = 0 o eth1, ifindex = 2, GbE port = 1 mvFpRuleDb (dfd00000): 16384 entries, 65536 bytes Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI Copyright (c) 1999-2006 Intel Corporation. e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI e100: Copyright(c) 1999-2006 Intel Corporation Warning Sata is Powered Off NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 2296 at 0x11f00000 Bad eraseblock 2544 at 0x13e00000 Bad eraseblock 2792 at 0x15d00000 Bad eraseblock 2982 at 0x174c0000 Bad eraseblock 3027 at 0x17a60000 Bad eraseblock 3512 at 0x1b700000 Bad eraseblock 3516 at 0x1b780000 Bad eraseblock 3938 at 0x1ec40000 2 cmdlinepart partitions found on MTD device nand_mtd Using command line partition definition Creating 2 MTD partitions on "nand_mtd": 0x00100000-0x00500000 : "uImage" 0x00500000-0x20000000 : "rootfs" ehci_marvell ehci_marvell.70059: Marvell Orion EHCI ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1 ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100 ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected USB Universal Host Controller Interface driver v3.0 usb 1-1: new high speed USB device using ehci_marvell and address 2 usb 1-1: configuration #1 chosen from 1 choice usbcore: registered new interface driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice i2c /dev entries driver Linux telephony interface: v1.00 Marvell Telephony Driver: mvBoardVoiceAssembleModeGet: TDM not supported(boardId=0x9) assembly=-1,irq=-1 mp_check_config: Error, invalid voice assembley mode md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 raid6: int32x1 97 MB/s raid6: int32x2 114 MB/s raid6: int32x4 122 MB/s raid6: int32x8 110 MB/s raid6: using algorithm int32x4 (122 MB/s) md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 raid5: measuring checksumming speed arm4regs : 1084.000 MB/sec 8regs : 754.800 MB/sec 32regs : 899.600 MB/sec raid5: using function: arm4regs (1084.000 MB/sec) device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com dm_crypt using the OCF package. sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman mvsdmmc: irq =28 start f1090000 mvsdmmc: no IRQ detect usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). mvCLAudioCodecRegGet: Error while reading register! mvCLAudioCodecInit: Error - Invalid Cirrus Logic chip/rev ID! Error - Cannot initialize audio decoder.at address =0xff<6>ALSA device list: #0: Marvell mv88fx_snd ALSA driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 eth0: started IP-Config: Complete: device=eth0, addr=10.4.50.4, mask=255.255.255.0, gw=10.4.50.5, host=DB88FXX81, domain=, nis-domain=(none), bootserver=10.4.50.5, rootserver=10.4.50.5, rootpath= md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Empty flash at 0x0d6d6b70 ends at 0x0d6d7000 Empty flash at 0x14191cb4 ends at 0x14192000 VFS: Mounted root (jffs2 filesystem). Freeing init memory: 104K scsi 0:0:0:0: Direct-Access SanDisk Cruzer 0.1 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 8027712 512-byte hardware sectors (4110 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] 8027712 512-byte hardware sectors (4110 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI removable disk sd 0:0:0:0: Attached scsi generic sg0 type 0 * Setting preliminary keymap... [80G [74G[ OK ] * Setting the system clock * Starting basic networking... [80G [74G[ OK ] * Starting kernel event manager... [80G [74G[ OK ] * Loading hardware drivers... [80G [74G[ OK ] * Setting the system clock * Loading kernel modules... [80G * Loading manual drivers... [80G [74G[ OK ] * Setting kernel variables (/etc/sysctl.conf)... [80G [74G[ OK ] * Setting kernel variables (/etc/sysctl.d/10-console-messages.conf)... [80G [74G[ OK ] * Setting kernel variables (/etc/sysctl.d/10-network-security.conf)... [80G [74G[ OK ] * Setting kernel variables (/etc/sysctl.d/10-process-security.conf)... [80G error: "vm.mmap_min_addr" is an unknown key [74G[[31mfail[39;49m] * Setting kernel variables (/etc/sysctl.d/10-tcp-timestamps-workaround.conf)... [80G [74G[ OK ] * Activating swap... [80G [74G[ OK ] FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory * Starting early crypto disks... [80G [74G[ OK ] FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory * Starting remaining crypto disks... [80G [74G[ OK ] * Checking file systems... [80G fsck 1.41.3 (12-Oct-2008) [74G[ OK ] * Mounting local filesystems... [80G [74G[ OK ] * Activating swapfile swap... [80G [74G[ OK ] * Configuring network interfaces... [80G [74G[ OK ] * Setting up console font and keymap... [80G [74G[ OK ] * Starting system log daemon... [80G Ubuntu jaunty (development branch) debian ttyS0 debian login: [74G[ OK ] * Starting kernel log daemon... [80G [74G[ OK ] * Starting OpenBSD Secure Shell server sshd [80G [74G[ OK ] * Starting periodic command scheduler crond [80G [74G[ OK ] fat: exports duplicate symbol fat_add_entries (owned by kernel) insmod: error inserting '/boot/fat.ko': -1 Invalid module format • Again with same parameters in Putty I only get a blank screen when opening a session on COM13. Pressing ENTER does nothing, and resetting the plug shows nothing either. Now for the INSTALLER PROCESS • I found and updated the “uboot-mmc-custom.txt” file with my plug MAC address • I found and replaced the “openocd” file with the new one posted by rooster earlier in this thread. • I tried both set of VIP and PID in the “sheevaplug.cfg” file • I tried 3 different version of “uboot.bin” file in my “installer/uboot/” directory : o The original one included in the installer package o The “rd88f6281Sheevaplug_400db_uart.bin” found as per the Installer README at http://plugcomputer.org/index.php/us/resources/downloads?func=select&id=6 o The “u-boot-rd88f6281Sheevaplug.bin” found at http://plugcomputer.org/index.php/us/resources/downloads?func=startdown&id=41 • I tried with and without a freshly formatted FAT Sandisk 2Go SD card inserted in the plug I also did the following many times • Disconnect/reconnect the mini usb cable • Use another mini usb cable • Power off / power on the plug • Reset the plug with the reset button on it (beside the sd card slot) • Reboot my pc • Various combination/sequence of the above Each attempt to “runme mmc” gave me the exact same results shown at the beginning, even when running it with no plug connected at all … So besides wondering why I can’t make it work, my questions are: 1. Should I run “runme mmc” with SD card inserted or not? 2. Should I set my “sheevaplug.cfg” file with (9e88 and 9e8f) or (0403 and 6010)? Currently my plugs shows (9e88 and 9e8f) in USBDeview. 3. What “uboot.bin” should I use and where exactly to download it from? (I mean should I find it under the exact same short simple name on the download page ? Or what exact file name am I looking for?) 4. Does both COM PORT must be set the same ? (More specifically for speed and Flow Control) 5. Should I also copy the “uboot-mmc-custom.txt” to the USB stick root ? (INSTALLER v1.0 procedure don’t ask for it, but I read it was necessary on previous version of the installer… ) 6. Does the plug need to be connected to my network router ? (INSTALLER v1.0 procedure don’t say so, but should I at this stage ?) 7. Anything else could be the problem ? Not a Linux user at all, and not used to these community forum, I did my best to help you helping me ;-) but feel free to educate me if I did something wrong. Otherwise, thank in advance for your help.

15	General Category / Application ideas and development Q/A / Re: CAN SHEEVA PLUG DO THIS ??	on: October 04, 2009, 11:04:28 AM
Hello adapted, I just recieved my plug Friday pm (2 days ago). Since then I am trying to succesfully complete the 'installer process' but with no luck so far. After many attemps and readings I am running out of hope ;-) I already posted a question about what I thought was my problem, (in the General Discussion \| Sheevaplug installer - version 1.0 discussion) but later discovered it was something else... I think... Anyhow, not to waste everyboy's time with mutiple questions and troubleshooting 1 step at a time, I am now trying to prepare a summary of my various attemps, findings, combination of options I tried, my set up, etc... Hopefully this could be usefull to someone more knowledgeable than I am to pin point where my problem is. Being long at this kind of task, I hope to be able to post it late today on the Sheevaplug installer - version 1.0 discussion. Of course, feel free to send in any clue or solution :-) Otherwise, thanks again for your good advice, I will come back to it later for sure. In a nutshell, I plan to use a MyBook World edition at the remote end, and hack it to autmotically "publish" its IP and run rsync more or less as explained in this tutorial : http://mybookworld.wikidot.com/tutorial-setup-2mbwe-with-rsync-over-the-internet Have fun !

Pages: [1] 2