• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3 ... 30
1  General Category / Success stories / Re: Managing a USB hard drive on the Plug on: August 07, 2014, 05:40:19 PM
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
2  General Category / Success stories / Re: Managing a USB hard drive on the Plug on: August 07, 2014, 05:29:03 PM
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.
3  General Category / Success stories / Re: Managing a USB hard drive on the Plug on: August 05, 2014, 04:42:42 PM
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)?
4  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: February 18, 2014, 07:43:31 PM
Anyone else having problems with http://www.xilka.com ?
Not at the moment. I've just browsed down through the 3.13.3 kernel listing with no problem.
Quote from: see above
Many links just redirect to www.appfail.com  Huh
Odd place to go.  The xilka site isn't accessed over https.  Well, it can be, but the certificate is issued for "*.scaleengine.net", which is where xilka.com lives, but isn't of any use for it.
Seems odd to go to the expense of a valid wildcard certificate (from Comodo) when the subject name isn't actually going to be used.
5  General Category / General Discussion / Re: filsystem on 2TB drive not using full capacity on: January 26, 2014, 07:31:07 PM
Then I used dd to copy the contents of the partitions to the new drive.
So you copied the file system (which includes its size) into what is now a larger partition.  But the file-system is still the same size.

You need to use resize2fs to expand the file-system on /dev/sda9 now (assuming it is an ext2/ext3/et4 file-system).

Take a look at it's man page, and:

   http://webapp5.rrz.uni-hamburg.de/SuSe-Dokumentation/manual/sles-manuals_en/manual/biuymaa.html

NOTE that you have already enlarged the partition - you just want to grow the file-system to use all of the space.

Also note that all of these things warn about backing up before you do anything.
6  Hardware and U-Boot firmware / U-Boot stuff / Re: SheevaPlug: no boot from SDHC after u-boot upgrade to DENX 2012.04.01-2 on: January 17, 2014, 06:25:57 PM
However, since all(?) of the files you need will be under /boot, you could just make an ext2 file-system  for that and use the ext2load.
Given that it will be fairly static you wont see any difference c.f. ext4.
7  Linux Stuff / General Linux questions / Re: Disable DHCP Client on: October 07, 2013, 05:01:17 PM
Here is the /etc/networking/interfaces file
Is that a typo?  The file should be /etc/network/interfaces.
At least that's where mine is.
8  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 26, 2013, 03:50:45 PM
Ladies and Gentlemen, you are genius's (geni'i?)
Or, indeed, geniuses.
But all I did was use Google - to stand on other's shoulders.  I sometimes wonder how I debugged things 20 years ago (but I did...)
9  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 26, 2013, 03:46:52 PM
It still doesn't auto-boot on power-on, though :-(.
I lied.  It does auto-boot!!

I can only assume that it failed last time because I tried to connect to the console during its boot sequence, so aborted it.
But I've just powered it up from a standing start and it's come all the way up with no problem.
Which is just as well, as it was difficult to see how changing the kernel would stop a boot attempt being made.
10  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 25, 2013, 02:06:29 PM
This is what my dmesg log now shows for booting that 3.10.6 kernel:
Quote
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
11  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 25, 2013, 01:45:24 PM
Yippee!!  One down!!!

I've built 3.10.6 (I was running 3.10.5, and wanted something close, but with no danger of a name-space clash).
All I've done is changed this in kirkwood-3.10.6.config
Quote
#GML -  CONFIG_SERIAL_OF_PLATFORM is not set
CONFIG_SERIAL_OF_PLATFORM=y
and I now have a working serial console again!

Well, I got a full set of boot up messages.  I didn't get the console prompt until I re-enabled the TO/getty line in inittab and ran "telinit q".  (I'd disabled as it was producing message about re-=spawning too quickly.).  That all works now.

It still doesn't auto-boot on power-on, though :-(.

PS:  I forgot to mention that the nice thing about using VirtualBox+qemu is that you can end up with a large memory, multi-CPU Sheevaplug (so make -j2, etc.), and can pause the while thing in mid kernel-build, switch everything off and then start again hours later, picking up in mid-compilation.
12  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 24, 2013, 04:36:02 PM
This page:(whcih is for a different hardware, but still a Kirkwood setup) metions:
Quote
To enable the serial console: (This is in addition to the 8250/16550 and serial console support you should generally have enabled for kirkwood.)

Device Drivers --> Character Devices --> Serial Drivers

    Serial port on Open Firmware platform bus (CONFIG_SERIAL_OF_PLATFORM)
but this isn't set on cbxbiker61's config.  Could this be the problem?
13  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 20, 2013, 03:04:07 PM
If someone can point me to a suitable cross-compiling toolchain for an Intel x86_64 host, I'm happy to try building some kernels to find out what change makes the difference.
I have the while thing set up for my Plug by using qemu in a VirtualBox host running Debian (which is all on my Linux Mint workstation, so I can run with multiple cores, and lots of memory, if I wish...).
That's quite simple to set-up.  (I have qemu setups there for my Raspberry Pi and Asus66 also..)
14  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 17, 2013, 06:20:12 PM
I am having one other problem with the Cbxbiker kernels, which I don't get with a Fedora kernel (my root filesystem is on sdb3).

Part way through the boot process, I get the following messages in the log:
[    9.821912] EXT3-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
[    9.823149] EXT2-fs (sdb3): error: couldn't mount because of unsupported optional features (240)
[    9.840065] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[    9.840113] VFS: Mounted root (ext4 filesystem) readonly on device 8:19.

and I end up with the root filesystem mounted read only.

Can anyone give me some suggestions about what is causing this problem..
Are you sure it's an actual problem?
Mine does the same (it tries ext3, ext2, ext4 in that order, hence the error messages).
But shortly after mounting the root readonly (which is always does at start with) it then reports:
Quote
Sep 16 00:23:46 plug kernel: EXT4-fs (sda1): re-mounted. Opts: (null)
Sep 16 00:23:46 plug kernel: EXT4-fs (sda1): re-mounted. Opts: (null)
and it is then mounted read/write.
15  Linux Stuff / General Linux questions / Re: Fresh install of Wheezy on: May 07, 2013, 05:15:58 PM
The image are dated from 2011 or 2012

Will they update to the latest Wheezy once plugged in the plug?
I would expect them to if you run an update.
I switched to wheezy just be editing my /etc/apt/sources.list file to change all instances of "squeeze" to "wheezy" then doing an update. Well, I seem to recall  had to remove an sgml package causing some odd dependency failure, and had to forcibly update one perl package manually, but apart from that it all went OK with several hundred (or >1000 - I forget) package updates.
Pages: [1] 2 3 ... 30