Michael,

To answer your questions, no, I never updated the pi to enable 512MB ram,
it has always shown it at 512MB.  Stock RSEL doesn't work, but stock
Raspian does (I haven't tried Fedora yet, but I may yet).

As your question about what distributions I used, here's the whole story.
 I had several distros handy, but I knew off the bat that I wanted a RHEL
clone, so the very first one I did was RedSleeve.  Since this was my first
RPi, and I didn't technically know what constituted a "working" state, when
the RS image didn't work, I figured I'd need to try an "official" distro in
order to understand what a "working" state looked like.  After Raspian
booted up fine (thus confirming that the RPi was in fact fine), seeing what
a proper boot looked like, and I played around with it for a while, I
decided that it was time to go back to RedSleeve to see if I could get it
working.  But it continued to fail to boot, despite following the
directions to a 'T'.  So I decided to try the alternative steps of
migrating a Raspian image to a Redsleeve one, and lo and behold, that
worked!  so I thought, well, I guess that means there's just something up
with the Redsleeve image on the site.  So after getting RedSleeve installed
with the packages I wanted and everything, I decided to make a dd image of
it (since my plan is to get more RPis, and use this image on them).  After
making one, I used another flash card (same brand, same size) to test the
image on, and to my surprise, it didn't work??!?!!  That is what boggles my
mind, that this image isn't working, despite being created from a known
working card.

Thanks for updating the list packages with updated RHEL6 btw ;)


On Sun, Jan 13, 2013 at 10:13 AM, Michael Lang <[email protected]>wrote:

>  On 04/01/2013 03:54, Mark Campbell wrote:
> >* Hey guys, I have to say I am really appreciative of this project--I've*>* 
> >always been a hardcore RH guy, and when I finally got my pi, the very*>* 
> >first thing I did was to find out if there was a RH-based pi distro out*>* 
> >there.  Found that I could do Fedora, but like you, I did not want to*>* run 
> >bleeding edge, I wanted a stable distro, as I plan to make this pi*>* into 
> >something that needs to stay stable for months/years at a time.*>**>* When I 
> >first followed the directions on the site to install to an SD*>* card, which 
> >were quite straight forward (I love dd!), I put it in my*>* r-pi, and it 
> >would not post--no blinking lights indicating activity,*>* nothing.  So I 
> >backtracked, and did it with the raspian distro so that I*>* could actually 
> >get a feel for a working r-pi, and it booted fine.  So, I*>* tried again, 
> >and the image failed to boot.  Grr.  So I decided to follow*>* the steps to 
> >migrate from raspian to rsel.  Works.  Awesome.  However,*>* my plans 
> >require making this image to several other r-pis (when I get*>* them), so I 
> >used dd to make a complete image of the working sd card, and*>* when I 
> >tested putting it back onto a card, that image fails too!  Any*>* ideas 
> >guys?  It would sure be nice to not have to follow the steps of*>
> * converting a raspian to rsel each time.
>
> Hi Mark,
>
> did you run any other distribution before ? AND did you use rpi-update to 
> enable 512M of RAM ?
> I didn't and on my PI I can recreate that after flushing the PI to 512 stock 
> Images will not boot anymore (same behavior, only RedLED nothing else)
>
> Luckily I had an dd image of the Fedora one which I was running to test and 
> flush, I copied the '/boot' partition files to the RedSleeve 0.3 Image and
> everything started working. If you need those boot files let me know, I can 
> provide the 3.2.27 kernel boot files (and modules for RSEL6)
>
> I also worked out to get RedSleeve 0.3 working under QEMU-ARM with kernel 
> 3.2.27 (same for my PI) and started building an Koji Builder Farm to
> rebuild the EPEL (6) packages ... or at least starting with the most useful 
> (from my point of view) ones :)
>
> so far already completed  (both architectures armv6l and armv5tel)
>
> ncdu-1.8-1.armv5tel.armv6l.rpm
> bwm-ng-0.6-1.el6.armv6l.rpm
> mimedefang-2.73-1.el6.armv6l.rpm
> mimedefang-contrib-2.73-1.armv6l.rpm
> vanessa_socket-pipe-0.0.10-1.armv5tel.armv6l.rpm
> vanessa_socket-devel-0.0.10-1.armv5tel.armv6l.rpm
> vanessa_socket-0.0.10-1.armv5tel.armv6l.rpm
> perdition-bdb-1.18-1.armv5tel.armv6l.rpm
> perdition-postgresql-1.18-1.armv5tel.armv6l.rpm
> perdition-mysql-1.18-1.armv5tel.armv6l.rpm
> perdition-odbc-1.18-1.armv5tel.armv6l.rpm
> perdition-ldap-1.18-1.armv5tel.armv6l.rpm
> perdition-1.18-1.armv5tel.armv6l.rpm
> bacula-5.2.12-1.el6.armv6l.rpm
> bacula-postgresql-5.2.12-1.el6.armv6l.rpm
> bacula-sqlite-5.2.12-1.el6.armv6l.rpm
> bacula-mysql-5.2.12-1.el6.armv6l.rpm
> bacula-client-5.2.12-1.el6.armv6l.rpm
> bacula-director-5.2.12-1.el6.armv6l.rpm
> bacula-console-5.2.12-1.el6.armv6l.rpm
> bacula-storage-5.2.12-1.el6.armv6l.rpm
> vanessa_logger-sample-0.0.10-1.el6.armv6l.rpm
> vanessa_logger-devel-0.0.10-1.el6.armv6l.rpm
> vanessa_logger-0.0.10-1.el6.armv6l.rpm
> pkcs11-helper-1.07-5.el6.armv6l.rpm
> pkcs11-helper-devel-1.07-5.el6.armv6l.rpm
> vanessa_adt-0.0.9-1.el6.armv6l.rpm
> vanessa_adt-devel-0.0.9-1.el6.armv6l.rpm
> openvpn-2.2.2-1.el6.armv6l.rpm
> perl-Unix-Syslog-1.1-3.el6.armv6l.rpm
> sslh-1.14-2.el6.armv6l.rpm
> clamav-devel-0.97.6-1.el6.armv6l.rpm
> clamav-milter-0.97.6-1.el6.armv6l.rpm
> clamav-0.97.6-1.el6.armv6l.rpm
> clamav-db-0.97.6-1.el6.armv6l.rpm
> clamd-0.97.6-1.el6.armv6l.rpm
> pycdio-0.15-4.el6.armv6l.rpm
> vpnc-consoleuser-0.5.3-4.el6.armv6l.rpm
> vpnc-0.5.3-4.el6.armv6l.rpm
> mod_security-2.7.1-3.el6.armv6l.rpm
> mlogc-2.7.1-3.el6.armv6l.rpm
> iftop-1.0-0.1.pre2.el6.armv6l.rpm
> keepalived-1.2.7-1.el6.armv6l.rpm
> gparted-0.6.0-1.el6.armv6l.rpm
> imlib2-1.4.2-5.el6.armv6l.rpm
> imlib2-devel-1.4.2-5.el6.armv6l.rpm
> imlib2-id3tag-loader-1.4.2-5.el6.armv6l.rpm
> libnet-devel-1.1.5-1.el6.armv6l.rpm
> libnet-1.1.5-1.el6.armv6l.rpm
> heartbeat-libs-3.0.4-1.el6.armv6l.rpm
> heartbeat-devel-3.0.4-1.el6.armv6l.rpm
> heartbeat-3.0.4-1.el6.armv6l.rpm
> fluxbox-1.1.1-5.el6.armv6l.rpm
> *
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.redsleeve.org/mailman/listinfo/users
>
>


-- 
--Mark
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to