Re: Problem with several Creative Labs soundcards, possibly more?

Re: Problem with several Creative Labs soundcards, possibly more?

[Lee Revell]

On Fri, 2005-10-21 at 17:19 -0500, Nazo wrote:
> When I got it to sucessfully boot, and tried to play something, it
> played one frame over and over in a loop (kind of like what happens
> when the system locks up in the middle of a game or something.)  When
> the application was closed and another different sound file was
> attempted, it gave an IO error and no sound came out at all.  Based on
> the way it kind of acted like the hardware locked up or something, my
> first guess would be maybe something along the lines of an IRQ
> conflict or somesuch?  That's just a guess though.  Anyway, he thought
> it might be useful if I provided some extra info, so I've added them
> to the bottom of the message:
> 

OK, this is a classic sign that interrupts are not being acknowledged
properly.  It's not a problem with the ALSA drivers but with the kernel.
Probably an ACPI issue.

What is the make and model of your motherboard?

Does it work if you boot with "pci=noacpi"?

Lee




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Problem with several Creative Labs soundcards, possibly more?

[Nazo]

If I boot with pci=noacpi, the normal mandriva kernel hangs just after
it says hit I for interactive setup.  The vanilla one starts up, but,
when I try to play an audio file, I have the same problem.  Bear in
mind when saying the problem lies with the kernel that I've seen this
issue on several different kernel versions.

As for my motherboard, it's a Gigabyte 9NDA3J.  The chipset is the
nForce 3 Ultra (which I believe is basically just a nForce 3 250 with
the only change being the socket type, but, I'm not 100% sure.)  I
think I saw some things using the 250 driver for the motherboard
rather than saying ultra, but, like I said, I think this is probably
ok.

On 10/21/05, Lee Revell <rlrevell@joe-job.com> wrote:
> On Fri, 2005-10-21 at 17:19 -0500, Nazo wrote:
> > When I got it to sucessfully boot, and tried to play something, it
> > played one frame over and over in a loop (kind of like what happens
> > when the system locks up in the middle of a game or something.)  When
> > the application was closed and another different sound file was
> > attempted, it gave an IO error and no sound came out at all.  Based on
> > the way it kind of acted like the hardware locked up or something, my
> > first guess would be maybe something along the lines of an IRQ
> > conflict or somesuch?  That's just a guess though.  Anyway, he thought
> > it might be useful if I provided some extra info, so I've added them
> > to the bottom of the message:
> >
>
> OK, this is a classic sign that interrupts are not being acknowledged
> properly.  It's not a problem with the ALSA drivers but with the kernel.
> Probably an ACPI issue.
>
> What is the make and model of your motherboard?
>
> Does it work if you boot with "pci=noacpi"?
>
> Lee
>
>
>


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Problem with several Creative Labs soundcards, possibly more?

[Lee Revell]

Please don't top post.

On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
> If I boot with pci=noacpi, the normal mandriva kernel hangs just after
> it says hit I for interactive setup.  The vanilla one starts up, but,
> when I try to play an audio file, I have the same problem.  Bear in
> mind when saying the problem lies with the kernel that I've seen this
> issue on several different kernel versions.
> 
> As for my motherboard, it's a Gigabyte 9NDA3J.  The chipset is the
> nForce 3 Ultra (which I believe is basically just a nForce 3 250 with
> the only change being the socket type, but, I'm not 100% sure.)  I
> think I saw some things using the 250 driver for the motherboard
> rather than saying ultra, but, like I said, I think this is probably
> ok.
> 

OK, it still sounds like a kernel problem.  The IRQ handling code in the
emu10k1 driver is quite simple and almost certainly free of bugs.  OTOH,
I see TONS of reports like this on LKML, and it's always an ACPI issue.

Unless someone on alsa-devel has a better idea, I think you need to
report this on the kernel bugzilla.

Can you check /proc/interrupts and see if the number of interrupts for
your soundcard increases when you play sounds?  Also please post the
output of "dmesg" after rebooting the machine and trying to play a
sound.

Lee

> On 10/21/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > On Fri, 2005-10-21 at 17:19 -0500, Nazo wrote:
> > > When I got it to sucessfully boot, and tried to play something, it
> > > played one frame over and over in a loop (kind of like what happens
> > > when the system locks up in the middle of a game or something.)  When
> > > the application was closed and another different sound file was
> > > attempted, it gave an IO error and no sound came out at all.  Based on
> > > the way it kind of acted like the hardware locked up or something, my
> > > first guess would be maybe something along the lines of an IRQ
> > > conflict or somesuch?  That's just a guess though.  Anyway, he thought
> > > it might be useful if I provided some extra info, so I've added them
> > > to the bottom of the message:
> > >
> >
> > OK, this is a classic sign that interrupts are not being acknowledged
> > properly.  It's not a problem with the ALSA drivers but with the kernel.
> > Probably an ACPI issue.
> >
> > What is the make and model of your motherboard?
> >
> > Does it work if you boot with "pci=noacpi"?
> >
> > Lee
> >
> >
> >
> 



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Problem with several Creative Labs soundcards, possibly more?

[Lee Revell]

Also, please don't top post, and please don't remove alsa-user and
alsa-devel from the cc: list.

I still think it's a kernel problem because you have bleeding edge
hardware (Athlon64) with relatively unknown specs (Nforce chipset).

On Sat, 2005-10-22 at 02:24 -0500, Nazo wrote:
> Firstly, the reason I really wonder if it's a kernel bug is the fact
> that it's shown up in so many different kernels.  That said, if you
> honestly think I should report it, can you tell me how to do so?  I've
> never even thought about reporting a kernel bug before, so have no
> idea where even to go.
> 
> Anyway, bad news.  I was trying to compile another kernel and messed
> up one thing so that when I booted it I was forced to do a hard reset.
>  Linux prevents lockups and other such problems like a dream, but, the
> moment a problem occurs it handles it so terribly it's not even funny.
>  Simply put, it no longer boots the normal kernel either due to severe
> filesystem damage and the repairs are beyond the scope of what I know
> to do, so I'd have to simply reinstall again (I swear my luck with
> linux is horrible.)  This takes a while and I'd rather not do it
> tonight.  If you really need me to I will, but, I wondered if maybe
> the results from GeeXBoX would do?  It doesn't do the hardware loop
> thing, but, this is the first place I get no sound (and, if it's a
> seperate issue then this just goes right back to the fact that that's
> the issue I REALLY want to fix.)  So, here are the outputs from
> GeeXBoX:
> 
> Ok, first of all, the interrupts.  It probably doesn't do any good,
> but, I thought I'd paste them.  The only difference I saw between the
> before and after was the second number (which I presume is something
> more along the lines of how much information it has been used for?)
>            CPU0
>   0:     214447    IO-APIC-edge  timer
>   1:       1021    IO-APIC-edge  i8042
>   8:       8552    IO-APIC-edge  rtc
>   9:          1   IO-APIC-level  acpi
>  14:      30997    IO-APIC-edge  ide0
>  15:        696    IO-APIC-edge  ide1
>  16:      20396   IO-APIC-level  eth0
>  17:          3   IO-APIC-level  ohci1394
>  18:          3   IO-APIC-level  ehci_hcd:usb1
>  19:          0   IO-APIC-level  ohci_hcd:usb2
>  20:         50   IO-APIC-level  ohci_hcd:usb3
>  21:        326   IO-APIC-level  EMU10K1
> NMI:          0
> LOC:     214348
> ERR:          0
> MIS:          0
> 
> And dmesg (apparently part got cut off, sorry, but, it got cut off
> before getting to the sound relate stuff):
> e driver v2.3
> Initializing USB Mass Storage driver...
> usbcore: registered new driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.01:USB HID core driver
> usb 3-1: new low speed USB device using ohci_hcd and address 2
> input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on
> usb-0000:00:02.1-1
> usb 3-2: new full speed USB device using ohci_hcd and address 3
> usbcore: registered new driver xpad
> drivers/usb/input/xpad.c: X-Box pad driver:v0.0.5
> pegasus: v0.6.12 (2005/01/13), Pegasus/Pegasus II USB Ethernet driver
> usbcore: registered new driver pegasus
> drivers/usb/net/rtl8150.c: rtl8150 based usb-ethernet driver v0.6.2 (2004/08/27)
> usbcore: registered new driver rtl8150
> gameport: EMU10K1 is pci0000:02:09.1/gameport0, io 0xc400, speed 1217kHz
> Advanced Linux Sound Architecture Driver Version 1.0.9b (Thu Jul 28
> 12:20:13 2005 UTC).
> ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
> ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [APC2] -> GSI 17 (level,
> low) -> IRQ 21
> Installing spdif_bug patch: Audigy 2 ZS [SB0350]
> ALSA device list:
>   #0: Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 0xc000, irq 21
> NET: Registered protocol family 2
> IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
> TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
> TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.50.3)
> powernow-k8:    0 : fid 0xe (2200 MHz), vid 0x6 (1400 mV)
> powernow-k8:    1 : fid 0xc (2000 MHz), vid 0x8 (1350 mV)
> powernow-k8:    2 : fid 0xa (1800 MHz), vid 0xa (1300 mV)
> powernow-k8:    3 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
> cpu_init done, current fid 0xc, vid 0x6
> Using IPI Shortcut mode
> ACPI wakeup devices:
> HUB0 HUB1 USB0 USB1 USB2 F139 MMAC MMCI
> ACPI: (supports S0 S1 S3 S4 S5)
> RAMDISK: Compressed image found at block 0
> input: AT Translated Set 2 keyboard on isa0060/serio0
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 300k freed
> ReiserFS: hda1: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hda1
> VFS: Can't find ext3 filesystem on dev hda1.
> VFS: Can't find an ext2 filesystem on dev hda1.
> ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00023c01510815d7]
> ReiserFS: hda2: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hda2
> VFS: Can't find ext3 filesystem on dev hda2.
> VFS: Can't find an ext2 filesystem on dev hda2.
> attempt to access beyond end of device
> hda3: rw=0, want=18, limit=2
> ReiserFS: hda3: warning: sh-2006: read_super_block: bread failed (dev
> hda3, block 8, size 1024)
> attempt to access beyond end of device
> hda3: rw=0, want=130, limit=2
> ReiserFS: hda3: warning: sh-2006: read_super_block: bread failed (dev
> hda3, block 64, size 1024)
> ReiserFS: hda3: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hda3
> attempt to access beyond end of device
> hda3: rw=0, want=4, limit=2
> EXT3-fs: unable to read superblock
> attempt to access beyond end of device
> hda3: rw=0, want=4, limit=2
> EXT2-fs: unable to read superblock
> FAT: bogus number of reserved sectors
> VFS: Can't find a valid FAT filesystem on dev hda3.
> attempt to access beyond end of device
> hda3: rw=0, want=66, limit=2
> isofs_fill_super: bread failed, dev=hda3, iso_blknum=16, block=32
> attempt to access beyond end of device
> hda3: rw=0, want=3, limit=2
> HFS+-fs: unable to find HFS+ superblock
> attempt to access beyond end of device
> hda3: rw=0, want=3, limit=2
> VFS: Can't find a HFS filesystem on dev hda3.
> NTFS-fs error (device hda3): read_ntfs_boot_sector(): Primary boot
> sector is invalid.
> NTFS-fs error (device hda3): read_ntfs_boot_sector(): Mount option
> errors=recover not used. Aborting without trying to recover.
> NTFS-fs error (device hda3): ntfs_fill_super(): Not an NTFS volume.
> You didn't specify the type of your ufs filesystem
> 
> mount -t ufs -o
> ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|netxstep-cd|openstep
> ...
> 
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
> attempt to access beyond end of device
> hda3: rw=0, want=18, limit=2
> attempt to access beyond end of device
> hda3: rw=0, want=68, limit=2
> attempt to access beyond end of device
> hda3: rw=0, want=1252, limit=2
> attempt to access beyond end of device
> hda3: rw=0, want=1028, limit=2
> UDF-fs: No partition found (1)
> ReiserFS: hda5: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hda5
> VFS: Can't find ext3 filesystem on dev hda5.
> VFS: Can't find an ext2 filesystem on dev hda5.
> FAT: bogus number of reserved sectors
> VFS: Can't find a valid FAT filesystem on dev hda5.
> Unable to identify CD-ROM format.
> HFS+-fs: unable to find HFS+ superblock
> VFS: Can't find a HFS filesystem on dev hda5.
> NTFS volume version 3.1.
> ReiserFS: hda6: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hda6
> ext3: No journal on filesystem on hda6
> ReiserFS: hda7: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hda7
> VFS: Can't find ext3 filesystem on dev hda7.
> VFS: Can't find an ext2 filesystem on dev hda7.
> FAT: invalid media value (0x7c)
> VFS: Can't find a valid FAT filesystem on dev hda7.
> Unable to identify CD-ROM format.
> HFS+-fs: unable to find HFS+ superblock
> VFS: Can't find a HFS filesystem on dev hda7.
> NTFS-fs warning (device hda7): is_boot_sector_ntfs(): Invalid boot
> sector checksum.
> NTFS-fs error (device hda7): read_ntfs_boot_sector(): Primary boot
> sector is invalid.
> NTFS-fs error (device hda7): read_ntfs_boot_sector(): Mount option
> errors=recover not used. Aborting without trying to recover.
> NTFS-fs error (device hda7): ntfs_fill_super(): Not an NTFS volume.
> You didn't specify the type of your ufs filesystem
> 
> mount -t ufs -o
> ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|netxstep-cd|openstep
> ...
> 
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
> ufs_read_super: bad magic number
> UDF-fs: No VRS found
> ReiserFS: hdc: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hdc
> VFS: Can't find ext3 filesystem on dev hdc.
> VFS: Can't find an ext2 filesystem on dev hdc.
> FAT: bogus number of reserved sectors
> VFS: Can't find a valid FAT filesystem on dev hdc.
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISO 9660 Extensions: RRIP_1991A
> usbcore: registered new driver rtusb
> InterWave soundcard not found or device busy
> Sound Blaster 16 soundcard not found or device busy
> In case, if you have AWE card, try snd-sbawe module
> Sound Blaster 16 soundcard not found or device busy
> In case, if you have AWE card, try snd-sbawe module
> lirc_dev: IR Remote Control driver registered, at major 61
> 
> lirc_atiusb: USB remote driver for LIRC v0.4
> lirc_atiusb: Paul Miller <pmiller9@users.sourceforge.net>
> usbcore: registered new driver lirc_atiusb
>  CIFS VFS: No response buffer
>  CIFS VFS: cifs_mount failed w/return code = -112
> ReiserFS: hda2: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on hda2
> VFS: Can't find ext3 filesystem on dev hda2.
> VFS: Can't find an ext2 filesystem on dev hda2.
> atkbd.c: Unknown key pressed (translated set 2, code 0xbc on isa0060/serio0).
> atkbd.c: Use 'setkeycodes e03c <keycode>' to make it known.
> atkbd.c: Unknown key released (translated set 2, code 0xbc on isa0060/serio0).
> atkbd.c: Use 'setkeycodes e03c <keycode>' to make it known.
> atkbd.c: Unknown key pressed (translated set 2, code 0xbb on isa0060/serio0).
> atkbd.c: Use 'setkeycodes e03b <keycode>' to make it known.
> atkbd.c: Unknown key released (translated set 2, code 0xbb on isa0060/serio0).
> atkbd.c: Use 'setkeycodes e03b <keycode>' to make it known.
> 
> 
> 
> On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > Please don't top post.
> >
> > On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
> > > If I boot with pci=noacpi, the normal mandriva kernel hangs just after
> > > it says hit I for interactive setup.  The vanilla one starts up, but,
> > > when I try to play an audio file, I have the same problem.  Bear in
> > > mind when saying the problem lies with the kernel that I've seen this
> > > issue on several different kernel versions.
> > >
> > > As for my motherboard, it's a Gigabyte 9NDA3J.  The chipset is the
> > > nForce 3 Ultra (which I believe is basically just a nForce 3 250 with
> > > the only change being the socket type, but, I'm not 100% sure.)  I
> > > think I saw some things using the 250 driver for the motherboard
> > > rather than saying ultra, but, like I said, I think this is probably
> > > ok.
> > >
> >
> > OK, it still sounds like a kernel problem.  The IRQ handling code in the
> > emu10k1 driver is quite simple and almost certainly free of bugs.  OTOH,
> > I see TONS of reports like this on LKML, and it's always an ACPI issue.
> >
> > Unless someone on alsa-devel has a better idea, I think you need to
> > report this on the kernel bugzilla.
> >
> > Can you check /proc/interrupts and see if the number of interrupts for
> > your soundcard increases when you play sounds?  Also please post the
> > output of "dmesg" after rebooting the machine and trying to play a
> > sound.
> >
> > Lee
> >
> > > On 10/21/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > > > On Fri, 2005-10-21 at 17:19 -0500, Nazo wrote:
> > > > > When I got it to sucessfully boot, and tried to play something, it
> > > > > played one frame over and over in a loop (kind of like what happens
> > > > > when the system locks up in the middle of a game or something.)  When
> > > > > the application was closed and another different sound file was
> > > > > attempted, it gave an IO error and no sound came out at all.  Based on
> > > > > the way it kind of acted like the hardware locked up or something, my
> > > > > first guess would be maybe something along the lines of an IRQ
> > > > > conflict or somesuch?  That's just a guess though.  Anyway, he thought
> > > > > it might be useful if I provided some extra info, so I've added them
> > > > > to the bottom of the message:
> > > > >
> > > >
> > > > OK, this is a classic sign that interrupts are not being acknowledged
> > > > properly.  It's not a problem with the ALSA drivers but with the kernel.
> > > > Probably an ACPI issue.
> > > >
> > > > What is the make and model of your motherboard?
> > > >
> > > > Does it work if you boot with "pci=noacpi"?
> > > >
> > > > Lee
> > > >
> > > >
> > > >
> > >
> >
> >
> 



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Nazo]

I'm not sure what "top post" means.  The cc thing was just
carelessness as I clicked the wrong reply button and didn't realize
it.  Anyway, the two log files you wanted me to check don't exist in
this I'm afraid.  I think I'll try reinstalling Mandriva later.  And I
did "install" the new kernel correctly, I just made a mistake and
removed something apparently vital for keyboard support.  Without a
keyboard, I couldnt' log in or reboot, so was forced to do a hardboot.
 And yes linux CAN handle lockups/forced reboots better.  If windows
can do it, linux can do it better.  Problem is, linux doesn't have the
practice at it.  You know every time I do a hardboot in linux, major
damage occurs, but, I've had the same copy of XP installed since I got
this system.  I'm not sure that nForce 3 counts as "bleeding edge"
though one could maybe argue that san diego is pretty new-ish.  Still,
it doesn't have many features versus older A64s.  Mainly just SSE3
(which isn't saying much.)

On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
> On Sat, 2005-10-22 at 02:24 -0500, Nazo wrote:
> > I was trying to compile another kernel and messed
> > up one thing so that when I booted it I was forced to do a hard reset.
> >  Linux prevents lockups and other such problems like a dream, but, the
> > moment a problem occurs it handles it so terribly it's not even
> > funny.
>
> You probably didn't install the kernel properly.  It's impossible to
> handle this any better.  This is not supposed to be done by end users
> anyway.
>
> The dmesg is incomplete - I need the full log.  Try
> checking /var/log/kernel or /var/log/kern.log and post all the messages
> since boot.
>
> Lee
>
>

On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
> Also, please don't top post, and please don't remove alsa-user and
> alsa-devel from the cc: list.
>
> I still think it's a kernel problem because you have bleeding edge
> hardware (Athlon64) with relatively unknown specs (Nforce chipset).
>
> On Sat, 2005-10-22 at 02:24 -0500, Nazo wrote:
> > Firstly, the reason I really wonder if it's a kernel bug is the fact
> > that it's shown up in so many different kernels.  That said, if you
> > honestly think I should report it, can you tell me how to do so?  I've
> > never even thought about reporting a kernel bug before, so have no
> > idea where even to go.
> >
> > Anyway, bad news.  I was trying to compile another kernel and messed
> > up one thing so that when I booted it I was forced to do a hard reset.
> >  Linux prevents lockups and other such problems like a dream, but, the
> > moment a problem occurs it handles it so terribly it's not even funny.
> >  Simply put, it no longer boots the normal kernel either due to severe
> > filesystem damage and the repairs are beyond the scope of what I know
> > to do, so I'd have to simply reinstall again (I swear my luck with
> > linux is horrible.)  This takes a while and I'd rather not do it
> > tonight.  If you really need me to I will, but, I wondered if maybe
> > the results from GeeXBoX would do?  It doesn't do the hardware loop
> > thing, but, this is the first place I get no sound (and, if it's a
> > seperate issue then this just goes right back to the fact that that's
> > the issue I REALLY want to fix.)  So, here are the outputs from
> > GeeXBoX:
> >
> > Ok, first of all, the interrupts.  It probably doesn't do any good,
> > but, I thought I'd paste them.  The only difference I saw between the
> > before and after was the second number (which I presume is something
> > more along the lines of how much information it has been used for?)
> >            CPU0
> >   0:     214447    IO-APIC-edge  timer
> >   1:       1021    IO-APIC-edge  i8042
> >   8:       8552    IO-APIC-edge  rtc
> >   9:          1   IO-APIC-level  acpi
> >  14:      30997    IO-APIC-edge  ide0
> >  15:        696    IO-APIC-edge  ide1
> >  16:      20396   IO-APIC-level  eth0
> >  17:          3   IO-APIC-level  ohci1394
> >  18:          3   IO-APIC-level  ehci_hcd:usb1
> >  19:          0   IO-APIC-level  ohci_hcd:usb2
> >  20:         50   IO-APIC-level  ohci_hcd:usb3
> >  21:        326   IO-APIC-level  EMU10K1
> > NMI:          0
> > LOC:     214348
> > ERR:          0
> > MIS:          0
> >
> > And dmesg (apparently part got cut off, sorry, but, it got cut off
> > before getting to the sound relate stuff):
> > e driver v2.3
> > Initializing USB Mass Storage driver...
> > usbcore: registered new driver usb-storage
> > USB Mass Storage support registered.
> > usbcore: registered new driver usbhid
> > drivers/usb/input/hid-core.c: v2.01:USB HID core driver
> > usb 3-1: new low speed USB device using ohci_hcd and address 2
> > input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on
> > usb-0000:00:02.1-1
> > usb 3-2: new full speed USB device using ohci_hcd and address 3
> > usbcore: registered new driver xpad
> > drivers/usb/input/xpad.c: X-Box pad driver:v0.0.5
> > pegasus: v0.6.12 (2005/01/13), Pegasus/Pegasus II USB Ethernet driver
> > usbcore: registered new driver pegasus
> > drivers/usb/net/rtl8150.c: rtl8150 based usb-ethernet driver v0.6.2 (2004/08/27)
> > usbcore: registered new driver rtl8150
> > gameport: EMU10K1 is pci0000:02:09.1/gameport0, io 0xc400, speed 1217kHz
> > Advanced Linux Sound Architecture Driver Version 1.0.9b (Thu Jul 28
> > 12:20:13 2005 UTC).
> > ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
> > ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [APC2] -> GSI 17 (level,
> > low) -> IRQ 21
> > Installing spdif_bug patch: Audigy 2 ZS [SB0350]
> > ALSA device list:
> >   #0: Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 0xc000, irq 21
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
> > TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
> > TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
> > TCP: Hash tables configured (established 131072 bind 65536)
> > TCP reno registered
> > TCP bic registered
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.50.3)
> > powernow-k8:    0 : fid 0xe (2200 MHz), vid 0x6 (1400 mV)
> > powernow-k8:    1 : fid 0xc (2000 MHz), vid 0x8 (1350 mV)
> > powernow-k8:    2 : fid 0xa (1800 MHz), vid 0xa (1300 mV)
> > powernow-k8:    3 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
> > cpu_init done, current fid 0xc, vid 0x6
> > Using IPI Shortcut mode
> > ACPI wakeup devices:
> > HUB0 HUB1 USB0 USB1 USB2 F139 MMAC MMCI
> > ACPI: (supports S0 S1 S3 S4 S5)
> > RAMDISK: Compressed image found at block 0
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > VFS: Mounted root (ext2 filesystem).
> > Freeing unused kernel memory: 300k freed
> > ReiserFS: hda1: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hda1
> > VFS: Can't find ext3 filesystem on dev hda1.
> > VFS: Can't find an ext2 filesystem on dev hda1.
> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00023c01510815d7]
> > ReiserFS: hda2: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hda2
> > VFS: Can't find ext3 filesystem on dev hda2.
> > VFS: Can't find an ext2 filesystem on dev hda2.
> > attempt to access beyond end of device
> > hda3: rw=0, want=18, limit=2
> > ReiserFS: hda3: warning: sh-2006: read_super_block: bread failed (dev
> > hda3, block 8, size 1024)
> > attempt to access beyond end of device
> > hda3: rw=0, want=130, limit=2
> > ReiserFS: hda3: warning: sh-2006: read_super_block: bread failed (dev
> > hda3, block 64, size 1024)
> > ReiserFS: hda3: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hda3
> > attempt to access beyond end of device
> > hda3: rw=0, want=4, limit=2
> > EXT3-fs: unable to read superblock
> > attempt to access beyond end of device
> > hda3: rw=0, want=4, limit=2
> > EXT2-fs: unable to read superblock
> > FAT: bogus number of reserved sectors
> > VFS: Can't find a valid FAT filesystem on dev hda3.
> > attempt to access beyond end of device
> > hda3: rw=0, want=66, limit=2
> > isofs_fill_super: bread failed, dev=hda3, iso_blknum=16, block=32
> > attempt to access beyond end of device
> > hda3: rw=0, want=3, limit=2
> > HFS+-fs: unable to find HFS+ superblock
> > attempt to access beyond end of device
> > hda3: rw=0, want=3, limit=2
> > VFS: Can't find a HFS filesystem on dev hda3.
> > NTFS-fs error (device hda3): read_ntfs_boot_sector(): Primary boot
> > sector is invalid.
> > NTFS-fs error (device hda3): read_ntfs_boot_sector(): Mount option
> > errors=recover not used. Aborting without trying to recover.
> > NTFS-fs error (device hda3): ntfs_fill_super(): Not an NTFS volume.
> > You didn't specify the type of your ufs filesystem
> >
> > mount -t ufs -o
> > ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|netxstep-cd|openstep
> > ...
> >
> > >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
> > attempt to access beyond end of device
> > hda3: rw=0, want=18, limit=2
> > attempt to access beyond end of device
> > hda3: rw=0, want=68, limit=2
> > attempt to access beyond end of device
> > hda3: rw=0, want=1252, limit=2
> > attempt to access beyond end of device
> > hda3: rw=0, want=1028, limit=2
> > UDF-fs: No partition found (1)
> > ReiserFS: hda5: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hda5
> > VFS: Can't find ext3 filesystem on dev hda5.
> > VFS: Can't find an ext2 filesystem on dev hda5.
> > FAT: bogus number of reserved sectors
> > VFS: Can't find a valid FAT filesystem on dev hda5.
> > Unable to identify CD-ROM format.
> > HFS+-fs: unable to find HFS+ superblock
> > VFS: Can't find a HFS filesystem on dev hda5.
> > NTFS volume version 3.1.
> > ReiserFS: hda6: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hda6
> > ext3: No journal on filesystem on hda6
> > ReiserFS: hda7: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hda7
> > VFS: Can't find ext3 filesystem on dev hda7.
> > VFS: Can't find an ext2 filesystem on dev hda7.
> > FAT: invalid media value (0x7c)
> > VFS: Can't find a valid FAT filesystem on dev hda7.
> > Unable to identify CD-ROM format.
> > HFS+-fs: unable to find HFS+ superblock
> > VFS: Can't find a HFS filesystem on dev hda7.
> > NTFS-fs warning (device hda7): is_boot_sector_ntfs(): Invalid boot
> > sector checksum.
> > NTFS-fs error (device hda7): read_ntfs_boot_sector(): Primary boot
> > sector is invalid.
> > NTFS-fs error (device hda7): read_ntfs_boot_sector(): Mount option
> > errors=recover not used. Aborting without trying to recover.
> > NTFS-fs error (device hda7): ntfs_fill_super(): Not an NTFS volume.
> > You didn't specify the type of your ufs filesystem
> >
> > mount -t ufs -o
> > ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|netxstep-cd|openstep
> > ...
> >
> > >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
> > ufs_read_super: bad magic number
> > UDF-fs: No VRS found
> > ReiserFS: hdc: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hdc
> > VFS: Can't find ext3 filesystem on dev hdc.
> > VFS: Can't find an ext2 filesystem on dev hdc.
> > FAT: bogus number of reserved sectors
> > VFS: Can't find a valid FAT filesystem on dev hdc.
> > ISO 9660 Extensions: Microsoft Joliet Level 3
> > ISO 9660 Extensions: RRIP_1991A
> > usbcore: registered new driver rtusb
> > InterWave soundcard not found or device busy
> > Sound Blaster 16 soundcard not found or device busy
> > In case, if you have AWE card, try snd-sbawe module
> > Sound Blaster 16 soundcard not found or device busy
> > In case, if you have AWE card, try snd-sbawe module
> > lirc_dev: IR Remote Control driver registered, at major 61
> >
> > lirc_atiusb: USB remote driver for LIRC v0.4
> > lirc_atiusb: Paul Miller <pmiller9@users.sourceforge.net>
> > usbcore: registered new driver lirc_atiusb
> >  CIFS VFS: No response buffer
> >  CIFS VFS: cifs_mount failed w/return code = -112
> > ReiserFS: hda2: warning: sh-2021: reiserfs_fill_super: can not find
> > reiserfs on hda2
> > VFS: Can't find ext3 filesystem on dev hda2.
> > VFS: Can't find an ext2 filesystem on dev hda2.
> > atkbd.c: Unknown key pressed (translated set 2, code 0xbc on isa0060/serio0).
> > atkbd.c: Use 'setkeycodes e03c <keycode>' to make it known.
> > atkbd.c: Unknown key released (translated set 2, code 0xbc on isa0060/serio0).
> > atkbd.c: Use 'setkeycodes e03c <keycode>' to make it known.
> > atkbd.c: Unknown key pressed (translated set 2, code 0xbb on isa0060/serio0).
> > atkbd.c: Use 'setkeycodes e03b <keycode>' to make it known.
> > atkbd.c: Unknown key released (translated set 2, code 0xbb on isa0060/serio0).
> > atkbd.c: Use 'setkeycodes e03b <keycode>' to make it known.
> >
> >
> >
> > On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > > Please don't top post.
> > >
> > > On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
> > > > If I boot with pci=noacpi, the normal mandriva kernel hangs just after
> > > > it says hit I for interactive setup.  The vanilla one starts up, but,
> > > > when I try to play an audio file, I have the same problem.  Bear in
> > > > mind when saying the problem lies with the kernel that I've seen this
> > > > issue on several different kernel versions.
> > > >
> > > > As for my motherboard, it's a Gigabyte 9NDA3J.  The chipset is the
> > > > nForce 3 Ultra (which I believe is basically just a nForce 3 250 with
> > > > the only change being the socket type, but, I'm not 100% sure.)  I
> > > > think I saw some things using the 250 driver for the motherboard
> > > > rather than saying ultra, but, like I said, I think this is probably
> > > > ok.
> > > >
> > >
> > > OK, it still sounds like a kernel problem.  The IRQ handling code in the
> > > emu10k1 driver is quite simple and almost certainly free of bugs.  OTOH,
> > > I see TONS of reports like this on LKML, and it's always an ACPI issue.
> > >
> > > Unless someone on alsa-devel has a better idea, I think you need to
> > > report this on the kernel bugzilla.
> > >
> > > Can you check /proc/interrupts and see if the number of interrupts for
> > > your soundcard increases when you play sounds?  Also please post the
> > > output of "dmesg" after rebooting the machine and trying to play a
> > > sound.
> > >
> > > Lee
> > >
> > > > On 10/21/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > > > > On Fri, 2005-10-21 at 17:19 -0500, Nazo wrote:
> > > > > > When I got it to sucessfully boot, and tried to play something, it
> > > > > > played one frame over and over in a loop (kind of like what happens
> > > > > > when the system locks up in the middle of a game or something.)  When
> > > > > > the application was closed and another different sound file was
> > > > > > attempted, it gave an IO error and no sound came out at all.  Based on
> > > > > > the way it kind of acted like the hardware locked up or something, my
> > > > > > first guess would be maybe something along the lines of an IRQ
> > > > > > conflict or somesuch?  That's just a guess though.  Anyway, he thought
> > > > > > it might be useful if I provided some extra info, so I've added them
> > > > > > to the bottom of the message:
> > > > > >
> > > > >
> > > > > OK, this is a classic sign that interrupts are not being acknowledged
> > > > > properly.  It's not a problem with the ALSA drivers but with the kernel.
> > > > > Probably an ACPI issue.
> > > > >
> > > > > What is the make and model of your motherboard?
> > > > >
> > > > > Does it work if you boot with "pci=noacpi"?
> > > > >
> > > > > Lee
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Lee Revell]

On Sat, 2005-10-22 at 12:24 -0500, Nazo wrote:
> I'm not sure what "top post" means.

When you type the reply above my last message, instead of below it.

Lee




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Lee Revell]

On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
> If I boot with pci=noacpi, the normal mandriva kernel hangs just after
> it says hit I for interactive setup.

OK, try "pci=routeirq".

Lee



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Nazo]

Well, I'm sorry, I'm going to stick with replying on top because, to
me this seems like the least inconvenience for the largest number of
people.

That said, Revell, I tried pci=routeirq on GeeXBoX and it made no
obvious changes.  It occurs to me that maybe the two systems actually
have seperate problems that just happen to have nearly the same
effect.  Unfortunately, my attempts to install Mandriva all fail
horribly.  It gets stuck every single time.  I've had a similar issue
with Fedora Core 4.  Kubuntu gets stuck after starting X.  In each of
these cases, the system is not frozen (I can move the mouse) but
nothing ever comes up and I'm unable to do anything.  At this point,
all I have left for diagnosing this problem is GeeXBoX.  (And yes, my
system is 100% stable.  Prime95 stable.)  Other than the filesystem
being damaged (and I've tried completely reformatting it, and, even
changed the partition table so that it's no longer even in the same
place, then reformatted again) I really can't think of a single thing
that changed between the first installation and this most recent
attempt.  I don't know if I can continue to diagnose this issue with
just GeeXBoX, but, right now it's all that's left.

One thing that is important to note about the issue in GeeXBoX is the
fact that when I try to change the volume control, it doesn't work. 
It defaults to zero, and when I try to raise it, nothing happens.  It
stays at zero.  I forgot this because most of the versions I get no
sound on show the volume changing, but, I still get no sound even if I
raise it to 100%.


On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
> On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
> > If I boot with pci=noacpi, the normal mandriva kernel hangs just after
> > it says hit I for interactive setup.
>
> OK, try "pci=routeirq".
>
> Lee
>
>


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: Problem with several Creative Labs soundcards, possibly more?

[Bill Unruh]

On Sat, 22 Oct 2005, Nazo wrote:

> That said, Revell, I tried pci=routeirq on GeeXBoX and it made no
> obvious changes.  It occurs to me that maybe the two systems actually
> have seperate problems that just happen to have nearly the same
> effect.  Unfortunately, my attempts to install Mandriva all fail
> horribly.  It gets stuck every single time.  I've had a similar issue

It sounds like not that the Mandrake installation gets stuck but that rebooting
afterwards gets stuck.

When you see the boot prompt asking which of the kernels to boot, press esc
and then type 
linux 3

This will bring you up in console, not X mode. Now you can log in, and run
startx 2>/tmp/X
If it still gets stuck, do alt-ctrl-F1 and hit ctrl-C to stop the X trying
to come up.
Look in the file /tmp/X and see if there is something which gives you a
clue as to where the problem is.


> with Fedora Core 4.  Kubuntu gets stuck after starting X.  In each of
> these cases, the system is not frozen (I can move the mouse) but
> nothing ever comes up and I'm unable to do anything.  At this point,

alt-ctrl-bksp to kill off X or alt-ctrl-F2 to get a console to log in on
and try to figure out what the problem is.


> all I have left for diagnosing this problem is GeeXBoX.  (And yes, my

Whatever thatis

> system is 100% stable.  Prime95 stable.)  Other than the filesystem
> being damaged (and I've tried completely reformatting it, and, even
> changed the partition table so that it's no longer even in the same
> place, then reformatted again) I really can't think of a single thing
> that changed between the first installation and this most recent
> attempt.  I don't know if I can continue to diagnose this issue with
> just GeeXBoX, but, right now it's all that's left.
>
> One thing that is important to note about the issue in GeeXBoX is the
> fact that when I try to change the volume control, it doesn't work.
> It defaults to zero, and when I try to raise it, nothing happens.  It
> stays at zero.  I forgot this because most of the versions I get no
> sound on show the volume changing, but, I still get no sound even if I
> raise it to 100%.
>
>
> On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
>> On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
>>> If I boot with pci=noacpi, the normal mandriva kernel hangs just after
>>> it says hit I for interactive setup.
>>
>> OK, try "pci=routeirq".
>>
>> Lee
>>
>>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@lists.sourceforge.net


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Nazo]

linux 3 fails on the Mandriva installer.  It says that it does not
have a normal init and goes into a kernel panic.  Also, I meant it
when I said that it is the installer which gets stuck.  X starts up,
runs smoothly, the installation begins, I configure language,
partitions, etc, and, every single time, it gets stuck at the point
where it's checking packages (I can't say for sure if this is before
or after it finishes, only that all drive access stops and it stays
there for as long as I can wait.)  I do not get as far as selecting
what packages to install, so, at this stage, nothing has actually been
written to my harddrive.  I also still have the original unmodified
kernel that Mandriva defaulted to and it's default initrd on my boot
partition, so if it installed the files, I could still boot into it
sucessfully using that.  Anyway, when it sticks, bear in mind that the
mouse can still move, so the system is not frozen and X is still at
least acting somewhat properly.  Unfortunately, they block out things
such as CTRL+ALT+F1 (probably doesn't even support multiple consoles)
and CTRL+ALT+BACKSPACE.  I think X isn't to blame here.  I'm pretty
sure something gets stuck in the installer itself.  Thing is, the disc
appears to be fully readable, so I'm just not sure what could have
happened.  I don't think I changed anything on any of the partitions
it's supposd to NOT be accessing, and the partition I'm trying to
install to is blank and verified to be undamaged (by three different
tools I might add.)  At this point, I just give up on getting that to
work.

Kubuntu and FC4's installer both ignore me hitting things like
CTRL+ALT+BACKSPACE and CTRL+ALT+F1.  Again, X itself seems to be ok I
suspect.  At the point they get stuck, I would tend to say that if
they use a window manager, it is that which is having troubles.

Can any of these diagnostics be done in GeeXBoX, or have we pretty
well hit the limit of what can be done with it's meagre debugging
abilities?

On 10/22/05, Bill Unruh <unruh@physics.ubc.ca> wrote:
> On Sat, 22 Oct 2005, Nazo wrote:
>
> > That said, Revell, I tried pci=routeirq on GeeXBoX and it made no
> > obvious changes.  It occurs to me that maybe the two systems actually
> > have seperate problems that just happen to have nearly the same
> > effect.  Unfortunately, my attempts to install Mandriva all fail
> > horribly.  It gets stuck every single time.  I've had a similar issue
>
> It sounds like not that the Mandrake installation gets stuck but that rebooting
> afterwards gets stuck.
>
> When you see the boot prompt asking which of the kernels to boot, press esc
> and then type
> linux 3
>
> This will bring you up in console, not X mode. Now you can log in, and run
> startx 2>/tmp/X
> If it still gets stuck, do alt-ctrl-F1 and hit ctrl-C to stop the X trying
> to come up.
> Look in the file /tmp/X and see if there is something which gives you a
> clue as to where the problem is.
>
>
> > with Fedora Core 4.  Kubuntu gets stuck after starting X.  In each of
> > these cases, the system is not frozen (I can move the mouse) but
> > nothing ever comes up and I'm unable to do anything.  At this point,
>
> alt-ctrl-bksp to kill off X or alt-ctrl-F2 to get a console to log in on
> and try to figure out what the problem is.
>
>
> > all I have left for diagnosing this problem is GeeXBoX.  (And yes, my
>
> Whatever thatis
>
> > system is 100% stable.  Prime95 stable.)  Other than the filesystem
> > being damaged (and I've tried completely reformatting it, and, even
> > changed the partition table so that it's no longer even in the same
> > place, then reformatted again) I really can't think of a single thing
> > that changed between the first installation and this most recent
> > attempt.  I don't know if I can continue to diagnose this issue with
> > just GeeXBoX, but, right now it's all that's left.
> >
> > One thing that is important to note about the issue in GeeXBoX is the
> > fact that when I try to change the volume control, it doesn't work.
> > It defaults to zero, and when I try to raise it, nothing happens.  It
> > stays at zero.  I forgot this because most of the versions I get no
> > sound on show the volume changing, but, I still get no sound even if I
> > raise it to 100%.
> >
> >
> > On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
> >> On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
> >>> If I boot with pci=noacpi, the normal mandriva kernel hangs just after
> >>> it says hit I for interactive setup.
> >>
> >> OK, try "pci=routeirq".
> >>
> >> Lee
> >>
> >>
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by the JBoss Inc.
> > Get Certified Today * Register for a JBoss Training Course
> > Free Certification Exam for All Training Attendees Through End of 2005
> > Visit http://www.jboss.com/services/certification for more information
> > _______________________________________________
> > Alsa-user mailing list
> > Alsa-user@lists.sourceforge.net
>


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Bill Unruh]

On Sat, 22 Oct 2005, Nazo wrote:

> linux 3 fails on the Mandriva installer.  It says that it does not
> have a normal init and goes into a kernel panic.  Also, I meant it
> when I said that it is the installer which gets stuck.  X starts up,
> runs smoothly, the installation begins, I configure language,
> partitions, etc, and, every single time, it gets stuck at the point
> where it's checking packages (I can't say for sure if this is before
> or after it finishes, only that all drive access stops and it stays
> there for as long as I can wait.)  I do not get as far as selecting

Alt-Ctrl-F3 will bring up the console which lists what was happening at
that time.

Note one problem I ran into was where I had made /var/lib a link to
elsewhere (Why is irrelevant) When Mandrake tried to install it found that
the link was invalid, and so it tried to dump the package into into /root,
which was a memory filesystem and it filled up rapidly and the installation
froze. 
If you do that ( /var, /var/lib, or /var/lib/rpm) remove that link before
you install.

> what packages to install, so, at this stage, nothing has actually been
> written to my harddrive.  I also still have the original unmodified
> kernel that Mandriva defaulted to and it's default initrd on my boot
> partition, so if it installed the files, I could still boot into it
> sucessfully using that.  Anyway, when it sticks, bear in mind that the
> mouse can still move, so the system is not frozen and X is still at
> least acting somewhat properly.  Unfortunately, they block out things
> such as CTRL+ALT+F1 (probably doesn't even support multiple consoles)
> and CTRL+ALT+BACKSPACE.  I think X isn't to blame here.  I'm pretty
> sure something gets stuck in the installer itself.  Thing is, the disc
> appears to be fully readable, so I'm just not sure what could have
> happened.  I don't think I changed anything on any of the partitions
> it's supposd to NOT be accessing, and the partition I'm trying to
> install to is blank and verified to be undamaged (by three different
> tools I might add.)  At this point, I just give up on getting that to
> work.
>
> Kubuntu and FC4's installer both ignore me hitting things like
> CTRL+ALT+BACKSPACE and CTRL+ALT+F1.  Again, X itself seems to be ok I
> suspect.  At the point they get stuck, I would tend to say that if
> they use a window manager, it is that which is having troubles.

I strongly suspect hardware problems, not software.

>
> Can any of these diagnostics be done in GeeXBoX, or have we pretty
> well hit the limit of what can be done with it's meagre debugging
> abilities?
>
> On 10/22/05, Bill Unruh <unruh@physics.ubc.ca> wrote:
>> On Sat, 22 Oct 2005, Nazo wrote:
>>
>>> That said, Revell, I tried pci=routeirq on GeeXBoX and it made no
>>> obvious changes.  It occurs to me that maybe the two systems actually
>>> have seperate problems that just happen to have nearly the same
>>> effect.  Unfortunately, my attempts to install Mandriva all fail
>>> horribly.  It gets stuck every single time.  I've had a similar issue
>>
>> It sounds like not that the Mandrake installation gets stuck but that rebooting
>> afterwards gets stuck.
>>
>> When you see the boot prompt asking which of the kernels to boot, press esc
>> and then type
>> linux 3
>>
>> This will bring you up in console, not X mode. Now you can log in, and run
>> startx 2>/tmp/X
>> If it still gets stuck, do alt-ctrl-F1 and hit ctrl-C to stop the X trying
>> to come up.
>> Look in the file /tmp/X and see if there is something which gives you a
>> clue as to where the problem is.
>>
>>
>>> with Fedora Core 4.  Kubuntu gets stuck after starting X.  In each of
>>> these cases, the system is not frozen (I can move the mouse) but
>>> nothing ever comes up and I'm unable to do anything.  At this point,
>>
>> alt-ctrl-bksp to kill off X or alt-ctrl-F2 to get a console to log in on
>> and try to figure out what the problem is.
>>
>>
>>> all I have left for diagnosing this problem is GeeXBoX.  (And yes, my
>>
>> Whatever thatis
>>
>>> system is 100% stable.  Prime95 stable.)  Other than the filesystem
>>> being damaged (and I've tried completely reformatting it, and, even
>>> changed the partition table so that it's no longer even in the same
>>> place, then reformatted again) I really can't think of a single thing
>>> that changed between the first installation and this most recent
>>> attempt.  I don't know if I can continue to diagnose this issue with
>>> just GeeXBoX, but, right now it's all that's left.
>>>
>>> One thing that is important to note about the issue in GeeXBoX is the
>>> fact that when I try to change the volume control, it doesn't work.
>>> It defaults to zero, and when I try to raise it, nothing happens.  It
>>> stays at zero.  I forgot this because most of the versions I get no
>>> sound on show the volume changing, but, I still get no sound even if I
>>> raise it to 100%.
>>>
>>>
>>> On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
>>>> On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
>>>>> If I boot with pci=noacpi, the normal mandriva kernel hangs just after
>>>>> it says hit I for interactive setup.
>>>>
>>>> OK, try "pci=routeirq".
>>>>
>>>> Lee
>>>>
>>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by the JBoss Inc.
>>> Get Certified Today * Register for a JBoss Training Course
>>> Free Certification Exam for All Training Attendees Through End of 2005
>>> Visit http://www.jboss.com/services/certification for more information
>>> _______________________________________________
>>> Alsa-user mailing list
>>> Alsa-user@lists.sourceforge.net
>>
>

-- 
William G. Unruh   |  Canadian Institute for|     Tel: +1(604)822-3273
Physics&Astronomy  |     Advanced Research  |     Fax: +1(604)822-5324
UBC, Vancouver,BC  |   Program in Cosmology |     unruh@physics.ubc.ca
Canada V6T 1Z1     |      and Gravity       |  www.theory.physics.ubc.ca/


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: [Alsa-devel] Re: Problem with several Creative Labs soundcards, possibly more?

[Lee Revell]

On Sat, 2005-10-22 at 20:00 -0500, Nazo wrote:
> Well, I'm sorry, I'm going to stick with replying on top because, to
> me this seems like the least inconvenience for the largest number of
> people.
> 

Your opinion does not matter.  On this list it's considered rude.

> That said, Revell, I tried pci=routeirq on GeeXBoX and it made no
> obvious changes.  It occurs to me that maybe the two systems actually
> have seperate problems that just happen to have nearly the same
> effect.  Unfortunately, my attempts to install Mandriva all fail
> horribly.  It gets stuck every single time.  I've had a similar issue
> with Fedora Core 4.  Kubuntu gets stuck after starting X.  In each of
> these cases, the system is not frozen (I can move the mouse) but
> nothing ever comes up and I'm unable to do anything.  At this point,
> all I have left for diagnosing this problem is GeeXBoX.  (And yes, my
> system is 100% stable.  Prime95 stable.)  Other than the filesystem
> being damaged (and I've tried completely reformatting it, and, even
> changed the partition table so that it's no longer even in the same
> place, then reformatted again) I really can't think of a single thing
> that changed between the first installation and this most recent
> attempt.  I don't know if I can continue to diagnose this issue with
> just GeeXBoX, but, right now it's all that's left.
> 
> One thing that is important to note about the issue in GeeXBoX is the
> fact that when I try to change the volume control, it doesn't work. 
> It defaults to zero, and when I try to raise it, nothing happens.  It
> stays at zero.  I forgot this because most of the versions I get no
> sound on show the volume changing, but, I still get no sound even if I
> raise it to 100%.

Sorry, no idea.  Maybe there's somethign wrong with the hardware.

Lee



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Nazo]

Just where am I supposed to reply so that everyone is happy then since
at the top isn't good enough?  The bottom so people have to scroll
every single time just to see the response even if they know the rest
of the statement?  I never said it was opinion, I said that from what
I can see so far, it looks to me like it is best for the majority of
people if they are not forced to do this every single time.

That said, on the comment about hardware issue, this might be
theoretically possible, but, I must point out that everything works
100% perfectly in Windows, Prime95, gaming, and all.  If there is a
hardware problem, somehow it is triggered only in linux.  Either way,
it shows none of the symptoms of a hardware issue at this point.  The
system does not freeze, makes no strange noises, and does not
spontaneously reboot.  This can be caused by hardware if the software
does not respond correctly to a problem in the hardware I admit. 
Still, considering that the hardware has not changed, I'm inclined to
say software.

Anyway, personally, I just can't take this whole issue anymore. 
Everyone tells me the problem is due to another thing and to go report
elsewhere.  I can't get any version of linux to install anymore, and
only GeeXBoX of the live distros will even fully start up.  At this
point, I'm just forced to admit that I really don't use linux hardly
at all, but, I use windows almost 24/7, so this uphill battle just to
get things to even install or boot correctly for something I almost
never use just to see if I MIGHT be able to figure out why I have no
sound (not exactly a vital process, not to mention the fact that it's
also just as likely I'll never figure this out) just isn't worth it. 
For now, I'll just stick to music, gaming, etc in windows on the main
pc and continue to use the Yamaha card in my HTPC (which is better
than the AWE anyway.)

On 10/22/05, Lee Revell <rlrevell@joe-job.com> wrote:
> On Sat, 2005-10-22 at 20:00 -0500, Nazo wrote:
> > Well, I'm sorry, I'm going to stick with replying on top because, to
> > me this seems like the least inconvenience for the largest number of
> > people.
> >
>
> Your opinion does not matter.  On this list it's considered rude.
>
> > That said, Revell, I tried pci=routeirq on GeeXBoX and it made no
> > obvious changes.  It occurs to me that maybe the two systems actually
> > have seperate problems that just happen to have nearly the same
> > effect.  Unfortunately, my attempts to install Mandriva all fail
> > horribly.  It gets stuck every single time.  I've had a similar issue
> > with Fedora Core 4.  Kubuntu gets stuck after starting X.  In each of
> > these cases, the system is not frozen (I can move the mouse) but
> > nothing ever comes up and I'm unable to do anything.  At this point,
> > all I have left for diagnosing this problem is GeeXBoX.  (And yes, my
> > system is 100% stable.  Prime95 stable.)  Other than the filesystem
> > being damaged (and I've tried completely reformatting it, and, even
> > changed the partition table so that it's no longer even in the same
> > place, then reformatted again) I really can't think of a single thing
> > that changed between the first installation and this most recent
> > attempt.  I don't know if I can continue to diagnose this issue with
> > just GeeXBoX, but, right now it's all that's left.
> >
> > One thing that is important to note about the issue in GeeXBoX is the
> > fact that when I try to change the volume control, it doesn't work.
> > It defaults to zero, and when I try to raise it, nothing happens.  It
> > stays at zero.  I forgot this because most of the versions I get no
> > sound on show the volume changing, but, I still get no sound even if I
> > raise it to 100%.
>
> Sorry, no idea.  Maybe there's somethign wrong with the hardware.
>
> Lee
>
>


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

Re: Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Tim Sawchuck]

[-- Attachment #1: Type: text/plain, Size: 887 bytes --]

On Sat, 22 Oct 2005 21:28:57 -0500
Nazo wrote:

> Just where am I supposed to reply so that everyone is happy
> then since at the top isn't good enough?  The bottom so people

many of us will just delete your posts and not even try to help.
If you do not want to follow the choices of this list,
Bottom posting is the convention on this list.

see why it is so destructive to a thread to top post.
Go read the archives when trying to solve a problem and you will
Books read top to bottom, why post otherwise?

read this once a week or two....
are very busy in professional and personal lives and can only
Why do you assume that we follow each and every post?  Some of us

-- 
A: Because it messes up the order in which people normally read
text. 
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Re: [Alsa-user] Problem with several Creative Labs soundcards, possibly more?

[Tim Sawchuck]

[-- Attachment #1: Type: text/plain, Size: 887 bytes --]

On Sat, 22 Oct 2005 21:28:57 -0500
Nazo wrote:

> Just where am I supposed to reply so that everyone is happy
> then since at the top isn't good enough?  The bottom so people

many of us will just delete your posts and not even try to help.
If you do not want to follow the choices of this list,
Bottom posting is the convention on this list.

see why it is so destructive to a thread to top post.
Go read the archives when trying to solve a problem and you will
Books read top to bottom, why post otherwise?

read this once a week or two....
are very busy in professional and personal lives and can only
Why do you assume that we follow each and every post?  Some of us

-- 
A: Because it messes up the order in which people normally read
text. 
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]