Re: Need help getting FreeBSD to run

2003-03-31 Thread Paharenko Gleb
Try to recompile your kernel with device rdp or rl
look at LINT there is a big section wich describes RealTek
RedHat found it becouse when it boots
it load modules for support hardware
If it does'n work try to port driver from
linux to FreeBSD
it isn't very difficult



On Mon, 31 Mar 2003, Mike Doyle wrote:

> I'm having a little problem with my ISP. They said they would lease me a new
> rack-mounted server and put FreeBSD on to it. However, they were unable to
> get it to recognize certain parts of the hardware (specifically getting errors
> on the network cards not being initialized correctly).
>
> In the end, they installed RedHat on the machine, since their main techie
> is a Linux fan. I have the dmesg ouput from RedHat. If there is anyone on the
> list who is familiar with both RedHat and with FreeBSD, could you look at this
> output and tell me what if any hardware is non-standard and/or unsupported
> by FreeBSD ? Will FreeBSD 4.7, 4.8 or 5.0 run on this kit ? Would it need a
> custom kernel ?
>
> I don't have physical access to the hardware at the moment, and the dmesg
> below is the most accurate technical description of the hardware that I have
> (other than its a 1u rackmounted server, celeron processor, ide hard drive)
>
>
> ---
>
> Linux version 2.4.18-26.7.xsmp ([EMAIL PROTECTED]) (gcc
> version 2.96 2731 (Red Hat Linux 7.3 2.96-112)) #1 SMP Mon Feb 24
> 09:37:16 EST 2003
> BIOS-provided physical RAM map:
>   BIOS-e820:  - 0009fc00 (usable)
>   BIOS-e820: 0009fc00 - 000a (reserved)
>   BIOS-e820: 000f - 0010 (reserved)
>   BIOS-e820: 0010 - 1dffc000 (usable)
>   BIOS-e820: 1dffc000 - 1dfff000 (ACPI data)
>   BIOS-e820: 1dfff000 - 1e00 (ACPI NVS)
>   BIOS-e820: fec0 - fec01000 (reserved)
>   BIOS-e820: fee0 - fee01000 (reserved)
>   BIOS-e820:  - 0001 (reserved)
> 0MB HIGHMEM available.
> 479MB LOWMEM available.
> On node 0 totalpages: 122876
> zone(0): 4096 pages.
> zone(1): 118780 pages.
> zone(2): 0 pages.
> Kernel command line: ro root=/dev/hda3
> Found and enabled local APIC!
> Initializing CPU#0
> Detected 1693.127 MHz processor.
> Speakup v-1.00 CVS: Tue Jun 11 14:22:53 EDT 2002 : initialized
> Console: colour VGA+ 80x25
> Calibrating delay loop... 3357.88 BogoMIPS
> Memory: 478716k/491504k available (1281k kernel code, 10224k reserved,
> 1073k data, 188k init, 0k highmem)
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
> Mount cache hash table entries: 8192 (order: 4, 65536 bytes)
> ramfs: mounted with options: 
> ramfs: max_pages=60111 max_file_pages=0 max_inodes=0 max_dentries=60111
> Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
> Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
> CPU: Before vendor init, caps: 3febfbff  , vendor = 0
> CPU: L1 I cache: 0K, L1 D cache: 8K
> CPU: Hyper-Threading is disabled
> CPU: After vendor init, caps: 3febfbff   
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> CPU: After generic, caps: 3febfbff   
> CPU: Common caps: 3febfbff   
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.40 (20010327) Richard Gooch ([EMAIL PROTECTED])
> mtrr: detected mtrr type: Intel
> CPU: Before vendor init, caps: 3febfbff  , vendor = 0
> CPU: L1 I cache: 0K, L1 D cache: 8K
> CPU: Hyper-Threading is disabled
> CPU: After vendor init, caps: 3febfbff   
> Intel machine check reporting enabled on CPU#0.
> CPU: After generic, caps: 3febfbff   
> CPU: Common caps: 3febfbff   
> CPU0: Intel(R) Celeron(R) CPU 1.70GHz stepping 03
> per-CPU timeslice cutoff: 22.85 usecs.
> task migration cache decay timeout: 1 msecs.
> SMP motherboard not detected.
> enabled ExtINT on CPU#0
> ESR value before enabling vector: 
> ESR value after enabling vector: 
> Using local APIC timer interrupts.
> calibrating APIC timer ...
> . CPU clock speed is 1692.1653 MHz.
> . host bus clock speed is 99.1130 MHz.
> cpu: 0, clocks: 194477, slice: 97238
> CPU0
> migration_task 0 on cpu=0
> PCI: PCI BIOS revision 2.10 entry at 0xf1150, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Using IRQ router default [1039/0962] at 00:02.0
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> speakup:  initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> I

Re: Need help getting FreeBSD to run

2003-03-31 Thread taxman
On Monday 31 March 2003 07:02 am, Mike Doyle wrote:
> I'm having a little problem with my ISP. They said they would lease me a
> new rack-mounted server and put FreeBSD on to it. However, they were unable
> to get it to recognize certain parts of the hardware (specifically getting
> errors on the network cards not being initialized correctly).

barring a more informed opinion, it seems that there is no support for that 
ethernet chipset on FreeBSD.  It is not listed on 
http://www.freebsd.org/releases/4.7R/hardware-i386.html
My guess is that the rest of that hardware will run fine with FreeBSD, but 
unless you get the FreeBSD dmesg for us I wouldn't know.  They can get you 
the FreeBSD dmesg if they get the rescue floppy and use that after booting 
from the install disk.  Then they can save the dmesg to floppy or whatever.

beyond that, you'd need to either have them put new network cards in the 
server, or you'd have to port the linux driver, or pay to have it done.

sorry,
Tim

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Need help getting FreeBSD to run

2003-04-01 Thread Scott Mitchell
On Mon, Mar 31, 2003 at 01:02:51PM +0100, Mike Doyle wrote:
> sis900.c: v1.08.06 9/24/2002
> divert: allocating divert_blk for eth0
> eth0: Realtek RTL8201 PHY transceiver found at address 1.
> eth0: Using transceiver found at address 1 as default
> eth0: SiS 900 PCI Fast Ethernet at 0x8800, IRQ 12, 00:e0:18:d8:b4:2a.
> eth0: Media Link On 100mbps full-duplex

Mike,

It looks like you have a SiS 900 Ethernet controller there, with a RealTek
PHY attached.  The SiS 900 is supposedly supported by the 'sis' driver,
which seems to be in the generic kernel config.  The 'miibus' driver knows
about a RealTek PHY8201L PHY, which may or may not be the same one you have
there.  It seems like this combination *should* work, but maybe this is a
strange configuration that the sis driver can't cope with.

Is there any chance you can get the so-called experts at your ISP to boot
FreeBSD on this box again and give you some more information on what's
actually going wrong?  ie, commands they're trying, error messages they're
getting, etc.

Cheers,

Scott

-- 
===
Scott Mitchell   | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England   | 0x54B171B9 |  don't get sucked into jet engines"
scott at fishballoon.org | 0xAA775B8B |  -- Anon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"