• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3
16  Hardware and U-Boot firmware / Hardware / Re: Fried SheevaPlug !!! on: June 24, 2010, 02:43:35 PM
I opened my sheevaplug and made some holes on the plastic case for the metal heat spreader to breathe but I found out that the heat is relatively high again especially in the summer hot days.
I think that the only way to keep the plug cooler is to replace the power supply with an external one.
Having in mind that many sheeva users have dead and melted power supplies and that generally heat is very bad for the life of chips, I 'm allready searching for a new 5V 3A (based on the sheevaplug specs) power supply.
17  Hardware and U-Boot firmware / Hardware / Re: Fried SheevaPlug !!! on: June 09, 2010, 12:43:24 PM
You don't have to be a rocket scientist to know that the excess heat is making the life of electronic devices shorter
I have some heat problems with my sheevaplug (especially the summer period) and I was thinking opening a few holes on the plastic case like you did, or adding some sort of extra passive heat sink.
Are those holes working? and making the device cooler? measuring the temperature of the plug with the holes covered or opened?
18  Linux Stuff / General Linux questions / Re: Which Debian distro: Lenny or squeeze? on: May 08, 2010, 11:03:38 AM
I 'm running squeeze for some months now with no problems at all
19  General Category / Application ideas and development Q/A / Re: Remote access over NAT and firewall on: April 24, 2010, 12:17:05 PM
I'm using ssh and X for lan remote acces and from work I'm connecting to tightVNCserver running on the plug with  tightvnc portable viewer.
If you have windows add to all those the swiss knife putty and connect to the plug with it through ssh, X or VNC tunneling to secure the remote acces.
You can also take the faster NX road but it's not recommended to noobs.
You can find a lot of information in the forum but you can also have a look at this page -->
http://www.computingplugs.com/index.php/Installing_X11
20  General Category / Success stories / Re: Transmission 1.80 released! Installed on my 9.04 plug on: February 20, 2010, 04:46:20 AM
With Debian, when I start or stop transmission-daemon "sudo /etc/init.d/transmission-daemon stop" I get this error/warning ...
Stopping bittorrent client transmission-daemon...
start-stop-daemon: warning: this system is not able to track process names
longer than 15 characters, please use --exec instead of --name.

Obviously it speaks for transmission-daemon that has more than 15 characters.

Any idea?
21  General Category / Success stories / Re: Managing a USB hard drive on the Plug on: February 17, 2010, 03:58:44 PM
To restamp
The script must be placed before or after cryptdisks ?
I'm asking that because debian has the files inside /etc/rcS.d/ in a different order that ubuntu has them.
22  General Category / Success stories / Re: Managing a USB hard drive on the Plug on: February 15, 2010, 03:37:12 PM
I have a similar problem with usb disk that if I mount it or run mount -a it's working fine,
but when I reboot It's prompting me with a recover shell to run fsck and only usb serial terminal access
Linking restamp's script ../init.d/wait4usbdisks /etc/rcS.d/S25wait4usbdisks, means that checkfs.sh has a greater value, S26...,S27...,etc
Given that I boot Debian from sdcard and my :~$ ls /etc/rcS.d :
Code:
S01mountkernfs.sh -> ../init.d/mountkernfs.sh
S02udev -> ../init.d/udev
S03mountdevsubfs.sh -> ../init.d/mountdevsubfs.sh
S04bootlogd -> ../init.d/bootlogd
S05hostname.sh -> ../init.d/hostname.sh
S05hwclockfirst.sh -> ../init.d/hwclockfirst.sh
S06checkroot.sh -> ../init.d/checkroot.sh
S07cryptdisks-early -> ../init.d/cryptdisks-early
S08cryptdisks -> ../init.d/cryptdisks
S09hwclock.sh -> ../init.d/hwclock.sh
S09ifupdown-clean -> ../init.d/ifupdown-clean
S09module-init-tools -> ../init.d/module-init-tools
S09mtab.sh -> ../init.d/mtab.sh
S09udev-mtab -> ../init.d/udev-mtab
S10checkfs.sh -> ../init.d/checkfs.sh
S11ifupdown -> ../init.d/ifupdown
S11mountall.sh -> ../init.d/mountall.sh
S12mountall-bootclean.sh -> ../init.d/mountall-bootclean.sh
S13mountoverflowtmp -> ../init.d/mountoverflowtmp
S14networking -> ../init.d/networking
S14procps -> ../init.d/procps
S14x11-common -> ../init.d/x11-common
S15mountnfs.sh -> ../init.d/mountnfs.sh
S16mountnfs-bootclean.sh -> ../init.d/mountnfs-bootclean.sh
S17bootmisc.sh -> ../init.d/bootmisc.sh
S17screen-cleanup -> ../init.d/screen-cleanup
S17urandom -> ../init.d/urandom
S18stop-bootlogd-single -> ../init.d/stop-bootlogd-single
For the script to run before checkfs.sh (as stated on the thread) in my case I must give it a number:
/etc/rcS.d/S09wait4usbdisks
because /init.d/checkfs.sh has number S10checkfs.sh ?
23  General Category / Success stories / Re: Transmission 1.80 released! Installed on my 9.04 plug on: February 14, 2010, 12:51:19 PM
I build transmission 1.83, with disable-gtk  and I couldn't believe it that it took ~420 MB (with all the required packages to build it, the downloaded tar and the installed daemon)
WTF?
All those MB to get torrent support and after that I must install something else to see what i'm downloading ratios etc...
I must admit that windows utorrent was the best torrent client with under 300 kB file size (I think last year was under 200 kB) and with all the bells and whistles.
Transmission sux a lotta! or not?

Edit: What is the recommended add-on to control the most out of transmission on the plug? 
24  Hardware and U-Boot firmware / U-Boot stuff / Re: Downgrade ext3 to ext2 on: February 13, 2010, 04:15:16 AM
Fortune favors the brave so I decided to proceed with the sd card conversion from ext3 to ext2.
I have a multiboot setup on my plug so I've got the backup nand boot to mess up with the sdcard.
So I removed the sdcard and booted from internal nand and inserted again the sdcard in th slot.
Mounted the 2nd partition (mmcblk0p2 with the rootfs "/" ) and check it out
Code:
user@debian:~$ sudo mount /dev/mmcblk0p2 /mnt/sdp2
user@debian:~$ df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
tmpfs        tmpfs      256740         0    256740   0% /lib/init/rw
udev         tmpfs       10240       144     10096   2% /dev
tmpfs        tmpfs      256740         4    256736   1% /dev/shm
rootfs      rootfs      471664    147828    318996  32% /
/dev/mmcblk0p2
              ext3     7732856    479552   6860492   7% /mnt/sdp2

it's ext3!
unmounted it and run " sudo tune2fs -O ^has_journal /dev/mmcblk0p2" to get rid of the journal
and after that "sudo fsck -f /dev/mmcblk0p2" to check things out,
mounted again to check the fstype = ext2
and rebooted from the sdcard...cross fingers...
Code:
user@debian:~$ sudo fdisk -l

Disk /dev/mmcblk0: 8048 MB, 8048869376 bytes
4 heads, 16 sectors/track, 245632 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0xf3bf8b45

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1               1         123        3928   83  Linux
/dev/mmcblk0p2             124      245632     7856288   83  Linux
user@debian:~$ sudo tune2fs -O ^has_journal /dev/mmcblk0p2
tune2fs 1.41.9 (22-Aug-2009)
user@debian:~$ sudo fsck -f /dev/mmcblk0p2
fsck from util-linux-ng 2.16.2
e2fsck 1.41.9 (22-Aug-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
sheevaplug-rootf: 11749/491520 files (0.6% non-contiguous), 117945/1964072 blocks
user@debian:~$ sudo mount /dev/mmcblk0p2 /mnt/sdp2
user@debian:~$ df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
tmpfs        tmpfs      256740         0    256740   0% /lib/init/rw
udev         tmpfs       10240       144     10096   2% /dev
tmpfs        tmpfs      256740         4    256736   1% /dev/shm
rootfs      rootfs      471664    157716    309112  34% /
/dev/mmcblk0p2
              ext2     7732856    348348   6991696   5% /mnt/sdp2
user@debian:~$ sudo shutdown -r now
The plug is working fine booting from the ext2 converted sdcard.
Edit: My"dmesg" gives me "VFS: Mounted root (ext2 filesystem) on device 179:2."
25  Hardware and U-Boot firmware / U-Boot stuff / Re: Downgrade ext3 to ext2 on: February 12, 2010, 06:58:24 AM
So has anybody done it?
Convert sucessfully the rootfs partition of an sdcard from ext3 to ext2?

I understood the instructions in the link you provided as a method to convert a root file system, not the root directory. The problem with the root file system is that you can't run tune2fs while it's mounted so you have to boot from a CD, or use an initramfs if it contains the required tools. Might be wrong, though -- I only glanced at the page for a few seconds.
Actually the case that the article gives as an example is exactly the same as with the plug booting from an sdcard with two partitions, one with the kernel uImage and another partition with the rootfs.

"Back-Converting the root directory
The root directory is a challenge for a number of reasons. First, it must be mounted for the system to run, but it must be unmounted to run the e2fsck command. Also, different distros behave different ways. The mkinitrd command varies widely between distros. ...
We'll assume that /dev/hda1 is /boot, while /dev/hda2 is the root directory (/)."


I'm little confused with the procedure involving the use of initrd, do I have to use initrid with debian on the plug to change from ext3 to ext2?

26  Hardware and U-Boot firmware / U-Boot stuff / Re: Downgrade ext3 to ext2 on: February 11, 2010, 02:22:04 PM
Remove the journal:
tune2fs -O ^has_journal /dev/XXXX

Edit /etc/fstab and change ext3 to ext2

and: fsck -f /dev/XXXX
afterwards to be sure.
I want to mount the mmcblk0p2 (rootfs sdcard partition) as ext2 first to check things out on the safe side, and latter  kill the journal.
Has anybody done it sucessfully on the plug, I mean to downgrade fromext3 to ext2?
I'm asking that because I saw an old article -->http://www.troubleshooters.com/linux/ext2toext3.htm#_three2two
has a very complicated procedure Back-Converting the root directory
Are all those valid or this is an obsolete information?
Meanwhile I was thinking of staying with ext3 and just tweak/reduce the writes on the sd card with some tricks described here--> http://www.earth.org.uk/note-on-SheevaPlug-setup.html#storage

27  Hardware and U-Boot firmware / U-Boot stuff / Downgrade ext3 to ext2 on: February 05, 2010, 03:44:15 PM
I boot debian from sd card with two partitions (used the installer) one with the kernel uImage ext2 formated, and the second with rootfs ext3 formated.
Now I want to mount the second partition as ext2 and maybe latter, kill the journal,
do I have to give some extra bootargs to u-boot or a permanent entry in the sd card's fstab will do the job?
By the way how can I see which partition is ext2 or ext3 from sd card or a usb drive with 2 partitions axt2 and ext3?
28  Linux Stuff / Kernel / Re: 2.6.32.6 new release on: February 02, 2010, 02:53:49 PM
Finally found a simple solution.
I mounted the first partition of the sd card
Code:
debian:~# mount /dev/mmcblk0p1 /mnt/sdcard
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
debian:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 251M     0  251M   0% /lib/init/rw
udev                   10M  120K  9.9M   2% /dev
tmpfs                 251M  4.0K  251M   1% /dev/shm
rootfs                7.4G  360M  6.7G   6% /
/dev/mmcblk0p1        3.8M  2.8M  807K  78% /mnt/sdcard
debian:~# ls -l /mnt/sdcard
total 2780
drwx------ 2 root root   12288 Jan 30 00:37 lost+found
-rw-r--r-- 1 root root 2821988 Jan 30 13:16 uImage
It was only 4 MB big and the kernel uImage inside.
My new /boot/sheeva-2.6.32.6-uImage was as you said in the other partition
So I did :
Copy/backup the old uImage as  last-working-2.6.30.2uImage
debian:~# cp -ax /mnt/sdcard/uImage /home/last-working-2.6.30.2uImage
delete the old uImage from the 1st partition
debian:~# rm -fr /mnt/sdcard/uImage
copy my new sheeva-2.6.32.6-uImage to the 1st partition as uImage
debian:~# cp -ax /boot/sheeva-2.6.32.6-uImage /mnt/sdcard/uImage
Restart
debian:~# shutdown -r now
And ...voila!
Code:
Last login: Sat Jan 30 23:33:51 EET 2010 on ttyS0
Linux debian 2.6.32.6 #1 PREEMPT Mon Jan 25 13:14:06 MST 2010 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
debian:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 251M     0  251M   0% /lib/init/rw
udev                   10M  120K  9.9M   2% /dev
tmpfs                 251M  4.0K  251M   1% /dev/shm
rootfs                7.4G  360M  6.7G   6% /
debian:~# mount /dev/mmcblk0p1 /mnt/sdcard
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
debian:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 251M     0  251M   0% /lib/init/rw
udev                   10M  120K  9.9M   2% /dev
tmpfs                 251M  4.0K  251M   1% /dev/shm
rootfs                7.4G  360M  6.7G   6% /
/dev/mmcblk0p1        3.8M  2.8M  807K  78% /mnt/sdcard
debian:~# ls -l /mnt/sdcard
total 2780
drwx------ 2 root root   12288 Jan 30 00:37 lost+found
-rw-r--r-- 1 root root 2821988 Jan 30 13:16 uImage
I don't know if I used the correct options on the copy process (correct me if i'm wrong) but the copied new uImage has at least the same permissions as the old one and some days now it's working fine.
Thank you for the info pingtoo...
PS.Some dates might be wrong because I didn't took all the snapshots the exact time I was doing the above and they are there just to explain the process.
29  Linux Stuff / Kernel / Re: 2.6.32.6 new release on: January 30, 2010, 11:41:43 AM
So is there a way to move or create the new sheeva-2.6.32.6-uImage to the first partition of the sdcard somehow or I must try the new u-boot 3.4.27: u-boot-rd88f6281Sheevaplug_400db_nand.bin-pingtoo-patch.01 with your patch?
I'd better have to move the new sheeva-2.6.32.6-uImage to the first partition because the second solution (updating the u-boot) maybe will bring other problems.
30  Linux Stuff / Kernel / Re: 2.6.32.6 new release on: January 30, 2010, 05:46:13 AM
First of all the same sd card with 8GB i had for the last 3 months with only one partition with the same uboot "U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19"  kernel 2.6.30.2 and the default ubuntu 9.04 and never had any problem multibooting from nand and mmc (sd card) , and this time I installed debian with new kernel but the same u-boot I can't boot from mmc.
That's why I think the problem is with the new kernel.
Despite all this I followed your advice and used the installer option "sudo php runme.php mmc" and succesfully created 2 partitions on sd card and installed debian with the installer's kernel 2.6.30.2
Code:
debian:~# uname -a
Linux debian 2.6.30.2 #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009 armv5tel GNU/Linux
debian:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 251M     0  251M   0% /lib/init/rw
udev                   10M  120K  9.9M   2% /dev
tmpfs                 251M  4.0K  251M   1% /dev/shm
rootfs                7.4G  357M  6.7G   5% /
debian:~# fdisk -l

Disk /dev/mmcblk0: 8048 MB, 8048869376 bytes
4 heads, 16 sectors/track, 245632 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk identifier: 0xd2dcad3a

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1               1         123        3928   83  Linux
/dev/mmcblk0p2             124      245632     7856288   83  Linux
debian:~#
After that I downloaded README-2.6.32.6 and succesfully created a new sheeva-2.6.32.6-uImage
Code:
debian:/home#./README-2.6.32.6 --rootkernel
Downloading files
--2010-01-30 12:22:01--  http://sheeva.with-linux.com/sheeva/2.6.32.6/sheeva-2.6.32.6-Modules.tar.gz
Resolving sheeva.with-linux.com... 216.146.103.100
...
...
Saving to: `sheeva-2.6.32.6-uImage.md5'
100%[======================================>] 57          --.-K/s   in 0s
2010-01-30 12:24:14 (1.92 MB/s) - `sheeva-2.6.32.6-uImage.md5' saved [57/57]
Extracting modules
Writing kernel to /boot
****************************************************************
 update your bootcmd to load sheeva-2.6.32.6-uImage
 or use a symlink from /boot/sheeva-2.6.32.6-uImage to /boot/uImage
****************************************************************
debian:/home#
debian:/# ls -l /boot
total 2760
-rw-r--r-- 1 root root 2821988 Jan 30 13:16 sheeva-2.6.32.6-uImage
Then I changed the:
 setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000'
to:
setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /boot/sheeva-2.6.32.6-uImage; bootm 0x00800000'
Cross fingers reset:
Code:
Hit any key to stop autoboot:  0
SDHC found. Card desciption is:
Manufacturer:       0x27, OEM "PH"
Product name:       "SD08G", revision 2.0
Serial number:      2953843753
Manufacturing date: 8/2009
CRC:                0x00, b0 = 0

** Unable to read "/boot/sheeva-2.6.32.6-uImage" from mmc 0:1 **
## Booting image at 00800000 ...
[b]Bad Magic Number[/b]
Marvell>>
changed back the :
setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /boot/sheeva-2.6.32.6-uImage; bootm 0x00800000'
to:
setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000'
the plug boots with the old /uImage
Code:
Hit any key to stop autoboot:  0
SDHC found. Card desciption is:
Manufacturer:       0x27, OEM "PH"
Product name:       "SD08G", revision 2.0
Serial number:      2953843753
Manufacturing date: 8/2009
CRC:                0x00, b0 = 0

2620504 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2620440 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.2 (kelly@speedy) (gcc version 4.2.1) #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009
...
...
Last login: Sat Jan 30 13:37:48 EET 2010 on ttyS0
Linux debian 2.6.30.2 #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
debian:~# uname -a
Linux debian 2.6.30.2 #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009 armv5tel GNU/Linux
debian:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 251M     0  251M   0% /lib/init/rw
udev                   10M  120K  9.9M   2% /dev
tmpfs                 251M  4.0K  251M   1% /dev/shm
rootfs                7.4G  357M  6.7G   5% /
debian:~#
Now I have two uImage, /uImage and /boot/sheeva-2.6.32.6-uImage, and I can only boot from the first and not the second updated one.
WTF?
I'm a total confused linux noob...
 
Pages: 1 [2] 3