Maybe you can consider splitting SD card image into individual
partitions using DD. You can use fdisk on image file to find
partitions starts and sizes (in extended mode). This values are in
512B sectors. Then simply use dd -skip <sectors> -bs=512
count=<partition size> on image to separate tmen into individual
files.
Check with mount -o loop
Also extrast master boot record (first 446 bytes from beggining)
Then use fdisk to create fresh sd card (with corect geomety) and dd
bootloader, kernel image, initrd.
mkfs fresh root partition and use tar -p to copy original root into it.
This way you have fresh SD card with minimal legacy from origilan
image (and no geomettry problems). But maybe simple dd+resize+fdisk is
fine ...
(I posted more detailed instruction few days ago for TS7400 DS card)
Petr
On Tue, Sep 8, 2009 at 21:28, Matthew Minuti<> wrote:
>
>
> On Sun, 2009-09-06 at 04:12 +0000, awolven wrote:
>>
>> --- In "matt.minuti" <> wrote:
>> >
>> > Hi there!
>> >
>> > After following some ts7300 instructions I found on this mailing
>> list, I managed to write this image to and SD card and expand the root
>> partition to about 1.5gb.
>>
>> ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7200-linux/binaries/ts-images/512mbsd-7400-linux26-lenny-eabi.dd.bz2
>> >
>> > The system almost worked, I had to fix the rc scripts loading
>> hwclock modules because for some strange reason the defaults weren't
>> working.
>> >
>> > All that's set now, and the system seems to run reliably. I set a
>> root password, and can log in and out fine. However, attempting a
>> login via SSH triggers an immediate password expiration and boots me
>> out of the SSH connection. Via serial, on next login, I need to reset
>> my password.
>> >
>> > How can I make my password persistent? It doesn't seem to hold no
>> matter what I do, and SSH is very necessary for my application.
>> >
>> > Thanks,
>> > ~Matt
>> >
>>
>> Hi Matt.
>>
>> I don't have a solution to your problem, but you have mentioned a few
>> things that have provoked my curiosity.
>>
>> The information that you have given seems to imply that:
>> a.) There is a 2.6 kernel in that image (duh, right?)
>> b.) That kernel runs on the ts-7260 as well as the 7400
>> c.) That kernel has support for sdcards on the 7260 (either a module
>> or built in)
>>
>> If so, that would be pretty close to what I need. In case I'm missing
>> some obvious documentation somewhere, I would suspect then that you
>> have either written the kernel to the 7260 flash or you tftp it or
>> similar using redboot. (if you're using redboot.) If the sd driver is
>> a module, you leapfrog into the the lenny rootfs using an initrd, or
>> perhaps if the sdcard support is built in (better) then you just boot
>> to the lenny rootfs from the kernel. Is this the case?
>>
>> As far as it goes for your original question I can only guess.
>> Have you tried creating a regular user account and instead of ssh'ing
>> into your 7260 and logging in as root, try logging in as the regular
>> user?
>> If that works without causing your problem you may be able to then "su
>> root" after you are ssh'ed in to the machine and do what you want.
>>
>> I seem to want to do everything the hard way. I compiled a 2.6 kernel
>> using emdebian crosstools. From a host linux, I used debootstrap to
>> create a lenny/armel root file system on a usb stick. Using another
>> linux filesystem (sarge from ftp.embeddedarm.com) and the new kernel,
>> but with oabi-compat, I booted to sarge, plugged in the lenny usb
>> stick, chroot'ed to it and ran /debootstrap/debootstrap
>> --second-stage. Then I tried to boot to the new lenny. It didn't work.
>> What I realized was that debootstrap lenny/armel didn't install udev
>> and couldn't use /dev/ttyAM0 correctly. So I backtracked to the chroot
>> environment and did apt-get install udev. Of course, there were other
>> details like having to edit /etc/inittab to use the tty correctly, and
>> also, udev made my system think it was grooving back in 1970. I
>> changed the udev rules file to point to rtc1 instead of rtc0 and that
>> fixed that icky issue. Basically, it works. It runs "Motion" and the
>> Logitech camera nicely, but unfortunately I don't have sdcard support!
>> So I have this stinking usb stick sticking out the back, which is no
>> good for field use. (not that I am close to field use even remotely)
>>
>> So am I to go home from work and realize that I could have used that
>> image?? It seems I would just have to compile my own uvcvideo.ko for
>> that kernel. (which may or may not be difficult to get one that loads)
>>
>> I wonder if there is source available for that kernel too. Probably,
>> right?
>>
>> -AKW
>
> I solved my problem by jumping JP7 to enable 5v on the board. I'd like
> to note that this is opposite of what the manual says. Enabling 5v
> allowed the RTC to work properly as well, without my hackish scripts.
>
> I went through the hard way too. I never got to the point of trying
> emdebian (although it looks great!), and managed to stumble onto some
> information which led me to believe that the 7400 images work for the
> 7260.
>
> I have the rough basics on how to get a sane setup documented here:
> http://nuclear.unh.edu/wiki/index.php?title=Setting_up_an_SD_card_to_boot_from
>
> It's really intended as an internal document, but this mailing list has
> been a great help and it's easier for to post a link than to make a
> generic guide.
>
> Let me know if it works for you!
>
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|