Tiny Core Base > TCB Q&A Forum

Help install TC - doesn't find the hard disk

<< < (3/4) > >>

maro:
jano: You mentioned that 'acer-puppy' manages to "find your HD". Why don't you compare the 'dmesg' output after booting with that CD, with the one you've extracted from TC?

Furthermore, what is the output that you get on 'acer-puppy' when executing the following command: fdisk -l

BTW, your 'dmesg' output is "a bit short". For reasons I'm not quite sure off the beginning seems to be "lost". To extract a more complete version, I'd suggest to start TC with a boot code of 'syslog', and then grab the '/var/log/messages' file.

jano:
Thanks for the reply.

I attach the dmseg report created with tinycore (I've used $ dmesg > tc-dmesg.txt to output it to a file, and I have then compared it with the report shown with control panel -> system statistics and they were identical). Note that there surely is a difference with the previously attached, as this one was created booting from a pendrive (sda1) while the former was created after booting from an external (usb) CD drive.

I have also attached the dmseg report from acer-puppy and the fdisk -l -> they seem to find the harddisk and its partitions without problem

jano:
No luck either with TC 2.10 final :(
GuessI'll  have to wait for TC 3 ;)

maro:
jano: I found it rather difficult to compare the acer-puppy with the TC results due to the unknown state of your hardware. I can "see" that there are different USB connected devices involved in each case, but this is what makes it so cumbersome.

You could give it one more shot using exactly the same hardware configuration to boot either OS e.g. using a CD-ROM. Use boot code 'syslog' for TC, so that you can provide the '/var/log/messages' file for either OS for comparison. Please note one could use sed -e "/ kernel: /!d" -e "s#.* kernel: ##" /var/log/messages > dmesg- to extract a more complete "quasi-dmesg" output. You also might want to describe the relevant hardware in more detail, e.g. in the 'fdisk -l' output for acer-puppy the fact that there is a 'Compaq diagnostics' partition seems a bit unusual to me. Could you provide more details about the use of these partitions? Am I correct to assume that this '/dev/sda' represents a 160GB Seagate SATA disk that TC does not detect?

curaga:
maro, see PATA_SCH. It's rather unfortunate that this chipset doesn't run with the generic driver.

Navigation

[0] Message Index

[#] Next page

[*] Previous page