• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 [2] 3
Author Topic: 2.6.30 uImage and kmods ipkg feed  (Read 17169 times)
bzhou
Global Moderator
Newbie
*****

Karma: 0
Posts: 43


View Profile
« Reply #15 on: April 19, 2009, 10:10:25 AM »

Have you flashed the uImage into mtd1? If not, you're still using the old kernel, which requires setting mainlineLinux to no to boot.
Logged

tehcrash
Newbie
*

Karma: 0
Posts: 8


View Profile
« Reply #16 on: April 19, 2009, 11:31:21 AM »

I had not flashed the image.   

It now gets past the point it was stuck at, but now I have a I get a Kernel panic:
Quote
rtc-mv rtc-mv: setting system clock to 2009-01-26 18:14:20 UTC (1232993660)
List of all partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (driver?)
No filesystem could mount root, tried:  ext3 ext2 cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[<c0029640>] (unwind_backtrace+0x0/0xdc) from [<c0034a38>] (panic+0x58/0x124)
[<c0034a38>] (panic+0x58/0x124) from [<c0008e88>] (mount_block_root+0x1c4/0x204)
[<c0008e88>] (mount_block_root+0x1c4/0x204) from [<c00090d8>] (prepare_namespace+0x11c/0x174)
[<c00090d8>] (prepare_namespace+0x11c/0x174) from [<c0008884>] (kernel_init+0xb8/0xe4)
[<c0008884>] (kernel_init+0xb8/0xe4) from [<c0037838>] (do_exit+0x0/0x6cc)
[<c0037838>] (do_exit+0x0/0x6cc) from [<00000000>] (0x0)
Logged

bzhou
Global Moderator
Newbie
*****

Karma: 0
Posts: 43


View Profile
« Reply #17 on: April 22, 2009, 08:04:03 PM »

Now updated to 2.6.30-rc3.
Logged

Rod Whitby
Newbie
*

Karma: 0
Posts: 1



View Profile
« Reply #18 on: April 23, 2009, 05:12:09 AM »

I use the following u-boot vars:

Code:
setenv mainlineLinux yes
setenv arcNumber 2097
setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:0x100000@0x000000(u-boot)ro,0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs) root=/dev/mtdblock2 rootfstype=jffs2 rw

and I do:

Code:
rm -rf /opt/lib/modules
ln -s /lib/modules /opt/lib/modules

before I start installing any optware modules.

Doing it this way means that I can use the normal Ubuntu depmod and modprobe, and don't need to ipkg install module-init-tools.

-- Rod
« Last Edit: April 23, 2009, 05:20:37 AM by Rod Whitby » Logged

kilowatt
Global Moderator
Full Member
*****

Karma: 3
Posts: 106


View Profile
« Reply #19 on: April 28, 2009, 12:03:31 PM »

Brian,

So I have this 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 would like to compile it for use on the Plug but I am using the optware kernel you created and I don't have the header files.  apt-get would install 2.6.28-11 and ipkg doesn't have the headers available.  What is the best way to get the header files so I could still use your optware kernel?  Would I also need the configure file that you used to create the kernel?

An optware linux-headers file that matched the kernel would be great.

Mark
Logged

KostaP
Global Moderator
Newbie
*****

Karma: 0
Posts: 20



View Profile
« Reply #20 on: April 29, 2009, 06:41:44 AM »

Mark, the easiest way to solve your problem is to put entire Linux kernel source tree on other system (PC or NAS) and mount this tree on SheevaPlug trough NFS. Then change the /lib/modules/<kernel-version>/build link to point into your source tree directory.
« Last Edit: April 29, 2009, 06:43:16 AM by KostaP » Logged

bzhou
Global Moderator
Newbie
*****

Karma: 0
Posts: 43


View Profile
« Reply #21 on: May 01, 2009, 07:58:47 AM »

Feed updated to rc4.
Logged

kilowatt
Global Moderator
Full Member
*****

Karma: 3
Posts: 106


View Profile
« Reply #22 on: May 01, 2009, 11:42:51 AM »

So, after much pain and many attempts I did get the x10 cm19a module to build.  Unfortunately it just crashes on load.

The nfs mount of the tree from another linux device didn't quite workout.  The module would not build because some of the tools needed had not be built from the source.  For instants scripts/mod/modpost.

In the end I loaded the tree on the sheeva.  Downloaded the defconfig from the optware sources.  And built the kernel and some modules on the sheeva.  Then I was able to get my module to build but it doesn't work properly.

« Last Edit: May 01, 2009, 01:05:42 PM by kilowatt » Logged

bzhou
Global Moderator
Newbie
*****

Karma: 0
Posts: 43


View Profile
« Reply #23 on: May 03, 2009, 08:04:39 PM »

Thanks for rabeeh's suggestion, 2.6.30-rc4 kernel ipk's have been updated to build #2.

The changes are:
1. enabled initrd
2. replaced SD patch with a new one from marvell git
3. added two patches related to power management from marvell git

Link to changeset http://trac.nslu2-linux.org/optware/changeset/10039

Logged

KostaP
Global Moderator
Newbie
*****

Karma: 0
Posts: 20



View Profile
« Reply #24 on: May 03, 2009, 10:26:41 PM »

In the end I loaded the tree on the sheeva.  Downloaded the defconfig from the optware sources.  And built the kernel and some modules on the sheeva.  Then I was able to get my module to build but it doesn't work properly.

Ya, the native build usually helps :-). What do you mean by saying "doesn't work properly"?  You cannot send commands to X10 devices? CM19 is not detected? Errors when the module is loaded?
I believe you are following this setup guide:
http://wp.pr0gr4mm3r.com/linux/getting-your-x10-cm19a-module-working-in-linux/
Logged

kilowatt
Global Moderator
Full Member
*****

Karma: 3
Posts: 106


View Profile
« Reply #25 on: May 04, 2009, 04:35:49 AM »

Yes I'm following that guide and I've built this module and used it on my NSLU2 using both the unslug firmware and debian.

The code must need some changes to work with 2.6.30.

The module crashes on load.  This is from dmesg after plugging in the cm19a:

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 ]---
« Last Edit: May 04, 2009, 04:38:04 AM by kilowatt » Logged

KostaP
Global Moderator
Newbie
*****

Karma: 0
Posts: 20



View Profile
« Reply #26 on: May 04, 2009, 04:57:02 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
Logged

kilowatt
Global Moderator
Full Member
*****

Karma: 3
Posts: 106


View Profile
« Reply #27 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
« Last Edit: May 04, 2009, 06:45:17 AM by kilowatt » Logged

kilowatt
Global Moderator
Full Member
*****

Karma: 3
Posts: 106


View Profile
« Reply #28 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
Logged

bzhou
Global Moderator
Newbie
*****

Karma: 0
Posts: 43


View Profile
« Reply #29 on: May 04, 2009, 07:42:59 AM »

Reverting mvsdio.patch to the old one in rc4 optware build #3.

I guess I did not give it enough test, when mounting it's giving me
Code:
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 8192
Buffer I/O error on device mmcblk0p1, logical block 0
lost page write due to I/O error on mmcblk0p1

[Update] rc4 build #3 is in the feed.
« Last Edit: May 04, 2009, 08:33:01 AM by bzhou » Logged

Pages: 1 [2] 3
Print
Jump to: