Problems mounting Creative Zen Nano Plus
Hi, I recently purchased a 1GB Creative Zen Nano Plus, and experience problems mounting it on the snapshot from 7th of June. It doesn't work on 3.9 either, but mounts OK on Windows and Linux. $ sudo mount /dev/sd0i /mnt^M mount_msdos: /dev/sd0i on /mnt: not an MSDOS filesystem $ Disklabel of the Zen Nano: # /dev/rsd0c: type: SCSI disk: SCSI disk label: Zen Nano Plus flags: bytes/sector: 2048 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 248 total sectors: 509184 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] c:509184 0 unused 0 0 # Cyl 0 - 248* i:50913351 MSDOS # Cyl 0*- 248* dmesg: OpenBSD 3.9-current (GENERIC) #870: Wed Jun 7 17:11:37 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Athlon(tm) XP 1800+ (AuthenticAMD 686-class, 256KB L2 cache) 1.54 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 536379392 (523808K) avail mem = 481722368 (470432K) using 4256 buffers containing 26923008 bytes (26292K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(b1) BIOS, date 06/30/03, BIOS32 rev. 0 @ 0xfb490, SMBIOS rev. 2.2 @ 0xf (37 entries) apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde90/240 (13 entries) pcibios0: PCI Exclusive IRQs: 5 11 12 pcibios0: no compatible PCI ICU found pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xfc00 0xd/0x4000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 NVIDIA nForce2 PCI rev 0xc1 NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 1 not configured NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 2 not configured NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 3 not configured NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 4 not configured NVIDIA nForce2 rev 0xc1 at pci0 dev 0 function 5 not configured pcib0 at pci0 dev 1 function 0 NVIDIA nForce2 ISA rev 0xa4 nviic0 at pci0 dev 1 function 1 NVIDIA nForce2 SMBus rev 0xa2 iic0 at nviic0 iic1 at nviic0 ohci0 at pci0 dev 2 function 0 NVIDIA nForce2 USB rev 0xa4: irq 11, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci0 dev 2 function 1 NVIDIA nForce2 USB rev 0xa4: irq 5, version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0 at pci0 dev 2 function 2 NVIDIA nForce2 USB rev 0xa4: irq 12 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered nfe0 at pci0 dev 4 function 0 NVIDIA nForce2 LAN rev 0xa1: irq 12, address 00:04:61:4d:30:9f rlphy0 at nfe0 phy 1: RTL8201L 10/100 PHY, rev. 1 ppb0 at pci0 dev 8 function 0 NVIDIA nForce2 PCI-PCI rev 0xa3 pci1 at ppb0 bus 1 eap0 at pci1 dev 8 function 0 Ensoniq CT5880 rev 0x02: irq 5 ac97: codec id 0x54524123 (TriTech Microelectronics TR28602) audio0 at eap0 midi0 at eap0: AudioPCI MIDI UART rl0 at pci1 dev 11 function 0 Realtek 8139 rev 0x10: irq 11, address 00:04:61:4d:30:3b rlphy1 at rl0 phy 0: RTL internal PHY ATT/Lucent FW322 1394 rev 0x61 at pci1 dev 13 function 0 not configured pciide0 at pci0 dev 9 function 0 NVIDIA nForce2 IDE rev 0xa2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: IC35L120AVV207-0 wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors wd1 at pciide0 channel 0 drive 1: SAMSUNG SV1604N wd1: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1(pciide0:0:1): 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: HL-DT-ST, DVDRAM GSA-4165B, DL03 SCSI0 5/cdrom removable wd2 at pciide0 channel 1 drive 1: WDC WD2000BB-00GUA0 wd2: 16-sector PIO, LBA48, 190782MB, 390721968 sectors cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5 ppb1 at pci0 dev 30 function 0 NVIDIA nForce2 AGP rev 0xc1 pci2 at ppb1 bus 2 vga1 at pci2 dev 0 function 0 NVIDIA GeForce4 MX 440 rev 0xa3 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot
Re: detect if a flag-day has happened in the meanwhile
Hi, On 2005-10-06 at 04:17, knitti wrote: On 10/3/05, Han Boetes [EMAIL PROTECTED] wrote: But this is not for me. This is to automate a sysadmin task. So I'd like to automate detecting a ``flag day.'' I know you stated you want to compare the binaries. But somewhere the new kernel has to be built, so you check the cvs output for a /M sys\// or someting like this? I think he wants to compare already built kernels, from two different snapshots.
gphoto2/gtkam segmentation fault on i386-current
Hi, Recently I've experienced (apparently libusb-related) segmentation faults when trying to use gphoto2 or gtkam. I'm running a snapshot from Sep 23 on i386. The camera I'm trying to access is a Canon Powershot A70. gphoto2 output: $ gphoto2 --auto-detect --shell gphoto2:/usr/local/lib/libusb.so.8.2: undefined symbol 'usb_free_bus' lazy binding failed! Segmentation fault (core dumped) I get the same messages when I start gtkam and select Camera - Add Camera... dmesg: http://aon.iki.fi/tmp/dmesg gtkam backtrace: http://aon.iki.fi/tmp/gtkam_bt gphoto2 backtrace: http://aon.iki.fi/tmp/gphoto2_bt (snipped, after that it was just No symbol table info available.)
Re: gphoto2/gtkam segmentation fault on i386-current
Hey, On 2005-09-25 at 21:05, Juan J. Martmnez wrote: I think this problem is related to PTP support. May be it supports other protocol, from gphoto2: No, I don't think so: $ gphoto2 --camera Canon PowerShot A70 --shell gphoto2:/usr/local/lib/libusb.so.8.2: undefined symbol 'usb_free_bus' lazy binding failed! Segmentation fault (core dumped) $ gphoto2 --camera Canon PowerShot A70 (PTP) --shell gphoto2:/usr/local/lib/libusb.so.8.2: undefined symbol 'usb_free_bus' lazy binding failed! Segmentation fault (core dumped) I don't think it even gets to the point where it starts dealing with the camera. Heck, it even happens without anything attached with any driver or --auto-detect :) Antti
Re: Banned from #openbsd
Hi, On 2005-09-21 at 02:59, John Kintaro Tate wrote: Since I have no idea where to go about this, I thought somebody here might be able to fill me in. For some reason I am banned from #openbsd on freenode. I want to get unbanned but I have no idea on who to contact about this. I don't know why I am banned, I guess someone on my netblock was being retarded or someone on my computer considering I had idiot friends using it the other day, but I am unsure. Gee, I wonder why... 17:00 xKintaro excuse me buit does anyone klnow how 2 clean the penis 17:00 xKintaro mine is a bitn itchy andf green 17:01 -!- mode/#openbsd [+o NicM] by ChanServ 17:01 -!- mode/#openbsd [+b [EMAIL PROTECTED] by NicM 17:01 -!- xKintaro was kicked from #openbsd by NicM [bye] Usually, bans will get removed eventually, and there's no reason to take this stuff to the mailing lists.
Re: Floppy problems... (fdc missing in /dev)
On 2005-09-05 at 21:31, [EMAIL PROTECTED] wrote:
I've noticed that fdc isn't in /dev/.
I noticed it during I tried to boot a floppy.
You probably want to access a floppy drive, which are called fd*, not
fdc*.
From fdc(4):
The standard names of a floppy drive will take the form
/dev/fd{0,1,2,3}{,B,C,D,E,F,G,H}[a-p].
On a working system you'd supposedly get something like:
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
HTH
Re: [OT]: good home switch?
Hi, On Sun, Sep 04, 2005 at 12:19:39PM +0200, Przemyslaw Nowaczyk wrote: the D-Link DES-1005D Switch 10/100 Mbit/s 5-port I've had one of these since 2002 or 2003 and it has worked solidly ever since. Of course, it'd be weird if such a simple device had any problems. -- Antti Nykdnen || [EMAIL PROTECTED] || http://aon.iki.fi
Re: [OT]: good home switch?
On Sun, Sep 04, 2005 at 04:01:26PM +0200, [EMAIL PROTECTED] wrote: Their Routers crash, their Firmware is insecure (Firmwareupdate - Admin-PW == empty but configuration still works), their Switches are fucked up and even their simple PCI-WLan-Cards have totaly fucked up Revisions or just no country-code (like my card). I never had any positiv experience with D-Link, realy never. No matter if it deals with manages/unmanages switches, Routers, PCI-Cards. Hmm. It's weird that I can't recall a single broken or otherwise malfunctioning D-Link product. This includes the switch and 802.11b PCMCIA cards I have at home and various other switches and NICs I've used elsewhere. Perhaps I have luck, then :) -- Antti Nykdnen || [EMAIL PROTECTED] || http://aon.iki.fi
Re: OpenCVS - Some questions
Hi, On Sun, Sep 04, 2005 at 09:32:32PM +0200, [EMAIL PROTECTED] wrote: So can we exspect some neat options GNU-CVS dosn't provide? This interview has some info: http://nedbsd.nl/modules/static/page/JorisVinkInterview
Re: sysctl tuning for maximum network performance [off topic]
On Fri, Sep 02, 2005 at 09:04:48AM +0200, Stephan A. Rickauer wrote: You see, most blokes will be playing at 10. Youre on 10, all the way up, all the way up...Where can you go from there? Nowhere. What we do, is if we need that extra push over the cliff...Eleven. One louder. Why dont you just make 10 louder and make 10 be the top number, and make that a little louder? ;) -- Antti Nykdnen || [EMAIL PROTECTED] || http://aon.iki.fi
Re: My OpenBSD system cannot load any shared object anymore!!!
On Mon, Aug 22, 2005 at 03:52:13PM +0200, Han Boetes wrote: Try rebooting. I think he did: Joco Salvatti wrote: I thought that restarting the system the problem would be solved, but it got wrost.
Re: how to stop chrooting
Hi, On Sat, Aug 20, 2005 at 05:05:51PM +0200, gwost wrote: I have chrooted openbsd 3.7 server, but temporary I neet to acces some other directoryes on machine, so I won't to stop chrooting. How to do that. See httpd(8) or /etc/rc.conf.
