September 2000 - openSUSE Users - openSUSE Mailing Lists

Re: [SLE] Still Notebook Shopping
by matt.wong＠intelligroup.co.nz 04 Sep '00

04 Sep '00

Hi Tim > another notebook I'm looking at, the Toshiba Satellite 550 MHz Celeron > Notebook > with 64 megs of ram, Dual Scan 12" LCD, 6 gig hard drive, etc. that is > mentioned > in the CompUSA ad for today (if you happened to read the ad today). Anyone > have any experience with it and Linux? What's the model number? You might want to check out: http://www.cs.utexas.edu/users/kharker/linux-laptop/ Probably repeating that here. > It looks quite nice, and it's price tag at Best Buy is merely $998. Is it > too good to be true for a Linux user? I'm running SuSE 6.3 on a Toshiba Satellite 4060XCDT and have had no issues. The above site was of some assistance for sound and an X Server for 6.1, but the SuSE Knowledge DB also provided me with some answers regarding my keyboard locking up on boot. Matt -- Matt Wong - Dude that does stuff at Intelligroup Asia/Pacific matt.wong(a)intelligroup.co.nz http://www.intelligroup.com Mobile: +64 25 710 233 Linux User #160471 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

3 4

[SLE] USB mouse not working after the install
by jlm＠compgen.com 04 Sep '00

04 Sep '00

The USB mouse is not working after installation. I have found and exact description of the problem in the suse support database entitled: "After the installation the USB mouse does not function any longer" But the fix doesn't seem to be working. If I replace INITRD_MODULES which is currently set to INITRD_MODULES="usbcore" with INITRD_MODULES="usbcore usb-uhci input hid mousedev keybdev", run mk_initrd, then run LILO from yast, and reboot, the machine perpetually reboots itself. Then if change back to the original INITRD_MODULES="usbcore", run mk_initrd, run LILO, and reboot, it stops the perpetual rebooting but the mouse still does not work. What does 'mousedev' refer to? Is it a module? Is anybody using a USB mouse successfully with suse 6.4? Thanks for any help. jlm -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

1 0

Re: [SLE] Still Notebook Shopping
by matt.wong＠intelligroup.co.nz 04 Sep '00

04 Sep '00

Hi Tim > > http://www.cs.utexas.edu/users/kharker/linux-laptop/ > > Thanks, that's helpful for other notebooks I was looking at. The one > CompUSA has is the 1675CDS. You should check out the link for the Toshiba Satellite 1620CDS and Toshiba Satellite 1640CDT: http://www.sslug.dk/~frank/toshiba1620.shtml They should be pretty close. > Perhaps a better question for everyone here is - if you were looking for > a lowend notebook (under $1,500) that worked well with Linux, which would you > recommend? Not too sure here. Perhaps a second hand one might be an option. > > I'm running SuSE 6.3 on a Toshiba Satellite 4060XCDT and have had no > > issues. > > The above site was of some assistance for sound and an X Server for 6.1, > > but the SuSE Knowledge DB also provided me with some answers regarding > > my keyboard locking up on boot. > > Thanks. Over all, are you satisified with you Linux Laptop experience? Yep, well it was either run windows (no flame war please) or get linux working on a laptop =) Matt -- Matt Wong - Dude that does stuff at Intelligroup Asia/Pacific matt.wong(a)intelligroup.co.nz http://www.intelligroup.com Mobile: +64 25 710 233 Linux User #160471 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

1 0

[SLE] LILO difficulties
by jpg＠cvuxgc.cvs.agilent.com 04 Sep '00

04 Sep '00

Hey GANG and Juergen, Trying to get LILO to work on a dual SCSI disk system. Done this successfully on two other, albeit different mobo's and SCSI HBA's, systems. I can get LILO to work if, and only if, the only SCSI disk active on the bus is the SuSE 6.4 disk. The SCSI HBA I have looks from SCSI ID 6 down to 0 for a bootable disk, which is opposite from the other Adaptec SCSI HBA's I've worked with in the past. The other Adaptec based cards search from ID 0 up to 6. Which means I would like to boot off of SCSI ID-2 (SuSE 6.4 /dev/sdb1), and see SCSI ID-1 (Windows 98 /dev/sda1) simultaneously. I have tried all different types of things, i.e. changing ID's of disks and modifying '/etc/fstab' and '/etc/lilo.conf' (and then re-executing lilo') so that the SuSE OS is at a lower SCSI ID than the Windows 98 OS. Re-compiling kernel, different boot managers (Partition Magic and Blue Sky Inovations Boot Manager) other than LILO to then point to which OS I wish to boot, but still use LILO on the SuSE disk. This system will end up being my packet filter (Firewall), and IP Masquerading host for our home network, so its kind of a relic. It is a 586 with 40 Mbytes of RAM. I am obviously overlooking something, can't see the forest for the trees, since this dual disk/dual boot has worked for me in the past on other systems. Help if you can. jpg Detailed basic rundown of events: ---------------------------------------------------------------------------- I got the plain vanilla SuSE 6.4 installed, with selected packages. However, at reboot I couldn't get LILO to load up the eide kernel. It would halt with: 'LI' Which, from the manual, indicates that something is in error with 'geometry mismatch' or moving '/boot/boot.b' without rerunning lilo. To verify/correct the 'boot.b' boot sector problem, even though I was sure I ran lilo, I booted off of floppy and selected 'Start installed system' on '/dev/sdb1'. No problem. I ran lilo, rebooted and attempted a boot off of the hard drive, same bad results with lilo. So now I thought it was the 'geometry mismatch' thing, I booted off of floppy again I then uncommented out the 'linear' option in lilo.conf, re-ran lilo again, and rebooted; same bad LILO results :( So after rebooting off of floppies, I re-commented the 'linear' option and re-ran lilo, to get back to where I started. I then unplugged the SCSI (windows 98) disk at ID-1, reset the '/etc/fstab' and '/etc/lilo.conf' accordingly to make the SuSE 6.4 disk '/dev/sda1'. This requires a couple of reboots and booting 'Rescue System' to successfully change these puppies, BTW. With just one disk, LILO works! But, although not a show-stopper, it would be nice to have the other SCSI disk available when up in Linux. I put LILO on the back burner, and recompiled my kernel to specifically match my old 586 machine hardwar and with firewalling and ip-masquerading. Installed my new kernel and saw that I now had a new boot sector '/boot/boot.b' file. What the heck, I thought I would see if this fixed the dual SCSI disk problem. So I plugged the windows 98 disk back in, reconfigured '/etc/fstab' and '/etc/lilo.conf' re-ran lilo (from rescue CD and booting from floppies again) and attempted a boot off of the SCSI hard drive partition at /dev/sdb1. Nope, same-old LILO problem, smiling at me. What the hey, I keep asking myself what am I missing? Below are printouts from pertinent files and kernel structures as to what I have currently on my system. And BTW, I still have to boot off of the floppy drive :( System specs: -------------- SCSI HBA = AHA-2920 BIOS v3.0 SCSI DISK ID2 = 2 Gbyte Seagate (SuSE 6.4) SCSI DISK ID1 = 2 Gbyte HP (Legacy Windows 98) $uname -a ------------------------------------------------------------- ------------------------------------------------------------- Linux gatekpr 2.2.14 #1 Fri Mar 17 11:58:46 GMT 2000 i486 unknown $cat /etc/lilo.conf ------------------------------------------------------------- ------------------------------------------------------------- # LILO Konfigurations-Datei # Start LILO global Section # If you want to prevent console users to boot with init=/bin/bash, # restrict usage of boot params by setting a passwd and using the option # restricted. #password=bootpwd #restricted initrd=/boot/initrd boot=/dev/sdb1 #compact # faster, but won't work on all systems. #linear # Generate linear sector addresses. vga = normal # force sane state read-only prompt timeout=100 # End LILO global Section # # SuSE 6.4 on SCSI disk at SCSI ID 2 image = /boot/vmlinuz root = /dev/sdb1 label = linux # # Windows 98 on SCSI disk at SCSI ID 1 #other = /dev/sda1 # label = winblows98 # table = /dev/sda # $cat /etc/fstab ------------------------------------------------------------- ------------------------------------------------------------- /dev/sdb1 / ext2 defaults 1 1 #/dev/sda1 /dos vfat defaults 0 0 /dev/hdd /cdrom auto ro,noauto,user,exec 0 0 /dev/fd0 /floppy auto noauto,user 0 0 none /proc proc defaults 0 0 # End of YaST-generated fstab lines $cat /proc/scsi/scsi ------------------------------------------------------------- ------------------------------------------------------------- Attached devices: Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: HP Model: C3325A Rev: 5172 Type: Direct-Access ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: SEAGATE Model: ST52160N Rev: 0344 Type: Direct-Access ANSI SCSI revision: 02 $fdisk -l /dev/sdb;fdisk -l /dev/sda ------------------------------------------------------------- ------------------------------------------------------------- Disk /dev/sdb: 255 heads, 63 sectors, 263 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 249 2000061 83 Linux /dev/sdb2 250 263 112455 82 Linux swap Disk /dev/sda: 255 heads, 63 sectors, 263 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 263 2112516 b Win95 FAT32 $lsmod ------------------------------------------------------------- ------------------------------------------------------------- Module Size Used by serial 19636 0 (autoclean) memstat 1476 0 (unused) fdomain 12460 1 tulip 30176 1 8390 6052 0 nvram 3340 0 (unused) snippets from '/usr/src/linux/.config ------------------------------------------------------------- ------------------------------------------------------------- # # SCSI support # CONFIG_SCSI=y . . . # # SCSI low-level drivers # CONFIG_SCSI_FUTURE_DOMAIN=y -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

2 2

[SLE] Re: [suse-security] X listening on 6000?
by ben＠whack.org 04 Sep '00

04 Sep '00

You could also add this to your /etc/profile as an alias to startx. This would work for you. alias startx='startx -- -nolisten tcp' --> -->startx -- -nolisten tcp --> -- Cheers, Ben Rosenberg mailto:ben@whack.org ------------------------- "The only 'intuitive' interface is the nipple. After that, it's all learned." -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

2 1

[SLE] Does being behind a proxy prevent upgrade?
by pbvanca＠ameritech.net 04 Sep '00

04 Sep '00

Dear List, My DSL (ATM Card) is on a win98 machine. I have a proxy running on win98 that my SuSE 6.3 linux sees across a 10/100 ethernet connection. I haven't been able to figure how to use the YAST FTP upgrade (as in "Upgrade to 7.0"). Netscape has a setting to use a proxy ( Proxy = 192.168.0.2:1080 ), but I can't find a YAST Setting to indicate the proxy address. The members of this list have been of great service to those less experianced users like me. Thanks for all your help! Pete VC -- =============================== Peter B.Van Campen pbvanca(a)ameritech.net =============================== -- <<Gnu is Not Unix / Linux Is Not UniX>> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

1 0

[SLE] Suse.com
by sienix＠flashmail.com 04 Sep '00

04 Sep '00

Has anyone noticed this... I can't access any of the SuSE sites (www.suse.com or ftp.suse.com) only the .de 's are available... There are links in the support database to the ftp.suse.com server... so this must be a problem... Kind regards Guy ______________________________________________________ Get Your FREE FlashMail Address now at http://www.flashmail.com It's Free, Easy, & Fun !!! -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

2 1

Re: [SLE] Major Ooops
by sienix＠flashmail.com 04 Sep '00

04 Sep '00

Just a question. Can I use my rescue system to boot any SuSE linux system or just the ones that were installed from that disk? If yes, this would be a serious security gap, because my linux server can't be placed in a secure location. It's in the normal offices... Being able to boot it with another rescue system would be a serious leak... Kind regards Guy ______________________________________________________ Get Your FREE FlashMail Address now at http://www.flashmail.com It's Free, Easy, & Fun !!! -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

3 2

Re: [SLE] Suse.com
by budr＠sirinet.net 04 Sep '00

04 Sep '00

"Guy Van Sanden" <sienix(a)flashmail.com> writes: > Has anyone noticed this... I can't access any of the SuSE sites > (www.suse.com or ftp.suse.com) only the .de 's are available... I had trouble getting to ftp.suse.com earlier today, but it seems to be up now. -- Bud Rogers <budr(a)sirinet.net> http://www.sirinet.net/~budr/zamm.html -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

1 0

[SLE] Kernel panick and cmos error
by dk983＠ncf.ca 04 Sep '00

04 Sep '00

Hi, I've been trying to build my own version of the 2.2.16 kernel but seem to be running into a problem. first the kernel goes in to a panic and stops and then when I try to reboot i get a CMOS error "cmos checksum error'. Is it possible that the kernel is trying to tinker with the cmos? Anyway I've done numerous kernel compiles, but this is the first time I've experienced this sort of thing. Can someone give me a hand? bruce Hi, <font size=3>Hi, I've been trying to build my own version of the 2.2.16 kernel but seem to be running into a problem. first the kernel goes in to a panic and stops and then when I try to reboot i get a CMOS error "cmos checksum error'. Is it possible that the kernel is trying to tinker with the cmos? Anyway I've done numerous kernel compiles, but this is the first time I've experienced this sort of thing. Can someone give me a hand? bruce Hi, </font>

2 1