Puppy Linux Discussion Forum

[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.

[amigo]

Any geode can run using a kernel compiled for 'i586'. However, the geode lx will suffer from severe slowdowns and should use a kernel compiled for 'i486'. Using an 'i486' kernel will ensure compatibility with the XO 1.5

[raffy]

Sorry, I have a Geode miniPC, actually a GX2. But what differs among the newer Geodes is the companion chip, with CS5536 for newer boards, the old ones having CS5535.

There's no problem booting those Geodes with the usual proprietary BIOSes.

XO is unique because it used OpenFirmware. You'll have to read about Mitch Bradley to find out what it means.

[mavrothal]

So,dia anyone had better luck than me with the latest OLPX XO1 quirky?

[mavrothal]

I also tried Barry's 3-file version of OLPC-quirky
As I describe in Barry's blog (5th comment) despite my best efforts it still can not find the sfs files.
Please take a look and help if you can
C'mon ttuuxxx. Do something

[ttuuxxx]

[wmb@firmworks.com]

I tried the 3-file version, with the same results as mavrothal - no console messages. That means that the kernel is not right for the machine.

As I have mentioned a couple of times so far, trying to use a kernel derived from upstream sources is very unlikely to work. Some OLPC stuff has been accepted upstream, but I think there are still some loose ends.

The XO-1 does not have a PC-compatible text-mode framebuffer - no EGA character/attribute mapped display at 0xb8000. You must use fbcon, and in addition to that, there is also some Geode GX/LX magic for getting the resolution set right, some stuff for the "DCON" display swizzler chip, some GPIO stuff, and some special PCI configuration stuff to work around the fact that the Geode chipset doesn't really have PCI configuration registers. Conventional BIOS emulates those configuration registers with some ultra-gnarly System Management Mode magic. The code for that was proprietary, not to mention uncompilable since the toolchain it uses is a commercial product that is no long available. So instead of turning on System Management Mode, I wrote a Linux kernel PCI driver addition that does the PCI config spoofing (30 lines of code and some tables).

The reason I described all that is to convince you that you really, really want to start with the OLPC kernel source and fold in aufs and squashfs and whatever.

Apparently mavrothal has done just that, but from what I can tell, he doesn't know how to replace the modules in initrd.gz. If aufs and squashfs are modules instead of being hard-linked, the init isn't going to work if vmlinuz mismatches the modules in initrd.gz .

If I can get a copy of that kernel plus modules, I'll try to get this working.

Mitch Bradley

[mavrothal]

Mitch, thank you for stopping by
I certainly do no do initramfs, but in my latest attempt (5th post) the initrd modules do come form the same build as vmlinuz and load just fine (as far as the dmesg shows).
The problem appears to be that usb_storage module has unknown symbols for the
usb_storage_usb_ids
usb_usual_ignore_device
usb_usual_clear_present
usb_usual_check_type
usb_usual_set_present.
This seems to be the case also with the original Barry's version in a Starbox SB-800 (geode LX800) machine (above link, 4th post). So is not Kernel/module specific (init script?... )
I also tried with the infopup script included in the initrd and indeed can not see any device or partition, like it booted from thin air.
Any ideas for that?
Please keep close

PS. I'll upload last night's kernel rmps and srpm somewhere and post the link here shortly.

[wmb@firmworks.com]

[wmb@firmworks.com]

[wmb@firmworks.com]

I see from the XOpupDOTconfig that you (mavrothal) posted earlier that indeed CONFIG_USB_LIBUSUAL=y . So you can try either unsetting that config option or "modprobe usb_libusual".

[mavrothal]

[wmb@firmworks.com]

I got the kernel RPM ...

[mavrothal]

[wmb@firmworks.com]

To make the modules.dep, I did this: