CD/DVD drive not detected on Lenovo3000-N200 with ACPI enabled

Forgot to add, but the Laptop also does not shut down to power off without using the power button.

It's probably better if you file separate issues for each of these problems. They may or may not be related. If they aren't related then it makes for confusion on the bug report.

For your wireless issue, see if running the following commands in a terminal helps:

  sudo modprobe -r acer_wmi
  rfkill unblock all

It seems that acer_wmi is sometimes matching against the WMI device on some Lenovo models, and when it gets loaded it's compatible enough to function at a basic level but incompatible enough to break things. I'm not sure what the resolution is, but if the above gets your wireless working then it will at least confirm that this is behind your wireless issue.

The commands you suggested worked once and wifi was activated, but when I rebooted wifi was not activated and your commands did not work again. Any ideas what that would suggest?

Happy to move the wireless problem to another bug, will do shortly.

I have logged the Wireless problem on Bug #857297

The acpi affecting the CDRW/DVDRW and battery power management functions is still an issue on this ticket.

I have done much testing to no avail so far. Seems like maybe something to do with ata_piix but not sure. There are so many reports across the www of people losing cdrom in relation to acpi after installing upgrades of linux. It's hard to believe there isn't an answer.

Simply put, if I disable acpi=off in the grub boot menu then the cdrom works.

But it is not acceptable to turn off acpi as it is required for much of the other hardware functionality, one of which is power management that is very important when running on battery. Hope someone can point me in the right direction of something new to try.

Output with acpi disabled --> acpi=off
# dmesg | grep sr0
[ 2.498187] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.498358] sr 0:0:1:0: Attached scsi CD-ROM sr0
[ 5684.010205] VFS: busy inodes on changed media or resized disk sr0

Output with acpi enabled
# dmesg | grep sr0
(no output)

Output with acpi disabled --> acpi=off
# lsscsi
[0:0:1:0] cd/dvd HL-DT-ST DVDRAM GMA-4082N TX07 /dev/sr0
[2:0:0:0] disk ATA Hitachi HTS54503 PB3O /dev/sda

Output with acpi enabled
# lsscsi
[2:0:0:0] disk ATA Hitachi HTS54503 PB3O /dev/sda
(no cd/dvd exists)

Tearing my hair out... whats left of it lol :)

Hi Seth, attached dsl files.

Regards,
Graham.

dsl0

dsl1

Hi Seth

Hope I did this right, I can only appear to attach one file at a time.

Have attached each of the following:
DSDT.DSL
SSDT0.dsl
SSDT1.dsl
SSDT2.dsl

Regards,
Graham.

Still no luck with CDRW/DVDRW not functional after much playing around, still tearing my hair out, I dont want to reload Windows :(

Please test the latest mainline build (v3.1-rc9 currently) and see if the issue still exists there. Instructions for installing mainline builds can be found at the link below. Thanks!

https://wiki.ubuntu.com/Kernel/MainlineBuilds

Hi Seth,

With v3.1-rc9 installed....

CDRW/DVDRW does not work
Wireless does not work again - should I put this bit on the wireless bug?

On Wed, Oct 12, 2011 at 12:43:33PM -0000, Graham Parker wrote:
> Hi Seth,
>
> With v3.1-rc9 installed....
>
> CDRW/DVDRW does not work

Okay, thanks for testing.

You mentioned something about reports of people loosing cdrom after
upgrading. Was there a previous version where your cdrom did work?

> Wireless does not work again - should I put this bit on the wireless bug?

No, it just doesn't have the fix I generated yet.

Oh yes, just from searching for any answers, it seems there a others experience similar. Maybe same issue maybe not.

The last version I recall where the cdrom mounted ok was Ubuntu 10.10 as I recall. I went back to my original Vista builld as there was some software I needed to use, but now longer require this so am back on Ubuntu, where I prefer to be, but I don't really want to go back to an older version, and not enjoy the benefits of the latest version of Ubuntu and Kernel.

I'm not suggesting that you should go back, but if it worked in a previous release then we can probably find what changed to break it.

Maverick is based off of kernel 2.6.35. So why don't you try installing the following three mainline builds, in order, until you find the first one where the CDROM doesn't work, and then let me know which kernel that is.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-maverick/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-natty/

After you install these builds you'll need to reboot, then press the Shift button immediately after the BIOS screen disappears, and hold it until a menu comes up. Use your keyboard to navigate to the "Older kernel versions" option, then select the kernel version that you are testing.

Note that after testing a kernel and booting into a different one, it's perfectly fine to remove the test kernels. It's not recommended to remove the kernel you are currently using, however.

Thanks!

Hi Seth

Thanks, I'll give those versions a go and let you know.

Sorry, I wasn't meaning you were suggesting I should back rev to an older version permantly, was just a thought I had re: keeping up with the newer versions which I just happen to express above :)

Just clarifying, I tried each of the kernel versions above and the CDROM didnt work with acpi enabled for each.

That's odd, given that 2.6.35 was the version used in 10.10. Let's go back further then. Start at the beginning of the list, and you can stop at the first one you test that doesn't work.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/

Will do Seth, I'll test as above.

Very strange, none of these worked either? So what does that mean? I don't understand...

If none of those work, it means your CD drive should have been broken at least as far back as lucid (10.04). Lucid is based off the 2.6.32 kernel. Are you sure that it worked in at least one of 10.04 or 10.10?

I was sure it did, becasue I used to play the odd music CD, I must be going mad :) I do recall using KDE at one part, so I installed this on 11.10 but still no good. I wouldn't think KDE would have any effect on the CD operation though. Is there something that I would need to compile into the Kernel that might recognise enable the CD, or is it going to be something needing modifying in acpi functionallity so acpi can still be used with the CD enabled?

I found an older report of this issue (bug #198319) that indicates that this problem is somehow related to grub (switching from lilo to grub caused the problem to appear, switching back made it go away) and that when grub was installed in a dual-boot scenario the drive stops working under Windows as well. This may explain why the old kernels aren't working now but were before.

Also noted there is that if you disable the drive in your bios settings, the drive starts working again. Can you verify this?

Interesting that worked in bug #198319 in cases where lilo was installed, although I installed fresh 11.04 and 11.10 from scratch so no lilo upgraded to switch to grub, just straight fresh install to grub.

I checked out bug #198319, interesting, but unsure why it would it possibly work in those cases where lilo is installed but not grub, what could grub be doing to disable the cdrom?

There isn't an option to disable optical drive on the Lenovo 3000 N200, only choice of SATA controller type AHCI or Compatible. I tried both but the cdrom still did not work. I also set BIOS defaults but cdrom still did not work.

The only way I can get the cdrom to load is by setting acpi=off in grub loader but this is not suitable as power functions are not active, battery management not enabled, fans not controlled etc., not good for effective cooling.

Hi Seth,

Just wondering if anything might have come to mind as to why the cdrom is not working with Ubuntu? I'm kind of lost without this being functional, especially writing capabilities.

Cheers,
Graham.

It's definitely odd that grub would be causing the cdrom to go undetected. I'm not very familiar with grub, so I have a hard time knowing what it might be doing to cause this.

Since this really looks the same as bug #198319, I'm going to mark this one as a duplicate and change that one to affecting grub, and perhaps someone who works on grub can take a look.