I recently did a YOU update of SuSE 9.2 (KDE 3.3) on my AMD64 and now I can't
reboot in WinXP having the following error when selecting Windows from the
Filesystem type unknown, partition type 0x7
the configuration files are:
# Modified by YaST2. Last modification on Tue Apr 19 14:07:08 2005
color white/blue black/light-gray
###Don't change this comment - YaST2 identifier: Original name: windows###
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 9.2
kernel (hd0,1)/boot/vmlinuz root=/dev/sdb2 selinux=0 splash=silent
console=tty0 resume=/dev/sdb1 desktop elevator=as showopts
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 9.2
kernel (hd0,1)/boot/vmlinuz root=/dev/sdb2 showopts ide=nodma apm=off
acpi=off vga=normal noresume selinux=0 barrier=off iommu=noforce maxcpus=0 3
###Don't change this comment - YaST2 identifier: Original name: memtest86###
title Prueba de memoria
install --stage2=/boot/grub/stage2 /boot/grub/stage1 d
(hd1) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst
/dev/sda is the windows drive having NTFS on /dev/sda1 perfectly seen when in
/dev/sdb is the suse drive having reiserfs on /dev/sdb2.
I'm pretty stucked as i've already tried to change menu.lst with options like
"savedefault", and "makeactive", but I cannot get windowsXP to boot. The
update had something to do with kernel and security updates after 9.2 fresh
install, I'm a newbie and did not pay much attention to what was going to be
installed and just accepted the YOU defaults.
Any kind of help to solve this issue will be appreciated a lot
I've downloaded this beast and it does run on my hardware.
Question though is how to show that the real thing will work and not
stop on loading the sata_sis.ko module as 9.2 does.
What's needed is some sort of boot CD that just does that like
the patch CD for 9.2 so can test if it will get further than 9.2.
The story so far:
In the beginning the Universe was created. This has made a lot
of people very angry and been widely regarded as a bad move.
I'm lucky enough to have been tasked with the installation of Suse 9.2
on an HP xw9300 workstation. This is a nice machine -
dual 250 Opterons
8 GB RAM
Nvidia Quadro FX3400
250 GB SATA HD
The board is based on the nForce Professional 2200 chipset. I'm having
a heck of a time getting 9.2 installed.
This is what I do - I have the Suse 9.2 distribution on an IDE drive
that I have connected to the machine. I boot with a CD burned with the
SUSE-Linux-9.2-mini-installation.iso disk from 29 November 2004, which
as far as I can tell is the most recent version of that file. In the
installation, a number of things can go wrong. Most involve problems
with the nForce chipset, I believe. I choose 'Manual Installation',
load the sata_nv module (which it often chokes on - I am not passing any
parameters for that module, and often while it says 'Trying to load
module "sata_nv", the machine will freeze up and I can only hard reset
it - I can't do an Alt-F4 to see what is going on in the kernel.), and
load the ext3 module (because that's what's on my /dev/hdb1). If it
makes it past the sata_nv loading, everything goes fine until it tries
to mount my root partition for installation. I get a 'Could not mount
partition /dev/sda2 to /mnt' error. If I flip to a console and try to
mount /dev/sda2 /mnt, I get a 'mount: Invalid argument' error. The
kernel logs say:
ReiserFS: sda2: found reiserfs format "3.6" with standard journal
ReiserFS: sda2: using ordered data mode
reiserfs: using flush barriers
ReiserFS: sda2: journal params: device sda2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: sda2: checking transaction log (sda2)
ReiserFS: sda2: warning: journal-837: IO error during journal replay
ReiserFS: sda2: warning: Replay Failure, unable to mount
ReiserFS: sda2: warning: sh-2022: reiserfs_fill_super: unable to
initialize journal space
I've tried using Ext3 for my root partition as well, but I get other
problems - a InstTarget: E_RpmDB_not_open error on the first package it
tries to install.
I hope someone can help...
is anyone out there who has successfully installed and run
SuSE 9.3 on a FSC V810 Celsius Opteron 250, 2 CPU with 8 GM
Memory and Bios 1.07?
We think of updating from SuSE 9.0, Kernel 2.4.21-280, so
my questions are:
- Is the Kernel Panic issue which we experienced with SuSE
9.2 (and was also reported on this list) resolved in 9.3?
- are Nvidia FX 4000 graphics cards running in accel mode
on X.org 6.x?
- any other known issues?
Andrew Halliwell wrote:
>And verily, didst Ken Siersma announce to the hordes:
>>I've tried using Ext3 for my root partition as well, but I get other
>>problems - a InstTarget: E_RpmDB_not_open error on the first package it
>>tries to install.
>>I hope someone can help...
>One thing I'll suggest...
>Forget ext3 and reiserfs... and try formatting the partitions with jfs.
>I had problems with ext2 and reiser on an x86-64 machine just the other
>week, in which it'd format the partition but then the thing would fall flat
>on its face when trying to write to disk.
>JFS worked fine however...
>Once you've got it installed, do an immediate online update to the latest
>kernel. That SHOULD fix your problems.
Thanks Andrew for your helpful suggestion.
I have Suse 9.2 running now on this machine, and everything works great
except for one thing - the QuadroFX 3400 card. X does work - I had to
pass the 'noapic' option to Grub, but it does indeed work with direct
rendering enabled. Unfortunately, my OpenGL application is quite flaky
on this machine. Frequently, it will stop drawing the scene. It
appears to me that the buffers are not getting swapped. If I resize the
window, the OpenGL app will return to normal, for a while. Then it will
stop drawing again. Also, the app will hesitate intermittenly. This
app works flawlessly on other cards, using the same Nvidia driver.
The main difference I see is that this QuadroFX card is a PCI-Express
card. I know historically AGP is preferred over PCI, but what about
this PCI-Express? Are their any known tweaks for a PCI-Express nvidia
card? I am getting what I think is good FPS with glxgears -> in the
39500s. Seems really good, actually. But my app is not so great...
Ken Siersma, Software Engineer
phone: (248) 624-9957
fax: (248) 624-7158
"Our lives begin to end
the day we become silent about things that matter."
I should have been more specific - this is for SuSE 9.3...
> -----Original Message-----
> From: Croker, Grant
> Sent: 19 April 2005 10:50
> To: suse-amd64(a)suse.com
> Subject: [suse-amd64] Boot CD for network install?
> is there any chance the boot cd for a networked 64 bit install can be
> posted to ftp.suse.com?
> Grant Croker
> Computer Associates
> Software Engineer, Ingres Development
> Tel: +44 1753 242154 (UK)
> Mobile: +44 7801 916524 (UK)
is there any chance the boot cd for a networked 64 bit install can be
posted to ftp.suse.com?
Software Engineer, Ingres Development
Tel: +44 1753 242154 (UK)
Mobile: +44 7801 916524 (UK)
I have been trying to get a second wireless card to work in my hp laptop
with a 64 AMD. I have not been successful at all. I have found that I
believe that SuSE is mis detecting the orinoco gold card that I am
trying to use. When that card is plugged in I get the following. When it
is not plugged in these lines are not in the system log.
Apr 18 16:50:55 DsHP cardmgr: executing: 'modprobe memory_cs 2>&1'
Apr 18 16:50:55 DsHP cardmgr: + FATAL: Module memory_cs not found.
Apr 18 16:50:55 DsHP cardmgr: modprobe exited with status 1
Apr 18 16:50:55 DsHP cardmgr: module
/lib/modules/2.6.8-24.14-default/pcmcia/memory_cs.o not available
Apr 18 16:50:55 DsHP cardmgr: bind 'memory_cs' to socket 0 failed:
I have never had a problem with the orinoco gold card and SuSE. I have
used it with 9.1 and 9.2 but only the 32 bit version. I am now using the
64b version. Any ideas?