May 2005 - openSUSE Users - openSUSE Mailing Lists

Dial in server with SLES9
by Chadley Wilson 03 May '05

03 May '05

Greetings, I would just like to know, is there a yast2 module for configuring a dialin server for SLES9, or must this be done backend, I can never get it working back end, and when ever I try webmin, it trashes my entire network and I have to reload again. I also don't know how to modify SuseFirewall2, to route traffic from ppp0 to my ftp site on the same PC. I have read read much on mgetty but am still not comfortable with it as it never works in the ISP fashion that I would like it to. -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================

1 0

postgresql
by David Bear 03 May '05

03 May '05

I have noted that when using the 9.2 install CD that postgresql is not listed as an installable option. It is not listed in yast as a package. Yet, using the 9.2 DVD it is. Why the difference? As a second questions, 9.2 still seems to be distributing postgresql 7.4. The postgres group has released version 8. Would I be better off grabbing the rpm for version 8? -- David Bear phone: 480-965-8257 fax: 480-965-9189 College of Public Programs/ASU Wilson Hall 232 Tempe, AZ 85287-0803 "Beware the IP portfolio, everyone will be suspect of trespassing"

4 6

Virus, Worm on Linux or what is it?
by Martin Deppe 03 May '05

03 May '05

This is the Postfix program at host linux.local. I'm sorry to have to inform you that the message returned below could not be delivered to one or more destinations. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the message returned below. The Postfix program <gbrown(a)localhost.linux.local>: host localhost[127.0.0.1] said: 451 4.5.0 Error in processing, id=02097-05, virus_scan FAILED: NO VIRUS SCANNERS AVAILABLE (in reply to end of DATA command) -------------------------------------------------------------------------------- Reporting-MTA: dns; linux.local Arrival-Date: Sun, 24 Apr 2005 14:24:45 -0600 (MDT) Final-Recipient: rfc822; gbrown(a)localhost.linux.local Action: failed Status: 4.0.0 Diagnostic-Code: X-Postfix; host localhost[127.0.0.1] said: 451 4.5.0 Error in processing, id=02097-05, virus_scan FAILED: NO VIRUS SCANNERS AVAILABLE (in reply to end of DATA command) -------------------------------------------------------------------------------- Subject: Re: [SLE] Please help: SuSE 9.1 lockups during high CPU/disk activity From: Martin Deppe <Martin.Deppe(a)web.de> Date: Sat, 23 Apr 2005 00:58:50 +0200 To: "SuSE Linux E..." <suse-linux-e(a)suse.com> Pieter Hulshoff wrote: > On Saturday 23 April 2005 00:16, Martin Deppe wrote: > > >> Maybe it is a combination of the heat problem and a too low voltage >> problem which only leads to the lock up if the temperature raises above >> a certain point so that the voltage goes even further down to the point >> that it finally causes the lock. >> > > > I think it's mostly heat. I've currently got the door open, it's > freezing in here, and my computer's rock stabily ripping a DVD to avi. > CPU temperature is at 48C right now. If a Tagan 480W PSU (and one with > very good reviews I might add) isn't capable of handling a 2 year old > system, Athlon XP2000+ with radeon 9000 AIW card, then there's a > serious problem I think. > > > >> I don't actually know whether you can use two or more PSU in one and the >> same box (I still have to check that for myself), but if this is >> possible it might be part of the solution beside the point to get the >> air better circulating inside your box for better cooling >> characteristics. >> > > > Using two or more PSUs is not a good thing. The voltages of those two > PSUs will never be exactly the same, so you get internal power leakage > (don't know the exact term for it in English I'm afraid). I wouldn't > recommend it. As said though: a good 480W PSU should be more than > enough for a system like mine. > > Regards, > > Pieter > I meant to use another PSU with the additional drives. Since they are connected only through the datacables it doesn't really matter that the voltages aren't exactly the same (I think). I think I will try it (or at least research on that) myself some time. I have a system with two CPU's which are 76°C to 77°C "warm" (always), if I can trust gkrellm and actually the BIOS too. So 48°C shouldn't be a problem at your side (I guess). However, I need to sleep now! Good luck Martin -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

3 5

9.3. install from HD
by Jul 03 May '05

03 May '05

Well, I 'm with SuSE since 5.0 currently 9.0. I just downloaded 9.3 last night and try install from HD using boot CD. Well it has a loop and it is no possible to get into installation from HD. Jul.

4 5

easing migration & administration
by Maccy 03 May '05

03 May '05

Hi guys, I've recently acquired a small network of 2 servers (1 serving home areas, the other serving RAID data space to users) and 50 desktop machines running Redhat 7.3 and have been given a remit to move to SuSE 9.3. I want to reduce single points of failure.....and implement a gradual move away from Redhat. How would I go about setting up each machine exactly the same, and then periodically apply updates to software and local config, without visiting each system in person? Would you install software on the server and NFS mount it to all hosts, or somehow update each system individually? What would be the best setup, in your opinions, and how do you have things set up at your places of work? Maccy

1 0

Interesting review of SuSE 9.3
by Basil Chupin 03 May '05

03 May '05

An interesting article about v9.3 to be found at www.theinquirer.net. The article is titled, "SuSE 9.3 fails home-use test". Cheers. -- Understanding only begins with the act of perception.

41 109

Sound, USB lost in 9.3" - HAL, D-BUS related?
by AD Marshall 03 May '05

03 May '05

Here's my second massive message on this subject. Feel free to tell me to work on it more or to get more specific. That's what i'm still trying to do. Herein, i'm just hoping for some quick direction. Is there some way I can tweak the following three files to get my USB Flash drive and sound card working? Or, given the logextracts and other info below, is there something else I should do, if only to get more specific info? Grateful for any help... AD Marshall The 3 files I'm hoping can do the trick: # From /etc/sysconfig/hardware/hwcfg-vpid-8086-7111 :: # If you change things manually here and want this configuration # to persist updates, then remove the following line. # HOTPLUG-FLAG: autocreated STARTMODE='auto' MODULE_0='piix' MODULE_OPTIONS_0='' # From /etc/sysconfig/hardware/hwcfg-vpid-8086-7112 :: # HOTPLUG-FLAG: autocreated STARTMODE='auto' MODULE_0='uhci-hcd' MODULE_OPTIONS_0='' # From /etc/sysconfig/hardware/hwcfg-vpid-8086-7113 :: # HOTPLUG-FLAG: autocreated STARTMODE='auto' MODULE_0='i2c-piix4' MODULE_OPTIONS_0='' # From /etc/modprobe.conf # ======================= install ata_piix /sbin/modprobe ahci; /sbin/modprobe --ignore-install ata_piix # Some HAL & USB related extracts from /var/log/messages, possibly related to this: # ================================================================================ Apr 29 18:03:34 tpad01 kernel: piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device Apr 29 18:03:34 tpad01 kernel: piix4_smbus 0000:00:07.3: IBM Laptop detected; this module may corrupt your serial eeprom! R efusing to load module! Apr 29 18:03:34 tpad01 kernel: piix4_smbus: probe of 0000:00:07.3 failed with error -1 # Note: Inserted CD Apr 29 18:30:34 tpad01 kernel: subfs 0.9 Apr 29 18:30:34 tpad01 hal-subfs-mount[7420]: registered at resmgrd and called(0) /bin/mount -t subfs -o fs=cdfss,ro,procuid,nosuid,nodev,exec /dev/hdc "/media/FORGE80" Apr 29 18:30:36 tpad01 hal.hotplug[7432]: DEVPATH is not set Apr 29 18:30:38 tpad01 hal.hotplug[7435]: DEVPATH is not set Apr 29 18:31:37 tpad01 hal.hotplug[7459]: DEVPATH is not set Apr 29 18:31:40 tpad01 hal.hotplug[7465]: DEVPATH is not set # Note: Inserted Kingston DataTraveller USB stick Apr 29 18:31:52 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 2 Apr 29 18:31:53 tpad01 kernel: uhci_hcd 0000:00:07.2: Unlink after no-IRQ? Controller is probably using the wrong IRQ. Apr 29 18:31:56 tpad01 kernel: usb 1-1: device descriptor read/64, error -110 Apr 29 18:32:12 tpad01 kernel: usb 1-1: device not accepting address 2, error -110 Apr 29 18:32:12 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 3 Apr 29 18:32:24 tpad01 kernel: usb 1-1: device not accepting address 3, error -110 Apr 29 18:32:24 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 4 Apr 29 18:32:34 tpad01 kernel: usb 1-1: device not accepting address 4, error -110 Apr 29 18:32:34 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 5 Apr 29 18:32:45 tpad01 kernel: usb 1-1: device not accepting address 5, error -110 Apr 29 18:41:20 tpad01 su: (to root) am on /dev/pts/5 Apr 29 19:03:25 tpad01 syslog-ng[3309]: STATS: dropped 0 Apr 29 20:25:46 tpad01 su: (to root) am on /dev/pts/2 Apr 29 20:25:46 tpad01 syslog-ng[3309]: STATS: dropped 0 # Note: modprobe ata_piix # Note: ReInserted Kingston DataTraveller USB stick Apr 29 21:24:43 tpad01 kernel: libata version 1.10 loaded. Apr 29 21:25:46 tpad01 syslog-ng[3309]: STATS: dropped 0 Apr 29 21:26:01 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 6 Apr 29 21:26:04 tpad01 kernel: usb 1-1: device descriptor read/64, error -110 Apr 29 21:26:20 tpad01 kernel: usb 1-1: device not accepting address 6, error -110 Apr 29 21:26:20 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 7 Apr 29 21:26:32 tpad01 kernel: usb 1-1: device not accepting address 7, error -110 Apr 29 21:26:32 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 8 Apr 29 21:26:43 tpad01 kernel: usb 1-1: device not accepting address 8, error -110 Apr 29 21:26:43 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 9 Apr 29 21:26:54 tpad01 kernel: usb 1-1: device not accepting address 9, error -110 Apr 29 21:29:06 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 10 Apr 29 21:29:10 tpad01 kernel: usb 1-1: device descriptor read/64, error -110 Apr 29 21:29:26 tpad01 kernel: usb 1-1: device not accepting address 10, error -110 Apr 29 21:29:26 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 11 Apr 29 21:29:38 tpad01 kernel: usb 1-1: device not accepting address 11, error -110 Apr 29 21:29:38 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 12 Apr 29 21:29:48 tpad01 kernel: usb 1-1: device not accepting address 12, error -110 Apr 29 21:29:48 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 13 Apr 29 21:29:59 tpad01 kernel: usb 1-1: device not accepting address 13, error -110 # Note: ran :: # modprobe -r ata_piix # Note: ReInserted Kingston DataTraveller USB stick Apr 29 21:35:25 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 14 Apr 29 21:35:28 tpad01 kernel: usb 1-1: device descriptor read/64, error -110 Apr 29 21:35:44 tpad01 kernel: usb 1-1: device not accepting address 14, error -110 Apr 29 21:35:44 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 15 Apr 29 21:35:56 tpad01 kernel: usb 1-1: device not accepting address 15, error -110 Apr 29 21:35:56 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 16 Apr 29 21:36:06 tpad01 kernel: usb 1-1: device not accepting address 16, error -110 Apr 29 21:36:06 tpad01 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 17 Apr 29 21:36:17 tpad01 kernel: usb 1-1: device not accepting address 17, error -110 # Some sound-related extracts from /var/log/messages :: ======================================================= # Note: Tried to play an mp3 in alsaplayer Apr 29 23:32:38 tpad01 kernel: ALSA sound/core/pcm_lib.c:2113: playback write error (DMA or IRQ trouble?) Apr 29 23:32:48 tpad01 kernel: ALSA sound/core/pcm_lib.c:2113: playback write error (DMA or IRQ trouble?) Apr 29 23:32:58 tpad01 kernel: ALSA sound/core/pcm_lib.c:2113: playback write error (DMA or IRQ trouble?) <cut> Apr 29 23:34:48 tpad01 kernel: ALSA sound/core/pcm_lib.c:2113: playback write error (DMA or IRQ trouble?) Apr 29 23:34:58 tpad01 kernel: ALSA sound/core/pcm_native.c:1433: playback drain error (DMA or IRQ trouble?) # /proc/interrupts, :: ====================== CPU0 0: 26516950 XT-PIC timer 1: 19914 XT-PIC i8042 2: 0 XT-PIC cascade 3: 56 XT-PIC 1.0 7: 0 XT-PIC parport0 8: 2 XT-PIC rtc 9: 5766 XT-PIC acpi 10: 200001 XT-PIC yenta 11: 100000 XT-PIC yenta, uhci_hcd, CS46XX 12: 76415 XT-PIC i8042 14: 175790 XT-PIC ide0 15: 53271 XT-PIC ide1 NMI: 0 LOC: 0 ERR: 0 MIS: 0 # /proc/ioports :: ================== 1 0000-001f : dma1 2 0020-0021 : pic1 3 0022-0022 : PM2_CNT_BLK 4 0040-0043 : timer0 5 0050-0053 : timer1 6 0060-006f : keyboard 7 0070-0077 : rtc 8 0080-008f : dma page reg 9 00a0-00a1 : pic2 10 00c0-00df : dma2 11 00f0-00ff : fpu 12 0170-0177 : ide1 13 01f0-01f7 : ide0 14 02f8-02ff : serial 15 0300-031f : pcmcia_socket1 16 0376-0376 : ide1 17 03bc-03be : parport0 18 03c0-03df : vesafb 19 03f6-03f6 : ide0 20 03f8-03ff : serial 21 0cf8-0cff : PCI conf1 22 15e0-15ef : motherboard 23 15e0-15ef : pnp 00:07 24 4000-401f : 0000:00:07.2 25 4000-401f : uhci_hcd 26 4400-44ff : 0000:00:03.0 27 4500-4507 : 0000:00:03.0 28 4800-48ff : PCI CardBus #02 29 4c00-4cff : PCI CardBus #02 30 5000-50ff : PCI CardBus #06 31 5400-54ff : PCI CardBus #06 32 d000-dfff : PCI Bus #01 33 ef00-ef3f : 0000:00:07.3 34 ef00-ef3f : motherboard 35 ef00-ef03 : PM1a_EVT_BLK 36 ef04-ef05 : PM1a_CNT_BLK 37 ef08-ef0b : PM_TMR 38 ef0c-ef0f : GPE0_BLK 39 ef10-ef15 : ACPI CPU throttle 40 efa0-efbf : 0000:00:07.3 41 efa0-efaf : motherboard 42 efa0-efaf : pnp 00:07 43 fcf0-fcff : 0000:00:07.1 44 fcf0-fcf7 : ide0 45 fcf8-fcff : ide1 -- AD (Andi) Marshall admarshall(a)gmail.com

1 0

9.3 crappy
by Chris 02 May '05

02 May '05

I loaded 9.3 up and install went well. I did the on line update part except the Nvidia ones. Rebooted did the you thing for the Nvidia. Rebooted fine. Diddled with a few personal setting such as screen saver and wallpaper. Shutdown and later fired up twice. Then I went to fire up and could only get a grey/blue screen that asks for log on and gives a console only. Its an x screen and does not allow for further options without knowledge on how to use the console a lot more than I do. I reinstalled and the same story! Any one got a clue what it's doing. I have reinstalled 9.2 and no probs. The screen did show an error about the floppy ( I did not write it down). There wasn't a disk in the floppy! Chris

9 21

libroken and SuSE 9.3
by Moby 02 May '05

02 May '05

What rpm would provide libroken on SuSE 9.3? From what I can tell, it is provided by heimdal* RPMs. However, it looks like SuSE 9.3 uses krb5 RPMs instead of heimdal* RPMs for kerberos, and none of the krb5* RPMs appear to have libroken. Has anyone successfully compiled software requiring libroken.so on SuSE 9.3? Thanks in advance for any help, -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller

1 0

Cups job summary including job-originating-host-name
by Mark Andrews 02 May '05

02 May '05

I've configured a SLES server as a CUPS server, installing several printers and enabling it as an IPP server. Several of my client SuSE workstations have been configured as IPP clients. When a job is printed from a client system, it is dispatched to the print server via IPP and successfully printed. We wish to employ some sort of billing service by collecting the IPP record reports from each individual print job. A list of printed jobs is available using 'lpstat -W completed -u' on the client or server, but it doesn't include the 'job-originating-host-name' available from the kjobviewer gui and encoded in the binary files (/var/spool/cups/<job #>) on the print server. Has anyone written or know of a command which will print the name information as 'lpstat -W completed', but also include the hostname/IP-addr of the host which originated the print request, in text? Thanks

2 1