kernel panic with a new kernel (V2.6.2)

xround · 05-25-2004, 11:16 AM

Hello,

I have problems when I try to boot on the new kernel I have built, so that I can use hyperthreading, and acpi on my inspiron 5150. I get the following message :

VFS: Cannot open root device "LABEL=/" or unknown block (0,0)
Please append a correct "root= " boot option.
KErnel panic VFS : unable to mmount root fs on unknown block (0,0).

I have tried with 2 versions, the last being kernel 2.6.2 (may be rather old from now on).
But I always have the same root device problem.

I use grub to boot. And I have built and installed a /boot partition.

While building the Kernel, I had some few surprises:
First, "make dep" told me there was nothing to be done (or something like this).
Otherwise, I had many warnings in my modules.err file while doing the command
"nohup make modules 1> modules.out 2> modules.err"
Here they are:

drivers/ide/legacy/ide-cs.c: Dans la fonction Â« ide_config Â»:
drivers/ide/legacy/ide-cs.c:364: AVERTISSEMENT: Â« MOD_INC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:488)
drivers/ide/legacy/ide-cs.c: Dans la fonction Â« ide_release Â»:
drivers/ide/legacy/ide-cs.c:410: AVERTISSEMENT: Â« MOD_DEC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:500)
drivers/ide/pci/serverworks.c: Dans la fonction Â« svwks_init_one Â»:
drivers/ide/pci/serverworks.c:804: AVERTISSEMENT: Â« MOD_INC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:488)
drivers/ide/pci/siimage.c: Dans la fonction Â« siimage_init_one Â»:
drivers/ide/pci/siimage.c:1171: AVERTISSEMENT: Â« MOD_INC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:488)
drivers/ide/pci/sis5513.c: Dans la fonction Â« sis5513_init_one Â»:
drivers/ide/pci/sis5513.c:956: AVERTISSEMENT: Â« MOD_INC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:488)
drivers/ide/pci/slc90e66.c: Dans la fonction Â« slc90e66_init_one Â»:
drivers/ide/pci/slc90e66.c:376: AVERTISSEMENT: Â« MOD_INC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:488)
drivers/ide/pci/triflex.c: Dans la fonction Â« triflex_init_one Â»:
drivers/ide/pci/triflex.c:227: AVERTISSEMENT: Â« MOD_INC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:488)
drivers/ide/pci/trm290.c: Dans la fonction Â« init_hwif_trm290 Â»:
drivers/ide/pci/trm290.c:378: AVERTISSEMENT: Â« check_region Â» est déprécié (déclaré Ã_ include/linux/ioport.h:119)
drivers/ide/pci/trm290.c: Dans la fonction Â« trm290_init_one Â»:
drivers/ide/pci/trm290.c:406: AVERTISSEMENT: Â« MOD_INC_USE_COUNT Â» est déprécié (déclaré Ã_ include/linux/module.h:488)
drivers/input/gameport/ns558.c: Dans la fonction Â« ns558_isa_probe Â»:
drivers/input/gameport/ns558.c:80: AVERTISSEMENT: Â« check_region Â» est déprécié (déclaré Ã_ include/linux/ioport.h:119)
drivers/input/gameport/ns558.c:121: AVERTISSEMENT: Â« check_region Â» est déprécié (déclaré Ã_ include/linux/ioport.h:119)
drivers/usb/media/pwc-if.c: Dans la fonction Â« pwc_video_release Â»:
drivers/usb/media/pwc-if.c:1124: AVERTISSEMENT: contrôle a atteint la fin non void de la fonction
drivers/usb/media/pwc-if.c: Dans la fonction Â« usb_pwc_probe Â»:
drivers/usb/media/pwc-if.c:1855: AVERTISSEMENT: affectation d'un type pointeur incompatible

Please help me for this problem. Cheers, Xround.

Here is the part of my "grub.conf" file :

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,4)
# kernel /vmlinuz-version ro root=/dev/hdc7
# initrd /initrd-version.img
#boot=/dev/hdc
default=0
timeout=5
splashimage=(hd0,4)/grub/splash.xpm.gz
# To boot Linux
title Red Hat Linux-up (2.4.20-8)
root (hd0,4)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hda=ide-scsi
initrd /initrd-2.4.20-8.img

# To boot Linux
title Red Hat Linux-up (2.6.2 20 Mai 2004)
root (hd0,4)
kernel /bzImage-2.6.2.200504 ro root=LABEL=/ hda=ide-scsi
initrd /initrd-2.6.2.200504.img

# To boot Linux
title Red Hat Linux-up (2.4.20-8) New Kernel
root (hd0,4)
kernel /vmlinuz-new ro root=/dev/hdc7 hda=ide-scsi
initrd /initrd-2.4.20-8.img

# To boot Linux
#title Red Hat Linux (2.4.20-8smp)
# root (hd0,4)
# kernel /vmlinuz-2.4.20-8smp ro root=LABEL=/ hda=ide-scsi
# initrd /initrd-2.4.20-8smp.img

Mara · 05-25-2004, 03:58 PM

The error you get usually happens when you forget to include support for the filesystem used on your / partition. Check this.

xround · 05-26-2004, 09:16 AM

Thanks you Mara, I didn't check that in my ".config" file and I may have not configured it well!

I checked some settings, in my ".config" file and I have further questions concerning it, so let me recall that my hardware is an inspiron 5150 DELL laptop which CPU is set to 3.05 Ghz and supports hyperthreading, and a 15 inches screen. I have installed the vesa drivers for my NVIDIA GEFORCE Go 5200 chipset.
I want to solve ACPI problem, SMP problem, and display problems. I don't know if I should or not open a new thread because I will now speak about related problems.

First let come back to the main problem of this thread.

Quote:

1) File systems settings

Here is what I have in file systems section CONFIG_EXT3_FS should be set to "y" I guess.

Code:

#
# File systems
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=m
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_JFS_FS=m
# CONFIG_JFS_POSIX_ACL is not set
CONFIG_JFS_DEBUG=y
# CONFIG_JFS_STATISTICS is not set
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_QUOTA=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

Do I need other tings ? Can I avoid some "m" or "y" settings in this section ?

Quote:

2) SCSI settings

As I don't know why my "grub.conf" was built on my 1st "redhat 9" install with the argument
"hda=ide-scsi", I would like to be sure if I need or not the SCSI device support, as:

Code:

#
# SCSI device support
#
# CONFIG_SCSI is not set

Do I have to change this parameter also ??
A further question is: why does grub uses "hda" (or hd0) to load when the "system monitor" window tells me linux recognizes my hard drive as /dev/hdc ??

Quote:

3) Using the ".config" file

I got my ".config" file from the first (failing) kernel I built to compile the 2.4.20-8 version.
I read somewhere I think in the native documentation of a kernel release that I should not edit
this ".config" file. I did modify this .config in order to change SMP settings and other parameters.
As "make xconfig" was not ok with the 2.6.2 version,I decided to modify the .config and then run the
"make oldconfig" insread of a complete configuration with "make config" that avoids time consuming!
Is it a problem ? What should I try else ?

Quote:

4) Compilation problems

Can the "warnings" be erased from the "make module_install" command ?
Why make dep tells me there is nothing to be done. Is it normal ?

Quote:

5) ACPI Problem.

I the following parameters in the "Power management options" and "ACPI Support" sections:

Code:

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DISK is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_ACPI_RELAXED_AML=y

I have the same question. Is it ok ? Shoud I avoid some "m" answers ??

Quote:

6) The SMP configuration.

I have found 4 parameters that seem to be related with SMP :
CONFIG_X86_BIGSMP,
CONFIG_SMP,
CONFIG_X86_FIND_SMP_CONFIG, and
CONFIG_X86_SMP.

In "Processor type and features", I set the following:

Code:

CONFIG_X86_PC=y
# CONFIG_X86_BIGSMP is not set
CONFIG_SMP=y

In "Kernel hacking", I set

Code:

CONFIG_X86_FIND_SMP_CONFIG=y

Finally in "Library routines", I set

Code:

CONFIG_X86_SMP=y

Is it OK ?

Quote:

7) Display Problem.

Under X, some lines are blur while others are well displayed in any editor I can use "XEmacs", "xterm" or my Internet browser. Here are my display settings.

Code:

Monitor type : DELL 1400x1050 Laptop Display Panel
Degree of horizontal refreshment: 31.5-90.0
Rate of vertical refreshment: 59.0-75.0
physical resolution: 117 X 116 points per inch

Video type: vesa driver (generic)
Memory size: 64MB
Disk: vesa

Can I improve this?

Finally I must apologize first for all these questions, but they seem to be important for me to improve my knowledge and ... let my linux work. I must admit I may have not read deeply all the related documentation. Secondly English is not my mother tongue some I may make mistake for some words.

Cheers, Xround.

Mara · 05-26-2004, 04:13 PM

Quote:

Originally posted by xround
I don't know if I should or not open a new thread because I will now speak about related problems.

Keeping new questions here is a good idea especially because they're closely related with the previous one.

Quote:

Here is what I have in file systems section CONFIG_EXT3_FS should be set to "y" I guess.

Do I need other tings ? Can I avoid some "m" or "y" settings in this section ?

If you're using Ext3, you should have it set to 'y' (you have initrd, so it may be also 'm', but 'y' is safer).
If you don't have Reiser or JFS and don't plan to insert disks with such filesystems, you can say 'no' to them. But you should think about it carefully. They may be useful one day, so I suggest at least one 'm' - to Reiser.

Quote:

As I don't know why my "grub.conf" was built on my 1st "redhat 9" install with the argument
"hda=ide-scsi", I would like to be sure if I need or not the SCSI device support, as:

Do I have to change this parameter also ??
A further question is: why does grub uses "hda" (or hd0) to load when the "system monitor" window tells me linux recognizes my hard drive as /dev/hdc ??

Interesting...It looks you have your disk connected as primary slave drive (so it's hdc). You probably have a cd burner in your machine and then it'll probably be hda (primary master, it's all about cables). If you want to use the burner to burn cds, you should keep the option (hda=ide-scsi) and add SCSI support (SCSI support plus IDE SCSI emulation). In Linux, cd buners, SATA disks and many other devices are used as SCSI (they don't have to be 'realy' SCSI, emulation is used instead - SCSI devices are just easy to program).

Quote:

I got my ".config" file from the first (failing) kernel I built to compile the 2.4.20-8 version.
I read somewhere I think in the native documentation of a kernel release that I should not edit
this ".config" file. I did modify this .config in order to change SMP settings and other parameters.
As "make xconfig" was not ok with the 2.6.2 version,I decided to modify the .config and then run the
"make oldconfig" insread of a complete configuration with "make config" that avoids time consuming!
Is it a problem ? What should I try else ?

Maybe "make menuconfig" ? Editing the .config file may be dangerous, but if you know what you're doing it shouldn't be a big problem.

Quote:

Can the "warnings" be erased from the "make module_install" command ?
Why make dep tells me there is nothing to be done. Is it normal ?

With kernel 2.6 it's probably possible to get nothing from make dep. The warnings I see (don't know French

look like standrad ones (you always get warnings when compiling a kernel), nothing to be scard of.

Quote:

I the following parameters in the "Power management options" and "ACPI Support" sections:

I have the same question. Is it ok ? Shoud I avoid some "m" answers ??

You have a laptop, so ptobably all the features will be in use...

Quote:

I have found 4 parameters that seem to be related with SMP :
CONFIG_X86_BIGSMP,
CONFIG_SMP,
CONFIG_X86_FIND_SMP_CONFIG, and
CONFIG_X86_SMP.

Is it OK ?

I'd change 'n' to the one in 'Kernel hacking' - options in that sections are generally not for normal use

All others are probably OK, but you should check in make menuconfig or so.

Quote:

Under X, some lines are blur while others are well displayed in any editor I can use "XEmacs", "xterm" or my Internet browser. Here are my display settings.

Code:

Monitor type : DELL 1400x1050 Laptop Display Panel
Degree of horizontal refreshment: 31.5-90.0
Rate of vertical refreshment: 59.0-75.0
physical resolution: 117 X 116 points per inch

Video type: vesa driver (generic)
Memory size: 64MB
Disk: vesa

Can I improve this?

You can. First step may be to check the 'nv' driver. It probably supports your graphic card. You can also use Nvidia's one, downloadable from www.nvidia.com (your card is on the list).

Quote:

Finally I must apologize first for all these questions, but they seem to be important for me to improve my knowledge and ... let my linux work. I must admit I may have not read deeply all the related documentation. Secondly English is not my mother tongue some I may make mistake for some words.

No problem, we are here to answer questions...
Your English is very good. I's not my mother tongue, either

You're perfectly understandable.

xround · 05-27-2004, 09:19 AM

Thanks again Mara, for your advice and your "congratulations concerning my english speaking or writing".
Finally I succeeded, booting with my kernel. With another kernel compiled with the more comfortable interface provided with "make menuconfig" command, I first couldn't boot. But I could change the parameters easily. For the filesystem section, I have now:

Code:

CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_REISERFS_FS=m

and all the others filesystems "not set".

Your (Mara) explanation concerning the way my hard drive and cdrom-writer were connected comforted me. And an advice in another thread I guess, telling the "root=LABEL=/" was not always understood during the boot process, let me do some few tests. In fact I have
/boot partition on /dev/hdc5
/ (root) partition on /dev/hdc7
I made the /boot partition in order to avoid a 1024 cylinder limit problem, as my / (root) partition goes beyond the 1024th cylinder. Even though I am not sure it is still a problem, and it could solve this problem.

However after few tests the following settings succeeded:

Code:

 
# To boot Linux
title Red Hat Linux-up (2.6.2 26 mai 2004) r-hd0 k-hdc7
        root (hd0,4)
        kernel /bzImage-2.6.2.2004mai26 ro root=/dev/hdc7 hda=ide-scsi
        initrd /2.6.2-2004.05.26.img

First it was not ok, and I had a message that said something like "try another init". So as I remembered I did not do the job exactly as it was mentioned in the KERNEL-HOWTO document in order to create my "2.6.2-2004.05.26.img" file, I did it exactly the same commands :

Code:

> cd /lib/modules
> ls -al 2.6.2*
drwxr-xr-x    3 root     root         4096 mai 26 06:55 	2.6.2-2004.05.26
...
> mkinitrd ./2.6.2-2004.05.26.img 2.6.2-2004.05.26
> cp 2.6.2-2004.05.26.img /boot

And I got a file that was not exactly the same size than the first mkinitrd I created.

Code:

> cd /boot
> ls -al *2.6.2*.img
-rw-r--r--    1 root     root        84477 mai 26 13:14 2.6.2-2004.05.26.img
-rw-r--r--    1 root     root        85654 mai 26 07:09 initrd-2.6.2.2004mai26.img

I had created the "initrd-2.6.2.2004mai26.img", doing:

Code:

> cd /lib/modules
> ls -al 2.6.2*
drwxr-xr-x    3 root     root         4096 mai 26 06:55 	2.6.2-2004.05.26
...
> mkinitrd initrd-2.6.2.2004mai26.img 2.6.2-2004.05.26
> cp initrd-2.6.2.2004mai26.img /boot

Is there a reason ? Or I may have made a mistake!
However, my new image is ok!!
Not completely because of other problems I will set out in the next post, but the boot process problem may be solved now!!

Thank you again. Cheers, Xround.

Mara · 05-27-2004, 04:26 PM

The only differences when creating initrd images were filenames and usage of ./ in the first one. I don't know why they're of different size...The only explanation is that there was a change in modules, but I don't know. It shouldn't be caused just by different filenames..

xround · 05-27-2004, 05:06 PM

Hello, again
I think that ACPI doesn't work, and concerning SMP, it may give problems, but it seems to be better.

Before dealing with my results, I would like to know more about differences between distributions.
Indeed, I am a bit lost with problems concerning distributions, I have installed the RedHat 9 few months ago.
Some guys at
http://www.livejournal.com/community/linux/528423.html
said a Redhat 9 should support ACPI and SMP (but they didn't try it), but others at
http://forums.us.dell.com/supportfor...message.id=542
say that one should install Fedora Core 2, Gentoo X.X.X or an FTP install of SUSE 9.0 !
Is it really a "distribution" problem ? Or rather a kernel update ?
Does anyone know about it ?

Dell Inspiron with broken BIOS detected. Refusing to enable the local APIC.

Now let go with the results.

Quote:

Results 1) SMP

Fisrt the smp seems to be ok, regarding the /proc/cpuinfo file, that gives

Code:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Mobile Intel(R) Pentium(R) 4     CPU 3.06GHz
stepping        : 9
cpu MHz         : 3057.003
cache size      : 512 KB
physical id     : 0
siblings        : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 6045.69
 
processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Mobile Intel(R) Pentium(R) 4     CPU 3.06GHz
stepping        : 9
cpu MHz         : 3057.003
cache size      : 512 KB
physical id     : 0
siblings        : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 6094.84

Before, I had only "processor 0".And this seems to be rather similar to the proc_cpuinfo.txt of a guy who succeeded in enabling SMP support, see

http://www.linuxforum.com/forums/ind...howtopic=14120

Watching the "dmesg" information, I wonder if there are problems, that may be related to the BIOS:

Code:

Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 3056.0043 MHz.
..... host bus clock speed is 132.0871 MHz.
checking TSC synchronization across 2 CPUs:
BIOS BUG: CPU#0 improperly initialized, has -4805 usecs TSC skew! FIXED.
BIOS BUG: CPU#1 improperly initialized, has 4805 usecs TSC skew! FIXED.

What does it mean ? Does the "FIXED" information mean that the problem is solved ??

Quote:

Results 2) ACPI

This may be a problem because I have the following message in "dmesg" information.

Code:

Dell Inspiron with broken BIOS detected. Refusing to enable the local APIC.

And also some following messages:

Code:

ACPI: RSDP (v000 DELL                                      ) @ 0x000fdea0
ACPI: RSDT (v001 DELL    CPi R   0x27d30b03 ASL  0x00000061) @ 0x1fff0000
ACPI: FADT (v001 DELL    CPi R   0x27d30b03 ASL  0x00000061) @ 0x1fff0400
ACPI: MADT (v001 DELL    CPi R   0x27d30b03 ASL  0x00000047) @ 0x1fff0c00
ACPI: DSDT (v001 INT430 SYSFexxx 0x00001001 MSFT 0x0100000e) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ES7000: did not find Unisys ACPI OEM table!
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 2
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, IRQ 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI BALANCE SET

And just after

Code:

Enabling APIC mode:  Physical Cluster.  Using 1 I/O APICs, target cpus 1

What does it mean ? How can I check if ACPI is OK or not? Do I need a bios update as it is suggested?

Quote:

Results 3) Modules Not loading

I do not have yet well configured the modules, since some of them are not loaded. I have configured the bcm4400
for my kernel version 2.4.20, and it is not yet recognized. Do I have to reinstall this module?
I have several message concerning modules that fall for loading, I have noticed some but they load to quickly.
I think I use the /etc/module.conf, and all modules in it fall. But I think other fall also.
For instance, something like
"usb hid interface"
<failed> to load, and it does not appear in the /etc/modules.conf.

Do I have something to do with the symbolic link module-info in /boot directory? Here it is:

Code:

# ls -al module-info*
lrwxrwxrwx    1 root     root           20 dÃ©c 30 20:25 module-info -> module-info-2.4.20-8
-rw-r--r--    1 root     root        15436 mar 14  2003 module-info-2.4.20-8
-rw-r--r--    1 root     root        15436 mai 19 15:49 module-info-2.4.20-8.backup
#

So here it is. i have still problems, I probably don't have configured my kernel in the best way I should, but
improvement is on the way! Cheers, Xround.

Mara · 05-28-2004, 04:16 PM

Quote:

Originally posted by xround

Before dealing with my results, I would like to know more about differences between distributions.
Indeed, I am a bit lost with problems concerning distributions, I have installed the RedHat 9 few months ago.
Some guys at
http://www.livejournal.com/community/linux/528423.html
said a Redhat 9 should support ACPI and SMP (but they didn't try it), but others at
http://forums.us.dell.com/supportfor...message.id=542
say that one should install Fedora Core 2, Gentoo X.X.X or an FTP install of SUSE 9.0 !
Is it really a "distribution" problem ? Or rather a kernel update ?

Kernel update. For many people who can't (or don't want to) compile a new kernel installing a new distribution/version is the only way to get newer kernel.

Your SMP looks correct.

Quote:

Watching the "dmesg" information, I wonder if there are problems, that may be related to the BIOS:

What does it mean ? How can I check if ACPI is OK or not? Do I need a bios update as it is suggested?

It looks like ACPI in your machine doesn't work as the kernel expects it to. A short googling showed that it's a long-running problem and there's a work-around (I haven't found info that BIOS update doesn't help, but I also haven't found an evidence of the opposite... so you may try it if it's safe).

The work-around is to disable ACPI and use APM (passwing to kernel 'acpi=off apm=on').

Quote:

I do not have yet well configured the modules, since some of them are not loaded. I have configured the bcm4400
for my kernel version 2.4.20, and it is not yet recognized. Do I have to reinstall this module?
I have several message concerning modules that fall for loading, I have noticed some but they load to quickly.
I think I use the /etc/module.conf, and all modules in it fall. But I think other fall also.
For instance, something like
"usb hid interface"
<failed> to load, and it does not appear in the /etc/modules.conf.

Please try to load a module manually (as root):
modprobe modulename
Does it help or not? You can also try to run 'depmod -a' to build module dependencies.

xround · 08-10-2004, 08:17 AM

Hi, a long time I ve been here.

No response, from now on, since I had other stuff to do. Hope you (Mara) won't feel hurt about this. I tried few things these days. I am on my desktop, so it won't be so easy to give you informations concerning the laptop, now since I cannot mount my usb floppy drive !

First using modprobe uhci-hcd, I can use my usb mouse. But how can I fix it so that it mounts automatically. For information, I do not start under graphic mode. I don't know if it can be a problem, but I prefer telling more than not enough.

Secondly, I finally reinstalled my bcm4400 broadcom ethernet controller for the kernel 2.6.2. It seems to be recognized, because it appears in the hardware browser. But I am connected via Internet with an usb modem relied to my desktop, and as I have not yet configured my local network ( that will be only my desktop and my laptop connected with an ethernet cable), I cannot reach easily information from my laptop. Forgive me about this.

Finally, a
"modprobe -l"
tells me many modules can be loaded. Some are related to the sound. They are located in the folders "drivers" "core" and "pci" in the directory :
"/lib/modules/mykernel2.6.2/kernel/sound".
A test to detect my sound card always fails, telling me the i810_audio is not loaded.
A "locate i810_audio" gives me no "i810_audio.o" (or .ko) in the folder
"/lib/modules/mykernel2.6.2/kernel/drivers/sound".
But a "i810_audio.o" occurs in the corresponding folder of "mykernel2.4.2", where the sound card is ok. How can I solve this problem ?

Cheers, xround.

xround · 08-11-2004, 12:20 PM

Please, does anybody habve an idea concerning audio modules, and getting permanent config for modules ?

Cheers, xround

comprookie2000 · 08-11-2004, 04:27 PM

With the 2.4 kernel it was most likely set up for oss [open sound system] the 2.6 kernel most likely will use alsa,it works better for me.http://www.google.com/search?q=red+h...n&lr=&ie=UTF-8