similar to: Ext3 fatal errors with Promise RAID

> Did you ever find out what was wrong? Nope, and personally I think there's a bug in 2.4.19. Since I sent the email below I did a make oldconfig and went thru the new options very carefully - no luck. I'm still running on 2.4.18, and I can compile a kernel, install, and it works fine. Randy Barton Hodges wrote: > Hi Randy > > Please pardon the intrusion, but I found your

What is really puzzling me is that the ataraid device (/dev/ataraid/d0p1 mounted as /bigdisk) 2x 123GB IBM Deskstar's is formated as ext2...top and ps etc... show a fight between kjournald and kupdated and all searches for kjournald or kupdated fights suggest ext3 issues... :-) It's a RedHat 7.2, 2.4.7-10 custom kernal (I added in the Promise FastTrak support and HIGH mem support to

Hi! Here is my isolinux.cfg. It's slackware based. ====================== default Kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=8192 rw root=/dev/ram ZILIX_KERNEL=bare.i prompt 1 timeout 1200 font lat1-16.psfu display mensagem.msg F1 mensagem.msg F2 opcoes.msg F3 help.msg label linux kernel Kernels/bare.i/bzImage append - label adaptec.s kernel

Hi, folks, Fully updated 7.2 system. I installed the correct proprietary NVidia driver (the user's expensive proprietary visualization software won't run with nouveau), I've put nouveau.modeset=0 rd.driver.blacklist=nouveau on the kernel line for grub2, and even yum removed the nouveau driver and built a new initrd... which won't boot, it seems to start and than does nothing,

Hi. I'm trying nouveau and I'm having some troubles. I filled a bug[1] a while ago about a problem I had (and I'm still experimenting), but I found another issue that I suspect is normal. I get this in my Xorg.log: [...] (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE drmOpenDevice: node name is

My system is RH7.2 with custom 2.4.18 or 2.4.19 kernel(s), downloaded from kernel.org. My root filesystem is ext3 on ataraid. I'm using initrd. My system comes up fine with 2.4.18 kernel, but when trying to boot a new 2.4.19 kernel I get the following sequence:

Hello, I'm trying to fix netbooting and I got quit far. Before this, it reported that it had no root disk, I fixed this by specifying my initrd. Nou it crys's: Kernel panic: I have no root and I want to scream I think I made the mistake whit the creation of the initrd file. What should I put in it except the /linuxrc. I put a echo "TEST" in de /linuxrc to see if it runs, in

I "wish" to not load the or even install the nouveau driver by default. I want to use the NVIDIA binary driver. I have tried a number of things: 1) in my kickstart package section add the line: -xorg-x11-drv-nouveau This did not work - it was still installed. 2) use the nvidia installer and it asks to create a modprobe.conf file to blacklist the driver. I said yes thats what I want.

On Sun, 2013-08-11 at 08:17 +0200, Maarten Lankhorst wrote: > > So I'm still a bit confused :-) > > > The fun has been doubled because TTM expects PAGE units, so some of > the PAGE_SHIFT's are > genuine. Some may be a result of PAGE_SHIFT == 12, so honestly I don't > know the specific ones. Right, and the other way around too :-) I think I found at least two

This patch creates special group attributes for special attrs like "*auto_point*". We check if we need them, and if we do, we set them up in special_groups structure, that then we pass to hwmon_device_register_with_info. --- linux/drivers/gpu/drm/nouveau/nouveau_hwmon.c.orig 2017-04-13 10:13:26.331391326 +0200 +++ linux/drivers/gpu/drm/nouveau/nouveau_hwmon.c 2017-04-13

On Mon, 29 Feb 2016, m.roth at 5-cent.us wrote: > Hi, folks, > > Fully updated 7.2 system. I installed the correct proprietary NVidia > driver (the user's expensive proprietary visualization software won't > run with nouveau), I've put nouveau.modeset=0 > rd.driver.blacklist=nouveau on the kernel line for grub2, and even yum > removed the nouveau driver and

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of John Hodrien > Sent: den 29 februari 2016 17:55 > To: CentOS mailing list > Subject: Re: [CentOS] CentOS 7.2, nouveau won't go away > > > Fully updated 7.2 system. I installed the correct proprietary NVidia > > driver (the user's

John Hodrien wrote: > On Mon, 29 Feb 2016, m.roth at 5-cent.us wrote: >> >> Fully updated 7.2 system. I installed the correct proprietary NVidia >> driver (the user's expensive proprietary visualization software won't >> run with nouveau), I've put nouveau.modeset=0 >> rd.driver.blacklist=nouveau on the kernel line for grub2, and even yum >>

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady

Hello, In some weeks I'm going to reinstall some old RedHat9 based servers with Promise FastTrak TX2000 "semi-hardware" RAID1 controllers. I just tried to install CentOS 4.0 on a computer with a spare card and as usual both HDD attached to the RAID1 controller are seen separately by the installer because the specific driver for the TX2000 wasn't loaded. Nothing new here, it

Just wondering if someone could help me debug this: I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes

Hello, I've met some quite strange reboots recently on my home gateway. I'm trying to reduce its power consumption, so I've loaded the cpufreq(4) driver, and enabled powerd. After this the box started to reboot randomly all over the place. I started to think what can cause the trouble, removing the cpufreq(4) support would be too trivial, so I've removed the ALTQ references from

It doen't seem to be anyting seriuos but I get this when crosscompiling not otherwise. <p><p> from ../../src/bitstream/bitstream.c:57: ../../src/bitstream/../portab.h:61: warning: `ARCH_IS_32BIT' redefined *Initialization*:1: warning: this is the location of the previous definition <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg

https://bugs.freedesktop.org/show_bug.cgi?id=77690 Priority: medium Bug ID: 77690 Assignee: nouveau at lists.freedesktop.org Summary: [nv49] Hearthstone corrupted display screen with wine Severity: normal Classification: Unclassified OS: Linux (All) Reporter: infyquest at gmail.com Hardware: x86 (IA32)

Hello CentOS, Does anyone know if there's a driver out there that'll enable CentOS 4.x to use the Intel Matrix SATA RAID settings on the 915 chipsets? -- Best regards, Mickael mailto:mike at kamloopsbc.com www.MickaelMaddison.com