Here's the log from serial console: Hit any key to stop autoboot: 0 Marvell>> setenv mtdparts 'mtdparts=spi0.0:0x7f000@0(uboot),0x1000@0x7f000(u-boo t-env)' Marvell>> setenv set_bootargs_usb 'setenv bootargs console=ttyS0,115200 root=LABby mikeh49 - Debian
OK, I'll get the boot log from serial. Is that right? Or, I can do it over while running the 5.2.9 kernel and 4.12 filesystem that is now booted.by mikeh49 - Debian
It is now working. I set up the USB on the M300 running the stock kernel and OS. I ran the dpkg command from the /tmp/usb/boot directory (/tmp/usb was the mount point of the USB) and it put the initramfs file in the boot directory of the M300 filesystem and the kernel modules in the /lib/modules directory of the M300 filesystem also. I'll look into dpkg to see if the install directory canby mikeh49 - Debian
Thanks, I may not have run the dpkg, I'll go back and review. I've been having linux and windows box problems, so it's been messy. Hybrid is 4.12 filesystem with 5.2.9 kernel. BTW, what do you guys use for this kind of work - Linux box using Terminal, Windows with Putty, or some way to use LInux with root privileges from a GUI? Lots of typing or copying and pasting without aby mikeh49 - Debian
I'm trying to install the new kernel and ran into a problem. First, i"m trying to install the 5.2.9 kernel on the usb with the 4.12.2 kernel and filesystem that was first used on the M300 last year. Is that a mistake and I should Install the 5.2.9 filesystem and kernel, and then update to this latest kernel? The problem with my "hybrid" system is that there is no initramfs-by mikeh49 - Debian
An epoxy bead around the connector body sounds like a good idea. Wish I'd thought of that when I had it apart.by mikeh49 - Debian
I missed Step 2 and in my search I only found your post that deleted the 2 udev files (a couple of posts above the Step 2 post). After looking at Step 2, and with what I now know, I think all you need to do is comment the line in the persistent-net rules file that contains the MAC address of the "donor". A new line is then generated with the MAC of the new box. In my case, theby mikeh49 - Debian
I have a Pogo Mobile (Kirkwood) running Bohdi's Debian kernel and file system (4.4) as a streaming player that works very well. It took a fair amount of time to get the ALSA sound system installed and working with a USB DAC and the Squeezelite player client. I wanted to set up a Pogo E02 the same so I installed the file system from the Mobile backup onto a new USB stick. It didn't booby mikeh49 - Debian
Not Debian but I thought I would share an experience with a Pogo Plug power connector. This is for E02, V3 but not Mobile or V4, i.e. for plugs with a 120 V cord connected to the box. One of my V3s would not boot and the power connector felt loose when inserting the cord. So I opened the case to investigate and found one of the pins of the cord connector had a loose solder connection; theby mikeh49 - Debian
Good to hear you plan to get back to this. I'd like to get mine going to boot from the internal flash card, Your file system from last year works fine from USB, but it would be nice to have the USB ports available. I'll follow.by mikeh49 - Debian
No problem, I don't have any time to work on the M300 for the next month at least. I'll check in with you at the end of the mont. If you had the environment for booting from USB without serial by the end of the month, I have a few days them. Otherwise, I will be available in early December. Thanks for the help and info. I have 3 Pogos running for 2-3 years with zero issues.by mikeh49 - Debian
If you can determine the environment settings to boot from USB before SATA, then we could make these changes from the stock OS and boot without a serial console. That would be a good start. Then, could the existing stock OS be replaced by putting your kernel files (contents of /boot directory) in the boot partition of the flash drive and the rest of the file system in the second partition?by mikeh49 - Debian
No problem, I'm not in a hurry. Just so I understand, we cannot change the uboot environment variables even from root on the stock OS. Right? Thanks for your help.by mikeh49 - Debian
I have root access in serial to the stock OS and can see the envitronment with fw_printenv. I won't be able to work on this after today until the end of October, so perhaps we should just put it away for the time being. For your info, here is the environment from the stock OS: root@dellkaceM300:~# fw_printenv baudrate=115200 loads_echo=0 rootpath=/mnt/ARM_FS/ kernel2bootup=noby mikeh49 - Debian
Yes, internal flash drive same as renojim: Disk /dev/sda: 14.9 GiB, 16013852672 bytes, 31277056 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sda1 * 32 524287by mikeh49 - Debian
Looks like it works, especially after I added the missing / in front of dev ;) root@debian:~# fw_printenv baudrate=115200 loads_echo=0 rootpath=/mnt/ARM_FS/ kernel2bootup=no usiversion=kacemini-1.5 console=console=ttyS0,115200 mtdparts=spi_flash:0x7f000@0(uboot),0x1000@0x7f000(u-boot-env) CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=root=/dev/nfs rw bootargs_end=:::DB88FXby mikeh49 - Debian
Got a M300 and trying to get it working. I built the Debian 4.12 file system with the M300 DTS. I have serial working with the M300. When I interrupt the boot, I can enter the 2 setenv lines, but when I get to usb start, the system cannot find the USB with the filesystem. Marvell>> usb start (Re)start USB... USB: scanning bus for devices... 3 USB Device(s) found Waiting for sby mikeh49 - Debian
Is this M300 device worth getting as a general purpose "toy" to supercede a Pogo for example. The price is right ($20) and the quality looks great. Is the Debian and uboot situation pretty solid now since nothing on this thread since June. Thanks.by mikeh49 - Debian
Small, headless, more or less embedded linux is where I'm at. So I think we're set. I'll make the environment setting. Again, thanks. You do good things here!by mikeh49 - Debian
OK, worked this time. Thanks! I think perhaps I messed up the file names when I did the kernel commands. But, all good now. Is it important to upgrade the kernel from the 4.4.0 that came with the 4.4.0 filesystem? For the u-boot environment, from what I can tell, I'd only need to change the usb_rootfstype to ext3 (I changed the fstab entry as specified in the instructions, and I thby mikeh49 - Debian
Thanks Bodhi. I think I followed the instructions as you describe in appending the DTB for E02 to zimage, but I'll start over. I'm suspicious of the USB drive, so I'll try another. The instructions say to do the steps as "root". I'd doing it from Terminal on a Linux Mint box, so I think I just "login" using "su" and then should be root. Iby mikeh49 - Debian
I'm repurposing a Pogo E02 and would like to use the latest Debian FS. I built the FS using the embedded DTB (I think) and it would not boot. The Pogo has an older u-boot that I think is Jeff Doozan's work. Kernel and u-boot info: root@BIZ02:~# uname -a Linux BIZ02 2.6.39.4-vamp #8 PREEMPT Wed Jan 23 22:18:57 EST 2013 armv5tel GNU/Linux root@BIZ02:~# grep -a --null-data U-Bootby mikeh49 - Debian
If Bodhi's new u-boot and new kernel do not overwrite the PogoPlug firmware, then it is still there. If someone tells me how, I could probably get it, especially if I don't have to crack the case and use the serial connection. I think Bodhi will need to answer this.by mikeh49 - Debian
Thanks for the hints, I'll do some more searching. Routing rules have been mentioned, but I didn't fully understand and didn't get a definitive configuration. I'll look some more.by mikeh49 - Debian
Does anyone have a working wireless (preferably with the stock card, but other ideas good too) on the Pogo Pro that they could share? I did the setup from Qui's blog (known as grayman here) and I can access the wireless as long as the wired is connected (2 ip addresses assigned, one for wired and one for wireless). Twinclouds had a similar problem but apparently did not get a solution. Thby mikeh49 - Debian
Thanks, that's what I figured. Installed OK and now will start playing.by mikeh49 - Debian
I want to run a cron on the PogoPro to operate a USB relay. I have the relay working from the command line, but there is apparently no cron daemon or service running/available. Before I mess things up by trying to install something, I could use some info on how cron is setup in Bodhi's debian file system. I see there are cron.weekly and cron.daily entries in /etc, so I'm assuming somby mikeh49 - Debian
I'm preparing to update a Pogo P21 with the new u-boot to use the new kernel and Debian file system. The bad blocks check returns the following: /$ dmesg | grep -i 'bad' [ 1.710000] Scanning device for bad blocks [ 1.780000] Bad eraseblock 981 at 0x000007aa0000 [ 2.260000] UBI: number of bad PEBs: 1 [ 2.290000] UBI: number of PEBs reserved for bad PEBby mikeh49 - uBoot
Bodhi- A follow-up comment. Could you put the full/real URL of the kernel, filesystem, etc package into the post so we can get it easily with wget? It worked with the bit.ly link, but the filename was the arbitrary letters format, which might confuse folks. The tar did extract fine, though. Not a big problem, just a suggestion.by mikeh49 - Debian