I have a old SuSe Linux 9.3 distribution with a 2.6.11.4-21 Suse Kernel.
Now i have new Hardware and will the old system run on this new Hardware, but some new Hardware
is not working (Network, PCI, Graphic an so on). And i need the old System (very important).
So i compiled an new Suse kernel (2.6.31 from Suse 11.2) on the old Suse 9.3 in the new Hardware System.
This is going without problems. I costomized the Kernel in the old System (with new initrd an so on).
The Kernel is starting but the HDs (/dev/sda1 /dev/sda2) are missing.
My HDs are on a SATA Raid Controller in Raid1 (3Ware 9500S-4LP). Is there the error?
Or ist the reiserfs Filesystem the Problem? At Suse 9.3 i had reiserfs 3.6.
How can i find out what reiserfs version is loading.
What is the error?
here is the message:
…
Loading kernel/drivers/scsi/3w-9xxx.ko
3ware 9000 Storage Controller device driver for Linux v2.26.02.012.
3w9xxx 0000:03:02.0: PCI INT A → GSI 17 (level, low) → IRQ 17
scsi4 : 3ware 9000 Storage Controller
3w-9xxx: scsi4: Found a 3ware 9000 Storage Controller at 0xfbeef000, IRQ: 17.
3w-9xxx: scsi4: Firmware FE9X 2.06.00.009, BIOS BE9X 2.03.01.051, Ports: 4.
scsi 4:0:0:0: Direct-Access AMCC 9500S-4LP DISK 2.06 PQ: 0 ANSI: 3
sd 4:0:0:0: [sda] 2929666048 512-byte logical blocks: (1.49 TB/1.36 TiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Write cache: enabled, read cache: disabled, donn’t support DPO …
sda: sda1 sda2 sda3
sd 4:0:0:0: [sda] Atached SCSI disk
Waiting for device /dev/sda2 to appear: …resume device /dev/sda2 not found (ignoring)
Loading kernel/fs/reiserfs/reiserfs.ko
Loading kernel/fs/fuse/fuse.ko
fuse init (API version 7.12)
Waiting for device /dev/sda1 to appear: …not found – exiting to /bin/sh
sh: can’t access tty: job control turned off
$
suggest you strongly consider a complete and tested backup archive of
all your data…then a new install of a supported version of openSUSE
(free) which will be updated/supported about a year, or SUSE Linux
Enterprise (free to download and good for 5 to 7 years of
updates/support, for a fee)
either way you then have all the bits and pieces needed to get your
new hardware working smoothly (if you bought Linux compatible
hardware)…
by the way, most folks have moved away from Reiserfs for the more
capable ext4…
is that raid what is often called “fake software raid” (which doesn’t
work with Linux but (surprise!) is the cat meow with Redmonds Best
(and most expensive)? [cat’s meow there but half-baked and trashy
compared to ext4]
I think you need udev for the device nodes to be created. I suspect the udev stuff goes into the initrd. Sorry, this is only a guess, never really done it.
I too would suggest replacing the whole OS and not just the kernel.
On 05/06/2010 07:16 AM, ken yap wrote:
>
> ‘udev - Wikipedia, the free encyclopedia’
> (http://en.wikipedia.org/wiki/Udev)
>
> The /dev device doesn’t have to contain every possible device needed
> and device nodes are created dynamically.
My opinion is that the driver for your disk system is not in the initrd.
Download the 11.2 Live CD and boot it. Open a terminal, issue the lsmod
command, and look for the disk drivers that are loaded. Make certain
that your configuration builds all of them, and that all of them are
included in the INITRD_MODULES line in /etc/sysconfig/kernel. (I’m
guessing that this part has not changed since 9.3.)
After the above change, then redo the ‘sudo make install’ step on your
new kernel.
I have parallel a Suse 10.2 distri installed in the Server on a second HD. This System ist running absolutely clean.
What must i do exactly?
Shoult i incluse all modules which are in the Suse 10.2 distri in INITRD_MODULES (/etc/sysconfig/kernel) in the INITRD_MODULES (/etc/sysconfig/kernel) from Suse 9.3 and than make a new initrd?
And must I compile the kernel new? Or is it enough to make the initrd new on the suse 9.3?
On 05/06/2010 09:46 AM, witjojo wrote:
>
> Can you explain exactly what i have to do?
>
> I have parallel a Suse 10.2 distri installed in the Server on a second
> HD. This System ist running absolutely clean.
>
> What must i do exactly?
> Shoult i incluse all modules which are in the Suse 10.2 distri in
> INITRD_MODULES (/etc/sysconfig/kernel) in the INITRD_MODULES
> (/etc/sysconfig/kernel) from Suse 9.3 and than make a new initrd?
Not all modules - just the ones that pertain to the disk. Since 9.3, the
entire structure of the disk drivers have changed. I don’t think 10.2 is
new enough for the change. You need to burn an 11.2 Live CD and boot it
to determine what drivers are needed.
On my machine, the end of the lsmod output contains
On 05/06/2010 12:46 PM, witjojo wrote:
>
> oh sorry i wrote it wrong - it is a 11.2 distri.
>
> I have parallel a Suse 11.2 distri installed in the Server on a second
> HD. This System ist running absolutely clean.
>
> helps this in any way?
Yes, you can use the lsmod on any 11.2 system to determine the modules
needed on your box.
Now i made the initrd new. The first error was the 3Ware module. The old name was 3W-9xxx and the new name is 3W_9xxx. Now the System is booting, but i have some problems with other modules.
For example I have no network. When i start Yast and want to manage my notwork interfaces i have no drivers for the new onboard Networkinterface. The Networkinterface will not be identified.
I think i have a error by design on the compile process.
Maybe the moduls are not compiled correctly.
So i will short describe what i have done.
copy kernel-2.6.31…)sources from parallel installed 11.2 to suse9.3 (/usr/src)
copy .config from parallel installed 11.2 to suse9.3 (/usr/src/kernel-2.6.31…)
i thought this is the easiesd way because i need the .config for the new hardware and the 11.2 distri was parallel installed on the same system. Is it wrong?
the openSUSE community tries it best to support current versions in
these fora…
versions now current are openSUSE 11.0, 11.1 and 11.2
SUSE Linux 9.3 has not been supported since April 30th 2007
i do not know, but maybe there is a commercial version of SUSE Linux
Enterprise available from Novell which you could use, try them at forums.novell.com
on the other hand, you are welcome to visit here everyday to see if
someone has discovered a way to get you rolling again in 9.3, but imo
bumping the thread is not likely to bring magic which is not available…
On 05/07/2010 04:56 AM, witjojo wrote:
>
> Now i made the initrd new. The first error was the 3Ware module. The old
> name was 3W-9xxx and the new name is 3W_9xxx. Now the System is booting,
> but i have some problems with other modules.
>
> here is the lspci:
> 0000:00:00.0 Host bridge: Intel Corporation: Unknown device 0040 (rev
> 12)
> 0000:00:02.0 VGA compatible controller: Intel Corporation: Unknown
> device 0042 (rev 12)
> 0000:00:16.0 Communication controller: Intel Corporation: Unknown
> device 3b64 (rev 06)
> 0000:00:16.2 IDE interface: Intel Corporation: Unknown device 3b66 (rev
> 06)
> 0000:00:16.3 Serial controller: Intel Corporation: Unknown device 3b67
> (rev 06)
> 0000:00:19.0 Ethernet controller: Intel Corporation: Unknown device
> 10ef (rev 06)
> 0000:00:1a.0 USB Controller: Intel Corporation: Unknown device 3b3c
> (rev 06)
> 0000:00:1b.0 Class 0403: Intel Corporation: Unknown device 3b56 (rev
> 06)
> 0000:00:1c.0 PCI bridge: Intel Corporation: Unknown device 3b42 (rev
> 06)
> 0000:00:1c.2 PCI bridge: Intel Corporation: Unknown device 3b46 (rev
> 06)
> 0000:00:1d.0 USB Controller: Intel Corporation: Unknown device 3b34
> (rev 06)
> 0000:00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
> 0000:00:1f.0 ISA bridge: Intel Corporation: Unknown device 3b0a (rev
> 06)
> 0000:00:1f.2 IDE interface: Intel Corporation: Unknown device 3b20 (rev
> 06)
> 0000:00:1f.3 SMBus: Intel Corporation: Unknown device 3b30 (rev 06)
> 0000:00:1f.5 IDE interface: Intel Corporation: Unknown device 3b26 (rev
> 06)
> 0000:00:1f.6 Signal processing controller: Intel Corporation: Unknown
> device 3b32 (rev 06)
> 0000:01:00.0 IDE interface: Unknown device 197b:2368
> 0000:03:01.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX
> [Boomerang]
> 0000:03:02.0 RAID bus controller: 3ware Inc 3ware Inc 3ware 9xxx-series
> SATA-RAID
>
> For example I have no network. When i start Yast and want to manage my
> notwork interfaces i have no drivers for the new onboard
> Networkinterface. The Networkinterface will not be identified.
>
> I think i have a error by design on the compile process.
> Maybe the moduls are not compiled correctly.
>
> So i will short describe what i have done.
>
> 1. copy kernel-2.6.31…)sources from parallel installed 11.2 to
> suse9.3 (/usr/src)
> 2. copy .config from parallel installed 11.2 to suse9.3
> (/usr/src/kernel-2.6.31…)
> i thought this is the easiesd way because i need the .config for the
> new hardware and the 11.2 distri was parallel installed on the same
> system. Is it wrong?
> 3. cd /usr/src/kernel-2.6.31…
> 4. make && make modules_install
If you change the above and make the change to /etc/sysconfig/kernel, to
make && make modules_install install, you can skip steps 5, 6, 7, 9, 10,
and 12.
> 5. cp ./arch/i386/boot/bzImage /boot/vmlinuz-2.6.31…
> 6. cp ./System.map /boot/System.map-2.6.31…
> 7. cp ./.config /boot/config-2.6.31…
> 8. change entries in /etc/sysconfig/kernel
> (INITRD_MODULES=“thermal ata_generic pata_jmicron ata_piix
> ide_pci_generic 3w_9xxx processor fan”)
> 9. cd /boot
> 10. mkinitrd -k vmlinuz-2.6.31… -i initrd-2.6.31…
> (Here i had dep. problems in module ata_piix but i ignored it)
> 11. two new links vmlinuz2 → kernel-2.6.31… and initrd2 →
> initrd-2.6.31…
> 12. changes for 2nd kernel /boot/grub/menu.lst
> (kernel → vmlinuz2 and initrd2)
> 13. booting
It is likely that your network card is not configured. Please provide
the output of
After i had some more problems with a new compiled kernel now i migrate the suse 9.3 system in a virtual machine.
All work fine but i have some problems with root login.
And I don’t know why. It’s exactly the same system.
What is the problem?
I have a System Administrator user “root” in my LDAP domain. I have been setup with “nsswitch.conf” (files ldap) to look to the local files first and then LDAP. But the system will pull the root user from LDAP first. So when i login with “root” it’s the wrong root (the LDAP root) without home and privileges.
Why is the problem after the migration to virtual machine?