RE: /dev/cuau* ports hang after a while
Hi, Have now tried this with 7.1-RELEASE, unfortunately with same results as before, the ports still hang after some time. -Timo -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: 30. tammikuuta 2009 14:52 To: Timo Rikkonen; freebsd-stable@freebsd.org Subject: RE: /dev/cuau* ports hang after a while At 05:50 AM 1/30/2009, Timo Rikkonen wrote: >Hi, > >The speed is 9600. Actually I already tried with 7.1-RELEASE, with >same results. >I'll try the device.hints-changes, thanks. Not sure if the code is in 7.0, so make sure you try it with 7.1-RELEASE ---Mike >-Timo > > >-Original Message- >From: Mike Tancsa [mailto:m...@sentex.net] >Sent: 29. tammikuuta 2009 22:34 >To: Timo Rikkonen; freebsd-stable@freebsd.org >Subject: Re: /dev/cuau* ports hang after a while > >At 08:00 AM 1/26/2009, Timo Rikkonen wrote: > >Hi, > > > >We are using "VScom PCI-200L" and "Moxa Technologies, C168H/PCI" > >-cards for serial ports. After installing 7.0 the ports or the > >connection to the port hang after a while. A "while" could be > >half-a-day or 10 minutes. > >There is no error message to be seen anywhere. > > > >Not all ports hang at the same time, it could be just one or two of > >them. Earlier versions (6.2-RELEASE) work just fine. > >The ports have different devicenames after 7.0, in 6.2 they were > >/dev/cuad4-7, now they are /dev/cuau0-3 (uart?) > > >Is the application fairly low speed (e.g. 9600bps or slower) ? If >so, try with 7.1R, not 7 and add > >hint.uart.0.flags="0x100" >hint.uart.1.flags="0x100" > >to /boot/device.hints > >http://www.freebsd.org/cgi/query-pr.cgi?pr=121421 > >has details > > ---Mike ___ 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: xorg 7.4 keyboard localisation (xorg.conf vs hal)
On Sun, Feb 1, 2009 at 5:57 PM, Robert Noland wrote: > On Sun, 2009-02-01 at 14:10 -0800, Joe Kelsey wrote: >> Sebastien Chassot wrote: >> > On Sun, 2009-02-01 at 17:19 +, Daniel Bye wrote: >> > >> >> On Sun, Feb 01, 2009 at 05:42:39PM +0100, Sebastien Chassot wrote: >> >> >> >>> Hi, >> >>> >> >>> I've upgrade to xorg7.4 and apparently keyboard and mouse are now >> >>> working with hald. >> >>> >> >>> In xorg.conf changing "old" keybord config as no effect and I can't find >> >>> how change it with hal. I've got /usr/local/etc/hal/fdi/* but no >> >>> *keymap* and I don't know how build such a file. >> >>> >> >> This should get you started: >> >> >> >> >> >> >> >> >> >> >> >> gb >> >> >> >> >> >> >> >> >> >> Change the `gb' in the example to your local keymap name, save the file >> >> as /usr/local/etc/hal/fdi/policy/x11-input.fdi and restart hald. >> >> >> This seems to have a way to enable HAL to detect a keyboard and export >> it to X, but what about mice? My Xorg log tells me that it is ignoring >> my USB mouse in addition to ignoring my keyboard, so what sort of HAL >> file do I add to enable it to find my mouse? > > The above is only to set keyboard layout, everything to detect the > keyboard is already present. > >> Where in HAL documentation is this information found? R. Noland seemed >> to think it was a trivial process to make HAL do keyboards and mice? In >> fact it is not trivial but a pain in the ass! If you intend to inflict >> broken software on unsuspecting users you had better think through all >> of the problems and come up with explicit solutions to all of those >> problems so that everyone has a chance to make their systems work. > > We (marcus and I) have gone to great pains to try and ensure that hal > behaves correctly in pretty much all mice configurations with or without > sysmouse. If you don't want to use hal, set AutoAddDevices off and > configure away. > >> There had better not be any more surprises waiting in the X 1.6 wings to >> surprise and confound everyone again! > > Are you going to stop paying me? You have no idea how many combinations > of hardware and configurations for X exist, or the amount of wok that > goes into making all of those combinations work. > > robert. I agree. If you really want to help Robert out, contribute funds and hardware for the time and effort he puts in, or volunteer in other areas that might make his life otherwise easier so he can help you out. Otherwise you're asking something extremely unreasonable that he's volunteering to work on. Or as the old adages go: 1. You get what you pay for. 2. I'll scratch your back if you scratch mine. My 2 cents, -Garrett ___ 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: problem with "cold" hardware? [Was: panic in callout_reset: bad link in callwheel]
Andriy Gapon schrieb: > on 28/01/2009 21:22 Andrew Snow said the following: > >> Andriy Gapon wrote: >> >>> Previously I heard about problems with hardware running hot, but not >>> with it being "cold". I put the word in quotes, because the system is in >>> a room with normal room temperature. >>> >>> Any guesses what hardware part might be acting up like this? >>> >> Power supply. Give all the capacitors a visual check. Or you may be >> drawing too much power from your rated supply. >> > > Right on the target. I opened the PSU after replacing it, visually it > looks OK (too me), nevertheless I have verified that the fault was in it. > > Thank you and everybody who helped! > Electronic devices, including computers, that become unable to /cold/ boot (and need a reset some seconds or minutes after power-up) usually suffer from dry or leaked capacitors, either in the PSU or - I've seen that more often - the voltage regulator on the main board. Dry capacitors often look innocuous, unlike leaked ones that show brownish stains (electrolytes) on the cap or underneath. ___ 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: xorg 7.4 keyboard localisation (xorg.conf vs hal)
Robert Noland wrote: On Sun, 2009-02-01 at 14:10 -0800, Joe Kelsey wrote: Sebastien Chassot wrote: On Sun, 2009-02-01 at 17:19 +, Daniel Bye wrote: On Sun, Feb 01, 2009 at 05:42:39PM +0100, Sebastien Chassot wrote: Hi, I've upgrade to xorg7.4 and apparently keyboard and mouse are now working with hald. In xorg.conf changing "old" keybord config as no effect and I can't find how change it with hal. I've got /usr/local/etc/hal/fdi/* but no *keymap* and I don't know how build such a file. This should get you started: gb Change the `gb' in the example to your local keymap name, save the file as /usr/local/etc/hal/fdi/policy/x11-input.fdi and restart hald. This seems to have a way to enable HAL to detect a keyboard and export it to X, but what about mice? My Xorg log tells me that it is ignoring my USB mouse in addition to ignoring my keyboard, so what sort of HAL file do I add to enable it to find my mouse? The above is only to set keyboard layout, everything to detect the keyboard is already present. Where in HAL documentation is this information found? R. Noland seemed to think it was a trivial process to make HAL do keyboards and mice? In fact it is not trivial but a pain in the ass! If you intend to inflict broken software on unsuspecting users you had better think through all of the problems and come up with explicit solutions to all of those problems so that everyone has a chance to make their systems work. We (marcus and I) have gone to great pains to try and ensure that hal behaves correctly in pretty much all mice configurations with or without sysmouse. If you don't want to use hal, set AutoAddDevices off and configure away. I did my best to follow ALL of the posted directions to absolutely NO AVAIL. When I start Xorg, it explicitly tells me it is disabling all automatic devices and refuses to use HAL or any other detectable methosd to find the mouse and/or keyboard. There is no documentation ANYWHERE about how HAL is supposed to help in any of this. There is no documentation ANYWHERE about what exaqctly the new Xorg is supposed to do about it. There is no documentation ANYWHERE about the new, secret, hidden options that you can put in your xorg.conf file to disable this whole HAL mess. The only documentation available ANYWHERE is the skimpy little paragraph that says, it works or it doesn't. No explanation about why it works or doesn't or how to determine exactly what might be wrong in your configuration to make it work or not work. I would not compalin if you actually documented what you are inflicting on us rather than just say, here it is, good luck! I understand how difficult some of these port upgrades are, but you have to realize that you have not provided ANY resources that anyone else can use to help themselves figure out their issues. I don't want to pay you with money I do not have from a job I do not have. You have to realize how many people may or may not have problems due to your blithe posting of this complicated mess. Either explain how to use HAL properly to configure X resources or disable the capability. Thank you for all of your effort so far. I really do appreciate it. /Joe There had better not be any more surprises waiting in the X 1.6 wings to surprise and confound everyone again! Are you going to stop paying me? You have no idea how many combinations of hardware and configurations for X exist, or the amount of wok that goes into making all of those combinations work. robert. I'll start with that Thank you Sebastien ___ 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-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-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: xorg 7.4 keyboard localisation (xorg.conf vs hal)
On Mon, 2009-02-02 at 11:18 -0800, Joe Kelsey wrote: > Robert Noland wrote: > > On Sun, 2009-02-01 at 14:10 -0800, Joe Kelsey wrote: > > > >> Sebastien Chassot wrote: > >> > >>> On Sun, 2009-02-01 at 17:19 +, Daniel Bye wrote: > >>> > >>> > On Sun, Feb 01, 2009 at 05:42:39PM +0100, Sebastien Chassot wrote: > > > > Hi, > > > > I've upgrade to xorg7.4 and apparently keyboard and mouse are now > > working with hald. > > > > In xorg.conf changing "old" keybord config as no effect and I can't find > > how change it with hal. I've got /usr/local/etc/hal/fdi/* but no > > *keymap* and I don't know how build such a file. > > > > > This should get you started: > > > > > > gb > > > > > Change the `gb' in the example to your local keymap name, save the file > as /usr/local/etc/hal/fdi/policy/x11-input.fdi and restart hald. > > > >> This seems to have a way to enable HAL to detect a keyboard and export > >> it to X, but what about mice? My Xorg log tells me that it is ignoring > >> my USB mouse in addition to ignoring my keyboard, so what sort of HAL > >> file do I add to enable it to find my mouse? > >> > > > > The above is only to set keyboard layout, everything to detect the > > keyboard is already present. > > > > > >> Where in HAL documentation is this information found? R. Noland seemed > >> to think it was a trivial process to make HAL do keyboards and mice? In > >> fact it is not trivial but a pain in the ass! If you intend to inflict > >> broken software on unsuspecting users you had better think through all > >> of the problems and come up with explicit solutions to all of those > >> problems so that everyone has a chance to make their systems work. > >> > > > > We (marcus and I) have gone to great pains to try and ensure that hal > > behaves correctly in pretty much all mice configurations with or without > > sysmouse. If you don't want to use hal, set AutoAddDevices off and > > configure away. > > > > > I did my best to follow ALL of the posted directions to absolutely NO AVAIL. > > When I start Xorg, it explicitly tells me it is disabling all automatic > devices and refuses to use HAL or any other detectable methosd to find > the mouse and/or keyboard. > > There is no documentation ANYWHERE about how HAL is supposed to help in > any of this. There is no documentation ANYWHERE about what exaqctly the > new Xorg is supposed to do about it. There is no documentation ANYWHERE > about the new, secret, hidden options that you can put in your xorg.conf > file to disable this whole HAL mess. man xorg.conf search for Input... > The only documentation available ANYWHERE is the skimpy little paragraph > that says, it works or it doesn't. No explanation about why it works or > doesn't or how to determine exactly what might be wrong in your > configuration to make it work or not work. > > I would not compalin if you actually documented what you are inflicting > on us rather than just say, here it is, good luck! I understand how > difficult some of these port upgrades are, but you have to realize that > you have not provided ANY resources that anyone else can use to help > themselves figure out their issues. > > I don't want to pay you with money I do not have from a job I do not > have. You have to realize how many people may or may not have problems > due to your blithe posting of this complicated mess. Either explain how > to use HAL properly to configure X resources or disable the capability. Set Options "AutoAddDevices" "off" and you have to configure everything like you used to. robert. > Thank you for all of your effort so far. I really do appreciate it. > > /Joe > > >> There had better not be any more surprises waiting in the X 1.6 wings to > >> surprise and confound everyone again! > >> > > > > Are you going to stop paying me? You have no idea how many combinations > > of hardware and configurations for X exist, or the amount of wok that > > goes into making all of those combinations work. > > > > robert. > > > > > >>> I'll start with that > >>> > >>> Thank you > >>> > >>> > >>> Sebastien > >>> > >>> ___ > >>> 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-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-stable@freebsd.org mailing list > http://lists.
Re: HEADS UP: multi-IPv4/v6/no-IP jails merge to 7-STABLE ahead
At 10:22 AM 1/28/2009, Bjoern A. Zeeb wrote: Hi, I have a possible MFC candidate patch at: http://people.freebsd.org/~bz/20090128-02-jail7-mfc.diff Hi Bjoern, Will this patch allow for the creation of tun interfaces inside of a jail ? Ideally I was hoping to run OpenVPN inside various jails which uses the tun device. ---Mike to merge the multi-IPv4/v6/no-IP jails to 7-STABLE. My plan would be to do so during the weekend of 6-8th February 2009. In addition to what the patch says at the beginning (__FreeBSD_version bump), the patch also has the regenerated compat/freebsd32 sysctl stuff in it so that people can apply, compile and run it directly. For the merge this would be a second commit. For committers who want to review that I have done the merge right, it is an svn diff with mergeinfo included. For details about the patch, features, .. see the original commit message and follow-up a few days later (both in one post): http://lists.freebsd.org/pipermail/freebsd-jail/2008-December/000631.html Since then a few bug fixes went in, some older PRs were handled, ... Now is the time for you to try and review it for 7-STABLE, etc. /bz -- Bjoern A. Zeeb The greatest risk is not taking one. ___ 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-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: xorg 7.4 keyboard localisation (xorg.conf vs hal)
Robert Noland wrote: man xorg.conf search for Input... This provides absolutely no help. I look at my /var/log/Xorg.0.log and it tells me nothing. If I remove the keyboard and mouse input devices from xorg.conf, the log tells me that it is disabling all input devices and never says anything else. There is no evidence that hal does anything that X want to know about. How would I detect that my configuration file needs changing? Is there a message in Xorg.0.log to look for? Is there a help file somehwere which explains how to change your configuration file to allow hal to work? I cannot find any information anywhere in the system to allow me to debug my problems in any way. I want to have fully automatic configuration using whatever means will allow it. You explanations about the mysterious behavior of hal and xorg do not give me any information I can use in any way to solve my problems. Set Options "AutoAddDevices" "off" and you have to configure everything like you used to. I WANT to use the new facilities. Is it possible to debug my configuration problems? Where do I start? How do I enable this magical new world of letting hal do things for me? What changes do I make to xorg.conf to allow this? /Joe ___ 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: HEADS UP: multi-IPv4/v6/no-IP jails merge to 7-STABLE ahead
On Mon, 2 Feb 2009, Mike Tancsa wrote: At 10:22 AM 1/28/2009, Bjoern A. Zeeb wrote: Hi, I have a possible MFC candidate patch at: http://people.freebsd.org/~bz/20090128-02-jail7-mfc.diff Hi Bjoern, Will this patch allow for the creation of tun interfaces inside of a jail ? Ideally I was hoping to run OpenVPN inside various jails which uses the tun device. Nope, you'll have to wait for vimages for that. /bz -- Bjoern A. Zeeb The greatest risk is not taking one. ___ 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: xorg 7.4 keyboard localisation (xorg.conf vs hal)
On Mon, 2009-02-02 at 12:43 -0800, Joe Kelsey wrote: > Robert Noland wrote: > > > > man xorg.conf search for Input... > > > > > This provides absolutely no help. > > I look at my /var/log/Xorg.0.log and it tells me nothing. If I remove > the keyboard and mouse input devices from xorg.conf, the log tells me > that it is disabling all input devices and never says anything else. > There is no evidence that hal does anything that X want to know about. > How would I detect that my configuration file needs changing? Is there > a message in Xorg.0.log to look for? Is there a help file somehwere > which explains how to change your configuration file to allow hal to work? > > I cannot find any information anywhere in the system to allow me to > debug my problems in any way. I want to have fully automatic > configuration using whatever means will allow it. You explanations > about the mysterious behavior of hal and xorg do not give me any > information I can use in any way to solve my problems. > > > > > Set Options "AutoAddDevices" "off" and you have to configure everything > > like you used to. > > > I WANT to use the new facilities. Is it possible to debug my > configuration problems? Where do I start? How do I enable this magical > new world of letting hal do things for me? What changes do I make to > xorg.conf to allow this? Ok, are you using gdm, xdm, or startx? You need to ensure that dbus and hald are running first. Set dbus_enable="YES" and hald_enable="YES" in your rc.conf. If you are using xdm or startx, there is a potential race on startup, where hal/dbus are not yet ready when Xorg starts up. This is an issue with linux as well and at least partial solutions have been proposed. I may try and finish it up if no-one beats me to it... But my preference is to work on FreeBSD specific issues, given that there is well, one of me compared to lots of linux folks. if you are using startx, give dbus/hald a little time to startup before you startx. If you are using xdm, some various solutions have been proposed on the mailing list. None of them are really pretty, but seem to be working for folks for the time being. Failing that, send me your xorg.conf and xorg.log, but it is working for most people. robert. > /Joe > -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
FreeBSD 7.1 on MacBook Pro: sysinstall keyboard problems
Hi, I'm trying to install FreeBSD 7.1-RELEASE/i386 on a MacBook Pro (October 2008 model) with a US international keyboard. The DVD boots fine, but once I get into sysinstall, it's like the Ctrl key is stuck. Whenever I type 'C' it actually does Ctrl+C (and exits the install), and I can't even get a dmesg from fixit because 'D' acts like Ctrl+D and logs me out. Has anyone seen this before, any ideas on how to fix this? Arjan ___ 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: Replace Cisco IOS/CBOS with freebsd - possible?
Quoting Łukasz Bromirski : On 2009-01-30 03:18, Chris H wrote: Please see: https://bsdforge.net/cisco-data/ for a list of manuals I have available for download on these (and similar). What's the sense of downloading it from Your site, if cisco.com contains the files? Because I was asked for more info on my hardware, and I /knew/ where my documentation was. Why try to discover (or ask others to) where the docs were on Cisco's site - which would assume it still existed. I guess I could have summarized in one word - convenience. ;) Go to cisco.com->Products and choose from routers. Or go to cisco.com/univercd and look for older interface to manuals. Thanks for the pointers. -- "Don't expect me to cry for all the | Łukasz Bromirski reasons you had to die" -- Kurt Cobain |http://lukasz.bromirski.net ___ 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: Soekris 4801 hangs (was Re: Hangs, maybe a clue)
On Sun, Feb 01, 2009 at 07:56:48PM -0500, Pete Carah wrote: > I fixed the problem on my 4801's by having noticed a correlation with > psm and hangs on my laptop, and > thought there may be a LOR or such involving the keyboard driver and/or > kbdmux. Since a 4801 has no need > of those drivers, but *does* contain the hardware they control, just > with no external peripherals connected, I tried > configuring the Soekris kernel with all vestiges of atkbdc, psm, kbdmux, > sc, and such removed. This did appear to fix the hangs. Hmmm... not for me. This is my kernel config for the hanging net4801s. It is being in use for a couple of years now and I didn't change it before the trouble began early December: -- cut here # SOEKRIS kernel config file, based upon FreeBSD 6.0-STABLE 2006-01-03. #cpuI486_CPU cpu I586_CPU ident SOEKRIS options CPU_SOEKRIS #Enable Soekris hardware stuff. options CPU_GEODE #GEODE GL1100 Chips (Soekris) #device pf #DON'T Enable PF (use as a module!) makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread 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 NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=1000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-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 STOP_NMI# Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing # options SMP # Symmetric MultiProcessor Kernel # device apic# I/O APIC # CPU frequency control device cpufreq # Bus support. device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID # Static device numbering device agp # support several AGP chipsets # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports device uart# Generic UART driver device miibus # MII bus support device sis # Silicon Integrated Systems SiS 900/SiS 7016 # Pseudo devices. device loop# Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci# UHCI PCI->USB interface device ohci# OHCI PCI->USB interface device usb # USB Bus (required) #device udbp
Re: problem with "cold" hardware? [Was: panic in callout_reset: bad link in callwheel]
on 28/01/2009 21:22 Andrew Snow said the following: > Andriy Gapon wrote: >> Previously I heard about problems with hardware running hot, but not >> with it being "cold". I put the word in quotes, because the system is in >> a room with normal room temperature. >> >> Any guesses what hardware part might be acting up like this? > > Power supply. Give all the capacitors a visual check. Or you may be > drawing too much power from your rated supply. Right on the target. I opened the PSU after replacing it, visually it looks OK (too me), nevertheless I have verified that the fault was in it. Thank you and everybody who helped! -- Andriy Gapon ___ 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-update: Fetching 25470 files... failed.
I am trying to upgrade some machines from FreeBSD 7.0 i386 to 7.1 with freebsd-update tool. It was successful on some of them, but on few others I am still getting the same error: Fetching files from 7.0-RELEASE for merging... done. Preparing to download files... done. Fetching 26988 patches.102030405060708090100. [...snip...] 4023502360237023802390240024102420243024402450 done. Applying patches... done. Fetching 25470 files... failed. I run 'freebsd-update -r 7.1-RELEASE upgrade' almost ten times on this machine and always got this error. What can I try to do to fix this? Thanks for any help. Miroslav Lachman ___ 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: Soekris 4801 hangs (was Re: Hangs, maybe a clue)
cpghost wrote: On Sun, Feb 01, 2009 at 07:56:48PM -0500, Pete Carah wrote: I fixed the problem on my 4801's by having noticed a correlation with psm and hangs on my laptop, and thought there may be a LOR or such involving the keyboard driver and/or kbdmux. Since a 4801 has no need of those drivers, but *does* contain the hardware they control, just with no external peripherals connected, I tried configuring the Soekris kernel with all vestiges of atkbdc, psm, kbdmux, sc, and such removed. This did appear to fix the hangs. Hmmm... not for me. This is my kernel config for the hanging net4801s. It is being in use for a couple of years now and I didn't change it before the trouble began early December: -- cut here # SOEKRIS kernel config file, based upon FreeBSD 6.0-STABLE 2006-01-03. #cpuI486_CPU cpu I586_CPU ident SOEKRIS options CPU_SOEKRIS #Enable Soekris hardware stuff. options CPU_GEODE #GEODE GL1100 Chips (Soekris) #device pf #DON'T Enable PF (use as a module!) makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread 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 NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=1000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-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 STOP_NMI# Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing # options SMP # Symmetric MultiProcessor Kernel # device apic# I/O APIC # CPU frequency control device cpufreq # Bus support. device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID # Static device numbering device agp # support several AGP chipsets # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports device uart# Generic UART driver device miibus # MII bus support device sis # Silicon Integrated Systems SiS 900/SiS 7016 # Pseudo devices. device loop# Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci# UHCI PCI->USB interface device ohci# OHCI PCI->USB interface device usb # USB Bus (required) #device
Re: 7.1, mpt and slow writes
On Sat, 31 Jan 2009, Gary Palmer wrote: On Sat, Jan 31, 2009 at 01:48:46AM -0500, Charles Sprickman wrote: On Fri, 30 Jan 2009, Gary Palmer wrote: On Thu, Jan 29, 2009 at 11:43:11PM -0500, Charles Sprickman wrote: [ snip ] Any idea what happened to the sysctl? Is there some other method to verify the loader tunable took (other than testing the throughput)? Boot with -v. If the loader tunable took effect, you should see "Enabling SATA WC on phy " instead of "Disabling SATA ..." Cool, it works then. Why was the info removed from the sysctl mib? mpt0: Enabling SATA WC on phy 0 mpt0: Enabling SATA WC on phy 1 Bonnie++ is showing me about 24MB/s writes and 70MB/s reads. Is any of this verbose stuff problematic? mpt0: No Handlers For Any Event Notify Frames. Event 0xa (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0xb (ACK not required). And is any of this info found at boot-time accessible while the system is running? Hi, Sorry, I can't answer your questions - all I did to find the boot -v information was to look in the kernel source code. Grepping through the CVS history I don't actually see a point in CVS history where there was a sysctl MIB value for the SATA WC status, although I might be mistaken. Perhaps you are remembering using kenv to get at hw.mpt.enable_sata_wc instead of sysctl? That, my friend, is precisely the problem. "kenv" didn't stick in my head because most of the FreeBSD-isms in my head still date back to 4.x. I am behind the times... Thanks for solving the mystery for me. Charles Regards, Gary mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority-ReSync ) mpt0:vol0(mpt0:0:0): Using Spare Pool: 0 mpt0:vol0(mpt0:0:0): 2 Members: (mpt0:1:32:0): Primary Online (mpt0:1:1:0): Secondary Online mpt0:vol0(mpt0:0:0): RAID-1 - Optimal mpt0:vol0(mpt0:0:0): Status ( Enabled ) (mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0) (mpt0:vol0:1): Online (mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0) (mpt0:vol0:0): Online Thanks, Charles ps - would it kill Dell to make a damn ISO of a bootable media for RAID controller firmware upgrades??? I don't even own anything with a floppy drive anymore. Regards, Gary ___ 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-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: FreeBSD 7.1 on MacBook Pro: sysinstall keyboard problems
On 02.02.2009 21:37 Uhr, Arjan van Leeuwen wrote: Hi, I'm trying to install FreeBSD 7.1-RELEASE/i386 on a MacBook Pro (October 2008 model) with a US international keyboard. The DVD boots fine, but once I get into sysinstall, it's like the Ctrl key is stuck. Whenever I type 'C' it actually does Ctrl+C (and exits the install), and I can't even get a dmesg from fixit because 'D' acts like Ctrl+D and logs me out. Has anyone seen this before, any ideas on how to fix this? Yes, I've seen this. It's the same in recent HEAD (both with old USB and USB2). This started to happen with the MacBook Pros 4,1. The keyboard does work in X but not on the console. (i installed using a USB keyboard). I would very much like to see this working, but i have absolutely no clue where to start looking... Cheers, Florian ___ 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"
