January 2004 - openSUSE Users - openSUSE Mailing Lists

dbz.h what package provides in 9.0
by sean＠tcob1.net 05 Feb '04

05 Feb '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As per subject? Sean - -- GPG Key Id 120A02FB ICQ: 679813 Jabber: tcobone(a)jabber.org TCOB1.net hosting service now availble -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: This key has an expiry date iD8DBQFAGlX7XjH8pRIKAvsRAnSwAKDCaLuA8zYamKUXO0FAdyUUcV7crwCaAgfS JWo5j0f1HWbpm0kL3IjF2HQ= =0WQU -----END PGP SIGNATURE-----

3 6

k_smp-2.4.20-102 deemed harmful to cdrecord
by David Krider 05 Feb '04

05 Feb '04

I can't believe this nonsense. I have been abusing myself for something like 5 years with "Linux on the desktop," always thinking that the next release would be "it." Today, I'm trying to burn a CD. JUST BURN A CD! And on two separate -- though very similar -- computers, I'm getting the exact same nonsense. (Which is to say that it's not my hardware, both of which have worked just fine the last time I tried on each.) I'm long past trying to burn as a normal user. Oh no. That would be too hard. I can't even burn as root any more. It's really simple. I have a completely-SCSI setup. ``cdrecord --scanbus'' as root sees all my hardware. 0,0,0 0) 'IBM ' 'DDYS-T18350N ' 'S96H' Disk 0,1,0 1) 'SEAGATE ' 'ST318437LW ' '0105' Disk 0,2,0 2) 'PLEXTOR ' 'CD-ROM PX-40TS ' '1.11' Removable CD-ROM 0,3,0 3) 'PLEXTOR ' 'CD-R PX-W124TS' '1.05' Removable CD-ROM 0,4,0 4) 'IOMEGA ' 'ZIP 100 ' 'J.03' Removable Disk 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * But today, all of a sudden, I get crap like this (in this example, I'm just trying to burn the image for the SuSE 8.2 boot CD, so I know it's good): enterprise:/home/david/tmp # cdrecord -v dev=0,3,0 speed=12 root Cdrecord 2.0 (i686-suse-linux) Copyright (C) 1995-2002 J?rg Schilling TOC Type: 1 = CD-ROM scsidev: '0,3,0' scsibus: 0 target: 3 lun: 0 Linux sg driver version: 3.1.24 Using libscg version 'schily-0.7' cdrecord: Warning: using inofficial libscg transport code version (okir(a)suse.de-scsi-linux-sg.c-1.75-resmgr-patch '@(#)scsi-linux-sg.c 1.75 02/10/21 Copyright 1997 J. Schilling'). atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : SYNC LINKED Vendor_info : 'PLEXTOR ' Identifikation : 'CD-R PX-W124TS' Revision : '1.05' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : MMC SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 2373168 = 2317 KB FIFO size : 4194304 = 4096 KB Track 01: data 44 MB Total size: 51 MB (05:05.38) = 22904 sectors Lout start: 51 MB (05:07/29) = 22904 sectors cdrecord: Input/output error. start/stop unit: scsi sendcmd: no error CDB: 1B 00 00 00 01 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F0 00 0B 00 00 00 00 00 Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (valid) cmd finished after 0.000s timeout 40s Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type A, high Beta category (A+) (3) ATIP start of lead in: -11634 (97:26/66) ATIP start of lead out: 359848 (79:59/73) Disk type: Short strategy type (Phthalocyanine or similar) Manuf. index: 3 Manufacturer: CMC Magnetics Corporation Blocks total: 359848 Blocks current: 359848 Blocks remaining: 336944 Starting to write CD/DVD at speed 12 in real TAO mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting new track at sector: 0 Track 01: 1 of 44 MB written (fifo 100%) [buf 67%] 23.9x.cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 03 A2 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F0 00 0B 00 00 00 00 00 Sense Key: 0xB Aborted Command, Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (valid) cmd finished after 0.000s timeout 40s write track data: error after 1904640 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 Writing time: 26.126s Average write speed 28.3x. Fixating... Fixating time: 24.048s cdrecord: fifo had 94 puts and 31 gets. cdrecord: fifo was 0 times empty and 13 times full, min fill was 95%. I know what errors like this are about. I know how involved, and how machine-specific they can be. I know there's no chance that someone can tell me what the problem would be. I keep up with all the patches, so the best I can hope for is for someone to tell me that the latest kernel or bugfix patch screwed something up. Otherwise, I think I'll just go insane. There's no excuse for this. Linux just CAN'T be this hard, or it will NEVER succeed on the desktop. Whatever is going on, I'll take the blame. Since it's not hardware, it's got to be software, and how I manage my machines. But, MAN!, I'm not a noob. I've working with Linux for almost 10 years now, and I'm a Unix admin in my day job. It's not like I don't know what I'm doing! Problematic CD burning was the final straw with Red Hat 8.0 for me. I actually filed a bug that got to be well known on their list, but the bug remained through 9, and it's probably still in Fedora, though I'm well past caring. I guess I'm just writing this to vent my frustration. If by some miracle, someone can actually tell me how to fix this, I'll just consider myself lucky. And, yes, I Googled myself silly with these messages. I even downloaded the entire backlog of the cdrecord-support listserv. Lots of people have the problems *like* this, and apparently NO ONE has any answers, even the guy who wrote cdrecord. Post mortem: I stared at my navel for a few minutes and downgraded to the k_smp-2.4.20-100 kernel. That was it. It's apparently been that long since I tried to burn a disc. I still say that there's no excuse for this. Why did a security fix break burning CD's? Who knows. Again, this sort of thing is pretty hardware-specific, I know. Aaaargh! Sigh, dk P.S. Just in case you're still reading, here's the nonsense from the messages file, in case anyone might be able to do something with it. If someone involved with the kernel development wants to contact me, I'd work myself silly getting whatever logs or scans or whatever is needed to fix this. Jan 30 21:20:17 enterprise kernel: scsi0:0:3:0: Attempting to queue an ABORT message Jan 30 21:20:17 enterprise kernel: CDB: 0x0 0x0 0x0 0x0 0x0 0x0 Jan 30 21:20:17 enterprise kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< Jan 30 21:20:17 enterprise kernel: scsi0: Dumping Card State in Command phase, at SEQADDR 0x178 Jan 30 21:20:17 enterprise kernel: Card was paused Jan 30 21:20:17 enterprise kernel: ACCUM = 0x80, SINDEX = 0xa0, DINDEX = 0xe4, ARG_2 = 0x3 Jan 30 21:20:17 enterprise kernel: HCNT = 0x0 SCBPTR = 0x1d Jan 30 21:20:17 enterprise kernel: SCSISIGI[0x84]:(BSYI|CDI) ERROR[0x0] SCSIBUSL[0xc0] Jan 30 21:20:17 enterprise kernel: LASTPHASE[0x80]:(CDI) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) Jan 30 21:20:17 enterprise kernel: SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x15]:(SINGLE_EDGE) Jan 30 21:20:17 enterprise kernel: SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0x0] SSTAT0[0x5]:(DMADONE|SDONE) Jan 30 21:20:17 enterprise kernel: SSTAT1[0x2]:(PHASECHG) SSTAT2[0x10]:(EXP_ACTIVE) SSTAT3[0x0] Jan 30 21:20:17 enterprise kernel: SIMODE0[0x8]:(ENSWRAP) SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) Jan 30 21:20:17 enterprise kernel: SXFRCTL0[0x88]:(SPIOEN|DFON) DFCNTRL[0x4]:(DIRECTION) Jan 30 21:20:17 enterprise kernel: DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) Jan 30 21:20:17 enterprise kernel: STACK: 0x35 0xee 0x170 0x186 Jan 30 21:20:17 enterprise kernel: SCB count = 36 Jan 30 21:20:17 enterprise kernel: Kernel NEXTQSCB = 19 Jan 30 21:20:17 enterprise kernel: Card NEXTQSCB = 19 Jan 30 21:20:17 enterprise kernel: QINFIFO entries: Jan 30 21:20:17 enterprise kernel: Waiting Queue entries: Jan 30 21:20:17 enterprise kernel: Disconnected Queue entries: Jan 30 21:20:17 enterprise kernel: QOUTFIFO entries: Jan 30 21:20:17 enterprise kernel: Sequencer Free SCB List: 13 25 21 9 12 0 30 27 1 10 3 20 2 4 23 11 14 8 19 6 18 17 24 7 22 16 26 15 31 5 28 Jan 30 21:20:17 enterprise kernel: Sequencer SCB Info: Jan 30 21:20:17 enterprise kernel: 0 SCB_CONTROL[0xc0]:(DISCENB|TARGET_SCB) SCB_SCSIID[0x37] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 1 SCB_CONTROL[0xc0]:(DISCENB|TARGET_SCB) SCB_SCSIID[0x37] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 2 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 3 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 4 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 5 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 6 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 7 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 8 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 9 SCB_CONTROL[0xc0]:(DISCENB|TARGET_SCB) SCB_SCSIID[0x37] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 10 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 11 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 12 SCB_CONTROL[0xc0]:(DISCENB|TARGET_SCB) SCB_SCSIID[0x37] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 13 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 14 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 15 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 16 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 17 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 18 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 19 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 20 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 21 SCB_CONTROL[0xc0]:(DISCENB|TARGET_SCB) SCB_SCSIID[0x37] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 22 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 23 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 24 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 25 SCB_CONTROL[0xc0]:(DISCENB|TARGET_SCB) SCB_SCSIID[0x37] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 26 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 27 SCB_CONTROL[0x80]:(TARGET_SCB) SCB_SCSIID[0x37] SCB_LUN[0x0] Jan 30 21:20:17 enterprise kernel: SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 28 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 29 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x37] SCB_LUN[0x0] Jan 30 21:20:17 enterprise kernel: SCB_TAG[0xe] Jan 30 21:20:17 enterprise kernel: 30 SCB_CONTROL[0xc0]:(DISCENB|TARGET_SCB) SCB_SCSIID[0x37] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: 31 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x17] Jan 30 21:20:17 enterprise kernel: SCB_LUN[0x0] SCB_TAG[0xff] Jan 30 21:20:17 enterprise kernel: Pending list: Jan 30 21:20:17 enterprise kernel: 14 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x37] SCB_LUN[0x0] Jan 30 21:20:17 enterprise kernel: Kernel Free SCB list: 18 28 0 30 29 20 15 26 12 2 35 13 1 4 31 22 10 25 11 27 8 7 9 16 23 34 21 17 3 24 5 6 33 32 Jan 30 21:20:17 enterprise kernel: Untagged Q(3): 14 Jan 30 21:20:17 enterprise kernel: DevQ(0:0:0): 0 waiting Jan 30 21:20:17 enterprise kernel: DevQ(0:1:0): 0 waiting Jan 30 21:20:17 enterprise kernel: DevQ(0:2:0): 0 waiting Jan 30 21:20:17 enterprise kernel: DevQ(0:3:0): 0 waiting Jan 30 21:20:17 enterprise kernel: DevQ(0:4:0): 0 waiting Jan 30 21:20:17 enterprise kernel: Jan 30 21:20:17 enterprise kernel: <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Jan 30 21:20:17 enterprise kernel: scsi0:0:3:0: Device is active, asserting ATN Jan 30 21:20:17 enterprise kernel: Recovery code sleeping Jan 30 21:20:17 enterprise kernel: (scsi0:A:3:0): Abort Message Sent Jan 30 21:20:17 enterprise kernel: (scsi0:A:3:0): SCB 14 - Abort Completed. Jan 30 21:20:17 enterprise kernel: Recovery SCB completes Jan 30 21:20:17 enterprise kernel: Recovery code awake Jan 30 21:20:17 enterprise kernel: aic7xxx_abort returns 0x2002

6 7

remote install
by Chris Herrnberger 04 Feb '04

04 Feb '04

Greetings: Just for fun was wondering how other would address this situation. Confronted with a server that is remote and is loaded with a foreign distro..:), and provided only with an ssh account, is there a safe way to load SuSE instead and ensure a successfull install, as the possibility for human and local intervention is not possible? Best and thanks /ch

4 4

"couldn't find the kernel version the module was compiled for"
by Curtis Rey 04 Feb '04

04 Feb '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI all. Having fits dealing with those wonderful ATI drivers. I had installed 2.6 kernels and then later uninstalled and reinstalled the SuSE kernel with updates to 2.4.21-166-athlon version. I have run make cloneconfig, make dep, and complete and successful recompiles, yadda yadda... Everytime now, when I try to install the fglrx V-3.7.0, following the instructions (actually couple of variations - but still essentially the same) it get the following message from "modprove -vv fglrx": /sbin/insmod /lib/modules/2.4.21-166-athlon/kernel/drivers/char/drm/fglrx.o Using /lib/modules/2.4.21-166-athlon/kernel/drivers/char/drm/fglrx.o Symbol version prefix '' /lib/modules/2.4.21-166-athlon/kernel/drivers/char/drm/fglrx.o: couldn't find the kernel version the module was compiled for /lib/modules/2.4.21-166-athlon/kernel/drivers/char/drm/fglrx.o: insmod /lib/modules/2.4.21-166-athlon/kernel/drivers/char/drm/fglrx.o failed /lib/modules/2.4.21-166-athlon/kernel/drivers/char/drm/fglrx.o: insmod fglrx failed Anyone experience anything similar? I would be very greatful for any tips or insights. TIA Curtis. - -- Spammers Beware: Tresspassers will be shot, survivors will be shot again! Warning: Individuals throwing objects at the crocodiles will be asked to retrieve them! If pro is the opposite of con, then the opposite of progress must be congress! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAGfK9N9r/ngHXpykRAsYFAKCmGntG6qoP4OUISGPQUf4xgrCFywCcDh/Q CQj7HWxkdQnUeEzjppADE+4= =Bb9Y -----END PGP SIGNATURE-----

2 1

Shutdown Problem --Post Update
by C Hamel 04 Feb '04

04 Feb '04

Before using 'YOU' I was able to touch the off switch & I'd auto-logoff KDE and the box would shut down. Post 'YOU' touching the off switch auto-logs off KDE and brings me to the using login prompt, instead; then, when I choose 'shutdown' I am prompted for the root PW before the box will shut down. Why would this be?? I have checked the settings within KDE & the 'powermanagement' file and they seem to be unchagned. Anyone else had this problem, or did I unknowingly change something else that caused this? Thanks... ...CH

2 1

GRUB Error 15 on installation
by bab13510＠comcast.net 04 Feb '04

04 Feb '04

Hi all, (I apologize for clogging your inboxes if this message is not kosher for this list. If you know a better place I can ask it, I'd really appreciate if you let me know....) I am trying to install SuSE 9 and am running into a peculiar problem with GRUB. I am a newbie when it comes to Linux installations-- I've only installed SuSE once (on the same machine - I'll sum up the changes below), and had no problems whatsoever. Perhaps you can clear this one up for me... I run the installation off CD. After the first CD is done copying, SuSE writes some stuff, among them the bootloader. As it is writing the bootloader, it throws an error box with the following: (I have to type this into another machine from the error screen, so I replace some boilerplate with ".......") --- Error message detail GRUB version 0.93 (640K lower / 3072 upper memory) [Minimal BASH-like editing ...... device/filename] grub> root (hd0,1) Filesystem type is reiserfs, partition type 0x83 grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd0,1)/grub/menu.lst Error 15: File not found grub> quit --- end My GRUB config files are as follows: --- /boot/grub/device.map (hd0) /dev/hda --- end --- /boot/grub/menu.lst color .... default 0 timeout 8 gfxmenu (hd0,1)/message title Linux kernel (hd0,1)/vmlinuz root=/dev/hda5 vga=0x31a splash=verbose acpi=force desktop hdc=ide-scsi hdclun=0 showopts initrd (hd0,1)/initrd title Windows root (hd0,0) chainloader +1 title Failsafe kernel (hd0,1)/vmlinuz root=/dev/hda5 showopts ide=nodma apm=off acpi=off vga=normal nosmp noapic maxcpus=0 3 initrd (hd0,1)/initrd --- end --- /boot/grub/grub.conf root (hd0,1) install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd0,1)/grub/menu.lst quit --- end My partition configuration is as follows: hda1 - NTFS (Win2k) 25GB, mounted to /windows/C hda2 - reiser 100M mounted to /boot hda3 - swap hda4 - extended partition covering the rest of the disk hda5 - reiser 25GB mounted to / I'm running 500Mhz P3 on Chaintech 6BTM mobo with 512 MB RAM. There's one HD in the system: 120 GB Seagate Barracuda ST3120026A. Last time I installed SuSE, it was on the same machine, except the HD was Maxtor DiamondMax Plus L01J100 and the size of Win2k partition (hda1) was 15 GB instead of 25. It installed perfectly. I'd really appreciate any help. Thanks in advance. Boulat Bash bab13510(a)comcast.net

3 2

Comcast and NAT
by Damon Register 04 Feb '04

04 Feb '04

In another post I commented that I had trouble yesterday with what seems to be Comcast blocking ports 21 and 80 so I couldn't serve ftp or http. I mentioned this to my brother who said he remembers reading somewhere that Comcast is "going after people running NAT" but he didn't remember any more. Has anyone else heard this? How would NAT be detected with SuSEfirewall2 on 9.0? Damon Register

15 57

Re: [SLE] KInternet - How can I stay connected? - SOLVED
by Michael Yartsev 04 Feb '04

04 Feb '04

Ok I solved the problem, it was quiet simple actually. I went to yast2, and then to configure DSL connection (the one you should have gone through when you were setting up your system). Then go through the configuration you have there and make sure you have "On Boot" selected and the Idle time set to zero. Save changes, exit KInternet and when it asks you wether you want it to start next time say NO. Restart your computer and you should have a permanent internet connection without ever worring about KInternet again Hope it helps =) On Saturday 31 January 2004 1:34 pm, Tom Reagan wrote: > Mike, > I have the same goal. Please let me know what you find out! > > Thanks, > Tom > > Michael Yartsev <anijap(a)execulink.com> wrote: > I have a DSL connection which works fine. > > My question is, how can I make the connection stay alive even when I log > out/ in to my account? (or another account e.g root) > > And will the connection stay alive even when no user is logged into my > machine? (@ the login screen). > > I also want to disable the timeout option when no internet activity has > been detected for a while, where can I disable that? > > Why am I asking? I want to set up an apache web server and I want it to be > up all the time even when no one's using the computer > > It doesn't have to be KInternet anything else is welcome as long as it gets > the job done. > > Cheers, > Mike

6 11

Weird output /var/log/messages
by C Hamel 03 Feb '04

03 Feb '04

Suddenly I am getting output I do not understand from the kernel. It is happening while I am online (firewall running, or not) and I am wondering if anyone may be able to tell me what this means! Jan 28 20:40:35 HP-YOGI kernel: martian source 204.250.144.60 from 204.250.144.60, on dev ppp0 Jan 28 20:40:35 HP-YOGI kernel: ll header: 45:00:00:39 Jan 28 20:40:45 HP-YOGI kernel: martian source 204.250.144.60 from 204.250.144.60, on dev ppp0 Jan 28 20:40:45 HP-YOGI kernel: ll header: 45:00:00:39 Jan 28 20:40:55 HP-YOGI kernel: martian source 204.250.144.60 from 204.250.144.60, on dev ppp0 Jan 28 20:40:55 HP-YOGI kernel: ll header: 45:00:00:39 Then, occasionally, a message is generated stating 'count too high, resetting' and the errors continue. This all started about a day ago. ...CH

2 1

Re: [SLE] Hotplug Device (wlan question)
by GarUlbricht7＠netscape.net 03 Feb '04

03 Feb '04

GarUlbricht7(a)netscape.net wrote: > >Andrea <linux(a)andac.it> wrote: > >> I need to change name because as I wrote in the past with Yast DSL >> module isn't possible setup an Internet connection with hotplug device >> (wlanX) ... so I want to make it using 'ethX' and then replace it into >> 'ifcfg-dsl'. This is the only right way that I found with any other >> distribution (that in any case named wireless device ethX !!!) >> >> If you can advice me ... >> >>Thanks. >>Andrea >> > >Hi Andrea, >> >It has to be frustrating. >You haven't really gotten answers to your questions. > >I think part of the problem is Your Subject; > > "Hotplug Device" > >Most hotplug devices are things like cameras and memory sticks, >whereas you have a WLAN - "namely a local area network >that uses high frequency radio signals to transmit and receive data >over distances of a few hundred feet; >and your wlan uses ethernet protocol." > >Am I right ??? > >Now, somehow you want to connect this "wlan" >to the world using over DSL (Digital Subscriber Line) >and you want to configure this using the yast gui, >the problem being that YaST hasn't caught up to wlans >yet and all you can find is "ifcfg-dsl" > >Am I right so far ??? > Andrea, I replying to my own mail-- I snipped off part, which you may want to read... However, it dawned on me, the YaST gui doesn't have "everything".. it only has the things which are installed on the machine...and you may not have installed al the rpms you need to yet. So my question to you is do you have: etherboot-5.0.7-17.i586.rpm km_pcmci-3.2.0-59.i586.rpm km_pcmci-3.2.0-59.i586.rpm and similar rpms installed ??? These rpms are from the SuSE 8.1 CD and they may not apply in your situation. However, how I found them was doing: "pin wlan" If you don't have "pin" installed, I would suggest installing it now. There was just a Security Update on pin. It can be found at: http://www.suse.co.uk/uk/private/download/updates/90_i386.html for SuSE 9.0 and http://www.suse.co.uk/uk/private/download/updates/82_i386.html for SuSE 8.2 (ifyou are running 8.1 or 8.0, it's there just change the 82_i386 to 81_i386... you got it) Once pin is installed do "pin wlan" Hope this helps, Gar -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. --- Lazarus Long -- __________________________________________________________________ New! Unlimited Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Act now to get a personalized email address! Netscape. Just the Net You Need.

2 1