This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!


I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!

After upgrading to 11.2 the terminal resolution is 640x480

XigmaNAS Basic Tune-up
Forum rules
• Set-Up Guide • FAQs • Forum Rules
Post Reply
guilhermerrrr
NewUser
NewUser
Posts: 3
Joined: 26 Jun 2018 23:02
Status: Offline

After upgrading to 11.2 the terminal resolution is 640x480

Post by guilhermerrrr »

Hello, I downloaded the new version of XigmaNAS, I was using nas4free 11.01 before, I had some problems with the GUI upgrade and I had to do the installation from scratch. I made a backup before it :idea: me... very... smart... (for once hehe)
I installed an embedded version of the OS on a hard drive.

The problem is when booting, the terminal changes its resolution to 640x480 and is very difficult to read, I don't remember the exact res. I was using with version 11.01, but for sure it was not this one
Here is the log (I don't know which part is important so I pasted the whole thing, but I guess is the line where says VT(vga): resolution 640x480)

Code: Select all

Jul 18 20:03:04	syslogd:	kernel boot file is /boot/kernel/kernel
Jul 18 20:03:04	kernel:	Waiting (max 60 seconds) for system process `vnlru' to stop... done
Jul 18 20:03:04	kernel:	Waiting (max 60 seconds) for system process `bufdaemon' to stop... done
Jul 18 20:03:04	kernel:	Waiting (max 60 seconds) for system process `syncer' to stop...
Jul 18 20:03:04	kernel:	Syncing disks, vnodes remaining... 0 0 done
Jul 18 20:03:04	kernel:	All buffers synced.
Jul 18 20:03:04	kernel:	Copyright (c) 1992-2018 The FreeBSD Project.
Jul 18 20:03:04	kernel:	Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Jul 18 20:03:04	kernel:	The Regents of the University of California. All rights reserved.
Jul 18 20:03:04	kernel:	FreeBSD is a registered trademark of The FreeBSD Foundation.
Jul 18 20:03:04	kernel:	FreeBSD 11.2-RELEASE #0 r336227M: Thu Jul 12 21:48:47 CEST 2018
Jul 18 20:03:04	kernel:	root@dev.xigmanas.com:/usr/obj/xigmanas/usr/src/sys/XIGMANAS-amd64 amd64
Jul 18 20:03:04	kernel:	FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
[b]Jul 18 20:03:04	kernel:	VT(vga): resolution 640x480[/b]
Jul 18 20:03:04	kernel:	CPU: Intel(R) Pentium(R) CPU G3260 @ 3.30GHz (3292.44-MHz K8-class CPU)
Jul 18 20:03:04	kernel:	Origin="GenuineIntel" Id=0x306c3 Family=0x6 Model=0x3c Stepping=3
Jul 18 20:03:04	kernel:	Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Jul 18 20:03:04	kernel:	Features2=0x4ddaebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,XSAVE,OSXSAVE,RDRAND>
Jul 18 20:03:04	kernel:	AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
Jul 18 20:03:04	kernel:	AMD Features2=0x21<LAHF,ABM>
Jul 18 20:03:04	kernel:	Structured Extended Features=0x2603<FSGSBASE,TSCADJ,ERMS,INVPCID,NFPUSG>
Jul 18 20:03:04	kernel:	XSAVE Features=0x1<XSAVEOPT>
Jul 18 20:03:04	kernel:	VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Jul 18 20:03:04	kernel:	TSC: P-state invariant, performance statistics
Jul 18 20:03:04	kernel:	real memory = 8589934592 (8192 MB)
Jul 18 20:03:04	kernel:	avail memory = 7990837248 (7620 MB)
Jul 18 20:03:04	kernel:	Event timer "LAPIC" quality 600
Jul 18 20:03:04	kernel:	ACPI APIC Table: <ALASKA A M I>
Jul 18 20:03:04	kernel:	FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Jul 18 20:03:04	kernel:	FreeBSD/SMP: 1 package(s) x 2 core(s)
Jul 18 20:03:04	kernel:	WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Jul 18 20:03:04	kernel:	ioapic0 <Version 2.0> irqs 0-23 on motherboard
Jul 18 20:03:04	kernel:	SMP: AP CPU #1 Launched!
Jul 18 20:03:04	kernel:	Timecounter "TSC-low" frequency 1646219710 Hz quality 1000
Jul 18 20:03:04	kernel:	random: entropy device external interface
Jul 18 20:03:04	kernel:	md0: Preloaded image </mfsroot> 134217728 bytes at 0xffffffff828a0328
Jul 18 20:03:04	kernel:	kbd1 at kbdmux0
Jul 18 20:03:04	kernel:	netmap: loaded module
Jul 18 20:03:04	kernel:	module_register_init: MOD_LOAD (vesa, 0xffffffff81194e10, 0) error 19
Jul 18 20:03:04	kernel:	random: registering fast source Intel Secure Key RNG
Jul 18 20:03:04	kernel:	random: fast provider: "Intel Secure Key RNG"
Jul 18 20:03:04	kernel:	nexus0
Jul 18 20:03:04	kernel:	vtvga0: <VT VGA driver> on motherboard
Jul 18 20:03:04	kernel:	cryptosoft0: <software crypto> on motherboard
Jul 18 20:03:04	kernel:	acpi0: <ALASKA A M I> on motherboard
Jul 18 20:03:04	kernel:	acpi0: Power Button (fixed)
Jul 18 20:03:04	kernel:	cpu0: <ACPI CPU> on acpi0
Jul 18 20:03:04	kernel:	cpu1: <ACPI CPU> on acpi0
Jul 18 20:03:04	kernel:	hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Jul 18 20:03:04	kernel:	Timecounter "HPET" frequency 14318180 Hz quality 950
Jul 18 20:03:04	kernel:	Event timer "HPET" frequency 14318180 Hz quality 550
Jul 18 20:03:04	kernel:	Event timer "HPET1" frequency 14318180 Hz quality 440
Jul 18 20:03:04	kernel:	Event timer "HPET2" frequency 14318180 Hz quality 440
Jul 18 20:03:04	kernel:	Event timer "HPET3" frequency 14318180 Hz quality 440
Jul 18 20:03:04	kernel:	Event timer "HPET4" frequency 14318180 Hz quality 440
Jul 18 20:03:04	kernel:	Event timer "HPET5" frequency 14318180 Hz quality 440
Jul 18 20:03:04	kernel:	Event timer "HPET6" frequency 14318180 Hz quality 440
Jul 18 20:03:04	kernel:	atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
Jul 18 20:03:04	kernel:	atrtc0: Warning: Couldn't map I/O.
Jul 18 20:03:04	kernel:	atrtc0: registered as a time-of-day clock, resolution 1.000000s
Jul 18 20:03:04	kernel:	Event timer "RTC" frequency 32768 Hz quality 0
Jul 18 20:03:04	kernel:	attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Jul 18 20:03:04	kernel:	Timecounter "i8254" frequency 1193182 Hz quality 0
Jul 18 20:03:04	kernel:	Event timer "i8254" frequency 1193182 Hz quality 100
Jul 18 20:03:04	kernel:	Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Jul 18 20:03:04	kernel:	acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
Jul 18 20:03:04	kernel:	pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Jul 18 20:03:04	kernel:	pcib0: _OSC returned error 0x10
Jul 18 20:03:04	kernel:	pci0: <ACPI PCI bus> on pcib0
Jul 18 20:03:04	kernel:	pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
Jul 18 20:03:04	kernel:	pci1: <ACPI PCI bus> on pcib1
Jul 18 20:03:04	kernel:	vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
Jul 18 20:03:04	kernel:	vgapci0: Boot video device
Jul 18 20:03:04	kernel:	xhci0: <Intel Lynx Point USB 3.0 controller> mem 0xf7d00000-0xf7d0ffff irq 21 at device 20.0 on pci0
Jul 18 20:03:04	kernel:	xhci0: 32 bytes context size, 64-bit DMA
Jul 18 20:03:04	kernel:	xhci0: Port routing mask set to 0xffffffff
Jul 18 20:03:04	kernel:	usbus0 on xhci0
Jul 18 20:03:04	kernel:	usbus0: 5.0Gbps Super Speed USB v3.0
Jul 18 20:03:04	kernel:	pci0: <simple comms> at device 22.0 (no driver attached)
Jul 18 20:03:04	kernel:	ehci0: <Intel Lynx Point USB 2.0 controller USB-B> mem 0xf7d18000-0xf7d183ff irq 20 at device 26.0 on pci0
Jul 18 20:03:04	kernel:	usbus1: EHCI version 1.0
Jul 18 20:03:04	kernel:	usbus1 on ehci0
Jul 18 20:03:04	kernel:	usbus1: 480Mbps High Speed USB v2.0
Jul 18 20:03:04	kernel:	hdac0: <Intel Lynx Point HDA Controller> mem 0xf7d10000-0xf7d13fff irq 22 at device 27.0 on pci0
Jul 18 20:03:04	kernel:	pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
Jul 18 20:03:04	kernel:	pcib2: [GIANT-LOCKED]
Jul 18 20:03:04	kernel:	pcib3: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
Jul 18 20:03:04	kernel:	pci2: <ACPI PCI bus> on pcib3
Jul 18 20:03:04	kernel:	re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xe000-0xe0ff mem 0xf7c00000-0xf7c00fff,0xf0000000-0xf0003fff irq 18 at device 0.0 on pci2
Jul 18 20:03:04	kernel:	re0: Using 1 MSI-X message
Jul 18 20:03:04	kernel:	re0: ASPM disabled
Jul 18 20:03:04	kernel:	re0: Chip rev. 0x4c000000
Jul 18 20:03:04	kernel:	re0: MAC rev. 0x00000000
Jul 18 20:03:04	kernel:	miibus0: <MII bus> on re0
Jul 18 20:03:04	kernel:	rgephy0: <RTL8251 1000BASE-T media interface> PHY 1 on miibus0
Jul 18 20:03:04	kernel:	rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
Jul 18 20:03:04	kernel:	re0: Using defaults for TSO: 65518/35/2048
Jul 18 20:03:04	kernel:	re0: Ethernet address: 38:d5:47:28:1d:26
Jul 18 20:03:04	kernel:	re0: netmap queues/slots: TX 1/256, RX 1/256
Jul 18 20:03:04	kernel:	ehci1: <Intel Lynx Point USB 2.0 controller USB-A> mem 0xf7d17000-0xf7d173ff irq 23 at device 29.0 on pci0
Jul 18 20:03:04	kernel:	usbus2: EHCI version 1.0
Jul 18 20:03:04	kernel:	usbus2 on ehci1
Jul 18 20:03:04	kernel:	usbus2: 480Mbps High Speed USB v2.0
Jul 18 20:03:04	kernel:	isab0: <PCI-ISA bridge> at device 31.0 on pci0
Jul 18 20:03:04	kernel:	isa0: <ISA bus> on isab0
Jul 18 20:03:04	kernel:	ahci0: <Intel Lynx Point AHCI SATA controller> port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7d16000-0xf7d167ff irq 19 at device 31.2 on pci0
Jul 18 20:03:04	kernel:	ahci0: AHCI v1.30 with 4 6Gbps ports, Port Multiplier not supported
Jul 18 20:03:04	kernel:	ahcich0: <AHCI channel> at channel 0 on ahci0
Jul 18 20:03:04	kernel:	ahcich1: <AHCI channel> at channel 1 on ahci0
Jul 18 20:03:04	kernel:	ahcich5: <AHCI channel> at channel 5 on ahci0
Jul 18 20:03:04	kernel:	ahciem0: <AHCI enclosure management bridge> on ahci0
Jul 18 20:03:04	kernel:	acpi_button0: <Power Button> on acpi0
Jul 18 20:03:04	kernel:	acpi_tz0: <Thermal Zone> on acpi0
Jul 18 20:03:04	kernel:	acpi_tz1: <Thermal Zone> on acpi0
Jul 18 20:03:04	kernel:	atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
Jul 18 20:03:04	kernel:	atkbd0: <AT Keyboard> irq 1 on atkbdc0
Jul 18 20:03:04	kernel:	kbd0 at atkbd0
Jul 18 20:03:04	kernel:	atkbd0: [GIANT-LOCKED]
Jul 18 20:03:04	kernel:	ppc0: cannot reserve I/O port range
Jul 18 20:03:04	kernel:	coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Jul 18 20:03:04	kernel:	est0: <Enhanced SpeedStep Frequency Control> on cpu0
Jul 18 20:03:04	kernel:	p4tcc0: <CPU Frequency Thermal Control> on cpu0
Jul 18 20:03:04	kernel:	coretemp1: <CPU On-Die Thermal Sensors> on cpu1
Jul 18 20:03:04	kernel:	est1: <Enhanced SpeedStep Frequency Control> on cpu1
Jul 18 20:03:04	kernel:	p4tcc1: <CPU Frequency Thermal Control> on cpu1
Jul 18 20:03:04	kernel:	ZFS filesystem version: 5
Jul 18 20:03:04	kernel:	ZFS storage pool version: features support (5000)
Jul 18 20:03:04	kernel:	Timecounters tick every 1.000 msec
Jul 18 20:03:04	kernel:	iSCSI boot driver version 0.2.13
Jul 18 20:03:04	kernel:	hdacc0: <Realtek ALC887 HDA CODEC> at cad 0 on hdac0
Jul 18 20:03:04	kernel:	hdaa0: <Realtek ALC887 Audio Function Group> at nid 1 on hdacc0
Jul 18 20:03:04	kernel:	pcm0: <Realtek ALC887 (Rear Analog)> at nid 20 and 24,26 on hdaa0
Jul 18 20:03:04	kernel:	pcm1: <Realtek ALC887 (Front Analog)> at nid 27 and 25 on hdaa0
Jul 18 20:03:04	kernel:	pcm2: <Realtek ALC887 (Internal Digital)> at nid 17 on hdaa0
Jul 18 20:03:04	kernel:	ugen1.1: <Intel EHCI root HUB> at usbus1
Jul 18 20:03:04	kernel:	ugen2.1: <Intel EHCI root HUB> at usbus2
Jul 18 20:03:04	kernel:	uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Jul 18 20:03:04	kernel:	uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
Jul 18 20:03:04	kernel:	ugen0.1: <0x8086 XHCI root HUB> at usbus0
Jul 18 20:03:04	kernel:	uhub2: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Jul 18 20:03:04	kernel:	uhub2: 17 ports with 17 removable, self powered
Jul 18 20:03:04	kernel:	uhub1: 2 ports with 2 removable, self powered
Jul 18 20:03:04	kernel:	uhub0: 2 ports with 2 removable, self powered
Jul 18 20:03:04	kernel:	ugen2.2: <vendor 0x8087 product 0x8000> at usbus2
Jul 18 20:03:04	kernel:	uhub3 on uhub1
Jul 18 20:03:04	kernel:	uhub3: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.05, addr 2> on usbus2
Jul 18 20:03:04	kernel:	ugen1.2: <vendor 0x8087 product 0x8008> at usbus1
Jul 18 20:03:04	kernel:	uhub4 on uhub0
Jul 18 20:03:04	kernel:	uhub4: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.05, addr 2> on usbus1
Jul 18 20:03:04	kernel:	uhub4: 4 ports with 4 removable, self powered
Jul 18 20:03:04	kernel:	uhub3: 6 ports with 6 removable, self powered
Jul 18 20:03:04	kernel:	ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Jul 18 20:03:04	kernel:	ada0: <WDC WD5000AAKX-003CA0 15.01H15> ATA8-ACS SATA 3.x device
Jul 18 20:03:04	kernel:	ada0: Serial Number WD-WCAYUM747900
Jul 18 20:03:04	kernel:	ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Jul 18 20:03:04	kernel:	ada0: Command Queueing enabled
Jul 18 20:03:04	kernel:	ada0: 476940MB (976773168 512 byte sectors)
Jul 18 20:03:04	kernel:	ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
Jul 18 20:03:04	kernel:	ada1: <ST1500DL003-9VT16L CC32> ATA8-ACS SATA 3.x device
Jul 18 20:03:04	kernel:	ada1: Serial Number 6YD166R0
Jul 18 20:03:04	kernel:	ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Jul 18 20:03:04	kernel:	ada1: Command Queueing enabled
Jul 18 20:03:04	kernel:	ada1: 1430799MB (2930277168 512 byte sectors)
Jul 18 20:03:04	kernel:	ada1: quirks=0x1<4K>
Jul 18 20:03:04	kernel:	ada2 at ahcich5 bus 0 scbus2 target 0 lun 0
Jul 18 20:03:04	kernel:	ada2: <ST500DM002-1BD142 KC45> ATA8-ACS SATA 3.x device
Jul 18 20:03:04	kernel:	ada2: Serial Number Z3TM5ZX3
Jul 18 20:03:04	kernel:	ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jul 18 20:03:04	kernel:	ada2: Command Queueing enabled
Jul 18 20:03:04	kernel:	ada2: 476938MB (976771055 512 byte sectors)
Jul 18 20:03:04	kernel:	ada2: quirks=0x1<4K>
Jul 18 20:03:04	kernel:	ses0 at ahciem0 bus 0 scbus3 target 0 lun 0
Jul 18 20:03:04	kernel:	ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
Jul 18 20:03:04	kernel:	ses0: SEMB SES Device
Jul 18 20:03:04	kernel:	Trying to mount root from ufs:/dev/md0 []...
Jul 18 20:03:04	kernel:	random: unblocking device.
Jul 18 20:03:04	kernel:	re0: link state changed to DOWN
Jul 18 20:03:04	kernel:	re0: link state changed to UP
Jul 18 20:03:18	proftpd[1914]:	192.168.0.15 - ProFTPD 1.3.6 (stable) (built Thu Jul 12 2018 23:41:01 CEST) standalone mode STARTUP
Jul 18 20:03:18	nmbd[1966]:	[2018/07/18 20:03:18.866939, 0] ../lib/util/become_daemon.c:138(daemon_ready)
Jul 18 20:03:18	nmbd[1966]:	daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Jul 18 20:03:18	nmbd[1966]:	[2018/07/18 20:03:18.867163, 0] ../source3/nmbd/nmbd_become_dmb.c:294(become_domain_master_browser_bcast)
Jul 18 20:03:18	nmbd[1966]:	become_domain_master_browser_bcast:
Jul 18 20:03:18	nmbd[1966]:	Attempting to become domain master browser on workgroup WORKGROUP on subnet 192.168.0.15
Jul 18 20:03:18	nmbd[1966]:	[2018/07/18 20:03:18.867235, 0] ../source3/nmbd/nmbd_become_dmb.c:307(become_domain_master_browser_bcast)
Jul 18 20:03:18	nmbd[1966]:	become_domain_master_browser_bcast: querying subnet 192.168.0.15 for domain master browser on workgroup WORKGROUP
Jul 18 20:03:19	smbd[1969]:	[2018/07/18 20:03:19.110144, 0] ../lib/util/become_daemon.c:138(daemon_ready)
Jul 18 20:03:19	smbd[1969]:	daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Jul 18 20:03:19	smartd[2007]:	Device: /dev/ada1, 272 Currently unreadable (pending) sectors
Jul 18 20:03:19	smartd[2007]:	Device: /dev/ada1, 272 Offline uncorrectable sectors
Jul 18 20:03:21	lighttpd[2084]:	(server.c.1423) server started (lighttpd/1.4.49)
Jul 18 20:03:26	sudo:	root : TTY=ttyv0 ; PWD=/ ; USER=vboxusers ; COMMAND=/usr/local/bin/vboxmanage list vms
Jul 18 20:03:26	sudo:	root : TTY=ttyv0 ; PWD=/ ; USER=vboxusers ; COMMAND=/usr/local/bin/vboxmanage getextradata 31f9d85e-7ad2-4b56-b4d8-05b2e365963e pvbx/startupMode
Jul 18 20:03:26	sudo:	root : TTY=ttyv0 ; PWD=/ ; USER=vboxusers ; COMMAND=/usr/local/bin/vboxmanage getextradata ad288dc2-2448-4e8e-989c-8446012809ec pvbx/startupMode
Jul 18 20:03:26	sudo:	root : TTY=ttyv0 ; PWD=/ ; USER=vboxusers ; COMMAND=/usr/local/bin/vboxmanage showvminfo ad288dc2-2448-4e8e-989c-8446012809ec --machinereadable
Jul 18 20:03:26	sudo:	root : TTY=ttyv0 ; PWD=/ ; USER=vboxusers ; COMMAND=/usr/local/bin/vboxmanage startvm ad288dc2-2448-4e8e-989c-8446012809ec --type headless
Jul 18 20:03:26	kernel:	vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
Jul 18 20:03:26	kernel:	vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
Jul 18 20:03:26	kernel:	re0: promiscuous mode enabled
Jul 18 20:03:27	nmbd[1966]:	[2018/07/18 20:03:27.136024, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2)
Jul 18 20:03:27	nmbd[1966]:	*****
Jul 18 20:03:27	nmbd[1966]:	Samba server NAS4FREE is now a domain master browser for workgroup WORKGROUP on subnet 192.168.0.15
Jul 18 20:03:27	nmbd[1966]:	*****
Jul 18 20:03:29	lighttpd[2600]:	(server.c.1423) server started (lighttpd/1.4.49)
Jul 18 20:03:30	INADYN[2623]:	Wed Jul 18 20:03:30 2018: E:CACHE_LIST Failed opening cache file in ip_cache_list_read...
Jul 18 20:03:30	root:	onebuttoninstaller: started
Jul 18 20:03:30	root:	extended-gui: Saved Release: 11.1.0.4-5673 New Release: 11.2.0.4-5762 - new backup of standard GUI files!
Jul 18 20:03:30	root:	extended-gui: enabled, starting ...
Jul 18 20:03:32	root:	extended-gui: startup OK
Jul 18 20:03:32	lighttpd[2084]:	(server.c.2016) server stopped by UID = 0 PID = 2830
Jul 18 20:03:32	lighttpd[2872]:	(server.c.1423) server started (lighttpd/1.4.49)
Jul 18 20:03:32	root:	nextowncloud-extension: GUI loaded
Jul 18 20:03:33	plexinit:	script has been started successfully!
Jul 18 20:03:33	login:	login on ttyv0 as root
Jul 18 20:03:35	INADYN[2623]:	Wed Jul 18 20:03:35 2018: W:INADYN: IP address for alias 'coxinhanet.ddnsking.com:auto' needs update to '177.52.28.109'...
Jul 18 20:03:36	INADYN[2623]:	Wed Jul 18 20:03:36 2018: W:INADYN: Alias 'coxinhanet.ddnsking.com' to IP '177.52.28.109' updated successfully.
Jul 18 20:03:36	INADYN[2623]:	Wed Jul 18 20:03:36 2018: W:INADYN: DYNDNS Server response: HTTP/1.1 200 OK^M Content-Type: text/plain; charset=UTF-8^M Connection: close^M Cache-Control: private, must-revalidate^M pragma: no-cache^M expires: -1^M Date: Wed, 18 Jul 2018 23:03:36 GMT^M ^M nochg 177.52.28.109^M
Jul 18 20:03:39	sudo:	root : TTY=unknown ; PWD=/usr/local/www ; USER=vboxusers ; COMMAND=/usr/local/bin/VBoxManage list runningvms
Jul 18 20:03:39	sudo:	root : TTY=unknown ; PWD=/usr/local/www ; USER=vboxusers ; COMMAND=/usr/local/bin/VBoxManage showvminfo --machinereadable ad288dc2-2448-4e8e-989c-8446012809ec
Jul 18 20:03:42	nmbd[1966]:	[2018/07/18 20:03:42.178082, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Jul 18 20:03:42	nmbd[1966]:	*****
Jul 18 20:03:42	nmbd[1966]:	Samba name server NAS4FREE is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.15
Jul 18 20:03:42	nmbd[1966]:	*****
Jul 18 20:03:58	kernel:	re0: promiscuous mode disabled
Jul 18 20:04:06	kernel:	vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
Jul 18 20:04:20	kernel:	vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
Jul 18 20:04:20	kernel:	vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
Jul 18 20:04:20	kernel:	re0: promiscuous mode enabled
I tried to look for this problem but all I found was for older versions of FreeBSD so I don't know if they apply, I saw that this could be related to kernel configuration, UEFI...
I've been using nas4free for some time now, but i've never posted here, so I hope this is not a stupid question, I'll try to give as much information as I can.

Thank you
Guilherme
Top
jamaroney
Advanced User
Advanced User
Posts: 245
Joined: 13 Aug 2012 17:32
Location: Stroudsburg, PA
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by jamaroney »

I have the same situation with the new upgrade. I rarely use the terminal, but the new resolution does make for difficult reading.
Top
User avatar
raulfg3
Site Admin
Site Admin
Posts: 4865
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Contact raulfg3
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by raulfg3 »

Code: Select all

Changes after NAS4Free release 11.1.0.4.5673
===============================
- Changes to use our final name: XigmaNAS.
- Upgrade FreeBSD to 11.2-RELEASE-P0.
- Change syscons sc to vt virtual terminal console driver.
- Add UEFI support for Embedded and Full(UFS) platforms.
- Upgrade samba to 4.8.2.
- Upgrade php to 7.2.7.
- Upgrade iperf3 to 3.6.
- Upgrade msmtp to 1.6.8.
- Upgrade virtualbox-ose to 5.2.14.
- Fix export/import function phpvirtiualbox.
new vt syscon <- revise how to configure: https://www.freebsd.org/cgi/man.cgi?query=vt&sektion=4
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)

Wiki
Last changes

HP T510
Top
guilhermerrrr
NewUser
NewUser
Posts: 3
Joined: 26 Jun 2018 23:02
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by guilhermerrrr »

Thanks to point out the manual article, but if I read it correctly I need to change the kernel configurations. I have no idea how to do it.
I read this article: https://www.freebsd.org/doc/handbook/ke ... onfig.html (the pages 8.4 and 8.5), it explains that I have to download the FreeBSD source tree, make a copy of the Kernel configurations file inside the appropriate architecture folder I have, make the changes and then load the kernel (chapter 8.5), is that it?
I'll probably f everything up spectacularly and i'll need to read the chapter 8.6 (If Something Goes Wrong) :mrgreen:
Top
User avatar
ms49434
Developer
Developer
Posts: 828
Joined: 03 Sep 2015 18:49
Location: Neuenkirchen-Vörden, Germany - GMT+1
Contact:
Contact ms49434
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by ms49434 »

vt is the default console in FreeBSD. You can easily revert to sc, please read vt man pages provided by Raulfg3 again.
1) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 22GB out of 32GB ECC RAM, LSI 9300-8i IT mode in passthrough mode. Pool 1: 2x HGST 10TB, mirrored, L2ARC: Samsung 850 Pro; Pool 2: 1x Samsung 860 EVO 1TB, SLOG: Samsung SM883, services: Samba AD, CIFS/SMB, ftp, ctld, rsync, syncthing, zfs snapshots.
2) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 8GB out of 32GB ECC RAM, IBM M1215 crossflashed, IT mode, passthrough mode, 2x HGST 10TB , services: rsync.
Top
User avatar
JoseMR
Hardware & Software Guru
Hardware & Software Guru
Posts: 1058
Joined: 16 Apr 2014 04:15
Location: PR
Contact:
Contact JoseMR
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by JoseMR »

I thinks this has been previously posted some where, but people willing to roll back to old "SC" console driver follow below steeps:

On the WebGUI
1: Go to "System > Advanced > loader.conf" and click on the add [+] icon.
2: Add below configuration:
sc-console-revert.PNG
3: Click [Add] thebn click [Apply changes] and reboot.

That's all, but remember DO NOT set "SC" on EFI booting systems.

Regards
You do not have the required permissions to view the files attached to this post.
System: FreeBSD 12 RootOnZFS Mirror, MB: Supermicro X8SI6-F, Xeon X3450, 16GB DDR3 ECC RDIMMs.
XigmaNAS RootOnZFS
Addons at GitHub
BastilleBSD
Boot Environments Intro
Resources Home Page
Top
User avatar
Maurizio
Starter
Starter
Posts: 63
Joined: 05 Jul 2018 21:49
Location: Linate (MIlan)
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by Maurizio »

From the man page VT(4):

Code: Select all

To set a 1024x768 mode on all output connectors, put the following line in /boot/loader.conf:

	   kern.vt.fb.default_mode="1024x768"
In System > Advanced > loader.conf add a variable with name: kern.vt.fb.default_mode and value "1024x768"
XigmaNAS 12.1.0.4 on Dell R710 144GB RAM - RootOnZFS zroot on 2x 64GB 15k HDDs in mirror, zdata on 3x 1TB SSD in RAIDZ1.
2x XigmaNAS 11.2.0.4 - RootOnZFS on HPE Proliant Microserver gen10 X3216 - 3x 4TB WD RED. In mirror with zrep.
Top
User avatar
lux
Advanced User
Advanced User
Posts: 193
Joined: 23 Jun 2012 11:37
Location: Bielefeld, Germany
Contact:
Contact lux
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by lux »

@ Maurizio

doesnt work for me with 11.2...

theres no kern.vt.fb.default_mode Variable available

referred this website: http://lme.postach.io/post/changing-con ... -with-vt-4

i should load this Kernel Module: i915kms

but this resulted in the following error:

Code: Select all

kernel: linker_load_file: Unsupported file type
kernel: KLD i915kms.ko: depends on drmn - not available or version mismatch
Home:11.3.x.7538/emb@32GB USB|1270v2@X9SCA-F|ECC32GB|i340-T4[lagg@GS108Tv2&smb-mch]|M1015@IT|9HDD~40TB@3xRaidZ1+1HDD+2SSD i335&i520+1xi800P@ZIL|~44W idle@SS-400FL2|Nanoxia Deep Silence 6B|24/7
Services: CIFS, FTP, TFTP, SSH, NFS, Rsync, Syncthing, Webserver, BitTorrent, VirtualBox | Extensions: OBI, TheBrig[certbot, Asterisk] | Extensions via vBox: Pi-hole, Jellyfin & zigbee2mqtt @DebianVM's
Test:12.x/emb@16GB USB|X3 420e@M4A88TD-V|16GB|i350-T2|M1015@IT|8xHDD+3xSSD[different Size&Brand]RaidZ1+2|for TESTing only
Top
guilhermerrrr
NewUser
NewUser
Posts: 3
Joined: 26 Jun 2018 23:02
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by guilhermerrrr »

Tried loading
"kern.vt.fb.default_mode" "1024x768"
and also
"i915kms" "YES"

But they didn't work. I don't know if my system is booting EFI or BIOS (is there an easy way to know?) so I didn't use the @JoseMR 's tip
Top
User avatar
Maurizio
Starter
Starter
Posts: 63
Joined: 05 Jul 2018 21:49
Location: Linate (MIlan)
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by Maurizio »

@ lux and guilhermerrrr
from the shell at console give these 2 commands for loading the i915kms driver:

Code: Select all

# kldload drm2
# kldload i915kms
If the 915kms driver is loaded without error add the variables in loader.conf in this order:
Screenshot-2018-07-25-22-44-24.png
You do not have the required permissions to view the files attached to this post.
XigmaNAS 12.1.0.4 on Dell R710 144GB RAM - RootOnZFS zroot on 2x 64GB 15k HDDs in mirror, zdata on 3x 1TB SSD in RAIDZ1.
2x XigmaNAS 11.2.0.4 - RootOnZFS on HPE Proliant Microserver gen10 X3216 - 3x 4TB WD RED. In mirror with zrep.
Top
User avatar
lux
Advanced User
Advanced User
Posts: 193
Joined: 23 Jun 2012 11:37
Location: Bielefeld, Germany
Contact:
Contact lux
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by lux »

loading both Kernel Modules in you order works without any Error

BUT after adding these to loader.conf results in a fatal Kernel trap after reboot :geek:

i had to manually disable Kernel Modules at boot Console Menu Item (5) to get my System up'n running

i think this is not compatible with my IPMI...
Home:11.3.x.7538/emb@32GB USB|1270v2@X9SCA-F|ECC32GB|i340-T4[lagg@GS108Tv2&smb-mch]|M1015@IT|9HDD~40TB@3xRaidZ1+1HDD+2SSD i335&i520+1xi800P@ZIL|~44W idle@SS-400FL2|Nanoxia Deep Silence 6B|24/7
Services: CIFS, FTP, TFTP, SSH, NFS, Rsync, Syncthing, Webserver, BitTorrent, VirtualBox | Extensions: OBI, TheBrig[certbot, Asterisk] | Extensions via vBox: Pi-hole, Jellyfin & zigbee2mqtt @DebianVM's
Test:12.x/emb@16GB USB|X3 420e@M4A88TD-V|16GB|i350-T2|M1015@IT|8xHDD+3xSSD[different Size&Brand]RaidZ1+2|for TESTing only
Top
User avatar
Maurizio
Starter
Starter
Posts: 63
Joined: 05 Jul 2018 21:49
Location: Linate (MIlan)
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by Maurizio »

BUT after adding these to loader.conf results in a fatal Kernel trap after reboot :geek:
For me works even loading the kernel drivers in Command Script
Screenshot-2018-07-27-09-53-48.png
after disabling the the modules kernel load from loader.conf.
You do not have the required permissions to view the files attached to this post.
XigmaNAS 12.1.0.4 on Dell R710 144GB RAM - RootOnZFS zroot on 2x 64GB 15k HDDs in mirror, zdata on 3x 1TB SSD in RAIDZ1.
2x XigmaNAS 11.2.0.4 - RootOnZFS on HPE Proliant Microserver gen10 X3216 - 3x 4TB WD RED. In mirror with zrep.
Top
User avatar
Maurizio
Starter
Starter
Posts: 63
Joined: 05 Jul 2018 21:49
Location: Linate (MIlan)
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by Maurizio »

Note: disabling kern.vt.fb.default_mode the PC shows the preferred resolution, not 640x480.
Screenshot-2018-07-27-10-38-49.png
You do not have the required permissions to view the files attached to this post.
XigmaNAS 12.1.0.4 on Dell R710 144GB RAM - RootOnZFS zroot on 2x 64GB 15k HDDs in mirror, zdata on 3x 1TB SSD in RAIDZ1.
2x XigmaNAS 11.2.0.4 - RootOnZFS on HPE Proliant Microserver gen10 X3216 - 3x 4TB WD RED. In mirror with zrep.
Top
User avatar
lux
Advanced User
Advanced User
Posts: 193
Joined: 23 Jun 2012 11:37
Location: Bielefeld, Germany
Contact:
Contact lux
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by lux »

Thx!

will trying next Days... very busy at the moment... :|
Home:11.3.x.7538/emb@32GB USB|1270v2@X9SCA-F|ECC32GB|i340-T4[lagg@GS108Tv2&smb-mch]|M1015@IT|9HDD~40TB@3xRaidZ1+1HDD+2SSD i335&i520+1xi800P@ZIL|~44W idle@SS-400FL2|Nanoxia Deep Silence 6B|24/7
Services: CIFS, FTP, TFTP, SSH, NFS, Rsync, Syncthing, Webserver, BitTorrent, VirtualBox | Extensions: OBI, TheBrig[certbot, Asterisk] | Extensions via vBox: Pi-hole, Jellyfin & zigbee2mqtt @DebianVM's
Test:12.x/emb@16GB USB|X3 420e@M4A88TD-V|16GB|i350-T2|M1015@IT|8xHDD+3xSSD[different Size&Brand]RaidZ1+2|for TESTing only
Top
User avatar
M*I*B
Starter
Starter
Posts: 19
Joined: 28 Feb 2019 01:02
Location: Germany
Status: Offline

Re: After upgrading to 11.2 the terminal resolution is 640x480

Post by M*I*B »

... I know... A quite old thread ... but I'm standing in front of the same problem ... and I'm a noop in that ... (/version 11.3.0.4)

Simple Q: Is there any way for me to change the resolution of the console direct connected to the VGA- port of the NAS ???

I have try all the stuff before with no results... I use a KVM where the NAS and some Debian, RaspBian and WIN- machines are connected. All other are ok but the default-res of the NAS with 60HZ are not right working on the screen I use...
Greetings...
Michael
Top
Post Reply

Return to “XigmaNAS Basic Tune-up”