Small linux distro for my embedded box

[laga]

That would be fine. The init already does special things for certain hardware (e.g. NVIDIA graphics). The special behavior is keyed off of the output of 'lspci -mn', 'lsusb', 'dmidecode -t baseboard' and 'dmidecode -t processor'. Could you provide this information for the S100?

Here we go:

lspci -mn

Code: Select all

root@s100:~ $ lspci -mn
00:00.0 "0600" "8086" "3575" -r04 "7065" "8086"
00:02.0 "0300" "8086" "3577" -r04 "" ""
00:02.1 "0380" "8086" "3577" "" ""
00:1d.0 "0c03" "8086" "24c2" -r02 "8086" "24c0"
00:1d.1 "0c03" "8086" "24c4" -r02 "8086" "24c0"
00:1d.2 "0c03" "8086" "24c7" -r02 "8086" "24c0"
00:1d.7 "0c03" "8086" "24cd" -r02 -p20 "8086" "24c0"
00:1e.0 "0604" "8086" "244e" -r82 "" ""
00:1f.0 "0601" "8086" "24c0" -r02 "" ""
00:1f.1 "0101" "8086" "24cb" -r02 -p8a "8086" "24c0"
00:1f.3 "0c05" "8086" "24c3" -r02 "8086" "24c0"
00:1f.5 "0401" "8086" "24c5" -r02 "8086" "24c0"
01:06.0 "0200" "10ec" "8139" -r10 "10ec" "8139"
01:07.0 "0280" "1260" "3890" -r01 "17cf" "0014"


lsusb:

Code: Select all

Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000


dmidecode -t baseboard

Code: Select all

# dmidecode 2.9
SMBIOS 2.3 present.

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
        Manufacturer: To be filled by O.E.M.
        Product Name: To be filled by O.E.M.
        Version: To be filled by O.E.M.
        Serial Number: To be filled by O.E.M.

Handle 0x0026, DMI type 10, 6 bytes
On Board Device Information
        Type: Video
        Status: Enabled
        Description:   To Be Filled By O.E.M.



dmidecode -t processor:

Code: Select all

# dmidecode 2.9
SMBIOS 2.3 present.

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
        Socket Designation: CPU 1
        Type: Central Processor
        Family: Pentium III
        Manufacturer: Intel
        ID: B4 06 00 00 FF FB 83 03
        Signature: Type 0, Family 6, Model 11, Stepping 4
        Flags:
                FPU (Floating-point unit on-chip)
                VME (Virtual mode extension)
                DE (Debugging extension)
                PSE (Page size extension)
                TSC (Time stamp counter)
                MSR (Model specific registers)
                PAE (Physical address extension)
                MCE (Machine check exception)
                CX8 (CMPXCHG8 instruction supported)
                APIC (On-chip APIC hardware supported)
                SEP (Fast system call)
                MTRR (Memory type range registers)
                PGE (Page global enable)
                MCA (Machine check architecture)
                CMOV (Conditional move instruction supported)
                PAT (Page attribute table)
                PSE-36 (36-bit page size extension)
                MMX (MMX technology supported)
                FXSR (Fast floating-point save and restore)
                SSE (Streaming SIMD extensions)
        Version: Mobile Intel(R) Celeron(TM) CPU          733MHz
        Voltage: 3.3 V 2.9 V
        External Clock: 133 MHz
        Max Speed: 733 MHz
        Current Speed: 733 MHz
        Status: Populated, Enabled
        Upgrade: 370-pin Socket
        L1 Cache Handle: 0x0005
        L2 Cache Handle: 0x0006
        L3 Cache Handle: 0x0007
        Serial Number: To Be Filled By O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Part Number: To Be Filled By O.E.M.

Handle 0x0008, DMI type 4, 35 bytes
Processor Information
        Socket Designation: CPU 2
        Type: Central Processor
        Family: Other
        Manufacturer:
        ID: 00 00 00 00 00 00 00 00
        Version:
        Voltage: 3.3 V 2.9 V
        External Clock: Unknown
        Max Speed: 2000 MHz
        Current Speed: Unknown
        Status: Unpopulated
        Upgrade: ZIF Socket
        L1 Cache Handle: 0x0009
        L2 Cache Handle: 0x000A
        L3 Cache Handle: 0x000B
        Serial Number: To Be Filled By O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Part Number: To Be Filled By O.E.M.


[laga]

In that case, I think that it would be easier to apply the patches all the time. If you point me to the patches, then I will add them.

Here's the intel-agp patch:
http://laga.ath.cx/minimyth-iegd/patche ... lagp.patch

It's to be placed in minimyth/script/kernel-2.6.17/linux/files.

Get the MythTV colorspace patch from here:

http://laga.ath.cx/minimyth-iegd/patche ... 2241.patch

I haven't prepared a patch for MythTV SVN yet, but that's not hard. See ticket #2241, that #define was renamed in SVN. I'll create a patch later when I can find some spare time.

By the way, can the preferred colorspace be changed without patching MythTV?

I don't think so. However, it's just a very small patch. Maybe I could try to put it into the ./configure script and have upstream merge that patch.

-- Michael

p.s.: Here's my minimyth-lib-list.iegd. It's missing some libGL file needed for hardware 3d acceleration. I think it's used in a way similar to the nvidia driver. I'll try to find out more

Code: Select all

# IEGD

libXiegd_escape.so.2.0.0
# these should be just symbolic links.
# I don't know if we should include them that way.
# They might be created as new files, ie the sym links might be followed
libXiegd_escape.so.2.0
libXiegd_escape.so.2
libXiegd_escape.so
# tv out encoder
xorg/modules/fs454.so
# the real driver
xorg/modules/drivers/intel_drv.so
# IEGD kernel modules
# I don't know if these are sane.
# Not sure about the correct syntax either :)
# modules/*/misc/iegd/
modules/*/misc/iegd/*

# we need libGL!!


[Pablo]

In that case, I think that it would be easier to apply the patches all the time. If you point me to the patches, then I will add them.

Here's the intel-agp patch:
http://laga.ath.cx/minimyth-iegd/patche ... lagp.patch

It's to be placed in minimyth/script/kernel-2.6.17/linux/files.

This patch appears to remove things from the intel-agp driver, yet the one included in IEGD 6.1 does not. I have created and checked in a patch (*-iegd_6.1.patch) based on the on the 2.6.15 patch in IEGD 6.1. Could you check whether or not it works?

Get the MythTV colorspace patch from here:

http://laga.ath.cx/minimyth-iegd/patche ... 2241.patch

I haven't prepared a patch for MythTV SVN yet, but that's not hard. See ticket #2241, that #define was renamed in SVN. I'll create a patch later when I can find some spare time.

This patch uncomments at #define. This can be done from inside the package Makefile using -D compile time flag. I have added the appropriated -D compile time flags to the mythtv packages. Could you check whether or not they work?

p.s.: Here's my minimyth-lib-list.iegd. It's missing some libGL file needed for hardware 3d acceleration. I think it's used in a way similar to the nvidia driver. I'll try to find out more

Code: Select all

# IEGD

libXiegd_escape.so.2.0.0
# these should be just symbolic links.
# I don't know if we should include them that way.
# They might be created as new files, ie the sym links might be followed
libXiegd_escape.so.2.0
libXiegd_escape.so.2
libXiegd_escape.so
# tv out encoder
xorg/modules/fs454.so
# the real driver
xorg/modules/drivers/intel_drv.so
# IEGD kernel modules
# I don't know if these are sane.
# Not sure about the correct syntax either :)
# modules/*/misc/iegd/
modules/*/misc/iegd/*

# we need libGL!!


Is libXiegd_escape needed?

libGL should get included as a result of other packages that depend on it. Does IEGD include binary libGL somewhere?

[Pablo]

dmidecode -t baseboard

Code: Select all

# dmidecode 2.9
SMBIOS 2.3 present.

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
        Manufacturer: To be filled by O.E.M.
        Product Name: To be filled by O.E.M.
        Version: To be filled by O.E.M.
        Serial Number: To be filled by O.E.M.

Handle 0x0026, DMI type 10, 6 bytes
On Board Device Information
        Type: Video
        Status: Enabled
        Description:   To Be Filled By O.E.M.



Well, so much for using DMI information to identify the hardware.

I guess the best thing to do for the graphics is to explicitly set MM_X_DRIVER=intel_iegd in minimyth.conf.

By the way, does this hardware have a sensor chip?

[laga]

Hey Pablo,

sorry for not replying. I was really busy with my finals. Now I've got a few weeks where I'll start playing with minimyth again (and provide you with the outstanding information)

Thanks for your patience

[ReKa]

Did anybody get a solution for the S100 in the last two years?

In the meanwhile ebay (at least in germany) is full of T-Online S100 boxes. You can get them for 20 € (used) to 46 € (new).

So I think there might be a lot of people out there who would appreciate minimyth on the S100.

-- ReKa

[Verzweifler]

Hi guys,

I'd like to *bump* again this topic, since I'd like to try MiniMyth on all my frontends now, which include TWO S100...

Thanks


Michael