No video signal after POST

[keitalbame]

Hi all

I have a HP Microserver N54L on FreeNAS-9.2.1.9-RELEASE-x64, with 16GB ECC RAM.

Since the begining, I'm unable to see nothing after POST. I'm able to enter BIOS a change configurations but after that, nothing.
FreeNAS config menu does not appear.

I firstly install to the USB on my laptop and somehow, I was able to configure the NIC to receive an ip automatically and after that I'm doing all configuration via webadmin.

Now I want to update to 9.3 but don't want to risk on doing that and something goes wrong and I'm unable to access my files.

Do you think this could be problem with the AMD video driver, monitor driver or some other configuration?


I only have a Tandberg 1700 as monitor (connecting with VGA cable). This works ok with all my laptops. This are the supported resolutions:

Input: 800 x 600 (@ 60, 72, 75, 85 Hz), 1024 x 768 (@ 60, 70, 75 Hz), 1280 x 720 (HD720P) (@ 50, 60 Hz), 1280 x 1024 @ 60/Hz, 1280x768, 1280x800, 1360x768, 1366x768 (@60 Hz)
Output: 1280x800 @ 60 Hz

More info: http://www.cisco.com/c/en/us/produc...ce-system-1700-mxp/data_sheet_c78-628615.html

I already tried to find something related with this but ended with nothing similar. Any help would be appreciated.


Some info from the server. At the moment I don't have the monitor connected but if it helps, please let me know and I will add more information with it.

vgapci0@pci0:1:5:0: class=0x030000 card=0x1609103c chip=0x97121002 rev=0x00 hdr=0x00
vendor = 'ATI Technologies Inc'
device = 'M880G [Mobility Radeon HD 4200]'
class = display
subclass = VGA

Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.2-RELEASE-p15 #0 r262572+5b7d179: Mon Nov 17 16:27:51 PST 2014
root@build3.ixsystems.com:/tank/home/jkh/build/921/FN/os-base/amd64/fusion/jkh/921/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: AMD Turion(tm) II Neo N54L Dual-Core Processor (2196.39-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x100f63 Family = 0x10 Model = 0x6 Stepping = 3
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x802009<SSE3,MON,CX16,POPCNT>
AMD Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!>
AMD Features2=0x837ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,NodeId>
TSC: P-state invariant
real memory = 17179869184 (16384 MB)
avail memory = 16496680960 (15732 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <HP ProLiant>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic0 <Version 2.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: No AESNI support.
padlock0: No ACE support.
acpi0: <HP ProLiant> on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of fee00000, 1000 (3) failed
acpi0: reservation of ffb80000, 80000 (3) failed
acpi0: reservation of fec10000, 20 (3) failed
acpi0: reservation of fed80000, 1000 (3) failed
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, ddf00000 (3) failed
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 450
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xe000-0xe0ff mem 0xfc000000-0xfdffffff,0xfe8f0000-0xfe8fffff,0xfe700000-0xfe7fffff irq 18 at device 5.0 on pci1
pcib2: <ACPI PCI-PCI bridge> irq 18 at device 6.0 on pci0
pci2: <ACPI PCI bus> on pcib2
bge0: <HP NC107i PCIe Gigabit Server Adapter, ASIC rev. 0x5784100> mem 0xfe9f0000-0xfe9fffff irq 18 at device 0.0 on pci2
bge0: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E
miibus0: <MII bus> on bge0
brgphy0: <BCM5784 10/100/1000baseT PHY> PHY 1 on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Ethernet address: 28:92:4a:34:4b:18
ahci0: <ATI IXP700 AHCI SATA controller> port 0xd000-0xd007,0xc000-0xc003,0xb000-0xb007,0xa000-0xa003,0x9000-0x900f mem 0xfe6ffc00-0xfe6fffff irq 19 at device 17.0 on pci0
ahci0: AHCI v1.20 with 4 3Gbps ports, Port Multiplier supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fe000-0xfe6fefff irq 18 at device 18.0 on pci0
usbus0 on ohci0
ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff800-0xfe6ff8ff irq 17 at device 18.2 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fd000-0xfe6fdfff irq 18 at device 19.0 on pci0
usbus2 on ohci1
ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff400-0xfe6ff4ff irq 17 at device 19.2 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci1
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci0: <ATI IXP700/800 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0
ata0: <ATA channel> at channel 0 on atapci0
ata1: <ATA channel> at channel 1 on atapci0
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib3: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci3: <ACPI PCI bus> on pcib3
ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe6fc000-0xfe6fcfff irq 18 at device 22.0 on pci0
usbus4 on ohci2
ehci2: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe6ff000-0xfe6ff0ff irq 17 at device 22.2 on pci0
usbus5: EHCI version 1.0
usbus5 on ehci2
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb4
acpi_button0: <Power Button> on acpi0
amdsbwd0: <AMD SB8xx Watchdog Timer> at iomem 0xfec000f0-0xfec000f3,0xfec000f4-0xfec000f7 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0

 

[BigDave]

Since the begining, I'm unable to see nothing after POST. I'm able to enter BIOS a change configurations but after that, nothing.

Check onboard display chipset settings in the BIOS. Sounds like you might need to just turn on the VGA port
as your primary graphics output source.

 

[cyberjock]

And if that doesn't work, it sounds like a hardware problem of some kind. You should at least get past POST to the basic boot menus for FreeNAS (or any OS for that matter). If you aren't, that sounds like hardware. But, it's probably just misconfigured BIOS settings somewhere.

 

[rogerh]

Unlike 9.2 you can't just copy an OS image of 9.3 to a USB stick and boot it in another computer. It actually needs installing and I doubt if installing it on one computer and booting it in another would work. By the way, you haven't got an HP remote management card plugged into the first PCIe slot, have you?

 

[danb35]

It actually needs installing and I doubt if installing it on one computer and booting it in another would work.

Installing 9.3 on one computer and booting it on another works just fine, and there's no reason to believe it wouldn't. The reason the installer is needed is to properly create the ZFS boot volume--it doesn't do anything specific to the hardware it's being installed on.

 

[rogerh]

Installing 9.3 on one computer and booting it on another works just fine, and there's no reason to believe it wouldn't. The reason the installer is needed is to properly create the ZFS boot volume--it doesn't do anything specific to the hardware it's being installed on.

That's good to know. So it installs all the drivers etc, not just the ones the hardware it is installed on needs?

 

[Ericloewe]

Drivers aren't installed per se. Drivers are compiled with the OS and loaded as-needed.

 

[keitalbame]

Hi all

Unfortunatly I don't have IPMI, to be able to connect remotly.

I went to confirm on the BIOS and the VGA is enabled. I was able to enter the BIOS and change settings since the begining.
At the moment I changed the video memory available from 32MB to 512MB (just to test) and I have the same issue. I can see POST but when FreeNAS starts to load, nothing is displayed and a OSD message "Unsupported VGA Input" is displayed.
I don't have other monitor to test but I believe that this could be some resolution range/refresh/..., that the monitor is not able to handle.
When I bought the server, I was able to install Windows and Ubuntu (for testing) and it was working ok on the GUI side, although some fases of the boot weren't displayed at all.

Any other suggestion? I have the monitor plugged on the server. Let me know if additional information can help.

Thanks

 

[Darren Myers]

Hi all

Unfortunatly I don't have IPMI, to be able to connect remotly.

I went to confirm on the BIOS and the VGA is enabled. I was able to enter the BIOS and change settings since the begining.
At the moment I changed the video memory available from 32MB to 512MB (just to test) and I have the same issue. I can see POST but when FreeNAS starts to load, nothing is displayed and a OSD message "Unsupported VGA Input" is displayed.
I don't have other monitor to test but I believe that this could be some resolution range/refresh/..., that the monitor is not able to handle.
When I bought the server, I was able to install Windows and Ubuntu (for testing) and it was working ok on the GUI side, although some fases of the boot weren't displayed at all.

Any other suggestion? I have the monitor plugged on the server. Let me know if additional information can help.

Thanks

Do you have a cheapie graphics card floating around you could plug in just for testing purposes? If the Micro server has a slot for it of course

 

[keitalbame]

Do you have a cheapie graphics card floating around you could plug in just for testing purposes? If the Micro server has a slot for it of course

No, I don't have any spare video card at the moment but I will check for a cheaper one.

Any advice on the model? I belive Nvidia should have the best support on the kernel right? I would prefer Intel for that but I believe there's none besides onboard...

 

[Ericloewe]

No, I don't have any spare video card at the moment but I will check for a cheaper one.

Any advice on the model? I belive Nvidia should have the best support on the kernel right? I would prefer Intel for that but I believe there's none besides onboard...

Completely and utterly irrelevant. It'll be used in text mode, supported by every graphics card since the original VGA.

 

[rogerh]

Very limited and inconclusive research suggests that it may be booting (grub and then FreeBSD) into 640 x 480, which doesn't seem to be something your monitor supports. Two solutions are either get a cheap second had flat screen monitor which supports this, which is probably all very old ones. Or SSH (or use the shell window in the GUI) and edit the relevant grub files (I am afraid I am a bit lost with grub2 - but the method is easily found on Google) to start in a different VGA resolution. Grub can pass this on to Linux and I expect the same is true of FreeNAS. It is highly possible that FreeNAS updates will re-install grub and change this, though. I hope just rebooting won't, it depends which bit of grub you need to edit. It does seem to occupy acres of disk space nowadays that is not accessible to the OS.