• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3 4 ... 8
16  Linux Stuff / Kernel / Re: 2.6.30-rc8 new release on: June 08, 2009, 07:47:26 PM
Check to see if you have 'ro' in your bootargs definition following the '(uImage)'

The 'ro' sets the partition to read only.  You would have to remove it to be able to write to /dev/mtd1.
17  General Category / Success stories / Re: Sheevaplug with MIMO monitor on: June 05, 2009, 06:07:36 AM
The attachment issue is fixed.  Thanks
18  General Category / Success stories / Re: Sheevaplug with MIMO monitor on: June 04, 2009, 09:59:18 AM
I can't see the attachment.

Mark
19  Hardware and U-Boot firmware / U-Boot stuff / Re: NFS boot problem on: May 26, 2009, 03:41:52 PM
You should be able to use DHCP as long as the router is configured to give out the correct address. 

Can you tell from the router logs if it is getting the DHCP request from the plug?

Do you have more than one plug?  I found that if I booted a second plug using the file system I had previously used to boot another plug it confused the network settings.

udev enters a rule in /etc/udev/rules.d/70-persistent-net.rules based on the mac address so that the same device is always associated with a particular network interface.  So when I booted the first plug it entered a rule associating eth0 with the mac address of that plug.  When I booted the second plug it created a rule and assigned eth1 to the Ethernet interface since it had a different mac address.  If this happens you can fix it by just deleteing the rules from /etc/udev/rules.d/70-persistent-net.rules and it will assign eth0 to the first network interface it finds.
20  Hardware and U-Boot firmware / U-Boot stuff / Re: NFS boot problem on: May 25, 2009, 06:40:10 AM
In uboot you give the plug 192.168.178.23 for an ip address. 

In your /etc/exports you allow addresses of the range 192.168.178.20/30 (192.168.178.20 - 192.168.178.23) to access your nfs server.

It looks like it is working fine up until it is initializing the Ethernet interface.

If your /etc/network/interfaces is causes the plug to get an address range other than (192.168.178.20 - 192.168.178.23) when the ethernet interface is initialized then your nfs server will no longer let it access the file system.

Try setting a static ip address in /etc/network/interfaces or make sure your dhcp server will assign the plug a address in the range allowed by your nfs server.

example of a static address in /etc/network/interfaces:
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
auto eth0
iface eth0 inet static
        address 192.168.178.21
        netmask 255.255.255.0
        network 192.168.178.0
        broadcast 192.168.178.255
        gateway 192.168.178.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 192.168.178.1
        dns-search example.org
21  Linux Stuff / Kernel / Re: Trouble building module for x10 cm19a on: May 06, 2009, 07:26:54 PM
I've done some more testing of this.  I upgraded my eeePC 1000 to Ubuntu Jaunty and compiled the module.  It works fine on that system.  I even grabbed 2.6.30-rc4 for the eeePC and it compiled and worked on with version kernel also.

On the plug I downloaded the orion git and built that version of 2.6.30-rc3.  It failed the same way running with that build on the sheeva plug.

So I'm starting to think this is a problem in the kernel and not my module.
22  Linux Stuff / General Linux questions / Re: apt-get not working on: May 04, 2009, 01:59:10 PM
If your just starting out with this and haven't spent a lot of time setting stuff up yet you might want to just rewrite the file system and start over.

Are you running the file system from the internal flash?  

Do you have another linux system you could use as an nfs server to boot via nfs from?

in order to erase and re write the file system to the flash you will need to bootup with the file system running some where other than flash.

we should be able to help you do that.

23  Linux Stuff / General Linux questions / Re: apt-get not working on: May 04, 2009, 11:03:29 AM
# apt-get update
Hit http://ports.ubuntu.com jaunty Release.gpg
Hit http://ports.ubuntu.com jaunty Release
Hit http://ports.ubuntu.com jaunty/main Packages
Hit http://ports.ubuntu.com jaunty/restricted Packages
Hit http://ports.ubuntu.com jaunty/universe Packages
Hit http://ports.ubuntu.com jaunty/multiverse Packages
Reading package lists... Done
24  Linux Stuff / Kernel / Re: 2.6.30-rc uImage and kmods ipkg feed on: May 04, 2009, 09:50:59 AM
Ok, I reverted back to using the previous patch along with the two new power patches and it is happy again.

I guess we still need " Voodoo "
25  Linux Stuff / General Linux questions / Re: Trouble following "Boot USB" wiki on: May 04, 2009, 09:39:13 AM
pushbx,

With ext2 you don't need the extra partition.  I just put the kernel in /boot of my files system partition and then use.
 
Code:
set bootcmd 'usb start; ext2load usb 0:1 0x800000 /boot/uImage; bootm 0x800000; reset'
set bootargs 'console=ttyS0,115200 mtdparts=orion_nand:0x100000@0x000000(u-boot)ro,0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/sda1 rootdelay=10'

Actually I create a link in /boot/uImage that points to the kernel I want to use so I can switch it easily.

Code:
root@server:~# ls -l /boot
total 8244
lrwxrwxrwx 1 root root      17 May  4 11:14 uImage -> uImage-2.6.30-rc4
-rw-r--r-- 1 root root 2113572 May  4 11:10 uImage-2.6.30-rc4
-rw-r--r-- 1 root root 2094736 May  3 13:01 uImage-2.6.30-rc4-optware-build-2
-rw-r--r-- 1 root root 2098736 May  4 09:03 uImage-2.6.30-rc4.sav
-rw-r--r-- 1 root root 2106760 Mar 19 15:05 uImage.sheeva.20090319

Make it seem like a more normal Linux system setup that way.
26  Linux Stuff / Kernel / Re: 2.6.30-rc uImage and kmods ipkg feed on: May 04, 2009, 07:47:10 AM
Brian,

Was this patch supposed to replace the previous mods or be in addition to them.  I replaced the previous ones in my build as I think you did also.

Mark
27  Linux Stuff / Kernel / Re: 2.6.30-rc uImage and kmods ipkg feed on: May 04, 2009, 07:05:25 AM
======
kernel BUG at arch/arm/mm/dma-mapping.c:497!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c4b68000
======

Hmmm.... Hope there is not a problem with kernel DMA code. We need to review the driver sources first. It should be easier than reviewing kernel DMA engine.  Smiley


This is a bit off topic so I started a new topic here:

http://openplug.org/plugforum/index.php?topic=239.msg1356#msg1356
28  Linux Stuff / Kernel / Trouble building module for x10 cm19a on: May 04, 2009, 07:03:04 AM
I have code for a module for an X10 cm19a (USB transceiver) that I have compiled and used in the past.  I got it from http://lemaymd.com/drupal/node/3 but then I customized it a bit for my own use. 

I'm using this setup guide:
http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/

For directions on building the module and I have built this module with my changes in the past and used it on my NSLU2 with both the unslug firmware and debian.

I have setup a native build environment for my kernel using the defconfig and patches from the optware trunk http://svn.nslu2-linux.org/svnroot/optware/trunk/sources/kernel-modules/kirkwood/ which is producing a good kernel and modules that should be the same as the one bzhou has provided us in the NSLU2 optware feeds.

The module code compiles ok but when I plug the cm19a device into my USB hub the module crashes with the following dump.

Code:
x10-cm19a: Found input endpoint: 81, and output endpoint: 2
kernel BUG at arch/arm/mm/dma-mapping.c:497!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c4b68000
[00000000] *pgd=1f2d6031, *pte=00000000, *ppte=00000000
Internal error: Oops: 817 [#1] PREEMPT
Modules linked in: x10_cm19a(+) nfsd nfs_acl auth_rpcgss exportfs dm_crypt dm_mod ipv6 sg
CPU: 0    Not tainted  (2.6.30-rc4 #1)
PC is at __bug+0x1c/0x28
LR is at __bug+0x18/0x28
pc : [<c0028bb4>]    lr : [<c0028bb0>]    psr: 60000013
sp : df2d3d18  ip : 000024dc  fp : 00000000
r10: dfb5ec00  r9 : d4851464  r8 : 00000000
r7 : de8e6b80  r6 : 00000005  r5 : d4851400  r4 : ffc03060
r3 : 00000000  r2 : 00000000  r1 : c0439ecc  r0 : 00000030
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 0005317f  Table: 04b68000  DAC: 00000015
Process modprobe (pid: 10676, stack limit = 0xdf2d2268)
Stack: (0xdf2d3d18 to 0xdf2d4000)
3d00:                                                       c04b9f9d c002ab10
3d20: 3fc03060 d4851400 000000d0 c01ffd08 0000000d 00000000 ffffffff 00000010
3d40: ffffffff ffffffff 00000001 df2d3d5c df2d3d7c 00000400 00000000 00000000
3d60: ffffffff 00000010 ffffffff 000024ac 000024ac c00367c8 d4851400 00000000
3d80: d4851400 00000000 c04b9f9f de8e6bc0 000000d0 df81dbd8 00000000 c0036df4
3da0: 00000007 20000013 00000000 a0000013 000000d0 ffc03060 d4851400 df2d2000
3dc0: 00000005 df2d3de4 d4851464 df2d3df0 00000000 bf0d00cc 00000000 df2d3e33
3de0: bf0d3b88 df2d3e33 d4851400 00000002 00000050 df0d0d00 c019ef88 df2d3e33
3e00: d4851400 df2d3e2e df2d3e26 df0d0d00 c019ef88 df2ada48 00000000 bf0d12c4
3e20: c4bea7b0 01803e40 24140000 01802020 20142000 a758cb34 bf0d3bd8 df0d0d20
3e40: df0d0d00 bf0d3b58 bf0d3b88 bf0d3bd8 dfb90000 c0203d74 df0d0d28 df0d0d20
3e60: df0d0d20 bf0d3b88 bf0d3b88 c042d048 00000060 c019ffd8 bf0d3b58 df0d0d20
3e80: df0d0d54 bf0d3b88 df2d3ea0 c01a0110 00000000 c01a00b0 bf0d3b88 c019f7c4
3ea0: df95c0b8 df868f90 c042d048 00000000 bf0d3c68 bf0d3b88 df122120 c019f098
3ec0: bf0d2237 c00760f4 bf0d3b58 bf0d3c68 bf0d3b88 bf0d3b88 00000000 df2d2000
3ee0: 00000000 c01a03ec bf0d3b58 bf0d3c68 bf0d21a0 bf0d3b88 00000000 c0203b2c
3f00: 40155000 bf0d3b54 bf0d3c68 40155000 bf0d6000 bf0d609c 00025242 c0025300
3f20: 00000000 fffffffc 00000000 c0065190 00000001 c03083b4 00000000 c0416a20
3f40: c0416a14 ffffffff 00000001 00000000 c0416a14 c0050dc8 00000000 00000000
3f60: 00025242 bf0d3c68 40155000 00000000 00025242 bf0d3c68 40155000 00000000
3f80: c0025b04 c005f950 00001000 00000003 00000000 4015202c 00000000 00018eb0
3fa0: 00000080 c0025980 4015202c 00000000 40155000 00025242 00018330 00000000
3fc0: 4015202c 00000000 00018eb0 00000080 00000000 40155000 00000000 00000000
3fe0: 00000000 bed7d904 0000b484 400ee6f4 60000010 40155000 0a29303d 00000000
[<c0028bb4>] (__bug+0x1c/0x28) from [<c002ab10>] (dma_cache_maint+0x78/0xe8)
[<c002ab10>] (dma_cache_maint+0x78/0xe8) from [<c01ffd08>] (usb_hcd_submit_urb+0x160/0x948)
[<c01ffd08>] (usb_hcd_submit_urb+0x160/0x948) from [<bf0d00cc>] (write_intr_data+0x1b4/0x208 [x10_cm19a])
[<bf0d00cc>] (write_intr_data+0x1b4/0x208 [x10_cm19a]) from [<bf0d12c4>] (x10_cm19a_probe+0x1c0/0x2e0 [x10_cm19a])
[<bf0d12c4>] (x10_cm19a_probe+0x1c0/0x2e0 [x10_cm19a]) from [<c0203d74>] (usb_probe_interface+0xec/0x14c)
[<c0203d74>] (usb_probe_interface+0xec/0x14c) from [<c019ffd8>] (driver_probe_device+0xb0/0x188)
[<c019ffd8>] (driver_probe_device+0xb0/0x188) from [<c01a0110>] (__driver_attach+0x60/0x84)
[<c01a0110>] (__driver_attach+0x60/0x84) from [<c019f7c4>] (bus_for_each_dev+0x4c/0x8c)
[<c019f7c4>] (bus_for_each_dev+0x4c/0x8c) from [<c019f098>] (bus_add_driver+0x130/0x2a4)
[<c019f098>] (bus_add_driver+0x130/0x2a4) from [<c01a03ec>] (driver_register+0xc0/0x14c)
[<c01a03ec>] (driver_register+0xc0/0x14c) from [<c0203b2c>] (usb_register_driver+0x68/0xec)
[<c0203b2c>] (usb_register_driver+0x68/0xec) from [<bf0d609c>] (x10_cm19a_init+0x9c/0x120 [x10_cm19a])
[<bf0d609c>] (x10_cm19a_init+0x9c/0x120 [x10_cm19a]) from [<c0025300>] (do_one_initcall+0x50/0x194)
[<c0025300>] (do_one_initcall+0x50/0x194) from [<c005f950>] (sys_init_module+0x90/0x194)
[<c005f950>] (sys_init_module+0x90/0x194) from [<c0025980>] (ret_fast_syscall+0x0/0x2c)
Code: e1a01000 e59f000c eb0b6c1b e3a03000 (e5833000)
---[ end trace de5dfc3b178aba34 ]---
 

Any ideas how I should proceed?

Mark

Edit:
I went back and tried the code without my customizations and got the same results.


29  Linux Stuff / Kernel / Re: 2.6.30-rc4 new release on: May 04, 2009, 06:41:30 AM
I just tested this new mvsdio patch in my native build and the optware build and both now fail with my kingston 8gb class 6 card.

Has anyone had better luck?

See details in this post

http://openplug.org/plugforum/index.php?topic=92.msg1354#msg1354
30  Linux Stuff / Kernel / Re: 2.6.30-rc uImage and kmods ipkg feed on: May 04, 2009, 06:37:43 AM
So the new mvsdio.patch for 2.6.30-rc4 broke my ability to read my sdcard.

I'm using a 8GB kingston class 6 SDHC card.

I first tried the patch on my own kernel build which is a native build using the defconfig and patches from the optware trunk http://svn.nslu2-linux.org/svnroot/optware/trunk/sources/kernel-modules/kirkwood/

This failed so I installed the new optware kernel using ipkg.  I get the same results so it doesn't seem to be something wrong with my build.

When I insert the card it looks normal when I mount the card I now get the following error.

Code:
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 0002
mmcblk0: mmc0:0002 SD8GB 7.56 GiB
 mmcblk0: p1
kjournald starting.  Commit interval 5 seconds
mmc0: unhandled error status 0x4000
mmcblk0: error -42 sending read/write command, response 0x900, card status 0xd00
end_request: I/O error, dev mmcblk0, sector 16
Buffer I/O error on device mmcblk0p1, logical block 0
lost page write due to I/O error on mmcblk0p1
EXT3 FS on mmcblk0p1, internal journal
EXT3-fs: mounted filesystem with writeback data mode.

The card is still fine and mounts normally if I stick it in a usb reader and mount it.

Mark
Pages: 1 [2] 3 4 ... 8