acpi, dma on cdrom, and other installation issues

Murdock1979 · 10-08-2007, 06:55 AM

Hello!

I am currently testing out a recent Slackware 12 installation on my dell inspiron 6000 and have ran into a few problems:

1. It seems the acpi is only partially configured, or something like that. Acpi services, such as hibernate, work fine on Kubuntu, and would like to see how I could accomplish this on Slackware.

2. The cdrom does not seem to have its dma activated. Using hdparm only gives some sort of error. I remember coming across this problems a while back, but can't recall how to fix it. Again, Kubuntu worked out of the box, so I am trying to figure out what configuration is different that gives this problem.

3. My wireless card was not being recognized, but that was solved by adding the firmware to the appropriate directory. Is there any sort of licensing problem that Slackware did not include the firmware in the installation?

Thanks,
Murdock

onebuck · 10-08-2007, 07:21 AM

Hi,

Which kernel? From the cli;

Code:

~#uname -r

When posting questions, please provide some basic information, Distro, kernel and basic hardware. I know you are using Slackware 12 and a 'dell inspiron 6000'.

Murdock1979 · 10-08-2007, 08:23 AM

Thanks for the quick reply!

I thought stating that I installed a clean Slackware 12 installation, with all the generic configuration, would be sufficient to describe my setup. However, here are few more pointers:

1. Kernel 2.6.21.5-smp (the generic one provided by Slackware)
2. Using a DVD+-RW ND-6650A

Any help would be great.

Murdock

GrapefruiTgirl · 10-08-2007, 09:33 AM

Quote:

Originally Posted by Murdock1979

2. The cdrom does not seem to have its dma activated. Using hdparm only gives some sort of error. I remember coming across this problems a while back, but can't recall how to fix it.

3. My wireless card was not being recognized, but that was solved by adding the firmware to the appropriate directory. Is there any sort of licensing problem that Slackware did not include the firmware in the installation?

2 - Can you expand upon this error produced, and what command you issued that resulted in it? Perhaps copy and paste it here for us..
What does hdparm -I /dev/cdrom return to you? If necessary, replace the term /dev/cdrom with the appropriate device instead, like /dev/hdc.

3 - Wireless device firmware is not usually included, and Slackware simply doesn't include it, for whatever reason, atleast in my experience. Plus, that would be a lot of different and unnecessary junk for Slackware to include, if they included every piece of firmware for every piece of hardware on the planet

Murdock1979 · 10-08-2007, 12:38 PM

Thanks, but the result is:

/dev/cdrom:
HDIO_GET_IDENTITY failed: Function not implemented

Later,
Murdock

onebuck · 10-08-2007, 02:39 PM

Quote:

Originally Posted by Murdock1979

Thanks, but the result is:

/dev/cdrom:
HDIO_GET_IDENTITY failed: Function not implemented

Later,
Murdock

Hi,

Do from cli as root;

Code:

~#dmesg |grep -i hd >myhd          #assume that the cdrom/dvd 
                                   #is ide
~#dmesg |grep -i dvd >mydvd        #please post both myhd, mydvd

~#ls -al /proc/ide                 #your cdrom/dvd should be
                                   #linked too ide1                                 
~#cat /proc/ide/ide1/hdc/settings  #show the cdrom settings

You should look at the udev rules for the optical devices in /etc/udev/rules.d.

Code:

~# ls /etc/udev/rules.d
50-udev.rules           75-network-devices.rules      80-libnjb.rules
60-bluetooth.rules      75-network-devices.rules-org  80-libpisock.rules
60-pcmcia.rules         75-optical-devices.rules      80-libsane.rules
64-device-mapper.rules  80-libmtp.rules               90-hal.rules

The '75-optical-devices.rules' is the file you want to look at;

Code:

~# cat /etc/udev/rules.d/75-optical-devices.rules


# Local optical devices rules to make links to your
# optical devices
#
# These rules were generated by cdrom-symlinks.sh, but you
# can customize them.
#
# You may edit them as needed.
# (If, for example, your machine has more than one CD or
# DVD drive and you need to be sure they will always be
# given the same symlinks.)
#
# If you delete this file, /lib/udev/cdrom-symlinks.sh will
# try to generate it again the next time udev is started.

ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-ide-1:0", SYMLINK+="cdrom0"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-ide-1:0", SYMLINK+="cdrom"

You can delete this file and a new one will be generated by the 'cdrom-symlinks.sh' when you next re-boot. Look at it again too see what is generated.

We need to get one problem at a time fixed. When posting something, please post what you input as a command and the resulting error if any as a whole.

Alien_Hominid · 10-08-2007, 04:21 PM

In 2.6 kernel DMA is auto-enabled. There was a driver change (search please, cause I don't remember everything) and not all function calls from hdparm were implemented in the new one. I could dig it in the Net if you need it. Maybe libata??? Anyone remembers?

EDIT: oh, yes, maybe this: In 2.4 all cdroms were scsi identified, now libata is used for ata/atapi cdroms. You can get more info at libata dev page.

Slackware does not include any third-party firmware. To get better ACPI SUpport, you can try to recompile the kernel.