Mandriva 2010 on Dell Vostro V13 - ACPI issue, Battery & Touchpad not detected

ongte · 01-26-2010, 08:22 AM

Just got my hands on a brand new Vostro V13.
The ACPI on this machine seems to be screwed. If I bootup to the LiveCD normally, the touchpad & battery will not work, they are just not detected.

I managed to make Mandriva work better by passing noacpi to the kernel, This made the battery & touchpad start working. But then after installing it, the machine refuses to powerdown on shutdown & is complete incapable of any power management. (Obviously because there is no ACPI)

This machine very new, so can't find any information anywhere about it. It's actually a very simple CULV system. Video,Audio,Wireless,Bluetooth, they all work fine. Only the ACPI is screwed up.

Any ideas how to begin troubleshooting this?

GlennsPref · 01-28-2010, 01:17 AM

Hi, just for now, (being a new machine, the kernel devs will catch up, promise.

)

add the same command you used before to the kernel boot config command line.

You should find a place to configure it in MCC (Mandriva Control Center)
aka, "Configure Your Computer" boot.

you could also add the command to the grub list.file:///boot/grub/menu.lst

for instance, marked in red is not standard.

/boot/grub/menu.lst

Code:

timeout 2
color black/cyan yellow/cyan
gfxmenu (hd0,0)/gfxmenu
default 1

title desktop 2.6.32.3-2mnb
kernel (hd0,0)/vmlinuz-2.6.32.3-desktop-2mnb BOOT_IMAGE=desktop_2.6.32.3-2mnb root=UUID=93a866a5-8621-44ac-91b5-fc08153eff3a splash=none iommu=noaperture resume=UUID=18e353a7-a5f5-438b-9912-49b265ae0f56 PROFILE=default vga=794
initrd (hd0,0)/initrd-2.6.32.3-desktop-2mnb.img

title 2.6.31.6-1mnb_GamesBox-v=2
kernel (hd0,0)/vmlinuz-2.6.31.6-1mnb_GamesBox-v=2 BOOT_IMAGE=2.6.31.6-1mnb_GamesBox-v=2 root=UUID=93a866a5-8621-44ac-91b5-fc08153eff3a  splash=none iommu=noaperture vga=794 resume=UUID=18e353a7-a5f5-438b-9912-49b265ae0f56 PROFILE=default
initrd (hd0,0)/initrd-2.6.31.6-1mnb_GamesBox-v=2.img

title 2.6.33rc5-1mnb-GamesBox
kernel (hd0,0)/vmlinuz-2.6.33-0.rc5.1mnb-GamesBox BOOT_IMAGE=2.6.33rc5-1mnb-GamesBox root=UUID=93a866a5-8621-44ac-91b5-fc08153eff3a splash=none iommu=noaperture resume=UUID=18e353a7-a5f5-438b-9912-49b265ae0f56 PROFILE=default vga=794
initrd (hd0,0)/initrd-2.6.33-0.rc5.1mnb-GamesBox.img

title 2.6.33-desktoprc5-1mnb
kernel (hd0,0)/vmlinuz-2.6.33-desktop-0.rc5.1mnb BOOT_IMAGE=2.6.33-desktoprc5-1mnb root=UUID=93a866a5-8621-44ac-91b5-fc08153eff3a splash=none iommu=noaperture resume=UUID=18e353a7-a5f5-438b-9912-49b265ae0f56 PROFILE=default vga=794
initrd (hd0,0)/initrd-2.6.33-desktop-0.rc5.1mnb.img

title windows
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1

title MusicBox
root (hd2,5)
configfile /boot/grub/menu.lst

title linux
kernel (hd0,0)/vmlinuz BOOT_IMAGE=linux root=UUID=93a866a5-8621-44ac-91b5-fc08153eff3a splash=none iommu=noaperture resume=UUID=18e353a7-a5f5-438b-9912-49b265ae0f56 PROFILE=default vga=794
initrd (hd0,0)/initrd.img

the noapeture is because I do not have an AGP system, but pci express
vga=794 , nice small fonts during boot.
splash=none, well it don't work, but I prefer to see the boot messages as they occur, rather than the "blind" splash picture.

Hope this helps, and sure, it will eventually be fixed. But it may take up to 6 months.

I've been there with graphics cards and motherboards.

It's happening.

Cheers, Regards Glenn

ongte · 01-29-2010, 12:13 AM

Thanks Glenn, I've already sorted out grub. I'm actually thinking along the lines of how can I help the development along. But when it comes to this, I dunno what I'm doing.