From florian.koch1981 at googlemail.com Sat Apr 7 18:15:47 2012 From: florian.koch1981 at googlemail.com (Florian Koch) Date: Sat, 7 Apr 2012 20:15:47 +0200 Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! Message-ID: Hi @all, today i recived my dreamplug, and installed armedslack on it. I grab the latest kernel from http://sheeva.with-linux.com/sheeva/kernel/3/3.3/3.3.1/ and the slack-current-miniroot_21Jan12.tar.xz. I put all together and now my dreamplug has a armedslack system, but the boot stops with this Error: Setting system time from the hardware clock (localtime). > Testing root filesystem status: read-write filesystem > > *** ERROR: Root partition has already been mounted read-write. Cannot > check! > > For filesystem checking to work properly, your system must initially mount > the root partition as read only. Please modify your kernel with 'rdev' so > that > it does this. If you're booting with LILO, add a line: > > read-only > > to the Linux section in your /etc/lilo.conf and type 'lilo' to reinstall > it. > > If you boot from a kernel on a floppy disk, put it in the drive and type: > rdev -R /dev/fd0 1 > > If you boot from a bootdisk, or with Loadlin, you can add the 'ro' flag. > > This will fix the problem *AND* eliminate this annoying message. :^) > > Press ENTER to continue. > Checking non-root filesystems: > if i continue, i can login and the system works. i tried to set ro to the kernel comandline in the uboot loader, does not change anything. regards Florian -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sun Apr 8 08:18:07 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 8 Apr 2012 09:18:07 +0100 (BST) Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! In-Reply-To: References: Message-ID: > i tried to set ro to the kernel comandline in the uboot loader, does not > change anything. What does this output? cat /proc/cmdline What might be happening is that the u-boot on your dreamplug does not honour the u-boot variable names that are laid out in the Slackware ARM docs. If this is the case you'll need to figure out which are the correct ones to edit. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Sun Apr 8 08:21:45 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 8 Apr 2012 09:21:45 +0100 (BST) Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! In-Reply-To: References: Message-ID: > > What does this output? > > > cat /proc/cmdline > If this is the case, go into u-boot and do: printenv and match the values found in /proc/cmdline and you should be able to identify which u-boot variable needs altering. -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Sun Apr 8 08:53:23 2012 From: louigi600 at yahoo.it (Davide) Date: Sun, 8 Apr 2012 09:53:23 +0100 (BST) Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! Message-ID: <1333875203.6386.BPMail_high_noncarrier@web29701.mail.ird.yahoo.com> I'd bet on "ro" missing on cmdline. ------------------------------ Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto: > >> >> What does this output? >> >> >> cat /proc/cmdline >> > >If this is the case, go into u-boot and do: >printenv > >and match the values found in /proc/cmdline and you should be able to >identify which u-boot variable needs altering. > >-- >Stuart Winter >Slackware ARM: www.armedslack.org >_______________________________________________ >ARMedslack mailing list >ARMedslack at lists.armedslack.org >http://lists.armedslack.org/mailman/listinfo/armedslack From florian.koch1981 at googlemail.com Sun Apr 8 12:57:45 2012 From: florian.koch1981 at googlemail.com (Florian Koch) Date: Sun, 8 Apr 2012 14:57:45 +0200 Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! In-Reply-To: References: <1333875203.6386.BPMail_high_noncarrier@web29701.mail.ird.yahoo.com> Message-ID: Hm ok, forgot what i say about the ro, i get the error, and if i set ro on the uboot bootargs, the kernel boots and stops at: > dfc0: 00000000 00000000 00000000 c003274c 00000000 00000000 df05b800 > 00000000 > dfe0: de4cdfe0 de4cdfe0 df259d38 c00326c8 c00095a4 c00095a4 00000000 > 00000000 > [] (mmc_io_rw_direct+0x20/0x2c) from [] > (sdio_readb+0x3c/0x5c) > [] (sdio_readb+0x3c/0x5c) from [] > (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) > [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [] > (sdio_irq_thread+0x74/0x234) > [] (sdio_irq_thread+0x74/0x234) from [] > (kthread+0x84/0x90) > [] (kthread+0x84/0x90) from [] > (kernel_thread_exit+0x0/0x8) > Code: 1a000000 e7f001f2 e58d4008 e58dc00c (e5900000) > ---[ end trace b7bb87bd4d1b074c ]--- > mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, > flow control disabled > i have to hit STRG+C and then the boot continues. On Sun, Apr 8, 2012 at 2:11 PM, Florian Koch < florian.koch1981 at googlemail.com> wrote: > Hi, > > yes i have set the wrong uboot var, but when i append ro to the right var, > the system won't boot, the services cannot start because of ro system. > > but forgot about this error, i have build a new minirootfs with the > buildscript, and installed the new rootfs to the dreamplug. > > I can boot into the system, no ro error , and i have not set the uboot > vars to ro. > > but i get a kernel oops during boot, and the boot hangs for some time. > (see attached oops.txt) > i think this come from missing modules. > > > > On Sun, Apr 8, 2012 at 10:53 AM, Davide wrote: > >> >> I'd bet on "ro" missing on cmdline. >> >> >> >> ------------------------------ >> Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto: >> >> > >> >> >> >> What does this output? >> >> >> >> >> >> cat /proc/cmdline >> >> >> > >> >If this is the case, go into u-boot and do: >> >printenv >> > >> >and match the values found in /proc/cmdline and you should be able to >> >identify which u-boot variable needs altering. >> > >> >-- >> >Stuart Winter >> >Slackware ARM: www.armedslack.org >> >_______________________________________________ >> >ARMedslack mailing list >> >ARMedslack at lists.armedslack.org >> >http://lists.armedslack.org/mailman/listinfo/armedslack >> >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From florian.koch1981 at googlemail.com Sun Apr 8 13:11:16 2012 From: florian.koch1981 at googlemail.com (Florian Koch) Date: Sun, 8 Apr 2012 15:11:16 +0200 Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! In-Reply-To: References: <1333875203.6386.BPMail_high_noncarrier@web29701.mail.ird.yahoo.com> Message-ID: OK, now i think i catch the problem: if i boot from the u-boot loader with "boot" on the cmd, all works as expected, if i boot "normal, ist broken as describes, so the bootparms are wrong" her is my printenv, > Marvell>> printenv > bootcmd=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; > ${x_bootcmd_ethernet}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv > bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000; > bootdelay=3 > baudrate=115200 > x_bootcmd_ethernet=ping 192.168.2.1 > x_bootcmd_usb=usb start > x_bootargs=console=ttyS0,115200 > ethaddr=F0:AD:4E:00:B0:6C > eth1addr=F0:AD:4E:00:B0:6D > x_bootcmd_kernel=fatload usb 0:1 0x6400000 uImage > ethact=egiga0 > bootargs=console=ttyS0,115200 root=/dev/sda2 rootdelay=10 ro > x_bootargs_root=root=/dev/sda2 rootdelay=10 ro > stdin=serial > stdout=serial > stderr=serial > > Environment size: 590/4092 bytes > On Sun, Apr 8, 2012 at 2:57 PM, Florian Koch < florian.koch1981 at googlemail.com> wrote: > Hm ok, forgot what i say about the ro, i get the error, and if i set ro > on the uboot bootargs, the kernel boots and stops at: > >> dfc0: 00000000 00000000 00000000 c003274c 00000000 00000000 df05b800 >> 00000000 >> dfe0: de4cdfe0 de4cdfe0 df259d38 c00326c8 c00095a4 c00095a4 00000000 >> 00000000 >> [] (mmc_io_rw_direct+0x20/0x2c) from [] >> (sdio_readb+0x3c/0x5c) >> [] (sdio_readb+0x3c/0x5c) from [] >> (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) >> [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [] >> (sdio_irq_thread+0x74/0x234) >> [] (sdio_irq_thread+0x74/0x234) from [] >> (kthread+0x84/0x90) >> [] (kthread+0x84/0x90) from [] >> (kernel_thread_exit+0x0/0x8) >> Code: 1a000000 e7f001f2 e58d4008 e58dc00c (e5900000) >> ---[ end trace b7bb87bd4d1b074c ]--- >> mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full >> duplex, flow control disabled >> > > i have to hit STRG+C and then the boot continues. > > > On Sun, Apr 8, 2012 at 2:11 PM, Florian Koch < > florian.koch1981 at googlemail.com> wrote: > >> Hi, >> >> yes i have set the wrong uboot var, but when i append ro to the right >> var, the system won't boot, the services cannot start because of ro system. >> >> but forgot about this error, i have build a new minirootfs with the >> buildscript, and installed the new rootfs to the dreamplug. >> >> I can boot into the system, no ro error , and i have not set the uboot >> vars to ro. >> >> but i get a kernel oops during boot, and the boot hangs for some time. >> (see attached oops.txt) >> i think this come from missing modules. >> >> >> >> On Sun, Apr 8, 2012 at 10:53 AM, Davide wrote: >> >>> >>> I'd bet on "ro" missing on cmdline. >>> >>> >>> >>> ------------------------------ >>> Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto: >>> >>> > >>> >> >>> >> What does this output? >>> >> >>> >> >>> >> cat /proc/cmdline >>> >> >>> > >>> >If this is the case, go into u-boot and do: >>> >printenv >>> > >>> >and match the values found in /proc/cmdline and you should be able to >>> >identify which u-boot variable needs altering. >>> > >>> >-- >>> >Stuart Winter >>> >Slackware ARM: www.armedslack.org >>> >_______________________________________________ >>> >ARMedslack mailing list >>> >ARMedslack at lists.armedslack.org >>> >http://lists.armedslack.org/mailman/listinfo/armedslack >>> >>> _______________________________________________ >>> ARMedslack mailing list >>> ARMedslack at lists.armedslack.org >>> http://lists.armedslack.org/mailman/listinfo/armedslack >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From florian.koch1981 at googlemail.com Sun Apr 8 12:11:32 2012 From: florian.koch1981 at googlemail.com (Florian Koch) Date: Sun, 8 Apr 2012 14:11:32 +0200 Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! In-Reply-To: <1333875203.6386.BPMail_high_noncarrier@web29701.mail.ird.yahoo.com> References: <1333875203.6386.BPMail_high_noncarrier@web29701.mail.ird.yahoo.com> Message-ID: Hi, yes i have set the wrong uboot var, but when i append ro to the right var, the system won't boot, the services cannot start because of ro system. but forgot about this error, i have build a new minirootfs with the buildscript, and installed the new rootfs to the dreamplug. I can boot into the system, no ro error , and i have not set the uboot vars to ro. but i get a kernel oops during boot, and the boot hangs for some time. (see attached oops.txt) i think this come from missing modules. On Sun, Apr 8, 2012 at 10:53 AM, Davide wrote: > > I'd bet on "ro" missing on cmdline. > > > > ------------------------------ > Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto: > > > > >> > >> What does this output? > >> > >> > >> cat /proc/cmdline > >> > > > >If this is the case, go into u-boot and do: > >printenv > > > >and match the values found in /proc/cmdline and you should be able to > >identify which u-boot variable needs altering. > > > >-- > >Stuart Winter > >Slackware ARM: www.armedslack.org > >_______________________________________________ > >ARMedslack mailing list > >ARMedslack at lists.armedslack.org > >http://lists.armedslack.org/mailman/listinfo/armedslack > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ata1: SATA max UDMA/133 irq 21 cfg80211: Calling CRDA to update world regulatory domain Bluetooth: Core ver 2.16 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized ata1: SATA link down (SStatus 0 SControl F300) Bluetooth: SCO socket layer initialized Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2 Bluetooth: sbi_interrupt(df077c00) card or priv is NULL, card=df3af840 libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman Bluetooth: request_firmware(helper) failed, error code = -2 Bluetooth: Failed to download helper! Bluetooth: Downloading firmware failed! usbcore: registered new interface driver snd-usb-audio libertas_sdio: failed to find firmware (-2) libertas_sdio: probe of mmc0:0001:1 failed with error -2 uap_probe: vendor=0x02DF device=0x9104 class=0 function=1 ------------[ cut here ]------------ WARNING: at drivers/mmc/core/core.c:465 mmc_wait_for_cmd+0x3c/0x78() Modules linked in: uap8xxx(+) snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer snd libertas_sdio btmrvl_sdio btmrvl libertas bluetooth soundcore cfg80211 rfkill sata_mv [] (unwind_backtrace+0x0/0xe0) from [] (warn_slowpath_common+0x4c/0x64) [] (warn_slowpath_common+0x4c/0x64) from [] (warn_slowpath_null+0x18/0x1c) [] (warn_slowpath_null+0x18/0x1c) from [] (mmc_wait_for_cmd+0x3c/0x78) [] (mmc_wait_for_cmd+0x3c/0x78) from [] (mmc_io_rw_direct_host+0xac/0x110) [] (mmc_io_rw_direct_host+0xac/0x110) from [] (sdio_readb+0x3c/0x5c) [] (sdio_readb+0x3c/0x5c) from [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [] (sdio_irq_thread+0x74/0x234) [] (sdio_irq_thread+0x74/0x234) from [] (kthread+0x84/0x90) [] (kthread+0x84/0x90) from [] (kernel_thread_exit+0x0/0x8) ---[ end trace e5bcda0b6bb19a49 ]--- ------------[ cut here ]------------ WARNING: at drivers/mmc/core/core.c:210 __mmc_start_req+0x74/0x140() Modules linked in: uap8xxx(+) snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer snd libertas_sdio btmrvl_sdio btmrvl libertas bluetooth soundcore cfg80211 rfkill sata_mv [] (unwind_backtrace+0x0/0xe0) from [] (warn_slowpath_common+0x4c/0x64) [] (warn_slowpath_common+0x4c/0x64) from [] (warn_slowpath_null+0x18/0x1c) [] (warn_slowpath_null+0x18/0x1c) from [] (__mmc_start_req+0x74/0x140) [] (__mmc_start_req+0x74/0x140) from [] (mmc_wait_for_req+0x10/0x20) [] (mmc_wait_for_req+0x10/0x20) from [] (mmc_wait_for_cmd+0x64/0x78) [] (mmc_wait_for_cmd+0x64/0x78) from [] (mmc_io_rw_direct_host+0xac/0x110) [] (mmc_io_rw_direct_host+0xac/0x110) from [] (sdio_readb+0x3c/0x5c) [] (sdio_readb+0x3c/0x5c) from [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [] (sdio_irq_thread+0x74/0x234) [] (sdio_irq_thread+0x74/0x234) from [] (kthread+0x84/0x90) [] (kthread+0x84/0x90) from [] (kernel_thread_exit+0x0/0x8) ---[ end trace e5bcda0b6bb19a4a ]--- Unable to handle kernel NULL pointer dereference at virtual address 00000000 pgd = c0004000 [00000000] *pgd=00000000 Internal error: Oops: 80000005 [#1] PREEMPT Modules linked in: uap8xxx(+) snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer snd libertas_sdio btmrvl_sdio btmrvl libertas bluetooth soundcore cfg80211 rfkill sata_mv CPU: 0 Tainted: G W (3.3.1 #5) PC is at 0x0 LR is at __mmc_start_req+0x12c/0x140 pc : [<00000000>] lr : [] psr: 60000013 sp : de4bdec8 ip : 40000013 fp : 00000000 r10: 00000a00 r9 : 00000a00 r8 : 00000001 r7 : de4bdf77 r6 : 00000000 r5 : de521800 r4 : de4bdee8 r3 : 00000000 r2 : 00000000 r1 : de4bdee8 r0 : de521800 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 0005397f Table: 1f340000 DAC: 00000017 Process ksdioirqd/mmc0 (pid: 798, stack limit = 0xde4bc270) Stack: (0xde4bdec8 to 0xde4be000) dec0: de4bdee8 de521800 00000000 c02e13fc de4bdf18 de521800 dee0: 00000000 c02e1470 00000000 de4bdf18 00000000 00000000 00000000 de4bdefc df00: de4bdefc c02e11a4 de521800 00000a00 00000a00 c02e8e00 00000034 00000a00 df20: 00000000 00000000 00000000 00000000 00000195 00000000 00000000 00000000 df40: 00000000 de4bdee8 de4bdf84 df077a00 de520000 00000001 00000000 00000000 df60: 00000000 c02e9e88 00000000 de4bdf77 de4bdf84 00000007 df3482e0 bf12013c df80: df077a00 00000000 df8fb800 7fffffff df8d0400 c02ea738 df2fdd48 c02ea6c4 dfa0: 00000001 00000000 00000000 df2fdd38 df8fb800 c02ea6c4 00000013 00000000 dfc0: 00000000 00000000 00000000 c003274c 00000000 00000000 df8fb800 00000000 dfe0: de4bdfe0 de4bdfe0 df2fdd38 c00326c8 c00095a4 c00095a4 00000000 00000000 [] (__mmc_start_req+0x12c/0x140) from [] (mmc_wait_for_req+0x10/0x20) [] (mmc_wait_for_req+0x10/0x20) from [] (mmc_wait_for_cmd+0x64/0x78) [] (mmc_wait_for_cmd+0x64/0x78) from [] (mmc_io_rw_direct_host+0xac/0x110) [] (mmc_io_rw_direct_host+0xac/0x110) from [] (sdio_readb+0x3c/0x5c) [] (sdio_readb+0x3c/0x5c) from [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [] (sdio_irq_thread+0x74/0x234) [] (sdio_irq_thread+0x74/0x234) from [] (kthread+0x84/0x90) [] (kthread+0x84/0x90) from [] (kernel_thread_exit+0x0/0x8) Code: bad PC value ---[ end trace e5bcda0b6bb19a4b ]--- From florian.koch1981 at googlemail.com Mon Apr 9 06:25:38 2012 From: florian.koch1981 at googlemail.com (Florian Koch) Date: Mon, 9 Apr 2012 08:25:38 +0200 Subject: [ARMedslack] Dreamplug: ERROR: Root partition has already been mounted read-write. Cannot check! In-Reply-To: References: <1333875203.6386.BPMail_high_noncarrier@web29701.mail.ird.yahoo.com> Message-ID: with another kernel , the problems are solved http://www.plugcomputer.org/plugforum/index.php?topic=6063.msg19900#msg19900 thanks anyway regards florian On Sun, Apr 8, 2012 at 3:11 PM, Florian Koch < florian.koch1981 at googlemail.com> wrote: > OK, now i think i catch the problem: > > if i boot from the u-boot loader with "boot" on the cmd, all works as > expected, if i boot "normal, ist broken as describes, so the bootparms are > wrong" > > her is my printenv, > >> Marvell>> printenv >> bootcmd=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact >> egiga1; ${x_bootcmd_ethernet}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; >> setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000; >> bootdelay=3 >> baudrate=115200 >> x_bootcmd_ethernet=ping 192.168.2.1 >> x_bootcmd_usb=usb start >> x_bootargs=console=ttyS0,115200 >> ethaddr=F0:AD:4E:00:B0:6C >> eth1addr=F0:AD:4E:00:B0:6D >> x_bootcmd_kernel=fatload usb 0:1 0x6400000 uImage >> ethact=egiga0 >> bootargs=console=ttyS0,115200 root=/dev/sda2 rootdelay=10 ro >> x_bootargs_root=root=/dev/sda2 rootdelay=10 ro >> stdin=serial >> stdout=serial >> stderr=serial >> >> Environment size: 590/4092 bytes >> > > > On Sun, Apr 8, 2012 at 2:57 PM, Florian Koch < > florian.koch1981 at googlemail.com> wrote: > >> Hm ok, forgot what i say about the ro, i get the error, and if i set ro >> on the uboot bootargs, the kernel boots and stops at: >> >>> dfc0: 00000000 00000000 00000000 c003274c 00000000 00000000 df05b800 >>> 00000000 >>> dfe0: de4cdfe0 de4cdfe0 df259d38 c00326c8 c00095a4 c00095a4 00000000 >>> 00000000 >>> [] (mmc_io_rw_direct+0x20/0x2c) from [] >>> (sdio_readb+0x3c/0x5c) >>> [] (sdio_readb+0x3c/0x5c) from [] >>> (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) >>> [] (sbi_interrupt+0xa4/0x1e4 [uap8xxx]) from [] >>> (sdio_irq_thread+0x74/0x234) >>> [] (sdio_irq_thread+0x74/0x234) from [] >>> (kthread+0x84/0x90) >>> [] (kthread+0x84/0x90) from [] >>> (kernel_thread_exit+0x0/0x8) >>> Code: 1a000000 e7f001f2 e58d4008 e58dc00c (e5900000) >>> ---[ end trace b7bb87bd4d1b074c ]--- >>> mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full >>> duplex, flow control disabled >>> >> >> i have to hit STRG+C and then the boot continues. >> >> >> On Sun, Apr 8, 2012 at 2:11 PM, Florian Koch < >> florian.koch1981 at googlemail.com> wrote: >> >>> Hi, >>> >>> yes i have set the wrong uboot var, but when i append ro to the right >>> var, the system won't boot, the services cannot start because of ro system. >>> >>> but forgot about this error, i have build a new minirootfs with the >>> buildscript, and installed the new rootfs to the dreamplug. >>> >>> I can boot into the system, no ro error , and i have not set the uboot >>> vars to ro. >>> >>> but i get a kernel oops during boot, and the boot hangs for some time. >>> (see attached oops.txt) >>> i think this come from missing modules. >>> >>> >>> >>> On Sun, Apr 8, 2012 at 10:53 AM, Davide wrote: >>> >>>> >>>> I'd bet on "ro" missing on cmdline. >>>> >>>> >>>> >>>> ------------------------------ >>>> Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto: >>>> >>>> > >>>> >> >>>> >> What does this output? >>>> >> >>>> >> >>>> >> cat /proc/cmdline >>>> >> >>>> > >>>> >If this is the case, go into u-boot and do: >>>> >printenv >>>> > >>>> >and match the values found in /proc/cmdline and you should be able to >>>> >identify which u-boot variable needs altering. >>>> > >>>> >-- >>>> >Stuart Winter >>>> >Slackware ARM: www.armedslack.org >>>> >_______________________________________________ >>>> >ARMedslack mailing list >>>> >ARMedslack at lists.armedslack.org >>>> >http://lists.armedslack.org/mailman/listinfo/armedslack >>>> >>>> _______________________________________________ >>>> ARMedslack mailing list >>>> ARMedslack at lists.armedslack.org >>>> http://lists.armedslack.org/mailman/listinfo/armedslack >>>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhm at mersenne.com Wed Apr 11 02:53:27 2012 From: dhm at mersenne.com (David Madden) Date: Tue, 10 Apr 2012 19:53:27 -0700 Subject: [ARMedslack] WiFi on GuruPlug (Standard) Message-ID: <4F84F227.20908@mersenne.com> FYI, I was able to get a vanilla 3.3.1 kernel compiled and running on the GuruPlug Standard. The mwifiex driver supports the sd8787 wifi chipset, but only (as far as I can tell) in client mode. The hardest part was finding a copy of the Marvell firmware: /lib/firmware/mrvl/sd8787_uapsta.bin. Other hints: I think the driver has to be compiled as a module so that the SDIO driver boots up first, then the mwifiex driver can talk to the wireless chipset. Does anybody know whether AP mode can be achieved (except with the older Marvell kernel & driver)? -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201