No sound on PWS500au (miata)
Hi I have a PWS500au running Debian testing/unstable with Kernel 2.4.18-custom. I modprobe sb and everything seems to be fine dmesg output: Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 sb: No ISAPnP cards found, trying standard ones... SB 3.01 detected OK (220) ESS chip ES1888 detected at 0x220 irq 7 dma 1,5 ojeoje:~# lsmod Module Size Used byNot tainted sb 10152 0 (unused) sb_lib 53582 0 [sb] uart401 8528 0 [sb_lib] sound 91048 0 [sb_lib uart401] soundcore 6608 4 [sb_lib sound] I can cat something>/dev/dsp and xmms seems to work too, is there something special I forgot, or seems my hardware to be defective? any suggestions? --Tran pgp4ZEbDA7UQN.pgp Description: PGP signature
Re: Debian Insatll Compaq XP 1000
Can you boot with bf24 ? I don't know if that is an option for the alpha, but you can give it try. i would disconnect the second hdd, install with 2.2.20, switch to 2.4.x and reconnect the hdd. Building boot-floopies will take much much more. I did that several times. Ionut On Tue, Sep 30, 2003 at 04:25:18PM -0300, Marcio Gustavo Di Vernieri Cuppari wrote: > Hi > > I am trying to install debian woody on a Compaq XP 1000. Tried te CD but > the ssytem freezes when probing the second SCSI disk. I tried a floppy > instalation with the same problem. > > Also tried to compile a kernel for this machine (2.4.22) and this time > there was no problem probing the SCSI hardware (the SCSI controller is a > Qlogic ISP1020 and the problem was solved using the iqslogic module). > > The probelma now is when using the root disk it gives a lot of weird > messages about no being able to find the tail comand. I think the > problem is that the root disk was created for a 2.2.20 kernel. > > Does anyone know how to create the install floppies from scratch? > > Thanks in advance > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- *** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * "In Windows you can do everything Microsoft wants you to do; in Unix you *can do anything the computer is able to do."
Re: No sound on PWS500au (miata)
On Wed, Oct 01, 2003 at 12:10:52PM +0200, Jan Hetges wrote: > > I have a PWS500au running Debian testing/unstable with Kernel > 2.4.18-custom. I modprobe sb and everything seems to be fine > > dmesg output: > > Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 > sb: No ISAPnP cards found, trying standard ones... > SB 3.01 detected OK (220) > ESS chip ES1888 detected > at 0x220 irq 7 dma 1,5 > > ojeoje:~# lsmod > Module Size Used byNot tainted > sb 10152 0 (unused) > sb_lib 53582 0 [sb] > uart401 8528 0 [sb_lib] > sound 91048 0 [sb_lib uart401] > soundcore 6608 4 [sb_lib sound] > > I can cat something>/dev/dsp and xmms seems to work too, > is there something special I forgot, or seems my hardware to be defective? Yes, it should NOT be IRQ 7, but IRQ 5. Good luck. --Jay++ - Jay A EstabrookHPTC - LINUX support Hewlett-Packard Company - MRO1-2/K15 (508) 467-2080 200 Forest Street, Marlboro MA 01752 [EMAIL PROTECTED] -
Re: No sound on PWS500au (miata)
On Wed, 1 Oct 2003 09:53:59 -0400 Jay Estabrook <[EMAIL PROTECTED]> wrote: > On Wed, Oct 01, 2003 at 12:10:52PM +0200, Jan Hetges wrote: > > > > I have a PWS500au running Debian testing/unstable with Kernel > > 2.4.18-custom. I modprobe sb and everything seems to be fine > > > > dmesg output: > > > > Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 > > sb: No ISAPnP cards found, trying standard ones... > > SB 3.01 detected OK (220) > > ESS chip ES1888 detected > > at 0x220 irq 7 dma 1,5 > > > > ojeoje:~# lsmod > > Module Size Used byNot tainted > > sb 10152 0 (unused) > > sb_lib 53582 0 [sb] > > uart401 8528 0 [sb_lib] > > sound 91048 0 [sb_lib uart401] > > soundcore 6608 4 [sb_lib sound] > > > > I can cat something>/dev/dsp and xmms seems to work too, > > is there something special I forgot, or seems my hardware to be defective? > > Yes, it should NOT be IRQ 7, but IRQ 5. I tried IRQ 5,7 and 10, both SRM isacfg and module-parameter, but with no effect, seems really to be a hardware problem! How can I tell SRM to completely switch off the onboard sound? thx -- tran pgp3u2lzLzUPu.pgp Description: PGP signature
RE: Dec Alpha 500 (panda boxes or PC164) Possibly OT
Hey.. My purpose is "because it sounds like fun". In reading your email, it doesn't' seem like I can really just throw in a new CPU. I wouldn't be opposed to a new MOBO, power supplies, & CPU, but that sounds like it will start to get expensive. I don't know the value of a 'current' Alpha ev67? <-- it the most current ? Then of course I would probably need all new memory, so this exercise just got real expensive.. h The panda Boxes are 7RU blue metal with an aggressive "V" cut in the middle. I' haven't taken a picture of them yet, but I could post a pic if you were REAL curious. Greg. -Original Message- From: Stefan Schroepfer [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 1:40 PM To: [EMAIL PROTECTED] Cc: debian-alpha@lists.debian.org Subject: Re: Dec Alpha 500 (panda boxes or PC164) Possibly OT Greg wrote: > > I have a couple Dec Alpha PC164 500s and a few more Panda Boxes (also 500s). Nice. PC164 boards together with 500 MHz (ev56) CPUs were sold rather chaep back in 1997. I don't know, what panda boxes are, though. > I'm wondering how much trouble it would be to throw in a current CPU ?? or > MOBO ?? Which parts exactly do you want to preserve? The next generation of Alpha CPUs was *incompatible* to the "Socket 499" of Alpha ev56 and had very new requirements regarding the memory interface. The next generation of Alpha CPUs (ev6 and ev67) were introduced back in 1999 (IIRC), so what do you mean by "throwing in a current CPU"? Even if you plan to preserve only the cases and Power-Supplies: Be aware of the fact, that the original PC164 boards had "special" requirements regarding the power supply (i.e.: were not really ATX- compatible). Use Google or ask again. > Or am I just F'n Crazy ? Maybe. Regards, Stefan Schroepfer
Re: Dec Alpha 500 (panda boxes or PC164) Possibly OT
Greg wrote: Hey.. My purpose is "because it sounds like fun". In reading your email, it doesn't' seem like I can really just throw in a new CPU. I wouldn't be opposed to a new MOBO, power supplies, & CPU, but that sounds like it will start to get expensive. I don't know the value of a 'current' Alpha ev67? <-- it the most current ? Then of course I would probably need all new memory, so this exercise just got real expensive.. A short lesson: To make it simple: Forget about that. IIRC, Alpha ev67 (as well as ev6 as it's precedessor) was introduced back in 1999. At that time, Compaq had already taken over DEC, the inventor of the Alpha architecture. All plans to create a competitive HW-platform (against Intel) were abandoned back then. As a result, the development of cheap ev6-based Systems was stopped by Compaq (as well as the development of Windows NT for the Alpha platform). Without having a explitily "cheap version" of ev6x (which was one of the goals of DEC), two branches of development started. One of these branches was based on the Tsunami chipset (AFAICT originally developed by DEC people). Most of this Tsumani-based Systems had their CPU sitting on a "daughtercard", which is of course incompatible to anything else. Tsunami based systems were anything else but chaep, at least in Dual-CPU configurations, back then. Look for a "DS10L" system at islandco.com for cheapest (but somewhat crippled, regarding memory interface) ev6x systems. The other branch was the path taken by Samsung, read: to create Motherboards based on the AMD 751 Chipset (look for UP1000, UP1100, UP1500). At least some of these boards had CPUs soldered directly on the board. Uh, did I forget API? ;-) Current CPUs would be of type ev7 (or even ev79), which are (respectively will be) sold by HP only together with systems to those people, who can not be convinced to buy "more convenient" systems. Of course, there is no "socket compatibility" to prior Alpha-Systems, as these CPUs have the memory controller On-Chip (similar to the Opteron/Athlon64 family, which took over this concept). Sorry if I told something wrong or forgot something, Stefan Schroepfer
