• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  Linux Stuff / Linux distributions / Re: update Globalscale Ubuntu to Squeeze on NAND on: January 28, 2013, 11:39:13 PM
Hello,

I add the initrd file in the google docs folder. You need to have it on your USB key if you want to do the actions describe in this post. Sorry for this miss.

Regards

2  Linux Stuff / Linux distributions / update Globalscale Ubuntu to Squeeze on NAND on: August 29, 2012, 11:48:22 PM
Hello,

because Ubuntu on Sheevaplug is not supported, I decided to update my Sheevaplug to Debian Squeeze, on the NAND. I use the restore procedure to do that. This method only works with Globalescale, Ionics has different rootfs ! This method also updates the Sheevaplug to the current last kernel, 3.4.5.

All needed files are available here : https://docs.google.com/folder/d/0BzksAE8XyQoAbG1yVjFHRW40SDQ/edit

prerequisite
------------

Your Sheevaplug need at least the Uboot 3.4.27. When you are in the Uboot prompt, and you enter the
command version, you may have this result:

Marvell>> version
U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27 - pingtoo patch.01

uboot update if needed
----------------------

- use the file provided here : uboot-3.4.27.bin
- put it on tftp server or USB key
- install it on your Sheevaplug from Uboot command
    from USB key
        usb start
        fatload usb 0:1 0x0800000 uboot-3.4.27.bin
        nand erase 0x0 0xa0000
        nand write 0x0800000 0x0 0xa0000
    from TFTP server
        set serverip 10.11.12.13
        set ipaddr 10.11.12.15
        tftpboot 0x0800000 uboot-3.4.27.bin
        nand erase 0x0 0xa0000
        nand write 0x0800000 0x0 0xa0000
- then, enter the command reset

sheevaplug update
-----------------

- only for Globalescale original sheevaplug
- you'll need a USB key in FAT or FAT32
- put on it's root these files : uImage, modules.tar.gz, rootfs.tar.gz
        these is a 3.4.5 Linux Kernel and Squeeze rootfs
- plug these USB key to your Sheevaplug
- reboot your sheevaplug, and go to Uboot prompt
- set this command in uboot
        setenv bootargs_console 'console=ttyS0,115200n8'
        setenv mtdpartitions 'mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)'
        setenv bootroot_nand 'ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs'
        setenv bootload_nand 'nand read.e 0x00800000 0x00100000 0x00400000'
        setenv nand_boot 'setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootroot_nand); run bootload_nand; bootm 0x00800000'
        setenv recover_ramdisk 'root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand'
        setenv recover1 'setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset'
        setenv recover2 'run recover3; setenv bootcmd run nand_boot; saveenv; run recover5'
        setenv recover3 'run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000'
        setenv recover4 'usb start; fatload usb 0:1 0x00800000 uImage; fatload usb 0:1 0x01100000 initrd'
        setenv recover5 'setenv bootargs $(bootargs_console) $(mtdpartitions) $(recover_ramdisk); bootm 0x00800000 0x01100000'
        setenv bootcmd 'run recover1'
        saveenv
        reset

after few minutes, and some restart, you'll have a UBIFS system, with Linux kernel 3.4.5 (currently
the last update in August 2012) with Squeeze Debian.
The root password is always : nosoup4u
The directories /tmp and /var/log are tmpfs system. You can check them by the command df:
        df
        Filesystem           1K-blocks      Used Available Use% Mounted on
        tmpfs                   256620         0    256620   0% /lib/init/rw
        udev                     10240       112     10128   2% /dev
        tmpfs                   256620         0    256620   0% /dev/shm
        rootfs                  472968    167008    301124  36% /
        tmpfs                   256620         0    256620   0% /tmp
        tmpfs                   256620        84    256536   1% /var/log
You can update the file /etc/fstab with this line (no set access time to file, to not write always on NAND)
        rootfs / rootfs rw,noatime,sync 0 0
If you have a proxy, you can create the file /etc/apt/apt.conf with these lines for example:
        Acquire::http::proxy "http://myproxy:1234/";
        Acquire::ftp::proxy "http://ftp://myproxy:1234/";
        Acquire::https::proxy "https://myproxy:1234/";
You can add softwares with apt-get command, but don't use the upgrade command. Because it wants to update
your kernel in 2.6.32 (August 2012), while you have a 3.4.5 kernel.

These updates will be done at your own risk. I decline all damages which can arrived during the
update.

long life to the sheevaplug
3  Linux Stuff / Linux distributions / Re: Debian Lenny unavailable on: August 29, 2012, 11:38:20 PM
Hello,

sorry for the late answer. I hope you found a solution. If not, perhaps you can use these commands:
apt-get clean
apt-get autoclean
apt-get update

Regards


4  Linux Stuff / Linux distributions / Re: Debian Lenny unavailable on: April 10, 2012, 11:17:46 PM
Hello

ok, I changed from Lenny to Squeeze by these actions under root user:

update /etc/apt/sources.list
     deb http://ftp.fr.debian.org/debian/ squeeze main contrib non-free
     deb-src http://ftp.fr.debian.org/debian/ squeeze main contrib non-free

update apt
    apt-get clean
    apt-get update

upgrade to new version
    apt-get dist-upgrade

be sure to have enough space to install new version.

After this update, dhcp configuration change. In Lenny, my dhclient.conf file was in /etc/dhcp3. In Squeeze, it is in /etc/dhcp.

Long live the Sheevaplug Shocked)
5  Linux Stuff / Linux distributions / Debian Lenny unavailable on: April 05, 2012, 12:08:16 AM

Hello,

I have some Ionics Sheevaplug computer, and I can't add package, because the command : apt-get update
generate error 404 not found for the Lenny package...

And when I go to the debian website, I can't found any reference to Lenny. There is now only stable and squeeze.

So, I update my sources.list and change all lenny reference to stable. And I comment volatile and Orion line. Now, I have only
these lines:


deb http://ftp.uk.debian.org/debian/ stable main
deb-src http://ftp.uk.debian.org/debian/ stable main

deb http://security.debian.org/ stable/updates main
deb-src http://security.debian.org/ stable/updates main

The apt-get update is working fine.

But I don't test the apt-get upgrade. Is someone had the same problem and try to update to this version.

I can see on internet some people who change lenny to squeeze. But I would prefer a stable version.

Thanks
6  Linux Stuff / General Linux questions / Re: Sheeva and Wifi on: November 18, 2010, 12:11:20 AM
Hi,

Here are the operations I done to work with a RTL8191 WIFI.


get from http://sheeva.with-linux.com/sheeva/2.6.36/ the uImage, the modules, the headers, the config file, the Linux sources, and the patches.
- Extract the sources package
- go to this directory : cd linux-2.6.36
- clean it : make mrproper
- create .config file from sheeva config file : cp /xxx/sheeva-2.6.36.config .config
- apply patches
        patch -p1 < /xxx/mvsdio-2.patch
        patch -p1 < /xxx/mvsdio-1-2.6.30.patch
        patch -p1 < /xxx/linux-2.6.36-88e1121.patch
        patch -p1 < /xxx/0003-Initial-defconfig.patch
        patch -p1 < /xxx/0002-Driver-for-Marvell-Libertas-8688-SDIO-micro-AP-suppo-2.6.35.patch
- update .config file to add new driver
        search CONFIG_RTL8192E, and add the line below
                CONFIG_R8712U=m
- update ./drivers/staging/Makefile
        search CONFIG_RTL8192E, and add the line below
                obj-$(CONFIG_R8712U)            += rtl8712/
- get the last Linux source (in my case linux-2.6.37-rc2.tar.bz2). Extract it in temporary folder. Copy the directory drivers/staging/rtl8712 from this temporary directory to our current linux sources : linux-2.6.36/drivers/staging
- create all configuration files : make ARCH=arm menuconfig
- compile kernel : make ARCH=arm CROSS_COMPILE=/xxx/gcc/bin/arm-none-linux-gnueabi- uImage
- compile modules : make ARCH=arm CROSS_COMPILE=/xxx/gcc/bin/arm-none-linux-gnueabi- modules
- send ./drivers/staging/rtl8712/r8712u.ko to your SheevaPlug, and put it into /lib/modules/2.6.36/kernel/drivers/staging/rtl8712

At this point, We can try with new kernel without erasing flash. But this step can be passed.

Boot from tftp
        - connect to the SheevaPlug by using console from USB port
        - reboot it, and stop in Uboot
        - set serverip and ipaddr to get uImage from tftp
        - get uImage : tftpboot 0x800000 uImage
        - boot on it : bootm 0x800000

Update flash
        - connect to the SheevaPlug by using console from USB port
        - reboot it, and stop in Uboot
        - set serverip and ipaddr to get uImage from tftp
        - get uImage : tftpboot 0x800000 uImage
        - erase flash : nand erase clean 0x00100000 0x00400000
        - update flash : nand write.e 0x00800000 0x00100000 0x00400000

- go to /boot directory, and get the sheeva-2.6.36-System.map in it.
- generate new modules dependencies : depmod -eF /boot/sheeva-2.6.36-System.map 2.6.36
- reboot (if you haven't update flash, don't forget to get uImage a new time from tftpboot)

- update /etc/network/interfaces
        auto wlan0
        iface wlan0 inet dhcp
        wireless-essid bond
        wireless-key 000000000000000000b0b007
        wireless-mode managed

-------------------------------------------------------------------------------------------------
With the interfaces configuration, I haven't problem with RT73 and RTL8192. But it doesn't work with RTL8191 ! The command line haven't problem, but during the boot, the key is not ready. It seems that it starts slower ?

To resolve my problem, I currently add into interfaces a post-up command that check wlan interface. And if it isn't connected, launch iwconfig command after 10 seconds. And now, it's ok. But, if you have a better solution.

-------------------------------------------------------------------------------------------------
For information, the kernel.log file contains this informations for the 3 USB keys:
-------------------------------------------------------------------------------------------------

Nov 16 14:56:08 g-sheeva-ionics-4 kernel: usbcore: registered new interface driver rt73usb
Nov 16 14:56:08 g-sheeva-ionics-4 kernel: device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
Nov 16 14:56:08 g-sheeva-ionics-4 kernel: wlan0: authenticate with 00:18:e7:51:50:07 (try 1)
Nov 16 14:56:08 g-sheeva-ionics-4 kernel: wlan0: authenticated
Nov 16 14:56:08 g-sheeva-ionics-4 kernel: wlan0: associate with 00:18:e7:51:50:07 (try 1)
Nov 16 14:56:08 g-sheeva-ionics-4 kernel: wlan0: RX AssocResp from 00:18:e7:51:50:07 (capab=0x431 status=0 aid=2)
Nov 16 14:56:08 g-sheeva-ionics-4 kernel: wlan0: associated

Nov 16 14:58:58 g-sheeva-ionics-4 kernel: usbcore: registered new interface driver rtl8187
Nov 16 14:58:58 g-sheeva-ionics-4 kernel: device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
Nov 16 14:58:58 g-sheeva-ionics-4 kernel: eth0: link up, 100 Mb/s, full duplex, flow control disabled
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: wlan0: authenticate with 00:18:e7:51:50:07 (try 1)
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: NET: Registered protocol family 10
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: wlan0: authenticated
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: wlan0: associate with 00:18:e7:51:50:07 (try 1)
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: wlan0: associate with 00:18:e7:51:50:07 (try 2)
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: wlan0: RX AssocResp from 00:18:e7:51:50:07 (capab=0x431 status=0 aid=1)
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: wlan0: associated
Nov 16 14:58:59 g-sheeva-ionics-4 kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: module is from the staging directory, the quality is unknown, you have been warned.
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: DriverVersion: v7_0.20100831
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: register rtl8712_netdev_ops to netdev_ops
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: USB_SPEED_HIGH with 4 endpoints
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: Boot from EFUSE: Autoload OK
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: CustomerID = 0x0000
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: MAC Address from efuse = 00:19:70:1b:f0:07
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: usbcore: registered new interface driver r8712u
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: 1 RCR=0x153f00e
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: r8712u: 2 RCR=0x553f00e
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: eth0: link up, 100 Mb/s, full duplex, flow control disabled
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: NET: Registered protocol family 10
Nov 16 15:02:40 g-sheeva-ionics-4 kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready


Bob

7  Hardware and U-Boot firmware / Hardware / Re: Which "Plug" should I buy? on: November 17, 2010, 11:52:54 PM
Hi,

currently, I work with Ionics Nimbus 100 and Globalscale SheevaPlug.

Nimbus 100 is smaller than Globalscale. You can manage three Leds by default (red, green, blue), and it's a Debian distribution. If you want to use sources from plugcomputer, you'll have to adjust the compilation (change sheevaplug-setup.c before compilation for example). To access to console, you'll have to plug a provided extention to the Jtag bus.

Globalscale doesn't allow the three Leds management (except if you update your kernel, explain in this forum). It is an Ubuntu distribution. All sources provided by plugcomputer are compatible with this SheevaPlug. Currently, last kernel are tested on this platform, I think. There is a SD card slot and direct access to console with a mini USB cable.

I had to manage WIFI USB key, on both platform. And I upgraded my Nimbus 100 with new kernel and Ubuntu distribution to work fine.

Bob

8  Linux Stuff / General Linux questions / Re: Sheeva and Wifi on: November 15, 2010, 06:01:33 AM

Hi,

I found how to have a RT73 driver ok. The native driver is correct in the module 2.6.36, it's just that there is no rt73.bin file. So, I get this file from my Ubuntu server in /lib/firmware/rt73.bin and put it in my SheevaPlug in /lib/firmware/rt73.bin. Then, I restart my SheevaPlug, and configure my Wifi network with iwconfig, and all is fine Wink

Thanks very much for all your help,

Now, I'm trying with a RTL8191, which doesn't work like the RTL8192 !

Regards

Bob
9  Linux Stuff / General Linux questions / Re: Sheeva and Wifi on: November 15, 2010, 12:16:49 AM
Hi,

yes I have /sbin in my PATH. And I can't find the iwconfig with the find command from /...

So, I decide to make my own kernel from kernel.org, with patch provided by plugcomputer website, and the specific sheevaplug-setup.c provided by Ionics. Then, I'll also change the rootfs with that provided by Globalscale, ubuntu 9.0.4. I have now a Ionics with Kernel 2.6.36

So, now, the RTL8192 is running fine  Cheesy
And now, I'll try to understand why rt73 isn't running, by using the wiki site recommended by guidol.

Thanks for your help

Bob
10  Hardware and U-Boot firmware / Hardware / three leds available on SheevaPlug on: November 10, 2010, 03:09:24 AM
Hi,

I wanted to manage the three Led on Globalscale SheevaPlug, like on Ionics. And I did it Smiley

First of all, I get the last kernel (2.6.36) sources, and its patch. I unzip it, apply all the patch, and copy config file into .config.
The update the sheevaplug-setup.c in the directory linux-2.6.36/arch/arm/mach-kirkwood by my update, provided here. Then, I cross compile the kernel. And I boot my sheevaPlug with this new kernel. And I can manage 3 Leds (green, blue, red), available in the directory /sys/devices/platform/leds-gpio/leds.

There are led1, led2 and led3. But if you change name into the file sheevaplug-setup.c, you can name them green, blue, red. In fact, I just had in this file the led 2 and 3 and their bind GPIO.

You just have use echo command to change their state

echo 0 > /sys/devices/platform/leds-gpio/leds/led1/brightness
echo 255 > /sys/devices/platform/leds-gpio/leds/led1/brightness

Have fun  Cheesy

Bob
11  Linux Stuff / General Linux questions / Re: Sheeva and Wifi on: November 09, 2010, 10:20:13 PM

Hi,

don't worry, I'm ready to test all possibilities.

So, I found a big difference between Globascale and Ionics SheevaPlug. Globalscale use an Ubuntu, and Ionics a Debian.

When I loaded wireless-tools on my Ionics, I haven't the command iwconfig Huh

So, yesterday, I overwrote all my Ionics with the standard Ubuntu package which is comming from plugcomputer. And the RTL8192 is running fine Smiley

But, I loose another functionnality, of course, because the kernel or the rootfs isn't completely compatible with this hard. I can't manage the 3 leds, which are available with the Debian distribution. And I suppose threre is another hard mechanism which won't work....

So, now, I'll try to compare the kernel configuration (if I found this file for Ionics). Because the /sys directory doesn't generate the same structure, and I suppose it depends of the kernel configuration.

I found also why the RT73 doesn't work on the Globalscale with the kernel 2.6.36. The driver exist in driver/net/wireless natively, but when I plug this component, I have an error : don't find rt73.bin in the syslog. So, I suppose the driver is not correct ? I'll look for older kernel version to check if there is the same problem today...

Regards

Bob

12  Linux Stuff / General Linux questions / Re: Sheeva and Wifi on: November 09, 2010, 05:34:09 AM
Hi,

finally, I found it on backport :
   deb http://backports.debian.org/debian-backports lenny-backports main non-free

But, if I ask about this package when it is installed, it tell me:

# dpkg -s firmware-realtek

Package: firmware-realtek
Status: install ok installed
Priority: optional
Section: non-free/kernel
Installed-Size: 184
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: all
Source: firmware-nonfree
Version: 0.24~bpo50+1
Suggests: initramfs-tools, linux-image
Description: Binary firmware for Realtek RTL8192 wireless cards
 This package contains the binary firmware for wireless network cards with
 the RTL8192 chips supported by the rtl8192e and rtl8192su drivers.
 .
 Contents:
  * Realtek RTL8192E boot code (RTL8192E/boot.img)
  * Realtek RTL8192E init data (RTL8192E/data.img)
  * Realtek RTL8192E main code (RTL8192E/main.img)
  * Realtek RTL8192SU firmware, version 703E (RTL8192SU/rtl8192sfw.bin)
Homepage: http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git


So, it isn't use with may RTL8187 wifi dongle.

Bob
13  Linux Stuff / General Linux questions / Re: Sheeva and Wifi on: November 09, 2010, 05:03:19 AM
Hi,

no I haven't install it. But I'm trying, but not found a source list available for Sheeva.

Do you know which URL to add to the sources.list file to have access to this package ?

Thanks

Regards

Bob
14  Linux Stuff / General Linux questions / Sheeva and Wifi on: November 09, 2010, 12:40:30 AM
Hello,

I have two SheevaPlug, a Globalscale with kernel 2.6.36 and a Ionics with a kernel 2.6.31.8.

I'm trying to work with a Wifi USB key.

On Globalscale,

I'm trying with RT2870 (Hercules HWNum-300), RT73 and RTL8187 (Netgear WG111) :
- the RT2870 driver is found in drivers/staging, so I suppose it is not yet ready, that's why I think it doesn't work.
- the RT73 driver is found in drivers/net/wireless, so I don't understand why it doesn't work ?
- the RTL8187 is working fine ;o)

Here is the informations that I can read on my Globalscale :

# lsmod
Module                  Size  Used by
rtl8187                50984  0
eeprom_93cx6            1166  1 rtl8187
ipv6                  235803  16
dm_crypt               11435  0
dm_mod                 60233  1 dm_crypt
mv_cesa                 9370  0

# tail /var/log/messages
Nov  9 06:30:45 g-sheeva-gb-2 kernel: usb 1-1: new high speed USB device using orion-ehci and address 2
Nov  9 06:30:45 g-sheeva-gb-2 kernel: phy0: hwaddr 00:14:6c:62:af:17, RTL8187vB (default) V1 + rtl8225, rfkill mask 2
Nov  9 06:30:45 g-sheeva-gb-2 kernel: rtl8187: Customer ID is 0xFF
Nov  9 06:30:45 g-sheeva-gb-2 kernel: rtl8187: wireless switch is on
Nov  9 06:30:45 g-sheeva-gb-2 kernel: usbcore: registered new interface driver rtl8187
Nov  9 06:30:47 g-sheeva-gb-2 kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready

# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:14:6c:62:af:17
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

# modprobe -l | head
kernel/fs/reiserfs/reiserfs.ko
kernel/fs/isofs/isofs.ko
kernel/fs/hfsplus/hfsplus.ko
kernel/fs/hfs/hfs.ko
kernel/fs/exportfs/exportfs.ko
kernel/fs/nfsd/nfsd.ko
kernel/fs/cifs/cifs.ko

Now, I'm trying the same operation on the Ionics. And all if KO ! The driver which have the best result is RTL8187.
Here is its configuration.

# lsmod
Module                  Size  Used by
rtl8187                51738  0
eeprom_93cx6            2044  1 rtl8187
ipv6                  271520  16
md_mod                 97756  0

# tail /var/log/messages
Nov  9 07:33:02 g-sheeva-ionics-4 kernel: usb 1-1: new high speed USB device using orion-ehci and address 2
Nov  9 07:33:03 g-sheeva-ionics-4 kernel: usb 1-1: configuration #1 chosen from 1 choice
Nov  9 07:33:03 g-sheeva-ionics-4 kernel: phy0: hwaddr 00:14:6c:62:af:17, RTL8187vB (default) V1 + rtl8225
Nov  9 07:33:03 g-sheeva-ionics-4 kernel: usbcore: registered new interface driver rtl8187


# modprobe -l | head
/lib/modules/2.6.31.8/kernel/sound/usb/snd-usb-lib.ko
/lib/modules/2.6.31.8/kernel/sound/usb/snd-usb-audio.ko
/lib/modules/2.6.31.8/kernel/sound/usb/caiaq/snd-usb-caiaq.ko
/lib/modules/2.6.31.8/kernel/sound/soundcore.ko

I don't know why my Ionics doesn't launch the 'ADDRCONF(NETDEV_UP)' see in messages.log
The modprobe command show module in absolute path, while my Globalscale use it in relative.

So, I'm trying the same kernel on my Ionics (2.6.36), and added also the modules.

# lsmod
Module                  Size  Used by

There are no module loaded Huh Something is going wrong.

# tail /var/log/messages
Nov  9 08:21:11 g-sheeva-ionics-4 kernel: usb 1-1: new high speed USB device using orion-ehci and address 3

# modprobe -l | head
kernel/fs/reiserfs/reiserfs.ko
kernel/fs/isofs/isofs.ko
kernel/fs/hfsplus/hfsplus.ko
kernel/fs/hfs/hfs.ko
kernel/fs/exportfs/exportfs.ko
kernel/fs/nfsd/nfsd.ko

modules have relative path. So, because nothing appears, I'm trying to load module of key.

# modprobe rtl8187
WARNING: Could not open 'kernel/drivers/misc/eeprom/eeprom_93cx6.ko': No such file or directory
FATAL: Could not open 'kernel/drivers/net/wireless/rtl818x/rtl8187.ko': No such file or directory

It couldn't find it in relative path ? The same error appears in the syslog file during boot:
Nov  9 07:50:19 g-sheeva-ionics-4 modprobe: FATAL: Could not open 'kernel/net/ipv6/ipv6.ko': No such file or directory

That's why no default module is found.

Now, I don't know where to look for ! Can you help me ?

Thanks

Regards

Bob
15  Linux Stuff / General Linux questions / Re: Globalscale versus Ionics on: October 20, 2010, 10:30:21 PM

Hello,

I found a marvelous site which explains how to update automatically a SheevaPlug Globalscales to UBIFS.

   http://plug.maisondouf.fr/doku.php?id=sheevaplug:distrib:ubuntu

It's in french. But the uboot command are universal  Cheesy

you have to update Uboot, save content of directory included in file sheevaplug-installer-v1.0.tar.gz in USB key, set some Uboot command, plug USB key, and reset PlugComputer.

There are just some little error on Uboot command. You have to change double quotation marks to no quotation marks for tow lines.

   setenv recover1 'setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd "run recover2"; saveenv; reset'
   setenv recover2 'run recover3; setenv bootcmd "run nand_boot"; saveenv; run recover5'

become

   setenv recover1 'setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset'
   setenv recover2 'run recover3; setenv bootcmd run nand_boot; saveenv; run recover5'

PS: in the file sheevaplug-installer-v1.0.tar.gz, you can change the rootfs.tar.gz and uImage files by the last available for SheevaPlug, and you'll have a new SheevaPlug in UBIFS with the lastest kernel  Cheesy  I've test it with the last 2.6.35.7

Regards
Pages: [1] 2