Puppy Linux Discussion Forum

[ttuuxxx]

ok I tried like 30+ different combinations ,lol the closest I managed to get was that it loaded vmlinuz and then loaded ramdisk and I received a invalid Opcode. Really it was my last test that got me the furthest but probably shouldn't of worked that far.

it did say "Loading ramdisk from disk:\boot\vmlinuz"
which is good, still haven't seen 1 single puppy screen.

this is my olpc.fth, it was option 2, the usb which went the furthest, when I tried like 15 or so test on SD card, nothing really, other than loading vmlinuz.

[ttuuxxx]

another notes the isolinux.cfg states,
append pmedia=cd
ummm what CD? shouldn't that be somethings else like, pmedia=usbflash
ttuuxxx

[mavrothal]

I tried some scripts my self (with Mitch Bradley's suggestions-thanks)

[eowens2]

Some of the more important changes I have made to Puppy 412's initrd.gz init include the following:

A limited set of modules (hardware, file systems, etc) that go with the newly compiled kernel of course have to be in init.

Line 52 - LAYERFS=unionfs (instead of = aufs; I never could get aufs to work)

Line 122 - this is the check status function, which would be evoked under certain error conditions, drop you to a shell, and report contents of some variables. I added a function,(modifying check status ())called dump (), which I could invoke by placing dump 0 at selected sites in init; at that point it would drop me to a shell and report pupmode, CREATEPUPXXXSFS, amount of free ram, .sfs file size, .sfs device location, .sfs device mount point as well as the last lines of /tmp/bootinit.log.

lines 211,212,215,216 commented because XO doesn't need modules for PCMCIA cards

line 266 commented out (modprobe nls_cp437) the module is unnecessary because XO kernel has this compiled into the body of the kernel

lines 921-25 commented out - this was a hack specifically for kernel 2.6.25.16 adding ssb modules

line 939 - adjusted [$RAMSIZE -gt 220000 -a "$PCOPY" = "yes"] downward a little, just to make sure I could get my bloated pup_412.sfs into RAM, then plan to clean up the mess later

line 991 - adjusted [ $RAMSIZE -gt 280000 ] downward - same reason as line 939

This init will proceed to a "dump 0" placed just before switch_root @ line 1350 ("exec switch_root /pup/new /sbin/init") without fatal error. The bootinit.log does list the problem "mount: mounting /dev/loop0 on /pup_ro2 failed, Invalid Argument" however.

When said "dump 0" is removed, we get the message "performing a switch root" and then kernel panic.

Is it crashing because it can't find the new OS on the (unmounted) /pup_ro2?

Anyone have any ideas?

Thanx.


P.S. I have been trying to look up some puppy source code and the site where I used to find them won't let me in. It now wants a user ID and password. Does anyone know where you get these?

[ttuuxxx]

hi username and passwords are just to stop spam
username:puppy
password:linux

[mavrothal]

So, eowens2
you are using a patched 2.6.25-olpc kernel from os802 or a newer one?
Does your modified system runs fine in full install?
Can you zip and post your init? I need to do some debugging with my attempts with uPup .
I got an olpc.fth that appears to pass the arguments OK and the system looks like it boots (by the camera, mic, and stick light changes) but does not get me into console.
BTW the olpc.fth looks like this
======
\ boot script
" ro root=/dev/sda1 rootfstype=vfat console=tty0 fbcon=font:SUN12x22 video=fb:1200x900 pmedia=usbflash pdev1=sda1" to boot-file
" u:\vmlinuz" to boot-device
" u:\initrd.gz" to ramdisk
setup-smbios
unfreeze
dcon-unfreeze
visible
boot
=====
Which one are you using?

Sorry only questions and no answers.

[davesurrey]

mavrothal wrote about making a comment on Barry's blog:

[raffy]

I also got opcode error when booting Quirky004, but it finished booting.

ttuuxxx, "pmedia=usbflash" should be there to be sure.

As to Mavrothal's issues with Barry's blog, he used Safari browser, so now he knows that he has to use Firefox or Opera.

[BarryK]

I suggested a super-simple olpc.fth:

http://bkhome.org/blog/?viewDetailed=01338

...from my brief reading, it seems that just a 2-line olpc.fth is enough.

Regarding invalid op-code, that sure is weird. The kernel is compiled for a i486. Well, I guess I can re-compile it with the instruction set dumbed-down even more.

[eowens2]

Mavrothal,

I am using a patched 2.6.25.15 kernel from os 802.

I have not intentionally tried to boot a full HD install. I think I unintentionally did so before I got pup_412.sfs into /mnt/tmpfs in RAM.

A few times I got thru switch_root and knocked on the door of Xorg (never got a window, though). I wish I had better notes from those attempts!

I am using the vanilla multiboot from the OLPC forums, nothing special. I do not try to pass any parameters from boot to the kernel.

Tuuxxx, thanks for the UserID/password info.

[ttuuxxx]

[BarryK]

ttuuxxx,
I haven't looked at any "official" olpc kernel .config file yet. The 2.6.30.5 kernel has a lot of olpc support built in, so that .config you posted is not entirely relevant, though the cpu architecture settings will be.

Anyway, I have already recompiled the kernel. Here is my latest one-file Quirky, with the kernel configured for a Geode GX1 CPU, which should fix the invalid-opcode problem...

http://bkhome.org/blog/?viewDetailed=01339

[mavrothal]

raffy, davesurrey, Thanks!
I can now post in Barry's blog using Opera.
(Firefox is a heavy "mission-critical" browser on my XO )

[mavrothal]

Here is an 2.6.31 DOTconfig that has Aufs2, Squashfs and hfsplus ( ) activated as the only difference from the official OLPC 2.6.31 XO-1 kernel.
Used it to compile with OLPC sources from OLPC Git and the official Aufs2 standalone sources and patches from Aufs Git
Runs both Fedora 11 and uPup451 (full install) on the XO1 (with an OLPC initrd) fine.

[BarryK]

ttuuxxx and others,
After discussion on my blog:

http://bkhome.org/blog/?viewDetailed=01339

...only the XO-1 has a Geode CPU, the XO 1.5 has a Via C7-M CPU.

So as my most recent one-file Quirky is compiled specifically for a Geode GX1 CPU, it might not work on the XO 1.5. Heck, there might even be a problem with the XO-1 as it has a Geode LX CPU and I'm only assuming that it is backwards compatible with the GX1.

I think Raffy has an XO-1, so can try the latest Quirky.

Anyway, I'll take a look at what mavrothal has posted and do another build.