LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Solaris / OpenSolaris (https://www.linuxquestions.org/questions/solaris-opensolaris-20/)
-   -   Solaris 10 in parallele with Centos and windows XP (https://www.linuxquestions.org/questions/solaris-opensolaris-20/solaris-10-in-parallele-with-centos-and-windows-xp-496534/)

hermouche 10-29-2006 01:08 AM
Solaris 10 in parallele with Centos and windows XP
 
Hy every body :Pengy:

I would like to install SOLARIS 10 in my box which has already windows XP installed in one HDD1, and Centos 4.4 installed in another HDD2.

I want to install SOLARIS 10 in the HDD2 (parallel with Centos).

Is it possible?
How to do it without affecting Centos or Windows XP?

In fact my problem reside in the space that i should allocate to SOLARIS since actually Centos is occupying the totality of the HDD2 (20GB).

How to resize the space allocated for Centos in order to be able to install SOLARIS 10, if this is acceptable of course?

Thanks a lot.

red :confused:

jlliagre 10-29-2006 01:36 AM
You certainly can install Solaris in a multi-boot configuration along with Windows and Linux. This is in fact a quite common setup and has been discussed many times in this forum. The main point is Solaris requires a primary partition and is installing a specific release of grub.

Concerning your Centos shrinking issue, you'd rather ask for advice in a Linux specific forum like "Linux - General". I would suggest you to split the disk in two 10 GB partitions.

hermouche 10-29-2006 04:57 AM
Quote:
Originally Posted by jlliagre
You certainly can install Solaris in a multi-boot configuration along with Windows and Linux. This is in fact a quite common setup and has been discussed many times in this forum. The main point is Solaris requires a primary partition and is installing a specific release of grub.

Concerning your Centos shrinking issue, you'd rather ask for advice in a Linux specific forum like "Linux - General". I would suggest you to split the disk in two 10 GB partitions.

It means that i should format the HDD2, split it into two partitions and then after intall Centos in one partition and Solaris in the other partition.

Is that correct?

thanks jlliagre

red

jlliagre 10-29-2006 05:24 AM
If you don't mind reinstalling CentOS, and loosing current work you may have done with it, that is indeed a way to go.

In any case, install Solaris after other O/Ses.

hermouche 10-29-2006 06:05 AM
Quote:
Originally Posted by jlliagre
If you don't mind reinstalling CentOS, and loosing current work you may have done with it, that is indeed a way to go.

In any case, install Solaris after other O/Ses.

OK, i will format, then install Centos in one partition and then at last Solaris.

Hope it works!!

I will resume here the result.

Bye

red :)

jlliagre 10-29-2006 08:09 AM
What precisely Solaris 10 release are you going to install ?

hermouche 10-29-2006 09:06 AM
Quote:
Originally Posted by jlliagre
What precisely Solaris 10 release are you going to install ?
I am planning to install the solaris 10 6/06 Operating System for the x86 platform, then after i will install the companion DVD.

Is this OK?

This will be my first attempt installing solaris, so i am not sure that i will succeed!!


red :)

jlliagre 10-29-2006 10:10 AM
You can check if your hardware is supported with a recently released java application, Sun Device Detection Tool, which runs under windows and linux:

http://www.sun.com/bigadmin/hcl/hcts/device_detect.html

There is also the installation check tool there:

http://www.sun.com/bigadmin/hcl/hcts/install_check.html

hermouche 10-29-2006 12:05 PM
Ok
 
Quote:
Originally Posted by jlliagre
You can check if your hardware is supported with a recently released java application, Sun Device Detection Tool, which runs under windows and linux:

http://www.sun.com/bigadmin/hcl/hcts/device_detect.html

There is also the installation check tool there:

http://www.sun.com/bigadmin/hcl/hcts/install_check.html
OK thanks jlliagre, i will do so.

A +

red

hermouche 10-29-2006 03:37 PM
Well

I've formated the HDD2.

I created two partitions, one for Centos and another for Solaris.

Now, i can have centos and windows when i boot the box from the HDD1. Both Windows and Centos work fine.

However in orther to have solaris, i should change the bios setting to boot from HDD2.

In this last case it seems that i can boot to have either solaris or windows.

Launching solaris seems in good shape and health but i could not have the graphical mode.

When i boot the solaris; it goes to console mode, it asks for my password and then how to go to graphical mode?

The 'ifconfig -a) command give's only the loopback (i've got two NIC's).

The (who -r) command tels me that i am in runlevel 3.

On the other hands if i launch windows, well i'am in trouble.
It says:
" Booting 'windows'
rootverify (hd0,0)
chainloader +1
ERROR 13: "invalid or unsupported executable format"

It seem's that i missed something when i installed the solaris!!
It has something with grub!!

Thanks.

red

hermouche 11-03-2006 12:26 PM
installed solaris but "internet" ?
 
hy

I 've managed to install Solaris 10 6/06 but now i can not have the internet (can't go outside).

While i installed it, never it asked me for the NIC. I' ve got two NIC's in my box.

What's the problem?

thanks
red

jlliagre 11-03-2006 01:53 PM
This is a common issue that has already been discussed several times in this very forum.

What NICs are there ?

Post the output of /usr/X11/bin/scanpci and have a look at the system messages (dmesg) for network devices.

hermouche 11-04-2006 12:05 AM
Quote:
Originally Posted by jlliagre
This is a common issue that has already been discussed several times in this very forum.

What NICs are there ?

Post the output of /usr/X11/bin/scanpci and have a look at the system messages (dmesg) for network devices.
Thanks jlliagre, well i am sorry it was a mistake, i wanted to open a new thread.

However, these are my NIC's:
- Carte Fast Ethernet CNet PRO200 PCI
- VIA VT6105 Rhine III Fast Ethernet Adapter

I can't really see what's inside the output of
vi /usr/X11/bin/scanpci: <\4^A^B\350^F^L......and so on, it is unreadable.

For the dmesg, well i don't now how to deal with since it is in another computer. I opened the dmesg with vi within a terminal. It is to long to write it down. If there is something special that i have to look for well i will search for it and will responde.

As far as i now there is only the loopback lo0 127.0.0.1. No other device on it.

Thanks again jlliagre.

red

jlliagre 11-04-2006 12:37 AM
scanpci is a binary program.
The correct way to see a program output is by running it, not editing it !

Same comment for dmesg.

hermouche 11-04-2006 10:52 AM
Quote:
Originally Posted by jlliagre
scanpci is a binary program.
The correct way to see a program output is by running it, not editing it !

Same comment for dmesg.
ok. After running scanpci, this is the output:

- pci bus 0x0002 cardnum 0x0c function 0x00: vendor 0x1282 device 0x9102 Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet
- pci bus 0x0002 cardnum 0x0c function 0x00 0x1106 device 0x3106 VIA Technologies, Inc. VT6105 [Rhine-III]

After running dmesg, this is the output:

Sat Nov 4 17:48:45 CET 2006
Nov 4 07:38:58 red.solaris.internal genunix: [ID 672855 kern.notice] syncing file systems...
Nov 4 07:38:58 red.solaris.internal genunix: [ID 904073 kern.notice] done
Nov 4 17:19:44 red.solaris.internal genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_118855-14 32-bit
Nov 4 17:19:44 red.solaris.internal genunix: [ID 943906 kern.notice] Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Nov 4 17:19:44 red.solaris.internal Use is subject to license terms.
Nov 4 17:19:44 red.solaris.internal unix: [ID 126719 kern.info] features: 1007fdf<cpuid,sse2,sse,sep,pat,cx8,pae,mca,mmx,cmov,pge,mtrr,msr,tsc,lgpg>
Nov 4 17:19:44 red.solaris.internal unix: [ID 168242 kern.info] mem = 392748K (0x17f8b000)
Nov 4 17:19:44 red.solaris.internal rootnex: [ID 466748 kern.info] root nexus = i86pc
Nov 4 17:19:44 red.solaris.internal rootnex: [ID 349649 kern.info] pseudo0 at root
Nov 4 17:19:44 red.solaris.internal genunix: [ID 936769 kern.info] pseudo0 is /pseudo
Nov 4 17:19:44 red.solaris.internal rootnex: [ID 349649 kern.info] scsi_vhci0 at root
Nov 4 17:19:44 red.solaris.internal genunix: [ID 936769 kern.info] scsi_vhci0 is /scsi_vhci
Nov 4 17:19:44 red.solaris.internal rootnex: [ID 349649 kern.info] isa0 at root
Nov 4 17:19:44 red.solaris.internal pcplusmp: [ID 658230 kern.info] NOTICE: apic: local nmi: 0 1 1 1
Nov 4 17:19:44 red.solaris.internal pcplusmp: [ID 736762 kern.info] pcplusmp: vector 0x9 ioapic 0x2 intin 0x9 is bound to cpu 0
Nov 4 17:19:44 red.solaris.internal rootnex: [ID 349649 kern.info] pci0 at root: space 0 offset 0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 936769 kern.info] pci0 is /pci@0,0
Nov 4 17:19:44 red.solaris.internal pcplusmp: [ID 637496 kern.info] pcplusmp: ide (ata) instance 0 vector 0xe ioapic 0x2 intin 0xe is bound to cpu 0
Nov 4 17:19:44 red.solaris.internal last message repeated 1 time
Nov 4 17:19:44 red.solaris.internal genunix: [ID 640982 kern.info] IDE device at targ 0, lun 0 lastlun 0x0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 846691 kern.info] model ST340016A
Nov 4 17:19:44 red.solaris.internal genunix: [ID 479077 kern.info] ATA/ATAPI-5 supported, majver 0x3e minver 0x0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 228648 kern.info] ata_set_feature: (0x66,0x0) failed
Nov 4 17:19:44 red.solaris.internal genunix: [ID 640982 kern.info] IDE device at targ 1, lun 0 lastlun 0x0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 846691 kern.info] model ST320410A
Nov 4 17:19:44 red.solaris.internal genunix: [ID 479077 kern.info] ATA/ATAPI-6 supported, majver 0x7e minver 0x0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 228648 kern.info] ata_set_feature: (0x66,0x0) failed
Nov 4 17:19:44 red.solaris.internal pci: [ID 370704 kern.info] PCI-device: ide@0, ata0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 936769 kern.info] ata0 is /pci@0,0/pci-ide@1f,1/ide@0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 773945 kern.info] UltraDMA mode 5 selected
Nov 4 17:19:44 red.solaris.internal last message repeated 1 time
Nov 4 17:19:44 red.solaris.internal gda: [ID 243001 kern.info] Disk1: <Vendor 'Gen-ATA ' Product 'ST320410A '>
Nov 4 17:19:44 red.solaris.internal ata: [ID 496167 kern.info] cmdk1 at ata0 target 1 lun 0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 936769 kern.info] cmdk1 is /pci@0,0/pci-ide@1f,1/ide@0/cmdk@1,0
Nov 4 17:19:44 red.solaris.internal unix: [ID 190185 kern.info] SMBIOS v2.3 loaded (1418 bytes)
Nov 4 17:19:44 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: dld0
Nov 4 17:19:44 red.solaris.internal genunix: [ID 936769 kern.info] dld0 is /pseudo/dld@0
Nov 4 17:19:45 red.solaris.internal pci: [ID 370704 kern.info] PCI-device: pci8086,1a31@1, pci_pci0
Nov 4 17:19:45 red.solaris.internal genunix: [ID 936769 kern.info] pci_pci0 is /pci@0,0/pci8086,1a31@1
Nov 4 17:19:45 red.solaris.internal pci: [ID 370704 kern.info] PCI-device: pci8086,244e@1e, pci_pci1
Nov 4 17:19:45 red.solaris.internal genunix: [ID 936769 kern.info] pci_pci1 is /pci@0,0/pci8086,244e@1e
Nov 4 17:19:45 red.solaris.internal pcplusmp: [ID 637496 kern.info] pcplusmp: pciclass,0c0320 (ehci) instance 0 vector 0x13 ioapic 0x2 intin 0x13 is bound to cpu 0
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Due to recently discovered incompatibilities
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): with this USB controller, USB2.x transfer
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): support has been disabled. This device will
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): continue to function as a USB1.x controller.
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): If you are interested in enabling USB2.x
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): support please, refer to the ehci(7D) man page.
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Please also refer to www.sun.com/io for
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Solaris Ready products and to
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): www.sun.com/bigadmin/hcl for additional
Nov 4 17:19:45 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): compatible USB products.
Nov 4 17:19:45 red.solaris.internal pcplusmp: [ID 637496 kern.info] pcplusmp: pciclass,0c0300 (uhci) instance 0 vector 0x13 ioapic 0x2 intin 0x13 is bound to cpu 0
Nov 4 17:19:46 red.solaris.internal pci: [ID 370704 kern.info] PCI-device: pci1043,8028@1f,2, uhci0
Nov 4 17:19:46 red.solaris.internal genunix: [ID 936769 kern.info] uhci0 is /pci@0,0/pci1043,8028@1f,2
Nov 4 17:19:46 red.solaris.internal pcplusmp: [ID 398438 kern.info] pcplusmp: pciclass,0c0300 (uhci) instance #1 vector 0x17 ioapic 0x2 intin 0x17 is bound to cpu 0
Nov 4 17:19:47 red.solaris.internal pci: [ID 370704 kern.info] PCI-device: pci1043,8028@1f,4, uhci1
Nov 4 17:19:47 red.solaris.internal genunix: [ID 936769 kern.info] uhci1 is /pci@0,0/pci1043,8028@1f,4
Nov 4 17:19:47 red.solaris.internal pcplusmp: [ID 398438 kern.info] pcplusmp: pciclass,0c0300 (uhci) instance #2 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 0
Nov 4 17:19:48 red.solaris.internal usba: [ID 912658 kern.info] USB 2.0 device (usb45e,dd) operating at low speed (USB 1.x) on USB 1.10 root hub: device@1, usb_mid0 at bus address 2
Nov 4 17:19:48 red.solaris.internal usba: [ID 349649 kern.info] Microsoft Comfort Curve Keyboard 2000
Nov 4 17:19:48 red.solaris.internal genunix: [ID 936769 kern.info] usb_mid0 is /pci@0,0/pci1043,8028@1f,2/device@1
Nov 4 17:19:48 red.solaris.internal genunix: [ID 408114 kern.info] /pci@0,0/pci1043,8028@1f,2/device@1 (usb_mid0) online
Nov 4 17:19:48 red.solaris.internal usba: [ID 912658 kern.info] USB 1.0 device (usb461,4d01) operating at low speed (USB 1.x) on USB 1.10 root hub: mouse@2, hid0 at bus address 3
Nov 4 17:19:48 red.solaris.internal genunix: [ID 936769 kern.info] hid0 is /pci@0,0/pci1043,8028@1f,2/mouse@2
Nov 4 17:19:48 red.solaris.internal genunix: [ID 408114 kern.info] /pci@0,0/pci1043,8028@1f,2/mouse@2 (hid0) online
Nov 4 17:19:48 red.solaris.internal usba: [ID 912658 kern.info] USB 2.0 interface (usbif45e,dd.config1.0) operating at low speed (USB 1.x) on USB 1.10 root hub: keyboard@0, hid1 at bus address 2
Nov 4 17:19:48 red.solaris.internal usba: [ID 349649 kern.info] Microsoft Comfort Curve Keyboard 2000
Nov 4 17:19:48 red.solaris.internal genunix: [ID 936769 kern.info] hid1 is /pci@0,0/pci1043,8028@1f,2/device@1/keyboard@0
Nov 4 17:19:48 red.solaris.internal genunix: [ID 408114 kern.info] /pci@0,0/pci1043,8028@1f,2/device@1/keyboard@0 (hid1) online
Nov 4 17:19:48 red.solaris.internal usba: [ID 912658 kern.info] USB 2.0 interface (usbif45e,dd.config1.1) operating at low speed (USB 1.x) on USB 1.10 root hub: input@1, hid2 at bus address 2
Nov 4 17:19:48 red.solaris.internal usba: [ID 349649 kern.info] Microsoft Comfort Curve Keyboard 2000
Nov 4 17:19:48 red.solaris.internal genunix: [ID 936769 kern.info] hid2 is /pci@0,0/pci1043,8028@1f,2/device@1/input@1
Nov 4 17:19:48 red.solaris.internal genunix: [ID 408114 kern.info] /pci@0,0/pci1043,8028@1f,2/device@1/input@1 (hid2) online
Nov 4 17:19:48 red.solaris.internal pci_pci: [ID 370704 kern.info] PCI-device: pci1043,8080@5, uhci2
Nov 4 17:19:48 red.solaris.internal genunix: [ID 936769 kern.info] uhci2 is /pci@0,0/pci8086,244e@1e/pci1043,8080@5
Nov 4 17:19:48 red.solaris.internal pcplusmp: [ID 398438 kern.info] pcplusmp: pciclass,0c0300 (uhci) instance #3 vector 0x12 ioapic 0x2 intin 0x12 is bound to cpu 0
Nov 4 17:19:49 red.solaris.internal pci_pci: [ID 370704 kern.info] PCI-device: pci1043,8080@5,1, uhci3
Nov 4 17:19:49 red.solaris.internal genunix: [ID 936769 kern.info] uhci3 is /pci@0,0/pci8086,244e@1e/pci1043,8080@5,1
Nov 4 17:19:50 red.solaris.internal unix: [ID 950921 kern.info] cpu0: x86 (GenuineIntel family 15 model 1 step 3 clock 1717 MHz)
Nov 4 17:19:50 red.solaris.internal unix: [ID 950921 kern.info] cpu0: Intel(r) Celeron(r) CPU 1.70GHz
Nov 4 17:19:50 red.solaris.internal usba: [ID 912658 kern.info] USB 1.0 device (usb6bd,2095) operating at full speed (USB 1.x) on USB 1.10 root hub: device@1, usb_mid1 at bus address 2
Nov 4 17:19:50 red.solaris.internal usba: [ID 349649 kern.info] AGFA SNAPSCAN
Nov 4 17:19:50 red.solaris.internal genunix: [ID 936769 kern.info] usb_mid1 is /pci@0,0/pci8086,244e@1e/pci1043,8080@5/device@1
Nov 4 17:19:50 red.solaris.internal genunix: [ID 408114 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5/device@1 (usb_mid1) online
Nov 4 17:19:50 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5/device@1 (usb_mid1): no driver found for interface 0 (nodename: 'interface') of AGFA SNAPSCAN
Nov 4 17:19:50 red.solaris.internal rootnex: [ID 349649 kern.info] iscsi0 at root
Nov 4 17:19:50 red.solaris.internal genunix: [ID 936769 kern.info] iscsi0 is /iscsi
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Due to recently discovered incompatibilities
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): with this USB controller, USB2.x transfer
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): support has been disabled. This device will
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): continue to function as a USB1.x controller.
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): If you are interested in enabling USB2.x
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): support please, refer to the ehci(7D) man page.
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Please also refer to www.sun.com/io for
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Solaris Ready products and to
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): www.sun.com/bigadmin/hcl for additional
Nov 4 17:19:56 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): compatible USB products.
Nov 4 17:20:01 red.solaris.internal genunix: [ID 773945 kern.info] UltraDMA mode 5 selected
Nov 4 17:20:01 red.solaris.internal last message repeated 1 time
Nov 4 17:20:02 red.solaris.internal genunix: [ID 454863 kern.info] dump on /dev/dsk/c0d1s1 size 596 MB
Nov 4 17:20:04 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: dtrace0
Nov 4 17:20:04 red.solaris.internal genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace@0
Nov 4 17:20:05 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: zfs0
Nov 4 17:20:05 red.solaris.internal genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs@0
Nov 4 17:20:06 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: pm0
Nov 4 17:20:06 red.solaris.internal genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Nov 4 17:20:07 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: power0
Nov 4 17:20:07 red.solaris.internal genunix: [ID 936769 kern.info] power0 is /pseudo/power@0
Nov 4 17:20:08 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Nov 4 17:20:08 red.solaris.internal genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Nov 4 17:20:18 red.solaris.internal pcplusmp: [ID 637496 kern.info] pcplusmp: asy (asy) instance 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 0
Nov 4 17:20:18 red.solaris.internal isa: [ID 202937 kern.info] ISA-device: asy0
Nov 4 17:20:18 red.solaris.internal genunix: [ID 936769 kern.info] asy0 is /isa/asy@1,3f8
Nov 4 17:20:18 red.solaris.internal rootnex: [ID 349649 kern.info] xsvc0 at root
Nov 4 17:20:18 red.solaris.internal genunix: [ID 936769 kern.info] xsvc0 is /xsvc
Nov 4 17:20:25 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: vol0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
Nov 4 17:20:25 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex@1
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Due to recently discovered incompatibilities
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): with this USB controller, USB2.x transfer
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): support has been disabled. This device will
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): continue to function as a USB1.x controller.
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): If you are interested in enabling USB2.x
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): support please, refer to the ehci(7D) man page.
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Please also refer to www.sun.com/io for
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): Solaris Ready products and to
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): www.sun.com/bigadmin/hcl for additional
Nov 4 17:20:25 red.solaris.internal usba: [ID 723738 kern.info] /pci@0,0/pci8086,244e@1e/pci1043,8080@5,2 (ehci0): compatible USB products.
Nov 4 17:20:25 red.solaris.internal pcplusmp: [ID 398438 kern.info] pcplusmp: ide (ata) instance #1 vector 0xf ioapic 0x2 intin 0xf is bound to cpu 0
Nov 4 17:20:25 red.solaris.internal last message repeated 1 time
Nov 4 17:20:25 red.solaris.internal genunix: [ID 640982 kern.info] ATAPI device at targ 0, lun 0 lastlun 0x0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 846691 kern.info] model HL-DT-ST GCE-8480B
Nov 4 17:20:25 red.solaris.internal genunix: [ID 640982 kern.info] ATAPI device at targ 1, lun 0 lastlun 0x0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 846691 kern.info] model LITE-ON DVDRW LDW-451S
Nov 4 17:20:25 red.solaris.internal genunix: [ID 479077 kern.info] ATA/ATAPI-5 supported, majver 0x20 minver 0x0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 228648 kern.info] ata_set_feature: (0x66,0x0) failed
Nov 4 17:20:25 red.solaris.internal pci: [ID 370704 kern.info] PCI-device: ide@1, ata1
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] ata1 is /pci@0,0/pci-ide@1f,1/ide@1
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal genunix: [ID 935449 kern.info] ATA DMA off: disabled. Control with "atapi-cd-dma-enabled" property
Nov 4 17:20:25 red.solaris.internal genunix: [ID 882269 kern.info] PIO mode 4 selected
Nov 4 17:20:25 red.solaris.internal pcplusmp: [ID 637496 kern.info] pcplusmp: fdc (fdc) instance 0 vector 0x6 ioapic 0x2 intin 0x6 is bound to cpu 0
Nov 4 17:20:25 red.solaris.internal isa: [ID 202937 kern.info] ISA-device: fdc0
Nov 4 17:20:25 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Nov 4 17:20:25 red.solaris.internal fdc: [ID 114370 kern.info] fd0 at fdc0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] fd0 is /isa/fdc@1,3f2/fd@0,0
Nov 4 17:20:25 red.solaris.internal scsi: [ID 193665 kern.info] sd0 at ata1: target 0 lun 0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] sd0 is /pci@0,0/pci-ide@1f,1/ide@1/sd@0,0
Nov 4 17:20:25 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 314293 kern.info] device pciclass,030000@0(display#0) keeps up device sd@0,0(sd#0), but the latter is not power managed
Nov 4 17:20:25 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: llc10
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Nov 4 17:20:25 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Nov 4 17:20:25 red.solaris.internal genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: profile0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Nov 4 17:20:26 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Nov 4 17:20:26 red.solaris.internal genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Nov 4 17:20:27 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Nov 4 17:20:27 red.solaris.internal genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Nov 4 17:20:27 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: pool0
Nov 4 17:20:27 red.solaris.internal genunix: [ID 936769 kern.info] pool0 is /pseudo/pool@0
Nov 4 17:20:27 red.solaris.internal ipf: [ID 774698 kern.info] IP Filter: v4.0.3, running.
Nov 4 17:20:29 red.solaris.internal gda: [ID 243001 kern.info] Disk0: <Vendor 'Gen-ATA ' Product 'ST340016A '>
Nov 4 17:20:29 red.solaris.internal ata: [ID 496167 kern.info] cmdk0 at ata0 target 0 lun 0
Nov 4 17:20:29 red.solaris.internal genunix: [ID 936769 kern.info] cmdk0 is /pci@0,0/pci-ide@1f,1/ide@0/cmdk@0,0
Nov 4 17:20:30 red.solaris.internal scsi: [ID 193665 kern.info] sd1 at ata1: target 1 lun 0
Nov 4 17:20:30 red.solaris.internal genunix: [ID 936769 kern.info] sd1 is /pci@0,0/pci-ide@1f,1/ide@1/sd@1,0
Nov 4 17:20:30 red.solaris.internal genunix: [ID 314293 kern.info] device pciclass,030000@0(display#0) keeps up device sd@1,0(sd#1), but the latter is not power managed
Nov 4 17:25:09 red.solaris.internal pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Nov 4 17:25:09 red.solaris.internal genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0

Well i am sorry it is to long.

i hope it will help.

thanks again.

red

jlliagre 11-04-2006 03:56 PM
I don't think there is a driver available for you Davicom card, but one seems to exist for your Rhine card.
Look at http://homepage2.nifty.com/mrym3/taiyodo/eng/ (vfe-2.3.1.tar.gz)

hermouche 11-05-2006 09:28 PM
Quote:
Originally Posted by jlliagre
I don't think there is a driver available for you Davicom card, but one seems to exist for your Rhine card.
Look at http://homepage2.nifty.com/mrym3/taiyodo/eng/ (vfe-2.3.1.tar.gz)

Yes jlliagre, I've downloaded the file and I tried to follow the README txt but i am in trouble.
how to install it?
This is the README txt from the downloaded driver

***************************************************************************
CAUTION: There is NO WARRANTY for this software.
As this software is loaded into the kernel, it might cause the kernel to
panic or hang.

Masayuki Murayama
KHF04453@nifty.ne.jp
***************************************************************************


1. Introduction

This is the VIA Rhine family NIC driver for Solaris. Rh will work with
VT86C100 (Rhine I), DL10030 (Rhine I), VT6102 (Rhine II), VT6105 (Rhine
III), built-in Rhine II ethernet mac in VT8235 and VT8237 south bridges.
It is distributed under the BSD license.

2. Specification of the driver

File name of the driver:
/kernel/drv/vfe
/kernel/drv/sparcv9/vfe (for sparc 64bit kernel)

Special file name:
/dev/vfeN (where N is a unit number, typcally 0 for first card)
For example
% ifconfig vfe0

Tested chips and cards
VT6102(Rhine II rev 43) -- Planex communications Inc.(Japan) FNW-9702-T3
VT6102(Rhine II rev 47)
DL10030(Rhine I rev 6) -- Corega Inc.(Japan) FEtherII PCI TX
VT6105(Rhine III rev 85) -- Corega Inc.(Japan) FEther PCI-TXA

This driver is ready for VT6105M (Rhine-III management adaptor) but not
tested.

3. Prepare for installation

(1) Install your PCI card and boot Solaris.

(2) Copy source and binary files.
# gunzip -cd vfe-x.x.x.tar.gz | tar xf -

(3) Add hostname for the NIC card into the /etc/hosts file

(4) If you have installed rh driver, remove it and reboot the system.
# rem_drv rh
# sync
# init 0

(5) Make links to correct binary directory and Makefile according to your
configuration. i386 and gcc are default.

% cd /.../vfe-x.x.x
% rm obj Makefile
% ln -s Makefile.${KARCH}_${COMPILER} Makefile
% ln -s ${KARCH} obj

where ${KARCH} is the result of `isainfo -n`, and ${COMPILER} is
"gcc" or "suncc" which you want to use to make the driver.

(6) Making binaries (only for sparc platform)
Rh driver is ready for 64bit and 32bit solaris8 10/00 sparc or
later. (But currently it is unstable on sparc platforms.)
This distribution does not include sparc binaries. To make the binaries,
you need Sun C compiler or gcc version 3, and do the following operations.

% /usr/ccs/bin/make

(7) Making binaries only for OpenSolaris users.
Rh driver likely work with GLD v3 in OpenSolaris, known as Nemo.
You can enjoy the new functions by recompiling vfe source code.

% rm Makefile.config
% ln -s Makefile.config_gld3 Makefile
% /usr/ccs/bin/make


4. Testing

# cd /.../vfe-x.x.x
# /usr/ccs/bin/make install
# ./adddrv.sh
# /usr/ccs/bin/make uninstall (don`t do this for Solaris7)
# modload obj/vfe
# devfsadm -i vfe ( for solaris7, use drvconfig and reboot with -r option )
# ifconfig vfeN plumb ( where N is unit number, typcally 0 for first card)
# ifconfig -a ( you will see an entry for vfe0, ensure ethernet address is correct)
# ifconfig vfeN HOSTNAME
# ifconfig vfeN ( ensure IP address is correct)
# ifconfig vfeN up ( and then you can test with ping, telnet, ftp ...)

5. Installation
After you ensure that the vfe driver is fully functional, install it.

(1) install the vfe driver into kernel directory
# cd /.../vfe-x.x.x
# /usr/ccs/bin/make install

If you did not test vfe driver yet, execute the following commands:
# ./adddrv.sh
# devfsadm -i vfe ( for Solaris7 use drvconfig and reboot with -r option )

(2) Configure the network interface. Create and/or modify the following files:
/etc/hostname.vfeN

If you want to use vfe with dhcp, you also need to create a empty file
below to get an assigned IP address automatically from a dhcp server
at boot time.
/etc/dhcp.vfe0

(3) Reboot the system.
# init 6


6. Troubleshooting

Q. Following message is printed in the /var/adm/messages file
NOTE: vfeN: link up but auto-negotiation failed.

A. This massage appears for Rhine I chips when the link partner does not
have auto negotiation capability.
Please disable auto negotiation capability for your NIC card by specifying
the correct media mode in /kernel/drv/vfe.conf with the following syntax:

vfeN-duplex=["full"|"half"] vfeN-speed=[100|10]; # where N is a unit number

For example
vfe0-duplex="full" vfe0-speed=100; # full-duplex 100Mbps for vfe0
vfe0-duplex="half" vfe0-speed=10; # half-duplex 10Mbps for vfe0

Q. The driver cannot be unloaded because the device is busy, and the following
message appears in /var/adm/messages file:
NOTICE: vfeN: vfe_detach: buffer is busy

A. Wait for a little while until some modules in the kernel release receive
buffers which were allocated by the vfe driver.

Q. The system does not boot after the driver is installed.
A. Uninstall the NIC card and reboot solaris. Then, unregister the driver:
# rem_drv vfe

Or boot solaris with -a option and use /etc/system.novfe instead of
default [etc/system]. This inhibits loading the driver.

/etc/system.novfe is automatically generated when executing 'make install'
or 'make test'

Q. Solaris boots, but the network interface does not work.
A. Is the network interface running?

Execute 'ifconfig -a'. If you see an entry for vfeN, the driver is loaded
and working correctly.
Please check the configuration of the network interface.


Is an ethernet cable connected properly?

Please check if the network interface is receiving packets.
% snoop -P -d vfeN

If Solaris panics while testing, please send me the following information:
(1) /var/adm/messages

(2) Output of prtconf -pv

(3) Output of prtconf -vD

(4) Output of adb
Solaris core dump consists of unix.N and vmcore.N which are created in
/var/crash/YOUR-HOST-NAME/ .

Execute 'adb -k unix.N vmcore.N' and type the following subcommands.
$c (stack trace back will be printed)
$<msgbuf (last messages are printed)
^D (To quit adb, type control-D)

jlliagre 11-06-2006 01:27 AM
Quote:
Originally Posted by hermouche
Yes jlliagre, I've downloaded the file and I tried to follow the README txt but i am in trouble.
how to install it?
The installation is explained with many details in the readme you posted.
In what step are you in trouble ?

hermouche 11-06-2006 09:43 AM
Quote:
Originally Posted by jlliagre
The installation is explained with many details in the readme you posted.
In what step are you in trouble ?
Ok you are patient, Thanks.

In step 3: is there any manner on how to edit the hosts?
In step 7: rm...... is OK
ls .......is OK
/usr/ccs/bin/make can't do it
/usr/ccs/make install i couldn't do it!!

the install process also?

so i stopped mainly si far in /usr/ccs/bin/make command.
I didn't go through the testing process.
red

jlliagre 11-06-2006 10:08 AM
Quote:
Originally Posted by hermouche
In step 3: is there any manner on how to edit the hosts?
My choice would be:
Code:
vi /etc/hosts
Quote:
In step 7: rm...... is OK
ls .......is OK
/usr/ccs/bin/make can't do it
/usr/ccs/make install i couldn't do it!!
If by "can't/couldn't do it" you mean you got a "command not found" error message, that mean you haven't installed some required packages because you choose an end user vs developer or full install at installation time.
You need to add the developer packages from the cd or dvd-rom: SUNWhea, SUNWsprot and probably a couple more, or just reinstall with choosing the full install option, which may be simpler if you don't mind loosing what you have done up to now.

hermouche 11-06-2006 10:10 PM
yes, i think i should reinstall it, because i will not be able to recognize and to install what is needed.

Thanks
red

Antonin 12-14-2006 11:49 PM
Hello all,

I am also trying to install (but 2 years after you !) Solaris 10 on my computer.

I have the same NIC, but when I go into the testing part indicated in the readme file, it gives me an error :

"can't load module: No such file or directory"

When I ceck, there is actually a file named vfe in the obj directory...

I have rebooted twice the PC, but nothing better.

Thanks for your help :)

I'm a :newbie:

stimpyjcat 02-08-2007 04:20 PM
same problem
 
Quote:
Originally Posted by Antonin
Hello all,

I am also trying to install (but 2 years after you !) Solaris 10 on my computer.

I have the same NIC, but when I go into the testing part indicated in the readme file, it gives me an error :

"can't load module: No such file or directory"

When I ceck, there is actually a file named vfe in the obj directory...

I have rebooted twice the PC, but nothing better.

Thanks for your help :)

I'm a :newbie:
mmm... i have exactly the same problem with the vfe drivers, dunno if modload has bugs or something


All times are GMT -5. The time now is 04:31 PM.