[ARMedslack] Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - Rev C
chekkizhar N
chekkizhar.linux at gmail.com
Tue Oct 30 08:21:15 UTC 2012
ok. I will wait and meanwhile will do searching as Stuart told.
I got this mail today [30/10/2012 in India ] only.
But, the question and the reply was made on that day [ Sun, 21 Oct 2012 ]
itself.
So, what went wrong?
On Tue, Oct 30, 2012 at 12:19 PM,
<armedslack-request at lists.armedslack.org>wrote:
> Send ARMedslack mailing list submissions to
> armedslack at lists.armedslack.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.armedslack.org/mailman/listinfo/armedslack
> or, via email, send a message with subject or body 'help' to
> armedslack-request at lists.armedslack.org
>
> You can reach the person managing the list at
> armedslack-owner at lists.armedslack.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARMedslack digest..."
>
>
> Today's Topics:
>
> 1. Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - Rev
> C (chekkizhar N)
> 2. Re: Failed to Boot ARMSlackware [13.37] in Beagle Board -xm -
> Rev C (Stuart Winter)
> 3. Using a bootdisk to install armedslack on TrimSlice
> (Frank Donkers)
> 4. Re: New Samsung Chromebook (Ottavio Caruso)
> 5. Re: fix for missing Xvnc in tightvnc (Stuart Winter)
> 6. Re: New Samsung Chromebook (Davide)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 21 Oct 2012 18:22:28 +0800
> From: chekkizhar N <chekkizhar.linux at gmail.com>
> To: armedslack at lists.armedslack.org
> Subject: [ARMedslack] Failed to Boot ARMSlackware [13.37] in Beagle
> Board -xm - Rev C
> Message-ID:
> <CA+SCa2YywYHf=D6dFiYzxiCmC_=_
> ZQX0s06oY-+9Dm1FMxpvig at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> I am trying to load slack-13.37-miniroot_01May11.tar in Beagle Board -xm -
> Rev C.
>
> So far, I made the following changes,
> 1. Created soft link, uImage, which points to uImage-kirkwood-2.6.38.4, in
> /etc/boot dir.
> 2. Edited the console port number to ttyS2 from ttyS0 in /etc/fstab file
>
> I *NOT* changed anything in "/boot" partition, which has
> MLO,uboot-bin,uEnv.txt file.[ came alone with the board ]
>
> Getting the following,
> ##########################################################################
> Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56)
> Beagle xM
> Reading boot sector
> Loading u-boot.bin from mmc
>
>
> U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42)
>
> OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
> OMAP3 Beagle board + LPDDR/NAND
> I2C: ready
> DRAM: 512 MiB
> NAND: 0 MiB
> MMC: OMAP SD/MMC: 0
> *** Warning - readenv() failed, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Beagle xM Rev C
> No EEPROM on expansion board
> Die ID #577200229ff80000016849a901022026
> Hit any key to stop autoboot: 0
> The user button is currently NOT pressed.
> SD/MMC found on device 0
> reading uEnv.txt
>
> 134 bytes read
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
> 2033192 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 80200000 ...
> Image Name: Linux-2.6.38.4-kirkwood
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2033128 Bytes = 1.9 MiB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... OK
> Loading Kernel Image ...
> #################################################################
>
> After the Loading Kernel Image , message nothing is happening.
> Can anyone Help?
>
> Thanks,
> Chekkiizhar
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.armedslack.org/pipermail/armedslack/attachments/20121021/beefdf0d/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Sun, 21 Oct 2012 13:34:54 +0100 (BST)
> From: Stuart Winter <m-lists at biscuit.org.uk>
> To: Slackware ARM port <armedslack at lists.armedslack.org>
> Subject: Re: [ARMedslack] Failed to Boot ARMSlackware [13.37] in
> Beagle Board -xm - Rev C
> Message-ID:
> <alpine.LNX.2.02.1210211329320.5654 at bourbon.biscuit.org.uk>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> On Sun, 21 Oct 2012, chekkizhar N wrote:
>
> [..]
> > 1. Created soft link, uImage, which points to uImage-kirkwood-2.6.38.4,
> in
> > /etc/boot dir.
> > 2. Edited the console port number to ttyS2 from ttyS0 in /etc/fstab file
>
> /etc/boot? what is using /etc/boot ?
> serial console in /etc/fstab? I assume you mean /etc/inittab
>
> The 'kirkwood' kernels are for the Marvell Kirkwood systems such as the
> Sheevaplug, not machines with a 'Cortex' CPU like the Beagleboard.
> Slackware ARM does not provided kernels for the Cortex. In Linux 3.7
> with the planned one kernel for all, once I've understood how it works
> I'll include support for as many of the main architectures as I can.
>
> For now, google 'armedslack beagleboard' and hopefully there'll be enough
> there to get you going.
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 24 Oct 2012 15:02:20 +0200
> From: Frank Donkers <fdonkers at zonnet.nl>
> To: armedslack at lists.armedslack.org
> Subject: [ARMedslack] Using a bootdisk to install armedslack on
> TrimSlice
> Message-ID: <5087E6DC.1090704 at zonnet.nl>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi all,
>
> I wanted to install armedslack 14.0 on my new TrimSlice, but didn't feel
> like setting up any (boot) servers. According to the wiki, the stock
> firmware looks for a boot.scr script file on an attached SD card,
> micro-SD or USB device, so I decided to use that method. Here are my steps:
>
> 1. You need the mkimage command from the u-boot toolkit. Install the
> u-boot-tools package from AlienBOB's repository.
>
> 2. Create a new text file called boot.cmd with the following content:
> ---------------------------------------------------------------
> # Slackware u-boot installation script. Create image with:
> # mkimage -A arm -O linux -T script -C none -d boot.cmd boot.scr
> setenv kerneladdr 0x00800000
> setenv initrdaddr 0x01100000
> setenv kernelfile /boot/uImage-tegra
> setenv initrdfile /boot/uinitrd-tegra.img
> #
> setenv loadinitrd ${fs}load ${interface} ${device} ${initrdaddr}
> ${initrdfile}
> setenv loadkernel ${fs}load ${interface} ${device} ${kerneladdr}
> ${kernelfile}
> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw
> setenv bootcmd bootm ${kerneladdr} ${initrdaddr}
> #
> run loadinitrd
> run loadkernel
> bootd
> ---------------------------------------------------------------
>
> 3. Create the script file as follows:
> mkimage -A arm -O linux -T script -C none -d boot.cmd boot.scr
>
> 4. Take an SD card or USB pendrive with an ext2/ext3/fat filesystem and
> enough room for the kernel and root fs. Create a new /boot directory on
> it. Copy the new boot.scr file to /boot.
>
> 5. From the ARM tree, copy isolinux/uinitrd-tegra.img and
> kernels/tegra/uImage-tegra to /boot.
>
> 6. Now insert the card/pendrive and start the TrimSlice. The default
> firmware will find the boot.scr file and execute it. This will load the
> slackware installer. I have my ARM tree on an external USB disk, so I
> installed from a pre-mounted directory.
>
> 7. Finish with the regular INSTALL_TEGRA.TXT instructions to setup u-boot.
>
> That's it. If your install device is large enough, you could put the ARM
> tree on that. My external HD has xfs, so I couldn't combine those steps.
> I tried to mount the SD card from the installer, but I couldn't get that
> to work. Maybe I did something wrong...
>
> NOTE: during the process, I upgraded the firmware to the latest 2012
> version. Big mistake; that version only works with the 3.5 kernel, so I
> couldn't boot. The 2010 firmware version works fine.
>
> Anyway, thought I would share this. Let me know what you think.
>
> regards,
> Frank Donkers.
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 26 Oct 2012 20:04:57 +0100
> From: Ottavio Caruso <pr0f3ss0r1492 at yahoo.com>
> To: ARMedslack at lists.armedslack.org
> Subject: Re: [ARMedslack] New Samsung Chromebook
> Message-ID:
> <CAEJNuHzTeRb=NY0ZEq=
> 9uQM2CFr+kE+AkrGTZ+yHEUVLOq4wDg at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 19 October 2012 10:42, Ottavio Caruso <pr0f3ss0r1492 at yahoo.com> wrote:
> > Does anybody know which ARM processor it has and if it can potentially
> > run Slackware ARM in a proper and easy way?
>
> Olof Johansson has just posted a way to install an alternative Linux
> distro on the new Chromebook:
> https://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ
>
> He has succeded with Suse just using the Suse root filesystem and the
> Chrome OS stock kernel. It looks like a complicated procedure (at
> least for me) and the catch is that it will boot from the Chrome
> partition, but I understand that he and other developers are working
> on booting from an external storage altogether.
>
> If anybody has any ideas on this subject they will do me a great
> favour. I have a limited budget. I was saving money to buy the new
> Genesi device which hasn't come yet but this little gem is tempting me
> now.
>
> --
> Ottavio Caruso
>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 28 Oct 2012 17:58:06 +0000 (GMT)
> From: Stuart Winter <m-lists at biscuit.org.uk>
> To: Slackware ARM port <armedslack at lists.armedslack.org>
> Subject: Re: [ARMedslack] fix for missing Xvnc in tightvnc
> Message-ID:
> <alpine.LNX.2.02.1210281757310.5654 at bourbon.biscuit.org.uk>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> hey Frank,
>
> [..]
> > With the help of xrdp and Xvnc I'm able to connect to my pi from any
> windows
> > pc without installing extra software. There are problems with
> international
> > keymaps, most of them patched for de layout in my version, thats not
> perfect,
> > but good enough for me.
>
> Thanks - I'll be putting out a patched package in 14.0 that contains Xvnc.
>
> --
> Stuart Winter
> Slackware ARM: www.armedslack.org
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 30 Oct 2012 06:46:41 +0000 (GMT)
> From: Davide <louigi600 at yahoo.it>
> To: Slackware ARM port <armedslack at lists.armedslack.org>
> Subject: Re: [ARMedslack] New Samsung Chromebook
> Message-ID:
> <1351579601.85320.YahooMailNeo at web29702.mail.ird.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
>
>
>
>
> ________________________________
>
> >> Does anybody know which ARM processor it has and if it can potentially
> >> run Slackware ARM in a proper and easy way?
> >
> >Olof Johansson has just posted a way to install an alternative Linux
> >distro on the new Chromebook:
> >ttps://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ
> >
> >He has succeded with Suse just using the Suse root filesystem and the
> >Chrome OS stock kernel. It looks like a complicated procedure (at
> >least for me) and the catch is that it will boot from the Chrome
> >partition, but I understand that he and other developers are working
> >on booting from an external storage altogether.
> >
> >If anybody has any ideas on this subject they will do me a great
> >favour. I have a limited budget. I was saving money to buy the new
> >Genesi device which hasn't come yet but this little gem is tempting me
> >now.
>
> Can't be much more difficult then any other arm platform:
> get a kernel that works for the hardware,
> get the tools to manipulate the kernel image so that the boot loader on
> the hardware will liad it (may need to package the initrd in there too),
> setup your initrd to look for whereever you plan to put the real root
> filesystem (that will contain whatever distro uou prefer)
> find a way of writing your boot image to the hardware (and root image if
> not on a removable media),
> cross your fingers and boot.
>
> Ciao
> David
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.armedslack.org/pipermail/armedslack/attachments/20121030/a4c70b9a/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>
>
> End of ARMedslack Digest, Vol 34, Issue 5
> *****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20121030/40ca48a9/attachment-0001.html>
More information about the ARMedslack
mailing list