[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems at booting after installation or Dist-upgrade with SARGE at ACER-Notebook



Hi,
     I have Acer 4102 and I experienced exactly same problem with Debian 3.1. Somehow I could resolve it by recompiling 2.6.12 kernel with appropriate options. If I understood properly ur not able to boot into ur system. The following is what I did and it works for me (but there should be better ways of doing this)
1. Installed with linux26 acpi=off boot option. Installation went well, but did not boot.
2. Problem comes from hotplug...which is trying to load some non existing modules.
3. So I used knoppix (another wonder) to boot into my laptop and removed hotplug (temporarily).
          a. fdisk -l to know ur partition and mount it somewhere (may be on /mnt or where ever).
          b. chroot into /mnt and use aptitiude or apt-get to remove hotplug.
4. Reboot and u should be able to boot.
5. Now first thing to doo..is to recompile 2.6.12 and then reinstall hotplug.

Thats it...
regards.


On 7/26/05, debian@linuxmaker.de <debian@linuxmaker.de> wrote:
Hello,

I have a problem with my new notebook and Debian Version 3.1
Hardware:
ACER Extensa 4101WLMi_MCE
Pentium® M 730 Centrino
1024 MB PC2700 DDR-SDRAM
ATI® Mobility™ RADEON™ X700 128 MB
Soundchip onboard
Intel PRO/Wireless 2200BG, 802.11 b/g

First, I have installed "Debian Sarge prerelease" from DVD with kernel 2.4
which is on that DVD. With kernel 2.6 I have had any problems with booting
the installer:
linux26 noapic nolapic           - the install routine hangs up
linux26 noapic nolapic vga=771 agp=noagp   -  the installer begans and runs
until "floppy", then the monitor became red.

The same problems I have with the latest CD from June 2005, only following
will run correctly
linux26 apm=off acpi=off

Now I have made a dist-upgarde with the installed Version of  "Debian Sarge
prerelease" kernel 2.4 over the Internet. After the first reboot I got the
same problems like I get also with the 2.4- and 2.6.-versions at the latest
CD.
First I saw at booting:
"PNPBIOS: fault attempting recovery
pnp dock_thread: unexpected status 0x28"

Also, I made a new installation with the following parameters:
boot: linux26 apm=off acpi=off pnpbios=off

Whether I used the 2.4 or the 2.6-kernel a part of the boot-messages looks
like here:
"Unable to handle kernel NULL pointer dereference at virtual address 00000024
printing eip:
e0cb71d2
*pde = 00000000
Oops: 0000
CPU: 0
EIP:   0010:[<e0cb71d2>]  Not tainted
EFLAGS: 00010246
eax: ffffffff      ebx: 00000000   ecx: daa32400   edx: daa32400
esi: dfe78c00  edi:  00000000   ebp: dd4d6080   esp: dc9e9e34
ds:  0018   es: 0018  ss: 0018
Process modprobe (pid: 547, stackpage=dc9e9000)
Stack: 00000282 00000246 c02c54c12 00000246 daa32400 dfe78c00 dd4d6118
dd4d6080
           e0cbafd7 dd4d6080 ffffffff 00000000 0057e820 0001d4d6080 00000a04
           00000000 00000000 dd4d60b0 daa32400 00000000 00000000 00000001
00000000
Call Trace: [<e0cbafd7>] [<e0cbce28>] [<e0cbb6f2>] [<e0cbc042>] [<e0cbce28>]
[<e0cbcf40>] [<c01b4195>] [<e0cbce28>] [<e0cbcf40>] [<c01b423c>] [<e0cbcf40>]
[<e0cbbddb>] [<e0cbcf40>] [<c011d1f2>] [<e0cb7060>] [<e0cbcbe8>] [<e0cb7060>]
[<c0108c0b>]


Code: 8b 43 24 8b 48 08 85 c9 75 27 0f b7 82 16 02 00 00 83 e0 fb
./pci.agent: linie 156:   547 Segment fault     $MODPROBE $MODULE >/dev/null
2>&1
i810_audio: can't be loaded
missing kernel or user mode driver i810_audio
<3>i810_rng: RNG not detected
insmod: /lib/modules/2.4.27-2-686/kernel/drivers/char/i810_rng.o: init_module:
No such device
insmod: Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.27-2-686/kernel/drivers/char/i810_rng.o: insmod
i810_rng failed
i810_rng: can't be loaded
missing kernel or user mode driver i810_rng
hw_random: RNG not detected
insmod: No such device
lib/modules/2.4.27-2-686/kernel/drivers/char/hw_random.o: init_module: insmod:
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.27-2-686/kernel/drivers/char/hw_random.o: insmod
hw_random failed
hw_random: can't be loaded
missing kernel or user mode driver i810_rng"

Now, can somebody explain me where is me problem and how I can resolve it?
I have thought to use the kernel 2.6.8-386, but I found no possibillity to
choice it at the installation and after that the system hangs up.

I hope you can help me and other people with the same problem
( www.debianforum.de/forum/viewtopic.php?t=50541&postdays=0&postorder=asc&start=0)

Many regards

Andreas Günther



Reply to: