[Arm-netbook] debian for mele a1000 / a2000
Rosimildo DaSilva
rosimildo at gmail.com
Thu May 31 04:38:30 BST 2012
Ok, going back to read everything again.... I have tried to post with a
complete LOG, but that bounced back.
R
On Wed, May 30, 2012 at 9:43 PM, Tom Cubie <mr.hipboi at gmail.com> wrote:
>
>
> On Thu, May 31, 2012 at 10:21 AM, Rosimildo DaSilva <rosimildo at gmail.com>wrote:
>
>> My system is going a bit further.... but still no luck, and the system
>> keeps rebooting.
>>
>> ----------------------------
>> [mmc_pm]: no sdio card used in configuration
>> [ 3.880000] [mmc_pm]: no sdio card used in configuration
>>
> Here, the script.bin(or whatever the name) is not loaded to 0x43000000
> before the kernel boots.
>
>> [mmc]: sunximmc_init
>> [ 3.890000] [mmc]: sunximmc_init
>> [mmc]: sunxi mmc controller using config : 0xb
>> [ 3.900000] [mmc]: sunxi mmc controller using config : 0xb
>> [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
>> [ 3.910000] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
>> [mmc]: mmc 0 power off !!
>> [ 3.920000] [mmc]: mmc 0 power off !!
>> [mmc]: mmc0 Probe: base:0xdc8de000 irq:32 dma:0 pdes:0xd9a88000, ret 0.
>> [ 3.920000] [mmc]: mmc0 Probe: base:0xdc8de000 irq:32 dma:0
>> pdes:0xd9a88000, ret 0.
>> [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
>> [ 3.940000] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
>> [mmc]: mmc 1 power off !!
>> [ 3.950000] [mmc]: mmc 1 power off !!
>> [mmc]: mmc1 Probe: base:0xdc8e0000 irq:33 dma:0 pdes:0xd9a90000, ret 0.
>> [ 3.960000] [mmc]: mmc1 Probe: base:0xdc8e0000 irq:33 dma:0
>> pdes:0xd9a90000, ret 0.
>> [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
>> [ 3.970000] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
>> [mmc]: mmc 3 power off !!
>> [ 3.980000] [mmc]: mmc 3 power off !!
>> [mmc]: mmc3 Probe: base:0xdc8e2000 irq:35 dma:0 pdes:0xd9a94000, ret 0.
>> [ 3.990000] [mmc]: mmc3 Probe: base:0xdc8e2000 irq:35 dma:0
>> pdes:0xd9a94000, ret 0.
>> <6>usbcore: registered new interface driver usbhid
>> [ 4.000000] usbcore: registered new interface driver usbhid
>> <6>usbhid: USB HID core driver
>> [ 4.010000] usbhid: USB HID core driver
>> <6>logger: created 256K log 'log_main'
>> [ 4.020000] logger: created 256K log 'log_main'
>> <6>logger: created 256K log 'log_events'
>> [ 4.030000] logger: created 256K log 'log_events'
>> <6>logger: created 256K log 'log_radio'
>> [ 4.040000] logger: created 256K log 'log_radio'
>> <6>logger: created 256K log 'log_system'
>> [ 4.040000] logger: created 256K log 'log_system'
>> enter sun4i Audio codec!!!
>> [ 4.050000] enter sun4i Audio codec!!!
>> <6>sun4i audio support initialized
>> [ 4.060000] sun4i audio support initialized
>> audiocodec_adap_awxx_init: script_parser_fetch err.
>> [ 4.070000] audiocodec_adap_awxx_init: script_parser_fetch err.
>> sun4i Audio codec successfully loaded..
>> [ 4.080000] sun4i Audio codec successfully loaded..
>> <6>asoc: sndhdmi <-> sun4i-hdmiaudio.0 mapping ok
>> [ 4.090000] asoc: sndhdmi <-> sun4i-hdmiaudio.0 mapping ok
>> <6>ALSA device list:
>> [ 4.100000] ALSA device list:
>> <6> #0: sun4i-CODEC Audio Codec
>> [ 4.100000] #0: sun4i-CODEC Audio Codec
>> <6> #1: sun4i-sndhdmi
>> [ 4.110000] #1: sun4i-sndhdmi
>> <6>IPv4 over IPv4 tunneling driver
>> [ 4.120000] IPv4 over IPv4 tunneling driver
>> <6>TCP cubic registered
>> [ 4.120000] TCP cubic registered
>> <6>Initializing XFRM netlink socket
>> [ 4.130000] Initializing XFRM netlink socket
>> <6>NET: Registered protocol family 17
>> [ 4.140000] NET: Registered protocol family 17
>> <6>NET: Registered protocol family 15
>> [ 4.140000] NET: Registered protocol family 15
>> <6>Bluetooth: RFCOMM TTY layer initialized
>> [ 4.150000] Bluetooth: RFCOMM TTY layer initialized
>> <6>Bluetooth: RFCOMM socket layer initialized
>> [ 4.160000] Bluetooth: RFCOMM socket layer initialized
>> <6>Bluetooth: RFCOMM ver 1.11
>> [ 4.170000] Bluetooth: RFCOMM ver 1.11
>> <6>Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>> [ 4.180000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>> <6>Bluetooth: BNEP filters: protocol multicast
>> [ 4.190000] Bluetooth: BNEP filters: protocol multicast
>> <6>802.1Q VLAN Support v1.8
>> [ 4.200000] 802.1Q VLAN Support v1.8
>> [mmc_pm]: No sdio card, please check your config !!
>> [ 4.200000] [mmc_pm]: No sdio card, please check your config !!
>> <6>VFP support v0.3: [ 4.210000] VFP support v0.3: implementor 41
>> architecture 3 part 30 variant c rev 3
>> implementor 41 architecture 3 part 30 variant c rev 3
>> <5>Registering SWP/SWPB emulation handler
>> [ 4.230000] Registering SWP/SWPB emulation handler
>> <6>registered taskstats version 1
>> [ 4.240000] registered taskstats version 1
>> <4>regulator_init_complete: axp20_buck3: incomplete constraints, leaving
>> on
>> [ 4.240000] regulator_init_complete: axp20_buck3: incomplete
>> constraints, leaving on
>> <4>regulator_init_complete: axp20_buck2: incomplete constraints, leaving
>> on
>> [ 4.260000] regulator_init_complete: axp20_buck2: incomplete
>> constraints, leaving on
>> <4>regulator_init_complete: axp20_ldo4: incomplete constraints, leaving on
>> [ 4.270000] regulator_init_complete: axp20_ldo4: incomplete
>> constraints, leaving on
>> <4>regulator_init_complete: axp20_ldo3: incomplete constraints, leaving on
>> [ 4.290000] regulator_init_complete: axp20_ldo3: incomplete
>> constraints, leaving on
>> <4>regulator_init_complete: axp20_ldo2: incomplete constraints, leaving on
>> [ 4.300000] regulator_init_complete: axp20_ldo2: incomplete
>> constraints, leaving on
>> <4>regulator_init_complete: axp20_ldo1: incomplete constraints, leaving on
>> [ 4.320000] regulator_init_complete: axp20_ldo1: incomplete
>> constraints, leaving on
>> <6>sunxi-rtc sunxi-rtc: sunxi_rtc_gettime
>> [ 4.330000] sunxi-rtc sunxi-rtc: sunxi_rtc_gettime
>> <6>sunxi-rtc sunxi-rtc: read time 2010-1-1 0:0:8
>> [ 4.340000] sunxi-rtc sunxi-rtc: read time 2010-1-1 0:0:8
>> <6>sunxi-rtc sunxi-rtc: setting system clock to 2010-01-01 00:00:08 UTC
>> (1262304008)
>> [ 4.350000] sunxi-rtc sunxi-rtc: setting system clock to 2010-01-01
>> 00:00:08 UTC (1262304008)
>> VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0)
>> [ 4.370000] VFS: Cannot open root device "mmcblk0p2" or
>> unknown-block(0,0)
>> Please append a correct "root=" boot option; here are the available
>> partitions:
>> [ 4.380000] Please append a correct "root=" boot option; here are the
>> available partitions:
>> 5d00 16384 nanda [ 4.390000] 5d00 16384 nanda
>> (driver?)
>> (driver?)
>> 5d08 32768 nandb [ 4.400000] 5d08 32768 nandb
>> (driver?)
>> (driver?)
>> 5d10 262144 nandc [ 4.410000] 5d10 262144 nandc
>> (driver?)
>> (driver?)
>> 5d18 1572864 nandd [ 4.420000] 5d18 1572864 nandd
>> (driver?)
>> (driver?)
>> 5d20 1024 nande [ 4.430000] 5d20 1024 nande
>> (driver?)
>> (driver?)
>> 5d28 32768 nandf [ 4.430000] 5d28 32768 nandf
>> (driver?)
>> (driver?)
>> 5d30 131072 nandg [ 4.440000] 5d30 131072 nandg
>> (driver?)
>> (driver?)
>> 5d38 2048 nandh [ 4.450000] 5d38 2048 nandh
>> (driver?)
>> (driver?)
>> 5d40 1839104 nandi [ 4.460000] 5d40 1839104 nandi
>> (driver?)
>> (driver?)
>> <0>Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>> [ 4.470000] Kernel panic - not syncing: VFS: Unable to mount root fs
>> on unknown-block(0,0)
>> Backtrace: [ 4.480000] Backtrace:
>>
>> [<c003bfe0>] (dump_backtrace+0x0/0x110) from [<c0582ab4>]
>> (dump_stack+0x18/0x1c)
>> [ 4.490000] [<c003bfe0>] (dump_backtrace+0x0/0x110) from [<c0582ab4>]
>> (dump_stack+0x18/0x1c)
>> r6:c07cf1e0[ 4.500000] r6:c07cf1e0 r5:c002b80c r5:c002b80c
>> r4:c07d2330 r4:c07d2330 r3:00000000 r3:00000000
>>
>> [<c0582a9c>] (dump_stack+0x0/0x1c) from [<c0582b2c>] (panic+0x74/0x194)
>> [ 4.510000] [<c0582a9c>] (dump_stack+0x0/0x1c) from [<c0582b2c>]
>> (panic+0x74/0x194)
>> [<c0582ab8>] (panic+0x0/0x194) from [<c0008f04>]
>> (mount_block_root+0x214/0x2b8)
>> [ 4.530000] [<c0582ab8>] (panic+0x0/0x194) from [<c0008f04>]
>> (mount_block_root+0x214/0x2b8)
>> r3:00000000[ 4.540000] r3:00000000 r2:d983a018 r2:d983a018
>> r1:d983bf60 r1:d983bf60 r0:c06e5840 r0:c06e5840
>>
>> r7:00008000[ 4.550000] r7:00008000
>>
>> [<c0008cf0>] (mount_block_root+0x0/0x2b8) from [<c00090f8>]
>> (mount_root+0x64/0x68)
>> [ 4.560000] [<c0008cf0>] (mount_block_root+0x0/0x2b8) from
>> [<c00090f8>] (mount_root+0x64/0x68)
>> [<c0009094>] (mount_root+0x0/0x68) from [<c000929c>]
>> (prepare_namespace+0x1a0/
>> 0x1e8)
>> [ 4.570000] [<c0009094>] (mount_root+0x0/0x68) from [<c000929c>]
>> (prepare_namespace+0x1a0/0x1e8)
>> r5:c002b821[ 4.590000] r5:c002b821 r4:c07cf1e0 r4:c07cf1e0
>>
>> [<c00090fc>] (prepare_namespace+0x0/0x1e8) from [<c0008b88>]
>> (kernel_init+0x154/0x160)
>> [ 4.590000] [<c00090fc>] (prepare_namespace+0x0/0x1e8) from
>> [<c0008b88>] (kernel_init+0x154/0x160)
>> r5:c002ade4[ 4.610000] r5:c002ade4 r4:c002ade4 r4:c002ade4
>>
>> [<c0008a34>] (kernel_init+0x0/0x160) from [<c006aa74>] (do_exit+0x0/0x74c)
>> [ 4.620000] [<c0008a34>] (kernel_init+0x0/0x160) from [<c006aa74>]
>> (do_exit+0x0/0x74c)
>> r5:c0008a34[ 4.630000] r5:c0008a34 r4:00000000 r4:00000000
>>
>> <0>Rebooting in 10 seconds..[ 4.640000] Rebooting in 10
>> seconds..[mmc]: mmc 0 detect change, present 1
>> [mmc]: mmc 0 detect change, present 1
>>
>>
>>
>>
>>
>> On Wed, May 30, 2012 at 8:55 PM, Gary Cramblitt <
>> garycramblitt at comcast.net> wrote:
>>
>>> On 05/30/2012 07:16 AM, Henrik Nordström wrote:
>>> > The only rules are
>>> >
>>> > a) dont partition space below sector 2048. That area is reserved for
>>> > uboot.
>>> >
>>> > b1) Default fallback boot is that first partition is FAT formatted and
>>> > have system.bin and uImage contents.
>>> >
>>> > b2) Preferred boot method is to look for boot.scr in /boot or / on
>>> first
>>> > partition in extX or FAT format
>>> >
>>> >
>>> > If boot.scr is used then it contains the uboot commands needed for
>>> > loading kernel (+ initrd) and booting. The uboot shell is enabled so
>>> you
>>> > have rudimentary sh syntax capabilities.
>>> >
>>> >
>>> > As long as you stay within these boundaries then you are free to decide
>>> > how to partition. Possible layouts are for example
>>> >
>>> > 1) Single extX partition, sector 2048-end. boot.scr in /boot with the
>>> > uboot commands needed for booting.
>>> >
>>> > 2) extX partition + swap partition. boot.scr as above.
>>> >
>>> > 3) FAT boot partition, extX system partition, optional swap partition.
>>> > system.bin + uImage in FAT partition. No boot.scr.
>>> >
>>> > 4) Any other partition scheme you see fit for your purpose.
>>> >
>>> > 5) Reserving even more space and loading kernel from fixed blocks, and
>>> > use some filesystem not supported by uboot for all partitioned storage.
>>> >
>>> > Regards
>>> > Henrik
>>> >
>>>
>>> I'm a bit confused. Suppose I want to go with layout #1. Do I need a
>>> script.bin/mele_stock.bin or not? Example boot.scr? Compile boot.cmd
>>> to boot.scr with mkimage? Should the kernel be uImage or zImage or
>>> vmlinux or what? How do I specify the MAC address?
>>>
>>> Thanks.
>>>
>>> --
>>> Gary Cramblitt
>>> Make a difference! http://kiva.org/invitedby/gary3714
>>>
>>> _______________________________________________
>>> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
>>> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
>>> Send large attachments to arm-netbook at files.phcomp.co.uk
>>>
>>
>>
>> _______________________________________________
>> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
>> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
>> Send large attachments to arm-netbook at files.phcomp.co.uk
>>
>
>
>
> --
> Keep simple, stay foolish.
>
>
>
> _______________________________________________
> arm-netbook mailing list arm-netbook at lists.phcomp.co.uk
> http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
> Send large attachments to arm-netbook at files.phcomp.co.uk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.phcomp.co.uk/pipermail/arm-netbook/attachments/20120530/6cd37c5b/attachment-0001.html
More information about the arm-netbook
mailing list