Re: Handbook Index
On Tue, 02 Mar 2010 11:25:42 +0800 Fbsd1 fb...@a1poweruser.com wrote: I find it very hard to find the subject I am looking for in the handbook. The index only gets me to the general area in the handbook and then I have to (next page) through it looking for what I hope is there. The Index really needs to be expanded to display each and every sub-section of all the major sections now in the index. For example Installing from a ms/dos partition or splash screen usage. These are both subjects in the handbook but are not in the index. What good is am index that does not index its content? The purpose of the index is to list all subjects documented in the handbook so the reader can skim through the index and click on the exact subject they want to read. Can not do that with the current handbook index. So what do other people think? Should I submit a Doc bug on this?? Hi A1Poweruser, why don't you build book.txt (add WITH_TXT=yes to /etc/make.conf and rebuild the docs port)? Then you can just use grep to search for what you want. With the examples you gave, grep -in msdos or grep -in splash screen give me a few places to look. An index is useful in a dead-tree book, but for a 4Mb text file you might as well use grep. Tony ___ 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: XFCE keyboard layout tab missing
On Fri, 27 Jan 2012 02:12:09 + Neil Munro neilmu...@gmail.com wrote: Hi all, first I apologise if this is a known issue, I have been searching but can't seem to find an answer. I am looking to switch to FreeBSD full time and this is the only thing holding me back I want to run XFCE and I know the 4.8 release has some issues with mounting devices which used to use HAL but doesn't now, from what I understand of the issue it's not a deal breaker for me, what I am struggling with is that I cannot set the keyboard in XFCE to dvorak, as the layout tab is missing and the keyboard icon in the settings window has no icon. I imagined this was at first just requiring the correct language pack but having installed the GB language pack the missing tab does not appear. Additionally I recompiled xfce4-settings with all options enabled to no avail. Does anyone know what may be causing this issue? Many thanks, Neil Hi Neil, I think you need to install the port /usr/ports/deskutils/xfce4-xkb-plugin (or package if you prefer). Tony ___ 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
Problem syncing Palm TX with jpilot on FreeBSD 8.0-BETA3
Hello, I am running FreeBSD 8.0-BETA3 amd64 and am having trouble syncing my Palm TX with jpilot. This used to work with 7.2-STABLE amd64 and I suspect I'm just not using the usb: connection correctly but have not been able to find a solution by searching the archives. I am running a custom kernel with device uvisor commented out, though the same problem occurs if I recompile with uvisor included. When I plug in the Palm TX I get the following at the end of dmesg output: ugen0.4: Palm, Inc. at usbus0 ugen0.4: Palm, Inc. at usbus0 (disconnected) If I tell jpilot to sync with a Palm at usb: I get the following error message: dlp_OpenConduit() failed Sync canceled Exiting with status SYNC_ERROR_OPEN_CONDUIT Finished. I also have the following in my /etc/devfs.rules: add path 'ugen*' unhide mode 0660 group operator and I am a member of the operator group. What should I set to get hotsync working? Thanks all in anticipation, Tony ___ 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: Problem syncing Palm TX with jpilot on FreeBSD 8.0-BETA3
On Thu, 27 Aug 2009 09:36:22 +0200 Marc Fonvieille black...@freebsd.org wrote: First you need to have uvisor(4) loaded (compiled in the kernel or via the loaded module). Last uvisor(4) revision was not merged in BETA3 so you will have to wait for the merge or directly grab it from http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/usb/serial/uvisor.c?rev=1.12;content-type=text%2Fplain;only_with_tag=HEAD replace you src/sys/dev/usb/serial/uvisor.c with that one and rebuild your module/kernel Then if you plug your device and launch Hotsync on the Palm a /dev/cuaU0 device should appear. You should check that. If you have jpilot installed, palm/pilot-link tools are installed (be sure it was compiled with USB support), so once the /dev/cuaU0 device node is created you can type: # pilot-xfer -p /dev/cuaU0 -l this should list the installed files on your device, # pilot-xfer -p /dev/cuaU0 -b your_backup_dir to backup your palm on your PC. If these commands worked, then jpilot should work as well. Marc, many thanks, that was a great help. I uncommented uvisor in the kernel config file, installed the newer uvisor.c, rebuilt and installed the new kernel. Pressing the hotsync button did indeed create a /dev/cuaU0 but I had to add myself to the 'dialer' group to use it. Palm syncing now works again with jpilot! BTW, when might that newer uvisor.c be merged into the RELENG_8 sources? Thanks also to Roland. I already had add path 'usb/*' in my /etc/devfs.rules. Best wishes, Tony ___ 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
DVD drive not detected
Hello, I am currently using 8.0-BETA4 amd64 and I noticed yesterday that my PC's internal DVD reader/writer is not detected at boot time. I'm not sure whether or not this was the case with BETA3 since I don't use the drive all that often. It was certainly working ok with 7.2-STABLE though. I have copied and pasted the messages from dmesg.boot below, in case that is of help in diagnosing the problem. If I remember correctly, it used to appear as /dev/acd0. Thanks in advance for any suggestions. Tony dmesg.boot -- Copyright (c) 1992-2009 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 8.0-BETA4 #11: Wed Sep 9 10:55:38 BST 2009 r...@elena.home:/usr/obj/usr/src/sys/ELENA Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (3000.00-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Stepping = 10 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=0x408e3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE AMD Features=0x2800SYSCALL,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 4112650240 (3922 MB) ACPI APIC Table: 071508 APIC1340 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: 071508 RSDT1340 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, cff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 1.0 (no driver attached) pci0: memory, RAM at device 1.1 (no driver attached) pci0: memory, RAM at device 1.2 (no driver attached) pci0: memory, RAM at device 1.3 (no driver attached) pci0: memory, RAM at device 1.4 (no driver attached) pci0: memory, RAM at device 1.5 (no driver attached) pci0: memory, RAM at device 1.6 (no driver attached) pci0: memory, RAM at device 2.0 (no driver attached) isab0: PCI-ISA bridge port 0x4f00-0x4fff at device 3.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 3.1 (no driver attached) pci0: memory, RAM at device 3.2 (no driver attached) pci0: processor at device 3.3 (no driver attached) pci0: memory, RAM at device 3.4 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xf9f7f000-0xf9f7 irq 22 at device 4.0 on pci0 ohci0: [ITHREAD] usbus0: OHCI (generic) USB controller on ohci0 ehci0: EHCI (generic) USB 2.0 controller mem 0xf9f7ec00-0xf9f7ecff irq 23 at device 4.1 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: EHCI (generic) USB 2.0 controller on ehci0 atapci0: nVidia nForce MCP73 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 8.0 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] hdac0: NVidia MCP73 High Definition Audio Controller mem 0xf9f78000-0xf9f7bfff irq 20 at device 9.0 on pci0 hdac0: HDA Driver Revision: 20090624_0136 hdac0: [ITHREAD] pcib1: ACPI PCI-PCI bridge at device 10.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 11.0 on pci0 pci2: ACPI PCI bus on pcib2 vgapci0: VGA-compatible display port 0xec00-0xec7f mem 0xfd00-0xfdff,0xd000-0xdfff,0xfa00-0xfbff irq 16 at device 0.0 on pci2 pcib3: ACPI PCI-PCI bridge at device 12.0 on pci0 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 13.0 on pci0 pci4: ACPI PCI bus on pcib4 atapci1: nVidia nForce MCP73 SATA300 controller port 0xd480-0xd487,0xd400-0xd403,0xd080-0xd087,0xd000-0xd003,0xcc00-0xcc0f mem 0xf9f7c000-0xf9f7dfff irq 21 at device 14.0 on pci0 atapci1: [ITHREAD] atapci1: AHCI v1.10 controller with 4 3Gbps ports, PM supported ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] ata4: ATA channel 2 on atapci1 ata4: [ITHREAD] ata5: ATA channel 3 on atapci1 ata5: [ITHREAD] nfe0: NVIDIA nForce MCP73 Networking Adapter port 0xc880-0xc887 mem 0xf9f77000-0xf9f77fff,0xf9f7e800-0xf9f7e8ff,0xf9f7e400-0xf9f7e40f irq 22 at device 15.0 on pci0 miibus0: MII bus on nfe0 rlphy0: RTL8201L 10/100 media interface PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto nfe0: Ethernet address: 00:24:21:1d:e3:e3 nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER] nfe0: [FILTER]
Re: flashplugin
On Tue, 27 Oct 2009 16:43:11 -0500 PJ af.gour...@videotron.ca wrote: I wish someone could explain to me why I am no longer able to install flashplugin ... none of the methods work for me on amy version... I have literally tried them all.. the latest was linux-f10 - I cleaned out all the linux stuff, umounted the proc sytem cleaned out everything I could find related (?) to linux and reinstalled. No go, no way, José! I did catch some kind of warning that flashed by on the screen about Glib - seems to be gstreamer related...??? and the only thing I can find is the error message that flashplugin.so (or whatever the file is) could not be loaded because shared file libfreetype.so.6 could not be found... and the only libfreetype.so.6 file on the s;ystem is ...so.6.something.something... If the system is smart enought to not find the right file, it ought to be smart enought to know where this file should be and to what it is related... duh ! Hi PJ, I hope you won't take this the wrong way, it really isn't intended to be an insult, but looking at your posting history I seriously wonder if FreeBSD is for you. You seem to want everything to just work without having to think about it, so perhaps Windows would be better for you? You ask questions in a very random way, try things without any clear plan, and when given advice you seem to quickly move on to some other difficulty rather than getting used to one thing at a time. It does take time and effort to learn to use FreeBSD effectively, but once you have learned it (i.e., started to gain a deep understanding of how things work separately and together rather than just managing to fix things piecemeal without any real understanding) it works wonderfully with a huge range of hardware and software. If you do want to stick with FreeBSD it might be better if you just sat down with the Manual and read through systematically before trying to tweak things. But my guess is that you really would be happier and more productive with a Windows OS. That isn't meant to be a please go away and let us get on with using FreeBSD, it is an honest reaction to the pain and confusion you seem to cause yourself as you randomly try things in FreeBSD. Best, Tony ___ 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: flashplugin
On Wed, 28 Oct 2009 14:10:25 +0100 Polytropon free...@edvax.de wrote: In Windows, things don't work without thinking. The misbelief that is does is grounded in the fact that other people have to deal with problems, while the user praises Windows for its easyness of use. In PJ's case, maybe PC-BSD is a good choice. As far as I know, they offer a working Flash plugin that can be installed by their PBI system. I haven't tested this because PC-BSD with its KDE centric concept simply isn't my cup of tea, but that doesn't mean that it's not a good OS - hey, it's still FreeBSD. :-) Tony, I can understand that you might get the impression that PJ doesn't have a full understanding of the concepts and procedures needed to know in order to properly operate FreeBSD. This may be true. But he's constantly learning and understanding, and I think even with the troubles he likes to use FreeBSD (PJ, correct me if I'm wrong). When I came to FreeBSD (from a Linux and WEGA background, with lots of strange mainframe knowledge), I had similar trouble. I had many issues with C, too, before it became my primary programming language, but the fact that I can master FreeBSD now (at a sufficient level) is due to the fact that I had much good help, especially from this list, as well as much practice. Recognizing and resolving library requirements can surely be such a step into the right direction. It's not a state, it's a process. In the future, PJ will not only know that things work, but additionally understand *how* and *why* they work, and this will make him a master of FreeBSD, too. Hi Polytropon, thanks, I hope you are right, and I would love to see PJ become a master of FreeBSD, but my impression from the mailing list is that that progress is going to be too long and too frustrating. I suppose only PJ can know if he/she feels that progress is happening. Nonetheless, I stand by the advice to work systematically through the handbook and try to gain a real understanding rather than a series of fixes. I suppose I was suggesting that rather than address endless frustrating symptoms of what looks like a mismatch between PJ's character (not ability, I certainly do not wish to disparage that - by character I mean a reluctance to stand back, slow down and approach the learning systematically and to give it the time it will need) and the FreeBSD way of doing things, it might be better to just move to something more pre-packaged. PC-BSD may well be a good choice, I haven't tried it. Oh, and you are exactly right about the kind of understanding that can come with spending time with FreeBSD. But perhaps it's not for everyone. Best, Tony ___ 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: flashplugin
On Wed, 28 Oct 2009 09:13:02 -0400 PJ af.gour...@videotron.ca wrote: But to study the manual is beyond the capabilities of anyone ... sure, you can read it and study it... but you will forget anything you have read almost immediately if you are not applying what you are studying at once... there may be some residual information captured by one's brain but practical application is about the only way to really learn and understand... especially with the help of those who have dared to tread there before you... and their help is really invaluable. Hi PJ, ok, I tried (I was also trying to offer you support, just a different kind). There was a lot of irrelevant material in your response but the part I have quoted shows such a deep misunderstanding of what I was trying to suggest that I think I'm done. I honestly hope you do get past your headaches with FreeBSD, one way or another. Best, Tony ___ 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: flashplugin
On Wed, 28 Oct 2009 16:00:00 + Tony McC af...@btinternet.com wrote: Hi PJ, ok, I tried (I was also trying to offer you support, just a different kind). There was a lot of irrelevant material in your response but the part I have quoted shows such a deep misunderstanding of what I was trying to suggest that I think I'm done. I honestly hope you do get past your headaches with FreeBSD, one way or another. Replying to myself, sorry. I think I owe you an apology for a grumpy response. I think it comes down to the fact our learning styles must be very different. You seem to like to try things first and then try to understand when things go wrong. I like to gain a reasonably firm theoretical understanding first and then try out things according to a plan, keeping notes at each stage. When something happens that I don't understand then of course I learn from that. I think we are just different. So no, I'm not suggesting you learn the manual by heart before going any further. I am suggesting that you *start* with the manual, take it step by step, and only try things that might break your system when a) you think you have a firm grasp of what you are doing and b) you have a contingency plan to revert to the way things were before if something surprising happens. And, again, as part of a learning style, when I do come across those uncomfortable surprises (and I do), I generally assume that I must have done something stupid, not that FreeBSD itself is stupid. That is also a learning experience for me. Best, Tony ___ 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: evince problem
On Sun, 13 Jun 2010 07:48:48 +0200 Istvan Galgand igalg...@freemail.hu wrote: Dear All, Gnome desktop. Right click e.g. on BSD_06_2010.pdf icon, selecting open with document viewer. A few seconds later the process dies. Regarding the issue by means of Google I have found two pieces of information. First: check the content of /etc/rc.conf: dbus_enable=YES, it is included. Second: use ePDFViewer instead of document viewer. I am actually using this and doing a very nice job... My question is, shall I give up using document viewer or is there any idea how to put document viewer into operation? One more thing: pkg_version -v | grep evince evince-2.30.1_1 = up-to-date with port If you type: evince BSD_06_2010.pdf at a command prompt, do you see any error messages? Tony ___ 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
