Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: peter76 on December 17, 2011, 05:10:42 PM
-
Hello, just new here, but know some Linux. I 'm playing around with TC on an old Toshiba 300cdt ( Pentium 166, 84 MB ram ). It boots fine from cdrom, only have to pass xsetup to get to the desktop correctly, but then I can't find the cdrom or the harddrive. "fdisk -l" doesn't give me anything, and I can't find anything either in dmesg about ide or hda or whatsoever... Harddrive has a swap and ext3 partition made under DSL, so it's not broken. What am I missing here?
Regards, Peter
-
Hi peter76
Open a terminal and enter:
dmesg > dmesg.txt
and attach the file to your next post.
Pentium 166, 84 MB ram
Stop bragging, it's very unbecoming.
-
Please post dmesg output from TC, and which ide driver is used under DSL/other linux.
-
Pentium 166, 84 MB ram
Stop bragging, it's very unbecoming.
Lol, I shall not anymore...
Here's the dmesg.
Regards, Peter
-
Hi peter76
Looks like it's finding IDE1:
pnp 00:0a: [io 0x0170-0x0177]
pnp 00:0a: [io 0x0376]
pnp 00:0a: [irq 15]
pnp 00:0a: Plug and Play ACPI device, IDs PNP0600 (active)
But there is probably nothing connected to that. It looks like this may be grabbing the I/O addresses
(0x1F0-0x1F7) required by IDE0:
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x220-0x22f 0x330-0x337 0x370-0x37f 0x388-0x38f
Just a guess on my part, but try adding the boot code:
pnp_reserve_io=0x1F0,8
-
Hi peter76
Looks like it's finding IDE1:
pnp 00:0a: [io 0x0170-0x0177]
pnp 00:0a: [io 0x0376]
pnp 00:0a: [irq 15]
pnp 00:0a: Plug and Play ACPI device, IDs PNP0600 (active)
But there is probably nothing connected to that. It looks like this may be grabbing the I/O addresses
(0x1F0-0x1F7) required by IDE0:
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x220-0x22f 0x330-0x337 0x370-0x37f 0x388-0x38f
Just a guess on my part, but try adding the boot code:
pnp_reserve_io=0x1F0,8
Hi Rich,
Tried that, but doesn't give me anything; also tried pnp_reserve_io=0x170,8, which seems more logical from your reply, but then I haven't got a clue what all this hex is about.
BTW, I tried noapic, nolapic, disabling dma and so forth to no avail.
Thanks for the help, and hope you or someone's got another clue.
Regards, Peter
-
Hi peter76
I'd like you to do two things. Burn Tinycore version 3.4 to a disk and see if that behaves any better.
Also, if you can, attach a copy of dmesg from DSL. Here is a link to TC3.4:
http://distro.ibiblio.org/tinycorelinux/3.x/archive/3.4/ (http://distro.ibiblio.org/tinycorelinux/3.x/archive/3.4/)
-
Hi Rich,
TC 3.4 recognises the hd and cd fine, also attaching the dmesg here. Curious what you find.
Regards, Peter
-
Hmmm, I'm not really sure if I want to take a look into a v2.4 kernel boot process output, but maybe it would help to know what PCI devices are on your system.
So maybe you could try to install 'pci-utils.tcz' (e.g. on the working TC 3.x system) and attach here the output of lspci -nnvv
Or if that is too cumbersome maybe the output of cat /proc/bus/pci/devices will be able to provide some kind of information.
-
Hi peter76
There is a lot of data to sift through, but this did catch my attention:
TC3.4
pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
TC4.?
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
See if the boot code pci=nocrs makes any difference.
-
Oh, it's an ISA controller and used the generic driver previously. I'm afraid that it's still marked experimental under the new ata layer, to which we moved in tc4 and so disabled in our config.
You could either run latest TC3, or compile your own kernel for the device.
-
Hi curaga
One of the reasons I had him try TC3.4 is because the old driver was still in there. I thought I read
somewhere that TC3.8.4 was libata only, and was not sure when the transition was made. Only one
way to be sure I guess, try booting TC3.8.4.
-
We generally don't change kernels in major series, the latest TC3 is still ide.
-
Hi peter76
There is a lot of data to sift through, but this did catch my attention:
TC3.4
pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
TC4.?
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
See if the boot code pci=nocrs makes any difference.
On my old box (98'), I had similar dmesg messages.
For both 3.8 and 4.x I have to use "pci=use_crs" in order to start xorg7.4 or 7.6.
And noacpi for making running xorg.
here are my boot codes
blacklist=snd_usb_audio
quiet
printk.time=1
vga=788
tz=CET-1CEST,M3.5.0,M10.5.0/3
showapps
lst=coreorgl.lst
home=sdc3
mydata=corexorg
tce=LABEL=CF_OldBoy/tce42
pnpbios=off
pci=use_crs
noisapnp
nozswap
noacpi
Perhaps it helps.
-
Hello all, thanks for all the replies!
I'd already given the nocrs thing a try to no avail, also lspci didn't give me anything on an ide controller, but as I understand now the version of libata in 4.1 doesn't work with my hardware...
I just burned and booted 3.8 and this works so I got something to play with:-)
If I can do some more checking with 4.1, please let me know.
Regards, Peter
-
Hi peter76
Based on what curaga wrote, it doesn't sound like there is anything left to try.
-
Hi Rich, no thought so, but thanks for all the help:-)
Peter
-
Hi peter76
Your welcome.