Re: ISDN4BSD removal
On Friday 08 October 2010 12:22:40 pm Dimitry Andric wrote: On 2010-10-08 18:12, Torfinn Ingolfsen wrote: Another thing about VoIP calls: have they solved the emergency call needs a location problem? Here (again: in Norway) they are still working out how to solve this: if you call emergency services (police, fire department, etc.) from yout VoIP number; how do the emergency center locate you? Ehm, you tell them? You have them on the phone. :) Um, could be a kid that dialed the phone, or someone may have lost consciousness. How can this still be a problem? Congres mandated that all phones have GPS, didn't they? ___ 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: loading module sdhci causes panic
On Sunday 14 February 2010 01:53:11 pm Gavin Atkinson wrote: On Sat, 30 Jan 2010, Steven Friedrich wrote: snip What happens if you just load sdhci? panic WHat happens if you load sdhci and mmcsd, but not mmc? panic WHat happens if you load sdhci and mmc, but not mmcsd? panic Given how early in the boot process you see problems, I'm wondering if this is somehow related to PR kern/141756... Thanks, Gavin If I load sdhci as a module, the system panics with a page fault while in kernel mode. All is ok if I build sdhci into the kernel. ___ 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: [HEADSUP]: ports feature freeze now in effect
On Monday 15 February 2010 12:19:01 pm Erwin Lansing wrote: In preparation for 7.3-RELEASE, the ports tree is now in feature freeze. Normal upgrade, new ports, and changes that only affect other branches are allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commts to ports with unusually high number of dependent ports, and any other commit that requires the rebuilding of many packages is not allowed without prior explicit approval from portmgr after that date. When in doubt, please do not hesitate to contact portmgr. -erwin I suspect this means we won't get KDE 4.4 for quite some time... ___ 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: loading module sdhci causes panic
On Sunday 31 January 2010 07:33:19 pm Steven Friedrich wrote: On Sunday 31 January 2010 05:57:14 pm Jeremy Chadwick wrote: On Sun, Jan 31, 2010 at 04:44:39PM -0500, Steven Friedrich wrote: On Saturday 30 January 2010 08:56:06 am Bartosz Fabianowski wrote: Can anyone verify that sdhci is compatible with FreeBSD 8? I loaded mmc, mmcsd, and sdhci when I first installed FreeBSD 8.0 without any problems. Since then, I have updated to -STABLE and put these three devices in my kernel configuration file. No problems either. It must be very recent breakage or some incompatibility with your particular hardware. - Bartosz When I add the three drivers to my kernel, I don't get a panic, but when I insert an SD 1GB card, nothing happens. pciconf -lv reveals that the driver attached to my device: sdh...@pci0:11:0:4: class=0x080500 card=0x3082103c chip=0x8034104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'SDA Standard Compliant SD Host Controller (10981734)' class = base peripheral subclass = SD host controller I verified that this SD card is recognized by Windows XP. When I plug in a card, should some message appear on the console? Will it auto-mount? Can you please post your entire kernel configuration file (specifically the one which includes the above 3 drivers in it)? # # LAPTOP -- Laptop kernel configuration file for FreeBSD/i386 # ident LAPTOP machine i386 cpu I586_CPU cpu I686_CPU # To statically compile in device wiring instead of /boot/device.hints #hintsLAPTOP.hints # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols # hopefully, cure the shutdown anomaly options PRINTF_BUFR_SIZE=128 options INCLUDE_CONFIG_FILE options SCHED_ULE # ULE scheduler #options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption # IPI_PREEMPTION instructs the kernel to preempt threads running on other # CPUS if needed. Relies on the PREEMPTION option options IPI_PREEMPTION options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling #options MD_ROOT # MD is a potential root device options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework #options GEOM_GPT# GUID Partition Tables. # The options COMPAT_43 kernel configuration option has been deemed unnecessary and # has been removed from GENERIC and related kernel configurations. This change may # result in a small performance increase for some workloads. #options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev #options ADAPTIVE_GIANT # Giant mutex is adaptive. options SC_HISTORY_SIZE=1000 options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache options KTRACE # ktrace(1) support options STACK # stack(9) support #options KDTRACE_HOOKS # Kernel DTrace hooks # PERFMON causes the driver for Pentium/Pentium Pro performance counters # to be compiled. See perfmon(4) for more
Re: loading module sdhci causes panic
On Saturday 30 January 2010 08:56:06 am Bartosz Fabianowski wrote: Can anyone verify that sdhci is compatible with FreeBSD 8? I loaded mmc, mmcsd, and sdhci when I first installed FreeBSD 8.0 without any problems. Since then, I have updated to -STABLE and put these three devices in my kernel configuration file. No problems either. It must be very recent breakage or some incompatibility with your particular hardware. - Bartosz ___ 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 When I add the three drivers to my kernel, I don't get a panic, but when I insert an SD 1GB card, nothing happens. pciconf -lv reveals that the driver attached to my device: sdh...@pci0:11:0:4: class=0x080500 card=0x3082103c chip=0x8034104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'SDA Standard Compliant SD Host Controller (10981734)' class = base peripheral subclass = SD host controller I verified that this SD card is recognized by Windows XP. When I plug in a card, should some message appear on the console? Will it auto-mount? ___ 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: loading module sdhci causes panic
On Sunday 31 January 2010 05:57:14 pm Jeremy Chadwick wrote: On Sun, Jan 31, 2010 at 04:44:39PM -0500, Steven Friedrich wrote: On Saturday 30 January 2010 08:56:06 am Bartosz Fabianowski wrote: Can anyone verify that sdhci is compatible with FreeBSD 8? I loaded mmc, mmcsd, and sdhci when I first installed FreeBSD 8.0 without any problems. Since then, I have updated to -STABLE and put these three devices in my kernel configuration file. No problems either. It must be very recent breakage or some incompatibility with your particular hardware. - Bartosz When I add the three drivers to my kernel, I don't get a panic, but when I insert an SD 1GB card, nothing happens. pciconf -lv reveals that the driver attached to my device: sdh...@pci0:11:0:4: class=0x080500 card=0x3082103c chip=0x8034104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'SDA Standard Compliant SD Host Controller (10981734)' class = base peripheral subclass = SD host controller I verified that this SD card is recognized by Windows XP. When I plug in a card, should some message appear on the console? Will it auto-mount? Can you please post your entire kernel configuration file (specifically the one which includes the above 3 drivers in it)? # # LAPTOP -- Laptop kernel configuration file for FreeBSD/i386 # ident LAPTOP machine i386 cpu I586_CPU cpu I686_CPU # To statically compile in device wiring instead of /boot/device.hints #hints LAPTOP.hints # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols # hopefully, cure the shutdown anomaly options PRINTF_BUFR_SIZE=128 options INCLUDE_CONFIG_FILE options SCHED_ULE # ULE scheduler #optionsSCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption # IPI_PREEMPTION instructs the kernel to preempt threads running on other # CPUS if needed. Relies on the PREEMPTION option options IPI_PREEMPTION options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling #optionsMD_ROOT # MD is a potential root device options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework #optionsGEOM_GPT# GUID Partition Tables. # The options COMPAT_43 kernel configuration option has been deemed unnecessary and # has been removed from GENERIC and related kernel configurations. This change may # result in a small performance increase for some workloads. #optionsCOMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev #optionsADAPTIVE_GIANT # Giant mutex is adaptive. options SC_HISTORY_SIZE=1000 options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache options KTRACE # ktrace(1) support options STACK # stack(9) support #optionsKDTRACE_HOOKS # Kernel DTrace hooks # PERFMON causes the driver for Pentium/Pentium Pro performance counters # to be compiled. See perfmon(4) for more information. # options PERFMON # To make an SMP kernel, the next line is needed options SMP
loading module sdhci causes panic
I stopped the boot before the timer expired, after it had loaded modules specified in /boot/loader.conf I loaded mmc, mmcsd, and sdhci. I continued the boot, and it panic'ed right after apic. I rebooted everal times, to load each individually, to narrow it down to sdhci. Can anyone verify that sdhci is compatible with FreeBSD 8? I updated and built today. ___ 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: loading module sdhci causes panic
On Saturday 30 January 2010 11:04:15 am Alexander Motin wrote: Steven Friedrich wrote: I stopped the boot before the timer expired, after it had loaded modules specified in /boot/loader.conf I loaded mmc, mmcsd, and sdhci. I continued the boot, and it panic'ed right after apic. I rebooted everal times, to load each individually, to narrow it down to sdhci. Can anyone verify that sdhci is compatible with FreeBSD 8? I updated and built today. I am using it daily since written it and till present 9-CURRENT. Show your verbose boot messages and crash information. I updated source and built world and kernel today. My machine won't complete a dump and reboot. I'll work on that, but the below text is from a successful boot, and I show where the panic occurred. I don't build all modules, but I added mmc, mmcsd, and sdhci to the var in make.conf. When this all began, I had built the modules and loaded them by hand. There was no panic, so I added them to /boot/loader.conf and then it panic'ed. I've also made it panic by stopping the boot and hand-loading the three modules. I haven't built these into a kernel... Copyright (c) 1992-2010 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-STABLE #31: Sat Jan 30 16:19:51 EST 2010 ad...@laptop2.stevenfriedrich.org:/usr/obj/usr/src/sys/LAPTOP i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 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=0x641dSSE3,DTES64,MON,DS_CPL,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2094256128 (1997 MB) ACPI APIC Table: HP 3082 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0 Version 2.0 irqs 0-23 on motherboard Here, it reported a trap 12 page fault while in Kernel mode fault code supervisor read, page not present The next line would have been: video4bsd: /dev/video0..9, /dev/video_daemon0..9 Here's a snip from the original topic and a response: On Friday 29 January 2010 23:14:06 Steven Friedrich wrote: I'd like to access the digital media slots on my laptop. Specifically, I want to read Sony Memory Sticks. pciconf -lv shows the devices: no...@pci0:11:0:3:class=0x018000 card=0x3082103c chip=0x8033104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'PCIxx11/21 Integrated FlashMedia Controller' class = mass storage no...@pci0:11:0:4:class=0x080500 card=0x3082103c chip=0x8034104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'SDA Standard Compliant SD Host Controller (10981734)' class = base peripheral subclass = SD host controller Probably supported by sdhci(4). I don't know which of the two controllers supports Sony Memory Sticks, but I figured I'd get the drivers installed and try it. ___ freebsd-stable
Re: 8.0-RELEASE - -STABLE and size of /
On Friday 22 January 2010 11:46:01 am Torfinn Ingolfsen wrote: On Fri, 22 Jan 2010 17:21:56 +0100 Oliver Brandmueller o...@e-gitt.net wrote: Instaling the new kernel failed, since /boot/kernel/ is already well over 230 MBytes in size. moving that to kernel.old and writing a new one with about the same size fails due to no space left on device. This is not a question; I do know how to get around this and how to configure custom kernels so they are a fragment of that size afterwards. It would also be nice if we knew how to configure the whole make world procedure[1] to make a new kernel and modules without symbols. The FAQ doesn't seem to have that answer either. References: 1) http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html in your /etc/make.conf, do you have a line like: makeoptions DEBUG=-g if so, comment it out. ___ 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: 8.0-RELEASE - -STABLE and size of /
On Friday 22 January 2010 06:32:02 pm Oliver Brandmueller wrote: Hi, On Fri, Jan 22, 2010 at 03:56:31PM -0500, Steven Friedrich wrote: in your /etc/make.conf, do you have a line like: makeoptions DEBUG=-g if so, comment it out. The GENEREIC kernel by default has the following config: makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols You don't need anything special in your make.conf In fact having the debug symbols is useful in many cases. So raising the default size for the / partition might be the better option (OK, doesn't help for already installed systems of course). - Oliver I'm sorry. My response to him should have been more precise. I was trying to clue him in on how to build a non-debug kernel, but my answer was in fact wrong. I said he may have a line in make.conf, but that was a mistake. I pulled the line from a kernel config file. If he wants to build a kernel with no symbols, as he stated he does, he needs to comment out the line and build a kernel. Could buildworld and installworld, too. But he and I went off topic. I should have changed the subject line to start a new thread to discuss building without symbols. He was complaining that it wasn't in the FAQ or the handbook. It's in GENERIC, which is required reading if you're ever going to build custom kernels. As for the main topic, I have been making 4GB root partitions for some time. Our disk requirements have been soaring over the last decade, while cost per MB have plummeted. I don't want to have to guess what sizes each partition should be. ___ 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: 8.0 stable if_bwi kmod not exist?
On Tuesday 19 January 2010 12:44:16 am wsk wrote: folks, There is not exist if_bwi.ko module in /boot/kernel under 8.0 Stable why? ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org Perhaps in /etc/make.conf, you define modules you want to build and this is a new one to be added? Look at variables MODULES_OVERRIDE and WITHOUT_MODULES. ___ 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: USB problems on 8.0-STABLE
On Saturday 09 January 2010 06:11:45 pm Frank wrote: On Sat, 9 Jan 2010, Steven Friedrich wrote: USB. I'm betting USB and I'm thinking that maybe the driver you used to use hasn't been converted to the new USB system in 8-Stable. If that's the case it makes sense. I guess I'll just have to wait until it's converted. Is it possible to boot one of your machines to an older release of FreeBSD, so you can discover what device driver you had been using, if any. Or any old logs may have the info. I haven't had an APC UPS, so I'm unfamiliar with apcupsd. Hope this is what you mean. On 7.2-STABLE the UPS attached to ugen0. It is the same now. P.S. Per the pkg-message directions I have commented out uhid in the kernel config file, compiled and installed. Is this still necessary? -- Frank I think someone is going to have to update apcupsd with changes necessary to be compatible with FreeBSD 8's new USB arch. I haven't seen any documentation, white paper, etc., that discusses what changes would be needed. You could try sending an email to the port's maintainer... ___ 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: USB problems on 8.0-STABLE
On Saturday 09 January 2010 06:50:59 am Frank wrote: On Fri, 8 Jan 2010, Steven Friedrich wrote: OK, first a disclaimer. I am not a FreeBSD developer, but I have been admin'ing my own *nix systems for decades. I think this is weird: ugen0.2: American Power Conversion at usbus0 What device or port was this on previous to 8-Stable? Is it connected via serial cable (rs232) or USB? USB. I'm betting USB and I'm thinking that maybe the driver you used to use hasn't been converted to the new USB system in 8-Stable. If that's the case it makes sense. I guess I'll just have to wait until it's converted. Is it possible to boot one of your machines to an older release of FreeBSD, so you can discover what device driver you had been using, if any. Or any old logs may have the info. I haven't had an APC UPS, so I'm unfamiliar with apcupsd. ___ 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: USB problems on 8.0-STABLE
On Friday 08 January 2010 05:47:55 pm Frank wrote: I am having problems with mouse, keyboard and APC UPS. When attempting to start apcupsd I get the following error: Jan 8 17:42:06 Ace apcupsd[1606]: apcupsd FATAL ERROR in generic-usb.c at line 636 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. Jan 8 17:42:06 Ace apcupsd[1606]: apcupsd error shutdown completed In X, I must move the mouse to get anything to update. For example, if I type in an xterm nothing will display or happen until the mouse is moved. This also happens using a browser or any other app. # dmesg | grep usb usbus0: OHCI (generic) USB controller on ohci0 usbus1: EHCI version 1.0 usbus1: EHCI (generic) USB 2.0 controller on ehci0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: nVidia at usbus0 uhub0: nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 ugen1.1: nVidia at usbus1 uhub1: nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus1 Root mount waiting for: usbus1 Root mount waiting for: usbus1 Root mount waiting for: usbus1 Root mount waiting for: usbus1 ugen0.2: American Power Conversion at usbus0 ugen0.3: vendor 0x0461 at usbus0 ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 3 on usbus0 ugen0.4: Dell at usbus0 ukbd0: Dell Dell USB Keyboard, class 0/0, rev 1.10/3.01, addr 4 on usbus0 Ace /usr/ports # usbdevs -d -v usbdevs: no USB controllers found Ace /usr/ports # usbconfig ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 American Power Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.3: USB Optical Mouse vendor 0x0461 at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.4: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON World and kernel built last night. -- Frank ___ 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 Check your /etc/X11/xorg.conf Make sure Option AllowEmptyInput is not on, 1, true, etc. We needed this option as a temporary work-around when a bug existed during the code freeze during the FreeBSD8.0 release process. So if you install FreeBSD 8.0-RELEASE from any media, to get Xorg to see your mouse, you'll have to add this option to the ServerOptions section of xorg.conf. If you then update your ports, you'll get a newer Xorg than was frozen for the 8.0 RELEASE, and you'll have to remove the option. ___ 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: USB problems on 8.0-STABLE
On Friday 08 January 2010 07:25:04 pm Frank wrote: On Fri, 8 Jan 2010, Steven Friedrich wrote: Check your /etc/X11/xorg.conf Make sure Option AllowEmptyInput is not on, 1, true, etc. We needed this option as a temporary work-around when a bug existed during the code freeze during the FreeBSD8.0 release process. So if you install FreeBSD 8.0-RELEASE from any media, to get Xorg to see your mouse, you'll have to add this option to the ServerOptions section of xorg.conf. If you then update your ports, you'll get a newer Xorg than was frozen for the 8.0 RELEASE, and you'll have to remove the option. This is what I have in /etc/X11/xorg.conf: Section ServerLayout Identifier X.org Configured Screen Screen0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard Option AutoAddDevices on Option AutoEnableDevices on Option AllowEmptyInput off EndSection -- Frank ___ 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 Comment out the line containing AllowEmptyInput. ___ 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: USB problems on 8.0-STABLE
On Friday 08 January 2010 08:47:54 pm Frank wrote: On Fri, 8 Jan 2010, Steven Friedrich wrote: Option AllowEmptyInput off EndSection Comment out the line containing AllowEmptyInput. OK, this took care of the nothing-works-unless-mouse-is-moved problem but why do I get this? It's keeping apcupsd from starting. Ace /usr/ports # usbdevs -d -v usbdevs: no USB controllers found Ace /usr/ports # usbconfig ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 American Power Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.3: USB Optical Mouse vendor 0x0461 at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.4: Dell USB Keyboard Dell at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON From dmesg: usbus0: OHCI (generic) USB controller on ohci0 usbus1: EHCI version 1.0 usbus1: EHCI (generic) USB 2.0 controller on ehci0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: nVidia at usbus0 uhub0: nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 ugen1.1: nVidia at usbus1 uhub1: nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus1 Root mount waiting for: usbus1 Root mount waiting for: usbus1 ugen0.2: American Power Conversion at usbus0 ugen0.3: vendor 0x0461 at usbus0 ums0: vendor 0x0461 USB Optical Mouse, class 0/0, rev 2.00/2.00, addr 3 on usbus0 ugen0.4: Dell at usbus0 ukbd0: Dell Dell USB Keyboard, class 0/0, rev 1.10/3.01, addr 4 on usbus0 I don't understand why usbdevs can't find any controllers and apcupsd can't find any device while the kernel and usbconfig can find it all. Thanks. -- Frank ___ 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 OK, first a disclaimer. I am not a FreeBSD developer, but I have been admin'ing my own *nix systems for decades. I think this is weird: ugen0.2: American Power Conversion at usbus0 What device or port was this on previous to 8-Stable? Is it connected via serial cable (rs232) or USB? I'm betting USB and I'm thinking that maybe the driver you used to use hasn't been converted to the new USB system in 8-Stable. ___ 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: Why does FreeBSD 8.-0 think that my Dell SX260 have non-unform processors?
On Tuesday 22 December 2009 06:41:30 pm Torfinn Ingolfsen wrote: On Mon, 21 Dec 2009 21:21:45 + (GMT) FreeBSD 7.2-STABLE #6: Sun Oct 11 11:14:33 CEST 2009 CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (1295.21-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,M CA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FX SR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNXT-ID,xTPR Logical CPUs per core: 2 ACPI APIC Table: DELL SX260 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Changing APIC ID to 2 My first thought was that perhaps you were running a uniprocessor kernel, but I checked GENERIC and SMP option is there. My dmesg is a little different: FreeBSD 8.0-STABLE #16: Sat Dec 19 22:56:44 EST 2009 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 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=0x641dSSE3,DTES64,MON,DS_CPL,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM TSC: P-state invariant FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 I think the clue to run down is why does FreeBSD think your sx260 is running at 1295.21-MHz. I think I would try updating your usb stick's kernel with 8-stable and rebuild it. I'm wondering if someone who made the stick image turned off SMP to make i fit on small sticks (above is 7.2-stable, not the 8 on a stick). I see HTT in your CPUs features, but I wonder what that's based on. What if the BIOS supports hyperthreading but the cpu doesn't? (there were p4 processors sold before hyperthreading came out, I know, I bought one. 8o) You might try finding a cpu diagnostic tool that describes the cpu in great detail, like from download.com, etc. You might also go to Intel's site and lookup the id 0xf29 and see if Intel says it actually supports hyperthreading. ___ 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: atheros issues with releng_8
On Monday 21 December 2009 09:23:57 pm Zane C.B. wrote: With the GENERIC kernel on releng_8 and releng_8_0, I am having issues with the Atheros wireless on my laptop. Upon boot I am getting the message below. ath0: Atheros 5424/2424 irq 17 at device 0.0 on pci3 ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x). ath0: cannot map register space device_attach: ath0 attach returned 6 Any suggestions? It was working fine on releng_6. I believe that you don't realize that under FreeBSD 8, you now have to use a wlan interface. Under FreeBSD7.2, I used a Windows ethernet driver, wrapped with NDIS (see ndisgen). Here's the line from /etc/rc.conf: ifconfig_ndis0=wpa dhcp Note that this line is simplified because a lot of the info, like SSID, is in /etc/wpa_supplicant.conf. (yes, I put it there) Under FreeBSD8.0R, you must use the wlan interface. wlans_ndis0=wlan0 # wlan(4) interfaces for ndis0 device ifconfig_wlan0=wpa syncdhcp I have to syncdhcp because I had this wireless device as the only network, and later in the boot process, ntpd will want to access Time Servers on the Internet. HTH ___ 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: Problems with Atheros card and hostpd
On Wednesday 16 December 2009 01:39:25 pm Derek Kulinski wrote: Also how to create wlan device by hand? ifconfig ath0 wlandev wlan0 doesn't seem to work. You have it backwards. It should be: ifconfig wlan0 create wlandev ath0 ___ 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: update to 8.0-RELEASE -- partition gone
On Tuesday 15 December 2009 04:42:06 pm Marian Hettwer wrote: Hi Folks, today I did an update from 7.2-RELEASE-p4 to 8.0-RELEASE using freebsd-update. Everything went smooth, apart from the fact that I can't mount my second disk. It's all a bit puzzling... Here are the facts: [r...@talisker ~]# cat /etc/fstab # DeviceMountpointFStypeOptionsDumpPass# /dev/ad4s2bnoneswapswOO /dev/ad4s1a/ufsrw11 /dev/ad4s2a/tmpufsrw22 /dev/ad4s2d/varufsrw22 /dev/ad4s2e/usrufsrw22 /dev/ad8s1a/BACKUPufsrw22 /dev/acd0/cdromcd9660ro,noauto00 linproc/compat/linux/proclinprocfsrw 00 The offending entry which isn't mountable anymore is ad8s1. [r...@talisker ~]# sysctl kern.disks kern.disks: ad8 ad4 fdisk and bsdlabel are showing my s1a partition/slice: [r...@talisker ~]# fdisk ad8 *** Working on device /dev/ad8 *** parameters extracted from in-core disklabel are: cylinders=775221 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=775221 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 781422705 (381554 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 52/ head 15/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED [r...@talisker ~]# bsdlabel ad8 # /dev/ad8: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 781422752 16unused0 0 c: 7814227680unused0 0 # raw part, don't edit but: [r...@talisker ~]# mount /dev/ad8s1a /BACKUP/ mount: /dev/ad8s1a : No such file or directory And in fact: [r...@talisker ~]# ls -l /dev/ad8* crw-r- 1 root operator0, 91 Dec 15 17:58 /dev/ad8 crw-r- 1 root operator0, 96 Dec 15 17:58 /dev/ad8a Huu? What's going on here? Where is s1? Never seen that before... (and I'm using FreeBSD since 4.0-RELEASE). and this mount obviously won't work either: [r...@talisker ~]# mount /dev/ad8a /BACKUP/ mount: /dev/ad8a : Invalid argument Anybody any idea how to recover here? The server is unluckily remote and in production. A downgrade back to 7.2 would be kinda difficult. I'd like to avoid that. Ideas anyone? Thanks in advance, Marian PS.: dmesg: http://crivens.terrorteam.de/~rabauke/FreeBSD/dmesg-8.0-release.txt [r...@talisker ~]# uname -rms FreeBSD 8.0-RELEASE i386 ___ 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 FreeBSD 8.0 no longer supports dangerously dedicated disks. Is this your issue? fdisk output appears to indicate that your disk has a partition table, but I never looked at one with fdisk that was dedicated... ___ 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
