> > >>2/3/02 11:44:19 AM, Derek Jennings <[EMAIL PROTECTED]> wrote: >> >>>On Sunday 03 February 2002 16:31, Marc Oestreicher wrote: >>>> Hi I am brand new to linux. >>>Welcome to Linux. It;s a lot of fun. You will be amazed at how good it >>>is....but.. there is a lot to learn. Signing up for this list is a good >>>start.. >>> >>>SNIP >>>> The only way that I could find to get out of it was to shut off the power >>>> switch. >>>First thing to learn is to avoid shutting down with the power switch. Thats >>>'Windows thinking' >>>If Linux has one weakness it is that it does not like sudden power downs >>>especially if you installed with the default Ext2 file system) (Search this >>>list archive for instructions on upgrading to Ext3 if you have not already >>>done so http://www.mail-archive.com/newbie@linux-mandrake.com/ ) >>> >>>If you cannot shut down any other way then hit keys in this sequence :- >>> >>>Alt+Sysreq+r (sysreq is above your 'Insert' key) to go into 'eaw' >>>keyboard mode. >>>Alt+Sysreq+t to close all open applications >>>Alt+Sysreq+s to write unsaved data to disc >>>Alt+Sysreq+b to reboot. >>> >>>Your shutdown will then be graceful and you will not corrupt your discs. >>> > THANKS Alt Sysreq b Got me out of the lockup on shutdown >>> >>>After doing some research I found that portmap was not needed and >>>> shut it off. but still got modem is busy message and then found that on >>>> shutdown the machine locked on ( stopping internet connection if needed ) >>>> again the only way I could find to get out of it was to use the power >>>> switch! >>> > I discovered the interactive startup function ( pressing the I key while >starting up ) > And disadled the usb devices at startup however that made no diferance, I >then tried to >disable other things one at a time on following startups. Wen I got to Sys Log >and shut it off >the machine did not lockup on the next shutdown However I still want to find a >better fix. so >that I dont have to do a interactive startup each time. > Also it seems to me that by disableing Sys Log I am probably masking the >problem rather >than fixing it. >>For the lock up there are a couple of possibilities. >>>First there is a known problem with usb interfaces causing lock up on power >>>down. Check this out http://mandrakeforum.com/article.php?sid=1321&lang=en >>> >>>Secondly, some users have reported that they get lock ups when shutting down >>>network services. I do not remember the exact fix, but I am sure someone will. >>>Are we talking about Dial up or Ethernet here? >> Just Dial up Nothing fancy until I figure out the basic stuff. > In desperation and after a few things going well for a change causeing > Me to lose some of my linux fear I started to mess around with the modem >settings > And in the KDE desktop tried Internet KPPP Setup Device > Change Modem To /dev/ttys2 That got rid of the modem is busy problem > And gave me a modem is ready message then a modem doesn't respond >message. > It still dosen't work but at least I am getting a message that makes some >sense!! > I am guessing that I may have to install a driver to get the modem >working the > rest of the way I HOPE I also got a ISA internal hardware modem from >my >neighbor this afternoon > that may be a better way to go but I havent figured that out for shure yet. > Any Ideas as to if I am ON THE RIGHT TRACK or not ??? > > >>>> I next tried a new modem with the intel ham m chipset, it is suposed to >>>> be a 90% hardware modem and work with Linux. and still the same problem. >>> >>>What type of modem? Make, model?, PCI or ISA? Internal or External? >>> > Intel V.90/56K intenal PCI fax modem MD563X-HaM chipset >>>> I then thought that hard drake would autodetect the modem if I reinsalled, >>>> so I deleted the linux partisions in windoze with partion magic and >>>> reinstalled Mandrake 8.1 from scratch and had the same problems, >>> >>>Linux scans for new hardware everytime it boots. You do not need to reinstall >>>to make it do a detection. >>> >>> >>>> and once >>>> again shut off portmap. Then still had the same problems as before. >>> >>>Many modem problems turn out to be IRQ conflict problems. Try reassigning IRQ >>>lines in your BIOS. Avoid any devices sharing IRQ's > > > I Just tried that with no sucess . > However the advise tht you have given me this far HAS BEEN A BIG HELP!!!!! > All my linux problems have not been solved yet but some have and your advise has >given >me a few new > things to think about and reserch. That a least provides a light at the end of >the tunnel!!!! > > THANKS > Marc >>> >>>derek >>> >>> >>> >>> >> >> > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
