Tiny Core Extensions > TCE Bugs

With TinyCore 4.2 grub finds no HDD

(1/2) > >>

chattrhand:
Hello and a Happy New Year to all,

my problem:
the bootloader of a new TinyCore 4.2 CD finds neither the builtin SATA nor IDE harddisks, hanging up.
However the boot options base norestore help TC to start, and then SATA and IDE drives are accessible.
I tried this on MacMini, iMac, DELL C540, LenovoR61ti with the same result.

So the frugal installations on the harddisk do not start, not even with full path added in the boot options; however, frugal installations on USB-stick can be started fine.

One workaround (a bit poor): booting TC 4.2 with base norestore and when it is up, install the extensions one by one from the local harddisk (or from internet if connected)

With the previous TinyCore up to 4.1 all of this frugal installations work fine.

I downloaded and burned TC with either of my computers listed above, all the same.

TC is a soapbox. But I love it.

chattrhand

chattrhand:
Hello to all,
meanwhile I found another workaround for TinyCore 4.2 booting:
Bootoption   tc norestore   starts TC 4.2 with all of the previously downloaded extensions, but without unpacking   mydata.tgz.   

So persistence of data and settings within TC 4.2 is not possible, you have to handle your working data on external drives (or you need TC 4.1).

A positive effect is a drastical acceleration of booting and rundown of TC. Probably this is also a good way to reduce writing operations on USB-sticks. 

TC is a soapbox. I love it
chattrhand

Juanito:

--- Quote from: chattrhand on January 14, 2012, 04:01:20 AM ---So persistence of data and settings within TC 4.2 is not possible, you have to handle your working data on external drives (or you need TC 4.1).

--- End quote ---

'not sure what you're saying here - the "norestore" boot code has been around since the very beginning of tinycore. If you want persistence, then don't use this bootcode.

tweetyhack:
If you use "base" and you get your SATA and IDE drives, then some extension or something is causing to problem. Sounds like you've isolated the problem to mydata.tgz. If you can look inside it and see if there is anything in there that is blocking your drives.

Rich:
Hi chattrhand
Lets start with the basics. Boot your machine using the  norestore  boot code and install  cdrtools.tcz.
Burn a new disc using the following command:

--- Code: ---cdrecord dev=/dev/sr0 padsize=63s -pad -dao -v -eject filename.iso
--- End code ---
Replace  sr0  with the device name for your CD drive. This is to ensure you are starting with an error
free disc. Reboot with the new disc and see if it behaves any better. If it doesn't, do the following:
Post the output of   cat /opt/.filetool.lst   Note: There is a period in front of  filetool
Enter the command   dmesg > dmesg.txt   and attach the file  dmesg.txt  to your next post.

Navigation

[0] Message Index

[#] Next page

Go to full version