• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3]
31  Linux Stuff / General Linux questions / Re: "UBI device does not have free logical eraseblocks"? on: June 01, 2011, 05:30:57 AM
Yes, I suspect those numbers are wrong, but at this point, this is Greek to me Undecided
32  Linux Stuff / General Linux questions / Re: "UBI device does not have free logical eraseblocks"? on: May 31, 2011, 06:57:24 AM
Since no size-related settings are required to call ubiattach, it looks like the Makefile is using wrong settings when compiling the root filesystem using mkfs.ubifs:
Code:
-m 2048 -e 204800 -c 1024 -d
33  Linux Stuff / General Linux questions / "UBI device does not have free logical eraseblocks"? on: May 31, 2011, 05:53:19 AM
Hello

I'm quite new to embedded Linux, and don't know how to compile a Ubifs root filesystem + Ubi volume so that it'll work on a 256MiB NAND flash with 248 MiB available in the second partition to hold the root filesystem.

Here's what I used:

On the workstation
Code:
# mkfs.ubifs -v --squash-uids -m 2048 -e 204800 -c 1024 -d ./romfs -D ./vendors/mfg/board/device_table-min.txt -o ./images/rootfs.ubifs

On the appliance
Code:
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00800000 00001000 "ROMfs"
mtd1: 00800000 00020000 "linux kernel(nand)"
mtd2: 0f800000 00020000 "file system(nand)"

# ubiattach /dev/ubi_ctrl -m 2
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: volume 0 ("rootfs") re-sized from 1626 to 1961 LEBs
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "file system(nand)"
UBI: MTD device size:            248 MiB
UBI: number of good PEBs:        1984
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 1984
UBI: number of PEBs reserved for bad PEB handling: 19
UBI: max/mean erase counter: 10/5
UBI: image sequence number: 364645537
mtd: Giving out device 3 to rootfs
UBI: background thread "ubi_bgt0d" started, PID 69
UBI device number 0, total 1984 LEBs (255983616 bytes, 244.1 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)

# mdev -s

# ubinfo /dev/ubi0 -a
ubi0:
Volumes count:                           1
Logical eraseblock size:                 129024
Total amount of logical eraseblocks:     1984 (255983616 bytes, 244.1 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  19
Current maximum erase counter value:     11
Minimum input/output unit size:          2048 bytes
Character device major/minor:            251:0
Present volumes:                         0

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        1961 LEBs (253016064 bytes, 241.3 MiB)
State:       OK
Name:        rootfs
Character device major/minor: 251:1

# ubimkvol /dev/ubi0 -N test --lebs=51
ubimkvol: error!: UBI device does not have free logical eraseblocks

Could someone tell me what numbers to use in mkfs.ubifs and ubimkvol so that I can proceed with "mount"?

Thank you.
34  Linux Stuff / Linux distributions / Re: Recommended distros to upgrade SheevaPlug? on: November 16, 2010, 06:01:23 AM
Thanks for the feedback.
35  Linux Stuff / Linux distributions / Recommended distros to upgrade SheevaPlug? on: November 10, 2010, 07:20:07 AM
Hello

I read the first post in this forum where it explains that it's not possible to upgrade the Ubuntu 9.04 that comes with the SheevaPlug to a more recent version of Ubuntu due to differences in compiling options.

As of November 2010, what are the recommended distributions to bring the SheevaPlug up to date?

Thank you.
36  General Category / General Discussion / Re: Network issue after upgrading on: July 04, 2010, 03:17:00 AM
Thank you for the help but... I'm still having the same issue :-/

1. After rebooting the SP, it waits for about 30 seconds at the line that says "eth0: link up, full duplex, speed 100 Mbps" before proceeding.

Here's what the default /etc/network/interfaces says:

Code:
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

2. I still cannot connect to the SP through SSH, even though SSHd is running and ifconfig looks right:

Code:
# netstat -nat
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:43:01:69:b7 
          inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0

# ping www.google.com
PING www.l.google.com (66.249.92.104) 56(84) bytes of data.
64 bytes from 66.249.92.104: icmp_seq=1 ttl=55 time=20.1 ms

What about those lines in dmesg?
Code:
#Do I really have to tell the kernel to use some static IP instead of letting the DHCP server hands one out?
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=[b]192.168.0.10:192.168.0.10:192.168.0.254:255.255.255.0[/b]:SheevaPlug:eth0:non

[...]

TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: link down
eth0: started

# I have no NIS server, nor do I use a boot/root server
IP-Config: Complete:
      device=eth0, addr=192.168.0.10, mask=255.255.255.0, gw=192.168.0.254,
     host=SheevaPlug, domain=, [b]nis-domain=(none),
     bootserver=192.168.0.10, rootserver=192.168.0.10[/b], rootpath=
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.

#Stuck 30 seconds here
eth0: link up, full duplex, speed 100 Mbps

Empty flash at 0x0bbc9abc ends at 0x0bbca000

3. The FATAL errors went away after typing the right "bootargs" env't variable in uBoot. Out of curiosity, I still ran "depmod -a", but Linux isn't happy:

Code:
# depmod -a
WARNING: Couldn't open directory /lib/modules/2.6.22.18: No such file or directory
FATAL: Could not open /lib/modules/2.6.22.18/modules.dep.temp for writing: No such file or directory

I guess updating Linux on the SP without reflashing the device with a whole new image causes collateral damages ;-)

Any idea appreciated.

Thank you.
37  General Category / General Discussion / Re: Network issue after upgrading on: June 30, 2010, 05:40:03 PM
Thank you for your help.

In (uBoot?), I updated the "bootargs" line to remove the trailing "init=/bin/bash", and let Linux boot up:

http://pastebin.com/SncMg7YQ

I highlighted problematic lines (187, 192, 199, 202).

1. For some reason, it stops at line 187 ("eth0: link up, full duplex, speed 100 Mbps") for about over 30 seconds, and then proceeds. Could it be some DNS or DHCP issue?

2. I still cannot connect from the workstation through SSH: Could it be related to what is on line 199 ("error: "net.ipv4.tcp_syncookies" is an unknown key")?

3. What about the FATAL errors ("Could not load /lib/modules/2.6.22.18/modules.dep")?

Thank you.
38  General Category / General Discussion / Network issue after upgrading on: June 30, 2010, 05:40:15 AM
Hello

Based on this article, I ran the following commands to upgrade the applications:

 1. apt-get update
 3. apt-get dist-upgrade
 5. apt-get autoremove
 7. Launch a new SSH connection to the device to make sure you can still connect
 8. reboot

After rebooting the SP, I can no longer connect through SSH Sad

So, following this article, I used the USB serial connection and typed the following commands, without understanding how to configure the IP part (192.168.0.10 = SP, 192.168.0.3 = Linux workstation, 192.168.0.254 = gw):

Code:
> setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=192.168.0.10:192.168.0.3:192.168.0.254:255.255.255.0:DB88FXX81:eth0:none init=/bin/bash
> boot

There seems to be an issue with how the network is configured:

Code:
eth0: link down
eth0: started
Sending DHCP requests .<5>eth0: link up, full duplex, speed 100 Mbps
..... timed out!
eth0: stopped
IP-Config: Reopening network devices...
eth0: link down
eth0: started
Sending DHCP requests .<5>eth0: link up, full duplex, speed 100 Mbps
., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.0.10
IP-Config: Complete:
      device=eth0, addr=192.168.0.10, mask=255.255.255.0, gw=192.168.0.254,
     host=DB88FXX81, domain=, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath=
md: Autodetecting RAID arrays.
[...]
Freeing init memory: 104K
root@DB88FXX81:/# ifconfig
Warning: cannot open /proc/net/dev (No such file or directory). Limited output.

FWIW, the LED on the hub shows that the SP is connected at 10Mbps, although the log says "eth0: link up, full duplex, speed 100 Mbps".

If someone's had the same issue, do you know what the problem is, and how to solve it?

Thank you.
39  Hardware and U-Boot firmware / Hardware / Re: Before ordering the Sheeva DevKit... on: November 13, 2009, 07:11:54 AM
Thanks. I'll check out NewIT also.

Changed the layout. Much easier to read ;-)
40  Hardware and U-Boot firmware / Hardware / Before ordering the Sheeva DevKit... on: November 12, 2009, 05:30:09 AM
Hello

I'd like to order a SheevaPlug to run a Freeswitch telephony server for SOHO users, but since I have no experience with this device, I'd like some feedback before placing an order:

1. I'm located in France. For those of you located in Europe, did you have good experience with  GlobalScaleTechnologies, or should I order it from another vendor?

2. Besides the SheevaPlug DevKit, are there other items recommdended, e. "OSGi + JVM Add-on for SheevaPlug Dev Kit on SD-Card", etc.?


Thank you.

PS: Is there a way to change the interface layout so that I can see what I type in the "Subject" line, instead of having black text over black background, the icons to send/cancel, etc?
Pages: 1 2 [3]