On Wed, 27 Mar 2002, Jean-Francois Cardoso wrote:
>
>
>
>
> On Mar 27, Stew Benedict wrote:
> > On Wed, 27 Mar 2002, Jean-Francois Cardoso wrote:
> > >
> > > I cannot play audio CDs on a tiBook
> > >
> > > The CD drive itself works ok: I can mount a data CD (like mdk iso's)
> > > and, launching tcd on an audio CD, I can see the audio tracks.
> > > However, I cannot play the CD tracks. The log says:
> > >
> > > : hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> > > : hdc: packet command error: error=0x54
> > > : ATAPI device hdc:
> > > : Error: Illegal request -- (Sense key=0x05)
> > > : Invalid command operation code -- (asc=0x20, ascq=0x00)
> > > : The failed "Play Audio MSF" packet command was:
> > > : "47 00 00 04 23 16 31 23 09 00 00 00 "
> > >
> > >
> > > Regarding ide/hdc, dmesg says:
> > >
> > > : pmac_ide: enabling IDE bus ID 2
> > > : pmac_ide: enabling IDE bus ID 0
> > > : pmac_ide: enabling IDE bus ID 1
> > > : hda: IBM-IC25N030ATDA04-0, ATA DISK drive
> > > : hdc: MATSHITADVD-ROM SR-8187, ATAPI CD/DVD-ROM drive
> > > : ide0 at 0xe5255000-0xe5255007,0xe5255160 on irq 19
> > > : ide1 at 0xe5259000-0xe5259007,0xe5259160 on irq 20
> > > : hda: Enabling Ultra DMA 4
> > > : ide_pmac: Set UDMA timing for mode 4, reg: 0x0c50038c
> > > : hda: 58605120 sectors (30006 MB) w/1806KiB Cache, CHS=58140/16/63, UDMA(66)
> > > : hdc: Enabling MultiWord DMA 2
> > > : ide_pmac: MDMA, cycleTime: 120, accessTime: 90, recTime: 30
> > > : ide_pmac: Set MDMA timing for mode 2, reg: 0x00011d26
> > > : hdc: ATAPI 24X DVD-ROM drive, 512kB Cache, (U)DMA
> > > : Uniform CD-ROM driver Revision: 3.12
> > >
> >
> > at least 2 possibilities:
> >
> > 1) Because Apple has opted to remove the audio interface between the CDROM
> > and the sound chip,
>
>
> Argh! Why, oh why, did they do that ?
>
save a nickel
>
> > you need to use xmms-cdread plugin to rip audio from the CD to play
> > music (ibook2 and beyond). It's in contribs.
>
> I just tried the latest version I could find : xmms-cdread-0.11d-1 but
> that does not work. Actually, the plug-in does not even see the
> tracks (yes, I disabled supermount).
>
you also need to disable the normal cdreader plugin
>
>
>
> Now, if we see error messages such as
>
> > > : ATAPI device hdc:
> > > : Error: Illegal request -- (Sense key=0x05)
> > > : Invalid command operation code -- (asc=0x20, ascq=0x00)
> > > : The failed "Play Audio MSF" packet command was:
>
> and also, in the same vein, such as
>
> : ATAPI device hdc:
> : Error: Illegal request -- (Sense key=0x05)
> : Invalid command operation code -- (asc=0x20, ascq=0x00)
> : The failed "Pause/Resume" packet command was:
> : "4b 00 00 00 00 00 00 00 00 00 00 00 "
>
> then does not that mean that we are facing a deeper problem ?
>
>
Possibly, but it doesn't seem to be global, that is I'm not able to
reproduce it.
>
> Now for something different:
>
> > > The system is an mdk-8.0 which has been upgraded to be in sync with
> > > cooker. In particular, rpm -qa | grep kern says:
> > >
> > > : kernel-source-2.4.18-4mdk
> > > : kernel-headers-2.4.17-24mdk
> > > : kernel-2.4.18.4mdk-1-1mdk
> > >
> >
> > Kernel headers do not need to be consistant with the kernel, but
> > they do need to be consistant with what was used to build
> > glibc. The kernel build is self contained, and does not use
> > kernel-headers. User space programs, for the most part, should be
> > using /usr/include/*. not /usr/src/linux/include/*.
>
>
> Thanks for the tip. That calls for two questions:
>
> 1) Out of curiosity: how does one find which kernel header version
> glibc is compiled against? (could not find it after a quick rpm
> -qxxx )
>
> 2) I used to blame failure to compile the kernel on the above (non
> existent) inconsistency. Shouldn't the kernel compile without
> error if I am in sync with cooker *and* use the .config found by
> default the kernel-source rpm ?
>
Actually, the rest of cooker doesn't have a lot to do with the kernel
compile, unless you happen to hit a couple of the times when various
components of binutils were broken. Of course you need the basics, gcc
etc. I think the thing that catches most folks is neglecting to "make
mrproper", before initiating the make menuconfig, etc. This is peculiar to
a Mandrake kernel and most likely different than what you're accustomed to
with plain kernel.org or BenH sources. There have been several discussions
on why this is so on the main cooker list, and I don't anticipate it's
going to change:
cd /usr/src/linux
make mrproper
make menuconfig (or config, or xconfig)
make dep && make vmlinux
make modules
make modules_install
installkernel KERNEL_VERSION vmlinux System.map
(you fill in KERNEL_VERSION, in my walkthrough it would be "2.4.18-6mdk")
reboot and enjoy - yaboot entry is done by installkernel
Of course if you're building the same Mandrake kernel version that you're
running, you may want to be careful with the install portions above.
I just walked through these steps with kernel-source-2.4.18-6mdk - no
errors.
Stew Benedict
--
MandrakeSoft
PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
