April 2004 - openSUSE Users - openSUSE Mailing Lists

Re: [SLE] Time synch problem
by Carlos E. R. 23 Feb '05

23 Feb '05

El 2003-07-09 a las 13:37, C Hamel escribió: (You forgot to post to the list) > I am afraid I don't even know how to ask a question, at this point, but I'll > make an attempt: Exactly where should this ntp thing be called to set the > clock ...or(/and) by what process? It is a very proper question :-) Well, it depends. There are two ways. If your computer is up all the time, and has a permanent network connection, you can use the ntpd daemon, which polls a set of servers about once a minute, and _very_ slowly adjusts the system clock; it can even note the systematic error or drift, and take that in to account to discipline the system clock. There are many options available for the daemon: see full doc in: http://localhost/usr/share/doc/packages/xntp-doc/html/index.htm Or, you may have a temporary network connection, like I do; I will explain this in some detail. We can adjust the clock to "internet" time, once, sometime after we connect to internet. This, apparently, can be done with the daemon, using some option I don't fully understand. Or we can use ntpdate - a program which is to disappear some time in the future, but that I use, and SuSE uses as well in its own script. For this, we can simply call "/etc/init.d/xntpd ntptimeset" - and assume that when "ntpdate" finally disappears SuSE will adjust the script appropriately ;-) Of course, /etc/ntp.conf has to be configured; at least, it must have a list of servers: server IP_address server name_address This is sufficient for "xntpd ntptimeset" to work; just leave the rest of the config at the default values. If you want to use the daemon, then I'm not the person to ask :-) Ok, so when is the appropriate time to make this time adjust? Well, ideally, during system boot-up, after network connection is established. This is done properly by the service xntpd, if enabled. The SuSE script "/etc/init.d/xntpd start" does first a clock set using ntpdate, if the variable XNTPD_INITIAL_NTPDATE is set to "AUTO". Then, it starts the daemon to keep time synchronized. And, if our network connection is not permanent? Then, the script "/etc/ppp/poll.tcpip", which is called from "/etc/ppp/ip-up", will adjust the clock first thing: assuming we have some servers configured, it will be done every time we connect to internet with the modem. I do it differently, only once every five times, and I also update the hwclock. The danger of this method is that the clock might suddenly go forward or backward a bit (seconds or hours, it depends): not very nice on a *nix system, but we can not avoid it. More details to be aware of: what happens to the hardware or CMOS clock? Well, the script "/etc/init.d/boot.clock" (read it, it is documented) does this sequence of things (using the command "hwclock") before starting system services: - Create if it doesn't exist, the file "/etc/adjtime" - Adjust hardware clock (CMOS) for known drift during the time the computer has been off; this depends on the previous file to work. - Copy CMOS clock (hardware) to system time (CPU and OS maintained). After this, the system goes fully up, and maybe, the clock is adjusted from the internet or by hand (danger!). But (and this is very different than windows) the CPU maintained clock has to be copied back to the CMOS, because the kernel doesn't do it. SuSE does it in the script "/etc/init.d/halt" that copies system time to hardware time just before power off. Me, I prefer to do it just after I adjust to network time, inside "ip-up.local", like this: /usr/sbin/rcxntpd ntptimeset /sbin/hwclock --systohc More things to be aware of: a common mistake is manually adjusting the system clock from kde control center (for example), and not updating the hwclock at the same time: the drift adjust algorithm of hwclock thinks that the CMOS clock is fast or slow by the same amount you adjusted the clock, and the next boot it will adjust the time by several hours... The solution is to delete "/etc/adjtime" and call "/sbin/hwclock --systohc" just then (documented on the SuSE sdb). Well, this has been enough chatter on my part; let's hope I didn't make many mistakes :-) -- Saludos Carlos Robinson

3 7

How to add secondary IP address to a SuSE box?
by joe_pr＠myrealbox.com 16 Sep '04

16 Sep '04

Hello, I am converting one of our Domino servers fro NT4 to SuSE 8.2. Is there any way to add a secondary IP to the network card? I used to have such a setup for the current NT box and eve tried this config with Mandrake but thi sdoes not seem to be possible with YAST2. Any idea anybody? Thanks Josef Prusa

6 5

[SLE] LILO - files
by sander.van.vugt＠azlan.nl 06 Sep '04

06 Sep '04

Hi, I'dd like to know what the following files in the directory /boot are about. Can anyone give me a clue or point me to some documentation? - boot.b - chain.b - map - System.map-2.2.14 - chos.* Thanks in advance, Sander ********************************************************************** Disclaimer This email is confidential and intended solely for the use of the individual to whom it is adressed. Any views or opinions presented are solely those of the author and do do not necessarily represent those of the Azlan Holdings bv and/or subsidairy. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited If you have received this email in error please notify Azlan Holdings MIS Helpdesk by telephone on +31 (0) 79 3443200. ********************************************************************* -- 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

4 3

9.1 unuseably slow
by David Bottrill 02 Sep '04

02 Sep '04

We received a copy of 9.1 today at work and I have installed this on three machines with dissapointing results. The first machine was an IBM Thinkpad R40 with a Centino 1600 CPU. This machine worked fine and the performance was great. The second and third machines were unusable, KDE takes serveral minutes to start, attempting to start YAST for instance will take about a minute for the SU box to appear and then another minute for YAST to load. I get similar results for all applications I have tried, in all instances the system performs like a P100 with very little RAM. The machines that run slowly are both Athlon XP based machines, one being an Athlon XP 2400 with 1GB of DDR RAM on an ECS Elite motherboard. The second machine is an XP2000 with 512MB of PC3200 RAM on a PCChips motherboard. I have applied all the updates with no effect. Any ideas would be appreciated, I've had to switch back to 9.0 as the whole 9.1 experience is unuseable has anybody got any ideas? David -- David Bottrill Registered Linux user number 330730 www.bottrill.org Internet SIP Phone: 1-747-244-2699

6 8

Partition Magic vs. Linux partitioner
by Paul W. Abrahams 17 Aug '04

17 Aug '04

I have a hard drive that works perfectly well under Linux but Partition Magic thinks it's incorrectly formatted. I've heard that there's some disagreement between PowerQuest (the company that wrote PM) and the Linux world over what the correct format of a partition table is; each thinks the other has it wrong. Does anyone on this list know about the disagreement and the best way to get around it? (The SuSE database yields nothing.) Paul Abrahams

21 36

SUSE DOES NOT RECOGNIZE ANY USB DEVICES
by coreygl＠comcast.net 24 May '04

24 May '04

PRODUCT: SuSE Linux (I386) 8.2 > My system does not recognize any USB devices that are > connected to it. I have a USB mouse and an All-in-one > printer, an HP PSC 2175 model. I have already performed > many of the steps in Suse Support articles in an effort to > solve this issue. So far, I have had no success. > I receive the following > messages in /var/log/messages: > Apr 13 21:04:06 linux syslogd 1.4.1: restart. > Apr 13 21:04:07 linux /etc/hotplug/usb.rc[1141]: loaded HCD: ehci-hcd > Apr 13 21:04:08 linux /etc/hotplug/usb.rc[1141]: loaded HCD: usb-ohci > Apr 13 21:04:08 linux /etc/hotplug/usb.rc[1141]: loaded HCD: ehci-hcd > Apr 13 21:04:11 linux kernel: klogd 1.4.1, log source = /proc/kmsg started. > Apr 13 21:04:11 linux kernel: Inspecting /boot/System.map-2.4.20-4GB-athlon > Apr 13 21:04:11 linux kernel: Loaded 20865 symbols from /boot/System.map-2.4.20-4GB-athlon. > Apr 13 21:04:11 linux kernel: Symbols match kernel version 2.4.20. > Apr 13 21:04:11 linux kernel: Loaded 560 symbols from 24 modules. > Apr 13 21:04:11 linux kernel: PCI: Setting latency timer of device 00:06.0 to 64 > Apr 13 21:04:11 linux kernel: intel8x0: clocking to 47377 > Apr 13 21:04:11 linux kernel: Got silent jpeg. > Apr 13 21:04:11 linux kernel: Got silent jpeg. > Apr 13 21:04:11 linux kernel: Linux Tulip driver version 0.9.15-pre12 (Nov 11, 2002) > Apr 13 21:04:11 linux kernel: eth0: ADMtek Comet rev 17 at 0xa000, 00:04:5A:87:BC:F9, IRQ 5. > Apr 13 21:04:11 linux kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html > Apr 13 21:04:11 linux kernel: See Documentation/networking/vortex.txt > Apr 13 21:04:11 linux kernel: 03:01.0: 3Com PCI 3c920 Tornado at 0xc000. Vers LK1.1.16 > Apr 13 21:04:11 linux kernel: 00:26:54:0b:f2:52, IRQ 11 > Apr 13 21:04:11 linux kernel: product code ffff rev 00.0 date 15-31-127 > Apr 13 21:04:11 linux kernel: Internal config register is 1600000, transceivers 0x40. > Apr 13 21:04:11 linux kernel: 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/MII interface. > Apr 13 21:04:11 linux kernel: MII transceiver found at address 2, status 7849. > Apr 13 21:04:11 linux kernel: Enabling bus-master transmits and whole-frame receives. > Apr 13 21:04:11 linux kernel: 03:01.0: scatter/gather enabled. h/w checksums enabled > Apr 13 21:04:11 linux kernel: ohci1394: $Rev: 758 $ Ben Collins <bcollins(a)debian.org> > Apr 13 21:04:11 linux kernel: PCI: Setting latency timer of device 00:0d.0 to 64 > Apr 13 21:04:11 linux kernel: ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[5] MMIO=[e9086000-e90867ff] Max Packet=[2048] > Apr 13 21:04:11 linux kernel: raw1394: /dev/raw1394 device initialized > Apr 13 21:04:11 linux kernel: usb-uhci.c: $Revision: 1.275 $ time 16:04:20 Mar 12 2004 > Apr 13 21:04:11 linux kernel: usb-uhci.c: High bandwidth mode enabled > Apr 13 21:04:11 linux kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver > Apr 13 21:04:11 linux kernel: uhci.c: USB Universal Host Controller Interface driver v1.1 > Apr 13 21:04:11 linux kernel: PCI: Setting latency timer of device 00:02.0 to 64 > Apr 13 21:04:11 linux kernel: usb-ohci.c: USB OHCI at membase 0xe48da000, IRQ 11 > Apr 13 21:04:11 linux kernel: usb-ohci.c: usb-00:02.0, PCI device 10de:0067 (nVidia Corporation) > Apr 13 21:04:11 linux kernel: usb.c: new USB bus registered, assigned bus number 2 > Apr 13 21:04:11 linux kernel: hub.c: USB hub found > Apr 13 21:04:11 linux kernel: hub.c: 3 ports detected > Apr 13 21:04:11 linux kernel: PCI: Setting latency timer of device 00:02.1 to 64 > Apr 13 21:04:11 linux kernel: usb-ohci.c: USB OHCI at membase 0xe48dc000, IRQ 10 > Apr 13 21:04:11 linux kernel: usb-ohci.c: usb-00:02.1, PCI device 10de:0067 (nVidia Corporation) > Apr 13 21:04:11 linux kernel: usb.c: new USB bus registered, assigned bus number 3 > Apr 13 21:04:11 linux kernel: hub.c: USB hub found > Apr 13 21:04:11 linux kernel: hub.c: 3 ports detected > Apr 13 21:04:11 linux kernel: hub.c: new USB device 00:02.1-1, assigned address 2 > Apr 13 21:04:12 linux kernel: Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0 > Apr 13 21:04:12 linux kernel: sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray > Apr 13 21:04:12 linux kernel: Uniform CD-ROM driver Revision: 3.12 > Apr 13 21:04:13 linux kernel: usb_control/bulk_msg: timeout > Apr 13 21:04:13 linux kernel: usb-ohci.c: unlink URB timeout > Apr 13 21:04:13 linux kernel: usb.c: USB device not accepting new address=2 (error=-110) > Apr 13 21:04:13 linux kernel: hub.c: new USB device 00:02.1-1, assigned address 3 > Apr 13 21:04:18 linux kernel: usb_control/bulk_msg: timeout > Apr 13 21:04:18 linux kernel: usb-ohci.c: unlink URB timeout > Apr 13 21:04:18 linux kernel: usb.c: USB device not accepting new address=3 (error=-110) > Apr 13 21:04:19 linux kernel: mice: PS/2 mouse device common for all mice > Apr 13 21:04:25 linux kernel: spurious 8259A interrupt: IRQ7. > Apr 13 21:04:26 linux kernel: isapnp: Scanning for PnP cards... > Apr 13 21:04:26 linux kernel: isapnp: No Plug & Play device found > Apr 13 21:04:29 linux kernel: IPv6 v0.8 for NET4.0 > Apr 13 21:04:29 linux kernel: IPv6 over IPv4 tunneling driver > Apr 13 21:04:29 linux sshd[1677]: Server listening on :: port 22. > Apr 13 21:04:31 linux /usr/sbin/cron[1893]: (CRON) STARTUP (fork ok) > Apr 13 21:04:34 linux kernel: Linux video capture interface: v1.00 > Apr 13 21:04:37 linux /etc/hotplug/net.agent[1714]: No HW description found ... exiting > Apr 13 21:04:39 linux kernel: parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] > Apr 13 21:04:39 linux kernel: parport0: irq 7 detected > Apr 13 21:04:39 linux kernel: lp0: using parport0 (polling). > Apr 13 21:04:39 linux kernel: usb.c: registered new driver serial > Apr 13 21:04:39 linux kernel: usbserial.c: USB Serial support registered for Generic > Apr 13 21:04:39 linux kernel: usbserial.c: USB Serial Driver core v1.4 > Apr 13 21:05:04 linux kdm[1945]: pam_unix2: session started for user root, service xdm > Apr 13 21:05:04 linux resmgr[1548]: accepted connection from user root > Apr 13 21:05:04 linux resmgr[1548]: disconnect from root > > The 'timeout' messages seem to be the issue. As mentioned > before, I have performed the steps in Suse Support articles > to try to address the issue. > > Thanks in advance, > Corey >

7 17

DVD playback...
by Matthew 14 May '04

14 May '04

Good day, Yes there are legal reasons why SuSE cannot have DVD playback of those pesky movies, but what be done? Would it be too expensive for Novell/SuSE to license a codec? Seems like there is a new copyright law in Germany that has made PackMan be more cautious. No one has made a player for Linux that is 100% legal, is it due to expense? Matt

2 1

Still cant connect to my ISP
by Keith Keesing 09 May '04

09 May '04

I seem to have trouble getting recognised by my ISP Can anyone point out to an ignorant novice what is going on here, and how to fix it. How do I inform myself about "signal 15" & "exit code 19" etc Where does the "[09]" in the "EARLY LOG" come from ? I have installed 8.2 personal - I haven't come across any other problems yet ##### EARLY LOG ################################### SuSE Meta pppd (smpppd-ifcfg), Version 1.00 on linux. We are disconnected. trying to connect to smpppd connect to smpppd We are disconnected. We are connecting. pppd: Plugin passwordfd.so loaded. pppd: --> WvDial: Internet dialer version 1.42 pppd: --> Initializing modem. pppd: --> Sending: ATZ pppd: ATZ pppd: OK pppd: --> Sending: AT&C1&D2 pppd: AT&C1&D2 pppd: OK pppd: --> Sending: ATM1 pppd: ATM1 pppd: OK pppd: --> Modem initialized. pppd: --> Sending: ATDT086707070 pppd: --> Waiting for carrier. pppd: ATDT086707070 pppd: CONNECT 115200 pppd: --> Carrier detected. Waiting for prompt. pppd: [09] pppd: login: pppd: --> Looks like a login prompt. pppd: --> Sending: kkeith pppd: kkeith pppd: Password: pppd: --> Looks like a password prompt. pppd: --> Sending: (password) pppd: --> Don't know what to do! Starting pppd and hoping for the best. pppd: Serial connection established. pppd: Using interface ppp0 pppd: Connect: ppp0 <--> /dev/ttyS0 We are disconnecting. pppd: Terminating on signal 15. We are disconnecting. We are disconnected. pppd died: non-normal exit ###### LATER LOG ################################## (I went back to set-up and enabled "stupid Mode") SuSE Meta pppd (smpppd-ifcfg), Version 1.00 on linux. We are disconnected. trying to connect to smpppd connect to smpppd We are disconnected. We are connecting. pppd: Plugin passwordfd.so loaded. pppd: --> WvDial: Internet dialer version 1.42 pppd: --> Initializing modem. pppd: --> Sending: ATZ pppd: ATZ pppd: OK pppd: --> Sending: AT&C1&D2 pppd: AT&C1&D2 pppd: OK pppd: --> Sending: ATM1 pppd: ATM1 pppd: OK pppd: --> Modem initialized. pppd: --> Sending: ATDT086707070 pppd: --> Waiting for carrier. pppd: ATDT086707070 pppd: CONNECT 115200 pppd: --> Carrier detected. Chatmode finished. pppd: Serial connection established. pppd: Using interface ppp0 pppd: Connect: ppp0 <--> /dev/ttyS0 pppd: No response to PAP authenticate-requests pppd: Connection terminated. pppd: Hangup (SIGHUP) We are disconnected. pppd died: Authentication error (exit code 19) Thanks keith

8 21

No mouse pointer after SuSE 9.0 Pro install.
by John N. Alegre 05 May '04

05 May '04

After an install of 9.0 Pro there is no Mouse Pointer. The configuration of the mouse in XF86config is "auto". It is a three button mouse. The mouse worked fine with pointer during the entire install process. The mouse works. I can select things fine with standard mouse clicks and double clicks. I just can NOT see the pointer. Can anybody help??? I am new to SuSE not to Linux (since Red Hat 5.2). I am very happy about the SuSE product. It is a superior distribution. Can anyone help me with the mouse problem or point me to the correct data. As I said above the mouse IS working there is just no visible pointer. john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------

1 1

SuSE indoctrination too early?
by Damon Register 05 May '04

05 May '04

Am I indoctrinating my 3 year old son too early? Now when I come home he says "I want SuSE Linux" so he can play music with XMMS. Maybe I should get more games setup too? If Gates can do it by "giving" all that software to schools, why can't I beat him to it at home? Damon Register

26 41