Re: Unhappy Xorg upgrade
I've just upgraded to the latest xorg on my amd64 box 7.1-STABLE FreeBSD 7.1-STABLE #0: Fri Jan 16 07:33:20 PST 2009 I have a radeon graphics card, drm0: ATI Radeon RV280 9250 on vgapci0 - had to add the option mentioned in UPDATING Section ServerLayout Option AllowEmptyInput off ... Things seem mostly running on my box, though there are many of these emacs Xlib: extension Generic Event Extension missing on display :0.0. ... I now see that ssh into a remote host (solaris 10 sparc), running emacs there pops up a window, but then typing anything into the window kills it, with X protocol error: BadAlloc (insufficient resources for operation) on protocol request 149 (on the remote machine). xv works ok. This doesn't happen if the remote host is linux rh4... This didn't happen before the xorg upgrade. Seems to be some sort of incompatibility in X11. Any ideas? Sam Sirlin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: recovering from the 6.3 xorg mess
On Mon, 17 Mar 2008 21:23:09 -0800 (AKDT) peter stern [EMAIL PROTECTED] wrote: On Mon, 17 Mar 2008, Kevin Oberman wrote: Date: Mon, 17 Mar 2008 07:36:23 +0100 From: Kurt Jaeger [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi! I'd appreciate suggestions on how to get a working xorg from the mess 6.3 shipped with. I've been using FreeBSD since 2.2 and have never had much trouble with it until the 6 branch was released. My hardware is pretty generic Intel brand D865 motherboard, matrox g550 video. I don't customize the kernel. I do clean installs not upgrades. Basically, the problem is with the matrox board. ... I have run the Matrox G550 under both 6 and 7. I had some problems, but not too many. I do need to use xrandr to set up the proper resolution, though. #!/bin/sh # Set 1280x1024 mode on second display xrandr --addmode VGA2 1280x1024 # Set 1024x768 mode on second port (Why? Why not.) xrandr --addmode VGA2 1024x768 # Set the second port to use 1280x1024 xrandr --output VGA2 --mode 1280x1024 ... Not unique to matrox. Some time before 6.3 there was an X update that broke various things. I also noticed I couldn't set resolution in xorg.conf or via keystrokes. xrandr seems the only way for most wm (kde can do it). I thought perhaps it was a 64bit problem since I'm using amd64, and some other keystrokes don't work (normally don't notice but was trying to find some way to set resolution). I've also noticed after xscreensaver can put X in a sleep mode where it just ignores anything (not a crash, but need to remote in to shut down X at least). Is resolution setting only through xrandr perhaps a deliberate (but undocumented) design change in xorg (feature)? Or just a temporary bug? I don't have a matrox: drm0: ATI Radeon RV280 9250 port 0xa000-0xa0ff mem 0xe000-0xe7ff,0xfd80-0xfd80 irq 16 at device 0.0 on pci1 info: [drm] AGP at 0xf000 128MB info: [drm] Initialized radeon 1.25.0 20060524 -- sam sirlin [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shutdown problem Stray IRQ9
Date: Fri, 5 Jan 2007 08:09:09 -0800 From: Jeremy Chadwick [EMAIL PROTECTED] On Fri, Jan 05, 2007 at 07:17:12AM -0800, vincent delft wrote: As new to FreeBSD I'm looking for info to solve my shutdown problem. When I shutdown the system (shutdown -h now), the messages displayed are: ... I think shutdown -h should just hang (always has on my amd64 machine). I think you want to do shutdown -p which should (and does for me) turn off power. Sam Sirlin Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
FYI, in case there was any doubt, this annoying bug is also present in a recent 6.0-STABLE (Sat Jan 14) on amd 64. CONFIG_SHELL=/bin/sh is a fix. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
acd0: FAILURE - MODE_SENSE_BIG timed out
I've been getting these timeouts for some time on boot, but up till now when they appear they just slow the boot down. After cvsup on 4/2, I now sometimes get a couple of new messages which hang up the boot process: ... acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - ATAPI_Identity ... acd0: timeout state=0 unexpected (hangs here till hard reboot) Are there some tweaks to parameters to prevent this? Sam Sirlin I 'm running FreeBSD celeborn.my.domain 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Sat Apr 2 17:48:39 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CELEBORN amd64 Here's an example of what used to happen, even with 5.4 up till 4/2: Copyright (c) 1992-2004 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 5.3-STABLE #0: Sun Nov 21 10:58:56 PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CELEBORN ACPI APIC Table: A M I OEMAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2002.57-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xf48 Stepping = 8 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MM X,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 1072889856 (1023 MB) avail memory = 1024090112 (976 MB) ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 0.3 irqs 0-23 on motherboard acpi0: A M I OEMRSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU 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 pci1: display, VGA at device 0.0 (no driver attached) fwohci0: VIA Fire II (VT6306) port 0xcc00-0xcc7f mem 0xf790-0xf79007ff irq 16 at device 7.0 on pc i0 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:00:62:29:1b fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:62:29:1b fwe0: Ethernet address: 02:e0:18:62:29:1b fwe0: if_start running deferred for Giant sbp0: SBP-2/SCSI over FireWire on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) skc0: 3Com 3C940 Gigabit Ethernet port 0xdc00-0xdcff mem 0xf7c0-0xf7c03fff irq 17 at device 10.0 on pci0 skc0: 3Com Gigabit LOM (3C940) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:0e:a6:74:6a:02 miibus0: MII bus on sk0 e1000phy0: Marvell 88E1000 Gigabit PHY on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto pcm0: Creative EMU10K1 port 0xec00-0xec1f irq 17 at device 12.0 on pci0 pcm0: eMicro EM28028 AC97 Codec atapci0: VIA 6420 SATA150 controller port 0xc800-0xc8ff,0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe 000-0xe003,0xe400-0xe407 irq 20 at device 15.0 on pci0 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: VIA 8237 UDMA133 controller port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 uhci0: VIA 83C572 USB controller port 0xb400-0xb41f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: VIA 83C572 USB controller port 0xc000-0xc01f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: VIA 83C572 USB controller port 0xc400-0xc41f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: VIA 83C572 USB controller on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 16.4 (no driver attached) isab0: PCI-ISA bridge at device 17.0 on pci0 isa0: ISA bus on isab0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0
Re: XFree86 crash w/Mozilla at Barnes Noble.com?
Date: Sat, 16 Nov 2002 10:19:05 -0600 From: Bruce Burden [EMAIL PROTECTED] Hi, I have the latest XFree86-4 changes (libraries 4.2.1_3) and Mozilla (1.1_1,2). If I go to www.barnesandnoble.com, about halfway through the load of the page, X crashes with signal 6. Has anybody else tried this? Going to the site with netscape produces no problems. No problem with a somewhat older setup XFree86-libraries-4.2.1_2 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Oct 28 Mozilla 1.1 Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020829 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
