Re: iwn stopped working after OpenBSD upgrade in January, 2010
There is no iwn-firmware-5.3. The latest package is rev 5.2. It contains the exact same images than you can download from: http://intellinuxwireless.org/?n=Downloads Please run ifconfig iwn0 debug before dhclient iwn0 and send me the output. | media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g) Have you forced media to OFDM54? If so, try with ifconfig iwn0 media autoselect. Damien
Re: ath AR5424 support
Brynet schrieb: Luis Henriques wrote: Hi! I finally got tired of not using my wireless card on my laptop and decided to take a look at the code. I compared the ath OpenBSD code with similar drivers on NetBSD and Linux kernels, start adding/correcting the ath code and finally got it to work. I am currently able to use my AR5424 wireless card! I think you may have just duplicated some existing work, Damien commited a new Atheros driver in -CURRENT.. it was named athn(4). http://marc.info/?l=openbsd-cvsm=125821878008903w=2 You might have been able to adapt this new driver, instead of pulling in code from Linux (..even if it may be ISC licenced). 1) Most of the code I'm using is from Linux driver which is AFAIK GPL'ed code. Is this a problem? If it is GPL code, it's very unlikely to be commited. -Bryan. If I remember correctly the AR5424 is the AzureWave assembled into some EEE Models amongst others. I don't think it is supported by athn http://www.openbsd.org/cgi-bin/man.cgi?query=athnapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html Regards, Dorian
Re: SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
Am 23.01.10 07:05, schrieb James Hartley: A quick search in the misc@ archives PR database didn't reveal that anyone has mentioned this before. In installing the 20 January (#511) i386 snapshot, I received a SHA256 mismatch on base46.tgz. Otherwise, the snapshot installs as expected. Why check SHA256, if you still install it?
Re: SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
On Fri, Jan 22, 2010 at 10:05:13PM -0800, James Hartley wrote: A quick search in the misc@ archives PR database didn't reveal that anyone has mentioned this before. In installing the 20 January (#511) i386 snapshot, I received a SHA256 mismatch on base46.tgz. Otherwise, the snapshot installs as expected. Me too. Just upgraded current. Right now I'm runnig OpenBSD 4.6-current (GENERIC.MP) #393: Wed Jan 20 06:54:30 MST 2010 Downloaded from ftp.eu.openbsd.org
perl script-cron fails, at and command line work
I just re-installed fresh from 4.5 to 4.6. I now have a problem with a script that ran from cron for many months without problems. From cron I get: Logfile LWP_SupeRref.log failed to open at /home/user/LWP/LWP_ref.pl line 73. I have tried altering permissions, deleting file, touching file, etc This script works just fine from command line and also using at command -- A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein
Re: perl script-cron fails, at and command line work
Chris Bennett wrote: I just re-installed fresh from 4.5 to 4.6. I now have a problem with a script that ran from cron for many months without problems. From cron I get: Logfile LWP_SupeRref.log failed to open at /home/user/LWP/LWP_ref.pl line 73. I have tried altering permissions, deleting file, touching file, etc This script works just fine from command line and also using at command Are you *sure* you know what directory the log file is being created in? If the script is writing to default/current directory; perhaps your cron environment has changed.
Re: Books on reverse engineering?
On Fri, Jan 22, 2010 at 05:24:24PM -0600, Chris Bennett wrote: The booklist on the OpenBSD site is very good. I was concerned that a few items were old, but that is just not relevant. An excellent grasp of C is going to be necessary. It takes a long time to get good at programming. I have seen the phrase For good code examples, just look at OpenBSD source many times. But that advice is a bit vague, sort of like For a good book to read, go to the library. Since I am trying to pick up C myself, I decided that using a historical approach might be best for me. So I am going to concentrate on studying basic and old but still very useful utilities such as sed, ed etc. Honestly, if you want to start seeing how to use C to do basic things, and understand what's under the hood of those utilities, I suggest beginning in the C library (src/lib/libc/). And Stevens is teh sexx. You will need to study in detail work that has already been done. I doubt that you will find many good books on reverse engineering, but you ought to be able to find the people who could but haven't written those books -- A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein
Re: perl script-cron fails, at and command line work
Frank Bax wrote: Chris Bennett wrote: I just re-installed fresh from 4.5 to 4.6. I now have a problem with a script that ran from cron for many months without problems. From cron I get: Logfile LWP_SupeRref.log failed to open at /home/user/LWP/LWP_ref.pl line 73. I have tried altering permissions, deleting file, touching file, etc This script works just fine from command line and also using at command Are you *sure* you know what directory the log file is being created in? If the script is writing to default/current directory; perhaps your cron environment has changed. Yes I messed up writing the new crontabs. I pulled out the old ones from archived copy of /var/cron/tabs This one was the only one that that affected, but I did the same error for several, now all are fixed -- A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein
Re: perl script-cron fails, at and command line work
Frank Bax wrote: Chris Bennett wrote: I just re-installed fresh from 4.5 to 4.6. I now have a problem with a script that ran from cron for many months without problems. From cron I get: Logfile LWP_SupeRref.log failed to open at /home/user/LWP/LWP_ref.pl line 73. I have tried altering permissions, deleting file, touching file, etc This script works just fine from command line and also using at command Are you *sure* you know what directory the log file is being created in? If the script is writing to default/current directory; perhaps your cron environment has changed. Doesn't cron runs as a service, hence simple environment? If you have a link in the path, try using the real (full) path. I remember icewm which need the full path, starting from /
Re: Acer Aspire One D250 mouse problem
On Fri, Jan 22, 2010 at 2:57 AM, J.C. Roberts list-...@designtools.org wrote: On Thu, 21 Jan 2010 00:42:26 -0500 electronmuontau neutrino emtneutr...@gmail.com wrote: I have an Acer Aspire One D250 running snapshot (2010-01-20). The mouse will work for a couple of seconds and then freeze. This has occured when running wsmoused in a console(not in X), inside of X, and when I run od /dev/wsmouse. If I kill wsmoused and start it again, the mouse works and then freezes. When I go to a console (ctrl+alt+f1) from X and go back to X, the mouse works, then freezes. When I run od /dev/wsmouse, I see output and then nothing after a couple of seconds. I can kill od and run it again and see the output again for a short time. This behavior occurs in releases 4.3, 4.4, 4.5, 4.6, and snapshot (2010-01-20). The mouse works fine in releases 4.0, 4.1, and 4.2. Something was done between 4.2 and 4.3 that causes this problem. The mouse is seen as a ps2 mouse. The easiest work around is to plug in a usb mouse which works in all the releases mentioned as well as current. Any help is appreciated. There was some discussion on the Acer AspireOne mouse just a few days ago on the bugs@ list, although it was a slightly different model. http://marc.info/?t=12639198483r=1w=2 Thanks for posting your dmesg, but I have an odd question. Do you ever see pmsattach: disable error in your dmesg? According to Stuart (sthen@), the message above is not consistent so you'd only see it some of the time. --
Re: Acer Aspire One D250 mouse problem
On Sat, Jan 23, 2010 at 11:13 AM, electronmuontau neutrino emtneutr...@gmail.com wrote: On Fri, Jan 22, 2010 at 2:57 AM, J.C. Roberts list-...@designtools.org wrote: On Thu, 21 Jan 2010 00:42:26 -0500 electronmuontau neutrino emtneutr...@gmail.com wrote: I have an Acer Aspire One D250 running snapshot (2010-01-20). The mouse will work for a couple of seconds and then freeze. This has occured when running wsmoused in a console(not in X), inside of X, and when I run od /dev/wsmouse. If I kill wsmoused and start it again, the mouse works and then freezes. When I go to a console (ctrl+alt+f1) from X and go back to X, the mouse works, then freezes. When I run od /dev/wsmouse, I see output and then nothing after a couple of seconds. I can kill od and run it again and see the output again for a short time. This behavior occurs in releases 4.3, 4.4, 4.5, 4.6, and snapshot (2010-01-20). The mouse works fine in releases 4.0, 4.1, and 4.2. Something was done between 4.2 and 4.3 that causes this problem. The mouse is seen as a ps2 mouse. The easiest work around is to plug in a usb mouse which works in all the releases mentioned as well as current. Any help is appreciated. There was some discussion on the Acer AspireOne mouse just a few days ago on the bugs@ list, although it was a slightly different model. http://marc.info/?t=12639198483r=1w=2 Thanks for posting your dmesg, but I have an odd question. Do you ever see pmsattach: disable error in your dmesg? According to Stuart (sthen@), the message above is not consistent so you'd only see it some of the time. -- Sorry, I have never seen that error on my Aspire One, just the odd mouse behavior. Have you tried to install previous releases like I did? The mouse worked fine on releases 4.0, 4.1, and 4.2, but did not work on 4.3, 4.4, 4.5, 4.6, and any of the snapshots.
Re: ath AR5424 support
On Fri, Jan 22, 2010 at 10:55:22PM -0500, Daniel Dickman wrote: 1) Most of the code I'm using is from Linux driver which is AFAIK GPL'ed code. Is this a problem? Why do you think the code is GPL'ed? What driver did you look at? Some of the atheros code in the linux kernel comes from OpenBSD. For example: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/wireless/ath/ath5k/ath5k.h;h=6a2a967621cc1523aadbad93a22e9edc4382;hb=HEAD Note the copyright at the top: Copyright (c) 2004-2007 Reyk Floeter r...@openbsd.org Not to mention the non-GPL license that follows... I used as reference the ath5k Linux device driver and the atheros_hal from NetBSD. My question is just: can I do this and publish a patch? I am using the code for myself at the moment and, of course, I would like to share it. I just don't want to get into troubles. 2) I know nothing about wireless cards and my code is probably doing very stupid things. This means that I will not be able to provide any kind of support to it. I'd imagine a dmesg with and without your patch would no doubt be helpful to start... Here's a dmesg with my patch applied. Note that it adds nothing to the output so there's not point in publishing the dmesg without the patch. OpenBSD 4.6-current (GENERIC.MP) #32: Fri Jan 22 22:38:21 WET 2010 mig...@hades.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2144796672 (2045MB) avail mem = 2078343168 (1982MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0170 (26 entries) bios0: vendor TOSHIBA version V2.00 date 06/10/2008 bios0: TOSHIBA Satellite A210 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP TCPA SLIC SSDT APIC MCFG HPET ASF! acpi0: wakeup devices PB2_(S4) PB3_(S4) PB4_(S4) PB5_(S3) PB6_(S0) BB4_(S4) BB5_(S4) OHC1(S4) OHC2(S4) OHC3(S4) OHC4(S4) OHC5(S4) EHCI(S4) P2P_(S5) AUDO(S4) MODM(S4) AZLA(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Turion(tm) 64 X2 Mobile Technology TL-60, 1995.25 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Turion(tm) 64 X2 Mobile Technology TL-60, 1995.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PB2_) acpiprt2 at acpi0: bus -1 (PB3_) acpiprt3 at acpi0: bus -1 (PB4_) acpiprt4 at acpi0: bus 8 (PB5_) acpiprt5 at acpi0: bus 14 (PB6_) acpiprt6 at acpi0: bus 20 (PB7_) acpiprt7 at acpi0: bus -1 (BB4_) acpiprt8 at acpi0: bus 8 (BB5_) acpiprt9 at acpi0: bus 26 (P2P_) acpiprt10 at acpi0: bus -1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PWRB acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model PA3457U serial 3658Q type Li-Ion oem TOSHIBA acpivideo0 at acpi0: VGA_ acpivout0 at acpivideo0: CRT_ acpivout1 at acpivideo0: LCD_ acpivout2 at acpivideo0: TV__ acpivout3 at acpivideo0: DVI_ acpivideo1 at acpi0: VGA_ acpivout4 at acpivideo1: CRT_ acpivout5 at acpivideo1: LCD_ acpivout6 at acpivideo1: TV__ cpu0: PowerNow! K8 1995 MHz: speeds: 2000 1800 1600 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 ATI RS690 Host rev 0x00 ppb0 at pci0 dev 2 function 0 ATI RS690M PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Mobility Radeon HD 2400 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) azalia0 at pci1 dev 0 function 1 ATI RS690M HD Audio rev 0x00: apic 2 int 19 (irq 11) azalia0: no supported codecs azalia0: initialization failure, detaching ppb1 at pci0 dev 5 function 0 ATI RS690 PCIE rev 0x00 pci2 at ppb1 bus 8 ppb2 at pci0 dev 6 function 0 ATI RS690 PCIE rev 0x00 pci3 at ppb2 bus 14 re0 at pci3 dev 0 function 0 Realtek 8101E rev 0x01: RTL8101E (0x3400), apic 2 int 18 (irq 3), address 00:1e:ec:3a:48:9f rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 ppb3 at pci0 dev 7 function 0 ATI RS690 PCIE rev 0x00 pci4 at ppb3 bus 20 ath0 at pci4 dev 0 function 0 Atheros AR5424
Re: ath AR5424 support
On Sat, Jan 23, 2010 at 10:23:36AM +0100, Dorian B?ttner wrote: Brynet schrieb: Luis Henriques wrote: Hi! I finally got tired of not using my wireless card on my laptop and decided to take a look at the code. I compared the ath OpenBSD code with similar drivers on NetBSD and Linux kernels, start adding/correcting the ath code and finally got it to work. I am currently able to use my AR5424 wireless card! I think you may have just duplicated some existing work, Damien commited a new Atheros driver in -CURRENT.. it was named athn(4). http://marc.info/?l=openbsd-cvsm=125821878008903w=2 You might have been able to adapt this new driver, instead of pulling in code from Linux (..even if it may be ISC licenced). 1) Most of the code I'm using is from Linux driver which is AFAIK GPL'ed code. Is this a problem? If it is GPL code, it's very unlikely to be commited. -Bryan. If I remember correctly the AR5424 is the AzureWave assembled into some EEE Models amongst others. I don't think it is supported by athn http://www.openbsd.org/cgi-bin/man.cgi?query=athnapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html Not sure about this, but I'm have been using -current and the driver that actually is being attached to my card is ath, not athn. The default behaviour (without my mods to the driver) is to crash my system (i.e., the system stops responding and I need to do a hard reboot on the laptop) as soon as I do something like ifconfig ath0 scan or ifconfig ath0 192.168.0.1. Luis
Re: ath AR5424 support
On 2010 Jan 23 (Sat) at 16:17:29 + (+), Luis Henriques wrote: :On Fri, Jan 22, 2010 at 10:55:22PM -0500, Daniel Dickman wrote: : 1) Most of the code I'm using is from Linux driver which is AFAIK GPL'ed code. : Is this a problem? : : Why do you think the code is GPL'ed? What driver did you look at? Some : of the atheros code in the linux kernel comes from OpenBSD. For : example: : : http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/wireless/ath/ath5k/ath5k.h;h=6a2a967621cc1523aadbad93a22e9edc4382;hb=HEAD : : Note the copyright at the top: : Copyright (c) 2004-2007 Reyk Floeter r...@openbsd.org : : Not to mention the non-GPL license that follows... : :I used as reference the ath5k Linux device driver and the atheros_hal from :NetBSD. My question is just: can I do this and publish a patch? I am using :the code for myself at the moment and, of course, I would like to share it. :I just don't want to get into troubles. : If the code that you used is based on ISC and/or BSD licenses, then it should be safe. The top of the file normally contians the actual license that it is under. -- Schlattwhapper, n.: The window shade that allows itself to be pulled down, hesitates for a second, then snaps up in your face. -- Rich Hall, Sniglets
Re: ath AR5424 support
On Sat, Jan 23, 2010 at 04:22:19PM +, Luis Henriques wrote: On Sat, Jan 23, 2010 at 10:23:36AM +0100, Dorian B?ttner wrote: Brynet schrieb: Luis Henriques wrote: Hi! I finally got tired of not using my wireless card on my laptop and decided to take a look at the code. I compared the ath OpenBSD code with similar drivers on NetBSD and Linux kernels, start adding/correcting the ath code and finally got it to work. I am currently able to use my AR5424 wireless card! I think you may have just duplicated some existing work, Damien commited a new Atheros driver in -CURRENT.. it was named athn(4). http://marc.info/?l=openbsd-cvsm=125821878008903w=2 You might have been able to adapt this new driver, instead of pulling in code from Linux (..even if it may be ISC licenced). 1) Most of the code I'm using is from Linux driver which is AFAIK GPL'ed code. Is this a problem? If it is GPL code, it's very unlikely to be commited. -Bryan. If I remember correctly the AR5424 is the AzureWave assembled into some EEE Models amongst others. I don't think it is supported by athn http://www.openbsd.org/cgi-bin/man.cgi?query=athnapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html Not sure about this, but I'm have been using -current and the driver that actually is being attached to my card is ath, not athn. The default behaviour (without my mods to the driver) is to crash my system (i.e., the system stops responding and I need to do a hard reboot on the laptop) as soon as I do something like ifconfig ath0 scan or ifconfig ath0 192.168.0.1. Luis Not to be rude, but shit or get off the pot; either you copied the code from GPL'ed sources or you didn't. If you did, it won't go in. If you didn't, then make sure that it's considered compatible with the BSD license. If it comes from a BSD-like license, the only way you'll know if anybody cares is by showing it, not talking about it. Patches traditionally have been sent to tech@, so that's the place for it, if it's not GPL'ed. Goddamn.
Re: Disks connected to ahd0 causes boot to fail
Kenneth R Westerback wrote: Is there a media in the drive? Ken No, it properly detects a 2880 block (1M) geometry when a floppy disk is inserted, otherwise it shows that SCSI message. It doesn't show the message in 4.6. Thanks. :-) -Bryan.
Re: SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
Julian Leyh wrote: Am 23.01.10 07:05, schrieb James Hartley: A quick search in the misc@ archives PR database didn't reveal that anyone has mentioned this before. In installing the 20 January (#511) i386 snapshot, I received a SHA256 mismatch on base46.tgz. Otherwise, the snapshot installs as expected. Why check SHA256, if you still install it? because sometimes things happen in the snapshot world that don't apply to releases. If a file gets left out of a snapshot, rather than re-rolling the entire release (which can take a day or more on a slow platform, and non-trivial time in all cases), perhaps only base46.tgz is re-rolled. Plus, re-rolling the entire release means it takes many times as long to work out to the mirrors (and this is non-trivial, too). Plus, in many cases, people do intentionally use mismatched bsd.rd and file sets. No, not a good idea, but a time saver in some cases, and some people understand the risks and benefits to being able to do so. As the replication time for snapshots is absolutely non-trivial, it is entirely possible one can download bsd.rd, start installing, and get a base46.tgz (or any other file set) from a NEWER snap. Or an older snap. Or maybe something bad happened to that snapshot. But I don't think so in this case. :) Nick.
Re: pfctl table cleared time is jumping around
On Wednesday 20 January 2010 23:21:35 Michael Lechtermann wrote: Am 20.01.2010 23:15, schrieb frantisek holop: hmm, on Wed, Jan 20, 2010 at 04:58:32PM +0100, Michael Lechtermann said that it seems there is a bug in pfctl regarding the cleared time of a table entry. The attack actually happend this year, but the date shown is constantly changing: been like this forever... -pa-r-- bad-ssh Addresses: 3 Cleared: Thu Jan 1 01:00:00 1970 References: [ Anchors: 0 Rules: 2 ] Evaluations: [ NoMatch: 0 Match: 0 ] In/Block:[ Packets: 0 Bytes: 0 ] In/Pass: [ Packets: 0 Bytes: 0 ] In/XPass:[ Packets: 0 Bytes: 0 ] Out/Block: [ Packets: 0 Bytes: 0 ] Out/Pass:[ Packets: 0 Bytes: 0 ] Out/XPass: [ Packets: 0 Bytes: 0 ] i think i have sent a message about it ages ago but only to misc@ For me, it is a new behavior. It still worked with OpenBSD snapshot from around 08/2009. Hello, I'm running latest current and I have the same issues now: # pfctl -t tb1 -Ts -vvv 172.16.43.34 Cleared: Wed Dec 31 11:19:39 1969 172.16.43.35 Cleared: Wed Dec 31 11:19:39 1969 Actually this used to be displayed correctly 2 or 3 snapshots ago. Is this a known bug? Kind regards, Didier
atactl setstandby time won't work
Hi List, In my new server, the commands given through rc.local are atactl wd1 setidle 180 atactl wd1 setstandby 900 The first time the command is given, the disk spins down, but after the disk is activated again, it won't go back to idl / standby modes. Giving again a standby order works, but not the timers. Has anyone ideas ? Regards
Re: iwn stopped working after OpenBSD upgrade in January, 2010
Re: iwn stopped working after OpenBSD upgrade in January, 2010 damien . bergamini Sat, 23 Jan 2010 01:01:44 -0800 There is no iwn-firmware-5.3. The latest package is rev 5.2. It contains the exact same images than you can download from: http://intellinuxwireless.org/?n=Downloads Please run ifconfig iwn0 debug before dhclient iwn0 and send me the output. | media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g) Have you forced media to OFDM54? If so, try with ifconfig iwn0 media autoselect. Damien Script started on Sat Jan 23 05:55:56 2010 leona...@genetraveller OpenBSD 498sudo ifconfig iwn0 media OFDM54 mode 11g leona...@genetraveller OpenBSD 499sudo ifconfig iwn0 debug leona...@genetraveller OpenBSD 500sudo ifconfig iwn0 iwn0: flags=8847UP,BROADCAST,DEBUG,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:21:5d:9c:76:80 priority: 4 groups: wlan media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g) status: no network ieee80211: nwid NETGEAR wpapsk 0x inet6 fe80::221:5dff:fe9c:7680%iwn0 prefixlen 64 scopeid 0x2 leona...@genetraveller OpenBSD 502sudo dhclient iwn0 iwn0: no link . sleeping leona...@genetraveller OpenBSD 503exit Script done on Sat Jan 23 05:57:10 2010 From /var/log/messages I see repeated many times Jan 23 06:10:41 genetraveller /bsd: iwn0: end passive scan Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:14:6c:1e:9d:f4 rssi -27 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:14:6c:1e:9d:f4 rssi -26 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:14:6c:1e:9d:f4 rssi -26 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:12:0e:13:31:10 rssi -79 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:12:0e:13:31:10 rssi -78 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:14:6c:1e:9d:f4 rssi -26 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:12:0e:13:31:10 rssi -77 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:0d:3a:70:51:f7 rssi -77 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:12:0e:13:31:10 rssi -77 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received beacon from 00:12:0e:13:31:10 rssi -77 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:14:6c:1e:9d:f4 rssi -37 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:14:6c:1e:9d:f4 rssi -45 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:14:6c:1e:9d:f4 rssi -36 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received beacon from 00:14:6c:1e:9d:f4 rssi -36 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received beacon from 00:0d:3a:70:51:f7 rssi -77 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:0d:3a:70:51:f7 rssi -79 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:0d:3a:70:51:f7 rssi -82 mode 11g Jan 23 06:10:41 genetraveller /bsd: iwn0: received probe_resp from 00:0d:3a:70:51:f7 rssi -81 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received probe_resp from 00:1a:70:ea:1d:5e rssi -78 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received probe_resp from 00:1e:2a:07:c5:c8 rssi -61 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received probe_resp from 00:1a:70:ea:1d:5e rssi -76 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received probe_resp from 00:1e:2a:07:c5:c8 rssi -59 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received beacon from 00:22:b0:b1:3b:fc rssi -84 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received beacon from 00:1a:70:ea:1d:5e rssi -77 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received beacon from 00:1e:2a:07:c5:c8 rssi -60 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: received beacon from 00:1a:70:ea:1d:5e rssi -82 mode 11g Jan 23 06:10:42 genetraveller /bsd: iwn0: end passive scan Len Zaifman
make OpenBSD beep at start
Hi list, Can someone give a hin on how to make the speaker to beep for example with a command or a C program ? I started to write a little C program thinking there was a beep() functione, but it seems not Regards.
Wrong cksum of base46.tgz set in 20th Jan 2010 snapshot
Hi, On all mirrors and on main openbsd server base46.tgz is giving failed cksum error. Not sure is that random error, as I never saw that before. File content seems to be fine as reported by gzip, but could someone fix that if possible? $ config -ef bsd OpenBSD 4.6-current (GENERIC) #511: Wed Jan 20 06:46:42 MST 2010 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC $ cksum -c SHA256 (SHA256) INSTALL.i386: OK (SHA256) INSTALL.linux: OK (SHA256) base46.tgz: FAILED (SHA256) bsd: OK (SHA256) bsd.mp: OK (SHA256) bsd.rd: OK (SHA256) cd46.iso: OK (SHA256) cdboot: OK (SHA256) cdbr: OK (SHA256) cdemu46.iso: OK (SHA256) comp46.tgz: OK (SHA256) etc46.tgz: OK (SHA256) floppy46.fs: OK (SHA256) floppyB46.fs: OK (SHA256) floppyC46.fs: OK (SHA256) game46.tgz: OK (SHA256) install46.iso: OK (SHA256) man46.tgz: OK (SHA256) misc46.tgz: OK (SHA256) pxeboot: OK (SHA256) xbase46.tgz: OK (SHA256) xetc46.tgz: OK (SHA256) xfont46.tgz: OK (SHA256) xserv46.tgz: OK (SHA256) xshare46.tgz: OK $ gzip -vt base46.tgz base46.tgz: OK -- best regards q#
Re: make OpenBSD beep at start
Can someone give a hin on how to make the speaker to beep for example with a command or a C program ? echo (that's control+v, then control+g)
Re: make OpenBSD beep at start
On 23/01/2010, joshua stein j...@openbsd.org wrote:
Can someone give a hin on how to make the speaker to beep for example with
a command or a C program ?
echo
(that's control+v, then control+g)
or
/usr/bin/printf \a
or
putchar('\a');
C.
Re: Disks connected to ahd0 causes boot to fail
Kenneth R Westerback wrote:
Does the diff below suppress the unwanted message?
Ken
Index: sd.c
===
RCS file: /cvs/src/sys/scsi/sd.c,v
retrieving revision 1.182
diff -u -p -r1.182 sd.c
--- sd.c 15 Jan 2010 05:50:31 - 1.182
+++ sd.c 24 Jan 2010 00:29:23 -
@@ -357,9 +357,8 @@ sdopen(dev_t dev, int flag, int fmt, str
} else {
/* Spin up non-UMASS devices ready or not. */
if ((sc-sc_link-flags SDEV_UMASS) == 0)
- scsi_start(sc_link, SSS_START, (rawopen ? SCSI_SILENT :
- 0) | SCSI_IGNORE_ILLEGAL_REQUEST |
- SCSI_IGNORE_MEDIA_CHANGE);
+ scsi_start(sc_link, SSS_START, SCSI_SILENT |
+ SCSI_IGNORE_ILLEGAL_REQUEST |
SCSI_IGNORE_MEDIA_CHANGE);
/* Use sd_interpret_sense() for sense errors.
*
Yup that works, I don't see the message anymore. :-)
Thanks!
-Bryan.
Re: Wrong cksum of base46.tgz set in 20th Jan 2010 snapshot
If you don't have time to search the archives, you could at least check today's mail. On Sat, Jan 23, 2010 at 7:30 PM, Mikolaj Kucharski miko...@kucharski.name wrote: Hi, On all mirrors and on main openbsd server base46.tgz is giving failed cksum error. Not sure is that random error, as I never saw that before. File content seems to be fine as reported by gzip, but could someone fix that if possible? $ config -ef bsd OpenBSD 4.6-current (GENERIC) #511: Wed Jan 20 06:46:42 MST 2010 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC $ cksum -c SHA256 (SHA256) INSTALL.i386: OK (SHA256) INSTALL.linux: OK (SHA256) base46.tgz: FAILED (SHA256) bsd: OK (SHA256) bsd.mp: OK (SHA256) bsd.rd: OK (SHA256) cd46.iso: OK (SHA256) cdboot: OK (SHA256) cdbr: OK (SHA256) cdemu46.iso: OK (SHA256) comp46.tgz: OK (SHA256) etc46.tgz: OK (SHA256) floppy46.fs: OK (SHA256) floppyB46.fs: OK (SHA256) floppyC46.fs: OK (SHA256) game46.tgz: OK (SHA256) install46.iso: OK (SHA256) man46.tgz: OK (SHA256) misc46.tgz: OK (SHA256) pxeboot: OK (SHA256) xbase46.tgz: OK (SHA256) xetc46.tgz: OK (SHA256) xfont46.tgz: OK (SHA256) xserv46.tgz: OK (SHA256) xshare46.tgz: OK $ gzip -vt base46.tgz base46.tgz: OK -- best regards q#
Re: current on HP EliteBook 8530w
On Fri, Jan 22, 2010 at 02:04:23PM +0100, Jan Stary wrote:
snip
correctly (?) recognizes the SpeedStep frequencies:
cpu0: Enhanced SpeedStep 2528 MHz: speeds: 2534, 2533, 1600, 800 MHz
The kernel without ACPI does not:
cpu0: unknown Enhanced SpeedStep CPU, msr 0x0617492506004925
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 2528 MHz: speeds: 19467, 1600 MHz
snip
mtrr: Pentium Pro MTRR support
RICOH, Bay8Controller (manufacturer 0x0, product 0x0) at pcmcia0 function 0
not configured
copyvalue: efff0021Store to default type! efff0021
5c12 Called: \\_SB_.PCI0.LPCB.EC0_.RPPC
local0: 0xd2c14d04 cnt:01 stk:60 integer: 2
local1: 0xd2c1d3c4 cnt:01 stk:61 integer: 0
local2: 0xd2c34384 cnt:02 stk:62 objref: 0xd2c20044 index:0 opcode:CondRef
uvm_fault(0xd08ad720, 0xefffe000, 0, 1) - d
kernel: page fault trap, code=0
Stopped ataml_nodename+0x1b: pushl 0(%ebx)
ddb{0} rebooting...
Hi!
This looks same as problem on my hp 6930p. According to Jordan it's some
reference counting bug somewhere. This makes it boot...
Index: dsdt.c
===
RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
retrieving revision 1.157
diff -u -p -r1.157 dsdt.c
--- dsdt.c 5 Dec 2009 02:38:11 - 1.157
+++ dsdt.c 23 Jan 2010 23:49:46 -
@@ -3629,7 +3629,7 @@ aml_xparse(struct aml_scope *scope, int
aml_freevalue(opargs[1]);
/* Create Object Reference */
- _aml_setvalue(opargs[1], AML_OBJTYPE_OBJREF, opcode,
opargs[0]);
+ _aml_setvalue(opargs[1], AML_OBJTYPE_INTEGER,
0xDEADBEEF, opargs[0]);
aml_xaddref(opargs[1], CondRef);
/* Mark that we found it */
Re: atactl setstandby time won't work
complain to your drive vendor On Sun, Jan 24, 2010 at 12:16:07AM +0100, jean-francois wrote: Hi List, In my new server, the commands given through rc.local are atactl wd1 setidle 180 atactl wd1 setstandby 900 The first time the command is given, the disk spins down, but after the disk is activated again, it won't go back to idl / standby modes. Giving again a standby order works, but not the timers. Has anyone ideas ? Regards
Re: Wrong cksum of base46.tgz set in 20th Jan 2010 snapshot
This is exactly what was predicted what would happen. No benefit to publish the digests minus a bunch of people whining that the damn digests are off for obvious reasons. On Sun, Jan 24, 2010 at 12:30:35AM +, Mikolaj Kucharski wrote: Hi, On all mirrors and on main openbsd server base46.tgz is giving failed cksum error. Not sure is that random error, as I never saw that before. File content seems to be fine as reported by gzip, but could someone fix that if possible? $ config -ef bsd OpenBSD 4.6-current (GENERIC) #511: Wed Jan 20 06:46:42 MST 2010 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC $ cksum -c SHA256 (SHA256) INSTALL.i386: OK (SHA256) INSTALL.linux: OK (SHA256) base46.tgz: FAILED (SHA256) bsd: OK (SHA256) bsd.mp: OK (SHA256) bsd.rd: OK (SHA256) cd46.iso: OK (SHA256) cdboot: OK (SHA256) cdbr: OK (SHA256) cdemu46.iso: OK (SHA256) comp46.tgz: OK (SHA256) etc46.tgz: OK (SHA256) floppy46.fs: OK (SHA256) floppyB46.fs: OK (SHA256) floppyC46.fs: OK (SHA256) game46.tgz: OK (SHA256) install46.iso: OK (SHA256) man46.tgz: OK (SHA256) misc46.tgz: OK (SHA256) pxeboot: OK (SHA256) xbase46.tgz: OK (SHA256) xetc46.tgz: OK (SHA256) xfont46.tgz: OK (SHA256) xserv46.tgz: OK (SHA256) xshare46.tgz: OK $ gzip -vt base46.tgz base46.tgz: OK -- best regards q#
Alerta De Segurança Bradesco
- This mail is a HTML mail. Not all elements could be shown in plain text mode. - Bradesco I com grande satisfagco que a equipe de seguranga do Internet Banking Bradesco envia este e-mail a vocj, cliente. O motivo pelo qual estamos entrando em contato, i para alertar que seu Cartco chave de seguranca Bradesco foi expirado, pedimos para que atualize o mesmo. A atualizagco do seu Cartco chave de seguranca Bradesco i necessaria, pois i fundamental para sua seguranga, caso o mesmo nco seja atualizado ati a data 01/01/2010: - As chaves de seguranga serco desativadas; - Seu acesso ao Internet Banking, Fone Facil e nos Caixas Eletronicos serco bloqueados (desbloqueio ss podera ser realizado com seu gerente de relacionamento); Atualize agora seu CARTCO, no link abaixo: http://www.bradesco.com.br/Recadastramento O Bradesco trabalha continuamente para o mais alto nmvel de seguranga de suas transagues contabeis. ) 2010 Bradesco SA. Todos os direitos reservados.
