Usually, logging in as "root" at the KDE login screen produces a
normal desktop.

Now, it goes straight into YaST, and closing YaST drops back to the
login screen.

How do I get out of this and back to a normal KDE desktop for
"root", please? Other users get the KDE desktop, as normal.

Tks....Steve J

On Sun, 01 Aug 2004 21:11:04 -0000
steve_johnson016 wrote:

> Usually, logging in as "root" at the KDE login screen produces a
> normal desktop.
>
> Now, it goes straight into YaST, and closing YaST drops back to the
> login screen.

Could it be that you have changed some security setting somewhere? What
you're experiencing as a 'problem' is actually a pretty sensible thing
for the root account, and therefore might be intended - there's nothing
root should want to do when logged in but administration - which is
YaST.

>
> How do I get out of this and back to a normal KDE desktop for
> "root", please? Other users get the KDE desktop, as normal.

I've no idea, but I suggest that you don't try at all. There's no reason
for you to want to log into KDE as root (no good reason, at least). Run
your computer as a normal user. When you need root priviledges, open an
xterm and do a:

su -

in there. If you want to run a graphical application from within this
xterm (again, there's no good reason to want this), you can copy the
.Xauthority file from the home directory of the user who started X to
/root/, if necessary also define the $DISPLAY variable:

export DISPLAY=":0.0"

and it should work.

Cheers

--
Horror Vacui

Registered Linux user #257714

Go get yourself... counted: http://counter.li.org/
- and keep following the GNU.

This situation is an error, it is not intended.  Logging into "root"
used to produce a KDE desktop, same as any other user.  Something
changed, but I don't know what.

I run my tape backups from "root", otherwise there are file
permission issues.

I appreciate your suggestion, but this is treating the symptom, not
the problem.  But if I have too, I'll give it a try.

Steve J

OK, here's what I'm going to do.  While SUSE somehow trashed my W2000
boot ability on my home box, making me spend the whole weekend
reinstalling stuff, it did NOT screw up the boot section on my work
computer.  I'll try learning Linux/SUSE on the work machine--as time
allows.  Probably the first thing to do is get it to connect to the
'net--which failed during the install.  The modem is an Ethernet Cisco
Soho (DSL)--I'm in Milan, Italy.

Benesesso

> It's better that way.  If I had known you had a 2nd machine available,
> I would have suggested that in the first place... Dual-booting,
> frankly, sucks.  Two computers sharing the same keyboard, video & mouse
> with a KVM switch is far superior.  You probably want seperate speaker
> systems.
>

Hi there,
I m using suse desktop edition, my yahoo chat applet is not loading in
konqueror and mozilla. Kindly help me to fix problem.

Raj

steve_johnson016 wrote:
> Usually, logging in as "root" at the KDE login screen produces a
> normal desktop.
>
> Now, it goes straight into YaST, and closing YaST drops back to the
> login screen.
>
> How do I get out of this and back to a normal KDE desktop for
> "root", please? Other users get the KDE desktop, as normal.
>
> Tks....Steve J

login to your normal user's login
You DID make some of those, right....

And from there, use the su command to become root

$ su

now, you have a TEXT-login to root.
from there, you can poke around at things with root privileges


All of you people who keep saying that you always rely on
the GUI tools for administration... Steve here has just
shown why, in the long run, that's a BAD idea.

Use the command line for administration for as much as possible.

benesesso wrote:
> OK, here's what I'm going to do.  While SUSE somehow trashed my W2000
> boot ability on my home box, making me spend the whole weekend
> reinstalling stuff, it did NOT screw up the boot section on my work
> computer.  I'll try learning Linux/SUSE on the work machine--as time
> allows.  Probably the first thing to do is get it to connect to the
> 'net--which failed during the install.  The modem is an Ethernet Cisco
> Soho (DSL)--I'm in Milan, Italy.

The modem is a seperate device from your computer.

As long as the Ethernet connection between the two is good,
then your networking should work  (A modem is nothing more than
a MODulator / DEModulator... i.e. a signal converter)... modems
do absolutely ZERO data-interpretation of their own.
They are merely wave-form converters.


>
> Benesesso
>
>
>>It's better that way.  If I had known you had a 2nd machine available,
>>I would have suggested that in the first place... Dual-booting,
>>frankly, sucks.  Two computers sharing the same keyboard, video & mouse
>>with a KVM switch is far superior.  You probably want seperate speaker
>>systems.
>>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>

some help please.
I have a pair of 120gb HDD halfway loaded with a broken install of SuSE  8.2 and
I want to Fdisk them, load XP Pro then install SuSE 9.1.


How can I get fdisk to work on these drives?  all I have are OS install CDs

thanks

--
chas
The new Canon DSLR elist.  no trolls, etc
http://groups.yahoo.com/group/canon-dslr/join

...

Yes, I knew that.  What I don't know is how to get SUSE to connect to
the internet.
>
> The modem is a seperate device from your computer.
>
> As long as the Ethernet connection between the two is good,
> then your networking should work  (A modem is nothing more than
> a MODulator / DEModulator... i.e. a signal converter)... modems
> do absolutely ZERO data-interpretation of their own.
> They are merely wave-form converters.
>

Sure, I made some normal users...using one right now.

"from there, you can poke around at things with root privileges".
Ah..but it's what I have to poke is the bit I don't know...hence the
question.

Steve J

> How can I get fdisk to work on these drives?  all I have are OS install
CDs

I don't have a Windows rescue disk?
If so, just start in DOS, use fdisk and then format.

I know this may sound silly!  But do have a linux driver for the modem?

Frank  Taylor

*********** REPLY SEPARATOR  ***********

On 03/08/2004 at 07:22 benesesso wrote:

    Yes, I knew that.  What I don't know is how to get SUSE to connect to
    the internet.
    >
    > The modem is a seperate device from your computer.
    >
    > As long as the Ethernet connection between the two is good,
    > then your networking should work  (A modem is nothing more than
    > a MODulator / DEModulator... i.e. a signal converter)... modems
    > do absolutely ZERO data-interpretation of their own.
    > They are merely wave-form converters.
    >











    Yahoo! Groups Links

benesesso wrote:
> Yes, I knew that.  What I don't know is how to get SUSE to connect to
> the internet.
>

The same way you would if the Network card was directly connected
to the router at the other end.  Modems are invisible devices.

>>The modem is a seperate device from your computer.
>>
>>As long as the Ethernet connection between the two is good,
>>then your networking should work  (A modem is nothing more than
>>a MODulator / DEModulator... i.e. a signal converter)... modems
>>do absolutely ZERO data-interpretation of their own.
>>They are merely wave-form converters.
>>
>
>
>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>

steve_johnson016 wrote:
>
> Sure, I made some normal users...using one right now.
>
> "from there, you can poke around at things with root privileges".
> Ah..but it's what I have to poke is the bit I don't know...hence the
> question.

try this:

$ su
password:
# cd ~root
# rm -rf .kde

Frank Taylor wrote:
> I know this may sound silly!  But do have a linux driver for the modem?

Proper modems (which includes all DSL modems) don't need drivers.

The only modems that need drivers are those glorified sound-cards
called "WinModems" which, truth be told SHOULD be called LoseModems.

Even internal modems that are REAL modems (i.e. not LoseModems)
appear as nothing more than serial ports, for which no special
drivers (beyond serial port drivers) are needed.

The Modulator/Demodulator activity of ALL **REAL** modems are 100%
transparent to the operating system...because the activity is done
completely by the modem's hardware, and the operating system does
not run it in any way.

>
> Frank  Taylor
>
> *********** REPLY SEPARATOR  ***********
>
> On 03/08/2004 at 07:22 benesesso wrote:
>
>    Yes, I knew that.  What I don't know is how to get SUSE to connect to
>    the internet.
>    >
>    > The modem is a seperate device from your computer.
>    >
>    > As long as the Ethernet connection between the two is good,
>    > then your networking should work  (A modem is nothing more than
>    > a MODulator / DEModulator... i.e. a signal converter)... modems
>    > do absolutely ZERO data-interpretation of their own.
>    > They are merely wave-form converters.
>    >
>
>
>
>
>
>
>
>
>
>
>
>    Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>

Nevertheless, some MODEM makers do list a Linux driver.

Frank

*********** REPLY SEPARATOR  ***********

On 03/08/2004 at 06:42 Aaron Kulkis wrote:

    Frank Taylor wrote:
    > I know this may sound silly!  But do have a linux driver for the
modem?

    Proper modems (which includes all DSL modems) don't need drivers.

    The only modems that need drivers are those glorified sound-cards
    called "WinModems" which, truth be told SHOULD be called LoseModems.

    Even internal modems that are REAL modems (i.e. not LoseModems)
    appear as nothing more than serial ports, for which no special
    drivers (beyond serial port drivers) are needed.

    The Modulator/Demodulator activity of ALL **REAL** modems are 100%
    transparent to the operating system...because the activity is done
    completely by the modem's hardware, and the operating system does
    not run it in any way.

    >
    > Frank  Taylor
    >
    > *********** REPLY SEPARATOR  ***********
    >
    > On 03/08/2004 at 07:22 benesesso wrote:
    >
    >    Yes, I knew that.  What I don't know is how to get SUSE to connect
    to
    >    the internet.
    >    >
    >    > The modem is a seperate device from your computer.
    >    >
    >    > As long as the Ethernet connection between the two is good,
    >    > then your networking should work  (A modem is nothing more than
    >    > a MODulator / DEModulator... i.e. a signal converter)... modems
    >    > do absolutely ZERO data-interpretation of their own.
    >    > They are merely wave-form converters.
    >    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >    Yahoo! Groups Links
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    > Yahoo! Groups Links
    >
    >
    >
    >
    >
    >






    Yahoo! Groups Links

Nevertheless, some MODEM makers do list a Linux driver.
Originally, I had an external ADSL MODEM which I could never get to work
with Linux.
I now have a Wireless router which uses ethernet to connect to both systems
- seamlessly.

Many of us exWindows people have problems with 'modems'
Windows tuition is conspicuous by its abscence.

Regards

    Frank

    *********** REPLY SEPARATOR  ***********

    On 03/08/2004 at 06:42 Aaron Kulkis wrote:

       Frank Taylor wrote:
       > I know this may sound silly!  But do have a linux driver for the
    modem?

       Proper modems (which includes all DSL modems) don't need drivers.

       The only modems that need drivers are those glorified sound-cards
       called "WinModems" which, truth be told SHOULD be called LoseModems.

       Even internal modems that are REAL modems (i.e. not LoseModems)
       appear as nothing more than serial ports, for which no special
       drivers (beyond serial port drivers) are needed.

       The Modulator/Demodulator activity of ALL **REAL** modems are 100%
       transparent to the operating system...because the activity is done
       completely by the modem's hardware, and the operating system does
       not run it in any way.

       >
       > Frank  Taylor
       >
       > *********** REPLY SEPARATOR  ***********
       >
       > On 03/08/2004 at 07:22 benesesso wrote:
       >
       >    Yes, I knew that.  What I don't know is how to get SUSE to
    connect
       to
       >    the internet.
       >    >
       >    > The modem is a seperate device from your computer.
       >    >
       >    > As long as the Ethernet connection between the two is good,
       >    > then your networking should work  (A modem is nothing more
than
       >    > a MODulator / DEModulator... i.e. a signal converter)...
modems
       >    > do absolutely ZERO data-interpretation of their own.
       >    > They are merely wave-form converters.
       >    >
       >
       >
       >
       >
       >
       >
       >
       >
       >
       >
       >
       >    Yahoo! Groups Links
       >
       >
       >
       >
       >
       >
       >
       >
       >
       >
       > Yahoo! Groups Links
       >
       >
       >
       >
       >
       >






       Yahoo! Groups Links










    Yahoo! Groups Links

I'm curious about those internal DSL modems that my provider (Qwest
DSL) offered for much cheaper. They said for Windows only, and that
for Linux I was required to pay tons for an external DSL router.
    --jeffs

--- In suselinuxusers@yahoogroups.com, Aaron Kulkis <akulkis@H...> wrote:

> Proper modems (which includes all DSL modems) don't need drivers.

Frank Taylor wrote:
> Nevertheless, some MODEM makers do list a Linux driver.
>

Yes...but not REAL modems, only "win" (lose) modems.

> Frank

Steve J,

I'm a little confused here.

The kde login you are referring to...  This is the kdm login screen that
SuSE defaults to, correct?  Typically, this offers not only different
users, but also different window managers and desktop environments.
When you type in "root" (root is not typically a displayed user), you
have the option of kde, but gnome is often an option here (depending on
how you setup initially), I believe "failsafe" will almost certainly be
there.

kdm is not generally very customizable for different users at the login
   screen, as it is not associated with any particular user...
re: configuring kdm:
http://docs.kde.org/en/3.1/kdebase/kdm/Configuring-kdm.html

Now, on the other hand, if you are clicking the "administration" button
(after "starting a new session"), that pops you into YaST exactly as you
have described.  It's very similar to doing a  "xinit /sbin/yast2 -- :1"
from another terminal.  This _is_ what it is supposed to do.  If you
want to change the behavior of the administration button... well... I'm
sure it's possible... probably deep in the kdm.conf file or something...
but, I wouldn't touch it if I were you...

One option you might try (for testing purposes) is logging in on a
different virtual terminal as root and typing "startx -- :1"  this
should bring you into a root kde session on tty08 (unless you set your
WINDOWMANAGER variable to something else (in fact, theoretically, I
suppose it's possible to setup your WINDOWMANAGER variable to
/sbin/yast2, but you could check that by typing "echo $WINDOWMANAGER".
You probably won't get anything back, so the default is kde (unless you
edited the startx script), anyway.  Regardless, that variable shouldn't
come into play if you are logging with the kdm gui, only if you use
startx...

so my questions to you:
1. Do you have different window managers installed on your machine and
do they operate normally with the root user -- or are they bring up YaST
as well?
2.  Including failsafe?
3.  Do you even get the kde starting up stuff?  The splash screen and
the lighting icons?   Because that would be really weird... Or are you
literally going straight into YaST? -- which is what I think is happening
4.  does the "startx -- :1" option work?
5.  does "xinit /usr/X11R6/bin/kde -- :1" work?  This is kind of like
the startx thing, but eliminates the WINDOWMANAGER EnvVar
6.  if #5 still brings up YaST, I guess that does indeed make it a
problem with kde.  Somehow you've managed to make kde mapped to
/sbin/yast2.  In fact, you should probably check the link at that point
(as /usr/X11R6/bin/kde is merely a link to startkde.  Okay,  I think
we're getting a little far out here of the realm of possibility.  I
doubt you've gone this far in my little list.  But if you have, check
out "file /usr/X11R6/bin/kde" and if it says that it's a symbolic link
to startkde, then it just gets worse from here, because that would be
the right answer and the problem develops into an issue with the
startkde script or the kde binaries or something much worse.



Anders Lankford


steve_johnson016 wrote:
> Usually, logging in as "root" at the KDE login screen produces a
> normal desktop.
>
> Now, it goes straight into YaST, and closing YaST drops back to the
> login screen.
>
> How do I get out of this and back to a normal KDE desktop for
> "root", please? Other users get the KDE desktop, as normal.
>
> Tks....Steve J
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>

OK, now we're getting somewhere.  The DSL modem is external.  I don't
think there are any drivers for it-Win or Linux.

All I know is that it was turned on when I installed SUSE, and it
reported that the modem installation (or whatever) failed.  Hmmm, now
that I think about it, every time I had to reinstall W2000 for one of
its frequent problems, I had to have the company computer guy come to
the office with some kind of software.  I'll ask him about Linux.

Benesesso

--- In suselinuxusers@yahoogroups.com, Aaron Kulkis <akulkis@H...> wrote:
> Frank Taylor wrote:
> > Nevertheless, some MODEM makers do list a Linux driver.
> >
>
> Yes...but not REAL modems, only "win" (lose) modems.
>
> > Frank

hmmm...

Which cisco soho DSL device is it?

76?  77?  78? (there are probably others).  It's probably irrelevant,
but it's good to mention it...

Since the device is -really- not as much a modem as it is a router to
your machine... "drivers" are probably not the issue.  All SuSE's going
to care about is if a device is talking/listening on the same subnet
over TCP/IP and if the route to the Internet (default route) is via that
device's IP address.  If you can ping it, and the default route is
correct, then you should be okay.  most likely the device is setup as a
DHCP server, as well, probably on the 10.0.0.255 subnet... so make sure
that you're system is looking for an address assignment from that
router.  Check the cable, too.  try a cat-5 into a hub and see if that
works.  That way you can play with both machines on the hub, too.

Oh yeah, and if you're going over a wireless network, you may want to
flash it with new firmware, anyway...

Firmware, however...  yeah, flash it with new firmware.  That might play
into it...

I ran across a forum thread where somebody had a pcmcia cisco soho and
after they used it with an XP machine, the device wouldn't work with
Linux anymore (yes, I know -- unbelievably weird).  They resolved the
issue by flashing the router with _old_ firmware, and suddenly the thing
worked.  weird.  If you're curious, here's the thread:
http://www.broadbandreports.com/forum/remark,10732119~mode=flat

But first:

Log on to it via the serial cable and make sure it's all setup correctly
for dhcp and such.  Are you getting good link lights?  I believe you
said this is the "work" computer at some point, so I assume you are
hooking this device up directly to the network card on your computer,
and not to a hub?  Are you setup for that device to be your dhcp server?
   Or are you using some other sort of routing?  Hmmm.. come to think of
it, if this is the "work" computer, than why aren't you using the "work"
network to reach the Internet...  Oh wait.  You "work" from home, or
something, right?  And I'll bet this whole thing ends up as some sort of
VPN nightmare with great clogged firewalls and proprietary vpn software
that only runs well with Windows ME or something and we'll have to play
around with wine to get it working and the documentation's only
available in Korean and... oy...

    ...Alright...  well, anyway, where were we?  oh yes.  log into the
device and check how it is setup, get it's ip and make sure DHCP is
setup how you like it, etc, etc, and then try the firmware thing.

The software that your "computer guy" probably dumped on your win2k
machine was probably something like "cisco dsl commander" (or it's got a
name that's similar to that).  Anyway, it's just a gui-driven method of
setting up the router, which can all be done via the serial cable, with
a few well placed cisco commands, anyway.  If the "computer guy" can't
setup your DSl router via telnet, you should probably call up your dsl
company for assistance.  Somebody at your ISP can almost certainly tell
you what to type, and how their equipment works with Linux.
...but, I'll bet it's not the first tech you talk to...


Anders Lankford




benesesso wrote:
> OK, now we're getting somewhere.  The DSL modem is external.  I don't
> think there are any drivers for it-Win or Linux.
>
> All I know is that it was turned on when I installed SUSE, and it
> reported that the modem installation (or whatever) failed.  Hmmm, now
> that I think about it, every time I had to reinstall W2000 for one of
> its frequent problems, I had to have the company computer guy come to
> the office with some kind of software.  I'll ask him about Linux.
>
> Benesesso
>
> --- In suselinuxusers@yahoogroups.com, Aaron Kulkis <akulkis@H...> wrote:
>
>>Frank Taylor wrote:
>>
>>>Nevertheless, some MODEM makers do list a Linux driver.
>>>
>>
>>Yes...but not REAL modems, only "win" (lose) modems.
>>
>>
>>>Frank
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>

I tried this approach, but it was not pretty.  In my case, I had to
do a clean install of 9.0 back on my PC.  For some reason 9.1 doesn't
support my SCSI card driver for initio anymore.

Good luck to all.
Vedat

MSI6380E w/ Athlon XP2000+
784MB PC2700 DDR RAM
Western Digital 80 GB w/8MB cache
SIIG SCSI controller
HP9210i SCSI CDR/CDRW
Lite-ON CD/DVDROM
XFX Nvidia FX5200 w/256MB RAM
Creative Sound Blaster 16
Netgear FX310 10/100 NIC

--- In suselinuxusers@yahoogroups.com, boschie <no_reply@y...> wrote:
> --- In suselinuxusers@yahoogroups.com, "Brian Greenberg" <bjg@a...>
wrote:
> > Ok, this has been bugging me for a while.  How can I upgrade from
> > 9.0 to 9.1 using YOU/YAST?  Each time I try to update either
using
> > the 'system update' or 'online update' there doesn't seem to be a
> > mechanism to go from 9.0 to 9.1.  Can anyone help me with this?
> >
> > Thanks,
> > Brian
>
> Go into YAST and then into Change Installationsource (or something
> like that, i have the dutch version so i don't know the Englisch
frase).
>
> Here you click add -> FTP.
> By servername you type the mirrorserver, in my case: ftp.mirror.nl
> By directory you type the directory on that server, in my case:
> pub/mirror/suse/i386/current/
> Click finish and then you should be able to do a system update to
9.1
>
> GRTZ,
> boschie

I had a rather interesting surprise this morning. My computer is set
up to dual-boot WinXP and Suse Linux... but it can't boot up WinXP
today. Everything has been working fine until now, but I'm getting an
error from the bootloader that says that NTLDR is missing. I can only
assume that is the NT loader.

I don't know how the file got corrupted, but I would like to fix it
because the other people who use this computer will ONLY use windows.
I installed Suse about 2 months ago to start learning linux, but am no
where near comfortable yet (I just haven't had a lot of time to spend
on it yet).

I could really use some help here. Can someone tell me how to install
(or re-install as the case may be) the NTLDR in the proper area so
that it will make the grub boot loader work again?

If it helps, I'm using the most recent personal desktop version of
Suse and KDE.

Thank you,
Nicole

On Tue, 03 Aug 2004 19:41:21 -0000
Nicole wrote:

> I had a rather interesting surprise this morning. My computer is set
> up to dual-boot WinXP and Suse Linux... but it can't boot up WinXP
> today. Everything has been working fine until now, but I'm getting an
> error from the bootloader that says that NTLDR is missing. I can only
> assume that is the NT loader.

That's right.

>
> I don't know how the file got corrupted, but I would like to fix it
> because the other people who use this computer will ONLY use windows.
> I installed Suse about 2 months ago to start learning linux, but am no
> where near comfortable yet (I just haven't had a lot of time to spend
> on it yet).

Just don't boot Linux because you "want to learn it", configure a
minimum that you need for approachingly normal usage - internet and
mail, say - and use it. The learning comes by itself.

>
> I could really use some help here. Can someone tell me how to install
> (or re-install as the case may be) the NTLDR in the proper area so
> that it will make the grub boot loader work again?

You have it a bit mixed up. grub is not the problem here, as long as it
points toward a correct partition for Windows. I think we may assume
that nothing has changed there. NTLDR resides on the partition where
Windows is installed, and it has somehow gone missing.

So Windows is what you need to troubleshoot. Use the Windows install
disk to boot the machine into repair mode and try to repair the windows
install. Remember to install grub to a floppy disk (see man grub on how
to do this, I don't know) before this operation though, since Windows
will probably overwrite the MBR, and you'll need the floppy to boot back
to Linux and reinstall grub.

Cheers

--
Horror Vacui

Registered Linux user #257714

Go get yourself... counted: http://counter.li.org/
- and keep following the GNU.

Nicole,

Well... you should probably take this XP issue to an XP group, but anyway...

I sincerely hope that you have merely left a floppy in the "A" drive
(ugh, NT terms)... but this link should clarify and will hopefully
enlighten you further regarding the potential unpleasantness of your
situation... (it also has some possible fixes)

http://www.computerhope.com/issues/ch000465.htm

Maybe you can get away with popping the XP cd in and running a (r)epair. ..

I'll keep my fingers crossed for you...

Anders Lankford



Nicole wrote:
> I had a rather interesting surprise this morning. My computer is set
> up to dual-boot WinXP and Suse Linux... but it can't boot up WinXP
> today. Everything has been working fine until now, but I'm getting an
> error from the bootloader that says that NTLDR is missing. I can only
> assume that is the NT loader.
>
> I don't know how the file got corrupted, but I would like to fix it
> because the other people who use this computer will ONLY use windows.
> I installed Suse about 2 months ago to start learning linux, but am no
> where near comfortable yet (I just haven't had a lot of time to spend
> on it yet).
>
> I could really use some help here. Can someone tell me how to install
> (or re-install as the case may be) the NTLDR in the proper area so
> that it will make the grub boot loader work again?
>
> If it helps, I'm using the most recent personal desktop version of
> Suse and KDE.
>
> Thank you,
> Nicole
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>

Ow, my head hurts!  Never heard of DHCP.  There are 2 computers on our
work network.  We (my coworker and I) are the customers (engineers) at
work, and we have the only DSL line in the place.

Somehow I think if I knew even half the stuff you have just written
about I could make W2000 work for me instead of the other way around.

I'll see what the CCG (company computer guy) has to say about all this
tomorrow.

Benesesso

--- In suselinuxusers@yahoogroups.com, Anders Lankford
<andersvidar@y...> wrote:
> hmmm...
>
> Which cisco soho DSL device is it?
>
> 76?  77?  78? (there are probably others).  It's probably irrelevant,
> but it's good to mention it...
>
> Since the device is -really- not as much a modem as it is a router to
> your machine... "drivers" are probably not the issue.  All SuSE's going
> to care about is if a device is talking/listening on the same subnet
> over TCP/IP and if the route to the Internet (default route) is via
that
> device's IP address.  If you can ping it, and the default route is
> correct, then you should be okay.  most likely the device is setup as a
> DHCP server, as well, probably on the 10.0.0.255 subnet... so make sure
> that you're system is looking for an address assignment from that
> router.  Check the cable, too.  try a cat-5 into a hub and see if that
> works.  That way you can play with both machines on the hub, too.
>
> Oh yeah, and if you're going over a wireless network, you may want to
> flash it with new firmware, anyway...
>
> Firmware, however...  yeah, flash it with new firmware.  That might
play
> into it...
>
> I ran across a forum thread where somebody had a pcmcia cisco soho and
> after they used it with an XP machine, the device wouldn't work with
> Linux anymore (yes, I know -- unbelievably weird).  They resolved the
> issue by flashing the router with _old_ firmware, and suddenly the
thing
> worked.  weird.  If you're curious, here's the thread:
> http://www.broadbandreports.com/forum/remark,10732119~mode=flat
>
> But first:
>
> Log on to it via the serial cable and make sure it's all setup
correctly
> for dhcp and such.  Are you getting good link lights?  I believe you
> said this is the "work" computer at some point, so I assume you are
> hooking this device up directly to the network card on your computer,
> and not to a hub?  Are you setup for that device to be your dhcp
server?
>   Or are you using some other sort of routing?  Hmmm.. come to think of
> it, if this is the "work" computer, than why aren't you using the
"work"
> network to reach the Internet...  Oh wait.  You "work" from home, or
> something, right?  And I'll bet this whole thing ends up as some
sort of
> VPN nightmare with great clogged firewalls and proprietary vpn software
> that only runs well with Windows ME or something and we'll have to play
> around with wine to get it working and the documentation's only
> available in Korean and... oy...
>
>    ...Alright...  well, anyway, where were we?  oh yes.  log into the
> device and check how it is setup, get it's ip and make sure DHCP is
> setup how you like it, etc, etc, and then try the firmware thing.
>
> The software that your "computer guy" probably dumped on your win2k
> machine was probably something like "cisco dsl commander" (or it's
got a
> name that's similar to that).  Anyway, it's just a gui-driven method of
> setting up the router, which can all be done via the serial cable, with
> a few well placed cisco commands, anyway.  If the "computer guy" can't
> setup your DSl router via telnet, you should probably call up your dsl
> company for assistance.  Somebody at your ISP can almost certainly tell
> you what to type, and how their equipment works with Linux.
> ...but, I'll bet it's not the first tech you talk to...
>
>
> Anders Lankford
>
>
>
>
> benesesso wrote:
> > OK, now we're getting somewhere.  The DSL modem is external.  I don't
> > think there are any drivers for it-Win or Linux.
> >
> > All I know is that it was turned on when I installed SUSE, and it
> > reported that the modem installation (or whatever) failed.  Hmmm, now
> > that I think about it, every time I had to reinstall W2000 for one of
> > its frequent problems, I had to have the company computer guy come to
> > the office with some kind of software.  I'll ask him about Linux.
> >
> > Benesesso
> >
> > --- In suselinuxusers@yahoogroups.com, Aaron Kulkis <akulkis@H...>
wrote:
> >
> >>Frank Taylor wrote:
> >>
> >>>Nevertheless, some MODEM makers do list a Linux driver.
> >>>
> >>
> >>Yes...but not REAL modems, only "win" (lose) modems.
> >>
> >>
> >>>Frank
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >

--- In suselinuxusers@yahoogroups.com, "steve_johnson016"
<stephen.johnson@i...> wrote:
> Usually, logging in as "root" at the KDE login screen produces a
> normal desktop.
>
> Now, it goes straight into YaST, and closing YaST drops back to the
> login screen.
>
> How do I get out of this and back to a normal KDE desktop for
> "root", please? Other users get the KDE desktop, as normal.
>
> Tks....Steve J

Is it possible that when previously running YaST, it did not close
or shutdown properly? Next time you login, close YaST when it comes
up. Open a console (Terminal) window. Type in 'ps -A | more'. If
YaST is closed but a process is still running, then 'kill' it. If
process is 'hung' it starts up everytime you boot.

example:

  3347 ?        00:00:01 kdesu
  3348 ?        00:00:00 yast2
  3362 ?        00:00:03 y2controlcenter

command - kill 3348 (and or 3362)

do a man on kill if you need to.

I had this problem with kaffiene. May or may not be the same thing.

Good Luck,
DapperDan

Anders Lankford wrote:
> Steve J,
>
> I'm a little confused here.
>
> The kde login you are referring to...  This is the kdm login screen that
> SuSE defaults to, correct?  Typically, this offers not only different
> users, but also different window managers and desktop environments.

No, he's referring to what comes up AFTER he types in the password.

benesesso wrote:
> OK, now we're getting somewhere.  The DSL modem is external.  I don't
> think there are any drivers for it-Win or Linux.

Correct, because ALL external modems are real modems.
[Although, like telephone modems, they CAN have vendor-defined
escape sequences (remember Hayes modems...and the Hayes
command protocol which is used by most every telephone modem
manufacturer to this day..)