similar to: ext3 and kernel 2.4.9-31

Hi. There's a rescue cd at ftp://ftp.pld.org.pl/people/areq/RescueCD/ that uses isolinux that don't work in my configuration. All I get is: --8<-- ISOLINUX 1.75 2002-06-14 isolinux: loading spec packet failed, trying to wing it... isolinux: extremly broken bios detected, last ditch attempt with drive=9F isolinux: disk error 80, ax=432E, drive 9F --8<-- My configuration is: VP_IDE:

I installed Asterisk 1.0.9 in a Freebsd 5.4 ( with no zaptel card); I have 2 zoom x5v and works great ( in extensions 123 and 321 ) but I was trying to test cmd Playback, MusicOnHold, MP3Player but when I call to extension 100 I don't hear the sound ( mp3 or gsm that I put) , I only hear noise If I leave a message in a mailbox the same, all the record is noise --------- extensionns.conf

Just wondering if anybody managed to get SMP kernel to boot properly on an old Asus CUV4X-DLS motherboard (older dual P-III)? I had this problem only with this specific motherboard and 2.6 kernels. First time couple of years ago. And again today (I've just installed CentOS4 on a box that used to run RH7.3). Previously those machines were running Red Hat 7.3 (2.4 kernels), and with 2.4

Hello List, I have a problem with an Onborad scsci, that won't boot a isolinux-cd: anyone got a clue? Mainboard is ASUS-CUV4X-DLS with onboard LSI 35c1010-33 Controller. Board-Bios is Award Medaillion 6.0 and Controller Bios is Symbios SDMS v4.0 (4.18.02) The CDRW device to boot from is a Yamaha CRW2100S Rev1.0H I tried Isolinux 1.63 and 1.66 with similar "success": here's

I have a 2 way machine. Soliciting folks opinion on whether it makes sense to smp enable DOM0 so that IO handling can be balanced over both CPU''s... Opinions? Thanks, Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I'm trying to get stable booted on a little ITX board off of a CF card, but it hangs as it's trying to run init. Here's what the boot looks like. SMAP type=01 base=0000000000000000 len=000000000009fc00 SMAP type=01 base=000000000009fc00 len=0000000000000400 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000ffff0000 len=0000000000010000 SMAP type=01

My new PC has an internal 16-in-1 card reader connected via USB 2.0. The device is the Techsolo TCR-1640 (http://www.techsolo.de/product/cardreader/tcr_1640/index.php). I boot from a compact flash inserted in it and I can mount and unmount the same CF once the system has booted and has mounted the root partition from my graid3 array. The problem arise when I replace the inserted CF with another

On Monday 14 March 2005 06:29 pm, Mark Williamson wrote: > > I don''t know if this is the right place to post, but I can''t find any > > info about my problem on the net. > > Yes, this is the right place. > > > title Xen2610 > > kernel /boot/xen.gz dom0_mem=131072 console=vga > > module /boot/vmlinuz-2.6.10-xen0 root=/dev/hde1 ro console=tty0

̨Íåºê´ó¹ú¼ÊÉÌó¹«Ë¾³ÏÑ°¹óµØºÏ×÷»ï°é£¬ÏúÊÛµçÄÔ¡¢Åä¼þ¡¢ÊÖ»ú¡¢±Ê¼Ç±¾µçÄÔ¡££¨²Î¿¼¼Û¸ñ±íÈçÏ£© ÎÒ˾±£Ö¤²úƷΪȫÐÂÔ­×°,»õµ½¸¶¿î¡£Óв»Ïê¿ÉÀ´ÈËÀ´µç×Éѯ£º ÁªÏµÈË:³ÂÊÀ½Ü µç»°:013850704389 Ò»¡¢Ä¦ÍÐÂÞÀ­ µ¥Î»/Ôª T189--400 T190--350 T191--500 C289--550 T2988--350 A388--1600 A6288--1300 V70--2000 V8088--800 V998++ --700 V60+ --1200 V66+GPRS--950 ŵ»ùÑÇ 3310--400 3330--450

Does anyone know if there's a patch out there for 2.4.9-ac10? I'm investigating what's involved to go from ext2 to 3. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20060816/cf899f58/attachment.htm>

I have an ext3 filesystem that I want to mount without loading the journal. I tried the "noload" option with both 2.4.9 and 2.4.18 series kernels and get the errors listed below. [root@host]# mount -t ext3 -o noload /dev/sdf1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdf1, or too many mounted file systems /var/log/messages: Apr 18 13:30:23 host kernel: ext3:

It's already mounted rw somewhere else. This enables the needs_recovery feature which prevents an ext2 mount. -Leslie -----Original Message----- From: Christopher J. PeBenito [mailto:pebenito@ieee.org] Sent: Tuesday, April 22, 2003 11:30 AM To: kuczynski, leslie Cc: 'ext3-users@redhat.com' Subject: Re: ext3 "noload" option to mount returning error in 2.4.9 & 2.4.18 s

I have an ext3 filesystem that I want to mount without loading the journal. I tried the "noload" option with both 2.4.9 and 2.4.18 series kernels and get the errors listed below. [root@host]# mount -t ext3 -o noload /dev/sdf1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdf1, or too many mounted file systems /var/log/messages: Apr 18 13:30:23 host kernel: ext3:

Is there a patch for 2.4.9 out there. I saw the ac one on http://www.uow.edu.au/~andrewm/linux/ext3/ but cant fond one for the main branch Regards Robert Stanford

Hello, I am going to set up a new file server ("smb" and "nfs") machine for the local network of my former school. Therefore I've just downloaded and successfully compiled "linux-2.4.9-ac5" (including "disk quota support" and, of course, support for "ext3 file system"). I've read the statement: | ... | | The quota code in the -ac

Hey all. I was wondering if an official patch vs 2.4.9 is in the works yet. I managed to apply it locally, but there was one or two changes that didn't apply cleanly. (mm/vmscan.c has had some stuffs moved around). I think I did it right, but an official patch is always nice. :) -- Tom Rini (TR1265) http://gate.crashing.org/~trini/

Hello, where do you had downloaded the ocfs-2.4.9-e-1.0.9-8.src.rpm -Package and where can I find a working combination of fw-kernel and ocfs? We are testing under SLES8 and had linux-2.4.20rc2-orafw Kernel downloaded from otn and try to compile the ocfs-sourcen also downloaded from otn. Problem is, that Suse SLES8 works with kernel 2.4.19, so we can't recompile the ocfs-sourcen for kernel

Hi all, I had a very simple samba-2.2.3a installation running. Not as domain master or such. Now after upgrading to 2.4.9-31 kernel, I am unable to start nmbd. smbd starts okay. Does anyone know of any selection in the config for a newly compiled kernel that could prevent nmbd from running? Is there a confict with this kernel downloaded from ftp.redhat.com? TIA Bob -- Bob

Hello, I just went back to 2.4.9-ac18 from 2.4.10 (i386), and then for the first time migrated all my ext2 partitions to ext3. I did this over a series of reboots, as I confirmed that indeed things continued to work. The last step I took was to convert /. I have set up /etc/fstab to mount my 'ext3' partitions with 'auto', I suppose thinking this will make it easier to roll

This is another take on logging for sftp-server. Given the number of private email requests I've received for this patch, I assume there is signifigant enough interest to request it be reviewed for inclusion into the release. The patch is against 3.1p1, and is completely disabled by default. To enable logging, one must use compile time directives (-DSFTP_LOGGING). This was done due to prior