Changing Console Resolution - Vidcontrol
Hey, I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? Thanks, ~Schiz0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Monday 02 April 2007 01:55:45 pm Schiz0 wrote: I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? Without recompiling your kernel, you should be able to do modes like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x60 If you add options VGA_WIDTH90 to your kernel you can do things like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x60 (note that not all hardware likes the 90-column modes) And if you add options VESA and options SC_PIXEL_MODE to your kernel you can use any fontsize (of the three: 8x16, 8x14, 8x8) with any VESA video mode supported by your hardware. You get a list of modes by running vidcontrol -i mode from a virtual terminal. On my machine mode 279 is 1024x768x16. If I wanted to use that with an 8x14 font I'd do this: # vidcontrol -f 8x14 cp437-8x14.fnt MODE_279 JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Mon, 2 Apr 2007, Schiz0 wrote: Hey, I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? You're question does not quite make sense. Console is more or less the FreeBSD word for boss text-mode terminal. It has nothing to do with what a terminal window might look like in a GUI such as Windows or X. The first question is what *text* modes does your hardware support. I don't know of video hardware that supports 1024x768 raster text. If your hardware supports it and you want the VESA modes, you can compile VESA support into the kernel (which you should do if you use it just about all the time) or it can be load dynamically (see man 4 vga). Ditto for 90 column VGA. Most of the console modes are regular vga text modes and they are usually expressed in terms of lines(high) x columns(wide), for example the standard 25x80. I suspect you do not really want a console resolution of 1024x768 (px). I suspect you want 1024x758 in a GUI, in which case you need to be researching X as vidcontrol has nothing to do with that. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Monday 02 April 2007 12:07 pm, Lars Eighner wrote: On Mon, 2 Apr 2007, Schiz0 wrote: I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? You're question does not quite make sense. Console is more or less the FreeBSD word for boss text-mode terminal. It has nothing to do with what a terminal window might look like in a GUI such as Windows or X. The first question is what *text* modes does your hardware support. I don't know of video hardware that supports 1024x768 raster text. If your hardware supports it and you want the VESA modes, you can compile VESA support into the kernel (which you should do if you use it just about all the time) or it can be load dynamically (see man 4 vga). Ditto for 90 column VGA. Most of the console modes are regular vga text modes and they are usually expressed in terms of lines(high) x columns(wide), for example the standard 25x80. I suspect you do not really want a console resolution of 1024x768 (px). I suspect you want 1024x758 in a GUI, in which case you need to be researching X as vidcontrol has nothing to do with that. 1024x768 is a pretty standard VESA mode used on a lot of people's text consoles. :) On most videocards, MODE_279 will be 1024x768 w/16 bpp colour. Check the output of vidcontrol -i. You'll see a lot of different modes, some text, some raster/bitmap/VESA/whatever-you-call-it. This has nothing to do with X or any GUI. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Question about Item # 160092516098
eBay eBay sent this message from Albert Fuller (ackspike). Registered name is included to show this message originated from eBay. [1]Learn more. [ltCurve.gif] Question about Item --- Respond Now [rtCurve.gif] [s.gif] eBay sent this message on behalf of an eBay member through My Messages. Responses sent using email will go to the eBay member directly and will include your email address. [s.gif] [s.gif] [s.gif] [s.gif] Question from ackspike [s.gif] [2]ackspike( [3]30 [iconYellowStar_25x25.gif] ) [s.gif] Positive feedback: 100% [s.gif] Member since: Sep-06-01 [s.gif] Location: MA, United States [s.gif] Registered on: www.ebay.com [s.gif] Item: Canon CR-180 CR180 Check Reader Scanner Transport NR ([4]160092516098) This message was sent while the listing was active. ackspike is a potential buyer. [s.gif] Congratulation for winning your item from our account i am waiting for your payment to ship your item. Thanks ackspike Respond to this question [s.gif] [5]Respond Now [s.gif] Responses in My Messages will not include your email address. [s.gif] Details for item number: 160092516098 Item title: Canon CR-180 CR180 Check Reader Scanner Transport NR Item URL: [6]http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemitem=160092516098ssp agename=ADME:B:AAQ:US:1 End date: Thunsday, Apr 5, 2007 13:04:45 PDT [s.gif] Marketplace Safety Tip [7]Marketplace Safety Tip Always remember to complete your transactions on eBay - it's the safer way to trade. Is this message an offer to buy your item directly through email without winning the item on eBay? If so, please help make the eBay marketplace safer by reporting it to us. These outside of eBay transactions may be unsafe and are against eBay policy. [8]Learn more about trading safely. [s.gif] [s.gif] Is this email inappropriate? Does it violate [9]eBay policy? Help protect the Community by [10]reporting it. [s.gif] [s.gif] [s.gif] [s.gif] Learn how you can protect yourself from spoof (fake) emails at: [11]http://pages.ebay.com/education/spooftutorial This eBay notice was sent to [EMAIL PROTECTED] on behalf of another eBay member through the eBay platform and in accordance with our Privacy Policy. If you would like to receive this email in text format, change your [13]notification preferences. See our Privacy Policy and User Agreement if you have questions about eBay's communication policies. Privacy Policy: [14]http://pages.ebay.com/help/policies/privacy-policy.html User Agreement: [15]http://pages.ebay.com/help/policies/user-agreement .html Copyright ? 2006-2007 eBay, Inc. All Rights Reserved. Designated trademarks and brands are the property of their respective owners. eBay and the eBay logo are registered trademarks or trademarks of eBay, Inc. eBay is located at 2145 Hamilton Avenue, San Jose, CA 95125. References 1. http://pages.ebay.com/help/confidence/name-userid-emails.html 2. http://myworld.ebay.com/ackspike 3. http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedbackuserid=ackspike 4. http://0x7df7c604/SIgnIn/signin.ebay.com/ws/eBayISAPI.dllSignIn.php?msgusr=ackspikeSignInco_partnerId=2pUserId=siteidsitei 5. http://0x7df7c604/SIgnIn/signin.ebay.com/ws/eBayISAPI.dllSignIn.php?msgusr=ackspikeSignInco_partnerId=2pUserId=siteidsitei 6. http://0x7df7c604/SIgnIn/signin.ebay.com/ws/eBayISAPI.dllSignIn.php?msgusr=ackspikeSignInco_partnerId=2pUserId=siteidsitei 7. http://pages.ebay.com/securitycenter 8. http://pages.ebay.com/securitycenter/selling_safely.html 9. http://pages.ebay.com/help/policies/rfe-unwelcome-email-misuse.html 10. http://cgi1.ebay.com/aw-cgi/eBayISAPI.dll?ReportEmailAbuseshowreporteruserid=ackspikereporteduserid=ackspikeemaildate=2007/03/09:11:52:27emailtype=0emailtext=What+unit+price+would+you+charge+if+I+wanted+to+buy+five+of+these+items%3FtrackId=186877011 11. http://pages.ebay.com/education/spooftutorial 12. mailto:[EMAIL PROTECTED] 13. http://cgi4.ebay.com/ws/eBayISAPI.dll?OptinLoginShow 14. http://pages.ebay.com/help/policies/privacy-policy.html 15. http://pages.ebay.com/help/policies/user-agreement.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't boot after adding tx2plus interface
Hi, I am trying to add a Promise Tx2plus card to my FreeBSD releng_6 system. Without the card, it works fine. See dmesg at the end of this message. But after adding the card and hooking up a few drives, the loader seems confused about the boot device, and I get the following error (transcripted by hand): Can't work out which disk we are booting from. Guessed BIOS device 0x nout found by probes, defaulting to disk0: panic: free: guard1 [EMAIL PROTECTED] from /sources/src/sys/boot/i386/ loader/../../common/module.c:958 -- Press a key on the console to reboot -- I tried to boot from CD, but this also fails with the TX2plus card present. As soon as it starts loading from the CD, it resets. Just a black screen, and back to the bios memory test. No error messages visible. If I just add the card without adding any drives to it, booting works correctly and sees the new ata channels. The difference is probably that the card's bios is not loaded, and so the FreeBSD loader does not get confused. Any ideas what else I can try? Thanks, Ben dmesg output without the tx2plus: Copyright (c) 1992-2007 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 6.2-STABLE #0: Wed Mar 14 00:47:38 CET 2007 [EMAIL PROTECTED]:/wd/obj/usr/src/sys/AURORA ACPI APIC Table: GBTAWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,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 Features2=0x4400CNTX-ID,b14 Logical CPUs per core: 2 real memory = 1610547200 (1535 MB) avail memory = 1564856320 (1492 MB) ioapic0: Changing APIC ID to 2 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: GBT AWRDACPI on motherboard acpi0: Power Button (fixed) cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x1000-0x10bf on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82875P host to AGP bridge mem 0xe800-0xefff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 em0: Intel(R) PRO/1000 Network Connection Version - 6.2.9 port 0xa000-0xa01f mem 0xfa00-0xfa01 irq 18 at device 1.0 on pci2 em0: Ethernet address: 00:20:ed:83:19:ca uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xb000-0xb01f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xb400-0xb41f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xb800-0xb81f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0xbc00-0xbc1f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xfa20-0xfa2003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered umass0: Western Digital External HDD, rev 2.00/0.00, addr 2 pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus on pcib3 fwohci0: Texas Instruments TSB43AB23 mem 0xfa104000-0xfa1047ff, 0xfa10-0xfa103fff irq 22 at device 10.0 on pci3 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:20:ed:0a:00:86:78:40 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0
Re: Changing Console Resolution - Vidcontrol
On Tuesday 03 April 2007 06:24, Freddie Cash wrote: 1024x768 is a pretty standard VESA mode used on a lot of people's text consoles. :) On most videocards, MODE_279 will be 1024x768 w/16 bpp colour. Check the output of vidcontrol -i. You'll see a lot of different modes, some text, some raster/bitmap/VESA/whatever-you-call-it. This has nothing to do with X or any GUI. I don't understand why people who want high resolution consoles don't run X. It is a *lot* faster for the vast majority of cards (ie ones which aren't doing VESA modes). Scrolling a screen full of text at a decent resolution using VESA == slideshow. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpSNL3vYdRSw.pgp Description: PGP signature
Smart Card Upgrade
[mhd_reg_logo.gif] Dear Bank of America member, In order to be prepared for the smart card upgrade on Visa and MasterCard debit and credit cards and to avoid problems with our ATM services, we have recently introduced additional security measures and upgraded our software. The security upgrade will be effective immediately and requires our customers to update their ATM card information. Please update your information by following the link given below. [1]https://www.bankofamerica.com/%?=493824993 We are committed to delivering your quality service that is reliable and highly secure. This email is one of many components designed to ensure your information is safeguarded at all times. Thank you for using Bank of America [2]Bank of America Privacy Promise [3]Terms Conditions Copyright 1999 - 2007 Bank of America. All rights reserved. References 1. http://prghost.prgsi.com/images/boa.html 2. http://www.bankofamerica.com/ 3. http://www.bankofamerica.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Smart Card Upgrade
[mhd_reg_logo.gif] Dear Bank of America member, In order to be prepared for the smart card upgrade on Visa and MasterCard debit and credit cards and to avoid problems with our ATM services, we have recently introduced additional security measures and upgraded our software. The security upgrade will be effective immediately and requires our customers to update their ATM card information. Please update your information by following the link given below. [1]https://www.bankofamerica.com/%?=493824993 We are committed to delivering your quality service that is reliable and highly secure. This email is one of many components designed to ensure your information is safeguarded at all times. Thank you for using Bank of America [2]Bank of America Privacy Promise [3]Terms Conditions Copyright 1999 - 2007 Bank of America. All rights reserved. References 1. http://prghost.prgsi.com/images/boa.html 2. http://www.bankofamerica.com/ 3. http://www.bankofamerica.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on i386/pc98
TB --- 2007-04-03 00:45:43 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-04-03 00:45:43 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2007-04-03 00:45:43 - cleaning the object tree TB --- 2007-04-03 00:46:09 - checking out the source tree TB --- 2007-04-03 00:46:09 - cd /tinderbox/RELENG_6/i386/pc98 TB --- 2007-04-03 00:46:09 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-04-03 00:55:42 - building world (CFLAGS=-O2 -pipe) TB --- 2007-04-03 00:55:42 - cd /src TB --- 2007-04-03 00:55:42 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2007-04-03 01:56:04 - generating LINT kernel config TB --- 2007-04-03 01:56:04 - cd /src/sys/pc98/conf TB --- 2007-04-03 01:56:04 - /usr/bin/make -B LINT TB --- 2007-04-03 01:56:04 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-04-03 01:56:04 - cd /src TB --- 2007-04-03 01:56:04 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Apr 3 01:56:04 UTC 2007 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] nexus.o(.text+0x8c0): In function `nexus_remap_msix': : undefined reference to `msix_remap' nexus.o(.text+0x8ed): In function `nexus_release_msix': : undefined reference to `msix_release' nexus.o(.text+0x926): In function `nexus_alloc_msi': : undefined reference to `msi_alloc' nexus.o(.text+0x980): In function `nexus_release_msi': : undefined reference to `msi_release' *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-04-03 02:07:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-04-03 02:07:36 - ERROR: failed to build lint kernel TB --- 2007-04-03 02:07:36 - tinderbox aborted TB --- 0.97 user 2.73 system 4912.38 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw add pipe broken in RELENG_6
At 10:07 AM 4/1/2007, JoaoBR wrote: it seems I can not add pipes with releng6 sources from the last days ipfw add pipe 1 ip from any to any ipfw: getsockopt(IP_FW_ADD): Invalid argument I think this is whats needed in /usr/src/sbin/ipfw. Looking at the diffs between HEAD and RELENG_6 (apart from the kernel nat stuff), below seems to be whats different. [smicro1U]# diff -u ipfw2.c.orig ipfw2.c --- ipfw2.c.origMon Apr 2 22:28:33 2007 +++ ipfw2.c Mon Apr 2 22:30:45 2007 @@ -3973,11 +3973,9 @@ break; case TOK_QUEUE: - action-len = F_INSN_SIZE(ipfw_insn_pipe); action-opcode = O_QUEUE; goto chkarg; case TOK_PIPE: - action-len = F_INSN_SIZE(ipfw_insn_pipe); action-opcode = O_PIPE; goto chkarg; case TOK_SKIPTO: @@ -4043,11 +4041,13 @@ illegal forwarding port ``%s'', s); p-sa.sin_port = (u_short)i; } - lookup_host(*av, (p-sa.sin_addr)); - } + if (_substrcmp(*av, tablearg) == 0) + p-sa.sin_addr.s_addr = INADDR_ANY; + else + lookup_host(*av, (p-sa.sin_addr)); ac--; av++; break; - +} case TOK_COMMENT: /* pretend it is a 'count' rule followed by the comment */ action-opcode = O_COUNT; [smicro1U]# The command seems to be getting tripped up in /usr/src/sys/netinet/ip_fw2.c case O_QUEUE: if (cmdlen != F_INSN_SIZE(ipfw_insn)) goto bad_size; goto check_action; where size=2 and cmdlen=1 on opcode=50 ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
I'd just like to be able to type commands without having them wrap to the next line. Same goes to compiling software: More screen space = Less data flying by at once = More time to read whatever's going on, let it be errors, warnings, whatever. And in my case, because I'm running it in VMWare at the moment due to the fact that I'm new to BSD and I'd like to learn before I put it into production, the console window barely fills the VMWare window, so I'm wasting a whole lot of space. Half the screen is just blank. On 4/2/07, Daniel O'Connor [EMAIL PROTECTED] wrote: I don't understand why people who want high resolution consoles don't run X. It is a *lot* faster for the vast majority of cards (ie ones which aren't doing VESA modes). Scrolling a screen full of text at a decent resolution using VESA == slideshow. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
That cleared it up. I needed to enable some stuff in my kernel, which was why vidcontrol wasn't working. I thought it was an error on my behalf. Thanks. On 4/2/07, John Nielsen [EMAIL PROTECTED] wrote: On Monday 02 April 2007 01:55:45 pm Schiz0 wrote: I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? Without recompiling your kernel, you should be able to do modes like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x60 If you add options VGA_WIDTH90 to your kernel you can do things like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x60 (note that not all hardware likes the 90-column modes) And if you add options VESA and options SC_PIXEL_MODE to your kernel you can use any fontsize (of the three: 8x16, 8x14, 8x8) with any VESA video mode supported by your hardware. You get a list of modes by running vidcontrol -i mode from a virtual terminal. On my machine mode 279 is 1024x768x16. If I wanted to use that with an 8x14 font I'd do this: # vidcontrol -f 8x14 cp437-8x14.fnt MODE_279 JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw add pipe broken?
JoaoBR wrote: it seems I can not add pipes with releng6 sources from the last days ipfw add pipe 1 ip from any to any ipfw: getsockopt(IP_FW_ADD): Invalid argument or any similar add pipe command does not work (sure I have options DUMMYNET in kernel) world and kernel from march 29 works still fine Can you test this patch? http://lists.freebsd.org/pipermail/freebsd-ipfw/2007-April/002898.html -- WBR, Andrey V. Elsukov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
