WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Booting problem on Dell Inspiron 2500 laptop  (Read 1632 times)

Offline OldAdamUser2

  • Full Member
  • ***
  • Posts: 199
Booting problem on Dell Inspiron 2500 laptop
« on: December 05, 2009, 05:33:10 AM »
I'm trying to put TC on a Dell Inspiron 2500 laptop and find that it hangs during boot-up as the core is examining  pci interfaces--specifically, "PCI bridge, secondary bus 0000:01". I used to use DSL on this computer and seem to recall having to feed it the noscsi cheat code in order to avoid a similar problem.
That code has no effect in this case.

Does anyone have any hints or tips? I tried noscsi, laptop, and vga=773 without result.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9624
Re: Booting problem on Dell Inspiron 2500 laptop
« Reply #1 on: December 05, 2009, 05:50:25 AM »
Using the "debug" bootcode, please post the last few lines of output.

noacpi, noapic, nolapic might be worth a try.
The only barriers that can stop you are the ones you create yourself.

Offline OldAdamUser2

  • Full Member
  • ***
  • Posts: 199
Re: Booting problem on Dell Inspiron 2500 laptop
« Reply #2 on: December 05, 2009, 07:20:11 AM »
The last few lines are:

pci 0000:00:1e.0: PCI bridge, secondary bus 0000:01
pci 0000:00:1e.0:   IO window: 0x2000-0x2fff
pci 0000:00:1e.0:   MEM window: 0x28000000-0x31ffffff
pci 0000:00:1e.0:   PREFETCH sindow: 0x00000020000000-0x00000027ffffff

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9624
Re: Booting problem on Dell Inspiron 2500 laptop
« Reply #3 on: December 05, 2009, 09:48:47 AM »
Well, pci=off turns pci scanning off completely. But it might disable some of your devices.
The only barriers that can stop you are the ones you create yourself.

Offline OldAdamUser2

  • Full Member
  • ***
  • Posts: 199
Re: Booting problem on Dell Inspiron 2500 laptop
« Reply #4 on: December 05, 2009, 12:06:59 PM »
pci=off did take it further along in the boot process, but then it ended in a kernel panic.

No worries, it's a secondary computer only, and it does run Windows XP and Puppy. I prefer Tiny Core, but perhaps some things are not meant to be.