Re: booting off a ZFS pool consisting of multiple striped mirror vdevs
On Mon, 2010-02-15 at 10:07 -0800, Matt Reimer wrote: > On Sat, Feb 13, 2010 at 12:04 PM, Dan Naumov wrote: > > > Hello > > > > I have succesfully tested and used a "full ZFS install" of FreeBSD 8.0 > > on both single disk and mirror disk configurations using both MBR and > > GPT partitioning. AFAIK, with the more recent -CURRENT and -STABLE it > > is also possible to boot off a root filesystem located on raidz/raidz2 > > pools. But what about booting off pools consisting of multiple striped > > mirror or raidz vdevs? Like this: > > > > Assume each disk looks like a half of a traditional ZFS mirror root > > configuration using GPT > > > > 1: freebsd-boot > > 2: freebsd-swap > > 3: freebsd-zfs > > > > |disk1+disk2| + |disk3+disk4| + |disk5+disk6| > > > > My logic tells me that while booting off any of the 6 disks, boot0 and > > boot1 stage should obviously work fine, but what about the boot2 > > stage? Can it properly handle booting off a root filesystem thats > > striped across 3 mirror vdevs or is booting off a single mirror vdev > > the best that one can do right now? > > > > > I don't know, but I plan to test that scenario in a few days. It *should* work... I made changes a while back that allow for multiple vdevs to attach to the root. In this case you should have 3 mirror vdevs attached to the root, so as long as the BIOS can enumerate all of the drives, we should find all of the vdevs and build the tree correctly. It should be simple enough to test in qemu, except that the BIOS in qemu is a little broken and might not id all of the drives. robert. > Matt > ___ > freebsd-sta...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: booting off GPT partitions
On Wed, 2010-01-27 at 20:23 -0600, Brooks Davis wrote: > On Thu, Jan 28, 2010 at 12:27:54AM +0100, Dimitry Andric wrote: > > On 2010-01-27 22:27, John Baldwin wrote: > >> GPT was defined along with EFI, so many folks assume that you have to use > >> EFI > >> to boot a GPT-labelled disk. However, FreeBSD has its own BIOS-based > >> bootstrap that can handle GPT-labelled disks. I doubt the SuperMicro tech > >> is > >> familiar with that case. I thought I heard that some folks had added GPT > >> support to grub as well. > > > > However, this won't boot disks larger than 2TiB, right? At least not > > without BIOS support... > > You won't be able to boot from a partition more than 2TiB in, but you > should still be able to boot as long as you boot from the front part of > the disk. John or Marcel can correct me, but I don't think that this is an issue. The bootstrap is located in the pmbr in sector 0 and the GPT headers and tables are in sectors 1 - 34. The bootstrap code knows how to read the GPT tables and can deal with > 2 tb lba's. So, as long as you can successfully load the bootstrap code from sector 0, all *should* be good. robert. > -- Brook -- Robert Noland FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Loader, MBR and the boot process
On Mon, 2010-01-25 at 09:45 +, Matthew Seaman wrote: > Andriy Gapon wrote: > > on 25/01/2010 04:41 Robert Noland said the following: > >> On Mon, 2010-01-25 at 07:57 +1100, Mark Andrews wrote: > >>> offset The offset of the start of the partition from the beginning > >>> of > >>> the drive in sectors, or * to have bsdlabel calculate the > >>> correct > >>> offset to use (the end of the previous partition plus one, > >>> ignor- > >>> ing partition `c'. For partition `c', * will be interpreted > >>> as > >>> an offset of 0. The first partition should start at offset > >>> 16, > >>> because the first 16 sectors are reserved for metadata. > >> Ok, now this has my attention... My gut feeling right now is that this > >> is a bug in geom_part_bsd. I don't understand why the label isn't > >> protected. (Adding -b 16 when adding the swap partition fixes this) > >> Another project to goes on my list... > >> > >> If anyone knows why this is done like this... please share. > > > > I presume that this is for purely historic reasons. > > > > I believe this has been known about since 5.x days: > >http://www.freebsd.org/cgi/query-pr.cgi?pr=72812 > > As far as I recall, sometime around 6.1-RELEASE this should have been > fixed. It certainly seems to be the case that it is harmless to have > a plain swap partition start at offset 0, but anything else, like encrypted > swap or putting a filesystem there needs the 16 sector offset. When the first partition (whatever it is), starts at offset 0, if you dd into that partition you wipe out the label entirely, which just doesn't make sense to me. Trying to manage this in the file system code and the swap pager or whatever other consumer might make use of the partition seems like madness to me. robert. > Cheers, > > Matthew > -- Robert Noland FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Loader, MBR and the boot process
P can > > > only be first if it is the ONLY thing using that slice (disk), otherwise, > > > you need a filesystem first to protect the partition table. > > > -- > > > > > > John Lind > > > j...@starfire.mn.org > > > > This explanation does sound logical, but holy crap, if this is the > > case, you'd think there would be bells, whistles and huge red label > > warnings in EVERY FreeBSD installation / partitioning guide out there > > warning people to not put swap first (unless given a dedicated slice) > > under any circumstances. The warnings were nowhere to be seen and lots > > of pointy hair first greyed and were then lost during the process of > > me trying to figure out why my system would install but wouldn't boot. > > >From "man bsdlabel". > > offset The offset of the start of the partition from the beginning of > the drive in sectors, or * to have bsdlabel calculate the correct > offset to use (the end of the previous partition plus one, ignor- > ing partition `c'. For partition `c', * will be interpreted as > an offset of 0. The first partition should start at offset 16, > because the first 16 sectors are reserved for metadata. Ok, now this has my attention... My gut feeling right now is that this is a bug in geom_part_bsd. I don't understand why the label isn't protected. (Adding -b 16 when adding the swap partition fixes this) Another project to goes on my list... If anyone knows why this is done like this... please share. robert. > > - Sincerely, > > Dan Naumov > > ___ > > freebsd-sta...@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 8.0-RELEASE / gpart / GPT / marking a partition as "active"
On Tue, 2010-01-19 at 19:11 +0200, Dan Naumov wrote: > It seems that quite a few BIOSes have serious issues booting off disks > using GPT partitioning when no partition present is marked as > "active". See http://www.freebsd.org/cgi/query-pr.cgi?pr=115406&cat=bin > for a prime example. > > In 8.0-RELEASE, using gpart, setting a slice as "active" in MBR > partitioning mode is trivial, ie: > > gpart set -a active -i 1 DISKNAME > > However, trying to do the same thing with GPT partitioning yields no results: > > gpart set -a active -i 1 DISKNAME > gpart: attrib 'active': Device not configured > > As a result of this issue, I can configure and make a succesfull > install using GPT in 8.0, but I cannot boot off it using my Intel > D945GCLF2 board. I have the same board... > I have found this discussion from about a month ago: > http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg106918.html > where Robert mentions that "gpart set -a active -i 1" is no longer > needed in 8-STABLE, because the pmbr will be marked as active during > the installation of the bootcode. Is there anything I can do to > archieve the same result in 8.0-RELEASE or is installing from a > snapshop of 8-STABLE my only option? Prior to fixing gpart to take care of this, I used fdisk to set the active partition. gpart knows the disk is GPT and GPT doesn't have an "active" parameter, so the above command doesn't (perhaps never) worked. Basically, an "fdisk -a /dev/devX" is what you want... robert. > Thanks. > > - Sincerely, > Dan Naumov -- Robert Noland FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFSROOT / Custom Kernels [or upgrades]
On Mon, 2009-11-30 at 02:17 -0500, Philip M. Gollucci wrote: > Hi All, > > 1) > I followed this wiki link to setup our server [sigyn.apache.org] > (Dell r710 with 4 disks mfid[0123] as raidz2) > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 > > Rebooted all was well. > > 2) off on another 'build' box [loki.apache.org], I had compiled > release/8.0.0 userland+kernel [with LOADER_ZFS_SUPPORT=yes]. > Whats the ETA for MFC from trunk->stable/8 for > http://svn.freebsd.org/viewvc/base?view=revision&revision=199714 I set the MFC timer for 2 weeks from the initial commit. You don't say what error that you are getting, but the loader is updated during installworld or via direct make install from /usr/src/sys/boot/i386/loader. The 8.0-RELEASE code has the fix for raidz boot, but may still have issues with disks larger than 2TB. You need to make sure that you have installed the fixed gptzfsboot code to the drives. If you have not yet done an installworld, then it will be /usr/obj/sys/boot/i386/gptzfsboot/gptzfsboot It sounds like when you install the new kernel, the block numbers are overflowing. (which should be addressed by the fix in 8.0) robert. > ** FWIW, loki is working nicely on 8.0-RELEASE geom+zfs. > > 3) I nfs mounted /usr/src, and /usr/obj on sigyn from loki. > $ cd /usr/src > $ sudo make installkernel KERNCONF=SIGYN > > It fails to mount from zfs:zroot upon reboot. Via great hoops and magic > I got back into the fixit on remote console. I didn't see a loader.old > or a zfsboot. So I repeated the steps in wiki to install zfsboot. > Rebooted, same diff. > > Jumped backed to fixit and reverted the kernel to a stock GENERIC that > worked the 1st time. Same error again. > cd /boot > $ mv kernel kernel.cust > $ mv kernel.old kernel > > So assuming you are lucky enough to get a zfsroot system. Is there an > actual upgrade path ? Am I missing something stupid ? > > Any help greatly appreciated. > > I have a few days to play with this machine before we forgoe zfsroot and > drop back to geom gmirror. > > I'm at a datacenter for $work on Monday/Tuesday so I'll be spare over > tonight. > > > > > > -- Robert Noland FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: MSI RAdeon R4670/512 and xf86-video-ati/xf86-video-radeonhd-devel crashes!
On Mon, 2009-11-09 at 10:16 +, O. Hartmann wrote: > Hello. > > Please respond also to my eMail address, since I'm not subscriber of > these lists! Thanks. > > Since I utilise a MSI Radeon R4670/512 RV730-based graphics card, I'im > incapable of using either > > x11-drivers/xf86-video-ati or > x11-drivers/xf86-video-radeonhd[-devel] Try updating xf86-video-ati, patch attached. robert. > > The box is a ASUS P5K-Premium based system (Intel P35 chipset, CPU Intel > Q6600), running FreeBSD 8.0-RC2/amd64 successfully. The X11 subsystem > ist the most recent as one can find in the ports collection. I'll attach > the logfile of the currently running Xserver. > > My box got a new 24 inch TFT display so using VESA driver or lower > resolutions than 1920x1200 isn't acceptable. The situation is as follows: > > In all cases it doesn't matter wheter kernel module 'drm.ko' is loaded > or not. > > Driver 'radeon' (x11-drivers/xf86-video-ati) crashes the box immediately > without any messages. I can see the xdm-login requester, but just > before this shows up, I realise that the mousepointer sprite gets a kind > of 'distorted', it shows up some 'stripes'. They vanish. When log in and > the desktop is about to show up (using windowmaker), the screen stays > black, the box crahes and in some lucky situations, it reboots, in less > lucky situations it remains frozen. > > Driver 'radeonhd' (xf86-video-radeonhd-1.2.5_2) works, but without > 'options EXA' and without 'options DRI'. It is bumpy, but shows a > 1920x1200 pixel screen in full colours. > > Driver 'radeonhd' (xf86-video-radeonhd-1.3.0) doesn't work, it shows the > same behaviour as 'radeon' (xf86-video-ati). I can wathc the mouse > pointer sprite getting striped and a kind of distorted, then the box > crashes. > > Those crashes occur mostly when switching from xdm-login requester to > desktop. In some cases I can switch to the console (pressing > ctrl-alt-[F1--F7]), but at some point, this also freezes/crashes the box. > > I'm a little bit confused, since the ATi-RV730LE chipset is supposed to > be supported. I run another box, an older nVidia CK804-based Athlon3500+ > box equipted with a MSI R4830/512 graphics card. The same base OS > (FreeBSD 8.0-RC2/amd64. The graphics board runs perfectly with ALL(!) > radeon-type drivers, options EXA and DRI enabled, kernel module drm.ko > loaded. > > Can someone help? Since I do not have Windows XP/Vista/7 running on the > box in question, I can not update the firmware of the MSI R4760 with a > potentially existing firmware-update (since those tasks can only be > performed via a special software from MSI running on XP/Vista as far as > I know). > > Thanks in advance, > Oliver > > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Robert Noland FreeBSD Index: Makefile === RCS file: /home/ncvs/ports/x11-drivers/xf86-video-ati/Makefile,v retrieving revision 1.18 diff -u -r1.18 Makefile --- Makefile 7 May 2009 19:42:35 - 1.18 +++ Makefile 9 Nov 2009 12:36:21 - @@ -6,8 +6,7 @@ # PORTNAME= xf86-video-ati -PORTVERSION= 6.12.2 -PORTREVISION= 1 +PORTVERSION= 6.12.4 CATEGORIES= x11-drivers MAINTAINER= x...@freebsd.org Index: distinfo === RCS file: /home/ncvs/ports/x11-drivers/xf86-video-ati/distinfo,v retrieving revision 1.14 diff -u -r1.14 distinfo --- distinfo 8 Apr 2009 15:18:49 - 1.14 +++ distinfo 9 Nov 2009 12:36:21 - @@ -1,3 +1,3 @@ -MD5 (xorg/driver/xf86-video-ati-6.12.2.tar.bz2) = 2bf50461378771497501ca7f678d36f3 -SHA256 (xorg/driver/xf86-video-ati-6.12.2.tar.bz2) = 1beebba17719f7b9bfbbede156dc33a2dd29ed164657badcb62c7149cfae2750 -SIZE (xorg/driver/xf86-video-ati-6.12.2.tar.bz2) = 902480 +MD5 (xorg/driver/xf86-video-ati-6.12.4.tar.bz2) = e662348f6f957fcedf52818d668ab9f5 +SHA256 (xorg/driver/xf86-video-ati-6.12.4.tar.bz2) = cfde066a7087a19b624f79e95cb9a6c97a847b8802cf38d4ae6022758bf338f6 +SIZE (xorg/driver/xf86-video-ati-6.12.4.tar.bz2) = 915124 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Attempting ZFS Only Install of 7.2
> > If you have invalid mount options, reboot, and first try the following from > > the loader prompt: > > > > set vfs.root.mountfrom.options=rw (did this,no luck.. also > > switched to an /etc/fstab layout, still no go) > > > > and then remove the invalid mount options from /etc/fstab. > > > > Loader Variables: > > vfs.root.mountfrom=zfs:zroot > > vfs.root.mountfrom.options=rw,noatime (this is from the /etc/fstab attempt) > > > > -- > > > > Then it describes some specifications on how to use the :. > > > > I just don't get how some are getting this working, yet it comes so hard > > for others. > > > > Drew, I hope you have had better luck than I. I may just give up until it > > is a viable solution. > > > > > >> > >> -- > >> Be a Great Magician! > >> Visit The Alchemist's Warehouse > >> > >> http://www.alchemistswarehouse.com > >> > >> > > > ___ > freebsd-curr...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: netbooks vs FreeBSD
On Sun, 2009-05-24 at 20:09 +0200, Gabor Kovesdan wrote: > Koichiro IWAO escribió: > > The integrated video chip Intel GMA 500 is not a original Intel product. > > So X11 does not work with Intel driver and the driver is still > > unavailable. VESA is the only available driver. Does anyone have the pci ids for this? I have some patches around here for an "IGD" device that I think is a G41 but afaik was un-released at the time that I created that patch. robert. > > If you want use X11, do not forget to choose Atom N series. > Uh, thanks a lot, I almost chose the 751h model, but now I decided to > take the 531. It comes with Intel 945GM. -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: Keyboard not working in gnome?
On Fri, 2009-05-15 at 18:56 +0200, Christopher Arnold wrote: > Problem solved, see below.. > > On Fri, 15 May 2009, Christopher Arnold wrote: > > > On Fri, 15 May 2009, Robert Noland wrote: > > > >> On Fri, 2009-05-15 at 13:05 +0200, Christopher Arnold wrote: > >>> In Xorg.0.log i see: > >>> (II) config/hal: Adding input device USB Receiver > >>> (EE) config/hal: NewInputDeviceRequest failed (8) > >>> (II) config/hal: Adding input device AT Keyboard > >>> (EE) config/hal: NewInputDeviceRequest failed (8) > >>> (The at part makes sense, i only have USB on this machine) > >>> > >>> So i guess this is the problem and that a rebuild of gnome/X11 did not > >>> help. It seems fairly close to the issues with hald/xorg.conf that we saw > >>> the last time upgrading gnome. > >>> > >>> What is actually the right config nowdays? > >>> > >>> I have the following in xorg.conf: > >>> Section "ServerLayout" > >>> Identifier "Simple Layout" > >>> Screen "Screen 1" 0 0 > >>> InputDevice"Mouse1" "CorePointer" > >>> InputDevice"Keyboard1" "CoreKeyboard" > >>> Option "AllowEmptyInput" "off" > >>> Option "AutoAddDevices" "off" > >>> EndSection > >> > >> Using the above, you shouldn't need the lines below. Your devices need > >> to be statically configured in xorg.conf. If you are using hald, then > >> remove both the AllowEmptyInput and AutoAddDevices lines above. I > > When i commment theese out i get neither keyboard or mouse. > > Also i notice in the xorg logfile that my "Keyboard1" gets ignored > > alltogether. That is if i would have got the keyboard to work i would have > > a > > us one instead of my swedish. > > > >>> And in /etc/rc.conf: > >>> bus_enable="YES" > >>> hald_enable="YES" > >>> > > If i comment these out then gdm dosn't even start since gdm requiers them i > > guess. > > > With AllowEmptyInput and AutoAddDevices set to "off" and both dbus and > hald enabled it now works... Why? This means that you are using purely static configured devices from xorg.conf. > Well i tried and xterm as usual and it didn't work. Decided to check if > another program accepted input to rule out an error in xterm. So i used > preferences/keyboard instead. I didn't expect it to work so i just pressed > a key and kept it down. Klick and then characters! > > So in the end i managed to find out that slow keys somehow had become > enabled in universal access preferences > > Embarrasing... > > But it is a bit strange that your suggestions did not work. > How come some people need the AllowEmptyInput and AutoAddDevices lines but > not others? It looks like hal is seeing your keyboard, but I don't see it picking up the mouse. You would need to look at lshal to figure out what is going on there. If you are using hal with a non-us keyboard layout you probably want to search the archives for the fdi setup to configure your keyboard layout. robert. > /Chris > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: Keyboard not working in gnome?
On Fri, 2009-05-15 at 10:09 -0500, Andrew Gould wrote: > > > > > > And in /etc/rc.conf: > > bus_enable="YES" > > Shouldn't the line above be: > > dbus_enable="YES" Yes, sorry... typo... robert. > > > > hald_enable="YES" > > > > Or does anyone have any hints on why a keyboard (that i'm > currently > > writing on...) don't work in X11/Gnome? > > Any hints on debugging this? > > > > /Chris > > Andrew -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: Keyboard not working in gnome?
On Fri, 2009-05-15 at 13:05 +0200, Christopher Arnold wrote: > Hi again, > > some more input on this. > > In Xorg.0.log i see: > (II) config/hal: Adding input device USB Receiver > (EE) config/hal: NewInputDeviceRequest failed (8) > (II) config/hal: Adding input device AT Keyboard > (EE) config/hal: NewInputDeviceRequest failed (8) > (The at part makes sense, i only have USB on this machine) > > So i guess this is the problem and that a rebuild of gnome/X11 did not > help. It seems fairly close to the issues with hald/xorg.conf that we saw > the last time upgrading gnome. > > What is actually the right config nowdays? > > I have the following in xorg.conf: > Section "ServerLayout" > Identifier "Simple Layout" > Screen "Screen 1" 0 0 > InputDevice"Mouse1" "CorePointer" > InputDevice"Keyboard1" "CoreKeyboard" > Option "AllowEmptyInput" "off" > Option "AutoAddDevices" "off" > EndSection Using the above, you shouldn't need the lines below. Your devices need to be statically configured in xorg.conf. If you are using hald, then remove both the AllowEmptyInput and AutoAddDevices lines above. I currently use moused as well, since there still seems to be some occasional issue with my mouse if I try and use native psm... robert. > And in /etc/rc.conf: > bus_enable="YES" > hald_enable="YES" > > Or does anyone have any hints on why a keyboard (that i'm currently > writing on...) don't work in X11/Gnome? > Any hints on debugging this? > > /Chris > > On Thu, 14 May 2009, Christopher Arnold wrote: > > > > > Hi, > > > > i'm currently debugging why my keyboard is not working in gnome, so i > > thought > > i might throw out a quick question here if someone else have run into this? > > > > Details: > > Im running 7.1-STABLE. > > > > It's a logitech wireless keyboard and mouse (connected with USB) that have > > been woriking for a couple of years. (Actually i'm writing on it now, but > > in > > a vty) Suddenly in the middle of a session everything hung, so i rebooted. > > > > Now i managed to login (That is it works in gdm!) but when i open a xterm > > or > > any other program it does not work. (as in no keys work not even caps lock) > > The mouse works perfectly. And since the mouse works i can use the GUI to > > logout and back in gdm keyboard works again... > > > > My first thought was that i might have rebuilt some port affecting this, so > > currently i'm rebuilding X11 and gnome. > > > > Have anyone else run into this? > > Any hints on what might be wrong? > > > > /Chris > > ___________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: xf86-video-intel-2.6.3 resolution issues [fixed?]
ap_control > (II) AIGLX: enabled GLX_texture_from_pixmap with driver support > (II) AIGLX: Loaded and initialized /usr/local/lib/dri/i915_dri.so > (II) GLX: Initialized DRI GL provider for screen 0 > (II) intel(0): Setting screen physical size to 306 x 230 > > > > vgap...@pci0:0:2:1: class=0x03 card=0x25821043 chip=0x25828086 > rev=0x04 hdr=0x00 > vendor = 'Intel Corporation' > device = '82915G/GV/GL, 82910GL Integrated Graphics Device' > class = display > subclass = VGA > vgapci0: child drm0 requested pci_enable_busmaster > info: [drm] AGP at 0xd000 256MB > info: [drm] Initialized i915 1.6.0 20080730 > vgapci1: mem 0xcfe0-0xcfe7 at device > 2.1 on pci0 > -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: Can't use psm/synaptics with my touchpad
On Tue, 2009-02-17 at 09:58 +0100, Lagrange Marc wrote: > Hi, > > I've installed FreeBSD 7-RELEASE to my laptop, a Fujitsu Siemens > CELSIUS Mobile H ( the p4 one, not the recent H series. ) > > But i get a problem with the touchpad. > > The touchpad/keyboard are removable and detected as: > > ums0 on > uhub2 > ums0: 2 buttons. > > It works, but basically, like a normal mouse... > > I've tried psm with hw.psm.synaptic on /boot/loader.conf without > success, doesn't detect and no /dev/psm0 created, with xorg/synaptics > same problem, it doesn't detect any compatible touchpad. So, without going and re-examining the code, the synaptics driver only supports the psm protocol. Your touchpad is on /dev/ums0, you could try setting the device entry to ums0, but I doubt that it will work correctly. It should however work fine as a standard mouse using the mouse driver. robert. > If someone have an idea how to get my touchpad supported, i just would > to use h/v scrolling features.. > > Thanks. > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: Problems with xf86-video-ati driver (6.10.0)
pi/" > FontPath "/usr/local/lib/X11/fonts/URW/" > FontPath "/usr/local/lib/X11/fonts/TrueType/" > EndSection > > Section "Module" > Load "GLcore" > Load "xtrap" > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > Section "Monitor" > Identifier "Monitor0" > VendorName "DELL" > ModelName"1905FP" > EndSection > > Section "Device" > Identifier "Card0" > Driver "radeon" > VendorName "ATI Technologies Inc" > BoardName "RV380 [Radeon X600 (PCIE)]" > BusID "PCI:1:0:0" > Option "DRI" "off" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor"Monitor0" > DefaultDepth24 > SubSection "Display" > Viewport 0 0 > Depth 1 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 4 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 8 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 15 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 16 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 24 > Modes "1280x1024" > EndSubSection > EndSection -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: 7.4 -> X -configure gives No devices to configure
On Fri, 2009-02-13 at 09:26 +, Anton Shterenlikht wrote: > On Thu, Feb 12, 2009 at 03:31:43PM -0500, Robert Noland wrote: > > On Wed, 2009-02-11 at 10:42 +, Anton Shterenlikht wrote: > > > Upgrade from 7.3 to 7.4 made X unsuable on FBSD 7.1-stable i386. > > > I followed the UPDATE procedures, had no errors on build, > > > but on X -configure I get > > > > > > No devices to configure. Configuration failed. > > > > > > This is a Compaq Armada 1700 laptop, old I know, but 7.3 worked > > > fine. The graphics is by Chips and Technologies, nothing fancy, > > > and the driver is xf86-video-chips-1.2.1. The full log is below. > > > > > > What's going on? > > > > > > many thanks > > > anton > > > > > > *** > > > > > > X.Org X Server 1.5.3 > > > Release Date: 5 November 2008 > > > X Protocol Version 11, Revision 0 > > > Build Operating System: FreeBSD 7.1-STABLE i386 > > > Current Operating System: FreeBSD mech-aslap33.men.bris.ac.uk 7.1-STABLE > > > FreeBSD 7.1-STABLE #0: Sat Jan 31 14:31:50 GMT 2009 > > > me...@mech-aslap33.men.bris.ac.uk:/usr/obj/usr/src/sys/ARMADA1700 i386 > > > Build Date: 09 February 2009 10:16:23AM > > > > > > Before reporting problems, check http://wiki.x.org > > > to make sure that you have the latest version. > > > Markers: (--) probed, (**) from config file, (==) default setting, > > > (++) from command line, (!!) notice, (II) informational, > > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > > (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 11 10:15:59 2009 > > > (II) Loader magic: 0x81bede0 > > > (II) Module ABI versions: > > > X.Org ANSI C Emulation: 0.4 > > > X.Org Video Driver: 4.1 > > > X.Org XInput driver : 2.1 > > > X.Org Server Extension : 1.1 > > > X.Org Font Renderer : 0.6 > > > (II) Loader running on freebsd > > > (--) Using syscons driver with X support (version 2.0) > > > (--) using VT number 9 > > > > > > (--) PCI:*(0...@0:8:0) Chips and Technologies F6 HiQVPro rev 168, Mem > > > @ 0x4000/0, BIOS @ 0x/65536 > > > List of video drivers: > > > chips > > > (II) LoadModule: "chips" > > > > > > (II) Loading /usr/local/lib/xorg/modules/drivers//chips_drv.so > > > (II) Module chips: vendor="X.Org Foundation" > > > compiled for 1.5.3, module version = 1.2.1 > > > Module class: X.Org Video Driver > > > ABI class: X.Org Video Driver, version 4.1 > > > (II) System resource ranges: > > > [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) > > > [1] -1 0 0x000f - 0x000f (0x1) MX[B] > > > [2] -1 0 0x000c - 0x000e (0x3) MX[B] > > > [3] -1 0 0x - 0x0009 (0xa) MX[B] > > > [4] -1 0 0x - 0x (0x1) IX[B] > > > [5] -1 0 0x - 0x00ff (0x100) IX[B] > > > (II) Primary Device is: PCI 0...@00:08:0 > > > No devices to configure. Configuration failed. > > > > I'll need to see a pciconf -lv, but it looks like the chips driver isn't > > recognizing your chip. You could try the vesa driver. The chips driver > > has not been maintained in quite a while I would say. Hrm, ok... The chips drivers attach routine is a bit odd. It looks like it should work with this chip, but I would have to dig into the driver more than I care to to figure out why it isn't attaching. I would just use vesa... You aren't likely to get much with this driver anyway really... robert. > #pciconf -lv > hos...@pci0:0:0:0:class=0x06 card=0x04600e11 chip=0x71928086 rev=0x02 > hdr=0x00 > vendor = 'Intel Corporation' > device = '82443BX/ZX 440BX/ZX CPU to PCI Bridge (AGP Not Implemented)' > class = bridge > subclass = HOST-PCI > is...@pci0:0:7:0: class=0x060100 card=0x chip=0x71108086 rev=0x02 > hdr=0x00 > vendor = 'Intel Corporation' > device = '82371AB/EB/MB PIIX4/4E/4M ISA Bridge' > class = bridge > subclass = PCI-ISA > atap...@pci0:0:7:1: class=0x010180 card=0x chip=0x71118086 rev=0x01 > hdr=0x00 > vendor = 'Intel Corporation' > device = '82371AB/EB/MB PIIX4/4E/4M IDE Controller' > class = mass storag
Re: 7.4 -> X -configure gives No devices to configure
On Wed, 2009-02-11 at 10:42 +, Anton Shterenlikht wrote: > Upgrade from 7.3 to 7.4 made X unsuable on FBSD 7.1-stable i386. > I followed the UPDATE procedures, had no errors on build, > but on X -configure I get > > No devices to configure. Configuration failed. > > This is a Compaq Armada 1700 laptop, old I know, but 7.3 worked > fine. The graphics is by Chips and Technologies, nothing fancy, > and the driver is xf86-video-chips-1.2.1. The full log is below. > > What's going on? > > many thanks > anton > > *** > > X.Org X Server 1.5.3 > Release Date: 5 November 2008 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.1-STABLE i386 > Current Operating System: FreeBSD mech-aslap33.men.bris.ac.uk 7.1-STABLE > FreeBSD 7.1-STABLE #0: Sat Jan 31 14:31:50 GMT 2009 > me...@mech-aslap33.men.bris.ac.uk:/usr/obj/usr/src/sys/ARMADA1700 i386 > Build Date: 09 February 2009 10:16:23AM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 11 10:15:59 2009 > (II) Loader magic: 0x81bede0 > (II) Module ABI versions: > X.Org ANSI C Emulation: 0.4 > X.Org Video Driver: 4.1 > X.Org XInput driver : 2.1 > X.Org Server Extension : 1.1 > X.Org Font Renderer : 0.6 > (II) Loader running on freebsd > (--) Using syscons driver with X support (version 2.0) > (--) using VT number 9 > > (--) PCI:*(0...@0:8:0) Chips and Technologies F6 HiQVPro rev 168, Mem @ > 0x4000/0, BIOS @ 0x/65536 > List of video drivers: > chips > (II) LoadModule: "chips" > > (II) Loading /usr/local/lib/xorg/modules/drivers//chips_drv.so > (II) Module chips: vendor="X.Org Foundation" > compiled for 1.5.3, module version = 1.2.1 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 4.1 > (II) System resource ranges: > [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) > [1] -1 0 0x000f - 0x000f (0x1) MX[B] > [2] -1 0 0x000c - 0x000e (0x3) MX[B] > [3] -1 0 0x - 0x0009 (0xa) MX[B] > [4] -1 0 0x - 0x (0x1) IX[B] > [5] -1 0 0x - 0x00ff (0x100) IX[B] > (II) Primary Device is: PCI 0...@00:08:0 > No devices to configure. Configuration failed. I'll need to see a pciconf -lv, but it looks like the chips driver isn't recognizing your chip. You could try the vesa driver. The chips driver has not been maintained in quite a while I would say. robert. -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: Xorg upgrade desaster: Xlib: extension "Generic Event Extension" missing on display ":0.0".
On Fri, 2009-01-30 at 18:23 -0500, Alex Goncharov wrote: > ,--- You/O. (Fri, 30 Jan 2009 23:19:41 +0100) * > | After upgrading one of my FreeBSD 8.0-CUR/amd64 boxes to new xorg-7.4 > | and having done hurting recompiling nearly everything/package twice now > | firefox3 still doesn't work properly and hits me when starting with this > | error message: > | > | Xlib: extension "Generic Event Extension" missing on display ":0.0". > > Interesting -- I just did my comprehensive upgrade, as a part of which > xorg-server went from 1.5.3_1,1 to 1.5.3_2,1. > > And this is what I see now, for the first time, and consistently: > > > $ xterm& > [3] 12585 > > $ emacs & > [4] 12644 > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". > Xlib: extension "Generic Event Extension" missing on display ":0.0". This is harmless, it indicates that libXext has support for generic events, but the server does not yet. robert. > > > The garbage still pollutes my windows periodically, so, I guess, my > next xorg-server will be 1.4. > > For reference, my system is: > >i386 FreeBSD 7.1-STABLE Sun Jan 25 06:28:38 EST 2009 > > It not being CURRENT, I took the liberty of cc: freebsd-po...@freebsd.org. > > -- Alex -- alex-goncha...@comcast.net -- > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
