Core v4.4

[ibaloo]

if You have/use X then
AppsAduit -> Dependencies -> Build Reporting Database -> Fetch Missing

or if you only use Core (no X) or Xorg did not start and only have a system prompt use:
tce-audit builddb
tce-audit fetchmissing

The release notes until the end I will read
The release notes until the end I will read
The release notes until the end I will read
The release notes until the end I will read
...
(x100)
....


Thanks, it works fine now.

[yoshi314]

Hi,

The 4.4 release doesn't work for me. X refuses to start and complains for a missing  /etc/sysconfig/xsession => Back to 4.3
simple and good ideas (I love Tiny core System Stats). Haven't seen such clever thing since the Thinstation project.

did you install it with tc installer? afaik that file is generated from desktop= parameter.

try installing e.g. fluxbox and adding desktop=fluxbox to boot parameters and see if that works.

[b1ackmai1er]

I seem to be having update issues as well. I was running 4.4RC2 and upgraded to 4.4 using the copy vmlinuz and core.gz method.

Like others it just booted to command line. I ran the Appsaudit steps which seemed to only load some dev file for the compile module
I downloaded the Xprogs module and then it would boot into the windows manager.

However, whereas with 4.4RC2 my boot disk would come up as /mnt/sdb1/ it now comes up as /mnt/sdc1/ which is a real problem because it has broken all the configurations for my installed programs.

What seems to be different with RC2 and the final is that the boot disk seems to mount really late in the final. So before installing Xprogs I would hit the command line but then the console message would come up with the boot drive being recognized.

Dunno if this explains anything.

I can rework all my script and update my configuration files but I am worries that the boot behaviour might change again.

Regards b1ackmai1er

[Rich]

Hi b1ackmai1er
You can make your scripts mountpoint agnostic:

Code: [Select]

tc@box:~$ blkid /dev/sda2
/dev/sda2: UUID="cf1bbc2f-abba-4032-8609-1d3789d269fe" TYPE="swap"
tc@box:~$ blkid -U cf1bbc2f-abba-4032-8609-1d3789d269fe | cut -c6-
sda2
tc@box:~$
In this example you would add the following to the beginning of your script:

Code: [Select]

MyDrive=`blkid -U cf1bbc2f-abba-4032-8609-1d3789d269fe | cut -c6-`and replace all references to  sda2  with  $MyDrive.

[b1ackmai1er]

@Rich

Thanks. I will definitely try that.

Regards b1ackmai1er

[Juanito]

I can confirm core64 v4.4 works fine 

The combination of new kernel version/new alsa version still doesn't seem to make my Cirrus Logic CS4206/Intel CougarPoint HDMI sound hardware work without intervention from HDA Analyzer though 

Edit: ..but, whereas I needed to patch the 3.0.3 kernel btusb module to work with my "Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)" hardware, things work fine "as-is" with the new kernel 

[vinnie]

Today I tried to upgrade core 4.2 -> 4.3 but the result was not positive.
First i update dependency, after i update package and after i fetch missing dependency, I replaced the following core.gz and vmlinux and restart.
At reboot xorg not run, during run of pack this package is missing ;
graphics-3.0.21-tinycore.tcz
v4l-dvb-3.0.21-tinycore.tcz
wireless-3.0.21-tinycore.tcz
(de facto making me impossible to even connect, i have only wireless connection).

Fortunately I never do an upgrade without backing up the partition of Core
I put old vmlinux and Core.gz and I restarted, for now the hybrid goes on (new xlibs Xprogs is overlapped).

I try new search of missing dependecies after a new dep update: only elfutils-lib for prelink and wine.

Code: [Select]

tc@box:~$ tce-audit fetchmissing
Downloading: elfutils-lib.tcz
elfutils-lib.tcz: OK

I try to search manually mi actual possession of module:

Code: [Select]

tc@box:~$ find /mnt/sdb1/tce/optional/ -iname "*3.0.3*"
/mnt/sdb1/tce/optional/OSS-modules-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/input-tablet-touchscreen-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/i2c-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/v4l-dvb-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/virtualbox-ose-modules-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/bluetooth-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/input-joystick-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/pci-hotplug-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/alsa-modules-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/alsa-modules-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/firewire-3.0.3-tinycore.tcz.dep
/mnt/sdb1/tce/optional/firewire-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/wireless-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/firewire-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/v4l-dvb-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/input-joystick-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/wireless-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/virtualbox-ose-modules-3.0.3-tinycore.tcz.dep
/mnt/sdb1/tce/optional/OSS-modules-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/i2c-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/bluetooth-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/v4l-dvb-3.0.3-tinycore.tcz.dep
/mnt/sdb1/tce/optional/graphics-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/input-tablet-touchscreen-3.0.3-tinycore.tcz.dep
/mnt/sdb1/tce/optional/pci-hotplug-3.0.3-tinycore.tcz
/mnt/sdb1/tce/optional/graphics-3.0.3-tinycore.tcz.dep
/mnt/sdb1/tce/optional/virtualbox-ose-modules-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/input-tablet-touchscreen-3.0.3-tinycore.tcz.md5.txt
/mnt/sdb1/tce/optional/alsa-modules-3.0.3-tinycore.tcz.dep
/mnt/sdb1/tce/optional/graphics-3.0.3-tinycore.tcz

in contrast to:

Code: [Select]

tc@box:~$ find /mnt/sdb1/tce/optional/ -iname "*3.0.21*"
/mnt/sdb1/tce/optional/linux-headers-3.0.21-tinycore.tcz
/mnt/sdb1/tce/optional/linux-headers-3.0.21-tinycore.tcz.md5.txt
I had downloaded the header at the prospect of future compilations

now I download the rest of missing module by hand, but it seems right to communicate on the forum to expose the issues to those who know more than me

[roberts]

First i update dependency, after i update package and after i fetch missing dependency, I replaced the following core.gz and vmlinux and restart.

That is backwards from posted instructions:


Update instructions, from the release distribution files area:
http://distro.ibiblio.org/tinycorelinux/4.x/x86/release/distribution_files/
1. Copy over new vmlinuz
2. Copy over new core.gz
3. boot into new system

if You have/use X then
AppsAduit -> Dependencies -> Build Reporting Database -> Fetch Missing

or if you only use Core (no X) or Xorg did not start and only have a system prompt use:
tce-audit builddb
tce-audit fetchmissing

[vinnie]

I figured the problem, I had to reboot the machine before to update modules for the reason that it use a variable for the version of the "kernel" in the package name.

in the steps listed by robert the order is right but it was too implied that I would understand.

However I could not install wireless packages after restarting (i do not having other way to connect), I was obliged to do so first, consider this for the next (kernel) update!

another problem, I think derived from the lack of virtualbox module: the fetchmissing has not downloaded Input-tablet-touchscreen and pci-hotplug. it has stopped at error of virtualbox:

Code: [Select]

tc@box:~$ tce-audit fetchmissing
Downloading: OSS-modules-3.0.21-tinycore.tcz
OSS-modules-3.0.21-tinycore.tcz: OK
Downloading: bluetooth-3.0.21-tinycore.tcz
bluetooth-3.0.21-tinycore.tcz: OK
Downloading: firewire-3.0.21-tinycore.tcz
firewire-3.0.21-tinycore.tcz: OK
Downloading: virtualbox-ose-modules-3.0.21-tinycore.tcz
Error on virtualbox-ose-modules-3.0.21-tinycore.tcz
tc@box:~$

at the end, after several builddb, I was forced to download them by hand.

[vinnie]

another reason could be that in my case the modules are not required by any other package, I belive this is more probable.

[roberts]

If wireless is the only network then you would ONLY have to pre-download any 3.0.21 wireless modules for the posted procedure to work. You have to be booted from the new kernel in order for the other new 3.0.21 files to be updated by AppsAudit. Doing it backwards AppsAudit would not know that a new kernel was about to be installed!

[vinnie]

Thanks, now everything is very clear, fortunately this only happens when a new kernel is on the way 

[AbNoRMiS]

when using nozswap bootcode then began to show something after boot

udevadm settle - timeout of 5 seconds reached, the event queue contains:
/sys/devices/virtual/bdi/7:6 (941)
/sys/devices/virtual/bdi/7:6 (7417)
/sys/devices/virtual/bdi/7:6 (7906)
/sys/devices/virtual/bdi/7:6 (8396)

[AbNoRMiS]

i would like to add that when i tried nozswap bootcode with kernel 3.0.3 then displayed a bit other messages

udevadm settle - timeout of 5 seconds reached, the event queue contains:
/sys/devices/virtual/block/loop5 (938)
/sys/devices/virtual/block/loop5 (966)
/sys/devices/virtual/block/loop5 (7414)
/sys/devices/virtual/block/loop5 (7903)
/sys/devices/virtual/block/loop5 (8393)

[curaga]

Those messages are harmless.