May 2005 - openSUSE AMD64 - openSUSE Mailing Lists

burning CDs
by Mike Roy 18 May '05

18 May '05

Hello everyone: I recently upgraded my system to SuSE 9.3 from 9.1 (AMD 64-bit). K3D (under SuSE 9.3) can burn a dual-layer DVD with no problem. But, I'm experiencing some problems when I try to create a music CD. All of the music files have been 'ripped' with GRIP and saved as *.ogg ( Ogg-Vorbis files ) I drag-n-drop to create the menu I want, name the CD and start to burn. Shortly afterwards I get the following error messages as the CD is ejected from the system: error while decoding audio tracks removing buffer files unlocking drive could not unlock CD drive at this point, the entire program just quits. I'm wondering if there might be some conflicts between the earlier and later flavors of k3b. I will be doing a full, clean install later and that might solve the problem. Any ideas? Cheers, Mike

1 0

RE: [suse-amd64] SuSE 9.3 Pro RAID /boot
by Black, Alain 18 May '05

18 May '05

Thanks Volker, I'll mirror /boot and stripe the rest. -----Original Message----- From: Volker Kuhlmann [mailto:hidden@paradise.net.nz] Sent: Tuesday, May 17, 2005 3:53 PM To: suse-amd64(a)suse.com Subject: Re: [suse-amd64] SuSE 9.3 Pro RAID /boot > I went to install 9.3 SuSE Pro last night. During the installation > phase I selected to RAID the two disks (SATA). ( I chose striping, not > mirroring, but the message was generic to RAID). > > A warning message appeared stating that the system may not be directly > bootable since I had elected to RAID /boot. Should I make a stand alone > partition for /boot, or will I be fine including it in the RAID > configuration? The problem is that the bootloader needs to know how to load the kernel image. With raid0 (and raid5), it would need to know how the actual file is striped across the two disks to locate the correct disk blocks to read. With raid1 it's simple: ignore the raid and pick either disk to load the file from. Unless the boot loader has somehow learned to undo the striping (dito for raid5), your system won't boot from a raided /boot. My question would be: how does one install a boot loader(s) on a raid0/raid5 system such that the system still boots + runs when removing any one disk? Does yast do this automagically... ? Btw nothing specific to amd64. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

1 0

Suspend to disk causes kernel OOPS when swap partition is on SATA drive
by ZhenLei Cai 18 May '05

18 May '05

I have an ASUS A8V with two SATA drives hooked to on board VIA Sata controller. The two drives (sda,sdb) are configured to form an ext2 (sda1 mounted as /boot), a swap (sdb1) and a RAID0 striped parition (sda2 and sdb2, mounted as root). I installed Suse Pro 9.3 with default kernel. When I do a suspend to disk ("powersave -U"), I got a Kernel oops. I don't think it's a hardware problem as I changed my SATA controller (Silicon Image and on-board Promise), changed power supply etc. and none worked. The strange thing is if I add a parallel ATA IDE drive and use a parition on that drive (hda1) as the SWAP then suspend works fine. To summarize, swsusp2 causes a kernel oops which happens only when the swap partition is on a SATA drive (I have sata_via module as the SATA driver). Have anyone seen this before? I may have to use a USB flash drive as the swap parition as using hda for swap is not an option for me. On the other hand I found suspend to RAM (powersave -u) will cause a complete freeze of machine when it's resumed and the first time the file system is accessed. ---------- begin Kernel oops message when suspend to disk ---- $ powersave -U stopping all tasks ... Writing data to swap (21475 pages), 0% ... <here the machines hangs for about 8 seconds before outputing the following oops stack, sorry I was not able to copy down all the oops messages> ,... <Stack trace 1>: {scsi_next_command+...} ... process events 10 (pid 3, threadinfo ffff810031c1e000 task ffff810003240720) <Stack trace 2>: ... {drain_array_locked + 118} <ffffffff8015b69c0> {cache_reap+106} <fff580142878> { worker_thread+424} ---------- end -----------------

2 1

SuSE 9.3 Pro RAID /boot
by Black, Alain 17 May '05

17 May '05

I went to install 9.3 SuSE Pro last night. During the installation phase I selected to RAID the two disks (SATA). ( I chose striping, not mirroring, but the message was generic to RAID). A warning message appeared stating that the system may not be directly bootable since I had elected to RAID /boot. Should I make a stand alone partition for /boot, or will I be fine including it in the RAID configuration? This is Linux based RAID, and not through any type of a controller card. -Alain.

2 1

Re: [suse-amd64] Problem with power switch on 9.3
by Michael Marion 17 May '05

17 May '05

On 17 May, Lew Wolfgang wrote: > I tried YaST's Power-Management screen, but no joy. It's > configured to "Power Off" instead of "Reboot", but just > hangs after the shutdown sequence. It even disables > the front-panel power switch (holding it in for more > than six-seconds doesn't turn the power off). I have > to reach behind and turn the actual power supply switch > off. Lew.. does running poweroff yourself work right? If not, add apm=smp-power-off to your grub (or lilo) config as a kernel option for the next boot.. there was (is?) an issue with smp and powering off like that which that option used to fix. Or maybe it's just apm=power-off now.. 9.2 might've added that before on it's own. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Beer recipe: free! ~= Source Cold pints: $2 ~= Product Safe rides home, any hour: $25 ~= Technical Support

1 0

Problem with power switch on 9.3
by Lewis Wolfgang 17 May '05

17 May '05

Hi Folks, On a Tyan 2875 with dual 246 Opterons I had 9.2 working so that a tap of the power button would issue a "halt" command and actually turn off the power. Alas, with 9.3 I get the "halt" behavior but the power isn't turned off. I rebooted with 9.2 and it works, back to 9.3 and it doesn't. I've configured everything I can find, but maybe I missed something? Other than this, so far 9.3 is a keeper in my book. Regards, Lew Wolfgang

3 2

PXE install on Fujitsu Siemens Scaleo T A64XP35
by Volkmar Glauche 17 May '05

17 May '05

Hi, I am trying to do a PXE install of SuSE Linux Professional on a Fujitsu Siemens Scaleo T A64XP35 box. However, it does seem to have problems initializing the network card after PXE. I have tried the following scenarios: 1) Boot from DVD with install=nfs://myserver/mydir. This works fine, the network card gets its IP over DHCP and starts the download. Yast detects the card as Asus CK804 (apparently using the forcedeth driver?). 2) Boot from the PXE PROM of the network card. This downloads the kernel (linux64 from the DVD) and initrd (initrd64 from DVD) and starts booting. The network card sends a DHCPDISCOVER 2 or 3 times, but does not answer the DHCPOFFER from the DHCP server. Thus it times out on mounting the installation source and I get into linuxrc. However, I did not have any luck to activate the network card manually, either. Any ideas? -- Volkmar Glauche - Department of Neurology volkmar.glauche(a)uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5310 79106 Freiburg

1 1

Sil 3114 and two disk
by zio budda 16 May '05

16 May '05

Hi, I have a Gygabite MotherBoard with Sil3114 Raid Chipset and 2 HD. Into the bios of Sil 3114 I have set one Raid0 so when I boot the PC (before the boot manager menu) I see the text: "Sil0 138GB". Ok, it is correct. Now I want to install Suse 9.3 Pro, I boot from DVD and I see 2 HDx73GB and not HD 1x138GB. Why ? This is correct ? Tnx in advance for all and sorry for my bad english. M.

6 6

RE: [suse-amd64] Tyan s2895, SUSE 9.3 install/boot problem
by Dima 16 May '05

16 May '05

Hi, after a frustrating weekend I finally installed and booted SUSE 9.3. It was maybe not the most intelligent way to make it work, but it worked anyway ... The BIOS is most likely up to date. At least I have not found updates on Tyan's website The key was to change BIOS settings. Also the power management was disabled using Yast. Here are the details: 1. System: Tyan S2895UA2NRF motherboard 2x252 Opteron 4Gb RAM (4x1Gb) or 8Gb (8x1Gb) PC3200 400DDR Infineon NVidia 6800 GT 2x160GB SATA Western Digital HD Audigy 2 ZS Sound Blaster 2. BIOS finds both CPU's, all system memory and reports 200Mhz CPU clock. 3. For whatever reason SuSE installer can see only one CPU, no matter how much memory installed. The only difference is that when 4gB installed, the system boots and crashes after install, while when it's 8Gb, it does not boot at all. The only way to boot it was to start installation again and when you are past language selection and prompted with choices "install", "repair", etc choose "boot installed system". Obviously it has drivers and kernel in memory and can boot. The catch is that it uses default, not smp kernel, with all consequences. That is, most of the necessary modules are not loaded, since it's default kernel is running, but smp kernel was installed (/lib/modules/2.6.11 .... has smp modules). 4. The situation was rectified when I disabled powermanagement in Yast and enabled "Node Memory Interleave" in BIOS. After that the system booted. Don't ask me why that helped, it's just a guess. 5. Below are the grub entries and BIOS settings. I hope it will be useful. ====================================================== /boot/grub/menu.lst : # Modified by YaST2. Last modification on Sun May 15 00:28:40 UTC 2005 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd1,0)/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.3 kernel (hd1,0)/vmlinuz root=/dev/sdb5 vga=0x31a selinux=0 splash=silent console=tty0 resume=/dev/sdb7 showopts initrd (hd1,0)/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows root (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy root (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX 9.3 kernel (hd1,0)/vmlinuz root=/dev/sdb5 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off iommu=noforce 3 initrd (hd1,0)/initrd ====================================================== Phoenix BIOS settings: Main: Installed OS: Linux BIOS Date: 02/21/05 BIOS Version: 1.00.2895 Advanced: Secured Setup Config: No Reset Config Data: No Hummer Config: HTLDT: 1000 ECC: Enable ECC Scrub Redirect: Disable DRMA ECC Scrub STL: Disable MemClock: Auto Node Mem Interleave: Enabled or Auto DRAM Bank Interleave: Auto 4 GB Mem Hole Adjust: Auto 4 Gb Mem Hole Size: 1280 DDR Clock jitter: Enable Mem Mapping: Disable Enable all Memory Clocks: Populated Controller Config mode: Auto Timing Config Mode: Auto Integrated Dev: USB Ctl: USB1.1+USB2 USB BIOS Legacy Supp: Disabled MAC LAN: Enabled MAC LAN Bridge: Enabled MAC ADDr: 00E0815486B2 Audio Codec: Enabled SATA0 Controller: Enabled SATA1 Controller: Enabled Interrupt Mode: APIC Slave Dev Config: MAC LAN: Enabled MAC LAN Bridge: Enabled MAC ADDr: xxxxxxxxxxxxxx NV Raid Config: Disabled FirstWare Config: FirstWare Language: English FirstWare Auth Level: High Firstware Video Mode: 1024x768 PCI Config: PCI Device, Slot #1: Option RAM Scan: Enabled Enable Master: Enabled Latency Timer: 0040h PCI Device, Slot #2: Option RAM Scan: Enabled Enable Master: Enabled Latency Timer: 0040h PCI Device, Slot #3: Option RAM Scan: Enabled Enable Master: Enabled Latency Timer: 0040h PCI Device, Slot #4: Option RAM Scan: Enabled Enable Master: Enabled Latency Timer: 0040h PCI Device, Slot #5: Option RAM Scan: Enabled Enable Master: Enabled Latency Timer: 0040h PCI Device, Slot #6: Option RAM Scan: Enabled Enable Master: Enabled Latency Timer: 0040h PCI Layout: PCI-Express PCI 32bit PCI-Express PCIX 100Mhz PCIX 100Mhz PCIX 133Mhz Integrated SCSI Controller: Integrated SCSI: Enabled Enabled Master: Disabled Latency Timer: Default Integrated 1394: Integrated 1394: Enabled PCI/PNP ISA UMB Region Exclusion: C800-CBFF: Available CC00-CFFF: Available D000-D3FF: Available D400-D7FF: Available D800-DBFF: Available DC00-DFFF: Available PCI/PNP ISA IRQ Resource Exclusion: IRQ 3: Available IRQ 4: Available IRQ 5: Available IRQ 7: Available IRQ 9: Available IRQ 10: Available IRQ 11: Available IRQ 15: Available IDE Config: Large Disk Access Mode: DOS Local Bus IDE Adapter: Primary IDE Channel 0 Master [CD-ROM]: Type: Auto Multi-Sector Transfers: Disabled LBA Mode Ctl: Disabled 32 Bit I/O: Disabled Transfer Mode: FPIO 4/DMA2 UltraDMA MOde: DMA2 IDE Channel 0 Master [None]: Type: Auto Multi-Sector Transfers: Disabled LBA Mode Ctl: Disabled 32 Bit I/O: Disabled Transfer Mode: Standard UltraDMA MOde: Disabled Floppy Config: Floppy Disk Controller: Auto Legacy Diskette A: .44/1.25M 3 1/2" Legacy Diskette B: Disabled I/O Device Config: Serial Port A: Auto Serial Port B: Auto Mode: Normal Memrory: Mem Cache: Enabled Cache Sys BIOS Area: Write Back Cache Video BIOS Area: Write Back Cache Base 0-512K: Write Back Cache Base 512-640K: Write Back Cache Ext Mem Area: Write Back Cache A000-Afff: Disable Cache B000-Bfff: Disable Cache C800-CBFF: Disable Cache CC00-Cfff: Disable Cache D000-D3FF: Disable Cache D400-D7ff: Disable Cache E000-E3FF: Disable Cache E400-E7FF: Disable Cache E800-EBFF: Disable Cache EC00-EFFF: Disable Ext Memory: 8386560 K Cache RAM: 1024K Sys Mem: 608K Security: Supervisor Passwd: Clear User Paswd: Clear Fixed disk boot sector: Normal Diskette Access: Supervisor Virus Check Remnder: Disable System Backup Reminder: Disable Boot: Quickboot Mode: Enabled Quietboot Mode: Enabled Summary Screen: Enabled Boot Dev Priority: 1. Floppy 2. Ide0 3. IDE CD: LITE-ON COMBO SOHC-5235K- 4. PCI SCSI: WDC WD1600JD-22HBB0 5. PCI BEV Excluded from boot order: 1. IDE1 2. USB FDC 3. USB HDD 4. USB CDROM 5. USB ZIP Power: ACPI S3: Disabled Spread Spectrum: Disabled After Power Failure: Last State ====================================================== --- "Black, Alain" <ablack(a)bloodsystems.org> wrote: > Are you at the latest BIOS release for the > motherboard? > > Does specifying "acpi=off" include "pci=noacpi" for > a boot option? > > -----Original Message----- > From: Dima [mailto:bryga66@yahoo.com] > Sent: Saturday, May 14, 2005 12:06 PM > To: suse-amd64(a)suse.com > Subject: [suse-amd64] Tyan s2895, SUSE 9.3 > install/boot problem > > Hi, > sorry for erroneous first post - accidentally hit > "send" button. > > I'm having a problem installing and booting SUSE 9.3 > on Tyan s2895 board: > Tyan S2895UA2NRF motherboard > 2x252 Opteron > 4 RAM (4x1Gb) > > SUSE itself installs ok (default system with KDE). > After initial boot it reconizes and configure all > hardware. But when I boot and it comes to a point > when > it "starting powersaved" it crashes. I tried to pass > option "acpi=off apm=off" but it did not help > either. > If I boot it in "failsafe mode" it crashes with > kernel > panic. > > Did anybody had/has same problem ? > > Dima. > > > > > __________________________________ > Do you Yahoo!? > Make Yahoo! your home page > http://www.yahoo.com/r/hs > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: > suse-amd64-help(a)suse.com > > Discover Yahoo! Have fun online with music videos, cool games, IM and more. Check it out! http://discover.yahoo.com/online.html

1 0

RE: [suse-amd64] Tyan s2895, SUSE 9.3 install/boot problem
by Black, Alain 16 May '05

16 May '05

Are you at the latest BIOS release for the motherboard? Does specifying "acpi=off" include "pci=noacpi" for a boot option? -----Original Message----- From: Dima [mailto:bryga66@yahoo.com] Sent: Saturday, May 14, 2005 12:06 PM To: suse-amd64(a)suse.com Subject: [suse-amd64] Tyan s2895, SUSE 9.3 install/boot problem Hi, sorry for erroneous first post - accidentally hit "send" button. I'm having a problem installing and booting SUSE 9.3 on Tyan s2895 board: Tyan S2895UA2NRF motherboard 2x252 Opteron 4 RAM (4x1Gb) SUSE itself installs ok (default system with KDE). After initial boot it reconizes and configure all hardware. But when I boot and it comes to a point when it "starting powersaved" it crashes. I tried to pass option "acpi=off apm=off" but it did not help either. If I boot it in "failsafe mode" it crashes with kernel panic. Did anybody had/has same problem ? Dima. __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

1 0