• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2 3 ... 10
 1 
 on: August 11, 2014, 02:23:52 PM 
Started by mgillespie - Last post by mhtsaras
I have the plug for some years now, booting from sd card debian wheezy, i have some old sd rootfs.tar.gz back ups that can extract to sd card if something is wrong.
I tried to get a fresh new copy and formated a partition on sd card, created inside the rootfs.tar.gz   with DebianSheeva1-7.sh script, copy to a usb disk attached with plug and extract it from the usb disk to the sd partition
I reboot and I try to connect with putty (from another lan computer) get the login screen and type  user: root   password:nosoup4u , I get "acess denied"
I reset the password from shadow file reboot--user:root-password:<enter>--"acess denied"
Can rootfs.tar.gz be used like this, meaning , extract and get it work;; or I am doing something wrong?
I also can boot form plug's internal memory if I pull the sd card and reboot so I do some stuff but not get the generated rootfs from your script....
Thanx in advance!

 2 
 on: August 07, 2014, 05:40:19 PM 
Started by restamp - Last post by birdman
Does your copy include the debian headers, as given by mgillespie in: http://www.plugcomputer.org/plugforum/index.php?topic=485.0#msg5425
Mind you, on looking at that more closely it appears to be wrong.  The
Quote
Required-Start; checkfs
part means that it will run after checkfs, but I suspect you need it to run before checkfs.

To do that you can leave the
Quote
Required-Start:
in wait4usbdisks empty, (i.e. you'll need to edit it to remove the checkfs that is there) but add wait4usbdisks to that line in the checkfs.sh script (after checkroot - with a space in between them).

Then run
Code:
update-rc.d wait4usbdisks defaults

 3 
 on: August 07, 2014, 05:29:03 PM 
Started by restamp - Last post by birdman
he right solution would be to have wait4usbdisks finish before checkfs.sh starts, without having to modify 'stock' initialization scripts. 
AFAIK wait4usbdisks is not a "stock" initialization script.  Indeed - it seems to have been posted in the first entry in this thread.

Does your copy include the debian headers, as given by mgillespie in: http://www.plugcomputer.org/plugforum/index.php?topic=485.0#msg5425

Have you made it executable?

Have you ensured that it gets run at the right time by running
Code:
update-rc.d wait4usbdisks defaults

Have you considered using a rootdelay in the boot environment settings?  I only have /boot on an SDcard, with everything else (including /) on a USB drive (which is running through a hub) so I must have the USB drive up, running and available before I can even boot.  It's always worked well.

 4 
 on: August 06, 2014, 02:38:17 PM 
Started by restamp - Last post by nhoeller
@birdman, that is definitely an option.  Unfortunately, I am still having problems getting my head around the LSB-compliant init scripts stuff.  I can read the words but the detailed logic still eludes me.  The right solution would be to have wait4usbdisks finish before checkfs.sh starts, without having to modify 'stock' initialization scripts. 

 5 
 on: August 05, 2014, 04:42:42 PM 
Started by restamp - Last post by birdman
Quote
...there is no standard way to get wait4usbdrives to run before checkfs.sh without modifying the headers in checkfs.sh.
Well, you could edit the checkfs.sh script to add a requirement for something which is provided by the wait4usbdrives script (so you might have to edit that too, to actually say what it is providing)?

 6 
 on: August 05, 2014, 07:54:50 AM 
Started by restamp - Last post by nhoeller
I tried the code provided by mgillespie (post #11) without success - mountall.sh is running before wait4usbdrives gets a chance to slow down the process.  It may be my setup: I am running Debian Squeeze and the USB harddrive is connected to a hub - it takes 8 seconds before the drive is recognized and added to /dev.  rcconf slotted wait4usbdisks after checkfs.sh and before mountall.sh but based on https://wiki.debian.org/LSBInitScripts/ it appears Debian Squeeze is running boot scripts according to dependency information provided by the scripts rather than the older numeric Snn sequence.  The FAQ at the bottom of https://wiki.debian.org/LSBInitScripts/ implies that there is no standard way to get wait4usbdrives to run before checkfs.sh without modifying the headers in checkfs.sh. 

For the moment, I have modified checkfs.sh at the beginning of the do_start routine to include the code from restamp amd mgillespie.  I will play around with the X-Start-Before and X-Stop-After headers mentioned in the FAQ when I get some time.

 7 
 on: April 13, 2014, 12:45:11 AM 
Started by elvis61 - Last post by elvis61
hi together,

this topic i posted in
https://forum.sparkfun.com/viewtopic.php?f=18&t=38034&p=170228#p170228

i hope i find here somebody who takes a little time for a hint

thanks in advance

 8 
 on: March 24, 2014, 11:27:54 PM 
Started by cbxbiker61 - Last post by cbxbiker61
I would like to update my GP+ kernel to the newest ones using the update script, but I don't know how to do it. Let me explain a bit more...

I'm running ArchLinux. Arch on GPs comes with a 3.1 kernel, but I am using 3.7.9 kernel downloaded from xilka. Until now I have been manually installing kernels from uboot via tftpboot/nand erase/nand write. So my GP+ reads the kernel from the NAND, and then the filesystem is mounted from the microSD card.

I was going to test manually updating to the latest 3.13 kernel, but now I see that not only the kernel image is needed, also the device tree must be flashed. And I don't know where do I need to flash it or how. So I think now it's time to do things the right way: updating the system using the update script instead of manually messing with uboot.

How can I do it? Do I need to format the internal flash in a special way and mount it? What boot command/params should I set it uboot? Is there a step by step tutorial anywhere?

Unfortunately I don't have a GP+ to test on, so here's how you probably want to proceed.

The kernel image is built with a device-tree backward compatibility mode,  If you look at the script you will see that it "merges" the zImage with the appropriate .dtb file.  When the zImage is loaded it looks for a .dtb that is appended to it's tail.  The .dtb describes the hardware and everything should work.

That merged zImage/.dtb can be in either system flash or on removable media (if your u-boot supports that).  If you look at the section that handles the original sheevaplug you should be able to duplicate that functionality for a GP+.

Please get back to me with patches if you decide to proceed with enhancing the UPDATE-KERNEL.sh script.


 9 
 on: March 21, 2014, 11:32:30 AM 
Started by cbxbiker61 - Last post by doragasu
I would like to update my GP+ kernel to the newest ones using the update script, but I don't know how to do it. Let me explain a bit more...

I'm running ArchLinux. Arch on GPs comes with a 3.1 kernel, but I am using 3.7.9 kernel downloaded from xilka. Until now I have been manually installing kernels from uboot via tftpboot/nand erase/nand write. So my GP+ reads the kernel from the NAND, and then the filesystem is mounted from the microSD card.

I was going to test manually updating to the latest 3.13 kernel, but now I see that not only the kernel image is needed, also the device tree must be flashed. And I don't know where do I need to flash it or how. So I think now it's time to do things the right way: updating the system using the update script instead of manually messing with uboot.

How can I do it? Do I need to format the internal flash in a special way and mount it? What boot command/params should I set it uboot? Is there a step by step tutorial anywhere?

 10 
 on: February 19, 2014, 01:07:31 AM 
Started by cbxbiker61 - Last post by mgillespie
Working OK again today. Grabbed the last 3.11 kernel and will stick with that seems more robust on my sheevaplug.

Pages: [1] 2 3 ... 10