From gregg.drwho8 at gmail.com Sun Jan 6 21:35:27 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Sun, 6 Jan 2013 16:35:27 -0500 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images Message-ID: Hello! At the moment, I have just the SDTV capable set here (Standard Definition TV). I managed to get the other guy's image to work properly, and even tweaked things so I can see what the device is displaying properly. However when I try for example the complete image from Stanley Garvey's site, I get the response I'd expect to see on a regular system that of a kernel crash because it could not find a mount point for the root file system. I used the DD command to write things to the SDHC card using the form of (Without quotes) "#dd if= of=/dev/sde" and then waited a reasonable amount of time. I also tried it again adding the "bs=1M" and "bs=2M" to the command string. Is there any special, ah. magic to restoring these images to an 8Gig SDHC card? (Class 4 since that's the same type as the one that came with the device.) Incidentally I did not try the installer card image because it seems to be more with the HDTV present, and mine is waiting for an appropriate stand, ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Mon Jan 7 08:54:03 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Mon, 7 Jan 2013 08:54:03 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: References: Message-ID: <231699742-1357548845-cardhu_decombobulator_blackberry.rim.net-328412903-@b25.c14.bise7.blackberry> Hi Gregg Sounds like the image is corruped I will chk whn bck frm wrkM Did you see a krnel Panic? Can you mount the sdcard on your linux pc and see the ext4 fs? Refmt in digital camera Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Gregg Levine Sender: armedslack-bounces at lists.armedslack.orgDate: Sun, 6 Jan 2013 16:35:27 To: Reply-To: Slackware ARM port Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images Hello! At the moment, I have just the SDTV capable set here (Standard Definition TV). I managed to get the other guy's image to work properly, and even tweaked things so I can see what the device is displaying properly. However when I try for example the complete image from Stanley Garvey's site, I get the response I'd expect to see on a regular system that of a kernel crash because it could not find a mount point for the root file system. I used the DD command to write things to the SDHC card using the form of (Without quotes) "#dd if= of=/dev/sde" and then waited a reasonable amount of time. I also tried it again adding the "bs=1M" and "bs=2M" to the command string. Is there any special, ah. magic to restoring these images to an 8Gig SDHC card? (Class 4 since that's the same type as the one that came with the device.) Incidentally I did not try the installer card image because it seems to be more with the HDTV present, and mine is waiting for an appropriate stand, ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From stanley at stanleygarvey.com Mon Jan 7 11:56:30 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Mon, 7 Jan 2013 11:56:30 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: References: Message-ID: <478894725-1357559792-cardhu_decombobulator_blackberry.rim.net-1851781750-@b25.c14.bise7.blackberry> Tweek cmdline.txt to point partion 3 mmcblk0p3. Sorry about that we have been runnig 16gb at home. Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Gregg Levine Sender: armedslack-bounces at lists.armedslack.orgDate: Sun, 6 Jan 2013 16:35:27 To: Reply-To: Slackware ARM port Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images Hello! At the moment, I have just the SDTV capable set here (Standard Definition TV). I managed to get the other guy's image to work properly, and even tweaked things so I can see what the device is displaying properly. However when I try for example the complete image from Stanley Garvey's site, I get the response I'd expect to see on a regular system that of a kernel crash because it could not find a mount point for the root file system. I used the DD command to write things to the SDHC card using the form of (Without quotes) "#dd if= of=/dev/sde" and then waited a reasonable amount of time. I also tried it again adding the "bs=1M" and "bs=2M" to the command string. Is there any special, ah. magic to restoring these images to an 8Gig SDHC card? (Class 4 since that's the same type as the one that came with the device.) Incidentally I did not try the installer card image because it seems to be more with the HDTV present, and mine is waiting for an appropriate stand, ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From gregg.drwho8 at gmail.com Mon Jan 7 15:03:47 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Mon, 7 Jan 2013 10:03:47 -0500 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: <231699742-1357548845-cardhu_decombobulator_blackberry.rim.net-328412903-@b25.c14.bise7.blackberry> References: <231699742-1357548845-cardhu_decombobulator_blackberry.rim.net-328412903-@b25.c14.bise7.blackberry> Message-ID: On Mon, Jan 7, 2013 at 3:54 AM, wrote: > Hi Gregg > Sounds like the image is corruped I will chk whn bck frm wrkM > Did you see a krnel Panic? > Can you mount the sdcard on your linux pc and see the ext4 fs? > Refmt in digital camera > Sent from my BlackBerry smartphone from Virgin Media > > -----Original Message----- > From: Gregg Levine > Sender: armedslack-bounces at lists.armedslack.orgDate: Sun, 6 Jan 2013 16:35:27 > To: > Reply-To: Slackware ARM port > Subject: [ARMedslack] Problems with making use of existing Slackware on ARM > for Raspberry PI images > > Hello! > At the moment, I have just the SDTV capable set here (Standard > Definition TV). I managed to get the other guy's image to work > properly, and even tweaked things so I can see what the device is > displaying properly. However when I try for example the complete image > from Stanley Garvey's site, I get the response I'd expect to see on a > regular system that of a kernel crash because it could not find a > mount point for the root file system. > > I used the DD command to write things to the SDHC card using the form > of (Without quotes) "#dd if= of=/dev/sde" and then waited a > reasonable amount of time. I also tried it again adding the "bs=1M" > and "bs=2M" to the command string. > > Is there any special, ah. magic to restoring these images to an 8Gig > SDHC card? (Class 4 since that's the same type as the one that came > with the device.) > > Incidentally I did not try the installer card image because it seems > to be more with the HDTV present, and mine is waiting for an > appropriate stand, > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > _______________________________________________ > 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 Hello! Yes to the first three. But no to the last. No camera here who uses those things. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Mon Jan 7 15:55:49 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 07 Jan 2013 15:55:49 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: References: <231699742-1357548845-cardhu_decombobulator_blackberry.rim.net-328412903-@b25.c14.bise7.blackberry> Message-ID: <20130107155549.95F4514182C6@bmail06.one.com> On Jan 7, 2013 15:03 "Gregg Levine" wrote: > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > Hi Gregg > > Sounds like the image is corruped I will chk whn bck frm wrkM > > Did you see a krnel Panic? > > Can you mount the sdcard on your linux pc and see the ext4 fs? > > Refmt in digital camera > > Sent from my BlackBerry smartphone from Virgin Media > > > > -----Original Message----- > > From: Gregg Levine > > ______________________________________________ > > snip > > -------------------------------------------------------------------- > > ------------- > > > Hello! > Yes to the first three. But no to the last. No camera here who uses > those things. > > > ----- > Gregg C Levine > "This signature fought the Time Wars, time and again." > > Gregg, > I have just downloaded SlackwareArm-14.0-8GB-20121201.zip unzipped it > re-flashed to a sandisk 8GB class 4 card like so: > bash-4.1# dd if=SlackwareArm-14.0-8GB-20121201.img of=/dev/sdc > bs=65536 > 123056+0 records in > 123056+0 records out > 8064598016 bytes (8.1 GB) copied, 1862.39 s, 4.3 MB/s > > (your /dev/sd?) will depend on your set up) > It booted fine. I can't reproduce the error. > I had suspected that I had got the /boot/cmdline.txt wrong, but it is > correct > Can you give me more details, what does the kernel say? > Did you download it from stanleygarvey.com/Slackberry/download.php or > via rsync or ftp (the files should all be identical). > regards > Stanley. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Mon Jan 7 15:58:34 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Mon, 7 Jan 2013 10:58:34 -0500 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: <20130107155549.95F4514182C6@bmail06.one.com> References: <231699742-1357548845-cardhu_decombobulator_blackberry.rim.net-328412903-@b25.c14.bise7.blackberry> <20130107155549.95F4514182C6@bmail06.one.com> Message-ID: On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey wrote: > On Jan 7, 2013 15:03 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > Hi Gregg > Sounds like the image is corruped I will chk whn bck frm wrkM > Did you see a krnel Panic? > Can you mount the sdcard on your linux pc and see the ext4 fs? > Refmt in digital camera > Sent from my BlackBerry smartphone from Virgin Media > > -----Original Message----- > From: Gregg Levine > ______________________________________________ > snip > --------------------------------------------------------------------------------- > > Hello! > Yes to the first three. But no to the last. No camera here who uses > those things. > > > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > > Gregg, > I have just downloaded SlackwareArm-14.0-8GB-20121201.zip unzipped it > re-flashed to a sandisk 8GB class 4 card like so: > bash-4.1# dd if=SlackwareArm-14.0-8GB-20121201.img of=/dev/sdc bs=65536 > 123056+0 records in > 123056+0 records out > 8064598016 bytes (8.1 GB) copied, 1862.39 s, 4.3 MB/s > > (your /dev/sd?) will depend on your set up) > It booted fine. I can't reproduce the error. > I had suspected that I had got the /boot/cmdline.txt wrong, but it is > correct > Can you give me more details, what does the kernel say? > Did you download it from stanleygarvey.com/Slackberry/download.php or via > rsync or ftp (the files should all be identical). > regards > Stanley. Hello! I think from Rsync function. I'll retrieve it again and from your website. I'll know more later. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Mon Jan 7 19:29:35 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 07 Jan 2013 19:29:35 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: References: <20130107155549.95F4514182C6@bmail06.one.com> Message-ID: <20130107192935.2346FA0808307@bmail02.one.com> On Jan 7, 2013 15:58 "Gregg Levine" wrote: > On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey > wrote: > > On Jan 7, 2013 15:03 "Gregg Levine" wrote: > > > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > > > > Hello! > I think from Rsync function. I'll retrieve it again and from your > website. I'll know more later. > > Hi, just checked all files are identical: > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip > (local copy) > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip > (Danish server powered by windmills) > > Suggest you re-download the zip file and do: > md5sum SlackwareArm-14.0-8GB-20121201.zip > to check integrity. > regards > Stanley. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Mon Jan 7 20:15:01 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Mon, 7 Jan 2013 15:15:01 -0500 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: <20130107192935.2346FA0808307@bmail02.one.com> References: <20130107155549.95F4514182C6@bmail06.one.com> <20130107192935.2346FA0808307@bmail02.one.com> Message-ID: On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey wrote: > On Jan 7, 2013 15:58 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey > wrote: > > On Jan 7, 2013 15:03 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > > Hello! > I think from Rsync function. I'll retrieve it again and from your > website. I'll know more later. > > Hi, just checked all files are identical: > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (local > copy) > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (Danish > server powered by windmills) > > Suggest you re-download the zip file and do: > md5sum SlackwareArm-14.0-8GB-20121201.zip > to check integrity. > regards > Stanley. Hello! Now it is getting baroque, I just ran the command against both a new file (downloaded today) and one that did cause the problems. The command returns the same hash codes. I'll try again momentarily. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Mon Jan 7 20:31:05 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 07 Jan 2013 20:31:05 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: References: <20130107192935.2346FA0808307@bmail02.one.com> Message-ID: <20130107203105.A4494D07BFC27@bmail03.one.com> On Jan 7, 2013 20:15 "Gregg Levine" wrote: > On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey > wrote: > > On Jan 7, 2013 15:58 "Gregg Levine" wrote: > > > > On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey > > wrote: > > > > On Jan 7, 2013 15:03 "Gregg Levine" wrote: > > > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > > > > > Hello! > > I think from Rsync function. I'll retrieve it again and from your > > website. I'll know more later. > > > > Hi, just checked all files are identical: > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip > > (local > > copy) > > > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip > > (Danish > > server powered by windmills) > > > > Suggest you re-download the zip file and do: > > md5sum SlackwareArm-14.0-8GB-20121201.zip > > to check integrity. > > regards > > Stanley. > > Hello! > Now it is getting baroque, I just ran the command against both a new > file (downloaded today) and one that did cause the problems. The > command returns the same hash codes. > > I'll try again momentarily. > ----- > Gregg C Levine > "This signature fought the Time Wars, time and again." > > Blimey, I like baroque, somethings obviously baroque, but I cant think > what it can be, if you live in Warwickshire I would cycle around and > fix it for you! I Guess you don't? are you confusing a kernel panic > will the annoying message from Pat regarding the file system being > read/write? try pressing enter. > With kind regards, > Stanley. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Mon Jan 7 20:37:54 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Mon, 7 Jan 2013 15:37:54 -0500 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: <20130107203105.A4494D07BFC27@bmail03.one.com> References: <20130107192935.2346FA0808307@bmail02.one.com> <20130107203105.A4494D07BFC27@bmail03.one.com> Message-ID: On Mon, Jan 7, 2013 at 3:31 PM, stanley garvey wrote: > On Jan 7, 2013 20:15 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey > wrote: > > On Jan 7, 2013 15:58 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey > wrote: > > On Jan 7, 2013 15:03 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > > Hello! > I think from Rsync function. I'll retrieve it again and from your > website. I'll know more later. > > Hi, just checked all files are identical: > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (local > copy) > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (Danish > server powered by windmills) > > Suggest you re-download the zip file and do: > md5sum SlackwareArm-14.0-8GB-20121201.zip > to check integrity. > regards > Stanley. > > > Hello! > Now it is getting baroque, I just ran the command against both a new > file (downloaded today) and one that did cause the problems. The > command returns the same hash codes. > > I'll try again momentarily. > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > > Blimey, I like baroque, somethings obviously baroque, but I cant think what > it can be, if you live in Warwickshire I would cycle around and fix it for > you! I Guess you don't? are you confusing a kernel panic will the annoying > message from Pat regarding the file system being read/write? try pressing > enter. > With kind regards, > Stanley. Hello! I see your point. I really do. This is indeed a kernel panic as the system starts to panic when it can't find and mount the root file system. Not the classic one regarding the file system being read/write. But I'll try again and see what happens next. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Mon Jan 7 21:09:54 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 07 Jan 2013 21:09:54 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: References: <20130107203105.A4494D07BFC27@bmail03.one.com> Message-ID: <20130107210954.3B0DB2F112080@bmail-n01.one.com> On Jan 7, 2013 20:37 "Gregg Levine" wrote: > On Mon, Jan 7, 2013 at 3:31 PM, stanley garvey > wrote: > > On Jan 7, 2013 20:15 "Gregg Levine" wrote: > > > > On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey > > wrote: > > > > On Jan 7, 2013 15:58 "Gregg Levine" wrote: > > > > On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey > > wrote: > > > > On Jan 7, 2013 15:03 "Gregg Levine" wrote: > > > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > > > > > Hello! > > I think from Rsync function. I'll retrieve it again and from your > > website. I'll know more later. > > > > Hi, just checked all files are identical: > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip > > (local > > copy) > > > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip > > (Danish > > server powered by windmills) > > > > Suggest you re-download the zip file and do: > > md5sum SlackwareArm-14.0-8GB-20121201.zip > > to check integrity. > > regards > > Stanley. > > > > > > Hello! > > Now it is getting baroque, I just ran the command against both a new > > file (downloaded today) and one that did cause the problems. The > > command returns the same hash codes. > > > > I'll try again momentarily. > > ----- > > Gregg C Levine > > "This signature fought the Time Wars, time and again." > > > > Blimey, I like baroque, somethings obviously baroque, but I cant > > think what > > it can be, if you live in Warwickshire I would cycle around and fix > > it for > > you! I Guess you don't? are you confusing a kernel panic will the > > annoying > > message from Pat regarding the file system being read/write? try > > pressing > > enter. > > With kind regards, > > Stanley. > > Hello! > I see your point. I really do. This is indeed a kernel panic as the > system starts to panic when it can't find and mount the root file > system. Not the classic one regarding the file system being > read/write. > > But I'll try again and see what happens next. > ----- > Gregg C Levine > "This signature fought the Time Wars, time and again." > OK I.m going to put a cold poltice on my forehead and retire, > listening to Bach's fantasia and fuge in D minor. good night and good > luck > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Wed Jan 9 21:49:44 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Wed, 09 Jan 2013 21:49:44 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: <20130107210954.3B0DB2F112080@bmail-n01.one.com> References: <20130107210954.3B0DB2F112080@bmail-n01.one.com> Message-ID: <20130109214944.289B1CAD7B06B@bmail03.one.com> On Jan 7, 2013 21:09 "stanley garvey" wrote: > On Jan 7, 2013 20:37 "Gregg Levine" wrote: > > > On Mon, Jan 7, 2013 at 3:31 PM, stanley garvey > > wrote: > > > On Jan 7, 2013 20:15 "Gregg Levine" > > > wrote: > > > > > > On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey > > > wrote: > > > > > > On Jan 7, 2013 15:58 "Gregg Levine" > > > wrote: > > > > > > On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey > > > wrote: > > > > > > On Jan 7, 2013 15:03 "Gregg Levine" > > > wrote: > > > > > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > > > > > > > > Hello! > > > I think from Rsync function. I'll retrieve it again and from your > > > website. I'll know more later. > > > > > > Hi, just checked all files are identical: > > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > > > 1dd852334977d734e5ff833ecacface9 > > > SlackwareArm-14.0-8GB-20121201.zip (local > > > copy) > > > > > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > > > 1dd852334977d734e5ff833ecacface9 > > > SlackwareArm-14.0-8GB-20121201.zip (Danish > > > server powered by windmills) > > > > > > Suggest you re-download the zip file and do: > > > md5sum SlackwareArm-14.0-8GB-20121201.zip > > > to check integrity. > > > regards > > > Stanley. > > > > > > > > > Hello! > > > Now it is getting baroque, I just ran the command against both a > > > new > > > file (downloaded today) and one that did cause the problems. The > > > command returns the same hash codes. > > > > > > I'll try again momentarily. > > > ----- > > > Gregg C Levine > > > "This signature fought the Time Wars, time and again." > > > > > > Blimey, I like baroque, somethings obviously baroque, but I cant > > > think what > > > it can be, if you live in Warwickshire I would cycle around and > > > fix it for > > > you! I Guess you don't? are you confusing a kernel panic will the > > > annoying > > > message from Pat regarding the file system being read/write? try > > > pressing > > > enter. > > > With kind regards, > > > Stanley. > > > > Hello! > > I see your point. I really do. This is indeed a kernel panic as the > > system starts to panic when it can't find and mount the root file > > system. Not the classic one regarding the file system being > > read/write. > > > > But I'll try again and see what happens next. > > > > Let me Know, as I have spent the last day testing the Image on 4 > > Raspberry PI boards 2x revision 1 256 mb and 2 x revision 2 512mb > > boards all 2x2 from RS 2x2 From farnell and I can still not > > replicate the error. Normally a kernel panic of the type you desribe > > is caused by the kernel modules for the ext4 fs not being loaded. > > The kernel provided requires no modules to boot, all FS modules > > being built in, you can even use the image as an installer, just > > uncomment the lines in config.txt relating to the initrd. > > I am starting to think that your sd card is clobbered, why not try > > to retrive the image with dd and then compare it with the file you > > wrote to the card? > > As for the difference with sdtv and hdtv all can be set in the > > config.txt I have tested the image on old tellys, monitors (using a > > hdmi to vga adaptor) both wide and 4:3 and HDTVs and all works as > > expected HDTV is better SDTV is a little crampt. > > once again good luck. > > Regards > > Stanley > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Wed Jan 9 22:13:00 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Wed, 9 Jan 2013 17:13:00 -0500 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: <20130109214944.289B1CAD7B06B@bmail03.one.com> References: <20130107210954.3B0DB2F112080@bmail-n01.one.com> <20130109214944.289B1CAD7B06B@bmail03.one.com> Message-ID: On Wed, Jan 9, 2013 at 4:49 PM, stanley garvey wrote: > > > On Jan 7, 2013 21:09 "stanley garvey" wrote: > > On Jan 7, 2013 20:37 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 3:31 PM, stanley garvey > wrote: > > On Jan 7, 2013 20:15 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey > wrote: > > On Jan 7, 2013 15:58 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey > wrote: > > On Jan 7, 2013 15:03 "Gregg Levine" wrote: > > On Mon, Jan 7, 2013 at 3:54 AM, wrote: > > > Hello! > I think from Rsync function. I'll retrieve it again and from your > website. I'll know more later. > > Hi, just checked all files are identical: > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (local > copy) > > bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip > 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (Danish > server powered by windmills) > > Suggest you re-download the zip file and do: > md5sum SlackwareArm-14.0-8GB-20121201.zip > to check integrity. > regards > Stanley. > > > Hello! > Now it is getting baroque, I just ran the command against both a new > file (downloaded today) and one that did cause the problems. The > command returns the same hash codes. > > I'll try again momentarily. > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > > Blimey, I like baroque, somethings obviously baroque, but I cant think what > it can be, if you live in Warwickshire I would cycle around and fix it for > you! I Guess you don't? are you confusing a kernel panic will the annoying > message from Pat regarding the file system being read/write? try pressing > enter. > With kind regards, > Stanley. > > > Hello! > I see your point. I really do. This is indeed a kernel panic as the > system starts to panic when it can't find and mount the root file > system. Not the classic one regarding the file system being > read/write. > > But I'll try again and see what happens next. > > Let me Know, as I have spent the last day testing the Image on 4 Raspberry > PI boards 2x revision 1 256 mb and 2 x revision 2 512mb boards all 2x2 from > RS 2x2 From farnell and I can still not replicate the error. Normally a > kernel panic of the type you desribe is caused by the kernel modules for the > ext4 fs not being loaded. The kernel provided requires no modules to boot, > all FS modules being built in, you can even use the image as an installer, > just uncomment the lines in config.txt relating to the initrd. > I am starting to think that your sd card is clobbered, why not try to > retrive the image with dd and then compare it with the file you wrote to the > card? > As for the difference with sdtv and hdtv all can be set in the config.txt I > have tested the image on old tellys, monitors (using a hdmi to vga adaptor) > both wide and 4:3 and HDTVs and all works as expected HDTV is better SDTV is > a little crampt. > once again good luck. > Regards > Stanley Hello! Interesting thought. So what did you use for both making your images? And then writing them to SD cards? -- ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Wed Jan 9 22:45:33 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Wed, 09 Jan 2013 22:45:33 +0000 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: References: <20130109214944.289B1CAD7B06B@bmail03.one.com> Message-ID: <20130109224533.24DB6D1E19FD3@bmail03.one.com> > Hello! > Interesting thought. > > So what did you use for both making your images? And then writing them > to SD cards? > OKay, I followed David Spencers suggestion for the SD-card format, see > also this article https://lwn.net/Articles/428584/ > I then recompiled a Raspberry-pi Kernel with initrd support as the > stock kernels do not come with initrd support enabled by default, bit > of a bodge, then saved the kernel modules and kernel source elsewhere > as the modules will be overwritten by the install. > rebooted and did a regular install over nfs. > copyed back the kernel source, did make _modules_install. To recreate > the modules, > Put the Kernel source in /usr/src/kernel-whatever made the historic > symlink to it ln -s /usr/src/kernel-whatever > Removed the shh keys in /etc/ssh Both Public and Private (You dont't > what my keys) > Remove /etc/udev/70-persistent.net-rules > dd if=/my/image of=/myfilename > > Does that help? > Regards Stanley. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmdebruin at xmsnet.nl Wed Jan 9 17:54:33 2013 From: jmdebruin at xmsnet.nl (Hans de Bruin) Date: Wed, 09 Jan 2013 18:54:33 +0100 Subject: [ARMedslack] file permissions php session directory wrong? Message-ID: <50EDAED9.40705@xmsnet.nl> There is a difference in file permissions of /var/lib/php/ between slack and armed slack: slack 14 # ls -ld /var/lib/php drwxrwx--- 1 root apache 0 Sep 14 22:21 /var/lib/php/ armedslack 14 # ls -ld /var/lib/php drwxr-x--- 1 root apache 0 Sep 16 11:20 /var/lib/php/ ^ I ran in to this when owncloud could not create php-session files on my raspberrypi -- Hans From m-lists at biscuit.org.uk Wed Jan 9 23:03:04 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 9 Jan 2013 23:03:04 +0000 (GMT) Subject: [ARMedslack] file permissions php session directory wrong? In-Reply-To: <50EDAED9.40705@xmsnet.nl> References: <50EDAED9.40705@xmsnet.nl> Message-ID: > There is a difference in file permissions of /var/lib/php/ between slack and > armed slack: [..] Thanks Hans, I know why that is. I'll put out a patch package for 14.0 & a -current update soon. -- Stuart Winter Slackware ARM: www.armedslack.org From gregg.drwho8 at gmail.com Wed Jan 9 22:52:42 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Wed, 9 Jan 2013 17:52:42 -0500 Subject: [ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images In-Reply-To: <20130109224533.24DB6D1E19FD3@bmail03.one.com> References: <20130109214944.289B1CAD7B06B@bmail03.one.com> <20130109224533.24DB6D1E19FD3@bmail03.one.com> Message-ID: On Wed, Jan 9, 2013 at 5:45 PM, stanley garvey wrote: > > > Hello! > Interesting thought. > > So what did you use for both making your images? And then writing them > to SD cards? > OKay, I followed David Spencers suggestion for the SD-card format, see also > this article https://lwn.net/Articles/428584/ > I then recompiled a Raspberry-pi Kernel with initrd support as the stock > kernels do not come with initrd support enabled by default, bit of a bodge, > then saved the kernel modules and kernel source elsewhere as the modules > will be overwritten by the install. > rebooted and did a regular install over nfs. > copyed back the kernel source, did make _modules_install. To recreate the > modules, > Put the Kernel source in /usr/src/kernel-whatever made the historic symlink > to it ln -s /usr/src/kernel-whatever > Removed the shh keys in /etc/ssh Both Public and Private (You dont't what my > keys) > Remove /etc/udev/70-persistent.net-rules > dd if=/my/image of=/myfilename > > Does that help? > Regards Stanley. Hello! Much better. Thank you! ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Sun Jan 13 21:31:15 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sun, 13 Jan 2013 21:31:15 +0000 Subject: [ARMedslack] BCM2835 what -march to use? Message-ID: <20130113213115.23C27530CE4BC@bmail-n01.one.com> Hi I am currently recompiling slackwarearm for the BCM2835 SOC. I am using -'march=native' this is fine for 'native builds' however if I want to use a xcompiler this is no good. would '-march=armv6 -mtune=arm1176jzf-s' be ok? or am I missing something. I have googled around for a while and have no definitive answers.What is the best -march name for an arm1176-jzf-s CPU, could someone please explain the suffixes. example `armv6', `armv6j', `armv6t2', `armv6z', `armv6zk', `armv6-m' regards. Stanley -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sat Jan 19 15:10:17 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 19 Jan 2013 15:10:17 +0000 (GMT) Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: <20130113213115.23C27530CE4BC@bmail-n01.one.com> References: <20130113213115.23C27530CE4BC@bmail-n01.one.com> Message-ID: > I am currently recompiling slackwarearm for the BCM2835 SOC. I am using > -'march=native' this is fine for 'native builds' however if I want to > use a xcompiler this is no good. would '-march=armv6 > -mtune=arm1176jzf-s' be ok? or am I missing something. I have googled > around for a while and have no definitive answers.What is the best > -march name for an arm1176-jzf-s CPU, could someone please explain the > suffixes. example `armv6', `armv6j', `armv6t2', `armv6z', `armv6zk', > `armv6-m' Well, this is the same CPU as the Raspberry, so check what everyone else's using for the RPI. -- Stuart Winter Slackware ARM: www.armedslack.org From gregg.drwho8 at gmail.com Sat Jan 19 15:20:52 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Sat, 19 Jan 2013 10:20:52 -0500 Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: References: <20130113213115.23C27530CE4BC@bmail-n01.one.com> Message-ID: On Sat, Jan 19, 2013 at 10:10 AM, Stuart Winter wrote: > >> I am currently recompiling slackwarearm for the BCM2835 SOC. I am using >> -'march=native' this is fine for 'native builds' however if I want to >> use a xcompiler this is no good. would '-march=armv6 >> -mtune=arm1176jzf-s' be ok? or am I missing something. I have googled >> around for a while and have no definitive answers.What is the best >> -march name for an arm1176-jzf-s CPU, could someone please explain the >> suffixes. example `armv6', `armv6j', `armv6t2', `armv6z', `armv6zk', >> `armv6-m' > > Well, this is the same CPU as the Raspberry, so check what everyone else's > using for the RPI. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org Hello! I quite agree folks. For some embedded environments the kernel (or any programming) is rarely built on the native platform. The builders, (you Stuart, yourself Stanley, or myself) would use a properly setup cross compiling environment. The big problem is setting the appropriate switches. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From m-lists at biscuit.org.uk Sat Jan 19 15:28:48 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 19 Jan 2013 15:28:48 +0000 (GMT) Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: References: <20130113213115.23C27530CE4BC@bmail-n01.one.com> Message-ID: > For some embedded environments the kernel (or any programming) is > rarely built on the native platform. The builders, (you Stuart, > yourself Stanley, or myself) would use a properly setup cross > compiling environment. All of Slackware ARM is built natively, using distcc to several x86 cores with the cross compiler. Cross compiling is problematic when the package wants to build against a particular library that's existant on the host which can be worked around but it's a lot of effort to maintain build scripts that produce what you're looking for in a package when x-compiling. > The big problem is setting the appropriate switches. Once you know what systems you're targetting, it's easy. -- Stuart Winter Slackware ARM: www.armedslack.org From stanley at stanleygarvey.com Sat Jan 19 15:49:46 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 19 Jan 2013 15:49:46 +0000 Subject: [ARMedslack] BCM2835 what -march to use? References: Message-ID: <20130119154946.6C86378A27055@bmail02.one.com> On Jan 19, 2013 15:47 "stanley garvey" wrote: > On Jan 19, 2013 15:28 "Stuart Winter" wrote: > > > > For some embedded environments the kernel (or any programming) is > > > rarely built on the native platform. The builders, (you Stuart, > > > yourself Stanley, or myself) would use a properly setup cross > > > compiling environment. > > > > All of Slackware ARM is built natively, using distcc to several x86 > > cores > > with the cross compiler. Cross compiling is problematic when the > > package > > wants to build against a particular library that's existant on the > > host > > which can be worked around but it's a lot of effort to maintain > > build > > scripts that produce what you're looking for in a package when > > x-compiling. > > > > > The big problem is setting the appropriate switches. > > > > Once you know what systems you're targetting, it's easy. > > > > Thanks for the reply, I must have been asking google the wrong > > question. asking what gcc flags to use put me right, most others are > > using -march=armv6j. > > I prefer to compile nativley, however mozilla-firefox compiled for 3 > > days the got stuck with ld in deep sleep 98%wait. > > so I might want to x-compile that one. Thanks for the great slackit! > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sat Jan 19 16:08:18 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 19 Jan 2013 16:08:18 +0000 (GMT) Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: <20130119154946.6C86378A27055@bmail02.one.com> References: <20130119154946.6C86378A27055@bmail02.one.com> Message-ID: Can you sort out your mail client? I'm not sure what's happened here - you have replied to a mail that you never sent? It's taxing my poor brain for moments in order to determine what you're quoting and what's fresh. [..] > > > using -march=armv6j. > > > I prefer to compile nativley, however mozilla-firefox compiled for 3 > > > days the got stuck with ld in deep sleep 98%wait. > > > so I might want to x-compile that one. Thanks for the great slackit! I don't cross compile it and it works for me - takes an hour or less to build, IIRC. Perhaps you don't have enough RAM on your machine? -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Sat Jan 19 16:13:20 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 19 Jan 2013 16:13:20 +0000 (GMT) Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: References: <20130119154946.6C86378A27055@bmail02.one.com> Message-ID: btw for clarification when I say cross compiling, I mean cross compiling proper - building entirely on a machine other than the target. What I do with distcc is *building* natively, with *some* of the code being compiled on a host that happens to be an x86 with the exact same toolchain as natively. There are only prisere [slackwarearm-current] # find . -type f -name '.no*distcc*' | wc -l 26 That aren't built with distcc, as they fail for what ever reason, but build natively. > > Can you sort out your mail client? I'm not sure what's happened here - > you have replied to a mail that you never sent? > It's taxing my poor brain for moments in order to determine what you're > quoting and what's fresh. > > [..] > > > > using -march=armv6j. > > > > I prefer to compile nativley, however mozilla-firefox compiled for 3 > > > > days the got stuck with ld in deep sleep 98%wait. > > > > so I might want to x-compile that one. Thanks for the great slackit! > > I don't cross compile it and it works for me - takes an hour or less to > build, IIRC. Perhaps you don't have enough RAM on your machine? > > -- Stuart Winter Slackware ARM: www.armedslack.org From atelszewski at gmail.com Sat Jan 19 20:19:17 2013 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 19 Jan 2013 21:19:17 +0100 Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: References: <20130113213115.23C27530CE4BC@bmail-n01.one.com> Message-ID: <50FAFFC5.9080606@gmail.com> On 01/19/2013 04:20 PM, Gregg Levine wrote: > For some embedded environments the kernel (or any programming) is > rarely built on the native platform. The builders, (you Stuart, > yourself Stanley, or myself) would use a properly setup cross > compiling environment. > > The big problem is setting the appropriate switches. Cross compiling the kernel is the most trivial part of the cross compilation. You need only to set the ARCH= and CROSS_COMPILE= variables and have the cross toolchain installed and accessible in the path. I have never had troubles with this part and it is really, really handy to build the kernel in the host machine with cross toolchain when you develop some driver or want to try out different kernel configs. And especially if you have your target (native) machine set to boot the kernel over NFS, the "config, build and try" procedure is as simple as configuring and building the kernel and then rebooting the target machine. It's a real time saver. -- Best regards, Andrzej Telszewski From stanley at stanleygarvey.com Fri Jan 25 22:13:36 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 25 Jan 2013 22:13:36 +0000 Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: References: Message-ID: <20130125221336.8ED0817523D17@bmail-n01.one.com> On Jan 19, 2013 16:13 "Stuart Winter" wrote: > btw for clarification when I say cross compiling, I mean cross > compiling > proper - building entirely on a machine other than the target. > What I do with distcc is *building* natively, with *some* of the > code being compiled on a host that happens to be an x86 with the exact > same toolchain as natively. There are only > > prisere [slackwarearm-current] # find . -type f -name '.no*distcc*' | > wc -l > 26 > > That aren't built with distcc, as they fail for what ever reason, but > build natively. > > > > > Can you sort out your mail client? I'm not sure what's happened here > > - > > you have replied to a mail that you never sent? > > It's taxing my poor brain for moments in order to determine what > > you're > > quoting and what's fresh. > > > > [..] > > > > > using -march=armv6j. > > > > > I prefer to compile nativley, however mozilla-firefox compiled > > > > > for 3 > > > > > days the got stuck with ld in deep sleep 98%wait. > > > > > so I might want to x-compile that one. Thanks for the great > > > > > slackit! > > > > I don't cross compile it and it works for me - takes an hour or less > > to > > build, IIRC. Perhaps you don't have enough RAM on your machine? > > > > Sorry about The Email client, it's web based, and very poor, I run > > my own mail server and prefer mutt, but Sorbs have blocked me : > > Name: Stanley Garvey > > IP/Host: 81.111.128.0/17 > > IP: 81.111.194.105 > > DNS: NXDOMAIN > > DNS TTL: -1 > > DNS Info is cached: No > > Additional Information: > > My response: > > Remove 81.111.128.105 from your database. I run my own mail-server. > > You have no legal right to blacklist this address. please provide > > reasons for blacklisting this address. > > Thank you. > > > > Anyway still rebuilding your packages for armv6j -mpu=vfp > > -mfloat-abi=softfp -mtune=arm1176jzf-f. > > can't get aspell to compile, Needed to patch fuse with #define > > _GNU_SOURCE. > > Also needed to upgrade to /a/usbutils.006 as source not in > > slackware64 > > Kind regards. > > Stanley > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jan 25 22:56:09 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 25 Jan 2013 22:56:09 +0000 (GMT) Subject: [ARMedslack] BCM2835 what -march to use? In-Reply-To: <20130125221336.8ED0817523D17@bmail-n01.one.com> References: <20130125221336.8ED0817523D17@bmail-n01.one.com> Message-ID: > > Anyway still rebuilding your packages for armv6j -mpu=vfp > > -mfloat-abi=softfp -mtune=arm1176jzf-f. > > can't get aspell to compile, Needed to patch fuse with #define > > _GNU_SOURCE. Yes as the toolchain changes there will always be something that won't build. > > Also needed to upgrade to /a/usbutils.006 as source not in > > slackware64 ls slackware64-current/source/a/usbutils/ slack-desc usbutils-006.tar.xz usbutils.SlackBuild* usbutils.url -- Stuart Winter Slackware ARM: www.armedslack.org From gregg.drwho8 at gmail.com Fri Jan 25 23:34:05 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Fri, 25 Jan 2013 18:34:05 -0500 Subject: [ARMedslack] First boot on Raspberry PI for Slackware 14.0 for ARM Message-ID: Hello! Okay group I just brought up the Slackware 14.0 for the Raspberry pi image available on Stanley Garvey's site. Aside from one nit, the device almost arbitrarily changed the eth0 setting to eth1 for reasons it did not clearly explain. Everything worked correctly from that one on. However how do I go about changing from UK keyboard to something resembling a US one? In this case Stanley I borrowed my screen from a (what else?) system running Slackware-13.37 and connected to it the HDMI cable via a HDMI-DVI adapter that I bought today. Earlier I also bought an 8 Gigabyte card on sale from Staples and used an image writing tool from that system to write things out. And then connected everything from there. It came up exactly as expected. Except for that one nit concerning the Ethernet device swap. I once saw that happen on an Intel system I was trying to revive and knew where to fix things. But here? No I don't. I have the installer based image that David Spencer made up and with that and the screen I'll probably create a more customized one. The one strange thing is why would things swap names for the Ethernet one? But otherwise it is all good. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From dowelld at netscape.net Sat Jan 26 01:05:55 2013 From: dowelld at netscape.net (Dave Dowell) Date: Sat, 26 Jan 2013 01:05:55 +0000 Subject: [ARMedslack] First boot on Raspberry PI for Slackware 14.0 for ARM In-Reply-To: References: Message-ID: <51032BF3.5010307@netscape.net> On 25/01/2013 23:34, Gregg Levine wrote: > Hello! > Okay group I just brought up the Slackware 14.0 for the Raspberry pi > image available on Stanley Garvey's site. Aside from one nit, the > device almost arbitrarily changed the eth0 setting to eth1 for reasons > it did not clearly explain. > > Everything worked correctly from that one on. > > However how do I go about changing from UK keyboard to something > resembling a US one? > > In this case Stanley I borrowed my screen from a (what else?) system > running Slackware-13.37 and connected to it the HDMI cable via a > HDMI-DVI adapter that I bought today. Earlier I also bought an 8 > Gigabyte card on sale from Staples and used an image writing tool from > that system to write things out. And then connected everything from > there. > > It came up exactly as expected. Except for that one nit concerning the > Ethernet device swap. I once saw that happen on an Intel system I was > trying to revive and knew where to fix things. But here? No I don't. > > I have the installer based image that David Spencer made up and with > that and the screen I'll probably create a more customized one. > > The one strange thing is why would things swap names for the Ethernet one? > > But otherwise it is all good. > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack Is there a udev rule left on the image from the installation system, check in /etc/udev/rules.d and see if the 70-persistent-net.rules files has an entry for the eth0 hardware address from the install system. If there is you can just delete that file and the system will recreate it next time it boots, with your device (MAC address) listed as the eth0 device. Thanks Dave From stanley at stanleygarvey.com Sat Jan 26 13:03:45 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 26 Jan 2013 13:03:45 +0000 Subject: [ARMedslack] First boot on Raspberry PI for Slackware 14.0 for ARM In-Reply-To: <51032BF3.5010307@netscape.net> References: <51032BF3.5010307@netscape.net> Message-ID: <20130126130347.3D44E7EDB369C@bmail04.one.com> On Jan 26, 2013 01:05 "Dave Dowell" wrote: > On 25/01/2013 23:34, Gregg Levine wrote: > > Hello! > > Okay group I just brought up the Slackware 14.0 for the Raspberry pi > > image available on Stanley Garvey's site. Aside from one nit, the > > device almost arbitrarily changed the eth0 setting to eth1 for > > reasons > > it did not clearly explain. > > > > Everything worked correctly from that one on. > > > > However how do I go about changing from UK keyboard to something > > resembling a US one? > > > > In this case Stanley I borrowed my screen from a (what else?) system > > running Slackware-13.37 and connected to it the HDMI cable via a > > HDMI-DVI adapter that I bought today. Earlier I also bought an 8 > > Gigabyte card on sale from Staples and used an image writing tool > > from > > that system to write things out. And then connected everything from > > there. > > > > It came up exactly as expected. Except for that one nit concerning > > the > > Ethernet device swap. I once saw that happen on an Intel system I > > was > > trying to revive and knew where to fix things. But here? No I don't. > > > > I have the installer based image that David Spencer made up and with > > that and the screen I'll probably create a more customized one. > > > > The one strange thing is why would things swap names for the > > Ethernet one? > > > > But otherwise it is all good. > > ----- > > Gregg C Levine > > "This signature fought the Time Wars, time and again." > > _______________________________________________ > > ARMedslack mailing list > > > > > Is there a udev rule left on the image from the installation system, > check in /etc/udev/rules.d and see if the 70-persistent-net.rules > files > has an entry for the eth0 hardware address from the install system. > > If there is you can just delete that file and the system will recreate > it next time it boots, with your device (MAC address) listed as the > eth0 > device. > > Thanks > Dave > _______________________________________________ > ARMedslack mailing list > > > > Hi, Great to hear you got the image to boot! > > I have known about this issue for a while, I missed it when testing > the images because I was swapping the cards between boards and assumed > that udev was just picking up on a new mac address. I all ways remove > /etc/udev/rules.d/70-persistent-net.rules and the ssh keys when making > an image. > The culprit here is /etc/rc.d/rc.wireless > > chmod -x /etc/rc.d/wireless > rm /etc/udev/rules.d/70-persistent-net.rules > reboot > > Should fix it. Sorry about that. I will make some new images with this > fixed and a prettier boot partition soon. > regards > Stanley > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Sat Jan 26 17:28:35 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Sat, 26 Jan 2013 12:28:35 -0500 Subject: [ARMedslack] First boot on Raspberry PI for Slackware 14.0 for ARM In-Reply-To: <20130126130347.3D44E7EDB369C@bmail04.one.com> References: <51032BF3.5010307@netscape.net> <20130126130347.3D44E7EDB369C@bmail04.one.com> Message-ID: On Sat, Jan 26, 2013 at 8:03 AM, stanley garvey wrote: > On Jan 26, 2013 01:05 "Dave Dowell" wrote: > > On 25/01/2013 23:34, Gregg Levine wrote: > > Hello! > Okay group I just brought up the Slackware 14.0 for the Raspberry pi > image available on Stanley Garvey's site. Aside from one nit, the > device almost arbitrarily changed the eth0 setting to eth1 for reasons > it did not clearly explain. > > Everything worked correctly from that one on. > > However how do I go about changing from UK keyboard to something > resembling a US one? > > In this case Stanley I borrowed my screen from a (what else?) system > running Slackware-13.37 and connected to it the HDMI cable via a > HDMI-DVI adapter that I bought today. Earlier I also bought an 8 > Gigabyte card on sale from Staples and used an image writing tool from > that system to write things out. And then connected everything from > there. > > It came up exactly as expected. Except for that one nit concerning the > Ethernet device swap. I once saw that happen on an Intel system I was > trying to revive and knew where to fix things. But here? No I don't. > > I have the installer based image that David Spencer made up and with > that and the screen I'll probably create a more customized one. > > The one strange thing is why would things swap names for the Ethernet one? > > But otherwise it is all good. > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > Is there a udev rule left on the image from the installation system, > check in /etc/udev/rules.d and see if the 70-persistent-net.rules files > has an entry for the eth0 hardware address from the install system. > > If there is you can just delete that file and the system will recreate > it next time it boots, with your device (MAC address) listed as the eth0 > device. > > Thanks > Dave > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > Hi, Great to hear you got the image to boot! > > I have known about this issue for a while, I missed it when testing the > images because I was swapping the cards between boards and assumed that udev > was just picking up on a new mac address. I all ways remove > /etc/udev/rules.d/70-persistent-net.rules and the ssh keys when making an > image. > The culprit here is /etc/rc.d/rc.wireless > > chmod -x /etc/rc.d/wireless > rm /etc/udev/rules.d/70-persistent-net.rules > reboot > > Should fix it. Sorry about that. I will make some new images with this fixed > and a prettier boot partition soon. > regards > Stanley Hello! Thanks. As it happens I typed that out in a hurry. I bought a 16, which I did write out your image to. I'm going to leave that image on it, and work out how to reset the keyboard settings. (Even if I end up importing the keyboard management tools from 13.37 or earlier via source code files.) I'll probably pick up the same card and try again with the installer image since it also complained about space sizing. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From stanley at stanleygarvey.com Sat Jan 26 20:27:33 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 26 Jan 2013 20:27:33 +0000 Subject: [ARMedslack] First boot on Raspberry PI for Slackware 14.0 for ARM In-Reply-To: References: <20130126130347.3D44E7EDB369C@bmail04.one.com> Message-ID: <20130126202747.833DAC8134144@bmail03.one.com> On Jan 26, 2013 17:28 "Gregg Levine" wrote: > Hello! > Thanks. As it happens I typed that out in a hurry. I bought a 16, > which I did write out your image to. I'm going to leave that image on > it, and work out how to reset the keyboard settings. (Even if I end up > importing the keyboard management tools from 13.37 or earlier via > source code files.) > > I'll probably pick up the same card and try again with the installer > image since it also complained about space sizing. > --------- > Hi, I don't know about keyboard management tools? > see http://docs.slackware.com/howtos:window_managers:keyboard_layout > that might help. > > If you are new to Slackware you should read these great texts: > http://code.google.com/p/slackbasics-i18n/ > http://slackbook.org/ > They where written a while ago, however Slackware does not change that > much. (Thankfully). > > I don't understand about David Spencers installer complaining about > space sizing? Do you mean the software you are using to burn the > image? It's intended that you use fdisk or cfdisk to remove the last > partition and recreate it using the total space remaining on the > sdcard. It's a great idea, I fell into the trap of putting the swap > partion at the end of the drive in the superstitious belief that the > seek times are higher at the end of a hard drive. I have no empirical > evidence to support this and an sdcard is solid state anyway. > Good luck and best regards. > Stanley > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrixnet at yahoo.com Wed Jan 30 09:07:16 2013 From: andrixnet at yahoo.com (Andrei B.) Date: Wed, 30 Jan 2013 01:07:16 -0800 (PST) Subject: [ARMedslack] New Raspberry PI and Slackware14, my experience so far Message-ID: <1359536836.15405.YahooMailClassic@web126202.mail.ne1.yahoo.com> Hi, I'm just trying out my new PI. It is model B, with 512MB RAM. I did try out 2012-10-28-wheezy-raspbian.zip and it works fine. Then I followed David Spencer's instructions here http://www.daves-collective.co.uk/raspi/ and created my boot SD, while on a separate USB drive I got slackwarearm-14.0 Insert SD, rainbow screen, nothing. Then I started searching the net, and this mailing list first and I came onto this article http://lists.armedslack.org/pipermail/armedslack/2012-August/001356.html which I read it all. Following the first workaround, I thought I'll try things step by step. I renamed start.elf and then copied that file from the raspbian SD card. There was no loader.bin, either on the card already, or on raspbian, so let's try it this way. Surprise! It worked. My PI booted and I managed to start the installation. First potential problem : my PI has 512MB RAM, but free shows just under 128. I haven't touched the config yet. After finishing the install, all instructions, including removing kirkwood, tegra and versatile kernels, and installing the raspi kernel and utilities, and reboot, Surprise! I see activity on the SD led, but the display is blank. Not even the rainbow. Wait a few minutes, so it can finish any first boot stuff... Activity seems to follow a single pattern. Eth does no come up. It clearly won't boot. I see now that the first partition contains different files, a loader.bin that wasn't previously there, config.txt which is empty (0 bytes), and other files. I import the config from raspbian, to ensure it starts with TV out, but nothing. Raspian SD card still works just fine, so I know the hardware works. At this point I'm lost. Any suggestion would be appreciated. Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From cv99rt at gmail.com Wed Jan 30 19:22:51 2013 From: cv99rt at gmail.com (Peter Morjan) Date: Wed, 30 Jan 2013 20:22:51 +0100 Subject: [ARMedslack] New Raspberry PI and Slackware14, my experience so far In-Reply-To: <1359536836.15405.YahooMailClassic@web126202.mail.ne1.yahoo.com> References: <1359536836.15405.YahooMailClassic@web126202.mail.ne1.yahoo.com> Message-ID: I'm also new to Raspberry Pi and Slackware and really like this combination. It works great. In addition to your links I followed the instructions on http://rpi.fatdog.eu/?p=home After the firmware/kernel upgrade via rpi-update loader.bin is no longer required and the memory limit is gone. Usually I'm using a serial console but for HMDI output my config is: /boot/cmdline.txt console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro (p3 for the 3rd partition) /boot/config.txt gpu_mem=16 peter