Re: interupt mapping
D. E. Evans wrote: On a Toshiba Satellite a35-s1593, without a PC-card currently plugged in, I get a mapping error for the CardBus (cbb). I intend to purchase a wireless PC-Card (I haven't decided on model yet), and wish to ensure it will work with the cardbus before doing so. Try changing the BIOS for the CardBus slot to Controlled by OS or other option. The a35-s1593 does not have a BIOS option for modifying cardbus settings. The only changes allowed (besides enable/disable for peripherals) are with the parallel port interupt and io. I'm currently on BIOS version 1.40. Would manually configuring the interupt via the kernel help, or would it not be worth it? Are there other possibilities, or should I consider the cardbus unsupported? P.S. The following has the specs on the laptop: URL:http://linux.toshiba-dme.co.jp/linux/eng/spec.php3?model=PSA30U-03Q URL:http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_modelLanding.jsp?ProductMenu_0=PortablesProductMenu_1=SatelliteProductMenu_2=538089x=13y=10BV_SessionID=%40%40%40%401950244644.1155527485%40%40%40%40BV_EngineID=ccceaddiifjhfiecgfkceghdgngdgmn.0moid=538089smoid=truect=MHListType=Model P.P.S. The following has the flash update history: URL:http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_dtlViewDL.jsp?soid=864871moid=538089BV_SessionID=1950244644.1155527485BV_EngineID=ccceaddiifjhfiecgfkceghdgngdgmn.0ct=DL
interupt mapping
On a Toshiba Satellite a35-s1593, without a PC-card currently plugged in, I get a mapping error for the CardBus (cbb). I intend to purchase a wireless PC-Card (I haven't decided on model yet), and wish to ensure it will work with the cardbus before doing so. OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) CPU 2.80GHz (GenuineIntel 686-class) 2.80 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID real mem = 770154496 (752104K) avail mem = 695263232 (678968K) using 4278 buffers containing 38608896 bytes (37704K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(ca) BIOS, date 10/31/03, BIOS32 rev. 0 @ 0xfd750 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xfd750/0x8b0 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xce00 0xcd000/0x1000 0xdf000/0x1000! 0xe/0x4000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82852GM Hub-PCI rev 0x02 Intel 82852GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82852GM Configuration rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xe800, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82852GM AGP rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x03: irq 10 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x03: irq 9 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x03: irq 9 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x03: irq 9 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x83 pci1 at ppb0 bus 1 rl0 at pci1 dev 1 function 0 Realtek 8139 rev 0x10: irq 9, address 00:02:3f:ce:8c:30 rlphy0 at rl0 phy 0: RTL internal PHY cbb0 at pci1 dev 4 function 0 ENE CB-1410 CardBus rev 0x01pci_intr_map: no mapping for pin A : couldn't map interrupt ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x03: SpeedStep pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: IC25N040ATMR04-0 wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TOSHIBA, DVD-ROM SD-R2412, 1015 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x03: irq 10 iic0 at ichiic0 unknown at iic0 addr 0x18 not configured auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x03: irq 10, ICH4 AC97 ac97: codec id 0x414c4740 (Avance Logic ALC202) ac97: codec features headphone, 20 bit DAC, 18 bit ADC, Realtek 3D audio0 at auich0 Intel 82801DB Modem rev 0x03 at pci0 dev 31 function 6 not configured isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: using exception 16 pcic0 at isa0 port 0x3e0/2 iomem 0xd/16384 pcic0 controller 0: Intel 82365SL rev 2 has socket A only pcmcia0 at pcic0 controller 0 socket 0 pcic0: irq 3, polling enabled biomask ef75 netmask ef75 ttymask pctr: user-level cycle counter enabled dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 -- D. E. Evans [EMAIL PROTECTED]
Re: kde: kio accessing files in /etc
giving you the benefit of the doubt. Now that you know what kio is for, does it start to make sense why it would access files in /etc that pertain to file sharing? It is interesting to see the leaps in your logic. I do not run samba. It actually got installed by my mistake and I deleted as much of it as I could because I consider it a big security vulnerability. This begs the question how you installed Samba by mistake if you needed to delete as much of it as you could. Am I assuming to much in asking whether you used ports to install samba? What is it that you had to delete if you had used pkg_delete? Am I assuming to much by thinking that actually got installed means that you installed samba? The fact that you admit you installed it, while denying that you run samba, begs a leap in logic to blame others for their leap in logic, when you are the one who mentioned samba (via /etc). For blaming us for using leaps in logic, you're not leaving us much to work with, though it is interesting now that you mention it, considering you are having problems with KDE regarding it. Hmmm...you hadn't mentioned this before.
Re: kde: kio accessing files in /etc
You just don't get it, do you? It doesn't matter if you're running Samba or not. Kio will attempt to access those files which it is Correct me if I'm being ignorant, but I don't remember seeing this message from 3.8 or 3.9 KDE binaries that I have used (from the CDs). Is it possible that a Samba install could change the configuration of KDE when compiled from ports? Or is it merely that I'm not installing one of the KDE components (from ports) that would look for samba in the first place? Dave mentioned in the past that he had intended to keep his KDE system up to date, since ports wasn't always on top of the current version. Could using a personal port of an updated KDE influence its configuration if samba was installed, or perhaps be configured to look for samba inadvertently? I guess I wouldn't be asking these questions if enough information was being provided by Dave regarding his question.
Re: kde: kio accessing files in /etc
Which window manager(s) do you recommend? I'll try it(them). See URL:http://www.xwinman.org. Keep in mind the applications you will be running, and whether they need ICCCM or NetWM (EWMH) hints, or other dependencies for certain functions the ports system may not automatically provide.
Re: kde: kio accessing files in /etc
The question is, if I am not doing anything with those files, then why is kio accessing them? Why are you repeating your question when you've already been answered? It would be more beneficial for you and us to send patches, after consulting with the ports mailing list, that better adapt KDE to OpenBSD. After all, you've been using KDE on OpenBSD, according to you, for about 3-4 years, which is now closing on 4-5. Reading through your posts in those last 4 years tells me that you aren't paying attention to the FAQs. My first posts to this list got me skewered. It appears that you have gone through this as well on more than just the OpenBSD mailing lists, but you aren't learning from it. From the responses to my original posts, I realized that the problem was my own ignorance. After spending some time reading the FAQs, and Michael Lucas's Absolute OpenBSD, I realized how ignorant I had been in those early posts. I expect to be rudely skewered again if I post something stupid. Some of us have to learn the hard way.
Re: www.openbsd.org defaults to Japanese
Roger Neth Jr [EMAIL PROTECTED] writes: Jesus said to him, I am the way, and the truth, and the life. No one comes to the Father except through me. That would directly contradict the previous advice of thinking for one's self. Why is this conversation persisting? If I wanted preaching, I'd join a Christian or athiest mailing list, not OpenBSD misc.
groff
I notice groff hasn't been updated in 2-3 years. Any particular reason?
Re: Mail option
Maybe my reply didn't make it: use ports' mail/nail package. It did. Nail is one option, but seems a bit much for the want of a single option, when the program that ships with OpenBSD will already do. It will be easier (and perhaps a learning experience) to submit a patch to the current Mail, or decide that a signature is something non-standard (or not-yet-standard), and therefore not worth the bother.
Re: Why advocate Old daemon book?
The state of the art of computer science has gone (steadily?) downhill for the last 30 (maybe 40) years. The computers are bigger and faster, but the knowedge of what to do with them has decayed. That time would it put it at about 1974, when the altair came out, and home users got to build their own computer for home use. Except I seem to remember that most software shipped in cartridges. The problem was when software was sold to the end user *and* technical support was offered to baby them along. There are a few pockets of resistance to the decay. A rebellion of a few programmers who refuse to baby their users, while at the same time enabling those users to learn the system. Imagine that... Hard love works.
Re: 3.7: weird IP address problem
Upgrade from 3.7 to 3.9. It may be fixed in 3.9 (I remember stuff that was For the sake of clarity, upgrade to 3.8 first, *then* 3.9.
Re: Mail option
I know this isn't the answer you were looking for, but in the past I've added the -- to my .signature. Technically that's not a correct thing to do, but in practice it worked fine for me. Since I use tin for news, and Mail for mail, this would cause a conflict, since tin automatically adds the -- and then appended .signature. As for the deafening silence / technical merit question: I think it's just a matter of priorities. It's not a problem that is stopping anyone from getting work done. Just an inconvenience that seems easily resolved. If I get some time, I'll look into how to add it myself.
startx
Perhaps this should be sent to x.org, but since OpenBSD maintains its own X, I must ask: why is startx using .serverauth.$$ for its xauth, instead of $XAUTHORITY? This seems redundant, and a pain in the ass for those of us who find xdm boring, finding xdm redundant. -- D. E. Evans [EMAIL PROTECTED]
Re: mount floppy drive
mount_msdos /dev/fd0c I get a 'device not configured' error. snip Any other ideas? What about a higher device letter? fd0d? fd0i?
Re: OpenBSD 3.9 stable from cvs
So you say that the patch should go into OPENBSD_3_9 branch after 3.9 is *officially* released? Well, I wonder how people who pre-orded their CDs, got them, installed 3.9-RELEASE and run Sendmail are going to patch their systems? I got 3.8 almost 2 weeks early, and seem to remember applying -stable that day, (though I don't believe there were needful security patches at the time). What I would have found unusual is to not have security patches applied to the tree. Just because upgrading via CVS will most likely hose your system, doesn't mean that once upgraded properly it shouldn't be available. CDs went out almost a month early this time around, which would have made for an awkward situation, even with the manual patches available.
Mail option
Maybe I'm the only one around who still uses it, but there's one option in mailx from SysV that I miss with OpenBSD: ~a. It would be simpler to have either ~a to add the -- with newline, and read in my .signature, or a .mailrc option that automates the additions, (preferably both). As it is now, I must manually add the -- and newline, then ~r my .signature. Any takers? -- D. E. Evans [EMAIL PROTECTED] URL:http://www.deevans.net
Re: openbsd ports or pkgsrc
On Thu, Apr 13, 2006 at 10:40:13AM +0200, Francois Visconte wrote: Is there many people using pkgsrc on openbsd ? I used it at one time, but found that OpenBSD's ports system made more sense for OpenBSD. Is there any particular problem using pkgsrc on openbsd ? URL:http://www.netbsd.org/Documentation/software/packages.html
Is there an append function ~a for inserting text, especially regarding signatures?
Re: lesstif
I finally got xpdf to compile without openmotif, (see the unanswered request from 17 June 2005). One nice feature of the ports is that if lesstif is already installed, it won't install openmotif. With xpdf, If I set USE_MOTIF to no, and then compile xpdf *after* having installed lesstif this will work, (I thought I tried this before, but it seems to work now). There's no FLAVOR for using lesstif instead of motif. Should there be, or is there a better way that I should be going about this, for which I've overlooked?
