Hi gary, Le 04/03/2013 21:36, gary a écrit :
I did a yast2 -i on the 19mbyte patch and didn't use the other two RPM files. This was on a freshly installed image of 12.2 XFCE.
I can't log into the system "normally", i.e. keyboard and monitor via HDMI/usb. Nor can I log into the system via the serial port. However, I can log into the system with SSH. Thus I can run some diagnostics if you have suggestions.
Could you give us output of thoses commands, please: cat /proc/cmdline lsmod Regards, Guillaume
The following in the output on the serial port.
Texas Instruments X-Loader 1.5.0 (Sep 8 2012 - 02:21:18) Beagle xM Reading boot sector Error: reading boot sector fat load failed, trying ext2 Loading u-boot.bin from mmc
U-Boot 2011.09 (Sep 08 2012 - 02:13:25)
OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB WARNING: Caches not enabled NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment
In: serial Out: serial Err: serial Beagle xM Rev C No EEPROM on expansion board Die ID #67dc00029ff80000016849a90401601a Net: No ethernet found. Hit any key to stop autoboot: 0 The user button is currently NOT pressed. SD/MMC found on device 0 Loading file "uEnv.txt" from mmc device 0:1 (xxa1) ** File not found uEnv.txt Loading file "boot.scr" from mmc device 0:1 (xxa1) 711 bytes read Loaded script from boot.scr Running bootscript from mmc0 ... ## Executing script at 80200000 ## Error: "kerneladdr" not defined ## Error: "ramdiskaddr" not defined Loading file "uImage" from mmc device 0:1 (xxa1) 4242344 bytes read Loading file "initrd" from mmc device 0:1 (xxa1) 12464100 bytes read ## Booting kernel from Legacy Image at 88000000 ... Image Name: Linux-3.7.9-0-omap2plus Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4242280 Bytes = 4 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 81600000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 12464036 Bytes = 11.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
On 3/4/2013 1:03 AM, Guillaume Gardet wrote:
Le 02/03/2013 01:28, gary a écrit :
I'm not sure if my direct replies are being caught in a spam filter. There were no instructions with the patch, which is 3 RPMs. I placed all three RPMs on the SD card for the Beagleboard XM. [Basically just do a save as with the sd card in an intel computer running opensuse.]
I booted the Beagleboard XM and ran all three patches, then rebooted. At that point I could no longer log into the Beagleboard XM. Not through the serial port or the "normally" (display driver and usb).
What is the output on the serial port (I mean from u-boot and then if you have something then)? Did you try a SSH login?
I have a program on the Beagleboard XM that I set up as a service that provides "telemetry" over a lan. That service was running since I coudl get data off the Beagleboard XM. I ran it for 3 days without a crash. [At that point I went to a different SD card / OS to work on other software.] The best I ever got prior to the patch is about 8 hours.
However, I think the performance of the software I was running was hampered by the patch since it seemed to be putting out less data. Since I couldn't log into the board, I have no way to analyze this.
So again, I am asking for someone to either explain how to apply the patch, or apply the patch to an image.
Install RPM kernel-omap2plus provided by Alex, using zypper and reboot.
As I stated before the JEOS wasn't booting on the Beagleboard XM. [The XFCE image works.] This might be a good way to get the bug out of JEOS and test the patch at the same time.
Try your patch on XFCE image first. One thing at a time. ;)
Since this appears to be a design flaw in the beagleboard XM, I'm sure all the board have an issue with this to some degree. My board is just worse than most. Thus I have a good test vehicle for the patched kernel, well provided I get one.
Thanks for your help in testing.
Guillaume
On 2/25/2013 4:05 PM, Alexander Graf wrote:
On 25.02.2013, at 19:00, Alexander Graf wrote:
On 25.02.2013, at 18:50, lists@lazygranch.com wrote:
Actually, I haven't tried the patch. The instructions are not detailed enough for me to use. The person who wrote has "issues" and isn't helpful. Let's leave it at that.
If anyone can explain in detail how to patch a kernel, I'm willing to try it.
I guess it's easiest if either Guillaume or me create a special kernel for you to try with that patch applied. I won't get to it before midnight today, but maybe can create one after that tonight that you can give a whirl. My Beagleboard XM is about 2 km away with lots and lots of snow lying in between me and it. :)
This is the 12.3 kernel + the patch you posted.
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org