Bug#477233: linux-image-2.6.26-1-amd64: Got *my* problem solved meanwhile
Package: linux-image-2.6.26-1-amd64 Followup-For: Bug #477233 Meanwhile I got the problem fixed on my machine. I still don't understand why, because the final steps to solve it are the same I tried out already before filing my other response, but then without solving it. The problem on my machine occured after an upgrade from Etch to Lenny, so after changing the kernel from 2.6.18-6-amd64 to 2.6.26-1-amd64. The impact was, that even with all the good looking stuff in /proc/asound I couldn't hear anything from the speakers. Today I tried again, running alsaconf in a terminal window. First all other sound apps were killed, then alsaconf detected an ICH6 sound card and configured it. At the end of the configuration I heard at least a click from the speakers. Executing playsound with a Wave file (e.g. from gnome-audio packet) then played the sound. Restarting KDEs sound system then also was able to play the KDE sounds and finally this also survives a complete reboot cycle. So I guess my problem is solved, but since I already tried out alsaconfig once without luck I'm still wondering what was different this time. Thanks for your attention. Rainer -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#477233: linux-image-2.6.26-1-amd64: Still there on 2.6.26-1-amd64 after upgrade from Etch to Lenny
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Followup-For: Bug #477233 -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: root=/dev/mapper/vg-lv--root ro ** Tainted: P (1) ** Kernel log: [ 11.335388] parport_pc 00:0b: assigning independent options [ 11.335388] parport_pc 00:0b: assigning dependent option 2 [ 11.335388] parport_pc 00:0b: assign io 0 0x278-0x27b [ 11.335388] parport_pc 00:0b: assign irq 0 5 [ 11.335388] parport_pc 00:0b: current resources: after pnp_assign_resources [ 11.335388] parport_pc 00:0b: irq 5 flags 0x4401 [ 11.335388] parport_pc 00:0b: io 0x278-0x27b flags 0x4101 [ 11.335388] parport_pc 00:0b: current resources: pnp_start_dev [ 11.335388] parport_pc 00:0b: irq 5 flags 0x4401 [ 11.335388] parport_pc 00:0b: io 0x278-0x27b flags 0x4101 [ 11.335388] parport_pc 00:0b: set resources [ 11.336003] parport_pc 00:0b: encode 2 resources [ 11.336008] parport_pc 00:0b: encode io 0x278-0x27b decode 0x1 [ 11.336013] parport_pc 00:0b: encode irq 5 edge high exclusive (2-byte descriptor) [ 11.336297] parport_pc 00:0b: activated [ 11.336372] parport_pc 00:0b: reported by Plug and Play ACPI [ 11.336470] parport0: PC-style at 0x278, irq 5 [PCSPP,EPP] [ 11.432053] parport_pc 00:0b: driver attached [ 11.432071] parport_pc 00:0c: reported by Plug and Play ACPI [ 11.432265] parport_pc 00:0c: disabled [ 13.229689] Adding 3004112k swap on /dev/sda5. Priority:-1 extents:1 across:3004112k [ 13.649349] EXT3 FS on dm-0, internal journal [ 14.258224] loop: module loaded [ 15.438531] kjournald starting. Commit interval 5 seconds [ 15.438531] EXT3 FS on sda1, internal journal [ 15.438531] EXT3-fs: mounted filesystem with ordered data mode. [ 15.500553] kjournald starting. Commit interval 5 seconds [ 15.500553] EXT3 FS on dm-1, internal journal [ 15.500553] EXT3-fs: mounted filesystem with ordered data mode. [ 19.141802] tg3: eth1: Link is up at 100 Mbps, full duplex. [ 19.141802] tg3: eth1: Flow control is off for TX and off for RX. [ 21.253133] NET: Registered protocol family 10 [ 21.253133] lo: Disabled Privacy Extensions [ 25.397973] lp0: using parport0 (interrupt-driven). [ 25.451563] ppdev: user-space parallel port driver [ 31.975230] warning: `ntpd' uses 32-bit capabilities (legacy support in use) [ 32.453045] eth1: no IPv6 routers present [ 34.103881] Bluetooth: Core ver 2.11 [ 34.105238] NET: Registered protocol family 31 [ 34.105238] Bluetooth: HCI device and connection manager initialized [ 34.105238] Bluetooth: HCI socket layer initialized [ 34.180015] Bluetooth: L2CAP ver 2.9 [ 34.180015] Bluetooth: L2CAP socket layer initialized [ 34.313249] Bluetooth: RFCOMM socket layer initialized [ 34.313249] Bluetooth: RFCOMM TTY layer initialized [ 34.313249] Bluetooth: RFCOMM ver 1.8 [ 42.970134] nvidia: module license 'NVIDIA' taints kernel. [ 43.227290] ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 16 [ 43.227307] PCI: Setting latency timer of device :01:00.0 to 64 [ 43.227463] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 173.14.09 Wed Jun 4 23:40:50 PDT 2008 [ 1071.066021] bacula-console-[15949] trap divide error ip:7f96ea5f2d58 sp:7427e180 error:0 in libwx_baseu-2.6.so.0.3.1[7f96ea567000+123000] [ 2180.128171] usb 5-1: new high speed USB device using ehci_hcd and address 2 [ 2180.363058] usb 5-1: configuration #1 chosen from 1 choice [ 2180.380149] usb 5-1: New USB device found, idVendor=1307, idProduct=0165 [ 2180.380160] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2180.380166] usb 5-1: Product: USB Mass Storage Device [ 2180.380170] usb 5-1: Manufacturer: USBest Technology [ 2180.380174] usb 5-1: SerialNumber: 00030A [ 2180.479223] Initializing USB Mass Storage driver... [ 2180.479223] scsi2 : SCSI emulation for USB Mass Storage devices [ 2180.482220] usb-storage: device found at 2 [ 2180.482220] usb-storage: waiting for device to settle before scanning [ 2180.479223] usbcore: registered new interface driver usb-storage [ 2180.479223] USB Mass Storage support registered. [ 2186.100527] usb-storage: device scan complete [ 2186.103539] scsi 2:0:0:0: Direct-Access UDISKPDU01-2G 88H2.0 0.00 PQ: 0 ANSI: 2 [ 2186.104519] sd 2:0:0:0: [sdb] 3948544 512-byte hardware sectors (2022 MB) [ 2186.104519] sd 2:0:0:0: [sdb] Write Protect is off [ 2186.104519] sd 2:0:0:0: [sdb] Mode Sense: 00 00 00 00 [ 2186.104519] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 2186.108521] sd 2:0:0:0: [sdb] 3948544 512-byte hardware sectors (2022 MB) [ 2186.108521] sd 2:0:0:0: [sdb] Write Protect is off [ 2186.108521] sd 2:0:0:0: [sdb] Mode Sense: 00 00 00 00 [ 2186.108521] sd 2:0:0:0: [sdb] Assuming drive cache: write through [
Question on driver availability / backports
Hi, quick introduction of myself: The guy that is repsonsible to bring Linux on the desktop PCs at Fujitsu Siemens Computers. Now my question: I tried to install the latest Lenny netinstall snapshot on our current destkop models today, but unfortunately this snapshot is missing the support for the Intel Boazman LAN in e1000e. Boazman is device ID 8086:10df. Yes, I understand the issues of freezes and that Lenny will come with a 2.6.26 kernel that doesn't support this device. So my concern is about how I can support our customers that still want to use Debian on actual PC hardware. So a few questions, I hope that this mailing list is the correct one to ask this: 1. Is there a sort of driver backport group that takes care of such issues? Or is the concept behind debian to move forward to newer kernels to obtain hardware support? 2. Is there a mechanism to replace drivers during installation. Imagining I would get a working e1000e module somehow I still would need to make it usable on the installation process, at the moment all I can think of is adding it by hand to the proper modules/../updates directory and inserting it by hand. Looks not like an easy to use setup. :-) Ok, maybe this is more for the debian-boot mailing list, is it? Please don't take this as a negative feedback. I'm very fond of Debian, and I would even volunteer to help on those issues somehow. Its sad to see that if Lenny will be released it will be too old for actual PC hardware already. Best regards Rainer -- Dipl.-Inf. (FH) Rainer Koenig -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: How do I build a XEN kernel with make-kpkg
Goswin von Brederlow [EMAIL PROTECTED] writes: The debian patch package is incompatible to make-kpkg. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382699 Thanks a lot. With this information I succeeded in building my PAE kernel. Regards Rainer -- Dipl.-Inf. (FH) Rainer Koenig -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How do I build a XEN kernel with make-kpkg
Hi there, let me start describing my problem: - Hardware is Dual Xeon workstation with 16 GB RAM - I run Debian/testing on it - The machine acts as a small laboratory server for testing purposes - One goal is to run XEN on it and to use paravirtualized guests like e.g. RHEL4 so that I can use the RHEL4 hwtest-server (for hardware certification issues) in a native enivornment. Starting from that point I installed the XEN hypervisor and the linux-image-2.6.18-3-xen-686 image. That gave me the first problem: In this setup I can only use 4 GB of the 16 GB my machine has, so this is not satisfying. Next try: Reading the package descriptions I found the xen hpyervisor is also available as a PAE enabled package for machines that have more than 4 GB of RAM. I installed that and ran into the next problem: The hpyervisor starts, but then I get a PAE mode mismatch error (xen=yes dom0=no) and the system reboots. Ok, I've learned from this that it would be better to have a PAE enabled XEN kernel, but since there are no packages out there I need to do it my own. Next try: Reading the chapter in the book of Martin Krafft about building Debian kernels with make-kpkg. Trying that out, by getting the linux-source package for 2.6.18, copying the config from the xen kernel, enabling 64 GB support and building the kernel. No, this one doesn't boot with the hypervisor since its not XEN enabled. Ok. Next try. Finding some sort of HowTos on the net, one describing that I need the XEN source package that applies patches to the kernel and then compile it. Whatever I do with 2.6.18 the kernel build process exits with errors that show me that something is very wrong in the kernel source tree. So I'm stuck, but I wonder: There IS a package linux-image-2.6.18-3-xen-686 so it SHOULD be possible to build such an image. But HOW can I do that? Is there any sort of magic spell that I have to say before building it or am I just missing an important point? On the other hand: I think there is really a need for PAE enabled XEN kernels since every guest kernel you can download at XenSource or whatever you get on installation media from SUSE or Red Hat ships with PAE enabled kernels. Even trying to install a Fedora Core system by using the defaults from xenman fails with a strange error -22 that (after some usage of Google) seems to be caused by the attempt to use a PAE enabled domU on a non-PAE dom0. With that restrictions using XEN on Debian is everything else but fun. Best regards, a happy new year and TIA for all the hints Rainer -- Dipl.-Inf. (FH) Rainer Koenig, Augsbur, Germany -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
