On Tue, 25 Jun 2002, Praedor Tempus wrote: > Manpage, schmanpage. I use them when possible but then there are those bogus > pages that give the wrong command syntax (outdated or based on a non-linux > system) or list the commands without providing for an example. To me, it > doesn't count as an example if the manpage begins with a command followed by > a series of bracketed or braced switches - in some cases, due to past > experience only, I can deal with this but when it is something newish, > perhaps half the time I can't make heads or tails of the actual proper > command syntax. > > Anyhoo. I have my laptop up to snuff and fine but my desktop is killing me. > First, a harddrive failure caused by a mobo failure plus cpu death - > expensive replacement for all. Fortunately, I had just installed 8.2 on it > and hadn't yet installed or done anything of importance on it so nothing was > lost but time and money. New mobo, new cpu, new hdd and a fresh install of > 8.2 croaked last night after working for all of 10 minutes. Different > problem this time, though the root of it is still a mystery to me. I THINK > it may be irq related though kcontrol shows nothing suspicious (nor does > lspci).
If you're allowing the install to configure your hardware I can't for the life of me figure how you're getting irq conflicts. as for your sound card Mandrake is Id-ing the device correctly. the SB16 card has an ESS chipset in it. ESS1371 to be exact. I don't really care for that chipset very much. in Mandrake it seems to require a lot of tweaking before it behaves correctly. > A couple things...I bought a SB 16 for the new mobo but Mandrake identifies it > as an ESS 1371 - it works but an ESS 1371 and no mention is the harddrake > list of any SB 16? Next, first bootup and start. OK. Open up a konsole and > begin typing in commands to change hostname ala the laptop and boop! > Soundcard beeps and beeps and beeps in an endless loop, the mouse freezes and > the keyboard is locked. Nothing to do but hard reboot. After that, OK until > about 30 minutes of typing and clicking then same thing. Reboot. KDE now > unstartable because of DCOP communication problems. I delete everything > related to KDE in my home directory (.kde and .kderc) and do a > Ctrl-Alt-Bkspc. Login and KDE still refuses to start now - dying at the it's very likely that your FS was trashed during the hard boots. that would explain he fact that nothing wanted to start for you. > splash screen. Login again and try Gnome. Nothing. Try Windowmaker - OK, > starts and works. Try Enlightenment - OK, starts and works. Look at my > .xsession-errors. One entry only about inability to connect to X server > :0.0. Try running XFDrake and resetting X. REALLY screwed up X so that no > window manager will start, just KDM a few times until it craps out and now > dumped to CLI. > > BAH! Reinstalling MDK 8.2 again, this time trying a different fs - third > reinstall. First tried ext3 for first time. SLOW! Then tried XFS. Good, > quick, but then the problems related above and it being seemingly impossible > to fix X or KDE. Reinstall and go back to my trusty ReiserFS which I have > been using for a couple years now. I no longer try to fix KDE problems such > as I related above as I have found it impossible to correct in the past, even > with total uninstalls and reinstalls. I can relate as far as the ReiserFS thing goes. I too have been using Reiser for a little while and I've come to the conclusion where this FS is concerned that if it ain't broke I'm not gonna try and fix it. Reiser runs the roost on my boxes. > Anyone ever run into something like this before? The difference in this > desktop vs before when there were no linux/software problems is the addition > of a PCI to PCMCIA adaptor, the connection of a linksys WUSB11 wlan box, a Praedor...sad but true...it's a proven fact that pcmcia is the worlds _worst_ form of connectivity technology. it is the spawn of satan. if at all possible I avoid this stuff like the plague. anything like this that is a HUGE PITA in a laptop surely hasn't got a snowball's chance in hell of being dependable and working well on a PC platform. yuck! > soundcard (was using mobo sound before but new mobo has no builtin sound), > and a Robotics PCI modem (not a winmodem). Since the wusb11 isn't recognized > or usable yet under linux (I'm trying), the pcmcia hasn't yet received a card > (intending to insert another wlan card), the only interrupts to be used are > for the i82365 pcmcia controller, the modem, and the soundcard. It looks > like the soundcard and modem share an irq but that is all. Why would the > soundcard lock into an endless loop (two installs so far) and freeze all > peripherals if it isn't sharing an irq with any of these other items? for real! at this point I would remove the sound and the peripheral hardware off this machine, install the OS and then go at it adding only one peice of hardware at a time till you find the guilty party that is screwing up you system. again...it this is being caused by an irq conflict I'm going to be very surprised, however, if it _is_ the case on this machine its no doubt a bad hardware mismatch from the peripherals that you're trying to get to play nice on this poor bugger all at the same time. -- daRmaTTeR R L U: #186492 When ever people annoy me I remember, "Vengence is mine saith the Lord." My prayer is, "...here am I Lord...send me!"
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
