Been using Kanotix (hd install, debian style) BH4 for months very happy and just added install of BH7a on another partition on that disk. Have run into a problem right off the bat.

User is unable to bring up modem at all (ttyS0), user is in dialout group - root has no trouble getting modem and configuring kppp. But I must log in as root. I am unable to bring it up from su when logged in as user. Nothing seems to work when I am root under user - although it accepts the root password commands such "kppp" "guarddog" or "kprint" results in an error along the lines of "server connection refused" "libx connection refused at server" I can get the exact message tonight and post from another machine (unable to access my old install at this time, will post separate topic).

Sudo doesn't seem to be working either. I get a message that user is not part of sudo group (user is and attempts to add it again result in message that user is already in that group.)

Very frustrating! suggestions of what to look at tonight most welcome, thanks

Some setups require you to be a part of a certain group to be able to su to root (usually the wheel group). It might be something as simple as that to be able to get you able to do that.

As far as the sudo group thing goes, you might try manually adding yourself to that group (editing the /etc/group file and placing your user name in where it should go*) and see if that helps that situation.


*In the /etc/group file, it would be something like this:
<group name>:x:<group number>:<group member>,<group member>,<...>

I will check the etc/group file, may already be in there as everything else says the user is but you never know stranger things happen

Wheel group I am not familiar with and don't remember seeing it in the groups list? Never had a problem like this with Kanotix before and I am quite disappointed. It is almost pure sid and updating is supposed to be very easy but I may never find out

Nearest to this problem I ever had was with some other live cd/hd install I think morphix. Dialup simply was not supported for users and I never went any further with that distro.

Awhile back had a problem with kppp after some update that I had to change ppp config to no auth for users, but this problem is different - it definitely is related to the inability to get su going.