Re: Unable to mount ext2fs partition
Hi, I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes or the mount is uncleanly shut down. Then I have to use a linux livecd to repair the partition as the freebsd e2fsck often isn't able to clean up the mess. Regards, Paul Rahul Siddharthan wrote: I decided to bump my laptop up to 5.0-CURRENT today. All seems to have gone well and all my old binaries work fine, it looks very nice. However, I can no longer mount my linux partition: when I try, I get # mount -t ext2fs /dev/ad0s2 /mnt ext2fs: /dev/ad0s2: No such file or directory Did something change when I install new bootblocks, and how do I fix it? Below, output from fdisk and disklabel. I don't remember anything unusual before the upgrade. Thanks, Rahul --- # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 13912227 (6793 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 865/ head 254/ sector 63 The data for partition 2 is: sysid 131 (0x83),(Linux native) start 13912290, size 5719140 (2792 Meg), flag 0 beg: cyl 866/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: The data for partition 4 is: # disklabel -r /dev/ad0s2 # /dev/ad0s2: type: ESDI disk: ad0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 356 sectors/unit: 5719140 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 5719140 13912290unused0 0 # (Cyl. 866 - 1221) e: 5719140 139122904.2BSD 1024 819216 # (Cyl. 866 - 1221) partition c: offset past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities partition e: offset past end of unit partition e: partition extends past end of unit 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: Unable to mount ext2fs partition
Hi Poul-Henning, I does printf, but it doesn't initiate the e2fsck. Using the ports e2fsck has not shown itself to be the way to do restore order. (I get "et hav" of ata unaligned access errors and lots of other garbage.) It's easier to boot up a Gentoo LiveCD and "do it right".) Thanks, Paul [EMAIL PROTECTED] wrote: In message <[EMAIL PROTECTED]>, "Paul A. Mayer" writes: Hi, I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes or the mount is uncleanly shut down. Then I have to use a linux livecd to repair the partition as the freebsd e2fsck often isn't able to clean up the mess. The kernel should probably printf a warning about this if it rejects the mount because the filesystem is dirty. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to mount ext2fs partition
Hi Bruce, Thanks for this info. It's way beyond my technical understanding (which is truely minimal!), but I think I get the idea. What would this look like as a series of commands? Or better yet, what's the "right" way to share data between FreeBSD -current/coming and linux in a dual boot situation? ... Which is the real objective, (not playing with e2fs! ;.-) /Paul Bruce Evans wrote: On Sun, 5 Jan 2003, Paul A. Mayer wrote: I does printf, but it doesn't initiate the e2fsck. Using the ports It prints essentially the same mount failure message as ufs. e2fsck has not shown itself to be the way to do restore order. (I get "et hav" of ata unaligned access errors and lots of other garbage.) It always worked for me until block devices were axed. Apparently it still depends on random accesses to non-block boundaries and sizes working. It's easier to boot up a Gentoo LiveCD and "do it right".) Or upgrade to FreeBSD-3 to get unaxed block devices :->. The ext2fs utilites work on regular files (better than ffs ones), so they can be used (very slowly and with muttering about axes) directly under FreeBSD by copying partitions to regular files, fixing them there, and copying them back. This is least painful for mke2fs since you can start with a sparse file instead of a copy of a partition. [Context lost to top posting] Bruce 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: Unable to mount ext2fs partition
Hi Rahul, The mount capability has to be included as a kernel option in a custom build kernel. I forget exactly what it's called (I'm writing in another OS on the system, so I can't check it right now), but I think it's something like this: option EXT2FS Have you included that in your kernel build? /Paul Rahul Siddharthan wrote: Paul A. Mayer wrote: I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. Hm, didn't know about this port.. but it still doesn't include a mount program, and I still can't mount the partition even after installing the port. I don't want to fsck it and risk screwing it up: it's a "real" linux system (ie, a dual-boot machine) and the linux continues to boot perfectly nicely. But here's what I get with an e2fsck -n : # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes Not a problem for me (it's likely to be mounted read-only anyway, and I can always boot into linux to fix it if it's dirty) - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound playback problem with Maestro3.c (?) -- clock issue
Hi Michael, Regarding your linux clock issue: There was a rather lively discussion at forums.gentoo.org about drastic clock sync loss caused by KDE. I don't know if it has been resolved in the 3.1 line, but if you were running linux KDE, you might take a look at that as a cause for the linux clock sync problem. /Paul Michael Ferguson wrote: Hi all, On a probably-unrelated side note, when I was running Linux on the same laptop (ducks), I had issues with the OS clock getting quickly out of sync with the HW clock; typically I would loose five minutes or more every hour. Although I haven't experienced the same thing with FreeBSD, I wonder if there is just something odd about interrupt handling or timing on the Inspiron 8000 line? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3 ACPI failure on locally compiled kernel
Hi folks, I was so delighted to see that the shipping (iso) version RC3 didn't crash immediately in ACPI thermal on my i845 based laptop! (I reported this after installing RC1 in December and it reoccured with RC2.) The problem comes back though if I compile a kernel myself after CVSUP'ing yesterday morning 2003-01-15 10.00 UTC. My configuration file is essentially GENERIC, make.conf is vanilla. Barring wiping out the machine with a clean install, (my installation was an upgrade), are there any suggestions about where I might look for critical differences that cause my compiles to generate faulty kernels/modules? (I've been following the procedure outlined for upgrading in /usr/src/Makefile .) Thanks, Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Error Mounting /dev/acd0 on /dist: during sysinstall of 5.0-RELEASE
Hi, I have a similar problem, i.e., a clean installation process for 5.0-RELEASE produces the error: "Error Mounting /dev/acd0 on dist: Operation not supported by device (19)" (I wound up doing a minimal ftp install and then did a binary upgrade with the CD as the distribution medium.) Nate suggests: >>Does setting hw.ata.atapi_dma=1 help? How would you do this in the clean installation scenario. Is there a way to pass this setting to the kernel during the boot process, or modify the running environment by some other means before sysinstall takes over? Regards, /Paul Thomas T. Veldhouse wrote: I am trying to install from the CD-ROM, so I don't really have the option unless I do it from the boot loader. I can say that it is not set for the installed system (which I installed via FTP) and yet, I can mount a CD just fine. It is just a problem from within sysinstall. Below are the results of dmesg on my system after I installed from an FTP server. Copyright (c) 1992-2003 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-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0673000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06730a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 600024637 Hz CPU: AMD-K7(tm) Processor (600.02-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ff AMD Features=0xc040 real memory = 402571264 (383 MB) avail memory = 384110592 (366 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 8 entries at 0xc00f15e0 ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 5 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uscanner0: Visioneer Visioneer 6100 USB Scanner, rev 1.00/0.00, addr 2 uhci1: port 0xb000-0xb01f irq 5 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 11.0 (no driver attached) pci0: at device 11.1 (no driver attached) fxp0: port 0x8800-0x883f mem 0xd600-0xd60f,0xd680-0xd6800fff irq 5 at device 13.0 on pci0 fxp0: Ethernet address 00:03:47:97:f6:b8 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_REGION_LIMIT psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: at iomem 0xc-0xcbfff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.
Re: Synaptics touchpad support
Hi Rahul, Well, it compiles on 5.0-Release-p1. The psm initialization gives some specs about the device and some of it's features. ... but I don't see any consequences of this in apps, like mozilla. And under gnome the pressure sensitivity of the touchpad (e.g., tap to click) is now gone. I have no great understanding of how any of this should work. Can you give some pointers. (How do I get touch sensitivity back? How should it be configured into X? Where should I be able to see the effects of the patch?) Thanks! /Paul Rahul Siddharthan wrote: Lest this disappear, like so much else, into the black hole that is GNATS, can some laptop user take a look at this? It works great for me, I can now scroll using the "up" and "down" touchpad buttons which were useless decorations earlier. Thanks to Marcin Dalecki. PR kern/48116 http://www.freebsd.org/cgi/query-pr.cgi?pr=48116 - Rahul 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: Synaptics touchpad support
Hi, Terry Lambert wrote: "Paul A. Mayer" wrote: You actually lose the tap/tap-tap click and doubleclick button emulation with the new driver, and, as you note, the pressure sensitivity. Both of these issues were noted when the driver was posted for review. It semed the consensus at the time that until at least the tap/tap-tap was brought back (via software emulation), the driver would not be replaced, only optioned. You can check the list archives for details, I think. I wasn't aware of the prehistory ... (Rahul's link in another post was very interesting.) The "pressure sensitivity is, I think, really an area sensitivity and not a real pressure sensitivity (I can't imagine actually losing an axis of data!). That would mean, like the tap/tap-tap, it could be emulated in software. It would be interesting to get this back. I can (and have) lived without the "roller" buttons, but I wasn't aware of how used I had become to tapping instead of clicking. Probably the best thing to do would be to disassemble the BIOS on your box, knowing the difference between the older driver's interface, and use the same techniques that were hidden from the older driver (and "just built in" instead). This is certainly beyond my technical understanding! /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Synaptics touchpad support
Hi, Rahul Siddharthan wrote: Paul A. Mayer said on Feb 10, 2003 at 11:01:45: Hi Rahul, Well, it compiles on 5.0-Release-p1. The psm initialization gives some specs about the device and some of it's features. ... but I don't see any consequences of this in apps, like mozilla. And under gnome the pressure sensitivity of the touchpad (e.g., tap to click) is now gone. Yes, this was noted back then. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2003/freebsd-hackers/20030112.freebsd-hackers I have no great understanding of how any of this should work. Can you give some pointers. (How do I get touch sensitivity back? How should it be configured into X? Where should I be able to see the effects of the patch?) Well, without doing anything, you should be able to see some activity from the "up" button: in my case, it worked by default as a middle button, while the "down" button did nothing but showed up in xev, for example. Basically, left=1, up=2 right=3 ,down=4. What I really wanted was for "up" to mean up, "down" to mean down, and I was happy to emulate "middle" with simultaneous left-right as before. The following does it for me: I run moused with the options -m 5=4 -m 4=2 -a 0.5 (the -a is because this driver scales the speed up a bit too much for my liking). And in my XF86Config I have Option "Emulate3Buttons" Option "Buttons" "5" I *don't* have the Option "ZAxisMapping "4 5" which the howto's for wheel mice will tell you to insert -- seems it's there by default. And if I insert it, curiously, it stops working... This was very helpful and works as you describe. Thank you very much! /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 3.2.2 import -- questions
Hmmm, fails to build for me: FreeBSD asus 5.0-RELEASE-p1 FreeBSD 5.0-RELEASE-p1 #3: Mon Feb 10 10:39:34 CET 2003 root@asus:/usr/obj/usr/src/sys/ASUS i386 gmake[3]: Entering directory `/usr/ports/lang/gcc32/work/build/gcc' for d in libgcc; do \ if [ -d $d ]; then true; else /bin/sh .././..//gcc-3.2.2/gcc/mkinstalldirs $d; fi; \ done if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi gmake[3]: Leaving directory `/usr/ports/lang/gcc32/work/build/gcc' gmake[2]: Leaving directory `/usr/ports/lang/gcc32/work/build/gcc' gmake[1]: *** [configure-target-libstdc++-v3] Illegal instruction (core dumped) gmake[1]: Leaving directory `/usr/ports/lang/gcc32/work/build' gmake: *** [bootstrap] Error 2 *** Error code 2 Stop in /usr/ports/lang/gcc32. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade97111.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! lang/gcc32(missing header) Any ideas? /Paul Wesley Morgan wrote: The import of gcc 3.2.2 brings a question to mind... Many people have mentioned problems with SSE / SSE2 instructions, optimizer problems etc that are supposedly fixed with 3.2.2... My question is, should I consider rebuilding my ports with this new compiler because of stability and/or speed improvements? Or is this point release not worth the effort. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
devastating 5.0R crash
H. I think that my 5.0R installation has self destructed. Background: * 60GB toshiba disk with two active OS partitions (win2k, freebsd) booted with ranish * Freebsd partition has 4 slices, swap (ca. 2GB), root (250MB), var (250MB), usr (ca. 6GB), other msdosfs partitions are occassionally mounted. * Kernel is 5.0 release p1, updated about 3-4 days ago (don't recall exactly but I did notice some updates to ffs.) Loads ko's for acpi, radeon, linux, sound support, and one or two other things I don't recall right now. * Hardware is Asus L3800, (i845-based p4 mobile w/ 1GB RAM). Has otherwise run great with 5.0R (there were acpi problems with RC* version, which have disappeared). The machine is new; it has about 8 weeks of running time. * Running configuration is strictly desktop. Not serving anything, not developing anything, not running a db app or similar. * After a normal shutdown in the evening, the machine rebooted normally in the morning. I logged on to my user account and start X (running gnome2). I checked mail in moz 1.2.1. I go to open phoenix and nothing happens. I was called away to look at something. When I return to my machine it's in the process of rebooting. It has hard reset itself for some reason and is stumbling through the tail end of the boot up sequence and goes into lock, clearly not able to read some thing in /etc like ttys (gives a blank shell type prompt, where I have my console set to secure.) Status: I'm presently running fsck_ffs from a live cd. It fsck'ed / with some complaints about an unreadable sector. It's now on /var and reporting vast, vast numbers of sectors as unreadable, with "UNEXPECTED SOFT UPDATE INCONSISTENCY". I've not visited /usr yet. I hope my disk (with less than 800 hours of service) hasn't been somehow physically borked. (The windows partition boots and runs seemingly fine.) Any ideas? Any guesses about what caused a hard reset (loading phoenix)? How to gaurd against this in the future? (Besides don't run 5.0R! ;-) ... I'm just hoping to be able to get /usr/home/(user) off, I'm assume the installation is utterly trashed.) /Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: devastating 5.0R crash
There were some ATA complaints, (don't recall exactly what though it was clear that there were read errors), when attempting to boot the system off the HD. I don't recall "medium error" there, and have not seen it in fsck_ffs booted from the live cd. The sector numbers I'm seeing seem to be in short sequences or in proximity, but spread in various groups with in the partitions. The /var fsck has resulted in clearing to the last phase pass, where it repeatedly asks for fsck to be rerun. I'm on /usr now. /Paul David Schultz wrote: Thus spake Paul A. Mayer <[EMAIL PROTECTED]>: I'm presently running fsck_ffs from a live cd. It fsck'ed / with some complaints about an unreadable sector. It's now on /var and reporting vast, vast numbers of sectors as unreadable, with "UNEXPECTED SOFT UPDATE INCONSISTENCY". I've not visited /usr yet. I hope my disk (with less than 800 hours of service) hasn't been somehow physically borked. (The windows partition boots and runs seemingly fine.) If many (say, more than a track's worth) of sectors are unreadable (e.g. you get a ``medium error''), your hard disk is probably failing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI kernel panic with 5.0-RC1
Greetings, Congratulations on RC1! I've found an issue! :-) I just upgraded my ASUS LC3800 portable to 5.0-RC1 from 5.0-DP2. The new kernel panics shortly after booting up and drops into the debugger. The messages look something like this: Fatal trap 12 Page fault in kernel mode fault virtual address 0x42 page not present process acpi_thermal Stopped at: vm_object_pip_add+0x37: movzwl 0x42(%esi),%eax This happens after the kernel is loaded and within approximately 15-30 seconds after the login prompt is shown. The machine is based on the i845MP chipset and is running a 2Ghz mobile P4. I'd be happy to provide more debugging info and work on patch testing, just tell me what needs to be known or done. Please mail my personal address as well as the list, as I've not been accepted for the list. Best regards, Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
