Some Suse (minor) problems I have

big_gie · 12-10-2004, 04:45 AM

Hi,

I'm trying Suse 9.2 and I think its great! Its really nice but I get some minor problems...

1- Wireless Card
My computer is a Dell Inspiron 8500 with a mini-pci TrueMobile 1300 wi-fi card. There is no linux drivers for it, so I'm using ndiswrapper, the rpm that came with suse.
Internet is working great, but I need to "modprobe ndiswrapper" each time the computer boots up. My boot log is as follow:

Quote:

Originally Posted by boot log

<notice>start services (network)
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
done eth0 device: Broadcom Corporation BCM4401 100Base-T (rev 01)
eth0 configuration: eth-id-00:0d:56:39:b2:35
eth0 Startmode is 'manual'
skippedWaiting for mandatory devices: wlan0
20 19 18 16 15 14 13 12 11 10 9 8 7 5 4 3 2 1 0
wlan0 interface could not be set up
failedSetting up service network . . . . . . . . . . . . . . . .failed
<notice>exit status of (network) is (7)

What can be wrong that prevent the card from being set up?

2- Keychain
I installed keychain from a package found @ rpm.pbone.net (keychain-2.4.3-1.noarch.rpm) but I can't figure out how to make it work: even if I enter the command "keychain" in a terminal, it doesn't go find my ~/.ssh/id_rsa key so in all my sftp and ssh sessions I need to enter the passphrase manually, as if keychain doesnt do something.

3- During the installation, I manually partitioned my hd to have a partition for different mount point. But I forgot to make an entry for my 3 windows ntfs drives (C:, D: and E

so I added them manually in yast after setup was finish. But I can't see the mount point in the desktop icon "My computer"... How can I add a link for those 3 partitions in suse's "My Computer"?

4- I'm able to let users mount a drive, but how may I let him umount it?

5- Translation
I'm really sad that suse is really badly translated in french...

Thank you very much in advance for your support!!

Caeda · 12-10-2004, 12:20 PM

Ah... right.

Number 1 first...

A normal person would have read the documentation and or suse help files for about 1 mintue before suse suggests the file /etc/init.d/boot.local which is created solely for the purpose that you can put any commands you want run at boot time into it and they will be executed...

However, that would be the absolutely, 100% wrong way to config your network card, as your currectly using it wrong anyway...

Run yast, network devices, click on the one labeled network card. Delete everything. Make a new card, and use ndiswrapper as the module to load to run the card, and follow through to set your essid and encryption codes and itll load at boot...

I'll skip number 2 as I dont use keychain...

Number 3... right click? If you miss the menu for creating new hard drive device links, cd links, and or links to location... somethings wrong.

JunctaJuvant · 12-10-2004, 01:52 PM

Dito on point 2.
Regarding point 4: Have you included the mount option "user" in the appropriate entry in /etc/fstab? If so, have you tried "users" instead?

big_gie · 12-11-2004, 06:54 AM

Quote:

Originally posted by Caeda
Ah... right.

Number 1 first...

A normal person would have read the documentation and or suse help files for about 1 mintue before suse suggests the file /etc/init.d/boot.local which is created solely for the purpose that you can put any commands you want run at boot time into it and they will be executed...

However, that would be the absolutely, 100% wrong way to config your network card, as your currectly using it wrong anyway...

Run yast, network devices, click on the one labeled network card. Delete everything. Make a new card, and use ndiswrapper as the module to load to run the card, and follow through to set your essid and encryption codes and itll load at boot...

Hum, if you don't like to respond, don't do it. But if you do, please keep in mind that not everybody is a linux god like you.
Also, ndiswrapper was installed via Yast, with the suse cd's rpm. The card was configured via yast to, so what you said is no use, sorry mister i-know-it-all. Thats why I posted here.

Quote:

Originally posted by Caeda
Number 3... right click? If you miss the menu for creating new hard drive device links, cd links, and or links to location... somethings wrong.

After a couple of reboots those shortcuts have came back... Thats a weird one.
I tryed to right click, but even if konqueror is run as root, I get a "cannot write to drive:/"... But at least the shortcuts are back.

Quote:

Originally posted by JunctaJuvant
Regarding point 4: Have you included the mount option "user" in the appropriate entry in /etc/fstab? If so, have you tried "users" instead?

Hum... here's my fstab:

Quote:

Originally Posted by fstab

/dev/hda7 / reiserfs acl,user_xattr 1 1
/dev/hda5 /boot ext3 acl,user_xattr 1 2
/dev/hda8 /home reiserfs acl,user_xattr 1 2
/dev/hda6 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/hda1 /mnt/windows/c ntfs ro,user,defaults,nosuid,umask=022 0 0
/dev/hda10 /mnt/windows/d ntfs ro,user,defaults,umask=022 0 0
/dev/hda9 /mnt/windows/e ntfs ro,user,defaults,umask=022 0 0

You say I should try adding "users"? Whats the difference between "user" and "users"?

Thanx

JunctaJuvant · 12-11-2004, 08:49 AM

The "users" option means any user can mount and umount, this is what works for me.
I also see on the last three lines, the ntfs entries, you use the "defaults" option after the "user" option. I thought this option implies "nouser" and "rw" amongst other things, so it looks like you are saying "ro,rw, user,nouser,...", but since you can mount as a normal user it apparantly gets overridden.
Hope that helps.

JJ

[edit]
Forgot to mention the difference. According to the manual, "user" implies that any user can mount, but only the same user or root can umount. For me it doesn't work that way, perhaps someone else can explain why.
I also think the umask options in the ntfs sections are not necessary, since the "ro" option is used, or am I mistaken?
[/edit]

big_gie · 12-11-2004, 09:51 AM

Thanks JunctaJuvant!
My new fstab is like this:

Quote:

Originally Posted by fstab

/dev/hda7 / reiserfs acl,user_xattr 1 1
/dev/hda5 /boot ext3 acl,user_xattr 1 2
/dev/hda8 /home reiserfs acl,user_xattr 1 2
/dev/hda6 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/hda1 /mnt/windows/c ntfs ro,user,users,umask=022 0 0
/dev/hda10 /mnt/windows/d ntfs ro,user,users,umask=022 0 0
/dev/hda9 /mnt/windows/e ntfs ro,user,users,umask=022 0 0

and I can mount/unmount just correct!

I forgot to add something to the problem list:
If I keep my laptop on for a couple of hours (I'm trying to download something) while I'm away, it always freeze. What could be wrong?

Thanx again

JunctaJuvant · 12-11-2004, 10:34 AM

Glad to hear it's working, just one detail: I believe it is safe to omit the "user" option if you use the "users" option. See also "man mount".
Regarding your laptop question, I would recommend asking that on the laptop & handheld section of the forum and including more (hardware) information (what laptop? what network card? what have you tried? ... etc)
Just a thought...

JJ

big_gie · 12-11-2004, 10:54 AM

Ok thanx