[PlanetCCRMA] Simple test - alsaplayer

[Mark Knecht]

Fernando,
   It is the drive reordering problem in the Planet kernel.

/dev/hdd has apparently become /dev/hdh. This is the way I think it is
working on this machine:

C=chipset
A=Adapter
P=Primary controller
S=Secondary controller
Ma=IDE Master
Sl=IDE Slave

	Device	Redhat		Planet
C-P-Ma	drive	/dev/hda	/dev/hde
C-P-Sl		/dev/hdb	/dev/hdf
C-S-Ma		/dev/hdc	/dev/hdg
C-S-Sl	CDROM	/dev/hdd	/dev/hdh
A-P-Ma		/dev/hde	/dev/hda	
A-P-Sl		/dev/hdf	/dev/hdb
A-S-Ma		/dev/hdg	/dev/hdc
A-S-Sl		/dev/hdh	/dev/hdd

I find that the only address that responds at all to a mount command is
/dev/hdh, the remapped address for the CDROM:

[root@Godzilla root]# mount /dev/hdd /dev/cdrom
mount: /dev/hdd is not a valid block device
[root@Godzilla root]# mount /dev/hdh /dev/cdrom
/dev/hdh: Input/output error
mount: block device /dev/hdh is write-protected, mounting read-only
/dev/hdh: Input/output error
mount: you must specify the filesystem type
[root@Godzilla root]#
[root@Godzilla root]# mount /dev/hdh /dev/cdrom -t iso9660
mount: block device /dev/hdh is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdh,
       or too many mounted file systems

I need to read about this though. I guess I have to mkdev or something
to make a new CDROM that would be associated with /dev/hdh?????


Mark


On Tue, 2002-12-10 at 17:57, Mark Knecht wrote:
> Fernando,
>    If you build it, I will test it, but I'm a little concerned that this
> might actually be another version of this kernel drive-reordering
> problem I've been having.
> 
> /dev/cdrom -> /dev/hdd
> 
> I'm worried that possibly hdd under the RH kernel has a new name when I
> boot under the Planet kernel...
> 
> I'll look for your announcement and keep my fingers crossed...
> 
> Mark
> 
> 
> On Tue, 2002-12-10 at 17:51, Fernando Pablo Lopez-Lezcano wrote:
> > > > Back home and starting testing of my new hardware. Following a nice,
> > > > long, significant upgrade of KDE from the planet, I attempt to run
> > > > alsaplayer.The app comes up fine, but when I tell it to connect to the
> > > > CD Player, I get an error message:
> > > > 
> > > > 
> > > > 
> > > > [root@Godzilla root]# alsaplayer -R -o jack &
> > > > [2] 2773
> > > > [root@Godzilla root]# got connect request
> > > > got connect request
> > > > jack: realtime scheduling active
> > > > /usr/lib/libvorbisfile.so.3: undefined symbol: ogg_stream_reset_serialno
> > 
> > That's definitely alsaplayer's fault. I built a new version today...
> > 
> > > It looks like one of your newly compiled tools (alsaplayer, the 
> > > drivers, jack?) is calling a function that doesn't exist in your 
> > > libvorbis package.  Something (most likely libvorbis) is not as 
> > > current as your latest builds of the other stuff.  The device error 
> > > may be spurious (or maybe not).
> > > 
> > > You would have seen an error during the build (ie, it wouldn't have 
> > > compiled, at least not without lots of complaining) if you built 
> > > from source/src.rpm.  The rpm dependencies are supposed to catch 
> > > that stuff, but only if everything is correctly defined by the packager.
> > > 
> > > It sounds like I'm blaming it on Fernando ;-)
> > > 
> > > Okay Fernando, it's time to speak up (I'll shut up now).
> > 
> > Definitely my fault. I'll redo the build and REALLY (paying attention
> > this time) watch the boring messages to see if I spot something in the
> > section that deals with ogg vorbis. 
> > 
> > -- Fernando
> > 
> > 
> > _______________________________________________
> > PlanetCCRMA mailing list
> > PlanetCCRMA@ccrma.stanford.edu
> > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> 
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma