XFree86 4.2.99.3 on -CURRENT
Hello, Has anyone had any success with this combo? It compiles fine, but the X server aborts due to bus error (SIGBUS) generated by something in xf86GetPciBridgeInfo() (xc/programs/Xserver/hw/xfree86/common/xf86pciBus.c) Running -CURRENT (World/kernel) as of December 29. XFree86 sources as of December 30, cvsup'ed with tag xf-4_2_99_3 Since this version is going to be XFree86 4.3.0 sometime in January, it would be nice to make sure it runs on FreeBSD 5.0 :) -- Frode Nordahl [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 4.2.99.3 on -CURRENT
On Tue, 2002-12-31 at 11:30, Szilveszter Adam wrote: Hmmm. I have the same version of X as you (roughly, the tag was already in place by the time I built although I always use HEAD, I built on 23rd December) and FreeBSD is from 25th December. I just updated the sources to HEAD, and I see changes was made in FreeBSD related configfiles and other related .c files around December 23. I will try to compile again and see what happends (I have tried to compile from HEAD earlier with the same results) I have a laptop with following hardware: - VIA Chipset NB: VIA8603 SB: VIA686B - Celeron 1.0Ghz - S3 ProSavage (Twister) AGP -- Frode Nordahl [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP2 won't stay powered off
Hey, Nate Sorry about the late reply, but here is my output: hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 2 hw.acpi.cpu.current_speed: 2 hw.acpi.cpu.performance_speed: 2 hw.acpi.cpu.economy_speed: 1 This is from a HP Vei8 computer, and it turns itself on about 20 minutes after a shutdown -p now. -- Mvh, Frode Nordahl On Thu, 2002-12-05 at 19:37, Nate Lawson wrote: On Thu, 5 Dec 2002, Mathew Kanner wrote: I've noticed some odd behavior when I installed DP2 on my machine last night. When I shutdown -p now, the machine will turn itself back-on in about twenty minutes. This would be nice feature if I had asked for it. Can everyone with the auto power on problem report the output of sysctl hw.acpi? -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: UMASS USB bug? (getting the Sony disk-on-key device working).
Hey, Matt While you're at it, could you have a look at PR kern/46176 ? =) At least would you tell me if you have the same problem with your device(s) On Thu, 2002-12-19 at 11:32, Matthew Dillon wrote: It took a hellofalong time pulling my hair out trying to figure out why the Sony disk-on-key I just bought didn't work. First I added a Quirk entry for the standard 6-byte problem, but it didn't solve the problem. Finally, after slogging through an insane amount of debugging (I mean, it really generates a lot of debugging if you turn it all on!) I came up with the following patch. It appears that when an error occurs and the umass device tries to read the sense data that it fails comparing: sc-transfer_datalen - sc-transfer_actlen != UGETDW(sc-csw.dCSWDataResidue). As far as I can sc-transfer_actlen is NEVER updated. It is always 0, so I don't quite see how the calculation could ever possibly be correct if DataResidue is what I think it is (a count-down of the number of unused bytes after a transfer). Note that my other UMASS device, a compact flash reader, has always worked fine with just the Quirk entry. I really need a USB expert to tell me what is going on :-) With the patch below my Sony diskkey works. Note that the junk at the end of the patch is debugging. I noticed that the CAM layer thought the READCAPACITY command succeeded when it didn't, and it was generating weird sector-size errors due to the malloc'd return buffer containing garbage. I had to put real values in the buffer to catch the problem consistently. I don't know why the UMASS layer was returning a success code to CAM for failed READCAPACITY commands but it took an hour just to figure that CAM was using garbage in the return buffer. USB Experts gravitate here! Tell me I'm right or explain to me why I'm wrong, because this stuff is incredibly complex and I'm having problems thinking straight at 2:30 a.m. :-) -Matt -- Frode Nordahl [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[no subject]
Installing 5.0-DP2 From: Frode Nordahl [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.8) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, Installation from DOS fs does not work. The firsr error message is Operation not permitted, conequetive attempts fails with /dist allready exists or similar. Unable to delete non-freebsd partitions from Fdisk. Setting them to type 165 and then deleting works. Since installation from DOS is my only option right now, i went ahead using installer from a june -CURRENT. This almost worked, but the boot code was not properly written. The BootMgr comes up, but I get no further. Trying Fixit from the 5.0-DP2 boot disks fails! Similar error as when trying install from DOS fs. Fixing this after boot does not work because of GEOM :( Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Installing 5.0-DP2
Sorry about previous posting without subject. It was supposed to be Installing 5.0-DP2. I was posting with my webmail using Lynx, so I guess that combination did not work well :) Mvh, Frode Nordahl Frode Nordahl said: Hello, Installation from DOS fs does not work. The firsr error message is Operation not permitted, conequetive attempts fails with /dist allready exists or similar. Unable to delete non-freebsd partitions from Fdisk. Setting them to type 165 and then deleting works. Since installation from DOS is my only option right now, i went ahead using installer from a june -CURRENT. This almost worked, but the boot code was not properly written. The BootMgr comes up, but I get no further. Trying Fixit from the 5.0-DP2 boot disks fails! Similar error as when trying install from DOS fs. Fixing this after boot does not work because of GEOM :( Mvh, Frode Nordahl -- Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [acpi-jp 1926] Re: acpid implementation?
On Sat, 2002-11-09 at 09:59, Michael Smith wrote: I'm sure people have this and other things they want to configure their computer to do on sleep / resume. I'm sure that you think that FreeBSD needs an acpid because Linux has an acpid. No, I think FreeBSD needs an acpid because it has a apmd, and this gives the user freedom and flexibility to do whatever he wants, and do something with acpi events in userland if he pleases. I don't know if Linux has a acpid or what features it has, and I don't care. Most of the other things that an 'acpid' would do are specific examples of more general classes of events, for which software should be able to request notification and handle it accordingly. That would be excellent. I don't see how any application would be able to do something before a sleep operation this way though. If the kernel was to wait for every app. requesting this, it would cause trouble. = Mike Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: acpid implementation?
On Fri, 2002-11-08 at 22:23, Hiten Pandya wrote: On Wed, Nov 06, 2002 at 10:27:47PM +0100, Frode Nordahl wrote the words in effect of: Hello, I have been searching mailing lists and my friend Google for information about a acpid (like apmd) implementation for FreeBSD, but I have found nothing. Does one exist anywhere, or has anyone started out on something without telling anyone? :) Why do you need an acpid? misc stuff instruct dhclient to get a new lease on resume (maybe free it on sleep), try to configure wlan if no link detected on ethernet etc. I put my computer to sleep instead of turning it of most of the time, and having to run killall dhclient; dhclient dc0 every time I resume it after coming home / go to work is a bit annoying :) I'm sure people have this and other things they want to configure their computer to do on sleep / resume. -- Hiten Pandya [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Some problems with Orinoco card in -CURRENT
Hello, With OLDCARD there is no problem. boot -v attached. On Wed, 2002-11-06 at 23:45, Frode Nordahl wrote: Hey, On Wed, 2002-11-06 at 23:28, M. Warner Losh wrote: Strange. OLDCARD or NEWCARD? Send me a full dmesg for each case, since it is likely some resource conflict or another. I do what you've described hundreds of times over the past few months, so it has to be something weird with your computer. My computer might be wierd :) I have a problem with the BIOS not initializing the memory correctly (I often see dmesg output and post morten messages from previous boot). So I even did a __cold__ reboot (unplug AC, remove battery for a while) before this dmesg (boot -v). I only hav NEWCARD kernel available at this time, will post a OLDCARD boot -v ASAP. (See attachment) Warner. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Mon Nov 4 14:23:41 CET 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SAMWISE Preloaded elf kernel /boot/kernel/kernel at 0xc05bc000. Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc05bc0b4. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc05bc168. Preloaded elf module /boot/kernel/acpi.ko at 0xc05bc214. Calibrating clock(s) ... TSC clock: 1193637253 Hz, i8254 clock: 1193135 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 1193693787 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1193.69-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 234881024 (229376K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x005e3000 - 0x0dee, 227594240 bytes (55565 pages) 0x0df0 - 0x0dff7fff, 1015808 bytes (248 pages) avail memory = 221925376 (216724K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7290 bios32: Entry = 0xfd6f0 (c00fd6f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd6f0+0x11e pnpbios: Found PnP BIOS data at 0xc00f72f0 pnpbios: Entry = f:97e0 Rev = 1.0 Other BIOS signatures found: Initializing GEOMetry subsystem null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 73 80 00 c0 01 00 00 00 22 00 00 01 ef 01 00 01 57 79 00 c0 68 79 00 c0 70 79 00 c0 00 01 01 01 03 01 05 01 07 01 0e 01 0f 01 11 01 12 01 14 01 15 01 17 01 18 01 1a 01 1b 01 VESA: 39 mode(s) found VESA: v2.0, 31680k memory, flags:0x1, mode table:0xc04c36a2 (122) VESA: S3 Incorporated. Twister BIOS VESA: S3 Incorporated. VBE 2.0 Rev 1.1 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06051106) Using $PIR table, 8 entries at 0xc00fdf40 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded00A 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00B 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00C 0x57 3 4 5 6 7 9 10 11 12 14 15 embedded00D 0x55 3 4 5 6 7 9 10 11 12 14 15 embedded07C 0x56 5 embedded07D 0x57 11 embedded04A 0x55 10 embedded04B 0x56 11 embedded0 13A 0x56 5 embedded01A 0x55 10 embedded10A 0x55 10 embedded0 16A 0x57 11 embedded0 16B 0x56 11 embedded0 17A 0x56 11 embedded0 17B 0x57 11 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial
Some problems with Orinoco card in -CURRENT
in wi_cmd 0x000a; event status 0x wi0: failed to allocate 1594 bytes on NIC wi0: tx buffer allocation failed wi0: timeout in wi_cmd 0x000a; event status 0x wi0: failed to allocate 1594 bytes on NIC wi0: mgmt. buffer allocation failed wi0: timeout in wi_cmd 0x0011; event status 0x wi0: timeout in wi_cmd 0x0011; event status 0x wi0: timeout in wi_cmd 0x0011; event status 0x wi0: timeout in wi_cmd 0x0011; event status 0x wi0: detached (the detached is probably me ejecting the card. Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
pccard state after ACPI resume
Hello, Another problem with my Orinoco card is that after a resume from (ACPI) sleep, the configuration set on the card is lost, so I have to set the ssid, wepkey etc again before it can operate properly. I am not sure if this is a flaw in the wi0 driver (probably not) or something missing in general for all cards. As of right now I do not have any other pccards available to check if this happens to other cards. What should be responsible for reconfiguring cards on resume? Should this be remembered by each individual driver or some other part of the kernel, or should this be done by userland programs? (apmd, acpid) Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
acpid implementation?
Hello, I have been searching mailing lists and my friend Google for information about a acpid (like apmd) implementation for FreeBSD, but I have found nothing. Does one exist anywhere, or has anyone started out on something without telling anyone? :) Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pccard state after ACPI resume
On Wed, 2002-11-06 at 23:22, M. Warner Losh wrote: In message: 010501c285dc$87da1170$[EMAIL PROTECTED] Matthew Emmerton [EMAIL PROTECTED] writes: : This also happens with my an0 card, so it's probably a larger ACPI + PCCARD : interoperability issue. Its a ACPI issue. We do the right things in the drivers and bridge drivers. Do the cards detach/attach? If not, then you aren't really suspending. wi0 detaches and reattaches here (both in sleep state 1 and 3). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pccard state after ACPI resume
On Wed, 2002-11-06 at 23:38, M. Warner Losh wrote: : wi0 detaches and reattaches here (both in sleep state 1 and 3). OK. OLDCARD or NEWCARD? My laptop still doesn't suspend/resume correctly, so I've been unable to test patches. NEWCARD Warner Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Some problems with Orinoco card in -CURRENT
Hey, On Wed, 2002-11-06 at 23:28, M. Warner Losh wrote: Strange. OLDCARD or NEWCARD? Send me a full dmesg for each case, since it is likely some resource conflict or another. I do what you've described hundreds of times over the past few months, so it has to be something weird with your computer. My computer might be wierd :) I have a problem with the BIOS not initializing the memory correctly (I often see dmesg output and post morten messages from previous boot). So I even did a __cold__ reboot (unplug AC, remove battery for a while) before this dmesg (boot -v). I only hav NEWCARD kernel available at this time, will post a OLDCARD boot -v ASAP. (See attachment) Warner. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Mon Nov 4 14:23:41 CET 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SAMWISE Preloaded elf kernel /boot/kernel/kernel at 0xc05bc000. Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc05bc0b4. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc05bc168. Preloaded elf module /boot/kernel/acpi.ko at 0xc05bc214. Calibrating clock(s) ... TSC clock: 1193637253 Hz, i8254 clock: 1193135 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 1193693787 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1193.69-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 234881024 (229376K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x005e3000 - 0x0dee, 227594240 bytes (55565 pages) 0x0df0 - 0x0dff7fff, 1015808 bytes (248 pages) avail memory = 221925376 (216724K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7290 bios32: Entry = 0xfd6f0 (c00fd6f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd6f0+0x11e pnpbios: Found PnP BIOS data at 0xc00f72f0 pnpbios: Entry = f:97e0 Rev = 1.0 Other BIOS signatures found: Initializing GEOMetry subsystem null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 73 80 00 c0 01 00 00 00 22 00 00 01 ef 01 00 01 57 79 00 c0 68 79 00 c0 70 79 00 c0 00 01 01 01 03 01 05 01 07 01 0e 01 0f 01 11 01 12 01 14 01 15 01 17 01 18 01 1a 01 1b 01 VESA: 39 mode(s) found VESA: v2.0, 31680k memory, flags:0x1, mode table:0xc04c36a2 (122) VESA: S3 Incorporated. Twister BIOS VESA: S3 Incorporated. VBE 2.0 Rev 1.1 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06051106) Using $PIR table, 8 entries at 0xc00fdf40 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded00A 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00B 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00C 0x57 3 4 5 6 7 9 10 11 12 14 15 embedded00D 0x55 3 4 5 6 7 9 10 11 12 14 15 embedded07C 0x56 5 embedded07D 0x57 11 embedded04A 0x55 10 embedded04B 0x56 11 embedded0 13A 0x56 5 embedded01A 0x55 10 embedded10A 0x55 10 embedded0 16A 0x57 11 embedded0 16B 0x56 11 embedded0 17A 0x56 11 embedded0 17B 0x57 11 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.PCI0.PIB_.LNKA irq 10: [ 10] low,level,sharable 0.1.0 \\_SB_.PCI0.PIB_.LNKA irq 10: [ 10] low,level,sharable 0.4.0 \\_SB_.PCI0.PIB_.LNKB irq 11: [ 11] low,level,sharable 0.4.1
Re: Some problems with Orinoco card in -CURRENT
(One note on this dmesg output, the detach and following attach is as you might guess me ejecting and reinserting the card. The previous mail and this was sent via the Orinoco card.. :) OLDCARD dmesg will follow tomorrow, gotta hit the sack...) On Wed, 2002-11-06 at 23:45, Frode Nordahl wrote: Hey, On Wed, 2002-11-06 at 23:28, M. Warner Losh wrote: Strange. OLDCARD or NEWCARD? Send me a full dmesg for each case, since it is likely some resource conflict or another. I do what you've described hundreds of times over the past few months, so it has to be something weird with your computer. My computer might be wierd :) I have a problem with the BIOS not initializing the memory correctly (I often see dmesg output and post morten messages from previous boot). So I even did a __cold__ reboot (unplug AC, remove battery for a while) before this dmesg (boot -v). I only hav NEWCARD kernel available at this time, will post a OLDCARD boot -v ASAP. (See attachment) Warner. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Mon Nov 4 14:23:41 CET 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SAMWISE Preloaded elf kernel /boot/kernel/kernel at 0xc05bc000. Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc05bc0b4. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc05bc168. Preloaded elf module /boot/kernel/acpi.ko at 0xc05bc214. Calibrating clock(s) ... TSC clock: 1193637253 Hz, i8254 clock: 1193135 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 1193693787 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1193.69-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 234881024 (229376K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x005e3000 - 0x0dee, 227594240 bytes (55565 pages) 0x0df0 - 0x0dff7fff, 1015808 bytes (248 pages) avail memory = 221925376 (216724K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7290 bios32: Entry = 0xfd6f0 (c00fd6f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd6f0+0x11e pnpbios: Found PnP BIOS data at 0xc00f72f0 pnpbios: Entry = f:97e0 Rev = 1.0 Other BIOS signatures found: Initializing GEOMetry subsystem null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 73 80 00 c0 01 00 00 00 22 00 00 01 ef 01 00 01 57 79 00 c0 68 79 00 c0 70 79 00 c0 00 01 01 01 03 01 05 01 07 01 0e 01 0f 01 11 01 12 01 14 01 15 01 17 01 18 01 1a 01 1b 01 VESA: 39 mode(s) found VESA: v2.0, 31680k memory, flags:0x1, mode table:0xc04c36a2 (122) VESA: S3 Incorporated. Twister BIOS VESA: S3 Incorporated. VBE 2.0 Rev 1.1 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06051106) Using $PIR table, 8 entries at 0xc00fdf40 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded00A 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00B 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00C 0x57 3 4 5 6 7 9 10 11 12 14 15 embedded00D 0x55 3 4 5 6 7 9 10 11 12 14 15 embedded07C 0x56 5 embedded07D 0x57 11 embedded04A 0x55 10 embedded04B 0x56 11 embedded0 13A 0x56 5 embedded01A 0x55 10 embedded10A 0x55 10 embedded0 16A 0x57 11 embedded0 16B 0x56 11 embedded0 17A 0x56 11 embedded0 17B 0x57 11 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b
CNet CNWLC-811 (PRISM2), kernel panic
Hello,
Just bought a CNet WLAN card, and it makes -CURRENT panic when inserted,
or if it is inserted while booting.
Userland installed from 20021101 snapshot.
Kernel from today: FreeBSD 5.0-CURRENT #0: Sat Nov 2 09:50:05 CET 2002
(second panic from me issuing panic from ddb)
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xd11fa000
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01aa2d5
stack pointer = 0x10:0xcc00494c
frame pointer = 0x10:0xcc004b78
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 9 (cbb1)
panic: from debugger
Fatal trap 3: breakpoint instruction fault while in kernel mode
instruction pointer = 0x8:0xc03b47d4
stack pointer = 0x10:0xcc0046bc
frame pointer = 0x10:0xcc0046c8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= IOPL = 0
current process = 9 (cbb1)
panic: from debugger
Uptime: 1m11s
Dumping 224 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112 128 144 160 176 192 208
---
#0 doadump () at ../../../kern/kern_shutdown.c:232
232 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:232
#1 0xc0242d89 in boot (howto=260) at ../../../kern/kern_shutdown.c:364
#2 0xc0242fd3 in panic () at ../../../kern/kern_shutdown.c:517
#3 0xc0147ac2 in db_panic () at ../../../ddb/db_command.c:450
#4 0xc0147a42 in db_command (last_cmdp=0xc0429b40, cmd_table=0x0,
aux_cmd_tablep=0xc0422fb8, aux_cmd_tablep_end=0xc0422fbc)
at ../../../ddb/db_command.c:346
#5 0xc0147b56 in db_command_loop () at ../../../ddb/db_command.c:472
#6 0xc014a80a in db_trap (type=12, code=0) at ../../../ddb/db_trap.c:72
#7 0xc03b4532 in kdb_trap (type=12, code=0, regs=0xcc00490c)
at ../../../i386/i386/db_interface.c:166
#8 0xc03c5e12 in trap_fatal (frame=0xcc00490c, eva=0)
at ../../../i386/i386/trap.c:841
#9 0xc03c5b22 in trap_pfault (frame=0xcc00490c, usermode=0,
eva=3508510720)
at ../../../i386/i386/trap.c:760
#10 0xc03c558d in trap (frame=
{tf_fs = -1037107176, tf_es = -872415216, tf_ds = -1072168944,
tf_edi = -1036984320, tf_esi = -1037051392, tf_ebp = -872395912, tf_isp
= -872396488, tf_ebx = 0, tf_edx = -786460672, tf_ecx = -1037071868,
tf_eax = 4096, tf_trapno = 12, tf_err = 0, tf_eip = -1071996203, tf_cs =
8, tf_eflags = 66050, tf_esp = -1037051392, tf_ss = -1036984320}) at
../../../i386/i386/trap.c:446
#11 0xc03b5d08 in calltrap () at {standard input}:98
#12 0xc01aa105 in pccard_read_cis (sc=0x0)
at ../../../dev/pccard/pccard_cis.c:98
#13 0xc01a7ab2 in pccard_attach_card (dev=0xc230e000)
at ../../../dev/pccard/pccard.c:168
#14 0xc01afd26 in cbb_insert (sc=0xc22f8a00) at card_if.h:66
#15 0xc01afad8 in cbb_event_thread (arg=0xc22f8a00)
at ../../../dev/pccbb/pccbb.c:917
#16 0xc022dab4 in fork_exit (callout=0xc01afa40 cbb_event_thread,
arg=0x0,
frame=0x0) at ../../../kern/kern_fork.c:860
(kgdb)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Installing CURRENT 20021101
Hello, Got the 20021101 snapshot from USW2 to have some fun with testing, and hoping to get my new WLAN card to work :) I got some trouble installing. - When installing over network, reinitializing network media does not work. If you select wrong the first time, the only way to redo your selection is to reboot. Using the dc0 driver. (Network connection pulled down and not set up again it seems.) I was unable to complete a NFS install, but I didn't try too hard because of having to reboot on every try. The nasty part: - fdisk showed all partitions as type 165 (FreeBSD), I took a chance and continued anyway. Now my two non-FreeBSD partitions are lost :) The partitions were: ad0s1 NTFS(WindowsXP) ad0s2 FreeBSD ad0s4 DOS, FAT32 (I guess I can get them back by setting correct type...) fdisk also showed them in the wrong order, ad0s1 first, then ad0s4 and then ad0s2. Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CNet CNWLC-811 (PRISM2), kernel panic
Hello, With OLDCARD it does not crash! After crafting a pccard.conf entry for the card, wi does not successfully attach to the card. Do you think it is feasible to add support for this card in the wi driver? Please don't hesitate to ask me for more information if you need it, thanks! If there is any dirty work to be done to make it work, tell me. I'll be more than happy to do it for you :) pccard.conf line: # CNet CNWLC-811 card OEM 11Mbps Wireless LAN PC Card V-3 config auto wi ? insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop I get the following output from the driver: wi0 at port 0x240-0x27f irq 11 slot 1 on pccard1 wi0: timeout in wi_cmd 0x; event status 0x wi0: timeout in wi_cmd 0x; event status 0x wi0: timeout in wi_cmd 0x; event status 0x wi0: init failed wi0: timeout in wi_cmd 0x0021; event status 0x wi0: timeout in wi_cmd 0x0021; event status 0x wi0: mac read failed 5 device_probe_and_attach: wi0 attach returned 5 # pccardc dumpcis Configuration data for card in slot 1 Tuple #1, code = 0x17 (Attribute memory descriptor), length = 3 000: d9 01 ff Attribute memory device information: Device number 1, type Function specific, WPS = ON Speed = 250nS, Memory block size = 2Kb, 1 units Tuple #2, code = 0x1d (Other conditions for attribute memory), length = 4 000: 01 d9 01 ff (MWAIT) Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 00 00 00 PCMCIA ID = 0x0, OEM ID = 0x0 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 39 000: 05 00 4f 45 4d 00 31 31 4d 62 70 73 20 57 69 72 010: 65 6c 65 73 73 20 4c 41 4e 20 50 43 20 43 61 72 020: 64 20 56 2d 33 00 ff Version = 5.0, Manuf = [OEM], card vers = [11Mbps Wireless LAN PC Card V-3] Tuple #6, code = 0x1a (Configuration map), length = 6 000: 01 02 00 08 03 ff Reg len = 2, config register addr = 0x800, last config = 0xff Registers: XX-- 1 bytes in subtuples Tuple #7, code = 0x1b (Configuration entry), length = 15 000: c1 81 9d 71 55 2e 2e 2d fc 14 45 10 b8 ff 20 Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2.5 x 100mA Max current average over 10 ms: 2.5 x 100mA Power down supply current: 2.5 x 10mA Wait scale Speed = 1.2 x 10 us Card decodes 5 address lines, limited 8/16 Bit I/O IRQ modes: IRQs: 3 4 5 7 8 9 10 11 12 13 14 15 Max twin cards = 0 Misc attr: (Power down supported) Tuple #8, code = 0xff (Terminator), length = 0 2 slots found Mvh, Frode Nordahl On Sat, 2002-11-02 at 19:15, M. Warner Losh wrote: Does this happen with OLDCARD? I have a couple of cards that do this, but haven't been able to track down why this happens. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CNet CNWLC-811 (PRISM2), kernel panic
On Sun, 2002-11-03 at 00:16, M. Warner Losh wrote: pccardc pccard_mem # pccardc pccardmem PCCARD Memory address set to 0xd pccardc pccard_mem 0xf800 # pccardc pccardmem 0xf800 PCCARD Memory address set to 0xf800 pccardc dumpcis # pccardc pccardmem PCCARD Memory address set to 0xf800 # pccardc dumpcis Configuration data for card in slot 1 Tuple #1, code = 0x17 (Attribute memory descriptor), length = 3 000: d9 01 ff Attribute memory device information: Device number 1, type Function specific, WPS = ON Speed = 250nS, Memory block size = 2Kb, 1 units Tuple #2, code = 0x1d (Other conditions for attribute memory), length = 4 000: 01 d9 01 ff (MWAIT) Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 00 00 00 PCMCIA ID = 0x0, OEM ID = 0x0 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 39 000: 05 00 4f 45 4d 00 31 31 4d 62 70 73 20 57 69 72 010: 65 6c 65 73 73 20 4c 41 4e 20 50 43 20 43 61 72 020: 64 20 56 2d 33 00 ff Version = 5.0, Manuf = [OEM], card vers = [11Mbps Wireless LAN PC Card V-3] Tuple #6, code = 0x1a (Configuration map), length = 6 000: 01 02 00 08 03 ff Reg len = 2, config register addr = 0x800, last config = 0xff Registers: XX-- 1 bytes in subtuples Tuple #7, code = 0x1b (Configuration entry), length = 15 000: c1 81 9d 71 55 2e 2e 2d fc 14 45 10 b8 ff 20 Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 2.5 x 100mA Max current average over 10 ms: 2.5 x 100mA Power down supply current: 2.5 x 10mA Wait scale Speed = 1.2 x 10 us Card decodes 5 address lines, limited 8/16 Bit I/O IRQ modes: IRQs: 3 4 5 7 8 9 10 11 12 13 14 15 Max twin cards = 0 Misc attr: (Power down supported) Tuple #8, code = 0xff (Terminator), length = 0 2 slots found (well, where 0xf800 is the same address that NEWCARD reported it was using for ccb bridge). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
dmesg showing garbage
Hello, I have noticed for some time now that the top of dmesg after a reboot often contains garbage. The more strange thing is that it some times also contains console output from the previous shutdown sequence. Example of somewhat garbled data: %dmesg |head module /bo\^?t/kErnel/snd_via82c686.ko\^B ap 0xc06560a8. Xre|oaded elf module /boot/kerned/snd_pcm.ko at \M-0xc065615c. Preloaded elf module /boot/kernel/uplcom.ko at 0xc0656208. Preloaded elf m/dule /boot/kernel/\M-ucom\M-.ko at 0xc06562b4. Preloaded elf module /boot/kerngl/firewire.ko at 0xc065636 . Preloaded elf module!/boot/iernel/acpi.ko at 0xc0656410. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequencY 11936924410Hz CPU: Pentium III'Pentium III Xeon/Celeron (1193.69-MHz 686-class CPU) Origin = GenuineIntel Id 5 0x6b1 Stepping = 1 % Whenever I reboot to singleusermode to run installworld + mergemaster, after a reboot I get some of the console output from before the reboot in the dmesg log. Example: %dmesg |head *** Temp ./etc/mtree/BSD.usr.dist and installed have the same CVS Id, deleting Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 13 13 13 done Uptime: 43s Terminate ACPI Rebooting... % Is this a feature, or a bug? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dmesg showing garbage
On Sun, 2002-10-13 at 01:11, Juli Mallett wrote: If you reboot and the memory is not cleared, the buffer (stored at a fixed address) may still be intact, and the kernel buffering code will be smart enough to span to the end of the buffer, and append (circularly) there. This does not explain the garbled data in the normal dmesg output though. And it also happens after a power-down (shutdown -p). But, this is a laptop, with battery (and power cord plugged in). And it may keep memory alive for some obscure reason. Anyway, it could show that FreeBSD could do a better job initializing memory on bootup? -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [Call for testers] acpica-unix-20020918
Hello, It works fine here, and the battery status works now! No lid switch yet though :-/ Thanks! Mvh, Frode Nordahl On Tue, 2002-10-01 at 17:27, Mitsuru IWASAKI wrote: [forgot to announce] Please try the latest version acpica-unix-20020829, patches for FreeBSD at: http://people.freebsd.org/~iwasaki/acpi/acpica-20020815-20020918-test20020920.diff CHANGES.txt can be fould as always at: http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt I'll import this coming weekend. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)
Hey, On Sun, 2002-09-29 at 14:51, walt wrote: [snip] I wonder if it could find the very annoying crashes in the X server. -- I'm sick of hearing about how big my Beziers are! I found this on the Xpert mailinglist: http://www.xfree86.org/pipermail/xpert/2002-June/018300.html Seems like this won't get fixed until XFree86 4.3.0, but the bug seems to be in the Type1 font handler only. (a call to abort()) I have removed it from my XFree86 config now, and I'm hoping for no more Bezier crashes :) Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting thekernel over the weekend?)
On Sun, 2002-09-29 at 21:17, Eric Anholt wrote: From what I had heard on the lists it was only a thing that happened when people upgraded kernels, and that it had stopped after some date of kernel. I hadn't experienced it, so I ignored it. I don't know about that link posted, I thought that was a mozilla bug that was supposed to be fixed. It seems like the bug has been present in XFree86 all the time. But some thing has changed in CURRENT that tickles this bug. I started to experience this after I removed all ports and recompiled XFree86 with the new GCC 3.2.1. X also dies with signal 11 some times, so theres more to it than the Bezier bug. But if it is a CURRENT kernel or compiler issue, I don't understand why / how this should affect -STABLE / -RELEASE. I'll take a backup of my current X installation and do some tests and comparisons against the Aug 24 port build of XFree86. I'll have to find a sure way to reproduce the abort() and / or SIGSEGV failure first though. -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/dri/ -- Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Opera 6.1 for FreeBSD!
Hello, As some of you may know, Opera has a native FreeBSD version of Opera in the works! http://web.opera.com/download/unix/untested/intel-freebsd/248-20020923-6.1-P1/ (Beware: the shared version requires qt-3.0.4, and will not work with 3.0.5) It is of course compiled for FreeBSD 4.x and requires libc_r.so.4. The lib/compat/libc_r.so.4 in CVS does not work after recent changes to threading in CURRENT(?). (Last buildworld September 24., kernel from today) Opera fails with: Fatal error 'Thread has returned from sigreturn or longjmp' at line ? in file /usr/src/libc_r/uthread_kern.c (errno = ?) Any chance the compat library can be updated to make this work with recent CURRENT? That would _rock_ ! :) Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
acpidump: DSDT is corrupt
Hello all, ACPI works pretty well for my machine. PCI routing seems to work (Don't need PCI_ENABLE_IO_MODES anymore, cool!), S1 and S3 sleep modes work (S2 provokes this kernel message: acpi0: AcpiGetSleepTypeData failed - AE_NOT_FOUND). However I cannot get the powerbutton nor the lid switch to work. If I try to run acpidump it prints out some information and then says DSDT is corrupt. Is this because of the errors in the DSDT itself, or is it something else? I have extracted the DSDT using Linux (cat /proc/acpi/dsdt dsdt), and I do not know how to disassemble it, so I have included the binary file in this mail. (I found some link about it on intel's homepages, but the link to a disassembler on Phoenix's homepages was dead) I have a Compal N30N3 computer with VIA PN133 chipset and Phoenix BIOS. Mvh, Frode dsdt.gz Description: GNU Zip compressed data
Re: Call for testers: acpica-unix-20020815
Hello, I applied the patch, and nothing changed, so it works :) What tools do you use to check battery state? Any links on userland tools for monitoring / controling the ACPI (other than acpiconf) ? On my laptop, power switch, lid switch and stuff like that show up under boot-up, but they do not work. Is there a default behaviour, or do I need a userland tool to configure what should happen? (VIA PN133 chipset) I also see CPU throttling show up on boot-up (a total of 16 steps, wow). When I unplug the power, system profile changes from power to economy. Is it possible to do any more fine-grained control of this? Anyone know what the status is on the disk spindown patch (ATA)? I saw some references to a old patch for this somewhere, and that Søren had some things he could commit, when he got the time :) My desktop computer automaticly shuts down whenever I hit the power button, so I guess it works there, but not on my laptop :( Is there a updated homepage for the ACPI project somewhere? I think the ACPI implementation for FreeBSD rocks, but it has a long way to go before it's perfect. So I would love to help out. Mvh, Frode On Thu, 2002-08-22 at 16:51, Mitsuru IWASAKI wrote: I'm going to import Intel acpica-unix-20020815 sometime early next week. Please test new version of acpica and give feedback before my importing. Major fix in this version is Ref/Deref operators bug fix. Personally I'm very happy with the new version because now my laptop (FIVA 206VL) reports correct battery info. :-) The full change log: http://developer.intel.com/technology/iapc/acpi/downloads/CHANGES.txt The patches against CURRENT sys tree are available at: http://people.freebsd.org/~iwasaki/acpi/acpica-20020725-20020815-test20020822.diff Please note that any feedback should be sent to [EMAIL PROTECTED] Enjoy! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
When will PCI_ENABLE_IO_MODES be default?
Hello, It seems like PCI_ENABLE_IO_MODES makes FreeBSD work on a lot of portable computers and possible newer desktop computers with lazy BIOS'es. As it is now, it is quite a hassle to complete something as simple as a network install of FreeBSD on an affected computer. My question is, when will PCI_ENABLE_IO_MODES be default? I know it will be by 5.0-RELEASE (hope?), but it would be nice to have it in there soon so people could install SNAPSHOT releases directly, or maby as a seperate disk-image if it makes some kind of trouble for other configurations. Having this in 5.0-DP2 would be nice ;) -- Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mozilla and gnome apps won't run after KSE [June 29]
Hello, I see no problems with neither GNOME nor Mozilla. Kernel compiled about an hour ago (15:30:13 CEST / GMT+2). Userland last compiled on June 27. On Sun, 2002-06-30 at 10:29, Julian Elischer wrote: Ithink these may be threaded it's possible the are using signals and they may be broken On Fri, 28 Jun 2002, walt wrote: Following make world make kernel after the KSE update I find that mozilla and any gnome app will suck up 98% of the CPU and will never actually write anything to the display. No crashes, no error messages, they just chew up cycles. I don't have KDE installed on my -current machine, so I can't comment on it, but most other basic X apps seem to work fine--like xterm, xvidtune, the X interface to emacs and the X interface for cvsup all work OK. Any one else seeing this? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Wake on PCI enabled by FreeBSD?
Hello, I was a bit stalked this morning by finding that my computer had tunrned itself on 5-10 minutes after I turned it off to go to bed last night :) I turned off, and it turned itself back on again. I have turned off most wake up events in the BIOS, but Wake on PCI is set to AUTO, meaning that the operating system decides wether this should be enabled or not. I have both a ISDN card (Asuscom 128 PCI, iwic driver) and a Ethernet card (3COM 590, xl driver) that could be triggered to wake up the computer. But this has never happened before, so I guess some changes (ACPI?) has caused FreeBSD to enable this feature. Anyone know anything about this? I'm running an HP Vei8, PII 400 MHz box and FreeBSD-CURRENT built one or two days ago. Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
/usr/bin/cut
Hello, The changes done to /usr/bin/cut recently seems to have broken it. I have fetched and built CURRENT from scratch this morning. cut compiles and runs, but it does not cut :) Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /usr/bin/cut
Hi again, I have included some examples below. cut.broken was compiled this morning, i got the replacement cut from the 5.0-DP1 release. Tim J. Robbins said: On Sun, May 26, 2002 at 01:26:25PM +0200, Frode Nordahl wrote: cut compiles and runs, but it does not cut :) Please give me an example of how you are invoking cut and why the output you get is incorrect or different from -STABLE. * %cat test.txt abc abc abc %cat test.txt | /usr/bin/cut.broken -c2- abc abc abc %cat test.txt | /usr/bin/cut -c2- bc bc bc * Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
calcru: negative time of XXX
Hey, I've had the microuptime problem some time, and I have somewhat followed the discussion about this on -current. It seems like the patch committed removed the messages, but they are now replaced by messages like: Feb 24 17:28:26 gandalf kernel: calcru: negative time of -680109 usec for pid 92704 (sed) Feb 25 10:25:05 gandalf kernel: calcru: negative time of -487 usec for pid 59222 (rm) Feb 25 19:42:23 gandalf kernel: calcru: negative time of -680904 usec for pid 48076 (sed) Feb 26 00:26:45 gandalf kernel: calcru: negative time of -666072 usec for pid 438 (gmake) Also, I have seen strange things reported by PS. Crond had negative CPU usage time. I am also unable to compile libgtop at the moment, (which makes it impossible to compile the GNOME port w/o changes). proctime.c: In function `calcru': proctime.c:88: aggregate value used where an integer was expected proctime.c:69: warning: unused variable `tv' proctime.c: In function `glibtop_get_proc_time_p': proctime.c:130: warning: unused variable `pstats' proctime.c:128: warning: unused variable `u_addr' proctime.c: At top level: proctime.c:62: warning: `calcru' defined but not used gmake[3]: *** [proctime.lo] Error 1 # uname -a FreeBSD gandalf.xu.nordahl.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 24 15:58:24 CET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Last make world: Feb 24 20:00 Cheers! Regds, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: calcru: negative time of XXX
on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x1 0x1 0x1 0x1 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0 failed to probe at port 0x300-0x30f irq 10 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff vt0 failed to probe on isa0 ep0: 3Com 3C509-Combo EtherLink III at port 0x210-0x21f irq 10 on isa0 ep0: Ethernet address 00:20:af:e8:55:57 bpf: ep0 attached isa_probe_children: probing PnP devices BIOS Geometries: 0:03feef3f 0..1022=1023 cylinders, 0..239=240 heads, 1..63=63 sectors 1:0209fe3f 0..521=522 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. procfs registered bpf: lo0 attached bpf: ppp0 attached acpi_cpu0: set speed to 100.0% acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% ad0: success setting UDMA2 on Intel chip Creating DISK ad0 ad0: IBM-DTTA-371440/T71OA73A ATA-4 disk at ata0-master ad0: 13783MB (28229040 sectors), 28005 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad2: success setting UDMA2 on Intel chip Creating DISK ad2 ad2: Maxtor 90430D2/GAS64812 ATA-4 disk at ata1-master ad2: 4104MB (8405775 sectors), 8895 C, 15 H, 63 S, 512 B ad2: 16 secs/int, 1 depth queue, UDMA33 ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 ata1-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-slave: success setting PIO4 on generic chip acd0: CD-ROM CDU601-25/1.0p CDROM drive at ata1 as slave acd0: read 1723KB/s (57255KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Writes: acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: CD-ROM 120mm data disc Mounting root from ufs:/dev/ad0s2a ad0s1: type 0x7, start 63, end = 8436959, size 8436897 : OK ad0s2: type 0xa5, start 8436960, end = 28229039, size 19792080 : OK start_init: trying /sbin/init ad2s1: type 0xc, start 63, end = 8401994, size 8401932 : OK Rgds, Frode Nordahl In message [EMAIL PROTECTED], Frode Nordahl writ es: Hey, I've had the microuptime problem some time, and I have somewhat followed the discussion about this on -current. It seems like the patch committed removed the messages, but they are now replaced by messages like: Feb 24 17:28:26 gandalf kernel: calcru: negative time of -680109 usec for pid 92704 (sed) Feb 25 10:25:05 gandalf kernel: calcru: negative time of -487 usec for pid 59222 (rm) Feb 25 19:42:23 gandalf kernel: calcru: negative time of -680904 usec for pid 48076 (sed) Feb 26 00:26:45 gandalf kernel: calcru: negative time of -666072 usec for pid 438 (gmake) Also, I have seen strange things reported by PS. Crond had negative CPU usage time. I am also unable to compile libgtop at the moment, (which makes it impossible to compile the GNOME port w/o changes). proctime.c: In function `calcru': proctime.c:88: aggregate value used where an integer was expected proctime.c:69: warning: unused variable `tv' proctime.c: In function `glibtop_get_proc_time_p': proctime.c:130: warning: unused variable `pstats' proctime.c:128: warning: unused variable `u_addr' proctime.c: At top level: proctime.c:62: warning: `calcru' defined but not used gmake[3]: *** [proctime.lo] Error 1 # uname -a FreeBSD gandalf.xu.nordahl.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 24 15:58:24 CET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Last make world: Feb 24 20:00 Cheers! Regds, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send
Re: lnc0: broke for us between 3.1 and 4.0?
p...@originative.co.uk writes: From: Richard Tobin [mailto:rich...@cogsci.ed.ac.uk] Is this fix going into stable? (I'm a little surprised that such a change was considered appropriate for the stable branch in the first place.) I didn't think the memory allocation change was in stable but I may merge the lnc changes back into -stable anyway since it's a cleaner way of doing things. I've got some other lnc problems to fix first though. Will this take very long? Because my stable source tree has not produced a working kernel for me for several weeks because of this. And does this all mean that if I want my kernel source tree to be consistent more often than not (and any errors be fixed as soon as possible), I'd be better off switching from -stable to -current? -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
MTRR registers
Is there a way in -current to manipulate the MTRR registers of recent intel processors? I really want to make my framebuffer write-combined. -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
