-----BEGIN PGP SIGNED MESSAGE-----
On Monday 17 June 2002 09:19 pm, Glen Lee Edwards wrote:
>
> Kent, I won't defend what I wrote, but by way of explanation: I had one
> quality server (Red Hat) that crashed during upgrade a few weeks back.
> It has several years of customizations and programming work on it that
> I can't afford to lose. Unfortunately I didn't have the budget to buy
> another quality server. So when the upgrade failed, I lost a lot of
> the customizations, plus I have a couple hundred people who rely
> heavily on that server wanting to burn me in effigy. They won't blame
> Red Hat. After all, it was my decision to upgrade to 7.3. Not Red
> Hat's.
Glen, could I interest you in apt-rpm ?? It's a rather sweet package
for
your RH boxes.
>
> Being brand new to Debian, and in a real desperate situation here, I've
> been trying to get the web sites, mail, mailman list program, MyPHPNuke
> boards, etc., up and running. I've posted several letters to the list
> asking for help in various areas. I've received some great replies.
> But I've received just as many replies from idiots who left the subject
> line of my letter the same but who wrote only to complain that
> something was wrong with the way I posted the letter - no Reply-to:
> field, line wrap not set at 72, real stupid stuff that has nothing to
> do with my post. Can you imagine what it's like to be sitting here on
> pins and needles desperately hoping for an answer from those
> experienced with Debian so I can get the 200 irate people off my back,
> only to open the letter to find someone bellyaching that my line wrap
> isn't set to 72? That does very little positive for the disposition!
>
> Kent, there are people on this list who really need to get a life.
Ouch! But, you DO have help. :--) My only request is "Purdy Please!, no
html mail"
>
> > So, your next best bet is probably to search the Debian Mail List
> > archives, and then to post specific questions to this list. However,
>
> So I can become the prime target at another turkey shoot?
>
Not by most of us! We've been down this sad, dark, lonely road. :--(
> > to get you started, I offer the following suggestions.
> >
[snip]
> $ lspci
> 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02)
> 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev
> d0)
> 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
> 00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
> 10/100 Ethernet (rev 82)
> 00:01.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
> 00:01.3 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07)
> 00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS]
> SiS PCI Audio Accelerator (rev 02)
> 00:01.6 Modem: Silicon Integrated Systems [SiS]: Unknown device 7013
> (rev a0)
> 00:02.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
> 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
> SiS630 GUI Accelerator+3D (rev 31)
>
> I compiled the SiS audio module into the kernel. Question: does the
> above actually state that I have an SiS audio card on the system, or
> does it just state that I have a slot for a sound card? (Please no
> rude comments from anyone. If I knew the answer to that question I
> wouldn't have asked it).
lspci shows that yes, you DO have the sound chip on your motherboard and
'accessable". That's all. :--) So, let's see. Can you look at
"dmesg | less" and see if you can see what it says about the
initialization? THIS is where you'll see if the chipset was actually
activated.
p.s. You might wanna use lspci -vv | less to get more information (just
for YOU to look at while troubleshooting. The -vv equals VERY VERBOSE and
dumps a squatload of info on each device. But what we have here now is fine
for now. :--)
>
> Now what?
>
> Glen
- --
______________________________________________________________________________
OutCast Computer Consultants of Central Oregon
http://outcast-consultants.redmond.or.us
[EMAIL PROTECTED]
(541) 504-1388 /\IRC: 205.227.115.251:6667:#OutCasts /\ICQ: UIN 138930
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
