openSUSE AMD64 October 2004

amd64@lists.opensuse.org

115 participants
131 discussions

Re: [suse-amd64] Suse 10 release schedule info request.

by rrpalma＠synopsis.ws

I was also able to get in the States. ________________________________________ Ricardo R Palma SYNOPSIS SA Telef. (+51 1) 275-4941 / 275-4708 / 275-7523 email : rrpalma(a)synopsis.ws www.synopsis.ws -----Johan Nielsen <yep(a)osterbo-net.dk> wrote: ----- To: suse-amd64(a)suse.com From: Johan Nielsen <yep(a)osterbo-net.dk> Date: 10/26/2004 08:30PM Subject: Re: [suse-amd64] Suse 10 release schedule info request. Onsdag den 27. oktober 2004 02:53 skrev Marco Maske: > Johan Nielsen wrote: > > 9.2 is in Beta right now > > > > have a look at their press-release > > Excuse. In Germany SuSE 9.2 is still in shops since last friday :-) > > -- > Ciao Marco, registered GNU/Linux-User 313353 > > Keine Macht George W.Bush und seiner Junta zur Ausbeutung, Unterdrueckung, > Weltmacht & 'BigBrother-watching'; kauft keine U$-Waren! The upgradeversion too ?? -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

17 years, 9 months

xfs + lvm + suse9.1 problem

by Joe Georger

I have been trying to get some 3TB raids online by merging the two sub-2TB luns into a 3TB LV using LVM in Suse 9.1. Problem is, when I go to format the logical volume in xfs it hangs, then upon subsequent reboot the machine hangs at nfsboot (sm_notify). If I use Reiser or JFS this does not happen. Also, how do I boot the machine around this nfsboot hangup? Failsafe does not work. Thanks, Joe

17 years, 9 months

install problem for Nvidia 3400 on dual Xeon EMT64 machine

by Oliver Otto

Hello, I just got a Dell precision 470 with a Nvidia FX 3400 and I installed the 64bit version of Suse 9.1 on it. The installation was successful and Suse is running fine. However, it could not recognise my graphics card and installed a VESA driver instead. I then downloaded the Nvidia driver amd64 and installed it without error message. If I now run sax2 in "init 3" without parameter I have the chance to chose the graphics card but my 3400 is not in the list. If I instead run "sax2 -m 0=nvidia" my linux is crashing with a black screen. Has anyone tried to install this PCI-express card on Suse 9.1?? Thanks for any help, Oliver

17 years, 9 months

Mplayer-Gxine

by Marios K.

I am new to the list and sorry if these questions are allreaedy answered. 1.I am trying to comile Mplayer 1pre5. My configure script is /configure --with-x11libdir=/usr/X11R6/lib64 --libdir=/usr/lib64 --prefix=/usr --disable-fbdev --enable-gui --enable-menu But is there anyway to compile mplayer using also win32-support? When i enable this option the compile crashes when using wine, since ( i think ) it doesn't support 64 bit. 2.I compiled succesufully xine-lib (with a lot of problems since some libraries like theora, libvorbis since the compilation stops so i had to disable them). But when i try to compile gxine it says cannot find -lXtst and stops. Whats wrong? Any help would be appreciated. Thanks

17 years, 9 months

Help Request- converting Raid root drives for 2.6.8+ boot

by Joel Wiramu Pauling

Hi all, Since 2.6.8.1 + kernels, the kernel is unable to find my raid arrays. I have searched and found that riadstart is deprecated and broken. (raidstart is what suse uses by default), I have since installed upto date mdadm tools, and tried setting up a /etc/mdadm/mdadm.conf with my raid drives, and also reruning mkinitrd for my new kernels with root specified. But the kernel still refuses to boot my root partition. I boot off a non raided partition sda1 and also have swap on a non raided partition sdb1. My raid setup is as bellow: ARRAY /dev/md1 level=raid0 num-devices=2 UUID=da49e3b8:d0b65de4:7817e388:54c4980d devices=/dev/sda3,/dev/sdb3 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3702dbfc:1572856f:4f673190:fc5212c4 devices=/dev/sda2,/dev/sdb2 Now I've tried using a number of howto's with sata raid root etc, but nothing seems to work. This is what the last functioning kernel that boots, boot process looks like: ata1: SATA max UDMA/133 cmd 0x9800 ctl 0x9C02 bmdma 0xA800 irq 20 ata2: SATA max UDMA/133 cmd 0xA000 ctl 0xA402 bmdma 0xA808 irq 20 ata1: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3e02 87:4023 88:203f ata1: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48 ata1: dev 0 configured for UDMA/100 scsi0 : sata_via ata2: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3e02 87:4023 88:203f ata2: dev 0 ATA, max UDMA/100, 321672960 sectors: lba48 ata2: dev 0 configured for UDMA/100 scsi1 : sata_via Vendor: ATA Model: HDS722516VLSA80 Rev: V34O Type: Direct-Access ANSI SCSI revision: 05 Vendor: ATA Model: HDS722516VLSA80 Rev: V34O Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sdb: 321672960 512-byte hdwr sectors (164697 MB) SCSI device sdb: drive cache: write back sdb: sdb1 sdb2 sdb3 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 mice: PS/2 mouse device common for all mice gameport: pci0000:00:08.1 speed 1187 kHz serio: i8042 AUX port at 0x60,0x64 irq 12 input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard on isa0060/serio0 i2c /dev entries driver md: raid0 personality registered as nr 2 md: raid1 personality registered as nr 3 md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm(a)uk.sistina.com Advanced Linux Sound Architecture Driver Version 1.0.4 (Mon May 17 14:31:44 2004 UTC). ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 19 ALSA device list: #0: Sound Blaster Audigy2 (rev.4) at 0x9000, irq 19 oprofile: using NMI interrupt. NET: Registered protocol family 2 IP: routing cache hash table of 16384 buckets, 128Kbytes TCP: Hash tables configured (established 524288 bind 65536) NET: Registered protocol family 1 md: Autodetecting RAID arrays. md: autorun ... md: considering sdb3 ... md: adding sdb3 ... md: sdb2 has different UUID to sdb3 md: adding sda3 ... md: sda2 has different UUID to sdb3 md: created md1 md: bind<sda3> md: bind<sdb3> md: running: <sdb3><sda3> md1: setting max_sectors to 64, segment boundary to 16383 raid0: looking at sdb3 raid0: comparing sdb3(128841216) with sdb3(128841216) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sda3 raid0: comparing sda3(128849216) with sdb3(128841216) raid0: NOT EQUAL raid0: comparing sda3(128849216) with sda3(128849216) raid0: END raid0: ==> UNIQUE raid0: 2 zones raid0: FINAL 2 zones raid0: zone 1 raid0: checking sda3 ... contained as device 0 (128849216) is smallest!. raid0: checking sdb3 ... nope. raid0: zone->nb_dev: 1, size: 8000 raid0: current zone offset: 128849216 raid0: done. raid0 : md_size is 257690432 blocks. raid0 : conf->hash_spacing is 257682432 blocks. raid0 : nb_zone is 2. raid0 : Allocating 16 bytes for hash. md: considering sdb2 ... md: adding sdb2 ... md: adding sda2 ... md: created md0 md: bind<sda2> md: bind<sdb2> md: running: <sdb2><sda2> raid1: raid set md0 active with 2 out of 2 mirrors md: ... autorun DONE. VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 188k freed md: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 md: could not lock unknown-block(8,2). md: could not import unknown-block(8,2)! md: autostart unknown-block(0,2050) failed! md: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 md: could not lock unknown-block(8,3). md: could not import unknown-block(8,3)! md: autostart unknown-block(0,2051) failed! md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. ReiserFS: sda1: found reiserfs format "3.6" with standard journal ReiserFS: sda1: using ordered data mode ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18,max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: sda1: checking transaction log (sda1) ReiserFS: sda1: Using r5 hash to sort names ReiserFS: md0: found reiserfs format "3.6" with standard journal ReiserFS: md0: using ordered data mode ReiserFS: md0: journal params: device md0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: md0: checking transaction log (md0) ReiserFS: md0: Using r5 hash to sort names Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0 hdb: CHECK for good STATUS hdc: CHECK for good STATUS But newer kernels stop at the autodetection part with an unable to find specified root device please specifiy with root= but it is correctly specified on the kernel command line as root=/dev/md1 (md0 is my home dir which is raid 1, md1 is root which is raid0) Kernels have raid 0 and 1 compiled in aswell as reiserfs which is what i'm using. Help! I need keep testing kernels but I can't continue with this fooked up raid.. BTW: This is related to this message: raidstart(pid 473) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 Any help and comments are appreciated... A step by step howto do this would be helpfull. Kind regards Joel W New Zealand

17 years, 9 months

laptop console video problem

by Brad Bourn

Well, I got the HP zv5000 and LOVE IT! I was able to get SuSE 9.1 on it without too much trouble. Got the nvidia driver working and the widescreen (1280x800) resolution running. I know the boadcom wireless isn't going to work until 9.2 (hint hint hint). I am only having one problem and have one request The problem I'm having is that once X has loaded, I cannot ever get back to a console, virtual or otherwise. I mean I can get to it, I just can't see it. The screen is messed up. Is there a way to fix this? I seem to remember some trouble I had way back when with SuSE 6 something and nvidia where I had to disable the graphical boot screens to stop the issues. Any ideas? The request would be that I remember seeing somewhere that someone was able to enable the touchpad scrolling feature with an aps kernel patch. Anyone heard of this or know where I might find more information? Thanks in advance B-)

17 years, 9 months

Gotchas: 3ware 9000 series AMD Opteron released driver - 3ware ti cket ID 20041021093354

by Kevin.Wilson＠comtrol.com

Thanks to the folks at 3ware we now have a released 64bit driver for their 9000 series SATA controllers...Kudos goes out to 3ware! If any of the information I provide below is inaccurate based upon your experience please reply and post your correction(s). There are a few gotchas that admins (that are not Linux masters) may want to be aware of before pulling down the latest kernel update using YOU. (This may only apply for a short period as I do not know if 3ware plans to get their code into SuSE's kernel tree before the next kernel update so it will then be a supported module.) For those that install directly to the SATA RAID array, if you do not follow the steps below your system will not find the raid array after you reboot to activate the kernel update resulting in a kernel panic and your OS not loading. (NOTE: If the kernel update breaks compatibility this method may not work and therefore you are screwed!) For those that installed to a IDE disk you will need to do as you did initially or follow the steps below if you don't want to recompile a new module. 1) After y.o.u. completes the updates DO NOT reboot. 2) copy the 3w-9xxx.ko from /lib/modules/<old version>/kernel/driver/scsi and /lib/modules/<old-version-override>/ to /lib/modules/<new version>/kernel/driver/scsi and /lib/modules/<new-version-override>/ 3) add line for 3w-9xxx dependencies in the new modules.dep (copying the old mod-dep line and modifying it worked nicely). 4) ensure that 3w-9xxx is still in the INITRD_MODULES parameter in /etc/sysconfig/kernel. 5) run mkinitrd You can then reboot and the driver will load at boot thereby allowing you to use your OS that is installed directly to the raid array. Since I don't know if 3ware plans to get their source into SuSE supported modules list I would have to say installing directly to the raid array would be risky for a production server. Since I experienced weird behavior for a directory mounted raid array (kernel reporting segmentation faults for moves and copies of files to the raid array but not from it) I am not sure if installing to a IDE disk is such a good idea either. According to a fellow from 3ware support, 3ware's code will be part of the 2.6.8 kernel source tree so if SuSE 9.2 is going to use that kernel version of later then ya gots no worries about any of the stuff I babbled on about here.

17 years, 9 months

9.1 / 9.2 and Adpatec 2410SA RAID 5

by rrpalma＠synopsis.ws

Hello, Does anybody know whether SuSE 9.1 for AMD64 will support hardware RAID 5 with the Adaptec 2410SA (Serial ATA) adapter? I'm configuring a Tyan motherboard (Thunder K8W S2885) with dual boot between SuSE 9.1 and Win XP (unfortunately). While Linux will support software RAID, Windows will not. So I need a card that will support both OS using hardware RAID. Any advice? Thanks! ________________________________________ Ricardo R Palma SYNOPSIS SA Telef. (+51 1) 275-4941 / 275-4708 / 275-7523 email : rrpalma(a)synopsis.ws www.synopsis.ws

17 years, 9 months

Re: [suse-amd64] How do I get enough "juice" for my AMD64 bit based system getting ready for SuSE 9.2 ;-)

by chu＠tes-mail.jpl.nasa.gov

First, what kind of capacity are you talking about? With the new crop of high capacity IDE drives, you can get very high storage density for pretty low price, so you may be able to get what you need with fewer drives. But if you realy need 20 drives, you may not have a simple solution. Most 3.5" drives will generally require about 15 watts each to operate. So for 20 of them, you will need a power supply to be able to sustain 300W output, so a 450W power supply will be a minimum recommended size just for them. I don't know if anyone makes a computer enclosure that can hold that many drives, so it means installing them in an external chassis of some sort. Then there is the problem of connecting them to the IDE interfaces on your computer; I don't think IDE cables, even the fancy round ones, can be more than a couple feet long, and most of them are for connections within the same cabinet. This means you need some form of controller to convert the protocol into something that can be driven over a meter outside of the enclosures, like SCSI or FCAL. So this implies some kind of RAID controller for the drives and a SCSI or FCAL HBA. There are a number of sources for low-cost RAID systems using IDE drives and SCSI or FCAL host interfaces. Here's an example controller with enclosure: http://www.scsi4me.com/?menu=menu_subsystem&pid=3381 You then add up to 16 drives to this. If you need more drives, you will have to get a second unit. This is a rack-mount system, but the desk-top model is the same unit with rubber feet and no rack mount slides. eyc

17 years, 9 months

laptop ethernet nic non-functional after upgrading kernel via YOU

by pvwoude＠alltel.net

I hope someone can help me. I am running SUSE 9.1 on my emachines m6805 in 64-bit mode. I recently used YOU to update the kernel from the kernel shipped with 9.1 up to 2.6.5-7.108. After this upgrade and re-booting, my laptop does not appear to be initializing the ethernet adapter properly. I have been using DHCP to configure the IP parms. Prior to the update, this worked just fine. After the update, DHCP times out and does not set the ip information correctly. I thought I saw something on this list previously, but cannot find it now. Any ideas/help? Pete

17 years, 9 months

← Newer
1
2
3
4
5
6
7
8
...
14
Older →

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE AMD64 October 2004