LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Installation error: Address space collision (https://www.linuxquestions.org/questions/slackware-14/installation-error-address-space-collision-879734/)

dr.s 05-09-2011 06:37 PM

Installation error: Address space collision - Toshiba Satellite laptop
 
Hi folks,
I've got Slackware 13.37 up and running without a hitch on a desktop and a laptop. I'm trying to install it on a new Toshiba laptop (spec provided below). Unfortunately the installer crashes right after pressing enter at the boot prompt (I went with the default kernel without entering any parameters). Some traces scroll by quickly, then the last few lines just before it freezes:

...
pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000cc000-0x000cffff] conflicts with Video ROM [mem 0x000c0000-0x000cf1ff]
pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000d0000-0x000d3fff] conflicts with Adapter ROM [mem 0x000cf800-0x000d07ff]

I've installed Slackware quite a few times but I'm clueless as to what goes on under the hood and this is the first time the installer fails on me. Any clues? should I provide some boot parameters to the kernel or disable something?

-Toshiba Satellite L650D-063
-AMD Phenom™II Quad-Core Mobile P960 processor 1.8GHz, 15.6” LED HD, ATI Mobility Radeon™ HD 5650, 4GB DDR3, 750GB HDD S-ATA, DVD Super-Multi Double Layer, LAN, Realtek Wireless 802.11 bgn, Integrated Web Camera, HDMI

Yes, the laptop comes with Windows 7, which I promptly remove without any regrets :)

Thanks in advance.

allend 05-09-2011 06:50 PM

Try booting with the "acpi=copy_dsdt" kernel parameter.
http://www.linuxquestions.org/questi...7/#post4345857

dr.s 05-09-2011 09:53 PM

Tried that and got the same error. Out of curiosity I downloaded the usbboot.img from Slackware 13.1 and was able to boot successfully.

dr.s 05-12-2011 10:57 AM

I was able to boot using the 13.1 usbboot image, then went through the excercise of installing both Slackware 13.1 (which boots up and works well, except for wireless) and then Slackware 13.37 from a dvd iso image, but seem to be hitting a brick wall. Slack 13.37 just does not boot up.
Given the same hardware, one kernel works and a newer one fails, you can't help but think the new kernel is broken somehow. Trying various combinations of kernel parameters did not make a difference.

After some google searches, I realized a bit late that Toshiba was not the best choice to work with Linux. I would stick with Slackware 13.1, but a laptop without wireless would be somewhat useless (the driver package provided by Realtek did not compile in 13.1, while ndiswrapper + xp driver failed to load with ntoskernel.exe errors).

Are there any other possible tricks or tweaks that can be tried to bring 13.37 to life on this laptop? otherwise it will be doomed to have Win 7 restored on it :)

Thanks.

tobyl 05-12-2011 01:37 PM

hi dr.s

As allend has suggested, this looks like a buggy bios.
The first thing I would do is check for bios updates. Also there may be a bios setting relating to shared video memory that you could experiment with.
There are some very involved ways to fix buggy bioses, but beyond the scope of this forum.

If you run 13.1 and are able to recompile your kernel, you could try the staging drivers for rtl wireless chipsets (not sure which wireless chip you have - lspci as root would tell us). I have an RTL8192 chip in my netbook which started working with the staging driver found in more recent kernels.
If you are up to recompiling kernels (which you would need for the preceding suggestion anyway), you could try an earlier or later kernel with 13.37. To do this, I would boot with a working kernel (your usb.boot image?), then mount and chroot into the 13.37 directory structure, copy over the new kernel and recompile. Its all a bit fiddly if you are new to linux, but possible.

I could give you a few more hints if you want to try.

tobyl

hf2046 05-12-2011 02:55 PM

It looks (from a bit of Googling) that your wireless card is a Realtek 8188 CE. There is support for it in the 2.6.38.x kernels. What I would advise is for you to boot using Slack 13.1, download the latest 2.6.38.x kernel source from kernel.org and build it for your machine. Then reboot and verify that the kernel works. After that, configure your wireless and then upgrade the machine to 13.37 following the instructions on the DVD.

dr.s 05-21-2011 11:02 AM

Quote:

Originally Posted by hf2046 (Post 4354621)
It looks (from a bit of Googling) that your wireless card is a Realtek 8188 CE. There is support for it in the 2.6.38.x kernels...

Thanks for the feedback hf2046
Yes it's an RTL8188CE, newer kernels support it but the problem is the retarded bios that comes with this Toshiba laptop, which newer kernels fail to boot with. I got around this by downgrading Slackware 13.37 to the lowest kernel that would boot (2.6.35.13) and where the driver provided by Realtek would compile (The staging driver did not work).

dr.s 05-21-2011 11:32 AM

Quote:

Originally Posted by tobyl (Post 4354564)
hi dr.s

As allend has suggested, this looks like a buggy bios.
The first thing I would do is check for bios updates. Also there may be a bios setting relating to shared video memory that you could experiment with.
There are some very involved ways to fix buggy bioses, but beyond the scope of this forum.

If you run 13.1 and are able to recompile your kernel, you could try the staging drivers for rtl wireless chipsets (not sure which wireless chip you have - lspci as root would tell us). I have an RTL8192 chip in my netbook which started working with the staging driver found in more recent kernels.
If you are up to recompiling kernels (which you would need for the preceding suggestion anyway), you could try an earlier or later kernel with 13.37. To do this, I would boot with a working kernel (your usb.boot image?), then mount and chroot into the 13.37 directory structure, copy over the new kernel and recompile. Its all a bit fiddly if you are new to linux, but possible.

I could give you a few more hints if you want to try.

tobyl

Hi tobyl
this is not a slackware problem but a bios issue, as i tried different kernels and even installed the latest Ubuntu distro to verify it :) All kernels newer than 2.6.35.13 would crash on startup.
There wasn't much I could find in the way of bios updates or shared memory settings to tweak. However I followed your instructions above and they worked to a tee, basically booting with usbboot.img from Slackware 13.1 and installing 13.37 then chroot'ing into its directory structure and re-compiling an older kernel, tried this with a few kernels (spent hours on this) and 2.6.35.13 was the highest kernel that worked for me and where the Realtek driver compiled and worked (The staging driver did not) so now I got a working 13.37 with working wireless but with an older kernel, hope that doesn't have any bad side effects but will buy me time, perhaps wait for newer kernels that might work etc.

I'm still playing around with various boot parameters and the 13.37 usbboot image with its newer kernel, and by chance i got it to boot without errors by adding pci=bios
Unfortunately, once booted, the kernel does not seem to see the hard disk. Running "fdisk -l" or lspci returns nothing at all. Is there a known kernel parameter that somehow forces reading this information? there's just way too many combinations to do this by trial and error :)

tobyl 05-22-2011 11:44 AM

dr.s

If you haven't already, could you try the pci=nocrs boot parameter

tobyl

dr.s 05-23-2011 07:09 AM

tried it, kernel freezes at a different stage but without the address space errors:
...
PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])

Bjorn Helgaas 06-30-2011 06:07 PM

The host bridge window conflict messages themselves are harmless.

If you see a hang, please report it as a bug on http://bugzilla.kernel.org or LKML (linux-kernel@vger.kernel.org). If you boot with "ignore_loglevel" and use a serial console or even take a photo of the screen after the hang, that would be useful information.

animeresistance 09-25-2011 06:14 PM

Hello ..

Maybe you can update the bios using windows ...

Or maybe kernel 3.x can make the trick ... who knows?

Cheers.


All times are GMT -5. The time now is 08:33 PM.