WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Overlay initrd files using cat  (Read 31103 times)

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Overlay initrd files using cat
« Reply #75 on: January 24, 2011, 05:04:54 AM »
"include *all* these fancy networking devices" was not at all what I had in mind, but e.g. a Intel Pro 100 NIC (not uncommon to be found in laptops): the e100 driver of size 15KB getting loaded from base, but not in a working state until firmware which has a size of 539B is installed by user.

My point regarding ethernet support in base was that it could be debatable to include either drivers and respective firmware, or none of the both.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline hiro

  • Hero Member
  • *****
  • Posts: 1157
Re: Overlay initrd files using cat
« Reply #76 on: January 24, 2011, 06:20:16 AM »
Do other distributions include that firmware?

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Overlay initrd files using cat
« Reply #77 on: January 24, 2011, 06:25:20 AM »
Yes, and AFAIK, the singling out of firmware from drivers is a recent kernel development, with older versions there was no seperate firmware required, just the driver.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline Michael Wells

  • WikiUser
  • *
  • Posts: 17
Re: Overlay initrd files using cat
« Reply #78 on: January 29, 2011, 10:26:17 AM »
As I am trying to test the microcore + Xgui, I ran into a problem. This probably will not be an issue if tinycore.gz is replaced with microcore.gz and the GUI module gz's overlaid ... but when I tried to put the Xlibs.gz and Xprogs.gz and a Xvesa.gz (from xvesa.tcz) in the tce directory to be loaded at microcore boot time ... I ran into the following problem:  later when I rebooted tinycore.gz the gz's files in the tce directory were also loaded and the GUI was all messed up.

Perhaps I am doing something wrong in using the same tce directory to boot both microcore and tinycore with gz's inside ... but moving them out every time I want to boot tinycore is troublesome under the 3.x current configuration.

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Overlay initrd files using cat
« Reply #79 on: January 29, 2011, 10:38:22 AM »
You have absolutely no reason to boot tinycore.gz with the X gzs in the tce directory.
That will cause problems.
Use a different tce directory.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Overlay initrd files using cat
« Reply #80 on: January 29, 2011, 10:54:56 AM »
If I understood right, in this way you loaded two different Xvesa versions from cpio archives to different paths in the initramfs, which is an unforeseen case.

Besides from using separate tce dirs as gerald_clark suggested, loading the cpio archives via bootparam initrd= from a different path (e.g. where tinycore.gz resp. microcore.gz are located) would give most control, also in specifying the order of loading.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)