• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 ... 8 9 [10]
 91 
 on: September 18, 2013, 07:11:58 AM 
Started by cbxbiker61 - Last post by pqa
Thanks for the update re read-only rootfs. After booting the rootfs is definitely mounted read-only, so it looks like my systemd scripts aren't running properly then when using the Cbxbiker kernels. I dig into this a bit more. It's probably due to Fedora using an initrd, and I am now suspecting that some scripts are run on that before switching to the permanent rootfs.

 92 
 on: September 18, 2013, 02:07:23 AM 
Started by cbxbiker61 - Last post by apemberton
I confirm that I find the same as Birdman on the disk thing. Also because my /etc/fstab requires it, my disks are unmounted, a fs check performed and then remounted. This is normal and a bit of a lifesaver as the i-node count get corrupted in service.

 93 
 on: September 17, 2013, 06:20:12 PM 
Started by cbxbiker61 - Last post by birdman
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.

 94 
 on: September 17, 2013, 04:43:49 PM 
Started by cbxbiker61 - Last post by pqa
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.

Many thanks.

 95 
 on: September 17, 2013, 01:11:29 PM 
Started by cbxbiker61 - Last post by pqa
Tony,

The Fedora kernels are downloadable from http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=3547 . The fc18 series are the last ones being built for armv5tel. If  you click on a kernel you are interested in, there is an option to download the source RPM. Alternatively all the source files for the build, except the kernel itself, are available from http://pkgs.fedoraproject.org/cgit/kernel.git/log/?h=f18

Quentin

 96 
 on: September 17, 2013, 12:23:52 PM 
Started by cbxbiker61 - Last post by apemberton
Thanks for your info and update. I think you are on to it. Is there a link for the Fedora kernel DT source? More minds the better especially to aid my old, worn out grey cells! Tony.

 97 
 on: September 17, 2013, 12:12:19 PM 
Started by Daniel Ng - Last post by trampjuice
IT WAS THE PSU!!!

It has taken me this long to connect a regulated bench PSU. INSANE. My old PSU was a cheap  220V in 5v 2a out dc, so at UK 240v it gradually must have failed over about 2 years. 

Have replaced and hopefully trouble free from now.

 98 
 on: September 17, 2013, 12:05:15 PM 
Started by recursix - Last post by trampjuice
You just have to wait 9 hrs unplugged if your scared the cap will discharge through you when you open the aluminum case to get at the psu.
The whole plug design is crazy as the aluminum is only there to screen the tiny electronics from the psu as its so close together.
I have went through trying to repair the capacitor in the orginal PSU, which worked for 6 months or so, and then taking out the entire module and directly wiring a 5v 2A psu (which was not great quality and lasted only 2 years more as it was not UK 240v in but 220v in) and now I got a proper bench psu thinking there were faults in the unit - only to find it worked perfectly when it had 5v regulated connected.
I hav finally dug out a LINKSYS ATA 5V 2A psu, and wired that in today. It looks higher quality I hope it lasts.
Basically 99% of all sheeva plug problems - erratic behavour, network going down etc.. are going to be down to a failing PSU.
 

 99 
 on: September 17, 2013, 07:24:51 AM 
Started by cbxbiker61 - Last post by pqa
apemberton, my Fedora 3.10.10 kernel IS a device tree kernel, booting a dreamplug device tree.

I have noticed that the device trees from Fedora are not the same as the device trees from Cbxbiker, so I will have a look at that and see if I can fathom if there is anything there.

 100 
 on: September 17, 2013, 02:02:46 AM 
Started by cbxbiker61 - Last post by apemberton
PQA, is your Fedora 3.10.10 kernel a Device Tree kernel? If not, this should help confirm that the console issue is in the Device Tree rather than the kernel itself.

I had a little look at schematics for a Guruplug and some of the Kirkwood data sheet and some of the MPP pins have multiple functions set up depending on initialisation. I see that MPP8 is shared between a gpio control of RTS (Request To Send) for serial and SDA for i2c/smbus; MPP9 is shared between gpio CTS (Clear To Send) and SCK for i2C/smbus.

I have the feeling that when the hardware is activated by the Device Tree code, the setup is not performed correctly for UART0 and possibly for other hardware. I'm not particularly familiar with the Kirkwood architecture so poring over code and datasheets to tie up the devices and initialisation may take some time and I do have other things to do. I am convinced that the kernel itself (as opposed to Device tree) is OK and the problem is not a .config issue.


Pages: 1 ... 8 9 [10]