error inserting ramzswap: invalid module format
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I've installed the system without any swap on the md RAID0 array and get this error message every time I boot:
FATAL: error inserting ramzswap (/lib/modules/
(I've removed plymouth themes so I can see the boot text every time)
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 45'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,
Controls : 12
Simple ctrls : 7
Date: Sun Aug 7 20:02:30 2011
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: ASUSTeK Computer INC. 901
ProcEnviron:
LANG=uk_UA.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.56
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1603
dmi.board.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 901
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
This looks like a duplicate of bug 832694 so I am marking it as such. Please continue to track this issue at that report. Thanks.